
From mcr@sandelman.ca  Tue Oct  1 11:29: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 A848B11E821A; Tue,  1 Oct 2013 11:29: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 57BEcf2yb0vy; Tue,  1 Oct 2013 11:29:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id AB5CA11E8211; Tue,  1 Oct 2013 11:29:45 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6ED4E20168; Tue,  1 Oct 2013 15:39:14 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id C99A463B18; Tue,  1 Oct 2013 14:29:24 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B8CF2636C7; Tue,  1 Oct 2013 14:29:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org, tools-discuss@ietf.org
Subject: independant submissions that update standards track, and datatracker
In-Reply-To: <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt>
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: Tue, 01 Oct 2013 14:29:24 -0400
Message-ID: <11884.1380652164@sandelman.ca>
Sender: 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: Tue, 01 Oct 2013 18:29:47 -0000

--=-=-=


This morning I had reason to re-read parts of RFC3777, and anything
that updated it.  I find the datatracker WG interface to really be
useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
first.  I guess I could have instead gone to:
   http://www.rfc-editor.org/info/rfc3777

but frankly, I'm often bad with numbers, especially when they repeat...
(3777? 3737? 3733?)

While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
in that line, it lists the things that update it, it doesn't actually list
the other documents.  Thinking this was an error, I asked, and Cindy kindly
explained:

>http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
>published by the NOMCOM Working Group.  The NOMCOM Working Group was
>open from 2002-2004, and only produced one RFC, which is RFC 3777.
>
>The RFCs that update 3777 were all produced by individuals (that is,
>outside of the NOMCOM Working Group), and so aren't listed individually
>on the NOMCOM Working Group documents page.

I wonder about this as a policy.

Seeing the titles of those documents would have helped me find what I wanted
quickly (RFC5680 it was)...

While I think that individual submissions that are not the result of
consensus do not belong on a WG page.  But, if the document was the result of
consensus, but did not occur in a WG because the WG had closed, I think that
perhaps it should appear there anyway.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUksUhIqHRg3pndX9AQLoRgP+Nmzc4ZVIhUPKYe8ju3FMmRYmrbpFPZoV
xADZUznz1zNvliLQ+8BdFPJda3OloLtM+vOZ1JRvLsj0L7eRx7sHynKnaI3QG9jS
otOkNpnwAtVnd6/8sbpsuPYGotCB82C6XISJZO0VGFBTtFnUTZmuDG5Ae2fZP97H
HyFhJQdumNM=
=uhW+
-----END PGP SIGNATURE-----
--=-=-=--

From adrian@olddog.co.uk  Tue Oct  1 11:36:08 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 B582611E821E; Tue,  1 Oct 2013 11:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  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 hzQSj9yb5LKU; Tue,  1 Oct 2013 11:36:04 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF8E21E805F; Tue,  1 Oct 2013 11:35: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 r91IZtPR023160;  Tue, 1 Oct 2013 19:35:55 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r91IZsxJ023154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 1 Oct 2013 19:35:55 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Michael Richardson'" <mcr+ietf@sandelman.ca>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca>	<rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca>
In-Reply-To: <11884.1380652164@sandelman.ca>
Subject: RE: independant submissions that update standards track, and datatracker
Date: Tue, 1 Oct 2013 19:35:54 +0100
Message-ID: <001701cebed5$104b87e0$30e297a0$@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: AQJAvZSZWOmuV4jo97NkkYR/9subcAJpQiu3AhNrUvMCdkRQs5jElyPA
Content-Language: en-gb
Cc: ietf@ietf.org, tools-discuss@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, 01 Oct 2013 18:36:08 -0000

Not to detract from your point, Michael, but
http://datatracker.ietf.org/doc/search/?name=nomcom&rfcs=on&sort= is pretty
good.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Michael Richardson
> Sent: 01 October 2013 19:29
> To: ietf@ietf.org; tools-discuss@ietf.org
> Subject: independant submissions that update standards track, and datatracker
> 
> 
> This morning I had reason to re-read parts of RFC3777, and anything
> that updated it.  I find the datatracker WG interface to really be
> useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
> first.  I guess I could have instead gone to:
>    http://www.rfc-editor.org/info/rfc3777
> 
> but frankly, I'm often bad with numbers, especially when they repeat...
> (3777? 3737? 3733?)
> 
> While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
> in that line, it lists the things that update it, it doesn't actually list
> the other documents.  Thinking this was an error, I asked, and Cindy kindly
> explained:
> 
> >http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
> >published by the NOMCOM Working Group.  The NOMCOM Working Group was
> >open from 2002-2004, and only produced one RFC, which is RFC 3777.
> >
> >The RFCs that update 3777 were all produced by individuals (that is,
> >outside of the NOMCOM Working Group), and so aren't listed individually
> >on the NOMCOM Working Group documents page.
> 
> I wonder about this as a policy.
> 
> Seeing the titles of those documents would have helped me find what I wanted
> quickly (RFC5680 it was)...
> 
> While I think that individual submissions that are not the result of
> consensus do not belong on a WG page.  But, if the document was the result of
> consensus, but did not occur in a WG because the WG had closed, I think that
> perhaps it should appear there anyway.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> 



From brian.e.carpenter@gmail.com  Tue Oct  1 12:14: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 CC2A411E8211; Tue,  1 Oct 2013 12:14:30 -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 evPAzbCha6IU; Tue,  1 Oct 2013 12:14:29 -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 BDB3C11E8229; Tue,  1 Oct 2013 12:14:28 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so7934066pad.0 for <multiple recipients>; Tue, 01 Oct 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:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UNhgdZgf4CC03TwBl+aWqWAeRyBX1F5Vf+RkCC6M1w0=; b=oKO/dBpBn9AU/YJQLBxkcDIKHZ9JsvUhKwUqnwOIpyqn2LilylLJK1yEqdqSRlCCqF VM3blF0wtLgfrGuWSUmZ1ZjPAaMc7ZFEMTH/gGYQbh28Ptli9EH1FV5oEjHiWuJFLABS QXBb2EazY2BX3A/apg+tTUktoMqEF9GSH98HxLF9PPGV5BQai3ZKzBqT3hC994t4PbVe UMp78YWipfe7L/ZFbkIDJk3YWxZnIZStHp9UdoEoxNrq7y/5f0qb+JWVCsDhj37cPn/p b1iWSx7Lf7+DC5ILREkqBHT8NLUNqz+oTJ/lg5OwEtQx6HPkb0VuKYwZ62/mQb1SfM7c /AVw==
X-Received: by 10.67.14.231 with SMTP id fj7mr35623868pad.115.1380654868440; Tue, 01 Oct 2013 12:14:28 -0700 (PDT)
Received: from [192.168.178.20] (180.194.69.111.dynamic.snap.net.nz. [111.69.194.180]) by mx.google.com with ESMTPSA id pu5sm9986629pac.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Oct 2013 12:14:27 -0700 (PDT)
Message-ID: <524B1F12.90103@gmail.com>
Date: Wed, 02 Oct 2013 08:14:26 +1300
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: adrian@olddog.co.uk
Subject: Re: independant submissions that update standards track, and datatracker
References: <RT-Ticket-59697@www.ietf.org/rt>	<12321.1380629642@sandelman.ca>	<rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt>	<11884.1380652164@sandelman.ca> <001701cebed5$104b87e0$30e297a0$@olddog.co.uk>
In-Reply-To: <001701cebed5$104b87e0$30e297a0$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Oct 2013 19:14:31 -0000

The place to go is definitely not the page for a closed WG. How can that
be expected to track things that happened after the WG closed?

Since it's a BCP, you get the lot at http://www.rfc-editor.org/info/bcp10
or http://www.rfc-editor.org/bcp/bcp10.txt.

In this particular case, you can also find it at
http://www.ietf.org/about/process-docs.html#anchor5

Regards
   Brian

On 02/10/2013 07:35, Adrian Farrel wrote:
> Not to detract from your point, Michael, but
> http://datatracker.ietf.org/doc/search/?name=nomcom&rfcs=on&sort= is pretty
> good.
> 
> Adrian
> 
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Michael Richardson
>> Sent: 01 October 2013 19:29
>> To: ietf@ietf.org; tools-discuss@ietf.org
>> Subject: independant submissions that update standards track, and datatracker
>>
>>
>> This morning I had reason to re-read parts of RFC3777, and anything
>> that updated it.  I find the datatracker WG interface to really be
>> useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
>> first.  I guess I could have instead gone to:
>>    http://www.rfc-editor.org/info/rfc3777
>>
>> but frankly, I'm often bad with numbers, especially when they repeat...
>> (3777? 3737? 3733?)
>>
>> While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
>> in that line, it lists the things that update it, it doesn't actually list
>> the other documents.  Thinking this was an error, I asked, and Cindy kindly
>> explained:
>>
>>> http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
>>> published by the NOMCOM Working Group.  The NOMCOM Working Group was
>>> open from 2002-2004, and only produced one RFC, which is RFC 3777.
>>>
>>> The RFCs that update 3777 were all produced by individuals (that is,
>>> outside of the NOMCOM Working Group), and so aren't listed individually
>>> on the NOMCOM Working Group documents page.
>> I wonder about this as a policy.
>>
>> Seeing the titles of those documents would have helped me find what I wanted
>> quickly (RFC5680 it was)...
>>
>> While I think that individual submissions that are not the result of
>> consensus do not belong on a WG page.  But, if the document was the result of
>> consensus, but did not occur in a WG because the WG had closed, I think that
>> perhaps it should appear there anyway.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>
> 
> 
> 

From ynir@checkpoint.com  Tue Oct  1 12:56:50 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 9233121E805F; Tue,  1 Oct 2013 12:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[AWL=0.001,  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 pejRLSZZNJLf; Tue,  1 Oct 2013 12:56:40 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 56B3F21E80C5; Tue,  1 Oct 2013 12:56:35 -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 r91JuX4K019528; Tue, 1 Oct 2013 22:56:33 +0300
X-CheckPoint: {524B28F1-B-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.30]) by IL-EX10.ad.checkpoint.com ([169.254.2.92]) with mapi id 14.02.0347.000; Tue, 1 Oct 2013 22:56:33 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: independant submissions that update standards track, and datatracker
Thread-Topic: independant submissions that update standards track, and datatracker
Thread-Index: AQHOvtRDzyxGS5cit0y+9EzWDqaODpngEMQA
Date: Tue, 1 Oct 2013 19:56:32 +0000
Message-ID: <F4A26C86-DC83-4559-B50A-B79F6413A26E@checkpoint.com>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca>
In-Reply-To: <11884.1380652164@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.231]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2156BF953F713E4C8316641CBEFB38B5@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<tools-discuss@ietf.org>" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Oct 2013 19:56:50 -0000

On Oct 1, 2013, at 9:29 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrot=
e:

>=20
> This morning I had reason to re-read parts of RFC3777, and anything
> that updated it.  I find the datatracker WG interface to really be
> useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
> first.  I guess I could have instead gone to:
>   http://www.rfc-editor.org/info/rfc3777
>=20
> but frankly, I'm often bad with numbers, especially when they repeat...
> (3777? 3737? 3733?)
>=20
> While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
> in that line, it lists the things that update it, it doesn't actually lis=
t
> the other documents.  Thinking this was an error, I asked, and Cindy kind=
ly
> explained:
>=20
>> http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
>> published by the NOMCOM Working Group.  The NOMCOM Working Group was
>> open from 2002-2004, and only produced one RFC, which is RFC 3777.
>>=20
>> The RFCs that update 3777 were all produced by individuals (that is,
>> outside of the NOMCOM Working Group), and so aren't listed individually
>> on the NOMCOM Working Group documents page.
>=20
> I wonder about this as a policy.
>=20
> Seeing the titles of those documents would have helped me find what I wan=
ted
> quickly (RFC5680 it was)=85

Like everything else in the IETF, there's a tools version for this as well:=
 http://tools.ietf.org/wg/nomcom/

You get the same list, but you also get the titles of those RFCs if you mou=
se over the links.



From mcr@sandelman.ca  Tue Oct  1 13:06:30 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 08FB321E826C; Tue,  1 Oct 2013 13:06:30 -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 AxSr2taHlthB; Tue,  1 Oct 2013 13:06:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 5396E21E808C; Tue,  1 Oct 2013 13:06:13 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5332020168; Tue,  1 Oct 2013 17:15:42 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1210963B18; Tue,  1 Oct 2013 16:05:51 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DD3BF636C7; Tue,  1 Oct 2013 16:05:51 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: independant submissions that update standards track, and datatracker
In-Reply-To: <524B1F12.90103@gmail.com>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <001701cebed5$104b87e0$30e297a0$@olddog.co.uk> <524B1F12.90103@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: Tue, 01 Oct 2013 16:05:51 -0400
Message-ID: <28669.1380657951@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: adrian@olddog.co.uk, ietf@ietf.org, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Oct 2013 20:06:30 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > The place to go is definitely not the page for a closed WG. How can that
    > be expected to track things that happened after the WG closed?

    > Since it's a BCP, you get the lot at http://www.rfc-editor.org/info/bcp10
    > or http://www.rfc-editor.org/bcp/bcp10.txt.

I think that you are right. We need to find ways to talk about BCP10
more frequently, rather than 3777.

--
]               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 mcr@sandelman.ca  Tue Oct  1 13:10:05 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 6B96011E8211; Tue,  1 Oct 2013 13:10:01 -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 lirPw1LSq4LW; Tue,  1 Oct 2013 13:09:53 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5BF11E822B; Tue,  1 Oct 2013 13:09:51 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0301220168; Tue,  1 Oct 2013 17:19:29 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id EB19463B18; Tue,  1 Oct 2013 16:09:38 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CAB12636C7; Tue,  1 Oct 2013 16:09:38 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: independant submissions that update standards track, and datatracker
In-Reply-To: <524B1F12.90103@gmail.com>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <001701cebed5$104b87e0$30e297a0$@olddog.co.uk> <524B1F12.90103@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: Tue, 01 Oct 2013 16:09:38 -0400
Message-ID: <29418.1380658178@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: adrian@olddog.co.uk, ietf@ietf.org, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Oct 2013 20:10:05 -0000

I note that neither:
  http://datatracker.ietf.org/wg/nomcom/

nor:
  http://datatracker.ietf.org/doc/search/?name=nomcom&rfcs=on&sort=

told me that 3777 was also BCP10 now.
(Even if 3777 wasn't BCP10 anymore, I think it would be useful for the
datatracker to tell me that it was part of BCP10, because I'll bet that 90%
of the time, I really want the latest info)

Although:
  http://www.rfc-editor.org/info/rfc3777

did point at BCP10, but just said "BCP10".  I think that perhaps
on that page, if it said, "BCP10 - IETF Nomination Process", that the
link would stand out better.

From kent@bbn.com  Tue Oct  1 14:08:14 2013
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E43011E8153; Tue,  1 Oct 2013 14:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.999
X-Spam-Level: 
X-Spam-Status: No, score=-103.999 tagged_above=-999 required=5 tests=[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 qOAmBccKHKGr; Tue,  1 Oct 2013 14:08:01 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id B9CE611E8211; Tue,  1 Oct 2013 14:07:51 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:51374) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1VR7AO-000E1G-W6; Tue, 01 Oct 2013 17:07:37 -0400
Message-ID: <524B3998.20009@bbn.com>
Date: Tue, 01 Oct 2013 17:07:36 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
References: <8D3D17ACE214DC429325B2B98F3AE712025DBB6FDA@MX15A.corp.emc.com> <5249BE21.4060702@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DBB7B41@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712025DBB7B41@MX15A.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------000001030905070006060701"
Cc: "sidr@ietf.org" <sidr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "stbryant@cisco.com" <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: Tue, 01 Oct 2013 21:08:14 -0000

This is a multi-part message in MIME format.
--------------000001030905070006060701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David,

Since this doc logically precedes the BGPsec design, I still think it's 
appropriate to
use PATHSEC here. But, we can add a sentence to connect the terms. I 
propose this modified text for the introduction:

*This document describes the security context in which PATHSEC is 
intended to operate. **(The term "PATHSEC" is employed in this document 
to refer to any design used to achieve the path security goal**described 
in the **SIDR WG charter. **The charter focuses on mechanisms**that will 
enable an AS to determine if the AS_path represented in a 
route**represents the path via which the NLRI traveled. Other SIDR 
documents use
the term "BGPsec" to refer to a specific design.) ...
*
The phrase "calls for" seems appropriate in the cache discussion. There 
is no MUST in the RFCs about using a local cache. The docs encourage RPs 
to maintain a local cache,
and 6481 states that not using one is "NOT RECOMMENDED."  All of the RP 
software of which
I am aware does so, but it is not an absolute requirement.

I think we've agreed that quoted is a static assertion and thus need not be
annotated to reflect more recent RFCs.

Steve





--------------000001030905070006060701
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 bgcolor="#FFFFFF" text="#000000">
    David,<br>
    <br>
    Since this doc logically precedes the BGPsec design, I still think
    it's appropriate to<br>
    use PATHSEC here. But, we can add a sentence to connect the terms. I
    propose this modified text for the introduction:<br>
    <br>
    <b>This document describes the security context in which PATHSEC is
      intended to operate.&nbsp; </b><b>(The term "PATHSEC" is employed in
      this document to refer to any design used to achieve the path
      security goal</b><b> described in the </b><b>SIDR WG charter. </b><b>The
      charter focuses on mechanisms</b><b> that will enable an AS to
      determine if the AS_path represented in a route</b><b> represents
      the path via which the NLRI traveled. Other SIDR documents use<br>
      the term "BGPsec" to refer to a specific design.) ...<br>
    </b><br>
    The phrase "calls for" seems appropriate in the cache discussion.
    There is no MUST in the RFCs about using a local cache. The docs
    encourage RPs to maintain a local cache, <br>
    and 6481 states that not using one is "NOT RECOMMENDED."&nbsp; All of the
    RP software of which<br>
    I am aware does so, but it is not an absolute requirement.<br>
    <br>
    I think we've agreed that quoted is a static assertion and thus need
    not be <br>
    annotated to reflect more recent RFCs.<br>
    <br>
    Steve<br>
    <br>
    <br>
    <br>
    <div class="WordSection1"><span
        style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p></o:p></span><span
        style="font-size:10.0pt;font-family:&quot;Courier New&quot;"></span><br>
    </div>
  </body>
</html>

--------------000001030905070006060701--

From david.black@emc.com  Tue Oct  1 18:13:34 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 1867221F9B07; Tue,  1 Oct 2013 18:13:34 -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=[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 SeH585Y0QfGp; Tue,  1 Oct 2013 18:13:19 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D069221F9AB4; Tue,  1 Oct 2013 18:13:15 -0700 (PDT)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r921Cnm4002397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Oct 2013 21:12:49 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r921Cnm4002397
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1380676370; bh=MJTc5QTgsDY+9DelFwb3PbvLbl8=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=SwCR6LIqFH+M2u72a0G5FEw+gvUOhfhQ+ff2hgdjMkqVgXYuhyd5/+EWtYaaHt0sa poMe9+M/7oGD8L+ZQZP+f41b6Bv30aFU+BB46dHp1tP93EYXlsgLYEyS2RQAXA+3/r FPuvODBe3uc10pIp864SkCx3PHRs5qrQBDPSrvsc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r921Cnm4002397
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd01.lss.emc.com (RSA Interceptor); Tue, 1 Oct 2013 21:12:37 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r921CarW021869 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 1 Oct 2013 21:12:37 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Tue, 1 Oct 2013 21:12:36 -0400
From: "Black, David" <david.black@emc.com>
To: Stephen Kent <kent@bbn.com>
Date: Tue, 1 Oct 2013 21:12:35 -0400
Subject: RE: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
Thread-Topic: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
Thread-Index: Ac6+6kZ659cHh6CITOajOWkx94Wf6gAIXwxA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712025DCE1852@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712025DBB6FDA@MX15A.corp.emc.com> <5249BE21.4060702@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DBB7B41@MX15A.corp.emc.com> <524B3998.20009@bbn.com>
In-Reply-To: <524B3998.20009@bbn.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_8D3D17ACE214DC429325B2B98F3AE712025DCE1852MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-EMM-GWVC: 1
X-EMM-McAfeeVC: 1
X-RSA-Classifications: public
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "sidr@ietf.org" <sidr@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "stbryant@cisco.com" <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: Wed, 02 Oct 2013 01:13:34 -0000

--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1852MX15Acorpemcc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Steve,

I think the modified introduction text suffices to connect the PATHSEC and =
BGPsec terms, but I don't think that referring to the SIDR WG charter for t=
he PATHSEC goals is reasonable - an RFC is an archive document, whereas a W=
G charter is not.

The explanation of "calls for" in the cache discussion is fine.

As I previously noted on the TCPMD5 reference:

Ok - I was suggesting adding an informative reference to RFC 2385, but this
is a nit, and so if the responsible AD is happy with omitting that referenc=
e
entirely, I don't have a problem.

Thanks,
--David

From: Stephen Kent [mailto:kent@bbn.com]
Sent: Tuesday, October 01, 2013 5:08 PM
To: Black, David
Cc: achi@cs.unc.edu; General Area Review Team (gen-art@ietf.org); stbryant@=
cisco.com; ietf@ietf.org; sidr@ietf.org
Subject: Re: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06

David,

Since this doc logically precedes the BGPsec design, I still think it's app=
ropriate to
use PATHSEC here. But, we can add a sentence to connect the terms. I propos=
e this modified text for the introduction:

This document describes the security context in which PATHSEC is intended t=
o operate.  (The term "PATHSEC" is employed in this document to refer to an=
y design used to achieve the path security goal described in the SIDR WG ch=
arter. The charter focuses on mechanisms that will enable an AS to determin=
e if the AS_path represented in a route represents the path via which the N=
LRI traveled. Other SIDR documents use
the term "BGPsec" to refer to a specific design.) ...

The phrase "calls for" seems appropriate in the cache discussion. There is =
no MUST in the RFCs about using a local cache. The docs encourage RPs to ma=
intain a local cache,
and 6481 states that not using one is "NOT RECOMMENDED."  All of the RP sof=
tware of which
I am aware does so, but it is not an absolute requirement.

I think we've agreed that quoted is a static assertion and thus need not be
annotated to reflect more recent RFCs.

Steve




--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1852MX15Acorpemcc_
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 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";
	color:black;}
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-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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Courier New"'>Steve,<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New"'>I think the modified intr=
oduction text suffices to connect the PATHSEC and BGPsec terms, but I don&#=
8217;t think that referring to the SIDR WG charter for the PATHSEC goals is=
 reasonable &#8211; an RFC is an archive document, whereas a WG charter is =
not.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;font-family:"Courier New"'>The explana=
tion of &#8220;calls for&#8221; in the cache discussion is fine.<o:p></o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family=
:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New"'>As I previously noted on t=
he TCPMD5 reference:<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal style=3D'text-indent:.5in'><span style=3D'font-size:1=
0.0pt;font-family:"Courier New"'>Ok &#8211; I was suggesting adding an info=
rmative reference to RFC 2385, but this<o:p></o:p></span></p><p class=3DMso=
Normal style=3D'text-indent:.5in'><span style=3D'font-size:10.0pt;font-fami=
ly:"Courier New"'>is a nit, and so if the responsible AD is happy with omit=
ting that reference<o:p></o:p></span></p><p class=3DMsoNormal style=3D'text=
-indent:.5in'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>en=
tirely, I don&#8217;t have a problem.<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;=
</o:p></span></p><div><div><p class=3DMsoNormal><span style=3D'font-size:10=
.0pt;font-family:"Courier New"'>Thanks,<br>--David</span><span style=3D'fon=
t-size:11.0pt;font-family:"Courier New"'><o:p></o:p></span></p></div></div>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:soli=
d blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;bord=
er-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal>=
<b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:=
windowtext'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Ta=
homa","sans-serif";color:windowtext'> Stephen Kent [mailto:kent@bbn.com] <b=
r><b>Sent:</b> Tuesday, October 01, 2013 5:08 PM<br><b>To:</b> Black, David=
<br><b>Cc:</b> achi@cs.unc.edu; General Area Review Team (gen-art@ietf.org)=
; stbryant@cisco.com; ietf@ietf.org; sidr@ietf.org<br><b>Subject:</b> Re: G=
en-ART review of draft-ietf-sidr-bgpsec-threats-06<o:p></o:p></span></p></d=
iv></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal sty=
le=3D'margin-bottom:12.0pt'>David,<br><br>Since this doc logically precedes=
 the BGPsec design, I still think it's appropriate to<br>use PATHSEC here. =
But, we can add a sentence to connect the terms. I propose this modified te=
xt for the introduction:<br><br><b>This document describes the security con=
text in which PATHSEC is intended to operate.&nbsp; (The term &quot;PATHSEC=
&quot; is employed in this document to refer to any design used to achieve =
the path security goal described in the SIDR WG charter. The charter focuse=
s on mechanisms that will enable an AS to determine if the AS_path represen=
ted in a route represents the path via which the NLRI traveled. Other SIDR =
documents use<br>the term &quot;BGPsec&quot; to refer to a specific design.=
) ...<br></b><br>The phrase &quot;calls for&quot; seems appropriate in the =
cache discussion. There is no MUST in the RFCs about using a local cache. T=
he docs encourage RPs to maintain a local cache, <br>and 6481 states that n=
ot using one is &quot;NOT RECOMMENDED.&quot;&nbsp; All of the RP software o=
f which<br>I am aware does so, but it is not an absolute requirement.<br><b=
r>I think we've agreed that quoted is a static assertion and thus need not =
be <br>annotated to reflect more recent RFCs.<br><br>Steve<br><br><br><o:p>=
</o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div>=
</body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1852MX15Acorpemcc_--

From sm@elandsys.com  Tue Oct  1 18:29: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 7BB4711E8153 for <ietf@ietfa.amsl.com>; Tue,  1 Oct 2013 18:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.412
X-Spam-Level: 
X-Spam-Status: No, score=-100.412 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, FRT_PROFILE2=1.981, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARTkqQO2HGpH for <ietf@ietfa.amsl.com>; Tue,  1 Oct 2013 18:28:56 -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 4F2EE11E8264 for <ietf@ietf.org>; Tue,  1 Oct 2013 18:28:39 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.149.116]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r921SOar022581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 1 Oct 2013 18:28:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1380677317; bh=LQYtGe+CfFmI5mj1JZx0oWu05ZuyQ+2ipWCgYD9fmTo=; h=Date:To:From:Subject; b=XFPg1x2NXr5DQKBpj6oTS7iFPxSy48qgRRX339WaVBvmNI5Gr3+J7OZJPRSXewfUZ g8RRV8WsA4/I0DeVyyfy2Zpjmv6I+goFsW5O1IXsTm3c4OwPM0BAnqR9HItZWHs4fW UE988ineDD/dY3jTpCpZ/7k+AHgQf/T2o7ZusiiI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1380677317; i=@elandsys.com; bh=LQYtGe+CfFmI5mj1JZx0oWu05ZuyQ+2ipWCgYD9fmTo=; h=Date:To:From:Subject; b=DFHUQOtGvP4mfHG6kwbKJ9jhLkeOc6ut0tUbUOKDkI+y3S2v95bSlGgAcq62SvAEF DMvPSgglFc941NxMFP1lxuqgjK939lASVKNr/JwaYL9wT1Pvdv5jZMH13kLTF32CFG LFLF4WaZ02fttB4UxxxACNXXb2NjQKcN7GDA61fc=
Message-Id: <6.2.5.6.2.20131001180343.0d799550@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 01 Oct 2013 18:24:11 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Attracting people from emerging regions into the IETF
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====================_38833001==_"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 01:29:03 -0000

--=====================_38833001==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hello,

Here is a draft which attempts to address the challenge of attracting 
people from emerging regions who can contribute to IETF work into the 
IETF.  Please note that I do not have a strong opinion about the suggestions.

Regards,
S. Moonesamy
--=====================_38833001==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="draft-ddt-fellowship-01.txt"

 



                                                            S. Moonesamy
                                                                        

Expires: April 4, 2014                                   October 1, 2013


         Attracting people from emerging regions into the IETF
                        draft-ddt-fellowship-01

1. Introduction

   The IETF Chair set up a Diversity Design Team in July, 2013 to
   determine how to address issues such as geographic diversity.  There
   is already an ISOC Fellowship programme to the IETF for participants
   from emerging regions.  This document attempts to address the
   challenge of attracting people from emerging regions who can
   contribute to IETF work into the IETF.

   Section 2 lists the objectives of the existing ISOC Fellowship
   programme and the selection criteria.  The current programme does
   help new participants to establish an initial face-to-face contact. 
   However, long-term benefit requires helping these participants to
   engage in the full range of IETF interactions.  The most effective
   way to contribute to the IETF is through on-going active
   participation and by reviewing and commenting about working group
   drafts.  There are suggestions in Section 4 to align the ISOC
   Fellowship programme with the expectations of the IETF by having
   selection criteria that encourages active IETF participation, and by
   having an evaluation panel with the expertise to evaluate IETF
   contributions.

2. Existing support for participants from emerging regions

2.1. Objectives of the ISOC Fellowship programme

   The Internet Society has provided significant financial support given
   that attendance by technologists from emerging and developing
   economies is currently limited [FEL].  It is considered that actually
   attending an event promotes a stronger understanding of the standards
   process, encourages active involvement in IETF work, and facilitates
   personal networking with others that have similar technical interests
   [FEL].

   The main purpose [FEL] of the ISOC Fellowship programme is to:

      - Raise global awareness about the IETF and its work.

      - Foster greater understanding of, and participation in, the work
 


                         Expires April 4, 2014                  [Page 1]

S. Moonesamy               Attracting people             October 1, 2013


        of the IETF by technologists from emerging and developing
        economies.

      - Provide an opportunity for networking with individuals from
        around the world with similar technical interests.

      - Identify and foster potential future leaders from emerging and
        developing economies

      - Demonstrate the Internet community's commitment to fostering
        greater global participation in Internet Forums such as the
        IETF.

   The goals of the ISOC Returning fellowship programme [RET] are to:

      - Provide an opportunity for highly committed former Fellows to
        return to the IETF to advance specific standards work.

      - More fully integrate technologists from emerging and developing
        economies into the IETF.

      - Advance the technical leadership potential of individuals from
        emerging and developing economies.

      - Provide immediate value to a working group by participating in
        scribing the working group meeting and contributing to the
        meeting minutes.

2.2. Selection criteria for the ISOC Fellowship programme

   Some of the requirements [SEL] for qualifying for ISOC Fellowship
   programme are:

      - Hold a university-level computer science, information
        technology, or similar degree, or can demonstrate similar and
        relevant work experience.

      - Be employed in a technical or technical management capacity with
        a data network provider (including university networks), a
        technology vendor, a local technical association, or other
        similar organisation OR be a university-level computer
        science/information technology professor, lecturer, or student
        currently undertaking research in one or more areas of current
        IETF standardisation work. Students must be enrolled in a
        graduate-level program (Masters or Ph.D).

      - Possess a strong understanding of how the IETF relates to and
        impacts their work or area of study and demonstrate how specific
 


                         Expires April 4, 2014                  [Page 2]

S. Moonesamy               Attracting people             October 1, 2013


        areas of current IETF work are relevant to their pursuits.

   Some of the attributes [SEL] that reflect favorably on the
   application are:

      - Involvement in one or more regional data networking
        organisations, such as regional operators groups

      - Having actively participated in the work of an IETF Working
        Group through the mailing lists.

3. Expectations of the IETF

   The objectives of the fellowship are less well aligned with the
   expectations of the IETF as it focuses on meeting attendance by
   technologists from emerging and developing economies and awareness of
   the IETF instead of active participation in the IETF.  Although
   attending IETF meetings fosters an understanding of the work of the
   IETF it does not ensure active participation.  Active participation
   in the work of an IETF Working Group is listed as an advantage
   instead of a requirement for the fellowship [SEL].

   The existing selection criteria puts an emphasis on university-level
   qualifications and the academic interests of the applicant [SEL].  It
   has been mentioned in discussions about academic participation that
   the IETF filters out proposals from researchers simply because they
   just do not fit in standardization work [DIN].

   The Returning Fellowship programme is a laudable initiative by the
   Internet Society to encourage IETF participation from emerging
   regions.  It is unclear how the goals to integrate technologists from
   emerging regions into the IETF or advance the technical leadership
   potential of individuals from emerging regions are pursued.

4. Suggestions

4.1. Selection criteria for the fellowship

   The most effective way to contribute to the IETF is through active
   participation and by reviewing and commenting about working group
   drafts [FAA].  It is proposed that the applicant fulfills the
   following criteria:

      - Be proficient in English.

      - Can be objectively said to have actively participated in IETF
        activities for more than six months, and subjectively, such that
        those contributions are considered useful.
 


                         Expires April 4, 2014                  [Page 3]

S. Moonesamy               Attracting people             October 1, 2013


        For example, reviewing drafts, commenting on IETF Last Calls,
        writing code for drafts or taking part in interop testing are
        fine ways to be seen to have participated. Candidates whose
        contributions are considered more useful should be preferred
        over those who are less useful. Judging utility for
        contributions requires knowledge of the specific field.

      - Resident of a country in an emerging region.

4.2. Evaluation panel

   It is suggested to include Area Directors or Working Group Chairs on
   the evaluation panel [FAS].  These people will bring in the expertise
   to evaluate the reviews performed by the applicant.  They can also
   determine whether the applicant has an understanding of the work done
   in the IETF.  It is suggested that the evaluation panel prioritize
   people who have been contributing over time to real IETF work.

4.3. Guidance for applicants

   The fellowship is about people who can demonstrate commitment and can
   collaborate with other IETF participants to perform IETF work. 
   Applicants can familiarize themselves with the technologies being
   discussed by, for example, implementing the relevant specifications
   or evaluating implementations [ACS].  Applicants can ask for advice
   on the edu-discuss@ietf.org mailing list [EDU].

4.4. Effectiveness of the fellowship

   The effectiveness of the fellowship can be assessed by tracking the
   IETF activities of the fellows and doing a follow-up to find out why
   fellows drop out.

5. Open Issue

   The following is left open as it may require broader feedback.

   There were comments to remove the "resident of a country in an
   emerging region" suggestion (Section 4.1) so that people from
   "developed" regions who would not ordinarily have the means to attend
   an IETF meeting are included in the programme.

6. Acknowledgements

   The author would like to thank Alejandro Acosta, Dave Crocker, Adrian
   Farrel, Stephen Farrell, Roque Gagliano, Vinayak Hegde and Kathleen
   Moriarty for contributing to the discussions about participation from
   emerging countries.
 


                         Expires April 4, 2014                  [Page 4]

S. Moonesamy               Attracting people             October 1, 2013


7. References

   [FEL]    <http://www.internetsociety.org/what-we-do/education-and-
            leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship-0>

   [RET]    <http://www.internetsociety.org/what-we-do/education-and-
            leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship-4>

   [SEL]    <http://www.internetsociety.org/what-we-do/education-and-
            leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship/selection-criteria>

   [DIN]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00344.html>

   [FAA]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00339.html>

   [FAS]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00337.html>

   [ACS]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00355.html>

   [EDU]   <https://www.ietf.org/mailman/listinfo/edu-discuss>

8. Author's Address


   S. Moonesamy

   Email: sm+ietf@elandsys.com

















                         Expires April 4, 2014                  [Page 5]

--=====================_38833001==_--


From gonzalo.camarillo@ericsson.com  Wed Oct  2 00:57:59 2013
Return-Path: <gonzalo.camarillo@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 21E8411E81B4 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 00:57: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=[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 CJkSStNkxufe for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 00:57:39 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id E5AB011E814D for <ietf@ietf.org>; Wed,  2 Oct 2013 00:56:21 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-6c-524bd1a1226d
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 85.E0.03802.1A1DB425; Wed,  2 Oct 2013 09:56:17 +0200 (CEST)
Received: from [131.160.36.43] (153.88.183.147) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.2.328.9; Wed, 2 Oct 2013 09:56:17 +0200
Message-ID: <524BD1A0.50209@ericsson.com>
Date: Wed, 2 Oct 2013 10:56:16 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Fwd: RAI AD - Gonzalo will not be re-running
References: <524A8EB1.5080009@ericsson.com>
In-Reply-To: <524A8EB1.5080009@ericsson.com>
X-Enigmail-Version: 1.5.1
X-Forwarded-Message-Id: <524A8EB1.5080009@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnluLIzCtJLcpLzFFi42KZGfG3VnfhRe8gg+ZLihbPNs5ncWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqkTM9kLznJWfD5+g7GB8Sp7FyMnh4SAicTpU1/YIGwxiQv3 1gPZXBxCAocZJTZOOAjlrGKUmNHymBGkildAU2JZ61IWEJtFQEXixsMnTCA2m4CFxJZb98Hi ogJREhu2X2CBqBeUODnzCZgtIiAsceTRP7DNwgKmEns3rQOzhQS0JT6fnQB2BaeAjsSs37+Y IS6SlNjyoh3qUnOJ9823wWqYBfQkplxtYYSw5SW2v53DDDNn+bMWlgmMQrOQrJ6FpGUWkpYF jMyrGNlzEzNz0suNNjECA/Pglt+qOxjvnBM5xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFp TmrxIUYmDk6pBsYlJpUb3rQpKKg0TAyW0um/kvTyhLP5x0vBHW+YypYvKzl3sdOy/nS6/qzf lyQOHOtm4IuvOloaJP5Fd5+084WTFRe/TV0kP/POnuU74wTyTELaA3vLb5Q7TD2dr1z0OoQv dOUk+T+J+c89XK4tuBO2vnEWm96ud//2en+4XbIrQ0XYVsM+q1GJpTgj0VCLuag4EQD4Q9Eq GgIAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 07:57:59 -0000

FYI. I have been asked to share the email below on this list as well.

Gonzalo

-------- Original Message --------
Subject: RAI AD - Gonzalo will not be re-running
Date: Tue, 01 Oct 2013 10:58:25 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
To: rai@ietf.org

Folks,

this email is to inform everyone that I am not going to be seeking a
third term as RAI Area Director. This means that the nomcom will need to
choose someone else to serve as RAI AD after my current term ends in March.

The consensus in the community seems to be that ADs SHOULD NOT serve
more than 4 years, and I fully agree with that. Such a limit is good for
the IETF and good for the ADs as well for a number of reasons.

The main reason I am writing this email is to give potential candidates
enough time to secure management support (or, in general, funding) in
order to provide the nomcom with enough good candidates. You can find
the expertise required for the position in the following link:

https://datatracker.ietf.org/nomcom/2013/expertise/

Additionally, RAI ADs have traditionally selected the beverages for the
IESG social gatherings, which is also an important skill ;-)

Cheers,

Gonzalo




From abdussalambaryun@gmail.com  Wed Oct  2 05:24: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 722CE11E8273; Wed,  2 Oct 2013 05:24: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 fWuQeqr9sJ23; Wed,  2 Oct 2013 05:24:37 -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 74D8121F99F8; Wed,  2 Oct 2013 05:24:00 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so955841pad.19 for <multiple recipients>; Wed, 02 Oct 2013 05:24:00 -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=IJNMTW+5Jq5tQVYj14hEscCH7RwPXhYKngY5LqhNn4M=; b=YilsjUbjvatIgtlaOlmsNwK3+Y7Xfvp0xAOc40xt5aKhYt5j4zUgrYC2O4bGZCCdKg 9XvUWHCLHSWBWiwtJyHT7hCvhntuKrddZgNaI1lcP9czaxSOG7Y/vSmo4ldBLW3asxje Nrce+gptK3dO18/LmUWW7aIjLCXSQgix1CGp9enbUiy43G1XQvcVXhBj/i4X9RM/Hqty /PnB+2gmzyQWcGg44DkXO2VyNuS5gz0EmmDS6w9jXFJAcf/qDlQpUNWlDv9hKL7CfRMw safoy7qXZmjqSahGfZa9W1TC5ypJ9V0S+oIUiFLltaksZs6XCSagQkCowE195KEV+bi7 BwFw==
MIME-Version: 1.0
X-Received: by 10.68.215.38 with SMTP id of6mr2263063pbc.14.1380716313079; Wed, 02 Oct 2013 05:18:33 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 2 Oct 2013 05:18:32 -0700 (PDT)
In-Reply-To: <11884.1380652164@sandelman.ca>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca>
Date: Wed, 2 Oct 2013 13:18:32 +0100
Message-ID: <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com>
Subject: Re: [Tools-discuss] independant submissions that update standards track, and datatracker
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a1134663860758104e7c111ea
Cc: ietf <ietf@ietf.org>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 12:24:44 -0000

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

Hi Michael,

I agree that it should appear in related WG's field or area. I see in IETF
we have WGs documents list but not areas' documents list, so the individual
document may not be found or discovered. I think any document of IETF
should be listed in its field area or related charter, but it seems like
the culture of IETF focusing on groups work not on the IETF documents. For
example, when I first joined MANET WG I thought that RFC3753 is related
because it is IETF, but in one discussion one participant did not accept to
use that document even though it was related. Fuethermore, some WGs don't
comment on related documents to their WG, which I think this should change
in future IETF culture (e.g. there was one individual doc that was
requested by AD to comment on by the WG but no respond).

 Therefore, IMHO, the IETF is divided by groups with different point of
views/documents and they force their WG Adopted-Work to list documents (not
all related to Group-Charters), but it seems that managemnet does not see
that there is a division in knowledge or in outputs of the IETF, which a
new comer may see it clearly. I recommend to focus/list documents related
to Charter, not related to WG adoptions, because all IETF document are
examined by IESG.

AB


On Tue, Oct 1, 2013 at 7:29 PM, Michael Richardson <mcr+ietf@sandelman.ca>wrote:

>
> This morning I had reason to re-read parts of RFC3777, and anything
> that updated it.  I find the datatracker WG interface to really be
> useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
> first.  I guess I could have instead gone to:
>    http://www.rfc-editor.org/info/rfc3777
>
> but frankly, I'm often bad with numbers, especially when they repeat...
> (3777? 3737? 3733?)
>
> While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
> in that line, it lists the things that update it, it doesn't actually list
> the other documents.  Thinking this was an error, I asked, and Cindy kindly
> explained:
>
> >http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
> >published by the NOMCOM Working Group.  The NOMCOM Working Group was
> >open from 2002-2004, and only produced one RFC, which is RFC 3777.
> >
> >The RFCs that update 3777 were all produced by individuals (that is,
> >outside of the NOMCOM Working Group), and so aren't listed individually
> >on the NOMCOM Working Group documents page.
>
> I wonder about this as a policy.
>
> Seeing the titles of those documents would have helped me find what I
> wanted
> quickly (RFC5680 it was)...
>
> While I think that individual submissions that are not the result of
> consensus do not belong on a WG page.  But, if the document was the result
> of
> consensus, but did not occur in a WG because the WG had closed, I think
> that
> perhaps it should appear there anyway.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>
>
>
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
>

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

<div dir=3D"ltr"><div>Hi Michael,</div><div>=A0</div><div>I agree that it s=
hould appear in related WG&#39;s field or area. I=A0see in IETF we have WGs=
 documents list but not areas&#39; documents list, so the individual docume=
nt may not be found or discovered. I think any document of IETF should be l=
isted in its field area or related charter, but it seems like the culture o=
f IETF focusing on groups work not on the IETF documents. For example, when=
 I first joined MANET WG I thought that RFC3753 is related because it is IE=
TF, but in one discussion one participant did not accept to use that docume=
nt even though it was related. Fuethermore, some WGs don&#39;t comment on r=
elated documents to their WG, which I think this should change in future IE=
TF culture (e.g. there was one individual doc that was requested by AD to c=
omment on=A0by the WG but no=A0respond).</div>
<div>=A0</div><div>=A0Therefore, IMHO, the IETF is divided by groups with d=
ifferent point of views/documents and they force their WG Adopted-Work to l=
ist documents (not all related to Group-Charters), but it seems that manage=
mnet does not see that there is a division in knowledge or in outputs of th=
e IETF, which a new comer may see it clearly. I recommend to focus/list doc=
uments related to Charter, not related to WG adoptions, because all IETF do=
cument=A0are examined by IESG.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Tue, Oct 1, 2013 at 7:29 PM, Michael Richardson <spa=
n 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"><br>
This morning I had reason to re-read parts of RFC3777, and anything<br>
that updated it. =A0I find the datatracker WG interface to really be<br>
useful, and so I visited <a href=3D"http://datatracker.ietf.org/wg/nomcom/"=
 target=3D"_blank">http://datatracker.ietf.org/wg/nomcom/</a><br>
first. =A0I guess I could have instead gone to:<br>
=A0 =A0<a href=3D"http://www.rfc-editor.org/info/rfc3777" target=3D"_blank"=
>http://www.rfc-editor.org/info/rfc3777</a><br>
<br>
but frankly, I&#39;m often bad with numbers, especially when they repeat...=
<br>
(3777? 3737? 3733?)<br>
<br>
While <a href=3D"http://datatracker.ietf.org/wg/nomcom/" target=3D"_blank">=
http://datatracker.ietf.org/wg/nomcom/</a> lists RFC3777, and<br>
in that line, it lists the things that update it, it doesn&#39;t actually l=
ist<br>
the other documents. =A0Thinking this was an error, I asked, and Cindy kind=
ly<br>
explained:<br>
<br>
&gt;<a href=3D"http://datatracker.ietf.org/wg/nomcom/" target=3D"_blank">ht=
tp://datatracker.ietf.org/wg/nomcom/</a> lists the documents that were<br>
&gt;published by the NOMCOM Working Group. =A0The NOMCOM Working Group was<=
br>
&gt;open from 2002-2004, and only produced one RFC, which is RFC 3777.<br>
&gt;<br>
&gt;The RFCs that update 3777 were all produced by individuals (that is,<br=
>
&gt;outside of the NOMCOM Working Group), and so aren&#39;t listed individu=
ally<br>
&gt;on the NOMCOM Working Group documents page.<br>
<br>
I wonder about this as a policy.<br>
<br>
Seeing the titles of those documents would have helped me find what I wante=
d<br>
quickly (RFC5680 it was)...<br>
<br>
While I think that individual submissions that are not the result of<br>
consensus do not belong on a WG page. =A0But, if the document was the resul=
t of<br>
consensus, but did not occur in a WG because the WG had closed, I think tha=
t<br>
perhaps it should appear there anyway.<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>
<br>_______________________________________________<br>
Tools-discuss mailing list<br>
<a href=3D"mailto:Tools-discuss@ietf.org">Tools-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tools-discuss" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/tools-discuss</a><br>
<br></blockquote></div><br></div>

--001a1134663860758104e7c111ea--

From jdrake@juniper.net  Wed Oct  2 05:53:16 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 C6FC711E8104; Wed,  2 Oct 2013 05:53:16 -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, 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 jAdWB2d85BuT; Wed,  2 Oct 2013 05:53:05 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE1011E80EA; Wed,  2 Oct 2013 05:52:36 -0700 (PDT)
Received: from mail6-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 12:52:30 +0000
Received: from mail6-va3 (localhost [127.0.0.1])	by mail6-va3-R.bigfish.com (Postfix) with ESMTP id 7CB6B2400B3; Wed,  2 Oct 2013 12:52:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(zz98dI9371Ic85fh1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h1033IL17326ah18c673h1de097h186068h18de19h8275bh8275dhz2fh2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h20f0h9a9j1155h)
Received-SPF: pass (mail6-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(51444003)(199002)(189002)(51704005)(377454003)(77982001)(59766001)(81342001)(66066001)(31966008)(56776001)(54316002)(19300405004)(50986001)(63696002)(15975445006)(76482001)(76796001)(15202345003)(76786001)(76576001)(83322001)(19580405001)(47736001)(49866001)(74706001)(46102001)(56816003)(74876001)(77096001)(4396001)(53806001)(19580395003)(47446002)(47976001)(16236675002)(74662001)(69226001)(19609705001)(74502001)(80976001)(81686001)(74366001)(81542001)(81816001)(74316001)(83072001)(80022001)(65816001)(33646001)(54356001)(51856001)(79102001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB142; H:BY2PR05MB142.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail6-va3 (localhost.localdomain [127.0.0.1]) by mail6-va3 (MessageSwitch) id 1380718348694840_13930; Wed,  2 Oct 2013 12:52:28 +0000 (UTC)
Received: from VA3EHSMHS014.bigfish.com (unknown [10.7.14.250])	by mail6-va3.bigfish.com (Postfix) with ESMTP id A0F1D3E0050; Wed,  2 Oct 2013 12:52:28 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS014.bigfish.com (10.7.99.24) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 12:52:28 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 12:52:27 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 12:52:25 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.177]) by BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.177]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 12:52:25 +0000
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: RE: [Tools-discuss] independant submissions that update standards track, and datatracker
Thread-Topic: [Tools-discuss] independant submissions that update standards track, and datatracker
Thread-Index: AQHOv2psSZZkh56kJ0Wc1Z9sttwWV5nhXSeA
Date: Wed, 2 Oct 2013 12:52:25 +0000
Message-ID: <634130acbbfc4f4389e39172cfcc8fad@BY2PR05MB142.namprd05.prod.outlook.com>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com>
In-Reply-To: <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: multipart/alternative; boundary="_000_634130acbbfc4f4389e39172cfcc8fadBY2PR05MB142namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: ietf <ietf@ietf.org>, "tools-discuss@ietf.org" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 12:53:17 -0000

--_000_634130acbbfc4f4389e39172cfcc8fadBY2PR05MB142namprd05pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Irrepressible

Yours Irrespectively,

John

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Abd=
ussalam Baryun
Sent: Wednesday, October 02, 2013 5:19 AM
To: Michael Richardson
Cc: ietf; tools-discuss@ietf.org
Subject: Re: [Tools-discuss] independant submissions that update standards =
track, and datatracker

Hi Michael,

I agree that it should appear in related WG's field or area. I see in IETF =
we have WGs documents list but not areas' documents list, so the individual=
 document may not be found or discovered. I think any document of IETF shou=
ld be listed in its field area or related charter, but it seems like the cu=
lture of IETF focusing on groups work not on the IETF documents. For exampl=
e, when I first joined MANET WG I thought that RFC3753 is related because i=
t is IETF, but in one discussion one participant did not accept to use that=
 document even though it was related. Fuethermore, some WGs don't comment o=
n related documents to their WG, which I think this should change in future=
 IETF culture (e.g. there was one individual doc that was requested by AD t=
o comment on by the WG but no respond).

 Therefore, IMHO, the IETF is divided by groups with different point of vie=
ws/documents and they force their WG Adopted-Work to list documents (not al=
l related to Group-Charters), but it seems that managemnet does not see tha=
t there is a division in knowledge or in outputs of the IETF, which a new c=
omer may see it clearly. I recommend to focus/list documents related to Cha=
rter, not related to WG adoptions, because all IETF document are examined b=
y IESG.

AB

On Tue, Oct 1, 2013 at 7:29 PM, Michael Richardson <mcr+ietf@sandelman.ca<m=
ailto:mcr+ietf@sandelman.ca>> wrote:

This morning I had reason to re-read parts of RFC3777, and anything
that updated it.  I find the datatracker WG interface to really be
useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
first.  I guess I could have instead gone to:
   http://www.rfc-editor.org/info/rfc3777

but frankly, I'm often bad with numbers, especially when they repeat...
(3777? 3737? 3733?)

While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
in that line, it lists the things that update it, it doesn't actually list
the other documents.  Thinking this was an error, I asked, and Cindy kindly
explained:

>http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
>published by the NOMCOM Working Group.  The NOMCOM Working Group was
>open from 2002-2004, and only produced one RFC, which is RFC 3777.
>
>The RFCs that update 3777 were all produced by individuals (that is,
>outside of the NOMCOM Working Group), and so aren't listed individually
>on the NOMCOM Working Group documents page.

I wonder about this as a policy.

Seeing the titles of those documents would have helped me find what I wante=
d
quickly (RFC5680 it was)...

While I think that individual submissions that are not the result of
consensus do not belong on a WG page.  But, if the document was the result =
of
consensus, but did not occur in a WG because the WG had closed, I think tha=
t
perhaps it should appear there anyway.

--
Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr%2BIETF@sandelman.ca>>,=
 Sandelman Software Works



_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org<mailto:Tools-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/tools-discuss


--_000_634130acbbfc4f4389e39172cfcc8fadBY2PR05MB142namprd05pro_
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 15 (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: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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Irrepressible<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours Irrespectively,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&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 #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> ietf-b=
ounces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Abdussalam Baryun<br>
<b>Sent:</b> Wednesday, October 02, 2013 5:19 AM<br>
<b>To:</b> Michael Richardson<br>
<b>Cc:</b> ietf; tools-discuss@ietf.org<br>
<b>Subject:</b> Re: [Tools-discuss] independant submissions that update sta=
ndards track, and datatracker<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Hi Michael,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I agree that it should appear in related WG's field =
or area. I&nbsp;see in IETF we have WGs documents list but not areas' docum=
ents list, so the individual document may not be found or discovered. I thi=
nk any document of IETF should be listed
 in its field area or related charter, but it seems like the culture of IET=
F focusing on groups work not on the IETF documents. For example, when I fi=
rst joined MANET WG I thought that RFC3753 is related because it is IETF, b=
ut in one discussion one participant
 did not accept to use that document even though it was related. Fuethermor=
e, some WGs don't comment on related documents to their WG, which I think t=
his should change in future IETF culture (e.g. there was one individual doc=
 that was requested by AD to comment
 on&nbsp;by the WG but no&nbsp;respond).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;Therefore, IMHO, the IETF is divided by groups=
 with different point of views/documents and they force their WG Adopted-Wo=
rk to list documents (not all related to Group-Charters), but it seems that=
 managemnet does not see that there is
 a division in knowledge or in outputs of the IETF, which a new comer may s=
ee it clearly. I recommend to focus/list documents related to Charter, not =
related to WG adoptions, because all IETF document&nbsp;are examined by IES=
G.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">AB<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Tue, Oct 1, 2013 at 7:29 PM, Michael Richardson &=
lt;<a href=3D"mailto:mcr&#43;ietf@sandelman.ca" target=3D"_blank">mcr&#43;i=
etf@sandelman.ca</a>&gt; wrote:<o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
This morning I had reason to re-read parts of RFC3777, and anything<br>
that updated it. &nbsp;I find the datatracker WG interface to really be<br>
useful, and so I visited <a href=3D"http://datatracker.ietf.org/wg/nomcom/"=
 target=3D"_blank">
http://datatracker.ietf.org/wg/nomcom/</a><br>
first. &nbsp;I guess I could have instead gone to:<br>
&nbsp; &nbsp;<a href=3D"http://www.rfc-editor.org/info/rfc3777" target=3D"_=
blank">http://www.rfc-editor.org/info/rfc3777</a><br>
<br>
but frankly, I'm often bad with numbers, especially when they repeat...<br>
(3777? 3737? 3733?)<br>
<br>
While <a href=3D"http://datatracker.ietf.org/wg/nomcom/" target=3D"_blank">=
http://datatracker.ietf.org/wg/nomcom/</a> lists RFC3777, and<br>
in that line, it lists the things that update it, it doesn't actually list<=
br>
the other documents. &nbsp;Thinking this was an error, I asked, and Cindy k=
indly<br>
explained:<br>
<br>
&gt;<a href=3D"http://datatracker.ietf.org/wg/nomcom/" target=3D"_blank">ht=
tp://datatracker.ietf.org/wg/nomcom/</a> lists the documents that were<br>
&gt;published by the NOMCOM Working Group. &nbsp;The NOMCOM Working Group w=
as<br>
&gt;open from 2002-2004, and only produced one RFC, which is RFC 3777.<br>
&gt;<br>
&gt;The RFCs that update 3777 were all produced by individuals (that is,<br=
>
&gt;outside of the NOMCOM Working Group), and so aren't listed individually=
<br>
&gt;on the NOMCOM Working Group documents page.<br>
<br>
I wonder about this as a policy.<br>
<br>
Seeing the titles of those documents would have helped me find what I wante=
d<br>
quickly (RFC5680 it was)...<br>
<br>
While I think that individual submissions that are not the result of<br>
consensus do not belong on a WG page. &nbsp;But, if the document was the re=
sult of<br>
consensus, but did not occur in a WG because the WG had closed, I think tha=
t<br>
perhaps it should appear there anyway.<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr&#43;I=
ETF@sandelman.ca</a>&gt;, Sandelman Software Works<br>
<br>
<br>
<br>
_______________________________________________<br>
Tools-discuss mailing list<br>
<a href=3D"mailto:Tools-discuss@ietf.org">Tools-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tools-discuss" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/tools-discuss</a><o:p></o:p></=
p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_634130acbbfc4f4389e39172cfcc8fadBY2PR05MB142namprd05pro_--

From l.wood@surrey.ac.uk  Wed Oct  2 06:26:16 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 537D721E8054; Wed,  2 Oct 2013 06:26:16 -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=[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 UvMDbO-s9lZ9; Wed,  2 Oct 2013 06:26:05 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.117]) by ietfa.amsl.com (Postfix) with ESMTP id 4950311E80C5; Wed,  2 Oct 2013 06:24:08 -0700 (PDT)
Received: from [193.109.255.147:50513] by server-13.bemta-14.messagelabs.com id 72/88-01215-67E1C425; Wed, 02 Oct 2013 13:24:06 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-72.messagelabs.com!1380720245!12289070!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10814 invoked from network); 2 Oct 2013 13:24:05 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-5.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 2 Oct 2013 13:24:05 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.148]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 2 Oct 2013 14:24:05 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <mcr+ietf@sandelman.ca>
Date: Wed, 2 Oct 2013 14:21:58 +0100
Subject: RE: [Tools-discuss] independant submissions that update standards track, and datatracker
Thread-Topic: [Tools-discuss] independant submissions that update standards track, and datatracker
Thread-Index: Ac6/aoTs7ZbCeLe9SleAqHgn34q1bwAB9pbv
Message-ID: <290E20B455C66743BE178C5C84F12408374274D584@EXMB01CMS.surrey.ac.uk>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca>, <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com>
In-Reply-To: <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@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, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 13:26:16 -0000

"because all IETF document are examined by IESG"

No they're not. See RFC4844.

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: 02 October 2013 13:18
To: Michael Richardson
Cc: ietf; tools-discuss@ietf.org
Subject: Re: [Tools-discuss] independant submissions that update standards =
     track, and datatracker

Hi Michael,

I agree that it should appear in related WG's field or area. I see in IETF =
we have WGs documents list but not areas' documents list, so the individual=
 document may not be found or discovered. I think any document of IETF shou=
ld be listed in its field area or related charter, but it seems like the cu=
lture of IETF focusing on groups work not on the IETF documents. For exampl=
e, when I first joined MANET WG I thought that RFC3753 is related because i=
t is IETF, but in one discussion one participant did not accept to use that=
 document even though it was related. Fuethermore, some WGs don't comment o=
n related documents to their WG, which I think this should change in future=
 IETF culture (e.g. there was one individual doc that was requested by AD t=
o comment on by the WG but no respond).

 Therefore, IMHO, the IETF is divided by groups with different point of vie=
ws/documents and they force their WG Adopted-Work to list documents (not al=
l related to Group-Charters), but it seems that managemnet does not see tha=
t there is a division in knowledge or in outputs of the IETF, which a new c=
omer may see it clearly. I recommend to focus/list documents related to Cha=
rter, not related to WG adoptions, because all IETF document are examined b=
y IESG.

AB


On Tue, Oct 1, 2013 at 7:29 PM, Michael Richardson <mcr+ietf@sandelman.ca<m=
ailto:mcr+ietf@sandelman.ca>> wrote:

This morning I had reason to re-read parts of RFC3777, and anything
that updated it.  I find the datatracker WG interface to really be
useful, and so I visited http://datatracker.ietf.org/wg/nomcom/
first.  I guess I could have instead gone to:
   http://www.rfc-editor.org/info/rfc3777

but frankly, I'm often bad with numbers, especially when they repeat...
(3777? 3737? 3733?)

While http://datatracker.ietf.org/wg/nomcom/ lists RFC3777, and
in that line, it lists the things that update it, it doesn't actually list
the other documents.  Thinking this was an error, I asked, and Cindy kindly
explained:

>http://datatracker.ietf.org/wg/nomcom/ lists the documents that were
>published by the NOMCOM Working Group.  The NOMCOM Working Group was
>open from 2002-2004, and only produced one RFC, which is RFC 3777.
>
>The RFCs that update 3777 were all produced by individuals (that is,
>outside of the NOMCOM Working Group), and so aren't listed individually
>on the NOMCOM Working Group documents page.

I wonder about this as a policy.

Seeing the titles of those documents would have helped me find what I wante=
d
quickly (RFC5680 it was)...

While I think that individual submissions that are not the result of
consensus do not belong on a WG page.  But, if the document was the result =
of
consensus, but did not occur in a WG because the WG had closed, I think tha=
t
perhaps it should appear there anyway.

--
Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr%2BIETF@sandelman.ca>>,=
 Sandelman Software Works



_______________________________________________
Tools-discuss mailing list
Tools-discuss@ietf.org<mailto:Tools-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/tools-discuss



From barryleiba.mailing.lists@gmail.com  Wed Oct  2 07:12:18 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 3744121F9DC7; Wed,  2 Oct 2013 07:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.328
X-Spam-Level: 
X-Spam-Status: No, score=-101.328 tagged_above=-999 required=5 tests=[AWL=0.650, 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 emlP+s+fcLiV; Wed,  2 Oct 2013 07:12:05 -0700 (PDT)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id F2B3E21F85BB; Wed,  2 Oct 2013 07:10:50 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id lh4so506482vcb.37 for <multiple recipients>; Wed, 02 Oct 2013 07:10:48 -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:message-id:subject :from:to:cc:content-type; bh=JUtePYxQDCTYU9n3RLBTHez73cl65+DYNfCghvileUU=; b=wV0NnEBxcwNgabSpFs00QXUxGwhruwJRMfijo9c6ZijJJgNvLHLoWi5qpHAijSJxGA JIInZVbYmphfg38mJahOp05ygfNbuSzWTTmkxMieWl5k7/MpL6SgJJx/0uxZraeDPSOL yeDAozm3+OKGOpq+iMaouwfGeOxvL3y8W6NgGfsC7hWjRqQjvw/w70XOK+SZTqhJDbcG D2CBecf2I5XGtglQgteTxE1wJsMDB1/e4+4Q17lSAP94ST7U9P3qKezEEjbGKHpyCSL3 H+Y7wYif9b4FP/1OfQMvjH5LLZhKPKLNJDOJB4lDsveHGPlB4CGqLZXVT2MirIdkZRI3 46RA==
MIME-Version: 1.0
X-Received: by 10.221.64.17 with SMTP id xg17mr2214423vcb.5.1380723047958; Wed, 02 Oct 2013 07:10:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Wed, 2 Oct 2013 07:10:47 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F12408374274D584@EXMB01CMS.surrey.ac.uk>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D584@EXMB01CMS.surrey.ac.uk>
Date: Wed, 2 Oct 2013 10:10:47 -0400
X-Google-Sender-Auth: 6vBOSvFr0TAK3apv4kyREzDy2T8
Message-ID: <CAC4RtVDOCBqK+D4bFPKFKkmxd=qEerJPBLKwSqNFfCS-bg1hSA@mail.gmail.com>
Subject: Re: [Tools-discuss] independant submissions that update standards track, and datatracker
From: Barry Leiba <barryleiba@computer.org>
To: l.wood@surrey.ac.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 14:12:18 -0000

> "because all IETF document are examined by IESG"
>
> No they're not. See RFC4844.

Lloyd, it *is* true that all documents in the IETF stream are reviewed
and approved by the IESG.  I would take "IETF documents" to refer to
documents in the IETF stream.

(In fact, documents in the IRTF and Independent streams are also
"examined" by the IESG, but only for conflict review, according to RFC
5742.  The only RFCs that the IESG doesn't look at in any formal way
are those in the IAB stream.)

Barry, Applications AD

From sob@sobco.com  Wed Oct  2 07:16:07 2013
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39F0E21F8F07; Wed,  2 Oct 2013 07:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 Y0LcNG8dys2d; Wed,  2 Oct 2013 07:15:55 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 9903B21F85BB; Wed,  2 Oct 2013 07:15:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id A1DE13063E9; Wed,  2 Oct 2013 10:15:19 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8oqI-17AQmc; Wed,  2 Oct 2013 10:15:18 -0400 (EDT)
Received: from [10.12.133.208] (wrls-67-134-207-237.wrls.harvard.edu [67.134.207.237]) by sobco.sobco.com (Postfix) with ESMTPSA id C58933063DA; Wed,  2 Oct 2013 10:15:18 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Tools-discuss] independant submissions that update standards track, and datatracker
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <CAC4RtVDOCBqK+D4bFPKFKkmxd=qEerJPBLKwSqNFfCS-bg1hSA@mail.gmail.com>
Date: Wed, 2 Oct 2013 10:15:19 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <6037477B-9C2A-4F6C-B268-01D52D23B6C2@sobco.com>
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D584@EXMB01CMS.surrey.ac.uk> <CAC4RtVDOCBqK+D4bFPKFKkmxd=qEerJPBLKwSqNFfCS-bg1hSA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1510)
Cc: IETF discussion list <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 14:16:07 -0000

 1 April RFCs excepted

Scott

On Oct 2, 2013, at 10:10 AM, Barry Leiba <barryleiba@computer.org> wrote:

>> "because all IETF document are examined by IESG"
>> 
>> No they're not. See RFC4844.
> 
> Lloyd, it *is* true that all documents in the IETF stream are reviewed
> and approved by the IESG.  I would take "IETF documents" to refer to
> documents in the IETF stream.
> 
> (In fact, documents in the IRTF and Independent streams are also
> "examined" by the IESG, but only for conflict review, according to RFC
> 5742.  The only RFCs that the IESG doesn't look at in any formal way
> are those in the IAB stream.)
> 
> Barry, Applications AD


From johnl@iecc.com  Wed Oct  2 07:55:06 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 87DAB21F9196 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 07:55:05 -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 hPvV+VKRG079 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 07:54:55 -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 7007921F8411 for <ietf@ietf.org>; Wed,  2 Oct 2013 07:53:02 -0700 (PDT)
Received: (qmail 77229 invoked from network); 2 Oct 2013 14:53:00 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Oct 2013 14:53:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=524c334c.xn--btvx9d.k1309; i=johnl@user.iecc.com; bh=sv/Ywx6Svc+xuNW4nAgmBlNe+qe8UiKejQq9TMtaH8A=; b=GVPLQVmu5nNeQ8wlMG6Kds/DM0O8QMJz/4X3xIo5CA0+qlY0RQQVQLfFYaFQtQgG9ZbIW0vCZHclsi27OSRdusg3tn7vxOnkiHnreYP2bVQzluz17Gsg5pWtBJSFEKSmsAL1nnR3kW/ZE5BsYyyPqDjH9XW3lRJpHCWN5WZKnuWBkWYL8M1mVGSQrlTJUhGMB9E84rjlbBdPqFWjxkTIQWhdOJyfyGaFIbleEx0OkAk6ldFVU+kAVhdwOuu8CQ15
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=524c334c.xn--btvx9d.k1309; olt=johnl@user.iecc.com; bh=sv/Ywx6Svc+xuNW4nAgmBlNe+qe8UiKejQq9TMtaH8A=; b=UnIq/uQ6WBNkiKGjcLrQl4AxAzySqjjRd8faVgeITH/VcMsOMkknFPM9GwN+JRV65SHKUDl6+Prt/S+BBDoSyeEEFkEcbqahaAuNDmgoaBA/fCqr+vXKgMzB168KtwyVtRnabyxYxmpMxf4ZF2wtAJ5nPXxWB1g9P4zLWLNWb9gABYiTc+3u0tHWtsQDxx0EvFaf3QHRfaGbSriiitktBOdH1lUuXXpx76sFB6aRPXjQJWp0JbC/IbvJZcvMLPgm
Date: 2 Oct 2013 14:52:38 -0000
Message-ID: <20131002145238.78084.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
In-Reply-To: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
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: Wed, 02 Oct 2013 14:55:06 -0000

>The IESG has received a request from an individual participant to make
>the following status changes:
>
>- RFC5617 from Proposed Standard to Historic
>
>The supporting document for this request can be found here:
>
>http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/

I'm one of the authors of this RFC and support the change.

ADSP was basically an experiment that failed.  It has no significant
deployment, and the problem it was supposed to solve is now being
addressed in other ways.

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 kent@bbn.com  Wed Oct  2 08:06:36 2013
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBF1021F89A6; Wed,  2 Oct 2013 08:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.299
X-Spam-Level: 
X-Spam-Status: No, score=-105.299 tagged_above=-999 required=5 tests=[AWL=1.299, 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 jOA1PlgBNVli; Wed,  2 Oct 2013 08:06:23 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 31EF121F91B7; Wed,  2 Oct 2013 08:03:42 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:51574) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1VRNxk-000O8a-KM; Wed, 02 Oct 2013 11:03:40 -0400
Message-ID: <524C35CC.1030501@bbn.com>
Date: Wed, 02 Oct 2013 11:03:40 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
References: <8D3D17ACE214DC429325B2B98F3AE712025DBB6FDA@MX15A.corp.emc.com> <5249BE21.4060702@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DBB7B41@MX15A.corp.emc.com> <524B3998.20009@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DCE1852@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712025DCE1852@MX15A.corp.emc.com>
Content-Type: multipart/alternative; boundary="------------010200040303030002040207"
Cc: "sidr@ietf.org" <sidr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "stbryant@cisco.com" <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: Wed, 02 Oct 2013 15:06:36 -0000

This is a multi-part message in MIME format.
--------------010200040303030002040207
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David,

> Steve,
>
> I think the modified introduction text suffices to connect the PATHSEC 
> and BGPsec terms, but I don't think that referring to the SIDR WG 
> charter for the PATHSEC goals is reasonable -- an RFC is an archive 
> document, whereas a WG charter is not.
>
The revised intro text now paraphrases the text from the SIDR charter that
describes the path security goals.

Steve

--------------010200040303030002040207
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 bgcolor="#FFFFFF" text="#000000">
    David,<br>
    <br>
    <blockquote
      cite="mid:8D3D17ACE214DC429325B2B98F3AE712025DCE1852@MX15A.corp.emc.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="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";
	color:black;}
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-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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">Steve,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier New&quot;">I
            think the modified introduction text suffices to connect the
            PATHSEC and BGPsec terms, but I don&#8217;t think that referring
            to the SIDR WG charter for the PATHSEC goals is reasonable &#8211;
            an RFC is an archive document, whereas a WG charter is not.</span></p>
      </div>
    </blockquote>
    The revised intro text now paraphrases the text from the SIDR
    charter that<br>
    describes the path security goals.<br>
    <br>
    Steve<br>
  </body>
</html>

--------------010200040303030002040207--

From sm@elandsys.com  Wed Oct  2 08:48:39 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 A8B0821F8FE5 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 08:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.485
X-Spam-Level: 
X-Spam-Status: No, score=-101.485 tagged_above=-999 required=5 tests=[AWL=1.114, 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 C5NgGGsy36kN for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 08:48:33 -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 055FB21F8F78 for <ietf@ietf.org>; Wed,  2 Oct 2013 08:47:52 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.43]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r92FlZij000673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Oct 2013 08:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1380728870; bh=I91TcFWgMThVmST0ECFqgthS6OxD0kAvId74PEOSYGI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AThMCYDtz3k9Opqkfj5Kde/KvYFY9b67hxYG0H5xGLIXI2UZXTXmHQGrPbQp7NqAc b17Ybw6WuZsyb3PzwpAoFLsBPjqHCIRBac5bSM7kKeb5b+ddLXxLv7KiksgXCsYmKd GHLXNedYLY+QCs7QXgvh4aUvnArWmKnDGpZC2fcc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1380728870; i=@elandsys.com; bh=I91TcFWgMThVmST0ECFqgthS6OxD0kAvId74PEOSYGI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=t+d/dWUSpScp7B12AbdiG4MYBqTD7QhoqtVcSLPtRYO/HEa/OcuRkF4Oa+3ASkoyC 9HoVDxFQsjrLtPbeOHOaMPB33Kve02c2CJpqxDxOkXpRTDKo2gKRwJC/rN89swZCkF ltp6BQbFdh3cYoCsSd2UVNhtMhcN97O0xMOhIq/U=
Message-Id: <6.2.5.6.2.20131002045328.0d46e8c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 02 Oct 2013 08:36:42 -0700
To: Steve Conte <conte@isoc.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [Diversity] Attracting people from emerging regions into the IETF
In-Reply-To: <CE7089B6.1B880%conte@isoc.org>
References: <F21BE712-9422-4C60-80D2-BB8AFBCC1B61@netapp.com> <CE7089B6.1B880%conte@isoc.org>
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, 02 Oct 2013 15:48:39 -0000

Hi Steve,
At 14:18 01-10-2013, Steve Conte wrote:
>One of the goals of the ISOC Fellowship to the IETF programme is to
>increase IETF participation in emerging and developing economies, and thus
>it contributes to increasing diversity within the IETF.  ISOC also has and
>supports other activities surrounding the increase of awareness and
>participation in the IETF.  The fellowship is just one component.
>
>I would like to better understand how the implementation and operation of
>this ISOC-driven programme speaks to the larger challenge question of
>increasing diversity at IETF.

There is a one-page overview of the IETF provided=20
by the Internet Society [1].  According to the document:

   "The IETF seeks broad participation.  The work=20
of the IETF takes places online,
    largely through email lists, reducing=20
barriers to participation and maximizing
    contributions from around the world.  IETF=20
Working Groups (WGs) are organized
    by topic into several areas (e.g. routing, transport, security, etc.)."

The document then has a title about "mission and principles" which I'll=
 quote:

   "The mission of the IETF is make the Internet work better by producing=
 high
    quality, relevant technical documents that influence the way people=
 design,
    use, and manage the Internet."

I read an article written by the Chair of the=20
IETF.  I'll do some selective quoting of that article:

   "The IETF can benefit of untapped potential and bring even more energy to
    the work."

   "We think of diversity as something that covers international=
 participation,
    different cultures, gender, age,=20
organisational background, and so on. While
    I am very proud of the IETF as a very international organisation =96=
 with
    participants from 60 countries working on documents, for instance =AD=
 there
    are many aspects of diversity where we could do much better.  Overall
    participation is concentrated in some areas of the world, with little
    participation from Africa and South America, for instance.  Similarly,
    while the IETF has some very active female participants and leadership
    members, the numbers are very small."

   "The diversity team is a design team tasked with understanding the issues
    we are facing, drawing in experience from other organizations affected=
 by
    similar issues, identifying obstacles to us having the widest breadth of
    talented participants and leaders, and making practical recommendations
    that could help us improve the situation."

The Chair of the IETF asked for practical=20
recommendations.  It is not for me to make=20
recommendations.  I can only make suggestions=20
(see=20
http://www.ietf.org/mail-archive/web/ietf/current/msg82776.html=20
).  If the IETF Area Directors believe that the=20
suggestions are unpractical or useless they are welcome to ignore them.

In my humble opinion the challenge of the IETF is=20
to produce high quality, relevant technical=20
documents.  The Chair of the IETF mentioned that=20
there is very little participation from Africa=20
and South America.  The main point raised during=20
the discussions about the draft is on-going and=20
active participation.  The question is what can=20
be done in practice to improve on-going and=20
active participation from, for example, Africa=20
and South America without making it even more=20
difficult for the IETF to produce high quality, relevant technical=
 documents.

I would like to see five Working Groups Chairs=20
who are residing in South America within a few=20
years.  They will have to earn the role based on=20
merit and not because they are from South=20
America.  They will have to work hard.  They will=20
have to learn by themselves what John Klensin=20
means when he says: The "I" in the IETF is not I.

Regards,
S. Moonesamy

1. http://www.ietf.org/about/about-the-ietf-en.pdf =20


From john-ietf@jck.com  Wed Oct  2 09:31:04 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 9B4BD21F9D89 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 09:31:04 -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 NCnDl6yqEXIP for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 09:30:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 719A721F997D for <ietf@ietf.org>; Wed,  2 Oct 2013 09:29:04 -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 1VRPIM-000Ksq-K0; Wed, 02 Oct 2013 12:29:02 -0400
Date: Wed, 02 Oct 2013 12:28:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, dcrocker@bbiw.ne
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
Message-ID: <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
In-Reply-To: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
References: <20131002144143.20697.85830.idtracker@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: Wed, 02 Oct 2013 16:31:04 -0000

--On Wednesday, October 02, 2013 07:41 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from an individual participant
> to make the following status changes:
> 
> - RFC5617 from Proposed Standard to Historic
> 
> The supporting document for this request can be found here:
> 
> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-
> historic/

Hi.  Just to be sure that everyone has the same understanding of
what is being proposed here, the above says "to Historic" but
the writeup at
http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
says "to Internet Standard".   Can one or the other be corrected?

After reading the description at the link cited above and
assuming that "Historic" is actually intended, I wonder,
procedurally, whether a move to Historic without document other
than in the tracker is an appropriate substitute for the
publication of an Applicability Statement that says "not
recommended" and that explains, at least in the level of detail
of the tracker entry, why using ADSP is a bad idea.  

If there were no implementations and no evidence that anyone
cared about this, my inclination would be to just dispose of RFC
5617 as efficiently and with as little effort as possible.  But,
since the tracker entry says that there are implementations and
that misconfiguration has caused harm (strongly implying that
there has even been deployment), it seems to me that a clear and
affirmative "not recommended" applicability statement is in
order.

thanks,
   john


From barryleiba@gmail.com  Wed Oct  2 09:33:46 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 D33AD21F8B04 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 09:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.761
X-Spam-Level: 
X-Spam-Status: No, score=-101.761 tagged_above=-999 required=5 tests=[AWL=0.217, 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 UkvOPApPkAKv for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 09:33:40 -0700 (PDT)
Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id F1F7821F9D89 for <ietf@ietf.org>; Wed,  2 Oct 2013 09:32:05 -0700 (PDT)
Received: by mail-qa0-f50.google.com with SMTP id j7so776959qaq.9 for <ietf@ietf.org>; Wed, 02 Oct 2013 09:32:05 -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:message-id:subject :from:to:cc:content-type; bh=dAZC853yVyIQG3hwMUalO8lmkGYcfHzzBIpgw5Vwk9o=; b=IjExpYz9H21E66ouaPEdMKlDFhNLdVmMbLxTK3PtDNE9nOcSVz+llCD+K5nrngSsQo Hq8IoMtg4gUR+hZ1UeiLPlR7fbm00V0jCnkjBbOQp+TuKbDdKqoGb0EngQJ41eEBFpTZ U5NOauoMZ6UoN4qIwEHEUcfW6K/JMV4MhoY9BkiKfZchXUaWiH0/K6lYepnaQWC9P6AI 9vy8X8YVUjMiYaWYRA0NcRZeL5FpSaVYh2fo0HnVPE8n3pbJASWo8bbeZGqfeoRU8s7U lHrkaCNX6cCe8vVflRtDk2tsuXtA551NsVONCzBpNq+SYnDOlQSd6qqPnzt74gagtY53 NNdA==
MIME-Version: 1.0
X-Received: by 10.49.0.198 with SMTP id 6mr4087149qeg.48.1380731525403; Wed, 02 Oct 2013 09:32:05 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.67.130 with HTTP; Wed, 2 Oct 2013 09:32:05 -0700 (PDT)
In-Reply-To: <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
Date: Wed, 2 Oct 2013 12:32:05 -0400
X-Google-Sender-Auth: 216ecl4qG8QsbiK0D62ztsNRGrU
Message-ID: <CALaySJLtMNgCLEUF1DKtVizD4z-WyP2qjrFtQK-ADT8TQoOBMA@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Dave Crocker <dcrocker@bbiw.ne>, 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, 02 Oct 2013 16:33:47 -0000

> Hi.  Just to be sure that everyone has the same understanding of
> what is being proposed here, the above says "to Historic" but
> the writeup at
> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
> says "to Internet Standard".   Can one or the other be corrected?

Gakk.  I don't know how that happened.  I'll see if the Secretariat
can fix it.  I'm sure it's my fault......

Sigh.

Barry

From ietfdbh@comcast.net  Wed Oct  2 10:44:12 2013
Return-Path: <ietfdbh@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 1B99221F9978 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 10:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQrlKE6Z3MNx for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 10:44:01 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 7B00D21F90AF for <ietf@ietf.org>; Wed,  2 Oct 2013 10:43:15 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta06.westchester.pa.mail.comcast.net with comcast id YEl91m00A17dt5G56HjFe6; Wed, 02 Oct 2013 17:43:15 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta13.westchester.pa.mail.comcast.net with comcast id YHjE1m00o2yZEBF3ZHjECw; Wed, 02 Oct 2013 17:43:15 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: <ietf@ietf.org>, <iesg@ietf.org>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
In-Reply-To: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
Subject: RE: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
Date: Wed, 2 Oct 2013 13:43:15 -0400
Message-ID: <01cb01cebf96$dfdf5c40$9f9e14c0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLn9VZJ4tImL+G4xH5n1aNH+3gA+ZevQoLg
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1380735795; bh=JpR26H9Xj1XCE/Trudg8rxfoppaP6nb1aCxjVtllTfY=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=SKrVB/3kGUwXNteES6MZwSCMQweV1Rc/jf3MPS3HBdeRnUULxfu2l7klgsarHDm5/ a3SqOxZdbyzpkp+1RAtUk29SxHl+PVxGfc/eZfjR8okdasOkggKDFo9dVZXoIbUE8E HKxcU4rgEPq5wfNYkJu/SxsnI0eF8cmgJ/rCIzQiaPtSpGusVEsly3H6WExraCXcUQ qAZ3v8hwJmHVH23teZAZ6Bk/MPUKmsyL3EsenC/SUmuPH5mrhvsF0S987DgMjx7UXJ qlKWjVt1mNycN8eF5Gdpx5zGC/lFKpxJ5+wVk7Ax4ILBPg7gWxnw/uqHna7v3k9ru4 XsaiGCyHjvwQg==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 17:44:12 -0000

Hi,

The subject lines says the intention is to move to Internet Standard; the
text says the intention is to move to Historic.
This Last Call should probably be re-published with matching intent.

David Harrington
ietfdbh@comcast.net
+1-603-828-1401
> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Wednesday, October 02, 2013 10:42 AM
> To: IETF-Announce
> Subject: Last Call: Change the status of ADSP (RFC 5617) to Internet
Standard
> 
> 
> The IESG has received a request from an individual participant to make
> the following status changes:
> 
> - RFC5617 from Proposed Standard to Historic
> 
> The supporting document for this request can be found here:
> 
> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
> 
> 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-10-30. 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.
> 
> The affected document can be obtained via
> http://datatracker.ietf.org/doc/rfc5617/
> 
> IESG discussion of this request can be tracked via
> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-
> historic/ballot/



From dhc@dcrocker.net  Wed Oct  2 10:48:07 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 8A0A621F9A43 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.454
X-Spam-Level: 
X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[AWL=1.145,  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 Bf+iOOUTXTsK for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 10:47:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C654B21F9D8B for <ietf@ietf.org>; Wed,  2 Oct 2013 10:45:18 -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 r92HjAx2014220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Oct 2013 10:45:13 -0700
Message-ID: <524C5B77.9000002@dcrocker.net>
Date: Wed, 02 Oct 2013 10:44:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com>
In-Reply-To: <7102E82AB09013B67371807F@JcK-HP8200.jck.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, 02 Oct 2013 10:45:13 -0700 (PDT)
Cc: Barry Leiba <barryleiba@computer.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: Wed, 02 Oct 2013 17:48:07 -0000

On 10/2/2013 9:28 AM, John C Klensin wrote:
> After reading the description at the link cited above and
> assuming that "Historic" is actually intended, I wonder,
> procedurally, whether a move to Historic without document other
> than in the tracker is an appropriate substitute for the
> publication of an Applicability Statement that says "not
> recommended" and that explains, at least in the level of detail
> of the tracker entry, why using ADSP is a bad idea.


This suggestion has the dual potential benefits of being inefficient and 
ineffective.

If a spec is Historic, it is redundant to say not recommended.  As in, 
duh...

Even better is that an applicability statement is merely another place 
for the potential implementer to fail to look and understand.

Anyone who fails to understand the implications of Historic (or fails to 
find the correct status) is not going to be better at finding and 
understanding an applicability statement.

ADSP is only worthy of a small effort, to correct its status, to reflect 
its current role in Internet Mail.  Namely, its universal non-use within 
email filtering.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From abdussalambaryun@gmail.com  Wed Oct  2 11:11:46 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 9045221F8578 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 11:11:46 -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 9h0o2YfS65LT for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 11:11:40 -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 45A2221F9D50 for <ietf@ietf.org>; Wed,  2 Oct 2013 11:10:04 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so1386637pad.28 for <ietf@ietf.org>; Wed, 02 Oct 2013 11:09:52 -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=gL9qkSW/37Z8GfxTu2XkoMiFBwHRniQs0ErBh3dJuxs=; b=zJuYAB3/hkznKdoyApB0tKeL+uZCKkpcuHkcwkj1PX94DMDmNaP2EyTMo4gLmbQQpj zIN/BpgN79KSGFag6vbkbX7BLiCMxH6+f2nRmB4i+qW7RmbWom/aqnArVnPhrHVZqqS9 mxIILpEg8WXbzMN5hp6wxm0yACcxttX7MUjUoTfFGnPO4FXPU+6W4PSZLGYuwpLUHFTS zBvTw/qxrBZeLQrWswNg34pPficuX1EckineDjR0GdTAuOOXJO5W7JZUcGjRDs/SvqMq GTrbSa+wJxl6U+fBrnivLr2Ug4RR2ARGTcPcNHQd1yzBFHV7Yr5FzrhSkCIuru/PaWq7 rP/A==
MIME-Version: 1.0
X-Received: by 10.66.162.73 with SMTP id xy9mr3689919pab.172.1380737392742; Wed, 02 Oct 2013 11:09:52 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 2 Oct 2013 11:09:52 -0700 (PDT)
Date: Wed, 2 Oct 2013 19:09:52 +0100
Message-ID: <CADnDZ88GJqRqSDtYTAK856DFfzF6Hjii4YB7H+aYMFkWxq_YzA@mail.gmail.com>
Subject: RE: [Tools-discuss] independant submissions that update standards track, and datatracker
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bacc3cad2979804e7c5f900
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 18:11:46 -0000

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

>While I think that individual submissions that are not the result of
consensus do not belong on a WG page.

Where do they belong? I prefer that they belong under the Area page, but is
there an area page, not sure why was that not a good idea.


>  But, if the document was the result of
> consensus, but did not occur in a WG because the WG had closed, I think
> that
> perhaps it should appear there anyway.
>

I agree, but still I think an area page is required, some day in the future
may be the Area will expire or be changed by the community, so don't we
should think where is the history of these areas. Also our procedural RFCs
and BCPs are not related to General Area, I prefer to see them all under an
area related, some day this general area may change as well (may be called
Procedural Area).

I agree that the way documents are related to IETF-fields or IETF-areas is
not an easy way for tracking information, also the documents are not much
connected but more separated (IETF is divided in WGs which creates
division/differences in documents of the same field). As once one AD
proposed Cross-Areas in IETF, I want to add proposing Cross-WGs, all are
responsible for related issues in IETF (i.e. Areas and Groups).

AB

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br>
<br>
&gt;While I think that individual submissions that are not the result of<br=
>
consensus do not belong on a WG page. <div>=A0</div><div>Where do they belo=
ng? I prefer that they belong under the Area page, but is there an area pag=
e, not=A0sure why was that not a good idea.</div><div>=A0</div><blockquote =
style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(20=
4,204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_qu=
ote">
=A0But, if the document was the result of<br>
consensus, but did not occur in a WG because the WG had closed, I think tha=
t<br>
perhaps it should appear there anyway.<br></blockquote><div>=A0</div><div>I=
 agree, but still I think an area page is required, some day in the future =
may be the Area will expire or be changed by the community, so don&#39;t we=
 should think where is the history of these areas.=A0Also our procedural RF=
Cs and BCPs are not related to General Area, I prefer to see them all under=
 an area related, some day this general area may change as well (may be cal=
led Procedural Area).</div>
<div>=A0</div><div>I agree that the way documents are related to IETF-field=
s or IETF-areas is not an easy way for tracking information, also the docum=
ents are not much connected but more separated (IETF is divided in WGs whic=
h creates division/differences in documents of the same field). As once one=
 AD proposed Cross-Areas in IETF, I want to add proposing Cross-WGs, all ar=
e responsible for related issues in IETF=A0(i.e. Areas and Groups).</div>
<div>=A0</div><div>AB</div><div>=A0</div></div></div></div>

--047d7bacc3cad2979804e7c5f900--

From john-ietf@jck.com  Wed Oct  2 11:50:47 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 3940121F9FA4 for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 11:50:47 -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 ODU3-XBoc6Yt for <ietf@ietfa.amsl.com>; Wed,  2 Oct 2013 11:50:34 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7740F21F938E for <ietf@ietf.org>; Wed,  2 Oct 2013 11:46: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 1VRRR2-000L1e-Nx; Wed, 02 Oct 2013 14:46:08 -0400
Date: Wed, 02 Oct 2013 14:46:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
Message-ID: <6D80EE3E9D28D2F9CB34E260@JcK-HP8200.jck.com>
In-Reply-To: <524C5B77.9000002@dcrocker.net>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com> <524C5B77.9000002@dcrocker.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: Barry Leiba <barryleiba@computer.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, 02 Oct 2013 18:50:47 -0000

I assume we will need to agree to disagree about this, but...

--On Wednesday, October 02, 2013 10:44 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> If a spec is Historic, it is redundant to say not recommended.
> As in, duh...

"Duh" notwithstanding, we move documents to Historic for many
reasons.  RFC 2026 lists "historic" as one of the reasons a
document may be "not recommended" (Section 3.3(e)) but says only
"superceded... or is for any other reason considered to be
obsolete" about Historic (Section 4.2.4).  That is entirely
consistent with Maturity Levels and Requirement Levels being
basically orthogonal to each other, even if "Not Recommended"
and "Internet Standard" are presumably mutually exclusive.

> Even better is that an applicability statement is merely
> another place for the potential implementer to fail to look
> and understand.

Interesting.   If a potential implementer or other potential
user of this capability fails to look for the status of the
document or protocol, then the reclassification to Historic
won't be found and this effort is a waste of the community's
time.  If, by contrast, that potential user checks far enough to
determine that the document has been reclassified to Historic,
why is it not desirable to point that user to a superceding
document that explains the problem and assigns as requirement
status of "not recommended"?  

The situation would be different if a huge amount of additional
work were involved but it seems to me that almost all of the
required explanation is already in the write-up and that the
amount of effort required to approve an action consisting of a
document and a status change is the same as that required to
approve the status change only.  If creating an I-D from the
write-up is considered too burdensome and it would help, I'd be
happy to do that rather than continuing to complain.

> ADSP is only worthy of a small effort, to correct its status,
> to reflect its current role in Internet Mail.  Namely, its
> universal non-use within email filtering.

If the specification had been universally ignored, I'd think
that a simple status change without further documentation was
completely reasonable.  However, the write-up discusses "harm
caused by incorrect configuration and by inappropriate use",
"real cases", and effects from posts from users.  That strongly
suggests that this is a [mis]feature that has been sufficiently
deployed to cause problems, not someone that is "universally
non-used".  And that, IMO, calls for a explanation --at least to
the extent of the explanation in the write-up-- as to why ADSP
was a bad idea, should be retired where it is used, and should
not be further deployed.  

best,
   john


From david.black@emc.com  Wed Oct  2 12:17:52 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 100B821F9FBA; Wed,  2 Oct 2013 12:17:52 -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=[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 euffcUSVarYD; Wed,  2 Oct 2013 12:17:41 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFE321E8087; Wed,  2 Oct 2013 12:01:54 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r92J1j38023009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Oct 2013 15:01:48 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com r92J1j38023009
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1380740508; bh=X7lduZ7wpQR/3+Pi+YVVUGVR1Vg=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=HhrXdYw/98o8dwoHanI7sKb/ktp1bpjYBhFW4uat+hSJI6YzRCqZkXCeQViA53oSZ 6P4NZhnSFhVVPWLymDH+AZnZ7Pljpo51U4uIWtwJrtQUiuO37aRIGlEk+9hM7dGZoP 8S0c6CHI7CEynKH0MgUC0hDyjoK0nQk3Vg502wQ8=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com r92J1j38023009
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd02.lss.emc.com (RSA Interceptor); Wed, 2 Oct 2013 15:01:29 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r92J1Qd8019701 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 2 Oct 2013 15:01:27 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Wed, 2 Oct 2013 15:01:26 -0400
From: "Black, David" <david.black@emc.com>
To: Stephen Kent <kent@bbn.com>
Date: Wed, 2 Oct 2013 15:01:25 -0400
Subject: RE: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
Thread-Topic: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
Thread-Index: Ac6/gKKlpXrFq8WgQde2122jwIv/AAAIRtdQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712025DCE1A00@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712025DBB6FDA@MX15A.corp.emc.com> <5249BE21.4060702@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DBB7B41@MX15A.corp.emc.com> <524B3998.20009@bbn.com> <8D3D17ACE214DC429325B2B98F3AE712025DCE1852@MX15A.corp.emc.com> <524C35CC.1030501@bbn.com>
In-Reply-To: <524C35CC.1030501@bbn.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_8D3D17ACE214DC429325B2B98F3AE712025DCE1A00MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-EMM-GWVC: 1
X-RSA-Classifications: public
X-EMM-McAfeeVC: 1
Cc: "sidr@ietf.org" <sidr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "stbryant@cisco.com" <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: Wed, 02 Oct 2013 19:17:52 -0000

--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1A00MX15Acorpemcc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sounds good - I look forward to seeing the revised draft.

Thanks,
--David

From: Stephen Kent [mailto:kent@bbn.com]
Sent: Wednesday, October 02, 2013 11:04 AM
To: Black, David
Cc: achi@cs.unc.edu; General Area Review Team (gen-art@ietf.org); stbryant@=
cisco.com; ietf@ietf.org; sidr@ietf.org
Subject: Re: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06

David,


Steve,

I think the modified introduction text suffices to connect the PATHSEC and =
BGPsec terms, but I don't think that referring to the SIDR WG charter for t=
he PATHSEC goals is reasonable - an RFC is an archive document, whereas a W=
G charter is not.
The revised intro text now paraphrases the text from the SIDR charter that
describes the path security goals.

Steve

--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1A00MX15Acorpemcc_
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 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";
	color:black;}
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;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Courier New"'>Sounds good &#82=
11; I look forward to seeing the revised draft.<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"'><=
o:p>&nbsp;</o:p></span></p><div><div><p class=3DMsoNormal><span style=3D'fo=
nt-size:10.0pt;font-family:"Courier New"'>Thanks,<br>--David</span><span st=
yle=3D'font-size:11.0pt;font-family:"Courier New"'><o:p></o:p></span></p></=
div></div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
"Courier New"'><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:"Tahoma","sans-ser=
if";color:windowtext'>From:</span></b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif";color:windowtext'> Stephen Kent [mailto:kent@b=
bn.com] <br><b>Sent:</b> Wednesday, October 02, 2013 11:04 AM<br><b>To:</b>=
 Black, David<br><b>Cc:</b> achi@cs.unc.edu; General Area Review Team (gen-=
art@ietf.org); stbryant@cisco.com; ietf@ietf.org; sidr@ietf.org<br><b>Subje=
ct:</b> Re: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06<o:p></o:p><=
/span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>David,<br><br><br><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>Steve,</span><o:p></o:p></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-=
size:10.0pt;font-family:"Courier New"'>I think the modified introduction te=
xt suffices to connect the PATHSEC and BGPsec terms, but I don&#8217;t thin=
k that referring to the SIDR WG charter for the PATHSEC goals is reasonable=
 &#8211; an RFC is an archive document, whereas a WG charter is not.</span>=
<o:p></o:p></p><p class=3DMsoNormal>The revised intro text now paraphrases =
the text from the SIDR charter that<br>describes the path security goals.<b=
r><br>Steve<o:p></o:p></p></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712025DCE1A00MX15Acorpemcc_--

From superuser@gmail.com  Wed Oct  2 14:04:21 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 4E13921F9D2A; Wed,  2 Oct 2013 14:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 pmE5ZyuqcyQF; Wed,  2 Oct 2013 14:04:14 -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 0D67621F9C05; Wed,  2 Oct 2013 14:04:04 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id l18so6929516wgh.0 for <multiple recipients>; Wed, 02 Oct 2013 14:04: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=+M4GBse0SPxFdzjn4kafhorAQDzvlsc31XLD4hy9E54=; b=tnyUah8bXC7MyGhvg61ySZw2SIZYC2+9ez9oD2zCLJDOhgcHVD9u50QPo2ysX0awaK 5YMnUXuAJinBky/9zAH1HqxEA/4nW2oNfeaFJNq1Blo0GuzBf8YmgxfPSSRegEct5MM2 9lOdjNwHrFbqO0IV7SCoef2Dmq6xRaI/duLqp6E97mXTFIg7vFD5nTj3MtoC5dSBwUR1 24xWecz3JJ3oL8BtarJm49d2FxJgLd1pXaPlnzGIU2OJJnPbsOVgBYtXf7cSdD2AI0QI pBR8iUpzYh36o5y11VpnN7gXogYSdsQQwHXla+yxfV6lxYKH/Cnxh8oCXqRDH3P5S6n3 445Q==
MIME-Version: 1.0
X-Received: by 10.180.72.226 with SMTP id g2mr25257483wiv.52.1380747842811; Wed, 02 Oct 2013 14:04:02 -0700 (PDT)
Received: by 10.180.18.202 with HTTP; Wed, 2 Oct 2013 14:04:02 -0700 (PDT)
In-Reply-To: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com>
Date: Wed, 2 Oct 2013 14:04:02 -0700
Message-ID: <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d043890edb1fe4a04e7c86875
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Oct 2013 21:04:21 -0000

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

On Wed, Oct 2, 2013 at 7:41 AM, The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has received a request from an individual participant to make
> the following status changes:
>
> - RFC5617 from Proposed Standard to Historic
>
> The supporting document for this request can be found here:
>
> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
> [...]
>

I support this change, for the reasons articulated in the request and in
this thread.

I am the lead developer and maintainer of OpenDKIM, an open source
implementation of DKIM and related standards, including VBR, ADSP, the
recent REPUTE work, and some others.  It is widely deployed, including use
at a few of the largest operators.  An informal survey was done on one of
the mailing lists where this package is supported, asking which operators
do ADSP queries and which act upon the results.  I have so far only
received a half dozen answers to this, but the consensus among them is
clear: All of the respondents either do not check ADSP, or check it but do
nothing with the results.  One operator puts disposition of messages based
on ADSP results into the hands of its users, but no statistics were offered
about how many of these users have ADSP-based filtering enabled.  That same
operator intends to remove that capability once this status change goes
into effect.

-MSK

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

<div dir=3D"ltr">On Wed, Oct 2, 2013 at 7:41 AM, The IESG <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secr=
etary@ietf.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IESG has received a request from an indi=
vidual participant to make<br>
the following status changes:<br>
<br>
- RFC5617 from Proposed Standard to Historic<br>
<br>
The supporting document for this request can be found here:<br>
<br>
<a href=3D"http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-hi=
storic/" target=3D"_blank">http://datatracker.ietf.org/doc/status-change-ad=
sp-rfc5617-to-historic/</a><br>
[...]<br></blockquote><div><br></div><div>I support this change, for the re=
asons articulated in the request and in this thread.<br><br></div><div>I am=
 the lead developer and maintainer of OpenDKIM, an open source implementati=
on of DKIM and related standards, including VBR, ADSP, the recent REPUTE wo=
rk, and some others.=A0 It is widely deployed, including use at a few of th=
e largest operators.=A0 An informal survey was done on one of the mailing l=
ists where this package is supported, asking which operators do ADSP querie=
s and which act upon the results.=A0 I have so far only received a half doz=
en answers to this, but the consensus among them is clear: All of the respo=
ndents either do not check ADSP, or check it but do nothing with the result=
s.=A0 One operator puts disposition of messages based on ADSP results into =
the hands of its users, but no statistics were offered about how many of th=
ese users have ADSP-based filtering enabled.=A0 That same operator intends =
to remove that capability once this status change goes into effect.<br>
<br></div><div>-MSK<br></div></div></div></div>

--f46d043890edb1fe4a04e7c86875--

From adrian@olddog.co.uk  Thu Oct  3 01:50:26 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 EFBE021F9633; Thu,  3 Oct 2013 01:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level: 
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[AWL=0.253,  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 S1yWNJkpT1by; Thu,  3 Oct 2013 01:50:13 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B79E621F9767; Thu,  3 Oct 2013 01:48: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 r938mccf011403;  Thu, 3 Oct 2013 09:48:38 +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 r938mZkw011333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Oct 2013 09:48:36 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> 
Date: Thu, 3 Oct 2013 09:48:32 +0100
Message-ID: <031601cec015$591026c0$0b307440$@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: Ac7AFRRiZXQ2TaqrQyKn1YTQ2cj7dw==
Content-Language: en-gb
Cc: mpls@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, 03 Oct 2013 08:50:26 -0000

Thanks for this document which was surprisingly readable.

I have a number of comments from my AD review, but they are all
trivial and can be handled as IETF last call comments.

Thanks,
Adrian

---

Nurit will want to change the minor details or her affiliation.

---

Abstract
Expand MPLS-TP and PW on first use.
Expand MS
s/recommendations/Recommendations/  >>> Apply throughout document
s/nor/or/

---

Section 1

s/telecommunication/Telecommunication/

---

Section 1.2

s/Administration and Maintenance/Administration, and Maintenance/

---

Section 3.4

s/APPENDIX/Appendix/

---

Section 3.5

Please expand PW

---

Section 3.7

One might ask whether a co-routed bidirectional path that traverses a
LAG or a link bundle uses the same component links in both directions.

---

Section 3.8 could probably usefully mention routing along with 
signaling.

---

Section 3.11

s/physical channels/a physical channel/

---

Section 3.16

Please expand LSR

---

One paragraph in 3.17 is a bit wild.

   Therefore, in the context of MPLS-TP LSP or PW Maintenance Entity
   (defined below) LERs and T-PEs can be MEPs while LSRs and S-PEs can
   be MIPs. In the case of Tandem Connection Maintenance Entity
   (defined below), LSRs and S-PEs can be either MEPs or MIPs.

s/context of/context of a/

"PW Maintenance Entity" is not defined below (I think).

Please expand LER

I don't find the definition of "Tandem Connection Maintenance Entity"
Maybe you could say
...the case of a Maintenance Entity for a Tandem Connection (defined below)


Please expand S-PE

---

Section 3.19
Penultimate paragraph
Second instance  s/(e.g. count packets)./(e.g. counts packets)./

---

Section 3.23

s/described in three ways:/described in one of three ways:/
s/Sub-Path Maintenance Element, and/Sub-Path Maintenance Element, or/
s/as a Tandem Connections./as a Tandem Connection./

---

Section 3.23.2  Section header

s/(SMPE):/(SPME):/

---

Section 3.35

The use of pipe ("|") and curly braces ("{" and "}") could usefully be
replaced with English language.

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 02 October 2013 22:45
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for
the
> Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP)
> drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational
> RFC
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'A Thesaurus for the Terminology used in Multiprotocol Label Switching
>    Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport
>    Network Recommendations.'
>   <draft-ietf-mpls-tp-rosetta-stone-12.txt> as Informational RFC


From olaf@NLnetLabs.nl  Thu Oct  3 01:57:46 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F15A621F9946 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 01:57:45 -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=[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 5IEV+Y3JJ93F for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 01:57:39 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 501C021F9E33 for <ietf@ietf.org>; Thu,  3 Oct 2013 01:56:38 -0700 (PDT)
Received: from [192.168.146.139] ([146.247.8.13]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r938uUtN055022 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 3 Oct 2013 10:56:31 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r938uUtN055022
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1380790594; bh=IGeNajmd36ODaPM7S9OJTdcZHBLXq9MDatlsIREgddM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=WZWWKbCfAo8MiQ7wm/y3dBQckXbvY3gbLUJqVuiubFa5vTkIpjqg0O66K9hQtfIgY sfT/OORUYH5FLUFqsQ73DuB4YwyuCB/i+y0wi64/3kA1Ma7sy53byWfNHRE7TeT/so vcy9cYGtiqIPLwJaueYsZIiT2zY9/UeZ3OCFYGw0=
X-Authentication-Warning: open.nlnetlabs.nl: Host [146.247.8.13] claimed to be [192.168.146.139]
Content-Type: multipart/signed; boundary="Apple-Mail=_13319BA8-1733-44A0-931C-F371A1DBD295"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-kolkman-proposed-standards-clarified-03.txt> (Characterization of Proposed Standards) to Best Current Practice
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <5242BE97.7030501@cisco.com>
Date: Thu, 3 Oct 2013 10:56:32 +0200
Message-Id: <CBFBF6D6-5984-4564-9123-AE14405DB80D@NLnetLabs.nl>
References: <20130918181807.14400.46970.idtracker@ietfa.amsl.com> <5242BE97.7030501@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Thu, 03 Oct 2013 10:56:32 +0200 (CEST)
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, 03 Oct 2013 08:57:46 -0000

--Apple-Mail=_13319BA8-1733-44A0-931C-F371A1DBD295
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_C1679C49-23B2-4DC2-A381-34087F6BD0A1"


--Apple-Mail=_C1679C49-23B2-4DC2-A381-34087F6BD0A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 25 sep. 2013, at 12:44, Benoit Claise <bclaise@cisco.com> wrote:

> Reading this draft, I wonder: why would someone still want to go for =
Internet Standard, since PS is "mature", "as mature as final standards =
from other standards development organizations"? Maybe you want to =
expand on this.


There is a real difference IMHO. For an Internet Standard the IETF came =
back after some time and assessed that there were really no hurdles to =
gain interoperability. It is an IETF seal of an observed =
track-record.That is a _maintenance_ issue.

An important piece of standardization is the maintenance of the =
standards suite.=20


Not sure if that needs words in the draft.


Thanks for the editorial nits. I'll safe them for after last call has =
finished.

--Olaf

--Apple-Mail=_C1679C49-23B2-4DC2-A381-34087F6BD0A1
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 25 sep. 2013, at 12:44, Benoit Claise &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span style=3D"font-family: Helvetica; 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; background-color: rgb(255, 255, 255); =
display: inline !important; float: none; ">Reading this draft, I wonder: =
why would someone still want to go for Internet Standard, since PS is =
"mature", "as mature as final standards from other standards development =
organizations"? Maybe you want to expand on =
this.</span></blockquote></div><br><div><br></div><div>There is a real =
difference IMHO. For an Internet Standard the IETF came back after some =
time and assessed that there were really no hurdles to gain =
interoperability. It is an IETF seal of an observed track-record.That is =
a _maintenance_ issue.</div><div><br></div><div>An important piece of =
standardization is the maintenance of the standards =
suite.&nbsp;</div><div><br></div><div><br></div><div>Not sure if that =
needs words in the draft.</div><div><br></div><div><br></div><div>Thanks =
for the editorial nits. I'll safe them for after last call has =
finished.</div><div><br></div><div>--Olaf</div></body></html>=

--Apple-Mail=_C1679C49-23B2-4DC2-A381-34087F6BD0A1--

--Apple-Mail=_13319BA8-1733-44A0-931C-F371A1DBD295
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBAgAGBQJSTTFAAAoJEFRqER47aqpkhjQP/14+yR+6Nybk78Y/2Jr9hPtB
9GvYzYvRLywN3l5H6Vrm2eon9MYY4JnREGFd4mso76cePrKjfYW7MQwS5qeNz0n2
Wm9QhLFpJEE4w33H2fGBS1r3P168U83w2au1o6tPn2VLZxoxidGmJwof20RPEZYk
4KgSyTYFtzpEOEU2U6aSfYAFbav+Cugyom72guXP1f1JJ7RaJoUge8f81cpad6FI
M29tjlzPMkWyFTl3HHMmQ0LUP0xzecrO5TLy3mFf47lCrThaw2EReNljdM+1vKIx
EvIwi9Fsz9OzvHRbXsKbwc9i9RbG4jgyI55x+IXk+JA6BOibscefVM+48hdaGMZP
3J8NTShXRGBw8hrVSshfJ2GNOK5gplfWQHnn3s1B7gVrBUJZ8nGt94gR4ftAFFLW
pgntZiYemJMFOLa1mRe8n9BvWp+HNFfSSs9Wc4Kz6Sno6VfzS14kfUG6nUb3oZL8
lA2ki002EqjmDpvv6X4BQfgUNdaEsb6PMQSDA7cE+uXfjLaCsIH26SN/fMKTjon9
DNxQGhPUvbelzytPcMKL/w77QBRM8GPvmMswNuqWJLDOaXv8XzbZ+1Uyoescnc9w
BaBtdcQsjp2Z4RzBY4JbzPt7ajVUMLfBx5deI+A0u2dx8oTN1BYcI8BWeWZRkLFv
cFcrkLw3yT+OCrNNC2fL
=aLeB
-----END PGP SIGNATURE-----

--Apple-Mail=_13319BA8-1733-44A0-931C-F371A1DBD295--

From chris.dearlove@baesystems.com  Thu Oct  3 04:05:10 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 A3AB121F9FC8 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:05:10 -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 ux2QEb+4n6mo for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:04:59 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id C957421F9928 for <ietf@ietf.org>; Thu,  3 Oct 2013 04:02:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1025,1371078000"; d="scan'208";a="318163992"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Oct 2013 12:02:34 +0100
X-IronPort-AV: E=Sophos;i="4.90,1025,1371078000"; d="scan'208";a="30678459"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 03 Oct 2013 12:02:33 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0328.009; Thu, 3 Oct 2013 12:02:34 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: NIST documents
Thread-Topic: NIST documents
Thread-Index: Ac7AJwX0W7rBM3a4SPuQRqRxFoxDqQ==
Date: Thu, 3 Oct 2013 11:02:33 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@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, 03 Oct 2013 11:05:10 -0000

One draft I'm working on references some standard NIST cryptographic docume=
nts. (RFCs don't include everything we need.)  I need to check some details=
 therein. Unfortunately the current US government shutdown has taken NIST's=
 website, including those documents, offline. And (not considering this pos=
sibility) I didn't download copies of them.

Any link to where copies of such documents are kept would be useful. (Of co=
urse I haven't been able to check the copyright on them to know if that's l=
egal, so there may be no appropriate site.)

Otherwise, consider the above an observation.

-- =

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 rdroms.ietf@gmail.com  Thu Oct  3 04:15:32 2013
Return-Path: <rdroms.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 6DAD621F9E83 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:15: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 MIkX-76a8pnL for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:15:25 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id B2D5A21F9E40 for <ietf@ietf.org>; Thu,  3 Oct 2013 04:11:14 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id t7so1497050qcv.35 for <ietf@ietf.org>; Thu, 03 Oct 2013 04:11:13 -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; bh=9c6cTDCCve6Id60kOjymQpEHfRpau2pw8K1ms4MFnRY=; b=avXDBILSAkU5c4QlFCqoVkN73lYZJSyFLvBwzdhK3ZqQgRcWGHZnrkknaut72lEwCO yvTaok7KTs4SLGo57mJ5Suh3DxzMs+bviDk5ONpfpZIdajp3AYeigVNal6xIY4Vs72mc bYxseW59PXlC4Bkslpz9+J8nCsz8n4prAERwheIyTp2NwDjVysSErl7Q4pExrDY4qvU1 4LaLlOsJzr0exMlMIpfDM8o6vIrR1uX4bwMKMWhFHDfGurquNSrtD0UkM1UMODPHDvCy +hQmZKbuRUX6fdnLsoCr2sxjSRKM4c+Z9s44h0SVC92pheC2Q/ETvp8gLPfK+GJfmXHJ 08Cg==
X-Received: by 10.49.116.19 with SMTP id js19mr64506qeb.34.1380798672101; Thu, 03 Oct 2013 04:11:12 -0700 (PDT)
Received: from che-vpn-cluster-2-199.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id da3sm12697432qeb.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 04:11:11 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: NIST documents
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net>
Date: Thu, 3 Oct 2013 07:11:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F803B94D-9DA9-4954-82CB-E3B532BDCCC7@gmail.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.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, 03 Oct 2013 11:15:32 -0000

Try Wayback, http://archive.org

- Ralph

On Oct 3, 2013, at 7:02 AM 10/3/13, "Dearlove, Christopher (UK)" =
<chris.dearlove@baesystems.com> wrote:

> One draft I'm working on references some standard NIST cryptographic =
documents. (RFCs don't include everything we need.)  I need to check =
some details therein. Unfortunately the current US government shutdown =
has taken NIST's website, including those documents, offline. And (not =
considering this possibility) I didn't download copies of them.
>=20
> Any link to where copies of such documents are kept would be useful. =
(Of course I haven't been able to check the copyright on them to know if =
that's legal, so there may be no appropriate site.)
>=20
> Otherwise, consider the above an observation.
>=20
> --=20
> 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 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> 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
>=20
>=20
> ********************************************************************
> 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.
> ********************************************************************
>=20


From chris.dearlove@baesystems.com  Thu Oct  3 04:26:14 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 E495321F9E40 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:26:13 -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 uv02YU+liJQL for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:26:03 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id E741921F9E94 for <ietf@ietf.org>; Thu,  3 Oct 2013 04:21:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1025,1371078000"; d="scan'208";a="318171240"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Oct 2013 12:21:42 +0100
X-IronPort-AV: E=Sophos;i="4.90,1025,1371078000"; d="scan'208";a="30682364"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 03 Oct 2013 12:21:42 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0328.009; Thu, 3 Oct 2013 12:21:42 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: RE: NIST documents
Thread-Topic: NIST documents
Thread-Index: Ac7AJwX0W7rBM3a4SPuQRqRxFoxDqf//87aA///tgNA=
Date: Thu, 3 Oct 2013 11:21:41 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF5519@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net> <F803B94D-9DA9-4954-82CB-E3B532BDCCC7@gmail.com>
In-Reply-To: <F803B94D-9DA9-4954-82CB-E3B532BDCCC7@gmail.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"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 03 Oct 2013 11:26:14 -0000

Good call, thanks Ralph.

Should it be useful to anyone else, the relevant link for what I was after =
is
http://web.archive.org/web/20130907062401/http://csrc.nist.gov/publications=
/PubsFIPS.html

(The first link I've tried works.)

--=20
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: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: 03 October 2013 12:11
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org list
Subject: Re: NIST documents

----------------------! 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.
--------------------------------------------------------

Try Wayback, http://archive.org

- Ralph

On Oct 3, 2013, at 7:02 AM 10/3/13, "Dearlove, Christopher (UK)" <chris.dea=
rlove@baesystems.com> wrote:

> One draft I'm working on references some standard NIST cryptographic docu=
ments. (RFCs don't include everything we need.)  I need to check some detai=
ls therein. Unfortunately the current US government shutdown has taken NIST=
's website, including those documents, offline. And (not considering this p=
ossibility) I didn't download copies of them.
>=20
> Any link to where copies of such documents are kept would be useful. (Of =
course I haven't been able to check the copyright on them to know if that's=
 legal, so there may be no appropriate site.)
>=20
> Otherwise, consider the above an observation.
>=20
> --=20
> 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 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>=20
> 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
>=20
>=20
> ********************************************************************
> 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.
> ********************************************************************
>=20



From alexandru.petrescu@gmail.com  Thu Oct  3 04:39:08 2013
Return-Path: <alexandru.petrescu@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 3A2DF21F99BD for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=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 cWyKflgPIcY4 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:38:55 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 40EF821F9E9D for <ietf@ietf.org>; Thu,  3 Oct 2013 04:34:49 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r93BYk9K012183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 3 Oct 2013 13:34:46 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r93BYkoA007943 for <ietf@ietf.org>; Thu, 3 Oct 2013 13:34:46 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r93BYZJp019320 for <ietf@ietf.org>; Thu, 3 Oct 2013 13:34:46 +0200
Message-ID: <524D564B.9040704@gmail.com>
Date: Thu, 03 Oct 2013 13:34:35 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: NIST and NASA documents
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Thu, 03 Oct 2013 11:39:08 -0000

Le 03/10/2013 13:02, Dearlove, Christopher (UK) a écrit :
> One draft I'm working on references some standard NIST cryptographic
>  documents. (RFCs don't include everything we need.)  I need to check
>  some details therein. Unfortunately the current US government
> shutdown has taken NIST's website, including those documents,
> offline. And (not considering this possibility) I didn't download
> copies of them.
>
> Any link to where copies of such documents are kept would be useful.
>  (Of course I haven't been able to check the copyright on them to
> know if that's legal, so there may be no appropriate site.)
>
> Otherwise, consider the above an observation.
>

Same here - I have problems accessing documents at NASA about IP network
mobility.

The error message says:
"Due to the lapse in federal government funding, this website is not
available. We sincerely regret this inconvenience. For information about
available government services, visit USA.gov."

(roland.grc.nasa.gov/ redirects to notice.usa.gov/)

Whereas I could find the document in Google's cache, I am dubious
about this situation.

I would have not imagined that documents in a US gov website would
become unavailable - for political reasons?  I would imagine engineering
problems like routing system failures, Internet meltdown...

Alex


From rdroms.ietf@gmail.com  Thu Oct  3 04:49:11 2013
Return-Path: <rdroms.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 4094921E8099 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:49:11 -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 PWANdsEdxVdW for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 04:49:04 -0700 (PDT)
Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 125A621F9AE7 for <ietf@ietf.org>; Thu,  3 Oct 2013 04:42:38 -0700 (PDT)
Received: by mail-qa0-f50.google.com with SMTP id j7so1534658qaq.9 for <ietf@ietf.org>; Thu, 03 Oct 2013 04:42:36 -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 :content-transfer-encoding:message-id:references:to; bh=u4GNhj/n+3jl6ad/10XMbL5GbbRsMXNQwj3yrl0PE40=; b=wB6zSKHr+qwPbrK/FtOcK4rLfS03wKEHMIgVSo4WEde2Wv7zv63SDwLxk6M+EN+/vN tXPuEFIwyStKwwXS3yWz/u84d9CbF3y9JjVCFAWslmj1j2hUhk7D0NRJQFsniXgJvOJF 25C3p3RZgBbZrZPfYJAn0TtnlLpZSB2o42wiJqfgK6nMD84FJPwk4fmPuhoi895ljzGK W/bJc7YZ/oIYESjf14oCyiSS4XzH+lk14xJduTkBn+X0P96W3RR0M6XvomEoCIQZ1W1Y mGzSvJRedf+DoYrSDRJC5GpbPc6RJjk7L7c33E4v/4ylItc2GF88TcnJrcsDiY/HAytr aINw==
X-Received: by 10.224.121.147 with SMTP id h19mr1233779qar.105.1380800556594;  Thu, 03 Oct 2013 04:42:36 -0700 (PDT)
Received: from che-vpn-cluster-2-199.cisco.com (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id y9sm16116160qaj.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 04:42:36 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: NIST and NASA documents
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <524D564B.9040704@gmail.com>
Date: Thu, 3 Oct 2013 07:42:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7BEB764-C904-4CC4-8C3A-71F89D4B73C0@gmail.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net> <524D564B.9040704@gmail.com>
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: Thu, 03 Oct 2013 11:49:11 -0000

On Oct 3, 2013, at 7:34 AM 10/3/13, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Le 03/10/2013 13:02, Dearlove, Christopher (UK) a =E9crit :
>> One draft I'm working on references some standard NIST cryptographic
>> documents. (RFCs don't include everything we need.)  I need to check
>> some details therein. Unfortunately the current US government
>> shutdown has taken NIST's website, including those documents,
>> offline. And (not considering this possibility) I didn't download
>> copies of them.
>>=20
>> Any link to where copies of such documents are kept would be useful.
>> (Of course I haven't been able to check the copyright on them to
>> know if that's legal, so there may be no appropriate site.)
>>=20
>> Otherwise, consider the above an observation.
>>=20
>=20
> Same here - I have problems accessing documents at NASA about IP =
network
> mobility.
>=20
> The error message says:
> "Due to the lapse in federal government funding, this website is not
> available. We sincerely regret this inconvenience. For information =
about
> available government services, visit USA.gov."
>=20
> (roland.grc.nasa.gov/ redirects to notice.usa.gov/)
>=20
> Whereas I could find the document in Google's cache, I am dubious
> about this situation.
>=20
> I would have not imagined that documents in a US gov website would
> become unavailable - for political reasons?  I would imagine =
engineering
> problems like routing system failures, Internet meltdown...

OK, so I'm not going to take a stand about the politics involved.  =
Trying to avoid wearing out my delete key, can we agree that the =
situation is a bummer, there's nothing we can do about it and we have a =
way to route around the damage.  Nothing more to contribute here, please =
move along...

Thanks and this will be my last post in this thread...

- Ralph

>=20
> Alex
>=20


From sob@sobco.com  Thu Oct  3 04:57:36 2013
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBDC21F9D2C; Thu,  3 Oct 2013 04:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 5egTvrfWq0TX; Thu,  3 Oct 2013 04:57:11 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 19EA621F856A; Thu,  3 Oct 2013 04:49:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id C047F309FC2; Thu,  3 Oct 2013 07:49:51 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHy2v5bErEy0; Thu,  3 Oct 2013 07:49:50 -0400 (EDT)
Received: from dhcp3.sobco.com (unknown [136.248.127.173]) by sobco.sobco.com (Postfix) with ESMTPSA id 44F3C309F36; Thu,  3 Oct 2013 07:49:50 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-roll-terminology-13.txt> (Terms used in Ruting for Low power And Lossy Networks) to Informational RFC
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <20131003103439.13078.31787.idtracker@ietfa.amsl.com>
Date: Thu, 3 Oct 2013 07:49:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2814ADA-6A29-4419-9D5F-97310A520A45@sobco.com>
References: <20131003103439.13078.31787.idtracker@ietfa.amsl.com>
To: <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: roll@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 11:57:36 -0000

On Oct 3, 2013, at 6:34 AM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from the Routing Over Low power and =
Lossy
> networks WG (roll) to consider the following document:
> - 'Terms used in Ruting for Low power And Lossy Networks'
>  <draft-ietf-roll-terminology-13.txt> as Informational RFC

"Ruting" - "R=FCting is a municipality in the Nordwestmecklenburg =
district, in Mecklenburg-Vorpommern, Germany"

the first sentence in the abstract says "routing" - maybe the title is =
in need of Vana White?

Scott


From hsantos@isdg.net  Thu Oct  3 05:01:32 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 5809421F84F8 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 05:01:32 -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 8fPGNLJFnyXJ for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 05:01:19 -0700 (PDT)
Received: from dkim.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 38F9021F9951 for <ietf@ietf.org>; Thu,  3 Oct 2013 04:53:57 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3136; t=1380801230; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=OncvI/kb0+ik5vy1rlPenTSffTI=; b=Mq6G4gaBNdbwl8+4FJyu QhNIVJMgHRwOIHuB5zI2wfpw5n18g/tKE9YM5XlAsZzdZQIQtD/VxuvixMNA81qk rq5cHIcO6s8tvsKNq7bCWHp6WkbbK2/yJNQskryPXNO16/dc5zr0o8RzUkS/A+39 8GUVUwAIftiNHNymMCIoIvs=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 07:53:50 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2968736922.4443.6100; Thu, 03 Oct 2013 07:53:50 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3136; t=1380800845; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=E2P6yJ2 l4PC5z+KHNV4slKy6SxzWzb7H03Lx0Pf1PTY=; b=oSBy6f+/M1Gu8WojR2fwkgE 3Xb9QSs+BRy/U3K846lxusBHhGGEGrH68IKRf59l2X8lED8qcXh1AqKUXuaCy69h 8MioUuzjNtDb+p1/XiAgoEmubhDFPgoMHKWwW39cH695nKvaHvHP/thGCUInVfDa 65g+qwuEx6PjJblIzU3o=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 07:47:25 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2415125878.9.7576; Thu, 03 Oct 2013 07:47:24 -0400
Message-ID: <524D5ACF.3020008@isdg.net>
Date: Thu, 03 Oct 2013 07:53:51 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com>
In-Reply-To: <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 12:01:32 -0000

On 10/2/2013 5:04 PM, Murray S. Kucherawy wrote:
> On Wed, Oct 2, 2013 at 7:41 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
>> The IESG has received a request from an individual participant to make
>> the following status changes:
>>
>> - RFC5617 from Proposed Standard to Historic
>>
>> The supporting document for this request can be found here:
>>
>> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>> [...]
>>
>
> I support this change, for the reasons articulated in the request and in
> this thread.
>
> I am the lead developer and maintainer of OpenDKIM, an open source
> implementation of DKIM and related standards, including VBR, ADSP, the
> recent REPUTE work, and some others.  It is widely deployed, including use
> at a few of the largest operators.  An informal survey was done on one of
> the mailing lists where this package is supported, asking which operators
> do ADSP queries and which act upon the results.  I have so far only
> received a half dozen answers to this, but the consensus among them is
> clear: All of the respondents either do not check ADSP, or check it but do
> nothing with the results.  One operator puts disposition of messages based
> on ADSP results into the hands of its users, but no statistics were offered
> about how many of these users have ADSP-based filtering enabled.  That same
> operator intends to remove that capability once this status change goes
> into effect.
>
> -MSK

I don't believe this would be a fair assessment of industry wide 
support -- using only one API to measure. There are other APIs and 
proprietary systems who most likely are not part of the OpenDKIM 
group.  There are commercial operations using DKIM and ADSP is part of 
it.

The interop problem is clearly due intentional neglect by specific MLS 
(Mailing List Software) of the DKIM security protocol, not because of 
the protocol itself.  Support of the protocol does not cause an 
interop problem -- it helps support the DKIM security protocol.    The 
ADSP (RFC5617) protocol is part of the DKIM security threat mitigation 
model (RFC4686), the DKIM Service Architecture (RFC5585), the DKIM 
Deployment Guide (RFC5863) and also the Mailing List for DKIM 
guideline (rfc6377).   That is FOUR documents.

Applicability and Impact reports *should* to be done before pulling 
the rug from under the non-OpenDKIM market feet.  In addition, it 
appears part of the request is to help move an alternative DMARC 
protocol forward. Why would the DMARC replacement do better?  Why 
should commercial development for ADSP be stopped and removed from 
products, and now a new investment for DMARC be done?  Would this 
resolve the apparent interop problem with the specific Mailing List 
Software who refuse to support a DKIM security protocol?

More importantly, why should any small operator and participant of the 
IETF continue to support IETF projects if their support is ignored and 
projects will be ended without their input or even explaining why it 
should be ended?  That doesn't play well for the IETF Diversity 
Improvement Program.


-- 
HLS



From dave@cridland.net  Thu Oct  3 05:06:01 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 5DD1321F9635 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 05:06:01 -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 J6tL5SmjzoAP for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 05:06:01 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id AE3F121F96B1 for <ietf@ietf.org>; Thu,  3 Oct 2013 05:00:50 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id eh20so1805330lab.5 for <ietf@ietf.org>; Thu, 03 Oct 2013 05:00: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=4YABXTf+Jw3T8xpuBo67zEd7xBdtgvGLh1uHHMEfbz4=; b=V8OWk9ZqB3kwJZuIXtXZLdQqpGR9L4V5OjiJ060Rr0sSbHlUyFxjsB9jSXjjlYPqSH Q70m/wyhGQbZ0zrsHh4+X+vxWbPvUDV7Oy+F6gvwnYdQnHQtcvs5A5IIcpwz1Y3A7DlF liBBgEs8QAHGLgOjELGDaLZ03Pa/jXjtAjDcc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4YABXTf+Jw3T8xpuBo67zEd7xBdtgvGLh1uHHMEfbz4=; b=QquTmzB/5FDtPovn/tiW/+TNdc1ice41k9vEe2EIlbqVGtLZZ5P+Z8vvuNYygtUoer IkTQgsO7dznJVpXr0ofSRd2zknnJ9I4GAYIq5rxcZhu7VehfoKPEgf7rcMRHPkbqV2iK G5pdjS7Na1MJiPQd4mOJviM0BbKDAs7C8gKXBTva45TPnhH9PJyuyHxP8HnfdCFAtigH G3uUPVqZQJbluIX3G5+NqVjBkACzG1MCJsVSUow1HuwXAykN0NLmYQwwcKlNPrVRiIez pP+IxfhyhL+Uv7HvYyPkKFzD887RrGqvrcczNEJIcrNzICuRXs4/wRD04uC1yq3IAni8 Cvvg==
X-Gm-Message-State: ALoCoQncOQ1NeZkTv3YN+R60ItRfn+detPSo/+t5q8YJnlld0fC0FSPlFRIECXJg+GBDXM4UWrod
MIME-Version: 1.0
X-Received: by 10.152.30.74 with SMTP id q10mr6671707lah.27.1380801648254; Thu, 03 Oct 2013 05:00:48 -0700 (PDT)
Received: by 10.114.183.47 with HTTP; Thu, 3 Oct 2013 05:00:48 -0700 (PDT)
In-Reply-To: <C2814ADA-6A29-4419-9D5F-97310A520A45@sobco.com>
References: <20131003103439.13078.31787.idtracker@ietfa.amsl.com> <C2814ADA-6A29-4419-9D5F-97310A520A45@sobco.com>
Date: Thu, 3 Oct 2013 13:00:48 +0100
Message-ID: <CAKHUCzyZJa=1bptBkxmY5673YwAje=iOoar++Szrk8F91nrU_Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-roll-terminology-13.txt> (Terms used in Ruting for Low power And Lossy Networks) to Informational RFC
From: Dave Cridland <dave@cridland.net>
To: Scott O Bradner <sob@sobco.com>
Content-Type: multipart/alternative; boundary=089e0158c410bff78704e7d4ef15
Cc: roll@ietf.org, "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, 03 Oct 2013 12:06:01 -0000

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

On Thu, Oct 3, 2013 at 12:49 PM, Scott O Bradner <sob@sobco.com> wrote:

>
> On Oct 3, 2013, at 6:34 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> >
> > The IESG has received a request from the Routing Over Low power and Los=
sy
> > networks WG (roll) to consider the following document:
> > - 'Terms used in Ruting for Low power And Lossy Networks'
> >  <draft-ietf-roll-terminology-13.txt> as Informational RFC
>
> "Ruting" - "R=FCting is a municipality in the Nordwestmecklenburg distric=
t,
> in Mecklenburg-Vorpommern, Germany"
>
> the first sentence in the abstract says "routing" - maybe the title is in
> need of Vana White?
>
>
I'd assumed that they'd misspelt "rutting", and was quite disappointed in
the document as a result.

Dave.

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

<div dir=3D"ltr">On Thu, Oct 3, 2013 at 12:49 PM, Scott O Bradner <span dir=
=3D"ltr">&lt;<a href=3D"mailto:sob@sobco.com" target=3D"_blank">sob@sobco.c=
om</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:1px #ccc solid;padding-left:1ex">
<br>
On Oct 3, 2013, at 6:34 AM, The IESG &lt;<a href=3D"mailto:iesg-secretary@i=
etf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt; The IESG has received a request from the Routing Over Low power and Lo=
ssy<br>
&gt; networks WG (roll) to consider the following document:<br>
&gt; - &#39;Terms used in Ruting for Low power And Lossy Networks&#39;<br>
&gt; =A0&lt;draft-ietf-roll-terminology-13.txt&gt; as Informational RFC<br>
<br>
&quot;Ruting&quot; - &quot;R=FCting is a municipality in the Nordwestmeckle=
nburg district, in Mecklenburg-Vorpommern, Germany&quot;<br>
<br>
the first sentence in the abstract says &quot;routing&quot; - maybe the tit=
le is in need of Vana White?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>I&#39;d assumed that they&#39;d misspelt &quot;rutti=
ng&quot;, and was quite disappointed in the document as a result.</div><div=
>
<br></div><div>Dave.</div></div></div></div>

--089e0158c410bff78704e7d4ef15--

From sob@sobco.com  Thu Oct  3 05:15:20 2013
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A29821F9B86; Thu,  3 Oct 2013 05:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 ez8pOd6T366D; Thu,  3 Oct 2013 05:15:06 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id B205811E80EA; Thu,  3 Oct 2013 05:10:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 1344830A0BC; Thu,  3 Oct 2013 08:10:10 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03qMdpeTsacR; Thu,  3 Oct 2013 08:10:08 -0400 (EDT)
Received: from dhcp3.sobco.com (unknown [136.248.127.173]) by sobco.sobco.com (Postfix) with ESMTPSA id 2D46C30A0AE; Thu,  3 Oct 2013 08:10:08 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-roll-terminology-13.txt> (Terms used in	Ruting for Low power And Lossy Networks) to Informational RFC
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <CAKHUCzyZJa=1bptBkxmY5673YwAje=iOoar++Szrk8F91nrU_Q@mail.gmail.com>
Date: Thu, 3 Oct 2013 08:10:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <033EBCD9-8D72-4264-B260-22F4207C9F0D@sobco.com>
References: <20131003103439.13078.31787.idtracker@ietfa.amsl.com> <C2814ADA-6A29-4419-9D5F-97310A520A45@sobco.com> <CAKHUCzyZJa=1bptBkxmY5673YwAje=iOoar++Szrk8F91nrU_Q@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1510)
Cc: roll@ietf.org, "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, 03 Oct 2013 12:15:20 -0000

that is what I thought at first which caused me to quickly take a look
since the topic seemed to be a bit out of scope, even for the quite =
broad=20
IETF official scope (though I'm not sure what SDO would be a an =
appropriate=20
venue for standardization in this field)

Scott

On Oct 3, 2013, at 8:00 AM, Dave Cridland <dave@cridland.net>
 wrote:

> On Thu, Oct 3, 2013 at 12:49 PM, Scott O Bradner <sob@sobco.com> =
wrote:
>=20
> On Oct 3, 2013, at 6:34 AM, The IESG <iesg-secretary@ietf.org> wrote:
>=20
> >
> > The IESG has received a request from the Routing Over Low power and =
Lossy
> > networks WG (roll) to consider the following document:
> > - 'Terms used in Ruting for Low power And Lossy Networks'
> >  <draft-ietf-roll-terminology-13.txt> as Informational RFC
>=20
> "Ruting" - "R=FCting is a municipality in the Nordwestmecklenburg =
district, in Mecklenburg-Vorpommern, Germany"
>=20
> the first sentence in the abstract says "routing" - maybe the title is =
in need of Vana White?
>=20
>=20
> I'd assumed that they'd misspelt "rutting", and was quite disappointed =
in the document as a result.
>=20
> Dave.


From huub.van.helvoort@huawei.com  Thu Oct  3 06:27:40 2013
Return-Path: <huub.van.helvoort@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C9C21F9A49; Thu,  3 Oct 2013 06:27:40 -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 ve5boVHbv1re; Thu,  3 Oct 2013 06:27:20 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C8B3421E8063; Thu,  3 Oct 2013 06:22:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AWK07469; Thu, 03 Oct 2013 13:22:17 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 3 Oct 2013 14:22:00 +0100
Received: from LHREML509-MBX.china.huawei.com ([10.201.4.177]) by lhreml401-hub.china.huawei.com ([10.201.5.240]) with mapi id 14.03.0146.000; Thu, 3 Oct 2013 14:22:15 +0100
From: Huub helvoort <huub.van.helvoort@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> 
Thread-Topic: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> 
Thread-Index: Ac7AFRRiZXQ2TaqrQyKn1YTQ2cj7dwAJk7pc
Date: Thu, 3 Oct 2013 13:22:14 +0000
Message-ID: <73E555AA235F3846B8051DB38C8776272E665629@lhreml509-mbx>
References: <031601cec015$591026c0$0b307440$@olddog.co.uk>
In-Reply-To: <031601cec015$591026c0$0b307440$@olddog.co.uk>
Accept-Language: en-GB, en-US, zh-CN
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.202.112.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 13:27:40 -0000

Hello Adrian,

Thnak you for your feedback/review.

You write: "can be handled as IETF last call comments",
so there is no need for revision 13 then.

Cheers, Huub.

--
=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=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
Always remember that you are unique...just like everyone else...

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] on behalf of Adrian Far=
rel [adrian@olddog.co.uk]
Sent: 03 October 2013 10:48
To: ietf@ietf.org
Cc: mpls@ietf.org
Subject: RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt>

Thanks for this document which was surprisingly readable.

I have a number of comments from my AD review, but they are all
trivial and can be handled as IETF last call comments.

Thanks,
Adrian

---

Nurit will want to change the minor details or her affiliation.

---

Abstract
Expand MPLS-TP and PW on first use.
Expand MS
s/recommendations/Recommendations/  >>> Apply throughout document
s/nor/or/

---

Section 1

s/telecommunication/Telecommunication/

---

Section 1.2

s/Administration and Maintenance/Administration, and Maintenance/

---

Section 3.4

s/APPENDIX/Appendix/

---

Section 3.5

Please expand PW

---

Section 3.7

One might ask whether a co-routed bidirectional path that traverses a
LAG or a link bundle uses the same component links in both directions.

---

Section 3.8 could probably usefully mention routing along with
signaling.

---

Section 3.11

s/physical channels/a physical channel/

---

Section 3.16

Please expand LSR

---

One paragraph in 3.17 is a bit wild.

   Therefore, in the context of MPLS-TP LSP or PW Maintenance Entity
   (defined below) LERs and T-PEs can be MEPs while LSRs and S-PEs can
   be MIPs. In the case of Tandem Connection Maintenance Entity
   (defined below), LSRs and S-PEs can be either MEPs or MIPs.

s/context of/context of a/

"PW Maintenance Entity" is not defined below (I think).

Please expand LER

I don't find the definition of "Tandem Connection Maintenance Entity"
Maybe you could say
...the case of a Maintenance Entity for a Tandem Connection (defined below)


Please expand S-PE

---

Section 3.19
Penultimate paragraph
Second instance  s/(e.g. count packets)./(e.g. counts packets)./

---

Section 3.23

s/described in three ways:/described in one of three ways:/
s/Sub-Path Maintenance Element, and/Sub-Path Maintenance Element, or/
s/as a Tandem Connections./as a Tandem Connection./

---

Section 3.23.2  Section header

s/(SMPE):/(SPME):/

---

Section 3.35

The use of pipe ("|") and curly braces ("{" and "}") could usefully be
replaced with English language.

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 02 October 2013 22:45
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesauru=
s for
the
> Terminology used in Multiprotocol Label Switching Transport Profile (MPLS=
-TP)
> drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informatio=
nal
> RFC
>
>
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'A Thesaurus for the Terminology used in Multiprotocol Label Switching
>    Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport
>    Network Recommendations.'
>   <draft-ietf-mpls-tp-rosetta-stone-12.txt> as Informational RFC=

From mcr@sandelman.ca  Thu Oct  3 06:58:23 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 3653B21F89FF for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 06:58:23 -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.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 sPvZxXEeE2P0 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 06:57:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 95F3C21E8097 for <ietf@ietf.org>; Thu,  3 Oct 2013 06:51:17 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 244EF2017B; Thu,  3 Oct 2013 11:00:51 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 00B0E63B18; Thu,  3 Oct 2013 09:51:05 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E580863AED; Thu,  3 Oct 2013 09:51:05 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [Tools-discuss] independant submissions that update standards track, and datatracker
In-Reply-To: <CADnDZ88GJqRqSDtYTAK856DFfzF6Hjii4YB7H+aYMFkWxq_YzA@mail.gmail.com>
References: <CADnDZ88GJqRqSDtYTAK856DFfzF6Hjii4YB7H+aYMFkWxq_YzA@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: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Thu, 03 Oct 2013 09:51:05 -0400
Message-ID: <13061.1380808265@sandelman.ca>
Sender: mcr@sandelman.ca
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, 03 Oct 2013 13:58:23 -0000

Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
    >> While I think that individual submissions that are not the result of
    >> consensus do not belong on a WG page.

    > Where do they belong? I prefer
    > that they belong under the Area page, but is there an area page,
    > not=C2=A0sure why was that not a good idea.

1) Please stop this discussion, or at least change the subject.

I don't think that one can have an independant submission that is standards
track, that is not the result of (at least IESG) consensus.

2) If you quote, please include attribution.



From mcr@sandelman.ca  Thu Oct  3 07:17:03 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 4178F21F999B; Thu,  3 Oct 2013 07:17:03 -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.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 UyXdXZAsTen1; Thu,  3 Oct 2013 07:16:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 5C05721E804D; Thu,  3 Oct 2013 07:11:18 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BB61A2017B; Thu,  3 Oct 2013 11:21:01 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 8858163B18; Thu,  3 Oct 2013 10:11:16 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 75EAD63AED; Thu,  3 Oct 2013 10:11:16 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Last Call: <draft-ietf-roll-terminology-13.txt> (Terms used in Ruting for Low power And Lossy Networks) to Informational RFC
In-Reply-To: <CAKHUCzyZJa=1bptBkxmY5673YwAje=iOoar++Szrk8F91nrU_Q@mail.gmail.com>
References: <20131003103439.13078.31787.idtracker@ietfa.amsl.com> <C2814ADA-6A29-4419-9D5F-97310A520A45@sobco.com> <CAKHUCzyZJa=1bptBkxmY5673YwAje=iOoar++Szrk8F91nrU_Q@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: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Thu, 03 Oct 2013 10:11:16 -0400
Message-ID: <16602.1380809476@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: roll@ietf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>, Scott O Bradner <sob@sobco.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, 03 Oct 2013 14:17:03 -0000

Dave Cridland <dave@cridland.net> wrote:
    >> The IESG has received a request from the Routing Over Low power and
    >> Lossy networks WG (roll) to consider the following document: - 'Terms
    >> used in Ruting for Low power And Lossy Networks'
    >> =C2=A0<draft-ietf-roll-terminology-13.txt> as Informational RFC

    > I'd assumed that they'd misspelt "rutting", and was quite disappointed
    > in the document as a result.

Well.  I think that we really do not want the motes to start replicating.

At least, we need to let Jack O'Neil decode the Ancient Knowledge first.
(I've been rewatching SG-1...)

--
]               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  =
  [



From barryleiba.mailing.lists@gmail.com  Thu Oct  3 07:21:02 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 2B24C21F9926 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 07:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[AWL=0.076, 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 dKzupIg75Ukl for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 07:20:54 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2C09A21F87B7 for <ietf@ietf.org>; Thu,  3 Oct 2013 07:14:19 -0700 (PDT)
Received: by mail-lb0-f178.google.com with SMTP id z5so2073570lbh.37 for <ietf@ietf.org>; Thu, 03 Oct 2013 07:14:19 -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:message-id:subject :from:to:content-type; bh=RYToDKHPXEYVV5UHo4o++nDdl5XnDvYhZvBrjnS9gOM=; b=tes8XNrlGRotIaFoOn5ydXOgcAwnOJBDuEVVCp1LlcfAanNwnj11dn/wJ0xHAx9vS9 CJhtsyzxFgQEmdEI4dbAwglCZxVOl7o0Fqf+5dkIX7R1d9bBOs55YNUlyVA4r4/MmRJR N8On2ceHaf6cMNgbsSZRGLkiUFwxSDDIb8B0wiGVZeB1qdkszS47zmMvGycxIFbaRqyq MQitHd/e+8JPRNRMCKvARYNdktg3hSxD8U4DpKqBlWe0V/ngcUhCLT9quWCE7p+rKyIE I+pnArrAdwQ4E5eyy3U+6Kk6V9i2FJsjvLpifJ3hh2wdE5FUN10ecdmgrbC7RYGqMYEh wshw==
MIME-Version: 1.0
X-Received: by 10.112.72.100 with SMTP id c4mr492048lbv.57.1380809658902; Thu, 03 Oct 2013 07:14:18 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Thu, 3 Oct 2013 07:14:18 -0700 (PDT)
In-Reply-To: <CALaySJLtMNgCLEUF1DKtVizD4z-WyP2qjrFtQK-ADT8TQoOBMA@mail.gmail.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com> <CALaySJLtMNgCLEUF1DKtVizD4z-WyP2qjrFtQK-ADT8TQoOBMA@mail.gmail.com>
Date: Thu, 3 Oct 2013 10:14:18 -0400
X-Google-Sender-Auth: Wv9CFT41QR8sLHCgAPOOonQtXT4
Message-ID: <CAC4RtVBxZ+ELU4u3M--t8onK0xLU0zw5gthuRBzWTvTRiFwPjQ@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <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, 03 Oct 2013 14:21:02 -0000

>> Hi.  Just to be sure that everyone has the same understanding of
>> what is being proposed here, the above says "to Historic" but
>> the writeup at
>> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>> says "to Internet Standard".   Can one or the other be corrected?
>
> Gakk.  I don't know how that happened.  I'll see if the Secretariat
> can fix it.  I'm sure it's my fault......

Noting that this has been fixed and that a revised Last Call note went
out.  Please, if you continue this discussion, change the subject line
to say "Historic" instead of "Internet Standard", so no one is
confused by the dissonance.

Thanks, all, and my apologies again for the error in the title.

Barry

From vesely@tana.it  Thu Oct  3 08:02:14 2013
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F6311E80E6 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 08:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 JsBIlnAtAA-F for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 08:01:56 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 1F35711E80E7 for <ietf@ietf.org>; Thu,  3 Oct 2013 07:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1380811882; bh=+uAHzrRJzrG+vnyNIqwM5K3tjfS51YhmC14hM+Wr/zk=; l=1356; h=Date:From:To:References:In-Reply-To; b=Co9RrnG5rDsU1DTSfU+xzd4TV3Fq5JuFMPT2uHYXvvYm/Vi+bJtihRIPIQOCaCFe3 CKgGYxoQ1EhH5hb5xLY7jffKvGDZUieBml1s8yLYwIrFN763w0p1m+5onQTEHlx7QV Y98MsFvLOSM+vCBqED1eP3EORqF64tNwSZlA3OTk=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Thu, 03 Oct 2013 16:51:22 +0200 id 00000000005DC039.00000000524D846A.000033DF
Message-ID: <524D846A.6030905@tana.it>
Date: Thu, 03 Oct 2013 16:51:22 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
References: <20131002145238.78084.qmail@joyce.lan>
In-Reply-To: <20131002145238.78084.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
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, 03 Oct 2013 15:02:14 -0000

On Wed 02/Oct/2013 16:52:38 +0200 John Levine wrote:
>>The IESG has received a request from an individual participant to make
>>the following status changes:
>>
>>- RFC5617 from Proposed Standard to Historic
>>
>>The supporting document for this request can be found here:
>>
>>http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
> 
> I'm one of the authors of this RFC and support the change.
> 
> ADSP was basically an experiment that failed.  It has no significant
> deployment, and the problem it was supposed to solve is now being
> addressed in other ways.

I oppose to the change as proposed, and support the explanation called
for by John Klensin instead.  Two arguments:

1)  The harm Barry exemplifies in the request --incompatibility with
    mailing list posting-- is going to be a feature of at least one
    of the other ways addressing that problem.  Indeed, "those who
    don't know history are destined to repeat it", and the explanation
    is needed to make history known.

2)  A possible fix for ADSP is explained by John Levine himself:
    http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.html
    I'm not proposing to mention it along with the explanation, but
    fixing is not the same as moving to historic.  It seems that it
    is just a part of RFC 5617, DNS records, that we want to move.

Ale

From scott@kitterman.com  Thu Oct  3 08:19:31 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B443C21F89EB for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 08:19: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 SKZnMvwm7bNU for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 08:19:21 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id D7BBA21F8F6D for <ietf@ietf.org>; Thu,  3 Oct 2013 08:10:57 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 51231D04081; Thu,  3 Oct 2013 11:10:54 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1380813054; bh=WiHEztlw4J8ls62YlxYUVhEFjO4fs2Tb6JtE3ENAa38=; h=In-Reply-To:References:Subject:From:Date:To:From; b=Y/QbsEaJPg59KOK244l1GWb5L/7y9d7UPea4p8Y4lBrXgcvq2AeZzKbnbjgwn5nkD nD6QHDU2k2TINetdnVdkUJVU+bbCpQd/mTloT21pkAxn3LMQbuYw1UKItrGlwV2fhU 2zevTXixCR0Qbd60jfjkyzB+OghCOtx+zfzHHHxk=
Received: from [IPV6:2600:1003:b102:9abd:366e:d33d:d3c9:288b] (unknown [IPv6:2600:1003:b102:9abd:366e:d33d:d3c9:288b]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id D1E09D0405E;  Thu,  3 Oct 2013 11:10:53 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <524D846A.6030905@tana.it>
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
From: Scott Kitterman <scott@kitterman.com>
Date: Thu, 03 Oct 2013 11:11:00 -0400
To: ietf@ietf.org
Message-ID: <04cb09f2-3321-4b5b-b791-a3bb16b80570@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 15:19:31 -0000

Alessandro Vesely <vesely@tana.it> wrote:
>On Wed 02/Oct/2013 16:52:38 +0200 John Levine wrote:
>>>The IESG has received a request from an individual participant to
>make
>>>the following status changes:
>>>
>>>- RFC5617 from Proposed Standard to Historic
>>>
>>>The supporting document for this request can be found here:
>>>
>>>http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>> 
>> I'm one of the authors of this RFC and support the change.
>> 
>> ADSP was basically an experiment that failed.  It has no significant
>> deployment, and the problem it was supposed to solve is now being
>> addressed in other ways.
>
>I oppose to the change as proposed, and support the explanation called
>for by John Klensin instead.  Two arguments:
>
>1)  The harm Barry exemplifies in the request --incompatibility with
>    mailing list posting-- is going to be a feature of at least one
>    of the other ways addressing that problem.  Indeed, "those who
>    don't know history are destined to repeat it", and the explanation
>    is needed to make history known.
>
>2)  A possible fix for ADSP is explained by John Levine himself:
>    http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.html
>    I'm not proposing to mention it along with the explanation, but
>    fixing is not the same as moving to historic.  It seems that it
>    is just a part of RFC 5617, DNS records, that we want to move.

That's not a fix for ADSP. It's an alternative to it.

ADSP failed. It's time to move on.

Scott K


From hsantos@isdg.net  Thu Oct  3 09:57:35 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 EEBD411E80F6 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 09:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.706
X-Spam-Level: 
X-Spam-Status: No, score=-101.706 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=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 RcW2q-Oht26z for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 09:57:21 -0700 (PDT)
Received: from mail.catinthebox.net (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 195E811E8118 for <ietf@ietf.org>; Thu,  3 Oct 2013 09:41:39 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2835; t=1380818496; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=6vowutvPyouTrYJY1TkeJvGNhQM=; b=B2M2h3hsHPLcgdcmjXm/ IRagmfUOlVnJCaOgnYbSQl0IZuf+CPxplKIgEpEfFc/8+etZCwiwDzDZA94JQKv9 3ZAX3wxEajK6OZZwBS3XcnAc8prBZjJ7Br131/oXnerIlgs18L+KwgGwTeirBEXF 8eMpaYGOnRixU1U+ErF38Ko=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 12:41:36 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2986002348.4443.4116; Thu, 03 Oct 2013 12:41:35 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2835; t=1380818110; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=kzectXD Xh4AVa30hjHo4/wvq5hbpKclYoUac48Qqc+g=; b=MxUBUUi2urvdfp3H3xv+eL/ 8vptBceokzqNjjZcp7mKOwMYOCLpwcERCGvanAGjubNN7C6XJtVMmT6lI3paIhj3 Atp++YY09o6ON6dTrIZdT9xSJk1ssw6yPCKPk5Pc3adcnLma/vJ2UlIZtuJw5iXl hCAWbHFjSmJIbg72Y7lY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 12:35:10 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2432391112.9.3344; Thu, 03 Oct 2013 12:35:09 -0400
Message-ID: <524D9E41.1000404@isdg.net>
Date: Thu, 03 Oct 2013 12:41:37 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it> <04cb09f2-3321-4b5b-b791-a3bb16b80570@email.android.com>
In-Reply-To: <04cb09f2-3321-4b5b-b791-a3bb16b80570@email.android.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: Thu, 03 Oct 2013 16:57:35 -0000

On 10/3/2013 11:11 AM, Scott Kitterman wrote:
>
>
> Alessandro Vesely <vesely@tana.it> wrote:
>> On Wed 02/Oct/2013 16:52:38 +0200 John Levine wrote:
>>>> The IESG has received a request from an individual participant to
>> make
>>>> the following status changes:
>>>>
>>>> - RFC5617 from Proposed Standard to Historic
>>>>
>>>> The supporting document for this request can be found here:
>>>>
>>>> http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>>>
>>> I'm one of the authors of this RFC and support the change.
>>>
>>> ADSP was basically an experiment that failed.  It has no significant
>>> deployment, and the problem it was supposed to solve is now being
>>> addressed in other ways.
>>
>> I oppose to the change as proposed, and support the explanation called
>> for by John Klensin instead.  Two arguments:
>>
>> 1)  The harm Barry exemplifies in the request --incompatibility with
>>     mailing list posting-- is going to be a feature of at least one
>>     of the other ways addressing that problem.  Indeed, "those who
>>     don't know history are destined to repeat it", and the explanation
>>     is needed to make history known.
>>
>> 2)  A possible fix for ADSP is explained by John Levine himself:
>>     http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.html
>>     I'm not proposing to mention it along with the explanation, but
>>     fixing is not the same as moving to historic.  It seems that it
>>     is just a part of RFC 5617, DNS records, that we want to move.
>
> That's not a fix for ADSP. It's an alternative to it.
>
> ADSP failed. It's time to move on.
>
> Scott K

For DKIM/ADSP investors (folks who put the $$$ into it and got on 
board with the IETF for this DKIM support effort), thats really not an 
acceptable answer.  What are we moving on to, DMARC?  Its the same 
issue, or is the suggestion that Mailing List Services or middleware 
will support DMARC to help protect DKIM signatures from 3rd party abuses?

ADSP did not fail if the same proof of concepts is going to be 
repeated with DMARC. As Alessandro stated, we are merely switching 
_ADSP to _DMARC zone records with new but similar SOFT (relaxed) vs 
HARD (restrictive) rejection policies and handling rules.   The same 
ones that MLS (Mailing List Services) will have to support as well. 
Its no different than ADSP.

Now, what it does say is that DKIM itself is a weaker protocol.  There 
will no longer be any marketing value for protecting DKIM signatures, 
even if its only in IETF theory.  No value to compare what a DOMAIN 
wanted with its signatures and no protection from abuse whatsoever.

I would say this, if this ADSP historic request was done before the 
DKIM request to change to Internet Standard a few months ago, I would 
of not supported the IS change for DKIM.


-- 
HLS



From john-ietf@jck.com  Thu Oct  3 10:28:43 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 D49AF11E814B for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 10:28:43 -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 47clkaw5vG4Q for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 10:28:33 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E49FC21E808A for <ietf@ietf.org>; Thu,  3 Oct 2013 10:09: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 1VRmOh-000NNK-Vb; Thu, 03 Oct 2013 13:09:07 -0400
Date: Thu, 03 Oct 2013 13:09:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
Message-ID: <19D662B6E38A1BC0CFE88A77@JcK-HP8200.jck.com>
In-Reply-To: <524D846A.6030905@tana.it>
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it>
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, 03 Oct 2013 17:28:44 -0000

--On Thursday, October 03, 2013 16:51 +0200 Alessandro Vesely
<vesely@tana.it> wrote:

>> ADSP was basically an experiment that failed.  It has no
>> significant deployment, and the problem it was supposed to
>> solve is now being addressed in other ways.
> 
> I oppose to the change as proposed, and support the
> explanation called for by John Klensin instead.  Two arguments:
> 
> 1)  The harm Barry exemplifies in the request
> --incompatibility with     mailing list posting-- is going to
> be a feature of at least one     of the other ways addressing
> that problem.  Indeed, "those who     don't know history are
> destined to repeat it", and the explanation     is needed to
> make history known.
> 
> 2)  A possible fix for ADSP is explained by John Levine
> himself:
> http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.ht
> ml     I'm not proposing to mention it along with the
> explanation, but     fixing is not the same as moving to
> historic.  It seems that it     is just a part of RFC 5617,
> DNS records, that we want to move.

Ale,

Just to be clear about what I proposed because I'm not sure that
you actually agree:  If the situation is as described in the
write-up (and/or as described by John Levine, Murray, and some
other documents), then I'm in favor of deprecating ADSP.  The
_only_ issue I'm raising in this case is that I believe that
deprecating a feature or protocol element by moving things to
Historic by IESG action and a note in the tracker is appropriate
only for things that have been completely ignored after an
extended period or that have long ago passed out of public
consciousness.   When something has been implemented and
deployed sufficiently that the reason for deprecating it
includes assertions that it has not worked out in practice, I
believe that should be documented in an RFC both to make the
historical record clear and to help persuade anyone who is still
trying to use it to cease doing so.

There may well be arguments for not deprecating the feature, for
improving it in various ways, or for contexts in which its use
would be appropriate, but someone else will have to make them or
propose other remedies.  I have not done so nor am I likely to
do so.

  best,
    john



From bmanning@isi.edu  Thu Oct  3 10:30:16 2013
Return-Path: <bmanning@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 1CAA811E8172; Thu,  3 Oct 2013 10:30: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 9-nZcpIQZ0+t; Thu,  3 Oct 2013 10:30:04 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 0023121E8136; Thu,  3 Oct 2013 10:10:20 -0700 (PDT)
Received: from [128.9.184.131] ([128.9.184.131]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r93H7hfi029512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 3 Oct 2013 10:07:44 -0700 (PDT)
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20131003154254.13078.69905.idtracker@ietfa.amsl.com>
Date: Thu, 3 Oct 2013 10:07:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com>
To: "<ietf@ietf.org> Discussion" <ietf@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: dnssd WG <dnssdext@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 17:30:16 -0000

  ----- The following addresses had permanent fatal errors -----
<dnssdext-request@ietf.org>
   (reason: 550 5.1.1 <dnssdext-request@ietf.org>: Recipient address =
rejected: User unknown in virtual alias table)



On 3October2013Thursday, at 8:42, The IESG wrote:

> A new IETF working group has been proposed in the Internet Area. The =
IESG
> has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please =
send
> your comments to the IESG mailing list (iesg at ietf.org) by =
2013-10-10.
>=20
> Extensions for Scalable DNS Service Discovery  (dnssd)
> ------------------------------------------------
> Current Status: Proposed WG
>=20
> Chairs:
>  Ralph Droms <rdroms.ietf@gmail.com>
>  Tim Chown <tjc@ecs.soton.ac.uk>
>=20
> Assigned Area Director:
>  Ted Lemon <ted.lemon@nominum.com>
>=20
> Mailing list
>  Address: dnssdext@ietf.org
>  To Subscribe: dnssdext-request@ietf.org
>  Archive: http://www.ietf.org/mail-archive/web/dnssdext
>=20
> Charter:
>=20
> Background
> ----------
>=20
> Zero configuration networking protocols are currently well suited to
> discover services within the scope of a single link.  In particular,
> the DNS-SD [RFC 6763] and mDNS [RFC6762] protocol suite (sometimes
> referred to using Apple Computer Inc.'s trademark, Bonjour) are
> widely used for DNS-based service discovery and host name resolution
> on a single link.
>=20
> The DNS-SD/mDNS protocol suite is used in many scenarios including
> home, campus, and enterprise networks.  However, the zero =
configuration
> mDNS protocol is constrained to link-local multicast scope by design,
> and therefore cannot be used to discover services on remote links.
>=20
> In a home network that consists of a single (possibly bridged) link,
> users experience the expected discovery behavior; available services
> appear because all devices share a common link.  However, in =
multi-link
> home networks (as envisaged by the homenet WG) or in routed campus or
> enterprise networks, devices and users can only discover services on
> the same link, which is a significant limitation.  This has led to
> calls, such as the Educause petition, to develop an appropriate =
service
> discovery solution to span multiple links or to perform discovery =
across
> a wide area, not necessarily on directly connected links.
>=20
> In addition, the "Smart Energy Profile 2 Application Protocol =
Standard",
> published by ZigBee Alliance and HomePlug Powerline Alliance specifies
> the DNS-SD/mDNS protocol suite as the basis for its method of zero
> configuration service discovery.  However, its use of wireless mesh
> multi-link subnets in conjunction with traditional routed networks =
will
> require extensions to the DNS-SD/mDNS protocols to allow operation
> across multiple links.
>=20
> The scenarios in which multi-link service discovery is required may
> be zero configuration environments, environments where administrative
> configuration is supported, or a mixture of the two.
>=20
> As demand for service discovery across wider area routed networks
> grows, some vendors are beginning to ship proprietary solutions.  It
> is thus both timely and important that efforts to develop improved,=20
> scalable, autonomous service discovery solutions for routed networks=20=

> are coordinated towards producing a single, standards-based solution.
>=20
> The WG will consider the tradeoffs between reusing/extending existing
> protocols and developing entirely new ones.  It is highly desirable
> that any new solution is backwardly compatible with existing =
DNS-SD/mDNS
> deployments.  Any solution developed by the dnssd WG must not conflict
> or interfere with the operation of other zero-configuration service =
and
> naming protocols such as uPnP or LLMNR.  Integration with such =
protocols
> is out of scope for this WG.
>=20
> The focus of the WG is to develop a solution for extended, scalable=20
> DNS-SD.  This work is likely to highlight problems and challenges with=20=

> naming protocols, as some level of coexistence will be required =
between=20
> local zero configuration name services and those forming part of the=20=

> global DNS.  It is important that these issues are captured and=20
> documented for further analysis; solving those problems is however not=20=

> within the scope of this WG.
>=20
> Working Group Description
> -------------------------
>=20
> To that end, the primary goals of the dnssd WG are as follows:
>=20
> 1. To document a set of requirements for scalable, autonomous
>   DNS-based service discovery in routed, multi-link networks in the
>   following five scenarios:
>=20
>   (A) Personal Area networks, e.g., one laptop and one printer.
>       This is the simplest example of a service discovery network,
>       and may or may not have external connectivity.=20
>=20
>   (B) Home networks, as envisaged by the homenet WG, consisting of=20
>       one or more exit routers, with one or more upstream providers=20
>       or networks, and an arbitrary internal topology with=20
>       heterogeneous media where routing is automatically configured.=20=

>       The home network would typically be a single zero configuration=20=

>       administrative domain with a relatively limited number of=20
>       devices.=20
>=20
>   (C) Wireless 'hotspot' networks, which may include wireless networks
>       made available in public places, or temporary or permanent
>       infrastructures targeted towards meeting or conference style
>       events, e.g., as provided for IETF meetings.  In such
>       environments other devices may be more likely to be 'hostile'
>       to the user.
>=20
>   (D) Enterprise networks, consisting of larger routed networks,=20
>       with large numbers of devices, which may be deployments=20
>       spanning over multiple sites with multiple upstreams, and
>       one more more administrative domains (depending on internal
>       administrative delegation).  The large majority of the=20
>       forwarding and security devices are configured.  These may
>       be commercial or academic networks, with differing levels=20
>       of administrative control over certain devices on the network,
>       and BYOD devices commonplace in the campus scenario.
>=20
>   (E) Mesh networks such as RPL/6LoWPAN, with one or more links per
>       routable prefix, which may or may not have external =
connectivity.
>       The topology may use technologies including 802.11 wireless,=20
>       HomePlug AV and GP, and ZigBee IP.=20
>=20
>   In the above scenarios, the aim is to facilitate service discovery=20=

>   across the defined site.  It is also desirable that a user or =
device,=20
>   when away from such a site, is still able to discover services=20
>   within that site, e.g. a user discovering services in their home=20
>   network while remote from it.
>=20
>   It is also desirable that multiple discovery scopes are supported,
>   from the point of view of announcements and discovery, be the
>   scope 'site', 'building', or 'room'.  A user for example may only
>   be interested in devices in the same room.
>=20
> 2. To develop an improved, scalable solution for service discovery=20
>   that can operate in multi-link networks, where devices may be
>   in neighboring or non-neighboring links, applicable to
>   the scenarios above.  The solution will consider tradeoffs between
>   reusing/extending existing protocols and developing entirely new
>   protocols.=20
>=20
>   The solution should include documentation or definition of the
>   interfaces that can be implemented, separately to transport of=20
>   the information.
>=20
> 3. To document challenges and problems encountered in the coexistence=20=

>   of zero configuration and global DNS name services in such=20
>   multi-link networks, including consideration of both the name=20
>   resolution mechanism and the namespace.
>=20
> It is important that the dnssd WG takes input from stakeholders in
> the scenarios it is considering.  For example, the homenet WG is
> currently evaluating its own requirements for naming and service
> discovery; it is up to the homenet WG as to whether it wishes to
> recommend adoption of the solution developed in the dnssd WG, but
> coordination between the WGs is desirable.
>=20
> Deliverables:
>=20
> The WG will produce three documents: an Informational RFC on the
> requirements for service discovery protocols operating on potentially
> non-neighboring multi-link networks as described above; a Standards
> Track RFC documenting an extended, scalable service discovery solution=20=

> that is applicable to those scenarios; and an Informational RFC=20
> describing the problems arising when developing the extended SD =
solution=20
> and how it affects the integration of local zero configuration and =
global
>=20
> DNS name services.
>=20
> Milestones:
>  Sep 2013 - Formation of the WG
>  Oct 2013 - Adopt requirements draft as WG document
>  Jan 2014 - Submit requirements draft to the IESG as an Informational
> RFC
>  Mar 2014 - Adopt wide-area service discovery solution draft as WG
> document=20
>  Mar 2014 - Adopt Informational document on the problems and =
challenges
> arising for zeroconf and unicast DNS name services
>  Sep 2014 - Submit wide-area service discovery solution draft to the
> IESG as Standards Track RFC=20
>  Sep 2014 - Submit the zeroconf and unicast DNS "problems and
> challenges" draft to the IESG as Informational.
>=20
>=20


From hsantos@isdg.net  Thu Oct  3 10:58:09 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 5F2FE21F8B07 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 10:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.153
X-Spam-Level: 
X-Spam-Status: No, score=-102.153 tagged_above=-999 required=5 tests=[AWL=0.447, 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 rEO-PXM7jyss for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 10:57:54 -0700 (PDT)
Received: from groups.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id DD6AA11E80D1 for <ietf@ietf.org>; Thu,  3 Oct 2013 10:42:19 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3589; t=1380822132; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=VKQdC+6MJMa/VR3XpRZJ9JiDzbE=; b=c8dHY37oQBgH4JMytNjL JfRfRCtkaguQOOvMVJI43tvZGf8q2WvQtYNi9ZUcF3WNzRN1r4hhoBuPXrURKLYt 406pe7pEg875r7l0oR4kZn3bJ5ammjilubnk6+h4v8Omi+oNaYcV47MhXtXlBMvh y1+/VYCmf7FLf4P6FIbzAB0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 13:42:12 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2989637748.4443.1624; Thu, 03 Oct 2013 13:42:11 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3589; t=1380821744; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=gmlVWWI JSCHllz9MKKQu67BbekU5NOpD5D6Z7AILf7A=; b=i5JT2GTHfCn8dGviRSrIJRf 0x7x7iJUGoRJ5BURYCU20ttqzXr/GBtdNFVVMTp89qvufkljWepbeLxFviHo5g9C IjlSrBSCIoOihrT6de7CfxEMmO2KKG75c8acZ0XWs5FFcbiIzaZhqmSDMpdnPV/6 mmttFa1eDyylUEhl7BZo=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 13:35:44 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2436025597.9.9256; Thu, 03 Oct 2013 13:35:44 -0400
Message-ID: <524DAC74.5010000@isdg.net>
Date: Thu, 03 Oct 2013 13:42:12 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it> <19D662B6E38A1BC0CFE88A77@JcK-HP8200.jck.com>
In-Reply-To: <19D662B6E38A1BC0CFE88A77@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 17:58:09 -0000

I agree, the problem IMV is the illusion that DMARC will replace it 
has some domains has already done by switching their strong exclusive 
mail operations declaration from _ADSP TXT record policy to a _DMARC 
policy.  Like FACEBOOK.COM. The REJECTING/DISCARD concept is still the 
same and active, just a different TXT domain policy protocol 
describing the expected behavior.

The problem I have is the lack of confidence that DMARC will be 
supported by the main conflictive software in the entire DKIM 
deployment and service architectural picture -- the resigners (mailing 
list software).  Thats the problem ADSP had.  DMARC does not change it.

So is making ADSP historic, killing the investment done with DKIM/ADSP 
support, going to be replacing with a plug and play protocol switch 
with DMARC?

If so, I don't like that lost of investment but I can support the move 
but now, not as an early adopter and I will wait until other mailing 
list software vendors/developers add that necessary support for DMARC 
rejection policies.   Its the same proof of concept issue as it was 
with ADSP.

DMARC just add some reporting, logging and feedback concepts to the 
picture.

--
HLS

On 10/3/2013 1:09 PM, John C Klensin wrote:
>
>
> --On Thursday, October 03, 2013 16:51 +0200 Alessandro Vesely
> <vesely@tana.it> wrote:
>
>>> ADSP was basically an experiment that failed.  It has no
>>> significant deployment, and the problem it was supposed to
>>> solve is now being addressed in other ways.
>>
>> I oppose to the change as proposed, and support the
>> explanation called for by John Klensin instead.  Two arguments:
>>
>> 1)  The harm Barry exemplifies in the request
>> --incompatibility with     mailing list posting-- is going to
>> be a feature of at least one     of the other ways addressing
>> that problem.  Indeed, "those who     don't know history are
>> destined to repeat it", and the explanation     is needed to
>> make history known.
>>
>> 2)  A possible fix for ADSP is explained by John Levine
>> himself:
>> http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.ht
>> ml     I'm not proposing to mention it along with the
>> explanation, but     fixing is not the same as moving to
>> historic.  It seems that it     is just a part of RFC 5617,
>> DNS records, that we want to move.
>
> Ale,
>
> Just to be clear about what I proposed because I'm not sure that
> you actually agree:  If the situation is as described in the
> write-up (and/or as described by John Levine, Murray, and some
> other documents), then I'm in favor of deprecating ADSP.  The
> _only_ issue I'm raising in this case is that I believe that
> deprecating a feature or protocol element by moving things to
> Historic by IESG action and a note in the tracker is appropriate
> only for things that have been completely ignored after an
> extended period or that have long ago passed out of public
> consciousness.   When something has been implemented and
> deployed sufficiently that the reason for deprecating it
> includes assertions that it has not worked out in practice, I
> believe that should be documented in an RFC both to make the
> historical record clear and to help persuade anyone who is still
> trying to use it to cease doing so.
>
> There may well be arguments for not deprecating the feature, for
> improving it in various ways, or for contexts in which its use
> would be appropriate, but someone else will have to make them or
> propose other remedies.  I have not done so nor am I likely to
> do so.
>
>    best,
>      john
>
>
>
>

-- 
HLS



From doug.mtview@gmail.com  Thu Oct  3 11:05: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 E6D5B21F9926 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 11:05: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=[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 vjJa18K3yMF5 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 11:05:33 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 859F111E818A for <ietf@ietf.org>; Thu,  3 Oct 2013 10:51:23 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kl14so2927626pab.25 for <ietf@ietf.org>; Thu, 03 Oct 2013 10:51:23 -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; bh=QKPEw6i/1VMBqPybI3FkQBBrBuVN4G7BSDHpQJXck5c=; b=cMcLhiGKc3qw85Os5Al36SiJmHaK4cCwD8YoKyfGDib/3BX7M/hhX/CakOSS4Avoby xoSWAV9jPhqYQHNOJPOnYTvuPHOlAmjlL2A9XxMFqABXkpfgzaAtey+GC6QVW1RRjTxR URo0RlI1kyWBTiywz9j9lb+3poC6P5xSu717wuPo4n6prrWjYUw5HEeyloHsjy1b44D9 YtPqTWQdj5PuUHpstKrCuwVs9fQlM4FsusgT1XPsVUmjgeH9tDA6x3CBRLokQKt6jtN3 VQkc/83Fc8lgC1zmPtXYuCHZwFejzkA0r5H6RTonT4nF7KxY42Fv8PholzdWzCTRN278 6R6g==
X-Received: by 10.66.218.198 with SMTP id pi6mr10906251pac.107.1380822683106;  Thu, 03 Oct 2013 10:51:23 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id so2sm9605938pbc.5.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 10:51:22 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <524D5ACF.3020008@isdg.net>
Date: Thu, 3 Oct 2013 10:51:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1510)
Cc: Barry Leiba <barryleiba@computer.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, 03 Oct 2013 18:05:40 -0000

On Oct 3, 2013, at 4:53 AM, Hector Santos <hsantos@isdg.net> wrote:

>=20
> On 10/2/2013 5:04 PM, Murray S. Kucherawy wrote:
>> On Wed, Oct 2, 2013 at 7:41 AM, The IESG <iesg-secretary@ietf.org> =
wrote:
>>=20
>>> The IESG has received a request from an individual participant to =
make
>>> the following status changes:
>>>=20
>>> - RFC5617 from Proposed Standard to Historic
>>>=20
>>> The supporting document for this request can be found here:
>>>=20
>>> =
http://datatracker.ietf.org/doc/status-change-adsp-rfc5617-to-historic/
>>> [...]
>>>=20
>>=20
>> I support this change, for the reasons articulated in the request and =
in
>> this thread.
>>=20
>> I am the lead developer and maintainer of OpenDKIM, an open source
>> implementation of DKIM and related standards, including VBR, ADSP, =
the
>> recent REPUTE work, and some others.  It is widely deployed, =
including use
>> at a few of the largest operators.  An informal survey was done on =
one of
>> the mailing lists where this package is supported, asking which =
operators
>> do ADSP queries and which act upon the results.  I have so far only
>> received a half dozen answers to this, but the consensus among them =
is
>> clear: All of the respondents either do not check ADSP, or check it =
but do
>> nothing with the results.  One operator puts disposition of messages =
based
>> on ADSP results into the hands of its users, but no statistics were =
offered
>> about how many of these users have ADSP-based filtering enabled.  =
That same
>> operator intends to remove that capability once this status change =
goes
>> into effect.
>>=20
>> -MSK
>=20
> I don't believe this would be a fair assessment of industry wide =
support -- using only one API to measure. There are other APIs and =
proprietary systems who most likely are not part of the OpenDKIM group.  =
There are commercial operations using DKIM and ADSP is part of it.
>=20
> The interop problem is clearly due intentional neglect by specific MLS =
(Mailing List Software) of the DKIM security protocol, not because of =
the protocol itself.  Support of the protocol does not cause an interop =
problem -- it helps support the DKIM security protocol.    The ADSP =
(RFC5617) protocol is part of the DKIM security threat mitigation model =
(RFC4686), the DKIM Service Architecture (RFC5585), the DKIM Deployment =
Guide (RFC5863) and also the Mailing List for DKIM guideline (rfc6377).  =
 That is FOUR documents.
>=20
> Applicability and Impact reports *should* to be done before pulling =
the rug from under the non-OpenDKIM market feet.  In addition, it =
appears part of the request is to help move an alternative DMARC =
protocol forward. Why would the DMARC replacement do better?  Why should =
commercial development for ADSP be stopped and removed from products, =
and now a new investment for DMARC be done?  Would this resolve the =
apparent interop problem with the specific Mailing List Software who =
refuse to support a DKIM security protocol?
>=20
> More importantly, why should any small operator and participant of the =
IETF continue to support IETF projects if their support is ignored and =
projects will be ended without their input or even explaining why it =
should be ended?  That doesn't play well for the IETF Diversity =
Improvement Program.

Dear Hector,

Indeed, more should be said about underlying reasons.  The reason for =
abandoning ADSP is for the same reason few providers reject messages not =
authorized by SPF records ending in "-all" (FAIL).  Mailing-List =
software existed long before either of these strategies and domains =
using mailing lists need to be excluded from having DMARC policies =
(until a revised ATPS specification able to use normal signatures is =
published.)  The reason for moving toward DMARC is, although aligned =
policy is only suitable for domains limited to messages of a =
transactional nature, places where one authorization scheme fails can be =
mostly recovered by the other which greatly increases the chances of a =
domain's policy being applied in the desired fashion.

Regards,
Douglas Otis


From tjc@ecs.soton.ac.uk  Thu Oct  3 11:52:06 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 11AD021F8D62; Thu,  3 Oct 2013 11:52:06 -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 qYpzdwZq6bDc; Thu,  3 Oct 2013 11:51:51 -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 F2C3021F8984; Thu,  3 Oct 2013 11:43:36 -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 r93IhUjm025455;  Thu, 3 Oct 2013 19:43:30 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r93IhUjm025455
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1380825810; bh=SXHCY0EZOq8r7Nj75r+vIh08TRE=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=NSs5dihBz9bfSTNDxdWxzh6rfqfmSGHaa6AlFhqio/w74KdGwTkYb7rf+jZLXSebq Mpteu7h18+wbsZ3SWet31Vhneol8gCfNFL1qOInKxu71QSaNC+d654ffrZxKH/Nz8Q duelj2QUfvzDTYK2Wd6qUxJHHkwYjwOVDanvYrjY=
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 p92JhU0544563631dS ret-id none; Thu, 03 Oct 2013 19:43:30 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r93IhO3B031347 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Oct 2013 19:43:25 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_2193BD6E-6B92-4549-A4F3-42F75A2BC089"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu>
Date: Thu, 3 Oct 2013 19:43:24 +0100
Message-ID: <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
To: manning bill <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p92JhU054456363100; tid=p92JhU0544563631dS; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r93IhUjm025455
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 18:52:06 -0000

--Apple-Mail=_2193BD6E-6B92-4549-A4F3-42F75A2BC089
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 3 Oct 2013, at 18:07, manning bill <bmanning@isi.edu> wrote:

>  ----- The following addresses had permanent fatal errors -----
> <dnssdext-request@ietf.org>
>   (reason: 550 5.1.1 <dnssdext-request@ietf.org>: Recipient address =
rejected: User unknown in virtual alias table)

I think the active list is still mdnsext@ietf.org?
See: http://www.ietf.org/mail-archive/web/mdnsext/current/maillist.html

And the 'header' information below should now probably read something =
like this:

--- snip ---

Scalable DNS Service Discovery  (dnssd)
------------------------------------------------
Current Status: Proposed WG

Chairs:
 Ralph Droms <rdroms.ietf@gmail.com>
 Tim Chown <tjc@ecs.soton.ac.uk>

Assigned Area Director:
 Ted Lemon <ted.lemon@nominum.com>

Mailing list
 Address: dnssd@ietf.org
 To Subscribe: dnssd-request@ietf.org
 Archive: http://www.ietf.org/mail-archive/web/dnssd
 Pre-WG BoF Archive: http://www.ietf.org/mail-archive/web/mdnsext=20


--- snip ---

Tim

>=20
>=20
>=20
> On 3October2013Thursday, at 8:42, The IESG wrote:
>=20
>> A new IETF working group has been proposed in the Internet Area. The =
IESG
>> has not made any determination yet. The following draft charter was
>> submitted, and is provided for informational purposes only. Please =
send
>> your comments to the IESG mailing list (iesg at ietf.org) by =
2013-10-10.
>>=20
>> Extensions for Scalable DNS Service Discovery  (dnssd)
>> ------------------------------------------------
>> Current Status: Proposed WG
>>=20
>> Chairs:
>> Ralph Droms <rdroms.ietf@gmail.com>
>> Tim Chown <tjc@ecs.soton.ac.uk>
>>=20
>> Assigned Area Director:
>> Ted Lemon <ted.lemon@nominum.com>
>>=20
>> Mailing list
>> Address: dnssdext@ietf.org
>> To Subscribe: dnssdext-request@ietf.org
>> Archive: http://www.ietf.org/mail-archive/web/dnssdext
>>=20
>> Charter:
>>=20
>> Background
>> ----------
>>=20
>> Zero configuration networking protocols are currently well suited to
>> discover services within the scope of a single link.  In particular,
>> the DNS-SD [RFC 6763] and mDNS [RFC6762] protocol suite (sometimes
>> referred to using Apple Computer Inc.'s trademark, Bonjour) are
>> widely used for DNS-based service discovery and host name resolution
>> on a single link.
>>=20
>> The DNS-SD/mDNS protocol suite is used in many scenarios including
>> home, campus, and enterprise networks.  However, the zero =
configuration
>> mDNS protocol is constrained to link-local multicast scope by design,
>> and therefore cannot be used to discover services on remote links.
>>=20
>> In a home network that consists of a single (possibly bridged) link,
>> users experience the expected discovery behavior; available services
>> appear because all devices share a common link.  However, in =
multi-link
>> home networks (as envisaged by the homenet WG) or in routed campus or
>> enterprise networks, devices and users can only discover services on
>> the same link, which is a significant limitation.  This has led to
>> calls, such as the Educause petition, to develop an appropriate =
service
>> discovery solution to span multiple links or to perform discovery =
across
>> a wide area, not necessarily on directly connected links.
>>=20
>> In addition, the "Smart Energy Profile 2 Application Protocol =
Standard",
>> published by ZigBee Alliance and HomePlug Powerline Alliance =
specifies
>> the DNS-SD/mDNS protocol suite as the basis for its method of zero
>> configuration service discovery.  However, its use of wireless mesh
>> multi-link subnets in conjunction with traditional routed networks =
will
>> require extensions to the DNS-SD/mDNS protocols to allow operation
>> across multiple links.
>>=20
>> The scenarios in which multi-link service discovery is required may
>> be zero configuration environments, environments where administrative
>> configuration is supported, or a mixture of the two.
>>=20
>> As demand for service discovery across wider area routed networks
>> grows, some vendors are beginning to ship proprietary solutions.  It
>> is thus both timely and important that efforts to develop improved,=20=

>> scalable, autonomous service discovery solutions for routed networks=20=

>> are coordinated towards producing a single, standards-based solution.
>>=20
>> The WG will consider the tradeoffs between reusing/extending existing
>> protocols and developing entirely new ones.  It is highly desirable
>> that any new solution is backwardly compatible with existing =
DNS-SD/mDNS
>> deployments.  Any solution developed by the dnssd WG must not =
conflict
>> or interfere with the operation of other zero-configuration service =
and
>> naming protocols such as uPnP or LLMNR.  Integration with such =
protocols
>> is out of scope for this WG.
>>=20
>> The focus of the WG is to develop a solution for extended, scalable=20=

>> DNS-SD.  This work is likely to highlight problems and challenges =
with=20
>> naming protocols, as some level of coexistence will be required =
between=20
>> local zero configuration name services and those forming part of the=20=

>> global DNS.  It is important that these issues are captured and=20
>> documented for further analysis; solving those problems is however =
not=20
>> within the scope of this WG.
>>=20
>> Working Group Description
>> -------------------------
>>=20
>> To that end, the primary goals of the dnssd WG are as follows:
>>=20
>> 1. To document a set of requirements for scalable, autonomous
>>  DNS-based service discovery in routed, multi-link networks in the
>>  following five scenarios:
>>=20
>>  (A) Personal Area networks, e.g., one laptop and one printer.
>>      This is the simplest example of a service discovery network,
>>      and may or may not have external connectivity.=20
>>=20
>>  (B) Home networks, as envisaged by the homenet WG, consisting of=20
>>      one or more exit routers, with one or more upstream providers=20
>>      or networks, and an arbitrary internal topology with=20
>>      heterogeneous media where routing is automatically configured.=20=

>>      The home network would typically be a single zero configuration=20=

>>      administrative domain with a relatively limited number of=20
>>      devices.=20
>>=20
>>  (C) Wireless 'hotspot' networks, which may include wireless networks
>>      made available in public places, or temporary or permanent
>>      infrastructures targeted towards meeting or conference style
>>      events, e.g., as provided for IETF meetings.  In such
>>      environments other devices may be more likely to be 'hostile'
>>      to the user.
>>=20
>>  (D) Enterprise networks, consisting of larger routed networks,=20
>>      with large numbers of devices, which may be deployments=20
>>      spanning over multiple sites with multiple upstreams, and
>>      one more more administrative domains (depending on internal
>>      administrative delegation).  The large majority of the=20
>>      forwarding and security devices are configured.  These may
>>      be commercial or academic networks, with differing levels=20
>>      of administrative control over certain devices on the network,
>>      and BYOD devices commonplace in the campus scenario.
>>=20
>>  (E) Mesh networks such as RPL/6LoWPAN, with one or more links per
>>      routable prefix, which may or may not have external =
connectivity.
>>      The topology may use technologies including 802.11 wireless,=20
>>      HomePlug AV and GP, and ZigBee IP.=20
>>=20
>>  In the above scenarios, the aim is to facilitate service discovery=20=

>>  across the defined site.  It is also desirable that a user or =
device,=20
>>  when away from such a site, is still able to discover services=20
>>  within that site, e.g. a user discovering services in their home=20
>>  network while remote from it.
>>=20
>>  It is also desirable that multiple discovery scopes are supported,
>>  from the point of view of announcements and discovery, be the
>>  scope 'site', 'building', or 'room'.  A user for example may only
>>  be interested in devices in the same room.
>>=20
>> 2. To develop an improved, scalable solution for service discovery=20
>>  that can operate in multi-link networks, where devices may be
>>  in neighboring or non-neighboring links, applicable to
>>  the scenarios above.  The solution will consider tradeoffs between
>>  reusing/extending existing protocols and developing entirely new
>>  protocols.=20
>>=20
>>  The solution should include documentation or definition of the
>>  interfaces that can be implemented, separately to transport of=20
>>  the information.
>>=20
>> 3. To document challenges and problems encountered in the coexistence=20=

>>  of zero configuration and global DNS name services in such=20
>>  multi-link networks, including consideration of both the name=20
>>  resolution mechanism and the namespace.
>>=20
>> It is important that the dnssd WG takes input from stakeholders in
>> the scenarios it is considering.  For example, the homenet WG is
>> currently evaluating its own requirements for naming and service
>> discovery; it is up to the homenet WG as to whether it wishes to
>> recommend adoption of the solution developed in the dnssd WG, but
>> coordination between the WGs is desirable.
>>=20
>> Deliverables:
>>=20
>> The WG will produce three documents: an Informational RFC on the
>> requirements for service discovery protocols operating on potentially
>> non-neighboring multi-link networks as described above; a Standards
>> Track RFC documenting an extended, scalable service discovery =
solution=20
>> that is applicable to those scenarios; and an Informational RFC=20
>> describing the problems arising when developing the extended SD =
solution=20
>> and how it affects the integration of local zero configuration and =
global
>>=20
>> DNS name services.
>>=20
>> Milestones:
>> Sep 2013 - Formation of the WG
>> Oct 2013 - Adopt requirements draft as WG document
>> Jan 2014 - Submit requirements draft to the IESG as an Informational
>> RFC
>> Mar 2014 - Adopt wide-area service discovery solution draft as WG
>> document=20
>> Mar 2014 - Adopt Informational document on the problems and =
challenges
>> arising for zeroconf and unicast DNS name services
>> Sep 2014 - Submit wide-area service discovery solution draft to the
>> IESG as Standards Track RFC=20
>> Sep 2014 - Submit the zeroconf and unicast DNS "problems and
>> challenges" draft to the IESG as Informational.
>>=20
>>=20
>=20


--Apple-Mail=_2193BD6E-6B92-4549-A4F3-42F75A2BC089
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; =
"><div><div>On 3 Oct 2013, at 18:07, manning bill &lt;<a =
href=3D"mailto:bmanning@isi.edu">bmanning@isi.edu</a>&gt; =
wrote:</div><br><blockquote type=3D"cite"> &nbsp;----- The following =
addresses had permanent fatal errors -----<br>&lt;<a =
href=3D"mailto:dnssdext-request@ietf.org">dnssdext-request@ietf.org</a>&gt=
;<br> &nbsp;&nbsp;(reason: 550 5.1.1 &lt;<a =
href=3D"mailto:dnssdext-request@ietf.org">dnssdext-request@ietf.org</a>&gt=
;: Recipient address rejected: User unknown in virtual alias =
table)<br></blockquote><div><br></div>I think the active list is still =
<a =
href=3D"mailto:mdnsext@ietf.org">mdnsext@ietf.org</a>?</div><div>See:&nbsp=
;<a =
href=3D"http://www.ietf.org/mail-archive/web/mdnsext/current/maillist.html=
">http://www.ietf.org/mail-archive/web/mdnsext/current/maillist.html</a></=
div><div><br></div><div>And the 'header' information below should now =
probably read something like this:</div><div><br></div><div>--- snip =
---</div><div><br></div><div>Scalable DNS Service Discovery =
&nbsp;(dnssd)<br>------------------------------------------------<br>Curre=
nt Status: Proposed WG<br><br>Chairs:<br>&nbsp;Ralph Droms &lt;<a =
href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@gmail.com</a>&gt;<br>&nb=
sp;Tim Chown &lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt;<br><br>Ass=
igned Area Director:<br>&nbsp;Ted Lemon &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt;<br><br=
>Mailing list<br>&nbsp;Address:&nbsp;<a =
href=3D"mailto:dnssdext@ietf.org">dnssd@ietf.org</a><br>&nbsp;To =
Subscribe:&nbsp;<a =
href=3D"mailto:dnssdext-request@ietf.org">dnssd-request@ietf.org</a><br>&n=
bsp;Archive:&nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/dnssd">http://www.ietf.org/ma=
il-archive/web/dnssd</a></div><div>&nbsp;Pre-WG BoF Archive:&nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/">http://www.ietf.org/mail-ar=
chive/web/</a>mdnsext&nbsp;</div><div><br></div><div><br></div><div>--- =
snip ---</div><div><br></div><div>Tim</div><div><br><blockquote =
type=3D"cite"><br><br><br>On 3October2013Thursday, at 8:42, The IESG =
wrote:<br><br><blockquote type=3D"cite">A new IETF working group has =
been proposed in the Internet Area. The IESG<br>has not made any =
determination yet. The following draft charter was<br>submitted, and is =
provided for informational purposes only. Please send<br>your comments =
to the IESG mailing list (iesg at <a =
href=3D"http://ietf.org">ietf.org</a>) by 2013-10-10.<br><br>Extensions =
for Scalable DNS Service Discovery =
&nbsp;(dnssd)<br>------------------------------------------------<br>Curre=
nt Status: Proposed WG<br><br>Chairs:<br> Ralph Droms &lt;<a =
href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@gmail.com</a>&gt;<br> =
Tim Chown &lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt;<br><br>Ass=
igned Area Director:<br> Ted Lemon &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt;<br><br=
>Mailing list<br> Address: <a =
href=3D"mailto:dnssdext@ietf.org">dnssdext@ietf.org</a><br> To =
Subscribe: <a =
href=3D"mailto:dnssdext-request@ietf.org">dnssdext-request@ietf.org</a><br=
> Archive: <a =
href=3D"http://www.ietf.org/mail-archive/web/dnssdext">http://www.ietf.org=
/mail-archive/web/dnssdext</a><br><br>Charter:<br><br>Background<br>------=
----<br><br>Zero configuration networking protocols are currently well =
suited to<br>discover services within the scope of a single link. =
&nbsp;In particular,<br>the DNS-SD [RFC 6763] and mDNS [RFC6762] =
protocol suite (sometimes<br>referred to using Apple Computer Inc.'s =
trademark, Bonjour) are<br>widely used for DNS-based service discovery =
and host name resolution<br>on a single link.<br><br>The DNS-SD/mDNS =
protocol suite is used in many scenarios including<br>home, campus, and =
enterprise networks. &nbsp;However, the zero configuration<br>mDNS =
protocol is constrained to link-local multicast scope by design,<br>and =
therefore cannot be used to discover services on remote links.<br><br>In =
a home network that consists of a single (possibly bridged) =
link,<br>users experience the expected discovery behavior; available =
services<br>appear because all devices share a common link. =
&nbsp;However, in multi-link<br>home networks (as envisaged by the =
homenet WG) or in routed campus or<br>enterprise networks, devices and =
users can only discover services on<br>the same link, which is a =
significant limitation. &nbsp;This has led to<br>calls, such as the =
Educause petition, to develop an appropriate service<br>discovery =
solution to span multiple links or to perform discovery across<br>a wide =
area, not necessarily on directly connected links.<br><br>In addition, =
the "Smart Energy Profile 2 Application Protocol Standard",<br>published =
by ZigBee Alliance and HomePlug Powerline Alliance specifies<br>the =
DNS-SD/mDNS protocol suite as the basis for its method of =
zero<br>configuration service discovery. &nbsp;However, its use of =
wireless mesh<br>multi-link subnets in conjunction with traditional =
routed networks will<br>require extensions to the DNS-SD/mDNS protocols =
to allow operation<br>across multiple links.<br><br>The scenarios in =
which multi-link service discovery is required may<br>be zero =
configuration environments, environments where =
administrative<br>configuration is supported, or a mixture of the =
two.<br><br>As demand for service discovery across wider area routed =
networks<br>grows, some vendors are beginning to ship proprietary =
solutions. &nbsp;It<br>is thus both timely and important that efforts to =
develop improved, <br>scalable, autonomous service discovery solutions =
for routed networks <br>are coordinated towards producing a single, =
standards-based solution.<br><br>The WG will consider the tradeoffs =
between reusing/extending existing<br>protocols and developing entirely =
new ones. &nbsp;It is highly desirable<br>that any new solution is =
backwardly compatible with existing DNS-SD/mDNS<br>deployments. =
&nbsp;Any solution developed by the dnssd WG must not conflict<br>or =
interfere with the operation of other zero-configuration service =
and<br>naming protocols such as uPnP or LLMNR. &nbsp;Integration with =
such protocols<br>is out of scope for this WG.<br><br>The focus of the =
WG is to develop a solution for extended, scalable <br>DNS-SD. =
&nbsp;This work is likely to highlight problems and challenges with =
<br>naming protocols, as some level of coexistence will be required =
between <br>local zero configuration name services and those forming =
part of the <br>global DNS. &nbsp;It is important that these issues are =
captured and <br>documented for further analysis; solving those problems =
is however not <br>within the scope of this WG.<br><br>Working Group =
Description<br>-------------------------<br><br>To that end, the primary =
goals of the dnssd WG are as follows:<br><br>1. To document a set of =
requirements for scalable, autonomous<br> &nbsp;DNS-based service =
discovery in routed, multi-link networks in the<br> &nbsp;following five =
scenarios:<br><br> &nbsp;(A) Personal Area networks, e.g., one laptop =
and one printer.<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This is the simplest =
example of a service discovery network,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and may or may not have external =
connectivity. <br><br> &nbsp;(B) Home networks, as envisaged by the =
homenet WG, consisting of <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;one or more =
exit routers, with one or more upstream providers <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;or networks, and an arbitrary internal =
topology with <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;heterogeneous media =
where routing is automatically configured. <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The home network would typically be a =
single zero configuration <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;administrative domain with a relatively =
limited number of <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;devices. <br><br> =
&nbsp;(C) Wireless 'hotspot' networks, which may include wireless =
networks<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;made available in public =
places, or temporary or permanent<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;infrastructures targeted towards meeting =
or conference style<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;events, e.g., as =
provided for IETF meetings. &nbsp;In such<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;environments other devices may be more =
likely to be 'hostile'<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;to the =
user.<br><br> &nbsp;(D) Enterprise networks, consisting of larger routed =
networks, <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with large numbers of =
devices, which may be deployments <br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;spanning over multiple sites with multiple =
upstreams, and<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;one more more =
administrative domains (depending on internal<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;administrative delegation). &nbsp;The =
large majority of the <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;forwarding and =
security devices are configured. &nbsp;These may<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;be commercial or academic networks, with =
differing levels <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of administrative =
control over certain devices on the network,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and BYOD devices commonplace in the campus =
scenario.<br><br> &nbsp;(E) Mesh networks such as RPL/6LoWPAN, with one =
or more links per<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;routable prefix, =
which may or may not have external connectivity.<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The topology may use technologies =
including 802.11 wireless, <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HomePlug =
AV and GP, and ZigBee IP. <br><br> &nbsp;In the above scenarios, the aim =
is to facilitate service discovery <br> &nbsp;across the defined site. =
&nbsp;It is also desirable that a user or device, <br> &nbsp;when away =
from such a site, is still able to discover services <br> &nbsp;within =
that site, e.g. a user discovering services in their home <br> =
&nbsp;network while remote from it.<br><br> &nbsp;It is also desirable =
that multiple discovery scopes are supported,<br> &nbsp;from the point =
of view of announcements and discovery, be the<br> &nbsp;scope 'site', =
'building', or 'room'. &nbsp;A user for example may only<br> &nbsp;be =
interested in devices in the same room.<br><br>2. To develop an =
improved, scalable solution for service discovery <br> &nbsp;that can =
operate in multi-link networks, where devices may be<br> &nbsp;in =
neighboring or non-neighboring links, applicable to<br> &nbsp;the =
scenarios above. &nbsp;The solution will consider tradeoffs between<br> =
&nbsp;reusing/extending existing protocols and developing entirely =
new<br> &nbsp;protocols. <br><br> &nbsp;The solution should include =
documentation or definition of the<br> &nbsp;interfaces that can be =
implemented, separately to transport of <br> &nbsp;the =
information.<br><br>3. To document challenges and problems encountered =
in the coexistence <br> &nbsp;of zero configuration and global DNS name =
services in such <br> &nbsp;multi-link networks, including consideration =
of both the name <br> &nbsp;resolution mechanism and the =
namespace.<br><br>It is important that the dnssd WG takes input from =
stakeholders in<br>the scenarios it is considering. &nbsp;For example, =
the homenet WG is<br>currently evaluating its own requirements for =
naming and service<br>discovery; it is up to the homenet WG as to =
whether it wishes to<br>recommend adoption of the solution developed in =
the dnssd WG, but<br>coordination between the WGs is =
desirable.<br><br>Deliverables:<br><br>The WG will produce three =
documents: an Informational RFC on the<br>requirements for service =
discovery protocols operating on potentially<br>non-neighboring =
multi-link networks as described above; a Standards<br>Track RFC =
documenting an extended, scalable service discovery solution <br>that is =
applicable to those scenarios; and an Informational RFC <br>describing =
the problems arising when developing the extended SD solution <br>and =
how it affects the integration of local zero configuration and =
global<br><br>DNS name services.<br><br>Milestones:<br> Sep 2013 - =
Formation of the WG<br> Oct 2013 - Adopt requirements draft as WG =
document<br> Jan 2014 - Submit requirements draft to the IESG as an =
Informational<br>RFC<br> Mar 2014 - Adopt wide-area service discovery =
solution draft as WG<br>document <br> Mar 2014 - Adopt Informational =
document on the problems and challenges<br>arising for zeroconf and =
unicast DNS name services<br> Sep 2014 - Submit wide-area service =
discovery solution draft to the<br>IESG as Standards Track RFC <br> Sep =
2014 - Submit the zeroconf and unicast DNS "problems and<br>challenges" =
draft to the IESG as =
Informational.<br><br><br></blockquote><br></blockquote></div><br></body><=
/html>=

--Apple-Mail=_2193BD6E-6B92-4549-A4F3-42F75A2BC089--

From superuser@gmail.com  Thu Oct  3 11:55:54 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 44DC521E80C5 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 11:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  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 1QmF7QYKXQ0g for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 11:55:47 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id A098921F8EEA for <ietf@ietf.org>; Thu,  3 Oct 2013 11:45:12 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id t60so3312567wes.14 for <ietf@ietf.org>; Thu, 03 Oct 2013 11:45:11 -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=A8Vs3PgAkGfXwPJaqkZk1YncK8+Q+e7OfGTOxiuE9MI=; b=xEIuzPlUSuL1iI00dHk2SxTsOXOi7O7IM4b45akBJeaGB8xjrnvp0LzG5HaI7gocbm nQhi8wWZAPitciPHp7ZizD8i/jvJYPfYNNJzYw9EfnVhkjC/04e+mt8H5/pi1mT8WQoL +67FY4Mm/A7nnFf/aeDcUBbGk+eCEPpjHtCJp/VfxkClNJwx8CD0nNwl/Cf8dzP8MaZU xJMLfQll2GXjt/li7SX0nkVgbvxj/J3FHCUcGhygDF8vMHaQilgUPZUIN5cXCRw8N0LE f3+JwZA8eBYyCNIOlzlmmQLp7hPkt4427JudPfcRz9nCinh1yfPlQNqRJKE+0WG9m2T1 uavg==
MIME-Version: 1.0
X-Received: by 10.180.189.132 with SMTP id gi4mr3804525wic.19.1380825911584; Thu, 03 Oct 2013 11:45:11 -0700 (PDT)
Received: by 10.180.18.202 with HTTP; Thu, 3 Oct 2013 11:45:11 -0700 (PDT)
In-Reply-To: <524D5ACF.3020008@isdg.net>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net>
Date: Thu, 3 Oct 2013 11:45:11 -0700
Message-ID: <CAL0qLwYi0nygjH+NWxp6OkKj3cLwBP=rkZd-Lj-6sV1JR4W2JA@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=001a11c35294f4f08a04e7da951a
Cc: Barry Leiba <barryleiba@computer.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, 03 Oct 2013 18:55:54 -0000

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

On Thu, Oct 3, 2013 at 4:53 AM, Hector Santos <hsantos@isdg.net> wrote:

>
> I don't believe this would be a fair assessment of industry wide support
> -- using only one API to measure. There are other APIs and proprietary
> systems who most likely are not part of the OpenDKIM group.  There are
> commercial operations using DKIM and ADSP is part of it.
>

I would hope this is obvious, but I didn't claim my little survey was
representative of the entire industry.  It's at best a cross section of
OpenDKIM's user base (which does include at least three of the largest
operators, but by no means all of them).  I made it clear how many replies
I'd gotten.


> Applicability and Impact reports *should* to be done before pulling the
> rug from under the non-OpenDKIM market feet.  In addition, it appears part
> of the request is to help move an alternative DMARC protocol forward. Why
> would the DMARC replacement do better?  Why should commercial development
> for ADSP be stopped and removed from products, and now a new investment for
> DMARC be done?  Would this resolve the apparent interop problem with the
> specific Mailing List Software who refuse to support a DKIM security
> protocol?
>

The ADSP impact reports that are part of RFC6377, the writeup for this
action, and elsewhere already exist and are not specific to one
implementation.

I don't think there's any particular DMARC-specific agenda here, but it is
indeed obvious that (a) they overlap in a few ways, and (b) DMARC has not
yet been accepted as IETF work but already has more deployment and support
momentum than ADSP ever enjoyed.

More importantly, why should any small operator and participant of the IETF
> continue to support IETF projects if their support is ignored and projects
> will be ended without their input or even explaining why it should be
> ended?  That doesn't play well for the IETF Diversity Improvement Program.
>

I think it's rather premature to claim anyone's input has been ignored when
the solicitation for comment is still open.

-MSK

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

<div dir=3D"ltr">On Thu, Oct 3, 2013 at 4:53 AM, Hector Santos <span dir=3D=
"ltr">&lt;<a href=3D"mailto:hsantos@isdg.net" target=3D"_blank">hsantos@isd=
g.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_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"HOEnZb"><div class=3D"h5"><br>=
</div></div>
I don&#39;t believe this would be a fair assessment of industry wide suppor=
t -- using only one API to measure. There are other APIs and proprietary sy=
stems who most likely are not part of the OpenDKIM group. =A0There are comm=
ercial operations using DKIM and ADSP is part of it.<br>
</blockquote><div><br></div><div>I would hope this is obvious, but I didn&#=
39;t claim my little survey was representative of the entire industry.=A0 I=
t&#39;s at best a cross section of OpenDKIM&#39;s user base (which does inc=
lude at least three of the largest operators, but by no means all of them).=
=A0 I made it clear how many replies I&#39;d gotten.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
Applicability and Impact reports *should* to be done before pulling the rug=
 from under the non-OpenDKIM market feet. =A0In addition, it appears part o=
f the request is to help move an alternative DMARC protocol forward. Why wo=
uld the DMARC replacement do better? =A0Why should commercial development f=
or ADSP be stopped and removed from products, and now a new investment for =
DMARC be done? =A0Would this resolve the apparent interop problem with the =
specific Mailing List Software who refuse to support a DKIM security protoc=
ol?<br>
</blockquote><div><br></div><div>The ADSP impact reports that are part of R=
FC6377, the writeup for this action, and elsewhere already exist and are no=
t specific to one implementation.<br><br></div><div>I don&#39;t think there=
&#39;s any particular DMARC-specific agenda here, but it is indeed obvious =
that (a) they overlap in a few ways, and (b) DMARC has not yet been accepte=
d as IETF work but already has more deployment and support momentum than AD=
SP ever enjoyed.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
More importantly, why should any small operator and participant of the IETF=
 continue to support IETF projects if their support is ignored and projects=
 will be ended without their input or even explaining why it should be ende=
d? =A0That doesn&#39;t play well for the IETF Diversity Improvement Program=
.<span class=3D"HOEnZb"><font color=3D"#888888"><br>

</font></span></blockquote><div><br></div><div>I think it&#39;s rather prem=
ature to claim anyone&#39;s input has been ignored when the solicitation fo=
r comment is still open.<br><br></div><div>-MSK<br></div></div></div></div>

--001a11c35294f4f08a04e7da951a--

From bmanning@isi.edu  Thu Oct  3 12:20:08 2013
Return-Path: <bmanning@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 98BD621F9AA1; Thu,  3 Oct 2013 12:20:08 -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=[AWL=2.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 Pqv-IN-fuCsB; Thu,  3 Oct 2013 12:19:56 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6C321F9C7B; Thu,  3 Oct 2013 12:07:05 -0700 (PDT)
Received: from [128.9.184.131] ([128.9.184.131]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r93J5pq2012326 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 3 Oct 2013 12:05:51 -0700 (PDT)
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
Date: Thu, 3 Oct 2013 12:05:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.edu>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 19:20:08 -0000

but the "To Subscribe" pointer is busted=85.


/bill


On 3October2013Thursday, at 11:43, Tim Chown wrote:

> On 3 Oct 2013, at 18:07, manning bill <bmanning@isi.edu> wrote:
>=20
>>  ----- The following addresses had permanent fatal errors -----
>> <dnssdext-request@ietf.org>
>>   (reason: 550 5.1.1 <dnssdext-request@ietf.org>: Recipient address =
rejected: User unknown in virtual alias table)
>=20
> I think the active list is still mdnsext@ietf.org?
> See: =
http://www.ietf.org/mail-archive/web/mdnsext/current/maillist.html
>=20
> And the 'header' information below should now probably read something =
like this:
>=20
> --- snip ---
>=20
> Scalable DNS Service Discovery  (dnssd)
> ------------------------------------------------
> Current Status: Proposed WG
>=20
> Chairs:
>  Ralph Droms <rdroms.ietf@gmail.com>
>  Tim Chown <tjc@ecs.soton.ac.uk>
>=20
> Assigned Area Director:
>  Ted Lemon <ted.lemon@nominum.com>
>=20
> Mailing list
>  Address: dnssd@ietf.org
>  To Subscribe: dnssd-request@ietf.org
>  Archive: http://www.ietf.org/mail-archive/web/dnssd
>  Pre-WG BoF Archive: http://www.ietf.org/mail-archive/web/mdnsext=20
>=20
>=20
> --- snip ---
>=20
> Tim
>=20
>>=20
>>=20
>>=20
>> On 3October2013Thursday, at 8:42, The IESG wrote:
>>=20
>>> A new IETF working group has been proposed in the Internet Area. The =
IESG
>>> has not made any determination yet. The following draft charter was
>>> submitted, and is provided for informational purposes only. Please =
send
>>> your comments to the IESG mailing list (iesg at ietf.org) by =
2013-10-10.
>>>=20
>>> Extensions for Scalable DNS Service Discovery  (dnssd)
>>> ------------------------------------------------
>>> Current Status: Proposed WG
>>>=20
>>> Chairs:
>>> Ralph Droms <rdroms.ietf@gmail.com>
>>> Tim Chown <tjc@ecs.soton.ac.uk>
>>>=20
>>> Assigned Area Director:
>>> Ted Lemon <ted.lemon@nominum.com>
>>>=20
>>> Mailing list
>>> Address: dnssdext@ietf.org
>>> To Subscribe: dnssdext-request@ietf.org
>>> Archive: http://www.ietf.org/mail-archive/web/dnssdext
>>>=20
>>> Charter:
>>>=20
>>> Background
>>> ----------
>>>=20
>>> Zero configuration networking protocols are currently well suited to
>>> discover services within the scope of a single link.  In particular,
>>> the DNS-SD [RFC 6763] and mDNS [RFC6762] protocol suite (sometimes
>>> referred to using Apple Computer Inc.'s trademark, Bonjour) are
>>> widely used for DNS-based service discovery and host name resolution
>>> on a single link.
>>>=20
>>> The DNS-SD/mDNS protocol suite is used in many scenarios including
>>> home, campus, and enterprise networks.  However, the zero =
configuration
>>> mDNS protocol is constrained to link-local multicast scope by =
design,
>>> and therefore cannot be used to discover services on remote links.
>>>=20
>>> In a home network that consists of a single (possibly bridged) link,
>>> users experience the expected discovery behavior; available services
>>> appear because all devices share a common link.  However, in =
multi-link
>>> home networks (as envisaged by the homenet WG) or in routed campus =
or
>>> enterprise networks, devices and users can only discover services on
>>> the same link, which is a significant limitation.  This has led to
>>> calls, such as the Educause petition, to develop an appropriate =
service
>>> discovery solution to span multiple links or to perform discovery =
across
>>> a wide area, not necessarily on directly connected links.
>>>=20
>>> In addition, the "Smart Energy Profile 2 Application Protocol =
Standard",
>>> published by ZigBee Alliance and HomePlug Powerline Alliance =
specifies
>>> the DNS-SD/mDNS protocol suite as the basis for its method of zero
>>> configuration service discovery.  However, its use of wireless mesh
>>> multi-link subnets in conjunction with traditional routed networks =
will
>>> require extensions to the DNS-SD/mDNS protocols to allow operation
>>> across multiple links.
>>>=20
>>> The scenarios in which multi-link service discovery is required may
>>> be zero configuration environments, environments where =
administrative
>>> configuration is supported, or a mixture of the two.
>>>=20
>>> As demand for service discovery across wider area routed networks
>>> grows, some vendors are beginning to ship proprietary solutions.  It
>>> is thus both timely and important that efforts to develop improved,=20=

>>> scalable, autonomous service discovery solutions for routed networks=20=

>>> are coordinated towards producing a single, standards-based =
solution.
>>>=20
>>> The WG will consider the tradeoffs between reusing/extending =
existing
>>> protocols and developing entirely new ones.  It is highly desirable
>>> that any new solution is backwardly compatible with existing =
DNS-SD/mDNS
>>> deployments.  Any solution developed by the dnssd WG must not =
conflict
>>> or interfere with the operation of other zero-configuration service =
and
>>> naming protocols such as uPnP or LLMNR.  Integration with such =
protocols
>>> is out of scope for this WG.
>>>=20
>>> The focus of the WG is to develop a solution for extended, scalable=20=

>>> DNS-SD.  This work is likely to highlight problems and challenges =
with=20
>>> naming protocols, as some level of coexistence will be required =
between=20
>>> local zero configuration name services and those forming part of the=20=

>>> global DNS.  It is important that these issues are captured and=20
>>> documented for further analysis; solving those problems is however =
not=20
>>> within the scope of this WG.
>>>=20
>>> Working Group Description
>>> -------------------------
>>>=20
>>> To that end, the primary goals of the dnssd WG are as follows:
>>>=20
>>> 1. To document a set of requirements for scalable, autonomous
>>>  DNS-based service discovery in routed, multi-link networks in the
>>>  following five scenarios:
>>>=20
>>>  (A) Personal Area networks, e.g., one laptop and one printer.
>>>      This is the simplest example of a service discovery network,
>>>      and may or may not have external connectivity.=20
>>>=20
>>>  (B) Home networks, as envisaged by the homenet WG, consisting of=20
>>>      one or more exit routers, with one or more upstream providers=20=

>>>      or networks, and an arbitrary internal topology with=20
>>>      heterogeneous media where routing is automatically configured.=20=

>>>      The home network would typically be a single zero configuration=20=

>>>      administrative domain with a relatively limited number of=20
>>>      devices.=20
>>>=20
>>>  (C) Wireless 'hotspot' networks, which may include wireless =
networks
>>>      made available in public places, or temporary or permanent
>>>      infrastructures targeted towards meeting or conference style
>>>      events, e.g., as provided for IETF meetings.  In such
>>>      environments other devices may be more likely to be 'hostile'
>>>      to the user.
>>>=20
>>>  (D) Enterprise networks, consisting of larger routed networks,=20
>>>      with large numbers of devices, which may be deployments=20
>>>      spanning over multiple sites with multiple upstreams, and
>>>      one more more administrative domains (depending on internal
>>>      administrative delegation).  The large majority of the=20
>>>      forwarding and security devices are configured.  These may
>>>      be commercial or academic networks, with differing levels=20
>>>      of administrative control over certain devices on the network,
>>>      and BYOD devices commonplace in the campus scenario.
>>>=20
>>>  (E) Mesh networks such as RPL/6LoWPAN, with one or more links per
>>>      routable prefix, which may or may not have external =
connectivity.
>>>      The topology may use technologies including 802.11 wireless,=20
>>>      HomePlug AV and GP, and ZigBee IP.=20
>>>=20
>>>  In the above scenarios, the aim is to facilitate service discovery=20=

>>>  across the defined site.  It is also desirable that a user or =
device,=20
>>>  when away from such a site, is still able to discover services=20
>>>  within that site, e.g. a user discovering services in their home=20
>>>  network while remote from it.
>>>=20
>>>  It is also desirable that multiple discovery scopes are supported,
>>>  from the point of view of announcements and discovery, be the
>>>  scope 'site', 'building', or 'room'.  A user for example may only
>>>  be interested in devices in the same room.
>>>=20
>>> 2. To develop an improved, scalable solution for service discovery=20=

>>>  that can operate in multi-link networks, where devices may be
>>>  in neighboring or non-neighboring links, applicable to
>>>  the scenarios above.  The solution will consider tradeoffs between
>>>  reusing/extending existing protocols and developing entirely new
>>>  protocols.=20
>>>=20
>>>  The solution should include documentation or definition of the
>>>  interfaces that can be implemented, separately to transport of=20
>>>  the information.
>>>=20
>>> 3. To document challenges and problems encountered in the =
coexistence=20
>>>  of zero configuration and global DNS name services in such=20
>>>  multi-link networks, including consideration of both the name=20
>>>  resolution mechanism and the namespace.
>>>=20
>>> It is important that the dnssd WG takes input from stakeholders in
>>> the scenarios it is considering.  For example, the homenet WG is
>>> currently evaluating its own requirements for naming and service
>>> discovery; it is up to the homenet WG as to whether it wishes to
>>> recommend adoption of the solution developed in the dnssd WG, but
>>> coordination between the WGs is desirable.
>>>=20
>>> Deliverables:
>>>=20
>>> The WG will produce three documents: an Informational RFC on the
>>> requirements for service discovery protocols operating on =
potentially
>>> non-neighboring multi-link networks as described above; a Standards
>>> Track RFC documenting an extended, scalable service discovery =
solution=20
>>> that is applicable to those scenarios; and an Informational RFC=20
>>> describing the problems arising when developing the extended SD =
solution=20
>>> and how it affects the integration of local zero configuration and =
global
>>>=20
>>> DNS name services.
>>>=20
>>> Milestones:
>>> Sep 2013 - Formation of the WG
>>> Oct 2013 - Adopt requirements draft as WG document
>>> Jan 2014 - Submit requirements draft to the IESG as an Informational
>>> RFC
>>> Mar 2014 - Adopt wide-area service discovery solution draft as WG
>>> document=20
>>> Mar 2014 - Adopt Informational document on the problems and =
challenges
>>> arising for zeroconf and unicast DNS name services
>>> Sep 2014 - Submit wide-area service discovery solution draft to the
>>> IESG as Standards Track RFC=20
>>> Sep 2014 - Submit the zeroconf and unicast DNS "problems and
>>> challenges" draft to the IESG as Informational.
>>>=20
>>>=20
>>=20
>=20


From Ted.Lemon@nominum.com  Thu Oct  3 12:34:36 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 E857521E805D; Thu,  3 Oct 2013 12:34:36 -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 3isgxgE7Ee56; Thu,  3 Oct 2013 12:34:23 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 436CB21E80B0; Thu,  3 Oct 2013 12:17:00 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUk3Cq2iPwqHbr6JLwMpvairt29Ciwt9S@postini.com; Thu, 03 Oct 2013 12:17:00 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 CB92F1B82EC; Thu,  3 Oct 2013 12:16:58 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 356C5190075; Thu,  3 Oct 2013 12:16:58 -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.03.0158.001; Thu, 3 Oct 2013 12:16:58 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Thread-Topic: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Thread-Index: AQHOwF5B0GotrtN9IE6CWx+CuArZj5njxX0AgAAJXwA=
Date: Thu, 3 Oct 2013 19:16:57 +0000
Message-ID: <869EE259-1A87-447B-A3A8-2B8254FCB6CA@nominum.com>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk>
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: <6059774F1402C9438CC2BDB1951A7395@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, manning bill <bmanning@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, 03 Oct 2013 19:34:37 -0000

Discussion of IETF consensus activities is supposed to occur on the IETF ma=
iling list, not on the working group mailing list, which doesn't yet exist.=
  We'll set up the new mailing list when the working group is approved.   S=
orry for the confusion.


From Ted.Lemon@nominum.com  Thu Oct  3 12:38:50 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 C85B221E80CD; Thu,  3 Oct 2013 12:38: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=[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 djiYzGBJswee; Thu,  3 Oct 2013 12:38:38 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 4842221F9AD5; Thu,  3 Oct 2013 12:20:11 -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 DSNKUk3Da4V5OJa4j02DazmNSXOsrMlsSVJD@postini.com; Thu, 03 Oct 2013 12:20:11 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 E1B1F1B82F0; Thu,  3 Oct 2013 12:20:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 D53C2190075; Thu,  3 Oct 2013 12:20:10 -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.03.0158.001; Thu, 3 Oct 2013 12:20:10 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: manning bill <bmanning@isi.edu>
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Thread-Topic: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Thread-Index: AQHOwF5B0GotrtN9IE6CWx+CuArZj5njxX0AgAAGRoCAAAQAAA==
Date: Thu, 3 Oct 2013 19:20:10 +0000
Message-ID: <E54878A5-3E14-4440-8CFA-8E5CF2887214@nominum.com>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.edu>
In-Reply-To: <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.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="Windows-1252"
Content-ID: <42B3C02C1C0FEF49A973B7E2E4D67F36@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 19:38:50 -0000

On Oct 3, 2013, at 3:05 PM, manning bill <bmanning@isi.edu> wrote:
> but the "To Subscribe" pointer is busted=85.

Correct.   I should have gotten the information right before sending out th=
e announcement, but I blew it=97sorry about that.


From jaap@NLnetLabs.nl  Thu Oct  3 13:05:19 2013
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3D6321E8114; Thu,  3 Oct 2013 13:05:16 -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 afGPs0l2xEpL; Thu,  3 Oct 2013 13:05:09 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4ccb]) by ietfa.amsl.com (Postfix) with ESMTP id 89AAA21F8319; Thu,  3 Oct 2013 12:47:12 -0700 (PDT)
Received: from bela.nlnetlabs.nl (localhost [IPv6:::1]) by bela.nlnetlabs.nl (8.14.7/8.14.7) with ESMTP id r93JkaUQ026289; Thu, 3 Oct 2013 21:46:37 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
Authentication-Results: bela.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
Message-Id: <201310031946.r93JkaUQ026289@bela.nlnetlabs.nl>
To: manning bill <bmanning@isi.edu>
Subject: Re: WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.edu>
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.edu>
Comments: In-reply-to manning bill <bmanning@isi.edu> message dated "Thu, 03 Oct 2013 12:05:51 -0700."
Date: Thu, 03 Oct 2013 21:46:36 +0200
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (bela.nlnetlabs.nl [IPv6:::1]); Thu, 03 Oct 2013 21:46:38 +0200 (CEST)
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 20:05:21 -0000

    but the "To Subscribe" pointer is busted.

According to <https://www.ietf.org/mailman/listinfo> the list is supposed
to be <https://www.ietf.org/mailman/listinfo/mdnsext>.

	jaap

From hsantos@isdg.net  Thu Oct  3 13:13:03 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 AF49121F9B66 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 13:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[AWL=0.298, 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 9s0bd5cEVNAL for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 13:12:52 -0700 (PDT)
Received: from ntbbs.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B553121E8096 for <ietf@ietf.org>; Thu,  3 Oct 2013 12:55:20 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2557; t=1380830112; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=BvraxwME9SThEpMkiUaY+FW+g+4=; b=GarF7FEOAYy9F7ClSEqA 4Of9I8D9d2Lki+38Z2TD6aQvkk69IQAQrMIbX9gWFz+RIR6or2MxM+qQ31ie+FKL RU65H/q4x1tPD/sIwHfqJlobMkpDVlOTs4i8HIuhl2o3CT8JJHhvLu20GE2zxCjV abKJrWZR6Zh/gpPb78WZW88=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 15:55:12 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2997618011.4443.1336; Thu, 03 Oct 2013 15:55:11 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2557; t=1380829723; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=5ReIjRo 23CaVFzLFr/RSjDwWGGJbiaZu8JyehWnMwoI=; b=ryi469Xdzz2LBlZSw2dRsvz PAkQUSBCOfn9/t7eZJP421O1YPlwO2xRWd0qfkjWUvszYU+fzg9D27jMiq99hohB 1xjlGWFDvbrEdw3z/8k/BPe6cAqGFr5UlM5pnFoV1izoDyj6qc5d6bb3P7+iSoph xkWavjUEg7GKvYTvDwwI=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 15:48:43 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2444004878.9.2624; Thu, 03 Oct 2013 15:48:43 -0400
Message-ID: <524DCBA0.1090302@isdg.net>
Date: Thu, 03 Oct 2013 15:55:12 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: How to protect DKIM signatures: Moving ADSP to Historic, supporting DMARC instead
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net> <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com>
In-Reply-To: <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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, 03 Oct 2013 20:13:03 -0000

On 10/3/2013 1:51 PM, Douglas Otis wrote:
>
> Dear Hector,
>
> Indeed, more should be said about underlying reasons.  The reason for abandoning ADSP is for the same reason few providers reject messages not authorized by SPF records ending in "-all" (FAIL).  Mailing-List software existed long before either of these strategies and domains using mailing lists need to be excluded from having DMARC policies (until a revised ATPS specification able to use normal signatures is published.)  The reason for moving toward DMARC is, although aligned policy is only suitable for domains limited to messages of a transactional nature, places where one authorization scheme fails can be mostly recovered by the other which greatly increases the chances of a domain's policy being applied in the desired fashion.
>

Whether its ADSP, DMARC or anything else, any DKIM resigner has to be 
aware of the consequences of blind signing.  It can not operate in a 
vacuum as if all of the following documents did not exist:

    RFC4686  Analysis of Threats Motivating DKIM
    RFC5016  Requirements for a DKIM Signing Practices Protocol
    RFC5585  DKIM Service Overview
    RFC5617  DKIM Author Domain Signing Practices (ADSP)
    RFC5863  DKIM Development, Deployment, and Operations
    RFC6377  DomainKeys Identified Mail (DKIM) and Mailing Lists

All of them describe a basic integrated concept of protecting the 
domain signature which is still a problem to be resolved today 
otherwise the payoff of the new DKIM "Internet Standard" is still 
Zilch, Nada, Nil.

So if the movement is now towards DMARC, are mailing list software 
going to support the policies exposed by DMARC restrictive domains?

We are not resolving the basic debate that was always with us. 
Stripping Policy from DKIM framework as a separate SSP, then further 
relaxing it and changing it to ADSP and now DMARC does not resolve the 
basic fundamental problem with securing DKIM signatures if middleware 
are not going to support the concept and continue with blind 
resigning.

Make ADSP historic and DKIM itself is at risk of finally falling into 
that wasted protocol project as well.  Sure everyone is signing but 
also stripping and replacing everyone's signature, its value has been 
totally lost.

Go figure. I think the requester of this change ought to write a 
report explaining how making ADSP historic and adopting DMARC 
minimizes any impact and also helps keep DKIM as a viable mail 
signature concept to have.  How the payoff is finally realized with 
DMARC rather an ADSP.

-- 
HLS



From barryleiba.mailing.lists@gmail.com  Thu Oct  3 13:52:51 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 ADADE21F969F for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 13:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.91
X-Spam-Level: 
X-Spam-Status: No, score=-101.91 tagged_above=-999 required=5 tests=[AWL=0.068, 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 LexacMT2KrYf for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 13:52:37 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED2B21F92CD for <ietf@ietf.org>; Thu,  3 Oct 2013 13:37:49 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id eh20so2461907lab.18 for <ietf@ietf.org>; Thu, 03 Oct 2013 13:37:48 -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:message-id:subject :from:to:cc:content-type; bh=hn0+AlcLwUyA9d6k/NX5zYSqpV/n4NWcch8oVLYSZ8M=; b=p0ZbSQAQx+gQM5DgwooN6aDrca8hob1jJloF5uCwEdp55O+Jny2ShB/NsQxRGkNRJS dZYUz1fY7C3aRFyLYMykp1RK1zWJRzGsxzoQZKmEoNamiAK7lq4zTiTrNNqMbh4UJ3cn 2hQ1FZKeVdefr2h7HODbukvQHnuDdey3J7mh5JbuBvXfvHjPIVjZC5zfAlX5bKRa4XOW bniWVJDHmHk0R2VUvbptJOijLiwzLQ4MKiItGZd3rBKatHCHvOsEQh9hmSaKA+9iwxwm U9Fv87XQD0fDvGu5mLGJ1YIUi78bHpyScTPKJgMyW6t5QMAjyJHXUWMDmVPHxutqSdoa h+4Q==
MIME-Version: 1.0
X-Received: by 10.112.98.66 with SMTP id eg2mr3243801lbb.36.1380832668388; Thu, 03 Oct 2013 13:37:48 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Thu, 3 Oct 2013 13:37:48 -0700 (PDT)
In-Reply-To: <524DCBA0.1090302@isdg.net>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net> <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com> <524DCBA0.1090302@isdg.net>
Date: Thu, 3 Oct 2013 16:37:48 -0400
X-Google-Sender-Auth: w6Sz6qPGys2S1FOZT7V5hpSb2XI
Message-ID: <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com>
Subject: Re: How to protect DKIM signatures: Moving ADSP to Historic, supporting DMARC instead
From: Barry Leiba <barryleiba@computer.org>
To: Hector Santos <hsantos@isdg.net>
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: Thu, 03 Oct 2013 20:52:52 -0000

To both Doug and Hector, and others who want to drift in this direction:

As I've said before, the question of moving ADSP to Historic is one
we're taking on its own, and is not connected to anything we do or
don't do with DMARC.  Bringing DMARC into the discussion is a
distraction, and, worse, makes it look like there's a tie-in.  There
is not.

So, please, let's not discuss DMARC as part of the "ADSP to Historic"
conversation.  The issue is purely one of whether ADSP can be shown to
have enough value to maintain it as a Proposed Standard, whether we're
not getting enough value from it, and whether there's harm resulting
from our recommending its use and seeing it poorly used.

Please, everyone: discussions of DMARC in relation to this topic are
out of scope.

Barry, Applications AD

From spencerdawkins.ietf@gmail.com  Thu Oct  3 14:41:22 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 54AEB21F856A; Thu,  3 Oct 2013 14:41:22 -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.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 pefpBjUzzTyB; Thu,  3 Oct 2013 14:41:16 -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 2C42511E80D1; Thu,  3 Oct 2013 14:39:52 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id l109so865627yhq.34 for <multiple recipients>; Thu, 03 Oct 2013 14:39:49 -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=HoKHPMjSpeW8QGtqJFA7k/t9NYb5HKh0ahUurcQ8n9Y=; b=pDZvSUFIp6DrfZnQbXr044Ics9LDyyn2VnN11lUJlBS8+PeBuos9n52SNZsplrxGkK Vmb2Hl8Rczpk38eRsoZ+YvdBTNQLLbsgooQfmtQArLJ2jLAp23VEx4AJ0+uwvnEhcrtc SecAUZI1esMZdJGKqWvVS4VLih52RbUjPQHkryxfzInqguPkjyI6u2b6nzzxPyesoxkY AlSDewY9X9wHVwtuRWN4DVK3AY9dcQxHhiPKisbo2lhSybNQeU98OSLsfXKGLhpGa1J5 r0P8mqLut4PD8uAYD4EISawZI5/xxu2qrXqNj0ACXH0ec5SxuenUfxwc1zTqbX5ozfva AAOg==
X-Received: by 10.236.44.42 with SMTP id m30mr8850299yhb.7.1380836388794; Thu, 03 Oct 2013 14:39:48 -0700 (PDT)
Received: from [192.168.0.23] (70-2-31-243.pools.spcsdns.net. [70.2.31.243]) by mx.google.com with ESMTPSA id g25sm13993793yhg.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 14:39:47 -0700 (PDT)
Message-ID: <524DE3CD.8010303@gmail.com>
Date: Thu, 03 Oct 2013 16:38:21 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Scott O Bradner <sob@sobco.com>
Subject: Re: [Tools-discuss] independant submissions that update standards track, and datatracker
References: <RT-Ticket-59697@www.ietf.org/rt> <12321.1380629642@sandelman.ca> <rt-3.6.5-5193-1380646584-794.59697-6-0@www.ietf.org/rt> <11884.1380652164@sandelman.ca> <CADnDZ8-R6b0PgWStLHBhGAf9d7TuLH5H10Oo-cj0sJcGDRAj=Q@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D584@EXMB01CMS.surrey.ac.uk> <CAC4RtVDOCBqK+D4bFPKFKkmxd=qEerJPBLKwSqNFfCS-bg1hSA@mail.gmail.com> <6037477B-9C2A-4F6C-B268-01D52D23B6C2@sobco.com>
In-Reply-To: <6037477B-9C2A-4F6C-B268-01D52D23B6C2@sobco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Oct 2013 21:41:22 -0000

On 10/2/2013 9:15 AM, Scott O Bradner wrote:
>   1 April RFCs excepted

Ah.

I'm sitting here banging my head on a desk thinking "I knew that" ... 
thanks, Scott!

Spencer

From rdroms.ietf@gmail.com  Thu Oct  3 15:10:01 2013
Return-Path: <rdroms.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 5A0B521F9248; Thu,  3 Oct 2013 15:10:01 -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 LE06FLcJGRZc; Thu,  3 Oct 2013 15:09:54 -0700 (PDT)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id A9E0821F918C; Thu,  3 Oct 2013 15:09:49 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id q4so2122173qcx.26 for <multiple recipients>; Thu, 03 Oct 2013 15:09:48 -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:from:subject:date:to; bh=gS5pasxw9YsxQK97WN1Gdc8ktOO2njrhWnM/b+GXclU=; b=s0vd7n8K20TREX5RYqMiLzvg20np0kLEW5lJmCItGspRcieEtDXuTacIhE/gIFn7gq bJfWoFvW4r79w3AgfJGZEGQUqQPMk8vUgGL9zsvvubdbuQa7GApByDRYvhnjvxgv1wEl Mr94SRVxyPqmK/4JjvP4A1eKnffYD39xDhdAqidbhoMBFz8XvyHsTeV7XW4JTCS0kyok DqobyjfCR7B6D6BdvPFLqEvoE5flS98KH4spPdIy6BYdjKtqOTX7HJVOiBk4GxRZIeJ3 bpcgh6hwrM9K4+0pvh8tkG4f8xd3115au3f51ztzDGgmF0xdwnj0VwJbg6ba4oOk+NdO 01rQ==
X-Received: by 10.224.22.202 with SMTP id o10mr4609550qab.117.1380838188204; Thu, 03 Oct 2013 15:09:48 -0700 (PDT)
Received: from [192.168.1.116] (c-24-62-108-202.hsd1.ma.comcast.net. [24.62.108.202]) by mx.google.com with ESMTPSA id 4sm18910336qak.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 15:09:47 -0700 (PDT)
References: <20131003154254.13078.69905.idtracker@ietfa.amsl.com> <72B4B7B0-2B15-4B64-AEC1-23B01F89AD71@isi.edu> <9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <EMEW3|db89e71161b3bb8f7117f7d83e2ef53ep92JhU03tjc|ecs.soton.ac.uk|9C2D0B1D-C493-41F5-B459-166098EAFC8D@ecs.soton.ac.uk> <D6ABF372-BAA8-4CCC-AFE7-41D480C2D28F@isi.edu> <201310031946.r93JkaUQ026289@bela.nlnetlabs.nl>
Mime-Version: 1.0 (1.0)
In-Reply-To: <201310031946.r93JkaUQ026289@bela.nlnetlabs.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <000F1B1E-93E6-432D-BC33-46D5E70B41E4@gmail.com>
X-Mailer: iPhone Mail (10B350)
From: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [mdnsext] WG Review: Extensions for Scalable DNS Service Discovery (dnssd)
Date: Thu, 3 Oct 2013 18:09:45 -0400
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Cc: "mdnsext@ietf.org mdnsext" <mdnsext@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "<ietf@ietf.org> Discussion" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, manning bill <bmanning@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, 03 Oct 2013 22:10:01 -0000

On Oct 3, 2013, at 3:46 PM, Jaap Akkerhuis <jaap@NLnetLabs.nl> wrote:

>=20
>    but the "To Subscribe" pointer is busted.
>=20
> According to <https://www.ietf.org/mailman/listinfo> the list is supposed
> to be <https://www.ietf.org/mailman/listinfo/mdnsext>.

mdnsext@ietf.org was used for the two BoFs.  The WG will be dnssd, and the m=
ailing list will be dnssd@ietf.org (which, I air, is not what is shown in th=
e charter header).

- Ralph

>=20
>    jaap
> _______________________________________________
> mdnsext mailing list
> mdnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/mdnsext

From hsantos@isdg.net  Thu Oct  3 15:23:17 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 0756821E8085 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 15:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.076
X-Spam-Level: 
X-Spam-Status: No, score=-102.076 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, J_CHICKENPOX_46=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 te1d4sTqhGtx for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 15:23:05 -0700 (PDT)
Received: from pop3.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A261821E8084 for <ietf@ietf.org>; Thu,  3 Oct 2013 15:22:36 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3176; t=1380838942; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=wqgjDsU77ELYjNS/sJMCnk+BmkM=; b=Nuc9GORJYFCejfEZNjsz LQYvUTreJxT6i5rbQBj7TscWQIeBCKsBiF9LHA9NjuZ/7kZr082jROsqv5xUKGWY vbxiUSVep6TlxUSx95bQflELY9gIsl5iJM7GGkP3VwDDimjWNu2AXm1TShfcADKr G66Lr58Uw0iH6TpJl6gP+Lg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 18:22:22 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3006448650.4443.4472; Thu, 03 Oct 2013 18:22:22 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3176; t=1380838556; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=LRNQ5r2 7QHB/vZcWcYeAcurCKHesrfFChkUmXPRJyOM=; b=NnjnFTSIlDv7eWGRrC8KhrW vxPS7hsg1vhmrtOKavAmsMLLJFuyDQ28z4xoJ3hs8VHauoWZKOQaUQ/pDbGQ6e0G 1+eF2bylCw2wuF7s3Hg9BayKxXIHWmWqzJ8xP8RhK5gfYoYhFKl5hkqFF3BQJGVd nWzejVYxXRDJR3Jp3yPA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 18:15:56 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2452837112.9.9124; Thu, 03 Oct 2013 18:15:55 -0400
Message-ID: <524DEE20.9000605@isdg.net>
Date: Thu, 03 Oct 2013 18:22:24 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: How to protect DKIM signatures: Moving ADSP to Historic, supporting DMARC instead
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net> <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com> <524DCBA0.1090302@isdg.net> <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com>
In-Reply-To: <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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, 03 Oct 2013 22:23:17 -0000

Please accept my apology as I do not mean to be disrespectful. I find 
it impossible to separate all design considerations that are involved 
in this decision you are requesting us to consider regarding a near 
7-8 years DKIM + POLICY investment.

DKIM originated with POLICY support built-in and it was a critical 
part of its marketing and selling point. It evolved from its 
predecessor Domainkeys with built-in policy support.  DKIM+POLICY was 
its technological advancement and attraction.  It made sense and it 
was elegant common sense design. It is why we supported DKIM.   It was 
then split as DKIM and SSP. SSP was relaxed and changed to ADSP.

Now you are asking us to just drop ADSP or in short, drop the basic 
idea of Domain Policy Layer support that sits on top of DKIM.

I don't think there was any question that the proof of concept is 
there. The implementators are there. The APIs have support.  The 
publishers are there.  Its value is high, so high Dave Crocker once 
stated "Its scary!" (check archives).  A strong deterministic protocol 
that allowed private domains to expose strong email policies and for 
receivers to honor and follow, immediately protecting domains from 
electronic mail spoofs.  A thing of beauty!

But the MAILING LIST SOFTWARE (MLS) needed to support it.

If this vote is a suggestion that MLS will not support ADSP, I am 
asking will it support DMARC because we will be repeating the same 7-8 
years integrated software design issue.

I will support a discussion of the entire AUTHOR DOMAIN POLICY 
protection layer for DKIM and finally determine if it will work or 
not, and if so, maybe some way that even the MLS developers will 
support -- the main barrier to this DKIM + POLICY problem.

If DMARC and MLS developers are expected to coexist without 
complaints, then the impact of deprecating ADSP will be less severe 
and the investment, time, energy and knowledge already learned will 
not be lost.

Why can't we just wait until at least DMARC is settled answering some 
of the same DKIM signature practice security questions surely to 
arise?   If its supported (which seems to far to be getting a higher 
mindset), then why can't ADSP be deprecated at that point, with DMARC 
making ADSP obsolete?

--
HLS

On 10/3/2013 4:37 PM, Barry Leiba wrote:
> To both Doug and Hector, and others who want to drift in this direction:
>
> As I've said before, the question of moving ADSP to Historic is one
> we're taking on its own, and is not connected to anything we do or
> don't do with DMARC.  Bringing DMARC into the discussion is a
> distraction, and, worse, makes it look like there's a tie-in.  There
> is not.
>
> So, please, let's not discuss DMARC as part of the "ADSP to Historic"
> conversation.  The issue is purely one of whether ADSP can be shown to
> have enough value to maintain it as a Proposed Standard, whether we're
> not getting enough value from it, and whether there's harm resulting
> from our recommending its use and seeing it poorly used.
>
> Please, everyone: discussions of DMARC in relation to this topic are
> out of scope.
>
> Barry, Applications AD
>
>

-- 
HLS



From doug.mtview@gmail.com  Thu Oct  3 15:26:39 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 88B6F21E8089 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 15:26: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=[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 JFIpE7SZo5uZ for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 15:26:30 -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 9701D21E809C for <ietf@ietf.org>; Thu,  3 Oct 2013 15:25:57 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz1so3228148pad.30 for <ietf@ietf.org>; Thu, 03 Oct 2013 15:25:57 -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; bh=4DJr+v8ZqxE9R2fyQ8eAypo9N2iTz0s2K4CJCFogET4=; b=lzrKQVyPEAqpyGoQeCtqPvk8NzngIIqBF4KAomSwxz3bx2Py9/6+RvYqVTjTafw/G3 MORhDQwFdSlZVmo/ER4o0FykBdLaDdieavNsRIv6T2EP+8QAczRMuGS0yGIYKhSRPrW/ AJJW8F23bIWZL4L1fZgtqultikmCvJG8KrOyooN5GBoIOmvYF4g5bZ7oyLnTOt8+adQz KAHXYAhH9JKj09QH8o8/b2IAJzTPrCnTuNTYRp1+1gdcb3wVm15er5AMExDFiFW77lfz 6NjlOnChe7Ll4VtMIurhFBxNd4679Qos6Q0UvGMEqxMaFfXdErWwqBss0YVhfIgS2RWB ysrA==
X-Received: by 10.66.25.133 with SMTP id c5mr11923049pag.4.1380839157410; Thu, 03 Oct 2013 15:25:57 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id aq1sm10492466pbc.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Oct 2013 15:25:55 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: How to protect DKIM signatures: Moving ADSP to Historic, supporting DMARC instead
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com>
Date: Thu, 3 Oct 2013 15:25:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8768A46-0C02-4884-87FE-78FFD4C6D3C8@gmail.com>
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net> <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com> <524DCBA0.1090302@isdg.net> <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1510)
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, 03 Oct 2013 22:26:39 -0000

On Oct 3, 2013, at 1:37 PM, Barry Leiba <barryleiba@computer.org> wrote:

> To both Doug and Hector, and others who want to drift in this =
direction:
>=20
> As I've said before, the question of moving ADSP to Historic is one
> we're taking on its own, and is not connected to anything we do or
> don't do with DMARC.  Bringing DMARC into the discussion is a
> distraction, and, worse, makes it look like there's a tie-in.  There
> is not.

Dear Berry,

Even John Levine the author had opine along these same lines.  The =
response to Hector was agreeing a reason should be given, along with =
agreeing with his justifications.  The tie-in may be limited, but =
nevertheless DMARC has become the chosen alternative.  It seems if any =
reasons are given for moving ADSP to historic it also should conjecture =
why DMARC and not ADSP, unless your point is nothing has been learned?

Regards,
Douglas Otis=

From superuser@gmail.com  Thu Oct  3 16:46:19 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 5FA5921F9228 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 16:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level: 
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260,  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 J1QS+sA4uzxV for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 16:46:12 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id B67A411E80FD for <ietf@ietf.org>; Thu,  3 Oct 2013 16:45:42 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id hj3so819496wib.1 for <ietf@ietf.org>; Thu, 03 Oct 2013 16:45: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=xlrAvODqJK8EgC0UVyduQ/PXt1316icx/DIdWZvQBsI=; b=JylTfZ6xK+C8ALCAmwuISvjR6O+y8dlv+j3vzdZqzfVZyXztvPVpP7uhe83dqUUKe3 cEm10/XaUNhNDPwvECgW0Pd0hUCGEfBYhC+SKWEGIHa3Nq0OLa3j+Gr5V82X8KoyUPyW iI//Mt06Hmme8OoKEEXEZClg3f+/DOMP8fQOLA7b/XBI7zd1AdgYs7HjTp5zXVa2Izko IQFnigR0CgRCvHOLyfth0BqvClz+sRGwNGkukxOhNKc3F7j4PBZwvUGw3aZcqkRPlltT 7yTRDFX/ZTt8BNETG/yxYcvkMXvfNSnm5V5tSLyB8T73MOvCbaWwqBL90CIqwXxAs/Gp byfg==
MIME-Version: 1.0
X-Received: by 10.194.77.167 with SMTP id t7mr9570128wjw.27.1380843941965; Thu, 03 Oct 2013 16:45:41 -0700 (PDT)
Received: by 10.180.18.202 with HTTP; Thu, 3 Oct 2013 16:45:41 -0700 (PDT)
In-Reply-To: <524D846A.6030905@tana.it>
References: <20131002145238.78084.qmail@joyce.lan> <524D846A.6030905@tana.it>
Date: Thu, 3 Oct 2013 16:45:41 -0700
Message-ID: <CAL0qLwZdWPdu5+B2V+EaiwbwqnD2+y6Fi_JtQ8EFj0FKC1ad_A@mail.gmail.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Historic
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary=047d7bf0d628a6b64504e7dec852
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, 03 Oct 2013 23:46:19 -0000

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

On Thu, Oct 3, 2013 at 7:51 AM, Alessandro Vesely <vesely@tana.it> wrote:

> I oppose to the change as proposed, and support the explanation called
> for by John Klensin instead.  Two arguments:
>
> 1)  The harm Barry exemplifies in the request --incompatibility with
>     mailing list posting-- is going to be a feature of at least one
>     of the other ways addressing that problem.  Indeed, "those who
>     don't know history are destined to repeat it", and the explanation
>     is needed to make history known.
>

Ample discussion of the problems exists in RFCs, most notably RFC 6377.  A
simple solution to your concern would be to modify the writeup to reference
what's written there.

John Klensin's proposal, however, is to write up and publish a short RFC
that makes the state change and possibly the "Historic" request, so that
the two things (status change and pointers to details) are in one, more
obvious, place.


>
> 2)  A possible fix for ADSP is explained by John Levine himself:
>     http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16969.html
>     I'm not proposing to mention it along with the explanation, but
>     fixing is not the same as moving to historic.  It seems that it
>     is just a part of RFC 5617, DNS records, that we want to move.
>
>
> To me, that post says ADSP is best implemented as a locally-configured
list of domains for which ADSP should be enforced.  That may be the better
solution, but then there's no protocol for the IETF to document, because
nothing is interoperating.  I don't believe this is an argument for
prolonging ADSP itself.

-MSK

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

<div dir=3D"ltr">On Thu, Oct 3, 2013 at 7:51 AM, Alessandro Vesely <span di=
r=3D"ltr">&lt;<a href=3D"mailto:vesely@tana.it" target=3D"_blank">vesely@ta=
na.it</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I oppose to the change as proposed, and supp=
ort the explanation called<br>
for by John Klensin instead. =A0Two arguments:<br>
<br>
1) =A0The harm Barry exemplifies in the request --incompatibility with<br>
=A0 =A0 mailing list posting-- is going to be a feature of at least one<br>
=A0 =A0 of the other ways addressing that problem. =A0Indeed, &quot;those w=
ho<br>
=A0 =A0 don&#39;t know history are destined to repeat it&quot;, and the exp=
lanation<br>
=A0 =A0 is needed to make history known.<br></blockquote><div><br></div><di=
v>Ample discussion of the problems exists in RFCs, most notably RFC 6377.=
=A0 A simple solution to your concern would be to modify the writeup to ref=
erence what&#39;s written there.<br>
<br></div><div>John Klensin&#39;s proposal, however, is to write up and pub=
lish a short RFC that makes the state change and possibly the &quot;Histori=
c&quot; request, so that the two things (status change and pointers to deta=
ils) are in one, more obvious, place.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
2) =A0A possible fix for ADSP is explained by John Levine himself:<br>
=A0 =A0 <a href=3D"http://www.mail-archive.com/ietf-dkim@mipassoc.org/msg16=
969.html" target=3D"_blank">http://www.mail-archive.com/ietf-dkim@mipassoc.=
org/msg16969.html</a><br>
=A0 =A0 I&#39;m not proposing to mention it along with the explanation, but=
<br>
=A0 =A0 fixing is not the same as moving to historic. =A0It seems that it<b=
r>
=A0 =A0 is just a part of RFC 5617, DNS records, that we want to move.<br>
<br><br></blockquote><div>To me, that post says ADSP is best implemented as=
 a locally-configured list of domains for which ADSP should be enforced.=A0=
 That may be the better solution, but then there&#39;s no protocol for the =
IETF to document, because nothing is interoperating.=A0 I don&#39;t believe=
 this is an argument for prolonging ADSP itself.<br>
<br>-MSK<br></div><div>=A0</div></div><br></div></div>

--047d7bf0d628a6b64504e7dec852--

From hsantos@isdg.net  Thu Oct  3 16:55:12 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 9EFD321F8F97 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 16:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.36
X-Spam-Level: 
X-Spam-Status: No, score=-102.36 tagged_above=-999 required=5 tests=[AWL=0.239, 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 9KtOcgmCxlZu for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 16:54:48 -0700 (PDT)
Received: from groups.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C9E3121E8082 for <ietf@ietf.org>; Thu,  3 Oct 2013 16:54:42 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4043; t=1380844474; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=hCu7jsje0il+qmISCfPSL3OocnA=; b=qPFThCtmVrbqLm4QRCvp QjBsyi8USqGBcHqpGKfGwJO0k8NHC652UfgkfzPB5p+xk5FzeYrz45MOUF8E4gh4 j/hMn+jI9GDBTdpEPY3+iAq8ROQeBzvniZmCmx4GcmWdjn3Xsekzk1ljk31WpK+C O3+bo7/wDfD6mK5a+5j8Wpg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 19:54:34 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3011978792.4443.3724; Thu, 03 Oct 2013 19:54:32 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4043; t=1380844087; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=hmASYUg +lDJRJzP4VNWPX/Fcvl+p/qGnlE/h+r92ZsM=; b=r1sRd28U8iz1dBglATRIi5Z Z/ZzGv+9fipluj07a8R+VO+vNWyplCAAoegYfMkR60MaxCO1jqaHW2SXEv5kqz+H AGAPpkXaqKed+jba2CrYqROX69QXYN3Jgp5PQwuZw2M5lNn0MVZ40pAhV+rT62wV ESbpcA+ABc6K6JseXTWY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 03 Oct 2013 19:48:07 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2458368222.9.4312; Thu, 03 Oct 2013 19:48:06 -0400
Message-ID: <524E03BB.4030607@isdg.net>
Date: Thu, 03 Oct 2013 19:54:35 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: How to protect DKIM signatures: Moving ADSP to Historic, supporting DMARC instead
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <CAL0qLwZQcXm=EauyKXVqGaUB99sTQgxf2csy0_N489TdfwRr4A@mail.gmail.com> <524D5ACF.3020008@isdg.net> <2F9821D3-C782-46FD-8AD6-B988CF0E6C55@gmail.com> <524DCBA0.1090302@isdg.net> <CAC4RtVCOtpUtziSOsa3N=vzKO3_gBHAm4UWhSQVgECdhc2zJcw@mail.gmail.com> <F8768A46-0C02-4884-87FE-78FFD4C6D3C8@gmail.com>
In-Reply-To: <F8768A46-0C02-4884-87FE-78FFD4C6D3C8@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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, 03 Oct 2013 23:55:13 -0000

On 10/3/2013 6:25 PM, Douglas Otis wrote:
>
> On Oct 3, 2013, at 1:37 PM, Barry Leiba <barryleiba@computer.org> wrote:
>
>> To both Doug and Hector, and others who want to drift in this direction:
>>
>> As I've said before, the question of moving ADSP to Historic is one
>> we're taking on its own, and is not connected to anything we do or
>> don't do with DMARC.  Bringing DMARC into the discussion is a
>> distraction, and, worse, makes it look like there's a tie-in.  There
>> is not.
>
> Dear Berry,
>
> Even John Levine the author had opine along these same lines.  The response to Hector was agreeing a reason should be given, along with agreeing with his justifications.  The tie-in may be limited, but nevertheless DMARC has become the chosen alternative.  It seems if any reasons are given for moving ADSP to historic it also should conjecture why DMARC and not ADSP, unless your point is nothing has been learned?
>

Doug, the whole problem was the middleware, the mailing list software 
or the 3rd party resigners who were either not supporting DKIM, 
ignorant of policy protocols and/or that did wish to have any 1st 
party domain controls dictating what mail can be resigned or not.

If DMARC is the "chosen alternative" we are still repeating the same 
related issues with this Author Domain Domain Policy Protocol as well. 
   The mailing list software needs to support this otherwise we still 
have the same problems as with ADSP.  In short, a subscriber to a list 
using a DOMAIN that is DMARC restrictive will also have a potential to 
cause automated unsubscribe events to members with DMARC compliant 
receivers supporting the DMARC restrictive policies.   Same thing as 
with ADSP, just change the protocol name.

Keep in mind that DMARC promises to offer better ADSP or as it 
documents "Super ADSP," in fact it outlines what seems to be the short 
comings of ADSP:

    http://tools.ietf.org/html/draft-kucherawy-dmarc-base-01#appendix-A.5

    A.5.  Issues With ADSP In Operation

    DMARC has been characterized as a "super-ADSP" of sorts.

    Contributors to DMARC have compiled a list of issues associated with
    ADSP, gained from operational experience, that have influenced the
    direction of DMARC:

    1.  ADSP has no support for subdomains, i.e., the ADSP record for
        example.com does not explicitly or implicitly apply to
        subdomain.example.com.  If wildcarding is not applied, then
        spammers can trivially bypass ADSP by sending from a subdomain
        with no ADSP record.

    2.  Non-existent subdomains are explicitly out of scope in ADSP.
        There is nothing in ADSP that states receivers should simply
        reject mail from NXDOMAINs regardless of ADSP policy (which of
        course allows spammers to trivially bypass ADSP by sending email
        from non-existent subdomains).

    3.  ADSP has no operational advice on when to look up the ADSP
        record.

    4.  ADSP has no support for using SPF as an auxiliary mechanism to
        DKIM.

    5.  ADSP has no support for a slow roll-out, i.e., no way to
        configure a percentage of email on which the receiver should
        apply the policy.  This is important for large-volume senders.

    6.  ADSP has no explicit support for an intermediate phase where the
        receiver quarantines (e.g., sends to the recipient's "spam"
        folder) rather than rejects the email.

    7.  The binding between the "From" header domain and DKIM is too
        tight for ADSP; they must match exactly.


We must consider that the requestor for the ADSP status change has 
also authored a DMARC "BCP:"

    Using DMARC
    http://tools.ietf.org/html/draft-crocker-dmarc-bcp-01

This draft only mentions ADSP once, and very briefly:

    10.  Interaction Issues

    Some issues come into play when DMARC is used in conjunction with one
    or more other services.

    o  Sender using both DMARC and ADSP


Ok, like what?

Lets try to get the issues straight. We are talking about dropping 
work that is already active in replace of some "super-ADSP" protocol.

Can we get it right please?


-- 
HLS



From dhc@dcrocker.net  Thu Oct  3 17:00:18 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 BD8BC21E8092 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 17:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.027
X-Spam-Level: 
X-Spam-Status: No, score=-6.027 tagged_above=-999 required=5 tests=[AWL=0.573,  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 GM-Y9Nmcd9z2 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 17:00:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 515CE21E8085 for <ietf@ietf.org>; Thu,  3 Oct 2013 17:00:05 -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 r93Nxvt2018947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Oct 2013 17:00:00 -0700
Message-ID: <524E04CA.1040608@dcrocker.net>
Date: Thu, 03 Oct 2013 16:59:06 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: Change the status of ADSP (RFC 5617) to Internet Standard
References: <20131002144143.20697.85830.idtracker@ietfa.amsl.com> <7102E82AB09013B67371807F@JcK-HP8200.jck.com> <524C5B77.9000002@dcrocker.net> <6D80EE3E9D28D2F9CB34E260@JcK-HP8200.jck.com>
In-Reply-To: <6D80EE3E9D28D2F9CB34E260@JcK-HP8200.jck.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]); Thu, 03 Oct 2013 17:00:00 -0700 (PDT)
Cc: Barry Leiba <barryleiba@computer.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: Fri, 04 Oct 2013 00:00:18 -0000

On 10/2/2013 11:46 AM, John C Klensin wrote:
> I assume we will need to agree to disagree about this, but...
>
> --On Wednesday, October 02, 2013 10:44 -0700 Dave Crocker
> <dhc@dcrocker.net> wrote:
>
>> If a spec is Historic, it is redundant to say not recommended.
>> As in, duh...
>
> "Duh" notwithstanding, we move documents to Historic for many
> reasons.

Sure.  And you seem to think that it's important to publish an RFC that 
documents the reasons.  You seem to think that it will somehow affect 
later handling of the historic document.

While an entirely reasonable theoretical premise, I'm not aware of its 
having any empirical basis.  Quite the opposite.

Further since your proposal constitutes additional work for someone, the 
benefit of doing it should be clear and compelling.  So far, what you've 
offered is neither.

In fact, the general view around the IETF is that the rest of the world 
deals with RFCs in a very coarse and inclusive manner, so that your 
proposal for fine-grained, formal documentation of rationales and the 
like constitutes mere noise to the rest of the world.


> The situation would be different if a huge amount of additional
> work were involved but it seems to me that almost all of the
> required explanation is already in the write-up and that the
> amount of effort required to approve an action consisting of a
> document and a status change is the same as that required to
> approve the status change only.

While it's laudable that you are volunteering to do this negligible 
extra work that will cause negligible amounts of additional delay, it 
still suffers the problem of producing negligible additional benefit.

If someone is all that interested in the reason the spec was moved to 
Historic, they can consult the IETF archives.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From narten@us.ibm.com  Thu Oct  3 21:53:37 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 E06C121F8F07 for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 21:53:37 -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 RxYZFfPhNGeQ for <ietf@ietfa.amsl.com>; Thu,  3 Oct 2013 21:53:25 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 460DA21F9767 for <ietf@ietf.org>; Thu,  3 Oct 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e8.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, 4 Oct 2013 00:53:06 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 4 Oct 2013 00:53:04 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id D80A46E803C for <ietf@ietf.org>; Fri,  4 Oct 2013 00:53:02 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp22035.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r944r3pN65339588 for <ietf@ietf.org>; Fri, 4 Oct 2013 04:53:03 GMT
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r944r3NA016084 for <ietf@ietf.org>; Fri, 4 Oct 2013 01:53:03 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r944r2ig016062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 4 Oct 2013 01:53:02 -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 r944r2HH024125 for <ietf@ietf.org>; Fri, 4 Oct 2013 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r944r2w4024027 for ietf@ietf.org; Fri, 4 Oct 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201310040453.r944r2w4024027@rotala.raleigh.ibm.com>
Date: Fri, 04 Oct 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: 13100404-0320-0000-0000-0000013D1F80
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Oct 2013 04:53:38 -0000

Total of messages in the last 7 days.
 
script run at: Fri Oct  4 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
--------+------+--------+----------+------------------------


From thierry.moreau@connotech.com  Fri Oct  4 05:47:24 2013
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BF521F9ED2 for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 05:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pWtF1Kb0FsWj for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 05:47:12 -0700 (PDT)
Received: from mail.connotech.com (connotech.com [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7157F21F9DAF for <ietf@ietf.org>; Fri,  4 Oct 2013 05:35:58 -0700 (PDT)
Received: from [192.168.1.200] (SUDOKU.CONNOTECH-INTERNAL.COM [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id DEB83318C1; Fri,  4 Oct 2013 08:33:37 -0400 (EDT)
Message-ID: <524EB619.6080900@connotech.com>
Date: Fri, 04 Oct 2013 08:35:37 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20090608)
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: NIST documents
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@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, 04 Oct 2013 12:47:24 -0000

Dearlove, Christopher (UK) wrote:
> One draft I'm working on [...]
> 
> (Of course I haven't been able to check the copyright on [NIST documents ...)
> 

As a author of IT-related documents, you should be aware that, by its 
constitution plus long lasting tradition, the US government "works of 
authorship" have no copyright claims on them. The principle being that 
"we, the people" paid for a civil servant to make a write-up, nobody can 
claim intellectual property. Maybe the openness of the Internet owes a 
lot to this tradition.

So, NIST documents can be used as if in the public domain.

Bizarrely, the RSA and early public key crypto patents were filed 
precisely because US government funding was involved, but that's part of 
a longer story.

Regards,

-- 
- Thierry Moreau

CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Montreal, QC, Canada H2M 2A1

Tel. +1-514-385-5691

From narten@us.ibm.com  Fri Oct  4 05:54:16 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 928D521F9BB1 for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 05:54:16 -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 tVTOiyizb6ZY for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 05:54:03 -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 7B5E321F9C0A for <ietf@ietf.org>; Fri,  4 Oct 2013 05:42:56 -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, 4 Oct 2013 08:42:55 -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, 4 Oct 2013 08:42:53 -0400
Received: from b01cxnp22033.gho.pok.ibm.com (b01cxnp22033.gho.pok.ibm.com [9.57.198.23]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 10F34C90041 for <ietf@ietf.org>; Fri,  4 Oct 2013 08:42:52 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22033.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r94Cgqrm49283102 for <ietf@ietf.org>; Fri, 4 Oct 2013 12:42:52 GMT
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 r94Cgp98030415 for <ietf@ietf.org>; Fri, 4 Oct 2013 08:42:51 -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 r94CgpLZ030380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 4 Oct 2013 08:42:51 -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 r94CgoVZ031877 for <ietf@ietf.org>; Fri, 4 Oct 2013 08:42:50 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r94CgonP031822 for ietf@ietf.org; Fri, 4 Oct 2013 08:42:50 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201310041242.r94CgonP031822@rotala.raleigh.ibm.com>
Date: Fri, 04 Oct 2013 08:42:50 -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: 13100412-7182-0000-0000-000008A1E371
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Oct 2013 12:54:16 -0000

Total of 79 messages in the last 7 days.
 
script run at: Fri Oct  4 08:42:50 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.86% |    7 |  9.36% |    66764 | hsantos@isdg.net
  3.80% |    3 |  9.16% |    65302 | david.black@emc.com
  6.33% |    5 |  4.74% |    33801 | john-ietf@jck.com
  5.06% |    4 |  5.48% |    39069 | adrian@olddog.co.uk
  3.80% |    3 |  4.65% |    33150 | kent@bbn.com
  5.06% |    4 |  3.37% |    24045 | barryleiba@computer.org
  3.80% |    3 |  4.42% |    31537 | sm+ietf@elandsys.com
  5.06% |    4 |  3.15% |    22491 | mcr@sandelman.ca
  3.80% |    3 |  4.01% |    28575 | superuser@gmail.com
  3.80% |    3 |  3.88% |    27640 | gonzalo.camarillo@ericsson.com
  3.80% |    3 |  2.98% |    21246 | rdroms.ietf@gmail.com
  2.53% |    2 |  4.17% |    29754 | bmanning@isi.edu
  3.80% |    3 |  2.46% |    17558 | sob@sobco.com
  1.27% |    1 |  4.21% |    30050 | tjc@ecs.soton.ac.uk
  2.53% |    2 |  2.92% |    20858 | abdussalambaryun@gmail.com
  2.53% |    2 |  2.29% |    16353 | doug.mtview@gmail.com
  2.53% |    2 |  2.07% |    14791 | chris.dearlove@baesystems.com
  2.53% |    2 |  1.92% |    13699 | ynir@checkpoint.com
  2.53% |    2 |  1.82% |    13001 | dhc@dcrocker.net
  2.53% |    2 |  1.80% |    12824 | ted.lemon@nominum.com
  2.53% |    2 |  1.78% |    12667 | alexandru.petrescu@gmail.com
  1.27% |    1 |  2.77% |    19748 | jdrake@juniper.net
  1.27% |    1 |  1.36% |     9707 | olaf@nlnetlabs.nl
  1.27% |    1 |  1.28% |     9155 | l.wood@surrey.ac.uk
  1.27% |    1 |  1.25% |     8881 | narten@us.ibm.com
  1.27% |    1 |  1.22% |     8667 | ben@nostrum.com
  1.27% |    1 |  1.21% |     8618 | huub.van.helvoort@huawei.com
  1.27% |    1 |  1.15% |     8225 | dave@cridland.net
  1.27% |    1 |  1.12% |     8023 | brian.e.carpenter@gmail.com
  1.27% |    1 |  1.00% |     7126 | joelja@bogus.com
  1.27% |    1 |  0.95% |     6809 | ietfdbh@comcast.net
  1.27% |    1 |  0.94% |     6715 | mcr+ietf@sandelman.ca
  1.27% |    1 |  0.93% |     6657 | scott@kitterman.com
  1.27% |    1 |  0.88% |     6245 | vesely@tana.it
  1.27% |    1 |  0.86% |     6150 | morrowc.lists@gmail.com
  1.27% |    1 |  0.85% |     6062 | johnl@taugh.com
  1.27% |    1 |  0.85% |     6059 | spencerdawkins.ietf@gmail.com
  1.27% |    1 |  0.73% |     5188 | jaap@nlnetlabs.nl
--------+------+--------+----------+------------------------
100.00% |   79 |100.00% |   713210 | Total


From steve@shinkuro.com  Fri Oct  4 07:47:36 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E344E21F9634 for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 07:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, 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 xKm22BoaFzWZ for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 07:47:24 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF2B21F967A for <ietf@ietf.org>; Fri,  4 Oct 2013 07:43:23 -0700 (PDT)
Received: from dummy.name; Fri, 04 Oct 2013 14:43:22 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: NIST documents
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <524EB619.6080900@connotech.com>
Date: Fri, 4 Oct 2013 10:43:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AC30EA2-0598-425E-9DEF-8C8E4398CC1C@shinkuro.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net> <524EB619.6080900@connotech.com>
To: Thierry Moreau <thierry.moreau@connotech.com>
X-Mailer: Apple Mail (2.1499)
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, 04 Oct 2013 14:47:36 -0000

In reference to

> Maybe the openness of the Internet owes a lot to this tradition.

let me offer a comment regarding the RFCs.  There might be a general =
connection, but there wasn't an explicit connection.  The decision that =
RFCs would be freely available and without restriction regarding use =
came primarily from me.  I was part of the team at UCLA, which together =
with our counterparts at SRI, UCSB and Utah developed the initial set of =
ideas about the Arpanet protocols.  When we started to write down our =
ideas, we wanted to remove all barriers for publication and use.  A =
participant from one of the institutions involved in the next round of =
connections, i.e., not one of the first four, expressed concern that his =
institution would require pre-publication review and approval, so we =
declared RFCs not to be "publications."

There was no directive from DARPA or anyone else in the government nor =
was there even discussion about this policy.  It was a pragmatic =
decision aimed at facilitating maximum communication with minimum =
overhead and minimum delay.  We implicitly assumed there would be formal =
processes for the "real" documents later, and, of course, the RFCs were =
just a temporary expedient intended to last just a few months=85

I suppose if the course we set had been antithetical to the U.S. =
Government's wishes, we might have gotten some guidance to do something =
different, but I don't recall the subject ever coming up.  We not only =
wanted the rules to be as unrestrictive as possible, we also wanted to =
spend as little time as possible discussing the rules.

Steve



On Oct 4, 2013, at 8:35 AM, Thierry Moreau =
<thierry.moreau@connotech.com> wrote:

> Dearlove, Christopher (UK) wrote:
>> One draft I'm working on [...]
>> (Of course I haven't been able to check the copyright on [NIST =
documents ...)
>=20
> As a author of IT-related documents, you should be aware that, by its =
constitution plus long lasting tradition, the US government "works of =
authorship" have no copyright claims on them. The principle being that =
"we, the people" paid for a civil servant to make a write-up, nobody can =
claim intellectual property. Maybe the openness of the Internet owes a =
lot to this tradition.
>=20
> So, NIST documents can be used as if in the public domain.
>=20
> Bizarrely, the RSA and early public key crypto patents were filed =
precisely because US government funding was involved, but that's part of =
a longer story.
>=20
> Regards,
>=20
> --=20
> - Thierry Moreau
>=20
> CONNOTECH Experts-conseils inc.
> 9130 Place de Montgolfier
> Montreal, QC, Canada H2M 2A1
>=20
> Tel. +1-514-385-5691


From nomcom-chair-2013@ietf.org  Fri Oct  4 10:31:50 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 1502421F9C12; Fri,  4 Oct 2013 10:31:50 -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 zbv-Ch22PiM8; Fri,  4 Oct 2013 10:31:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7589A21F9A2E; Fri,  4 Oct 2013 10:31:49 -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 - Second Call for Nominations - two weeks left
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131004173149.22991.14931.idtracker@ietfa.amsl.com>
Date: Fri, 04 Oct 2013 10:31:49 -0700
Cc: IETF Discuss List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: Nomcom@ietfa.amsl.com, Chair@ietfa.amsl.com, "2013 <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: Fri, 04 Oct 2013 17:31:50 -0000

Nominations for the IESG, IAB, and IAOC are due to the Nomcom by Friday, 18=
 October, 2013.

Is there someone you work with at IETF who has leadership potential and a g=
rowing track record? Please read the Nomcom call for nominations and consid=
er nominating her or him. Or several folks! Deadline for nominations is Oct=
ober 18.  Nominate soon to give your nominee(s) plenty time to fill in the =
questionnaire. Information about the desired expertise for positions is her=
e: =

           https://datatracker.ietf.org/nomcom/2013/expertise

Lots more, including which positions are open, how to make a nomination, an=
d how to =

send us your feedback on the desired expertise, follows.

IETFers, let's hear from you!  Make nominations, accept nominations!

If you have any questions about the process, feel free to get in touch with=
 me.

Best regards,

Allison for the Nomcom

Allison Mankin =

Nomcom Chair 2013-14

----- The Info You Need for Nominating -----

The 2013-14 Nominating Committee (Nomcom) is seeking nominations
from now until October 18, 2013. The open positions being considered
by this year's Nomcom can be found later in this section, and also on
this year's Nomcom website: =


https://datatracker.ietf.org/nomcom/2013/

Nominations may be made by selecting the Nominate link at the top of
the Nomcom 2013 home page, or by visiting the following URL: =


https://datatracker.ietf.org/nomcom/2013/nominate/

Note that nominations made using the web tool require an ietf.org =

datatracker account. You can create a datatracker ietf.org account =

if you don't have one already by visiting the following URL:

https://datatracker.ietf.org/accounts/create/

Nominations may also be made by email to nomcom13 at ietf.org.
If you nominate by email, please include the word "Nominate" in the Subject
and indicate in the email who is being nominated, their email address (to
confirm acceptance of the nomination), and the position for which you
are making the nomination. If you use email, please use a separate email for
each person you nominate, and for each position (if you are nominating one
person for multiple positions).

Self-nomination is welcome!  No need to be shy.

Nomcom 2013-14 will follow the policy for "Open Disclosure of Willing
Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of
nominees willing to be considered for positions under review in the
current Nomcom cycle is not confidential". Willing nominees for each
position will be listed in a publicly accessible way - anyone with a
datatracker account may access the lists.  In all other ways, the =

confidentiality requirements of RFC 3777/BCP10 remain in effect.  All
feedback and all Nomcom deliberations will remain confidential and will
not be disclosed.  =


In order to ensure time to collect sufficient community feedback about
each of the willing nominees, nominations must be received by the =

Nomcom on or before October 18, 2013.  Please submit your nominations  =

as early as possible for the sake of your nominees, as we've set the =

questionnaire submission deadline for October 25, 2013.

The list of people and posts whose terms end with the March 2014 IETF meeti=
ng, =

and thus the positions for which we are accepting nominations:  =


IAOC
Chris Griffiths

IAB
Bernard Aboba
Marc Blanchet
Ross Callon
Eliot Lear
Hannes Tschofenig

IESG
Barry Leiba (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
Martin Stiemerling (Transport)

Please be resourceful in identifying possible candidates for these
positions, as developing our talent is a very crucial requirement for
the IETF.  Also, please give serious consideration to accepting nominations
you receive.  =

 =

The summaries of the desired expertise for the positions, developed by the =

respective bodies, are found at:

https://datatracker.ietf.org/nomcom/2013/expertise/

In addition to nominations, the Nomcom seeks community input on =

the positions themselves.  We need and welcome the community's =

views and input on the jobs within each organization. If you =

have ideas on the positions' responsibilities (more, less, =

different), please let us know.  You can send us email about this to
nomcom13 at ietf.org, and we will use this feedback actively.

Thank you for your help in nominating a great pool of strong and interesting
nominees!




From daniel.karrenberg@ripe.net  Fri Oct  4 13:22:03 2013
Return-Path: <daniel.karrenberg@ripe.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 4583F21F9DD0 for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 13:22:03 -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 9MxLf5bDvXQh for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 13:21:57 -0700 (PDT)
Received: from kbg.karrenberg.net (kbg.karrenberg.net [88.198.84.162]) by ietfa.amsl.com (Postfix) with ESMTP id 3F10A21F9DDE for <ietf@ietf.org>; Fri,  4 Oct 2013 13:21:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by kbg.karrenberg.net (Postfix) with ESMTP id CB7F2981; Fri,  4 Oct 2013 20:21:43 +0000 (UTC)
Received: from kbg.karrenberg.net ([127.0.0.1]) by localhost (kbg.karrenberg.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZiglgCeENi9f; Fri,  4 Oct 2013 20:21:43 +0000 (UTC)
Received: from [10.71.1.25] (541C59C9.cm-5-5b.dynamic.ziggo.nl [84.28.89.201]) by kbg.karrenberg.net (Postfix) with ESMTPSA id C433B946; Fri,  4 Oct 2013 20:21:42 +0000 (UTC)
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net> <524EB619.6080900@connotech.com> <6AC30EA2-0598-425E-9DEF-8C8E4398CC1C@shinkuro.com>
In-Reply-To: <6AC30EA2-0598-425E-9DEF-8C8E4398CC1C@shinkuro.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <90A3B6BF-96F7-4EA3-BDCB-DCA2C529FE8C@ripe.net>
X-Mailer: iPad Mail (11A501)
From: Daniel Karrenberg <daniel.karrenberg@ripe.net>
Subject: Re: NIST documents
Date: Fri, 4 Oct 2013 22:21:43 +0200
To: Steve Crocker <steve@shinkuro.com>
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, 04 Oct 2013 20:22:03 -0000

----------
Sent from a hand held device.

> On 04.10.2013, at 16:43, Steve Crocker <steve@shinkuro.com> wrote:
> ...
> We not only wanted the rules to be as unrestrictive as possible, we also w=
anted to spend as little time as possible discussing the rules.

... and by doing so you (plural) made a very significant difference in our l=
ittle  Internet corner of the great scheme of things. I empathise withe the s=
iprit you evoke. I am grateful for what you (plural) did and  I hope we did h=
alf as well in the little corner across the pond. =20

Take care ( both proverbially and literally: "ICANN" eats people)=20

Daniel


From Fred.L.Templin@boeing.com  Fri Oct  4 13:41:56 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC37D21F9E00; Fri,  4 Oct 2013 13:41: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 0zJ-tqHw46a9; Fri,  4 Oct 2013 13:41:50 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 448B621F9E3A; Fri,  4 Oct 2013 13:41:39 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r94KfdPe026666; Fri, 4 Oct 2013 13:41:39 -0700
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r94Kfbbg026628 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 4 Oct 2013 13:41:38 -0700
Received: from XCH-BLV-406.nw.nos.boeing.com (130.247.25.162) by XCH-NWHT-08.nw.nos.boeing.com (130.247.25.112) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 4 Oct 2013 13:41:37 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-406.nw.nos.boeing.com ([169.254.6.110]) with mapi id 14.02.0328.011; Fri, 4 Oct 2013 13:41:36 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KmVHjrcZv7kkeUppI3Iq7lo5nk+jmg
Date: Fri, 4 Oct 2013 20:41:35 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
In-Reply-To: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Oct 2013 20:41:56 -0000

Hi, I have a concern about this document. In the definition of "IPv6
Header Chain", it says:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is considered to be an upper-layer header and terminates
   the header chain."

This means that stateless firewalls are being directed to discontinue
extension header parsing when a first encapsulated IPv6 header is
encountered - even though there may be many more parsable (inner)
headers that follow. As a result, the firewall would either have to
drop or forward the packet without examining the true upper layer
header. This may result in an incorrect perception that tunneled
traffic is either less reliable or more dangerous than non-tunneled
traffic.

Here are my suggested changes to address this issue:

1) Section 3, under "IPv6 Header Chain", change:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is considered to be an upper-layer header and terminates
   the header chain."

to:

  "However, if a second IPv6 header appears in the header chain, as
   is the case when IPv6 is tunneled over IPv6, the second IPv6
   header is optionally considered to be either an upper-layer header
   that terminates the header chain or another extension header that
   continues the chain."

2) Section 3, under "Upper-layer Header", change:

  "In the general case, the upper-layer header is the first member
   of the header chain that is neither an IPv6 header nor an IPv6
   extension header."

to:

  "In the general case, the upper-layer header is the first member
   of the header chain that is not considered to be an extension header."

3) Section 3, under "Upper-layer Header", delete the following sentence:

  "However, if either an ESP header, or a second IPv6 header occur in
   the header chain, they are considered to be upper layer headers and
   they terminate the header chain."

4) Section 5, change the final paragraph to:

  "As a result of the above mentioned requirements, a packet's header
   chain length cannot exceed the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821].  However, if a host does
   not discover the Path MTU, it MUST limit the header chain length to
   1024 bytes.  Limiting the header chain length to 1024 bytes ensures
   that the header chain length does not exceed the IPv6 minimum MTU
   [RFC2460] even if additional encapsulation headers are inserted by
   tunnels on the path."

Thanks - Fred
Fred.l.templin@boeing.com


=20

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: Wednesday, October 02, 2013 11:55 AM
> To: IETF-Announce
> Cc: ipv6@ietf.org
> Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
>=20
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Implications of Oversized IPv6 Header Chains'
>   <draft-ietf-6man-oversized-header-chain-08.txt> as Proposed Standard
>=20
> 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-10-16. 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.
>=20
> Abstract
>=20
>=20
>    The IPv6 specification allows IPv6 header chains of an arbitrary
>    size.  The specification also allows options which can in turn
> extend
>    each of the headers.  In those scenarios in which the IPv6 header
>    chain or options are unusually long and packets are fragmented, or
>    scenarios in which the fragment size is very small, the first
>    fragment of a packet may fail to include the entire IPv6 header
>    chain.  This document discusses the interoperability and security
>    problems of such traffic, and updates RFC 2460 such that the first
>    fragment of a packet is required to contain the entire IPv6 header
>    chain.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-chain/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> chain/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From gtw@gtwassociates.com  Fri Oct  4 15:30:12 2013
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C75321F9E00 for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 15:30:12 -0700 (PDT)
X-Quarantine-ID: <rr8DHRHLYYEu>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
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 rr8DHRHLYYEu for <ietf@ietfa.amsl.com>; Fri,  4 Oct 2013 15:30:07 -0700 (PDT)
Received: from s1.mail.rcig.net (s1.mail.rcig.net [216.87.38.201]) by ietfa.amsl.com (Postfix) with ESMTP id 249EB21F9A59 for <ietf@ietf.org>; Fri,  4 Oct 2013 15:30:06 -0700 (PDT)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:50718 helo=GTWPC) by s1.mail.rcig.net with esmtpa (Exim 4.72) (envelope-from <gtw@gtwassociates.com>) id 1VSDsp-0008TG-PC; Fri, 04 Oct 2013 17:30:06 -0500
Message-ID: <128CD0EA9DEE4DEF814B56BFF7516313@GTWPC>
From: "GTW" <gtw@gtwassociates.com>
To: "Thierry Moreau" <thierry.moreau@connotech.com>, "Dearlove, Christopher \(UK\)" <chris.dearlove@baesystems.com>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF54DE@GLKXM0002V.GREENLNK.net> <524EB619.6080900@connotech.com>
In-Reply-To: <524EB619.6080900@connotech.com>
Subject: Re: NIST documents
Date: Fri, 4 Oct 2013 18:29:56 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3505.912
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: GTW <gtw@gtwassociates.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, 04 Oct 2013 22:30:12 -0000

except see for example 
http://www.cendi.gov/publications/04-8copyright.html#317

3.1.7  Does the Government have copyright protection in U.S. Government 
works in other countries?

Yes, the copyright exclusion for works of the U.S. Government is not 
intended to have any impact on protection of these works abroad (S. REP. NO. 
473, 94th Cong., 2d Sess. 56 (1976)). Therefore, the U.S. Government may 
obtain protection in other countries depending on the treatment of 
government works by the national copyright law of the particular country. 
Copyright is sometimes asserted by U.S. Government agencies outside the 
United States.

best to be careful


George T. Willingmyre, P.E.
President GTW Associates


-----Original Message----- 
From: Thierry Moreau
Sent: Friday, October 04, 2013 8:35 AM
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: NIST documents

Dearlove, Christopher (UK) wrote:
> One draft I'm working on [...]
>
> (Of course I haven't been able to check the copyright on [NIST documents 
> ...)
>

As a author of IT-related documents, you should be aware that, by its
constitution plus long lasting tradition, the US government "works of
authorship" have no copyright claims on them. The principle being that
"we, the people" paid for a civil servant to make a write-up, nobody can
claim intellectual property. Maybe the openness of the Internet owes a
lot to this tradition.

So, NIST documents can be used as if in the public domain.

Bizarrely, the RSA and early public key crypto patents were filed
precisely because US government funding was involved, but that's part of
a longer story.

Regards,

-- 
- Thierry Moreau

CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Montreal, QC, Canada H2M 2A1

Tel. +1-514-385-5691 


From agenda@ietf.org  Fri Oct  4 15:53:50 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 87FE021F997D; Fri,  4 Oct 2013 15:53:50 -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 k-Gcq8PjrRlp; Fri,  4 Oct 2013 15:53:50 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A84821F9C81; Fri,  4 Oct 2013 15:53:46 -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 88 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131004225346.32223.38527.idtracker@ietfa.amsl.com>
Date: Fri, 04 Oct 2013 15:53:46 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 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: Fri, 04 Oct 2013 22:53:50 -0000

The IETF 88 Preliminary Agenda has been posted. The final agenda will be pu=
blished on Friday, October 11th.
 =

https://datatracker.ietf.org/meeting/88/agenda.html =

https://datatracker.ietf.org/meeting/88/agenda.txt =


We are still having some difficulty integrating the new agenda tool into th=
e datatracker and as a result some portions of the meeting agenda -- bevera=
ge and snack breaks, plenaries --  are not yet showing up on the html versi=
on. This will hopefully be resolved very soon.
 =

More information regarding IETF 88 in Vancouver, BC, Canada is located here=
: https://www.ietf.org/meeting/88/index.html =

 =

IETF Secretariat=20

From jari.arkko@piuha.net  Sun Oct  6 14:04:07 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 213D021F9D09 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:04:07 -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 HZ0yZaagunyb for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:04:03 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 613C821F855F for <ietf@ietf.org>; Sun,  6 Oct 2013 14:04:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3A58A2CC60; Mon,  7 Oct 2013 00:03:59 +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 R5NQwE8M98uA; Mon,  7 Oct 2013 00:03: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 AD5122CC48; Mon,  7 Oct 2013 00:03:57 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Last calling draft-resnick-on-consensus
Date: Mon, 7 Oct 2013 00:03:57 +0300
Message-Id: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
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)
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: Sun, 06 Oct 2013 21:04:07 -0000

The document talks about ways in which consensus processes can be =
successfully run in the IETF. After the last few rounds of versions, I =
believe this document is ready to move forward.=20

My goal is to publish it as an Informational RFC. It is an explanation =
of principles and how they can be applied to productively move IETF =
discussions forward. While there is no change to IETF processes or any =
presumption that guidance from this document must be followed, I have =
found the document very useful. It has been referred to numerous times =
in IETF and IESG discussions. Consensus is hard and many WG discussions =
have complex trade-offs and differing opinions. I believe having this =
document become an RFC would help us apply the useful principles even =
more widely than we are doing today. =20

The abstract says:

   The IETF has had a long tradition of doing its technical work through
   a consensus process, taking into account the different views among
   IETF participants and coming to (at least rough) consensus on
   technical matters.  In particular, the IETF is supposed not to be run
   by a "majority rule" philosophy.  This is why we engage in rituals
   like "humming" instead of voting.  However, more and more of our
   actions are now indistinguishable from voting, and quite often we are
   letting the majority win the day, without consideration of minority
   concerns.  This document is a collection of thoughts on what rough
   consensus is, how we have gotten away from it, and the things we can
   do in order to really achieve rough consensus.

      Note (to be removed before publication): This document is quite
      consciously being put forward as Informational.  It does not
      propose to change any IETF processes and is therefore not a BCP.
      It is simply a collection of principles, hopefully around which
      the IETF can come to (at least rough) consensus.

The draft can be obtained from =
http://tools.ietf.org/html/draft-resnick-on-consensus

You should see a last call announcement soon, and both me and Pete look =
forward to your feedback.

Jari


From melinda.shore@gmail.com  Sun Oct  6 14:14:36 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 EFF8F1F0EDB for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level: 
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[AWL=1.950,  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 ekw93ynsx6Fa for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:14:35 -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 D2AE01F0ED7 for <ietf@ietf.org>; Sun,  6 Oct 2013 14:14:34 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb1so6428141pad.37 for <ietf@ietf.org>; Sun, 06 Oct 2013 14:14: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=IQMZxNr7zONZaeCYRTmWqRC5R1CxNk1OiP1EfaBKvEQ=; b=iy389YcD5rVG4LvxpUdkGGLj26OBd0X+dsf7Mp29SmMV4a7H67BAU2nYN0n/yNnFo2 2RLSgNqgRI+3dBIh3h3MzU4gBSWNlLp7uh3O8CQr1ICsAwj07XQERmR8dv/ydDx4J2wy yrxOziJOhdXtlus5WhmszNzmArN49Ua4QFdHTVRXuYSAIu7y5/4kdv4kBkActRkFIBEh 1j4obhwuVoufLBz1e+zCaMU/arn0+8/bTf3l8hqiE6L9YcGSbmRiPtnMGc4TWNzYaapv Aj6dq82tMvyXzHaVJckAufUmorvn9juR30jsNCwgvjnkLl6UqNLWXAsIrMr/oSzZmUyZ +Syg==
X-Received: by 10.68.7.74 with SMTP id h10mr26847318pba.11.1381094074426; Sun, 06 Oct 2013 14:14:34 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id yh1sm28781070pbc.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 06 Oct 2013 14:14:33 -0700 (PDT)
Message-ID: <5251D2B6.3080301@gmail.com>
Date: Sun, 06 Oct 2013 13:14:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.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: Sun, 06 Oct 2013 21:14:36 -0000

On 10/6/13 1:03 PM, Jari Arkko wrote:
> My goal is to publish it as an Informational RFC. It is an
> explanation of principles and how they can be applied to productively
> move IETF discussions forward. While there is no change to IETF
> processes or any presumption that guidance from this document must be
> followed, I have found the document very useful. It has been referred
> to numerous times in IETF and IESG discussions. Consensus is hard and
> many WG discussions have complex trade-offs and differing opinions. I
> believe having this document become an RFC would help us apply the
> useful principles even more widely than we are doing today.

Glad to hear it - I think this is an enormously useful document.
I'm wondering if wg chair training at an upcoming meeting can't
be spent on it.  Vancouver's too soon, but what about London?

Melinda


From randy@psg.com  Sun Oct  6 14:30:44 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 1E25B11E8142 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.123
X-Spam-Level: 
X-Spam-Status: No, score=-2.123 tagged_above=-999 required=5 tests=[AWL=0.476,  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 lyu2FR5sljTe for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 14:30:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id B829211E8137 for <ietf@ietf.org>; Sun,  6 Oct 2013 14:30:43 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VSvuP-0004NE-7m; Sun, 06 Oct 2013 21:30:37 +0000
Date: Mon, 07 Oct 2013 06:30:35 +0900
Message-ID: <m2bo32f5ok.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last calling draft-resnick-on-consensus
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@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: Pete Resnick <presnick@qti.qualcomm.com>, 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, 06 Oct 2013 21:30:44 -0000

i have found it quite useful in venues other than the ietf.  go for it.

and thanks, pete.

randy

From dhc@dcrocker.net  Sun Oct  6 17:04: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 06A2B21E80F7 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.841
X-Spam-Level: 
X-Spam-Status: No, score=-4.841 tagged_above=-999 required=5 tests=[AWL=-0.842, BAYES_50=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 7qejF0WHdTU4 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:03:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0121A21E80F5 for <ietf@ietf.org>; Sun,  6 Oct 2013 17:03:57 -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 r9703rwQ012684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Oct 2013 17:03:56 -0700
Message-ID: <5251FA64.7020205@dcrocker.net>
Date: Sun, 06 Oct 2013 17:03:48 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Review of:   draft-resnick-on-consensus-05
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, 06 Oct 2013 17:03:57 -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: Mon, 07 Oct 2013 00:04:03 -0000

Review

Title:        On Consensus and Humming in the IETF
               draft-resnick-on-consensus-05

Reviewer:     D. Crocker
Reivew data:  6 Oct 2013


Summary:

      The draft discusses IETF processes for making group decisions, 
especially in the face of disagreement.  As the draft notes, the IETF 
has no formal membership, which makes strict voting impossible.  It also 
notes the engineering reasons that strict voting can be inappropriate. 
Hence the IETF uses the term "rough consensus" to describe it's approach 
to decisions.  The draft offers the view that this is term represents a 
group journey, rather than only a decision-making moment.  It also 
stresses the need for diligently dealing with objections, rather than 
merely developing an overwhelming numerical preference.

      In terms of philosophy and desirable practice, the draft discusses 
an extremely appealing model and generally explains its nature and 
practice well.  However the draft tends to confuse what is (or has been) 
with what should be.  This includes confusing the IETF's historical 
sense of what 'rough consensus' means, with what the draft suggests it 
mean. As a consequence, it sometimes merely explains what is preferred, 
rather than the problems with what is common practice.  (Sometimes.  At 
other times, it nicely makes its case.)  Also it sometimes does not lay 
out the context for its assertions.

      In effect, the draft is offering fundamental enhancements to 
existing IETF practice, rather than merely clarifying the ways things 
are "supposed to be".  By way of properly setting context, the draft 
should cite RFC 1603/3934, Working Group Guidelines and Procedures.  Its 
section 3.3 has text that describes long-standing community views on the 
meaning of rough consensus, which don't quite align with what the draft 
puts forward:

>                In general, the dominant view of the
>    working group shall prevail.  (However, it must be noted that
>    "dominance" is not to be determined on the basis of volume or
>    persistence, but rather a more general sense of agreement.) Consensus
>    can be determined by a show of hands, humming, or any other means on
>    which the WG agrees (by rough consensus, of course).  Note that 51%
>    of the working group does not qualify as "rough consensus" and 99% is
>    better than rough.  It is up to the Chair to determine if rough
>    consensus has been reached.

      The disparity between that document's text and what this draft 
describes should not be a problem for what the draft is recommending, 
but merely requires changing the explanatory tone of the draft and how 
it makes its case.

      On reflection, it's a bit odd that the draft hasn't already cited 
any formal IETF documentation on rough consensus and its use.

      The draft needs to distinguish historical practice from proposed 
enhancement.  It also needs to explicate things more clearly, as 
indicated in the detailed comments.  In some cases, discussion conflates 
two or more topics together and needs to separate them.

      The changes being suggested to the draft are substantial, but will 
not affect the essential points for which the draft is lobbying.



Detailed comments:

> Abstract
>
>    The IETF has had a long tradition of doing its technical work through
>    a consensus process, taking into account the different views among
>    IETF participants and coming to (at least rough) consensus on
>    technical matters.  In particular, the IETF is supposed not to be run
>    by a "majority rule" philosophy.  This is why we engage in rituals

    a "majority rule-> a "simple majority rule"

Majorities come in different forms or degrees and the fact that 'rough 
consensus' is often taken to mean 67% or 75%, as a rule of thumb can 
make this confusing.

 From what you've written, your basic point seems to be that 51% isn't 
enough; it's worth making that explicit.

However...


>    like "humming" instead of voting.  However, more and more of our
>    actions are now indistinguishable from voting, and quite often we are
>    letting the majority win the day, without consideration of minority

This is a more important sentence than what came before, IMO, but it 
doesn't have context.  What came before doesn't obviously have anything 
to do with paying attention to minority concerns.

If your above "majority rule" statement is meant to say that no 
mathematical majority of any degree is automatically sufficient -- which 
is what you've been stressing in our discussions and later in the 
document -- then you haven't made that point at all, yet.

For example, "voting" can be done with models that give quite a bit of 
power to minorities.  So, you need an explicit, direct, early statement 
that asserts the nature and importance of "rough consensus" factoring in 
minority views.


>    concerns.  This document is a collection of thoughts on what rough
>    consensus is, how we have gotten away from it, and the things we can
>    do in order to really achieve rough consensus.
...


> 1.  Introduction
>
>    Almost every IETF participant knows the aphorism from Dave Clark's
>    1992 plenary presentation [Clark] regarding how we make decisions in
>    the IETF:
>
>       We reject: kings, presidents and voting.
>
>       We believe in: rough consensus and running code.
>
>    That is, our credo is that we don't let a single individual make the

As the draft phrases it, that isn't really true.  We let individuals 
make decisions all the time.  What I believe the aphorism is saying -- 
and what reflects our community belief -- is:  We do not assign to any 
one individual the authority to /dictate/ a decision.  ("make" is too 
soft a word for this point, IMO.)


>    decisions, nor do we let the majority dictate decisions, nor do we

I believe the model being pursued in this draft -- of the nature and 
essential importance of properly dealing with minority views -- is 
hugely powerful and appropriate.  But I believe it has never been a 
prevalent view in the community, including back when the aphorism was 
seeking to summarize the community view.

The language I remember from the 90s primarily distinguished "strongly 
dominant majority" from 51% or 67% or 75%.  That is, it was about 
imprecise nature of the required clear and strong majority, rather than 
the moderating role of the minority.  Very occasionally -- but only 
occasionally -- we would use language that was along the lines of 
"strongly dominant view, with no vigorous and coherent opposition". That 
latter part probably should be seen as a crude version of what the draft 
is seeking to discuss, but I believe it was never consistently voiced or 
understood.

In other words, I think the role of minority views that the draft is 
putting forward is not a mere clarification and refinement to the 
existing IETF model, but rather is a significant enhancement.   So its 
premise about the potential importance of minority views does have some 
historical hooks in the IETF philosophy, but not as much as the draft 
seems to assert.


>    allow decisions to be made in a vacuum without practical experience.

Again, this statement goes beyond actual practice.  The language here 
prohibits decisions without experience and of course, the real IETF has 
always indulged in some decision-making based on theory that lacked 
practice.  We /prefer/ experience.  We /value/ the input it provides. 
But we are perfectly capable of making decision in a vacuum.


>    Instead, decisions are made by (more or less) consent of all

"Consent of all"?   Hell no.  Not even close, as your following text 
already note.


>    participants, and the actual products of engineering trump

Evidently, Pete hasn't been tracking the vigorous complaints about the 
SPF use of TXT records, arguing that such an offensive misuse of the DNS 
/must not/ be standardized, no matter how popular and integral the 
mechanism has become.  This represents a serious view that products 
absolutely do /not/ trump theoretical designs.  (Not surprisingly, I 
disagree with that view...)


>    theoretical designs.  Our ideal is full consensus, but we don't
>    require it: Full consensus would allow a single intransigent person

      Full consensus would allow
      ->
      Requiring full consensus gives each person a veto, by allowing

>
>
>
> Resnick                  Expires April 07, 2014                 [Page 2]
> 
> Internet-Draft                On Consensus                  October 2013
>
>
>    who simply keeps saying "No!" to stop the process cold.  We only
>    require rough consensus: If the chair of a working group determines

Again, this seems to conflate two points.  Both are extremely important. 
  Both need to be discussed.  But not intermixed.

One is that we do not require everyone to agree, as long as there is a 
strongly dominant group that do agree.

The other is that all concerns must be diligently considered, but do not 
have to be thoroughly resolved.  'Diligently considered' is an 
imposition on the entire group but it is mandatory.  'Not thoroughly 
resolved' is acceptable when the strongly dominant group agree that it 
is acceptable.


>    that a technical issue brought forward by an objector has been truly
>    considered by the working group, and the working group has made an
>    informed decision that the objection has been answered or is not
>    enough of a technical problem to prevent moving forward, the chair
>    can declare that there is rough consensus to go forward, the
>    objection notwithstanding.  To reinforce that we do not vote, we have

"To reinforce" switches from discussing the handling of minority 
concerns about voting.  At a minimum, break the paragraph.


>    also adopted the tradition of "humming": When (for example) the chair
>    of the working group wants to get a "sense of the room", instead of a
>    show of hands, the chair asks for each side to hum for or against a
>    question.

The draft has historically drawn a strong distinction between hands and 
hums.  It's an interesting distinction, and well might be useful, but I 
believe it has not been a universally-shared distinction in the 
community.  It essentially relies on a theoretical analysis of 
differences in psychological effects, but there's no objective basis for 
validating the one really is superior to the other.

In effect, the draft is asserting rationale and precision about audience 
measurement that haven't been present. Of course, there is an objective 
truth that humming does not permit counting, while hand-raising does. 
However humming has it's own psychologically biasing factors and they 
aren't trivial.

Now, perhaps the draft is seeking to lobby for use of humming, as 
preferred over hand-raising.  That's fine.  Cast it as such and argue 
for it.  It's relatively anonymous, it's a bit easier and quicker, it 
doesn't permit a false sense of measurement precision, ...


>    However, in recent years we have seen participants (and even some
>    folks in IETF leadership) who do not understand some of the
>    subtleties of consensus-based decision making.  Participants ask,
>    "Why are we bothering with this 'humming' thing?  Wouldn't a show of
>    hands be easier?  That way we could really see how many people want
>    one thing over another."  Chairs, many of whom have little experience
>    in leading large volunteer groups like those in the IETF, let alone
>    experience in how to gather consensus, are faced with factious
>    working groups with polarized viewpoints and long-running unresolved
>    issues that return again and again to the agenda.  More and more
>    frequently, people walk away from working groups, thinking that
>    "consensus" has created a document with horrible compromises to
>    satisfy everyone's pet peeve instead of doing "the right thing".
>    None of these things are indicators of a rough consensus process
>    being used, and are likely due to some basic misperceptions.

Is the issue their perception, or the fact that horrible compromises are 
actually being done?  From the text, I can't tell what point is intended.


>    This document attempts to explain some features of rough consensus,
>    explain what is not rough consensus, and suggest ways that we might
>    achieve rough consensus and judge it in the IETF.  Though this
>    document describes some behaviors of working groups and chairs, it
>    does so in broad brushstrokes and it is not intended to dictate

      it is not intended to dictate ->  it does not dictate


>    specific procedures.  It is intended to foster understanding of the
>    underlying principles of IETF consensus processes.
>
> 2.  Lack of disagreement is more important than agreement

The substance of this section has an important focus and makes useful 
comments.

However the title could be taken to cover such things as failure to gain 
affirmative support.  WGs often suffer from a lack of active involvement 
by more than a few participants.  In such cases, lack of disagreement is 
apathy, which is much worse than (active) agreement.


>    A working group comes to a technical question of whether to use
>    format A or format B for a particular data structure.  The chair
>    notices that a number of experienced people think format A is a good
>    choice.  The chair asks on the mailing, "Is everyone OK with format
>    A?"  Inevitably, a number of people object to format A for one or
>    another technical reason.  The chair then says, "It sounds like we
>    don't have consensus to use format A. Is everyone OK with format B?"
>    This time even more people object to format B, on different technical
>    grounds.  The chair, not having agreement on either format A or
>
>
>
> Resnick                  Expires April 07, 2014                 [Page 3]
> 
> Internet-Draft                On Consensus                  October 2013
>
>
>    format B, is left perplexed, thinking the working group has
>    deadlocked.
>
>    The problem that the chair got themselves into in the above case was
>    thinking that what they were searching for was agreement.  "After
>    all", thinks the chair, "consensus is a matter of getting everyone to
>    agree, so asking whether everyone agrees is what the chair ought to
>    do.  And if lots of people disagree, there's no consensus."  But
>    _determining_ consensus and _coming to_ consensus are different
>    things than _having_ consensus.  Consensus is not when everyone is

par break at start of sentence.  And possibly move this and the 
remaining sentences higher up, since they voice the essential point of 
the section.  In other words, try to start with the premise so that 
folks are oriented, and then explain it.


>    happy and agrees that the chosen solution is the best one.  Consensus
>    is when everyone is sufficiently satisfied with the chosen solution,
>    such that they no longer have specific objections to it.The
>    distinction might be a bit subtle, but it's important.    It is almost certain that any
>    time engineering choices need to be made, there will be options that
>    appeal to some people that are not appealing to some others.  The key
>    is to separate those choices that are simply unappealing from those
>    that are truly problematic.

Here's a suggestion for some re-casting to this separate paragraph, to 
help the reader bit, with the draft's logic and meaning:

      Engineering always involves a set of tradeoffs.  The process of 
gaining agreement about tradeoffs is the essence of a good rough 
consensus effort, and requires distinguishing the group debate and 
compromise needed to _come to_ consensus, the chair's process of 
_determining_ (or assessing) consensus, and the final point of the 
group's _having_ consensus on it choices.

...

>    However, there is another sense of "compromise" that involves
>    compromising between people, not engineering principles.  For
>    example, a minority of a group might object to a particular proposal,
>    and even after discussion still think the proposal is deeply
>    problematic, but decide that they don't have the energy to argue for
>    it and say, "Forget it, do what you want".  That surely can be called
>    a compromise, but a chair might mistakenly take this to mean that
>    they agree, and have therefore come to consensus.  But really all
>    that they've done is conceded; they've simply given up by trying to
>    appease the others.  That's not coming to consensus; there still
>    exists an outstanding unaddressed objection.  Even worse is the
>    "horse-trading" sort of compromise: "I object to your proposal for
>    such-and-so reasons.  You object to my proposal for this-and-that
>    reason.  Neither of us agree.  If you stop objecting to my proposal,
>    I'll stop objecting to your proposal and we'll put them both in."
>    That again results in an "agreement" of sorts, but it also results in
>    two outstanding unaddressed issues, again ignoring them for the sake
>    of expedience.  These sorts of "giving up" or "horse-trading"
>    compromises have no place in consensus decision making.  In each
>    case, a chair who looks for "agreement" might find it in these
>    examples because it appears that people have "agreed".  But again,
>    answering technical disagreements is what is needed to achieve
>    consensus, sometimes even when the people who stated the
>    disagreements no longer wish to discuss them.

This seems to argue that political compromise is never acceptable. 
That's not realistic.  Folks often can "live with" unresolved concerns. 
  The meta-issue is distinguishing disagreements about key points versus 
disagreement about minor ones.  Political compromise about a flat vs. 
hierarchical namespace is a rather different kettle of importance than 
between specifying a syntactic separator of comma vs. semicolon.  (No 
matter how much prettier I might think commas are, and superior for good 
visual presentation...)

The expedient of political compromise about more minor preferences is a 
huge benefit for making progress.  Compromising on major concerns, of 
course, is more likely to undermine utility or adoption.


>    Coming to consensus is when everyone comes to the conclusion that
>    either the objections are valid (and therefore making a change to
>    address the objection) or that the objection was not really a matter
>    of importance, but merely a matter of taste.  Of course, coming to
>    full consensus like that does not always happen.  That's why in the
>    IETF, we talk about "rough consensus".
>
> 3.  Rough consensus is achieved when all issues are addressed, but not
>     necessarily accommodated
...

>    So, an objector might say, "The proposal to go with protocol X is
>    much more complicated than going with protocol Y. Protocol Y is a
>    much more elegant and clean solution, which I can code much more
>    easily, and protocol X is a hack."  The working group might consider
>    this input, and someone might respond, "But we have a great deal of
>    code already written that is similar to protocol X. While I agree
>    that protocol Y is more elegant, the risks to interoperability with
>    an untested solution is not worth it compared to the advantages of
>    going with the well-understood protocol X." If the chair finds, in
>    their technical judgement, that the issue has truly been considered,
>    and that the vast majority of the working group has come to the
>    conclusion that the tradeoff is worth making, even in the face of
>    continued objection from the person(s) who raised the issue, the
>    chair can declare that the group has come to rough consensus.
>
>    Note that this portrays rough consensus as an "exception".  In one

I don't understand this first sentence.  How is it an exception?  Even 
with the following text, I don't see the basis for claiming that it 
might/would be seen as exceptional.


>    sense, it is: As a working group does its work and makes its choices,
>    it behaves as if it is striving toward full consensus and tries to
>    get all issues addressed to the satisfaction of everyone in the
>    group, even those who originally held objections.  It treats rough
>    consensus as a sort of "exception processing", to deal with cases
>    where the person objecting still feels strongly that their objection
>    is valid and must be accommodated.  But it is certainly true that
>    more often than not in the IETF, at least someone in the group will
>    be unsatisfied with a particular decision.  In that sense, rough
>    consensus might be closer to the norm than the "exception".  However,
>    when a participant says, "That's not my favorite solution, but I can
>    live with it; I'm satisfied that we've made a reasonable choice",
>    that participant is not in the "rough" part of a rough consensus; the
>    group actually reached consensus if that person is satisfied with the
>    outcome.  It's when the chair has to declare that an unsatisfied
>    person still has an open issue, but that the group has truly answered
>    the objection, that the consensus is only rough.
...


>    Now, a conclusion of having only rough consensus relies heavily on
>    the good judgement of the consensus caller.  The group must truly
>    consider and weigh an issue before the objection can be dismissed as
>    being "in the rough".  The chair of the working group in one of these

In spite of being appealing to use here, I think that the phrase "in the 
rough" is actually distracting, and possibly inappropriate:

      http://idioms.thefreedictionary.com/in+the+rough

      google:

         1. in a natural state; without decoration or other treatment.
            "a diamond in the rough"

         2. in difficulties. "even before the recession hit, the project
            was in the rough"


>    cases is going to have to decide that not only has the working group
>    taken the objection seriously, but that it has fully examined the
>    ramifications of not making a change to accommodate it, and that the
>    outcome does constitute a failure to meet the technical requirements
>    of the work.  In order to do this, the chair will need to have a good
>    idea of the purpose and architecture of the work being done and use
>    their own technical judgement to make sure that the solution meets
>    those requirements.  What can't happen is that the chair bases their
>    decision solely on hearing a large number of voices simply saying,
>    "The objection isn't valid."  That would simply be to take a vote.  A
>    valid justification needs to me made.

This begs the question of who determines that a justification is valid. 
  I'll suggest that it mostly should be the working group, with the 
chair as fall-back or safety valve, but not default.

By the way, the draft seems to think that it's always the chair who 
leads discussion and debate; it often/mostly isn't.  Rather it's 
typically the authors/editors, with a chair serving to moderate impasses.


>    Any finding of rough consensus needs, at some level, to provide a
>    reasoned explanation to the person(s) raising the issue of why their
>    concern is not going to be accommodated.  A good outcome is for the
>    objector to understand the decision taken and accept the outcome,
>    even though their particular issue is not being accommodated in the
>    final product.  Remember, if the objector feels that the issue is so

par break at Remember.


>    essential that it must be attended to, they always have the option to
>    file an appeal.  A technical error is always a valid basis for an
>    appeal.  The chair (or whoever is responsible to hear an appeal) may
>    determine that the issue was addressed and understood, but they also
>    have the freedom and the responsibility to say, "The group did not
>    take this technical issue into proper account" when appropriate.
>    Simply having a large majority of people agreeing to dismiss an
>    objection is not enough to claim there is rough consensus; the group
>    must have honestly considered the objection and evaluated that other
>    issues weighed sufficiently against it.  Failure to do that reasoning
>    and evaluating means that there is no true consensus.
>
> 4.  Humming should be the start of a conversation, not the end
...


>    So, why do we hum?  The first reason is pragmatic.  Quite often, a
>    chair is faced with a room full of people who seem to be
>    diametrically opposed on some choice facing the group.  In order to
>    find a starting place for the conversation, it is often useful for
>    the chair to ask for a hum to see if one of the choices already has a
>    stronger base of support than the other.  If choice "foo" has a
>    significant amount more support than choice "bar", it is likely
>    easier to start the discussion by saying, "OK, 'foo' seems to have
>    quite a bit of support.  Let's have the people that think 'foo' is a
>    bad idea come up and tell us why it is problematic."  At that point,

This section reads nicely and sounds quite good and very possibly might 
be something that we /should/ do.  However it has little to do with 
common IETF practice.  The simple reality is that hums are almost only 
used for indicating whether the group has a 'strongly dominant' 
preference.  Currently, it is rarely used as a means of deciding who to 
ask for objections.  Should we form a wg? Will folk work on the spec? Do 
folks prefer alternative A?  Is mechanism X workable here?

Even better is that I think the draft has buried it's more important 
point, namely that the /form of the question/ asked when seeking a hum 
is the really hard part of the effort, and the most important part. 
Some forms invite constructive discussion and some close it off.  Some 
are fair and balanced (...) and some are highly biasing.


>    the group can start going through the issues and see if any of them
>    are showstoppers.  It may turn out that one of the objections is
>    instantly recognized by the entire group as a fatal flaw in "foo" and
>    the group will then turn to a discussion of the merits (and demerits)
>    of "bar" instead.  All that the hum does is give the chair a starting
>    point: There were likely to be less objections to "foo" than to "bar"
>    at the beginning of the discussion, so starting with whatever got the
>    most hums can shorten the discussion.
...

>    But couldn't the above could have been done with a show of hands

This paragraph goes back to the hum-vs-hand methodology issue.  It's 
important, but it's out of place here, since this section is about the 
/role/ of a hum, not its method.  Discuss methodology separately, 
possibly up where it is first introduced.


>    instead of a hum?  Sure, but there are more formal reasons for using
>    a hum instead of a show of hands: Another reason we hum is because it
>    actually gives the chair the opportunity to take the temperature of
>    the room.  A smaller bunch of loud hums for choice A and a larger
>    number of non-committal hums for choice B might indicate that some
>    people believe that there are serious problems with choice B, albeit
>    the more popular by sheer number of people.  The chair might decide
>    that starting with choice A and getting objections to it is the
>    easier path forward and more likely to result in consensus in the
>    end.  Remember, coming to consensus is a matter of eliminating
>    disagreements, so the chair wants to choose the path that gets to the
>    least objections fastest.  A bunch of people who are not strongly

"the chair wants to choose the path that gets to the least objections 
fastest" sounds like an extremely appealing expedient, by virtue of 
being almost mechanical, but numbers often don't matter.  A single 
objection that observes (and substantiates) that a choice will not or 
cannot be used in the real world will outweigh a much larger number of 
trivial objections.


Perhaps merely qualifying the statement a bit will suffice:  the chair 
wants to choose the path that gets to the least number of significant 
objections fastest".  Hmmm.


>    committed to B might have no real technical objection to A, even
>    though it is not their first preference.  There is always a chance
>    that this could be misleading, because some people are more willing
>    to hum loudly than others (just by dint of personality), but keep in
>    mind that taking the hum is to figure out how to start the
>    conversation.  The chair could always be surprised because the hum
>    turns out to be unanimous.  Otherwise, the hum begins the discussion,
>    it doesn't end it.
>
>    Of course, a chair could get the temperature of the room by doing a
>    show of hands too, and knowing who specifically feels one way or
>    another can help a good chair guide the subsequent conversation.

And possibly place the minority under group pressure.


...

>    This also points to another misuse of the hum: If the chair is
>    already convinced that the group has come to consensus, there is no
>    reason to take a hum.  In fact, taking the hum only serves to
>    discourage those who might be in the minority from voicing their
>    concerns to the group in the face of a large majority who want to
>    move forward.  The right thing for the chair to do if they already
>    sense consensus is to say, "It sounds to me like we have consensus
>    for choice A. Does anybody have any concerns or objections to going
>    with A?"  This allows folks to bring up issues to the group that the
>    chair might have mistakenly missed without having them feel that the
>    majority has "already spoken".

+1


...

>
> 5.  Consensus is the path, not the destination
...

>    We often hear chairs say that they are making a "consensus call".
>    Sometimes, they simply mean they are making a call _of_ the
>    consensus; that is, they are declaring the consensus that has, in
>    their view, been reached when the discussion has reached an end.
>    That's a fine thing and what chairs are supposed to do: They are
>    "calling" the consensus.  Sometimes, when a chair says that they are

Might be worth tossing in the word "confirm" or "confirming existing 
consensus" here, to leave no doubt about what "calling" means.


...


>
> 6.  One hundred people for and five people against might not be rough
>     consensus
...

>
>    So in a large working group with over 100 active participants and
>    broad agreement to go forward with a particular protocol, if a few
>    participants say, "This protocol is going to cause congestion on the
>    network, and it has no mechanism to back off when congestion occurs;
>    we object to going forward without such a mechanism in place", and
>    the objection is met with silence on the mailing list, there is no

The problem here is who is the authority to determine that the objection 
needs to hold sway.  It's easy to lay this on the chair, but that makes 
the mechanisms fragile; it's too easy for one person to get this sort of 
thing wrong.


>    consensus.  Even if the working group chair makes a working group
>    last call on the document, and 100 people actively reply and say,
>    "This document is ready to go forward", if the open issue hasn't been
>    addressed, there's still no consensus.  It's the existence of the
>    unaddressed open issue, not the number of people, which is
>    determinative in judging consensus.  As discussed earlier, you can
>    have rough consensus with issues that have been purposely dismissed,
>    but not ones that have been ignored.
...


>
> 7.  Five people for and one hundred people against might still be rough
>     consensus
...


>    Now the worst case scenario happens.  The objector, still unhappy
>    that their preferred solution was not chosen, recruits one hundred
>    people, maybe a few who were silent participants in the working group
>    already, but mostly people who work at the same company as the
>    objector who never participated before.  The objector gets them all
>    to post a message to the list saying, "I believe we should go with
>    the new elegant algorithm in section Z instead of the current one.
>    It is more elegant, and works better on our hardware."  The chair
>    sees these dozens of messages coming in and posts a query to each of
>    them: "We discussed this on the list, and we seemed to have consensus
>    that, given the inherent risk of a new algorithm, and the widespread
>    deployment of this current one, it's better to stick with the current
>    one.  Do you have further information that indicates something
>    different?"  And in reply the chair gets utter silence.  These
>    posters to the list (say some of whom were from the company sales and
>    marketing department) thought that they were simply voting and have
>    no answer to give.  At that point, it is within bounds for the chair
>    to say, "We have objections, but the objections have been
>    sufficiently answered, and the objectors seem uninterested in
>    participating in the discussion.  Albeit rough in the extreme, there
>    is rough consensus to go with the current solution."

There's an interesting methodological point buried quite deep in this 
example, and probably worth surfacing sooner and more directly:

      Besides being careful about how the question for a consensus check 
is phrased, it is sometimes advisable to seek to discover what the 
responses mean.

In the example here, the question is whether those responding were 
sufficiently well-informed to be able to justify their position.


>    There is no doubt that this is the degenerate case and a clear
>    indication of something pathological.  But this is precisely what
>    rough consensus is designed to guard against: vote stuffing.  In the

Sorry, no.  It's not 'designed' for that at all, at least not in typical 
practice in the IETF.  It probably /should/ be, and the draft does a 
pretty good job of explaining how it /can/ be, but there is nothing in 
the "design" of the IETF's consensus process that has a history of 
mitigating against the problem the draft discusses here, and the problem 
isn't mentioned in formal IETF documents.


>    presence of an objection, the chair can use their technical judgement
>    to decide that the objection has been answered by the group and that
>    rough consensus overrides the objection.  Now, the case described
>    here is probably the hardest call for the chair to make (how many of
>    us are willing to make the call that the vast majority of people in
>    the room are simply stonewalling, not trying to come to consensus?),
>    and if appealed it would be incredibly difficult for the appeals body
>    to sort out.  Indeed, it is likely that if a working group got this
>    dysfunctional, it would put the whole concept of coming to rough
>    consensus at risk.  But still, the correct outcome in this case is to
>    look at the very weak signal against the huge background noise in
>    order to find the rough consensus.



d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Sun Oct  6 17:07:02 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 BC47821E80FE for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:06: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, 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 7swgixykyxOC for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:06:44 -0700 (PDT)
Received: from mail-ea0-x233.google.com (mail-ea0-x233.google.com [IPv6:2a00:1450:4013:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC1B21E80F2 for <ietf@ietf.org>; Sun,  6 Oct 2013 17:06:42 -0700 (PDT)
Received: by mail-ea0-f179.google.com with SMTP id b10so2793952eae.24 for <ietf@ietf.org>; Sun, 06 Oct 2013 17:06:41 -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=gW9uFYgHiUc3opTte2eKfHz0/UmQUtG9OM5vtERLpuo=; b=OIowgPTaTuzJt3RSbLXyTtjvSyNsMm/smfz3nQDfN5F1iSn4tRe2az2JeNqn+QiAlA Yk87y0cTN4hjO60ncPZVZIYatALJtgkQpNhFg8XsSFjLr9MRoluXTyp63iP05hZ2uKLm udpXsRYxLYMUY5ZXvg1n9MK60Im0rsxwUv/qUb4Rm38CZBQvPjA1+JM+gtJgYLsMzp2S 70hZCVcmIGTyqGxs0biz4/8AlqT//gx+Dtjx8Xty/pkJSTN2pgWkb4Wy+NvN579yw/kw x7evWvabQXSRBoqeL6y+AKYv1Xm/0feSBqTr4p07/5VmFNHwbPF4NSVeBasLZIoPk5sK reIw==
MIME-Version: 1.0
X-Received: by 10.14.8.72 with SMTP id 48mr44442320eeq.25.1381104401452; Sun, 06 Oct 2013 17:06:41 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Sun, 6 Oct 2013 17:06:41 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Sun, 6 Oct 2013 17:06:41 -0700 (PDT)
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
Date: Sun, 6 Oct 2013 20:06:41 -0400
Message-ID: <CAPv4CP-f0+hrw_VcRTFNkRFopCchcQVqTATeZ+dyYEM011WH=A@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Scott Brim <scott.brim@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11c1b9743f359f04e81b6d54
Cc: Pete Resnick <presnick@qti.qualcomm.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, 07 Oct 2013 00:07:06 -0000

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

+1. I've referred people to earlier versions already.

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

<p dir=3D"ltr">+1. I&#39;ve referred people to earlier versions already.=A0=
 </p>

--001a11c1b9743f359f04e81b6d54--

From mnot@mnot.net  Sun Oct  6 17:31:08 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 6F6C721E8105 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.493
X-Spam-Level: 
X-Spam-Status: No, score=-103.493 tagged_above=-999 required=5 tests=[AWL=-0.894, 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 f6kLBZgGa++o for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:31:04 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 0056521E80FE for <ietf@ietf.org>; Sun,  6 Oct 2013 17:31:03 -0700 (PDT)
Received: from [192.168.1.64] (unknown [118.209.193.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1538522E1FA; Sun,  6 Oct 2013 20:30:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
Date: Mon, 7 Oct 2013 11:30:52 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1510)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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: Mon, 07 Oct 2013 00:31:08 -0000

This is a VERY useful document, and I look forward to compelling my WG =
participants to read it, with a pop quiz afterwards.

The only issue I see is its length; while dedicated IETFers won't have a =
problem reading such a lengthy document, the people who could benefit =
most - new, potential or casual participants - will give up early, I =
fear.

Could we have someone take an editorial knife to it? Some of the =
descriptions of situations are quite long, and there's a fair amount of =
repetition in the document. Some of the paragraphs are quite long as =
well. I reckon 2-4 pages could be saved, making it appealing to a much =
wider audience.

Beyond that, the only suggestion I'd make is an alternate title -- "Why =
We Hum." Or maybe "The Things We Hum And Do Not Say" (apologies to Jerry =
Maguire).

Cheers,




On 07/10/2013, at 8:03 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> The document talks about ways in which consensus processes can be =
successfully run in the IETF. After the last few rounds of versions, I =
believe this document is ready to move forward.=20
>=20
> My goal is to publish it as an Informational RFC. It is an explanation =
of principles and how they can be applied to productively move IETF =
discussions forward. While there is no change to IETF processes or any =
presumption that guidance from this document must be followed, I have =
found the document very useful. It has been referred to numerous times =
in IETF and IESG discussions. Consensus is hard and many WG discussions =
have complex trade-offs and differing opinions. I believe having this =
document become an RFC would help us apply the useful principles even =
more widely than we are doing today. =20
>=20
> The abstract says:
>=20
>   The IETF has had a long tradition of doing its technical work =
through
>   a consensus process, taking into account the different views among
>   IETF participants and coming to (at least rough) consensus on
>   technical matters.  In particular, the IETF is supposed not to be =
run
>   by a "majority rule" philosophy.  This is why we engage in rituals
>   like "humming" instead of voting.  However, more and more of our
>   actions are now indistinguishable from voting, and quite often we =
are
>   letting the majority win the day, without consideration of minority
>   concerns.  This document is a collection of thoughts on what rough
>   consensus is, how we have gotten away from it, and the things we can
>   do in order to really achieve rough consensus.
>=20
>      Note (to be removed before publication): This document is quite
>      consciously being put forward as Informational.  It does not
>      propose to change any IETF processes and is therefore not a BCP.
>      It is simply a collection of principles, hopefully around which
>      the IETF can come to (at least rough) consensus.
>=20
> The draft can be obtained from =
http://tools.ietf.org/html/draft-resnick-on-consensus
>=20
> You should see a last call announcement soon, and both me and Pete =
look forward to your feedback.
>=20
> Jari
>=20

--
Mark Nottingham   http://www.mnot.net/




From mnot@mnot.net  Sun Oct  6 17:35:13 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 4366921E80FE for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.365
X-Spam-Level: 
X-Spam-Status: No, score=-103.365 tagged_above=-999 required=5 tests=[AWL=-0.766, 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 cB-4XyUaMIaV for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:35:08 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id E746B21E80FB for <ietf@ietf.org>; Sun,  6 Oct 2013 17:35:03 -0700 (PDT)
Received: from [192.168.1.64] (unknown [118.209.193.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4DB9E22E1F3; Sun,  6 Oct 2013 20:35:00 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Review of:   draft-resnick-on-consensus-05
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5251FA64.7020205@dcrocker.net>
Date: Mon, 7 Oct 2013 11:34:57 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F36C6D3-0173-4373-A72B-6E34489AD9A9@mnot.net>
References: <5251FA64.7020205@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
Cc: Pete Resnick <presnick@qti.qualcomm.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, 07 Oct 2013 00:35:13 -0000

On 07/10/2013, at 11:03 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>>   Now, a conclusion of having only rough consensus relies heavily on
>>   the good judgement of the consensus caller.  The group must truly
>>   consider and weigh an issue before the objection can be dismissed =
as
>>   being "in the rough".  The chair of the working group in one of =
these
>=20
> In spite of being appealing to use here, I think that the phrase "in =
the rough" is actually distracting, and possibly inappropriate:
>=20
>     http://idioms.thefreedictionary.com/in+the+rough
>=20
>     google:
>=20
>        1. in a natural state; without decoration or other treatment.
>           "a diamond in the rough"
>=20
>        2. in difficulties. "even before the recession hit, the project
>           was in the rough"

I think he's using it in the sense that it's used on a golf course...

Cheers,


--
Mark Nottingham   http://www.mnot.net/




From melinda.shore@gmail.com  Sun Oct  6 17:46:53 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 E50AE21E80FB for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level: 
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[AWL=0.975,  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 DJCLt9aFkC1q for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 17:46:53 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id C975721E8106 for <ietf@ietf.org>; Sun,  6 Oct 2013 17:46:52 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so6584878pab.12 for <ietf@ietf.org>; Sun, 06 Oct 2013 17:46:52 -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=8AooHK8hLcrfJD1QvJQ/pAx1tfrp2Cvb3Jid8RKbi0Q=; b=v13QtTNxDKoJI7PgCCCnZgxgdjg56tq/6vMuPh8h7+wB1Cbr3EeI8iv2Br/sh9v44l JdkzVw1qvTTrkNISTFEliAaZ76Lsr5njgQX7qndAFq6JGpOlAw0GLfDGwVMZuER9ajUY RFtQtdDOl249xtzh0D7W5qdj5rJV7Kn5rxOZzJa2BWOvykujLmPchLdvthui5Y5ZwPB2 c9hxbdMBYzq22tXKTIF8hLhjyW74kQx/on/QrEcySnJWsp5L7oWRVicrZWxrgPjk3bad kRmfU86Z4t0rnSRWm3I+DIBjYSYxelqSAZl2iaV710Agu1wuTloCVqW2RF6c2Z2FsLOW IEHQ==
X-Received: by 10.68.4.232 with SMTP id n8mr28039709pbn.9.1381106812448; Sun, 06 Oct 2013 17:46:52 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id qz9sm29426057pbc.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 06 Oct 2013 17:46:51 -0700 (PDT)
Message-ID: <52520479.9070807@gmail.com>
Date: Sun, 06 Oct 2013 16:46:49 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Review of:   draft-resnick-on-consensus-05
References: <5251FA64.7020205@dcrocker.net> <1F36C6D3-0173-4373-A72B-6E34489AD9A9@mnot.net>
In-Reply-To: <1F36C6D3-0173-4373-A72B-6E34489AD9A9@mnot.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: Mon, 07 Oct 2013 00:46:54 -0000

On 10/6/13 4:34 PM, Mark Nottingham wrote:
> On 07/10/2013, at 11:03 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> 1. in a natural state; without decoration or other treatment. "a
>> diamond in the rough"
>> 2. in difficulties. "even before the recession hit, the project was
>> in the rough"

> I think he's using it in the sense that it's used on a golf
> course...

I think that's pretty clearly the case, although it might
be confusing in juxtaposition with "rough consensus," where
"rough" means "approximate."  I'm not sure it's a big deal
and I don't want to lawyer the document to death.  We could
spin in circles for years trying to nail down "current practice."
Part of the problem that this document addresses is that some
current practice is anathema to consensus processes, not
because IETF process is wrong and needs modification but
because some chairs, I* folk, etc., aren't very skilled at
managing consensus.

Melinda


From presnick@qti.qualcomm.com  Sun Oct  6 22:45:26 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 F26AA21E8158 for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 22:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.643
X-Spam-Level: 
X-Spam-Status: No, score=-102.643 tagged_above=-999 required=5 tests=[AWL=-0.044, 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 WdMlIBDEtsuS for <ietf@ietfa.amsl.com>; Sun,  6 Oct 2013 22:45:18 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5791C21E814B for <ietf@ietf.org>; Sun,  6 Oct 2013 22:45:16 -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=1381124716; x=1412660716; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cqKP94tQvaarmtV54vTJAMZ75N0tkaqSFvgXnNmgS3I=; b=kHUcOACD/GAhLKYb8ckNczdrih3DAPfNVmOZm28fsAU+hBQKmUcDQj+a AA8gbquymfkqLH66WUNjaTCPSWvvAAl03E4oO3vp0ZzUa7Cqu1f8Mhfou TBSVY0HPF6RrwXpRpJrVb3tRJtaqXGeXJQfwjWjRUoltNKBOHQ6DMCEju A=;
X-IronPort-AV: E=McAfee;i="5400,1158,7220"; a="53654238"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 06 Oct 2013 22:45:15 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7220"; a="551567242"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Oct 2013 22:45:15 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 6 Oct 2013 22:45:15 -0700
Message-ID: <52524A68.7040800@qti.qualcomm.com>
Date: Mon, 7 Oct 2013 00:45:12 -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: Mark Nottingham <mnot@mnot.net>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net>
In-Reply-To: <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net>
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 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, 07 Oct 2013 05:45:26 -0000

On 10/6/13 7:30 PM, Mark Nottingham wrote:
> This is a VERY useful document, and I look forward to compelling my WG participants to read it, with a pop quiz afterwards.
>    

I've been exceedingly satisfied to hear this sort of thing from you and 
the other folks who posted and talked to me about this.

> The only issue I see is its length; while dedicated IETFers won't have a problem reading such a lengthy document, the people who could benefit most - new, potential or casual participants - will give up early, I fear.
>
> Could we have someone take an editorial knife to it? Some of the descriptions of situations are quite long, and there's a fair amount of repetition in the document. Some of the paragraphs are quite long as well. I reckon 2-4 pages could be saved, making it appealing to a much wider audience.
>    

I would be really disappointed by this. Indeed, my primary target was 
not at all new or casual participants; it was really intended for the 
dedicated folks and the chairs. I hope this is the start of a serious 
discussion in the IETF, not a primer for how the IETF works at a high 
level. For newer folks, I'm fine with the idea that some of this can be 
either incorporated into the Tao or the newcomer's orientation, or 
separated into a smaller primer document. But I really believe the long 
form is needed for real discussions among folks in the community.

> Beyond that, the only suggestion I'd make is an alternate title -- "Why We Hum." Or maybe "The Things We Hum And Do Not Say" (apologies to Jerry Maguire).
>    

And here I was originally paying homage to Wittgenstein, though it even 
got too long for that. Taken under advisement.

Now, off to tackle Dave's excellent (and extensive) review.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From mnot@mnot.net  Mon Oct  7 02:57:58 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 1ED3E21E8190 for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 02:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.269
X-Spam-Level: 
X-Spam-Status: No, score=-103.269 tagged_above=-999 required=5 tests=[AWL=-0.670, 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 mJeFKxw-RvtR for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 02:57:52 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDAB21E81F6 for <ietf@ietf.org>; Mon,  7 Oct 2013 02:57:37 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.103.242]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9A6F650A87; Mon,  7 Oct 2013 05:57:34 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <52524A68.7040800@qti.qualcomm.com>
Date: Mon, 7 Oct 2013 20:57:30 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D7920E1-5E12-4B67-995A-4D905E7B8FA4@mnot.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net> <52524A68.7040800@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1510)
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: Mon, 07 Oct 2013 09:57:58 -0000

On 07/10/2013, at 4:45 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> I would be really disappointed by this. Indeed, my primary target was =
not at all new or casual participants; it was really intended for the =
dedicated folks and the chairs. I hope this is the start of a serious =
discussion in the IETF, not a primer for how the IETF works at a high =
level. For newer folks, I'm fine with the idea that some of this can be =
either incorporated into the Tao or the newcomer's orientation, or =
separated into a smaller primer document. But I really believe the long =
form is needed for real discussions among folks in the community.

WFM; the Tao seems like a good first stop.

Thanks again,


--
Mark Nottingham   http://www.mnot.net/




From chris.dearlove@baesystems.com  Mon Oct  7 03:13:21 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 8329C21E81CD for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 03:13:20 -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_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 WaNcJHSimVBI for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 03:13:15 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2F421E81ED for <ietf@ietf.org>; Mon,  7 Oct 2013 03:13:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1049,1371078000"; d="scan'208";a="318842235"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 07 Oct 2013 11:13:03 +0100
X-IronPort-AV: E=Sophos;i="4.90,1049,1371078000"; d="scan'208";a="31002207"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 07 Oct 2013 11:13:03 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Mon, 7 Oct 2013 11:13:03 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: Review of:   draft-resnick-on-consensus-05
Thread-Topic: Review of:   draft-resnick-on-consensus-05
Thread-Index: AQHOwvDGIBj5qoN9x0KXWa7206/4/JnpAjHA
Date: Mon, 7 Oct 2013 10:13:03 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF6FAE@GLKXM0002V.GREENLNK.net>
References: <5251FA64.7020205@dcrocker.net>
In-Reply-To: <5251FA64.7020205@dcrocker.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 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, 07 Oct 2013 10:13:21 -0000

dcrocker@bbiw.net

> a "majority rule-> a "simple majority rule"

> Majorities come in different forms or degrees and the fact that 'rough =

> consensus' is often taken to mean 67% or 75%, as a rule of thumb can =

> make this confusing.

> From what you've written, your basic point seems to be that 51% isn't =

> enough; it's worth making that explicit.

To add to the confusion, and to emphasise the point about making clear, Bri=
tish and American English differ here. If three proposals (not the most com=
mon case, I agree, but it can happen) have 45%, 35% and 20% of the votes, t=
he first of these has a majority, sometimes emphasised as simple majority, =
in British English. (We do not - to our loss - use the word plurality. Just=
 51% is given the strong term absolute majority.) I haven't checked the con=
text here, but saying not just a simple majority might suggest to a British=
 English user that 51% is enough.

-- =

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 abdussalambaryun@gmail.com  Mon Oct  7 04:00:43 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 1CB0B21F9C7D for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 04:00: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=[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 UToigHeTLZiz for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 04:00:42 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 856BF21E80FD for <ietf@ietf.org>; Mon,  7 Oct 2013 04:00:41 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so6882319pdj.20 for <ietf@ietf.org>; Mon, 07 Oct 2013 04:00:41 -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=WwjWp2NRgqG84OMvJMExhbBwiVycXPGOmQgwAZDn04w=; b=TDroumRrUc332F3317VpU5u8S6BD7NTHVOO1GUwqAhEOY6GUJobdOVe75WT0HnPdUL 63aMqW4QA6yOM2as2iD5xpAIHpSpJiKMf8aIpQwssia9ShijilJHAVacbA4B17E/lrVL AZlrmEZTj2KUrgh318w/nCEAmEIPIrToVjgCm/zHVNArmjl22WwcKTTZlWxJ5KmKafZ1 JCZdnpp6iaSRK6rTzlL65BTg5nL/JYFU0rLxZ4cCbik+8Z/n5o930cPXMePeUh0M+BIb yESKqsHKxDc6vbf9gds9u7HoxJMZitcO+BaxyWGklhQuft5zNH21LyGLHhcT3pQ5wjh9 kSeQ==
MIME-Version: 1.0
X-Received: by 10.66.148.97 with SMTP id tr1mr2315771pab.163.1381143641172; Mon, 07 Oct 2013 04:00:41 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Mon, 7 Oct 2013 04:00:41 -0700 (PDT)
In-Reply-To: <5251D2B6.3080301@gmail.com>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <5251D2B6.3080301@gmail.com>
Date: Mon, 7 Oct 2013 12:00:41 +0100
Message-ID: <CADnDZ8_Hejod-yq3By_aDNhrMkD7Tmmsq5YJ--KUS9+8YZz_VQ@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b6d9fa21dc44904e8249079
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: Mon, 07 Oct 2013 11:00:43 -0000

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

I agree with Melinda, IETF WG Chair is the key to practice guiding the
group to clear consensus, otherwise guide them to best/productive
discussions related to improvements in the work or in the consensus.

AB


On Sun, Oct 6, 2013 at 10:14 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 10/6/13 1:03 PM, Jari Arkko wrote:
> > My goal is to publish it as an Informational RFC. It is an
> > explanation of principles and how they can be applied to productively
> > move IETF discussions forward. While there is no change to IETF
> > processes or any presumption that guidance from this document must be
> > followed, I have found the document very useful. It has been referred
> > to numerous times in IETF and IESG discussions. Consensus is hard and
> > many WG discussions have complex trade-offs and differing opinions. I
> > believe having this document become an RFC would help us apply the
> > useful principles even more widely than we are doing today.
>
> Glad to hear it - I think this is an enormously useful document.
> I'm wondering if wg chair training at an upcoming meeting can't
> be spent on it.  Vancouver's too soon, but what about London?
>
> Melinda
>
>

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

<div dir=3D"ltr"><div>I agree with Melinda, IETF WG Chair is the key to pra=
ctice guiding the group to clear consensus, otherwise guide them to best/pr=
oductive discussions related to improvements in the work or in the consensu=
s.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Sun, Oct 6, 2013 at 10:14 PM, Melinda Shore <span di=
r=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=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 10/6/13 1:03 PM, Jari A=
rkko wrote:<br>
&gt; My goal is to publish it as an Informational RFC. It is an<br>
&gt; explanation of principles and how they can be applied to productively<=
br>
&gt; move IETF discussions forward. While there is no change to IETF<br>
&gt; processes or any presumption that guidance from this document must be<=
br>
&gt; followed, I have found the document very useful. It has been referred<=
br>
&gt; to numerous times in IETF and IESG discussions. Consensus is hard and<=
br>
&gt; many WG discussions have complex trade-offs and differing opinions. I<=
br>
&gt; believe having this document become an RFC would help us apply the<br>
&gt; useful principles even more widely than we are doing today.<br>
<br>
</div>Glad to hear it - I think this is an enormously useful document.<br>
I&#39;m wondering if wg chair training at an upcoming meeting can&#39;t<br>
be spent on it. =A0Vancouver&#39;s too soon, but what about London?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b6d9fa21dc44904e8249079--

From lberger@labn.net  Mon Oct  7 05:48:56 2013
Return-Path: <lberger@labn.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 6324721E808C for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 05:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[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 S+czaymTOP1Q for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 05:48:52 -0700 (PDT)
Received: from outbound-ss-1943.hostmonster.com (outbound-ss-1943.hostmonster.com [67.222.57.249]) by ietfa.amsl.com (Postfix) with SMTP id CFDA921E8092 for <ietf@ietf.org>; Mon,  7 Oct 2013 05:48:50 -0700 (PDT)
Received: (qmail 23604 invoked by uid 0); 7 Oct 2013 12:48:26 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy6.mail.unifiedlayer.com with SMTP; 7 Oct 2013 12:48:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=K67M9WLPzHEhJV8OBdiu+52Bak2IzBYtVCZz/EdzI7g=;  b=S03zGfIf+pVXmClJp7aBkz3lvrshqvaZH4IfBeQKvp7kv67UKOvrOXdDhqNM286uxZ4/gUovWyNZ3MWgtOKtJ4WkHKJdAjbTd5TVZLDxL95LOKjy+toAMhSIV9AG3aSn;
Received: from box313.bluehost.com ([69.89.31.113]:52819 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1VTAEc-0004W0-0f; Mon, 07 Oct 2013 06:48:26 -0600
Message-ID: <5252AD9D.6010408@labn.net>
Date: Mon, 07 Oct 2013 08:48:29 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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: Mon, 07 Oct 2013 12:48:56 -0000

Hi,

I definitely agree that this is a really useful document. Lots of good
background and general considerations. But I think it misses two
important points that should be addressed prior to publication:

1)  The role WG/IETF mailing lists play in building and
     gauging consensus

The draft leaves me with an impression that mailing lists don't play any
substantive role.  (Said another way: if I'm participating remotely, or
miss a meeting, how do I hum/participate?)  Clearly this is the wrong
conclusion!

I suspect/hope that with all the recent discussion on remote
participation that I really don't need to elaborate on this point any
further.

2) That some participants/chairs/I*s like seeing hands, and that's okay

There are different ways to achieve and determine consensus.  As stated
in RFC2418:
   Consensus
   can be determined by a show of hands, humming, or any other means on
   which the WG agrees (by rough consensus, of course).  Note that 51%
   of the working group does not qualify as "rough consensus" and 99% is
   better than rough.  It is up to the Chair to determine if rough
   consensus has been reached.

I've been in and run many WG sessions where a show of hands is used to
help gauge consensus of those present.  I can't speak for others, but
hands are my preference for a pretty simple reason: my hearing is such
that in a large room, hums just don't provide me any real input -- I can
gauge silence vs hums, but that's about it.  I know that I've been in
rooms where my conclusion of which hummed response was "greater"
differed from others. Perhaps based on where we were each sitting,
perhaps based on hum frequency, perhaps on my/our hearing.  I just don't
know.

I think a show of hands can provide the same input into the consensus
principles described in the draft, and this should be mentioned.  Even
just quoting the 1st sentence from RFC2418 listed above in the draft
should help. Adding some words on how a show of hands differs from a
formal vote would be even better.

Lou


On 10/6/2013 5:03 PM, Jari Arkko wrote:
> The document talks about ways in which consensus processes can be successfully run in the IETF. After the last few rounds of versions, I believe this document is ready to move forward. 
> 
> My goal is to publish it as an Informational RFC. It is an explanation of principles and how they can be applied to productively move IETF discussions forward. While there is no change to IETF processes or any presumption that guidance from this document must be followed, I have found the document very useful. It has been referred to numerous times in IETF and IESG discussions. Consensus is hard and many WG discussions have complex trade-offs and differing opinions. I believe having this document become an RFC would help us apply the useful principles even more widely than we are doing today.  
> 
> The abstract says:
> 
>    The IETF has had a long tradition of doing its technical work through
>    a consensus process, taking into account the different views among
>    IETF participants and coming to (at least rough) consensus on
>    technical matters.  In particular, the IETF is supposed not to be run
>    by a "majority rule" philosophy.  This is why we engage in rituals
>    like "humming" instead of voting.  However, more and more of our
>    actions are now indistinguishable from voting, and quite often we are
>    letting the majority win the day, without consideration of minority
>    concerns.  This document is a collection of thoughts on what rough
>    consensus is, how we have gotten away from it, and the things we can
>    do in order to really achieve rough consensus.
> 
>       Note (to be removed before publication): This document is quite
>       consciously being put forward as Informational.  It does not
>       propose to change any IETF processes and is therefore not a BCP.
>       It is simply a collection of principles, hopefully around which
>       the IETF can come to (at least rough) consensus.
> 
> The draft can be obtained from http://tools.ietf.org/html/draft-resnick-on-consensus
> 
> You should see a last call announcement soon, and both me and Pete look forward to your feedback.
> 
> Jari
> 
> 
> 
> 
> 

From jari.arkko@piuha.net  Mon Oct  7 06:27:53 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 73FC821E80A6 for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 06:27:53 -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 fpnGgcgpz2CJ for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 06:27:48 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEF521E80A7 for <ietf@ietf.org>; Mon,  7 Oct 2013 06:27:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5572D2CC5F; Mon,  7 Oct 2013 16:27:46 +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 F875ao-2LipV; Mon,  7 Oct 2013 16:27:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 918912CC48; Mon,  7 Oct 2013 16:27:45 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5251D2B6.3080301@gmail.com>
Date: Mon, 7 Oct 2013 16:27:45 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <3A283D1F-3AD5-43AC-8C04-E1B5E8B4564E@piuha.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <5251D2B6.3080301@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, 07 Oct 2013 13:27:53 -0000

> Glad to hear it - I think this is an enormously useful document.
> I'm wondering if wg chair training at an upcoming meeting can't
> be spent on it.  Vancouver's too soon, but what about London?


Good idea.

Jari


From Fred.L.Templin@boeing.com  Mon Oct  7 11:13:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B94111E8109; Mon,  7 Oct 2013 11:13:41 -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 fZ6HgwJ1BXjV; Mon,  7 Oct 2013 11:13:36 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id D592521F9FEE; Mon,  7 Oct 2013 11:13:28 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r97IDSkk027794; Mon, 7 Oct 2013 11:13:28 -0700
Received: from XCH-NWHT-01.nw.nos.boeing.com (xch-nwht-01.nw.nos.boeing.com [130.247.70.222]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r97IDRNQ027784 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 7 Oct 2013 11:13:28 -0700
Received: from XCH-BLV-303.nw.nos.boeing.com (130.247.25.215) by XCH-NWHT-01.nw.nos.boeing.com (130.247.70.222) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 7 Oct 2013 11:13:27 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-303.nw.nos.boeing.com ([169.254.3.177]) with mapi id 14.02.0328.011; Mon, 7 Oct 2013 11:13:26 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KmVHjrcZv7kkeUppI3Iq7lo5nk+jmggASVUyA=
Date: Mon, 7 Oct 2013 18:13:26 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Oct 2013 18:13:41 -0000

Hi, I would like to make a small amendment to what I said in my
previous message as follows:

4) Section 5, change the final paragraph to:

   "As a result of the above mentioned requirements, a packet's header
   chain length MUST fit within the Path MTU associated with its
   destination.  Hosts MAY discover the Path MTU, using procedures such
   as those defined in [RFC1981] and [RFC4821]. However, if a host does
   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
   1280 bytes [RFC2460]. The host MUST then limit each packet's header
   chain length to the Path MTU minus 256 bytes in case additional
   encapsulation headers are inserted by tunnels on the path."

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Templin, Fred L
> Sent: Friday, October 04, 2013 1:42 PM
> To: ietf@ietf.org; IETF-Announce
> Cc: ipv6@ietf.org
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Hi, I have a concern about this document. In the definition of "IPv6
> Header Chain", it says:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is considered to be an upper-layer header and terminates
>    the header chain."
>=20
> This means that stateless firewalls are being directed to discontinue
> extension header parsing when a first encapsulated IPv6 header is
> encountered - even though there may be many more parsable (inner)
> headers that follow. As a result, the firewall would either have to
> drop or forward the packet without examining the true upper layer
> header. This may result in an incorrect perception that tunneled
> traffic is either less reliable or more dangerous than non-tunneled
> traffic.
>=20
> Here are my suggested changes to address this issue:
>=20
> 1) Section 3, under "IPv6 Header Chain", change:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is considered to be an upper-layer header and terminates
>    the header chain."
>=20
> to:
>=20
>   "However, if a second IPv6 header appears in the header chain, as
>    is the case when IPv6 is tunneled over IPv6, the second IPv6
>    header is optionally considered to be either an upper-layer header
>    that terminates the header chain or another extension header that
>    continues the chain."
>=20
> 2) Section 3, under "Upper-layer Header", change:
>=20
>   "In the general case, the upper-layer header is the first member
>    of the header chain that is neither an IPv6 header nor an IPv6
>    extension header."
>=20
> to:
>=20
>   "In the general case, the upper-layer header is the first member
>    of the header chain that is not considered to be an extension
> header."
>=20
> 3) Section 3, under "Upper-layer Header", delete the following
> sentence:
>=20
>   "However, if either an ESP header, or a second IPv6 header occur in
>    the header chain, they are considered to be upper layer headers and
>    they terminate the header chain."
>=20
> 4) Section 5, change the final paragraph to:
>=20
>   "As a result of the above mentioned requirements, a packet's header
>    chain length cannot exceed the Path MTU associated with its
>    destination.  Hosts MAY discover the Path MTU, using procedures such
>    as those defined in [RFC1981] and [RFC4821].  However, if a host
> does
>    not discover the Path MTU, it MUST limit the header chain length to
>    1024 bytes.  Limiting the header chain length to 1024 bytes ensures
>    that the header chain length does not exceed the IPv6 minimum MTU
>    [RFC2460] even if additional encapsulation headers are inserted by
>    tunnels on the path."
>=20
> Thanks - Fred
> Fred.l.templin@boeing.com
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of
> > The IESG
> > Sent: Wednesday, October 02, 2013 11:55 AM
> > To: IETF-Announce
> > Cc: ipv6@ietf.org
> > Subject: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> > (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >
> >
> > The IESG has received a request from the IPv6 Maintenance WG (6man)
> to
> > consider the following document:
> > - 'Implications of Oversized IPv6 Header Chains'
> >   <draft-ietf-6man-oversized-header-chain-08.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-10-16. 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 IPv6 specification allows IPv6 header chains of an arbitrary
> >    size.  The specification also allows options which can in turn
> > extend
> >    each of the headers.  In those scenarios in which the IPv6 header
> >    chain or options are unusually long and packets are fragmented, or
> >    scenarios in which the fragment size is very small, the first
> >    fragment of a packet may fail to include the entire IPv6 header
> >    chain.  This document discusses the interoperability and security
> >    problems of such traffic, and updates RFC 2460 such that the first
> >    fragment of a packet is required to contain the entire IPv6 header
> >    chain.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> chain/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-6man-oversized-header-
> > chain/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------

From ted.ietf@gmail.com  Mon Oct  7 12:04:25 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 C30B421F843F; Mon,  7 Oct 2013 12:04:25 -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 PrbAfsE17oWQ; Mon,  7 Oct 2013 12:04:24 -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 083DD11E8146; Mon,  7 Oct 2013 12:03:55 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id e14so16233103iej.6 for <multiple recipients>; Mon, 07 Oct 2013 12:03: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 :cc:content-type; bh=uAdTWfYAv19Y1i94lS8vsxHoJC0x1ZaMVRkl7DHZsSw=; b=n+SggzDTe1uuMpPqaslgJk7WhanZrWrbsuzEGwpIQy+eAuk3Mn/iyi6LV1wk5Rh9Il 1b9EMnjss2v3SQ7gBLY+2TjSU8R5G2+7YJgfKnNkyd/RResMs4r9OJLjpMTt89pjJgmd yhiCvs8yFY0whlNHfzi+SDdaS1ZuCGaynMb0vzCJKBy/FLO1IitxDD6FcDfqnbM4Iqh1 Ugv5DjdOcOMAaD90OVOllJivMHJ0ahJ0b9ujW1yzBNvAGCKjwXJV0jsR4FV4S5siOL7n oQcGige/eNlEQysKXQ1400jXuHZfXQHo5taw3t9fkDduUnYdouoKZHc+mOg4m0j5zHnq 0qUA==
MIME-Version: 1.0
X-Received: by 10.43.3.196 with SMTP id nz4mr1340659icb.74.1381172635393; Mon, 07 Oct 2013 12:03:55 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 7 Oct 2013 12:03:55 -0700 (PDT)
In-Reply-To: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
Date: Mon, 7 Oct 2013 12:03:55 -0700
Message-ID: <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec516197d4e665a04e82b5087
Cc: 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, 07 Oct 2013 19:04:25 -0000

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

First, I am always happy when folks take the time to think deeply about the
IETF's processes and share those thoughts with the community.  I think the
conversation this has already started has been useful, and I hope that the
last call conversation is the same.

That said, I do not think this document is ready for publication as an RFC,
and I personally suspect that it wouldn't be the best fate for it even it
were.  On the second point, the truth is that informational RFCs are
treated as actual requests for comments much any more, but are taken as
fixed; if the points this raises are to be maintained as items of
conversation (which is my personal preference), then incorporating pieces
of it into the Tao, Edu Team documents, or WG training may be appropriate
instead.  That is, put this into some form where folks will not take it as
an item of dogma, but as the start of a conversation, and the community
will be better served.  Even as an Informational document, if it is
published as an RFC by a sitting AD via the IETF stream, it may not get
that treatment.

If the IESG does believe that this should be published as an RFC, I think
it continues to need serious work before publication.  At the very base, I
think it needs a much stronger sense of its audience (advice to WG chairs
and those that deal with them? new participants in the IETF? those who want
to understand the workings of the IETF from the outside?) and a structure
which relates to that audience.  I note, for example, that the document
references none of the IETF's process documents or discussions that arose
out previous work in this area; that's fine for some audiences but is going
to be missed by folks who might get handed this as an explanatory document
on how things work (or ought to) in the IETF.

Once it has that audience, some of the issues with the current document may
fall out, but among those with which I have personal disagreements:

The document consistently describes a test for objection model of document
processing; that's a fair summary of how the IETF works, but shoe-horning
the description into "rough consensus" because we like the slogan is not
really helping folks understand the IETF.  The core of the IETF is a
participatory process which is meant to be cooperative rather than
adversarial; to that extent it is fair to describe it in consensus terms.
Beyond that, however, we are really not seeking the consent of all parties,
even as an ideal.  We are trying to make sure that there are no known
technical issues with a proposal and that there is sufficient support to
believe that it will be implemented and deployed to the good of the
network.  Encouraging folks to believe that the ideal is full consensus is
highly problematic, for exactly the reasons that Pete later raises with
regards to voting:  it is very difficult to determine when you have the
consent of all parties if you cannot limit the parties in some way.  We
cannot name our members, so we cannot either count votes *or count all of
them as consenting*.

The document has vastly improved its description of compromise over its
previous iterations, for which Pete should be commended.  But it remains
problematic in its description of participation. In the section "Five
people for
and one hundred people against might still be rough consensus", the
document describes what can occur when one proposal is favoured over
another by a working group's active participants:  one set of participants
may recruit new voices to add to their preferences.  The difficulty with the
given description is that it is a strawman compared to that actual
complexity
of dealing with this situation, because it posits sales and marketing folks
being the new voices.  The far more difficult reality is that the voices
often
come from members of an impacted technical community who generally do
not attend or participate in the IETF.  Were they known participants in the
IETF process, it is clear that their message "I agree with X's points" would
be heard in one way, where them being new participants causes them, in
this approach, to be discounted entirely if they raise no new points.
Novelty
is the wrong test here, as is length of participation; the test that WG
chairs
must use is the much messier judgement call of what the impact of the
objections is on the likely implementation and deployment of the system
under
discussion.

Lastly, I think Pete has failed to capture that one reason for using
humming or hands is that it is easy for very active participants to
dominate a conversation
but much less easy for them to pretend to be a large group.  Particularly
in BoFs, using those methods to indicate the likely breadth of interest is
critical.  The same method can be used, with some of the caution Pete
recommends, to gauge whether an issue which appears to be contentious based
on a mic line is actually a problem.  It can also, in some cases, be a
valuable method of reinforcing the resolve a room that has already likely
come to a broad agreement.  That does not contravene Pete's point that this
should not be used to silence objections, but there are cases where it is
important in its own right.

Again, I believe this is a valuable conversation and one that ought to keep
going; my recommendation against publication should also be taken as a
recommendation both to Pete to keep working on these ideas and to the
General Area Director to support a forum for that discussion.

regards,

Ted Hardie



On Mon, Oct 7, 2013 at 9:48 AM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'On Consensus and Humming in the IETF'
>   <draft-resnick-on-consensus-05.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-11-04. 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 IETF has had a long tradition of doing its technical work through
>    a consensus process, taking into account the different views among
>    IETF participants and coming to (at least rough) consensus on
>    technical matters.  In particular, the IETF is supposed not to be run
>    by a "majority rule" philosophy.  This is why we engage in rituals
>    like "humming" instead of voting.  However, more and more of our
>    actions are now indistinguishable from voting, and quite often we are
>    letting the majority win the day, without consideration of minority
>    concerns.  This document is a collection of thoughts on what rough
>    consensus is, how we have gotten away from it, and the things we can
>    do in order to really achieve rough consensus.
>
>       Note (to be removed before publication): This document is quite
>       consciously being put forward as Informational.  It does not
>       propose to change any IETF processes and is therefore not a BCP.
>       It is simply a collection of principles, hopefully around which
>       the IETF can come to (at least rough) consensus.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-resnick-on-consensus/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-resnick-on-consensus/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

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

<div dir=3D"ltr"><div><div>First, I am always happy when folks take the tim=
e to think deeply about the IETF&#39;s processes and share those thoughts w=
ith the community.=A0 I think the conversation this has already started has=
 been useful, and I hope that the last call conversation is the same.<br>
<br>That said, I do not think this document is ready for publication as an =
RFC, and I personally suspect that it wouldn&#39;t be the best fate for it =
even it were.=A0 On the second point, the truth is that informational RFCs =
are treated as actual requests for comments much any more, but are taken as=
 fixed; if the points this raises are to be maintained as items of conversa=
tion (which is my personal preference), then incorporating pieces of it int=
o the Tao, Edu Team documents, or WG training may be appropriate instead.=
=A0 That is, put this into some form where folks will not take it as an ite=
m of dogma, but as the start of a conversation, and the community will be b=
etter served.=A0 Even as an Informational document, if it is published as a=
n RFC by a sitting AD via the IETF stream, it may not get that treatment.<b=
r>
<br></div>If the IESG does believe that this should be published as an RFC,=
 I think it continues to need serious work before publication.=A0 At the ve=
ry base, I think it needs a much stronger sense of its audience (advice to =
WG chairs and those that deal with them? new participants in the IETF? thos=
e who want to understand the workings of the IETF from the outside?) and a =
structure which relates to that audience.=A0 I note, for example, that the =
document references none of the IETF&#39;s process documents or discussions=
 that arose out previous work in this area; that&#39;s fine for some audien=
ces but is going to be missed by folks who might get handed this as an expl=
anatory document on how things work (or ought to) in the IETF.<br>
<br></div><div>Once it has that audience, some of the issues with the curre=
nt document may fall out, but among those with which I have personal disagr=
eements:<br><br></div><div>The document consistently describes a test for o=
bjection model of document processing; that&#39;s a fair summary of how the=
 IETF works, but shoe-horning the description into &quot;rough consensus&qu=
ot; because we like the slogan is not really helping folks understand the I=
ETF.=A0 The core of the IETF is a participatory process which is meant to b=
e cooperative rather than adversarial; to that extent it is fair to describ=
e it in consensus terms.=A0 Beyond that, however, we are really not seeking=
 the consent of all parties, even as an ideal.=A0 We are trying to make sur=
e that there are no known technical issues with a proposal and that there i=
s sufficient support to believe that it will be implemented and deployed to=
 the good of the network.=A0 Encouraging folks to believe that the ideal is=
 full consensus is highly problematic, for exactly the reasons that Pete la=
ter raises with regards to voting:=A0 it is very difficult to determine whe=
n you have the consent of all parties if you cannot limit the parties in so=
me way.=A0 We cannot name our members, so we cannot either count votes *or =
count all of them as consenting*.<br>
<br></div><div>The document has vastly improved its description of compromi=
se over its previous iterations, for which Pete should be commended.=A0 But=
 it remains problematic in its description of participation. In the section=
 &quot;<font>Five people for<br>
</font></div><div><font>and one hundred people against might still be rough=
 consensus&quot;, the <br>document describes what can occur when one propos=
al is favoured over<br></font></div><div><font>another by a working group&#=
39;s active participants:=A0 one set of participants<br>
may recruit new voices to add to their preferences.=A0 The difficulty with =
the<br>given description is that it is a strawman compared to that actual c=
omplexity<br>of dealing with this situation, because it posits sales and ma=
rketing folks<br>
being the new voices.=A0 The far more difficult reality is that the voices =
often <br>come from members of an impacted technical community who generall=
y do <br>not attend or participate in the IETF.=A0 Were they known particip=
ants in the<br>
IETF process, it is clear that their message &quot;I agree with X&#39;s poi=
nts&quot; would<br>be heard in one way, where them being new participants c=
auses them, in<br>this approach, to be discounted entirely if they raise no=
 new points.=A0 Novelty<br>
is the wrong test here, as is length of participation; the test that WG cha=
irs<br>must use is the much messier judgement call of what the impact of th=
e<br>objections is on the likely implementation and deployment of the syste=
m under<br>
discussion.=A0 <br><br></font></div><div><font>Lastly, I think Pete has fai=
led to capture that one reason for using humming or hands is that it is eas=
y for very active participants to dominate a conversation<br></font></div>
<div><font>but much less easy for them to pretend to be a large group.=A0 P=
articularly in BoFs, using those methods to indicate the likely breadth of =
interest is critical.=A0 The same method can be used, with some of the caut=
ion Pete recommends, to gauge whether an issue which appears to be contenti=
ous based on a mic line is actually a problem.=A0 It can also, in some case=
s, be a valuable method of reinforcing the resolve a room that has already =
likely come to a broad agreement.=A0 That does not contravene Pete&#39;s po=
int that this should not be used to silence objections, but there are cases=
 where it is important in its own right.<br>
<br></font></div><div><font>Again, I believe this is a valuable conversatio=
n and one that ought to keep going; my recommendation against publication s=
hould also be taken as a recommendation both to Pete to keep working on the=
se ideas and to the General Area Director to support a forum for that discu=
ssion.<br>
<br>regards,<br><br>Ted Hardie<br></font></div><div><br><pre class=3D""><fo=
nt><span class=3D""></span></font><font><span class=3D""></span></font></pr=
e></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mo=
n, Oct 7, 2013 at 9:48 AM, The IESG <span dir=3D"ltr">&lt;<a href=3D"mailto=
:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@ietf.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"><br>
The IESG has received a request from an individual submitter to consider<br=
>
the following document:<br>
- &#39;On Consensus and Humming in the IETF&#39;<br>
=A0 &lt;draft-resnick-on-consensus-05.txt&gt; as Informational RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-11=
-04. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0The IETF has had a long tradition of doing its technical work throug=
h<br>
=A0 =A0a consensus process, taking into account the different views among<b=
r>
=A0 =A0IETF participants and coming to (at least rough) consensus on<br>
=A0 =A0technical matters. =A0In particular, the IETF is supposed not to be =
run<br>
=A0 =A0by a &quot;majority rule&quot; philosophy. =A0This is why we engage =
in rituals<br>
=A0 =A0like &quot;humming&quot; instead of voting. =A0However, more and mor=
e of our<br>
=A0 =A0actions are now indistinguishable from voting, and quite often we ar=
e<br>
=A0 =A0letting the majority win the day, without consideration of minority<=
br>
=A0 =A0concerns. =A0This document is a collection of thoughts on what rough=
<br>
=A0 =A0consensus is, how we have gotten away from it, and the things we can=
<br>
=A0 =A0do in order to really achieve rough consensus.<br>
<br>
=A0 =A0 =A0 Note (to be removed before publication): This document is quite=
<br>
=A0 =A0 =A0 consciously being put forward as Informational. =A0It does not<=
br>
=A0 =A0 =A0 propose to change any IETF processes and is therefore not a BCP=
.<br>
=A0 =A0 =A0 It is simply a collection of principles, hopefully around which=
<br>
=A0 =A0 =A0 the IETF can come to (at least rough) consensus.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-resnick-on-consensus/" tar=
get=3D"_blank">http://datatracker.ietf.org/doc/draft-resnick-on-consensus/<=
/a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-resnick-on-consensus/ballo=
t/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-resnick-on-cons=
ensus/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br></div></div>

--bcaec516197d4e665a04e82b5087--

From jaap@NLnetLabs.nl  Mon Oct  7 12:12:54 2013
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2F5611E812A for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 12:12:53 -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 9ip4sL1PoBei for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 12:12:53 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4ccb]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9D411E8130 for <ietf@ietf.org>; Mon,  7 Oct 2013 12:12:50 -0700 (PDT)
Received: from bela.nlnetlabs.nl (localhost [IPv6:::1]) by bela.nlnetlabs.nl (8.14.7/8.14.7) with ESMTP id r97JCYDn096118; Mon, 7 Oct 2013 21:12:35 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
Authentication-Results: bela.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
Message-Id: <201310071912.r97JCYDn096118@bela.nlnetlabs.nl>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: Review of: draft-resnick-on-consensus-05
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF6FAE@GLKXM0002V.GREENLNK.net>
References: <5251FA64.7020205@dcrocker.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF6FAE@GLKXM0002V.GREENLNK.net>
Comments: In-reply-to "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> message dated "Mon, 07 Oct 2013 10:13:03 -0000."
Date: Mon, 07 Oct 2013 21:12:34 +0200
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (bela.nlnetlabs.nl [IPv6:::1]); Mon, 07 Oct 2013 21:12:36 +0200 (CEST)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, 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, 07 Oct 2013 19:12:54 -0000

    To add to the confusion, and to emphasise the point about making
    clear, British and American English differ here.  If three
    proposals (not the most common case, I agree, but it can happen)
    have 45%, 35% and 20% of the votes, the first of these has a
    majority, sometimes emphasised as simple majority, in British
    English. (We do not - to our loss - use the word plurality.
    Just 51% is given the strong term absolute majority.) I haven't
    checked the context here, but saying not just a simple majority
    might suggest to a British English user that 51% is enough.

Let's avoid any dependency on either idioms. Given that the bulk
of the intended audience might not be aware of either specific idiom
but have english as their second of nth language, it is probably
better to explain what is meant.

	jaap

From brian.e.carpenter@gmail.com  Mon Oct  7 12:34:49 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 72ED111E812B; Mon,  7 Oct 2013 12:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.517
X-Spam-Level: 
X-Spam-Status: No, score=-102.517 tagged_above=-999 required=5 tests=[AWL=0.082, 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 cvceMf75Mj1D; Mon,  7 Oct 2013 12:34:49 -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 5023721E81B7; Mon,  7 Oct 2013 12:34:42 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id bj1so7717499pad.35 for <multiple recipients>; Mon, 07 Oct 2013 12:34:42 -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=UHY2Crzs5WLxZS5ofT14DWhJzz0jy9CiaSOdHPgMbbI=; b=ierIGtE4xid5K6laNh0mKUgw72dMunr0fMH0TWFRDEy+3ppGllc0hRm8qjENc31bZB Eo+tU9/EyL+GfKvzx9ZFHdfIav82sIjI2m+nssSOVSUDVvdL9FuIzfvU8JkkvTrFHeUU nLXBA+IbLiQwroIlAbIOD3haowL/JeagSea8DEyz3v66SJQ4nmbYFuNDK9DdmmGVP9bn OOi8hBlim3xYQAPWotaFfXg5upNNUchD0PRFTNNjf8a17pZaDuMp8F6dexE1QN4mNnpo 5L863Q3+RarNJRgyfK9RT6TkjiTP4Xckc/ykw4bUOakGyIQ/pO86WaCaRSg7TwT7hSoP DxSQ==
X-Received: by 10.66.66.202 with SMTP id h10mr34419563pat.70.1381174481979; Mon, 07 Oct 2013 12:34:41 -0700 (PDT)
Received: from [192.168.178.20] (58.197.69.111.dynamic.snap.net.nz. [111.69.197.58]) by mx.google.com with ESMTPSA id ve9sm35067909pbc.19.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 12:34:41 -0700 (PDT)
Message-ID: <52530CCF.8090605@gmail.com>
Date: Tue, 08 Oct 2013 08:34:39 +1300
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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
In-Reply-To: <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>, 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, 07 Oct 2013 19:34:49 -0000

On 08/10/2013 08:03, Ted Hardie wrote:
...

> were.  On the second point, the truth is that informational RFCs are [not]
> treated as actual requests for comments much any more, but are taken as
> fixed; 

I've inserted the "not" that Ted certainly intended. But I think he raises
an important point. If the phrase "Request For Comments" no longer means
what it says, we need another RFC, with a provisional title of
"Request For Comments Means What It Says".

We still see comments on RFC 791 reasonably often, and I see comments
on RFC 2460 practically every day. That's as it should be.

So I'd like to dispute Ted's point that by publishing a version of
resnick-on-consensus as an RFC, we will engrave its contents in stone.
If that's the case, we have an even deeper problem than misunderstandings
of rough consensus.

otoh Ted's specific points on the draft are all valuable.

    Brian

From Ted.Lemon@nominum.com  Mon Oct  7 13:35:18 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 46A5B11E8152; Mon,  7 Oct 2013 13:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 gGC7tFUn106z; Mon,  7 Oct 2013 13:35:07 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id CADC011E8136; Mon,  7 Oct 2013 13:35:06 -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 DSNKUlMa+nHhDGCFdsZjtvpkh1VIC1MIQhIz@postini.com; Mon, 07 Oct 2013 13:35: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 2A9C81B82DF; Mon,  7 Oct 2013 13:35:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 1E8E2190061; Mon,  7 Oct 2013 13:35:06 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Oct 2013 13:35:06 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1811\))
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52530CCF.8090605@gmail.com>
Date: Mon, 7 Oct 2013 16:35:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1811)
X-Originating-IP: [192.168.1.10]
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>, 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, 07 Oct 2013 20:35:18 -0000

On Oct 7, 2013, at 3:34 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> So I'd like to dispute Ted's point that by publishing a version of
> resnick-on-consensus as an RFC, we will engrave its contents in stone.
> If that's the case, we have an even deeper problem than =
misunderstandings
> of rough consensus.

Right, I think what Ted is describing is a BCP, not an Informational =
RFC.


From mrex@sap.com  Mon Oct  7 14:02:19 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 7C04421E81B7 for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 14:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.649
X-Spam-Level: 
X-Spam-Status: No, score=-8.649 tagged_above=-999 required=5 tests=[AWL=1.600,  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 QIRF505x3Top for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 14:02:14 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 14BBF21E80C5 for <ietf@ietf.org>; Mon,  7 Oct 2013 14:02:13 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r97KuTg3013084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Oct 2013 22:56:30 +0200 (MEST)
Subject: Re: Review of: draft-resnick-on-consensus-05
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF6FAE@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Date: Mon, 7 Oct 2013 22:56:29 +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: <20131007205629.CF5801A9E1@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, IETF Discussion <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: Mon, 07 Oct 2013 21:02:19 -0000

Dearlove, Christopher (UK) wrote:
> dcrocker@bbiw.net
>>
>> From what you've written, your basic point seems to be that 51% isn't 
>> enough; it's worth making that explicit.
> 
> To add to the confusion, and to emphasise the point about making clear,
> British and American English differ here. If three proposals (not the
> most common case, I agree, but it can happen) have 45%, 35% and 20%
> of the votes, the first of these has a majority, sometimes emphasised
> as simple majority, in British English. (We do not - to our loss - use
> the word plurality. Just 51% is given the strong term absolute majority.)
> I haven't checked the context here, but saying not just a simple
> majority might suggest to a British English user that 51% is enough.


Voting as is done in elections for political parties is often going
to produce a political result, a personal preference of a few rather
than an engineering solution that adequately addresses the concerns
of the community at large.


What we could do in the IETF, is not just trying to pick the lesser evil,
but rather use the _engineering_ skills to modify and/or merge proposals
to increase the number of folks that support the result and reduce
the amount of folks that object the result.


With your example of three competing proposals: A, B and C, and by couting
"votes" the WG chair determine support of 45%, 35% and 20% respectively,
does this mean that A has signficant support?   Not at all.  It could be
that the folks who voted for B and C did so because they are both strongly
opposed to A.

A WG chair who wants to be neutral on the decision should probably not
just call:
   which of the three proposals do you prefer:  A, B or C

and perform political inferences on the result, but rather
_ask_ the engineers direclty:

   if we were to select A, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for A?

   if we were to select B, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for B?

   if we were to select C, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for C?


I've seen a few "WG consensus calls" which appeared somewhat skewed/biased
to me towards exclusing specific outcomes.  I do _not_ know whether this
was causes by malicous intent or just accidental / not sufficiently well
thought out.  I'm OK with a leadership decision, but leadership decisions
should not be exerted early in the process by preventing certain questions
to get asked at all.  

How well the process works can be seen by how objections are resolved.
Are objections handled by spin doctors, or by engineers that are open
to improvements of their work.


-Martin

From john@jlc.net  Mon Oct  7 14:08:25 2013
Return-Path: <john@jlc.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 1D5A011E8160 for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 14:08:25 -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=[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 lA7DfENKKT2E for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 14:08:21 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id C1DB321F9A8D for <ietf@ietf.org>; Mon,  7 Oct 2013 14:08:17 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 7E4F5C94BF; Mon,  7 Oct 2013 17:08:12 -0400 (EDT)
Date: Mon, 7 Oct 2013 17:08:12 -0400
From: John Leslie <john@jlc.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
Message-ID: <20131007210812.GA33849@verdi>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52530CCF.8090605@gmail.com>
User-Agent: Mutt/1.4.1i
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: Mon, 07 Oct 2013 21:08:25 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> ... If the phrase "Request For Comments" no longer means what it says,
> we need another RFC, with a provisional title of
> "Request For Comments Means What It Says".

   ;^)

> We still see comments on RFC 791 reasonably often, and I see comments
> on RFC 2460 practically every day. That's as it should be.

   Absolutely!

> So I'd like to dispute Ted's point that by publishing a version of
> resnick-on-consensus as an RFC, we will engrave its contents in stone.

   Well, of course, all RFCs have always been "archival" -- to that
extent, they _are_ "engraved in stone"...

> If that's the case, we have an even deeper problem than misunderstandings
> of rough consensus.

   Alas, IMHO, we do. :^(

   Ted and Dave Crocker _have_ made very good comments on this I-D which
is proposed to be an Informational RFC. For the most part, these comments
could just as well come _after_ it is published as such.

   The _problem_ is that an RFC clearly labeled as an individual
contribution _should_ have value _as_ an individual contribution. It
should not have to pass muster of our famous peanut gallery before
being published.

   The story is completely different for working-group documents
published on the Standards Track. For those, our quality-control process
is quite necessary.

   Perhaps the problem comes from the boilerplate for Informational:
] 
] Status of This Memo
] 
]  This document is not an Internet Standards Track specification; it is
]  published for informational purposes.
] 
]  This document is a product of the Internet Engineering Task Force
]  (IETF).  It represents the consensus of the IETF community.  It has
]  received public review and has been approved for publication by the
]  Internet Engineering Steering Group (IESG).  Not all documents
]  approved by the IESG are a candidate for any level of Internet
]  Standard; see Section 2 of RFC 5741.
] 
]  Information about the current status of this document, any errata,
]  and how to provide feedback on it may be obtained at
]  http://www.rfc-editor.org/info/rfc7017.

   The only differences between this boilerplate and the boilerplate
for standards track is that the Standards Track has a different first
paragraph
]
] This is an Internet Standards Track document.

and the Standards Track boilerplate omits the sentence
] 
]  Not all documents approved by the IESG are a candidate for any level
]  of Internet Standard; see Section 2 of RFC 5741.

replacing it with
] 
]  Further information on Internet Standards is available in Section 2
]  of RFC 5741.

   (In fact, the IESG review is quite different for these categories.)

   We see that all these categories state, "It represents the consensus
of the IETF community." In fact, if there is an easy way to tell from
the published RFC whether an Informational RFC represents an individual
contribution or a Working Group output, it escapes me at the moment. :^(

   Thus perhaps Ted and Dave are right to hold this draft to a high
"consensus of the IETF community" standard.

   I just wish that were not so...

--
John Leslie <john@jlc.net>

From chair@ietf.org  Mon Oct  7 15:35:08 2013
Return-Path: <chair@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 7C4D321E80C7; Mon,  7 Oct 2013 15:35: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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUhRXeKK+UKf; Mon,  7 Oct 2013 15:35:03 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 7029421E8212; Mon,  7 Oct 2013 15:35:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 4B7C3A61F0; Mon,  7 Oct 2013 15:34:35 -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 OW4GUH4SRsmE; Mon,  7 Oct 2013 15:34:35 -0700 (PDT)
Received: from [10.30.0.144] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 6C1D1A61D2; Mon,  7 Oct 2013 15:34:34 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Montevideo statement
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 8 Oct 2013 01:34:58 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
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
Reply-To: "ietf@ietf.org list" <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, 07 Oct 2013 22:35:08 -0000

I wanted to send a link to a statement that Russ and I signed as a part =
of a meeting that we held last week with the leaders of other Internet =
organisations.

=
http://www.internetsociety.org/news/montevideo-statement-future-internet-c=
ooperation

Jari Arkko
IETF Chair


From bortzmeyer@nic.fr  Mon Oct  7 15:51:48 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363FE11E817F for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 15:51:48 -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 1jHOsUk-bieh for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 15:51:46 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) by ietfa.amsl.com (Postfix) with ESMTP id 9FAE211E817E for <ietf@ietf.org>; Mon,  7 Oct 2013 15:51:42 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id D9CE53ACF0; Mon,  7 Oct 2013 22:51:40 +0000 (UTC)
Received: by tyrion (Postfix, from userid 1000) id 8EA0BF0080E; Mon,  7 Oct 2013 15:51:29 -0700 (MST)
Date: Mon, 7 Oct 2013 15:51:29 -0700
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Montevideo statement
Message-ID: <20131007225129.GA572@laperouse.bortzmeyer.org>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 13.04 (raring)
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: Mon, 07 Oct 2013 22:51:48 -0000

On Tue, Oct 08, 2013 at 01:34:58AM +0300,
 IETF Chair <chair@ietf.org> wrote 
 a message of 10 lines which said:

> I wanted to send a link to a statement that Russ and I signed as a part of a meeting that we held last week with the leaders of other Internet organisations.
> 
> http://www.internetsociety.org/news/montevideo-statement-future-internet-cooperation

> They expressed strong concern over the undermining of the trust and
> confidence of Internet users globally due to recent revelations of
> pervasive monitoring and surveillance.

This wording is surprising. It looks like it is the revelations that
undermined confidence, and not the NSA actions. I would prefer
something like, to avoid shooting the messenger:

They expressed strong concern over the undermining of the trust and
confidence of Internet users globally, due to pervasive monitoring and
surveillance by powerful actor(s). 

From jari.arkko@piuha.net  Mon Oct  7 16:05:16 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 28ABF21E80CF for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 16:05:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 UIrKtMg47IRX for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 16:05:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD8C21E80D0 for <ietf@ietf.org>; Mon,  7 Oct 2013 16:05:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DDD052CC5F; Tue,  8 Oct 2013 02:05: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 2ow1Hu0IH7Lw; Tue,  8 Oct 2013 02:05: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 6A3A12CC48; Tue,  8 Oct 2013 02:05:09 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Montevideo statement
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20131007225129.GA572@laperouse.bortzmeyer.org>
Date: Tue, 8 Oct 2013 02:05:09 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
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, 07 Oct 2013 23:05:16 -0000

>=20
> This wording is surprising. It looks like it is the revelations that
> undermined confidence, and not the NSA actions. I would prefer
> something like, to avoid shooting the messenger:

Of course :-) We meant that the loss of privacy causes concern, not the =
revelations.

Jari


From john@jlc.net  Mon Oct  7 16:23:32 2013
Return-Path: <john@jlc.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 AF01021E80E8; Mon,  7 Oct 2013 16:23:27 -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=[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 nB7jx7WeYaj1; Mon,  7 Oct 2013 16:23:20 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1C73221F856A; Mon,  7 Oct 2013 16:23:17 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id C6138C94BF; Mon,  7 Oct 2013 19:23:14 -0400 (EDT)
Date: Mon, 7 Oct 2013 19:23:14 -0400
From: John Leslie <john@jlc.net>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
Message-ID: <20131007232314.GC48229@verdi>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
User-Agent: Mutt/1.4.1i
Cc: IESG <iesg@ietf.org>, Ted Hardie <ted.ietf@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: Mon, 07 Oct 2013 23:23:33 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:
> On Oct 7, 2013, at 3:34 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> So I'd like to dispute Ted's point that by publishing a version of
>> resnick-on-consensus as an RFC, we will engrave its contents in stone.
>> If that's the case, we have an even deeper problem than misunderstandings
>> of rough consensus.
> 
> Right, I think what Ted is describing is a BCP, not an Informational RFC.

   Oh my! I just saw the IESG agenda, and this _is_ proposed for BCP.

   I retract anything I said which might criticize Ted and/or Dave Crocker
for being too picky!

--
John Leslie <john@jlc.net>

From Aaron.Ding@cl.cam.ac.uk  Mon Oct  7 16:29:29 2013
Return-Path: <Aaron.Ding@cl.cam.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 A5AE721E811A; Mon,  7 Oct 2013 16:29:29 -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 07YZ0vFfnOaL; Mon,  7 Oct 2013 16:29:23 -0700 (PDT)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 577FC21E81CC; Mon,  7 Oct 2013 16:29:21 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:57761) by ppsw-42.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtp id 1VTKEq-0000P3-8h (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 00:29:20 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1VTKEq-0000yg-KN (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 00:29:20 +0100
Received: from s218i40.wolfson.cam.ac.uk ([131.111.218.40]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 08 Oct 2013 00:29:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 08 Oct 2013 00:29:20 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: ietf@ietf.org
Subject: year for highest number of IETF participants
Organization: Cambridge University
Message-ID: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.4
Cc: diversity@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Oct 2013 23:29:29 -0000

Hello,

Is there a pointer (maybe from IETF secretary)? The year with highest 
number of attendees - which one is that? The exact number of 
participants will be even better.

Thanks,
Aaron

From stpeter@stpeter.im  Mon Oct  7 16:32: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 DD95821E81D2; Mon,  7 Oct 2013 16:32: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=[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 z6X0oaHI+rHU; Mon,  7 Oct 2013 16:32:16 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7A121E80E6; Mon,  7 Oct 2013 16:32:16 -0700 (PDT)
Received: from sjc-vpn3-515.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 85DD5414C7; Mon,  7 Oct 2013 17:38:08 -0600 (MDT)
Message-ID: <52534471.4050302@stpeter.im>
Date: Mon, 07 Oct 2013 17:32:01 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com> <20131007232314.GC48229@verdi>
In-Reply-To: <20131007232314.GC48229@verdi>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>, 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, 07 Oct 2013 23:32:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/7/13 5:23 PM, John Leslie wrote:
> Ted Lemon <ted.lemon@nominum.com> wrote:
>> On Oct 7, 2013, at 3:34 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>> 
>>> So I'd like to dispute Ted's point that by publishing a version
>>> of resnick-on-consensus as an RFC, we will engrave its contents
>>> in stone. If that's the case, we have an even deeper problem
>>> than misunderstandings of rough consensus.
>> 
>> Right, I think what Ted is describing is a BCP, not an
>> Informational RFC.
> 
> Oh my! I just saw the IESG agenda, and this _is_ proposed for BCP.

It might not be the first time that an IESG agenda has the wrong text
for intended status.

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/

iQIcBAEBAgAGBQJSU0RxAAoJEOoGpJErxa2p2wcQAIjahTLFEiIK31muEQTY+ure
Jx2ymwciHR/nhL/3GreeqBE6skMokaewsiBd4C1Umx/Gru3XmwGCgD5KBY/f729p
Nt45TosOrP0Vqg9+qD516tuwDb+sUkTGws0AMoxbvSaz2NkDqgtfsUrY5U/+wZve
v7+hNgqzfxCxEw7cjK7e8lK8RKRLk41Qyo3n1VhQhReEzJ7sNLGNzvZ3bwcHGE7A
0FrW8IV+SFaUWQJ6CTmlhFxxDyHjX84AjIje4P5RBaIuvTUUs7EorRYmI4YwmN3Z
AqJvtiipJ+S/8JZVLCZ1x0I81mC0wtVP4sCMYFOUgCnlCeS57rtX1U/PQyZbEJjo
18HeMaKGJoar8ZILwoH/R2K0gZcnA3B/DnRCtTXIM1FQaMrHKHb1e04BZBB53PEo
GG1qIfeGv0n71hs4rsnPW7ymZjEP+9UtjKb9dy926aiNasfGSvJOsIYgxzpfOEQX
UMTHj7ET2b59bvTiQjzK5KrvOlzyMWIiArox/AS7NcFbXbZgot+0C/q3fzr92kGm
uNYFzlz1wk22ChKYCTxIaZfZnZLJ4nMyTViZHk8jPBGriIY4ICt7sHSwajYMQ4Gr
TQY8NNGW5KibayIU1geP1Jbx4A8Ry8WQzYR8Zvkl9+JgHkZE1AbSs/PgvAIFZI+a
+B981ttjErcPGZyFBl01
=3AY7
-----END PGP SIGNATURE-----

From Aaron.Ding@cl.cam.ac.uk  Mon Oct  7 17:03:28 2013
Return-Path: <Aaron.Ding@cl.cam.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 02B6E21E80EC; Mon,  7 Oct 2013 17:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745,  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 3w-RHjIaDTBi; Mon,  7 Oct 2013 17:03:22 -0700 (PDT)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id C63EE21E80D0; Mon,  7 Oct 2013 17:03:21 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-1b.csi.cam.ac.uk ([131.111.9.33]:58343) by ppsw-42.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtp id 1VTKll-00076w-6X (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 01:03:21 +0100
Received: from [127.0.0.1] (helo=webmail.hermes.cam.ac.uk) by webmail-1b.csi.cam.ac.uk with esmtp id 1VTKlk-000VZc-V4 (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 01:03:21 +0100
Received: from s218i40.wolfson.cam.ac.uk ([131.111.218.40]) by webmail.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 08 Oct 2013 01:03:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 08 Oct 2013 01:03:20 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: ietf@ietf.org
Subject: Re: year for highest number of IETF participants
Organization: Cambridge University
In-Reply-To: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>
Message-ID: <d255463d26c1203c01526e0d35477005@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.4
Cc: diversity@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 00:03:28 -0000

Thanks for the pointer from Ray Pelletier.

It seems IETF-49 got the highest number - 2810.

2nd is IETF-46, 2379.

Cheers,
Aaron


On 08.10.2013 00:29, Aaron Yi DING wrote:
> Hello,
> 
> Is there a pointer (maybe from IETF secretary)? The year with highest
> number of attendees - which one is that? The exact number of
> participants will be even better.
> 
> Thanks,
> Aaron

From Ted.Lemon@nominum.com  Mon Oct  7 18:09:01 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 D4D7121E8102; Mon,  7 Oct 2013 18:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 6oQdJw4hSs1Y; Mon,  7 Oct 2013 18:08:55 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1199B21E80EC; Mon,  7 Oct 2013 18:08:55 -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 DSNKUlNbJUvLg0G2jY+VOg8JHUysezZ4Qfui@postini.com; Mon, 07 Oct 2013 18:08: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 8A4BA1B8237; Mon,  7 Oct 2013 18:08:53 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 848D6190061; Mon,  7 Oct 2013 18:08:53 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Oct 2013 18:08:53 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1811\))
Subject: Re: year for highest number of IETF participants
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>
Date: Mon, 7 Oct 2013 21:08:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
X-Mailer: Apple Mail (2.1811)
X-Originating-IP: [192.168.1.10]
Cc: diversity@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, 08 Oct 2013 01:09:02 -0000

On Oct 7, 2013, at 7:29 PM, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk> =
wrote:
> Is there a pointer (maybe from IETF secretary)? The year with highest =
number of attendees - which one is that? The exact number of =
participants will be even better.

Wasn't it in Berlin?   ISTR that we had a remarkably good attendance.   =
If not, it would have been probably the IETF in San Jose, quite some =
time ago.


From jabley@hopcount.ca  Mon Oct  7 18:37:45 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 398B621E80EC for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 18:37: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 OPRTBi83aCmD for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 18:37:44 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id AE97121E81B7 for <ietf@ietf.org>; Mon,  7 Oct 2013 18:37:41 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so7984225pdj.31 for <ietf@ietf.org>; Mon, 07 Oct 2013 18:37:36 -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; bh=Hi7d2jMoCTbZa+4G/4aSH2O6BKveKaNMMEWkqfyVNEg=; b=QLn8788DYLOxRbV/3se69oDYxr4VX5r597YhFEqhKTjHRKDLRr9CT4T3z4rGV5eJQx 9qajPI78Rch07ScKkyXMUG8L0O8cXWn74dL4jnHw8mjS2Eiw+XMLifULgtAJbi0ceYKL b4TliZvWYU0hy5RT9WLX4or4TrtdGqwBNt5BE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Hi7d2jMoCTbZa+4G/4aSH2O6BKveKaNMMEWkqfyVNEg=; b=lubyCjFu+XNw53DsVzWPhHiW78NDv+NXdxZ9ERI0vFxtQBStjLgnfI2pgrgP5XRpKV YZj4La4UiFMVCS4RC5nb7rFO5pf1ssh2eXM+ZwMFnvb9KGuxLxOR/4dOzE0yy8toYI9J K0mXQqx3sNYWq+Mf+xGCCWeX00+RH8ZrLJx3ovxkRMowqBekviYCbFymSY5ak4X3Jg1j zqNTlj+xb1UmURv8TiJfyXf5g7zszDq8boFsfaKwOBPVVyRTUUgs1/Dqn7QcODRrnRtl rUr7Z8BIxYJ8N4A3sKXJ1cKOXZ9rtnpivU9c6od4gQR7q1StwrZ0GXDxGFf3IwNBP4q9 ISgw==
X-Gm-Message-State: ALoCoQlgDB6irVHo9muIyBn37qFbaHonY8grPL3QaEnLs/9JFYaiKTWkn6EfW+ESZEJC/AgAkmqV
X-Received: by 10.68.162.5 with SMTP id xw5mr3788605pbb.71.1381196256116; Mon, 07 Oct 2013 18:37:36 -0700 (PDT)
Received: from static-219-138.meetings.nanog.org (static-219-138.meetings.nanog.org. [199.187.219.138]) by mx.google.com with ESMTPSA id im2sm36221950pbd.31.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 18:37:35 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: year for highest number of IETF participants
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com>
Date: Mon, 7 Oct 2013 18:37:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <72C88D25-6668-4086-8E50-7AA21C549113@hopcount.ca>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk> <F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: diversity@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, 08 Oct 2013 01:37:45 -0000

On 2013-10-07, at 18:08, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 7, 2013, at 7:29 PM, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk> =
wrote:
>> Is there a pointer (maybe from IETF secretary)? The year with highest =
number of attendees - which one is that? The exact number of =
participants will be even better.
>=20
> Wasn't it in Berlin?   ISTR that we had a remarkably good attendance.  =
 If not, it would have been probably the IETF in San Jose, quite some =
time ago.

Attendance numbers for the last 14 meetings are trivially available from =
the command-line (and figuring that out was about two minutes' work =
following a search for "ietf 87 attendance").

Berlin was the best-attended meeting in that period. And also the =
meeting with the most unexpectedly high ambient temperatures, although I =
have no science to back up that claim, just recurring nightmares.


Joe

[krill:~]% for n in $(jot 15 73); do=20
curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" | \
  awk -v n=3D${n} '/ registrations:/ { sub(/ registrations:.*$/, ""); =
sub(/^.*\>/, ""); print n, $0; }'
done
73 1111
74 1332
75 1230
76 1249
77 1350
78 1304
79 1337
80 1317
81 1244
82 1051
83 1529
84 1356
85 1351
86 1223
87 1585
[krill:~]%=20


From tony@att.com  Mon Oct  7 20:43:37 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 A0F9921E812A; Mon,  7 Oct 2013 20:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.645, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52KmbJZPxnLB; Mon,  7 Oct 2013 20:43:32 -0700 (PDT)
Received: from tlpi046.enaf.dadc.sbc.com (egssmtp01.att.com [144.160.112.12]) by ietfa.amsl.com (Postfix) with ESMTP id 776BD21E8128; Mon,  7 Oct 2013 20:43:30 -0700 (PDT)
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp01.att.com (8.14.4/8.14.4) with ESMTP id r983hTmI019866; Mon, 7 Oct 2013 22:43:29 -0500
Received: from [135.70.110.11] (vpn-135-70-110-11.vpn.swst.att.com[135.70.110.11]) by maillennium.att.com (mailgw1) with ESMTP id <20131008034327gw100q0g1oe> (Authid: tony); Tue, 8 Oct 2013 03:43:28 +0000
X-Originating-IP: [135.70.110.11]
Message-ID: <52537F5F.8070706@att.com>
Date: Mon, 07 Oct 2013 23:43:27 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
Subject: Re: year for highest number of IETF participants
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk> <d255463d26c1203c01526e0d35477005@cam.ac.uk>
In-Reply-To: <d255463d26c1203c01526e0d35477005@cam.ac.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: diversity@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, 08 Oct 2013 03:43:37 -0000

On 10/7/2013 8:03 PM, Aaron Yi DING wrote:
> Thanks for the pointer from Ray Pelletier.
>
> It seems IETF-49 got the highest number - 2810.
>
> 2nd is IETF-46, 2379.

For those wondering where to see a list of attendees by meeting, see

http://www.ietf.org/meeting/past.html

    Tony Hansen

From presnick@qti.qualcomm.com  Mon Oct  7 20:50:12 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 2C6D821E8128; Mon,  7 Oct 2013 20:50:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.641
X-Spam-Level: 
X-Spam-Status: No, score=-102.641 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 LNT5navwhCwp; Mon,  7 Oct 2013 20:50:08 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7CBEB21E8136; Mon,  7 Oct 2013 20:50:01 -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=1381204207; x=1412740207; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UCWkCklEteG74/InYawdznT1P/JnFZSbdkb5V+7JQEw=; b=k/KwDmcEmsIZNZ6ku+G/3hMZFOZRfCSNEkGcQcVaT8SmRsv9dmslXZOT s++FHqrMSIWBfbQnBqP5pSAslFOJChH7vba4w1yIqE2KjB/Jk8FEAlfPr QpvS3qC/HzSTLYQRHV48vQzzcdDttQtSNC2kK/M62merfoTzi5jWcgEt7 g=;
X-IronPort-AV: E=McAfee;i="5400,1158,7221"; a="53717124"
Received: from unknown (HELO ironmsg01-lv.qualcomm.com) ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 07 Oct 2013 20:49:54 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7221"; a="20799903"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Oct 2013 20:49:54 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Oct 2013 20:49:53 -0700
Message-ID: <525380DE.4080301@qti.qualcomm.com>
Date: Mon, 7 Oct 2013 22:49:50 -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: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and	Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>	<CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>	<52530CCF.8090605@gmail.com>	<F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com> <20131007232314.GC48229@verdi>
In-Reply-To: <20131007232314.GC48229@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>, 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, 08 Oct 2013 03:50:12 -0000

On 10/7/13 6:23 PM, John Leslie wrote:
>     Oh my! I just saw the IESG agenda, and this_is_  proposed for BCP.
>    

No, it's not. I'm just prolific this month. What you see on the agenda 
is draft-resnick-retire-std1, not this document. That one *is* for BCP, 
but draft-resnick-on-consensus isn't.

Remain calm. All is well.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From michael.scharf@alcatel-lucent.com  Tue Oct  8 02:48:00 2013
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCFE21E819F for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 02:48:00 -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 ajq8EtfW-0Ib for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 02:47:54 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id B7C4521E818C for <ietf@ietf.org>; Tue,  8 Oct 2013 02:47:51 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r989lmkA024275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 8 Oct 2013 04:47:50 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r989lmb6024032 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Tue, 8 Oct 2013 11:47:48 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 8 Oct 2013 11:47:48 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-trammell-ipfix-tcpcontrolbits-revision-04.txt>	(Revision of the tcpControlBits IPFIX Information Element) to	Informational RFC
Thread-Topic: Last Call: <draft-trammell-ipfix-tcpcontrolbits-revision-04.txt>	(Revision of the tcpControlBits IPFIX Information Element) to	Informational RFC
Thread-Index: AQHOw6qG6GqB/vKmikqKfyysqMhs25nqgdYw
Date: Tue, 8 Oct 2013 09:47:47 +0000
Message-ID: <655C07320163294895BBADA28372AF5D0D8EA2@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20131007221317.14968.99718.idtracker@ietfa.amsl.com>
In-Reply-To: <20131007221317.14968.99718.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 09:48:00 -0000

Hi all,

A small editorial nit: RFC 793, RFC3168 and RFC3540 (which is experimental,=
 BTW) all classify bits 3,4,5 in octets 13 and 14 of the TCP header as "Res=
erved".

In the information element according to this draft, the corresponding bits =
are named "Future Use", with the reference "per the definition of the bits =
in the TCP header [RFC0793]". Strictly speaking, this terminology differs s=
lightly to RFC 793 and the very well-known figure depicting the TCP header.
=20
For whatever it is worth, I suggest to better explain the different wording=
. For instance, instead of ...

      Each of the three future use bits (0x800, 0x400, and 0x200) should
      be exported as observed in the TCP headers of the packets of this
      Flow, as they may be used subsequent to a future update of
      [RFC0793].

... an alternative wording better reflecting the exact header definition in=
 RFC 793 could be:

      Each of the three future use bits (0x800, 0x400, and 0x200) should
      be exported as observed in the TCP headers of the packets of this
      Flow, which are reserved for future use in [RFC0793].

Best regards

Michael
=20

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Tuesday, October 08, 2013 12:13 AM
> To: IETF-Announce
> Subject: Last Call: <draft-trammell-ipfix-tcpcontrolbits-revision-
> 04.txt> (Revision of the tcpControlBits IPFIX Information Element) to
> Informational RFC
>=20
>=20
> The IESG has received a request from an individual submitter to
> consider
> the following document:
> - 'Revision of the tcpControlBits IPFIX Information Element'
>   <draft-trammell-ipfix-tcpcontrolbits-revision-04.txt> as
> Informational
> RFC
>=20
> 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-11-04. 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.
>=20
> Abstract
>=20
>=20
>    This document revises the tcpControlBits IPFIX Information Element
> as
>    originally defined in [RFC5102] to reflect changes to the TCP Flags
>    header field since [RFC0793].
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-trammell-ipfix-tcpcontrolbits-
> revision/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-trammell-ipfix-tcpcontrolbits-
> revision/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20


From gonzalo.camarillo@ericsson.com  Tue Oct  8 02:49:45 2013
Return-Path: <gonzalo.camarillo@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 2100121E819A; Tue,  8 Oct 2013 02:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.793
X-Spam-Level: 
X-Spam-Status: No, score=-105.793 tagged_above=-999 required=5 tests=[AWL=0.456, 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 nkbANdJizGKF; Tue,  8 Oct 2013 02:49:38 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8B021E8192; Tue,  8 Oct 2013 02:49:37 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-6e-5253d5307347
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 59.09.03802.035D3525; Tue,  8 Oct 2013 11:49:37 +0200 (CEST)
Received: from [147.214.22.155] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.2.328.9; Tue, 8 Oct 2013 11:48:04 +0200
Message-ID: <5253D4D4.2030407@ericsson.com>
Date: Tue, 8 Oct 2013 11:48:04 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Piling on [Gen-art] Gen-ART review of draft-kaplan-insipid-session-id-03.txt
References: <201309041941.r84Jfm7H004331@rcdn-core-1.cisco.com> <52319BD8.2080106@ericsson.com> <52333BBE.6020706@nostrum.com> <D85334BB1373A34AA5FF84F9A623928A1F030C7D@xmb-rcd-x04.cisco.com> <523C0CCF.1050506@ericsson.com>
In-Reply-To: <523C0CCF.1050506@ericsson.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+Jvra7h1eAggxUruS32/F3EbjF3ip/F p02fmC1m/JnIbPFs43wWB1aPKb83snosWfKTyWPWzicsHh+f3mIJYInisklJzcksSy3St0vg ylhx5AhzQb94Re+ZySwNjFeFuhg5OSQETCTurLrIBmGLSVy4tx7I5uIQEjjMKDHhyhomCGc1 o8Tdv9cYQap4BbQlJi8/zAxiswioSEzv3gjWzSZgIbHl1n0WEFtUIEpiw/YLLBD1ghInZz4B sjk4RAT0JI7e4wSZySzQyyix5tFSVpAaYYFIiTXP3rJCLLvPKNHw5z8TSIJTQEfiyM2bUOdJ Smx50c4OYjMDDZpytYURwpaX2P52DthBQkDHLX/WwjKBUWgWkt2zkLTMQtKygJF5FSN7bmJm Tnq50SZGYHgf3PJbdQfjnXMihxilOViUxHk/vHUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp 1cDY9mZ5sdQqzgY+m617q0S2aa6QWNp8al7aYfVwdvunsnllNyTu3XRn1dK1Oqq848ic9++M /Zb1V3By9+RnOK3Ik0tW2am8O3d30/GirBZHHTfr2yVVe9/8rlzYeOMp586uE7svWx/2VJ4n dLqvsUEheMPRwIzCRXavV9SaabLVp7902XVS9rISS3FGoqEWc1FxIgCXX/DiPQIAAA==
Cc: The IESG <iesg@ietf.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, 08 Oct 2013 09:49:45 -0000

Hi Hadriel,

the additional IPR disclosure is already out. Could you please revise
the draft per my email below so that I can IETF LC it again?

Thanks,

Gonzalo

On 20/09/2013 10:52 AM, Gonzalo Camarillo wrote:
> Hi Hadriel,
> 
> to summarize the status of this IETF LC, we are still expecting (at
> least) an additional IPR disclosure on this draft (as announced on the
> INSIPID list). When that happens, I will IETF LC it again.
> 
> In the mean time, we need to address the comments related to the IANA
> registration the draft requests. I have discussed with the expert
> reviewer (Adam) and adding something along these lines would help:
> 
> "This registration is intended to be temporary. The authors expect that
> a standards-track definition of Session-ID will be published at a future
> date. Assuming such a document is published, it will replace this
> registration with a reference to itself, at which point this document
> will no longer be referenced by IANA."
> 
> You have also received a review from the OPS directorate and I do not
> think that has been addressed so far.
> 
> So, while we are waiting for the IPR disclosure, please go ahead and
> revise the draft.
> 
> Thanks,
> 
> Gonzalo
> 
> On 13/09/2013 6:40 PM, Gonzalo Salgueiro (gsalguei) wrote:
>>
>>> Here's what I do feel strongly about: whatever the plan of record needs to be clearly recorded in a place that people will find it. If draft-kaplan registers Session-ID, we need two changes to the existing documents: First, draft-kaplan needs to be crystal clear about the plan of record its section 10 (e.g., "This registration is intended to be temporary, and should be removed when [draft-ietf-insipid-...] is published.")  Secondly, draft-ietf-insipid must clearly state that its IANA registration *removes* the old reference and *completely* replaces it with a pointer to the standards-track document.
>>
>> Fully agree.
>>>
>>> The situation that I want to ensure cannot happen is an IANA-registered SIP header field that points to two documents simultaneously, especially if the ABNF is not absolutely identical between the two documents.
>>
>> The reality is that the backwards compatibility between the INSIPID Sess-ID mechanism and the kaplan draft is still undetermined and we cannot yet make a definitive statement on how it will look.  Assuming the Session-ID header field is (re-)used, the ABNF can't be identical because the session identifier used for INSIPID MUST address requirements that the kaplan id does not meet; so construction of the id will be different.  At this point the most that can be said is that one won't break the other (through non-intersection like using different header field names, etc.) or through direct backwards compatibility (same header field name but the INSIPID with expanded ABNF that plays nice with the kaplan id).
>>
>> Cheers,
>>
>> Gonzalo
>>
>>>
>>> /a
>>
>>
> 


From gonzalo.camarillo@ericsson.com  Tue Oct  8 02:54:32 2013
Return-Path: <gonzalo.camarillo@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 8452411E8173 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 02:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.843
X-Spam-Level: 
X-Spam-Status: No, score=-105.843 tagged_above=-999 required=5 tests=[AWL=0.406, 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 wqhJg7yagG3i for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 02:54:25 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 91BF021E81F5 for <ietf@ietf.org>; Tue,  8 Oct 2013 02:54:07 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-e8-5253d63ee91c
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 5A.F9.03802.E36D3525; Tue,  8 Oct 2013 11:54:07 +0200 (CEST)
Received: from [147.214.22.155] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.2.328.9; Tue, 8 Oct 2013 11:54:06 +0200
Message-ID: <5253D63E.4010000@ericsson.com>
Date: Tue, 8 Oct 2013 11:54:06 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: IPR disclosure for draft-kaplan-insipid-session-id
References: <201309041941.r84Jfm7H004331@rcdn-core-1.cisco.com> <52319BD8.2080106@ericsson.com> <52333BBE.6020706@nostrum.com> <D85334BB1373A34AA5FF84F9A623928A1F030C7D@xmb-rcd-x04.cisco.com> <523C0CCF.1050506@ericsson.com> <6.2.5.6.2.20130920220323.0b677040@resistor.net>
In-Reply-To: <6.2.5.6.2.20130920220323.0b677040@resistor.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprILMWRmVeSWpSXmKPExsUyM+Jvra79teAgg5n/uS2ebZzPYnF8wyF2 ByaPJUt+Mnm8737GFsAUxWWTkpqTWZZapG+XwJXxY0UPW0GLcMWP2R3sDYyL+bsYOTkkBEwk nn1+xgxhi0lcuLeerYuRi0NI4DCjxMlPX9lAEkICqxklzl1IBLF5BbQlFnZvBouzCKhILF/2 G6yZTcBCYsut+ywgtqhAlMSG7RdYIOoFJU7OfAJmiwhISOzduJIJxGYWEJZ4t242WFxYwF7i 6a0DUIsnMEl83HqGHSTBKWAr0fjqITvEdZISW160s0M060lMudrCCGHLS2x/O4cZ4lBtieXP WlgmMArNQrJ7FpKWWUhaFjAyr2Jkz03MzEkvN9rECAzWg1t+q+5gvHNO5BCjNAeLkjjvh7fO QUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYuSbWbuC+XizmkbNGLH/F1mDee4/f6qtt6ntw VCL5TMXMsuIN4VU5Im/Z2AQunrrmmqXVv+uZhL5Nzv556q02vlbrnvzb0psn0Tqzmn9Lkkna 57C1q/ScGy71rMtmFQtW432qbsFiI9zyO+WDpmrCikC5pnei5TcL3y0LVlUvklVR9v/1LE+J pTgj0VCLuag4EQCSIA2kJAIAAA==
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, 08 Oct 2013 09:54:33 -0000

Hi,

these disclosures were already made long ago against the WG's drafts.
So, the WG has been very much aware of them for a long time and they
have been discussed several times in the face-to-face meetings. Some of
the comments during the chartering of INSIPID actually related to the
knowledge of well-known existing IPR in that particular area.

The disclosures were just not updated in time to reflect their
applicability to this new draft. Now they have been updated and we will
re-IETF LC the draft so that everybody is on the same page.

Cheers,

Gonzalo


On 21/09/2013 7:29 AM, SM wrote:
> Hello,
> At 01:52 20-09-2013, Gonzalo Camarillo wrote:
>> to summarize the status of this IETF LC, we are still expecting (at
>> least) an additional IPR disclosure on this draft (as announced on the
>> INSIPID list). When that happens, I will IETF LC it again.
> 
> There was a discussion about IPR on this mailing list but nobody
> mentioned RFC 6701 or RFC 6702.  It is a mystery why the IETF cannot
> remember the (Informational) RFCs it published one year ago.
> 
> There was a Last Call for draft-kaplan-insipid-session-id-03 (
> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg11753.html
> ).  The announcement did not mention any IPR disclosure.  Does the above
> qualify as a late disclosure?
> 
>> In the mean time, we need to address the comments related to the IANA
>> registration the draft requests. I have discussed with the expert
>> reviewer (Adam) and adding something along these lines would help:
>>
>> "This registration is intended to be temporary. The authors expect that
>> a standards-track definition of Session-ID will be published at a future
>> date. Assuming such a document is published, it will replace this
>> registration with a reference to itself, at which point this document
>> will no longer be referenced by IANA."
> 
> draft-ietf-insipid-session-id-02 is a WG document intended as a Proposed
> Standard.  The INSIPID charter mentions a milestone for February 2013. 
> It would be good if the IESG takes into consideration the overhead of
> getting this temporary assignment published as an IETF RFC.  The reason
> given for publication was that 3GPP has tight deadlines.  It is
> understandable that there can be delays in reaching a milestone.  What
> is the INSIPID WG estimate for that future date?
> 
> Regards,
> -sm 
> 


From chris.dearlove@baesystems.com  Tue Oct  8 03:27:29 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 6902321E81D0 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 03:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.289
X-Spam-Level: 
X-Spam-Status: No, score=-10.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 GRpwDGENNqfc for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 03:27:25 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 8F89521E81D7 for <ietf@ietf.org>; Tue,  8 Oct 2013 03:27:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1056,1371078000"; d="scan'208";a="379096339"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 08 Oct 2013 11:27:21 +0100
X-IronPort-AV: E=Sophos;i="4.90,1056,1371078000"; d="scan'208";a="29283500"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasmds017.greenlnk.net with ESMTP; 08 Oct 2013 11:27:21 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.02.0328.009; Tue, 8 Oct 2013 11:27:21 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: "mrex@sap.com" <mrex@sap.com>
Subject: RE: Review of: draft-resnick-on-consensus-05
Thread-Topic: Review of: draft-resnick-on-consensus-05
Thread-Index: AQHOw6B81fd7xbhRnkG92GEx0rmPUpnqmFuA
Date: Tue, 8 Oct 2013 10:27:20 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF731F@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBF6FAE@GLKXM0002V.GREENLNK.net> <20131007205629.CF5801A9E1@ld9781.wdf.sap.corp>
In-Reply-To: <20131007205629.CF5801A9E1@ld9781.wdf.sap.corp>
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: Pete Resnick <presnick@qti.qualcomm.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, 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: Tue, 08 Oct 2013 10:27:29 -0000

I wasn't making any suggestion about what we should be doing. My sole point=
 was that as the language differs, we should be aware of that and word acco=
rdingly, i.e. not use phrases like "simple majority" to mean 51%, as it may=
 not.

-- =

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: Martin Rex [mailto:mrex@sap.com] =

Sent: 07 October 2013 21:56
To: Dearlove, Christopher (UK)
Cc: dcrocker@bbiw.net; Pete Resnick; IETF Discussion
Subject: Re: Review of: draft-resnick-on-consensus-05

----------------------! 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.
--------------------------------------------------------

Dearlove, Christopher (UK) wrote:
> dcrocker@bbiw.net
>>
>> From what you've written, your basic point seems to be that 51% isn't =

>> enough; it's worth making that explicit.
> =

> To add to the confusion, and to emphasise the point about making clear,
> British and American English differ here. If three proposals (not the
> most common case, I agree, but it can happen) have 45%, 35% and 20%
> of the votes, the first of these has a majority, sometimes emphasised
> as simple majority, in British English. (We do not - to our loss - use
> the word plurality. Just 51% is given the strong term absolute majority.)
> I haven't checked the context here, but saying not just a simple
> majority might suggest to a British English user that 51% is enough.


Voting as is done in elections for political parties is often going
to produce a political result, a personal preference of a few rather
than an engineering solution that adequately addresses the concerns
of the community at large.


What we could do in the IETF, is not just trying to pick the lesser evil,
but rather use the _engineering_ skills to modify and/or merge proposals
to increase the number of folks that support the result and reduce
the amount of folks that object the result.


With your example of three competing proposals: A, B and C, and by couting
"votes" the WG chair determine support of 45%, 35% and 20% respectively,
does this mean that A has signficant support?   Not at all.  It could be
that the folks who voted for B and C did so because they are both strongly
opposed to A.

A WG chair who wants to be neutral on the decision should probably not
just call:
   which of the three proposals do you prefer:  A, B or C

and perform political inferences on the result, but rather
_ask_ the engineers direclty:

   if we were to select A, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for A?

   if we were to select B, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for B?

   if we were to select C, would you "support it, are neutral, are opposed"
     if you're either neutral or opposed to A, what change(s) to A would
     make you supportive for C?


I've seen a few "WG consensus calls" which appeared somewhat skewed/biased
to me towards exclusing specific outcomes.  I do _not_ know whether this
was causes by malicous intent or just accidental / not sufficiently well
thought out.  I'm OK with a leadership decision, but leadership decisions
should not be exerted early in the process by preventing certain questions
to get asked at all.  =


How well the process works can be seen by how objections are resolved.
Are objections handled by spin doctors, or by engineers that are open
to improvements of their work.


-Martin

********************************************************************
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 ynir@checkpoint.com  Tue Oct  8 03:52:46 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 B72FC21E81F6 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 03:52:46 -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 fanYCFh5jrcw for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 03:52:41 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 82A1521E81DF for <ietf@ietf.org>; Tue,  8 Oct 2013 03:52:38 -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 r98AqDDI004831; Tue, 8 Oct 2013 13:52:13 +0300
X-CheckPoint: {5253E3DD-A-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.92]) by DAG-EX10.ad.checkpoint.com ([169.254.3.173]) with mapi id 14.02.0347.000; Tue, 8 Oct 2013 13:52:09 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "<mrex@sap.com>" <mrex@sap.com>
Subject: Re: Review of: draft-resnick-on-consensus-05
Thread-Topic: Review of: draft-resnick-on-consensus-05
Thread-Index: AQHOw6CPswScLHnVakGZTPS2j6URtpnqb1kA
Date: Tue, 8 Oct 2013 10:52:09 +0000
Message-ID: <A1E383F4-3DCF-4324-8967-60274255F9FB@checkpoint.com>
References: <20131007205629.CF5801A9E1@ld9781.wdf.sap.corp>
In-Reply-To: <20131007205629.CF5801A9E1@ld9781.wdf.sap.corp>
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
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C4666BB2AA2A7749B8A8CE0946AAB8A8@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, 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: Tue, 08 Oct 2013 10:52:46 -0000

On Oct 7, 2013, at 11:56 PM, Martin Rex <mrex@sap.com> wrote:

> Dearlove, Christopher (UK) wrote:
>> dcrocker@bbiw.net
>>>=20
>>> From what you've written, your basic point seems to be that 51% isn't=20
>>> enough; it's worth making that explicit.
>>=20
>> To add to the confusion, and to emphasise the point about making clear,
>> British and American English differ here. If three proposals (not the
>> most common case, I agree, but it can happen) have 45%, 35% and 20%
>> of the votes, the first of these has a majority, sometimes emphasised
>> as simple majority, in British English. (We do not - to our loss - use
>> the word plurality. Just 51% is given the strong term absolute majority.=
)
>> I haven't checked the context here, but saying not just a simple
>> majority might suggest to a British English user that 51% is enough.
>=20
>=20
> Voting as is done in elections for political parties is often going
> to produce a political result, a personal preference of a few rather
> than an engineering solution that adequately addresses the concerns
> of the community at large.
>=20
>=20
> What we could do in the IETF, is not just trying to pick the lesser evil,
> but rather use the _engineering_ skills to modify and/or merge proposals
> to increase the number of folks that support the result and reduce
> the amount of folks that object the result.
>=20
>=20
> With your example of three competing proposals: A, B and C, and by coutin=
g
> "votes" the WG chair determine support of 45%, 35% and 20% respectively,
> does this mean that A has signficant support?   Not at all.  It could be
> that the folks who voted for B and C did so because they are both strongl=
y
> opposed to A.
>=20
> A WG chair who wants to be neutral on the decision should probably not
> just call:
>   which of the three proposals do you prefer:  A, B or C
>=20
> and perform political inferences on the result, but rather
> _ask_ the engineers direclty:
>=20
>   if we were to select A, would you "support it, are neutral, are opposed=
"
>     if you're either neutral or opposed to A, what change(s) to A would
>     make you supportive for A?
>=20
>   if we were to select B, would you "support it, are neutral, are opposed=
"
>     if you're either neutral or opposed to A, what change(s) to A would
>     make you supportive for B?
>=20
>   if we were to select C, would you "support it, are neutral, are opposed=
"
>     if you're either neutral or opposed to A, what change(s) to A would
>     make you supportive for C?

I think in this case the WG chair should do something different. A better q=
uestion would be:

  Which is worse? To decide on *any* of these 3 proposals, or to keep debat=
ing this for another few months?

At that point you might get something like
    - Just choose any of them - 90%
    - No, we need to choose the right one - 10%

But percentages don't really matter. You get the people who are in the 10% =
(1-3 in most working groups) and get them to the mic or mailing list and as=
k them what is so terrible about proposal A (or B or C, whichever one or tw=
o they really object to) that it's better to delay the process by some extr=
a months. That gets the objections that are really worth discussing.=20

If you can get those objections ironed out so that there's consensus (rough=
 or not) for the assertion that "Any of them is better than not proceeding"=
, the selection can proceed by any method that seems fair: majority, coin t=
oss, 3-way Rechambeau ([1]), shortest document.

Yoav

[1] http://tools.ietf.org/html/draft-harkins-rochambeau-02


From michawe@ifi.uio.no  Tue Oct  8 04:56:41 2013
Return-Path: <michawe@ifi.uio.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89F2021E81EB for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 04:56: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=[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 8n-KL5NrHR1L for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 04:56:35 -0700 (PDT)
Received: from mail-out2.uio.no (mail-out2.uio.no [IPv6:2001:700:100:10::58]) by ietfa.amsl.com (Postfix) with ESMTP id 8B19421E80FD for <ietf@ietf.org>; Tue,  8 Oct 2013 04:56:31 -0700 (PDT)
Received: from mail-mx6.uio.no ([129.240.10.40]) by mail-out2.uio.no with esmtp (Exim 4.75) (envelope-from <michawe@ifi.uio.no>) id 1VTVtt-0006Yv-3y for ietf@ietf.org; Tue, 08 Oct 2013 13:56:29 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx6.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1VTVts-0000Hr-IL for ietf@ietf.org; Tue, 08 Oct 2013 13:56:29 +0200
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_97E52895-1EB9-4487-B895-F40FDC8171FD"
Subject: Call for participation: Transport Services
Date: Tue, 8 Oct 2013 13:56:28 +0200
Message-Id: <7A00A580-79CA-485D-967D-1111D7B9DF0C@ifi.uio.no>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 13 msgs/h 7 sum rcpts/h 16 sum msgs/h 8 total rcpts 8232 max rcpts/h 40 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.05, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: B9FAFC629E7D79D6B628582E9915881A203F0E74
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -59 maxlevel 80 minaction 2 bait 0 mail/h: 7 total 3216 max/h 16 blacklist 0 greylist 0 ratelimit 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, 08 Oct 2013 11:56:41 -0000

--Apple-Mail=_97E52895-1EB9-4487-B895-F40FDC8171FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear all,

Sorry if you receive multiple copies of this! I sent it to all the lists =
with potentially interested folks...  (this should be okay to do =
according to RFC5434, which says "various mailing lists").

A community of interest is being formed to gauge whether there is =
sufficient interest to host a BOF at the London IETF, on the topic of =
"Transport Services". The intention is to create a WG that would define =
the set of services that transport protocols offer to applications, such =
that applications could at some point in the future request a service, =
not a protocol. This could foster innovation (protocols could be tried =
out, with a fall-back, without requiring the application programmer to =
include such functionality); it could also give more freedom to whatever =
resides below the API to automatically make the best out of what it =
currently has available.

If you're interested in this problem space, please visit the related =
webpage that I have set up:
https://sites.google.com/site/transportprotocolservices/
There you'll find an initial stab at a charter and all information about =
the mailing list - please join us and participate in discussions! =
Thanks!

Cheers,
Michael


--Apple-Mail=_97E52895-1EB9-4487-B895-F40FDC8171FD
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; =
"><div>Dear all,</div><div><br></div><div>Sorry if you receive multiple =
copies of this! I sent it to all the lists with potentially interested =
folks... &nbsp;(this should be okay to do according to RFC5434, which =
says "various mailing lists").</div><div><br></div><div>A community of =
interest is being formed to gauge whether there is sufficient interest =
to host a BOF at the London IETF, on the topic of "Transport Services". =
The intention is to create a WG that would define the set of services =
that transport protocols offer to applications, such that applications =
could at some point in the future request a service, not a protocol. =
This could foster innovation (protocols could be tried out, with a =
fall-back, without requiring the application programmer to include such =
functionality); it could also give more freedom to whatever resides =
below the API to automatically make the best out of what it currently =
has available.</div><div><br></div><div>If you're interested in this =
problem space, please visit the related webpage that I have set =
up:</div><div><a =
href=3D"https://sites.google.com/site/transportprotocolservices/">https://=
sites.google.com/site/transportprotocolservices/</a></div><div>There =
you'll find an initial stab at a charter and all information about the =
mailing list - please join us and participate in discussions! =
Thanks!</div><div><br></div><div>Cheers,</div><div>Michael</div><div><br><=
/div></body></html>=

--Apple-Mail=_97E52895-1EB9-4487-B895-F40FDC8171FD--

From hallam@gmail.com  Tue Oct  8 05:24:52 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 78AF321E8198 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:24: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, 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 5oaoeqyJA57R for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:24:51 -0700 (PDT)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id BB4AA21E808A for <ietf@ietf.org>; Tue,  8 Oct 2013 05:24:50 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id ec20so6958089lab.0 for <ietf@ietf.org>; Tue, 08 Oct 2013 05:24: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=70oaGPLxKRNKK1mqt8kJVkR3qhpTQvVXSG86/HgETQQ=; b=UcAzxc1mHOuNS0sc+I4H+juogAR/Cerc1AFKoM1YGGAD3KiXHKiy67t12F8lLaHW8x gRKJKa/esntGYtktTRsCY3jgej6yoldzXgphfzzOlkp4f9oyp5c7NWbQxrxZYvZlGiCK 9dBwF5GmKMmLgF3W++CJ4ie0nEU0XGrV6XmOJaoUiQRWE5ZW4mMfGktMCctpJ+ZsNf1q ZuS7PChznHEzkcAwcTUcoto5T+QHxen34TcJPnDrXiXbRGqai8ed2Lr5qtISWOALDQdA Kpp92co2nmD4nn4b2pcUEtkQxL730rQugQ7tjYBi/VW0kIWFuHl77SXmlJtZtGbLDm44 d+Rw==
MIME-Version: 1.0
X-Received: by 10.152.120.37 with SMTP id kz5mr1112077lab.21.1381235089433; Tue, 08 Oct 2013 05:24:49 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 8 Oct 2013 05:24:49 -0700 (PDT)
In-Reply-To: <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net>
Date: Tue, 8 Oct 2013 08:24:49 -0400
Message-ID: <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
Subject: Re: Montevideo statement
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=089e01228148db697204e839dae8
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, 08 Oct 2013 12:24:52 -0000

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

On Mon, Oct 7, 2013 at 7:05 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> >
> > This wording is surprising. It looks like it is the revelations that
> > undermined confidence, and not the NSA actions. I would prefer
> > something like, to avoid shooting the messenger:
>
> Of course :-) We meant that the loss of privacy causes concern, not the
> revelations.
>

No, it is the revelations that cause concern.

Nobody is in the least concerned about the fact that the British government
and royal family has been replaced by a group of reptilian dopplegangers
apart from David Ike who is the only person who knows about it.

It is the actions that justify the concern but without the revelations
there is no concern.


The problem with the language used as I see it is that it is unfortunately
rather close to the language used by the establishment types who run round
telling us all not to worry our heads about what they are doing and we must
certainly not ever question their motives or intentions.

The reason I keep reminding people about the previous uses of the syncretic
power of GCHQ and the NSA is that they prove that we do need to keep
questioning their motives. For years people were dismissed as paranoid
leftist hippies for suggesting that the CIA installed a dictatorship in
Greece. And now it is known that exactly that happened.


In the same way, the idea that US government might attempt to use control
over ICANN or IANA for leverage has to be taken seriously. The question is
not whether Steve Crocker is comfortable with the situation, it is whether
the governance infrastructure is strong enough to prevent abuse over
centuries.

The US government is currently shut down because some folk in Congress are
trying to use the threat of a recession to deny access to health care to a
fifth of the population. It is certainly not inconceivable that a future
Congress would attempt to abuse control over ICANN is nonsense. It is a US
registered corporation subject to US law.

If nothing is done then sooner or later there will be some idiot on his
hind legs in the Senate talking for 21 hours demanding that Cuba or
Palestine be dropped out of the DNS root or be denied IPv6 allocations or
some equally stupid grandstanding demand designed to give him a platform on
which to run for higher office.


I think the US executive branch would be better rid of the control before
the vandals work out how to use it for mischief. But better would be to
ensure that no such leverage exists. There is no reason for the apex of the
DNS to be a single root, it could be signed by a quorum of signers (in
addition to the key splitting which I am fully familiar with). And every
government should be assigned a sovereign reserve of IPv6 addresses to
prevent a scarcity being used as leverage.

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

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

<div dir=3D"ltr">On Mon, Oct 7, 2013 at 7:05 PM, Jari Arkko <span dir=3D"lt=
r">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko=
@piuha.net</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">&gt;<br>
&gt; This wording is surprising. It looks like it is the revelations that<b=
r>
&gt; undermined confidence, and not the NSA actions. I would prefer<br>
&gt; something like, to avoid shooting the messenger:<br>
<br>
</div>Of course :-) We meant that the loss of privacy causes concern, not t=
he revelations.<br></blockquote><div><br></div><div>No, it is the revelatio=
ns that cause concern.</div><div><br></div><div>Nobody is in the least conc=
erned about the fact that the British government and royal family has been =
replaced by a group of reptilian dopplegangers apart from David Ike who is =
the only person who knows about it.</div>
<div><br></div><div>It is the actions that justify the concern but without =
the revelations there is no concern.<br></div><div><br></div><div><br></div=
><div>The problem with the language used as I see it is that it is unfortun=
ately rather close to the language used by the establishment types who run =
round telling us all not to worry our heads about what they are doing and w=
e must certainly not ever question their motives or intentions.</div>
<div><br></div><div>The reason I keep reminding people about the previous u=
ses of the syncretic power of GCHQ and the NSA is that they prove that we d=
o need to keep questioning their motives. For years people were dismissed a=
s paranoid leftist hippies for suggesting that the CIA installed a dictator=
ship in Greece. And now it is known that exactly that happened.</div>
<div><br></div><div><br></div><div>In the same way, the idea that US govern=
ment might attempt to use control over ICANN or IANA for leverage has to be=
 taken seriously. The question is not whether Steve Crocker is comfortable =
with the situation, it is whether the governance infrastructure is strong e=
nough to prevent abuse over centuries.</div>
<div><br></div><div>The US government is currently shut down because some f=
olk in Congress are trying to use the threat of a recession to deny access =
to health care to a fifth of the population. It is certainly not inconceiva=
ble that a future Congress would attempt to abuse control over ICANN is non=
sense. It is a US registered corporation subject to US law.</div>
<div><br></div><div>If nothing is done then sooner or later there will be s=
ome idiot on his hind legs in the Senate talking for 21 hours demanding tha=
t Cuba or Palestine be dropped out of the DNS root or be denied IPv6 alloca=
tions or some equally stupid grandstanding demand designed to give him a pl=
atform on which to run for higher office.</div>
<div><br></div><div><br></div><div>I think the US executive branch would be=
 better rid of the control before the vandals work out how to use it for mi=
schief. But better would be to ensure that no such leverage exists. There i=
s no reason for the apex of the DNS to be a single root, it could be signed=
 by a quorum of signers (in addition to the key splitting which I am fully =
familiar with). And every government should be assigned a sovereign reserve=
 of IPv6 addresses to prevent a scarcity being used as leverage.=A0</div>
<div><br></div></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>
</div></div>

--089e01228148db697204e839dae8--

From martin@millnert.se  Tue Oct  8 05:47:24 2013
Return-Path: <martin@millnert.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 B770011E81B9 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, 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 TaPvVX1PvITW for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:47:10 -0700 (PDT)
Received: from mail.millnert.se (unknown [95.80.32.84]) by ietfa.amsl.com (Postfix) with ESMTP id F014F21E809C for <ietf@ietf.org>; Tue,  8 Oct 2013 05:46:59 -0700 (PDT)
Received: from [172.25.90.101] (gw.ipnett.ideon.se [85.235.1.171]) by mail.millnert.se (Postfix) with ESMTPSA id 2ABC9167; Tue,  8 Oct 2013 14:48:44 +0200 (CEST)
Message-ID: <1381236415.19391.11.camel@galileo.millnert.se>
Subject: Re: Montevideo statement
From: Martin Millnert <martin@millnert.se>
To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Tue, 08 Oct 2013 14:46:55 +0200
In-Reply-To: <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-M4w6r5FHEEQPjiJq6iiJ"
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
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, 08 Oct 2013 12:47:24 -0000

--=-M4w6r5FHEEQPjiJq6iiJ
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Phillip,

On Tue, 2013-10-08 at 08:24 -0400, Phillip Hallam-Baker wrote:
> If nothing is done then sooner or later there will be some idiot on
> his hind legs in the Senate talking for 21 hours demanding that Cuba
> or Palestine be dropped out of the DNS root or be denied IPv6
> allocations or some equally stupid grandstanding demand designed to
> give him a platform on which to run for higher office.

This has already happened.  Some US-Israeli lobby thing asked RIPE NCC
in 2012 (IIRC) to stop economically support a by some nation states
blockaded Iran via removing its routing registration information and IP
assignments, etc. Not sure exactly how it went from there, but the
request was essentially ignored AFAIK.

The problem is not what happens when a lobbyist approaching on of these
bodies directly is ignored, but when said lobbyists persuades a legal
apparatus with standing, to make similarly ill-advised requests.
  Or to connect back to the Montevideo statement, how to manage a
globally cohesive One Internet without exposing it to the threat of
legal assault.  I.e. how to put the Internet above the law of any one
nation state, essentially.=20
 Today, a popular belief in Swedish "IGF" circles is "the law applies
equally to online as it does to offline" -- but this doesn't really
compile well for the Internet IMHO where we have 250 something different
laws, as it is absolutely fragmenting the Internet judicially speaking
to each nation state having some sort of power over its national
Internet segment...

IMHO, the Internet is a global communications fabric, transcending and
superseding individual nation states. Forcefully and offensively
removing someones access to it is a crime by any human standard.

/M

--=-M4w6r5FHEEQPjiJq6iiJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAABAgAGBQJSU/6/AAoJEKgraNdZrwxMziYP/jH1bJwOOaXtB4+ecfhEsRDi
R5/42jzUErCHNEW2jlnoO/RS62FocTE7Us0kjFQ0z22x8d70ILRI4knEGIvPV7pd
gZXKqUoieXGhbZWJarz9s2c5EMKjiB1n85hO960yzG6AOKV1hhocizS+IczSc0sn
pVqsed8dAmw5+uiLeKOgVvE9buQq8L8PcZpNn+0K8nBE9TP8C51DfofOT2svdTal
tPf8g9/XAVO1XpnVZPtxcdqA8oa1oahejMm7dEJfkF7cKMYil+mY4u134uJh4vQy
L5uH7prhq63/5AfRUy7UL18KqM7On7sr548Wdg0oZXmhp6TU9iFzpRSApVYCXP27
Hz87FruA7MAou+hSqJfYZTI7Q007ROcRKuUHTeDj8tMZSFeDI50I9PX/A1xar0AN
hF5j6mRrWYMEODBVyHJGCWn4irfoxpLusHYg1tTyragIXQaINpGVwHjBkdGN2vR3
js0wYaokTZeF/OSbG6nbLlFG5h/IcuefdZ6/Ks6Jmkkgrc+sBkDmqstwzIWfa26/
2WRsj4aQwE+7cZ/IuqcVqn9nUpn3v+/AWkYrmd1VSHl/eRhk1swy53h7jiiGJJa+
dCyvkvbe0B3PWcfUTr7HS7womrXucrlqdi/K5T4ChbsAcPreVMs4b6OdVbWKdZsT
gimmkBqOxVUiznBxdktp
=ixNi
-----END PGP SIGNATURE-----

--=-M4w6r5FHEEQPjiJq6iiJ--


From adrian@olddog.co.uk  Tue Oct  8 05:51:43 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 71E2F21E809C; Tue,  8 Oct 2013 05:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  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 e9wEoOGhsOCT; Tue,  8 Oct 2013 05:51:25 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD0521E818B; Tue,  8 Oct 2013 05:51:25 -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 r98CpMct013078;  Tue, 8 Oct 2013 13:51:22 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r98CpKAu013070 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Oct 2013 13:51:21 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joe Abley'" <jabley@hopcount.ca>, "'Ted Lemon'" <ted.lemon@nominum.com>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk>	<F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com> <72C88D25-6668-4086-8E50-7AA21C549113@hopcount.ca>
In-Reply-To: <72C88D25-6668-4086-8E50-7AA21C549113@hopcount.ca>
Subject: RE: year for highest number of IETF participants
Date: Tue, 8 Oct 2013 13:51:20 +0100
Message-ID: <044d01cec425$1756c680$46045380$@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: AQGfUJYDc6tnLO82x8sm9+0ae0jrSAIMVeE4A4Rw30CaHSGkMA==
Content-Language: en-gb
Cc: diversity@ietf.org, '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: Tue, 08 Oct 2013 12:51:43 -0000

Curiously these numbers do not match those at
https://www.ietf.org/meeting/past.html

Registration, we may conclude, does not equate to attendance.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joe
> Abley
> Sent: 08 October 2013 02:38
> To: Ted Lemon
> Cc: diversity@ietf.org; IETF
> Subject: Re: year for highest number of IETF participants
>
> [krill:~]% for n in $(jot 15 73); do
> curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" | \
>   awk -v n=${n} '/ registrations:/ { sub(/ registrations:.*$/, "");
sub(/^.*\>/, "");
> print n, $0; }'
> done
> 73 1111
> 74 1332
> 75 1230
> 76 1249
> 77 1350
> 78 1304
> 79 1337
> 80 1317
> 81 1244
> 82 1051
> 83 1529
> 84 1356
> 85 1351
> 86 1223
> 87 1585
> [krill:~]%


From bmanning@isi.edu  Tue Oct  8 05:55:20 2013
Return-Path: <bmanning@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 8EB7621E805F for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:55:20 -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=[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 3fyyG9Bx-sBQ for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 05:55:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id ADFAF11E81B5 for <ietf@ietf.org>; Tue,  8 Oct 2013 05:55:14 -0700 (PDT)
Received: from bondarenko-nb.intervale.ru ([156.106.233.80]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r98Crgr0016379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 05:53:53 -0700 (PDT)
Subject: Re: Montevideo statement
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: manning bill <bmanning@isi.edu>
In-Reply-To: <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
Date: Tue, 8 Oct 2013 05:53:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <10B2223B-CDCA-491A-BC53-45FD7E54A16E@isi.edu>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 08 Oct 2013 12:55:21 -0000

>=20
>=20
> I think the US executive branch would be better rid of the control =
before the vandals work out how to use it for mischief. But better would =
be to ensure that no such leverage exists. There is no reason for the =
apex of the DNS to be a single root, it could be signed by a quorum of =
signers (in addition to the key splitting which I am fully familiar =
with). And every government should be assigned a sovereign reserve of =
IPv6 addresses to prevent a scarcity being used as leverage.=20
>=20
> --=20
> Website: http://hallambaker.com/

	Quorum signing with split keys  was already built and tested in =
a root server operator testbed (the OTDR testbed) from 1998-2005.  It =
was considered more fragile than the current system.

/bill  =20=

From rlb@ipv.sx  Tue Oct  8 06:07:14 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 4B16421E8098 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.803
X-Spam-Level: 
X-Spam-Status: No, score=-2.803 tagged_above=-999 required=5 tests=[AWL=0.173,  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 Kndl1Q6WbKU2 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:07:10 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9BAE721E81C2 for <ietf@ietf.org>; Tue,  8 Oct 2013 06:06:57 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id m6so7401990oag.7 for <ietf@ietf.org>; Tue, 08 Oct 2013 06:06:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=i+8scrlyQhATE2EN7HvqWjRKnfZnAT7IxdSOuStbByQ=; b=mAOgNnNRBMvApN05e3QPgg/HF5r5gk8FCf+/AdndOITUVEMx3DHZa1uucJJgauJemc guE86i27ruSZt2nLQp+og7LnFuvO10QhRNq5Fp5iMKb4SwXPv/Ac7DoNXvJw1FT5bfg3 e+MMTpWelnDxGPW5tOh3dIFJLuyazeeKPfzJBS5XLEXH45rAdnvO9UvlSc0eGunjOnLJ l0Z2Kl11vhtM4W8s9bXexG6/w2G85JViy92RfJy1zSI7hC21faa7DMh6Nqiyr+TIjOTW EWgkObcjPbvHS87HzcbXBK12REnm/v7g80gDgD0hiHoMEWiBbJ6scRfHmMREH2yi8shx tOPw==
X-Gm-Message-State: ALoCoQmgq1+DWN3yqYXQrGaqPxTf+HDIyewJYBf47sINRsuVsTjYSMb5TLNu7TpSRUjcF5O7kxYf
MIME-Version: 1.0
X-Received: by 10.60.68.135 with SMTP id w7mr1179810oet.9.1381237615473; Tue, 08 Oct 2013 06:06:55 -0700 (PDT)
Received: by 10.76.101.10 with HTTP; Tue, 8 Oct 2013 06:06:55 -0700 (PDT)
In-Reply-To: <044d01cec425$1756c680$46045380$@olddog.co.uk>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk> <F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com> <72C88D25-6668-4086-8E50-7AA21C549113@hopcount.ca> <044d01cec425$1756c680$46045380$@olddog.co.uk>
Date: Tue, 8 Oct 2013 09:06:55 -0400
Message-ID: <CAL02cgScRCYt_gJa1Sp6arJg-wykhJZQPMEtdyBz6FxxGKDHqQ@mail.gmail.com>
Subject: Re: year for highest number of IETF participants
From: Richard Barnes <rlb@ipv.sx>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a1134c4c26bc2e604e83a71cf
Cc: diversity@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, 08 Oct 2013 13:07:14 -0000

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

Indeed, the number Joe was counting was the number who filled out a
registration form.  Counting those who actually paid their registration
yields closer numbers.

rbarnes$ for n in $(jot 15 73); do
att=$(curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" |
grep -o ">Yes<" | wc -l);
echo $n $att;
done
73 969
74 1170
75 1102
76 1129
77 1242
78 1159
79 1144
80 1231
81 1127
82 948
83 1395
84 1199
85 1157
86 1115
87 1435


On Tue, Oct 8, 2013 at 8:51 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Curiously these numbers do not match those at
> https://www.ietf.org/meeting/past.html
>
> Registration, we may conclude, does not equate to attendance.
>
> Adrian
>
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Joe
> > Abley
> > Sent: 08 October 2013 02:38
> > To: Ted Lemon
> > Cc: diversity@ietf.org; IETF
> > Subject: Re: year for highest number of IETF participants
> >
> > [krill:~]% for n in $(jot 15 73); do
> > curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" | \
> >   awk -v n=${n} '/ registrations:/ { sub(/ registrations:.*$/, "");
> sub(/^.*\>/, "");
> > print n, $0; }'
> > done
> > 73 1111
> > 74 1332
> > 75 1230
> > 76 1249
> > 77 1350
> > 78 1304
> > 79 1337
> > 80 1317
> > 81 1244
> > 82 1051
> > 83 1529
> > 84 1356
> > 85 1351
> > 86 1223
> > 87 1585
> > [krill:~]%
>
>

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

<div dir=3D"ltr">Indeed, the number Joe was counting was the number who fil=
led out a registration form. =A0Counting those who actually paid their regi=
stration yields closer numbers.<div><br></div><div><div>rbarnes$ for n in $=
(jot 15 73); do =A0 =A0=A0</div>
<div>att=3D$(curl -s &quot;<a href=3D"https://www.ietf.org/registration/iet=
f${n}/attendance.py">https://www.ietf.org/registration/ietf${n}/attendance.=
py</a>&quot; | grep -o &quot;&gt;Yes&lt;&quot; | wc -l);</div><div>echo $n =
$att;=A0</div>
<div>done</div><div>73 969</div><div>74 1170</div><div>75 1102</div><div>76=
 1129</div><div>77 1242</div><div>78 1159</div><div>79 1144</div><div>80 12=
31</div><div>81 1127</div><div>82 948</div><div>83 1395</div><div>84 1199</=
div>
<div>85 1157</div><div>86 1115</div><div>87 1435</div></div></div><div clas=
s=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Oct 8, 2013 at=
 8:51 AM, Adrian Farrel <span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@oldd=
og.co.uk" target=3D"_blank">adrian@olddog.co.uk</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">Curiously these numbers do not match those a=
t<br>
<a href=3D"https://www.ietf.org/meeting/past.html" target=3D"_blank">https:=
//www.ietf.org/meeting/past.html</a><br>
<br>
Registration, we may conclude, does not equate to attendance.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</=
a> [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</=
a>] On Behalf Of Joe<br>
&gt; Abley<br>
&gt; Sent: 08 October 2013 02:38<br>
&gt; To: Ted Lemon<br>
&gt; Cc: <a href=3D"mailto:diversity@ietf.org">diversity@ietf.org</a>; IETF=
<br>
&gt; Subject: Re: year for highest number of IETF participants<br>
&gt;<br>
&gt; [krill:~]% for n in $(jot 15 73); do<br>
&gt; curl -s &quot;<a href=3D"https://www.ietf.org/registration/ietf${n}/at=
tendance.py" target=3D"_blank">https://www.ietf.org/registration/ietf${n}/a=
ttendance.py</a>&quot; | \<br>
&gt; =A0 awk -v n=3D${n} &#39;/ registrations:/ { sub(/ registrations:.*$/,=
 &quot;&quot;);<br>
sub(/^.*\&gt;/, &quot;&quot;);<br>
&gt; print n, $0; }&#39;<br>
&gt; done<br>
&gt; 73 1111<br>
&gt; 74 1332<br>
&gt; 75 1230<br>
&gt; 76 1249<br>
&gt; 77 1350<br>
&gt; 78 1304<br>
&gt; 79 1337<br>
&gt; 80 1317<br>
&gt; 81 1244<br>
&gt; 82 1051<br>
&gt; 83 1529<br>
&gt; 84 1356<br>
&gt; 85 1351<br>
&gt; 86 1223<br>
&gt; 87 1585<br>
&gt; [krill:~]%<br>
<br>
</div></div></blockquote></div><br></div>

--001a1134c4c26bc2e604e83a71cf--

From mcr@sandelman.ca  Tue Oct  8 06:19:33 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 CD5E111E81B9 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:19:33 -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 Gg0K17kXOqbn for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:19:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 1822E11E81B3 for <ietf@ietf.org>; Tue,  8 Oct 2013 06:19:15 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9DF192017C for <ietf@ietf.org>; Tue,  8 Oct 2013 10:29:14 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A772463B88; Tue,  8 Oct 2013 09:19:09 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 93A3663AEF for <ietf@ietf.org>; Tue,  8 Oct 2013 09:19:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Montevideo statement
In-Reply-To: <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@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: Tue, 08 Oct 2013 09:19:09 -0400
Message-ID: <11948.1381238349@sandelman.ca>
Sender: 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: Tue, 08 Oct 2013 13:19:33 -0000

--=-=-=


Phillip Hallam-Baker <hallam@gmail.com> wrote:
    > I think the US executive branch would be better rid of the control
    > before the
    > vandals work out how to use it for mischief. But better would be to
    > ensure that
    > no such leverage exists. There is no reason for the apex of the DNS to
    > be a
    > single root, it could be signed by a quorum of signers (in addition to
    > the key

k-of-n signing for the DNSSEC root was talked about by many, including Tatu
Ylonen back in 1996...

I have an alternate proposal: every country's ccTLD should sign the root,
and/or the other TLDs.  That actually hands control of the DNS root back
to the legislatures in each country.  True: some countries might have
perverted notions of what belongs in the root, and we might get different
views of the Internet.  But, this happens already using a variety of
wrong mechanisms that cause harm to the Internet.

Better they do this using good crypto, than that they do this by trying to
subvert the (US-controlled) crypto.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUlQGS4qHRg3pndX9AQJOBQP+M1mPoTn1/LfvUm2FASwKac06S6y+XjBZ
AuRuh2iYNbS/Zex8gn14JhsVIEUmYpE0CuMoF7TWGNHZN1lVOIW+OCS2OZoSoUY0
4vALFbAAeO6AF/VaCgV9qGz3jvtnbqPBBJtIlOBlZhj7Ufxla29hPhRCmYvGuXdV
i3NXcFpIyuw=
=YbhK
-----END PGP SIGNATURE-----
--=-=-=--

From hallam@gmail.com  Tue Oct  8 06:19:52 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 4A12A21E8162 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:19: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, 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 DHPXp1EZij37 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:19:51 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7960021E808A for <ietf@ietf.org>; Tue,  8 Oct 2013 06:19:36 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id eh20so6782464lab.4 for <ietf@ietf.org>; Tue, 08 Oct 2013 06:19: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=kVtoxFYNIjtaSzYPpjDubATw1BBQoWC5/jDX7A9ZdxU=; b=xuJ3ucEdU5pD+fVIBwxf9IRHTsPDQxO4eCw372JVb35f6XD/R9HsshPpOnBYx9d6oS fPfQ6I/bB0vjzgBpiMEb6vgJCVhH1IWpyy8p24NVDVYHjcdTc6bAXpREM3idcl5oR7Gu b6HX4snM3B46YazWvfehSi6RGVSUfFFyv4AU4XiTbs8SA/9BInm1lmQCxuo54DKbHZi+ 5Vevn9Tj96CzWQrHU4A0EiNcrKthfwvkS/Yd4xmrok8HjoSz+AkM/4EPHz1ngH3JpOR3 X26K/+juPFvgTQ0N394e8Y2kfbBAUHGeK4FDapf0sdBfzZ+JZORwVMbD5LDEcIv56S2q 5uqQ==
MIME-Version: 1.0
X-Received: by 10.152.203.233 with SMTP id kt9mr1309210lac.29.1381238375263; Tue, 08 Oct 2013 06:19:35 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 8 Oct 2013 06:19:35 -0700 (PDT)
In-Reply-To: <10B2223B-CDCA-491A-BC53-45FD7E54A16E@isi.edu>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <10B2223B-CDCA-491A-BC53-45FD7E54A16E@isi.edu>
Date: Tue, 8 Oct 2013 09:19:35 -0400
Message-ID: <CAMm+LwhA58HBpkk_+n+JbR=MvrdCZ_AjYEw2rOgLewAjZ2fd8w@mail.gmail.com>
Subject: Re: Montevideo statement
From: Phillip Hallam-Baker <hallam@gmail.com>
To: manning bill <bmanning@isi.edu>
Content-Type: multipart/alternative; boundary=001a11345984b533ce04e83a9e61
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, 08 Oct 2013 13:19:52 -0000

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

On Tue, Oct 8, 2013 at 8:53 AM, manning bill <bmanning@isi.edu> wrote:

> >
> >
> > I think the US executive branch would be better rid of the control
> before the vandals work out how to use it for mischief. But better would be
> to ensure that no such leverage exists. There is no reason for the apex of
> the DNS to be a single root, it could be signed by a quorum of signers (in
> addition to the key splitting which I am fully familiar with). And every
> government should be assigned a sovereign reserve of IPv6 addresses to
> prevent a scarcity being used as leverage.
> >
> > --
> > Website: http://hallambaker.com/
>
>         Quorum signing with split keys  was already built and tested in a
> root server operator testbed (the OTDR testbed) from 1998-2005.  It was
> considered more fragile than the current system.
>

Considered more fragile by whom?

By the members of the $250m/yr NSA mole program?


Very few people in DNS land recognize the class of attack as being
realistic. Even when they have prime ministers and members of the GRU
visiting them to tell them how important the issue is to their country.

We already have one example of lobbyists attempting this type of attack
(see Martin's post). So it is far from unrealistic.


At present ICANN's power over the DNS is entirely discretionary. Attempting
to drop Palestine out of the routing tables would simply be the end of the
ICANN root zone. ICANN could continue to manage .com but their influence
over the rest of the system would end completely.

But DNSSEC changes the balance of power. With the root signed and embedded
infrastructure verifying DNSSEC trust chains, the cost of a switchover
rises remarkably. And when I tried to mention the fact I tended to get
nasty threats.

The third question of power is 'how do we get rid of you'. The answer in
the case of DNSSEC is that you can't.


Fortunately the issue is quite easily fixed, just as the problem of using
IPv6 or BGP allocations for leverage is fixable. Governments don't need to
wait on ICANN or the IETF to develop a quorum signing model for the DNS
apex, they could and should institute one themselves and tell their
infrastructure providers to chain to the quorum roots rather than the
monolithic apex root.


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

--001a11345984b533ce04e83a9e61
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, Oct 8, 2013 at 8:53 AM, manning bill <span dir=3D"ltr">&lt;=
<a href=3D"mailto:bmanning@isi.edu" target=3D"_blank">bmanning@isi.edu</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">&gt;<br>
&gt;<br>
&gt; I think the US executive branch would be better rid of the control bef=
ore the vandals work out how to use it for mischief. But better would be to=
 ensure that no such leverage exists. There is no reason for the apex of th=
e DNS to be a single root, it could be signed by a quorum of signers (in ad=
dition to the key splitting which I am fully familiar with). And every gove=
rnment should be assigned a sovereign reserve of IPv6 addresses to prevent =
a scarcity being used as leverage.<br>

&gt;<br>
&gt; --<br>
&gt; Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">http://=
hallambaker.com/</a><br>
<br>
</div>=A0 =A0 =A0 =A0 Quorum signing with split keys =A0was already built a=
nd tested in a root server operator testbed (the OTDR testbed) from 1998-20=
05. =A0It was considered more fragile than the current system.<br></blockqu=
ote><div>
<br></div><div>Considered more fragile by whom?</div><div><br></div><div>By=
 the members of the $250m/yr NSA mole program?</div><div><br></div><div><br=
></div><div>Very few people in DNS land recognize the class of attack as be=
ing realistic. Even when they have prime ministers and members of the GRU v=
isiting them to tell them how important the issue is to their country.</div=
>
<div><br></div><div>We already have one example of lobbyists attempting thi=
s type of attack (see Martin&#39;s post). So it is far from unrealistic.=A0=
</div><div><br></div><div><br></div><div>At present ICANN&#39;s power over =
the DNS is entirely discretionary. Attempting to drop Palestine out of the =
routing tables would simply be the end of the ICANN root zone. ICANN could =
continue to manage .com but their influence over the rest of the system wou=
ld end completely.</div>
<div><br></div><div>But DNSSEC changes the balance of power. With the root =
signed and embedded infrastructure verifying DNSSEC trust chains, the cost =
of a switchover rises remarkably. And when I tried to mention the fact I te=
nded to get nasty threats.</div>
</div><div><br></div><div>The third question of power is &#39;how do we get=
 rid of you&#39;. The answer in the case of DNSSEC is that you can&#39;t.=
=A0</div><div><br></div><div><br></div><div>Fortunately the issue is quite =
easily fixed, just as the problem of using IPv6 or BGP allocations for leve=
rage is fixable. Governments don&#39;t need to wait on ICANN or the IETF to=
 develop a quorum signing model for the DNS apex, they could and should ins=
titute one themselves and tell their infrastructure providers to chain to t=
he quorum roots rather than the monolithic apex root.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11345984b533ce04e83a9e61--

From hallam@gmail.com  Tue Oct  8 06:39:10 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 95C8321E817E for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:39:10 -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 kUMwCyjdwZvp for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:39:09 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id AD0B721E805F for <ietf@ietf.org>; Tue,  8 Oct 2013 06:39:08 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id eh20so6991222lab.32 for <ietf@ietf.org>; Tue, 08 Oct 2013 06:39: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=bIVTH3IaCshLsrLRJuh+nIbKIZoCdUOZUsfW9Dzl960=; b=DZuqbhY+ksKvFCGbM7uaueCZbQuqMPZ9BctZSsNYZx0i8zbJs2xctsWxxtAnDoAx0D hPj/u/iQU2eYx1BZrNfvX3o8Wol2iwWDywxLxJM1+SonlKbPO37hexBLu/fcWh+VQlGn bTe1DvP9cSCSUd1fLcNtOi8KmR9kcVXD7mkFW4lDKXQvEk/qAEOuCB+clC4K3EymR8Rn 9RqdfG6enQdrARxYZufIkAVw9hPaqU66+incJQZWEbB9YYuXxmltcdkYKvMOkhxMalwe 0Y7dsQE5nnBSaYGGnma7RBkqWICPFqmL2yLwrrOE51s+NB04szvc7XxOg1haf5uVqJFX f2LQ==
MIME-Version: 1.0
X-Received: by 10.152.29.103 with SMTP id j7mr1363446lah.7.1381239547495; Tue, 08 Oct 2013 06:39:07 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 8 Oct 2013 06:39:07 -0700 (PDT)
In-Reply-To: <11948.1381238349@sandelman.ca>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca>
Date: Tue, 8 Oct 2013 09:39:07 -0400
Message-ID: <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com>
Subject: Re: Montevideo statement
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=089e0160b828940a5d04e83ae4c4
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, 08 Oct 2013 13:39:10 -0000

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

On Tue, Oct 8, 2013 at 9:19 AM, Michael Richardson <mcr+ietf@sandelman.ca>wrote:

>
> Phillip Hallam-Baker <hallam@gmail.com> wrote:
>     > I think the US executive branch would be better rid of the control
>     > before the
>     > vandals work out how to use it for mischief. But better would be to
>     > ensure that
>     > no such leverage exists. There is no reason for the apex of the DNS
> to
>     > be a
>     > single root, it could be signed by a quorum of signers (in addition
> to
>     > the key
>
> k-of-n signing for the DNSSEC root was talked about by many, including Tatu
> Ylonen back in 1996...
>

Most crypto hardware supports k-of-n keysplitting and most of the code out
there makes use of it. And PKIX CAs use k-of-n keysplitting on a monolithic
trust anchor rather than a composite trust anchor. So it is easy to see how
a technical decision would go that way.

But the idea of signing the root did not become a practical possibility
until much later. I certainly gave the issue no thought when looking at
signing .com. I certainly did not think that it was necessary to wait for
the root to be signed to sign .com.



> I have an alternate proposal: every country's ccTLD should sign the root,
> and/or the other TLDs.  That actually hands control of the DNS root back
> to the legislatures in each country.  True: some countries might have
> perverted notions of what belongs in the root, and we might get different
> views of the Internet.  But, this happens already using a variety of
> wrong mechanisms that cause harm to the Internet.
>

I think that is a better approach actually. The CC TLDs are in effect
members of a bridge CA and ICANN is merely the bridge administrator.

There would have to be adequate controls to ensure that transfer of the
root was practical of course. It is probably necessary for the CC TLDs to
be able to sign more than one bridge. After all, Europe has just spent many
billions replicating GPS. This would cost less.

And anyone who is a relying party can choose to chain to a single trust
anchor or use multiple anchors. So the quorate approach is still available
for those who want it. If France, Cuba, the US and India all agree on the
validity of the bridge root, then it is probably valid.



> Better they do this using good crypto, than that they do this by trying to
> subvert the (US-controlled) crypto.
>

Its not all US controlled, you can use GOST...


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

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

<div dir=3D"ltr">On Tue, Oct 8, 2013 at 9:19 AM, Michael Richardson <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">m=
cr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><d=
iv 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>
Phillip Hallam-Baker &lt;<a href=3D"mailto:hallam@gmail.com">hallam@gmail.c=
om</a>&gt; wrote:<br>
=A0 =A0 &gt; I think the US executive branch would be better rid of the con=
trol<br>
=A0 =A0 &gt; before the<br>
=A0 =A0 &gt; vandals work out how to use it for mischief. But better would =
be to<br>
=A0 =A0 &gt; ensure that<br>
=A0 =A0 &gt; no such leverage exists. There is no reason for the apex of th=
e DNS to<br>
=A0 =A0 &gt; be a<br>
=A0 =A0 &gt; single root, it could be signed by a quorum of signers (in add=
ition to<br>
=A0 =A0 &gt; the key<br>
<br>
</div>k-of-n signing for the DNSSEC root was talked about by many, includin=
g Tatu<br>
Ylonen back in 1996...<br></blockquote><div><br></div><div>Most crypto hard=
ware supports k-of-n keysplitting and most of the code out there makes use =
of it. And PKIX CAs use k-of-n keysplitting on a monolithic trust anchor ra=
ther than a composite trust anchor. So it is easy to see how a technical de=
cision would go that way.</div>
<div><br></div><div>But the idea of signing the root did not become a pract=
ical possibility until much later. I certainly gave the issue no thought wh=
en looking at signing .com. I certainly did not think that it was necessary=
 to wait for the root to be signed to sign .com.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have an alternate proposal: every country&#39;s ccTLD should sign the roo=
t,<br>
and/or the other TLDs. =A0That actually hands control of the DNS root back<=
br>
to the legislatures in each country. =A0True: some countries might have<br>
perverted notions of what belongs in the root, and we might get different<b=
r>
views of the Internet. =A0But, this happens already using a variety of<br>
wrong mechanisms that cause harm to the Internet.<br></blockquote><div><br>=
</div><div>I think that is a better approach actually. The CC TLDs are in e=
ffect members of a bridge CA and ICANN is merely the bridge administrator.<=
/div>
<div><br></div><div>There would have to be adequate controls to ensure that=
 transfer of the root was practical of course. It is probably necessary for=
 the CC TLDs to be able to sign more than one bridge. After all, Europe has=
 just spent many billions replicating GPS. This would cost less.</div>
<div><br></div><div>And anyone who is a relying party can choose to chain t=
o a single trust anchor or use multiple anchors. So the quorate approach is=
 still available for those who want it. If France, Cuba, the US and India a=
ll agree on the validity of the bridge root, then it is probably valid.<br>
</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Better t=
hey do this using good crypto, than that they do this by trying to<br>
subvert the (US-controlled) crypto.<br></blockquote><div><br></div><div>Its=
 not all US controlled, you can use GOST...</div></div><br clear=3D"all"><d=
iv><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hal=
lambaker.com/</a><br>

</div></div>

--089e0160b828940a5d04e83ae4c4--

From Aaron.Ding@cl.cam.ac.uk  Tue Oct  8 06:51:11 2013
Return-Path: <Aaron.Ding@cl.cam.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 8301021E8088; Tue,  8 Oct 2013 06:51:10 -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 ZG8feo1Dxq2E; Tue,  8 Oct 2013 06:51:05 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id DD05221E80A3; Tue,  8 Oct 2013 06:51:04 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:38393) by ppsw-33.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtp id 1VTXgj-0007aB-iF (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 14:51:01 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1VTXgj-000TxX-LC (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 14:51:01 +0100
Received: from chesterfield.cl.cam.ac.uk ([128.232.10.127]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 08 Oct 2013 14:51:01 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 08 Oct 2013 14:51:01 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: adrian@olddog.co.uk
Subject: Re: [Diversity] year for highest number of IETF participants
Organization: Cambridge University
Message-ID: <a94078aa098fd58dfa1a7727fff175f6@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.4
Cc: diversity@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, 08 Oct 2013 13:51:11 -0000

Hi Adrian,

True, that also puzzled me a bit since the numbers do not match, 
registration and attendee - the registration number is in general higher 
than that of attendees.

Cheers,
Aaron

On 08/10/13 13:51, Adrian Farrel wrote:
> Curiously these numbers do not match those at
> https://www.ietf.org/meeting/past.html
> 
> Registration, we may conclude, does not equate to attendance.
> 
> Adrian
> 
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf 
>> Of Joe
>> Abley
>> Sent: 08 October 2013 02:38
>> To: Ted Lemon
>> Cc: diversity@ietf.org; IETF
>> Subject: Re: year for highest number of IETF participants
>> 
>> [krill:~]% for n in $(jot 15 73); do
>> curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" | \
>>   awk -v n=${n} '/ registrations:/ { sub(/ registrations:.*$/, "");
> sub(/^.*\>/, "");
>> print n, $0; }'
>> done
>> 73 1111
>> 74 1332
>> 75 1230
>> 76 1249
>> 77 1350
>> 78 1304
>> 79 1337
>> 80 1317
>> 81 1244
>> 82 1051
>> 83 1529
>> 84 1356
>> 85 1351
>> 86 1223
>> 87 1585
>> [krill:~]%
> 
> _______________________________________________
> diversity mailing list
> diversity@ietf.org
> https://www.ietf.org/mailman/listinfo/diversity


From Aaron.Ding@cl.cam.ac.uk  Tue Oct  8 06:56:13 2013
Return-Path: <Aaron.Ding@cl.cam.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 01E1521E8096; Tue,  8 Oct 2013 06:56:13 -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 M9wkTxxmHK3T; Tue,  8 Oct 2013 06:56:08 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 6078821E809F; Tue,  8 Oct 2013 06:56:08 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:37922) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtp id 1VTXlf-0002Zs-0o (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 14:56:07 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1VTXlf-000V07-64 (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 08 Oct 2013 14:56:07 +0100
Received: from chesterfield.cl.cam.ac.uk ([128.232.10.127]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 08 Oct 2013 14:56:07 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 08 Oct 2013 14:56:07 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: rlb@ipv.sx
Subject: Re: year for highest number of IETF participants
Organization: Cambridge University
Message-ID: <023a67c04403e65508b32a0acf2a4e22@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.4
Cc: adrian@olddog.co.uk, ietf@ietf.org, diversity@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 13:56:13 -0000

The registration number may include remote participants while attendee 
number shows how many actually went on-site.

Cheers,
Aaron


On 08/10/13 14:06, Richard Barnes wrote:
> Indeed, the number Joe was counting was the number who filled out a 
> registration form.  Counting those who actually paid their registration 
> yields closer numbers.
> rbarnes$ for n in $(jot 15 73); do
> att=$(curl -s 
> "https://www.ietf.org/registration/ietf${n}/attendance.py" | grep -o 
> ">Yes<" | wc -l);
> echo $n $att;
> done
> 73 969
> 74 1170
> 75 1102
> 76 1129
> 77 1242
> 78 1159
> 79 1144
> 80 1231
> 81 1127
> 82 948
> 83 1395
> 84 1199
> 85 1157
> 86 1115
> 87 1435
> 
> 
> On Tue, Oct 8, 2013 at 8:51 AM, Adrian Farrel <adrian@olddog.co.uk> 
> wrote:
> 
>     Curiously these numbers do not match those at
>     https://www.ietf.org/meeting/past.html
> 
>     Registration, we may conclude, does not equate to attendance.
> 
>     Adrian
> 
>     > -----Original Message-----
>     > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On 
> Behalf Of Joe
>     > Abley
>     > Sent: 08 October 2013 02:38
>     > To: Ted Lemon
>     > Cc: diversity@ietf.org; IETF
>     > Subject: Re: year for highest number of IETF participants
>     >
>     > [krill:~]% for n in $(jot 15 73); do
>     > curl -s 
> "https://www.ietf.org/registration/ietf${n}/attendance.py" | \
>     >   awk -v n=${n} '/ registrations:/ { sub(/ registrations:.*$/, 
> "");
>     sub(/^.*\>/, "");
>     > print n, $0; }'
>     > done
>     > 73 1111
>     > 74 1332
>     > 75 1230
>     > 76 1249
>     > 77 1350
>     > 78 1304
>     > 79 1337
>     > 80 1317
>     > 81 1244
>     > 82 1051
>     > 83 1529
>     > 84 1356
>     > 85 1351
>     > 86 1223
>     > 87 1585
>     > [krill:~]%
> 


From daedulus@btconnect.com  Tue Oct  8 06:59:22 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 56A7221E818B for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:59:22 -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_13=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 7CBAApJIyLHM for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 06:59:17 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id C14E121E818C for <ietf@ietf.org>; Tue,  8 Oct 2013 06:59:09 -0700 (PDT)
Received: from mail47-co9-R.bigfish.com (10.236.132.232) by CO9EHSOBE030.bigfish.com (10.236.130.93) with Microsoft SMTP Server id 14.1.225.22; Tue, 8 Oct 2013 13:59:06 +0000
Received: from mail47-co9 (localhost [127.0.0.1])	by mail47-co9-R.bigfish.com (Postfix) with ESMTP id 7AEEE6C01D9; Tue,  8 Oct 2013 13:59:06 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: PS-18(zzbb2dI98dI9371I542I1432I1418I1415Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah1de097h186068h8275bh8275dhz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail47-co9 (localhost.localdomain [127.0.0.1]) by mail47-co9 (MessageSwitch) id 1381240744369493_6504; Tue,  8 Oct 2013 13:59:04 +0000 (UTC)
Received: from CO9EHSMHS007.bigfish.com (unknown [10.236.132.240])	by mail47-co9.bigfish.com (Postfix) with ESMTP id 4B66DC8004F; Tue,  8 Oct 2013 13:59:04 +0000 (UTC)
Received: from AMSPRD0710HT005.eurprd07.prod.outlook.com (157.56.249.85) by CO9EHSMHS007.bigfish.com (10.236.130.17) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 8 Oct 2013 13:59:02 +0000
Received: from AMXPRD0310HT003.eurprd03.prod.outlook.com (157.56.248.133) by pod51017.outlook.com (10.255.160.168) with Microsoft SMTP Server (TLS) id 14.16.371.2; Tue, 8 Oct 2013 13:58:52 +0000
Message-ID: <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net><6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net> <52524A68.7040800@qti.qualcomm.com>
Subject: Re: Last calling draft-resnick-on-consensus
Date: Tue, 8 Oct 2013 14:56:32 +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.248.133]
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: Tue, 08 Oct 2013 13:59:22 -0000

I think that this I-D is flawed and should not become an RFC.  It has
several implicit presumptions that I think wrong.

1) It does not state its target audience until, perhaps, the reference
in the Conclusions, to WG Chairs.  It makes no mention of the consensus
calls made by ADs, such as at IETF Last Call, which I think far more
important.  If a WG Chair calls it wrong, there are ADs and IESG who may
put
things right.  When an AD does so, it may be time to abandon hope; and
it is some, a few, of the consensus calls made by ADs at IETF Last Call
that I have thought plain wrong, more so than those by WG Chairs.  Are
ADs assumed to be above and beyond the considerations in this I-D:-(

2)  There is an extensive discussion on the show of hands and the hum.
What technology allows you to conduct those on a mailing list?  The
fundamental rule of the IETF, for me, is that business is conducted on
the mailing list.  What happens at meetings some find useful, and it may
be the quickest way to make progress on thorny issues, but the consensus
call belongs on the mailing list.  Unless this I-D is intending to
subvert that.

3) References to working groups with 100 active participants sound like
a chimera.  I track quite a number of lists, and some have about five
active participants.  (Some Working Group Last Calls attract one or even
zero responses; the reactions of chairs to this is interesting and
varies widely).  Even the busiest lists, v6ops and tcpm, for me, do not
remotely approach 100 active participants.

4)  "Five people for and one hundred people against might still be rough
    consensus".  Can you see the presumption in that?  Read on and the
following text makes it clear that five are 'right' and one hundred
'wrong', but you are presuming that "for" is the right answer.  The
right answer to a consensus call is a consensus,which can be "against",
as much as "for", something that does not seem to be contemplated here.

5) Good WG chairs, and happily there are plenty of them, make their
presumptions plain, as in asking for information about implementations
at or around judging consensus.  The views of someone who has
independently produced rough code is then likely to outweigh those of a
dozen people who have not, so three such expressing a view in one
direction will prevail over several dozen who have not in the opposite
direction.  (This is all right as far as it goes, but I would like the
views of users and operators to count for even more, since it is they
who have the most to gain or lose; but sadly, their representation here
is small and often not apparent).  You quote Dave Clark's aphorism but
then ignore half of it.

6)  The document is strangely silent about what the vast mass of the
IETF who are not WG Chairs might do to help reach a consensus,
such as express an opinion, clearly, technically; else, perhaps, keep
quiet.

7) As has been said before when documents like this are up for
discussion, the IETF is an organisation of engineers and, for the most
part, we do it rather well.  Managing and leading loose and diverse
groups of people is more psychology or sociology  than technology, at
which we are mostly amateurs.  We then go beyond our capabilities and
get it wrong.  As here.

Tom Petch

----- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "Mark Nottingham" <mnot@mnot.net>
Cc: <ietf@ietf.org>
Sent: Monday, October 07, 2013 6:45 AM
Subject: Re: Last calling draft-resnick-on-consensus


> On 10/6/13 7:30 PM, Mark Nottingham wrote:
> > This is a VERY useful document, and I look forward to compelling my
WG participants to read it, with a pop quiz afterwards.
> >
>
> I've been exceedingly satisfied to hear this sort of thing from you
and
> the other folks who posted and talked to me about this.
>
> > The only issue I see is its length; while dedicated IETFers won't
have a problem reading such a lengthy document, the people who could
benefit most - new, potential or casual participants - will give up
early, I fear.
> >
> > Could we have someone take an editorial knife to it? Some of the
descriptions of situations are quite long, and there's a fair amount of
repetition in the document. Some of the paragraphs are quite long as
well. I reckon 2-4 pages could be saved, making it appealing to a much
wider audience.
> >
>
> I would be really disappointed by this. Indeed, my primary target was
> not at all new or casual participants; it was really intended for the
> dedicated folks and the chairs. I hope this is the start of a serious
> discussion in the IETF, not a primer for how the IETF works at a high
> level. For newer folks, I'm fine with the idea that some of this can
be
> either incorporated into the Tao or the newcomer's orientation, or
> separated into a smaller primer document. But I really believe the
long
> form is needed for real discussions among folks in the community.
>
> > Beyond that, the only suggestion I'd make is an alternate title --
"Why We Hum." Or maybe "The Things We Hum And Do Not Say" (apologies to
Jerry Maguire).
> >
>
> And here I was originally paying homage to Wittgenstein, though it
even
> got too long for that. Taken under advisement.
>
> Now, off to tackle Dave's excellent (and extensive) review.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>



From rpelletier@isoc.org  Tue Oct  8 07:04:47 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 716A611E81A3; Tue,  8 Oct 2013 07:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level: 
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=0.481, 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 GYXg-hqxjh9p; Tue,  8 Oct 2013 07:04:43 -0700 (PDT)
Received: from smtp118.ord1c.emailsrvr.com (smtp118.ord1c.emailsrvr.com [108.166.43.118]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF1F11E8195; Tue,  8 Oct 2013 07:04:42 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 91D711B81B7; Tue,  8 Oct 2013 10:04:41 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id D74981B824E;  Tue,  8 Oct 2013 10:04:40 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B7A1308A-0368-41BF-B21B-928617D6872E"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: year for highest number of IETF participants
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <CAL02cgScRCYt_gJa1Sp6arJg-wykhJZQPMEtdyBz6FxxGKDHqQ@mail.gmail.com>
Date: Tue, 8 Oct 2013 10:04:40 -0400
Message-Id: <C12F355F-3B0D-419B-A8D3-F0A17FBE98C1@isoc.org>
References: <4695b41878ea8459411ba325bb173fc1@cam.ac.uk> <F882939A-800D-41DB-BC2C-81E3E7CD771F@nominum.com> <72C88D25-6668-4086-8E50-7AA21C549113@hopcount.ca> <044d01cec425$1756c680$46045380$@olddog.co.uk> <CAL02cgScRCYt_gJa1Sp6arJg-wykhJZQPMEtdyBz6FxxGKDHqQ@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1510)
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, IETF <ietf@ietf.org>, diversity@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 14:04:47 -0000

--Apple-Mail=_B7A1308A-0368-41BF-B21B-928617D6872E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

All;

Prior to this Vancouver meeting in which Remote Participants will have =
an opportunity to register, registrations did -not- include Remote =
Participants.

Attendees are those who showed up.  Registrations are typically a much =
higher number.  Not all those who register attend.

Ray
IAD

On Oct 8, 2013, at 9:06 AM, Richard Barnes <rlb@ipv.sx> wrote:

> Indeed, the number Joe was counting was the number who filled out a =
registration form.  Counting those who actually paid their registration =
yields closer numbers.
>=20
> rbarnes$ for n in $(jot 15 73); do    =20
> att=3D$(curl -s =
"https://www.ietf.org/registration/ietf${n}/attendance.py" | grep -o =
">Yes<" | wc -l);
> echo $n $att;=20
> done
> 73 969
> 74 1170
> 75 1102
> 76 1129
> 77 1242
> 78 1159
> 79 1144
> 80 1231
> 81 1127
> 82 948
> 83 1395
> 84 1199
> 85 1157
> 86 1115
> 87 1435
>=20
>=20
> On Tue, Oct 8, 2013 at 8:51 AM, Adrian Farrel <adrian@olddog.co.uk> =
wrote:
> Curiously these numbers do not match those at
> https://www.ietf.org/meeting/past.html
>=20
> Registration, we may conclude, does not equate to attendance.
>=20
> Adrian
>=20
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Joe
> > Abley
> > Sent: 08 October 2013 02:38
> > To: Ted Lemon
> > Cc: diversity@ietf.org; IETF
> > Subject: Re: year for highest number of IETF participants
> >
> > [krill:~]% for n in $(jot 15 73); do
> > curl -s "https://www.ietf.org/registration/ietf${n}/attendance.py" | =
\
> >   awk -v n=3D${n} '/ registrations:/ { sub(/ registrations:.*$/, =
"");
> sub(/^.*\>/, "");
> > print n, $0; }'
> > done
> > 73 1111
> > 74 1332
> > 75 1230
> > 76 1249
> > 77 1350
> > 78 1304
> > 79 1337
> > 80 1317
> > 81 1244
> > 82 1051
> > 83 1529
> > 84 1356
> > 85 1351
> > 86 1223
> > 87 1585
> > [krill:~]%
>=20
>=20


--Apple-Mail=_B7A1308A-0368-41BF-B21B-928617D6872E
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; =
">All;<div><br></div><div>Prior to this Vancouver meeting in which =
Remote Participants will have an opportunity to register, registrations =
did -not- include Remote =
Participants.</div><div><br></div><div>Attendees are those who showed =
up. &nbsp;Registrations are typically a much higher number. &nbsp;Not =
all those who register =
attend.</div><div><br></div><div>Ray</div><div>IAD</div><div><br><div><div=
>On Oct 8, 2013, at 9:06 AM, Richard Barnes &lt;<a =
href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr">Indeed, the number Joe was counting was the number who =
filled out a registration form. &nbsp;Counting those who actually paid =
their registration yields closer =
numbers.<div><br></div><div><div>rbarnes$ for n in $(jot 15 73); do =
&nbsp; &nbsp;&nbsp;</div>
<div>att=3D$(curl -s "<a =
href=3D"https://www.ietf.org/registration/ietf${n}/attendance.py">https://=
www.ietf.org/registration/ietf${n}/attendance.py</a>" | grep -o =
"&gt;Yes&lt;" | wc -l);</div><div>echo $n $att;&nbsp;</div>
<div>done</div><div>73 969</div><div>74 1170</div><div>75 =
1102</div><div>76 1129</div><div>77 1242</div><div>78 1159</div><div>79 =
1144</div><div>80 1231</div><div>81 1127</div><div>82 948</div><div>83 =
1395</div><div>84 1199</div>
<div>85 1157</div><div>86 1115</div><div>87 1435</div></div></div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Oct 8, =
2013 at 8:51 AM, Adrian Farrel <span dir=3D"ltr">&lt;<a =
href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</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">Curiously these =
numbers do not match those at<br>
<a href=3D"https://www.ietf.org/meeting/past.html" =
target=3D"_blank">https://www.ietf.org/meeting/past.html</a><br>
<br>
Registration, we may conclude, does not equate to attendance.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a =
href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> =
[mailto:<a =
href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] On =
Behalf Of Joe<br>
&gt; Abley<br>
&gt; Sent: 08 October 2013 02:38<br>
&gt; To: Ted Lemon<br>
&gt; Cc: <a href=3D"mailto:diversity@ietf.org">diversity@ietf.org</a>; =
IETF<br>
&gt; Subject: Re: year for highest number of IETF participants<br>
&gt;<br>
&gt; [krill:~]% for n in $(jot 15 73); do<br>
&gt; curl -s "<a =
href=3D"https://www.ietf.org/registration/ietf${n}/attendance.py" =
target=3D"_blank">https://www.ietf.org/registration/ietf${n}/attendance.py=
</a>" | \<br>
&gt; &nbsp; awk -v n=3D${n} '/ registrations:/ { sub(/ =
registrations:.*$/, "");<br>
sub(/^.*\&gt;/, "");<br>
&gt; print n, $0; }'<br>
&gt; done<br>
&gt; 73 1111<br>
&gt; 74 1332<br>
&gt; 75 1230<br>
&gt; 76 1249<br>
&gt; 77 1350<br>
&gt; 78 1304<br>
&gt; 79 1337<br>
&gt; 80 1317<br>
&gt; 81 1244<br>
&gt; 82 1051<br>
&gt; 83 1529<br>
&gt; 84 1356<br>
&gt; 85 1351<br>
&gt; 86 1223<br>
&gt; 87 1585<br>
&gt; [krill:~]%<br>
<br>
</div></div></blockquote></div><br></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail=_B7A1308A-0368-41BF-B21B-928617D6872E--

From bmanning@isi.edu  Tue Oct  8 07:52:04 2013
Return-Path: <bmanning@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 D290121E80F0 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 07:52:04 -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=[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 lu7nmPSC-qse for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 07:51:59 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 17DC121E818C for <ietf@ietf.org>; Tue,  8 Oct 2013 07:51:54 -0700 (PDT)
Received: from [192.168.48.44] ([217.193.203.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r98EnZkY011617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 07:49:47 -0700 (PDT)
Subject: Re: Montevideo statement
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <CAMm+LwhA58HBpkk_+n+JbR=MvrdCZ_AjYEw2rOgLewAjZ2fd8w@mail.gmail.com>
Date: Tue, 8 Oct 2013 07:49:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <94EC37C2-4BF7-4FC6-A42E-C765BDDE7070@isi.edu>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <10B2223B-CDCA-491A-BC53-45FD7E54A16E@isi.edu> <CAMm+LwhA58HBpkk_+n+JbR=MvrdCZ_AjYEw2rOgLewAjZ2fd8w@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 08 Oct 2013 14:52:05 -0000

On 8October2013Tuesday, at 6:19, Phillip Hallam-Baker wrote:

>=20
>=20
>=20
> On Tue, Oct 8, 2013 at 8:53 AM, manning bill <bmanning@isi.edu> wrote:
> >
> >
> > I think the US executive branch would be better rid of the control =
before the vandals work out how to use it for mischief. But better would =
be to ensure that no such leverage exists. There is no reason for the =
apex of the DNS to be a single root, it could be signed by a quorum of =
signers (in addition to the key splitting which I am fully familiar =
with). And every government should be assigned a sovereign reserve of =
IPv6 addresses to prevent a scarcity being used as leverage.
> >
> > --
> > Website: http://hallambaker.com/
>=20
>         Quorum signing with split keys  was already built and tested =
in a root server operator testbed (the OTDR testbed) from 1998-2005.  It =
was considered more fragile than the current system.
>=20
> Considered more fragile by whom?
>=20
> By the members of the $250m/yr NSA mole program?
>=20
>=20
> Very few people in DNS land recognize the class of attack as being =
realistic. Even when they have prime ministers and members of the GRU =
visiting them to tell them how important the issue is to their country.
>=20
> We already have one example of lobbyists attempting this type of =
attack (see Martin's post). So it is far from unrealistic.=20
>=20
>=20
> At present ICANN's power over the DNS is entirely discretionary. =
Attempting to drop Palestine out of the routing tables would simply be =
the end of the ICANN root zone. ICANN could continue to manage .com but =
their influence over the rest of the system would end completely.
>=20
> But DNSSEC changes the balance of power. With the root signed and =
embedded infrastructure verifying DNSSEC trust chains, the cost of a =
switchover rises remarkably. And when I tried to mention the fact I =
tended to get nasty threats.
>=20
> The third question of power is 'how do we get rid of you'. The answer =
in the case of DNSSEC is that you can't.=20
>=20
>=20
> Fortunately the issue is quite easily fixed, just as the problem of =
using IPv6 or BGP allocations for leverage is fixable. Governments don't =
need to wait on ICANN or the IETF to develop a quorum signing model for =
the DNS apex, they could and should institute one themselves and tell =
their infrastructure providers to chain to the quorum roots rather than =
the monolithic apex root.
>=20
>=20

	Been there, done that, outgrew the teeshirt.
        Interestingly, the perceived value of a common, global namespace =
is _MUCH_ higher than the value of a controlled, boundary constrained =
namespace=85

	At least by nearly every government to date.

	The fragile vectors could be classed in two buckets,  Human =
Factors & Timing.

/bill=

From skyper@thc.org  Mon Oct  7 13:23:43 2013
Return-Path: <skyper@thc.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 4D01F21E81BB for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 13:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.425
X-Spam-Level: 
X-Spam-Status: No, score=-0.425 tagged_above=-999 required=5 tests=[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 yIoFmvfXAFbs for <ietf@ietfa.amsl.com>; Mon,  7 Oct 2013 13:23:39 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id D254121F8445 for <ietf@ietf.org>; Mon,  7 Oct 2013 13:23:31 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id aq17so17351340iec.13 for <ietf@ietf.org>; Mon, 07 Oct 2013 13:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thc.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mS1gXrCrFvrh/KgDROvVpi+04VaJCST0NQMlVRqxfG8=; b=daO0NYBYXZUfG5770LCzlBqoFuUGIfyfc0xhztrtSa4NoPz3ykrwJZ7rv5PE5vodLd olZJvBb1Ku408m0khKf88IhACIewM4KmFdhYyp4qE9JDAiB4ekhV2Ud6rqcndiU3PJXZ xvB/J2pdHhDg2dk7BlBOHFN4zXOqhPOMfsp3U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=mS1gXrCrFvrh/KgDROvVpi+04VaJCST0NQMlVRqxfG8=; b=Q+abSdBJV7KrP8zyvnrkMvDJ+Q8n/Kf6CcOP8dfK50GFSG7gzZzsXrZqU7yEDGoxCg Bf9F2QHzh53kAW6J+ERPkTyYItzBcvyoWcpGchIXzLjzQj6QcW3G/ZzxoFmwHd23xv/r +IMZdwI9Mvv9kdivsXdfmBx4gvGlc5JAAZ2CtBiLMPMT7V7JgUX8QavBlN+VRnC7flMh 78dpHOrlup6rP27rCwkIG04MsF533m7xQgEcMJ57nR7olNVosqiocc2onslQgYP3v4g9 FMwIsMDlvHGI5NVQglHqBK54NhMFK75PJgN1703erAPCnR4zjwlmZVNieYh+dauvU2BV m8CQ==
X-Gm-Message-State: ALoCoQl7qcBPzO100SqKLNDIeKlQRkuVjBrjinCX5Qt+/lS15U7m+QzqDpw5PSxWq3vR7biHjGjG
MIME-Version: 1.0
X-Received: by 10.50.13.8 with SMTP id d8mr18616127igc.46.1381177410898; Mon, 07 Oct 2013 13:23:30 -0700 (PDT)
Received: by 10.64.9.179 with HTTP; Mon, 7 Oct 2013 13:23:30 -0700 (PDT)
X-Originating-IP: [87.106.82.87]
In-Reply-To: <20131004225346.32223.38527.idtracker@ietfa.amsl.com>
References: <20131004225346.32223.38527.idtracker@ietfa.amsl.com>
Date: Mon, 7 Oct 2013 21:23:30 +0100
Message-ID: <CA+BZK2ppnxFKYFBPrG939-LRuukN2bmU1m=K0rXy8UaH+-x8pA@mail.gmail.com>
Subject: Re: IETF 88 Preliminary Agenda
From: Ralf Skyper Kaiser <skyper@thc.org>
To: ietf@ietf.org, agenda@ietf.org
Content-Type: multipart/alternative; boundary=089e013c66daf2e26704e82c6c1a
X-Mailman-Approved-At: Tue, 08 Oct 2013 08:32:04 -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: Mon, 07 Oct 2013 20:23:43 -0000

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

Hi,

Is it still possible to submit a talk? I would like to speak at the IETF/88
and a 15-30 minutes slot would be sufficient.

The topic of my talk is "Transport Layer Security in a Post-Prism Era".

Best Regards,

Ralf Kaiser



On Fri, Oct 4, 2013 at 11:53 PM, IETF Agenda <agenda@ietf.org> wrote:

> The IETF 88 Preliminary Agenda has been posted. The final agenda will be
> published on Friday, October 11th.
>
> https://datatracker.ietf.org/meeting/88/agenda.html
> https://datatracker.ietf.org/meeting/88/agenda.txt
>
> We are still having some difficulty integrating the new agenda tool into
> the datatracker and as a result some portions of the meeting agenda --
> beverage and snack breaks, plenaries --  are not yet showing up on the html
> version. This will hopefully be resolved very soon.
>
> More information regarding IETF 88 in Vancouver, BC, Canada is located
> here: https://www.ietf.org/meeting/88/index.html
>
> IETF Secretariat
>

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

<div dir=3D"ltr"><div><div>Hi,<br><br></div>Is it still possible to submit =
a talk? I would like to speak at the IETF/88 and a 15-30 minutes slot would=
 be sufficient.<br><br>The topic of my talk is &quot;Transport Layer Securi=
ty in a Post-Prism Era&quot;.<br>
<br></div>Best Regards,<br><br>Ralf Kaiser<br><br></div><div class=3D"gmail=
_extra"><br><br><div class=3D"gmail_quote">On Fri, Oct 4, 2013 at 11:53 PM,=
 IETF Agenda <span dir=3D"ltr">&lt;<a href=3D"mailto:agenda@ietf.org" targe=
t=3D"_blank">agenda@ietf.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">The IETF 88 Preliminary Agenda has been post=
ed. The final agenda will be published on Friday, October 11th.<br>
<br>
<a href=3D"https://datatracker.ietf.org/meeting/88/agenda.html" target=3D"_=
blank">https://datatracker.ietf.org/meeting/88/agenda.html</a><br>
<a href=3D"https://datatracker.ietf.org/meeting/88/agenda.txt" target=3D"_b=
lank">https://datatracker.ietf.org/meeting/88/agenda.txt</a><br>
<br>
We are still having some difficulty integrating the new agenda tool into th=
e datatracker and as a result some portions of the meeting agenda -- bevera=
ge and snack breaks, plenaries -- =A0are not yet showing up on the html ver=
sion. This will hopefully be resolved very soon.<br>

<br>
More information regarding IETF 88 in Vancouver, BC, Canada is located here=
: <a href=3D"https://www.ietf.org/meeting/88/index.html" target=3D"_blank">=
https://www.ietf.org/meeting/88/index.html</a><br>
<br>
IETF Secretariat<br>
</blockquote></div><br></div>

--089e013c66daf2e26704e82c6c1a--

From ted.ietf@gmail.com  Tue Oct  8 08:36:52 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 977E321E818C; Tue,  8 Oct 2013 08:36: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, 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 f3te0poFw2Xl; Tue,  8 Oct 2013 08:36: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 3465C21E81FA; Tue,  8 Oct 2013 08:36:24 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id aq17so219949iec.34 for <multiple recipients>; Tue, 08 Oct 2013 08:36:24 -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=7cLPNQCd9nAoT+zNkVR9LTRgopSjnirwfy8aGRoc898=; b=I5tHMv0nfvsBk9M472P4VEwOT2QU/4GgExqdBSTeucT5XUpqQPNr34yfLYL4dA7VeD cKAPdt2gmdjUUj53qi3EkkQxSOBkcG7BKCJvp8s2vf6xeR7ST+mIG/DATz0/OKljgJwo +pvp6x5dGPRN2RW/ePWHiDwbjBWjKAvvPP5oz2JnxnQyl/C2mpyXja37aGp04z/Yx/S/ e8Gly7qnHOBAuGHSJQKGYMGSvYv+Wys4TE2+DkrQFT/5yo48d+0OePteOr8sk3jUP0GF PDb4edR0KsMrU90iMyREwkobXFoDeQnCpc9kkLMwO8hyJe56RtiFBjz4UxHlFRel9urI SY/A==
MIME-Version: 1.0
X-Received: by 10.50.61.205 with SMTP id s13mr1765895igr.29.1381246584387; Tue, 08 Oct 2013 08:36:24 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Tue, 8 Oct 2013 08:36:24 -0700 (PDT)
In-Reply-To: <52530CCF.8090605@gmail.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com>
Date: Tue, 8 Oct 2013 08:36:24 -0700
Message-ID: <CA+9kkMB-x3B5QD9T9Q4eFRH9QSXza8AcB=4=zvmrOqyyUTnFJQ@mail.gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Hardie <ted.ietf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd7679a02913904e83c88e2
Cc: IETF <ietf@ietf.org>, 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, 08 Oct 2013 15:36:52 -0000

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

On Mon, Oct 7, 2013 at 12:34 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 08/10/2013 08:03, Ted Hardie wrote:
> ...
>
> > were.  On the second point, the truth is that informational RFCs are
> [not]
> > treated as actual requests for comments much any more, but are taken as
> > fixed;
>
> I've inserted the "not" that Ted certainly intended.


Indeed, thanks for the correction.


> But I think he raises
> an important point. If the phrase "Request For Comments" no longer means
> what it says, we need another RFC, with a provisional title of
> "Request For Comments Means What It Says".
>
>



> We still see comments on RFC 791 reasonably often, and I see comments
> on RFC 2460 practically every day. That's as it should be.
>
>
And what are the RFC numbers for the comments?  If none, as I suspect, then
the comments aren't the same status as the documents--that's fine for RFC
791 and 2460, but it is not clear that Pete's document falls into the same
class.  I would argue it does not.



> So I'd like to dispute Ted's point that by publishing a version of
> resnick-on-consensus as an RFC, we will engrave its contents in stone.
> If that's the case, we have an even deeper problem than misunderstandings
> of rough consensus.
>
>
Archival may not mean "engraved in stone", but it does impute status.  If
we want, as a community, to create an archival document on this topic, then
we should take on the work.  Pete's document is a good spark for the
conversation that might kick off that work, but I personally don't think it
is a good output document for that; if it is meant to be a spark, I don't
see why moving it into
an archival series is useful for us at this stage.

regards,

Ted


> otoh Ted's specific points on the draft are all valuable.
>
>     Brian
>

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

<div dir=3D"ltr">On Mon, Oct 7, 2013 at 12:34 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 08/10/2013 08:=
03, Ted Hardie wrote:<br>
...<br>
<br>
&gt; were. =A0On the second point, the truth is that informational RFCs are=
 [not]<br>
<div class=3D"im">&gt; treated as actual requests for comments much any mor=
e, but are taken as<br>
&gt; fixed;<br>
<br>
</div>I&#39;ve inserted the &quot;not&quot; that Ted certainly intended. </=
blockquote><div><br></div><div>Indeed, thanks for the correction.<br></div>=
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
But I think he raises<br>
an important point. If the phrase &quot;Request For Comments&quot; no longe=
r means<br>
what it says, we need another RFC, with a provisional title of<br>
&quot;Request For Comments Means What It Says&quot;.<br>
<br></blockquote><div><br><br>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We still see comments on RFC 791 reasonably often, and I see comments<br>
on RFC 2460 practically every day. That&#39;s as it should be.<br>
<br></blockquote><div><br></div><div>And what are the RFC numbers for the c=
omments?=A0 If none, as I suspect, then the comments aren&#39;t the same st=
atus as the documents--that&#39;s fine for RFC 791 and 2460, but it is not =
clear that Pete&#39;s document falls into the same class.=A0 I would argue =
it does not.<br>
<br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So I&#39;d like to dispute Ted&#39;s point that by publishing a version of<=
br>
resnick-on-consensus as an RFC, we will engrave its contents in stone.<br>
If that&#39;s the case, we have an even deeper problem than misunderstandin=
gs<br>
of rough consensus.<br>
<br></blockquote><div><br></div><div>Archival may not mean &quot;engraved i=
n stone&quot;, but it does impute status.=A0 If we want, as a community, to=
 create an archival document on this topic, then we should take on the work=
.=A0 Pete&#39;s document is a good spark for the conversation that might ki=
ck off that work, but I personally don&#39;t think it is a good output docu=
ment for that; if it is meant to be a spark, I don&#39;t see why moving it =
into<br>
an archival series is useful for us at this stage.<br><br>regards,<br><br><=
/div><div>Ted<br></div><div>=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
otoh Ted&#39;s specific points on the draft are all valuable.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 Brian<br>
</font></span></blockquote></div><br></div></div>

--047d7bd7679a02913904e83c88e2--

From ted.ietf@gmail.com  Tue Oct  8 08:39:25 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 1808821E818D; Tue,  8 Oct 2013 08:39:25 -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 yWuINqnWP9qE; Tue,  8 Oct 2013 08:39:24 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 78C4421E818C; Tue,  8 Oct 2013 08:39:24 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id ar20so1921587iec.35 for <multiple recipients>; Tue, 08 Oct 2013 08:39: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=OQh76Vcd5i+a01vVT2u+hxzbOkEUjPECvUD1AfLtFts=; b=H5SUGjr0BNfZlAb/CHaYQnQdDL0njDIueVNNlr6ekQf8qeYWZdabEbmM8CWLTMmNi8 eGlvvkjfzzM6EgncTzT4sHWL/4stNNrRUfq4IPYgY5g2EgHOODLss3ibvqNfFy63py65 Bm7E/A83sMR+b088EYgqK0NuW1lnsoXVnU8bIawv3tZQyEPVE53nFVHKvFpsTeSFJBVY dbNmuhk6ysBZRT+ieF3ub76EzHOfnDUDpzNrDZxc66MnhMLHSVrTMEJMSqnfazoDQ3GZ 56AAYHP/Pjop3Y05jLv6n0P1NN2R7kMPsq/ZQ/Map8L3iacv+eGCWS8pDpIRD7atCDaq Xjpw==
MIME-Version: 1.0
X-Received: by 10.43.106.198 with SMTP id dv6mr1527385icc.51.1381246763829; Tue, 08 Oct 2013 08:39:23 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Tue, 8 Oct 2013 08:39:23 -0700 (PDT)
In-Reply-To: <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com>
Date: Tue, 8 Oct 2013 08:39:23 -0700
Message-ID: <CA+9kkMDMUjnFwYD2NFjiWx0dMmNOFNerXQtwp6urco+F7-ffTA@mail.gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Hardie <ted.ietf@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=20cf303344f9b4919404e83c92fb
Cc: IESG <iesg@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, 08 Oct 2013 15:39:25 -0000

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

On Mon, Oct 7, 2013 at 1:35 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 7, 2013, at 3:34 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
> wrote:
> > So I'd like to dispute Ted's point that by publishing a version of
> > resnick-on-consensus as an RFC, we will engrave its contents in stone.
> > If that's the case, we have an even deeper problem than misunderstandings
> > of rough consensus.
>
> Right, I think what Ted is describing is a BCP, not an Informational RFC.
>
> To be clear here, I did not think Pete's document was going for BCP.  I
remain concerned that the publication of this document as an an
AD-sponsored Informational RFC will impute status to it as a community
conclusion, rather than the start of a conversation (or, rather, the
continuation of one).  Some of the comments of "I've wanted something like
this to hand to..." are part of what cause me to believe that.

And, to re-iterate, I do not think the document is ready, even if the IESG
believes that a document of this type should be published; it needs a much
clearer sense of audience as well as attention to the other points that
have been raised.

regards,

Ted

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

<div dir=3D"ltr">On Mon, Oct 7, 2013 at 1:35 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><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 Oct 7, 2013, at 3:34 PM=
, Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">bria=
n.e.carpenter@gmail.com</a>&gt; wrote:<br>

&gt; So I&#39;d like to dispute Ted&#39;s point that by publishing a versio=
n of<br>
&gt; resnick-on-consensus as an RFC, we will engrave its contents in stone.=
<br>
&gt; If that&#39;s the case, we have an even deeper problem than misunderst=
andings<br>
&gt; of rough consensus.<br>
<br>
</div>Right, I think what Ted is describing is a BCP, not an Informational =
RFC.<br>
<br>
</blockquote></div>To be clear here, I did not think Pete&#39;s document wa=
s going for BCP.=A0 I remain concerned that the publication of this documen=
t as an an AD-sponsored Informational RFC will impute status to it as a com=
munity conclusion, rather than the start of a conversation (or, rather, the=
 continuation of one).=A0 Some of the comments of &quot;I&#39;ve wanted som=
ething like this to hand to...&quot; are part of what cause me to believe t=
hat.<br>
<br></div><div class=3D"gmail_extra">And, to re-iterate, I do not think the=
 document is ready, even if the IESG believes that a document of this type =
should be published; it needs a much clearer sense of audience as well as a=
ttention to the other points that have been raised.<br>
<br>regards,<br><br>Ted<br></div></div>

--20cf303344f9b4919404e83c92fb--

From dhc@dcrocker.net  Tue Oct  8 08:48:25 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 AA73F21E81F1; Tue,  8 Oct 2013 08:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.001
X-Spam-Level: 
X-Spam-Status: No, score=-6.001 tagged_above=-999 required=5 tests=[AWL=0.598,  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 2tmKJAk9Fxi9; Tue,  8 Oct 2013 08:48:20 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFB921E8186; Tue,  8 Oct 2013 08:48:20 -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 r98Fm6gV030565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Oct 2013 08:48:09 -0700
Message-ID: <5254292C.9020809@dcrocker.net>
Date: Tue, 08 Oct 2013 08:47:56 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <CA+9kkMB-x3B5QD9T9Q4eFRH9QSXza8AcB=4=zvmrOqyyUTnFJQ@mail.gmail.com>
In-Reply-To: <CA+9kkMB-x3B5QD9T9Q4eFRH9QSXza8AcB=4=zvmrOqyyUTnFJQ@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, 08 Oct 2013 08:48:10 -0700 (PDT)
Cc: IESG <iesg@ietf.org>, IETF <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, 08 Oct 2013 15:48:25 -0000

On 10/8/2013 8:36 AM, Ted Hardie wrote:
> And what are the RFC numbers for the comments?  If none, as I suspect,
> then the comments aren't the same status as the documents--that's fine
> for RFC 791 and 2460, but it is not clear that Pete's document falls
> into the same class.  I would argue it does not.


Unfortunately the concern you are raising has often been applied to all 
sorts of IETF work.  Many bits of IETF work are subject to on-going 
comments and often reach the practical status of de facto -- or, in the 
case of the errata mechanism, IETF de jure -- modifications to the 
published document.

In fact, the line of argument you raise has frequently been lodged 
against the BCP construct.  Yet we keep finding BCPs useful to create.


    1.  Does the IETF need a modern, thorough, community-approved 
statement of it's consensus model and the application of the model? 
That is, both theory and practice.

        So far, it looks as if the community certainly thinks we do, and 
  strongly agree.  In fact I think we suffer greatly by not having it. 
And as we've gone through multiple generations of participants, we've 
tended towards reliance on catch-phrases, without a shared understanding 
of their deeper meaning and specific practice.  So folks invent their 
own meanings as best they can.  Something like Pete's draft is needed to 
provide shared substance to what we mean when we talk about rough consensus.


    2.  Should the statement be an RFC or something more malleable (and 
therefore ephemeral)?

        Why would we not want something this essential to be available 
through our formal publishing and archiving mechanism?  To the extent 
that later discussions prompt modifications, that's what the errata 
mechanism is for.  And eventual revision to the RFC.  Unless someone 
thinks that this core construct for the IETF is going to be subject to 
constant and fundamental modification???

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stpeter@stpeter.im  Tue Oct  8 08:54:27 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 8835F11E80E9 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 08:54: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 tzYNX7oGvO3o for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 08:54:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA6411E80FB for <ietf@ietf.org>; Tue,  8 Oct 2013 08:53:50 -0700 (PDT)
Received: from ergon.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DCD39414CD; Tue,  8 Oct 2013 09:59:43 -0600 (MDT)
Message-ID: <52542A8B.3000901@stpeter.im>
Date: Tue, 08 Oct 2013 09:53:47 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
In-Reply-To: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
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, 08 Oct 2013 15:54:27 -0000

On 10/7/13 10:48 AM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'On Consensus and Humming in the IETF'
>   <draft-resnick-on-consensus-05.txt> as Informational RFC

I would like to perform a thorough review and provide more detailed
feedback, but time is short right now. Here are a few questions in the
meantime...

The Abstract states:

      It is simply a collection of principles, hopefully around which
      the IETF can come to (at least rough) consensus.

Does that mean you aim to make *this* I-D an IETF stream RFC that will
itself have consensus, or do you instead aim to use this document to
generate discussion that might result in consensus in the future (e.g.,
as a BCP)? If the latter, publishing in the Independent Stream seems
sensible. If the former, then I think we need to have more discussion
(along the lines of other Last Call feedback I've glanced at).

The Introduction states:

   Our ideal is full consensus, but we don't
   require it: Full consensus would allow a single intransigent person
   who simply keeps saying "No!" to stop the process cold.

By "full consensus" do you mean "unanimity"?

And do you think that unanimity or "full consensus" is our ideal,
although an ideal that's not always reachable in practice? Or is our
ideal actually rough consensus (i.e., something like general agreement
without unanimity)?

If unanimity or "full consensus" is our ideal then we might expend more
energy to win over instransigent persons or those who are "in the rough"
than we would if rough consensus were our ideal. So I think it's
important to be clear on what we're aiming for.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stephen.farrell@cs.tcd.ie  Tue Oct  8 09:26:25 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 9B2BE21E809A for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 09:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 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 qEyBeOxG8Sch for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 09:26:21 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 47F8F21E821A for <ietf@ietf.org>; Tue,  8 Oct 2013 09:26:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D1A1CBE51; Tue,  8 Oct 2013 17:26:14 +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 5MEP+ORqB6Pb; Tue,  8 Oct 2013 17:26:14 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B281BBDCA; Tue,  8 Oct 2013 17:26:14 +0100 (IST)
Message-ID: <52543226.7060107@cs.tcd.ie>
Date: Tue, 08 Oct 2013 17:26:14 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Ralf Skyper Kaiser <skyper@thc.org>, ietf@ietf.org
Subject: Re: IETF 88 Preliminary Agenda
References: <20131004225346.32223.38527.idtracker@ietfa.amsl.com> <CA+BZK2ppnxFKYFBPrG939-LRuukN2bmU1m=K0rXy8UaH+-x8pA@mail.gmail.com>
In-Reply-To: <CA+BZK2ppnxFKYFBPrG939-LRuukN2bmU1m=K0rXy8UaH+-x8pA@mail.gmail.com>
X-Enigmail-Version: 1.5.2
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, 08 Oct 2013 16:26:25 -0000

Hi Ralf,

On 10/07/2013 09:23 PM, Ralf Skyper Kaiser wrote:
> Hi,
> 
> Is it still possible to submit a talk? I would like to speak at the IETF/88
> and a 15-30 minutes slot would be sufficient.
> 
> The topic of my talk is "Transport Layer Security in a Post-Prism Era".

We don't really schedule talks like that.

However, I'd encourage you to write up your ideas in an
internet-draft and post that before Oct 21st (which is
the deadline for posting drafts before the meeting).

And depending on the content, that could be usefully
discussed on either the perpass@ietf.org or tls@ietf.org
lists.

Cheers,
Stephen.

PS: Any questions about details or similar, feel free
to ask me off-list.

> 
> Best Regards,
> 
> Ralf Kaiser
> 
> 
> 
> On Fri, Oct 4, 2013 at 11:53 PM, IETF Agenda <agenda@ietf.org> wrote:
> 
>> The IETF 88 Preliminary Agenda has been posted. The final agenda will be
>> published on Friday, October 11th.
>>
>> https://datatracker.ietf.org/meeting/88/agenda.html
>> https://datatracker.ietf.org/meeting/88/agenda.txt
>>
>> We are still having some difficulty integrating the new agenda tool into
>> the datatracker and as a result some portions of the meeting agenda --
>> beverage and snack breaks, plenaries --  are not yet showing up on the html
>> version. This will hopefully be resolved very soon.
>>
>> More information regarding IETF 88 in Vancouver, BC, Canada is located
>> here: https://www.ietf.org/meeting/88/index.html
>>
>> IETF Secretariat
>>
> 

From Ted.Lemon@nominum.com  Tue Oct  8 09:31:35 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 E048721E8240; Tue,  8 Oct 2013 09:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.575
X-Spam-Level: 
X-Spam-Status: No, score=-106.575 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 1Sg-JfrWqk18; Tue,  8 Oct 2013 09:31:29 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 3952921E8266; Tue,  8 Oct 2013 09:31:29 -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 DSNKUlQzYaD7JubM7G6t9WyCp2q5TYJdQVh2@postini.com; Tue, 08 Oct 2013 09:31:29 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 D1CC61B814F; Tue,  8 Oct 2013 09:31:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 CB699190061; Tue,  8 Oct 2013 09:31:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 8 Oct 2013 09:31:28 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1811\))
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CA+9kkMDMUjnFwYD2NFjiWx0dMmNOFNerXQtwp6urco+F7-ffTA@mail.gmail.com>
Date: Tue, 8 Oct 2013 12:31:27 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <4B683894-92F1-465C-9278-EB8D45AC96C7@nominum.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <F854C30D-78C6-4FCF-BC48-AB1E7C270164@nominum.com> <CA+9kkMDMUjnFwYD2NFjiWx0dMmNOFNerXQtwp6urco+F7-ffTA@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1811)
X-Originating-IP: [192.168.1.10]
Cc: IESG <iesg@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, 08 Oct 2013 16:31:36 -0000

On Oct 8, 2013, at 11:39 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> To be clear here, I did not think Pete's document was going for BCP. 

Indeed, but you are speaking of it as if it were, which was my point.


From otroan@employees.org  Tue Oct  8 10:35:29 2013
Return-Path: <otroan@employees.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 CB79221E8271; Tue,  8 Oct 2013 10:35:29 -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 Qi3qBnT55re9; Tue,  8 Oct 2013 10:35:29 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 6B30D21E8213; Tue,  8 Oct 2013 10:35:29 -0700 (PDT)
Received: from dhcp-10-61-105-20.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5B50C5FF8; Tue,  8 Oct 2013 10:35:28 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 8 Oct 2013 18:16:30 +0200
Message-Id: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 17:35:29 -0000

--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

> Hi, I would like to make a small amendment to what I said in my
> previous message as follows:
>=20
> 4) Section 5, change the final paragraph to:
>=20
>   "As a result of the above mentioned requirements, a packet's header
>   chain length MUST fit within the Path MTU associated with its
>   destination.  Hosts MAY discover the Path MTU, using procedures such
>   as those defined in [RFC1981] and [RFC4821]. However, if a host does
>   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
>   1280 bytes [RFC2460]. The host MUST then limit each packet's header
>   chain length to the Path MTU minus 256 bytes in case additional
>   encapsulation headers are inserted by tunnels on the path."

I would claim that additional encapsulation headers are already =
considered in the 1280 minimum MTU.
as in: 1500 - 1280.

cheers,
Ole


--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSVC/eAAoJEFuJXizso86gh94H/jJKuujErKuYtUuNt+76rscy
wcx5MwBLGTEOhwGmZxhmScKtruLrcjH96v+bmaBKMGXsga+37lyJWd45TB2EeAU2
bePszxUXpStZfSvoFHWhEV424N6IDU8AAq5snbmakWKBwMBYeMxO/hWgf24OazSi
Sn4R62UiJvF8jePMSaiIcGCPFJN+oQGjZB9oh3Eb48+vsSsJ4oC6iIG0idn0AIrB
G79FTpELYujBoam01SUromjpuJuwkHog1MZXySskKIIauFtoh2XuBLeNcH3pklLX
5HLELg78n2oKnswXDj6m2ziB5e10rNHUeUDwRhfIbmQOpOTeQBYA/QWhQ28To4M=
=6pim
-----END PGP SIGNATURE-----

--Apple-Mail=_4799F997-C3FE-4A9C-8293-DC74B62CF3B2--

From ted.ietf@gmail.com  Tue Oct  8 10:49:18 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 C9F0111E81B3; Tue,  8 Oct 2013 10:49: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=[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 K11anrarSNwu; Tue,  8 Oct 2013 10:49:17 -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 9C19011E81B5; Tue,  8 Oct 2013 10:49:14 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id to1so19597366ieb.23 for <multiple recipients>; Tue, 08 Oct 2013 10:49:14 -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=GmIyj9MVvJfXaPWHO9+WopznjCu4J+xayHFAA7oXwkA=; b=HMxXMFpwfVHr/6ZnwNqM81AB9Yybh63FiVuXpcKeGzVP92+kfmO2C8bvWUNXdzn/nx OzwmMmn7VkOdPLHzxXdPSvRCS++30ZIaxSA8+7Vzm3tUZyacNIiuRT8Uq1ZrvkJUDPel N7XyVWAxELMTOIAgcv44nIN+nUaUZnnNap3epf+DXYN0uGZVBeXSfosw4v+x1qWa3GVm QBrx49uVncdeQ3yYKOWfg+xzsB7FGW05TKReW+hIEXKnJOKmf1UZCh96OUZi5jhvSYLG PPJKhMaF6+CBT4mWNZYb7B5opuTv2BN+2EzkiaNtaX7yMoAMbadYcb1sQF1iQnRR4pep XylQ==
MIME-Version: 1.0
X-Received: by 10.42.82.196 with SMTP id e4mr1905204icl.58.1381254553981; Tue, 08 Oct 2013 10:49:13 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Tue, 8 Oct 2013 10:49:13 -0700 (PDT)
In-Reply-To: <5254292C.9020809@dcrocker.net>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com> <52530CCF.8090605@gmail.com> <CA+9kkMB-x3B5QD9T9Q4eFRH9QSXza8AcB=4=zvmrOqyyUTnFJQ@mail.gmail.com> <5254292C.9020809@dcrocker.net>
Date: Tue, 8 Oct 2013 10:49:13 -0700
Message-ID: <CA+9kkMD1Bw0pgmNCGmB-tjnEAveG0TRfhqCBFc9B41z2yjbZJg@mail.gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
From: Ted Hardie <ted.ietf@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=20cf30363fa109271c04e83e63a0
Cc: IESG <iesg@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, 08 Oct 2013 17:49:18 -0000

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

Some comments in-line.

On Tue, Oct 8, 2013 at 8:47 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 10/8/2013 8:36 AM, Ted Hardie wrote:
>
>> And what are the RFC numbers for the comments?  If none, as I suspect,
>> then the comments aren't the same status as the documents--that's fine
>> for RFC 791 and 2460, but it is not clear that Pete's document falls
>> into the same class.  I would argue it does not.
>>
>
>
> Unfortunately the concern you are raising has often been applied to all
> sorts of IETF work.  Many bits of IETF work are subject to on-going
> comments and often reach the practical status of de facto -- or, in the
> case of the errata mechanism, IETF de jure -- modifications to the
> published document.
>
> In fact, the line of argument you raise has frequently been lodged against
> the BCP construct.  Yet we keep finding BCPs useful to create.
>
>
>    1.  Does the IETF need a modern, thorough, community-approved statement
> of it's consensus model and the application of the model? That is, both
> theory and practice.
>
>        So far, it looks as if the community certainly thinks we do, and
>  strongly agree.  In fact I think we suffer greatly by not having it. And
> as we've gone through multiple generations of participants, we've tended
> towards reliance on catch-phrases, without a shared understanding of their
> deeper meaning and specific practice.  So folks invent their own meanings
> as best they can.  Something like Pete's draft is needed to provide shared
> substance to what we mean when we talk about rough consensus.
>
>
If the community believes that we need a community-approved statement of
its  decision-making model and how it is applied, then we should develop one
in a community process.  It may at that point be something that becomes a
BCP.

As an input draft to that discussion or community process, I think Pete's
draft is very useful--it has sparked multiple rounds of discussion.  But I
don't think it is clear that this is its intended function (that "unclear
on the audience bit") and I think it might be read to be a proposed output
document from that process. I don't think it is anywhere near ready to be
considered as an output document, for reasons I already laid out.


>    2.  Should the statement be an RFC or something more malleable (and
> therefore ephemeral)?
>
>        Why would we not want something this essential to be available
> through our formal publishing and archiving mechanism?  To the extent that
> later discussions prompt modifications, that's what the errata mechanism is
> for.  And eventual revision to the RFC.  Unless someone thinks that this
> core construct for the IETF is going to be subject to constant and
> fundamental modification???
>
>
Again, I think this is the question of the document's audience and
function.  If the aim is to use it to spark debate, than ephemeral is
better than fixed.  If it is meant to be a community statement of our
process, in theory and practice, it should be fixed--but this document is
not that community statement in its current form.

regards,

Ted


> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

<div dir=3D"ltr">Some comments in-line.<br><div><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote">On Tue, Oct 8, 2013 at 8:47 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>
<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 10/8/2013 8:36 AM, Ted =
Hardie wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
And what are the RFC numbers for the comments? =A0If none, as I suspect,<br=
>
then the comments aren&#39;t the same status as the documents--that&#39;s f=
ine<br>
for RFC 791 and 2460, but it is not clear that Pete&#39;s document falls<br=
>
into the same class. =A0I would argue it does not.<br>
</blockquote>
<br>
<br></div>
Unfortunately the concern you are raising has often been applied to all sor=
ts of IETF work. =A0Many bits of IETF work are subject to on-going comments=
 and often reach the practical status of de facto -- or, in the case of the=
 errata mechanism, IETF de jure -- modifications to the published document.=
<br>

<br>
In fact, the line of argument you raise has frequently been lodged against =
the BCP construct. =A0Yet we keep finding BCPs useful to create.<br>
<br>
<br>
=A0 =A01. =A0Does the IETF need a modern, thorough, community-approved stat=
ement of it&#39;s consensus model and the application of the model? That is=
, both theory and practice.<br>
<br>
=A0 =A0 =A0 =A0So far, it looks as if the community certainly thinks we do,=
 and =A0strongly agree. =A0In fact I think we suffer greatly by not having =
it. And as we&#39;ve gone through multiple generations of participants, we&=
#39;ve tended towards reliance on catch-phrases, without a shared understan=
ding of their deeper meaning and specific practice. =A0So folks invent thei=
r own meanings as best they can. =A0Something like Pete&#39;s draft is need=
ed to provide shared substance to what we mean when we talk about rough con=
sensus.<br>

<br></blockquote><div><br></div><div>If the community believes that we need=
 a community-approved statement of its=A0 decision-making model and how it =
is applied, then we should develop one<br>in a community process.=A0 It may=
 at that point be something that becomes a BCP.=A0 <br>
<br>As an input draft to that discussion or community process, I think Pete=
&#39;s draft is very useful--it has sparked multiple rounds of discussion.=
=A0 But I don&#39;t think it is clear that this is its intended function (t=
hat &quot;unclear on the audience bit&quot;) and I think it might be read t=
o be a proposed output document from that process. I don&#39;t think it is =
anywhere near ready to be considered as an output document, for reasons I a=
lready laid out.<br>
</div><div>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=A0=A0 2. =A0Should the statement be an RFC or something more malleable (an=
d therefore ephemeral)?<br>
<br>
=A0 =A0 =A0 =A0Why would we not want something this essential to be availab=
le through our formal publishing and archiving mechanism? =A0To the extent =
that later discussions prompt modifications, that&#39;s what the errata mec=
hanism is for. =A0And eventual revision to the RFC. =A0Unless someone think=
s that this core construct for the IETF is going to be subject to constant =
and fundamental modification???<span class=3D"HOEnZb"><font color=3D"#88888=
8"><br>

<br></font></span></blockquote><div><br></div><div>Again, I think this is t=
he question of the document&#39;s audience and function.=A0 If the aim is t=
o use it to spark debate, than ephemeral is better than fixed.=A0 If it is =
meant to be a community statement of our process, in theory and practice, i=
t should be fixed--but this document is not that community statement in its=
 current form.<br>
<br></div><div>regards,<br><br>Ted<br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"HOEnZb"><font color=3D"#888888">
d/<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></div></div></div>

--20cf30363fa109271c04e83e63a0--

From eric.gray@ericsson.com  Tue Oct  8 11:32:08 2013
Return-Path: <eric.gray@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 271BD21E8278 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:32:08 -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 DXt5lqXB5IzE for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:32:02 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9DFA421E8221 for <ietf@ietf.org>; Tue,  8 Oct 2013 11:32:02 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-79-52544fa1b835
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id EC.CB.09414.1AF44525; Tue,  8 Oct 2013 20:32:01 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Tue, 8 Oct 2013 14:32:01 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: RE: The RFC xx99 Series
Thread-Topic: The RFC xx99 Series
Thread-Index: AQHOxE78F+wCIuM0LkqSMiJUQgLhBpnrIHIA
Date: Tue, 8 Oct 2013 18:32:00 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF6441951@eusaamb107.ericsson.se>
References: <20131008175033.22298.53192.idtracker@ietfa.amsl.com>
In-Reply-To: <20131008175033.22298.53192.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLLMWRmVeSWpSXmKPExsUyuXRPuO5C/5Aggy+7LS2ebZzPYnHweAOb A5PHkiU/mTwa2o6xBjBFcdmkpOZklqUW6dslcGX8OnyFtaBFuOLqp43MDYxHhLoYOTkkBEwk flx5yQRhi0lcuLeeDcQWEjjKKPHpaW0XIxeQvYxR4smTNWBFbAIaEsfurGUEsUUEkiQ2HD/I DGILCyhILHy/gQkirijx9uFCqBojiX/Tp4HVsAioSHz+vZS9i5GDg1fAW+LrBl+IXY4Sz0/N YgMJcwo4SdzvigEJMwKd8/0UxFZmAXGJW0/mQ50pILFkz3lmCFtU4uXjf6wQtrLE9zmPWEDG MAtoSqzfpQ/RqigxpfshO4jNKyAocXLmE5YJjKKzkEydhdAxC0nHLCQdCxhZVjFylBanluWm GxlsYgRGwTEJNt0djHteWh5ilOZgURLn/fLWOUhIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD 44wLl85raNz3s2nkTHm6517XoWtTpirFvSiKiHuXncx6Ql9065Kv1f+m3r1dqjCZdfObQoWU Hy3Wu9m9FfvCGPXyNjJU5S57/OShNmsMW05THWtgmsWu3M6kf8o7/0zU4uPtfm03d1noTclV Lg/3N2efZj+Z+5dntWNHSEGrTeEZvyUKGuYOSizFGYmGWsxFxYkA/2sc+1ACAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 18:32:08 -0000

TWF5YmUgd2Ugc2hvdWxkIHJlc2VydmUgUkZDIDMzOTkgZm9yIGFuIEFwcmlsIDFzdCBSRkM/DQoN
Ci0tDQpFDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmLWFubm91bmNl
LWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmdd
IE9uIEJlaGFsZiBPZiBSRkMgU2VyaWVzIEVkaXRvcg0KU2VudDogVHVlc2RheSwgT2N0b2JlciAw
OCwgMjAxMyAxOjUxIFBNDQpUbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdA0KQ2M6IHJzb2NAaWFi
Lm9yZw0KU3ViamVjdDogVGhlIFJGQyB4eDk5IFNlcmllcw0KDQpHcmVldGluZ3MsDQoNClRoZSBS
RkMgRWRpdG9yIGlzIHByb3Bvc2luZyB0byByZXRpcmUgdGhlIHByYWN0aWNlIG9mIHB1Ymxpc2hp
bmcgUkZDcyB4eDk5LCB0aGUgUmVxdWVzdCBmb3IgQ29tbWVudHMgU3VtbWFyeSBmb3IgUkZDIE51
bWJlcnMgeHgwMC14eDk5LiAgSW4gRGVjZW1iZXIgMTk5MSwgUkZDIDEwOTkgd2FzIHRoZSBmaXJz
dCAiUmVxdWVzdCBmb3IgQ29tbWVudHMgU3VtbWFyeSINClJGQyBwdWJsaXNoZWQuICBJdCBwcm92
aWRlcyBhIGxpc3Qgb2YgZG9jdW1lbnQgdGl0bGVzLCBhdXRob3JzLCBkYXRlIG9mIHB1YmxpY2F0
aW9uLCBhbmQgYWJzdHJhY3RzIGZvciBlYWNoIG9mIHRoZSBSRkNzIHB1Ymxpc2hlZCBpbiB0aGUg
cmFuZ2UgMTAwMCAtIDEwOTkuICBTaW5jZSB0aGF0IHRpbWUsIHRocm91Z2ggdGhlIHRpbWUgdGhh
dCBSRkMgMzI5OSB3YXMgcHVibGlzaGVkLCBhIG5ldyBzdW1tYXJ5IFJGQyB3YXMgcHVibGlzaGVk
IGV2ZXJ5IDEwMCBSRkNzLCBhbmQgUkZDIG51bWJlcnMgZW5kaW5nIHdpdGggOTkgd2VyZSByZXNl
cnZlZCBmb3IgdGhlc2Ugc3VtbWFyeSBkb2N1bWVudHMuICBSRkMNCjMzOTkgd2FzIG5ldmVyIHB1
Ymxpc2hlZCAoZm9yIHZhcmlvdXMgcmVhc29ucyksIHRob3VnaCBSRkNzIDM0OTkgYW5kDQozNTk5
IHdlcmUuICBSRkMgMzU5OSB3YXMgdGhlIGxhc3Qgb2YgdGhlc2Ugc3VtbWFyeSBkb2N1bWVudHMg
dG8gYmUgcHVibGlzaGVkIGluIERlY2VtYmVyIDIwMDMuDQoNClRoZXNlIHNuYXBzaG90cyBhcmUg
bm8gbG9uZ2VyIG5lZWRlZCBiZWNhdXNlIHVwLXRvLWRhdGUgZGF0YSBpcyBhdmFpbGFibGUgb25s
aW5lLiAgUkZDIGFic3RyYWN0cyBhcmUgYXZhaWxhYmxlIHVzaW5nIHRoZSBSRkMgc2VhcmNoIGVu
Z2luZSAoaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9zZWFyY2gvcmZjX3NlYXJjaC5waHApIGFu
ZCB0aGV5IGFyZSBpbmNsdWRlZCBpbiByZmMtaW5kZXgueG1sLiAgUkZDcyB4eDk5IHN1bW1hcmll
cyB3ZXJlIG5ldmVyIHJlcXVlc3RlZCBieSB0aGUgSW50ZXJuZXQgQ29tbXVuaXR5IGFuZCBhcmUg
bm90IGN1cnJlbnRseSBmaWxsaW5nIGEgbmVlZDsgdGhlcmVmb3JlLCB0aGUgUkZDIEVkaXRvciBp
cyByZXRpcmluZyB0aGUgcHVibGljYXRpb24gb2YgdGhlIFJGQyBzdW1tYXJ5IGRvY3VtZW50cy4N
ClJGQyBudW1iZXJzIHR5cGljYWxseSByZXNlcnZlZCBmb3IgdGhlc2UgZG9jdW1lbnRzIChpLmUu
LCBudW1iZXJzIGVuZGluZyB3aXRoIDk5KSBtYXkgYmUgYXNzaWduZWQgdG8gZnV0dXJlIFJGQ3Mu
DQoNCklmIHRoZXJlIGFyZSBhbnkgY29uY2VybnMgYWJvdXQgdGhpcyBjb3Vyc2Ugb2YgYWN0aW9u
LCBwbGVhc2UgY29tbWVudCBieSBPY3RvYmVyIDE4LCAyMDEzLCBvbiB0aGUgcmZjLWludGVyZXN0
QHJmYy1lZGl0b3Iub3JnIG1haWxpbmcgbGlzdC4NCg0KVGhhbmsgeW91LA0KSGVhdGhlciBGbGFu
YWdhbiwgUlNFDQo=

From Fred.L.Templin@boeing.com  Tue Oct  8 11:34:06 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1F121E828A; Tue,  8 Oct 2013 11:34:06 -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 yghdhBE3N+Mk; Tue,  8 Oct 2013 11:34:00 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 3810E21E8278; Tue,  8 Oct 2013 11:34:00 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r98IXxgR008418; Tue, 8 Oct 2013 13:33:59 -0500
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r98IXwhd008382 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 8 Oct 2013 13:33:59 -0500
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-06.nw.nos.boeing.com (130.247.25.110) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 8 Oct 2013 11:33:58 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.159]) with mapi id 14.02.0328.011; Tue, 8 Oct 2013 11:33:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxEzPebc9KTehbEGO6mhunuAlj5nrHdCQ
Date: Tue, 8 Oct 2013 18:33:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
In-Reply-To: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 18:34:06 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Tuesday, October 08, 2013 9:17 AM
> To: Templin, Fred L
> Cc: ietf@ietf.org; IETF-Announce; ipv6@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > Hi, I would like to make a small amendment to what I said in my
> > previous message as follows:
> >
> > 4) Section 5, change the final paragraph to:
> >
> >   "As a result of the above mentioned requirements, a packet's header
> >   chain length MUST fit within the Path MTU associated with its
> >   destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> does
> >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> >   1280 bytes [RFC2460]. The host MUST then limit each packet's header
> >   chain length to the Path MTU minus 256 bytes in case additional
> >   encapsulation headers are inserted by tunnels on the path."
>=20
> I would claim that additional encapsulation headers are already
> considered in the 1280 minimum MTU.
> as in: 1500 - 1280.

It is kind of like that, but what I am concerned about is tunnels
in the path that fragment either because they cannot meet the IPv6
minimum MTU without doing so, or because they are trying to allow
a larger-sized MTU when the path doesn't support it due to the
addition of the encapsulating headers.

Take the simplest case when the host assumes a path MTU of 1280.
If there is a tunnel in the path that crosses another 1280 link,
then the tunnel has to fragment, and the header chain might not
all fit within the first fragment if the host does not allow
headspace room. If the host limits the size of its header chain
to 1280 - 512 =3D 1024 bytes, then the entire chain should fit
within the first fragment even if there are multiple nested
tunnel ingresses on the path and each one of them fragments.

That said, I am wondering how this document relates to the
discussions we had earlier and the resulting draft from Mark
Andrews on what to do when the header chain spans multiple
fragments? Are we trying to keep the header chain all within
the first fragment or not?

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole


From d3e3e3@gmail.com  Tue Oct  8 11:39: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 7E78921E8113 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:39: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=[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 0Lnwxqcj946c for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:39:22 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 55CCE21E8213 for <ietf@ietf.org>; Tue,  8 Oct 2013 11:39:21 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so9203746pab.40 for <ietf@ietf.org>; Tue, 08 Oct 2013 11:39:19 -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:content-transfer-encoding; bh=JOq3C8QjGgWLJTvPeG1cBkT+GDl69hRgcRCZceURiK0=; b=AH3gNqVDXWTxq5WirRX788GfqE6SHO3PCOBuGSuKumY/Zp3dwPmFhW86erXki/hsVd OGqKN+TSkhOE6FSKGnxIcegInFcn8X21cFApnjY2yyW6kzZ0QK5K3wjymu7h4d7TzpKV PQIl6GBZJ5/E6ALC94jWKJoKD27gZK1IvEwGTEqk+JolK/kFV4g/O3aijXc004VfeKlV 4dOFbsE9NbMsM89oe3ZuWTzpNNRGdfPHREgsVoSSUGGHqXhu09TyPOHJ4bi/zo7JY5t/ ZTOKJDhxSGPeJCxFELO+GNVqXwY1+tGIWBiGHE6wpAII+t8w9xioqDv9Ese0sPuaEfDn RF8A==
X-Received: by 10.68.252.68 with SMTP id zq4mr3560928pbc.154.1381257559479; Tue, 08 Oct 2013 11:39:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.70.108.161 with HTTP; Tue, 8 Oct 2013 11:38:59 -0700 (PDT)
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF6441951@eusaamb107.ericsson.se>
References: <20131008175033.22298.53192.idtracker@ietfa.amsl.com> <48E1A67CB9CA044EADFEAB87D814BFF6441951@eusaamb107.ericsson.se>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 8 Oct 2013 14:38:59 -0400
Message-ID: <CAF4+nEEzbKHKGbATwz5xJAJkyoE26b9SpeXSSbDb_FWfOaVSpg@mail.gmail.com>
Subject: Re: The RFC xx99 Series
To: Eric Gray <eric.gray@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "rfc-interest@rfc-editor.org" <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: Tue, 08 Oct 2013 18:39:22 -0000

Or how about reserving "RFC 3399" for use as an example RFC number...

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

On Tue, Oct 8, 2013 at 2:32 PM, Eric Gray <eric.gray@ericsson.com> wrote:
> Maybe we should reserve RFC 3399 for an April 1st RFC?
>
> --
> E
>
> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg] On Behalf Of RFC Series Editor
> Sent: Tuesday, October 08, 2013 1:51 PM
> To: IETF Announcement List
> Cc: rsoc@iab.org
> Subject: The RFC xx99 Series
>
> Greetings,
>
> The RFC Editor is proposing to retire the practice of publishing RFCs xx9=
9, the Request for Comments Summary for RFC Numbers xx00-xx99.  In December=
 1991, RFC 1099 was the first "Request for Comments Summary"
> RFC published.  It provides a list of document titles, authors, date of p=
ublication, and abstracts for each of the RFCs published in the range 1000 =
- 1099.  Since that time, through the time that RFC 3299 was published, a n=
ew summary RFC was published every 100 RFCs, and RFC numbers ending with 99=
 were reserved for these summary documents.  RFC
> 3399 was never published (for various reasons), though RFCs 3499 and
> 3599 were.  RFC 3599 was the last of these summary documents to be publis=
hed in December 2003.
>
> These snapshots are no longer needed because up-to-date data is available=
 online.  RFC abstracts are available using the RFC search engine (http://w=
ww.rfc-editor.org/search/rfc_search.php) and they are included in rfc-index=
.xml.  RFCs xx99 summaries were never requested by the Internet Community a=
nd are not currently filling a need; therefore, the RFC Editor is retiring =
the publication of the RFC summary documents.
> RFC numbers typically reserved for these documents (i.e., numbers ending =
with 99) may be assigned to future RFCs.
>
> If there are any concerns about this course of action, please comment by =
October 18, 2013, on the rfc-interest@rfc-editor.org mailing list.
>
> Thank you,
> Heather Flanagan, RSE

From nomcom-chair@ietf.org  Tue Oct  8 11:45:15 2013
Return-Path: <nomcom-chair@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 5F01321E80B2; Tue,  8 Oct 2013 11:45: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 nZ8kVzv9hhUr; Tue,  8 Oct 2013 11:45:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB3611E80F1; Tue,  8 Oct 2013 11:45:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM 2013 - UPDATED 2nd Call for Nominations - APP, OAM, RAI, TSV
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131008184514.32189.48777.idtracker@ietfa.amsl.com>
Date: Tue, 08 Oct 2013 11:45:14 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 08 Oct 2013 18:45:15 -0000

UPDATE: nominations are too sparse in several of the IESG areas:  APP, OAM,
RAI, and TSV.  If you know one or more of those areas, exercise your social
network and submit nominations.  We'll be very grateful!

Is there someone you work with at IETF who has leadership potential and a
growing track record? Please read this Nomcom call for nominations and cons=
ider
nominating her or him. Or several folks! Deadline for nominations is Octobe=
r 18. =

Nominate soon to give your nominee(s) plenty time to fill in the questionna=
ire.

If you're nominated, even if you support the present incumbent, being revie=
wed
by Nomcom is great IETF experience.  The questionnaire offers a chance to
think about IETF and about your area.  Whether or not your candidacy progre=
sses
this time, you'll have gained some valuable insights, and you'll have contr=
ibuted
greatly. This process only works because many IETFers take part; please joi=
n in.

Lots more, including which positions are open, how to make a nomination
(including nomination of yourself), and how to send us your feedback on
the desired expertise, follows.

IETFers, let's hear from you!  Make nominations, accept nominations!

If you have any questions about the process, feel free to get in touch with=
 me.

Best regards,

Allison for the Nomcom

Allison Mankin
Nomcom Chair 2013-14

----- The Info You Need for Nominating -----

The 2013-14 Nominating Committee (Nomcom) is seeking nominations
from now until October 18, 2013. The open positions being considered
by this year's Nomcom can be found later in this section, and also on
this year's Nomcom website:

https://datatracker.ietf.org/nomcom/2013/

Information about the desired expertise for positions is here:
          https://datatracker.ietf.org/nomcom/2013/expertise

Nominations may be made by selecting the Nominate link at the top of
the Nomcom 2013 home page, or by visiting the following URL:

https://datatracker.ietf.org/nomcom/2013/nominate/

Note that nominations made using the web tool require an ietf.org
datatracker account. You can create a datatracker ietf.org account
if you don't have one already by visiting the following URL:

https://datatracker.ietf.org/accounts/create/

Nominations may also be made by email to nomcom13 at ietf.org.
If you nominate by email, please include the word "Nominate" in the Subject
and indicate in the email who is being nominated, their email address (to
confirm acceptance of the nomination), and the position for which you
are making the nomination. If you use email, please use a separate email for
each person you nominate, and for each position (if you are nominating one
person for multiple positions).

Self-nomination is welcome!  No need to be shy.

Nomcom 2013-14 will follow the policy for "Open Disclosure of Willing
Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of
nominees willing to be considered for positions under review in the
current Nomcom cycle is not confidential". Willing nominees for each
position will be listed in a publicly accessible way - anyone with a
datatracker account may access the lists.  In all other ways, the
confidentiality requirements of RFC 3777/BCP10 remain in effect.  All
feedback and all Nomcom deliberations will remain confidential and will
not be disclosed. =


In order to ensure time to collect sufficient community feedback about
each of the willing nominees, nominations must be received by the
Nomcom on or before October 18, 2013.  Please submit your nominations =

as early as possible for the sake of your nominees, as we've set the
questionnaire submission deadline for October 25, 2013.

The list of people and posts whose terms end with the March 2014 IETF meeti=
ng,
and thus the positions for which we are accepting nominations: =


IAOC
Chris Griffiths

IAB
Bernard Aboba
Marc Blanchet
Ross Callon
Eliot Lear
Hannes Tschofenig

IESG
Barry Leiba (Applications)
Brian Haberman (Internet)
Benoit Claise (Operations and Management)
Gonzalo Camarillo (RAI)
Stewart Bryant (Routing)
Sean Turner (Security)
Martin Stiemerling (Transport)

Please be resourceful in identifying possible candidates for these
positions, as developing our talent is a very crucial requirement for
the IETF.  Also, please give serious consideration to accepting nominations
you receive. =


The summaries of the desired expertise for the positions, developed by the
respective bodies, are found at:

https://datatracker.ietf.org/nomcom/2013/expertise/

In addition to nominations, the Nomcom seeks community input on
the positions themselves.  We need and welcome the community's
views and input on the jobs within each organization. If you
have ideas on the positions' responsibilities (more, less,
different), please let us know.  You can send us email about this to
nomcom13 at ietf.org, and we will use this feedback actively.

Thank you for your help in nominating a great pool of strong and interesting
nominees!

From fernando@gont.com.ar  Tue Oct  8 11:52:12 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD4111E80F2; Tue,  8 Oct 2013 11:52: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zOdMnHMnVcQ; Tue,  8 Oct 2013 11:52:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1F711E80D9; Tue,  8 Oct 2013 11:52:11 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.101]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1VTcNz-0007lz-Jg; Tue, 08 Oct 2013 20:52:02 +0200
Message-ID: <52545449.2020701@gont.com.ar>
Date: Tue, 08 Oct 2013 15:51:53 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ole Troan <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 18:52:13 -0000

Hi, Fred,

Thanks so much for your feedback! -- Please find my comments in-line...

On 10/08/2013 03:33 PM, Templin, Fred L wrote:
>> I would claim that additional encapsulation headers are already
>> considered in the 1280 minimum MTU.
>> as in: 1500 - 1280.
> 
> It is kind of like that, but what I am concerned about is tunnels
> in the path that fragment either because they cannot meet the IPv6
> minimum MTU without doing so, or because they are trying to allow
> a larger-sized MTU when the path doesn't support it due to the
> addition of the encapsulating headers.
> 
> Take the simplest case when the host assumes a path MTU of 1280.
> If there is a tunnel in the path that crosses another 1280 link,
> then the tunnel has to fragment, 

Well, at least in theory, the tunnel could do Path-MTU... In which case,
if the underlying MTU is of, say, 1500 bytes, then you can probably go
through several layers of encapsulation, without problem.

Besides, while one would probably would nto phrase it like this, truth
is that even 512 f headers would be pretty much non-sensical: Headers
are overhead. So at the point in which you have 50$ of overhead in every
single packet, it starts looking that the inforation is probably being
conveyed in thr wrong place.

That is, in the real world, you would not even get to 1K headers even
ater several layers of encapsulation.


> That said, I am wondering how this document relates to the
> discussions we had earlier and the resulting draft from Mark
> Andrews on what to do when the header chain spans multiple
> fragments? Are we trying to keep the header chain all within
> the first fragment or not?

Yes.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fred@cisco.com  Tue Oct  8 12:06:10 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 218F821F994A; Tue,  8 Oct 2013 12:06: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 uPh8gBl9YUyS; Tue,  8 Oct 2013 12:06:03 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 88B7E21F9AD5; Tue,  8 Oct 2013 12:05:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1814; q=dns/txt; s=iport; t=1381259102; x=1382468702; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=7/w9082FBjX8YY9AR+MOI5jTcMbaE7pT/MUNk7RPcck=; b=Xg1OULc6xOeooksDD8csjORdhGEBO8WWQ36CTSBDaQBTCp4heQnIGHRf SOi2QBoVfq0ttlP1kyTTbSuirq83CEAoy/xSSCeIUc4HFeu1OJUDOfnwJ yCPv26bNs1/Dtq6SKphRAITV/PCc3AyFfMo8fmKvTdPluIHl5Ua18TR8v k=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFALhWVFKtJV2d/2dsb2JhbABZgweBCsElgSIWdIIlAQEBAwF5BQsCAQgiGQshESUCBA4FCAaHZgMJBrEmDYlrjFeCOjEHgx+BBAOQKIEwggqCNo4zhTaBZoE+gio
X-IronPort-AV: E=Sophos;i="4.90,1058,1371081600";  d="asc'?scan'208";a="269713148"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 08 Oct 2013 19:05:02 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r98J51Lu011735 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Oct 2013 19:05:02 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Tue, 8 Oct 2013 14:05:01 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and	Humming in the IETF) to Informational RFC
Thread-Topic: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and	Humming in the IETF) to Informational RFC
Thread-Index: AQHOw30s0TWcxGWP6Uu+rrPHqasxUpnp7MeAgAGThQA=
Date: Tue, 8 Oct 2013 19:05:01 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA5F628@xmb-rcd-x09.cisco.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
In-Reply-To: <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_F0F564E5-6FCE-4E59-9C24-4322B11C2270"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>, 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, 08 Oct 2013 19:06:10 -0000

--Apple-Mail=_F0F564E5-6FCE-4E59-9C24-4322B11C2270
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 7, 2013, at 12:03 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Lastly, I think Pete has failed to capture that one reason for using =
humming or hands is that it is easy for very active participants to =
dominate a conversation
> but much less easy for them to pretend to be a large group.  =
Particularly in BoFs, using those methods to indicate the likely breadth =
of interest is critical.  The same method can be used, with some of the =
caution Pete recommends, to gauge whether an issue which appears to be =
contentious based on a mic line is actually a problem.  It can also, in =
some cases, be a valuable method of reinforcing the resolve a room that =
has already likely come to a broad agreement.  That does not contravene =
Pete's point that this should not be used to silence objections, but =
there are cases where it is important in its own right.

In my working group, that is the principal use of a hum. It is useful =
when a set of people have made a viewpoint known, and the chairs are =
trying to see if that represents a general view, or whether a focused =
minority is speaking.=20

--Apple-Mail=_F0F564E5-6FCE-4E59-9C24-4322B11C2270
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSVFgabjEdbHIsm0MRAiMmAKD46uYISwReP8AnRRG24dEkPsRiQgCg5pxB
3tmx4Ag5zBvP8dZsHx8j4Ro=
=X4bf
-----END PGP SIGNATURE-----

--Apple-Mail=_F0F564E5-6FCE-4E59-9C24-4322B11C2270--

From jabley@hopcount.ca  Tue Oct  8 12:45:58 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 90BAB21F9CC2 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 12:45: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=[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 iHGNtF3Vfint for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 12:45:56 -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 DACD421F9C33 for <ietf@ietf.org>; Tue,  8 Oct 2013 12:45:38 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kp14so9389602pab.10 for <ietf@ietf.org>; Tue, 08 Oct 2013 12:45:37 -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; bh=OmikCGbxVp7e3QyTtTZ4dkRyZUOGbJeqwnxpjeNHZOA=; b=JOIwGU24tgT3q+qNxMON8vU1ZovbF77Zl686qxgGD08xm8Kyg41mAqYXLrQZhUscGx /B7yYWs9JhnH+9c8Qch1zsFvXYwifkF7Y7GPpBHhXihWDqd+2qRe4pUcdWgB1BpPlO0n FoG9h7y/iOcLislsQ3T1E15VWCR3Ij97NWGZA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=OmikCGbxVp7e3QyTtTZ4dkRyZUOGbJeqwnxpjeNHZOA=; b=jm9CaRz9P7SvBeBGqbQ+1diGx5UHYY6CpeELhbmpXSizBAYCgOKIBxpV8wEgpBou8g tptLBpArICNutAxKEmT6s2M52UxcuWtJxaYg0rwEj6+8Lqy9pYg+059DjTodKWkVNaA5 UMuYX1jkMPyxKiyjO215e0MkFvvDXBZdLSwXu+KOChL2ChswOthHzw6lOhO0h4CBd97z Sp2ryB4Vxmz5fKeSuO4+7Sl0kCk/k41pSQML6s43+OrblvuTLqa7zjvwLBgYtw3ThWol lH+wxKCFHJb7fRm4skOEKizKfKtek6siz8tkAA05Mjq/q1yDEG7EKvzDA0Uh9vAEqsAI xFNw==
X-Gm-Message-State: ALoCoQnsKQ8pzh+Z3foxPE8FMbXep7HclnnC2Q7rmYeZ6KqTWU1yY7h/2GqAEcUpnLl1jizw9cNN
X-Received: by 10.66.226.46 with SMTP id rp14mr5420137pac.133.1381261537685; Tue, 08 Oct 2013 12:45:37 -0700 (PDT)
Received: from static-219-138.meetings.nanog.org (static-219-138.meetings.nanog.org. [199.187.219.138]) by mx.google.com with ESMTPSA id lm2sm49413350pab.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 12:45:36 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: The RFC xx99 Series
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <CAF4+nEEzbKHKGbATwz5xJAJkyoE26b9SpeXSSbDb_FWfOaVSpg@mail.gmail.com>
Date: Tue, 8 Oct 2013 12:45:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <052FFAC0-0EDA-4BCF-BF7D-481248BD7CA3@hopcount.ca>
References: <20131008175033.22298.53192.idtracker@ietfa.amsl.com> <48E1A67CB9CA044EADFEAB87D814BFF6441951@eusaamb107.ericsson.se> <CAF4+nEEzbKHKGbATwz5xJAJkyoE26b9SpeXSSbDb_FWfOaVSpg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "rfc-interest@rfc-editor.org" <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: Tue, 08 Oct 2013 19:45:58 -0000

On 2013-10-08, at 11:38, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Or how about reserving "RFC 3399" for use as an example RFC number...

Do we need a document to document that document for use in documents as =
documentation?


Joe


From linda.dunbar@huawei.com  Tue Oct  8 13:18:39 2013
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F3F21F9C47 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 13:18:39 -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 jLQXl+K21Ocz for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 13:18:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 21BE021F9BF7 for <ietf@ietf.org>; Tue,  8 Oct 2013 13:18:34 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYS60003; Tue, 08 Oct 2013 20:18:32 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 8 Oct 2013 21:18:00 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 8 Oct 2013 21:18:30 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.209]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.03.0146.000; Tue, 8 Oct 2013 13:18:23 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service Provider) to	Informational RFC
Thread-Topic: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service Provider) to	Informational RFC
Thread-Index: AQI/ndlfzgUZlnPbGghF8PiUqVuXwpkH30OggAAazqCAAYpg4A==
Date: Tue, 8 Oct 2013 20:18:22 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645BD4A63@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.153.169]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 20:18:39 -0000

Adrian,=20

Thanks for sharing this draft. This is a very good draft to summarize SDN f=
or carrier networks.=20

Two comments:
- 100% Agree with the draft on the emphasis of PDP (Policy Decision Point) =
and PEP (Policy enforcement Point) components of SDN. why does the draft em=
phasize that "SDN approach should be global, network-wide"? Here are a coup=
le of examples that SDN is not global based:

1) The wireless' PCRF (Policy and Charging rules function) and PCEF (Policy=
 Charging Enforcement Function) are good examples of SDN. However, PCRF and=
 PCEF only control the access segments, not global network.=20

2) In data center, centralized controller(s), with the information passed f=
rom VM management system,  can define (virtual) networks to interconnect Vi=
rtual machines. This network is local to Data Center, not necessarily globa=
l based.=20
 =20

- We all understand the challenges of "Full Automation". However, the SDN a=
nd Full automation are two separate angles to Carrier networks. I find the =
Section 4.1  "Implications of full automation" actually de-rails the focus =
of the draft on SDN.=20


My two cents.=20

Linda=20
 =20

> -----Original Message-----
> From: sdn-bounces@irtf.org [mailto:sdn-bounces@irtf.org] On Behalf Of
> Adrian Farrel
> Sent: Monday, October 07, 2013 1:49 PM
> To: sdn@irtf.org
> Subject: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt>
> (Software-Defined Networking: A Perspective From Within A Service
> Provider) to Informational RFC
>=20
> Heads up!
>=20
> This document which was discussed from time-to-time in the SDNRG is
> going for
> IETF last call as an AD-sponsored independent submission.
>=20
> Review comments are welcome as always. Please follow the instructions
> in the
> email below.
>=20
> Thanks,
> Adrian
>=20
> > -----Original Message-----
> > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> > bounces@ietf.org] On Behalf Of The IESG
> > Sent: 07 October 2013 19:40
> > To: IETF-Announce
> > Subject: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-
> Defined
> > Networking: A Perspective From Within A Service Provider) to
> Informational RFC
> >
> >
> > The IESG has received a request from an individual submitter to
> consider
> > the following document:
> > - 'Software-Defined Networking: A Perspective From Within A Service
> >    Provider'
> >   <draft-sin-sdnrg-sdn-approach-04.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-11-04. 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
> >
> >    Software-Defined Networking (SDN) has been one of the major buzz
> >    words of the networking industry for the past couple of years.
> And
> >    yet, no clear definition of what SDN actually covers has been
> broadly
> >    admitted so far.  This document aims at contributing to the
> >    clarification of the SDN landscape by providing a perspective on
> >    requirements, issues and other considerations about SDN, as seen
> from
> >    within a service provider environment.
> >
> >    It is not meant to endlessly discuss what SDN truly means, but
> rather
> >    to suggest a functional taxonomy of the techniques that can be
> used
> >    under a SDN umbrella and to elaborate on the various pending
> issues
> >    the combined activation of such techniques inevitably raises.  As
> >    such, a definition of SDN is only mentioned for the sake of
> >    clarification.
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-sin-sdnrg-sdn-approach/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-sin-sdnrg-sdn-approach/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
>=20
> _______________________________________________
> sdn mailing list
> sdn@irtf.org
> https://www.irtf.org/mailman/listinfo/sdn

From fluffy@cisco.com  Tue Oct  8 13:31:04 2013
Return-Path: <fluffy@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 65FB521F99DD; Tue,  8 Oct 2013 13:31:03 -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 ZiLFae1wY0ib; Tue,  8 Oct 2013 13:30:57 -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 CC84021F9E6A; Tue,  8 Oct 2013 13:30:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4502; q=dns/txt; s=iport; t=1381264238; x=1382473838; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=O2Skf5ZXfSNfBnucdwDsvEcjTAv7fhWXJ41CeQKOtuI=; b=XPx5inqYFF+H2g07AgEvHiOPmLC2GTXlNCPHM8Re6AwchBV0wPMvmuwC yZXBYbVBdwhKjD7b2n8UAVW2IGxUNpypwpMEIvusEQzvq3aZOQLcqjC7R uEBo+UYLdwQODo5mGeJAVg/jxiwHT7tPpW5qHf48FiHI4O3o1GtOyYnoN 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AowFABRrVFKtJV2c/2dsb2JhbABZgwc4UsEngSMWbQeCJQEBAQMBbgsQAgEIIhkLMhQRAgQOBQiHeAYMulSOCoEFAjEHgx+BBAOZMJBRgWaBPoIq
X-IronPort-AV: E=Sophos;i="4.90,1058,1371081600"; d="scan'208";a="269694375"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 08 Oct 2013 20:30:37 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r98KUb12022768 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Oct 2013 20:30:37 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 8 Oct 2013 15:30:36 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Index: AQHOxGU+x36dkMJ3pkem9MOxfSCBUg==
Date: Tue, 8 Oct 2013 20:30:36 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com>
In-Reply-To: <20130919215457.30925.98345.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5275A41775A20145A8667DA6B35F94CD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Oct 2013 20:31:04 -0000

(Dear OPs ADs, please read =85 )


I disagree with the advice in section 8.  Cisco IP phones have been deploye=
d with DHCP options that use FQDN and with options that use IP addresses. F=
or this type of use case the FQDM turned out to be much better from an oper=
ational and administration point of view. IT departments are used to making=
 sure that changes of IP addresses on servers are well coordinated with cha=
nges to the DNS - they are good at doing that and that and have good tools =
for it. Conversely, they are not used to coordinating server changes with D=
HCP changes and do not have good tools for that. Part of why you can't do t=
his with DHCP is that clients are written so that when an IP address fails =
to work for an application connection, the application re does the DNS and =
gets the new address (assuming TTL had been moved down during the move). Ap=
plications can not tell the  OS to redo DHCP when they fail an application =
level connection.=20

For nearly every case in the real world, the power and RTT and reliability =
issues are simply not relevant -   regardless of which way you do it, the a=
pplication is unlikely to work if DNS is down, the extra RTT make no speed =
difference the user can percieve and the power difference over a day of use=
 of the application is so small it is not measurable.=20

FQDN allow usage of things like DNS SRV for load balancing, happy eye balls=
 for v6 transition, and make it easier to get things to geographically clos=
e servers.=20

I don't think it should come a a shock to anyone that the level of indirect=
ion that FQDNs provides turns out to be a really useful tool. Lets use that=
 indirection tool where appropriate.=20


Related to this, the advice in section 12 seems a bit off to me. I understa=
nd the issues - but keep in mind that many modern applications (browsers an=
d SIP phones for example) do the DNS inside the application instead of usin=
g the OS resolvers. Part of the reason for this is asynchronous resolution =
but part of it is also control of which interface is used for DNS and if mu=
ltiple interfaces are used, being able to keep the applications traffic on =
the the appropriate interface for the DNS server that returned the address.=
 So while I agree that=20

"Existing nodes cannot be assumed to systematically segregate
   configuration information on the basis of its source;"

Equally true is you can't assume the converse of that. So I think the state=
ment that=20

   As a consequence, DNS
   resolution done by the DHCP server is more likely to behave
   predictably than DNS resolution done on a multi-interface or multi-
   homed client.

Is just plain wrong. I think it would be more accurate to say in these case=
s the results are not always predictable. The issue is the DHCP server may =
get an DNS answer that contains and server that can not even be reached by =
the DHCP client.=20

As a general rule of thumb, using FQDN in the configuration of a DHCP serve=
r is a really bad idea because IT admins assume that if they change the the=
 DNS information, the clients will get the new information. But they don't.=
=20


Cullen







On Sep 19, 2013, at 3:54 PM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from the Dynamic Host Configuration WG
> (dhc) to consider the following document:
> - 'Guidelines for Creating New DHCPv6 Options'
>  <draft-ietf-dhc-option-guidelines-14.txt> as Best Current Practice
>=20
> 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-10-03. 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.
>=20
> Abstract
>=20
>=20
>   This document provides guidance to prospective DHCPv6 Option
>   developers to help them creating option formats that are easily
>   adoptable by existing DHCPv6 software.  This document updates
>   RFC3315.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20


From ben@nostrum.com  Tue Oct  8 13:40:07 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 B79A321F918C; Tue,  8 Oct 2013 13:40:07 -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 2fmH+dLa+yAu; Tue,  8 Oct 2013 13:40:07 -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 E80A821F9D39; Tue,  8 Oct 2013 13:39:58 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r98Kdvuh057976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Oct 2013 15:39:58 -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 Telechat Review of draft-yusef-dispatch-ccmp-indication-06
Date: Tue, 8 Oct 2013 15:39:57 -0500
Message-Id: <6C5232DC-1221-4C87-8A9C-ABA457A1FC13@nostrum.com>
To: "draft-yusef-dispatch-ccmp-indication.all@tools.ietf.org" <draft-yusef-dispatch-ccmp-indication.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org \(gen-art@ietf.org\)" <gen-art@ietf.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: Tue, 08 Oct 2013 20:40:07 -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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-yusef-dispatch-ccmp-indication-06
Reviewer: Ben Campbell
Review Date: 2013-10-08
IESG Telechat date: 2013-10-10

Summary: This draft is ready for publication as an informational RFC. =
This version addresses all the comments from my last call review of =
version 04. I do have a couple of new (or I missed the first time) =
editorial comments that might be worth addressing if there is a new =
version prior to approval.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- General:

idnits 2.12.18 reports some missing references--please check.

-- Abstract and Intro

Please expand UA and XCON on first mention (Both in Abstract and in =
Section 1).


From ben@nostrum.com  Tue Oct  8 13:50:18 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 A053021F9FD6; Tue,  8 Oct 2013 13:50:18 -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 rmBlyc+W03Jo; Tue,  8 Oct 2013 13:50:18 -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 AEBE121F9E80; Tue,  8 Oct 2013 13:50:17 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r98KoGF7059152 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Oct 2013 15:50:16 -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 Telechat Review of draft-ietf-intarea-flow-label-balancing-02
Date: Tue, 8 Oct 2013 15:50:16 -0500
Message-Id: <9BDC86EA-FBC6-400B-8ABF-2D88CB775F96@nostrum.com>
To: "draft-ietf-intarea-flow-label-balancing.all@tools.ietf.org" <draft-ietf-intarea-flow-label-balancing.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org \(gen-art@ietf.org\)" <gen-art@ietf.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: Tue, 08 Oct 2013 20:50:18 -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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-intarea-flow-label-balancing-02
Reviewer: Ben Campbell
Review Date: 2013-10-08
IESG Telechat date: 2013-10-10

Summary: This version is ready for publication as an informational RFC. =
All of the comments from my previous last call review have been =
addressed either in this version or in email correspondence.=20

Major issues: None

Minor issues: None

Nits/editorial comments: None

From Ted.Lemon@nominum.com  Tue Oct  8 14:38:27 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 D6D1621F9425; Tue,  8 Oct 2013 14:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 e8GjRvGWcHF6; Tue,  8 Oct 2013 14:38:21 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id D6A0A21F9E36; Tue,  8 Oct 2013 14:38:12 -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 DSNKUlR7QzyilopJqYkJl6Dx3Zbkv4gYEYJs@postini.com; Tue, 08 Oct 2013 14:38:12 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 A82C21B82DF; Tue,  8 Oct 2013 14:38:11 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 6630F190061; Tue,  8 Oct 2013 14:38:10 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 8 Oct 2013 14:38:10 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com>
Date: Tue, 8 Oct 2013 17:38:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <EF97C65E-A58C-4076-B737-014126786442@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@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, 08 Oct 2013 21:38:28 -0000

On Oct 8, 2013, at 4:30 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:
> Part of why you can't do this with DHCP is that clients are written so =
that when an IP address fails to work for an application connection, the =
application re does the DNS and gets the new address (assuming TTL had =
been moved down during the move). Applications can not tell the  OS to =
redo DHCP when they fail an application level connection.=20

This use case is a good example of when to use an FQDN format for a DHCP =
option.   However, it's not a great example of when to use a DHCP =
option=97configuring SIP servers with DHCP is generally a bad idea, =
because if your device is connected to a new network, it will blindly =
take the SIP server IP address or FQDN information from the DHCP server =
and use it, and that SIP server might well perform an MitM attack or the =
like.

So it's only in the very restricted use case of a Cisco IP phone =
permanently installed on a desktop and connected to a trusted network =
that (a) configuring SIP via DHCP makes sense, and (b) using the FQDN is =
a good idea.   Of course it's possible that my limited understanding of =
how SIP works is preventing me from seeing why it's safe to configure =
SIP service using DHCP, but I'm assuming that that's not the case in =
this argument; please feel free to correct me.

We've actually been having this same conversation on the iesg mailing =
list, and I asserted that SIP was something you ought not to configure =
with DHCP; your use case is the one case where it sort of makes sense.   =
Can you think of similar use cases where it actually makes sense to =
configure these parameters via DHCP?

Possibly the right solution is to update the document to talk about this =
sort of restricted use case as one where FQDNs actually do make sense.   =
The document certainly doesn't say you _can't_ use FQDNs, but we see =
people wanting to use them a lot in cases where they really don't make =
sense, hence the advice.   Historically I don't think we bothered to =
make this distinction when defining new DHCP options, but it seems like =
a useful distinction to make.


From sm@elandsys.com  Tue Oct  8 15:37:29 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 B548211E80E6 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 15:37: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 q6SlS7zSX5+f for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 15:37:28 -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 543D311E8127 for <ietf@ietf.org>; Tue,  8 Oct 2013 15:36:51 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.128]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r98MaYep025523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Oct 2013 15:36:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381271807; bh=IA52NiJSLj7WTZucQXdAtrvHjbxx2z/VMQaboLFITW8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CoUW70fBh365J/cipolb4ibQAXYe1blIORDekMbYynC6jCJIDSJ2jPC7WnnKix2R1 yy8cPID12Gm2sodsgfVFGeF5wFMmk4PvptikzcvlqpkzTypL/QlMZddd0m7zWvmXW+ sj9GkYg3yjcJdJBWJmTp2OAXwr4PhRBOA0V9q70I=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1381271807; i=@elandsys.com; bh=IA52NiJSLj7WTZucQXdAtrvHjbxx2z/VMQaboLFITW8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AdOZXdpuJHHrFTOhsS7GC5LCVF2Aj3HsR/6PdedORSkYhVitpGMMlZg/feVhT6eD4 BOX4Dvnywc91j98Tj2KcaI/9RYGm2NVfF3j5U3DMPXeBChGXTwTRZp9TwiK5MXyVkm 2QAjneiU/edVOM+XacEwU0PQXqB2JLb+J5su2Usg=
Message-Id: <6.2.5.6.2.20131008054041.0d74aa88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Oct 2013 13:56:14 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
In-Reply-To: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 08 Oct 2013 22:37:29 -0000

At 09:48 07-10-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'On Consensus and Humming in the IETF'
>   <draft-resnick-on-consensus-05.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-11-04. Exceptionally, comments may be

I found the review by Dave Crocker [1] interesting.  Instead of 
reading the latest revision of the draft I wrote a draft [2].  I read 
what Pete Resnick said about consensus after that to compare notes.

The intended status of draft-resnick-on-consensus-05 is 
Informational.  What we have here is a document about consensus which 
will reflect the consensus of the IETF.  Should the document reflect 
the consensus of the IETF or not?

In Section 1:

   'Our ideal is full consensus, but we don't require it: Full consensus
    would allow a single intransigent person who simply keeps saying
    "No!" to stop the process cold.'

The above introduces the term "full consensus".  I took a quick look 
and I found at least one occurrence of the term in IETF discussions 
[3].  However, none of the IETF process documents use that term.

   "If the chair of a working group determines that a technical issue
    brought forward by an objector has been truly considered by the
    working group, and the working group has made an informed decision
    that the objection has been answered or is not enough of a
    technical problem to prevent moving forward, the chair can declare
    that there is rough consensus to go forward, the objection
    notwithstanding."

The word "objector" emphasizes that there is one person who 
dissents.  My preference is to consider the objection and address it 
instead of viewing the issue as dissent from one person.

    "This document attempts to explain some features of rough consensus,
     explain what is not rough consensus, and suggest ways that we might
     achieve rough consensus and judge it in the IETF."

The title of the document is "on consensus and humming in the 
IETF".  According to the above sentence the document attempts to 
discuss about rough consensus.  In my opinion there a nuance between 
"consensus" and "rough consensus".  As a quick reaction I would say 
that rough consensus provides a faster path to shape up a 
proposal.  It helps to cut down on document delivery time to the 
IESG.  The consensus part is sought by getting a broader perspective.

Section 2 sounds like objection-based processing.  A binary choice 
(re. technical question) can end up polarizing a discussion.  The 
section provides a good discussion about lack of disagreement.

One of the questions I wondered about is whether the person making 
the determination should use technical judgement or whether the 
person should only make a determination about the comments 
received.  I mentioned in an unrelated discussion that if it is the 
consensus of the group that the sky is green, that's what goes in the 
document.  The person making the determination can flag it as an 
issue as a matter of technical judgement.  I'll highlight a point 
from Section 3:

   "Remember, if the objector feels that the issue is so essential that it
    must be attended to, they always have the option to file an appeal."

There are very few people who exercise that option.

According to the title of Section 4 humming should be the start of a 
conversation, not the end.  BCP 25 states that:

   "Consensus can be determined by a show of hands, humming, or any
    other means on which the WG agrees (by rough consensus, of course)."

I am not sure whether hums are for a starting point or not.  It can 
be argued in different ways, for example, see Section 4.  Humming 
helps to get a sense of the room without people making a decision 
under duress.  It is a useful way to resolve a controversy.  I would 
say that it ties in Section 5, i.e. consensus is the path, not the 
destination.  A show of hands is a disguised way to vote [4].

Section 5 identifies a few issues with the way people talk about 
"consensus".  I understand what Pete Resnick wrote as he has 
explained that to me in an unrelated discussion.  The text discusses 
about "making the call".  I don't know whether the reader will easily 
understand the meaning of that.

Section 6 and Section 7 attempt to explain that a high percentage of 
votes in a direction does not necessarily mean that there is rough 
consensus for that.  I agree with the conclusion in Section 8.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/ietf/current/msg82843.html
2. http://tools.ietf.org/html/draft-moonesamy-consensus-00
3. http://www.ietf.org/mail-archive/web/isms/current/msg00943.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg25014.html  


From ben@nostrum.com  Tue Oct  8 15:49:09 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 A779321F9339; Tue,  8 Oct 2013 15:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.45
X-Spam-Level: 
X-Spam-Status: No, score=-101.45 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, 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 sETQt8ulR-7F; Tue,  8 Oct 2013 15:49:09 -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 438C321F9DAA; Tue,  8 Oct 2013 15:49:04 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r98Mn05g072035 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Oct 2013 17:49:01 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Gen-ART LC Review of draft-ietf-l2vpn-pbb-vpls-interop-05
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <69670F7146898C4583F56DA9AD32F77B215BDA7B@xmb-aln-x13.cisco.com>
Date: Tue, 8 Oct 2013 17:49:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC9CEDBC-864B-48EC-81EE-EE776B0D8246@nostrum.com>
References: <69670F7146898C4583F56DA9AD32F77B215BDA7B@xmb-aln-x13.cisco.com>
To: Ali Sajassi (sajassi) <sajassi@cisco.com>
X-Mailer: Apple Mail (2.1510)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "draft-ietf-l2vpn-pbb-vpls-interop.all@tools.ietf.org" <draft-ietf-l2vpn-pbb-vpls-interop.all@tools.ietf.org>, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.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: Tue, 08 Oct 2013 22:49:09 -0000

Hi Ali,

Those changes would resolve my comments.=20

Thanks!

Ben.

On Oct 8, 2013, at 5:13 PM, Ali Sajassi (sajassi) <sajassi@cisco.com> =
wrote:

>=20
> Ben,
>=20
> Thanks for your comments. I have incorporated all your comments in =
rev06
> of this draft.
>=20
>=20
> On 9/23/13 1:29 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>=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-ietf-l2vpn-pbb-vpls-interop-05
>> Reviewer: Ben Campbell
>> Review Date: 2013-09-23
>> IETF LC End Date: 2013-09-24
>>=20
>> Summary: Ready for publication as an informational RFC.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> None
>>=20
>> Nits/editorial comments:
>>=20
>> -- Abstract:
>>=20
>> Please expand H-VPLS on first mention
>=20
> Done.
>=20
>>=20
>> -- section 1, 1st paragraph:
>>=20
>> Please expand VPLS on first mention.
>=20
> Done.
>=20
>>=20
>> -- section 4, 3rd to last paragraph: "Different PBB access =
networks..."
>>=20
>> The previous and subsequent paragraphs say "PBBN access networks". =
Should
>> this instance also say PBBN?
>=20
> Done.
>=20
>>=20
>> -- section 4.3:
>>=20
>> 2nd paragraph says this scenario is applicable to "Loosely Coupled
>> Service Domains" and "Different Service Domains". The 4th paragraph
>> mentions "Tightly...". Does that mean the scenario also applies to
>> "Tightly Coupled Service Domains"? (i.e. should it be added to the =
2nd
>> paragraph, or removed from the 4th?)
>>=20
>=20
> Removed "Tightly =8A" from the 4th paragraph.
>=20
> Cheers,
> Ali
>=20


From fallenpegasus@gmail.com  Tue Oct  8 11:50:08 2013
Return-Path: <fallenpegasus@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 17E1D11E80D9 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:50:08 -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 qWOqXG0p-3ei for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 11:50:07 -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 F246621E81AF for <ietf@ietf.org>; Tue,  8 Oct 2013 11:50:05 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id q14so4642265vbe.13 for <ietf@ietf.org>; Tue, 08 Oct 2013 11:50:05 -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:from:date:message-id :subject:to:cc:content-type; bh=Lrcji5w2M+4ZT+1z1QlSRm3u5BQEZHCcEOFQKYHLLxM=; b=h3p6EP/6hw2WM1tNgjZBovW4LkYAW5EULCrSjdWponk532OeVBeWxvBNUJaSKp0fDf pzubG3cSVWw4iPEgH2dQ5dZOUNA5EASfocu+olsRAMe9Y8LJ43ql5cy/tTRwkjTF1VR8 nXO70HfytQ5zDiypuQN5S0PC15cxNHrYS/0HAMluJEhE7QBxVXaQO2lujUz9gEG8kPXo 43rDBliTrVoBfDfaugvETIsVx0tpxzphIsDoBbcjk+GOLnMsqfibLzm6wscS5JRUV9zZ v/ph3oeORoMEGpKU6Kc7Aa71b8/umqjIIrHP8UNavi8UAl0FyeVahSzxSszaZXj09iZj rCQQ==
X-Received: by 10.52.65.136 with SMTP id x8mr1780592vds.23.1381258205386; Tue, 08 Oct 2013 11:50:05 -0700 (PDT)
MIME-Version: 1.0
Sender: fallenpegasus@gmail.com
Received: by 10.52.173.80 with HTTP; Tue, 8 Oct 2013 11:49:45 -0700 (PDT)
In-Reply-To: <20131008175033.22298.53192.idtracker@ietfa.amsl.com>
References: <20131008175033.22298.53192.idtracker@ietfa.amsl.com>
From: Mark Atwood <me@mark.atwood.name>
Date: Tue, 8 Oct 2013 11:49:45 -0700
X-Google-Sender-Auth: p2u_tFROrTZQA7tPo8-SesxJvjo
Message-ID: <CANW5CYWidc=0W+eBudkdSvkfxy=5O-VoowptOtWE0g57n7bK=A@mail.gmail.com>
Subject: Re: The RFC xx99 Series
To: "ietf@ietf.org Ietf@ietf.org" <ietf@ietf.org>, rfc-interest@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Tue, 08 Oct 2013 15:50:17 -0700
Cc: rsoc@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: Tue, 08 Oct 2013 18:50:08 -0000

Hello.

I would like to express my concern about retiring the xx99 RFCs.  I
think they still fill a need, especially over longer periods of time,
and should not be discontinued.

It was stated that they are no longer needed because "up to date
information" is available online, and the RFC search engine is
mentioned.  This makes RFC indexing dependent on the operation of
external applications, such as RFC search, or Google, or whatever.
While I am sure that the operators of the RFC search engine and of
Google firmly plan on operating their service for the duration, the
"duration" can end or be interrupted (as is being discovered by all
the users of the NIST web document servers right now).

Also, the RFC docs have been and will only continue to be important
historical and foundational documents, and should have their own
in-line canonical summary index in the same format, for inclusion into
larger document collections, and into historical archives and
printings.

Does it cost IETF anything to keep creating the xx99's?

They should not be discontinued.

Thanks!

On Tue, Oct 8, 2013 at 10:50 AM, RFC Series Editor <rse@rfc-editor.org> wrote:
> Greetings,
>
> The RFC Editor is proposing to retire the practice of publishing RFCs
> xx99, the Request for Comments Summary for RFC Numbers xx00-xx99.  In
> December 1991, RFC 1099 was the first "Request for Comments Summary"
> RFC published.  It provides a list of document titles, authors, date
> of publication, and abstracts for each of the RFCs published in the
> range 1000 - 1099.  Since that time, through the time that RFC 3299
> was published, a new summary RFC was published every 100 RFCs, and RFC
> numbers ending with 99 were reserved for these summary documents.  RFC
> 3399 was never published (for various reasons), though RFCs 3499 and
> 3599 were.  RFC 3599 was the last of these summary documents to be
> published in December 2003.
>
> These snapshots are no longer needed because up-to-date data is
> available online.  RFC abstracts are available using the RFC search
> engine (http://www.rfc-editor.org/search/rfc_search.php) and they are
> included in rfc-index.xml.  RFCs xx99 summaries were never requested by
> the Internet Community and are not currently filling a need; therefore,
> the RFC Editor is retiring the publication of the RFC summary documents.
> RFC numbers typically reserved for these documents (i.e., numbers
> ending with 99) may be assigned to future RFCs.
>
> If there are any concerns about this course of action, please comment by
> October 18, 2013, on the rfc-interest@rfc-editor.org mailing list.
>
> Thank you,
> Heather Flanagan, RSE

From sajassi@cisco.com  Tue Oct  8 15:13:46 2013
Return-Path: <sajassi@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 51AD921F9EDA; Tue,  8 Oct 2013 15:13:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.299
X-Spam-Level: 
X-Spam-Status: No, score=-8.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, 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 2d4u0p7RKS0z; Tue,  8 Oct 2013 15:13:41 -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 768E421F9D96; Tue,  8 Oct 2013 15:13:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1482; q=dns/txt; s=iport; t=1381270416; x=1382480016; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=nQVM/GPbpLvRWm2fnXW/nNB7WpHdGJd/Ktkvt3j6Q+Y=; b=jjYs6W4QVPR8mD6rLCsreWZ+le7QviD6h/NJlNmvsciN0zj8EemDef6E m4RegzjVkwgbVUfVdQd3zz+vtzGFCM9NFSp3gUKm9w7CJye5TO8xaPCPK 9Apyhs72GB7nB0FwAV5ohALdJVX3Z2uffLD2obO/lr0mPGp9sQA95YewX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAMeCVFKtJXG8/2dsb2JhbABZgmYhOFLBKYEmFnSCJwEEeRIBCBQOViUCBAENBQiHfgELui+PETEHgx+BBAOMUYxfhgKKT4Mkgio
X-IronPort-AV: E=Sophos;i="4.90,1059,1371081600"; d="scan'208";a="269515555"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 08 Oct 2013 22:13:34 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r98MDWg2021501 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Oct 2013 22:13:32 GMT
Received: from xmb-aln-x13.cisco.com ([fe80::5404:b599:9f57:834b]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 8 Oct 2013 17:13:32 -0500
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-l2vpn-pbb-vpls-interop.all@tools.ietf.org" <draft-ietf-l2vpn-pbb-vpls-interop.all@tools.ietf.org>
Subject: Re: Gen-ART LC Review of draft-ietf-l2vpn-pbb-vpls-interop-05
Thread-Topic: Gen-ART LC Review of draft-ietf-l2vpn-pbb-vpls-interop-05
Thread-Index: AQHOuJubX0jJczo/r06LXwRyi7CvPJnrVISA
Date: Tue, 8 Oct 2013 22:13:31 +0000
Message-ID: <69670F7146898C4583F56DA9AD32F77B215BDA7B@xmb-aln-x13.cisco.com>
In-Reply-To: <5D62D2D2-26DD-4BC4-A296-0C4AB414F549@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.128.2.47]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <437A7FFFB22F604D8524373F0CBD7817@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Oct 2013 15:50:24 -0700
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.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: Tue, 08 Oct 2013 22:13:46 -0000

Ben,

Thanks for your comments. I have incorporated all your comments in rev06
of this draft.


On 9/23/13 1:29 PM, "Ben Campbell" <ben@nostrum.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-ietf-l2vpn-pbb-vpls-interop-05
>Reviewer: Ben Campbell
>Review Date: 2013-09-23
>IETF LC End Date: 2013-09-24
>
>Summary: Ready for publication as an informational RFC.
>
>Major issues:
>
>None
>
>Minor issues:
>
>None
>
>Nits/editorial comments:
>
>-- Abstract:
>
>Please expand H-VPLS on first mention

Done.

>
>-- section 1, 1st paragraph:
>
>Please expand VPLS on first mention.

Done.

>
>-- section 4, 3rd to last paragraph: "Different PBB access networks..."
>
>The previous and subsequent paragraphs say "PBBN access networks". Should
>this instance also say PBBN?

Done.

>
>-- section 4.3:
>
>2nd paragraph says this scenario is applicable to "Loosely Coupled
>Service Domains" and "Different Service Domains". The 4th paragraph
>mentions "Tightly...". Does that mean the scenario also applies to
>"Tightly Coupled Service Domains"? (i.e. should it be added to the 2nd
>paragraph, or removed from the 4th?)
>

Removed "Tightly =8A" from the 4th paragraph.

Cheers,
Ali


From fred@cisco.com  Tue Oct  8 16:21:37 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 019DB21F9D7E for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 16:21:37 -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 3PD76nVudKfA for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 16:21:31 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 8446111E8116 for <ietf@ietf.org>; Tue,  8 Oct 2013 16:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2496; q=dns/txt; s=iport; t=1381274468; x=1382484068; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5NknVn/muVkjszNgW4OdBpAGyDZdjrlSYprha+a9IsA=; b=lDjotrarUjGwDX1OuImp5IsSje3P2zKq0mS2pm1+JrP+fEFZJUuWTcJc mspaVMD/ZVwmgp8N1dCd8YxRJnFo3w/bex5zjYt7QyhEZ05Fhg7ngW8aR mkWIrOCl8spS3uNjV60X6C2QVzSgkmjBBl5x+PbfbbvuxJe476szzX98s w=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFALmDVFKtJV2Y/2dsb2JhbABZgweBCsEpgSYWdIIlAQEBAwF5BQsCAQgiGQsyJQIEDgUIBg2HZQa6PI8RMQeDH4EEA5AogTCYKYFmgT6CKg
X-IronPort-AV: E=Sophos;i="4.90,1059,1371081600";  d="asc'?scan'208";a="269715791"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP; 08 Oct 2013 23:21:07 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r98NL7EQ031526 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Oct 2013 23:21:07 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Tue, 8 Oct 2013 18:21:07 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
Thread-Topic: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
Thread-Index: AQHOxHcGWASw5Ik7I0Sp/eUpwVVD/Znrxe0A
Date: Tue, 8 Oct 2013 23:21:07 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net>
In-Reply-To: <6.2.5.6.2.20131008054041.0d74aa88@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_174EB805-BAAE-4D1B-988B-92FAD4A098E9"; protocol="application/pgp-signature"; micalg=pgp-sha1
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: Tue, 08 Oct 2013 23:21:37 -0000

--Apple-Mail=_174EB805-BAAE-4D1B-988B-92FAD4A098E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 8, 2013, at 1:56 PM, S Moonesamy <sm+ietf@elandsys.com>
 wrote:

> I am not sure whether hums are for a starting point or not.  It can be =
argued in different ways, for example, see Section 4. Humming helps to =
get a sense of the room without people making a decision under duress.=20=


Personally, I think focusing on Jeff Case's hums is missing the point. =
The point is the meaning of the term "rough consensus", and how that =
plays out in working group process. The manner of measurement is a =
secondary issue.

To my small and somewhat naive mind, the difference between rough =
consensus on a topic and a vote on the same topic is something about =
winners and losers. In a purely political process, when a set of parties =
vote on something and the preponderance (by some definition of =
"preponderance") say something, the views of the losing set of parties =
are deemed irrelevant. In IETF process, and hopefully in any technical =
process, there is understanding that the parties who disagree may have =
valid reasons to disagree, and a phase of negotiation. When we talk =
about "rough consensus", I understand it to mean - and would like to =
believe that we all understand it this way - that we investigate the =
reasons for disagreement, perhaps discover that some of them are valid, =
and address those issues to the satisfaction of those who raised them. =
As a result, the ultimate solution, even though it may not be the =
specific solution we would all have designed or selected, is one that in =
fact addresses all known issues. While we may not all agree, we don't =
disagree.

I think the document on the table tries to address that. There are =
points of phraseology that I might express differently, but it's close =
enough that I don't disagree.

--Apple-Mail=_174EB805-BAAE-4D1B-988B-92FAD4A098E9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSVJQmbjEdbHIsm0MRAsZHAKDmUA1wWVmU7EU/wM5kWwtumy4hDACgha1s
PDZAE45bVpcZtM1+SVl+nmU=
=YRrf
-----END PGP SIGNATURE-----

--Apple-Mail=_174EB805-BAAE-4D1B-988B-92FAD4A098E9--

From rbonica@juniper.net  Tue Oct  8 17:46:44 2013
Return-Path: <rbonica@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 3CED521F9FB0; Tue,  8 Oct 2013 17:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.724
X-Spam-Level: 
X-Spam-Status: No, score=-102.724 tagged_above=-999 required=5 tests=[AWL=-0.125, 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 cSG7XsC3eMZP; Tue,  8 Oct 2013 17:46:38 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0189.outbound.messaging.microsoft.com [213.199.154.189]) by ietfa.amsl.com (Postfix) with ESMTP id 2041C21F9FA3; Tue,  8 Oct 2013 17:46:35 -0700 (PDT)
Received: from mail134-db8-R.bigfish.com (10.174.8.230) by DB8EHSOBE027.bigfish.com (10.174.4.90) with Microsoft SMTP Server id 14.1.225.22; Wed, 9 Oct 2013 00:46:32 +0000
Received: from mail134-db8 (localhost [127.0.0.1])	by mail134-db8-R.bigfish.com (Postfix) with ESMTP id 63DEDA00C7; Wed,  9 Oct 2013 00:46:32 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail134-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(377454003)(199002)(189002)(13464003)(54316002)(56776001)(85306002)(81686001)(76482001)(65816001)(66066001)(80022001)(74366001)(79102001)(77982001)(63696002)(59766001)(81816001)(74876001)(74706001)(83072001)(69226001)(47736001)(49866001)(50986001)(47976001)(53806001)(4396001)(46102001)(51856001)(54356001)(80976001)(31966008)(47446002)(74662001)(19580405001)(74502001)(83322001)(19580395003)(81542001)(74316001)(76796001)(76786001)(76576001)(81342001)(77096001)(33646001)(56816003)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB436; H:BLUPR05MB433.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail134-db8 (localhost.localdomain [127.0.0.1]) by mail134-db8 (MessageSwitch) id 138127959026135_8924; Wed,  9 Oct 2013 00:46:30 +0000 (UTC)
Received: from DB8EHSMHS018.bigfish.com (unknown [10.174.8.238])	by mail134-db8.bigfish.com (Postfix) with ESMTP id EBBF6480067; Wed,  9 Oct 2013 00:46:29 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS018.bigfish.com (10.174.4.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 9 Oct 2013 00:46:29 +0000
Received: from BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Wed, 9 Oct 2013 00:46:28 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com (10.141.27.140) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.0.785.10; Wed, 9 Oct 2013 00:46:27 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com ([169.254.16.72]) by BLUPR05MB433.namprd05.prod.outlook.com ([169.254.16.72]) with mapi id 15.00.0785.001; Wed, 9 Oct 2013 00:46:27 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Ole Troan <otroan@employees.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KsdJvRhXd90UuLWVq4yr1RsZnlBPWAgASNmgCAAXGqAIAAjlqg
Date: Wed, 9 Oct 2013 00:46:27 +0000
Message-ID: <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
In-Reply-To: <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0994F5E0C5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 00:46:44 -0000

I agree with Ole.

       Ron

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Ole Troan
> Sent: Tuesday, October 08, 2013 12:17 PM
> To: Templin, Fred L
> Cc: ipv6@ietf.org; ietf@ietf.org; IETF-Announce
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > Hi, I would like to make a small amendment to what I said in my
> > previous message as follows:
> >
> > 4) Section 5, change the final paragraph to:
> >
> >   "As a result of the above mentioned requirements, a packet's header
> >   chain length MUST fit within the Path MTU associated with its
> >   destination.  Hosts MAY discover the Path MTU, using procedures
> such
> >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> does
> >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> >   1280 bytes [RFC2460]. The host MUST then limit each packet's header
> >   chain length to the Path MTU minus 256 bytes in case additional
> >   encapsulation headers are inserted by tunnels on the path."
>=20
> I would claim that additional encapsulation headers are already
> considered in the 1280 minimum MTU.
> as in: 1500 - 1280.
>=20
> cheers,
> Ole



From stpeter@stpeter.im  Tue Oct  8 19:06:01 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 BBB2D21F9A10 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 19:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.121
X-Spam-Level: 
X-Spam-Status: No, score=-102.121 tagged_above=-999 required=5 tests=[AWL=0.478, 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 qYPL5zaWdYuE for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 19:05:56 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0D621F9FC3 for <ietf@ietf.org>; Tue,  8 Oct 2013 19:05:51 -0700 (PDT)
Received: from [192.168.1.3] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2C2CF414CD; Tue,  8 Oct 2013 20:11:48 -0600 (MDT)
Message-ID: <5254B9FD.1020400@stpeter.im>
Date: Tue, 08 Oct 2013 20:05:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net><6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net>	<52524A68.7040800@qti.qualcomm.com> <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net>
In-Reply-To: <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 09 Oct 2013 02:06:01 -0000

On 10/08/2013 07:56 AM, t.p. wrote:
> 3) References to working groups with 100 active participants sound like
> a chimera.  I track quite a number of lists, and some have about five
> active participants.  (Some Working Group Last Calls attract one or even
> zero responses; the reactions of chairs to this is interesting and
> varies widely).
Although I see Pete's draft more as conceptual than as a handbook for 
every possible situation, I do think that working groups with very few 
participants are a hard case that we need to think about.

Peter


From melinda.shore@gmail.com  Tue Oct  8 20:23:06 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 35A8E11E8122 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 20:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=0.325,  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 S5EyljQyUfun for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 20:23:05 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id B5EE511E8120 for <ietf@ietf.org>; Tue,  8 Oct 2013 20:23:05 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wz12so247076pbc.25 for <ietf@ietf.org>; Tue, 08 Oct 2013 20:23:05 -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=EcqU2KBTgouLCps0w2vDZovPv0WN0RrMD02+RejQ6yw=; b=HbbVD88QIWwuIN6FpJuqZz6HBaQZavNG184tN2QbNe9+x0edD8bwJpsfVNw40Wz19r Y3G4r053etcyRQuHUKrC1BY+bCpIsmtVpk66EcxQBvS6bXCZuZz6c9EhItiAUuvas4XP oZv5Drhp1Y3iQv0HY+nGT7spODNcRK8Buu2w4tSykITfQqYb9V3H25wM/EON47/dgC2s EUfJ60MsjAzXuuSTQ9wB/XSnzCuS/lVnaozhSEDHFz/SAe+UFIe8XRGWnxGOqNm2NMDz k8GdNEms/97qo/FWf+DxeMR9aU/cTUokrzIdEabhxutY+ig9XJHMOh1jOC3CPG12Agot DKsw==
X-Received: by 10.66.65.108 with SMTP id w12mr69868pas.183.1381288985365; Tue, 08 Oct 2013 20:23:05 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id vz4sm51232320pab.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 20:23:04 -0700 (PDT)
Message-ID: <5254CC15.3050802@gmail.com>
Date: Tue, 08 Oct 2013 19:23:01 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.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, 09 Oct 2013 03:23:06 -0000

On 10/8/13 3:21 PM, Fred Baker (fred) wrote:
> To my small and somewhat naive mind, the difference between rough
> consensus on a topic and a vote on the same topic is something about
> winners and losers. In a purely political process, when a set of
> parties vote on something and the preponderance (by some definition
> of "preponderance") say something, the views of the losing set of
> parties are deemed irrelevant. In IETF process, and hopefully in any
> technical process, there is understanding that the parties who
> disagree may have valid reasons to disagree, and a phase of
> negotiation. When we talk about "rough consensus", I understand it to
> mean - and would like to believe that we all understand it this way -
> that we investigate the reasons for disagreement, perhaps discover
> that some of them are valid, and address those issues to the
> satisfaction of those who raised them. As a result, the ultimate
> solution, even though it may not be the specific solution we would
> all have designed or selected, is one that in fact addresses all
> known issues. While we may not all agree, we don't disagree.

I've done a lot of work on consensus over the years and I think
this is fundamentally correct, although I'd amend the last sentence
to something along the lines of "While we may not all agree, those
who disagree can live with it."  That is to say, it's not a binary
question, and sometimes things we disagree with just aren't
showstoppers.  (I'd like to see people take that position more
often - for some reason a lot of people seem to take disagreement
as a reason to block a decision even when it doesn't matter that
much).

Melinda


From fred@cisco.com  Tue Oct  8 21:08:30 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 6756611E8137 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 21:08:30 -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 o00FOe8-zj8E for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 21:08:24 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 1B92F11E8132 for <ietf@ietf.org>; Tue,  8 Oct 2013 21:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1309; q=dns/txt; s=iport; t=1381291702; x=1382501302; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0l9ANiWou5k+xcu4YW/nAQg14P1E7hfLiy6O94TTBjQ=; b=hNdIc2bwkUT2QbtZ7PoFFwLsxvJsAESNVPJUUpRPJq9lyxUlcOIj6O4y vQ1h9rEdr85YQ3LqP9BWUecPLYlfLQVGqTuS85jxKpJl+fwr21QgtBJeP W/Cld0yPo4fKWKyLWTiOVS1HJyExxFss5VuOKNIuSUIS6yjrvsCQaEdZw M=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFALzVVFKtJV2Z/2dsb2JhbABagweBCsEwgSQWdIIlAQEBAwF5BQsCAQgiGQshESUCBA4FCAaHZgMJBq9XDYlrjFiCOzEHgx+BBAOQKYEwhECOM4U2gWaBPoIq
X-IronPort-AV: E=Sophos;i="4.90,1060,1371081600";  d="asc'?scan'208";a="269761375"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 09 Oct 2013 04:08:21 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9948LL7001569 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Oct 2013 04:08:21 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Tue, 8 Oct 2013 23:08:21 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
Thread-Topic: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
Thread-Index: AQHOxH03J/+EIBd6jESdU5Pb3tvilZnsCI6AgAANnwA=
Date: Wed, 9 Oct 2013 04:08:21 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA60386@xmb-rcd-x09.cisco.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com>
In-Reply-To: <5254CC15.3050802@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_8F308CC4-9AD1-4848-AD0C-E6CA5C53D68A"; protocol="application/pgp-signature"; micalg=pgp-sha1
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, 09 Oct 2013 04:08:30 -0000

--Apple-Mail=_8F308CC4-9AD1-4848-AD0C-E6CA5C53D68A
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 8, 2013, at 8:23 PM, Melinda Shore <melinda.shore@gmail.com> wrote:

> I've done a lot of work on consensus over the years and I think
> this is fundamentally correct, although I'd amend the last sentence
> to something along the lines of "While we may not all agree, those
> who disagree can live with it."  That is to say, it's not a binary
> question, and sometimes things we disagree with just aren't
> showstoppers.  (I'd like to see people take that position more
> often - for some reason a lot of people seem to take disagreement
> as a reason to block a decision even when it doesn't matter that
> much).

wfm

--Apple-Mail=_8F308CC4-9AD1-4848-AD0C-E6CA5C53D68A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSVNeDbjEdbHIsm0MRAlilAJ9v/EwelPXkcCKKAgmHIv6vSBsZUwCfUvQN
wvM41X0CL8LBJMcRFXLcb5Q=
=pjsV
-----END PGP SIGNATURE-----

--Apple-Mail=_8F308CC4-9AD1-4848-AD0C-E6CA5C53D68A--

From loa@pi.nu  Tue Oct  8 22:21:18 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 D075021E80DB for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:21: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=[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 KtyX9bZRKYBt for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:20:57 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id E400621E80D3 for <ietf@ietf.org>; Tue,  8 Oct 2013 22:20:55 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.84.108]) (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 4FB3918014F6; Wed,  9 Oct 2013 07:20:53 +0200 (CEST)
Message-ID: <5254E7A3.8050507@pi.nu>
Date: Wed, 09 Oct 2013 13:20:35 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com>
In-Reply-To: <5254CC15.3050802@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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Oct 2013 05:21:18 -0000

All,

FWIW - my personal way of thinking about consensus vd. rough consensus,
please note that it my personal view not a definition.

Consensus - An agreement by everyone in a group that a proposed
             solution is the best of all of all possible solutions

Rough consensus - An agreement by almost everyone that the proposed
             solution is good enough for everyone to live with.

/Loa

On 2013-10-09 11:23, Melinda Shore wrote:
> On 10/8/13 3:21 PM, Fred Baker (fred) wrote:
>> To my small and somewhat naive mind, the difference between rough
>> consensus on a topic and a vote on the same topic is something about
>> winners and losers. In a purely political process, when a set of
>> parties vote on something and the preponderance (by some definition
>> of "preponderance") say something, the views of the losing set of
>> parties are deemed irrelevant. In IETF process, and hopefully in any
>> technical process, there is understanding that the parties who
>> disagree may have valid reasons to disagree, and a phase of
>> negotiation. When we talk about "rough consensus", I understand it to
>> mean - and would like to believe that we all understand it this way -
>> that we investigate the reasons for disagreement, perhaps discover
>> that some of them are valid, and address those issues to the
>> satisfaction of those who raised them. As a result, the ultimate
>> solution, even though it may not be the specific solution we would
>> all have designed or selected, is one that in fact addresses all
>> known issues. While we may not all agree, we don't disagree.
>
> I've done a lot of work on consensus over the years and I think
> this is fundamentally correct, although I'd amend the last sentence
> to something along the lines of "While we may not all agree, those
> who disagree can live with it."  That is to say, it's not a binary
> question, and sometimes things we disagree with just aren't
> showstoppers.  (I'd like to see people take that position more
> often - for some reason a lot of people seem to take disagreement
> as a reason to block a decision even when it doesn't matter that
> much).
>
> Melinda
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From melinda.shore@gmail.com  Tue Oct  8 22:30:29 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 A389721F9AF0 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5 tests=[AWL=0.244,  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 2zlv-QQepDDo for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:30:29 -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 9600C11E8135 for <ietf@ietf.org>; Tue,  8 Oct 2013 22:30:27 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc17so373613pbc.18 for <ietf@ietf.org>; Tue, 08 Oct 2013 22:30: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=b2Npd9YZNvuwDL6zbmxGA9wsJbMOju2QJ8gHHhGfaUQ=; b=RAlCYzzqgvxGoVhHHdrQN3plxgVgLjJ1DRo1sfjtiNpjfpvIFhdyEoSP696BQ5NeBe F4u6bzAzpMmbcnYnISnSSDxCm0xDtIA4qXxLq7QAR7FLO+22aY/GB6yqbbMeEF4rtzBm VS+QLN8JOqdPpMtBxR11Re3CZ6t2864bamxQIjdusXOu6VhMlOE5VdXxSu0S4/B7vx2m Di1b3BYro9bCeFSCe788gOE9cYK00yjuqL1gNiST8XL1roK1RowNuKxu7aHrLV2gNZpo frRGVe8lq0Ci1ovHYtDtZUfCGUutYQMP9UH3yX26+cxQhZvPBkcgY5d7F/OqwqnwO1EY VTKw==
X-Received: by 10.68.252.68 with SMTP id zq4mr5887218pbc.154.1381296627366; Tue, 08 Oct 2013 22:30:27 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id k4sm44027173pbd.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 22:30:25 -0700 (PDT)
Message-ID: <5254E9EF.6010807@gmail.com>
Date: Tue, 08 Oct 2013 21:30:23 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu>
In-Reply-To: <5254E7A3.8050507@pi.nu>
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, 09 Oct 2013 05:30:29 -0000

On 10/8/13 9:20 PM, Loa Andersson wrote:
> FWIW - my personal way of thinking about consensus vd. rough consensus,
> please note that it my personal view not a definition.
> 
> Consensus - An agreement by everyone in a group that a proposed
>             solution is the best of all of all possible solutions
> 
> Rough consensus - An agreement by almost everyone that the proposed

That's a lot like voting, I think.

Melinda


From loa@pi.nu  Tue Oct  8 22:54:15 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 53E9A21E80CE for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:54: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 10ivdVM29OeV for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 22:54:07 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 15AA711E812B for <ietf@ietf.org>; Tue,  8 Oct 2013 22:54:06 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.84.108]) (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 7DDB618014F6; Wed,  9 Oct 2013 07:54:04 +0200 (CEST)
Message-ID: <5254EF77.903@pi.nu>
Date: Wed, 09 Oct 2013 13:53:59 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu> <5254E9EF.6010807@gmail.com>
In-Reply-To: <5254E9EF.6010807@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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Oct 2013 05:54:15 -0000

On 2013-10-09 13:30, Melinda Shore wrote:
> On 10/8/13 9:20 PM, Loa Andersson wrote:
>> FWIW - my personal way of thinking about consensus vs. rough consensus,
>> please note that it my personal view not a definition.
>>
>> Consensus - An agreement by everyone in a group that a proposed
>>              solution is the best of all of all possible solutions
>>
>> Rough consensus - An agreement by almost everyone that the proposed
                solution is good enough for everyone to live with.
>
> That's a lot like voting, I think.

Well - if you say so, but then we don't have even a rough consensus on
what consensus and rough consensus means.

Note I talked about what a group need to reach to be able to say that
there is "consensus" or "rough consensus". Not how it is measured, in
IETF we trust the wg chairs to correctly judge if we have reached a
rough consensus.

/Loa

>
> Melinda
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From swmike@swm.pp.se  Tue Oct  8 23:04:08 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 34A4021F9EDB for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:04:08 -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 NN+7PS9akVxo for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:04:07 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 525D111E8143 for <ietf@ietf.org>; Tue,  8 Oct 2013 23:04:05 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 39DAD9C; Wed,  9 Oct 2013 08:04:03 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 34A869A; Wed,  9 Oct 2013 08:04:03 +0200 (CEST)
Date: Wed, 9 Oct 2013 08:04:03 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last calling draft-resnick-on-consensus
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
Message-ID: <alpine.DEB.2.02.1310090800020.20065@uplift.swm.pp.se>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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, 09 Oct 2013 06:04:08 -0000

On Mon, 7 Oct 2013, Jari Arkko wrote:

> You should see a last call announcement soon, and both me and Pete look 
> forward to your feedback.

As a semi-newbie (2 meetings, a few years worth of remote participation), 
I found this document useful. It clearified my understanding of "rough 
consensus".

I am sure the document can be made even better (there have been good 
suggestions in this thread), but I fully support a document of this kind 
being published in some manner (I don't have an opinion if it should be 
BCP or Informational RFC or something else).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From sm@resistor.net  Tue Oct  8 23:13:25 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 5509A21E80DF for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:13: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 wG84cOVePDzl for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:13:24 -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 44C4521E80E6 for <ietf@ietf.org>; Tue,  8 Oct 2013 23:13:20 -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 r996DBOr005560; Tue, 8 Oct 2013 23:13:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381299199; bh=/pxIm3A+SQMa3jSn8HPPu8+wbwM2fEKmHh/3bMYXq9M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Je0oTyINfM8M3dj4BOK3uPa6wqZBIg9k+HWzonlrCXxduZy/j/N/knivPUkKJJBAl QfAgPFDATHPnCiAqxtgD+Kw+RNUUIru27OIXgj/xnREJ51376xznie/6Lood/7ZOV2 fRa4sR1k2Rfgq3bWp4D2vBQ5AfP7+aChxE8F7AuE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381299199; i=@resistor.net; bh=/pxIm3A+SQMa3jSn8HPPu8+wbwM2fEKmHh/3bMYXq9M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bzgr04l8RSpPuMVV5LzJy4+EruAhGGO0q7pQp3WwkNdZ1bfp+iVh1WtbOROeYCCzk ChZVivjGymW4QW8Nt1vNaiYlIqNymlKwU5emrDzlhzGEBJlkX6Zkx85XUtXuyX47aR 63FA0yQNz1xSXHnuCRVgPA3Yno5bwwiYSq/1NSZc=
Message-Id: <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Oct 2013 22:55:08 -0700
To: Russ Housley <housley@vigilsec.com>
From: SM <sm@resistor.net>
Subject: Re: Montevideo statement
In-Reply-To: <20131007225129.GA572@laperouse.bortzmeyer.org>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.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: Wed, 09 Oct 2013 06:13:25 -0000

Hi Russ,
At 15:51 07-10-2013, Stephane Bortzmeyer wrote:
>This wording is surprising. It looks like it is the revelations that
>undermined confidence, and not the NSA actions. I would prefer
>something like, to avoid shooting the messenger:
>
>They expressed strong concern over the undermining of the trust and
>confidence of Internet users globally, due to pervasive monitoring and
>surveillance by powerful actor(s).

The wording could have been different instead of one expressing a 
strong concern about the "revelations".

There is a statement from LACNIC about allegations of espionage 
(http://www.lacnic.net/en/web/anuncios/2013-lacnic-acerca-espionaje). 
The statement signed by the IAB Chair 
(http://www.iab.org/documents/correspondence-reports-documents/2013-2/montevideo-statement-on-the-future-of-internet-cooperation/) 
is about future of Internet Cooperation.

This is the second time that the IAB has issued a statement without 
requesting comments from the IETF Community.  In my humble opinion it 
would be good if there was a comment period.

Regards,
-sm 


From ajs@anvilwalrusden.com  Tue Oct  8 23:45:16 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 3571D21F8E97 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:45:16 -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 W6oll30ioso8 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:45:10 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB7C21F99F3 for <ietf@ietf.org>; Tue,  8 Oct 2013 23:45:01 -0700 (PDT)
Received: from mx1.yitter.info (wsip-70-186-133-98.ph.ph.cox.net [70.186.133.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 34A3C8A031 for <ietf@ietf.org>; Wed,  9 Oct 2013 06:44:43 +0000 (UTC)
Date: Wed, 9 Oct 2013 02:44:39 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Montevideo statement
Message-ID: <20131009064438.GA47673@mx1.yitter.info>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>
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: Wed, 09 Oct 2013 06:45:16 -0000

Dear colleagues,

On Tue, Oct 08, 2013 at 10:55:08PM -0700, SM wrote:
> This is the second time that the IAB has issued a statement

Speaking only (empahtically only) for myself, I quite strongly
disagree.  The IAB has issued no statement in this case.

The text as posted is quite clear:

---%<---cut here---

"The leaders of organizations â€¦ have met"
[â€¦]
Russ Housley, Chair
Internet Architecture Board (IAB)

--->%---cut here---

That does not say that the IAB has issued a statement.  On the
contrary, the IAB did not issue a statement.  I think the difference
between some individuals issuing a statement in their capacity as
chairs and CEOs and so on, and the body for which they are chair or
CEO or so on issuing a similar statement, is an important one.  We
ought to attend to it.

Please note that this message is not in any way a comment on such
leadership meetings.  In addition, for the purposes of this discussion
I refuse either to affirm or deny concurrence in the IAB chair's
statement.  I merely request that we, all of us, attend to the difference
between "the IAB Chair says" and "the IAB says".

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From joelja@bogus.com  Tue Oct  8 23:54:19 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 3F4CC11E8128 for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:54:19 -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.000, 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 y1b+B6aANI4g for <ietf@ietfa.amsl.com>; Tue,  8 Oct 2013 23:54:18 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2D16621F99E9 for <ietf@ietf.org>; Tue,  8 Oct 2013 23:54:18 -0700 (PDT)
Received: from [192.168.1.11] (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r996sF2b028488 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 06:54:16 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_8C25EDBB-8ACA-4B78-9686-1165F1189835"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Montevideo statement
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <20131009064438.GA47673@mx1.yitter.info>
Date: Tue, 8 Oct 2013 23:54:10 -0700
Message-Id: <219DFA10-FD42-42AC-8461-E2F2E724E6D6@bogus.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 09 Oct 2013 06:54:16 +0000 (UTC)
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, 09 Oct 2013 06:54:19 -0000

--Apple-Mail=_8C25EDBB-8ACA-4B78-9686-1165F1189835
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 8, 2013, at 11:44 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> Dear colleagues,
>=20
> On Tue, Oct 08, 2013 at 10:55:08PM -0700, SM wrote:
>> This is the second time that the IAB has issued a statement
>=20
> Speaking only (empahtically only) for myself, I quite strongly
> disagree.  The IAB has issued no statement in this case.
>=20
> The text as posted is quite clear:
>=20
> ---%<---cut here---
>=20
> "The leaders of organizations =85 have met"
> [=85]
> Russ Housley, Chair
> Internet Architecture Board (IAB)
>=20
> --->%---cut here---
>=20
> That does not say that the IAB has issued a statement.  On the
> contrary, the IAB did not issue a statement.  I think the difference
> between some individuals issuing a statement in their capacity as
> chairs and CEOs and so on, and the body for which they are chair or
> CEO or so on issuing a similar statement, is an important one.  We
> ought to attend to it.
>=20
> Please note that this message is not in any way a comment on such
> leadership meetings.  In addition, for the purposes of this discussion
> I refuse either to affirm or deny concurrence in the IAB chair's
> statement.  I merely request that we, all of us, attend to the =
difference
> between "the IAB Chair says" and "the IAB says".

It would be highly salubrious if in the future if things that look like =
open letters are simply signed by individuals listing their =
organizational role/affiliation rather than stating that leaders of the =
following organizations support this statement. There is  abundant =
historical precedent for that.



>=20
> Best regards,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
>=20


--Apple-Mail=_8C25EDBB-8ACA-4B78-9686-1165F1189835
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJU/ZIACgkQ8AA1q7Z/VrLKFQCfQ4Q1vWJdPaMbsKHPH+SG9fGg
YgsAn1IZ/2GfmEKNQFC3wyQWgLjyWTZ7
=jJkS
-----END PGP SIGNATURE-----

--Apple-Mail=_8C25EDBB-8ACA-4B78-9686-1165F1189835--

From lear@cisco.com  Wed Oct  9 03:20:55 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 A180811E8167 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 03:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.515
X-Spam-Level: 
X-Spam-Status: No, score=-110.515 tagged_above=-999 required=5 tests=[AWL=0.084, 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 OLFPN8cxA1fH for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 03:20:50 -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 B315111E8168 for <ietf@ietf.org>; Wed,  9 Oct 2013 03:20:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3218; q=dns/txt; s=iport; t=1381314049; x=1382523649; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=47SrqdA6pu5Q11vWJPiPT4x9/YYkJkdfVWfiLs2h0sE=; b=l6C+XGtIVc4Y44zDHVR6fX4RJGEtfRqOGfS0+RORQadzu/FPHTjl4CWO 3YpDEyJnoSbLHbaO1i0QctDw0RW4FmHhQBLGLVCy3I5Dw+DXL0IkPoxRG 0t54DAdvFI3kwbGMnH7CT5w/zFHJvkjafc3HbTdKls2OUky/lxupZBJas 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAKQtVVKQ/khN/2dsb2JhbABagwc4g3q+CoEgFnSCJQEBAQQjQgkKEQsYAgIFDAoEBwICCQMCAQIBKwkREwYCAQEah2gMph6SRYEpjiMKgmCBOQOUJoNdgS+QUoFmgVog
X-IronPort-AV: E=Sophos;i="4.90,1062,1371081600"; d="scan'208";a="87284363"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 09 Oct 2013 10:20:48 +0000
Received: from mctiny.local ([10.61.166.243]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r99AKgAH013134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 9 Oct 2013 10:20:44 GMT
Message-ID: <52552DFA.9030904@cisco.com>
Date: Wed, 09 Oct 2013 06:20:42 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
In-Reply-To: <20131007164829.16131.73595.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
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: Wed, 09 Oct 2013 10:20:55 -0000

Pete,

As usual, I really like your writing style, and I think you're
addressing a very important issue.  There are two aspects that I would
suggest require further exploration, both having to do with the role of
the chair (the whole document has to do with the role of the chair, I
suppose):

1.  No matter how you slice the definition of rough consensus, if the
chair does not act in a fair and balanced way, the outcome will be
incorrect.  This is what the appeals process is for, and I would suggest
mentioning it, perhaps in some detail.

2.  The case of Section 7 is, as you say, a mind bender.  I would
suggest adding another use case: what if those 100 people write their
own draft.  Can they use the exact same process to get the draft adopted
and approved, so long as they answer the technical issues that arise? 
In other words, if there are multiple valid alternatives, and one suits
one vendor group and another suits another, can there be just one
standard?  At the neck of the hourglass, perhaps so?  What happens in
this case, from your point of view?  What makes group (a) more special
than group (b)?

Eliot


On 10/7/13 12:48 PM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'On Consensus and Humming in the IETF'
>   <draft-resnick-on-consensus-05.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-11-04. 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 IETF has had a long tradition of doing its technical work through
>    a consensus process, taking into account the different views among
>    IETF participants and coming to (at least rough) consensus on
>    technical matters.  In particular, the IETF is supposed not to be run
>    by a "majority rule" philosophy.  This is why we engage in rituals
>    like "humming" instead of voting.  However, more and more of our
>    actions are now indistinguishable from voting, and quite often we are
>    letting the majority win the day, without consideration of minority
>    concerns.  This document is a collection of thoughts on what rough
>    consensus is, how we have gotten away from it, and the things we can
>    do in order to really achieve rough consensus.
>
>       Note (to be removed before publication): This document is quite
>       consciously being put forward as Informational.  It does not
>       propose to change any IETF processes and is therefore not a BCP.
>       It is simply a collection of principles, hopefully around which
>       the IETF can come to (at least rough) consensus.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-resnick-on-consensus/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-resnick-on-consensus/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>


From tobias.gondrom@gondrom.org  Wed Oct  9 03:45:48 2013
Return-Path: <tobias.gondrom@gondrom.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 A18F611E816D for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 03:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.362
X-Spam-Level: 
X-Spam-Status: No, score=-95.362 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.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 mqAp0CGJYOTF for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 03:45:42 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id 24FDC21F9A50 for <ietf@ietf.org>; Wed,  9 Oct 2013 03:45:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=Zconrx73Nde8+rAAhcTHQ2IomQKlLtPQVJp/zf1wxDnX8GFonpaNySYbQsLA2ZI+5poFYJdi1CmRDdnxkYCK/x2dzxqW7MfOi9XUsKUHiov1KTsVS7OrfqrkXOZkoScW; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 1552 invoked from network); 9 Oct 2013 12:45:37 +0200
Received: from 188-222-103-191.zone13.bethere.co.uk (HELO ?192.168.1.71?) (188.222.103.191) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 9 Oct 2013 12:45:37 +0200
Message-ID: <525533D0.8060409@gondrom.org>
Date: Wed, 09 Oct 2013 11:45:36 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ajs@anvilwalrusden.com, ietf@ietf.org
Subject: Re: Montevideo statement
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info>
In-Reply-To: <20131009064438.GA47673@mx1.yitter.info>
X-Enigmail-Version: 1.5.2
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: Wed, 09 Oct 2013 10:45:48 -0000

On 09/10/13 07:44, Andrew Sullivan wrote:
> Dear colleagues,
>
> On Tue, Oct 08, 2013 at 10:55:08PM -0700, SM wrote:
>> This is the second time that the IAB has issued a statement
> Speaking only (empahtically only) for myself, I quite strongly
> disagree.  The IAB has issued no statement in this case.
>
> The text as posted is quite clear:
>
> ---%<---cut here---
>
> "The leaders of organizations â€¦ have met"
> [â€¦]
> Russ Housley, Chair
> Internet Architecture Board (IAB)
>
> --->%---cut here---
>
> That does not say that the IAB has issued a statement.  On the
> contrary, the IAB did not issue a statement.  I think the difference
> between some individuals issuing a statement in their capacity as
> chairs and CEOs and so on, and the body for which they are chair or
> CEO or so on issuing a similar statement, is an important one.  We
> ought to attend to it.
>
> Please note that this message is not in any way a comment on such
> leadership meetings.  In addition, for the purposes of this discussion
> I refuse either to affirm or deny concurrence in the IAB chair's
> statement.  I merely request that we, all of us, attend to the difference
> between "the IAB Chair says" and "the IAB says".

Andrew,
Although there is obviously a difference in wording, it is not that simple.
As people had the meeting and signed this directly linked to their roles
(IAB chair, IETF chair), it implies to the public that there is a
correlation with the organisation's positions and the support from their
organisations,  putting weight behind their statements.
Don't get me wrong, I definitely support that this situation deserved
statement to be made. But I support SM's proposal that it would be good
to do a few days comment period for such important statements in the
future - if timing is not critical. There is no harm in a few days delay
and getting input from the community.


And I second sm's concern that "The wording could have been different
instead of one expressing a strong concern about the "revelations"."
Agree, personally I am not concerned that certain activities were
revealed, I am very concerned that some of these things happened in the
first place.

Best regards, Tobias


> Best regards,
>
> A
>


From jnc@mercury.lcs.mit.edu  Wed Oct  9 04:46:30 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 3DFD411E817C for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 04:46: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 bGhYJspbZ6to for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 04:46:25 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B087711E8141 for <ietf@ietf.org>; Wed,  9 Oct 2013 04:46:22 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E2DD518C132; Wed,  9 Oct 2013 07:46:21 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Montevideo statement
Message-Id: <20131009114621.E2DD518C132@mercury.lcs.mit.edu>
Date: Wed,  9 Oct 2013 07:46:21 -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, 09 Oct 2013 11:46:30 -0000

    > From: Andrew Sullivan <ajs@anvilwalrusden.com>

    > I merely request that we, all of us, attend to the difference between
    > "the IAB Chair says" and "the IAB says".

We may attend to it, but we are unable to make sure that the rest of the world
pays attention to that nuance.

    > From: SM <sm@resistor.net>

    > In my humble opinion it would be good if there was a comment period.

Yes; if there is no time-pressure, why not take a week or so and find out what
the community thinks? Then it is not just one person (remember, we have no
kings...)

	Noel

From Ted.Lemon@nominum.com  Wed Oct  9 05:35:27 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 2CCA511E80E3 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 05:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 GHwJNl5Zl-Kd for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 05:35:20 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 1452811E8178 for <ietf@ietf.org>; Wed,  9 Oct 2013 05:35:19 -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 DSNKUlVNhqXEH3du+wd7rXAYeqJna/TAOt/w@postini.com; Wed, 09 Oct 2013 05:35: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 615851B82D5 for <ietf@ietf.org>; Wed,  9 Oct 2013 05:35:18 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 4108B190061; Wed,  9 Oct 2013 05:35:18 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 05:35:18 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5254E9EF.6010807@gmail.com>
Date: Wed, 9 Oct 2013 08:35:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu> <5254E9EF.6010807@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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, 09 Oct 2013 12:35:27 -0000

On Oct 9, 2013, at 1:30 AM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
>> Rough consensus - An agreement by almost everyone that the proposed
>=20
> That's a lot like voting, I think.

It's worse than voting, because it encourages people to invite their =
friends to sway the consensus.   At least with voting you have the =
transparency of knowing who the electorate is.   So if this were what =
"rough consensus" meant, rough consensus would most often be won by =
whoever has the most friends, which in practice is probably whoever =
works for the biggest company.  So whatever "rough consensus" means, it =
can't mean "only a few people disagree."


From Ted.Lemon@nominum.com  Wed Oct  9 06:14:22 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 D748911E818F for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 06:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 xTMA+UWADnuM for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 06:14:16 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id D3D7411E818D for <ietf@ietf.org>; Wed,  9 Oct 2013 06:14:12 -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 DSNKUlVWpPcGU+RCdNZAsVcOQB/dhMQtJnu7@postini.com; Wed, 09 Oct 2013 06:14:12 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 590901B82DD for <ietf@ietf.org>; Wed,  9 Oct 2013 06:14:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 4FD12190061; Wed,  9 Oct 2013 06:14:12 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 06:14:06 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Montevideo statement
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <525533D0.8060409@gondrom.org>
Date: Wed, 9 Oct 2013 09:14:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <5BEDC090-F92D-47D8-A9D1-55C8011919D7@nominum.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <525533D0.8060409@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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, 09 Oct 2013 13:14:23 -0000

On Oct 9, 2013, at 6:45 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> =
wrote:
> But I support SM's proposal that it would be good
> to do a few days comment period for such important statements in the
> future - if timing is not critical. There is no harm in a few days =
delay
> and getting input from the community.

This is a nice theory, but the usual last call time at IETF is either =
two weeks or four weeks, not a few days, and that's for a good reason.  =
I think there is no way that a statement of the type we are discussing =
can ever represent IETF consensus unless we go through an actual =
consensus call.

So the real question here is, is it ever appropriate for the chair of =
the IAB or the chair of the IETF to sign a statement like this without =
getting consensus?   I think that's a good question, and I don't have a =
strong opinion on the answer.   But if the answer is that we need =
consensus, then we actually need to do a consensus call.

The only value I see in "a few days" would be an opportunity for =
wordsmithing=97as someone pointed out, the current statement could be =
read as expressing concern that secrets were leaked, rather than concern =
about what was done in secret, and it would have been nice if that =
wording could have been corrected.   If that is what you were asking =
for, then that does make sense.

(thinking out loud...)


From john-ietf@jck.com  Wed Oct  9 07:00:53 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 9C04121F8FF8 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:00:53 -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=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, 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 lfwqHj+5sVOR for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:00:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A89D121F8F24 for <ietf@ietf.org>; Wed,  9 Oct 2013 07:00:46 -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 1VTuJg-00097P-8s; Wed, 09 Oct 2013 10:00:44 -0400
Date: Wed, 09 Oct 2013 10:00:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Montevideo statement
Message-ID: <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com>
In-Reply-To: <20131009064438.GA47673@mx1.yitter.info>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Oct 2013 14:00:53 -0000

--On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

>...
> That does not say that the IAB has issued a statement.  On the
> contrary, the IAB did not issue a statement.  I think the
> difference between some individuals issuing a statement in
> their capacity as chairs and CEOs and so on, and the body for
> which they are chair or CEO or so on issuing a similar
> statement, is an important one.  We ought to attend to it.
> 
> Please note that this message is not in any way a comment on
> such leadership meetings.  In addition, for the purposes of
> this discussion I refuse either to affirm or deny concurrence
> in the IAB chair's statement.  I merely request that we, all
> of us, attend to the difference between "the IAB Chair says"
> and "the IAB says".

Andrew,

While I agree that the difference is important for us to note,
this is a press release.  It would be naive at best to assume
that its intended audience would look at it and say "Ah. A bunch
of people with leadership roles in important Internet
organizations happened to be in the same place and decided to
make a statement in their individual capacities".  Not only does
it not read that way, but there are conventions for delivering
the "individual capacity" message, including prominent use of
phrases like "for identification only". 

Independent of how I feel about the content of this particular
statement,  if the community either doesn't like the message or
doesn't like this style of doing things, I think that needs to
be discussed and made clear.  That includes not only at the
level of preferences about community consultation but about
whether, in in the judgment of the relevant people, there is
insufficient time to consult the community, no statement should
be made at all.

Especially from the perspective of having been in the
sometimes-uncomfortable position of IAB Chair, I don't think IAB
members can disclaim responsibility in a situation like this.
Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at
the pleasure and convenience of the IAB.  If you and your
colleagues are not prepared to share responsibility for
statements (or other actions) the IAB Chair makes that involve
that affiliation, then you are responsible for taking whatever
actions are required to be sure that only those actions are
taken for which you are willing to share responsibility.   Just
as you have done, I want to stress that I'm not recommending any
action here, only that IAB members don't get to disclaim
responsibility made by people whose relationship with the IAB is
the reason why that are, e.g., part of a particular letter or
statement.

      john


From loa@pi.nu  Wed Oct  9 07:04:48 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 9C85811E819D for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:04:48 -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 7LdwclPQzGPi for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:04:42 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 758E611E8183 for <ietf@ietf.org>; Wed,  9 Oct 2013 07:04:42 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.84.108]) (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 908241802039; Wed,  9 Oct 2013 16:04:39 +0200 (CEST)
Message-ID: <52556274.30204@pi.nu>
Date: Wed, 09 Oct 2013 22:04:36 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu> <5254E9EF.6010807@gmail.com> <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com>
In-Reply-To: <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 09 Oct 2013 14:04:48 -0000

On 2013-10-09 20:35, Ted Lemon wrote:
> On Oct 9, 2013, at 1:30 AM, Melinda Shore <melinda.shore@gmail.com> wrote:
>>> Rough consensus - An agreement by almost everyone that the proposed
>>
>> That's a lot like voting, I think.
>
> It's worse than voting, because it encourages people to invite their friends to sway the consensus.   At least with voting you have the transparency of knowing who the electorate is.   So if this were what "rough consensus" meant, rough consensus would most often be won by whoever has the most friends, which in practice is probably whoever works for the biggest company.  So whatever "rough consensus" means, it can't mean "only a few people disagree."
>

OK - I don't know what is wrong, but either
- I can't write; or
- some leading members of our community can't or don't care to read

Ted,

what you are describing is is not a "group", it is a group or a loosely
collection of people subject to manipulation.

There is no room for that type of manipulation if we shall be able to
talk about consensus/rough consensus (at least we seem to agree on
that).

If we have wg-chairs, ADs or chairs that are not able to detect this
kind of manipulation we are in bad shape.

What I tried to talk about is the the state of mind the (un-manipulated) 
group needs to be in before someone can make a
consensus call; again not a definition, just a way of thinking about
it.

With that I rest my case.

/Loa


-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From wesley.george@twcable.com  Wed Oct  9 07:18:44 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31EEB21E809C for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.663
X-Spam-Level: 
X-Spam-Status: No, score=-0.663 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.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 u--SO-KS0xXN for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 07:18:39 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id DEA8F21E808A for <ietf@ietf.org>; Wed,  9 Oct 2013 07:18:34 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.90,1064,1371096000"; d="scan'208";a="141480678"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 09 Oct 2013 10:16:52 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 9 Oct 2013 10:17:48 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, IETF Discussion <ietf@ietf.org>
Date: Wed, 9 Oct 2013 10:17:47 -0400
Subject: RE: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service	Provider) to	Informational RFC
Thread-Topic: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service	Provider) to	Informational RFC
Thread-Index: AQI/ndlfzgUZlnPbGghF8PiUqVuXwpkH30OggAAazqCAAYpg4IABIvUg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923043C7557D4@PRVPEXVS15.corp.twcable.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645BD4A63@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645BD4A63@dfweml509-mbx.china.huawei.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: Wed, 09 Oct 2013 14:18:44 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Linda Dunbar

>
> - We all understand the challenges of "Full Automation". However, the
> SDN and Full automation are two separate angles to Carrier networks. I
> find the Section 4.1  "Implications of full automation" actually de-
> rails the focus of the draft on SDN.

[WEG] I strongly disagree. First, "we all understand..." is an overgenerali=
zation, and a dangerous and grossly inaccurate one at that. Lots of SDN ven=
dors have repeatedly demonstrated to me how little they actually understand=
 about this problem. It's not a new problem by any means, but there's a rea=
lly significant amount of hand-waving going on around the complexities of a=
ctually doing what they're saying is possible through the "magic" of SDN, w=
hen few have demonstrated how the abstract concept "SDN" actually makes sol=
ving this problem easier. The reality is that SDN and automation are inextr=
icably linked. The next to last sentence in section 2.3 reinforces this, an=
d I believe that 4.1 is absolutely appropriate for this draft. A truly soft=
ware-defined network is an automated one, and any discussion of an operator=
's perspective on SDN is going to need to consider the same challenges that=
 have been present in prior attempts to better automate network management,=
 provisioning, and control. There are two models for managing a network lik=
e this, one that is fully automated, meaning that it is quite a lot more co=
mplex and susceptible to "ghost in the machine" problems, the other which h=
as a human making most of the important decisions and then dictating those =
to the network. Even the latter model requires a significant amount of auto=
mation to execute what the human has decided should be done.
The things covered in section 4.1 mirrors a lot of the discussion that I ha=
ve had both internally and with other operators around the challenges of se=
parating the hype of SDN from the actual benefit, and in selling this model=
 to operations folks who are skeptical of ceding control to a set of comput=
er logic.

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From cgriffiths@gmail.com  Wed Oct  9 07:44:04 2013
Return-Path: <cgriffiths@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 0E92221E8092; Wed,  9 Oct 2013 07:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.282
X-Spam-Level: 
X-Spam-Status: No, score=-2.282 tagged_above=-999 required=5 tests=[AWL=0.317,  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 ZXnMl7sWyWIC; Wed,  9 Oct 2013 07:44:03 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 65B2321E8056; Wed,  9 Oct 2013 07:44:03 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id t7so646610qcv.35 for <multiple recipients>; Wed, 09 Oct 2013 07:44:02 -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; bh=5IzwB/OKTkiSLANJbk3ycu2ZHYt9YjJUuUVTTwSyqqw=; b=P6W001K3nHoTY5LSaH5BQSgPcDeQoTSPW3t79dw55IuBMz3KbkRJdR/gm9Q6lTws/D hC/rRQuGDAbSPPqpVbO/NAWQneWBNelKGeb6VOuxQ0l/gf/sQOHZ/WoksieS1yLENFsR /pxplHOBUVMNalL8aHac69ftj8c/7fqisYgArDloUHxA4MoxivON7jzEXTcsZctD0RR8 BVnjvatAFZ8q1Lg9ySW4GpQA24TwZ5Cznlshopyn84WBO6NHVSt7Qunp3n7SPCukUwjQ HbRR0oSnQfJFKeXcbbnMjUlCYBpTPPI4wbP7bj0fET3Z3QXnb2KzUdVnUr5Vh+oj7Nyo 9mVw==
X-Received: by 10.224.120.138 with SMTP id d10mr11460299qar.20.1381329842280;  Wed, 09 Oct 2013 07:44:02 -0700 (PDT)
Received: from [172.16.28.177] (nat-08-mht.dyndns.com. [216.146.45.247]) by mx.google.com with ESMTPSA id i4sm86918165qan.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 07:44:01 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_DD7D16BF-DBB8-4224-A5B8-7151C6451525"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Chris Griffiths <cgriffiths@gmail.com>
In-Reply-To: <9824D1EA-EDAA-4BFB-A9D0-A0AFEAE546CD@gmail.com>
Date: Wed, 9 Oct 2013 10:43:55 -0400
Message-Id: <C8BCDFAF-EBAC-4D0F-AD80-8320F22B9FF3@gmail.com>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <6.2.5.6.2.20130924135945.0d561cd0@resistor.net> <9824D1EA-EDAA-4BFB-A9D0-A0AFEAE546CD@gmail.com>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1510)
Cc: Trustees Trustees <trustees@ietf.org>, John C Klensin <klensin@jck.com>, Nevil Brownlee <n.brownlee@auckland.ac.nz>, "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, 09 Oct 2013 14:44:04 -0000

--Apple-Mail=_DD7D16BF-DBB8-4224-A5B8-7151C6451525
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Sep 26, 2013, at 3:12 PM, Chris Griffiths <cgriffiths@gmail.com> =
wrote:

> On Sep 24, 2013, at 6:11 PM, SM <sm@resistor.net> wrote:
>=20
>> At 23:48 02-08-2013, Chris Griffiths wrote:
>>> Issue 1
>>>=20
>>> We have recently been asked permission to republish the TAO with a =
creative commons license, but according to counsel, the current trust =
agreement does not give the trustees the rights to do this.
>>>=20
>>> - Without specific language being added to the trust agreement, we =
cannot grant these types of requests.
>>> - The current open request for a creative commons license from =
6/18/2013 cannot be completed.
>>=20
>> In term of "outgoing" rights the Independent Submission Stream is =
different from the IETF Stream.  The draft version of the Tao might =
offer a path forward.  Would it be possible to have it submitted through =
the Independent Submission Stream and use that version and changes to =
address the above request?
>> I haven't looked into the process stuff.  It might be possible [1] to =
sort that out once the legal hurdles are settled.

SM,

I wanted to follow-up with this specific request and advise that based =
on discussions with legal council and feedback from the Trustees that =
the current rules don't allow granting permission to republish this =
using the Independent Submission Stream, nor to grant a Community =
Commons license.  At this time we also do not have community consensus =
to prioritize a change to the rules in order to meet this request.

Thank you=20

Chris Griffiths


--Apple-Mail=_DD7D16BF-DBB8-4224-A5B8-7151C6451525
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSVWuvAAoJEE4wr5snmnsMgYAIAMroH45RojKp8Q46ztmdS9hd
svD+heJRxT0YBM/8RraQtq2+XkvFSyFncQ6hIxMLnfWee0rfXdJRrhuSZt4BZwES
9nCmG5k+5G3JDQdNKSBrb3XhBuNh6G8DeIs2vvsDngdXfdGjmbNOSfdMSru21Ev4
kUjqyEzwyi5ks9l53JSGEUxGec4t5OFIAh+zwx3NRgZv62olMymNUVjg/9E/BaZx
V4PJvER5SehlqdfBf6TaTnFka/QQtXyiu7gf7ahs2Ne18z0DqM7DERdFh69DQq4Q
qwZR8KWZZQo7VFcn2eYEcFBz8TwUqe/+kavtFvMDmSuI69KISOoam2mHLcBqwnc=
=hwF9
-----END PGP SIGNATURE-----

--Apple-Mail=_DD7D16BF-DBB8-4224-A5B8-7151C6451525--

From fluffy@cisco.com  Wed Oct  9 08:27:50 2013
Return-Path: <fluffy@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 BEBED11E81B0; Wed,  9 Oct 2013 08:27: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 3y5ZAqeIGv0t; Wed,  9 Oct 2013 08:27:16 -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 2426811E81A7; Wed,  9 Oct 2013 08:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2731; q=dns/txt; s=iport; t=1381332423; x=1382542023; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=jubzkgbSbqERMjtJAeztuR6yTTZVdoDs9f7hl0UjD7Q=; b=lXMUfdjK4b+TlYUqdVIeVLiTSN2xVAij4olj36oqyS6mu5iPB6NgokJI Ie++TiAQbDYudDsz5NGBdGuT0XjyXlCcTo7IyoWnQ5lkWjRmIThU/A8/S en4C7zXvTyeESMxzvedxjBWa+rQjEWZE7y/b0CJCJZwQVs9ARpcZlwkOC g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAOZ0VVKtJXHB/2dsb2JhbABagweBCsE2gR0WdIIlAQEBAwFuCwULAgEIGAoZCzIlAgQOBQgTh2UGuSOOBoEMAjEHAoMdgQQDqgSBZoE+gWhC
X-IronPort-AV: E=Sophos;i="4.90,1064,1371081600"; d="scan'208";a="267025528"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 09 Oct 2013 15:26:59 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r99FQwn7029704 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Oct 2013 15:26:58 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Wed, 9 Oct 2013 10:26:58 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Index: AQHOxG6tx36dkMJ3pkem9MOxfSCBUpns0u+A
Date: Wed, 9 Oct 2013 15:26:57 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com>
In-Reply-To: <EF97C65E-A58C-4076-B737-014126786442@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5603CDFB277C35468D0983C357766839@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@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, 09 Oct 2013 15:27:51 -0000

On Oct 8, 2013, at 3:38 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Oct 8, 2013, at 4:30 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> w=
rote:
>> Part of why you can't do this with DHCP is that clients are written so t=
hat when an IP address fails to work for an application connection, the app=
lication re does the DNS and gets the new address (assuming TTL had been mo=
ved down during the move). Applications can not tell the  OS to redo DHCP w=
hen they fail an application level connection.=20
>=20
> This use case is a good example of when to use an FQDN format for a DHCP =
option.   However, it's not a great example of when to use a DHCP option=97=
configuring SIP servers with DHCP is generally a bad idea, because if your =
device is connected to a new network, it will blindly take the SIP server I=
P address or FQDN information from the DHCP server and use it, and that SIP=
 server might well perform an MitM attack or the like.

>=20
> So it's only in the very restricted use case of a Cisco IP phone permanen=
tly installed on a desktop and connected to a trusted network that (a) conf=
iguring SIP via DHCP makes sense, and (b) using the FQDN is a good idea.   =
Of course it's possible that my limited understanding of how SIP works is p=
reventing me from seeing why it's safe to configure SIP service using DHCP,=
 but I'm assuming that that's not the case in this argument; please feel fr=
ee to correct me.

Nah, it's not quite like that - Long story how that it but the security mec=
hanism make sure you authenticate both ends to stop that.=20

>=20
> We've actually been having this same conversation on the iesg mailing lis=
t, and I asserted that SIP was something you ought not to configure with DH=
CP; your use case is the one case where it sort of makes sense.   Can you t=
hink of similar use cases where it actually makes sense to configure these =
parameters via DHCP?
>=20
> Possibly the right solution is to update the document to talk about this =
sort of restricted use case as one where FQDNs actually do make sense.   Th=
e document certainly doesn't say you _can't_ use FQDNs, but we see people w=
anting to use them a lot in cases where they really don't make sense, hence=
 the advice.   Historically I don't think we bothered to make this distinct=
ion when defining new DHCP options, but it seems like a useful distinction =
to make.

Help educate me on this a bit - I don't see all the things that get request=
ed of DHCP. What are some examples of things where people are request FQDN =
where IP would be better. I think having some real examples that have come =
up would make it easier to see what advice is needed.=20


From Fred.L.Templin@boeing.com  Wed Oct  9 08:38:34 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF7B11E81A0; Wed,  9 Oct 2013 08:38: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 4jQkWYCyevaE; Wed,  9 Oct 2013 08:38:25 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 807FD11E81AC; Wed,  9 Oct 2013 08:38:17 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99FcGCu028861; Wed, 9 Oct 2013 08:38:16 -0700
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99FcEUr028393 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 08:38:15 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.168]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 08:38:14 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KsVHjrcZv7kkeUppI3Iq7lo5nlBPWAgASNmgCAAXGqAIAAjlqggAD4aZA=
Date: Wed, 9 Oct 2013 15:38:14 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
In-Reply-To: <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 15:38:34 -0000

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Tuesday, October 08, 2013 5:46 PM
> To: Ole Troan; Templin, Fred L
> Cc: ipv6@ietf.org; ietf@ietf.org
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> I agree with Ole.

How so? A tunnel that crosses a 1280 MTU link MUST fragment
in order to satisfy the IPv6 minMTU. If it must fragment, then
an MTU-length IPv6 header chain would not fit within the first
fragment, and we have opened an attack vector against tunnels.
This is not a matter to be agreed or disagreed with - it is
a simple fact.

Thanks - Fred
fred.l.templin@boeing.com
=20
>        Ron
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of
> > Ole Troan
> > Sent: Tuesday, October 08, 2013 12:17 PM
> > To: Templin, Fred L
> > Cc: ipv6@ietf.org; ietf@ietf.org; IETF-Announce
> > Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> > (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >
> > Fred,
> >
> > > Hi, I would like to make a small amendment to what I said in my
> > > previous message as follows:
> > >
> > > 4) Section 5, change the final paragraph to:
> > >
> > >   "As a result of the above mentioned requirements, a packet's
> header
> > >   chain length MUST fit within the Path MTU associated with its
> > >   destination.  Hosts MAY discover the Path MTU, using procedures
> > such
> > >   as those defined in [RFC1981] and [RFC4821]. However, if a host
> > does
> > >   not discover the Path MTU, it MUST assume the IPv6 minumum MTU of
> > >   1280 bytes [RFC2460]. The host MUST then limit each packet's
> header
> > >   chain length to the Path MTU minus 256 bytes in case additional
> > >   encapsulation headers are inserted by tunnels on the path."
> >
> > I would claim that additional encapsulation headers are already
> > considered in the 1280 minimum MTU.
> > as in: 1500 - 1280.
> >
> > cheers,
> > Ole
>=20


From Ted.Lemon@nominum.com  Wed Oct  9 08:48: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 AA1AD11E819A; Wed,  9 Oct 2013 08:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.581
X-Spam-Level: 
X-Spam-Status: No, score=-106.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 UWDjX2-zqf07; Wed,  9 Oct 2013 08:48:01 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id ACDF611E81BF; Wed,  9 Oct 2013 08:47:54 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUlV6qWz2SHwhh8JD4oTjEwVHPyPYR5p+@postini.com; Wed, 09 Oct 2013 08:47:54 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 F2B231B82E5; Wed,  9 Oct 2013 08:47:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 EA09A190061; Wed,  9 Oct 2013 08:47:52 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 08:47:52 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com>
Date: Wed, 9 Oct 2013 11:47:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@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, 09 Oct 2013 15:48:07 -0000

On Oct 9, 2013, at 11:26 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:
> Help educate me on this a bit - I don't see all the things that get =
requested of DHCP. What are some examples of things where people are =
request FQDN where IP would be better. I think having some real examples =
that have come up would make it easier to see what advice is needed.

DNS server IP address.   NTP server IP address.   Router IP address (not =
in DHCPv6, of course).   AFTR IP address.   Basically, network =
infrastructure IP addresses.

Bear in mind that the set of services configured by DHCP ought to be =
pretty small=97just things that really are local network infrastructure =
services, not things that are specific to the host and not to the =
network.   It's not even clear to me that NTP ought to be configured by =
DHCP, and indeed in most cases it is not, despite there being an RFC =
describing how to do it.

Considering the case of SIP, when you configure SIP I think that's =
probably a configuration that shouldn't change as the phone moves from =
network to network.   So it shouldn't be configured by DHCP.   In the =
case where the phone happens not to be likely to move from network to =
network, you could _get away_ with using DHCP.   But a solution that =
would work for phones that _do_ move from network to network would also =
work for phones that do not, and that solution would therefore be =
preferable, particularly as an MTI solution, since it addresses all use =
cases.

As I mentioned in the IESG discussion, it is a shame that aggsrv didn't =
become a working group, since it was intended to address this specific =
problem, at least as I understood it.


From tobias.gondrom@gondrom.org  Wed Oct  9 09:03:57 2013
Return-Path: <tobias.gondrom@gondrom.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 41FE421F9DDE for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 09:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.362
X-Spam-Level: 
X-Spam-Status: No, score=-95.362 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.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 x1I8-rI3PV92 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 09:03:52 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id EDC9421F9B9F for <ietf@ietf.org>; Wed,  9 Oct 2013 09:02:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=YMoKFBkGSkh6nR6yafhc3W+B0mzwY9hKDGdQW04OqQRgG153NFhmFltF9ckEKP+LRBQqVNnAqLwZ7K+o5JsR7ythneQbOkAM9CD3F4Y5kAlq8pH/R4bFqZux/XMFCJmM; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type;
Received: (qmail 5341 invoked from network); 9 Oct 2013 18:02:18 +0200
Received: from 188-222-103-191.zone13.bethere.co.uk (HELO ?192.168.1.71?) (188.222.103.191) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 9 Oct 2013 18:02:18 +0200
Message-ID: <52557E09.9010102@gondrom.org>
Date: Wed, 09 Oct 2013 17:02:17 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ted.lemon@nominum.com
Subject: Re: Montevideo statement
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <525533D0.8060409@gondrom.org> <5BEDC090-F92D-47D8-A9D1-55C8011919D7@nominum.com>
In-Reply-To: <5BEDC090-F92D-47D8-A9D1-55C8011919D7@nominum.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------070002060707010302050908"
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, 09 Oct 2013 16:03:57 -0000

This is a multi-part message in MIME format.
--------------070002060707010302050908
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

On 09/10/13 14:14, Ted Lemon wrote:
> On Oct 9, 2013, at 6:45 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> wrote:
>> But I support SM's proposal that it would be good
>> to do a few days comment period for such important statements in the
>> future - if timing is not critical. There is no harm in a few days delay
>> and getting input from the community.
> This is a nice theory, but the usual last call time at IETF is either two weeks or four weeks, not a few days, and that's for a good reason.  I think there is no way that a statement of the type we are discussing can ever represent IETF consensus unless we go through an actual consensus call.
>
> So the real question here is, is it ever appropriate for the chair of the IAB or the chair of the IETF to sign a statement like this without getting consensus?   I think that's a good question, and I don't have a strong opinion on the answer.   But if the answer is that we need consensus, then we actually need to do a consensus call.
>
> The only value I see in "a few days" would be an opportunity for wordsmithing—as someone pointed out, the current statement could be read as expressing concern that secrets were leaked, rather than concern about what was done in secret, and it would have been nice if that wording could have been corrected.   If that is what you were asking for, then that does make sense.
>
> (thinking out loud...)
>

Yes, that is what is was thinking about. Probably wisdom of the crowds
could have helped with the wordsmithing part.
And in my view even some little feedback (3-7 days) is better than none.
And just to be clear: with such a short comment option, the goal is just
comments not to get a rough consensus.

All the best, Tobias


--------------070002060707010302050908
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 09/10/13 14:14, Ted Lemon wrote:<br>
    </div>
    <blockquote
      cite="mid:5BEDC090-F92D-47D8-A9D1-55C8011919D7@nominum.com"
      type="cite">
      <pre wrap="">On Oct 9, 2013, at 6:45 AM, Tobias Gondrom <a class="moz-txt-link-rfc2396E" href="mailto:tobias.gondrom@gondrom.org">&lt;tobias.gondrom@gondrom.org&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">But I support SM's proposal that it would be good
to do a few days comment period for such important statements in the
future - if timing is not critical. There is no harm in a few days delay
and getting input from the community.
</pre>
      </blockquote>
      <pre wrap="">
This is a nice theory, but the usual last call time at IETF is either two weeks or four weeks, not a few days, and that's for a good reason.  I think there is no way that a statement of the type we are discussing can ever represent IETF consensus unless we go through an actual consensus call.

So the real question here is, is it ever appropriate for the chair of the IAB or the chair of the IETF to sign a statement like this without getting consensus?   I think that's a good question, and I don't have a strong opinion on the answer.   But if the answer is that we need consensus, then we actually need to do a consensus call.

The only value I see in "a few days" would be an opportunity for wordsmithing—as someone pointed out, the current statement could be read as expressing concern that secrets were leaked, rather than concern about what was done in secret, and it would have been nice if that wording could have been corrected.   If that is what you were asking for, then that does make sense.

(thinking out loud...)

</pre>
    </blockquote>
    <font face="Arial"><br>
      Yes, that is what is was thinking about. Probably wisdom of the
      crowds could have helped with the wordsmithing part. <br>
      And in my view even some little feedback (3-7 days) is better than
      none. And just to be clear: with such a short comment option, the
      goal is just comments not to get a rough consensus. <br>
      <br>
      All the best, Tobias<br>
      <br>
    </font>
  </body>
</html>

--------------070002060707010302050908--

From housley@vigilsec.com  Wed Oct  9 09:25: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 C202521E815E for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 09:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, 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 Obz8YXLhNnCs for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 09:25:06 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0159221F8CDD for <ietf@ietf.org>; Wed,  9 Oct 2013 09:24:08 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 06B9AF24089; Wed,  9 Oct 2013 12:24:21 -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 OGhSYJ8sbGQQ; Wed,  9 Oct 2013 12:23:56 -0400 (EDT)
Received: from [192.168.2.107] (pool-71-191-197-233.washdc.fios.verizon.net [71.191.197.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B2290F2408B; Wed,  9 Oct 2013 12:24:19 -0400 (EDT)
Subject: Re: Montevideo statement
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>
Date: Wed, 9 Oct 2013 12:24:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <63642766-94C3-4A0A-A5D9-6722E89FBFC4@vigilsec.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
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, 09 Oct 2013 16:25:23 -0000

SM:

> This is the second time that the IAB has issued a statement without =
requesting comments from the IETF Community.  In my humble opinion it =
would be good if there was a comment period.

This is a statement about what happened at a meeting.  Discussion would =
not change what happened at the meeting.  Making the statement very =
public allows a good discussion of what should happen next.  I look =
forward to that discussion.

Russ


From david.black@emc.com  Wed Oct  9 09:30:45 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 D3C1F21F99F0; Wed,  9 Oct 2013 09:30: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=[AWL=0.001, 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 6qSQ5CTFo2c1; Wed,  9 Oct 2013 09:30:40 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E744421F880F; Wed,  9 Oct 2013 09:28:27 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r99GRsQn003031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 12:27:55 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r99GRsQn003031
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1381336075; bh=GKyJC2XbFKRMKdRcyRsXRTllMz8=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=JNPjmDwK8flzFwELo6wTtVT2xPYUONpTNQO3teab5MSVZN+TrdOeoiL9QeVApPrNx 0Pgs4k1S0tEycCSmVYQTDnSrbVsjUoSZM0JJxnVcMFLKT47+d+3bnuelYaIhwmfUCn olRyNfJDjjAR9hCoo1Is988mz265/aT1CipCIKXc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r99GRsQn003031
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd02.lss.emc.com (RSA Interceptor); Wed, 9 Oct 2013 12:27:46 -0400
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r99GRjwl030080 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Oct 2013 12:27:46 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Wed, 9 Oct 2013 12:27:46 -0400
From: "Black, David" <david.black@emc.com>
To: "kent@bbn.com" <kent@bbn.com>, "achi@cs.unc.edu" <achi@cs.unc.edu>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Wed, 9 Oct 2013 12:27:44 -0400
Subject: Gen-ART review of draft-ietf-sidr-bgpsec-threats-07
Thread-Topic: Gen-ART review of draft-ietf-sidr-bgpsec-threats-07
Thread-Index: Ac7FDHoXTpnzCWzcRRiztQCbALnpTw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712025DCE24E0@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-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-EMM-GWVC: 1
X-EMM-McAfeeVC: 1
X-RSA-Classifications: public
Cc: "sidr@ietf.org" <sidr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <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: Wed, 09 Oct 2013 16:30:45 -0000

After discussion with the authors, the -07 version of this draft resolves
the two issues in the Gen-ART review of the -06 version.  In summary:

- Text has been added to explain the relationship of the PATHSEC and BGPsec=
 terms.
- Citations have been added to the RFCs that explain the RPKI RP caching
	requirements.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, September 23, 2013 8:25 PM
> To: kent@bbn.com; achi@cs.unc.edu; General Area Review Team (gen-art@ietf=
.org)
> Cc: Black, David; stbryant@cisco.com; ietf@ietf.org; sidr@ietf.org
> Subject: Gen-ART review of draft-ietf-sidr-bgpsec-threats-06
>=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>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-sidr-bgpsec-threats-06
> Reviewer: David L. Black
> Review Date: September 23, 2012
> IETF LC End Date: September 23, 2012
>=20
> Summary:  This draft is on the right track, but has open issues
> described in the review.
>=20
> This draft describes the threat model for BGP Path Security.  The
> draft generally reads well, but does contain quite a bit of serious
> security analysis of an important routing protocol and hence requires
> both security and routing expertise to fully understand.
>=20
> Major issue:
>=20
> This draft contains more than just a threat model.  It also contains
> a high level security analysis of the security architecture/approach
> that applies the RPKI to secure use of BGP.  That analysis appears to
> be good, but it's somehow disconnected from the rest of the sidr WG's
> work, by what I hope is simply a terminology problem:
> 	- This draft refers to the security architecture/approach for
> 		BGP as PATHSEC.
> 	- Many of the other sidr WG draft refer to that security as
> 		BGPsec
> In effect, the PATHSEC security architecture/approach appears to be
> implicit in this draft.
>=20
> Something's missing - if those two terms were meant to be the same,
> BGPsec should probably be used in this draft, otherwise, the relationship
> should be described.  I've tagged this as a major issue, as it makes
> text like the following in Section 4.2 rather unclear:
>=20
>       Stale Path Announcement: If PATHSEC-secured announcements can
>       expire, such an announcement may be propagated with PATHSEC data
>       that is "expired".  This behavior would violate the PATHSEC goals
>       and is considered a type of replay attack.
>=20
> What is "PATHSEC data"?  What are "the PATHSEC goals"?  The statement
> in the abstract that " We use the term PATHSEC to refer to any BGP
> path security technology that makes use of the RPKI" doesn't seem to
> answer these questions.
>=20
> Minor Issue:
>=20
> Section 4.4 seems somewhat loose on caching by RPs, considering the
> importance of that caching in countering a number of the attacks describe=
d
> in that section - in multiple cases, RP detection of an attack relies
> upon the RP noticing that something has changed at the publication point
> wrt the RP's cached copy in a fashion that should not have happened.
>=20
> Statements such as "the RPKI calls for RPs to cache" and "RPs are
> expected to make use of local caches" strike me as a weak foundation
> for the level of security dependence on that caching.  A pointer to a
> SHOULD or MUST requirement for caching by RPKI RPs in another document
> would alleviate this concern; surely that language exists somewhere.
>=20
> Nits/editorial comments:
>=20
> Also in Section 4.4:
>=20
>    (The RP would be very unhappy if
>    there is no CRL for the CA instance anyway.)
>=20
> Please rewrite to describe how the RP reacts to failure to find a CRL
> - the RP surely does something in addition to becoming "very unhappy" ;-)=
.
> Some of that may already be in the sentence immediately following the
> "very unhappy" text.
>=20
> idnits 2.12.17 complains about a missing reference:
>=20
>   =3D=3D Missing Reference: 'TCPMD5' is mentioned on line 114, but not de=
fined
>=20
> That citation is embedded in a quote from RFC 4272, nonetheless, [TCPMD5]
> should be informatively referenced here - it was RFC 2385, which has been
> obsoleted by RFC 5925, which is referenced here.  The fact that RFC 2385
> is obsolete will generate a different idnits warning, which is ok to igno=
re.
>=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
> ----------------------------------------------------
>=20


From mary.ietf.barnes@gmail.com  Wed Oct  9 03:10:27 2013
Return-Path: <mary.ietf.barnes@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 C340821F9A6C; Wed,  9 Oct 2013 03:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.386
X-Spam-Level: 
X-Spam-Status: No, score=-102.386 tagged_above=-999 required=5 tests=[AWL=0.213, 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 Kzms+hD-+gCd; Wed,  9 Oct 2013 03:10:27 -0700 (PDT)
Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED3B21F9A70; Wed,  9 Oct 2013 03:10:21 -0700 (PDT)
Received: by mail-qe0-f50.google.com with SMTP id a11so462263qen.23 for <multiple recipients>; Wed, 09 Oct 2013 03:10: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=y+cFXqu2ytIxy4TBmvHfjur6Gn8WXxS802lCdnziGo0=; b=rUsz2uuAwd8y9epJC1sbiL9xNr9P4C7Nsxbcb5YG2hmqLSUely9LZapLIEew9+yuXb K2rC2BtVbO8xwKzEKtOaD7cIjrYBirQ/0tiw18DlcCdQZeLx6VTDY7tpqRR0T5Ofl2Qq iTWtMH3mMVb2B09tm51pcFHRb9dUyIB4f1KJ/QwcS74Tz8EyOVDIFlYNAwYkBlJu2Zs1 rmGUmI4BJ+HOTFFw5x4b0ax2C4A7O2rizioxt+6AuwXqYk8fJ/2TaguvfU8++i4AYSWZ VLxxSfj+NK7CFdBjyJfGJmTkzmeU0yVc67vr3Jwt7OYDCbu/cp7+XgSO8e134jN0s+nZ LAtQ==
MIME-Version: 1.0
X-Received: by 10.224.67.3 with SMTP id p3mr1228599qai.98.1381313421098; Wed, 09 Oct 2013 03:10:21 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Wed, 9 Oct 2013 03:10:21 -0700 (PDT)
In-Reply-To: <6C5232DC-1221-4C87-8A9C-ABA457A1FC13@nostrum.com>
References: <6C5232DC-1221-4C87-8A9C-ABA457A1FC13@nostrum.com>
Date: Wed, 9 Oct 2013 05:10:21 -0500
Message-ID: <CAHBDyN7POboN=LKZjnrNVdxr3KcWFtab-OHZDjr2j=_QS0y35w@mail.gmail.com>
Subject: Re: Gen-ART Telechat Review of draft-yusef-dispatch-ccmp-indication-06
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001a11c3dfa6c9c6e804e84c17eb
X-Mailman-Approved-At: Wed, 09 Oct 2013 09:35:30 -0700
Cc: "gen-art@ietf.org \(gen-art@ietf.org\)" <gen-art@ietf.org>, "draft-yusef-dispatch-ccmp-indication.all@tools.ietf.org" <draft-yusef-dispatch-ccmp-indication.all@tools.ietf.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: Wed, 09 Oct 2013 10:10:27 -0000

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

Thanks Ben.  We'll fix these nits in the next version.

Mary.


On Tue, Oct 8, 2013 at 3:39 PM, Ben Campbell <ben@nostrum.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 wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-yusef-dispatch-ccmp-indication-06
> Reviewer: Ben Campbell
> Review Date: 2013-10-08
> IESG Telechat date: 2013-10-10
>
> Summary: This draft is ready for publication as an informational RFC. This
> version addresses all the comments from my last call review of version 04.
> I do have a couple of new (or I missed the first time) editorial comments
> that might be worth addressing if there is a new version prior to approval.
>
> Major issues:
>
> None
>
> Minor issues:
>
> None
>
> Nits/editorial comments:
>
> -- General:
>
> idnits 2.12.18 reports some missing references--please check.
>
> -- Abstract and Intro
>
> Please expand UA and XCON on first mention (Both in Abstract and in
> Section 1).
>
>

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

<div dir=3D"ltr">Thanks Ben. =A0We&#39;ll fix these nits in the next versio=
n.<div><br></div><div>Mary.</div></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Tue, Oct 8, 2013 at 3:39 PM, Ben Campbell <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@=
nostrum.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">I am the assigned Gen-ART reviewer for this =
draft. For background on<br>
Gen-ART, please see the FAQ at<br>
&lt; <a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" ta=
rget=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>=
&gt;.<br>
<br>
Please wait for direction from your document shepherd<br>
or AD before posting a new version of the draft.<br>
<br>
Document: draft-yusef-dispatch-ccmp-indication-06<br>
Reviewer: Ben Campbell<br>
Review Date: 2013-10-08<br>
IESG Telechat date: 2013-10-10<br>
<br>
Summary: This draft is ready for publication as an informational RFC. This =
version addresses all the comments from my last call review of version 04. =
I do have a couple of new (or I missed the first time) editorial comments t=
hat might be worth addressing if there is a new version prior to approval.<=
br>

<br>
Major issues:<br>
<br>
None<br>
<br>
Minor issues:<br>
<br>
None<br>
<br>
Nits/editorial comments:<br>
<br>
-- General:<br>
<br>
idnits 2.12.18 reports some missing references--please check.<br>
<br>
-- Abstract and Intro<br>
<br>
Please expand UA and XCON on first mention (Both in Abstract and in Section=
 1).<br>
<br>
</blockquote></div><br></div>

--001a11c3dfa6c9c6e804e84c17eb--

From tony@yaanatech.com  Wed Oct  9 04:44:31 2013
Return-Path: <tony@yaanatech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C0C11E816F for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 04:44: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 Lo7m41AmVwUA for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 04:44:25 -0700 (PDT)
Received: from extmail1.yaanatech.com (extmail1.yaanatech.com [63.128.177.51]) by ietfa.amsl.com (Postfix) with SMTP id DA05C11E8172 for <ietf@ietf.org>; Wed,  9 Oct 2013 04:44:23 -0700 (PDT)
Received: from [192.168.0.18] (pool-71-171-119-184.clppva.fios.verizon.net [71.171.119.184]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.yaanatech.com (Postfix) with ESMTP id 143A65808F for <ietf@ietf.org>; Wed,  9 Oct 2013 11:44:51 +0000 (UTC)
Message-ID: <52554196.8030307@yaanatech.com>
Date: Wed, 09 Oct 2013 07:44:22 -0400
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: [mile] Last Call: <draft-ietf-mile-sci-09.txt> (IODEF-extension for structured cybersecurity information) to Proposed
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040008020209010105010505"
X-Mailman-Approved-At: Wed, 09 Oct 2013 09:35:34 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2013 11:44:31 -0000

This is a cryptographically signed message in MIME format.

--------------ms040008020209010105010505
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

This proposed standard is both
urgently needed as well an innovative
and ideal model for structured
exchange of this information.
It also has received considerable
broad review over the past two
years.  The authors deserve cudos
for their work.

--tony




--------------ms040008020209010105010505
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINDTCC
BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0
aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp
bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx
MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh
dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg
U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn
/R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb
jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR
I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk
VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh
xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI
KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t
MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG
AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw
Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl
cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx
GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE
Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT
MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD
BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB
dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP
wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM
YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi
Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t
lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ
3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggbDMIIFq6ADAgECAhBT
hNb1O1n4bTJo0Ah1+gicMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE
ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv
cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzAzMDgwMDAwMDBa
Fw0xNDAzMDkyMzU5NTlaMIHEMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx
MzYyNzM4NTgzNTAzMSEwHwYJKoZIhvcNAQkBFhJ0b255QHlhYW5hdGVjaC5jb20xDzANBgNV
BAsMBlMvTUlNRTEeMBwGA1UECwwVUGVyc29uYSBOb3QgVmFsaWRhdGVkMR8wHQYDVQQLDBZT
eW1hbnRlYyBUcnVzdCBOZXR3b3JrMR0wGwYDVQQKDBRTeW1hbnRlYyBDb3Jwb3JhdGlvbjCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALTsANG1JvM4PXw45I4MAIPHPeu6urf2
ml82bH8tuyaGBzUX8AaxBPzChNDbng2wU264FzNKHOVQbiFAH14Xxb1Ih5uPvWh45feCO7PU
tSlkdHQSzilC8aOWEdy4+DZXzujp331xSZkjbT1iNWBhjhXubJTDwiYQWT0MBiN3A2IWC+1a
PVQvzSZyLLrM7QexO0A3fGuzWtJ9RMUBw++KuB3FQ/nM5iyKhfu2tfP7yiBV4rlwWdbbNe02
PLs2qwMPxIja/JT6tUdgjTn04XUynFgAbTVZniUkra+OodXxk9JGeIGgB+GorAwT0x/TcDeN
+DXoHfiBSso2Vmvwx+JkFNECAwEAAaOCAsswggLHMAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/
BAQDAgWgMCAGA1UdJQEB/wQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU+ENL
NB52WskhlVdfucmC2XHR4Y8wHQYDVR0RBBYwFIESdG9ueUB5YWFuYXRlY2guY29tMB8GA1Ud
IwQYMBaAFK35w5NyLbW5KGHkpNdg1cQKXhoBMIIBKwYIKwYBBQUHAQEEggEdMIIBGTCCARUG
CCsGAQUFBzAChoIBB2xkYXA6Ly9kaXJlY3RvcnkudmVyaXNpZ24uY29tL0NOJTIwJTNEJTIw
U3ltYW50ZWMlMjBDbGFzcyUyMDElMjBJbmRpdmlkdWFsJTIwU3Vic2NyaWJlciUyMENBJTIw
LSUyMEc0JTJDJTIwT1UlMjAlM0QlMjBQZXJzb25hJTIwTm90JTIwVmFsaWRhdGVkJTJDJTIw
T1UlMjAlM0QlMjBTeW1hbnRlYyUyMFRydXN0JTIwTmV0d29yayUyQyUyME8lMjAlM0QlMjBT
eW1hbnRlYyUyMENvcnBvcmF0aW9uJTJDJTIwQyUyMCUzRCUyMFVTP2NBQ2VydGlmaWNhdGU7
YmluYXJ5MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9wa2ktY3JsLnN5bWF1dGguY29tL2Nh
XzU2MWMxMDM2OTBjOTdhNjkyNDdhMGVmMDcxYWM4MWFmL0xhdGVzdENSTC5jcmwwbAYDVR0g
BGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGgu
Y29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTAqBgpg
hkgBhvhFARADBBwwGgYRYIZIAYb4RQEQAQICBAGGsxcWBTEwOTIyMA0GCSqGSIb3DQEBBQUA
A4IBAQDGN/ju6G1Df12wYlBSOzo39vOfJuVASX31X0WWvLieGYzIFPY1IRubH/TCfsUmdGxT
12q1Y6zm1nK+wmPg1xOFhgJNK9+Tfixu2WoKtkG5ZCeWcv48tyUGcr6+UHfvSdLxSQfmNuEU
6T30xH9zEkzChmI9FoUP4V+DjS49bbP9b3KlMNkJDOKrVNI5I233qmYxZZYatMartahrBIwy
Qfgor3+M/O8QYzYCAeSMwtpNYNqNXOlLBSCbGt4Y1Kdz7Xgg0fD49vMvRloZ3cMCCv2cLeg2
WlbxotVsn9IbWHq4CZbUKytgREtcbHUgbiIrYnlC4rcSxjX71W1W/u/gDNqgMYIEUjCCBE4C
AQEwgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEf
MB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3Qg
VmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEc0AhBThNb1O1n4bTJo0Ah1+gicMAkGBSsOAwIaBQCgggJrMBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMTAwOTExNDQyMlowIwYJKoZI
hvcNAQkEMRYEFIW3GgyMzCKdIYmopopfklYfwJ55MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZI
AWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZI
hvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgcwGCSsGAQQBgjcQBDGBvjCBuzCB
pjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBvcmF0aW9uMR8wHQYDVQQL
ExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0
ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENB
IC0gRzQCEFOE1vU7WfhtMmjQCHX6CJwwgc4GCyqGSIb3DQEJEAILMYG+oIG7MIGmMQswCQYD
VQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFu
dGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG
A1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNAIQ
U4TW9TtZ+G0yaNAIdfoInDANBgkqhkiG9w0BAQEFAASCAQAqPH+n7bPtlGzTIHlmGYjz2TlY
Gjls9+k1WU7THr8LpNwxp6MObtg2sc7IHhh1KwWczOaBUI3Akt5ddMDolnW1I4caGZC+I285
bV08ynQJcqOgZLjy7X+vuQ2MaRZt7f0gMXIrxbT8m2eh2gVXlEQdSQTM2HiqRX3FbMY3NNX1
IbCfW+hE/8Er6pGrlAZC/HqeSIsCN9JxjEVtAfIcLT8moMi8y9h2u8gJ4zBpgNAL3yjmm2Ry
EDsGEyapg9qHzTXCCEPwTMJa6vq0r7L6bDaMKyq1EGjQZfArTGIEFCObwsSKSOJfLi+9W2Vp
2YjSygagnY20B154BCcY6DcS0srxAAAAAAAA
--------------ms040008020209010105010505--

From otroan@employees.org  Wed Oct  9 09:54:04 2013
Return-Path: <otroan@employees.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 3A77C21F9EF6; Wed,  9 Oct 2013 09:54: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 UDalrdE9AQtq; Wed,  9 Oct 2013 09:53:58 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id D91D821F8DDD; Wed,  9 Oct 2013 09:53:54 -0700 (PDT)
Received: from dhcp-10-61-105-179.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id EDE946052; Wed,  9 Oct 2013 09:53:52 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 9 Oct 2013 18:53:48 +0200
Message-Id: <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 16:54:04 -0000

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Fred,

>> -----Original Message-----
>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>> Sent: Tuesday, October 08, 2013 5:46 PM
>> To: Ole Troan; Templin, Fred L
>> Cc: ipv6@ietf.org; ietf@ietf.org
>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>> 
>> I agree with Ole.
> 
> How so? A tunnel that crosses a 1280 MTU link MUST fragment
> in order to satisfy the IPv6 minMTU. If it must fragment, then
> an MTU-length IPv6 header chain would not fit within the first
> fragment, and we have opened an attack vector against tunnels.
> This is not a matter to be agreed or disagreed with - it is
> a simple fact.

right, and RFC2460 has this to say about it:

   IPv6 requires that every link in the internet have an MTU of 1280
   octets or greater.  On any link that cannot convey a 1280-octet
   packet in one piece, link-specific fragmentation and reassembly must
   be provided at a layer below IPv6.

cheers,
Ole

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSVYocAAoJEFuJXizso86ggAsIAJnGAgJoyw+0vJ4g5UQE3KQC
Y+L90GWYQCx6ae1BCbDqdklSlUSRYKyBWwyScpPEaH5cCiobKVA3IKbFf18f0BST
DsArIO3aZ0aTe0PmBqoHeW8M0At40jJYw6O3OTXrm1Hw7z3LS2DLfzflWgXoXjDz
SF8R32yClsU7IcZi1wgHxvERFk/DgGcDtCBOPpAXKtxwDU53tnpy9NgqCWfmH9hd
B5dmCgHkEknbrGo2ebWgdwrvMF8AVDxpnh4vtn0YrrP+8frN6FnpAIVjQvizAvyM
6+ze3z2XjA9oNbsmHQnQeN7+lcdJTWuPmUHvzdPuozM+2N/ecXCdNaP+w0FsDLk=
=N2+D
-----END PGP SIGNATURE-----

--Apple-Mail=_3F38F5EB-81AD-41C7-9D61-91842357817C--

From joelja@bogus.com  Wed Oct  9 10:07:23 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 EF2AD21E808F for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:07: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=[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 K2QVoNQeM0hy for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:07:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0966F21E814E for <ietf@ietf.org>; Wed,  9 Oct 2013 10:07:22 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r99H7Iqi035481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 17:07:19 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_979229A8-227D-4A4C-9FAF-B89E0C4C6203"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Montevideo statement
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <52557E09.9010102@gondrom.org>
Date: Wed, 9 Oct 2013 10:07:16 -0700
Message-Id: <70658ABA-E38A-429B-A3E6-519D5009D309@bogus.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <525533D0.8060409@gondrom.org> <5BEDC090-F92D-47D8-A9D1-55C8011919D7@nominum.com> <52557E09.9010102@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 09 Oct 2013 17:07:19 +0000 (UTC)
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, 09 Oct 2013 17:07:24 -0000

--Apple-Mail=_979229A8-227D-4A4C-9FAF-B89E0C4C6203
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 9, 2013, at 9:02 AM, Tobias Gondrom <tobias.gondrom@gondrom.org> =
wrote:

> On 09/10/13 14:14, Ted Lemon wrote:
>> On Oct 9, 2013, at 6:45 AM, Tobias Gondrom =
<tobias.gondrom@gondrom.org>
>>  wrote:
>>=20
>>> But I support SM's proposal that it would be good
>>> to do a few days comment period for such important statements in the
>>> future - if timing is not critical. There is no harm in a few days =
delay
>>> and getting input from the community.
>>>=20
>> This is a nice theory, but the usual last call time at IETF is either =
two weeks or four weeks, not a few days, and that's for a good reason.  =
I think there is no way that a statement of the type we are discussing =
can ever represent IETF consensus unless we go through an actual =
consensus call.
>>=20
>> So the real question here is, is it ever appropriate for the chair of =
the IAB or the chair of the IETF to sign a statement like this without =
getting consensus?   I think that's a good question, and I don't have a =
strong opinion on the answer.   But if the answer is that we need =
consensus, then we actually need to do a consensus call.
>>=20
>> The only value I see in "a few days" would be an opportunity for =
wordsmithing=97as someone pointed out, the current statement could be =
read as expressing concern that secrets were leaked, rather than concern =
about what was done in secret, and it would have been nice if that =
wording could have been corrected.   If that is what you were asking =
for, then that does make sense.
>>=20
>> (thinking out loud...)
>>=20
>>=20
>=20
> Yes, that is what is was thinking about. Probably wisdom of the crowds =
could have helped with the wordsmithing part.=20

I imagine that's exctly the part of course that they aren't interested =
in once they're hashed out a high-level statement (and have general =
agreement between the signatories ) is more input.=20

It seems dramatically simpler to just make the satement as individuals =
who put their name on something.


> And in my view even some little feedback (3-7 days) is better than =
none. And just to be clear: with such a short comment option, the goal =
is just comments not to get a rough consensus.=20
>=20

We have a process for obtaining consensus. It takes a little while.

> All the best, Tobias
>=20


--Apple-Mail=_979229A8-227D-4A4C-9FAF-B89E0C4C6203
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJVjUQACgkQ8AA1q7Z/VrLlWwCeLNnh0Ftutl9X7g90ipSD9aJ5
LGcAmwSCBX5Xu2DAcLUSFf4diycd/tYW
=kM1y
-----END PGP SIGNATURE-----

--Apple-Mail=_979229A8-227D-4A4C-9FAF-B89E0C4C6203--

From Fred.L.Templin@boeing.com  Wed Oct  9 10:20:28 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43AF21E80A8; Wed,  9 Oct 2013 10:20:28 -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.000,  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 BTzulXFa5UTY; Wed,  9 Oct 2013 10:20:22 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 2B88A21E805F; Wed,  9 Oct 2013 10:20:17 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99HKDXB003755; Wed, 9 Oct 2013 10:20:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99HK9rY003654 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 9 Oct 2013 10:20:13 -0700
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 9 Oct 2013 10:20:03 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.159]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 10:20:02 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxRAfebc9KTehbEGO6mhunuAlj5nsnKbg
Date: Wed, 9 Oct 2013 17:20:01 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
In-Reply-To: <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 17:20:29 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 09, 2013 9:54 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> >> -----Original Message-----
> >> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >> Sent: Tuesday, October 08, 2013 5:46 PM
> >> To: Ole Troan; Templin, Fred L
> >> Cc: ipv6@ietf.org; ietf@ietf.org
> >> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >> I agree with Ole.
> >
> > How so? A tunnel that crosses a 1280 MTU link MUST fragment
> > in order to satisfy the IPv6 minMTU. If it must fragment, then
> > an MTU-length IPv6 header chain would not fit within the first
> > fragment, and we have opened an attack vector against tunnels.
> > This is not a matter to be agreed or disagreed with - it is
> > a simple fact.
>=20
> right, and RFC2460 has this to say about it:
>=20
>    IPv6 requires that every link in the internet have an MTU of 1280
>    octets or greater.  On any link that cannot convey a 1280-octet
>    packet in one piece, link-specific fragmentation and reassembly must
>    be provided at a layer below IPv6.

Very true. In this case, the "link" is the tunnel and the "link-specific
fragmentation" is IPv6 fragmentation. Which places the first part of an
MTU-length IPv6 header chain in the first fragment and the remainder of
the header chain in the second fragment.

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole

From melinda.shore@gmail.com  Wed Oct  9 10:22:38 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 2180421F9CCC for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  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 2yGCYht8YfzW for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:22:37 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 227BB21F9D3B for <ietf@ietf.org>; Wed,  9 Oct 2013 10:22:35 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so1378390pab.12 for <ietf@ietf.org>; Wed, 09 Oct 2013 10:22: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=TvhVdfCD8LHFxQH4LpKCkag1zjLjv+APOfUW4CQjD+4=; b=y0CMOhowniU122/9H83DoKQxxNwTr0b3bJ1nZd8L8W3ed41XWEAkQcC3I9unDQKbIv ah+m9xBTwWDQs8qkF4BAELFejPZtdwt2E6I49keQCjym3+Lyoz/4WiB0AlFvzgGGLtDk S69KyNTFciYCQ1TA1a3qnhs2kRRna4q3Mgyq4ug0BNnf5qfqz/DwmatLV6bFkgyv8KS0 L3opoytJOQGXWesAKm808yr6yCS/NpW92EobA5YlsAi05HptKCiPnAks8hZyfp9mJnKh 6Y2eGsuwA7L/oFTjdFFWWwXYElz0R9AcGvAtO3wzOC9tPrjLbb1dad6i6pz+/SfUUrzi GlkA==
X-Received: by 10.67.2.4 with SMTP id bk4mr10790822pad.78.1381339354410; Wed, 09 Oct 2013 10:22:34 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id ja5sm47834471pbc.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 10:22:33 -0700 (PDT)
Message-ID: <525590D5.3050606@gmail.com>
Date: Wed, 09 Oct 2013 09:22:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu> <5254E9EF.6010807@gmail.com> <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com>
In-Reply-To: <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 09 Oct 2013 17:22:38 -0000

On 10/9/13 4:35 AM, Ted Lemon wrote:
> On Oct 9, 2013, at 1:30 AM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>>> Rough consensus - An agreement by almost everyone that the
>>> proposed

>> That's a lot like voting, I think.

> It's worse than voting, because it encourages people to invite their
> friends to sway the consensus. 

Excellent point.

Melinda


From otroan@employees.org  Wed Oct  9 10:31:24 2013
Return-Path: <otroan@employees.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 4EA2621E815F; Wed,  9 Oct 2013 10:31:24 -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 Wk4hj0wrUEbF; Wed,  9 Oct 2013 10:31:23 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 9411A21E8149; Wed,  9 Oct 2013 10:31:16 -0700 (PDT)
Received: from dhcp-10-61-106-139.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 2665B6002; Wed,  9 Oct 2013 10:31:13 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 9 Oct 2013 19:31:10 +0200
Message-Id: <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 17:31:24 -0000

--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

>>>> -----Original Message-----
>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>> Sent: Tuesday, October 08, 2013 5:46 PM
>>>> To: Ole Troan; Templin, Fred L
>>>> Cc: ipv6@ietf.org; ietf@ietf.org
>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt>
>>>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>>>=20
>>>> I agree with Ole.
>>>=20
>>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
>>> in order to satisfy the IPv6 minMTU. If it must fragment, then
>>> an MTU-length IPv6 header chain would not fit within the first
>>> fragment, and we have opened an attack vector against tunnels.
>>> This is not a matter to be agreed or disagreed with - it is
>>> a simple fact.
>>=20
>> right, and RFC2460 has this to say about it:
>>=20
>>   IPv6 requires that every link in the internet have an MTU of 1280
>>   octets or greater.  On any link that cannot convey a 1280-octet
>>   packet in one piece, link-specific fragmentation and reassembly =
must
>>   be provided at a layer below IPv6.
>=20
> Very true. In this case, the "link" is the tunnel and the =
"link-specific
> fragmentation" is IPv6 fragmentation. Which places the first part of =
an
> MTU-length IPv6 header chain in the first fragment and the remainder =
of
> the header chain in the second fragment.

indeed. which would violate the MUST in oversized-header-chain.

what do we do?
a) ignore this particular corner case
b) suggest the tunnel head end to drop the packet
c) develop a new tunnel segmentations scheme that doesn't depend on IPv6 =
fragmentation. :-)

cheers,
Ole


--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSVZLeAAoJEFuJXizso86gXzEH+wcd6qhbVkHKDUDLAuPxgiNu
Q2W1lXgeeT3u4bzfEolKEeYRgnOV1nscX94feKCKuQfX2XHaK8IEnQ2R22CkzZMQ
WXjwrRVIjJ2xuSCNJodEJjoRpbv5KhjNP/uEyyj/GE+zKa1eYaQ3aYC7ZPhlLW/p
lLekX6kwMGkHfbCGDWD5HpHgEUEJOUfkWZTxYl45BlZ5BrYZ8BHuzG87QlUFLLrG
+EpE1ch6mTV2hdxuTpRfDRRlgVmgmv6xE+bR5vZ6+psrxCPAzJZVnVBRbj8TGwFF
05cfiMyFlOjzPh5Dt2+jiyPhuCKC+7x7u5GqQpAhV3U8UvhBn5MhrYiCzjPasIo=
=pUDl
-----END PGP SIGNATURE-----

--Apple-Mail=_D6F7732C-6360-4A9A-8B7E-20A0DFE08AEA--

From fluffy@iii.ca  Wed Oct  9 10:33:11 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 A619821E811C; Wed,  9 Oct 2013 10:33: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 og7NnDy-2hbR; Wed,  9 Oct 2013 10:33:06 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8883B21E805F; Wed,  9 Oct 2013 10:33:06 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 50CE722E200; Wed,  9 Oct 2013 13:32:59 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com>
Date: Wed, 9 Oct 2013 11:32:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org" <dhcwg@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, 09 Oct 2013 17:33:11 -0000

On Oct 9, 2013, at 9:47 AM, Ted Lemon <ted.lemon@nominum.com>
 wrote:

> On Oct 9, 2013, at 11:26 AM, Cullen Jennings (fluffy) =
<fluffy@cisco.com> wrote:
>> Help educate me on this a bit - I don't see all the things that get =
requested of DHCP. What are some examples of things where people are =
request FQDN where IP would be better. I think having some real examples =
that have come up would make it easier to see what advice is needed.
>=20
> DNS server IP address.   NTP server IP address.   Router IP address =
(not in DHCPv6, of course).   AFTR IP address.   Basically, network =
infrastructure IP addresses.

Well DNS and Router obviously won't work with FQDN so lets talk about =
NTP for a minute. (and sorry, I don't even know what AFTR IP is). I =
design lots of devices that have to be plugged into a network and just =
start working with no user interaction. Getting the correct time is =
often really useful to have - particularly with synchronization =
protocols.=20

One approach would be to hard code that NTP server name in the the =
product. That is not my preferred approach because stuff goes wrong and =
you end up with things like =
http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse . Another =
approach is for DHCP to provide the NTP server info. I would argue that =
getting a FQDN of the NTP server pool is a better design for DHCP than =
getting an IP address because this allow DNS load balancing across the =
pool and allows the server IP to change over time and still not have =
client failures.=20

You agree that FQDN is would be a better design than IP for NTP ?


>=20
> Bear in mind that the set of services configured by DHCP ought to be =
pretty small=97just things that really are local network infrastructure =
services, not things that are specific to the host and not to the =
network.   It's not even clear to me that NTP ought to be configured by =
DHCP, and indeed in most cases it is not, despite there being an RFC =
describing how to do it.
>=20
> Considering the case of SIP, when you configure SIP I think that's =
probably a configuration that shouldn't change as the phone moves from =
network to network.  =20

Agree - it does not change as phones move network to network. It is uses =
DHCP the first time the phone is plugged in. The whole design is around =
making sure the phone can go from the manufacture to the end user =
without ever being removed from the box or powered up be an admin. The =
admin configures the call control system based on knowledge about the =
phone and which user the phone is going to but the admin does not need =
to touch the phone. When the phone first boots it imprint baby duck =
style on a network to get the configuration information which is =
encrypted with that phones public key. After that the phone use that =
configuration information not the DHCP (unless the phone is factory =
reset). It's actually a lot more complicated than that because security =
relies on replacement of manufacture certificates with the service =
provider certificates to make sure a comprise of the manufactures CA =
only results in service provider not being able to enroll new phones but =
does not compromise security of operational phone network.=20

However, the first time the phone boots, DHCP needs to let the phone =
know who the likely service provider might be. If the phone gets the =
wrong DHCP information from an attacker or wrong network, the phone =
fails to configure but does not suffer MITM attacks. Using DHCP for =
phones has been used by pretty much every IP phone manufactures and most =
enterprise deployments and many residential providers including folks =
ranging from vonage to AT&T take advantage of it.  DHCP greatly reduce =
the deployment costs of setting up VoIP networks.=20

We had a lot of learning from the phone deployments and I expect us to =
use what we learned there for how we do IoT. (I presented a paper on =
this at the IAB workshop on IoT). One of the things we learned the hard =
way was names work better than numbers.=20


> So it shouldn't be configured by DHCP.   In the case where the phone =
happens not to be likely to move from network to network, you could _get =
away_ with using DHCP.   But a solution that would work for phones that =
_do_ move from network to network would also work for phones that do =
not, and that solution would therefore be preferable, particularly as an =
MTI solution, since it addresses all use cases.
>=20
> As I mentioned in the IESG discussion, it is a shame that aggsrv =
didn't become a working group, since it was intended to address this =
specific problem, at least as I understood it.
>=20



From Fred.L.Templin@boeing.com  Wed Oct  9 10:43:05 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F17C21E814A; Wed,  9 Oct 2013 10:43:05 -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 gZVczlVSfcOd; Wed,  9 Oct 2013 10:42:59 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id E290C21E8151; Wed,  9 Oct 2013 10:42:58 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99HgujR023300; Wed, 9 Oct 2013 12:42:56 -0500
Received: from XCH-PHX-409.sw.nos.boeing.com (xch-phx-409.sw.nos.boeing.com [10.57.37.40]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99HgtaJ023293 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 9 Oct 2013 12:42:56 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-PHX-409.sw.nos.boeing.com ([169.254.9.8]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 10:42:55 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxRVXebc9KTehbEGO6mhunuAlj5nsok8A
Date: Wed, 9 Oct 2013 17:42:54 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
In-Reply-To: <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 17:43:05 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 09, 2013 10:31 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> >>>> -----Original Message-----
> >>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >>>> Sent: Tuesday, October 08, 2013 5:46 PM
> >>>> To: Ole Troan; Templin, Fred L
> >>>> Cc: ipv6@ietf.org; ietf@ietf.org
> >>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt>
> >>>> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
> >>>>
> >>>> I agree with Ole.
> >>>
> >>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
> >>> in order to satisfy the IPv6 minMTU. If it must fragment, then
> >>> an MTU-length IPv6 header chain would not fit within the first
> >>> fragment, and we have opened an attack vector against tunnels.
> >>> This is not a matter to be agreed or disagreed with - it is
> >>> a simple fact.
> >>
> >> right, and RFC2460 has this to say about it:
> >>
> >>   IPv6 requires that every link in the internet have an MTU of 1280
> >>   octets or greater.  On any link that cannot convey a 1280-octet
> >>   packet in one piece, link-specific fragmentation and reassembly
> must
> >>   be provided at a layer below IPv6.
> >
> > Very true. In this case, the "link" is the tunnel and the "link-
> specific
> > fragmentation" is IPv6 fragmentation. Which places the first part of
> an
> > MTU-length IPv6 header chain in the first fragment and the remainder
> of
> > the header chain in the second fragment.
>=20
> indeed. which would violate the MUST in oversized-header-chain.
>=20
> what do we do?
> a) ignore this particular corner case
> b) suggest the tunnel head end to drop the packet
> c) develop a new tunnel segmentations scheme that doesn't depend on
> IPv6 fragmentation. :-)

You know I have an interest in alternative c), but that does not
address the issue of splitting the header chain across multiple
fragments. So, my choice is:

d) limit the size of the IPv6 header chain so that the chain will
fit within the first fragment by having the host limit the chain
to the MTU size minus 256 bytes.

Actually, I would be even happier if we just asked the host to limit
the size of the header chain to 1024 bytes regardless of the path MTU.

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole


From Ted.Lemon@nominum.com  Wed Oct  9 10:53:35 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 6A97611E80E2; Wed,  9 Oct 2013 10:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.582
X-Spam-Level: 
X-Spam-Status: No, score=-107.582 tagged_above=-999 required=5 tests=[AWL=1.017, BAYES_00=-2.599, GB_I_LETTER=-2, 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 9pDW2RT3iMge; Wed,  9 Oct 2013 10:53:29 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id E05E221F9FB6; Wed,  9 Oct 2013 10:53:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUlWYFVr9E7wT2rdblFrRe5XEEfQb5mFW@postini.com; Wed, 09 Oct 2013 10:53:25 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 655811B82CE; Wed,  9 Oct 2013 10:53:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 5775B190061; Wed,  9 Oct 2013 10:53:25 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 10:53:25 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca>
Date: Wed, 9 Oct 2013 13:53:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@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, 09 Oct 2013 17:53:35 -0000

On Oct 9, 2013, at 1:32 PM, Cullen Jennings <fluffy@iii.ca> wrote:
> Well DNS and Router obviously won't work with FQDN so lets talk about =
NTP for a minute. (and sorry, I don't even know what AFTR IP is). I =
design lots of devices that have to be plugged into a network and just =
start working with no user interaction. Getting the correct time is =
often really useful to have - particularly with synchronization =
protocols.=20

An AFTR IP address is like a router IP address, but for a particular =
IPv4 transition technology.   Other transition technologies of this sort =
are classic examples of services that make sense to configure with DHCP, =
because they are part of the network infrastructure.

> One approach would be to hard code that NTP server name in the the =
product. That is not my preferred approach because stuff goes wrong and =
you end up with things like =
http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse .

Apple hard-codes the FQDN of a set of NTP servers they control into all =
their products.   I think other OS vendors do as well, but am not clear =
on the details.   The advantage of doing this is that you can then =
authenticate your communication with the NTP server.   If you use DHCP =
to configure your NTP server, you cannot validate your communication =
with your NTP server.   Of course there's a bit of a chicken-and-egg =
problem here in terms of replay attacks and key repudiation, but in =
principle you get more security if you hard code the FQDN of your NTP =
server than if you use DHCP to configure it.

Of course there are cases where this doesn't matter, and DHCP is just =
fine, but I can't think of any other than perhaps a self-setting wall =
clock.

Of course, if a CPE vendor were to hard-code the FQDN of an NTP server =
belonging to someone else into their devices, that would be disastrous.

> Another approach is for DHCP to provide the NTP server info. I would =
argue that getting a FQDN of the NTP server pool is a better design for =
DHCP than getting an IP address because this allow DNS load balancing =
across the pool and allows the server IP to change over time and still =
not have client failures.=20

You'd get the same effect if the DHCP server did the lookup.   I agree =
that if you want to suddenly add an NTP server and need it to be adopted =
in a time frame shorter than your typical lease time, and your DNS TTL =
is shorter than your typical lease time, you will get better service =
using DNS, but there's no clear win here=97this would be a pretty weird =
requirement.

> You agree that FQDN is would be a better design than IP for NTP ?

No.   I think the boxes that need NTP configuration via DHCP are most =
likely constrained devices, and that requiring them to do a DNS lookup =
in addition to the DHCP transaction is unnecessary.   Probably not a =
hugely bad thing, but that depends on the device.   A device with severe =
constraints probably isn't using DHCP anyway.

> Agree - it does not change as phones move network to network. It is =
uses DHCP the first time the phone is plugged in.  The whole design is =
around making sure the phone can go from the manufacture to the end user =
without ever being removed from the box or powered up be an admin. The =
admin configures the call control system based on knowledge about the =
phone and which user the phone is going to but the admin does not need =
to touch the phone. When the phone first boots it imprint baby duck =
style on a network to get the configuration information which is =
encrypted with that phones public key. After that the phone use that =
configuration information not the DHCP (unless the phone is factory =
reset). It's actually a lot more complicated than that because security =
relies on replacement of manufacture certificates with the service =
provider certificates to make sure a comprise of the manufactures CA =
only results in service provider not being able to enroll new phones but =
does not compromise security of operational phone network.=20

>=20
> However, the first time the phone boots, DHCP needs to let the phone =
know who the likely service provider might be. If the phone gets the =
wrong DHCP information from an attacker or wrong network, the phone =
fails to configure but does not suffer MITM attacks. Using DHCP for =
phones has been used by pretty much every IP phone manufactures and most =
enterprise deployments and many residential providers including folks =
ranging from vonage to AT&T take advantage of it.  DHCP greatly reduce =
the deployment costs of setting up VoIP networks.=20
>=20
> We had a lot of learning from the phone deployments and I expect us to =
use what we learned there for how we do IoT. (I presented a paper on =
this at the IAB workshop on IoT). One of the things we learned the hard =
way was names work better than numbers.=20


So what you've done here is to invent a service configuration protocol =
that leverages existing DHCP server infrastructure, uses packets that =
look just like DHCP packets, but is not actually DHCP.   A client that =
behaves in the way you have described is not following RFC3315.   It =
might be following the letter of RFC2131, but that's because RFC2131 has =
a known bug in that it doesn't _require_ clients to use new information =
they get from DHCP servers during lease renewals.

This is not an academic distinction: I've seen all sorts of support =
calls and questions about IP phones from at least one manufacturer, =
because these phones do not follow the DHCP protocol specification, and =
their behavior is surprising to network administrators.   I didn't =
realize until now that this was by design, and not just a bug in the =
implementation.


From jabley@hopcount.ca  Wed Oct  9 11:00:36 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 9890821E8179 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 11:00:35 -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 f4TC8p9+kUez for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 11:00:33 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B4E8D21E8157 for <ietf@ietf.org>; Wed,  9 Oct 2013 11:00:01 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kp14so1417132pab.6 for <ietf@ietf.org>; Wed, 09 Oct 2013 11:00:00 -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; bh=ijwhYAiyrBwWKq0mQTB/5PzwTsyn0aWjUbDqdU+0tpY=; b=opHDIugjhu7LIqsaxkwqRfK97f5uB3Pr2q0yqGWJs2Z3MU6cG+KtulyBS2iOhTDJ3N qa7/aoAwxZwWZRA8uE89wPUq7eUIncuR5wyqnycKDCjG6FP4bXEMiMxmLUd70CcztqYD 5u8K/yeoLPW4W2HQteE/sZ2dp6ywQHIkb3Z0Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ijwhYAiyrBwWKq0mQTB/5PzwTsyn0aWjUbDqdU+0tpY=; b=MxdUz0B6MUqewbLwXj4SZdbHLEPnsp21IyexmDjD+xfQr6u6ift0bdRTF40oMBVRaF NVA3PtHbRgACpyGOZpJ2FubYyfPTmBCnQQ0kU5DZrBm0SA21Y+fO9ZGTC+4wUQO6qB9L mdh4p2NRsNbdaGzt1axLuNy85owbVG2j1J+cQ/JjQKDthxTHVZbsuA6zOT/Wi0lLw9cN LOvnP3oxafKUAWwhCzOH9TFcPPALtfGbQ1upUKYcfMAE9c6DAcXii2lxSkuvQpedF6uS G/EZC6MGpcRnQXA1K1pueBYTqgHLywuOnkBs82822ACfM1DMX+i4WEJymuvlsce8ceUq JeYg==
X-Gm-Message-State: ALoCoQnYt+hTxuQVwOCBsLCaZChwizyAJC3u1z5xT5PHsBNZWeJDVhOS/maLLNcTc+NZtJ8AbBZQ
X-Received: by 10.66.170.168 with SMTP id an8mr11079387pac.58.1381341600303; Wed, 09 Oct 2013 11:00:00 -0700 (PDT)
Received: from ?IPv6:2620::ce0:104:a8af:1749:23a8:ed08? ([2620:0:ce0:104:a8af:1749:23a8:ed08]) by mx.google.com with ESMTPSA id tz3sm47980277pbc.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 10:59:59 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com>
Date: Wed, 9 Oct 2013 10:59:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EF36A1D-8A3E-40DB-B2A3-C8D8A5D451D8@hopcount.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Cullen Jennings <fluffy@iii.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: Wed, 09 Oct 2013 18:00:36 -0000

On 2013-10-09, at 10:53, Ted Lemon <ted.lemon@nominum.com> wrote:

> Of course there are cases where this doesn't matter, and DHCP is just =
fine, but I can't think of any other than perhaps a self-setting wall =
clock.

DNSSEC validation imposes a requirement for clock sync (to the accuracy =
reasonably required to consider signature inception and expiry times). =
There is a possible future in which such validation takes place on end =
hosts, rather than intermediate resolvers. (We may wind up somewhere =
else, but there are certainly people who think that is the Right Way).

In that sense any device that needs to look up names in the DNS has a =
potential requirement for time sync.

Of course even the wall clock you imagine might have a vendor who is =
capable of running their own array of time servers as (e.g.) Apple does, =
but it seems reasonable to imagine that there will be people who are not =
in that position, and since I agree with you when you say:

> Of course, if a CPE vendor were to hard-code the FQDN of an NTP server =
belonging to someone else into their devices, that would be disastrous.

it seems to me that there's a plausible use case for a DHCP client to =
receive direction on what servers to chime against.


Joe


From adrian@olddog.co.uk  Wed Oct  9 11:09: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 BB50821F9EA2; Wed,  9 Oct 2013 11:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  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 21jw24ndP5i7; Wed,  9 Oct 2013 11:09:31 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 71C6D21E8178; Wed,  9 Oct 2013 11:07:46 -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 r99I7WFZ018319;  Wed, 9 Oct 2013 19:07:32 +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 r99I7VMi018301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 Oct 2013 19:07:32 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Chris Griffiths'" <cgriffiths@gmail.com>, "'SM'" <sm@resistor.net>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<6.2.5.6.2.20130924135945.0d561cd0@resistor.net>	<9824D1EA-EDAA-4BFB-A9D0-A0AFEAE546CD@gmail.com> <C8BCDFAF-EBAC-4D0F-AD80-8320F22B9FF3@gmail.com>
In-Reply-To: <C8BCDFAF-EBAC-4D0F-AD80-8320F22B9FF3@gmail.com>
Subject: RE: Community Feedback:  IETF Trust Agreement Issues
Date: Wed, 9 Oct 2013 19:07:31 +0100
Message-ID: <07f701cec51a$6cc16bc0$46444340$@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: AQIVyLD2so6lMhMJRkYiESOWmefQhgIqgsPRAWFYocIC1P+ZK5krl9fA
Content-Language: en-gb
Cc: 'Trustees Trustees' <trustees@ietf.org>, 'Nevil Brownlee' <n.brownlee@auckland.ac.nz>, 'John C Klensin' <klensin@jck.com>, 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: Wed, 09 Oct 2013 18:09:35 -0000

Hi Chris,

I have become confused between the permission necessary to republish the Tao,
and the request to republish under a Creative Commons license.

Can I try to clarify.

Do we or do we not grant permission for others to publish the Tao and the
translations of the Tao under section 3c of the TLP at
http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf ?

Thanks and sorry for dragging this on.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Chris
> Griffiths
> Sent: 09 October 2013 15:44
> To: SM
> Cc: Trustees Trustees; John C Klensin; Nevil Brownlee; ietf@ietf.org list
> Subject: Re: Community Feedback: IETF Trust Agreement Issues
> 
> On Sep 26, 2013, at 3:12 PM, Chris Griffiths <cgriffiths@gmail.com> wrote:
> 
> > On Sep 24, 2013, at 6:11 PM, SM <sm@resistor.net> wrote:
> >
> >> At 23:48 02-08-2013, Chris Griffiths wrote:
> >>> Issue 1
> >>>
> >>> We have recently been asked permission to republish the TAO with a
> creative commons license, but according to counsel, the current trust
agreement
> does not give the trustees the rights to do this.
> >>>
> >>> - Without specific language being added to the trust agreement, we cannot
> grant these types of requests.
> >>> - The current open request for a creative commons license from 6/18/2013
> cannot be completed.
> >>
> >> In term of "outgoing" rights the Independent Submission Stream is different
> from the IETF Stream.  The draft version of the Tao might offer a path
forward.
> Would it be possible to have it submitted through the Independent Submission
> Stream and use that version and changes to address the above request?
> >> I haven't looked into the process stuff.  It might be possible [1] to sort
that out
> once the legal hurdles are settled.
> 
> SM,
> 
> I wanted to follow-up with this specific request and advise that based on
> discussions with legal council and feedback from the Trustees that the current
> rules don't allow granting permission to republish this using the Independent
> Submission Stream, nor to grant a Community Commons license.  At this time we
> also do not have community consensus to prioritize a change to the rules in
order
> to meet this request.
> 
> Thank you
> 
> Chris Griffiths



From Ted.Lemon@nominum.com  Wed Oct  9 11:11: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 6F78F21E805F; Wed,  9 Oct 2013 11:11:37 -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 mgq-QzsJeZxX; Wed,  9 Oct 2013 11:11:30 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 27B0E21F9A71; Wed,  9 Oct 2013 11:11:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUlWcRG13RmhvmCFbOTlsOspX8LOB6ZWm@postini.com; Wed, 09 Oct 2013 11:11: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 9E4031B82D5; Wed,  9 Oct 2013 11:11:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 98716190061; Wed,  9 Oct 2013 11:11:16 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 11:11:16 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <0EF36A1D-8A3E-40DB-B2A3-C8D8A5D451D8@hopcount.ca>
Date: Wed, 9 Oct 2013 14:11:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <E5439F1D-2710-44D8-8827-9C926C5915AB@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <0EF36A1D-8A3E-40DB-B2A3-C8D8A5D451D8@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Cullen Jennings <fluffy@iii.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: Wed, 09 Oct 2013 18:11:37 -0000

On Oct 9, 2013, at 1:59 PM, Joe Abley <jabley@hopcount.ca> wrote:
> DNSSEC validation imposes a requirement for clock sync (to the =
accuracy reasonably required to consider signature inception and expiry =
times). There is a possible future in which such validation takes place =
on end hosts, rather than intermediate resolvers. (We may wind up =
somewhere else, but there are certainly people who think that is the =
Right Way).

Sure.   Including me.

> In that sense any device that needs to look up names in the DNS has a =
potential requirement for time sync.

Yes, definitely.

> Of course even the wall clock you imagine might have a vendor who is =
capable of running their own array of time servers as (e.g.) Apple does, =
but it seems reasonable to imagine that there will be people who are not =
in that position, and since I agree with you when you say:
>=20
>> Of course, if a CPE vendor were to hard-code the FQDN of an NTP =
server belonging to someone else into their devices, that would be =
disastrous.
>=20
> it seems to me that there's a plausible use case for a DHCP client to =
receive direction on what servers to chime against.

Yup.   There's an equally plausible use case for distributing DNSSEC =
root keys using DHCP, so that the DHCP client has a current copy of the =
keys.   This totally solves the key rollover problem!

:)

Of course, the situations are not precisely analogous, but the point is =
that just because DHCP could be conveniently used to suit some purpose, =
does not mean that it _should_ be used to suit that purpose.  I think =
reasonable people can differ about configuring NTP over DHCP, but it =
really does depend on how you are using NTP.   I think the main =
justification for using DHCP to configure NTP is in fact that it is =
expedient, even though it's not secure.


From linda.dunbar@huawei.com  Wed Oct  9 11:41:09 2013
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72B621F9D62 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 11:41:07 -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 zEQaYGpZyHtE for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 11:40:58 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D10A621F9A16 for <ietf@ietf.org>; Wed,  9 Oct 2013 11:40:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYX48641; Wed, 09 Oct 2013 18:40:54 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 9 Oct 2013 19:40:18 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Wed, 9 Oct 2013 19:40:51 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.209]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.03.0146.000; Wed, 9 Oct 2013 11:40:45 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "George, Wes" <wesley.george@twcable.com>, IETF Discussion <ietf@ietf.org>
Subject: RE: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service	Provider) to	Informational RFC
Thread-Topic: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined	Networking: A Perspective From Within A	Service	Provider) to	Informational RFC
Thread-Index: AQHOxPp19lWAP+TdNkWZQwasso6e/JnsrhGA
Date: Wed, 9 Oct 2013 18:40:45 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645BD5357@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645BD4A63@dfweml509-mbx.china.huawei.com> <2671C6CDFBB59E47B64C10B3E0BD5923043C7557D4@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923043C7557D4@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.245.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Oct 2013 18:41:09 -0000

It is true that SDN depends on automation.=20

IMHO, "Automation" is a much bigger area than SDN.=20

When you look at Amazon EC2 graphic interface, you can click X number of VM=
s, and create any kind of virtual networks among them, along with a set of =
service functions to dictate inter-subnet communication. That is a "Softwar=
e defined network".=20

Linda

 =20

> -----Original Message-----
> From: George, Wes [mailto:wesley.george@twcable.com]
> Sent: Wednesday, October 09, 2013 9:18 AM
> To: Linda Dunbar; IETF Discussion
> Subject: RE: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt>
> (Software-Defined Networking: A Perspective From Within A Service
> Provider) to Informational RFC
>=20
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
> > Linda Dunbar
>=20
> >
> > - We all understand the challenges of "Full Automation". However, the
> > SDN and Full automation are two separate angles to Carrier networks.
> I
> > find the Section 4.1  "Implications of full automation" actually de-
> > rails the focus of the draft on SDN.
>=20
> [WEG] I strongly disagree. First, "we all understand..." is an
> overgeneralization, and a dangerous and grossly inaccurate one at that.
> Lots of SDN vendors have repeatedly demonstrated to me how little they
> actually understand about this problem. It's not a new problem by any
> means, but there's a really significant amount of hand-waving going on
> around the complexities of actually doing what they're saying is
> possible through the "magic" of SDN, when few have demonstrated how the
> abstract concept "SDN" actually makes solving this problem easier. The
> reality is that SDN and automation are inextricably linked. The next to
> last sentence in section 2.3 reinforces this, and I believe that 4.1 is
> absolutely appropriate for this draft. A truly software-defined network
> is an automated one, and any discussion of an operator's perspective on
> SDN is going to need to consider the same challenges that have been
> present in prior attempts to better automate network management,
> provisioning, and control. There are two models for managing a network
> like this, one that is fully automated, meaning that it is quite a lot
> more complex and susceptible to "ghost in the machine" problems, the
> other which has a human making most of the important decisions and then
> dictating those to the network. Even the latter model requires a
> significant amount of automation to execute what the human has decided
> should be done.
> The things covered in section 4.1 mirrors a lot of the discussion that
> I have had both internally and with other operators around the
> challenges of separating the hype of SDN from the actual benefit, and
> in selling this model to operations folks who are skeptical of ceding
> control to a set of computer logic.
>=20
> Wes George
>=20
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
> to copyright belonging to Time Warner Cable. This E-mail is intended
> solely for the use of the individual or entity to which it is addressed.
> If you are not the intended recipient of this E-mail, you are hereby
> notified that any dissemination, distribution, copying, or action taken
> in relation to the contents of and attachments to this E-mail is
> strictly prohibited and may be unlawful. If you have received this E-
> mail in error, please notify the sender immediately and permanently
> delete the original and any copy of this E-mail and any printout.

From arturo.servin@gmail.com  Wed Oct  9 12:06:21 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 A419521E8185 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level: 
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, 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 MjxghVaBXVtK for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:06:21 -0700 (PDT)
Received: from mail-yh0-x231.google.com (mail-yh0-x231.google.com [IPv6:2607:f8b0:4002:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2AB21E8190 for <ietf@ietf.org>; Wed,  9 Oct 2013 12:05:38 -0700 (PDT)
Received: by mail-yh0-f49.google.com with SMTP id a41so335802yho.8 for <ietf@ietf.org>; Wed, 09 Oct 2013 12:05:37 -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=9JVi6adzayHCsDJvMjJ5SLCADGKDq2xmF2w/yjqD3Ms=; b=BRBU2ubi2RbYACvKmVeocJsf0FUV6zKP5oG8+kr5iqts/JeoaU0iFoe1XnfN5DRbAy 7jlDTA5X1I2aHJA07MKlW0JCqeKS0ASitCMhaeS6DDDa4Uhj2xhWTutxrdnmOukK3Zp4 wP0Hacg966VGeGQiD5MpxEE2hWP0P0BAhRVerSZAtGuWb3VKq//pxSqSN1pJWg15zIT5 sHBXfS32E7kmROlCUt3PvDnn2vwFYuojweB+8AsB3HSSfOXNJ0zuVdDKQ88ODkKkRRRk UVpOFgMoJ0S9Q3Enq5xsDYj8VCuEitZF4Ll8lIEXbuc6puW0cMge6IXgiAHTgrYmhjkF oOYg==
X-Received: by 10.236.89.71 with SMTP id b47mr1872981yhf.83.1381345537671; Wed, 09 Oct 2013 12:05:37 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:85a2:4d29:b62a:aacb]) by mx.google.com with ESMTPSA id c44sm63066849yho.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 12:05:36 -0700 (PDT)
Message-ID: <5255A905.10700@gmail.com>
Date: Wed, 09 Oct 2013 17:05:41 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Montevideo statement
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com>
In-Reply-To: <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.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, 09 Oct 2013 19:06:21 -0000

	We appointed our leaders, we have to trust them. They had to do a call,
an important one and they made it.

	I support what they did, that is what we chose them for, to represent
us and be our voice. We cannot expect that they ask our opinion for
every decision they made, that is not practical or possible in today's
world. Sometimes like in this statement, we need to trust in their good
judgment.

My 20 cents,
as

	
	
	

On 10/9/13 12:00 PM, John C Klensin wrote:
> 
> 
> --On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan
> <ajs@anvilwalrusden.com> wrote:
> 
>> ...
>> That does not say that the IAB has issued a statement.  On the
>> contrary, the IAB did not issue a statement.  I think the
>> difference between some individuals issuing a statement in
>> their capacity as chairs and CEOs and so on, and the body for
>> which they are chair or CEO or so on issuing a similar
>> statement, is an important one.  We ought to attend to it.
>>
>> Please note that this message is not in any way a comment on
>> such leadership meetings.  In addition, for the purposes of
>> this discussion I refuse either to affirm or deny concurrence
>> in the IAB chair's statement.  I merely request that we, all
>> of us, attend to the difference between "the IAB Chair says"
>> and "the IAB says".
> 
> Andrew,
> 
> While I agree that the difference is important for us to note,
> this is a press release.  It would be naive at best to assume
> that its intended audience would look at it and say "Ah. A bunch
> of people with leadership roles in important Internet
> organizations happened to be in the same place and decided to
> make a statement in their individual capacities".  Not only does
> it not read that way, but there are conventions for delivering
> the "individual capacity" message, including prominent use of
> phrases like "for identification only". 
> 
> Independent of how I feel about the content of this particular
> statement,  if the community either doesn't like the message or
> doesn't like this style of doing things, I think that needs to
> be discussed and made clear.  That includes not only at the
> level of preferences about community consultation but about
> whether, in in the judgment of the relevant people, there is
> insufficient time to consult the community, no statement should
> be made at all.
> 
> Especially from the perspective of having been in the
> sometimes-uncomfortable position of IAB Chair, I don't think IAB
> members can disclaim responsibility in a situation like this.
> Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at
> the pleasure and convenience of the IAB.  If you and your
> colleagues are not prepared to share responsibility for
> statements (or other actions) the IAB Chair makes that involve
> that affiliation, then you are responsible for taking whatever
> actions are required to be sure that only those actions are
> taken for which you are willing to share responsibility.   Just
> as you have done, I want to stress that I'm not recommending any
> action here, only that IAB members don't get to disclaim
> responsibility made by people whose relationship with the IAB is
> the reason why that are, e.g., part of a particular letter or
> statement.
> 
>       john
> 

From ajs@anvilwalrusden.com  Wed Oct  9 12:28:01 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 AD28A21E8190 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:27:59 -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 SQR9sUKJJmxr for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:27:44 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 669D221E81B8 for <ietf@ietf.org>; Wed,  9 Oct 2013 12:27:17 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-220-111.meetings.nanog.org [199.187.220.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id EC92B8A031 for <ietf@ietf.org>; Wed,  9 Oct 2013 19:27:15 +0000 (UTC)
Date: Wed, 9 Oct 2013 15:27:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: leader statements (was: Montevideo statement)
Message-ID: <20131009192715.GG49231@mx1.yitter.info>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E003D3DC4E4B3208CF14E8E0@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: Wed, 09 Oct 2013 19:28:01 -0000

Dear colleagues,

Once again, I'm speaking only for myself.  I think there is an
important matter here for the IETF community to think about,
particularly as the Nomcom is _right now_ seeking nominees for open
positions.  I want to be very careful to emphasise that I do not
intend to specify a preference for how things should go.  This is
because I am currently the IAB's liaison to the nomcom, and I
therefore think it's important to avoid expressing my personal
preferences in this case.  But I encourage people to talk to the
nomcom about their views on this general topic.  (Also, if you have
views about this, you might want to consider standing for an open IESG
or IAB position.)

So,

On Wed, Oct 09, 2013 at 10:00:39AM -0400, John C Klensin wrote:
> this is a press release.  It would be naive at best to assume
> that its intended audience would look at it and say "Ah. A bunch
> of people with leadership roles in important Internet
> organizations happened to be in the same place and decided to
> make a statement in their individual capacities".  Not only does
> it not read that way, but there are conventions for delivering
> the "individual capacity" message, including prominent use of
> phrases like "for identification only". 

I don't think that "individual capacity" is what the identified people
were doing at that meeting.  They went to the meeting _as the chairs_
of the IAB and the IETF.  Therefore, it is quite appropriate that they
(but they alone) sign the statement in their capacity as chairs.  And
under those circumstances, I don't actually see what feedback about
the statement could be appropriate.  They did something, as
chairs. They make a statement, as chairs, about it.  Someone else's
thoughts about what the meeting should have been about are certainly
appropriate topics for discussion; but I don't see why those thoughts
should affect the contents of a statement about the actual meeting
that happened.

Now, there is indeed a possible issue, and that is that these chairs
were attending a "chief officer"-type meeting: there were CEOs and so
on, and (presumably by analogy) the chairs got invited to represent
the organizations of which they are chairs.  John is quite right that
people unfamiliar with the way the IETF or IAB work might interpret
the statement along the lines of, "The CEO of the IETF said that the
IETF subscribes to some view."  Normally, the leader of an
organization can direct that organization to some end; the Chair is
the leader; therefore, the Chair can direct the organization.  Of
course, that's not how we operate (this is, I think, at the bottom of
this very discussion).  But others might get that impression.

What I am not sure about is whether people are willing to accept the
chairs acting in that sort of "leader of organization" role.  If we do
accept it, then I think as a consequence some communications will
happen without consultation.  For a CEO is not going to agree to issue
a joint communiquĂ© with someone who has to go negotiate the contents
of that communiquĂ© (and negotiate those contents in public).  If we do
not accept it, then we must face the fact that there will be meetings
where the IETF or IAB just isn't in the room, because we'll have
instructed the chairs not to act in that capacity.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Wed Oct  9 12:31:38 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 CFDAC21E8190 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:31: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 CD3+f7a2RI6W for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:31: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 4B5E421E8176 for <ietf@ietf.org>; Wed,  9 Oct 2013 12:31:36 -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 r99JVT5D015909; Wed, 9 Oct 2013 12:31:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381347094; bh=AxLF9KFN6uLh1Ahm6gDPMzvW/4GZ5zwisa/tcgxFlsA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mDsChtjsYkxA11iW383TCBdtGk35mChyC9MlZWYM8mOoImq5kJJB2Wwj/C3nANITS 92eikrkbnGYegXdqiiUeQbRKlaF5LRbPt59nDD+VVk0Vdoe3gpFq8W8payMtQANab8 hmIhQZEepxCJi/f+StEBjYd6XG7gmSN72kqeCTE4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381347094; i=@resistor.net; bh=AxLF9KFN6uLh1Ahm6gDPMzvW/4GZ5zwisa/tcgxFlsA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=o0Ap6a8ksBIM/kQcvwYrRSGrNuopn2UEwfv2AB5IfUKUdLFXSfwL9PwvlP4pCBeqg BXgEso7nt0YRLIBX2AYQM2yjREZv/OfVbNbJ4FLCXTiAUJFr03KbQ0KPPj2kle4xo2 bnQLysNAi0HqzPk6w1SWwrnQklBwmqwQTSJig6OQ=
Message-Id: <6.2.5.6.2.20131009104030.0d2de770@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 Oct 2013 12:27:14 -0700
To: Russ Housley <housley@vigilsec.com>
From: SM <sm@resistor.net>
Subject: Re: Montevideo statement
In-Reply-To: <63642766-94C3-4A0A-A5D9-6722E89FBFC4@vigilsec.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <63642766-94C3-4A0A-A5D9-6722E89FBFC4@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
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, 09 Oct 2013 19:31:38 -0000

Hi Russ,
At 09:24 09-10-2013, Russ Housley wrote:
>This is a statement about what happened at a=20
>meeting.  Discussion would not change what=20
>happened at the meeting.  Making the statement=20
>very public allows a good discussion of what=20
>should happen next.  I look forward to that discussion.

One of the organizations mentioned in the=20
statement commented about it as follows:

   "Internet/Web Organizations Issue Montevideo Statement on the Future
    of Internet Cooperation"

   "The leaders of organizations responsible for coordination of the=
 Internet
    technical infrastructure globally met in Montevideo, Uruguay, to=
 consider
    current issues affecting the future of the Internet. They issued today
    a Montevideo Statement on the Future of Internet Cooperation, signed by
    African Network Information Center (AFRINIC), American Registry for
    Internet Numbers (ARIN), Asia-Pacific Network Information Centre=
 (APNIC),
    Internet Architecture Board (IAB), Internet Corporation for Assigned=
 Names
    and Numbers (ICANN), Internet Engineering Task Force (IETF), Internet
    Society (ISOC), Latin America and Caribbean Internet Addresses Registry
    (LACNIC), R=E9seaux IP Europ=E9ens Network=20
Coordination Centre (RIPE NCC), W3C."

One of the signatories of the statement mentioned=20
(if I understood correctly) that the statement was from the organizations.

Is the statement an IAB statement or a statement=20
from the IAB Chair?  Please note that I have read=20
the message from Andrew (see=20
http://www.ietf.org/mail-archive/web/ietf/current/msg82926.html ).

I agree that discussion would not change what=20
happened.  I don't think that it is a good idea=20
to have a "fait accompli" [1] for the IETF=20
Community to discuss about.  It has been said=20
that "we reject: kings, presidents and=20
voting".  The statement creates the perception=20
that the leaders of the Internet Architecture=20
Board and the Internet Engineering Task Force are=20
like kings or presidents. The Internet=20
Architecture Board is supposed to be based on=20
collegial responsibility.  I read that as meaning=20
not to have statements which commits the Internet=20
Architecture Board to a course of action without=20
some form of approval from the members of that=20
Board.  Obviously, some form of approval would=20
not have to be sought if the course of action has been discussed previously.

   "The [IAB] board discussed the issue of a joint OpenStand statement or
    an IAB specific statement. Many members were against a closed review
    period for such a statement and would prefer to have an open discussion
    period in the IETF if such a statement was required."

There is a comment on the www.iab.org web site=20
about "allegations of interference by some=20
governments in the standards development process"=20
and a link to an "OpenStand" statement.  It seems=20
that there was a closed review period for the joint OpenStand statement.

I don't think that it is possible to build trust=20
if openness and transparency are in name only.  I=20
am not enthusiastic about having a discussion=20
which does not materially affect the outcome.

Regards,
-sm

1. something that has been done and cannot be changed.=20


From housley@vigilsec.com  Wed Oct  9 12:43:51 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 7948621E819A for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 J5oVvpzUf+3y for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 12:43:46 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8A83521E8188 for <ietf@ietf.org>; Wed,  9 Oct 2013 12:43:42 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 57661F24094; Wed,  9 Oct 2013 15:44:04 -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 2b2TAAIJpNEn; Wed,  9 Oct 2013 15:43:13 -0400 (EDT)
Received: from [192.168.2.107] (pool-71-191-197-233.washdc.fios.verizon.net [71.191.197.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id AC553F24093; Wed,  9 Oct 2013 15:44:02 -0400 (EDT)
Subject: Re: Montevideo statement
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=iso-8859-1
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20131009104030.0d2de770@resistor.net>
Date: Wed, 9 Oct 2013 15:43:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E81A99FF-E8DC-4103-9A9A-F81FBED29780@vigilsec.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <63642766-94C3-4A0A-A5D9-6722E89FBFC4@vigilsec.com> <6.2.5.6.2.20131009104030.0d2de770@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
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, 09 Oct 2013 19:43:51 -0000

SM:

Each of these leaders comes from a different organization, and each of =
these organizations grants their leaders different degrees of autonomy.  =
So, the amount of coordination that was done differs for each. In all =
cases, there was one business day to do the coordination.

In my case, I shared the draft statement with the whole IAB, stating my =
intention to include my name and role at the bottom of the statement.  I =
asked for no wordsmithing because ten organizations were simultaneously =
handling the statement in their own way.

Russ


On Oct 9, 2013, at 3:27 PM, SM wrote:

> Hi Russ,
> At 09:24 09-10-2013, Russ Housley wrote:
>> This is a statement about what happened at a meeting.  Discussion =
would not change what happened at the meeting.  Making the statement =
very public allows a good discussion of what should happen next.  I look =
forward to that discussion.
>=20
> One of the organizations mentioned in the statement commented about it =
as follows:
>=20
>  "Internet/Web Organizations Issue Montevideo Statement on the Future
>   of Internet Cooperation"
>=20
>  "The leaders of organizations responsible for coordination of the =
Internet
>   technical infrastructure globally met in Montevideo, Uruguay, to =
consider
>   current issues affecting the future of the Internet. They issued =
today
>   a Montevideo Statement on the Future of Internet Cooperation, signed =
by
>   African Network Information Center (AFRINIC), American Registry for
>   Internet Numbers (ARIN), Asia-Pacific Network Information Centre =
(APNIC),
>   Internet Architecture Board (IAB), Internet Corporation for Assigned =
Names
>   and Numbers (ICANN), Internet Engineering Task Force (IETF), =
Internet
>   Society (ISOC), Latin America and Caribbean Internet Addresses =
Registry
>   (LACNIC), R=E9seaux IP Europ=E9ens Network Coordination Centre (RIPE =
NCC), W3C."
>=20
> One of the signatories of the statement mentioned (if I understood =
correctly) that the statement was from the organizations.
>=20
> Is the statement an IAB statement or a statement from the IAB Chair?  =
Please note that I have read the message from Andrew (see =
http://www.ietf.org/mail-archive/web/ietf/current/msg82926.html ).
>=20
> I agree that discussion would not change what happened.  I don't think =
that it is a good idea to have a "fait accompli" [1] for the IETF =
Community to discuss about.  It has been said that "we reject: kings, =
presidents and voting".  The statement creates the perception that the =
leaders of the Internet Architecture Board and the Internet Engineering =
Task Force are like kings or presidents. The Internet Architecture Board =
is supposed to be based on collegial responsibility.  I read that as =
meaning not to have statements which commits the Internet Architecture =
Board to a course of action without some form of approval from the =
members of that Board.  Obviously, some form of approval would not have =
to be sought if the course of action has been discussed previously.
>=20
>  "The [IAB] board discussed the issue of a joint OpenStand statement =
or
>   an IAB specific statement. Many members were against a closed review
>   period for such a statement and would prefer to have an open =
discussion
>   period in the IETF if such a statement was required."
>=20
> There is a comment on the www.iab.org web site about "allegations of =
interference by some governments in the standards development process" =
and a link to an "OpenStand" statement.  It seems that there was a =
closed review period for the joint OpenStand statement.
>=20
> I don't think that it is possible to build trust if openness and =
transparency are in name only.  I am not enthusiastic about having a =
discussion which does not materially affect the outcome.
>=20
> Regards,
> -sm
>=20
> 1. something that has been done and cannot be changed.=20


From brian.e.carpenter@gmail.com  Wed Oct  9 13:02:48 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 B121121E8186 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 dWMN1QwQBE-o for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:02:39 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9821E8099 for <ietf@ietf.org>; Wed,  9 Oct 2013 13:02:21 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w10so1450248pde.23 for <ietf@ietf.org>; Wed, 09 Oct 2013 13:02: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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YBkccO6ChomD3hZR9T+1d5G1K21Ekf/8ygLFx2Whnws=; b=SyFaJZQx5TngoXRxy7Wk3mfjaCJGKqIR0FSd+Y03DYtRXg2af0wY5lIq9qpztpiaRy 8frc2xo7J04za+yPWz0cbpHUeJWtdMFYQ2EebjwwaHM9uYLDCTcu9ySe+nzo+PblcJRs 9Isr7rJ9Xdkriczsmz5CQBuMJ1v4QJvaOF/lY8AD2iD4cyVyLFbpkoTGjdvlN/vaP9BZ IBbehSVQIDxMXzRP0drgB8U51y0qfwL8jk7sE73S7tFEGnIio55TydGV7upyIjLuIvdg CC6JNuVosCdCTW6r4Mip82r0yO/xuziCo5gV1amfelkRfoA3u53OS4lZb7/Lz6G3/wva bpVw==
X-Received: by 10.66.165.106 with SMTP id yx10mr11124813pab.159.1381348931994;  Wed, 09 Oct 2013 13:02:11 -0700 (PDT)
Received: from [192.168.178.20] (103.197.69.111.dynamic.snap.net.nz. [111.69.197.103]) by mx.google.com with ESMTPSA id og5sm48427111pbb.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 13:02:11 -0700 (PDT)
Message-ID: <5255B647.4090103@gmail.com>
Date: Thu, 10 Oct 2013 09:02:15 +1300
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: leader statements
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info>
In-Reply-To: <20131009192715.GG49231@mx1.yitter.info>
Content-Type: text/plain; charset=UTF-8
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: Wed, 09 Oct 2013 20:02:48 -0000

On 10/10/2013 08:27, Andrew Sullivan wrote:
=2E..
> What I am not sure about is whether people are willing to accept the
> chairs acting in that sort of "leader of organization" role.  If we do
> accept it, then I think as a consequence some communications will
> happen without consultation.  For a CEO is not going to agree to issue
> a joint communiqu=C3=A9 with someone who has to go negotiate the conten=
ts
> of that communiqu=C3=A9 (and negotiate those contents in public).  If w=
e do
> not accept it, then we must face the fact that there will be meetings
> where the IETF or IAB just isn't in the room, because we'll have
> instructed the chairs not to act in that capacity.

I've been there in the past, as IAB Chair, ISOC Board Chairman, and IETF =
Chair.

Either we trust our current and future chairs, on certain occasions,
to speak in our name without there being a discursive debate in advance,
or we will have no voice on those occasions.

If there was a pattern of I* chairs subscribing to statements that the
relevant community clearly found quite outrageous, there might be an
argument for having no voice.

I suggest that there is no such pattern. There may be quibbles over
wording sometimes, but that is inevitable when several different
stakeholder organisations have to agree on wording. The wording is
inevitably a compromise; it can't be otherwise.

It's perfectly reasonable to ask our chairs to invite debate in
advance when that is possible; but in many of these cases, it
simply isn't. It's also perfectly reasonable that people should comment
on the wording even after it's set in stone; that helps us to do better
next time.

If we nominate good candidates for our leadership positions, and send
thoughtful comments to the NomCom (and the IESG and IAB for their
nominating duties), we won't get leaders who put their names to
anything outrageous.

We should trust our chairs to act as figureheads and leaders towards
the outside world.

   Brian Carpenter


From abdussalambaryun@gmail.com  Wed Oct  9 13:15:52 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 A3A6421F9FEE for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:15:52 -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 Q9tP-z9xbXmM for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:15:51 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BF3AB21F970E for <ietf@ietf.org>; Wed,  9 Oct 2013 13:15:51 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y13so1467162pdi.33 for <ietf@ietf.org>; Wed, 09 Oct 2013 13:15: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=k9NULAQy1jfvT4vt2zQSPMI0ihBoGIccLYy0vndFbkY=; b=NNmWMcpN0lv+0tURu7C7KXyIdQKn7Utamq85gbOc65/4ELXLtZ24Rsuj5wbdULwO/0 N0EAdsv7akWS3PlMDS1EvxgIT/WrscaftR5rBySmK13ml7tenoDbne3umypWn7bbOZde 7nsVxirFfDXbdS8dZBTJXedLX7XAXOSBy0d9FBT5Y/dc+i7OqOCj5/FLkUlFJCiZVb35 qc77fWwSz8E+3s83H3hk+OYRK2nEDA+8apOMN9pjig++FI+XgJBEBXpAK9vECNvxOFGf aJJbikvZA11rXs5j4JsOpjCdML8YcPsGSSAnTHnt/UH+/tNdh+c8nmwpbHOTnhN2AE1K Xkgg==
MIME-Version: 1.0
X-Received: by 10.66.162.167 with SMTP id yb7mr11662863pab.16.1381349746995; Wed, 09 Oct 2013 13:15:46 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 9 Oct 2013 13:15:46 -0700 (PDT)
In-Reply-To: <5255A905.10700@gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <5255A905.10700@gmail.com>
Date: Wed, 9 Oct 2013 21:15:46 +0100
Message-ID: <CADnDZ8-vaM64D9T79XgCzgby-6TEmgsPeEvA6XfZwwUCHtX1fA@mail.gmail.com>
Subject: Re: Montevideo statement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacbe70faf5cc04e8548cd3
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, 09 Oct 2013 20:15:53 -0000

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

I agree to appoint leader under clear procedures, so I am not sure of
representing without procedure is authorised in ietf, but I trust that ietf
leaders do practice procedure, but not sure if discussion meant that there
was something missing in this statement practice.

AB

On Wednesday, October 9, 2013, Arturo Servin wrote:

>
>         We appointed our leaders, we have to trust them. They had to do a
> call,
> an important one and they made it.
>
>         I support what they did, that is what we chose them for, to
> represent
> us and be our voice. We cannot expect that they ask our opinion for
> every decision they made, that is not practical or possible in today's
> world. Sometimes like in this statement, we need to trust in their good
> judgment.
>
> My 20 cents,
> as
>
>
>
>
>
> On 10/9/13 12:00 PM, John C Klensin wrote:
> >
> >
> > --On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan
> > <ajs@anvilwalrusden.com <javascript:;>> wrote:
> >
> >> ...
> >> That does not say that the IAB has issued a statement.  On the
> >> contrary, the IAB did not issue a statement.  I think the
> >> difference between some individuals issuing a statement in
> >> their capacity as chairs and CEOs and so on, and the body for
> >> which they are chair or CEO or so on issuing a similar
> >> statement, is an important one.  We ought to attend to it.
> >>
> >> Please note that this message is not in any way a comment on
> >> such leadership meetings.  In addition, for the purposes of
> >> this discussion I refuse either to affirm or deny concurrence
> >> in the IAB chair's statement.  I merely request that we, all
> >> of us, attend to the difference between "the IAB Chair says"
> >> and "the IAB says".
> >
> > Andrew,
> >
> > While I agree that the difference is important for us to note,
> > this is a press release.  It would be naive at best to assume
> > that its intended audience would look at it and say "Ah. A bunch
> > of people with leadership roles in important Internet
> > organizations happened to be in the same place and decided to
> > make a statement in their individual capacities".  Not only does
> > it not read that way, but there are conventions for delivering
> > the "individual capacity" message, including prominent use of
> > phrases like "for identification only".
> >
> > Independent of how I feel about the content of this particular
> > statement,  if the community either doesn't like the message or
> > doesn't like this style of doing things, I think that needs to
> > be discussed and made clear.  That includes not only at the
> > level of preferences about community consultation but about
> > whether, in in the judgment of the relevant people, there is
> > insufficient time to consult the community, no statement should
> > be made at all.
> >
> > Especially from the perspective of having been in the
> > sometimes-uncomfortable position of IAB Chair, I don't think IAB
> > members can disclaim responsibility in a situation like this.
> > Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at
> > the pleasure and convenience of the IAB.  If you and your
> > colleagues are not prepared to share responsibility for
> > statements (or other actions) the IAB Chair makes that involve
> > that affiliation, then you are responsible for taking whatever
> > actions are required to be sure that only those actions are
> > taken for which you are willing to share responsibility.   Just
> > as you have done, I want to stress that I'm not recommending any
> > action here, only that IAB members don't get to disclaim
> > responsibility made by people whose relationship with the IAB is
> > the reason why that are, e.g., part of a particular letter or
> > statement.
> >
> >       john
> >
>

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

I agree to appoint leader under clear procedures, so I am not sure of repre=
senting without procedure is authorised in ietf,=A0but I trust that ietf le=
aders do practice procedure, but not sure if discussion meant that there wa=
s something missing in this statement practice.<div>
<br></div><div>AB<br><div><br>On Wednesday, October 9, 2013, Arturo Servin =
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><br>
=A0 =A0 =A0 =A0 We appointed our leaders, we have to trust them. They had t=
o do a call,<br>
an important one and they made it.<br>
<br>
=A0 =A0 =A0 =A0 I support what they did, that is what we chose them for, to=
 represent<br>
us and be our voice. We cannot expect that they ask our opinion for<br>
every decision they made, that is not practical or possible in today&#39;s<=
br>
world. Sometimes like in this statement, we need to trust in their good<br>
judgment.<br>
<br>
My 20 cents,<br>
as<br>
<br>
<br>
<br>
<br>
<br>
On 10/9/13 12:00 PM, John C Klensin wrote:<br>
&gt;<br>
&gt;<br>
&gt; --On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan<br>
&gt; &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39=
;ajs@anvilwalrusden.com&#39;)">ajs@anvilwalrusden.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; ...<br>
&gt;&gt; That does not say that the IAB has issued a statement. =A0On the<b=
r>
&gt;&gt; contrary, the IAB did not issue a statement. =A0I think the<br>
&gt;&gt; difference between some individuals issuing a statement in<br>
&gt;&gt; their capacity as chairs and CEOs and so on, and the body for<br>
&gt;&gt; which they are chair or CEO or so on issuing a similar<br>
&gt;&gt; statement, is an important one. =A0We ought to attend to it.<br>
&gt;&gt;<br>
&gt;&gt; Please note that this message is not in any way a comment on<br>
&gt;&gt; such leadership meetings. =A0In addition, for the purposes of<br>
&gt;&gt; this discussion I refuse either to affirm or deny concurrence<br>
&gt;&gt; in the IAB chair&#39;s statement. =A0I merely request that we, all=
<br>
&gt;&gt; of us, attend to the difference between &quot;the IAB Chair says&q=
uot;<br>
&gt;&gt; and &quot;the IAB says&quot;.<br>
&gt;<br>
&gt; Andrew,<br>
&gt;<br>
&gt; While I agree that the difference is important for us to note,<br>
&gt; this is a press release. =A0It would be naive at best to assume<br>
&gt; that its intended audience would look at it and say &quot;Ah. A bunch<=
br>
&gt; of people with leadership roles in important Internet<br>
&gt; organizations happened to be in the same place and decided to<br>
&gt; make a statement in their individual capacities&quot;. =A0Not only doe=
s<br>
&gt; it not read that way, but there are conventions for delivering<br>
&gt; the &quot;individual capacity&quot; message, including prominent use o=
f<br>
&gt; phrases like &quot;for identification only&quot;.<br>
&gt;<br>
&gt; Independent of how I feel about the content of this particular<br>
&gt; statement, =A0if the community either doesn&#39;t like the message or<=
br>
&gt; doesn&#39;t like this style of doing things, I think that needs to<br>
&gt; be discussed and made clear. =A0That includes not only at the<br>
&gt; level of preferences about community consultation but about<br>
&gt; whether, in in the judgment of the relevant people, there is<br>
&gt; insufficient time to consult the community, no statement should<br>
&gt; be made at all.<br>
&gt;<br>
&gt; Especially from the perspective of having been in the<br>
&gt; sometimes-uncomfortable position of IAB Chair, I don&#39;t think IAB<b=
r>
&gt; members can disclaim responsibility in a situation like this.<br>
&gt; Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at<br>
&gt; the pleasure and convenience of the IAB. =A0If you and your<br>
&gt; colleagues are not prepared to share responsibility for<br>
&gt; statements (or other actions) the IAB Chair makes that involve<br>
&gt; that affiliation, then you are responsible for taking whatever<br>
&gt; actions are required to be sure that only those actions are<br>
&gt; taken for which you are willing to share responsibility. =A0 Just<br>
&gt; as you have done, I want to stress that I&#39;m not recommending any<b=
r>
&gt; action here, only that IAB members don&#39;t get to disclaim<br>
&gt; responsibility made by people whose relationship with the IAB is<br>
&gt; the reason why that are, e.g., part of a particular letter or<br>
&gt; statement.<br>
&gt;<br>
&gt; =A0 =A0 =A0 john<br>
&gt;<br>
</blockquote></div></div>

--047d7bacbe70faf5cc04e8548cd3--

From abdussalambaryun@gmail.com  Wed Oct  9 13:26: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 18DEB21E81C0 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, 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 Drn40oc3Z8Dg for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 13:26:36 -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 F09C321E81BA for <ietf@ietf.org>; Wed,  9 Oct 2013 13:26:34 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id bj1so1610889pad.35 for <ietf@ietf.org>; Wed, 09 Oct 2013 13:26: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=He5UY64pvrhKHS9Exs/Nbdt4Gow7PviZUWmt9iODUl0=; b=BjzdrMc0oAPzZyfe+whlyRK/RLkpdTEfI/r7Rz8xSyOZ7Wjmcadd0Phe8qhJ7+RtAK 57eH+ZfVtHOCV2ijK1yc2fGSeEQEphP9I/qV81pzPc1C6l/ftLpojQRWZ2NF07NDWEF0 VQZRJT1pysX888aKvEExz0FJ8z1QSfrbmfPcCGh42PX8aSj/rG+olOcCi/B9MdDb3Tfv GqAwxv5EuG2LiHCRGVVMOCoR/cv3+Ge3L3/8kTkSSAPpi0OUJT4hV/6H9sWcV6vpHufc X0V98WyV8/oqhNyhmbvWwwPZIxCTRzWMDDeeVnpJh2bOK+ByvL1aoCpqWgX9NPZTeNsE P6gA==
MIME-Version: 1.0
X-Received: by 10.68.254.132 with SMTP id ai4mr9902634pbd.51.1381350394677; Wed, 09 Oct 2013 13:26:34 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 9 Oct 2013 13:26:34 -0700 (PDT)
In-Reply-To: <5255B647.4090103@gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com>
Date: Wed, 9 Oct 2013 21:26:34 +0100
Message-ID: <CADnDZ89i84gxt+1Tm6a36qS5Qrt=4y3gTxoN1Xz4hkdqScAP1w@mail.gmail.com>
Subject: Re: leader statements
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2e0a1195d23204e854b3ae
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, 09 Oct 2013 20:26:37 -0000

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

There should be known limits for chairs, leaders, only if the procedures
have mentioned no limits of representation. Trust is there but still there
is also levels and limits for trust and representation.

AB

On Wednesday, October 9, 2013, Brian E Carpenter wrote:

> On 10/10/2013 08:27, Andrew Sullivan wrote:
> ...
> > What I am not sure about is whether people are willing to accept the
> > chairs acting in that sort of "leader of organization" role.  If we do
> > accept it, then I think as a consequence some communications will
> > happen without consultation.  For a CEO is not going to agree to issue
> > a joint communiqu=E9 with someone who has to go negotiate the contents
> > of that communiqu=E9 (and negotiate those contents in public).  If we d=
o
> > not accept it, then we must face the fact that there will be meetings
> > where the IETF or IAB just isn't in the room, because we'll have
> > instructed the chairs not to act in that capacity.
>
> I've been there in the past, as IAB Chair, ISOC Board Chairman, and IETF
> Chair.
>
> Either we trust our current and future chairs, on certain occasions,
> to speak in our name without there being a discursive debate in advance,
> or we will have no voice on those occasions.
>
> If there was a pattern of I* chairs subscribing to statements that the
> relevant community clearly found quite outrageous, there might be an
> argument for having no voice.
>
> I suggest that there is no such pattern. There may be quibbles over
> wording sometimes, but that is inevitable when several different
> stakeholder organisations have to agree on wording. The wording is
> inevitably a compromise; it can't be otherwise.
>
> It's perfectly reasonable to ask our chairs to invite debate in
> advance when that is possible; but in many of these cases, it
> simply isn't. It's also perfectly reasonable that people should comment
> on the wording even after it's set in stone; that helps us to do better
> next time.
>
> If we nominate good candidates for our leadership positions, and send
> thoughtful comments to the NomCom (and the IESG and IAB for their
> nominating duties), we won't get leaders who put their names to
> anything outrageous.
>
> We should trust our chairs to act as figureheads and leaders towards
> the outside world.
>
>    Brian Carpenter
>
>

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

There should be known=A0limits for chairs, leaders, only if the procedures =
have mentioned no limits of representation. Trust is there but still there =
is also levels and limits for trust and representation.<div><br></div><div>
AB<br><br>On Wednesday, October 9, 2013, Brian E Carpenter  wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">On 10/10/2013 08:27, Andrew Sullivan wrote:<br>
...<br>
&gt; What I am not sure about is whether people are willing to accept the<b=
r>
&gt; chairs acting in that sort of &quot;leader of organization&quot; role.=
 =A0If we do<br>
&gt; accept it, then I think as a consequence some communications will<br>
&gt; happen without consultation. =A0For a CEO is not going to agree to iss=
ue<br>
&gt; a joint communiqu=E9 with someone who has to go negotiate the contents=
<br>
&gt; of that communiqu=E9 (and negotiate those contents in public). =A0If w=
e do<br>
&gt; not accept it, then we must face the fact that there will be meetings<=
br>
&gt; where the IETF or IAB just isn&#39;t in the room, because we&#39;ll ha=
ve<br>
&gt; instructed the chairs not to act in that capacity.<br>
<br>
I&#39;ve been there in the past, as IAB Chair, ISOC Board Chairman, and IET=
F Chair.<br>
<br>
Either we trust our current and future chairs, on certain occasions,<br>
to speak in our name without there being a discursive debate in advance,<br=
>
or we will have no voice on those occasions.<br>
<br>
If there was a pattern of I* chairs subscribing to statements that the<br>
relevant community clearly found quite outrageous, there might be an<br>
argument for having no voice.<br>
<br>
I suggest that there is no such pattern. There may be quibbles over<br>
wording sometimes, but that is inevitable when several different<br>
stakeholder organisations have to agree on wording. The wording is<br>
inevitably a compromise; it can&#39;t be otherwise.<br>
<br>
It&#39;s perfectly reasonable to ask our chairs to invite debate in<br>
advance when that is possible; but in many of these cases, it<br>
simply isn&#39;t. It&#39;s also perfectly reasonable that people should com=
ment<br>
on the wording even after it&#39;s set in stone; that helps us to do better=
<br>
next time.<br>
<br>
If we nominate good candidates for our leadership positions, and send<br>
thoughtful comments to the NomCom (and the IESG and IAB for their<br>
nominating duties), we won&#39;t get leaders who put their names to<br>
anything outrageous.<br>
<br>
We should trust our chairs to act as figureheads and leaders towards<br>
the outside world.<br>
<br>
=A0 =A0Brian Carpenter<br>
<br>
</blockquote></div>

--047d7b2e0a1195d23204e854b3ae--

From chair@ietf.org  Wed Oct  9 14:09:14 2013
Return-Path: <chair@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 E2CAF21E81D3; Wed,  9 Oct 2013 14:09:13 -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.158, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVsuCAsZg5R9; Wed,  9 Oct 2013 14:09:13 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id B7D8521E81D5; Wed,  9 Oct 2013 14:08:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id F075EA60D6; Wed,  9 Oct 2013 14:08:05 -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 YRy_pdD55ZOB; Wed,  9 Oct 2013 14:08:05 -0700 (PDT)
Received: from [10.30.0.146] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id DDC6FA60CD; Wed,  9 Oct 2013 14:08:04 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Nominations for the Internet Hall of Fame Awards
From: IETF Chair <chair@ietf.org>
Date: Thu, 10 Oct 2013 00:08:36 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE2ED3FA-D0A6-4562-B55F-6D043D596917@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
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
Reply-To: "ietf@ietf.org list" <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: Wed, 09 Oct 2013 21:09:14 -0000

I wanted to forward this message on behalf of the ISOC:

----
=20
Nominations Now Open for the Prestigious Internet Hall of Fame Awards

Hong Kong to Host Third Annual Awards Ceremony
=20
[Washington, D.C. and Geneva, Switzerland] - The Internet Society today =
announced that nominations for the 2014 Internet Hall of Fame are now =
open.  Hong Kong has been selected as the site of the 2014 Internet Hall =
of Fame awards ceremony, to be held on 8 April 2014.=20
=20
Now in its third year, the Internet Hall of Fame honors and celebrates =
Internet visionaries, innovators, and leaders from around the world who =
have significantly contributed to the development and advancement of the =
open, global Internet. The Internet Hall of Fame reflects the living =
history of the Internet and the 2014 honorees will add to that history, =
available for all to experience through the Internet Hall of Fame, =
http://www.internethalloffame.org.
=20
Organizations and individuals from around the world are invited to make =
nominations, and the form is available on the Internet Hall of Fame =
website, http://www.internethalloffame.org/nominations.  Nominees are =
considered for induction into one of three categories:
=20
=95 Pioneers: individuals instrumental in the early design and =
development of the Internet
=20
=95 Innovators:  individuals who made outstanding technological, =
commercial, or policy advances and helped expand the Internet=92s reach
=20
=95 Global Connectors: individuals who made major contributions to the =
growth, connectivity, and use of the Internet, either on a global scale =
or within a specific region or community
=20
"The Internet would not have happened without the incredible work of =
many pioneers and visionaries," said Robert Hinden, Chair of the =
Internet Society Board of Trustees. =93The Internet has made a =
significant difference in the lives of millions of people around the =
world; this would not have happened without the work and devotion of =
these people.  This is your opportunity to recognize them for their =
contributions that made the Internet a reality."
=20
A vibrant city with a highly connected population, Hong Kong will host =
the 2014 Internet Hall of Fame ceremony on 8 April.  The ceremony will =
be one of the highlights of the International IT Fest 2014 in Hong Kong, =
7-20 April. Reflecting the dynamic, global nature of the Internet, the =
awards ceremony will move to a different region of the world each year.  =
Following Hong Kong, the ceremony will be held in Latin America in 2015, =
Africa in 2016, and North America in 2017.
=20
=93Hong Kong is consistently ranked among the world=92s most dynamic =
cities and will provide the ideal setting for next year=92s ceremony,=94 =
remarked Lynn St. Amour, President and CEO of the Internet Society. =93The=
 2014 event promises to be as inspiring as the previous events, =
gathering some of the greatest thinkers and collaborators.=94
=20
More details on the historic contributions of the 2012 and 2013 Internet =
Hall of Fame inductees can be found at =
http://www.internethalloffame.org. You can follow the Internet Hall of =
Fame on Facebook and on Twitter at @Internet_HOF.=

From derhoermi@gmx.net  Wed Oct  9 14:21:50 2013
Return-Path: <derhoermi@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 E357C21E81BE for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 14:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.876
X-Spam-Level: 
X-Spam-Status: No, score=-0.876 tagged_above=-999 required=5 tests=[AWL=-0.237, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUV598PzQ+r6 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 14:21:46 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id D944C21E81BD for <ietf@ietf.org>; Wed,  9 Oct 2013 14:21:45 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.20.241]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0LlleO-1W34tz3fvc-00ZP0Q for <ietf@ietf.org>; Wed, 09 Oct 2013 23:21:44 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: leader statements
Date: Wed, 09 Oct 2013 23:21:45 +0200
Message-ID: <nkfb59p3oujs3n14sled2esahfsu76282c@hive.bjoern.hoehrmann.de>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com>
In-Reply-To: <5255B647.4090103@gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:nMTyzd5Ow7tQBH2ojBiLuU0NmWp5upj5UdBIwzs6LJ4NIKurIpe jWE15shp2jVNFDNKKacgUs4hf5eE+ktkMKgC8exur95WvIpI2uLGeNWEWUc5fE6BSmmXYwe lo/TkQXSVRXDtpLTtKqiQBCouoswpOvZkIvhspztWT2y2ADwP/yF6sh+dTFGI3Z6JmJQxkt gBqp3uvtVuMDj8d8TQdPg==
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, 09 Oct 2013 21:21:51 -0000

* Brian E Carpenter wrote:
>Either we trust our current and future chairs, on certain occasions,
>to speak in our name without there being a discursive debate in advance,
>or we will have no voice on those occasions.

We should think before we speak, and discursive debate is our collective
thought process. Accordingly I would expect Chairs to anticipate and fa-
cilitate debates that might be necessary or useful, especially on issues
where they find giving the collective a voice may be important. It seems
implausible to me that there would be notably many such occasions. Maybe
because as German I am inclined towards disregarding phatic expressions.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From jari.arkko@piuha.net  Wed Oct  9 14:29:18 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 BF58321E81FF; Wed,  9 Oct 2013 14:29:17 -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 J4R02JUSMs5V; Wed,  9 Oct 2013 14:29:10 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B095921E81BA; Wed,  9 Oct 2013 14:28:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5EEB42CCAE; Thu, 10 Oct 2013 00:28:33 +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 cNDksdejFMfM; Thu, 10 Oct 2013 00:28:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3C7092CC48; Thu, 10 Oct 2013 00:28:32 +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 Telechat Review of draft-ietf-intarea-flow-label-balancing-02
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <9BDC86EA-FBC6-400B-8ABF-2D88CB775F96@nostrum.com>
Date: Thu, 10 Oct 2013 00:28:32 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <63F1CC6B-BA15-48A6-A157-1679CE316C80@piuha.net>
References: <9BDC86EA-FBC6-400B-8ABF-2D88CB775F96@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1508)
Cc: "draft-ietf-intarea-flow-label-balancing.all@tools.ietf.org" <draft-ietf-intarea-flow-label-balancing.all@tools.ietf.org>, "gen-art@ietf.org \(gen-art@ietf.org\)" <gen-art@ietf.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: Wed, 09 Oct 2013 21:29:19 -0000

All: Thanks much for the review & changes.

Jari

On Oct 8, 2013, at 11:50 PM, Ben Campbell <ben@nostrum.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>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-intarea-flow-label-balancing-02
> Reviewer: Ben Campbell
> Review Date: 2013-10-08
> IESG Telechat date: 2013-10-10
>=20
> Summary: This version is ready for publication as an informational =
RFC. All of the comments from my previous last call review have been =
addressed either in this version or in email correspondence.=20
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments: None
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From fluffy@iii.ca  Wed Oct  9 15:02:58 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 1FCA621E825E; Wed,  9 Oct 2013 15:02:58 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWoiTpzCeuB2; Wed,  9 Oct 2013 15:02:53 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8F521E8238; Wed,  9 Oct 2013 15:02:47 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.235]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F2578509B5; Wed,  9 Oct 2013 18:02:45 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com>
Date: Wed, 9 Oct 2013 16:02:44 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org" <dhcwg@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, 09 Oct 2013 22:02:58 -0000

On Oct 9, 2013, at 11:53 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Oct 9, 2013, at 1:32 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>> Well DNS and Router obviously won't work with FQDN so lets talk about =
NTP for a minute. (and sorry, I don't even know what AFTR IP is). I =
design lots of devices that have to be plugged into a network and just =
start working with no user interaction. Getting the correct time is =
often really useful to have - particularly with synchronization =
protocols.=20
>=20
> An AFTR IP address is like a router IP address, but for a particular =
IPv4 transition technology.   Other transition technologies of this sort =
are classic examples of services that make sense to configure with DHCP, =
because they are part of the network infrastructure.
>=20
>> One approach would be to hard code that NTP server name in the the =
product. That is not my preferred approach because stuff goes wrong and =
you end up with things like =
http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse .
>=20
> Apple hard-codes the FQDN of a set of NTP servers they control into =
all their products.   I think other OS vendors do as well, but am not =
clear on the details.   The advantage of doing this is that you can then =
authenticate your communication with the NTP server.   If you use DHCP =
to configure your NTP server, you cannot validate your communication =
with your NTP server.   Of course there's a bit of a chicken-and-egg =
problem here in terms of replay attacks and key repudiation, but in =
principle you get more security if you hard code the FQDN of your NTP =
server than if you use DHCP to configure it.

Hard coding it means you can't make your device work if you are on a =
network that behind a firewall that does not allow the traffic or is on =
a networks that is not part of the internet or is being set up for use =
in emergency communications where the the device is on a network say in =
Hati that has become partitioned from rest of network after an disaster. =
 Obviously one can fallback to a hard coded option if no DHCP option is =
found but it's pretty important to have a chance of being able to =
configure things to work on networks with less than ideal connectivity.=20=


>=20
> Of course there are cases where this doesn't matter, and DHCP is just =
fine, but I can't think of any other than perhaps a self-setting wall =
clock.
>=20
> Of course, if a CPE vendor were to hard-code the FQDN of an NTP server =
belonging to someone else into their devices, that would be disastrous.
>=20
>> Another approach is for DHCP to provide the NTP server info. I would =
argue that getting a FQDN of the NTP server pool is a better design for =
DHCP than getting an IP address because this allow DNS load balancing =
across the pool and allows the server IP to change over time and still =
not have client failures.=20
>=20
> You'd get the same effect if the DHCP server did the lookup.   I agree =
that if you want to suddenly add an NTP server and need it to be adopted =
in a time frame shorter than your typical lease time, and your DNS TTL =
is shorter than your typical lease time, you will get better service =
using DNS, but there's no clear win here=97this would be a pretty weird =
requirement.

I think this is the part where we disagree. I don't think you get the =
same effect if the DHCP server did the lookup and returned a single IP =
address. I realize you understand DNS better than me but DNS returns a  =
lot more than a single IP address. In the most simple case it can be =
returning a list of IP so that if one server is down, the client can =
contact another. I don't see how to do that with single IP returned from =
DHCP. (yes, I realize that some people have requested DHCP options to =
return a list of IP). But more impotently if someone wants to do =
something like move the server from one data center to another, it is =
well understood by admins how to do that when clients access the server =
by FQDN. It's much harder when it's an IP address that has to be updated =
in DHCP servers. Not to mention opening up the use DNS tools like SRV =
and NAPTR.=20

>=20
>> You agree that FQDN is would be a better design than IP for NTP ?
>=20
> No.   I think the boxes that need NTP configuration via DHCP are most =
likely constrained devices, and that requiring them to do a DNS lookup =
in addition to the DHCP transaction is unnecessary.

This is not really a constrained device issue - it has to do with hosts =
that don't have an IT administrator and need to just work. They might be =
constrained, but right now my house has devices doing DHCP, DNS, and =
HTTP all fitting in 12 k of flash, 512 bytes of ram, and an 8 bit =
processor at 16Mhz so don't think that DNS needs to be big - probably =
not fully standards compliant but it works. My house also has things =
like NAS, WiFI GW, TVs etc that have pretty powerful computers yet still =
need to turn on and just work with no administration.=20

>   Probably not a hugely bad thing, but that depends on the device.   A =
device with severe constraints probably isn't using DHCP anyway.

Seriously ? How do you think IPv4 constrained devices get an IP address?

>=20
>> Agree - it does not change as phones move network to network. It is =
uses DHCP the first time the phone is plugged in.  The whole design is =
around making sure the phone can go from the manufacture to the end user =
without ever being removed from the box or powered up be an admin. The =
admin configures the call control system based on knowledge about the =
phone and which user the phone is going to but the admin does not need =
to touch the phone. When the phone first boots it imprint baby duck =
style on a network to get the configuration information which is =
encrypted with that phones public key. After that the phone use that =
configuration information not the DHCP (unless the phone is factory =
reset). It's actually a lot more complicated than that because security =
relies on replacement of manufacture certificates with the service =
provider certificates to make sure a comprise of the manufactures CA =
only results in service provider not being able to enroll new phones but =
does not compromise security of operational phone network.=20
>=20
>>=20
>> However, the first time the phone boots, DHCP needs to let the phone =
know who the likely service provider might be. If the phone gets the =
wrong DHCP information from an attacker or wrong network, the phone =
fails to configure but does not suffer MITM attacks. Using DHCP for =
phones has been used by pretty much every IP phone manufactures and most =
enterprise deployments and many residential providers including folks =
ranging from vonage to AT&T take advantage of it.  DHCP greatly reduce =
the deployment costs of setting up VoIP networks.=20
>>=20
>> We had a lot of learning from the phone deployments and I expect us =
to use what we learned there for how we do IoT. (I presented a paper on =
this at the IAB workshop on IoT). One of the things we learned the hard =
way was names work better than numbers.=20
>=20
>=20
> So what you've done here is to invent a service configuration protocol =
that leverages existing DHCP server infrastructure, uses packets that =
look just like DHCP packets, but is not actually DHCP.   A client that =
behaves in the way you have described is not following RFC3315.   It =
might be following the letter of RFC2131, but that's because RFC2131 has =
a known bug in that it doesn't _require_ clients to use new information =
they get from DHCP servers during lease renewals.
>=20
> This is not an academic distinction: I've seen all sorts of support =
calls and questions about IP phones from at least one manufacturer, =
because these phones do not follow the DHCP protocol specification, and =
their behavior is surprising to network administrators.   I didn't =
realize until now that this was by design, and not just a bug in the =
implementation.
>=20

Hmm - this is much more interesting - help me understand what part it =
does not follow 3315. When it boots, it uses DHCP to find the address of =
a configuration server. If it needs a configuration, it downloads that =
from the configuration server. If it does not need a configuration, it =
does not download it. I would not be shocked to find out that this was =
not following 3315 but I think I can speak for at least most the folks =
doing this that they did not know it was not consistent with 3315 and =
would be very interested in hearing why.=20




From brian.e.carpenter@gmail.com  Wed Oct  9 15:21: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 9032321F9B90; Wed,  9 Oct 2013 15:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level: 
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 WqQl7Y85ScDf; Wed,  9 Oct 2013 15:21:35 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 40B5821E81C6; Wed,  9 Oct 2013 15:21:32 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id y10so1607351pdj.8 for <multiple recipients>; Wed, 09 Oct 2013 15:21: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=UtIt7IW8dgroLa5U6prSejhIJGLl3dTBB1Vf3Gv5uSs=; b=oq/eHwqT/s1vH9KSq8dntWuNJAk95daRkCdIDXTi/pddV8U/GSov9qq1p1kEY1IJ2+ kVqYgBb++2dGYOBpFvWphSWyazZZ3aRDJGUeE0dU2pm0EsdCCaHpxEkEEFVCuQEsN4pk 0S35Y8yP9HGgV025FOezObrWmRJWok5Z7zEY15yixa6q/i5Hj3cvDNjLFGnEKXIEdKc+ TFt9YfId5uDGnuNTrA4jUGTrHbEHDpH7cPgt+LbGZk06QvQZWvjya38ikESAkqTcr+ZU BQ09RG1rkz3k4B8C37JWBGWJ93AHFwkKwRMR52VhgtKoBFvBVPVesBtMduKMjEeL9pby XVrg==
X-Received: by 10.67.5.132 with SMTP id cm4mr65764pad.186.1381357291923; Wed, 09 Oct 2013 15:21:31 -0700 (PDT)
Received: from [192.168.178.20] (103.197.69.111.dynamic.snap.net.nz. [111.69.197.103]) by mx.google.com with ESMTPSA id zq10sm57534522pab.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 15:21:31 -0700 (PDT)
Message-ID: <5255D6EE.4050300@gmail.com>
Date: Thu, 10 Oct 2013 11:21:34 +1300
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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>	(Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 22:21:35 -0000

Fred,

See below...

On 10/10/2013 06:42, Templin, Fred L wrote:
> Hi Ole,
> 
>> -----Original Message-----
>> From: Ole Troan [mailto:otroan@employees.org]
>> Sent: Wednesday, October 09, 2013 10:31 AM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; ipv6@ietf.org; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> Fred,
>>
>>>>>> -----Original Message-----
>>>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>>>> Sent: Tuesday, October 08, 2013 5:46 PM
>>>>>> To: Ole Troan; Templin, Fred L
>>>>>> Cc: ipv6@ietf.org; ietf@ietf.org
>>>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>>>> 08.txt>
>>>>>> (Implications of Oversized IPv6 Header Chains) to Proposed
>> Standard
>>>>>> I agree with Ole.
>>>>> How so? A tunnel that crosses a 1280 MTU link MUST fragment
>>>>> in order to satisfy the IPv6 minMTU. If it must fragment, then
>>>>> an MTU-length IPv6 header chain would not fit within the first
>>>>> fragment, and we have opened an attack vector against tunnels.
>>>>> This is not a matter to be agreed or disagreed with - it is
>>>>> a simple fact.
>>>> right, and RFC2460 has this to say about it:
>>>>
>>>>   IPv6 requires that every link in the internet have an MTU of 1280
>>>>   octets or greater.  On any link that cannot convey a 1280-octet
>>>>   packet in one piece, link-specific fragmentation and reassembly
>> must
>>>>   be provided at a layer below IPv6.
>>> Very true. In this case, the "link" is the tunnel and the "link-
>> specific
>>> fragmentation" is IPv6 fragmentation. Which places the first part of
>> an
>>> MTU-length IPv6 header chain in the first fragment and the remainder
>> of
>>> the header chain in the second fragment.
>> indeed. which would violate the MUST in oversized-header-chain.
>>
>> what do we do?
>> a) ignore this particular corner case
>> b) suggest the tunnel head end to drop the packet
>> c) develop a new tunnel segmentations scheme that doesn't depend on
>> IPv6 fragmentation. :-)
> 
> You know I have an interest in alternative c), but that does not
> address the issue of splitting the header chain across multiple
> fragments. So, my choice is:
> 
> d) limit the size of the IPv6 header chain so that the chain will
> fit within the first fragment by having the host limit the chain
> to the MTU size minus 256 bytes.
> 
> Actually, I would be even happier if we just asked the host to limit
> the size of the header chain to 1024 bytes regardless of the path MTU.

Since the problem recurses as we tunnel tunnels, I don't see how any
finite limit can solve the problem. 1280 itself is a pragmatic choice
of "a bit shorter than 1500".

The problem is that you are asserting that middleboxes that a tunnel
passes through are expected to examine the complete header chain of
the encapsulated packet even if the encapsulated packet is a fragment.
I think that's an unreasonable expectation. A reasonable expectation
is that middleboxes should identify the encapsulated packet as
a payload that they cannot analyse, and let it go (unless they
have a policy setting to drop tunnelled packets, which is a
different discussion).

I understood that to be the basis on which the WG reached consensus.

    Brian


From brian.e.carpenter@gmail.com  Wed Oct  9 15:42:43 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 1647A21E81E5 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 15:42:43 -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 z75vsZ8TQzmX for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 15:42:42 -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 BE17A21E81ED for <ietf@ietf.org>; Wed,  9 Oct 2013 15:42:39 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so1616693pbb.28 for <ietf@ietf.org>; Wed, 09 Oct 2013 15:42:39 -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=4EbnsCBXQvxDZQQVeligDNRla9FKgB9v2cEoP/JNF4s=; b=XzIVx9vsgh0J/U5aTUm0OfqOVaG1XySWB3Jve7IUf0XXudcGb3nU3wSP60vdi8PjHw ELdeQceFaWu6gMs6UN/CXx6febZwqhSlp/1x/lXnfq/vytPptcSYZVdd0it7lBaEzRVe boV5Gg15eZkZnbYM5RZrm4xdSiwcaFhppopicWnFE1G8GQtnLURu6tkX7y6nfadXLQIV bz/nrPOsFj9IepcLS0AX1rJbEmwt7vBx249+zAGgJsO/Kqs3BOf4DzMYKh0rdyWl251u Z6TSXfl0nWFqlHzjcvX164vJB24Pk6j2iTaY9rgQOCFIi+HXXQ+Ns1OSHK0bN8fXIY74 L6Zw==
X-Received: by 10.68.247.36 with SMTP id yb4mr10424253pbc.138.1381358559693; Wed, 09 Oct 2013 15:42:39 -0700 (PDT)
Received: from [192.168.178.20] (103.197.69.111.dynamic.snap.net.nz. [111.69.197.103]) by mx.google.com with ESMTPSA id nj9sm48906605pbc.13.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Oct 2013 15:42:38 -0700 (PDT)
Message-ID: <5255DBE3.3040503@gmail.com>
Date: Thu, 10 Oct 2013 11:42:43 +1300
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: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: leader statements
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <nkfb59p3oujs3n14sled2esahfsu76282c@hive.bjoern.hoehrmann.de>
In-Reply-To: <nkfb59p3oujs3n14sled2esahfsu76282c@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=UTF-8
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, 09 Oct 2013 22:42:43 -0000

Bj=C3=B6rn,

On 10/10/2013 10:21, Bjoern Hoehrmann wrote:
> * Brian E Carpenter wrote:
>> Either we trust our current and future chairs, on certain occasions,
>> to speak in our name without there being a discursive debate in advanc=
e,
>> or we will have no voice on those occasions.
>=20
> We should think before we speak, and discursive debate is our collectiv=
e
> thought process. Accordingly I would expect Chairs to anticipate and fa=
-
> cilitate debates that might be necessary or useful, especially on issue=
s
> where they find giving the collective a voice may be important. It seem=
s
> implausible to me that there would be notably many such occasions. Mayb=
e
> because as German I am inclined towards disregarding phatic expressions=
=2E

I assure you that after looking up "phatic" I feel the same way.
And I agree with your point: when there's time to consult the community,
of course it should be done. But sometimes there isn't time, which
is when IMHO we should show some trust in our various Chairs.

    Brian


From Fred.L.Templin@boeing.com  Wed Oct  9 16:13:34 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE5421E81F2; Wed,  9 Oct 2013 16:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.335
X-Spam-Level: 
X-Spam-Status: No, score=-6.335 tagged_above=-999 required=5 tests=[AWL=0.264,  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 dJFQgSs59KA4; Wed,  9 Oct 2013 16:13:19 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 227D121E81ED; Wed,  9 Oct 2013 16:13:14 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r99NDDWV009348; Wed, 9 Oct 2013 16:13:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r99NDCkY009345 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 9 Oct 2013 16:13:12 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (130.247.25.213) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 9 Oct 2013 16:13:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.29]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.180]) with mapi id 14.02.0328.011; Wed, 9 Oct 2013 16:13:11 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxT3pVHjrcZv7kkeUppI3Iq7lo5ns+Qtg
Date: Wed, 9 Oct 2013 23:13:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com>
In-Reply-To: <5255D6EE.4050300@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ipv6@ietf.org" <ipv6@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, 09 Oct 2013 23:13:34 -0000

SGkgQnJpYW4sDQoNClJlc3BvbmRpbmcgaW4gYSBzbGlnaHRseSByZS1hcnJhbmdlZCBvcmRlcjoN
Cg0KPiBUaGUgcHJvYmxlbSBpcyB0aGF0IHlvdSBhcmUgYXNzZXJ0aW5nIHRoYXQgbWlkZGxlYm94
ZXMgdGhhdCBhIHR1bm5lbA0KPiBwYXNzZXMgdGhyb3VnaCBhcmUgZXhwZWN0ZWQgdG8gZXhhbWlu
ZSB0aGUgY29tcGxldGUgaGVhZGVyIGNoYWluIG9mDQo+IHRoZSBlbmNhcHN1bGF0ZWQgcGFja2V0
IGV2ZW4gaWYgdGhlIGVuY2Fwc3VsYXRlZCBwYWNrZXQgaXMgYSBmcmFnbWVudC4NCg0KWWVzLCBi
dXQgY2hhbmdlICJhcmUgZXhwZWN0ZWQgdG8iIHRvICJzaG91bGQgYmUgYWJsZSB0byIuDQoNCj4g
SSB0aGluayB0aGF0J3MgYW4gdW5yZWFzb25hYmxlIGV4cGVjdGF0aW9uLiBBIHJlYXNvbmFibGUg
ZXhwZWN0YXRpb24NCj4gaXMgdGhhdCBtaWRkbGVib3hlcyBzaG91bGQgaWRlbnRpZnkgdGhlIGVu
Y2Fwc3VsYXRlZCBwYWNrZXQgYXMNCj4gYSBwYXlsb2FkIHRoYXQgdGhleSBjYW5ub3QgYW5hbHlz
ZSwgYW5kIGxldCBpdCBnbyAodW5sZXNzIHRoZXkNCj4gaGF2ZSBhIHBvbGljeSBzZXR0aW5nIHRv
IGRyb3AgdHVubmVsbGVkIHBhY2tldHMsIHdoaWNoIGlzIGENCj4gZGlmZmVyZW50IGRpc2N1c3Np
b24pLg0KDQpCdXQgd2h5PyBJZiBoZWFkZXJzIGJleW9uZCB0aGUgZmlyc3QgSVB2NiBlbmNhcHN1
bGF0aW9uIGhlYWRlciBhcmUNCmF2YWlsYWJsZSBpbiB0aGUgY2xlYXIsIHRoZSBtaWRkbGVib3gg
c2hvdWxkIGJlIGFibGUgdG8gcGFyc2UgdGhlbQ0KaWYgaXQgd2FudHMgdG8uIFdpcmVzaGFyayBh
bHJlYWR5IGRvZXMgZXhhY3RseSB0aGF0IC0gaXQga2VlcHMgb24NCnBhcnNpbmcgYmV5b25kIHRo
ZSBmaXJzdCBlbmNhcHN1bGF0aW9uIGhlYWRlciB1cCB0byBhbmQgaW5jbHVkaW5nDQp0aGUgdHJ1
ZSBVTFAgaGVhZGVyLiBBbmQsIGlmIFdpcmVzaGFyayBjYW4gZG8gaXQsIHNvIGNhbiBhbnkgb3Ro
ZXINCm1pZGRsZWJveCB0aGF0IGJlbGlldmVzIHNlY3VyaXR5IHdvdWxkIGJlIGltcHJvdmVkIGJ5
IGNvbnRpbnVpbmcNCnRvIHBhcnNlIHRoZSBlbnRpcmUgY2hhaW4gLSB3aGV0aGVyIG9yIG5vdCB0
aGVyZSBpcyBhIHN0YW5kYXJkDQpzYXlpbmcgaXQgbXVzdCBub3QgZG8gc28uDQoNClBhcnNpbmcg
dGhlIGFkZGl0aW9uYWwgaGVhZGVycyBiZXlvbmQgdGhlIGZpcnN0IGVuY2Fwc3VsYXRpb24gaGVh
ZGVyDQpwcm92aWRlcyBkZWZlbnNlLWluLWRlcHRoLiBQZXJpbWV0ZXIgbWlkZGxlYm94ZXMgY2Fu
IHRoZW4gd2VlZCBvdXQNCnRoZSBiYWQgc3R1ZmYgd2l0aG91dCBlaXRoZXIgYWxsb3dpbmcgdGhl
IGJhZCBzdHVmZiB0byBwZW5ldHJhdGUgbW9yZQ0KZGVlcGx5IGludG8gdGhlIG9yZ2FuaXphdGlv
biBvciBkcm9wcGluZyBnb29kIHN0dWZmIHRoYXQgc2hvdWxkIGJlDQphbGxvd2VkIHRocm91Z2gu
DQoNCj4gU2luY2UgdGhlIHByb2JsZW0gcmVjdXJzZXMgYXMgd2UgdHVubmVsIHR1bm5lbHMsIEkg
ZG9uJ3Qgc2VlIGhvdyBhbnkNCj4gZmluaXRlIGxpbWl0IGNhbiBzb2x2ZSB0aGUgcHJvYmxlbS4g
MTI4MCBpdHNlbGYgaXMgYSBwcmFnbWF0aWMgY2hvaWNlDQo+IG9mICJhIGJpdCBzaG9ydGVyIHRo
YW4gMTUwMCIuDQoNClRoZSAxMjgwIGlzIGFzc3VtaW5nIHRoYXQgYWxsIGxpbmtzIGluIHRoZSBw
YXRoIGhhdmUgYSAxNTAwIE1UVSBhbmQNCnNvIFJGQzI0NjAgYWxsb3dlZCAoMTUwMCAtIDEyODAp
ID0gMjIwIGJ5dGVzIGZvciBhZGRpdGlvbmFsIElQdjYNCmhlYWRlcnMgYWRkZWQgYnkgbmVzdGVk
IHR1bm5lbHMgd2l0aG91dCBpbmN1cnJpbmcgZnJhZ21lbnRhdGlvbi4NCkkgYW0gYXNzZXJ0aW5n
IGluc3RlYWQgdGhhdCB3ZSBoYXZlIHRvIGFsbG93IGZvciBwYXRocyB0aGF0IGluY2x1ZGUNCmxp
bmtzIHdpdGggYSAxMjgwIE1UVSBhbmQgc28gdHVubmVscyB3aWxsIGhhdmUgdG8gZnJhZ21lbnQg
b3Zlcg0Kc3VjaCBwYXRocy4NCg0KVGhhdCBtZWFucyB0aGF0IHRoZSBmaXJzdCBmcmFnbWVudGlu
ZyB0dW5uZWwgd291bGQgaGF2ZSByb29tIGZvcg0KMTI0MCBpbiB0aGUgZmlyc3QgZnJhZ21lbnQs
IHRoZSBzZWNvbmQgZnJhZ21lbnRpbmcgdHVubmVsIHdvdWxkDQpoYXZlIHJvb20gZm9yIDEyMDAg
aW4gdGhlIGZpcnN0IGZyYWdtZW50LCBldGMuIFRoYXQgaXMgd2h5IEkgd291bGQNCnByZWZlciB0
aGF0IGhvc3RzIGxpbWl0IHRoZSBzaXplIG9mIHRoZWlyIGhlYWRlciBjaGFpbnMgdG8gMTAyNDsg
c28NCnRoYXQgbmVzdGVkIHR1bm5lbHMgdGhhdCBmcmFnbWVudCB3aWxsIHN0aWxsIGJlIGhpZ2hs
eSBsaWtlbHkgdG8NCmhhdmUgdGhlIGVudGlyZSBoZWFkZXIgY2hhaW4gaW4gdGhlIGZpcnN0IGZy
YWdtZW50Lg0KIA0KPiBJIHVuZGVyc3Rvb2QgdGhhdCB0byBiZSB0aGUgYmFzaXMgb24gd2hpY2gg
dGhlIFdHIHJlYWNoZWQgY29uc2Vuc3VzLg0KDQpNYXliZSB0aGUgV0cgZGlkbid0IHVuZGVyc3Rh
bmQgdGhhdCBzdWNoIGEgY29uc2Vuc3VzIHdvdWxkIG1ha2UNCnR1bm5lbHMgbGVzcyByZWxpYWJs
ZSBhbmQgbGVzcyBzZWN1cmUuDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50ZW1wbGluQGJvZWlu
Zy5jb20NCg0KPiAgICAgQnJpYW4NCg0K

From scott.brim@gmail.com  Wed Oct  9 16:55:26 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 1E9B821E822B for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 16:55: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, 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 etInQFDzmiMY for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 16:55:25 -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 535E421E8218 for <ietf@ietf.org>; Wed,  9 Oct 2013 16:55:25 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id h10so763758eaj.11 for <ietf@ietf.org>; Wed, 09 Oct 2013 16:55:24 -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=KA8YYAvLF+WKZSaGwU3rZJLMIpv/E+gdgsPN5Js+rxU=; b=YEUr+AAEjIWiP/3bp0oRVFdKART/BGdHb9N0e7TrdkZ8lfHULbCb3GZWtpr9N33o16 O3DuhiKdw/QA033Nf/UaIEgYqbFxeqGT97CqEHd+QT1XWoWza/6wfQ23iXxwRzfmz6xO 1GTztVZrHJgNxiE4yk6MOzjYCHo1ADkw6Lg4KDOGK8nig87yCIa7cQDHa7IMB4GoxGVo b1jIY5zk1KKsyn1hLy/Ww8yP5POjvDYKwq4XCgl/9V1MVt/ErzMqSaAiYtH2d9k7K/Ym XpRH3+gNexP2odiTZpeyo38EPg9TO/KYvjZAYdlmgcqjIZ25MF/1V5H9g42zrZ/5gCXE /auQ==
MIME-Version: 1.0
X-Received: by 10.15.33.132 with SMTP id c4mr15706055eev.2.1381362924382; Wed, 09 Oct 2013 16:55:24 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Wed, 9 Oct 2013 16:55:24 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Wed, 9 Oct 2013 16:55:24 -0700 (PDT)
In-Reply-To: <5255DBE3.3040503@gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <nkfb59p3oujs3n14sled2esahfsu76282c@hive.bjoern.hoehrmann.de> <5255DBE3.3040503@gmail.com>
Date: Wed, 9 Oct 2013 19:55:24 -0400
Message-ID: <CAPv4CP-4vp1=6M7Qb_5pu9rBM0fJ14ORaKWxeF_j1SxXkiozGg@mail.gmail.com>
Subject: Re: leader statements
From: Scott Brim <scott.brim@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e0163457269ee5d04e8579ee9
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, 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, 09 Oct 2013 23:55:26 -0000

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

Discursive debate in advance is for establishing principles, and
establishing the level of trust invested in someone. Then you let them go
to do the job you chose them for. If an issue is of such weight that it
requires a lot of discussion, and you chose the right people, they will
know that already.
On Oct 9, 2013 3:43 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> Bj=F6rn,
>
> On 10/10/2013 10:21, Bjoern Hoehrmann wrote:
> > * Brian E Carpenter wrote:
> >> Either we trust our current and future chairs, on certain occasions,
> >> to speak in our name without there being a discursive debate in advanc=
e,
> >> or we will have no voice on those occasions.
> >
> > We should think before we speak, and discursive debate is our collectiv=
e
> > thought process. Accordingly I would expect Chairs to anticipate and fa=
-
> > cilitate debates that might be necessary or useful, especially on issue=
s
> > where they find giving the collective a voice may be important. It seem=
s
> > implausible to me that there would be notably many such occasions. Mayb=
e
> > because as German I am inclined towards disregarding phatic expressions=
.
>
> I assure you that after looking up "phatic" I feel the same way.
> And I agree with your point: when there's time to consult the community,
> of course it should be done. But sometimes there isn't time, which
> is when IMHO we should show some trust in our various Chairs.
>
>     Brian
>
>

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

<p dir=3D"ltr">Discursive debate in advance is for establishing principles,=
 and establishing the level of trust invested in someone. Then you let them=
 go to do the job you chose them for. If an issue is of such weight that it=
 requires a lot of discussion, and you chose the right people, they will kn=
ow that already.=A0 </p>

<div class=3D"gmail_quote">On Oct 9, 2013 3:43 PM, &quot;Brian E Carpenter&=
quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@=
gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
Bj=F6rn,<br>
<br>
On 10/10/2013 10:21, Bjoern Hoehrmann wrote:<br>
&gt; * Brian E Carpenter wrote:<br>
&gt;&gt; Either we trust our current and future chairs, on certain occasion=
s,<br>
&gt;&gt; to speak in our name without there being a discursive debate in ad=
vance,<br>
&gt;&gt; or we will have no voice on those occasions.<br>
&gt;<br>
&gt; We should think before we speak, and discursive debate is our collecti=
ve<br>
&gt; thought process. Accordingly I would expect Chairs to anticipate and f=
a-<br>
&gt; cilitate debates that might be necessary or useful, especially on issu=
es<br>
&gt; where they find giving the collective a voice may be important. It see=
ms<br>
&gt; implausible to me that there would be notably many such occasions. May=
be<br>
&gt; because as German I am inclined towards disregarding phatic expression=
s.<br>
<br>
I assure you that after looking up &quot;phatic&quot; I feel the same way.<=
br>
And I agree with your point: when there&#39;s time to consult the community=
,<br>
of course it should be done. But sometimes there isn&#39;t time, which<br>
is when IMHO we should show some trust in our various Chairs.<br>
<br>
=A0 =A0 Brian<br>
<br>
</blockquote></div>

--089e0163457269ee5d04e8579ee9--

From Ted.Lemon@nominum.com  Wed Oct  9 18:15: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 1699E21E824F; Wed,  9 Oct 2013 18:15: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 jg3tMYMjWrJQ; Wed,  9 Oct 2013 18:15:48 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5D35A21E823A; Wed,  9 Oct 2013 18:15:48 -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 DSNKUlX/xBtXI/wm2K6DTGIBUkA2Uwev7krT@postini.com; Wed, 09 Oct 2013 18:15: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 C252D1B82CE; Wed,  9 Oct 2013 18:15:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 89C9119005C; Wed,  9 Oct 2013 18:15:46 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Oct 2013 18:15:46 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca>
Date: Wed, 9 Oct 2013 21:15:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@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, 10 Oct 2013 01:15:55 -0000

On Oct 9, 2013, at 6:02 PM, Cullen Jennings <fluffy@iii.ca> wrote:
> Hard coding it means you can't make your device work if you are on a =
network that behind a firewall that does not allow the traffic or is on =
a networks that is not part of the internet or is being set up for use =
in emergency communications where the the device is on a network say in =
Hati that has become partitioned from rest of network after an disaster. =
 Obviously one can fallback to a hard coded option if no DHCP option is =
found but it's pretty important to have a chance of being able to =
configure things to work on networks with less than ideal connectivity.=20=


If this argument were correct, we'd expect to see major O.S. vendors =
supporting the NTP option, but we don't=97instead, it's something that =
can be configured in the UI for situations like the one you describe, =
and that otherwise is defaulted to the preconfigured value, which of =
course can be updated when the operating system is updated.

So where I would expect to see the NTP option used is in devices that =
don't _have_ user interfaces.   Your IP phone might be such a device.   =
I suspect the bias you have toward using a DHCP option has a lot to do =
with where these devices are typically installed: in corporate =
environments.   I don't even know if I could get one to use at home, or =
if it would work.   So in this environment, it certainly makes sense to =
use a DHCP option to do NTP service, as long as you are doing something =
to validate the NTP server so that you can't be trivially attacked by =
being fed false time information.   A hardware RTC would help to sanity =
check the result received from the DHCP-provided NTP server, for =
example.

>>> Another approach is for DHCP to provide the NTP server info. I would =
argue that getting a FQDN of the NTP server pool is a better design for =
DHCP than getting an IP address because this allow DNS load balancing =
across the pool and allows the server IP to change over time and still =
not have client failures.=20
>>=20
>> You'd get the same effect if the DHCP server did the lookup.   I =
agree that if you want to suddenly add an NTP server and need it to be =
adopted in a time frame shorter than your typical lease time, and your =
DNS TTL is shorter than your typical lease time, you will get better =
service using DNS, but there's no clear win here=97this would be a =
pretty weird requirement.
>=20
> I think this is the part where we disagree.  I don't think you get the =
same effect if the DHCP server did the lookup and returned a single IP =
address. I realize you understand DNS better than me but DNS returns a  =
lot more than a single IP address. In the most simple case it can be =
returning a list of IP so that if one server is down, the client can =
contact another. I don't see how to do that with single IP returned from =
DHCP. (yes, I realize that some people have requested DHCP options to =
return a list of IP).

There's nothing to disagree about.   This is in fact how it works with =
most DHCP servers today: you do a DHCP transaction, the DHCP server =
looks up the name in the DNS, stuffs whatever it gets back into the DHCP =
option (hence the advice in the option guidelines draft to allow more =
than one IP address in cases where it makes sense), and merrily sends it =
to the DHCP client, which, if it only wanted one address, likely picks =
the first, just as it would have done had it done the DNS lookup itself.

It's true that it doesn't behave exactly the same as if the device =
repeatedly queries the same name it got from the DHCP server, rather =
than repeatedly using the list of IP addresses it got from the DHCP =
server.

>  But more impotently if someone wants to do something like move the =
server from one data center to another, it is well understood by admins =
how to do that when clients access the server by FQDN. It's much harder =
when it's an IP address that has to be updated in DHCP servers.

This is a really brittle use case, even if you are using DNS.   Whatever =
TTL you are using, you will see outages for that duration.   I can't =
think of a single case where a service you'd sensibly configure with =
DHCP would be moved this way, because servers of this type are typically =
either related to network infrastructure, or are replicable.   So you =
don't just pick up your DNS cache and move it to a different data =
center, not even if it's on an SDN.   Instead, you launch a new DNS =
cache in the new data center, and leave the old DNS cache running until =
the DNS TTLs or DHCP leases have had time to expire.   In either case, =
you get the same behavior and the same outcome.

>  Not to mention opening up the use DNS tools like SRV and NAPTR.=20

Right, and SRV isn't something you'd use for a service that it makes =
sense to configure using DHCP.   Nor is NAPTR.   I would argue that if =
it makes any sense at all for there to be a SRV record, that's a strong =
argument against using DHCP to configure that service.   But yes, if you =
can find an edge case where it does make sense to use DHCP, and a SRV =
record would work and would be useful, then that option should deliver =
an FQDN, not an IP address.

>=20
>>=20
>>> You agree that FQDN is would be a better design than IP for NTP ?
>>=20
>> No.   I think the boxes that need NTP configuration via DHCP are most =
likely constrained devices, and that requiring them to do a DNS lookup =
in addition to the DHCP transaction is unnecessary.
>=20
> This is not really a constrained device issue - it has to do with =
hosts that don't have an IT administrator and need to just work. They =
might be constrained, but right now my house has devices doing DHCP, =
DNS, and HTTP all fitting in 12 k of flash, 512 bytes of ram, and an 8 =
bit processor at 16Mhz so don't think that DNS needs to be big - =
probably not fully standards compliant but it works. My house also has =
things like NAS, WiFI GW, TVs etc that have pretty powerful computers =
yet still need to turn on and just work with no administration.=20

Right, and at the moment they almost certainly have their NTP server =
FQDNs hard-coded, and it works, and you don't even know it's working =
this way, because it's a solid solution in a home network.  The issue =
with DNS on constrained devices is that it's another packet round trip, =
and packets burn battery.   And there are constrained devices where =
adding another network protocol means less space for what the device =
needs to be doing.   But I tend to agree that if you can afford to put a =
DHCP client in a device, there's probably room for a DNS resolver as =
well.

>>  Probably not a hugely bad thing, but that depends on the device.   A =
device with severe constraints probably isn't using DHCP anyway.
>=20
> Seriously ? How do you think IPv4 constrained devices get an IP =
address?

When I say "constrained device," I really mean 6lowpan device.   =
Remember that this document is specifically about DHCPv6.

> Hmm - this is much more interesting - help me understand what part it =
does not follow 3315. When it boots, it uses DHCP to find the address of =
a configuration server. If it needs a configuration, it downloads that =
from the configuration server. If it does not need a configuration, it =
does not download it. I would not be shocked to find out that this was =
not following 3315 but I think I can speak for at least most the folks =
doing this that they did not know it was not consistent with 3315 and =
would be very interested in hearing why.=20

If you are using DHCP to provide the location of a configuration server, =
and you make a leap of faith with that server on first configuration, =
and never talk to it again, then you probably are in compliance with =
RFC3315.   If you take the value of a DHCP option and retain it forever, =
and do not take note of the fact that it has changed, then you are out =
of spec.   I was under the impression from reading your explanation that =
you were doing the latter.=

From fluffy@iii.ca  Wed Oct  9 20:49:24 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 10D1221F9E9D; Wed,  9 Oct 2013 20:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 DaxZTbOAqf4y; Wed,  9 Oct 2013 20:49:19 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id B7A5621E823D; Wed,  9 Oct 2013 20:49:18 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 2A55822E1F3; Wed,  9 Oct 2013 23:49:11 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com>
Date: Wed, 9 Oct 2013 21:49:10 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org" <dhcwg@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, 10 Oct 2013 03:49:24 -0000

Ted, I'm trying hard to get my head around the argument you are making =
and obviously I am coming to the problem from a narrow point of view =
from the VoIP domain and I realize the WG has dealt with DHCP solutions =
for a wide range of solutions - but so far I'm not very convinced by =
this power + extra RTT when the device boots outweighs the opertational =
simplicity concerns of using names. I just can't think of a application =
or device where that extra DNS query at boot accounted for more than =
0.1% of the power usage of the device. I've also received a couple =
private emails that I would more or less summarize as the DHCP WG is =
impossible on this topic, you will never convince them, just ignore the =
spec, it's not a MUST so just don't worry and do whatever you need to =
do. I really don't want to do that - if using FQDN really is the wrong =
choice, it sure would be nice if this draft offered a compelling =
argument of that. Few more comments inline=85.
=20

On Oct 9, 2013, at 7:15 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Oct 9, 2013, at 6:02 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>> Hard coding it means you can't make your device work if you are on a =
network that behind a firewall that does not allow the traffic or is on =
a networks that is not part of the internet or is being set up for use =
in emergency communications where the the device is on a network say in =
Hati that has become partitioned from rest of network after an disaster. =
 Obviously one can fallback to a hard coded option if no DHCP option is =
found but it's pretty important to have a chance of being able to =
configure things to work on networks with less than ideal connectivity.=20=

>=20
> If this argument were correct, we'd expect to see major O.S. vendors =
supporting the NTP option, but we don't=97instead, it's something that =
can be configured in the UI for situations like the one you describe, =
and that otherwise is defaulted to the preconfigured value, which of =
course can be updated when the operating system is updated.

Right - I am certainly more focused on the devices that don't have an =
administrator that can configure them locally.=20

>=20
> So where I would expect to see the NTP option used is in devices that =
don't _have_ user interfaces.   Your IP phone might be such a device.   =
I suspect the bias you have toward using a DHCP option has a lot to do =
with where these devices are typically installed: in corporate =
environments.

Agree I am focused on the VoIP stuff but it is both SP and enterprises.=20=


>   I don't even know if I could get one to use at home, or if it would =
work.

They work in residential deployments (which might be a bit different =
than you mean by home) and DHCP can provide some very critical services =
for them. For example rfc5223 is a DHCP options that provides the LOST =
server that provides the mapping to locations that can be used for E911 =
calls and is applicable to residential.=20

>   So in this environment, it certainly makes sense to use a DHCP =
option to do NTP service, as long as you are doing something to validate =
the NTP server so that you can't be trivially attacked by being fed =
false time information.   A hardware RTC would help to sanity check the =
result received from the DHCP-provided NTP server, for example.
>=20
>>>> Another approach is for DHCP to provide the NTP server info. I =
would argue that getting a FQDN of the NTP server pool is a better =
design for DHCP than getting an IP address because this allow DNS load =
balancing across the pool and allows the server IP to change over time =
and still not have client failures.=20
>>>=20
>>> You'd get the same effect if the DHCP server did the lookup.   I =
agree that if you want to suddenly add an NTP server and need it to be =
adopted in a time frame shorter than your typical lease time, and your =
DNS TTL is shorter than your typical lease time, you will get better =
service using DNS, but there's no clear win here=97this would be a =
pretty weird requirement.
>>=20
>> I think this is the part where we disagree.  I don't think you get =
the same effect if the DHCP server did the lookup and returned a single =
IP address. I realize you understand DNS better than me but DNS returns =
a  lot more than a single IP address. In the most simple case it can be =
returning a list of IP so that if one server is down, the client can =
contact another. I don't see how to do that with single IP returned from =
DHCP. (yes, I realize that some people have requested DHCP options to =
return a list of IP).
>=20
> There's nothing to disagree about.

Sure I believe you about what DHCP servers are capable of doing (which I =
will note might be different than how they are commonly deployed). I was =
talking about the issue here of from a protocol design point of view, =
one should prefer the use of an IP address or FQDN in the DHCP option =
for a case like this.=20

>   This is in fact how it works with most DHCP servers today: you do a =
DHCP transaction, the DHCP server looks up the name in the DNS, stuffs =
whatever it gets back into the DHCP option (hence the advice in the =
option guidelines draft to allow more than one IP address in cases where =
it makes sense), and merrily sends it to the DHCP client, which, if it =
only wanted one address, likely picks the first, just as it would have =
done had it done the DNS lookup itself.
>=20
> It's true that it doesn't behave exactly the same as if the device =
repeatedly queries the same name it got from the DHCP server, rather =
than repeatedly using the list of IP addresses it got from the DHCP =
server.
>=20
>> But more impotently if someone wants to do something like move the =
server from one data center to another, it is well understood by admins =
how to do that when clients access the server by FQDN. It's much harder =
when it's an IP address that has to be updated in DHCP servers.
>=20
> This is a really brittle use case, even if you are using DNS.   =
Whatever TTL you are using, you will see outages for that duration.   I =
can't think of a single case where a service you'd sensibly configure =
with DHCP would be moved this way, because servers of this type are =
typically either related to network infrastructure, or are replicable.   =
So you don't just pick up your DNS cache and move it to a different data =
center, not even if it's on an SDN.   Instead, you launch a new DNS =
cache in the new data center, and leave the old DNS cache running until =
the DNS TTLs or DHCP leases have had time to expire.   In either case, =
you get the same behavior and the same outcome.

When I said "move" I'm talking the roughly the same thing as you mean =
here of bring up a new service. So lets take a VoIP provider like AT&T =
or a large enterprise like GE. Let say that have a server called =
time.ge.com in DNS. Figuring out the TTL for that is pretty easy. =
Changing it to reduce down around the time of the move is pretty easy as =
you can chance it one place and DNS sync it to the other DNS servers. =
Now lets consider doing the same thing with DHCP. How many DHCP server =
do you think either of theses have? Consistent tools to manage all them =
from a central location? The admin know when they are moving servers =
they need to deal with the DNS - but do they all even remember to update =
the DHCP?

The we have the issue of NATs that act as DHCP clients, get an option, =
then re-advertise that option as a DHCP server on the private side. I =
realize that if they advertise it for longer on the private side than =
the lease was valid on the public side is just really broken, but none =
the less I'm sure no one will be shocked to find out there are broken =
NATs.=20

I've been involved with deployments bitten by every one of of the above. =
That make me prefer FQDN unless it is a case where DNS might not be =
supported or not operational, or a case where the time / power of the =
DNS query makes a significant difference to the  system.=20


>=20
>> Not to mention opening up the use DNS tools like SRV and NAPTR.=20
>=20
> Right, and SRV isn't something you'd use for a service that it makes =
sense to configure using DHCP.   Nor is NAPTR.

I thought about what you wrote here for a long time. I suspect that is =
part of the issue is that people such as myself that are not DHCP =
experts don't know what services are not appropriate to use it for. We =
see it as a hammer and we are off pounding nails, or screws. I view SRV =
as an OK way to control load balancing across a set of servers that have =
different capacity - often due to be deployed on faster computers over =
time. Why would a service with that property not be someone one would =
use DHCP for.=20
=20
>   I would argue that if it makes any sense at all for there to be a =
SRV record, that's a strong argument against using DHCP to configure =
that service.  =20

tell me more - this one I did not get.=20

> But yes, if you can find an edge case where it does make sense to use =
DHCP, and a SRV record would work and would be useful, then that option =
should deliver an FQDN, not an IP address.
>=20
>>=20
>>>=20
>>>> You agree that FQDN is would be a better design than IP for NTP ?
>>>=20
>>> No.   I think the boxes that need NTP configuration via DHCP are =
most likely constrained devices, and that requiring them to do a DNS =
lookup in addition to the DHCP transaction is unnecessary.
>>=20
>> This is not really a constrained device issue - it has to do with =
hosts that don't have an IT administrator and need to just work. They =
might be constrained, but right now my house has devices doing DHCP, =
DNS, and HTTP all fitting in 12 k of flash, 512 bytes of ram, and an 8 =
bit processor at 16Mhz so don't think that DNS needs to be big - =
probably not fully standards compliant but it works. My house also has =
things like NAS, WiFI GW, TVs etc that have pretty powerful computers =
yet still need to turn on and just work with no administration.=20
>=20
> Right, and at the moment they almost certainly have their NTP server =
FQDNs hard-coded, and it works, and you don't even know it's working =
this way, because it's a solid solution in a home network.  The issue =
with DNS on constrained devices is that it's another packet round trip, =
and packets burn battery.  =20

Give me an example where that makes a difference. When I look at this as =
the power to do a DNS query amortized over the lifetime of the lease or =
uptime of the device I'm just having a hard time thinking of the right =
example to motivate this.=20

> And there are constrained devices where adding another network =
protocol means less space for what the device needs to be doing.   But I =
tend to agree that if you can afford to put a DHCP client in a device, =
there's probably room for a DNS resolver as well.

Space always seems to be an issue on embedded device so I sort of buy =
that for that very narrow case but this draft is about v6 in general.=20

>=20
>>> Probably not a hugely bad thing, but that depends on the device.   A =
device with severe constraints probably isn't using DHCP anyway.
>>=20
>> Seriously ? How do you think IPv4 constrained devices get an IP =
address?
>=20
> When I say "constrained device," I really mean 6lowpan device.   =
Remember that this document is specifically about DHCPv6.

Given 6lowpan is a subset of even just the wireless devices and does not =
include the wired devices, I had a much broader view of the word =
"constrained" device but point well taken that this is the DHCPv6. I had =
sort of assume the same arguments would apply about the IP vs FQDN for =
v4 options.=20

>=20
>> Hmm - this is much more interesting - help me understand what part it =
does not follow 3315. When it boots, it uses DHCP to find the address of =
a configuration server. If it needs a configuration, it downloads that =
from the configuration server. If it does not need a configuration, it =
does not download it. I would not be shocked to find out that this was =
not following 3315 but I think I can speak for at least most the folks =
doing this that they did not know it was not consistent with 3315 and =
would be very interested in hearing why.=20
>=20
> If you are using DHCP to provide the location of a configuration =
server, and you make a leap of faith with that server on first =
configuration, and never talk to it again, then you probably are in =
compliance with RFC3315.   If you take the value of a DHCP option and =
retain it forever, and do not take note of the fact that it has changed, =
then you are out of spec.   I was under the impression from reading your =
explanation that you were doing the latter.

Sorry for my overly brief description leading to confusion.=20



From sm@resistor.net  Thu Oct 10 02:18:10 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 802B721E80DE for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 02:18: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=[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 m2TX7X6oxhsu for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 02:18: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 942B021E80E9 for <ietf@ietf.org>; Thu, 10 Oct 2013 02:18:00 -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 r9A9HrT8025949 for <ietf@ietf.org>; Thu, 10 Oct 2013 02:17:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381396678; bh=Sz+At2hAHEhdufhPg8opuU/IUOL5+fIibkm3ay/XOb4=; h=Date:To:From:Subject:In-Reply-To:References; b=ghXUsFFQP1VNO75O/R63/XzWZWEwwQcGmQsf+xlZb9GhfOXL/czf8McK0oPAm4EgI TOFecPXThPfFSbO3gyJNQWfmx0WMWHq6uKnyVErv7u9AszZwR6s2HAKm0uisIAUJSw bEh06WQrZX44IsT8+ZpBu8QnrAUtN1bz/jD6Kdvc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381396678; i=@resistor.net; bh=Sz+At2hAHEhdufhPg8opuU/IUOL5+fIibkm3ay/XOb4=; h=Date:To:From:Subject:In-Reply-To:References; b=HZEiQMlZ2z3ZWTp8tfBaMjDqHmg3hNvuAXoQ6JabaTZdJpOKeQ+8ivu1TOixAhAuE ZyX+HIPfemAlkjxM8Ar8B9qbANvI2OvlNFEEg377OfKS0x8o0STvZ2iPvzgOWyqy03 b8HOZO0xPZeAdG9fw3vSgkzwzDrK7SjgD58CxkFc=
Message-Id: <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Oct 2013 01:30:45 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: leader statements (was: Montevideo statement)
In-Reply-To: <20131009192715.GG49231@mx1.yitter.info>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info>
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, 10 Oct 2013 09:18:10 -0000

At 12:27 09-10-2013, Andrew Sullivan wrote:
>Now, there is indeed a possible issue, and that is that these chairs
>were attending a "chief officer"-type meeting: there were CEOs and so
>on, and (presumably by analogy) the chairs got invited to represent
>the organizations of which they are chairs.  John is quite right that
>people unfamiliar with the way the IETF or IAB work might interpret
>the statement along the lines of, "The CEO of the IETF said that the
>IETF subscribes to some view."  Normally, the leader of an
>organization can direct that organization to some end; the Chair is
>the leader; therefore, the Chair can direct the organization.  Of
>course, that's not how we operate (this is, I think, at the bottom of
>this very discussion).  But others might get that impression.
>
>What I am not sure about is whether people are willing to accept the
>chairs acting in that sort of "leader of organization" role.  If we do
>accept it, then I think as a consequence some communications will
>happen without consultation.  For a CEO is not going to agree to issue
>a joint communique with someone who has to go negotiate the contents
>of that communique (and negotiate those contents in public).  If we do
>not accept it, then we must face the fact that there will be meetings
>where the IETF or IAB just isn't in the room, because we'll have
>instructed the chairs not to act in that capacity.

There might be some history to the "we reject: kings, presidents and voting".

Should the IETF change the way it operates?  There are advantages to 
the Chair directing the organization.  It is easier to set 
policy.  It is easier for the Chair to negotiate with other 
organizations.  There are disadvantages, for example, the policy 
might not reflect the wishes of the community.  The IETF might have 
to reconsider whether people participate as individuals or as corporate folks.

There is the question of openness.  If the IETF were to set policy 
behind closed doors, can it say that it is open?  "We" don't take 
working group decisions behind closed doors.  The IESG tries to take 
its decisions in a transparent manner.  There may have been a time 
when it was not like that.

As I mentioned previously the IAB [1] is supposed to be based on 
collegial responsibility.  There hasn't been any discussion to change 
that during the tenure of the last two IAB Chairs.  What's different 
now?  The IAB has published statements and RFCs about its 
positions.  The Chairs can exercise their discretion.

The members of the IESG and the IAB have not mentioned that they do 
not have the ability to negotiate under current rules [2].  The IETF 
Chair and the IAB Chair have not mentioned that they are not able to 
negotiate due to the current rules.  The question of trust comes up 
every now and then.  Responsibility [3] seems to be an inconvenient 
word on this mailing list.

What's the opinion of the persons who are part of "leadership" about all this?

Regards,
-sm

1. "People outside think IAB has power  :-)"
2. I chose a word quickly.
3. the state or fact of being responsible, answerable, or accountable.  


From hallam@gmail.com  Thu Oct 10 06:28:27 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 B6E0921F9E85 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 06:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  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 DOwj-0hy3Fu4 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 06:28:27 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id BE84721F9A10 for <ietf@ietf.org>; Thu, 10 Oct 2013 06:28:21 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id y6so2116025lbh.35 for <ietf@ietf.org>; Thu, 10 Oct 2013 06: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=KmUsaXExRwbdPonoIaIPh8xsa/sjl3tjFbNmBUG8hlc=; b=BR3yZ7jn+hkLk796OdLI6MBv8VDNOIw51xBfI5Fv7xxkXvUmFlhvbBXFSecy/vC2KF b3hKAzMt/HOKYQV9hYd9+cifMZlGUNgMsnfhXSVbg2O6hXlm6E/qTGVznPlJ/YLaw9RL Xu/nSAauAyODPgcEJjVthBbp/NlREwXE5Y9B5GDNbjgQpEYbs80FQgDyKc3jC3HnfhV/ 7AUpppD6jzhsmaD+JfvMKcrAjLAurmmqY682Zt1CLtxssdTlV2rgC6y+WctkuJbqCNhh +WlicSZxsBeyywHDreJLDXB+qHzfkIyffx+d8yKBcwaTby3Oi06u24X0gY94r30GSR8+ UflA==
MIME-Version: 1.0
X-Received: by 10.152.10.99 with SMTP id h3mr11491990lab.13.1381411700651; Thu, 10 Oct 2013 06:28:20 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Thu, 10 Oct 2013 06:28:20 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
Date: Thu, 10 Oct 2013 09:28:20 -0400
Message-ID: <CAMm+LwjRFu0G8vJFUyYrUosk+KsYt+e49bSvvgyoXuNjkVdirg@mail.gmail.com>
Subject: Re: leader statements (was: Montevideo statement)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=001a1132f26ab4bf0804e862f9a7
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, 10 Oct 2013 13:28:28 -0000

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

As a practical matter any organization that tries to do things with other
organizations needs to have some party that can act on its behalf. That is
why Ambassadors are necessary.

The current constitution of the IETF means that the chairs of the IAB and
the IETF have very limited authority to speak for the organization, but of
course they have to.

I have argued for junking the DARPA constitution for years. It was designed
to keep power in the hands of the few while the rest of the organization
didn't worry their pretty heads about it. They don't even get to call
themselves members.

We should junk the noncon completely and the constituency currently
qualified to stand for noncon should elect the chair.

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

<div dir=3D"ltr">As a practical matter any organization that tries to do th=
ings with other organizations needs to have some party that can act on its =
behalf. That is why Ambassadors are necessary.<div><br></div><div>The curre=
nt constitution of the IETF means that the chairs of the IAB and the IETF h=
ave very limited authority to speak for the organization, but of course the=
y have to.=A0</div>
<div><br></div><div>I have argued for junking the DARPA constitution for ye=
ars. It was designed to keep power in the hands of the few while the rest o=
f the organization didn&#39;t worry their pretty heads about it. They don&#=
39;t even get to call themselves members.</div>
<div><br></div><div>We should junk the noncon completely and the constituen=
cy currently qualified to stand for noncon should elect the chair.</div></d=
iv>

--001a1132f26ab4bf0804e862f9a7--

From jnc@mercury.lcs.mit.edu  Thu Oct 10 06:41:39 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 740F721F8427 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 06:41: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 q66sBcaKRUGI for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 06:41:18 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E3A2A21E8104 for <ietf@ietf.org>; Thu, 10 Oct 2013 06:41:17 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CE09B18C110; Thu, 10 Oct 2013 09:41:15 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: leader statements (was: Montevideo statement)
Message-Id: <20131010134115.CE09B18C110@mercury.lcs.mit.edu>
Date: Thu, 10 Oct 2013 09:41:15 -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, 10 Oct 2013 13:41:41 -0000

    > From: Phillip Hallam-Baker <hallam@gmail.com>

    > I have argued for junking the DARPA constitution for years. It was
    > designed to keep power in the hands of the few while the rest of the
    > organization didn't worry their pretty heads about it.

Factually incorrect in a number of ways. The NomComm system was set up to
keep personal politics out of the selection process (or at least keep it to a
minimum). And it wasn't the 'DARPA' system - it resulted from discussion
among a number of people in the IETF.

    > We should junk the noncon completely and the constituency currently
    > qualified to stand for noncon should elect the chair.

The last thing the IETF needs is elections.

	Noel

From Ted.Lemon@nominum.com  Thu Oct 10 06:42:01 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 62DF921F9E68; Thu, 10 Oct 2013 06:42:01 -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 wIZmW3Cz40Ee; Thu, 10 Oct 2013 06:41:55 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 55D1621F90DC; Thu, 10 Oct 2013 06:41:49 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUlaumqZmL9ruZ8euLOmmrIdyUITiTpk8@postini.com; Thu, 10 Oct 2013 06:41:49 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 B64491B80A0; Thu, 10 Oct 2013 06:41:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 96B0B19005C; Thu, 10 Oct 2013 06:41:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Oct 2013 06:41:45 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca>
Date: Thu, 10 Oct 2013 09:41:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@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, 10 Oct 2013 13:42:01 -0000

On Oct 9, 2013, at 11:49 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>> If this argument were correct, we'd expect to see major O.S. vendors =
supporting the NTP option, but we don't=97instead, it's something that =
can be configured in the UI for situations like the one you describe, =
and that otherwise is defaulted to the preconfigured value, which of =
course can be updated when the operating system is updated.
>=20
> Right - I am certainly more focused on the devices that don't have an =
administrator that can configure them locally.=20

This is great, but that's not all devices.   And devices of this type =
often wind up being very vulnerable to attack precisely because no =
usable escape mechanism is offered.   DHCP may be your only choice for =
configuring such a device, but it's a really lousy choice.

>> So where I would expect to see the NTP option used is in devices that =
don't _have_ user interfaces.   Your IP phone might be such a device.   =
I suspect the bias you have toward using a DHCP option has a lot to do =
with where these devices are typically installed: in corporate =
environments.
>=20
> Agree I am focused on the VoIP stuff but it is both SP and =
enterprises.=20
>=20
>>  I don't even know if I could get one to use at home, or if it would =
work.
>=20
> They work in residential deployments (which might be a bit different =
than you mean by home) and DHCP can provide some very critical services =
for them. For example rfc5223 is a DHCP options that provides the LOST =
server that provides the mapping to locations that can be used for E911 =
calls and is applicable to residential.=20

I challenge you to find a single commonly-used home gateway that =
supports this RFC, and that is not VoIP-specific.   If one does, it's =
hard to see any reason why it matters whether the IP address of the E911 =
location service protocol is delivered directly or through an FQDN.

> Sure I believe you about what DHCP servers are capable of doing (which =
I will note might be different than how they are commonly deployed). I =
was talking about the issue here of from a protocol design point of =
view, one should prefer the use of an IP address or FQDN in the DHCP =
option for a case like this.=20

Commonly deployed by whom?   The ISC DHCP server supported the =
functionality that I'm describing in 1997.   Nominum's DHCP server =
supported it on first release.   Cisco's server supported it back when =
it was still a separate company called American Internet, at least as =
early as 1997.   The only commonly-used server that I think does not =
support this functionality is Microsoft's.   I suppose some enterprise =
environments might use this server, which might explain why you are =
assuming that behavior, but we shouldn't decide how to do things based =
on a single implementation that, if it operates in the way you describe, =
is IMHO broken.

> When I said "move" I'm talking the roughly the same thing as you mean =
here of bring up a new service. So lets take a VoIP provider like AT&T =
or a large enterprise like GE. Let say that have a server called =
time.ge.com in DNS. Figuring out the TTL for that is pretty easy. =
Changing it to reduce down around the time of the move is pretty easy as =
you can chance it one place and DNS sync it to the other DNS servers. =
Now lets consider doing the same thing with DHCP. How many DHCP server =
do you think either of theses have? Consistent tools to manage all them =
from a central location? The admin know when they are moving servers =
they need to deal with the DNS - but do they all even remember to update =
the DHCP?
>=20
> The we have the issue of NATs that act as DHCP clients, get an option, =
then re-advertise that option as a DHCP server on the private side. I =
realize that if they advertise it for longer on the private side than =
the lease was valid on the public side is just really broken, but none =
the less I'm sure no one will be shocked to find out there are broken =
NATs.=20
>=20
> I've been involved with deployments bitten by every one of of the =
above. That make me prefer FQDN unless it is a case where DNS might not =
be supported or not operational, or a case where the time / power of the =
DNS query makes a significant difference to the  system.=20

Right, and I think I already said that (a) SIP is a bad example of a use =
case for DHCP, because it's a node-specific service, not a =
network-specific service, and (b) it's probably fine, if you must use =
DHCP to configure SIP, to use an FQDN, as I already said several =
messages back.

> I thought about what you wrote here for a long time. I suspect that is =
part of the issue is that people such as myself that are not DHCP =
experts don't know what services are not appropriate to use it for. We =
see it as a hammer and we are off pounding nails, or screws. I view SRV =
as an OK way to control load balancing across a set of servers that have =
different capacity - often due to be deployed on faster computers over =
time. Why would a service with that property not be someone one would =
use DHCP for.=20

Well, for example, would you use SRV records to do load balancing on a =
DNS server?   An NTP server?   A router (which in the context of DHCPv6 =
probably means an AFTR)?   I think you would not.

>>  I would argue that if it makes any sense at all for there to be a =
SRV record, that's a strong argument against using DHCP to configure =
that service.  =20
>=20
> tell me more - this one I did not get.=20

SRV records are normally used for application-layer services, like SIP, =
which I don't think should be configured with DHCP.   Similarly, would =
you use DHCP to configure the address of an HTTP server? :)

>> Right, and at the moment they almost certainly have their NTP server =
FQDNs hard-coded, and it works, and you don't even know it's working =
this way, because it's a solid solution in a home network.  The issue =
with DNS on constrained devices is that it's another packet round trip, =
and packets burn battery.  =20
>=20
> Give me an example where that makes a difference. When I look at this =
as the power to do a DNS query amortized over the lifetime of the lease =
or uptime of the device I'm just having a hard time thinking of the =
right example to motivate this.=20

Any device that has a battery and needs to run unattended for a long =
period of time will pay a penalty for doing DNS queries over and over =
again; requiring it to do so is a bad practice.   If such a device does =
use DHCP, it almost certainly wants to use very long information refresh =
timers.   Using a short TTL in DNS for a service used by such a device =
either will not work, or will cause the device to prematurely drain its =
battery.

These devices are real, likely represent a very significant area of IP =
service growth in the coming decade or two, and need to be supported.   =
If such a device uses a service discovery protocol, and that service =
discovery protocol probably were to deliver information via FQDNs, the =
device would have to query the DNS multiple times, at least one for each =
service, in order to resolve those FQDNs, each time it does a service =
discovery refresh.   It would also be well advised to query those FQDNs =
again anytime the TTL on the record returned in the previous query =
expired.

DHCP does all the queries for you at the same time and hands you a =
single packet with all the information you need to contact all the =
services offered by DHCP.   This can be expected to result in many fewer =
packet round trips, and consequently much less power spent.   This is a =
significant feature; getting rid of it in order to make life a little =
more convenient for operators who do not have to deal with these =
constraints is a poor value proposition for the protocol as a whole.

BTW, another example of a constrained device is a network booted device, =
where despite the fact that the node itself is quite capable once it's =
booted, the boot prom is quite constrained.   I think this was a primary =
motivation for the choice of address versus FQDN back in DHCPv4 days; I =
suspect relevant in fewer cases now, but still relevant in some.

(I will note, by the way, that you have yet to raise a point that was =
not considered and addressed by the working group.   I think this =
discussion is useful, because it points to clarifications that should be =
made to the document, but I don't yet see anything that would suggest to =
me that the consensus call went the wrong way.)=

From jari.arkko@piuha.net  Thu Oct 10 08:19:33 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 88AB311E8184 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 08:19:24 -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 v+erZwymf6eJ for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 08:19:15 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0EA11E817D for <ietf@ietf.org>; Thu, 10 Oct 2013 08:19:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EE73F2CC95 for <ietf@ietf.org>; Thu, 10 Oct 2013 18:19:05 +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 syeOaBdgNv4U for <ietf@ietf.org>; Thu, 10 Oct 2013 18:19:05 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 65CC32CC48 for <ietf@ietf.org>; Thu, 10 Oct 2013 18:19:05 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: leader statements (was: Montevideo statement)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
Date: Thu, 10 Oct 2013 18:19:05 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7102600B-179B-4170-9A2C-0AF11EE91B91@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Oct 2013 15:19:34 -0000

First off, we like to be in a situation where past IETF discussion, =
consensus, RFCs, and current work program guide what the leaders say. I =
think this was largely the case with the Montevideo statement as well. =
Of course these are judgment calls. Please send us feedback - I for =
instance talk in various external events pretty much on a weekly basis, =
and I'd appreciate feedback in cases where I've done this well or less =
well.

Secondly, there may be times where the leaders might make statements =
that are suggestions for a future path to take. I do think that is =
important. The S in IESG, for instance. Often the status of these =
statements would be obvious from the text "I think that we should =85" =
Again, feedback is appreciated if we're not being clear.

Thirdly, you need to understand that the context of the discussion or =
statements matters a lot from a practical perspective. If I talk to the =
press, I have very little opportunity to finesse what the final message =
is. If we talk to other organisations it is in practice difficult to =
arrange for simultaneous editing by a large group of people. Or get all =
nuances exactly as you want them. But the best model is to have whatever =
we say supported by earlier discussions. But I hope that we can use our =
own words. If we support open standards at the IETF or we have a working =
group on HTTP 2.0, I need to be able to say so.

In short, my hope at least is that I can speak about IETF matters that =
are decided & obvious openly, that I can make suggestions on future =
paths in some contexts, and that where we see a need to make new =
substantive consensus calls, we actually run them with the usual IETF =
process. And we appreciate feedback - there will be mistakes, for which =
I apologize. And I hope we all understand how important communication =
with the external world is.

Jari - speaking as himself only


From mgramirez@globe.com.ph  Wed Oct  9 19:12:33 2013
Return-Path: <mgramirez@globe.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 530B111E8114 for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 19:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.228
X-Spam-Level: 
X-Spam-Status: No, score=-3.228 tagged_above=-999 required=5 tests=[AWL=1.748,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, 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 MENK4+0wh7jN for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 19:12:23 -0700 (PDT)
Received: from mail-qa0-f50.google.com (mail-qa0-f50.google.com [209.85.216.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1A47611E8108 for <ietf@ietf.org>; Wed,  9 Oct 2013 19:12:20 -0700 (PDT)
Received: by mail-qa0-f50.google.com with SMTP id cm18so1188091qab.2 for <ietf@ietf.org>; Wed, 09 Oct 2013 19:12:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tD4FScOlZlbCsk1kiUPk7hX6qDsQRQuExsGe5A6DQO4=; b=SHtA3Qs5c7+jFlrNS8X4x+qFQUwoI60UPlYkRT7tbQQyrH3TlWH5QYeNY0QQGUrfPv AZaUfflWgds2VkGk0vsCaJuDUetSOYW1Jmw/8ETj1yDm8ox/3pM9PsbJ8S2MXnIW07RL hwX209osdbVqPrRt6LpdFQr6Cus+VSmKkquYscX6TLeWF8faTW/L1Dib08kkYIY4KsIU nMuvRBe29cLOKKN7SsDQBAVptdC9a2w6fLNHs9wlk9pLNkIfaOW4+ardJBmtsdQvWyuO PTKVPbwLqPVPzhKed2VC9duROxLrRypCcrzr6LKJx+/7F+i/bX9g1A3kiSBLNgWXE0No qXpA==
X-Gm-Message-State: ALoCoQnf/WAiMgjU5Pkb++1vRohY3u6scI7Gczpjsp8cN3NvQxZw7XnmuzNYAj1j6XczwuJs94H5v9BJFsQJ6BKH68fmYZQfVQ==
X-Received: by 10.229.219.199 with SMTP id hv7mr4160641qcb.15.1381371139949; Wed, 09 Oct 2013 19:12:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.192.65 with HTTP; Wed, 9 Oct 2013 19:11:59 -0700 (PDT)
In-Reply-To: <CADnDZ8-vaM64D9T79XgCzgby-6TEmgsPeEvA6XfZwwUCHtX1fA@mail.gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <5255A905.10700@gmail.com> <CADnDZ8-vaM64D9T79XgCzgby-6TEmgsPeEvA6XfZwwUCHtX1fA@mail.gmail.com>
From: Medel v6 Ramirez <mgramirez@globe.com.ph>
Date: Thu, 10 Oct 2013 10:11:59 +0800
Message-ID: <CALw3TGGkSmxz-+HPAwqF-JAv3EZjfHPTwEgJjq3Lz+e_BRDq7g@mail.gmail.com>
Subject: Re: Montevideo statement
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134487419b86404e8598845
X-Mailman-Approved-At: Thu, 10 Oct 2013 09:28:18 -0700
Cc: Arturo Servin <arturo.servin@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: Thu, 10 Oct 2013 02:12:33 -0000

--001a1134487419b86404e8598845
Content-Type: text/plain; charset=US-ASCII

Leaders were "processed" thoroughly prior to their appointment so I trust
them. And that they hold through the "spirit" of being an IETF and shall be
responsible under oath for any impact on the organization.

BR,
Medel

GOOGLE IS IPv6 COMPLIANT !


On Thu, Oct 10, 2013 at 4:15 AM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> I agree to appoint leader under clear procedures, so I am not sure of
> representing without procedure is authorised in ietf, but I trust that ietf
> leaders do practice procedure, but not sure if discussion meant that there
> was something missing in this statement practice.
>
> AB
>
>
> On Wednesday, October 9, 2013, Arturo Servin wrote:
>
>>
>>         We appointed our leaders, we have to trust them. They had to do a
>> call,
>> an important one and they made it.
>>
>>         I support what they did, that is what we chose them for, to
>> represent
>> us and be our voice. We cannot expect that they ask our opinion for
>> every decision they made, that is not practical or possible in today's
>> world. Sometimes like in this statement, we need to trust in their good
>> judgment.
>>
>> My 20 cents,
>> as
>>
>>
>>
>>
>>
>> On 10/9/13 12:00 PM, John C Klensin wrote:
>> >
>> >
>> > --On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan
>> > <ajs@anvilwalrusden.com> wrote:
>> >
>> >> ...
>> >> That does not say that the IAB has issued a statement.  On the
>> >> contrary, the IAB did not issue a statement.  I think the
>> >> difference between some individuals issuing a statement in
>> >> their capacity as chairs and CEOs and so on, and the body for
>> >> which they are chair or CEO or so on issuing a similar
>> >> statement, is an important one.  We ought to attend to it.
>> >>
>> >> Please note that this message is not in any way a comment on
>> >> such leadership meetings.  In addition, for the purposes of
>> >> this discussion I refuse either to affirm or deny concurrence
>> >> in the IAB chair's statement.  I merely request that we, all
>> >> of us, attend to the difference between "the IAB Chair says"
>> >> and "the IAB says".
>> >
>> > Andrew,
>> >
>> > While I agree that the difference is important for us to note,
>> > this is a press release.  It would be naive at best to assume
>> > that its intended audience would look at it and say "Ah. A bunch
>> > of people with leadership roles in important Internet
>> > organizations happened to be in the same place and decided to
>> > make a statement in their individual capacities".  Not only does
>> > it not read that way, but there are conventions for delivering
>> > the "individual capacity" message, including prominent use of
>> > phrases like "for identification only".
>> >
>> > Independent of how I feel about the content of this particular
>> > statement,  if the community either doesn't like the message or
>> > doesn't like this style of doing things, I think that needs to
>> > be discussed and made clear.  That includes not only at the
>> > level of preferences about community consultation but about
>> > whether, in in the judgment of the relevant people, there is
>> > insufficient time to consult the community, no statement should
>> > be made at all.
>> >
>> > Especially from the perspective of having been in the
>> > sometimes-uncomfortable position of IAB Chair, I don't think IAB
>> > members can disclaim responsibility in a situation like this.
>> > Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at
>> > the pleasure and convenience of the IAB.  If you and your
>> > colleagues are not prepared to share responsibility for
>> > statements (or other actions) the IAB Chair makes that involve
>> > that affiliation, then you are responsible for taking whatever
>> > actions are required to be sure that only those actions are
>> > taken for which you are willing to share responsibility.   Just
>> > as you have done, I want to stress that I'm not recommending any
>> > action here, only that IAB members don't get to disclaim
>> > responsibility made by people whose relationship with the IAB is
>> > the reason why that are, e.g., part of a particular letter or
>> > statement.
>> >
>> >       john
>> >
>>
>

-- 
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 
information that is privileged, proprietary, confidential and exempt from 
disclosure. If you are not the intended recipient, you are notified that 
any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, 
please notify the sender and delete this E-mail message immediately.


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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:large">Leaders were &quot;processed&quot; thor=
oughly prior to their appointment so I trust them. And that they hold throu=
gh the &quot;spirit&quot; of being an IETF and shall be responsible under o=
ath for any impact on the organization.</div>

<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:large"><br></div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif;font-size:large">BR,</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:large"=
>

Medel</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=
=3D"ltr">GOOGLE IS IPv6 COMPLIANT !</div></div>
<br><br><div class=3D"gmail_quote">On Thu, Oct 10, 2013 at 4:15 AM, Abdussa=
lam Baryun <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.c=
om" target=3D"_blank">abdussalambaryun@gmail.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">

I agree to appoint leader under clear procedures, so I am not sure of repre=
senting without procedure is authorised in ietf,=A0but I trust that ietf le=
aders do practice procedure, but not sure if discussion meant that there wa=
s something missing in this statement practice.<span class=3D"HOEnZb"><font=
 color=3D"#888888"><div>


<br></div></font></span><div><span class=3D"HOEnZb"><font color=3D"#888888"=
>AB</font></span><div><div class=3D"h5"><br><div><br>On Wednesday, October =
9, 2013, Arturo Servin  wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
=A0 =A0 =A0 =A0 We appointed our leaders, we have to trust them. They had t=
o do a call,<br>
an important one and they made it.<br>
<br>
=A0 =A0 =A0 =A0 I support what they did, that is what we chose them for, to=
 represent<br>
us and be our voice. We cannot expect that they ask our opinion for<br>
every decision they made, that is not practical or possible in today&#39;s<=
br>
world. Sometimes like in this statement, we need to trust in their good<br>
judgment.<br>
<br>
My 20 cents,<br>
as<br>
<br>
<br>
<br>
<br>
<br>
On 10/9/13 12:00 PM, John C Klensin wrote:<br>
&gt;<br>
&gt;<br>
&gt; --On Wednesday, October 09, 2013 02:44 -0400 Andrew Sullivan<br>
&gt; &lt;<a>ajs@anvilwalrusden.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; ...<br>
&gt;&gt; That does not say that the IAB has issued a statement. =A0On the<b=
r>
&gt;&gt; contrary, the IAB did not issue a statement. =A0I think the<br>
&gt;&gt; difference between some individuals issuing a statement in<br>
&gt;&gt; their capacity as chairs and CEOs and so on, and the body for<br>
&gt;&gt; which they are chair or CEO or so on issuing a similar<br>
&gt;&gt; statement, is an important one. =A0We ought to attend to it.<br>
&gt;&gt;<br>
&gt;&gt; Please note that this message is not in any way a comment on<br>
&gt;&gt; such leadership meetings. =A0In addition, for the purposes of<br>
&gt;&gt; this discussion I refuse either to affirm or deny concurrence<br>
&gt;&gt; in the IAB chair&#39;s statement. =A0I merely request that we, all=
<br>
&gt;&gt; of us, attend to the difference between &quot;the IAB Chair says&q=
uot;<br>
&gt;&gt; and &quot;the IAB says&quot;.<br>
&gt;<br>
&gt; Andrew,<br>
&gt;<br>
&gt; While I agree that the difference is important for us to note,<br>
&gt; this is a press release. =A0It would be naive at best to assume<br>
&gt; that its intended audience would look at it and say &quot;Ah. A bunch<=
br>
&gt; of people with leadership roles in important Internet<br>
&gt; organizations happened to be in the same place and decided to<br>
&gt; make a statement in their individual capacities&quot;. =A0Not only doe=
s<br>
&gt; it not read that way, but there are conventions for delivering<br>
&gt; the &quot;individual capacity&quot; message, including prominent use o=
f<br>
&gt; phrases like &quot;for identification only&quot;.<br>
&gt;<br>
&gt; Independent of how I feel about the content of this particular<br>
&gt; statement, =A0if the community either doesn&#39;t like the message or<=
br>
&gt; doesn&#39;t like this style of doing things, I think that needs to<br>
&gt; be discussed and made clear. =A0That includes not only at the<br>
&gt; level of preferences about community consultation but about<br>
&gt; whether, in in the judgment of the relevant people, there is<br>
&gt; insufficient time to consult the community, no statement should<br>
&gt; be made at all.<br>
&gt;<br>
&gt; Especially from the perspective of having been in the<br>
&gt; sometimes-uncomfortable position of IAB Chair, I don&#39;t think IAB<b=
r>
&gt; members can disclaim responsibility in a situation like this.<br>
&gt; Unlike the Nomcom-appointed IETF Chair, the IAB Chair serves at<br>
&gt; the pleasure and convenience of the IAB. =A0If you and your<br>
&gt; colleagues are not prepared to share responsibility for<br>
&gt; statements (or other actions) the IAB Chair makes that involve<br>
&gt; that affiliation, then you are responsible for taking whatever<br>
&gt; actions are required to be sure that only those actions are<br>
&gt; taken for which you are willing to share responsibility. =A0 Just<br>
&gt; as you have done, I want to stress that I&#39;m not recommending any<b=
r>
&gt; action here, only that IAB members don&#39;t get to disclaim<br>
&gt; responsibility made by people whose relationship with the IAB is<br>
&gt; the reason why that are, e.g., part of a particular letter or<br>
&gt; statement.<br>
&gt;<br>
&gt; =A0 =A0 =A0 john<br>
&gt;<br>
</blockquote></div></div></div></div>
</blockquote></div><br></div>

<br>
<div>This e-mail message (including attachments, if any) is intended for th=
e use of the individual or the entity to whom it is addressed and may conta=
in information that is privileged, proprietary, confidential and exempt fro=
m disclosure. If you are not the intended recipient, you are notified that =
any dissemination, distribution or copying of this communication is strictl=
y prohibited. If you have received this communication in error, please noti=
fy the sender and delete this E-mail message immediately.</div><div><br></d=
iv>
--001a1134487419b86404e8598845--

From avri@ella.com  Wed Oct  9 10:04:43 2013
Return-Path: <avri@ella.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9888221E808F for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:04: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 hyaIPyE66Jgc for <ietf@ietfa.amsl.com>; Wed,  9 Oct 2013 10:04:37 -0700 (PDT)
Received: from atl4mhob09.myregisteredsite.com (atl4mhob09.myregisteredsite.com [209.17.115.47]) by ietfa.amsl.com (Postfix) with ESMTP id 7750D21E811C for <ietf@ietf.org>; Wed,  9 Oct 2013 10:04:11 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob09.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r99H48Rv030681 for <ietf@ietf.org>; Wed, 9 Oct 2013 13:04:08 -0400
Received: (qmail 32527 invoked by uid 0); 9 Oct 2013 17:04:08 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?192.168.15.112?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 9 Oct 2013 17:04:08 -0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Last calling draft-resnick-on-consensus
From: Avri Doria <avri@ella.com>
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
Date: Wed, 9 Oct 2013 13:04:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7FCDDD5-09AC-40BA-AFBD-98AD1C90AF44@ella.com>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Thu, 10 Oct 2013 09:28:41 -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: Wed, 09 Oct 2013 17:09:56 -0000

Hi,

I think this is an excellent draft and have already sent a pointer of it =
to colleagues in other organizations as  stuff to consider.

And although it has been eons since I chaired anything in the IETF, it =
perfectly matches my recollection of what humming  and rough consensus =
was all about.


thanks

avri


On 6 Oct 2013, at 17:03, Jari Arkko wrote:

> The document talks about ways in which consensus processes can be =
successfully run in the IETF. After the last few rounds of versions, I =
believe this document is ready to move forward.=20
>=20
> My goal is to publish it as an Informational RFC. It is an explanation =
of principles and how they can be applied to productively move IETF =
discussions forward. While there is no change to IETF processes or any =
presumption that guidance from this document must be followed, I have =
found the document very useful. It has been referred to numerous times =
in IETF and IESG discussions. Consensus is hard and many WG discussions =
have complex trade-offs and differing opinions. I believe having this =
document become an RFC would help us apply the useful principles even =
more widely than we are doing today. =20
>=20
> The abstract says:
>=20
>   The IETF has had a long tradition of doing its technical work =
through
>   a consensus process, taking into account the different views among
>   IETF participants and coming to (at least rough) consensus on
>   technical matters.  In particular, the IETF is supposed not to be =
run
>   by a "majority rule" philosophy.  This is why we engage in rituals
>   like "humming" instead of voting.  However, more and more of our
>   actions are now indistinguishable from voting, and quite often we =
are
>   letting the majority win the day, without consideration of minority
>   concerns.  This document is a collection of thoughts on what rough
>   consensus is, how we have gotten away from it, and the things we can
>   do in order to really achieve rough consensus.
>=20
>      Note (to be removed before publication): This document is quite
>      consciously being put forward as Informational.  It does not
>      propose to change any IETF processes and is therefore not a BCP.
>      It is simply a collection of principles, hopefully around which
>      the IETF can come to (at least rough) consensus.
>=20
> The draft can be obtained from =
http://tools.ietf.org/html/draft-resnick-on-consensus
>=20
> You should see a last call announcement soon, and both me and Pete =
look forward to your feedback.
>=20
> Jari
>=20
>=20


From dhc@dcrocker.net  Thu Oct 10 10:06:22 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 08AB121F9FCE for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:06: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 JwpuDW5WRG6J for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:06:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D8A4221F9F51 for <ietf@ietf.org>; Thu, 10 Oct 2013 10:06:10 -0700 (PDT)
Received: from [10.100.255.252] ([203.167.240.58]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9AH65RA003162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 10 Oct 2013 10:06:10 -0700
Message-ID: <5256DE72.4010705@dcrocker.net>
Date: Fri, 11 Oct 2013 06:05:54 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Montevideo statement
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
In-Reply-To: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
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, 10 Oct 2013 10:06:10 -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, 10 Oct 2013 17:06:22 -0000

On 10/8/2013 11:34 AM, IETF Chair wrote:
> I wanted to send a link to a statement that Russ and I signed as a
> part of a meeting that we held last week with the leaders of other
> Internet organisations.
>
> http://www.internetsociety.org/news/montevideo-statement-future-internet-cooperation


Folks,

There are a few things that we should consider rather more carefully
than we've been doing, beyond a few of the postings. (I'd especially 
like to suggest that there be more careful review of Andrew Sullivan's 
postings on the thread, since he raises essential point, in my view.)

In any event:

      1. In spite of calling itself a press release (at the bottom) and
having gone through an ISOC media person, what was released was not a
press release.   Neither in form nor substance.  Its title says
"statement", and the bottom list of people is in the style of a
signature list, rather than merely listing attendees -- and note that 
Jari does characterize this as being signed.  Hence what was released 
was in the style of a formal statement, issued under the control of its 
signatories.

      2. The statement does not merely say that these folk met and
discussed stuff.  It says they agreed to stuff, or at leased "called 
for" stuff.

      3. These people were acting as representatives of their
organizations; hence the use of their titles.  And the statement does
not explicitly say they were speaking only for themselves.  So their
agreement to the Statement needs to be taken as their speaking for their
organizations.

      4. Having both IETF Chair and IAB Chair makes it look like there 
were two organizations being represented, but in practical terms there 
really weren't.

      5. It has been noted that the IAB is largely autonomous for 
something like this; hence the IAB Chair formally only has to answer to 
the IAB itself, and we are told he was in this case.  What this begs is 
a question about the IAB acting independently of the IETF community...


My initial reading of the Statement was that it was quite benign, so
that any concern about it's speaking for the IETF was purely a matter of
principle.  In that regard, I considered it a nice test case for some
basic IETF discussion of the authority of our 'leaders' to make 
statements on our behalf but without our review or approval.  Then I 
re-read the statement more carefully and landed on:

> They called for accelerating the globalization of ICANN and IANA
> functions, towards an environment in which all stakeholders,
> including all governments, participate on an equal footing.

     5.  It's not at all clear what "accelerating the globalization" 
means here, since the statement offers no context for whatever 
'globalization' efforts with ICANN and IANA are happening.  Worse, this 
item is entirely political, involving organizations with which the IETF 
has on-going agreements and reliance.  Further, I believe there is no 
IETF context -- nevermind consensus -- for the topic.  As far as I know 
the IETF has no basic discomfort with its relationship with IANA, for 
example.  We might individually make guesses about what this item in the 
Statement means, but my point is that a) we shouldn't have to, and b) it 
has no context within the IETF community.  For any of our 'leaders' to 
make agreements on our behalf, about political issues of organizations 
with which we have formal arrangements -- and probably any other 
organizations -- is significantly problematic.


As has been noted, there are practical and formal limits to requirements 
for getting IETF rough consensus.  Any constraints on public statements 
by IETF leaders needs to balance against those limits, if we are to 
allow folk to speak publicly at all.

      6. The realities of trying to get IETF community rough consensus 
means that anything requiring timely action cannot seek formal 
consensus.  To that end, we need to distinguish between 'review' and 
'approval'.  IETF community review can be very quick indeed, though 
probably not less than 24 hours, if the range of review comments is to 
be a good sampling of the community.  In the current example, community 
review quickly noted the erroneous phrasing that confuses concern about 
disclosure of an act from concern about the act itself.  (I'm working on 
the assumption that the Montevideo group is really more concerned that 
monitoring was/is taking place than that someone made this fact public...)


Now to a more basic issue.  It's likely to be uncomfortable, but I'll 
stress that this isn't about individual people.  Fortunately, no sane 
person can have any concerns about the intent of either of the IETF folk 
who participated in this event and its resulting Statement.  So what 
follows is about IETF roles, responsibilities and authorities, not about 
individuals...

What does it mean to be a 'leader' in the IETF, who is Chair of the IETF 
or the IAB?  Unlike CEOs and Presidents and Chairs of corporations, IETF 
leaders mostly don't lead.  They don't set work agendas. They don't 
control overall budgets.  They don't hire and fire people.  For almost 
all of the formal IETF 'decisions' they participate in, it is with 
exactly one vote in a group, and not more authority than that.  (And by 
the way, the IESG largely does not 'steer' the IETF.  Initiatives for 
work come from the community and very nearly never from ADs or the IESG.)

IETF leaders are best viewed as facilitators, rather than leaders.  They 
do huge amounts of organizing, coordinating, interfacing, in the classic 
style of the cliche'd 'shepherding cats'.

So when they speak on our behalf, it really does need to be an accurate 
rendition of IETF community views and not merely their guesses of those 
views or their hopes of what those views might or should be.

      7. The released Statement was formulated by the group including 
two IETF 'leaders'.  It was not subject to random formulation by a 
reporter, or the like.  When people holding formal IETF roles 
participate in the formulation of formal Statements, things need to be 
carefully based on actual IETF community views.


We need to find some sort of language that gives constructive guidance 
and constraint about public representations of the IETF, by our 
'leaders'.  Not very long ago, there was a concern raised by Pete 
Resnick, when an IETF working group chair made statements at an ITU 
gathering and represented himself as an IETF wg chair.  We might want to 
review whatever guidance came out of that.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From bmanning@isi.edu  Thu Oct 10 10:50:41 2013
Return-Path: <bmanning@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 A4FE521F85EF for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:50:40 -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=[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 ZYSsizMIzukt for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:50:34 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id CD93D11E8185 for <ietf@ietf.org>; Thu, 10 Oct 2013 10:49:56 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r9AHnQL3009174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 10:49:38 -0700 (PDT)
Subject: Re: leader statements
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: manning bill <bmanning@isi.edu>
In-Reply-To: <5255B647.4090103@gmail.com>
Date: Thu, 10 Oct 2013 10:49:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 10 Oct 2013 17:50:41 -0000

the "leaders" are there to inform and moderate the discussion and where =
possible, indicate
that consensus has been reached (or not).    when "leaders" speak out on =
behalf of organization
-particularly- this organization and they are _NOT_ relaying the =
consensus of the group at large,
they have exceeded their remit. =20

glossing over  or ignoring conflicting opinions simply because it does =
not reflect the "leader" bias
is demonstrable - often to serious harm to an otherwise worthy effort.   =
 Chairs should _NOT_ =20
presume to speak for an organization without consultation.  =20

Concerns about "being in the room" reflect a serious insecurity in the =
type and quality of work that
we are supposed to be producing.=20

/bill


On 9October2013Wednesday, at 13:02, Brian E Carpenter wrote:

> On 10/10/2013 08:27, Andrew Sullivan wrote:
> ...
>> What I am not sure about is whether people are willing to accept the
>> chairs acting in that sort of "leader of organization" role.  If we =
do
>> accept it, then I think as a consequence some communications will
>> happen without consultation.  For a CEO is not going to agree to =
issue
>> a joint communiqu=E9 with someone who has to go negotiate the =
contents
>> of that communiqu=E9 (and negotiate those contents in public).  If we =
do
>> not accept it, then we must face the fact that there will be meetings
>> where the IETF or IAB just isn't in the room, because we'll have
>> instructed the chairs not to act in that capacity.
>=20
> I've been there in the past, as IAB Chair, ISOC Board Chairman, and =
IETF Chair.
>=20
> Either we trust our current and future chairs, on certain occasions,
> to speak in our name without there being a discursive debate in =
advance,
> or we will have no voice on those occasions.
>=20
> If there was a pattern of I* chairs subscribing to statements that the
> relevant community clearly found quite outrageous, there might be an
> argument for having no voice.
>=20
> I suggest that there is no such pattern. There may be quibbles over
> wording sometimes, but that is inevitable when several different
> stakeholder organisations have to agree on wording. The wording is
> inevitably a compromise; it can't be otherwise.
>=20
> It's perfectly reasonable to ask our chairs to invite debate in
> advance when that is possible; but in many of these cases, it
> simply isn't. It's also perfectly reasonable that people should =
comment
> on the wording even after it's set in stone; that helps us to do =
better
> next time.
>=20
> If we nominate good candidates for our leadership positions, and send
> thoughtful comments to the NomCom (and the IESG and IAB for their
> nominating duties), we won't get leaders who put their names to
> anything outrageous.
>=20
> We should trust our chairs to act as figureheads and leaders towards
> the outside world.
>=20
>   Brian Carpenter
>=20


From arturo.servin@gmail.com  Thu Oct 10 10:55:53 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 B1FF111E8183 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, 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 vNWxN1TLMSq0 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:55:51 -0700 (PDT)
Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9047611E8187 for <ietf@ietf.org>; Thu, 10 Oct 2013 10:55:50 -0700 (PDT)
Received: by mail-qe0-f43.google.com with SMTP id nc12so2228098qeb.2 for <ietf@ietf.org>; Thu, 10 Oct 2013 10:55: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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XgiP6bKK+d1aMXKIZdGs6H0qOm8E4Ae+/bP63N0dXxo=; b=SP5XxoFeRSx/BcTNbIO84P/Vz3pJLHLRKBvXFEyveEtk7w2EvR9D6eRlxBOryCB47I wlM6CMMeCRHsPha4cK0nYJOtB6K7ldpHlMezb1qihlSQTVLaz12WRgn4ZdVrUP61C0hA A0yNQIBi8B17FBpEpAqVCPsdXJ7WxXihY4JoqCTGeskKAjnZ1HsuXsBRpbxqST4yLzXy A2KMwTAuMM7StcSStkHhVb+YCJHoFLsRnB2t5tPbAxtez3V5/FP6uNx+BDjEfrlAQ1YD r8suRMLaqaX3spX4wqC1Tnp02fI/YWf1kjvNsWTF6kXwx755UjNKWUKkotlfVqQreD2g 8/Dw==
X-Received: by 10.49.130.233 with SMTP id oh9mr15054270qeb.10.1381427750039; Thu, 10 Oct 2013 10:55:50 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([200.7.87.33]) by mx.google.com with ESMTPSA id n10sm100814349qas.5.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 10:55:49 -0700 (PDT)
Message-ID: <5256EA24.5060903@gmail.com>
Date: Thu, 10 Oct 2013 15:55:48 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: manning bill <bmanning@isi.edu>
Subject: Re: leader statements
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu>
In-Reply-To: <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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, 10 Oct 2013 17:55:54 -0000

	Then we have a big problem as organization, we are then leaderless.

	That is not good for the IETF and it reflects that we are not ready for
the dynamics of the Internet that we created.

.as

On 10/10/13 3:49 PM, manning bill wrote:
> the "leaders" are there to inform and moderate the discussion and where possible, indicate
> that consensus has been reached (or not).    when "leaders" speak out on behalf of organization
> -particularly- this organization and they are _NOT_ relaying the consensus of the group at large,
> they have exceeded their remit.  
> 
> glossing over  or ignoring conflicting opinions simply because it does not reflect the "leader" bias
> is demonstrable - often to serious harm to an otherwise worthy effort.    Chairs should _NOT_  
> presume to speak for an organization without consultation.   
> 
> Concerns about "being in the room" reflect a serious insecurity in the type and quality of work that
> we are supposed to be producing. 
> 
> /bill
> 
> 
> On 9October2013Wednesday, at 13:02, Brian E Carpenter wrote:
> 
>> On 10/10/2013 08:27, Andrew Sullivan wrote:
>> ...
>>> What I am not sure about is whether people are willing to accept the
>>> chairs acting in that sort of "leader of organization" role.  If we do
>>> accept it, then I think as a consequence some communications will
>>> happen without consultation.  For a CEO is not going to agree to issue
>>> a joint communiqué with someone who has to go negotiate the contents
>>> of that communiqué (and negotiate those contents in public).  If we do
>>> not accept it, then we must face the fact that there will be meetings
>>> where the IETF or IAB just isn't in the room, because we'll have
>>> instructed the chairs not to act in that capacity.
>>
>> I've been there in the past, as IAB Chair, ISOC Board Chairman, and IETF Chair.
>>
>> Either we trust our current and future chairs, on certain occasions,
>> to speak in our name without there being a discursive debate in advance,
>> or we will have no voice on those occasions.
>>
>> If there was a pattern of I* chairs subscribing to statements that the
>> relevant community clearly found quite outrageous, there might be an
>> argument for having no voice.
>>
>> I suggest that there is no such pattern. There may be quibbles over
>> wording sometimes, but that is inevitable when several different
>> stakeholder organisations have to agree on wording. The wording is
>> inevitably a compromise; it can't be otherwise.
>>
>> It's perfectly reasonable to ask our chairs to invite debate in
>> advance when that is possible; but in many of these cases, it
>> simply isn't. It's also perfectly reasonable that people should comment
>> on the wording even after it's set in stone; that helps us to do better
>> next time.
>>
>> If we nominate good candidates for our leadership positions, and send
>> thoughtful comments to the NomCom (and the IESG and IAB for their
>> nominating duties), we won't get leaders who put their names to
>> anything outrageous.
>>
>> We should trust our chairs to act as figureheads and leaders towards
>> the outside world.
>>
>>   Brian Carpenter
>>

From bmanning@isi.edu  Thu Oct 10 10:58:32 2013
Return-Path: <bmanning@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 A178C21F9E1A for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:58:32 -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=[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 qZXSVVZ7ORUE for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 10:58:26 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id AD3D411E8176 for <ietf@ietf.org>; Thu, 10 Oct 2013 10:58:18 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r9AHv6bb026424 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 10:57:18 -0700 (PDT)
Subject: Re: leader statements (was: Montevideo statement)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: manning bill <bmanning@isi.edu>
In-Reply-To: <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
Date: Thu, 10 Oct 2013 10:57:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <75A18E39-F4E8-4E0D-ABEF-3D6150D34BF9@isi.edu>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <6.2.5.6.2.20131009152317.0c6db408@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 10 Oct 2013 17:58:32 -0000

On 10October2013Thursday, at 1:30, SM wrote:

> At 12:27 09-10-2013, Andrew Sullivan wrote:
>> Now, there is indeed a possible issue, and that is that these chairs
>> were attending a "chief officer"-type meeting: there were CEOs and so
>> on, and (presumably by analogy) the chairs got invited to represent
>> the organizations of which they are chairs.  John is quite right that
>> people unfamiliar with the way the IETF or IAB work might interpret
>> the statement along the lines of, "The CEO of the IETF said that the
>> IETF subscribes to some view."  Normally, the leader of an
>> organization can direct that organization to some end; the Chair is
>> the leader; therefore, the Chair can direct the organization.  Of
>> course, that's not how we operate (this is, I think, at the bottom of
>> this very discussion).  But others might get that impression.
>>=20
>> What I am not sure about is whether people are willing to accept the
>> chairs acting in that sort of "leader of organization" role.  If we =
do
>> accept it, then I think as a consequence some communications will
>> happen without consultation.  For a CEO is not going to agree to =
issue
>> a joint communique with someone who has to go negotiate the contents
>> of that communique (and negotiate those contents in public).  If we =
do
>> not accept it, then we must face the fact that there will be meetings
>> where the IETF or IAB just isn't in the room, because we'll have
>> instructed the chairs not to act in that capacity.
>=20
> There might be some history to the "we reject: kings, presidents and =
voting".
>=20
> Should the IETF change the way it operates?  There are advantages to =
the Chair directing the organization.  It is easier to set policy.  It =
is easier for the Chair to negotiate with other organizations.  There =
are disadvantages, for example, the policy might not reflect the wishes =
of the community.  The IETF might have to reconsider whether people =
participate as individuals or as corporate folks.
>=20
> There is the question of openness.  If the IETF were to set policy =
behind closed doors, can it say that it is open?  "We" don't take =
working group decisions behind closed doors.  The IESG tries to take its =
decisions in a transparent manner.  There may have been a time when it =
was not like that.
>=20
> As I mentioned previously the IAB [1] is supposed to be based on =
collegial responsibility.  There hasn't been any discussion to change =
that during the tenure of the last two IAB Chairs.  What's different =
now?  The IAB has published statements and RFCs about its positions.  =
The Chairs can exercise their discretion.
>=20
> The members of the IESG and the IAB have not mentioned that they do =
not have the ability to negotiate under current rules [2].  The IETF =
Chair and the IAB Chair have not mentioned that they are not able to =
negotiate due to the current rules.  The question of trust comes up =
every now and then.  Responsibility [3] seems to be an inconvenient word =
on this mailing list.
>=20
> What's the opinion of the persons who are part of "leadership" about =
all this?
>=20
> Regards,
> -sm

	well, I will stand up and claim to be part of the "leadership" - =
since this supposed to be a bottom up organization.

        the IETF has changed the way it works and we see other fora come =
into existence that reflect a true bottom up approach.  If we (the =
affected community) feel that a top down approach would be=20
        for the best, going forward,  I see no better top-down =
organization than the ITU-T.    The community will decide the relevance =
of a group that ignores or dismisses their needs.

/bill

>=20
> 1. "People outside think IAB has power  :-)"
> 2. I chose a word quickly.
> 3. the state or fact of being responsible, answerable, or accountable. =
=20


From melinda.shore@gmail.com  Thu Oct 10 11:30:33 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 70D3421F99F0 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level: 
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177,  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 FgFS0+gBtT1a for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:30:32 -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 C6D0D21E8098 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:30:31 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so2978524pbb.14 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:30:21 -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=xIG+gFsD8hx9bphOYERWuyEL50dWyqVRwXC/sior3yk=; b=zhtQeJ1x4u9Ui0gwqovfI6rLF1RTfmfgagE1EaBJC5M+W1LZ8pDloPjWme6HgL5MQE BJtpgMOqnCRvFRg+VYmy4jpkvDIwrc9rQZsGbBK9ClVYiEyjYQJMoBXH1ra0IU4UNZ79 5VZW37kURQ5vXSJ/yVmpqDQK18dKtlPub3I43Ie8sBcYz9wWegpgc938097EGw4y2RbU WZiUDo9wvVZxrRP2ymatyLmQWO8mayIstfb5xX6C7hg90tswE75JkljAxb9XwUqv902J fDNamdTSt9IssoYq6v1rPv9Yr0q168xb+V5P13th6J97pXybT8bcy8EFXzlOTJiY3rfi jJJA==
X-Received: by 10.66.170.168 with SMTP id an8mr17394741pac.58.1381429820986; Thu, 10 Oct 2013 11:30:20 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id b3sm54654023pbu.38.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 11:30:20 -0700 (PDT)
Message-ID: <5256F239.1000400@gmail.com>
Date: Thu, 10 Oct 2013 10:30:17 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: leader statements
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu>
In-Reply-To: <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu>
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, 10 Oct 2013 18:30:33 -0000

On 10/10/13 9:49 AM, manning bill wrote:
> the "leaders" are there to inform and moderate the discussion and
> where possible, indicate that consensus has been reached (or not).
> when "leaders" speak out on behalf of organization -particularly-
> this organization and they are _NOT_ relaying the consensus of the
> group at large, they have exceeded their remit.

I really think we need to stop behaving as if the IETF is a
small group of people who know each other well.  Consensus
decision-making does not scale well with the number of
participants, and if we're going to require consensus on
every leadership decision we're not going to get anything
done.  Now, being frozen and inactive may be preferable to
having Jari and Russ go off and make a cooperative public
statement about internet governance, but it seems to me that
as long as we have recall and appeals processes we have
incentives for IETF and IAB chairs, and IESG and IAB members,
not to go off and do controversial things unilaterally, as
well as a remedy if they do.

Melinda

From jari.arkko@piuha.net  Thu Oct 10 11:32:26 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 6B40721F99F0 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 J529Wlv4VnQ1 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:32:05 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DC4F421E80B9 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:31:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 66CB02CC6C; Thu, 10 Oct 2013 21:31:19 +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 M5O0jXHw-7AC; Thu, 10 Oct 2013 21:31:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 458412CC48; Thu, 10 Oct 2013 21:31:18 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Montevideo statement
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5256DE72.4010705@dcrocker.net>
Date: Thu, 10 Oct 2013 21:31:17 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD554473-CD9D-4795-A125-A4E52EAEC68D@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <5256DE72.4010705@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
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, 10 Oct 2013 18:32:26 -0000

Dave:

On IANA:

> Further, I believe there is no IETF context

RFC 6020 and =
http://www.iab.org/wp-content/IAB-uploads/2011/07/IANA-IAB-FNOI-2011.pdf

Jari


From Ted.Lemon@nominum.com  Thu Oct 10 11:33:11 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 DA3C521F9E12 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:32:48 -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 JYru1e41zg-1 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:32:34 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id E117721F8423 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:32:26 -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 DSNKUlbyrAKpFwDpzXpBG+F08oGLac0W6tQj@postini.com; Thu, 10 Oct 2013 11:32: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 519E61B82EA for <ietf@ietf.org>; Thu, 10 Oct 2013 11:32:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 3464119005C; Thu, 10 Oct 2013 11:32:12 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Oct 2013 11:32:11 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Montevideo statement
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CALw3TGGkSmxz-+HPAwqF-JAv3EZjfHPTwEgJjq3Lz+e_BRDq7g@mail.gmail.com>
Date: Thu, 10 Oct 2013 14:32:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <5796ADF9-DEAB-4FF4-B6D4-441ED7D0BD78@nominum.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <5255A905.10700@gmail.com> <CADnDZ8-vaM64D9T79XgCzgby-6TEmgsPeEvA6XfZwwUCHtX1fA@mail.gmail.com> <CALw3TGGkSmxz-+HPAwqF-JAv3EZjfHPTwEgJjq3Lz+e_BRDq7g@mail.gmail.com>
To: Medel v6 Ramirez <mgramirez@globe.com.ph>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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, 10 Oct 2013 18:33:13 -0000

On Oct 9, 2013, at 10:11 PM, Medel v6 Ramirez <mgramirez@globe.com.ph> =
wrote:
> Leaders were "processed" thoroughly prior to their appointment so I =
trust them. And that they hold through the "spirit" of being an IETF and =
shall be responsible under oath for any impact on the organization.

I don't know precisely what you mean by this, but I assure you that =
there is no oath given.   Speaking for myself, much of what I have =
learned about how to be a leader (at the AD level) in the IETF I have =
learned on the job.   This is an iterative process.   Nomcom appointees =
are not magical.   We do our best, and when we screw up the community =
corrects us, sometimes harshly, sometimes eloquently, but without fail.  =
 This is a good thing.


From carlosm3011@gmail.com  Thu Oct 10 11:48:44 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 6BF7F21E80DE for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:48:44 -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 uhl-jsNPotq4 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:48:43 -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 CA55621F9A7D for <ietf@ietf.org>; Thu, 10 Oct 2013 11:48:16 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id w16so1927952vbb.22 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:48:08 -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=Nawc0FdXaJ7QwRNJh9PmD4Bzgqr5QlqfSXeEsoC80KA=; b=CZnxMUkUjGecqg5TR743ylH5sbLvU8b0Keb0O/NZCOWEhIbXAG5VPXe9/QrhUVSHpJ RjK6aTrrYunDHLx4F3leA6CI7e4Bwl0kDasvBKgAr0Oe6pSehT5VNMQ4e5ZrPttOAvBk DMwwdFrX1PptvY1F1BRulrJFJr2zSIvRYQRIikDF+0J+LHsje69yCV1N1onpzPIvTS1D veO3mPbApytteDF/IPY1ZucvVpiLAJ5gcOK00TdpbOmJa2joPDY4YU91GSFDC/gz6T56 WvpdColvLV7oZZJtzpzO1x1rasG1q3EbliYs8hITKlpIBGQL2yhJ6AxuiFXD8hDBJo2s HxRA==
X-Received: by 10.220.47.10 with SMTP id l10mr11451279vcf.32.1381430888380; Thu, 10 Oct 2013 11:48:08 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:e5f9:36a:85ed:d59a]) by mx.google.com with ESMTPSA id lo10sm51485896vdb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 11:48:07 -0700 (PDT)
Message-ID: <5256F663.2080505@gmail.com>
Date: Thu, 10 Oct 2013 16:48:03 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: leader statements
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu> <5256F239.1000400@gmail.com>
In-Reply-To: <5256F239.1000400@gmail.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
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, 10 Oct 2013 18:48:44 -0000

Hello,

On 10/10/13 4:30 PM, Melinda Shore wrote:
> On 10/10/13 9:49 AM, manning bill wrote:
>> the "leaders" are there to inform and moderate the discussion and
>> where possible, indicate that consensus has been reached (or not).
>> when "leaders" speak out on behalf of organization -particularly-
>> this organization and they are _NOT_ relaying the consensus of the
>> group at large, they have exceeded their remit.
> 
> I really think we need to stop behaving as if the IETF is a
> small group of people who know each other well.  Consensus
> decision-making does not scale well with the number of
> participants, and if we're going to require consensus on
> every leadership decision we're not going to get anything
> done.  

Couldn't be more true. If we want the IETF to have a voice on the larger
stage then we need to trust the people we appoint. While having a public
consultation period would be ideal we need to understand, and come to
terms with, the fact that it will not be possible to have this in all cases.

Now, being frozen and inactive may be preferable to
> having Jari and Russ go off and make a cooperative public
> statement about internet governance, but it seems to me that
> as long as we have recall and appeals processes we have
> incentives for IETF and IAB chairs, and IESG and IAB members,
> not to go off and do controversial things unilaterally, as
> well as a remedy if they do.

So true, again.


> 
> Melinda
> 

Carlos

From dhc@dcrocker.net  Thu Oct 10 11:49: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 D643621E815C for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:49:51 -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 qC-fUFViXqIt for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:49:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9558E21E814F for <ietf@ietf.org>; Thu, 10 Oct 2013 11:49:02 -0700 (PDT)
Received: from [10.100.255.252] ([203.167.240.58]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9AImvuT007540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 10 Oct 2013 11:49:01 -0700
Message-ID: <5256F68D.7020509@dcrocker.net>
Date: Fri, 11 Oct 2013 07:48:45 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Montevideo statement
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <5256DE72.4010705@dcrocker.net> <BD554473-CD9D-4795-A125-A4E52EAEC68D@piuha.net>
In-Reply-To: <BD554473-CD9D-4795-A125-A4E52EAEC68D@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]); Thu, 10 Oct 2013 11:49:01 -0700 (PDT)
Cc: 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, 10 Oct 2013 18:49:55 -0000

On 10/11/2013 7:31 AM, Jari Arkko wrote:
> Dave:
>
> On IANA:
>
>> Further, I believe there is no IETF context
>
> RFC 6020 and http://www.iab.org/wp-content/IAB-uploads/2011/07/IANA-IAB-FNOI-2011.pdf


Jari,

The fact that you had to reach back 2.5 years, to a frankly rather 
obscure document that came from the IAB and not the broader IETF, 
demonstrates my point that we lacked meaningful context and, in 
particular, you lacked mandate for speaking about this on behalf of the 
IETF.


And lest the end of the above sentence be taken as too stern or 
critical, I'll point out that I think we, the IETF, have been marching 
down a path of causing our 'leaders' to feel empowered in this way -- we 
have actually been moving towards kings and voting -- and hence, again, 
this is not a criticism of you or Russ personally.  If anyone feels 
compelled to apply the word criticism here, they need to apply it to all 
of us, the IETF community.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jnc@mercury.lcs.mit.edu  Thu Oct 10 11:53:40 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 1F8D921F9C99 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:53:39 -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.000,  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 jXvyJVuM3daZ for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:53:34 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8E621F92C2 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:52:56 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3BE2A18C118; Thu, 10 Oct 2013 14:52:55 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: leader statements
Message-Id: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
Date: Thu, 10 Oct 2013 14:52:55 -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, 10 Oct 2013 18:53:40 -0000

    > From: Arturo Servin <arturo.servin@gmail.com>

    > Then we have a big problem as organization, we are then leaderless.

I'm not sure this is true. The IETF worked quite well (and produced a lot of
good stuff) back in, e.g. the Phill Gross era, when I am pretty sure Phill's
model of his job was indeed as a 'facilitator', not a 'leader' in the sense
you seem to be thinking of. So why do we now need a 'leader'?

	Noel

From melinda.shore@gmail.com  Thu Oct 10 12:00:50 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 51E1E21F9CED for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[AWL=0.163,  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 V9jBYRCWqEAp for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:00:23 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB1021F84B7 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:59:02 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id y10so3025475pdj.11 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:59:02 -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=beomFl3dXfIBYvPh3Y1B+Q2fhG/V0z18lKQk60ldBi4=; b=FXn+LZhPMQ/W1emXJrWSnd4nA90VDhSDJqrq5WCCAaw0AHx+gZbLrjK3epnMWJOmRs nif8SXoVOQDB8EdPwA+Rqjnu6wOfThl3E3N5C9UN+k7UFjHA0d281QQo4uBhIPSupmGd XglOU5ke8DDxUMEt0VvhqfB0Ehjj0RvwAyaf2NNLSeLLjH/oTRZ3w6opcyUYXaY1V6NU xxaAuliKbVKT0kmRcqFYlYQsM4H3456JuPGuJptQ3UwN9vv9COZ1ovX4K/GdpR2vMuqb soY6oI71AxT6h82dswJPQpw4RsEqWAIsyyMvHuPKmR06mYnXlQWmxhk4l0wdsGjfPvC3 XKvA==
X-Received: by 10.68.189.5 with SMTP id ge5mr15872600pbc.42.1381431542097; Thu, 10 Oct 2013 11:59:02 -0700 (PDT)
Received: from spandex.local (216-67-113-166.dynamic.dsl.acsalaska.net. [216.67.113.166]) by mx.google.com with ESMTPSA id ha10sm54787517pbc.23.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 11:59:01 -0700 (PDT)
Message-ID: <5256F8F2.4060102@gmail.com>
Date: Thu, 10 Oct 2013 10:58:58 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: leader statements
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
In-Reply-To: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
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, 10 Oct 2013 19:00:51 -0000

On 10/10/13 10:52 AM, Noel Chiappa wrote:
> I'm not sure this is true. The IETF worked quite well (and produced a lot of
> good stuff) back in, e.g. the Phill Gross era, when I am pretty sure Phill's
> model of his job was indeed as a 'facilitator', not a 'leader' in the sense
> you seem to be thinking of. So why do we now need a 'leader'?

Because we've got more than 120 working groups, thousands of
participants, and the internet is now part of the world's
communications infrastructure.  I don't like hierarchy but
I don't know how to scale up the organization without it.

Melinda



From sm@elandsys.com  Thu Oct 10 12:01:10 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 2BCCE21F9C53 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.102
X-Spam-Level: 
X-Spam-Status: No, score=-101.102 tagged_above=-999 required=5 tests=[AWL=-0.484, BAYES_00=-2.599, FRT_PROFILE2=1.981, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eC3vuRO+Mxpc for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:01:06 -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 C078A21F9D65 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:00:04 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.138.16]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9AIxVFb004391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Oct 2013 11:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381431587; bh=B9yVN/feIUJT+8AGVXwhw5Uu7p8prasJIGnA4eSXI9o=; h=Date:To:From:Subject:Cc; b=v5wQhAT/R+X8GGko2UaMLTIQTXt6j2UHTEikzDOaPfzR5trhtj9ipp5ETIhphU1LJ dwrJhxjOEZwVXgTz8JK+sAWk/8sJsI3uZ1XsmnEsj30RcgJbEHITzGEg/Uo5bhFiRg iCWrCbAvPX5eJQ5dnvtXejQ+D8ChqLEz4589Rlz4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1381431587; i=@elandsys.com; bh=B9yVN/feIUJT+8AGVXwhw5Uu7p8prasJIGnA4eSXI9o=; h=Date:To:From:Subject:Cc; b=fffrtXktgTwVJxM6rktl9qv2qRC+FZB6Nmrdnp1jG79LqU2A/Skd2bdwS58e5sDPu pyJD2kJSlbGwF+9eoDlY+gC7z7VyhyJaXcpJMxrMddg/cVoAuenI8ByYACpcRRSW5y ZnuQm2W2Sa/O+FlyNhEmLguRA1SS8vVKVEqdLkKk=
Message-Id: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Oct 2013 11:10:47 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====================_16894206==_"
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: Thu, 10 Oct 2013 19:01:10 -0000

--=====================_16894206==_
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi Jari,

Here's is a draft about improving the ISOC Fellowship programme to 
attract people from under-represented regions into the IETF.  The 
draft builds upon the ISOC work, proposing adjustments and additional 
efforts, with the goal of enabling more sustained and active 
participation by contributors from under-represented regions.

In a blog article ( http://www.ietf.org/blog/2013/04/diversity/ ), it 
is mentioned that:

  "The design team will present their recommendations to the community,
   and engage in the discussion.  Recommendations with community support
   will be taken forward."

The draft only makes suggestions instead of recommendations.  I am 
copying this message to ietf@ietf.org so that the community can 
comment about the draft.

Regards,
S. Moonesamy
--=====================_16894206==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="draft-ddt-fellowship-03.txt"

 



                                                            S. Moonesamy
                                                                        

Expires: April 13, 2014                                 October 10, 2013


       Improving the ISOC Fellowship programme to attract people
              from under-represented regions into the IETF
                        draft-ddt-fellowship-03

1. Introduction

   The IETF Chair set up a Diversity Design Team in July, 2013 to
   understand the diversity problem and suggest solutions to make the
   IETF more inclusive.  There is already an ISOC Fellowship programme
   to the IETF for participants from emerging regions.  The Fellowship
   to the IETF helps to increase the diversity of inputs to, and global
   awareness of the IETF's vital work.  This document builds upon the
   ISOC work, proposing adjustments and additional efforts, with the
   goal of enabling more sustained and active participation by
   contributors from under-represented regions.

   Section 2 lists the objectives of the existing ISOC Fellowship
   programme and the selection criteria.  The current programme does
   help new participants to establish an initial face-to-face contact. 
   However, long-term benefit requires helping these participants to
   engage in the full range of IETF interactions.  The most effective
   way to contribute to the IETF is through on-going active
   participation and by reviewing and commenting about working group
   drafts.  There are suggestions in Section 4 to better align the ISOC
   Fellowship programme with the expectations of the IETF Community by
   having selection criteria that encourages active IETF participation,
   and by having an evaluation panel with the expertise to evaluate IETF
   contributions.

2. Existing support for participants from emerging regions

2.1. Objectives of the ISOC Fellowship programme

   The Internet Society's efforts are encompassed by a basic Fellowship
   Programme and a Returning Fellowship Programme.  The Internet Society
   has provided significant financial support given that attendance by
   technologists from emerging and developing economies is currently
   limited [FEL].  It is considered that actually attending a face-to-
   face IETF meeting promotes a stronger understanding of the standards
   process, lays the foundation for active involvement in IETF work, and
   facilitates personal networking with others that have similar
   technical interests [FEL].
 


                         Expires April 13, 2014                 [Page 1]

S. Moonesamy               Attracting people            October 10, 2013


   The main purpose [FEL] of the ISOC Fellowship programme is to:

      - Raise global awareness about the IETF and its work.

      - Foster greater understanding of, and participation in, the work
        of the IETF by technologists from emerging and developing
        economies.

      - Provide an opportunity for networking with individuals from
        around the world with similar technical interests.

      - Identify and foster potential future leaders from emerging and
        developing economies

      - Demonstrate the Internet community's commitment to fostering
        greater global participation in Internet Forums such as the
        IETF.

   The goals of the ISOC Returning fellowship programme [RET] are to:

      - Provide an opportunity for highly committed former Fellows to
        return to the IETF to advance specific standards work.

      - More fully integrate technologists from emerging and developing
        economies into the IETF.

      - Advance the technical leadership potential of individuals from
        emerging and developing economies.

      - Provide immediate value to a working group by participating in
        scribing the working group meeting and contributing to the
        meeting minutes.

2.2. Selection criteria for the ISOC Fellowship programme

   Some of the requirements [SEL] for qualifying for ISOC Fellowship
   programme are:

      - Hold a university-level computer science, information
        technology, or similar degree, or can demonstrate similar and
        relevant work experience.

      - Be employed in a technical or technical management capacity with
        a data network provider (including university networks), a
        technology vendor, a local technical association, or other
        similar organisation OR be a university-level computer
        science/information technology professor, lecturer, or student
        currently undertaking research in one or more areas of current
 


                         Expires April 13, 2014                 [Page 2]

S. Moonesamy               Attracting people            October 10, 2013


        IETF standardisation work. Students must be enrolled in a
        graduate-level program (Masters or Ph.D).

      - Possess a strong understanding of how the IETF relates to and
        impacts their work or area of study and demonstrate how specific
        areas of current IETF work are relevant to their pursuits.

   Some of the attributes [SEL] that reflect favorably on the
   application are:

      - Involvement in one or more regional data networking
        organisations, such as regional operators groups

      - Having actively participated in the work of an IETF Working
        Group through the mailing lists.

   A Returning Fellowship award will not be given to the same individual
   twice in one calendar year.

3. Expectations of the IETF Community

   The current ISOC Fellowship Programme is primarily useful for initial
   introductions to IETF activities and culture.  However the goal in
   the IETF, itself, is for continuing and active participation, which
   goes considerably beyond introductions.  Moving from introduction to
   participation requires additional effort..  Although attending IETF
   meetings fosters an understanding of the work of the IETF it does not
   ensure active participation.  Active participation in the work of an
   IETF Working Group is listed as an advantage instead of a requirement
   for the fellowship [SEL].

   The existing selection criteria puts an emphasis on university-level
   qualifications and the academic interests of the applicant [SEL]. 
   However, it has been mentioned in discussions about academic
   participation that the IETF filters out proposals from researchers
   simply because they just do not fit in standardization work [DIN].

   The Returning Fellowship programme is a laudable initiative by the
   Internet Society to further encourage IETF participation from an
   under-represented sector.  It is unclear how an ISOC Fellow can build
   upon the initial -- but limited -- experiences of the basic Programme
   and Returning Fellow Programme, to achieve the Fellow's technical
   leadership potential, through on-going, active participation in the
   IETF.

4. Suggestions

4.1. Selection criteria for the basic Programme and Returning Fellow
 


                         Expires April 13, 2014                 [Page 3]

S. Moonesamy               Attracting people            October 10, 2013


   Programme

   The most effective way to contribute to the IETF is through active
   participation and by reviewing and commenting about working group
   drafts [FAA].  It is proposed that the applicant fulfills the
   following criteria:

      - Be proficient in English.

      - Has been actively and constructively participating in the IETF
        for at least six months.

        For example, reviewing drafts, commenting on IETF Last Calls,
        writing code for drafts or taking part in interop testing are
        fine ways to be seen to have participated. Candidates whose
        contributions are considered more useful should be preferred
        over those who are less useful. Judging utility for
        contributions requires knowledge of the specific field.

      - Resident of a country in an under-represented region.

4.2. Evaluation panel

   It is suggested to include Area Directors or Working Group Chairs on
   the evaluation panel [FAS].  These people will bring in the expertise
   to evaluate the contributions made by the applicant.  They can also
   determine whether the applicant has an understanding of the work done
   in the IETF.  It is suggested that the evaluation panel prioritize
   people who have been contributing over time to real IETF work.

4.3. Guidance for applicants

   Applicants can familiarize themselves with the technologies being
   discussed by, for example, implementing the relevant specifications
   or evaluating implementations [ACS].  Applicants can ask for advice
   on the edu-discuss@ietf.org mailing list [EDU].

4.4. Effectiveness of the fellowship

   The effectiveness of the fellowship can be assessed by tracking the
   IETF activities of the fellows and doing a follow-up to find out why
   fellows drop out.

5. Open Issue

   The following is left open as it may require broader feedback.

   There were comments to remove the "resident of a country in an under-
 


                         Expires April 13, 2014                 [Page 4]

S. Moonesamy               Attracting people            October 10, 2013


   represented region" suggestion (Section 4.1) so that people from
   "developed" regions who would not ordinarily have the means to attend
   an IETF meeting are included in the programme.

6. Acknowledgements

   The author would like to thank Alejandro Acosta, Adrian Farrel, Roque
   Gagliano, Vinayak Hegde and Kathleen Moriarty for contributing to the
   discussions about participation from emerging countries.  Thanks to
   Dave Crocker and Stephen Farrell for their substantial contributions
   to improve the document.

7. References

   [FEL]    Internet Society, About the Fellowship, Accessed 4 October,
            2013, <http://www.internetsociety.org/what-we-do/education-
            and-leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship-0>

   [RET]    Internet Society, Returning Fellowship to the IETF
            Programme, Accessed 4 October, 2013,
            <http://www.internetsociety.org/what-we-do/education-and-
            leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship-4>

   [SEL]    Internet Society, Selection Criteria for Fellowships to the
            IETF, Accessed 4 October, 2013,
            <http://www.internetsociety.org/what-we-do/education-and-
            leadership-programmes/ietf-and-ois-programmes/internet-
            society-fellowship/selection-criteria>

   [DIN]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00344.html>

   [FAA]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00339.html>

   [FAS]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00337.html>

   [ACS]    <http://www.ietf.org/mail-
            archive/web/diversity/current/msg00355.html>

   [EDU]   <https://www.ietf.org/mailman/listinfo/edu-discuss>

8. Author's Address


 


                         Expires April 13, 2014                 [Page 5]

S. Moonesamy               Attracting people            October 10, 2013


   S. Moonesamy

   Email: sm+ietf@elandsys.com
















































                         Expires April 13, 2014                 [Page 6]

--=====================_16894206==_--


From jnc@mercury.lcs.mit.edu  Thu Oct 10 12:17:15 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 A54F121E805F for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:17: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 HhxSKZHDxbp9 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:17:10 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id AD66221F8D0B for <ietf@ietf.org>; Thu, 10 Oct 2013 12:15:34 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0A10118C118; Thu, 10 Oct 2013 15:15:34 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: leader statements
Message-Id: <20131010191534.0A10118C118@mercury.lcs.mit.edu>
Date: Thu, 10 Oct 2013 15:15:34 -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, 10 Oct 2013 19:17:15 -0000

    > From: Melinda Shore <melinda.shore@gmail.com>

    >> The IETF worked quite well (and produced a lot of good stuff) back in,
    >> e.g. the Phill Gross era, when I am pretty sure Phill's model of his
    >> job was indeed as a 'facilitator', not a 'leader' in the sense you
    >> seem to be thinking of.

    > Because we've got more than 120 working groups, thousands of
    > participants ... I don't like hierarchy but I don't know how to scale
    > up the organization without it.

I don't believe this necessarily invalidates my point.

Yes, a larger organization will need to make organizational changes (scaling
factors apply not just in protocols), but it is not at all clear that this
includes changing the role of the leaders from 'facilitators' to 'they chose
the direction, the rest of us follow' (which is what the original post seemed
to imply was needed).

	Noel

From abdussalambaryun@gmail.com  Thu Oct 10 12:31:19 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 35AEC21F93BF for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:31:19 -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, 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 fcZT22Fg5CLr for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:31:17 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 851A621F9E63 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:31:17 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id g10so3047046pdj.2 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:31: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=iA93fwwN8i+q0elKjGDVShHMZXk/taja7ouRiqx1oKM=; b=pVjQeQMcn9qLBl6wv1lmaiZueLWTXuoue7tm/4kS+yBb8R2AVI7Q1oNTDlv4eFy0Qp 6CquA4EcRw9Pro2g1ZIkiVM0tUhjCSIvDvmBLApPyYkAyrh4y4gHw+lBUEN3/SJfe0CA GjVOKD5dYXmJau1y8VNOEpMaWIuzL6hU0bUnzjVhlzzivCz3VGJyKeFt4s3bwO0iIzgo 90t22dcM5A+jW5RvxbSQDSE7I1FTPID+biC7zRPsDQWW98h/xyrk497cqA5MzTIF18QB 5QDQTjh+kgG8ats50LikleFgD7nR6c27m3joe8PTpVBa+GWZ0j4umw7qNnoRL+EqSRCf DJAg==
MIME-Version: 1.0
X-Received: by 10.66.162.167 with SMTP id yb7mr17621552pab.16.1381433477144; Thu, 10 Oct 2013 12:31:17 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Thu, 10 Oct 2013 12:31:17 -0700 (PDT)
In-Reply-To: <5256DE72.4010705@dcrocker.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <5256DE72.4010705@dcrocker.net>
Date: Thu, 10 Oct 2013 20:31:17 +0100
Message-ID: <CADnDZ8_dkwGdeVrpLoFVXqNhEU8=s6RCUt_i5+XmUE=vc+CWXQ@mail.gmail.com>
Subject: Re: Montevideo statement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7bacbe70afaa5704e8680bf8
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, 10 Oct 2013 19:31:19 -0000

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

I like your approach and comments, and I think that our ietf leaders are
not always leaders but in IESG they are the managers.  Mostly ietf ruled by
community consensus not presidents, so we have many leaders including you
and some others may be additional leaders for the community. The ietf wants
feedback because there are not less than 50 leaders in ietf that lead the
Internet community or leaders that make/discover things for the community
when they participate.

I really want to say the important thing about leaders that they have
followers (not statements). Managers have workers and they may represent
organisation decisions and statements. The body that is managing the
decisions of ietf can make representation statements, but leader statements
has no value if there is no followers. Therefore, IMO, if there is no time
for asking feedback of community then the IETF chair can ask the IESG, to
support such represent statement. Otherwise we wait to review the community
feedback for two weeks.

AB

On Thursday, October 10, 2013, Dave Crocker wrote:

>
> Folks,
>
> There are a few things that we should consider rather more carefully
> than we've been doing, beyond a few of the postings. (I'd especially like
> to suggest that there be more careful review of Andrew Sullivan's postings
> on the thread, since he raises essential point, in my view.)
>
> In any event:
>
>      1. In spite of calling itself a press release (at the bottom) and
> having gone through an ISOC media person, what was released was not a
> press release.   Neither in form nor substance.  Its title says
> "statement", and the bottom list of people is in the style of a
> signature list, rather than merely listing attendees -- and note that Jari
> does characterize this as being signed.  Hence what was released was in the
> style of a formal statement, issued under the control of its signatories.
>
>      2. The statement does not merely say that these folk met and
> discussed stuff.  It says they agreed to stuff, or at leased "called for"
> stuff.
>
>      3. These people were acting as representatives of their
> organizations; hence the use of their titles.  And the statement does
> not explicitly say they were speaking only for themselves.  So their
> agreement to the Statement needs to be taken as their speaking for their
> organizations.
>
>      4. Having both IETF Chair and IAB Chair makes it look like there were
> two organizations being represented, but in practical terms there really
> weren't.
>
>      5. It has been noted that the IAB is largely autonomous for something
> like this; hence the IAB Chair formally only has to answer to the IAB
> itself, and we are told he was in this case.  What this begs is a question
> about the IAB acting independently of the IETF community...
>
>
> My initial reading of the Statement was that it was quite benign, so
> that any concern about it's speaking for the IETF was purely a matter of
> principle.  In that regard, I considered it a nice test case for some
> basic IETF discussion of the authority of our 'leaders' to make statements
> on our behalf but without our review or approval.  Then I re-read the
> statement more carefully and landed on:
>
>  They called for accelerating the globalization of ICANN and IANA
>> functions, towards an environment in which all stakeholders,
>> including all governments, participate on an equal footing.
>>
>
>     5.  It's not at all clear what "accelerating the globalization" means
> here, since the statement offers no context for whatever 'globalization'
> efforts with ICANN and IANA are happening.  Worse, this item is entirely
> political, involving organizations with which the IETF has on-going
> agreements and reliance.  Further, I believe there is no IETF context --
> nevermind consensus -- for the topic.  As far as I know the IETF has no
> basic discomfort with its relationship with IANA, for example.  We might
> individually make guesses about what this item in the Statement means, but
> my point is that a) we shouldn't have to, and b) it has no context within
> the IETF community.  For any of our 'leaders' to make agreements on our
> behalf, about political issues of organizations with which we have formal
> arrangements -- and probably any other organizations -- is significantly
> problematic.
>
>
> As has been noted, there are practical and formal limits to requirements
> for getting IETF rough consensus.  Any constraints on public statements by
> IETF leaders needs to balance against those limits, if we are to allow folk
> to speak publicly at all.
>
>      6. The realities of trying to get IETF community rough consensus
> means that anything requiring timely action cannot seek formal consensus.
>  To that end, we need to distinguish between 'review' and 'approval'.  IETF
> community review can be very quick indeed, though probably not less than 24
> hours, if the range of review comments is to be a good sampling of the
> community.  In the current example, community review quickly noted the
> erroneous phrasing that confuses concern about disclosure of an act from
> concern about the act itself.  (I'm working on the assumption that the
> Montevideo group is really more concerned that monitoring was/is taking
> place than that someone made this fact public...)
>
>
> Now to a more basic issue.  It's likely to be uncomfortable, but I'll
> stress that this isn't about individual people.  Fortunately, no sane
> person can have any concerns about the intent of either of the IETF folk
> who participated in this event and its resulting Statement.  So what
> follows is about IETF roles, responsibilities and authorities, not about
> individuals...
>
> What does it mean to be a 'leader' in the IETF, who is Chair of the IETF
> or the IAB?  Unlike CEOs and Presidents and Chairs of corporations, IETF
> leaders mostly don't lead.  They don't set work agendas. They don't control
> overall budgets.  They don't hire and fire people.  For almost all of the
> formal IETF 'decisions' they participate in, it is with exactly one vote in
> a group, and not more authority than that.  (And by the way, the IESG
> largely does not 'steer' the IETF.  Initiatives for work come from the
> community and very nearly never from ADs or the IESG.)
>
> IETF leaders are best viewed as facilitators, rather than leaders.  They
> do huge amounts of organizing, coordinating, interfacing, in the classic
> style of the cliche'd 'shepherding cats'.
>
> So when they speak on our behalf, it really does need to be an accurate
> rendition of IETF community views and not merely their guesses of those
> views or their hopes of what those views might or should be.
>
>      7. The released Statement was formulated by the group including two
> IETF 'leaders'.  It was not subject to random formulation by a reporter, or
> the like.  When people holding formal IETF roles participate in the
> formulation of formal Statements, things need to be carefully based on
> actual IETF community views.
>
>
> We need to find some sort of language that gives constructive guidance and
> constraint about public representations of the IETF, by our 'leaders'.  Not
> very long ago, there was a concern raised by Pete Resnick, when an IETF
> working group chair made statements at an ITU gathering and represented
> himself as an IETF wg chair.  We might want to review whatever guidance
> came out of that.
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

I like your approach and comments,=A0and I=A0think that our ietf leaders ar=
e not always leaders but in IESG they are the=A0managers. =A0Mostly ietf ru=
led by community consensus not presidents, so we have many leaders includin=
g you and some=A0others may be additional=A0leaders for the community. The =
ietf=A0wants feedback because there are not less than 50=A0leaders in ietf =
that lead the Internet=A0community or leaders that make/discover things for=
 the community when they participate.<div>
<br></div><div>I really want to say the important thing about=A0leaders tha=
t they have followers (not statements). Managers have workers and they may =
represent organisation decisions and statements. The body that=A0is managin=
g the decisions of ietf can make representation statements, but leader stat=
ements has no value if there is no followers. Therefore, IMO, if there is n=
o time for asking feedback of community then the IETF chair can ask the IES=
G, to support such represent=A0statement. Otherwise we=A0wait to review=A0t=
he community feedback=A0for two weeks.</div>
<div><br></div><div>AB<br><br>On Thursday, October 10, 2013, Dave Crocker  =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><br>
Folks,<br>
<br>
There are a few things that we should consider rather more carefully<br>
than we&#39;ve been doing, beyond a few of the postings. (I&#39;d especiall=
y like to suggest that there be more careful review of Andrew Sullivan&#39;=
s postings on the thread, since he raises essential point, in my view.)<br>

<br>
In any event:<br>
<br>
=A0 =A0 =A01. In spite of calling itself a press release (at the bottom) an=
d<br>
having gone through an ISOC media person, what was released was not a<br>
press release. =A0 Neither in form nor substance. =A0Its title says<br>
&quot;statement&quot;, and the bottom list of people is in the style of a<b=
r>
signature list, rather than merely listing attendees -- and note that Jari =
does characterize this as being signed. =A0Hence what was released was in t=
he style of a formal statement, issued under the control of its signatories=
.<br>

<br>
=A0 =A0 =A02. The statement does not merely say that these folk met and<br>
discussed stuff. =A0It says they agreed to stuff, or at leased &quot;called=
 for&quot; stuff.<br>
<br>
=A0 =A0 =A03. These people were acting as representatives of their<br>
organizations; hence the use of their titles. =A0And the statement does<br>
not explicitly say they were speaking only for themselves. =A0So their<br>
agreement to the Statement needs to be taken as their speaking for their<br=
>
organizations.<br>
<br>
=A0 =A0 =A04. Having both IETF Chair and IAB Chair makes it look like there=
 were two organizations being represented, but in practical terms there rea=
lly weren&#39;t.<br>
<br>
=A0 =A0 =A05. It has been noted that the IAB is largely autonomous for some=
thing like this; hence the IAB Chair formally only has to answer to the IAB=
 itself, and we are told he was in this case. =A0What this begs is a questi=
on about the IAB acting independently of the IETF community...<br>

<br>
<br>
My initial reading of the Statement was that it was quite benign, so<br>
that any concern about it&#39;s speaking for the IETF was purely a matter o=
f<br>
principle. =A0In that regard, I considered it a nice test case for some<br>
basic IETF discussion of the authority of our &#39;leaders&#39; to make sta=
tements on our behalf but without our review or approval. =A0Then I re-read=
 the statement more carefully and landed on:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
They called for accelerating the globalization of ICANN and IANA<br>
functions, towards an environment in which all stakeholders,<br>
including all governments, participate on an equal footing.<br>
</blockquote>
<br>
=A0 =A0 5. =A0It&#39;s not at all clear what &quot;accelerating the globali=
zation&quot; means here, since the statement offers no context for whatever=
 &#39;globalization&#39; efforts with ICANN and IANA are happening. =A0Wors=
e, this item is entirely political, involving organizations with which the =
IETF has on-going agreements and reliance. =A0Further, I believe there is n=
o IETF context -- nevermind consensus -- for the topic. =A0As far as I know=
 the IETF has no basic discomfort with its relationship with IANA, for exam=
ple. =A0We might individually make guesses about what this item in the Stat=
ement means, but my point is that a) we shouldn&#39;t have to, and b) it ha=
s no context within the IETF community. =A0For any of our &#39;leaders&#39;=
 to make agreements on our behalf, about political issues of organizations =
with which we have formal arrangements -- and probably any other organizati=
ons -- is significantly problematic.<br>

<br>
<br>
As has been noted, there are practical and formal limits to requirements fo=
r getting IETF rough consensus. =A0Any constraints on public statements by =
IETF leaders needs to balance against those limits, if we are to allow folk=
 to speak publicly at all.<br>

<br>
=A0 =A0 =A06. The realities of trying to get IETF community rough consensus=
 means that anything requiring timely action cannot seek formal consensus. =
=A0To that end, we need to distinguish between &#39;review&#39; and &#39;ap=
proval&#39;. =A0IETF community review can be very quick indeed, though prob=
ably not less than 24 hours, if the range of review comments is to be a goo=
d sampling of the community. =A0In the current example, community review qu=
ickly noted the erroneous phrasing that confuses concern about disclosure o=
f an act from concern about the act itself. =A0(I&#39;m working on the assu=
mption that the Montevideo group is really more concerned that monitoring w=
as/is taking place than that someone made this fact public...)<br>

<br>
<br>
Now to a more basic issue. =A0It&#39;s likely to be uncomfortable, but I&#3=
9;ll stress that this isn&#39;t about individual people. =A0Fortunately, no=
 sane person can have any concerns about the intent of either of the IETF f=
olk who participated in this event and its resulting Statement. =A0So what =
follows is about IETF roles, responsibilities and authorities, not about in=
dividuals...<br>

<br>
What does it mean to be a &#39;leader&#39; in the IETF, who is Chair of the=
 IETF or the IAB? =A0Unlike CEOs and Presidents and Chairs of corporations,=
 IETF leaders mostly don&#39;t lead. =A0They don&#39;t set work agendas. Th=
ey don&#39;t control overall budgets. =A0They don&#39;t hire and fire peopl=
e. =A0For almost all of the formal IETF &#39;decisions&#39; they participat=
e in, it is with exactly one vote in a group, and not more authority than t=
hat. =A0(And by the way, the IESG largely does not &#39;steer&#39; the IETF=
. =A0Initiatives for work come from the community and very nearly never fro=
m ADs or the IESG.)<br>

<br>
IETF leaders are best viewed as facilitators, rather than leaders. =A0They =
do huge amounts of organizing, coordinating, interfacing, in the classic st=
yle of the cliche&#39;d &#39;shepherding cats&#39;.<br>
<br>
So when they speak on our behalf, it really does need to be an accurate ren=
dition of IETF community views and not merely their guesses of those views =
or their hopes of what those views might or should be.<br>
<br>
=A0 =A0 =A07. The released Statement was formulated by the group including =
two IETF &#39;leaders&#39;. =A0It was not subject to random formulation by =
a reporter, or the like. =A0When people holding formal IETF roles participa=
te in the formulation of formal Statements, things need to be carefully bas=
ed on actual IETF community views.<br>

<br>
<br>
We need to find some sort of language that gives constructive guidance and =
constraint about public representations of the IETF, by our &#39;leaders&#3=
9;. =A0Not very long ago, there was a concern raised by Pete Resnick, when =
an IETF working group chair made statements at an ITU gathering and represe=
nted himself as an IETF wg chair. =A0We might want to review whatever guida=
nce came out of that.<br>

<br>
d/<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</blockquote></div>

--047d7bacbe70afaa5704e8680bf8--

From brian.e.carpenter@gmail.com  Thu Oct 10 12:38: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 7D7F321F8266 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 38wVwVDgmaDA for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:38:25 -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 93E1821F853A for <ietf@ietf.org>; Thu, 10 Oct 2013 12:38:04 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so3041075pbb.38 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:38:04 -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=HfGZ7vrqCfXyotE4y2vraATN/MuyB6kWI8YBAKIARUc=; b=jWfMjgJpQCSGjoGbHZywAzO5ZfCBUDcwSDk1phaWy4NXyhq/jqzEXpjYUqG/sQpcje RewQ7S+alb+Y8PpKUP2tDYY+UQBfRrjXsc32lwrbaEMoXupdhUiOoQXWO4QXMNFOcDd1 +myGy5pE4r2G0fB/KvDHGseTdxa3AofVRORHgY/1U4k7Dsakr50UGXR0ueqS4wEM2fAl dsjmE6ifw6XhvGjNfBaSp+Rgnw1JwsXa1iIx9av56+KzIX/GlMkhAbe180cgjprv6awa PM6eM/g0ZVAhFSDp3OKQDDGsF4u2+NroyrwHvr7A3HBSBYPXkD4TWJAmZ+qAFu9bDh24 d6JA==
X-Received: by 10.66.177.71 with SMTP id co7mr4998165pac.181.1381433884396; Thu, 10 Oct 2013 12:38:04 -0700 (PDT)
Received: from [192.168.178.20] (167.201.69.111.dynamic.snap.net.nz. [111.69.201.167]) by mx.google.com with ESMTPSA id ed3sm54951949pbc.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 12:38:03 -0700 (PDT)
Message-ID: <52570222.5090601@gmail.com>
Date: Fri, 11 Oct 2013 08:38:10 +1300
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: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: leader statements
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
In-Reply-To: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
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, 10 Oct 2013 19:38:38 -0000

On 11/10/2013 07:52, Noel Chiappa wrote:
>     > From: Arturo Servin <arturo.servin@gmail.com>
> 
>     > Then we have a big problem as organization, we are then leaderless.
> 
> I'm not sure this is true. The IETF worked quite well (and produced a lot of
> good stuff) back in, e.g. the Phill Gross era, when I am pretty sure Phill's
> model of his job was indeed as a 'facilitator', not a 'leader' in the sense
> you seem to be thinking of. So why do we now need a 'leader'?

We have a collective leadership, which is quite a good system as long as
it avoids groupthink, and I think the IETF community is talkative enough
to reduce (not eliminate) that risk. But when we're invited to wider
inter-organisation meetings, we can't all go, and the ones who do go
are certain to be viewed as our leaders by the other organisations.

Inevitably, it's the Chairs who get invited; up to them to delegate
if they want.

  Brian

From hallam@gmail.com  Thu Oct 10 12:42: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 3D25D21F9EE1 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level: 
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.023,  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 PIVqR9akFrqL for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:42:37 -0700 (PDT)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) by ietfa.amsl.com (Postfix) with ESMTP id 553D821F8B04 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:42:13 -0700 (PDT)
Received: by mail-lb0-f177.google.com with SMTP id w7so2514772lbi.22 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:41: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=Un5ECCj52ss4hzTZgCADCr0i+dNqthoBvArVUguZvvM=; b=IQR89IyL2uOqo5kao1vEqINfiilC4wwQK+fdnszMUJltN96PTNQdLuR2CLGQi7W6oD coaj4v50iJ+dYinlxkL293E854+Rh3nt09KsMGxN9dsI/yizuEeN49O0pv+S7Kml8XtT PPSldWKh7jbZfC2eSXGROuc1rPYlAuqiIURa81uI3T4UBWdKMFjP64H9yeMWr2hNmKYW se1ZAaPJ+GTtowngeW6+AwjXXH8/c+ZxYkIFXCQP33LlCzvI+f47S87pdchUgUpxoZTa 6smIu6WHqz8FywIakozcQQ2Cd0urhmQuWn/mlEwzSBY9UCfnAttm555ZroygIg3SNIpm Mm6Q==
MIME-Version: 1.0
X-Received: by 10.112.57.49 with SMTP id f17mr13469339lbq.26.1381434118050; Thu, 10 Oct 2013 12:41:58 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Thu, 10 Oct 2013 12:41:57 -0700 (PDT)
In-Reply-To: <52570222.5090601@gmail.com>
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu> <52570222.5090601@gmail.com>
Date: Thu, 10 Oct 2013 15:41:57 -0400
Message-ID: <CAMm+LwhJhjkCzJWt5-ktmcQaeBVb8dU9B1b_ngbzL9j9eZ5rYw@mail.gmail.com>
Subject: Re: leader statements
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133eacae319ba04e8683122
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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, 10 Oct 2013 19:42:39 -0000

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

To have a leader there must be followers. Ergo there are no IETF leader
statements.

--001a1133eacae319ba04e8683122
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">To have a leader there must be followers. Ergo there are no IETF leader statements.</div>

--001a1133eacae319ba04e8683122--

From johnl@iecc.com  Thu Oct 10 12:45:12 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 35A4F11E81B1 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.254
X-Spam-Level: 
X-Spam-Status: No, score=-102.254 tagged_above=-999 required=5 tests=[AWL=0.345, 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 0QnQNi9tClhm for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 12:44:58 -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 A544211E8187 for <ietf@ietf.org>; Thu, 10 Oct 2013 12:44:04 -0700 (PDT)
Received: (qmail 87635 invoked from network); 10 Oct 2013 19:43:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Oct 2013 19:43:40 -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=5257036c.xn--hew.k1309; i=johnl@user.iecc.com; bh=B+H2BUpHG3cLv8HAOVqe1srjUbmUpavOxIRs0KdNOO4=; b=n3M0d2L9ataVylk+wsIGNG1iB4zCyoHa/zVGvNT1PRFDbTW4Oqq9VlMQCWsGBFI8bYRxWAfOzJVQGtNqxL05RDlvRZYqtTQGL6N9e1OBukmayVrCEdJFnTwV2XD/Wb/sCUqgYg1H/58L30ta60MWMLII004wLEFuK4wjHRut07+BWGpUdO7KjnepEkvEBP00+KJN5zNNB2RRht/eVGw0RqMOn1ZfFL897wbVCSCoYJs8ksSQWEubCJseJZ+RTZ1u
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=5257036c.xn--hew.k1309; olt=johnl@user.iecc.com; bh=B+H2BUpHG3cLv8HAOVqe1srjUbmUpavOxIRs0KdNOO4=; b=V6IsvO8AiXIejzeMOL9WSfNWO7qgeLna7ImqT1aMrWtvkNsaQmzTQgBem/9NchNXx4YxBf0gnB8tsQ1Pwgx5SJLI6nuj88vIul+TL2fpZPuDKW3XRbKt7FuJebc/crA/7J3Mow6E2NWCKws0l5fGeH/SEGNtPEKQEP7c0xViU9MC7UZQbDe6oEpeq8/2byPa6qMDhoOUn+Ex7FqVaItfrFYWanC+Ng9H1+zxdEWNHz1+DUu+fzTMRr7Ku6Hd21VX
Date: 10 Oct 2013 19:43:18 -0000
Message-ID: <20131010194318.14443.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: consensus, was leader statements
In-Reply-To: <5256F8F2.4060102@gmail.com>
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: Thu, 10 Oct 2013 19:45:13 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>Because we've got more than 120 working groups, thousands of
>participants, and the internet is now part of the world's
>communications infrastructure.  I don't like hierarchy but
>I don't know how to scale up the organization without it.

There are largish organizations that work by consensus, notably Quaker
meetings and their regional and national organizations.  But we are
not like the Quakers.  For one thing, they have long standing
traditions of how consensus works, including a tradition of "standing
aside" and not blocking consensus if you disagee but see that most
people agree in good faith.  For another, they are very, very patient.
The meeting in Ithaca NY, near where I live, took ten years to decide
about getting their own meeting house rather than rented space.  

I don't see us as that disciplined or that patient (including myself,
I'm not a Quaker, but married to one.)

So it is a reasonable question how an organization like the IETF can
govern itself.  My inclination is to be careful in the choice of
leadership, and then trust the leaders to act reasonably.

R's,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iEYEARECAAYFAlJXA2oACgkQkEiFRdeC/kXbFACfYcKTHPfjK3yFvyGvydHZB0jx
z6AAn23U7x2tygklXyGav0DuYWjEdAvV
=s3DJ
-----END PGP SIGNATURE-----

From cgriffiths@gmail.com  Thu Oct 10 12:46:38 2013
Return-Path: <cgriffiths@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 0170F11E81C9; Thu, 10 Oct 2013 12:46: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 IntFI0mqsBpJ; Thu, 10 Oct 2013 12:46:34 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id BC83911E8181; Thu, 10 Oct 2013 12:44:58 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id k4so2155qaq.18 for <multiple recipients>; Thu, 10 Oct 2013 12:44:48 -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; bh=QGZHA1zCAwCAZUDr/kuGXwLbNNSsT1D79OG01YFdT2k=; b=g7qd6UrMRdDE9TmYqylcb5GPwjQB27JHipUX/FtzV/4deicGH/Dx3wLZiXjSPlxFTN p7kiUWt60H5PzuJ2Dg83j1UkOY0K+dWTboHOpBrzHuEG9O+6JOcZtzsPSGfC35HP6/Eg xM7Y683OL+/VYHP+7HCSSS3lJ1JiOrZgB5MjKvTE51kcZazkUwWpkmICj/wNBcJq1CHc +63AJfbc4tjbjb7f5s939Zw7BpEJn9IWV4BDtj0zsKWrFZh0SXNl/rovF+a2XRPQPO3L Kr9I6zvLsYHPFCW+bMYb9rkBvOleHl/GKfF/478ARB0r73uO+nyXq8gwMZXJCg2yjlMo QiZg==
X-Received: by 10.49.30.227 with SMTP id v3mr3516272qeh.92.1381434288057; Thu, 10 Oct 2013 12:44:48 -0700 (PDT)
Received: from [192.168.1.106] (pool-173-49-195-187.phlapa.fios.verizon.net. [173.49.195.187]) by mx.google.com with ESMTPSA id jw9sm3078040qeb.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 12:44:46 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_DB5F63BC-DFB0-47D2-BD50-A51781BF5465"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Chris Griffiths <cgriffiths@gmail.com>
In-Reply-To: <07f701cec51a$6cc16bc0$46444340$@olddog.co.uk>
Date: Thu, 10 Oct 2013 15:44:44 -0400
Message-Id: <8F12D4C7-A5A5-436D-B92F-3885A40EAE4A@gmail.com>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<6.2.5.6.2.20130924135945.0d561cd0@resistor.net>	<9824D1EA-EDAA-4BFB-A9D0-A0AFEAE546CD@gmail.com> <C8BCDFAF-EBAC-4D0F-AD80-8320F22B9FF3@gmail.com> <07f701cec51a$6cc16bc0$46444340$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1510)
Cc: 'Trustees Trustees' <trustees@ietf.org>, 'SM' <sm@resistor.net>, 'John C Klensin' <klensin@jck.com>, 'Nevil Brownlee' <n.brownlee@auckland.ac.nz>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Oct 2013 19:46:38 -0000

--Apple-Mail=_DB5F63BC-DFB0-47D2-BD50-A51781BF5465
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Oct 9, 2013, at 2:07 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi Chris,
>=20
> I have become confused between the permission necessary to republish =
the Tao,
> and the request to republish under a Creative Commons license.
>=20
> Can I try to clarify.
>=20
> Do we or do we not grant permission for others to publish the Tao and =
the
> translations of the Tao under section 3c of the TLP at
> http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf ?
>=20
> Thanks and sorry for dragging this on.

Hi Adrian,

Yes we do indeed grant others to publish the Tao under the existing =
license, we however cannot grant the license to republish it under =
Creative Commons based on legal advice, and there is currently no =
community support to change that per my original message.  I hope that =
helps.

Thank you

Chris




--Apple-Mail=_DB5F63BC-DFB0-47D2-BD50-A51781BF5465
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSVwOwAAoJEE4wr5snmnsMHRUH/07rPfiORChLHdx28+i716QH
yn5//qgJOKvmiYKYqAuIWrpLk8XuFLN5gJ043J6++yhIWgwzIt6euq9sYnbqubId
RF7aMqKZxYf1Y1H8cko0X07tKQ9ZAz9NuuQvg+29S7NYylFY4Qj12m/xKLn0KA/z
7ReMkhfQ1IX03ZOMKM8bQIdaGPrs1Y2UMmjHsEKmm5iatZqfXLhryZd3R3uJ7WSo
nvEbTLGnfliEB42qPzYLCJ70sSFTOrW4E3aNkTcMVxH39nTS7ENCPdevNhl5FEsy
G7l4HQauGL4nI7gxndmQW6GN0XBWOMtFM1jqqTyZRdYuMcBPbSds0m7OW3Mv8oY=
=Ye2F
-----END PGP SIGNATURE-----

--Apple-Mail=_DB5F63BC-DFB0-47D2-BD50-A51781BF5465--

From doug.mtview@gmail.com  Thu Oct 10 13:06:56 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 94CD211E8181 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:06: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 c2ts5ocubWRM for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:06:56 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D685A11E8183 for <ietf@ietf.org>; Thu, 10 Oct 2013 13:06:55 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so3079596pdj.6 for <ietf@ietf.org>; Thu, 10 Oct 2013 13:06:49 -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; bh=R21H/SIH8IkqtvczYU8FxxQRQT65d3oBcX0C7K/oKQ4=; b=WxgnGKw+5EoQgH48c/n7HINRZS6gayomzHWKWXutViUYGF6IF+nQRHf5AVHseOKi+L IW3OxzGCJmpd9WmY5pDdSQVj5ZOXhNUJn2ncDz46IkUOTjXE4QUV0HdYQSyKd4oX4bS1 SGSSxEH251sHvNpolxHpnrxHz86enzW2d4dwMltgroa8vmECrsJQwwkfyxpcMjJA0Nmz 3PRzS3jcb+ISXdeE9lN7QACSTuuNa73zYggrkWHjYDpoJtZ1F7Bw4xdqS1RA5rBhcjD3 Jtr0sa2QxF7FGmVrHmnJkwfMGbhfc+6yZD78J14MPaKsEK5q3K2kLB26WHCWP3xwrW6R Zr7A==
X-Received: by 10.66.146.199 with SMTP id te7mr17779351pab.106.1381435609709;  Thu, 10 Oct 2013 13:06:49 -0700 (PDT)
Received: from [192.168.2.233] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id q4sm55034887pba.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 13:06:48 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: leader statements
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
Date: Thu, 10 Oct 2013 15:06:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <284FD9C5-AF6A-422E-9159-8585D3000DAD@gmail.com>
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Mailer: Apple Mail (2.1510)
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, 10 Oct 2013 20:06:56 -0000

On Oct 10, 2013, at 1:52 PM, jnc@mercury.lcs.mit.edu (Noel Chiappa) =
wrote:

>> From: Arturo Servin <arturo.servin@gmail.com>
>=20
>> Then we have a big problem as organization, we are then leaderless.
>=20
> I'm not sure this is true. The IETF worked quite well (and produced a =
lot of
> good stuff) back in, e.g. the Phill Gross era, when I am pretty sure =
Phill's
> model of his job was indeed as a 'facilitator', not a 'leader' in the =
sense
> you seem to be thinking of. So why do we now need a 'leader'?

Agreed.

To quote Alan Greenspan about the 2008 economic debacle-

"And the answer is that we're not smart enough as people. We just cannot =
see events that far in advance. And unless we can, it's very difficult =
to look back and say, why didn't we catch something?"

Couple human limitations with a desire to accept questionable =
justifications at bypassing concerns driven by leadership notoriety for =
pushing a group's agenda.  A common symptom is to declare objections to =
be from an aberrant individual, even when also expressed by others.  The =
IETF must remain critical of its process and its leadership to better =
avoid future debacles.

Regards,
Douglas Otis
=20
 =20



From dhc@dcrocker.net  Thu Oct 10 13:26: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 AAF5311E8126 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:26: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 kUsSf2IgeYQ2 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:26:14 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5C311E818D for <ietf@ietf.org>; Thu, 10 Oct 2013 13:25:42 -0700 (PDT)
Received: from [10.100.255.252] ([203.167.240.58]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9AKPYsV009961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 10 Oct 2013 13:25:38 -0700
Message-ID: <52570D32.9020107@dcrocker.net>
Date: Fri, 11 Oct 2013 09:25:22 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net>
In-Reply-To: <508943C8-BE40-4128-9B70-6CB568FC82D3@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]); Thu, 10 Oct 2013 13:25:40 -0700 (PDT)
Cc: Pete Resnick <presnick@qti.qualcomm.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: Thu, 10 Oct 2013 20:26:29 -0000

On 10/7/2013 10:03 AM, Jari Arkko wrote:
> The abstract says:
>
> The IETF has had a long tradition of doing its technical work
> through a consensus process, taking into account the different views
> among IETF participants and coming to (at least rough) consensus on
> technical matters.  In particular, the IETF is supposed not to be
> run by a "majority rule" philosophy.  This is why we engage in
> rituals


As I noted in my review of the draft, the document has a core flaw in
its sense of history.  It has invented an interpretation of "rough
consensus" that was not part of its original formulation.

I consider the current focus on reconciling minority views to be quite 
an excellent enhancement to that original interpretation, but it really 
is an addition.  In classic IETF fashion, documenting that enhancement 
flows from common -- though not universal -- IETF practice that has 
emerged, and it likely to produce better consistency to the current, ad 
hoc behavior.  But we need to stop asserting the meaning of "rough 
consensus" to have always or obviously included this.

Part of the confusion about the history is over-interpreting the context 
the phrase was used.  Dave Clark drew a contrast against 'voting'. 
Voting is a mechanical counting process, with formal lines of 
distinction, whether a simple model like 51% or 67%, or the like, or 
something more complex.  But it's based on a strict counting of votes 
and a strict model for using them.

By contrast, the phrase "rough consensus" simply meant that there is 
massive support, and leaves the determination of 'massive' to subjective
processes.  If something has massive support, it is likely to get
implemented, deployed and used.  If it doesn't, the formalities of a
voting mechanism won't help it succeed in the marketplace.  The idea 
that voting will suffice for this concern by simply moving the thresh 
hold to some sort of super-majority imposes an artificial precision; the 
idea behind rough consensus is the subject sense that there is obviously 
'enough' support.

I believe the IETF has only two documents that talk about the meaning of
rough consensus.  The first is Working Group Guidelines and Procedures
that was originally written by Erik Huizer and myself; Scott Bradner's
update to the document didn't change this part of it.  And the relevant
text was something I wrote rather carefully, since the construct was new 
and quite unusual for a standards group:

      http://tools.ietf.org/html/rfc1603#section-3.2

> 3.3. Session management
>
>
> Working groups make decisions through a "rough consensus" process.
> IETF consensus does not require that all participants agree although
> this is, of course, preferred.  In general the dominant view of the
> working group shall prevail.  (However, it must be noted that
> "dominance" is not to be determined on the basis of volume or
> persistence, but rather a more general sense of agreement.) Consensus
> can be determined by balloting, humming, or any other means on which
> the WG agrees (by rough consensus, of course).


The other document is recent versions of the Tao of the IETF. It did not 
originally discuss the issue but Sue Harris added discussion of
it in 2001, and the latest text on the Tao web page seems to have the 
same text.[*]

      http://tools.ietf.org/html/rfc3160

> 3.2 Getting Things Done in a Working Group
...
> Another aspect of Working Groups that confounds many people is the
> fact that there is no formal voting.  The general rule on disputed
> topics is that the Working Group has to come to "rough consensus,"
> meaning that a very large majority of those who care must agree.


And the simple focus on a strongly dominant group preference was what 
was presented in the original Working Group Chair training I initiated 
also in the early 90s:

      http://bbiw.net/presentations/ietf-stds-4.pdf

So, folks, please do press for Pete's document to move towards readiness 
to be published.  But let's not invent history and thereby fail to 
understand the difference between 'clarifying' and 'enhancing'.

d/




[*]  Small observation about the current fashion of moving things to web 
pages rather than RFCs:  We completely lose version tracking, and being 
able to review the history of the document.  While one might add a 
mechanism to remedy this, note that we don't do that now.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Thu Oct 10 13:38:04 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 86F2721F9A5F for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:38: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 RQWnsy4BWe-X for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:37:51 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DC81E21F856A for <ietf@ietf.org>; Thu, 10 Oct 2013 13:37:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 79F212CCBF; Thu, 10 Oct 2013 23:37:48 +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 QCWwSfDSmeQY; Thu, 10 Oct 2013 23:37:48 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id C0E042CC95; Thu, 10 Oct 2013 23:37:47 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52570D32.9020107@dcrocker.net>
Date: Thu, 10 Oct 2013 23:37:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7FFD66D-D555-42B0-8D18-39CA675F338B@piuha.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <52570D32.9020107@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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, 10 Oct 2013 20:38:04 -0000

> As I noted in my review of the draft, the document has a core flaw in
> its sense of history.  It has invented an interpretation of "rough
> consensus" that was not part of its original formulation.
>=20
> I consider the current focus on reconciling minority views to be quite =
an excellent enhancement to that original interpretation, but it really =
is an addition.

Ok. I was not there at the time to witness the history. Thanks for the =
clarification.

Jari


From jari.arkko@piuha.net  Thu Oct 10 13:42:33 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 2A10021F9C52 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3HEQPSiQ+xV7 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 13:42:28 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C237221F9B8A for <ietf@ietf.org>; Thu, 10 Oct 2013 13:42:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2C27D2CC95 for <ietf@ietf.org>; Thu, 10 Oct 2013 23:42:26 +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 h3fq6pG7Krtw for <ietf@ietf.org>; Thu, 10 Oct 2013 23:42:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B528C2CC48 for <ietf@ietf.org>; Thu, 10 Oct 2013 23:42:25 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <525590D5.3050606@gmail.com>
Date: Thu, 10 Oct 2013 23:42:25 +0300
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF9C9D3F-24A9-4471-A518-BEEF92E17677@piuha.net>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <8C48B86A895913448548E6D15DA7553BA5FFA8@xmb-rcd-x09.cisco.com> <5254CC15.3050802@gmail.com> <5254E7A3.8050507@pi.nu> <5254E9EF.6010807@gmail.com> <B8F18391-6CEC-4A5B-A881-CFCD9E6BE602@nominum.com> <525590D5.3050606@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Oct 2013 20:42:33 -0000

FWIW, on the issue of Informational RFCs seen as cast in stone:

I think I've seen that problem occasionally. I.e. people assigning a far =
too high value to a document, just because it is an RFC. The world =
changes, our understanding changes, and as Dave pointed out processes =
evolve=85 RFCs need to change now and then as well.=20

I agree that the issue is much more serious for BCPs. But I think we =
really need to get over the issue. The best defense for that problem is =
to be seen publishing and revising RFCs. If we start to be afraid of =
publishing an RFC=85 I think we've already lost too much. I do not want =
to go there.=20

Just a personal opinion, of course.

Jari


From sm@resistor.net  Thu Oct 10 14:10:39 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 CC38921E80DE for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 14:10: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=[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 QYSh4lmv2GH6 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 14:10:39 -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 5E79211E80E9 for <ietf@ietf.org>; Thu, 10 Oct 2013 14:10:27 -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 r9ALADRD023354; Thu, 10 Oct 2013 14:10:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381439418; bh=v/tqn05JpNQOBCj7IHaHFBVwRTCKEUv7Ly00jD3/8rQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fnTJvHLS+xDfmjr1OowVHv6w2tICaV3PNF7OuSpXHTXwAff0UMwObtgulNvX72s82 b3Qp/L9hHizs/Kr73TF1Zz5tpLtv298FWwd6UjHTy5rx/5ZiAS9S9P0Le1nSOVd6rE NS01wHxmSyiOoE4vyt2l1rdSepZ248PeKRUAAlyY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381439418; i=@resistor.net; bh=v/tqn05JpNQOBCj7IHaHFBVwRTCKEUv7Ly00jD3/8rQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SqYfgYMP0eizjMUfwR+tfQa5wcWtiqOhxdR8aXMB/50LDHb0mLevEUW0U5UqmiRZU Qz4LtWRD2VpJEfVRA0f9ZXdfhtnORGJC6ursHN/epR+6Uh7fa7aENx8zyMdiH6b1W2 B3weoft11zpMd7k9bFi0pdIMupcpdK1FbKLz9Zs4=
Message-Id: <6.2.5.6.2.20131010131758.0bf2c528@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Oct 2013 13:49:37 -0700
To: Medel v6 Ramirez <mgramirez@globe.com.ph>
From: SM <sm@resistor.net>
Subject: Re: Montevideo statement
In-Reply-To: <CALw3TGGkSmxz-+HPAwqF-JAv3EZjfHPTwEgJjq3Lz+e_BRDq7g@mail.g mail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <6.2.5.6.2.20131008213432.0c1e4b30@resistor.net> <20131009064438.GA47673@mx1.yitter.info> <E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <5255A905.10700@gmail.com> <CADnDZ8-vaM64D9T79XgCzgby-6TEmgsPeEvA6XfZwwUCHtX1fA@mail.gmail.com> <CALw3TGGkSmxz-+HPAwqF-JAv3EZjfHPTwEgJjq3Lz+e_BRDq7g@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: Thu, 10 Oct 2013 21:10:40 -0000

Hi Medel,
At 19:11 09-10-2013, Medel v6 Ramirez wrote:
>Leaders were "processed" thoroughly prior to their appointment so I 
>trust them. And that they hold through the "spirit" of being an IETF 
>and shall be responsible under oath for any impact on the organization.

There was a Recall petition last year (see 
http://www.ietf.org/mail-archive/web/ietf/current/msg75672.html 
).  Note that the IETF "Trustee have a fiduciary duty to protect the 
IETF's property".

What are the implications of:

   "They identified the need for ongoing effort to address Internet Governance
    challenges, and agreed to catalyze community-wide efforts towards the
    evolution of global multistakeholder Internet cooperation."

Should a global body have oversight over the IETF?  Some people are 
arguing for that as part of the future of Internet Cooperation.

Regards,
-sm 


From jari.arkko@piuha.net  Thu Oct 10 14:32:53 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 F384611E80E2 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 14:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.384
X-Spam-Level: 
X-Spam-Status: No, score=-102.384 tagged_above=-999 required=5 tests=[AWL=0.215, 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 Xkna-1cil-l5 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 14:32:48 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 08FA321F9C53 for <ietf@ietf.org>; Thu, 10 Oct 2013 14:32:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3B48C2CC95; Fri, 11 Oct 2013 00:32:42 +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 Ctx4b_RI83Tu; Fri, 11 Oct 2013 00:32:41 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A9D352CC48; Fri, 11 Oct 2013 00:32:41 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Montevideo statement
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5256F68D.7020509@dcrocker.net>
Date: Fri, 11 Oct 2013 00:32:41 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <63FC31E7-840D-44C0-96F8-A046889CCF71@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <5256DE72.4010705@dcrocker.net> <BD554473-CD9D-4795-A125-A4E52EAEC68D@piuha.net> <5256F68D.7020509@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
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, 10 Oct 2013 21:32:53 -0000

Dave,

> The fact that you had to reach back 2.5 years, to a frankly rather =
obscure document that came from the IAB and not the broader IETF, =
demonstrates my point that we lacked meaningful context=20

You asked for context and I provided a context. We can certainly debate =
how meaningful it is. There are obvious arguments that we can make =
against its meaningfulness. But I disagree with your characterisation of =
the most recent RFC (6020) on topic from the organisation that in the =
IETF ecosystem has IANA oversight in its charter (per RFC 2580, a BCP) =
as "obscure". In any case I don't want to argue too much, because I _do_ =
agree with your larger points:

> They don't set work agendas. They don't control overall budgets.  They =
don't hire and fire people.  For almost all of the formal IETF =
'decisions' they participate in, it is with exactly one vote in a group, =
and not more authority than that.
...
> IETF leaders are best viewed as facilitators, rather than leaders.  =
They do huge amounts of organizing, coordinating, interfacing, in the =
classic style of the cliche'd 'shepherding cats'.

Although I would claim that while there is no traditional "leading" at =
the IETF, I do think that IETF facilitators do occasionally lead in the =
sense of suggesting paths forward, identifying potential challenges, =
etc.

And I of course would love to have this:

> We need to find some sort of language that gives constructive guidance =
and constraint about public representations of the IETF, by our =
'leaders'.

Jari


From scott.brim@gmail.com  Thu Oct 10 15:42:14 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 F2ABB21E811C for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 15:42: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=[AWL=0.000, 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 un3vQZeISVAL for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 15:42:13 -0700 (PDT)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4DC21E8084 for <ietf@ietf.org>; Thu, 10 Oct 2013 15:42:13 -0700 (PDT)
Received: by mail-ee0-f54.google.com with SMTP id e53so1478932eek.41 for <ietf@ietf.org>; Thu, 10 Oct 2013 15:42:12 -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=h2zSpgXtoC1eYsL3z1j+p3h/4bsnIWWo+QlDg/7E5VU=; b=nz1FPtjwy4Ftq4zsGe3qjs7vnlQFLMVwEvbIpn2mtprYwb/qI9QjsT+z2iK0U7xZao AQs8h5bD0SetJrjzoPzYDKX5lI5YWmmEAnxVpBUw5pdwvtrXgQZi/m88a9BEyL3UOZaU e/cxgrV2R7h4P+4AE6iqU8j6L3UWjk5ZISraKhRFfrkOcCTbjAi5iYP6W0l+W37KkMP3 rwyV7tkV3Yhen5TPnc5aaiNknL81Pxh9eZFLbomMdr/twdRQSCpcViA4ZCt6qg0zpbzd 4eLqslPxBQOJQcaUjA9LlkkLJmAknIyq1Eiqv3uaITqb+/gSLCc2hURBce60uOh4nGee MNwA==
MIME-Version: 1.0
X-Received: by 10.15.83.2 with SMTP id b2mr24260722eez.28.1381444932372; Thu, 10 Oct 2013 15:42:12 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Thu, 10 Oct 2013 15:42:12 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Thu, 10 Oct 2013 15:42:12 -0700 (PDT)
In-Reply-To: <52570D32.9020107@dcrocker.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <52570D32.9020107@dcrocker.net>
Date: Thu, 10 Oct 2013 18:42:12 -0400
Message-ID: <CAPv4CP__njrPwQOGCaxjFmZhSQF2dgQHTxok45m+Jis=8xa_Vw@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Scott Brim <scott.brim@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0160bc92788d6a04e86ab6b4
Cc: Pete Resnick <presnick@qti.qualcomm.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: Thu, 10 Oct 2013 22:42:14 -0000

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

True, it was mostly a reaction to the IETF's tendency to over-proceduralize
everything, and an inclination to voting. The main issue I have been
concerned with since then, and something this draft helps with, is
redefinition of "rough consensus" to manipulate WG outcomes.  WGs need to
get beyond the primitive basic concept of rough consensus, to get more
nuance in the principles of how they are run. I like this draft as
contributing to that.

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

<p dir=3D"ltr">True, it was mostly a reaction to the IETF&#39;s tendency to=
 over-proceduralize everything, and an inclination to voting. The main issu=
e I have been concerned with since then, and something this draft helps wit=
h, is redefinition of &quot;rough consensus&quot; to manipulate WG outcomes=
.=A0 WGs need to get beyond the primitive basic concept of rough consensus,=
 to get more nuance in the principles of how they are run. I like this draf=
t as contributing to that. </p>


--089e0160bc92788d6a04e86ab6b4--

From presnick@qti.qualcomm.com  Thu Oct 10 15:48:32 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 703E021E814B for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 15:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.356
X-Spam-Level: 
X-Spam-Status: No, score=-101.356 tagged_above=-999 required=5 tests=[AWL=-1.357, 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 l9q3qjPF9LL1 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 15:48:28 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id BFA3F21F9AA8 for <ietf@ietf.org>; Thu, 10 Oct 2013 15:48:27 -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=1381445307; x=1412981307; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ykiP5+JRm1kl9cUVVjVfW60+xTvZuWEHjxErxOFOCew=; b=Bt4gL2P+F0lFsGiwWyF4vAUmO5bdjGMwiSYk9cJrervXfI7Km1YEHYE0 L/cwT54EITMM9TRiA1MmOuGlmn7pZzTpGGkoAErVExeYSGop8606U/O6o iOj8ESK11swsSCYyEs/DpOUm6A2U4kwLgtoA/Q50rzm+F1dO7SkD2jgel E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="54002221"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 10 Oct 2013 15:48:26 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="566971577"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Oct 2013 15:48:12 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Oct 2013 15:48:12 -0700
Message-ID: <52572EA9.4030807@qti.qualcomm.com>
Date: Thu, 10 Oct 2013 17:48: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: <dcrocker@bbiw.net>
Subject: Re: Review of:   draft-resnick-on-consensus-05
References: <5251FA64.7020205@dcrocker.net>
In-Reply-To: <5251FA64.7020205@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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: Thu, 10 Oct 2013 22:48:32 -0000

Finally back to this original review.

On 10/6/13 7:03 PM, Dave Crocker wrote:
>      In terms of philosophy and desirable practice, the draft 
> discusses an extremely appealing model and generally explains its 
> nature and practice well.  However the draft tends to confuse what is 
> (or has been) with what should be.  This includes confusing the IETF's 
> historical sense of what 'rough consensus' means, with what the draft 
> suggests it mean. As a consequence, it sometimes merely explains what 
> is preferred, rather than the problems with what is common practice.  
> (Sometimes.  At other times, it nicely makes its case.)  Also it 
> sometimes does not lay out the context for its assertions.
>
>      In effect, the draft is offering fundamental enhancements to 
> existing IETF practice, rather than merely clarifying the ways things 
> are "supposed to be".

I think this is a fair criticism and I will do a grand editing pass to 
try to tease the two apart: Where the draft is actually describing real 
historical practices vs. where it is describing a theory that does not 
comport with our practices. I know of several places beyond what you've 
mentioned that make the same conflation, and I think it's well worth 
making it clear. There are some instances where "what is (or has been)" 
is actually mushy: That is, people haven't really thought about it in 
depth. In those cases, I've definitely done a bit of saying what I think 
folks would mean if they were actually asked about it. (See more on this 
point in the discussion of the intro.) But with all of these, I think I 
should be more explicit about which is which.

> By way of properly setting context, the draft should cite RFC 1603/3934

You mean 2418. But yes, I think you're right.

> Working Group Guidelines and Procedures.  Its section 3.3 has text 
> that describes long-standing community views on the meaning of rough 
> consensus, which don't quite align with what the draft puts forward:
>
>>                In general, the dominant view of the
>>    working group shall prevail.  (However, it must be noted that
>>    "dominance" is not to be determined on the basis of volume or
>>    persistence, but rather a more general sense of agreement.) Consensus
>>    can be determined by a show of hands, humming, or any other means on
>>    which the WG agrees (by rough consensus, of course).  Note that 51%
>>    of the working group does not qualify as "rough consensus" and 99% is
>>    better than rough.  It is up to the Chair to determine if rough
>>    consensus has been reached.

Yup. I think this document has to cite that statement in 2418, and it 
has to disagree with it, at least to the extent of claiming it is an 
over-simplification. I had intended to do so and simply forgot. That 
51%/99% statement actually leads down the path that the document wants 
to discourage.

>      The disparity between that document's text and what this draft 
> describes should not be a problem for what the draft is recommending, 
> but merely requires changing the explanatory tone of the draft and how 
> it makes its case.
> [...]
>      The changes being suggested to the draft are substantial, but 
> will not affect the essential points for which the draft is lobbying.

I agree, though I think the changes are actually pretty straightforward. 
Maybe substantial in number of actual edits, but not in essential content.

>> Abstract
>
>    a "majority rule-> a "simple majority rule"
>
> Majorities come in different forms or degrees and the fact that 'rough 
> consensus' is often taken to mean 67% or 75%, as a rule of thumb can 
> make this confusing.
>
> From what you've written, your basic point seems to be that 51% isn't 
> enough; it's worth making that explicit.

Setting aside the possible confusion in British usage, I don't think you 
understood my intention here. And since you and Christopher and Jaap 
ended up in the same place, I'm happy to say that it's my fault for not 
being clear enough.

I intended that the abstract simply summarize the document's *purpose*, 
not its conclusions. I was using it like the abstracts that appear on 
scientific papers. Of course, the abstracts on our technical 
specifications usually give away the punch line, which is what we're 
used to seeing. I'll have a go at an edit, at least to clarify what I'm 
doing.

> For example, "voting" can be done with models that give quite a bit of 
> power to minorities.  So, you need an explicit, direct, early 
> statement that asserts the nature and importance of "rough consensus" 
> factoring in minority views.

This is an abstract, not a place to put early statements. I think the 
kind of statement you're looking for goes in the intro, which I 
hopefully address below.


>> 1.  Introduction
>> [...]
>> That is, our credo is that we don't let a single individual make the
>
> As the draft phrases it, that isn't really true.  We let individuals 
> make decisions all the time.  What I believe the aphorism is saying -- 
> and what reflects our community belief -- is:  We do not assign to any 
> one individual the authority to /dictate/ a decision.  ("make" is too 
> soft a word for this point, IMO.)

Fair enough.

>>    decisions, nor do we let the majority dictate decisions, nor do we
>
> I believe the model being pursued in this draft -- of the nature and 
> essential importance of properly dealing with minority views -- is 
> hugely powerful and appropriate.  But I believe it has never been a 
> prevalent view in the community, including back when the aphorism was 
> seeking to summarize the community view.

Yes, I think this all goes to your earlier point of cleanly 
distinguishing between historical view and new theory.

> The language I remember from the 90s primarily distinguished "strongly 
> dominant majority" from 51% or 67% or 75%.  That is, it was about 
> imprecise nature of the required clear and strong majority, rather 
> than the moderating role of the minority.  Very occasionally -- but 
> only occasionally -- we would use language that was along the lines of 
> "strongly dominant view, with no vigorous and coherent opposition".

When I started having conversations about the draft with folks, 
especially people who've been around quite a while, I was struck by the 
number of times the discussion started with, "No, that's not what we 
meant", but ended in, "Oh, yes, in those extreme cases, that's exactly 
what we meant." That is, I think the "51% is not enough, but 99% is more 
than enough" view was certainly in the front of people's minds, but when 
probed about the implications of that, almost everyone came to the same 
conclusion as the document: 51/99 is often a good rule of thumb if one 
wanted to guess about the consensus based on numbers of people, but it's 
still reasonable to call certain outcomes (like the ones described in 
the document) "rough consensus" even if the views of a huge majority 
might not win the day.

But it is certainly fair to say that in the 90s, few of us would have 
independently articulated the idea that a 90% majority might not be 
rough consensus.

> That latter part probably should be seen as a crude version of what 
> the draft is seeking to discuss, but I believe it was never 
> consistently voiced or understood.
>
> In other words, I think the role of minority views that the draft is 
> putting forward is not a mere clarification and refinement to the 
> existing IETF model, but rather is a significant enhancement.   So its 
> premise about the potential importance of minority views does have 
> some historical hooks in the IETF philosophy, but not as much as the 
> draft seems to assert.

Yep. I hope I can edit to make that clearer.

>>    allow decisions to be made in a vacuum without practical experience.
>
> Again, this statement goes beyond actual practice.  The language here 
> prohibits decisions without experience and of course, the real IETF 
> has always indulged in some decision-making based on theory that 
> lacked practice.  We /prefer/ experience.  We /value/ the input it 
> provides. But we are perfectly capable of making decision in a vacuum.

Remember that I'm saying what the "credo" says, not how tightly we 
adhere to it. How well we stick to it is talked about later. I think we 
do take as a principle that we want to base decisions on running code. 
We certainly don't always do so.

>>    Instead, decisions are made by (more or less) consent of all
>>    participants, and the actual products of engineering trump
>>    theoretical designs.
>
> "Consent of all"?   Hell no.  Not even close, as your following text 
> already note.

Again, here it is stating what the credo says, not the specifics of what 
we do (or even mean to do) in practice.

[Compare: Person A: "The US Constitution says, 'Congress shall make no 
law...abridging the freedom of speech.' Our credo is that the government 
will not limit speech." Person B: "But that's not true. The government 
limits all sorts of speech." Person A: "Never said it didn't. I said 
what the credo was. I will talk at length in a moment about how the 
government does and does not adhere to the credo, and how some of that 
is fine and still inline with our overall principles, and how some of it 
is problematic, and how they can do things that are less problematic."]

This is the Introduction. It's setting up the bigger picture. It's not 
the place to say, "The details are complicated"; of course they are.

>>    Our ideal is full consensus, but we don't
>>    require it: Full consensus would allow a single intransigent person
>
>      Full consensus would allow
>      ->
>      Requiring full consensus gives each person a veto, by allowing

Right. I'm inclined to skip the "veto" language, but I will definitely edit.

>>    who simply keeps saying "No!" to stop the process cold.  We only
>>    require rough consensus: If the chair of a working group determines
>
> Again, this seems to conflate two points.  Both are extremely 
> important.  Both need to be discussed.  But not intermixed.
>
> One is that we do not require everyone to agree, as long as there is a 
> strongly dominant group that do agree.
>
> The other is that all concerns must be diligently considered, but do 
> not have to be thoroughly resolved.  'Diligently considered' is an 
> imposition on the entire group but it is mandatory.  'Not thoroughly 
> resolved' is acceptable when the strongly dominant group agree that it 
> is acceptable.

All true, but that discussion is not appropriate to the Introduction. 
The distinction between the two points is discussed at length later.

>>    that a technical issue brought forward by an objector has been truly
>>    considered by the working group, and the working group has made an
>>    informed decision that the objection has been answered or is not
>>    enough of a technical problem to prevent moving forward, the chair
>>    can declare that there is rough consensus to go forward, the
>>    objection notwithstanding.  To reinforce that we do not vote, we have
>
> "To reinforce" switches from discussing the handling of minority 
> concerns about voting.  At a minimum, break the paragraph.

Done.

>>    also adopted the tradition of "humming": When (for example) the chair
>>    of the working group wants to get a "sense of the room", instead of a
>>    show of hands, the chair asks for each side to hum for or against a
>>    question.
>
> The draft has historically drawn a strong distinction between hands 
> and hums.  It's an interesting distinction, and well might be useful, 
> but I believe it has not been a universally-shared distinction in the 
> community.  It essentially relies on a theoretical analysis of 
> differences in psychological effects, but there's no objective basis 
> for validating the one really is superior to the other.

And the draft says as much. See section 4, paragraphs 3-5. This is 
discussed at length. I don't see what's missing from here.

>>    More and more
>>    frequently, people walk away from working groups, thinking that
>>    "consensus" has created a document with horrible compromises to
>>    satisfy everyone's pet peeve instead of doing "the right thing".
>>    None of these things are indicators of a rough consensus process
>>    being used, and are likely due to some basic misperceptions.
>
> Is the issue their perception, or the fact that horrible compromises 
> are actually being done?  From the text, I can't tell what point is 
> intended.

Here, it's only about the perception. I talk about the real problems 
with compromises at the end of section 2.

>      it is not intended to dictate ->  it does not dictate

Will fix.

>> 2.  Lack of disagreement is more important than agreement
>
> The substance of this section has an important focus and makes useful 
> comments.
>
> However the title could be taken to cover such things as failure to 
> gain affirmative support.

I don't intend any of my section titles to be complete and precise. If 
folks really don't like that, I can go about changing them, but I'd 
really rather not.

>> ... Consensus is not when everyone is
>
> par break at start of sentence.

Sure.

> And possibly move this and the remaining sentences higher up, since 
> they voice the essential point of the section.  In other words, try to 
> start with the premise so that folks are oriented, and then explain it.

I know this is apropos of a conversation we're having offline, but I do 
believe that people can get through the example of the problem before we 
tell them what the solution is.

> Here's a suggestion for some re-casting to this separate paragraph, to 
> help the reader bit, with the draft's logic and meaning:
>
>      Engineering always involves a set of tradeoffs.  The process of 
> gaining agreement about tradeoffs is the essence of a good rough 
> consensus effort, and requires distinguishing the group debate and 
> compromise needed to _come to_ consensus, the chair's process of 
> _determining_ (or assessing) consensus, and the final point of the 
> group's _having_ consensus on it choices.

Did you intend for that to replace something or just to insert it? I 
think it works well inserted, but if you meant something to be deleted, 
please clarify.

>>    However, there is another sense of "compromise" that involves
>>    compromising between people, not engineering principles.
>
> This seems to argue that political compromise is never acceptable. 
> That's not realistic.  Folks often can "live with" unresolved 
> concerns.  The meta-issue is distinguishing disagreements about key 
> points versus disagreement about minor ones.  Political compromise 
> about a flat vs. hierarchical namespace is a rather different kettle 
> of importance than between specifying a syntactic separator of comma 
> vs. semicolon.  (No matter how much prettier I might think commas are, 
> and superior for good visual presentation...)

So, the "live with" case is mentioned above, but I think it needs 
clarification in the previous paragraph. But I *do* want to argue that 
political compromise *is* never acceptable. It's one thing for me to 
conclude that I can live with semicolons over commas even though my 
preference is for commas (i.e., that it is a reasonable, though not 
preferred, engineering choice); that's just fine. It's quite different 
for me to conclude that the rest of these people are idiots for not 
choosing commas, but I'm going to put up with the semicolons because I 
want to make people happy so they'll do a hierarchical namespace, or 
because I've simply given up on trying to make this a good document. If 
it's a serious issue, giving up or trading is bad. If it's an "I can 
live with it" issue, then you're simply agreeing that the choice is 
acceptable.

And I'm not saying that the bad sort of compromise won't ever happen (we 
are humans, after all), or that there are no borderline cases (Is this 
me "living with it" or capitulating?), but I do want to say that 
participants have to decide whether they're making a reasonable 
engineering compromise or they are capitulating (or horse trading), and 
not do it if it's the latter.

And all that said, I need to clarify this.

>>    Note that this portrays rough consensus as an "exception".
>
> I don't understand this first sentence.  How is it an exception?  Even 
> with the following text, I don't see the basis for claiming that it 
> might/would be seen as exceptional.

Maybe I need a different word. I didn't mean "exceptional" in the sense 
of "extraordinary" or "atypical". I simply meant it in the "exception 
handling" sense: We work toward full agreement, but if there's still 
disagreement, we undertake an alternative path. I'm open to suggestions 
for text.

>>    Now, a conclusion of having only rough consensus relies heavily on
>>    the good judgement of the consensus caller.  The group must truly
>>    consider and weigh an issue before the objection can be dismissed as
>>    being "in the rough".  The chair of the working group in one of these
>
> In spite of being appealing to use here, I think that the phrase "in 
> the rough" is actually distracting

As I mentioned earlier, I think it is worth defining as the golf term, 
since it is used quite frequently among IETFers nowadays.

>>    cases is going to have to decide that not only has the working group
>>    taken the objection seriously, but that it has fully examined the
>>    ramifications of not making a change to accommodate it, and that the
>>    outcome does constitute a failure to meet the technical requirements
>>    of the work.  In order to do this, the chair will need to have a good
>>    idea of the purpose and architecture of the work being done and use
>>    their own technical judgement to make sure that the solution meets
>>    those requirements.  What can't happen is that the chair bases their
>>    decision solely on hearing a large number of voices simply saying,
>>    "The objection isn't valid."  That would simply be to take a vote.  A
>>    valid justification needs to me made.
>
> This begs the question of who determines that a justification is 
> valid.  I'll suggest that it mostly should be the working group, with 
> the chair as fall-back or safety valve, but not default.

Remember, this is precisely the case where the working group claims to 
have considered the objection and found it to be wanting, but the 
objector still insists that the objection is valid. The rest of the 
working group can make the case that it has properly considered the 
objection, but it can't make the final call on whether it has; only the 
chair can do that.

> By the way, the draft seems to think that it's always the chair who 
> leads discussion and debate; it often/mostly isn't.  Rather it's 
> typically the authors/editors, with a chair serving to moderate impasses.

During my large edit, I'll have a look at this. My intention wasn't to 
say that the chair *leads* discussion. Indeed, beyond authors/editors, 
quite often it is someone else in the group who takes up the mantle of 
analyzing the discussion and proposing paths forward. But the chair in 
the end is responsible for making the final call as to the consensus of 
the group.

>>    A good outcome is for the
>>    objector to understand the decision taken and accept the outcome,
>>    even though their particular issue is not being accommodated in the
>>    final product.  Remember, if the objector feels that the issue is so
>
> par break at Remember.

Sure.

>>    So, why do we hum?
>
> This section reads nicely and sounds quite good and very possibly 
> might be something that we /should/ do.  However it has little to do 
> with common IETF practice.

Yep. This goes back to your main critique. So really the above should 
say, "So why should we hum?", or something to that effect. Wilco.

> Even better is that I think the draft has buried it's more important 
> point, namely that the /form of the question/ asked when seeking a hum 
> is the really hard part of the effort, and the most important part. 
> Some forms invite constructive discussion and some close it off.  Some 
> are fair and balanced (...) and some are highly biasing.

I'll try to expand on that.

>>    But couldn't the above could have been done with a show of hands
>
> This paragraph goes back to the hum-vs-hand methodology issue.  It's 
> important, but it's out of place here, since this section is about the 
> /role/ of a hum, not its method.  Discuss methodology separately, 
> possibly up where it is first introduced.

I disagree with you on this one. The previous discussion was in the 
Introduction, which says, "Something's screwy here. What's up with 
that?" Here, I am trying to say, "Here's what we ought to be doing. Hums 
are good. Hands work too, but have their weaknesses." I think it works 
together well.

> "the chair wants to choose the path that gets to the least objections 
> fastest" sounds like an extremely appealing expedient, by virtue of 
> being almost mechanical, but numbers often don't matter.  A single 
> objection that observes (and substantiates) that a choice will not or 
> cannot be used in the real world will outweigh a much larger number of 
> trivial objections.
>
>
> Perhaps merely qualifying the statement a bit will suffice:  the chair 
> wants to choose the path that gets to the least number of significant 
> objections fastest".  Hmmm.

Yeah, this gets talked two paragraphs previously, but I think it's fair 
to reiterate here. I think the better fix is to add to the below sentence:

>>    There is always a chance
>>    that this could be misleading, because some people are more willing
>>    to hum loudly than others (just by dint of personality), but keep in
>>    mind that taking the hum is to figure out how to start the
>>    conversation.

Add after the parenthetical: "or that one of the quieter hums actually 
turn outs to be a showstopper that makes the original choice impossible,"


>>    Of course, a chair could get the temperature of the room by doing a
>>    show of hands too, and knowing who specifically feels one way or
>>    another can help a good chair guide the subsequent conversation.
>
> And possibly place the minority under group pressure.

Sometimes a hum can do exactly the same.

>>    Sometimes, they simply mean they are making a call _of_ the
>>    consensus; that is, they are declaring the consensus that has, in
>>    their view, been reached when the discussion has reached an end.
>>    That's a fine thing and what chairs are supposed to do: They are
>>    "calling" the consensus.  Sometimes, when a chair says that they are
>    We often hear chairs say that they are making a "consensus call".
>
> Might be worth tossing in the word "confirm" or "confirming existing 
> consensus" here, to leave no doubt about what "calling" means.

Yeah, or use the word "stating" or "expressing". I'll work on that.

>>    So in a large working group with over 100 active participants and
>>    broad agreement to go forward with a particular protocol, if a few
>>    participants say, "This protocol is going to cause congestion on the
>>    network, and it has no mechanism to back off when congestion occurs;
>>    we object to going forward without such a mechanism in place", and
>>    the objection is met with silence on the mailing list, there is no
>
> The problem here is who is the authority to determine that the 
> objection needs to hold sway.  It's easy to lay this on the chair, but 
> that makes the mechanisms fragile; it's too easy for one person to get 
> this sort of thing wrong.

The case we're talking about here is an objection being met with 
silence. In that case, the presumption (i.e., not the conclusion) is, 
"Real objection; needs to be dealt with." The only way that the chair 
can "get this sort of thing wrong" is to at that point silently decide 
that it's not an objection worth addressing. The chair can say to the 
group, "I've seen this objection, but I don't think it's valid. Can 
someone confirm my view that it's not valid, or can the objector or 
someone else please explain why it is?" But this is only about whether a 
completely dropped-on-the-floor objection is OK. It's not.

Did I miss your point?

>
>>
>> 7.  Five people for and one hundred people against might still be rough
>>     consensus
> ...
>
>
>>    Now the worst case scenario happens.  The objector, still unhappy
>>    that their preferred solution was not chosen, recruits one hundred
>>    people, maybe a few who were silent participants in the working group
>>    already, but mostly people who work at the same company as the
>>    objector who never participated before.  The objector gets them all
>>    to post a message to the list saying, "I believe we should go with
>>    the new elegant algorithm in section Z instead of the current one.
>>    It is more elegant, and works better on our hardware."  The chair
>>    sees these dozens of messages coming in and posts a query to each of
>>    them: "We discussed this on the list, and we seemed to have consensus
>>    that, given the inherent risk of a new algorithm, and the widespread
>>    deployment of this current one, it's better to stick with the current
>>    one.  Do you have further information that indicates something
>>    different?"  And in reply the chair gets utter silence.  These
>>    posters to the list (say some of whom were from the company sales and
>>    marketing department) thought that they were simply voting and have
>>    no answer to give.  At that point, it is within bounds for the chair
>>    to say, "We have objections, but the objections have been
>>    sufficiently answered, and the objectors seem uninterested in
>>    participating in the discussion.  Albeit rough in the extreme, there
>>    is rough consensus to go with the current solution."
>
> There's an interesting methodological point buried quite deep in this 
> example, and probably worth surfacing sooner and more directly:
>
>      Besides being careful about how the question for a consensus 
> check is phrased, it is sometimes advisable to seek to discover what 
> the responses mean.
>
> In the example here, the question is whether those responding were 
> sufficiently well-informed to be able to justify their position.

I'll take an edit pass. Yes, that is exactly what I was trying to get at 
(among other things).

>>    There is no doubt that this is the degenerate case and a clear
>>    indication of something pathological.  But this is precisely what
>>    rough consensus is designed to guard against: vote stuffing.  In the
>
> Sorry, no.  It's not 'designed' for that at all, at least not in 
> typical practice in the IETF.  It probably /should/ be, and the draft 
> does a pretty good job of explaining how it /can/ be, but there is 
> nothing in the "design" of the IETF's consensus process that has a 
> history of mitigating against the problem the draft discusses here, 
> and the problem isn't mentioned in formal IETF documents.

Yes, fair criticism. "But this is precisely what rough consensus is 
ideally suited to guard against:"

Excellent comments. Thanks.

On to the next set....

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From ted.ietf@gmail.com  Thu Oct 10 17:04:38 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 35AFE11E8103 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 17:04: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, 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 TDune+3m5O2I for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 17:04:37 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4421121E813F for <ietf@ietf.org>; Thu, 10 Oct 2013 17:04:34 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id ar20so6492249iec.21 for <ietf@ietf.org>; Thu, 10 Oct 2013 17:04: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=TYXNFyGKX61vqLYGMsbqkmNQ9pMcFxdSZbD6O3QtUSQ=; b=ICNwCkJfJuNIwaUfw+V25b7mq9zWtMBN5bS5wLWBqU95zT6QS/o2TgRs8Fx3GcTQaH kQNoKrtmRwxTp1xSHO8gbugDPXWKfV1ZmVsgW4K+gS8ClWFs1KC2urpOKfx8xHMlZoVD dMUIp249mYbFP/Xn2xA0X6WSh+Ne3BX7ZL2ZOV142S63PoAFgeABz2sGKZNzoWqS5yJ8 J3e561zlps9R4Fv7gGEYLoZddZTaTsbUGwMJ+BIUHWZRUJnnKza0cJiwg3y7yrmQCjEt jG3Jj4YnEhH2ZwrjDGo3MKq8cS9Ph5evLfnKAW+b0ohdO8rSuoVBr9TmArf5Tf1iaVEJ tIKg==
MIME-Version: 1.0
X-Received: by 10.50.9.72 with SMTP id x8mr622183iga.19.1381449873518; Thu, 10 Oct 2013 17:04:33 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Thu, 10 Oct 2013 17:04:33 -0700 (PDT)
In-Reply-To: <52570D32.9020107@dcrocker.net>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <52570D32.9020107@dcrocker.net>
Date: Thu, 10 Oct 2013 17:04:33 -0700
Message-ID: <CA+9kkMBdz597LNBrvSZ5ZGPvwdo5wBkccwxCfoWd9eLnfkCFgA@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Ted Hardie <ted.ietf@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c2fdc4fcc97604e86bdc29
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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, 11 Oct 2013 00:04:38 -0000

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

A small comment in-line.


On Thu, Oct 10, 2013 at 1:25 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 10/7/2013 10:03 AM, Jari Arkko wrote:
>
>> The abstract says:
>>
>> The IETF has had a long tradition of doing its technical work
>> through a consensus process, taking into account the different views
>> among IETF participants and coming to (at least rough) consensus on
>> technical matters.  In particular, the IETF is supposed not to be
>> run by a "majority rule" philosophy.  This is why we engage in
>> rituals
>>
>
>
> As I noted in my review of the draft, the document has a core flaw in
> its sense of history.  It has invented an interpretation of "rough
> consensus" that was not part of its original formulation.
>
> I consider the current focus on reconciling minority views to be quite an
> excellent enhancement to that original interpretation, but it really is an
> addition.  In classic IETF fashion, documenting that enhancement flows from
> common -- though not universal -- IETF practice that has emerged, and it
> likely to produce better consistency to the current, ad hoc behavior.  But
> we need to stop asserting the meaning of "rough consensus" to have always
> or obviously included this.
>
> Part of the confusion about the history is over-interpreting the context
> the phrase was used.  Dave Clark drew a contrast against 'voting'. Voting
> is a mechanical counting process, with formal lines of distinction, whether
> a simple model like 51% or 67%, or the like, or something more complex.
>  But it's based on a strict counting of votes and a strict model for using
> them.
>
> By contrast, the phrase "rough consensus" simply meant that there is
> massive support, and leaves the determination of 'massive' to subjective
> processes.  If something has massive support, it is likely to get
> implemented, deployed and used.  If it doesn't, the formalities of a
> voting mechanism won't help it succeed in the marketplace.  The idea that
> voting will suffice for this concern by simply moving the thresh hold to
> some sort of super-majority imposes an artificial precision; the idea
> behind rough consensus is the subject sense that there is obviously
> 'enough' support.
>
> I believe the IETF has only two documents that talk about the meaning of
> rough consensus.


In addition to the two you cite, RFC 3929  does, primarily in Section 2 but
also 3.3 and a few other places.  As the author of that Experimental RFC, I
will note that I am not aware of any case in which any of its proposals has
been carried out, though it has been discussed as a possibility more than
once.

The first thing most readers note is that using one of its methods does not
get you out of building consensus--it requires you to build consensus for
an alternate approach when consensus on a technical matter cannot be
reached by the baseline process (and it is clear that it is not trying to
change the baseline).

regards,

Ted

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

<div dir=3D"ltr">A small comment in-line.<br><div><div class=3D"gmail_extra=
"><br><br><div class=3D"gmail_quote">On Thu, Oct 10, 2013 at 1:25 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:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 10/7=
/2013 10:03 AM, Jari Arkko wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
The abstract says:<br>
<br>
The IETF has had a long tradition of doing its technical work<br>
through a consensus process, taking into account the different views<br>
among IETF participants and coming to (at least rough) consensus on<br>
technical matters. =A0In particular, the IETF is supposed not to be<br>
run by a &quot;majority rule&quot; philosophy. =A0This is why we engage in<=
br>
rituals<br>
</blockquote>
<br>
<br></div>
As I noted in my review of the draft, the document has a core flaw in<br>
its sense of history. =A0It has invented an interpretation of &quot;rough<b=
r>
consensus&quot; that was not part of its original formulation.<br>
<br>
I consider the current focus on reconciling minority views to be quite an e=
xcellent enhancement to that original interpretation, but it really is an a=
ddition. =A0In classic IETF fashion, documenting that enhancement flows fro=
m common -- though not universal -- IETF practice that has emerged, and it =
likely to produce better consistency to the current, ad hoc behavior. =A0Bu=
t we need to stop asserting the meaning of &quot;rough consensus&quot; to h=
ave always or obviously included this.<br>

<br>
Part of the confusion about the history is over-interpreting the context th=
e phrase was used. =A0Dave Clark drew a contrast against &#39;voting&#39;. =
Voting is a mechanical counting process, with formal lines of distinction, =
whether a simple model like 51% or 67%, or the like, or something more comp=
lex. =A0But it&#39;s based on a strict counting of votes and a strict model=
 for using them.<br>

<br>
By contrast, the phrase &quot;rough consensus&quot; simply meant that there=
 is massive support, and leaves the determination of &#39;massive&#39; to s=
ubjective<br>
processes. =A0If something has massive support, it is likely to get<br>
implemented, deployed and used. =A0If it doesn&#39;t, the formalities of a<=
br>
voting mechanism won&#39;t help it succeed in the marketplace. =A0The idea =
that voting will suffice for this concern by simply moving the thresh hold =
to some sort of super-majority imposes an artificial precision; the idea be=
hind rough consensus is the subject sense that there is obviously &#39;enou=
gh&#39; support.<br>

<br>
I believe the IETF has only two documents that talk about the meaning of<br=
>
rough consensus. =A0</blockquote><div><br></div><div>In addition to the two=
 you cite, RFC 3929=A0 does, primarily in Section 2 but also 3.3 and a few =
other places.=A0 As the author of that Experimental RFC, I will note that I=
 am not aware of any case in which any of its proposals has been carried ou=
t, though it has been discussed as a possibility more than once.=A0=A0 <br>

</div><br></div><div class=3D"gmail_quote">The first thing most readers not=
e is that using one of its methods does not get you out of building consens=
us--it requires you to build consensus for an alternate approach when conse=
nsus on a technical matter cannot be reached by the baseline process (and i=
t is clear that it is not trying to change the baseline). <br>
<br></div><div class=3D"gmail_quote">regards,<br><br>Ted<br></div></div></d=
iv></div>

--001a11c2fdc4fcc97604e86bdc29--

From arturo.servin@gmail.com  Thu Oct 10 17:59:09 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 D9FFD11E8106 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 17:59: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 O4284Vu11tCh for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 17:59:04 -0700 (PDT)
Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by ietfa.amsl.com (Postfix) with ESMTP id F241011E8101 for <ietf@ietf.org>; Thu, 10 Oct 2013 17:59:01 -0700 (PDT)
Received: by mail-gg0-f182.google.com with SMTP id h13so540962ggd.27 for <ietf@ietf.org>; Thu, 10 Oct 2013 17:58: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=sGOY7mCvdKgd0kPG7dBhfUM2jKN8k+cIt0y5GKifXH4=; b=IgLmM/Edc1mVtUSgJTidMUpdIqZq+bTveBThg1RwGl50+yNKUYClAF7CFZGqZCfgqB TKlZ0GsZvyyaumisWfDcQVMUOfGuRlpA+0usJMlwKRfo3S5SmKSRy8zYiM0nrZhOXKBB NPIXvg0UC3f35S+Zxuz+VNCzz5NGYptVTFinLq7fNg0juPpMdaHdu7ZT3qjRKItS40Fu sSX5jCv65dOlw85WJSAzsdMcmTTMTsviG9YuM643RlGcuxcZDJXpt2Nmz3nNcEmcqmIM hPjcpgvNQt+n+B+a+zpdXq2fBvbxa96QT07mKFPjoRiINypPsJKu9SW8Fqph80WrbjBw f3ew==
X-Received: by 10.236.100.144 with SMTP id z16mr9272607yhf.9.1381453126056; Thu, 10 Oct 2013 17:58:46 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:c192:4ce2:5bab:af6b:307a]) by mx.google.com with ESMTPSA id 48sm74354429yhq.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 17:58:45 -0700 (PDT)
Message-ID: <52574D45.7060002@gmail.com>
Date: Thu, 10 Oct 2013 22:58:45 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: leader statements
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
In-Reply-To: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu>
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: Fri, 11 Oct 2013 00:59:10 -0000

	Just to clarify, I am no saying that today we are leaderless. In fact I
think we have a very good leadership.

	What I am saying is that if we that we want our leaders to only
moderate discussion we are in a big problem.

Regards,
as

On 10/10/13 4:52 PM, Noel Chiappa wrote:
>     > From: Arturo Servin <arturo.servin@gmail.com>
> 
>     > Then we have a big problem as organization, we are then leaderless.
> 
> I'm not sure this is true. The IETF worked quite well (and produced a lot of
> good stuff) back in, e.g. the Phill Gross era, when I am pretty sure Phill's
> model of his job was indeed as a 'facilitator', not a 'leader' in the sense
> you seem to be thinking of. So why do we now need a 'leader'?
> 
> 	Noel
> 

From randy@psg.com  Thu Oct 10 19:52:52 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 DB3F221F8790 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 19:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[AWL=0.152,  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 PQ5h6CgQyMsY for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 19:52:52 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 1102B21F880F for <ietf@ietf.org>; Thu, 10 Oct 2013 19:52:52 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VUSqL-0001Uu-50; Fri, 11 Oct 2013 02:52:45 +0000
Date: Fri, 11 Oct 2013 11:52:43 +0900
Message-ID: <m2wqlky0w4.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: leader statements
In-Reply-To: <52574D45.7060002@gmail.com>
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu> <52574D45.7060002@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: Fri, 11 Oct 2013 02:52:53 -0000

> What I am saying is that if we that we want our leaders to only
> moderate discussion we are in a big problem.

we are in a big problem, and this is one major part.  two decades of
lack of coherent architectural oversight is another symptom of this.
i'm surprised that we are not overwhelmed with focus groups.

randy

From presnick@qti.qualcomm.com  Thu Oct 10 20:02:52 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 A996611E8107 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 20:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, 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 D0GNsdttoBux for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 20:02:48 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 08C6321F9DF6 for <ietf@ietf.org>; Thu, 10 Oct 2013 20:02:45 -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=1381460566; x=1412996566; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ujUCr5hGMOh1pGFR+WZkbm3Xk5fLlCpTXqxbGO6OhHo=; b=S/t3vgqX2oRl4DkNOWSV1l9DFK1nq2hTGC7dQcUhuW7PygFimwC/T37X XzMOrylAduwEJXUechGlEiFn6RSAo40pdUnICYfFK9/czuIVKSTQFE3Ge PK18CoIRcoAfXPB1+nwzRoM1Es0jgMMjcf0Q+avO/MipAriLI84tPeSPC Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="53927299"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth01.qualcomm.com with ESMTP; 10 Oct 2013 20:02:45 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="620975070"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Oct 2013 20:02:45 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Oct 2013 20:02:45 -0700
Message-ID: <52576A52.8030002@qti.qualcomm.com>
Date: Thu, 10 Oct 2013 22:02:42 -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: t.p. <daedulus@btconnect.com>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net><6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net>	<52524A68.7040800@qti.qualcomm.com> <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net>
In-Reply-To: <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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, 11 Oct 2013 03:02:52 -0000

On 10/8/13 8:56 AM, t.p. wrote:
> 1) It does not state its target audience until, perhaps, the reference
> in the Conclusions, to WG Chairs.  [...]  Are
> ADs assumed to be above and beyond the considerations in this I-D:-(
>    

An excellent point. No, *every* consensus caller in the IETF should in 
my view be taking these points into consideration, ADs and chairs alike. 
The examples are full of WG/chair stories, but exactly the same kinds of 
things should happen, IMO, when ADs make consensus calls.

As I said elsewhere, my primary (though not sole) audience is IETF 
leadership (ADs, chairs, editors, secretaries, etc.) and experienced 
IETFers who already understand the basics of our process and/or might 
some day wish to be in such roles. Hopefully the document is somewhat 
accessible to newer or once-in-a-blue-moon participants, but I hope the 
main consumers of this document are folks who need to make consensus 
calls or might some day.

> 2)  There is an extensive discussion on the show of hands and the hum.
> What technology allows you to conduct those on a mailing list?
>    

I don't really talk about mailing lists, and I think you're right that 
it's worth spending at least a bit of time on in the document. In fact, 
neither a "hum" or a show of "hands" (messages?) on a mailing list makes 
a bunch of sense. Methodologically, I think the best way for chairs (or 
ADs) to deal with a mailing list is to checkpoint every so often, 
summarizing issues and perhaps even keeping an issues list, and then 
explicitly calling the consensus: "I hear that people are in favor of X 
and I haven't heard strong objections. Unless there's anyone who can't 
live with X, I am going to say that we have consensus for it." It's the 
same sort of thing I describe for f2f conclusions of consensus. I think 
that's worth pointing out.

> 3) References to working groups with 100 active participants sound like
> a chimera.
>    

The only place where there's mention of large groups is in the last two 
sections, which are specifically the extreme examples. They are 
illustrative examples of the worst case scenario, not meant to be 
representational of the common case.

> 4)  "Five people for and one hundred people against might still be rough
>      consensus".  Can you see the presumption in that?  Read on and the
> following text makes it clear that five are 'right' and one hundred
> 'wrong', but you are presuming that "for" is the right answer.

Yes, that's the example I've used. In this example, the five people have 
made their case for a technical solution, one person has made an 
objection, the five people fully address the objection, and therefore 
there is rough consensus. So in this case consensus was "for". The 
example is meant to show that 100 people blindly piling on the "against" 
side does not make them "right" and does not change the consensus.

> The
> right answer to a consensus call is a consensus,which can be "against",
> as much as "for", something that does not seem to be contemplated here.
>    

Sure. But that would be a different example.

I don't understand your concern here.

> 5) Good WG chairs, and happily there are plenty of them, make their
> presumptions plain, as in asking for information about implementations
> at or around judging consensus.  The views of someone who has
> independently produced rough code is then likely to outweigh those of a
> dozen people who have not, so three such expressing a view in one
> direction will prevail over several dozen who have not in the opposite
> direction.  (This is all right as far as it goes, but I would like the
> views of users and operators to count for even more, since it is they
> who have the most to gain or lose; but sadly, their representation here
> is small and often not apparent).  You quote Dave Clark's aphorism but
> then ignore half of it.
>    

Two things about this:

1. This document is about how we can come to consensus, not about the 
criteria around which we get that consensus (of which running code is 
one). And interesting document could be written about how we do (and 
sometimes don't) take running code into account, but it's not this document.

2. I take issue with one thing you do say above: "The views of someone 
who has independently produced rough code is then likely to outweigh 
those of a dozen people who have not". I think this is actually wrong: 
It is not that the implementer's view is given more weight *because it 
came from the implementer*; that would be an ad hominem judgement. The 
implementer's view is given more weight when it contains a solid 
technical case based on implementation experience. If an implementer 
says, "I've implemented this code and I can tell you that the way you 
are proposing won't interoperate", and someone with no implementation 
experience is able to say, "I can point you to implementations X Y and Z 
that implemented it my way and do interoperate", the fact that it's an 
implementer should make no difference at all. It is the existence of the 
implementation and how well it works that's the trump card, not who 
talks about it.

> 6)  The document is strangely silent about what the vast mass of the
> IETF who are not WG Chairs might do to help reach a consensus,
> such as express an opinion, clearly, technically; else, perhaps, keep
> quiet.
>    

I think the document is useful without this discussion. I certainly 
would not object to adding such a section in the future, but I don't 
think it's necessary in this version. Again, this is mostly aimed at 
discussions of how leaders can facilitate getting to consensus.

> 7) As has been said before when documents like this are up for
> discussion, the IETF is an organisation of engineers and, for the most
> part, we do it rather well.  Managing and leading loose and diverse
> groups of people is more psychology or sociology  than technology, at
> which we are mostly amateurs.  We then go beyond our capabilities and
> get it wrong.  As here.
>    

I'm not clear on how the discussions of how to manage and lead consensus 
discussion that are presented in the document you think "gets it wrong". 
Quite a few folks have found it useful and productive. More specifics 
welcome.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From presnick@qti.qualcomm.com  Thu Oct 10 20:08:46 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 632BB21F940D for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 20:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.677
X-Spam-Level: 
X-Spam-Status: No, score=-106.677 tagged_above=-999 required=5 tests=[AWL=-0.078, 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 BasulKOvFXj5 for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 20:08:41 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id D386921F94FF for <ietf@ietf.org>; Thu, 10 Oct 2013 20:08:34 -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=1381460914; x=1412996914; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=57QerM9I4VdNFYctlzR1oKchMWrYUdnBOwHwf0aqb6k=; b=FNPR7VGnIjl+8jgIriBMrSHntnHmeEGso78Y5cN2GrfYqOOHr8dgkVoF aaQBhS1u989MC2vT+hD+bUWz3S/uqlHE+Lq0B1EyS1wbNPKabcUYzcdau /SPuDz8c7NIqqzRX+p0cPKsE7U+YYEnBbvT+NijeyNrW6GKI6OYdzUcvZ 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="80237782"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 10 Oct 2013 20:08:34 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7224"; a="531654227"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Oct 2013 20:08:34 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Oct 2013 20:08:34 -0700
Message-ID: <52576BB1.6040708@qti.qualcomm.com>
Date: Thu, 10 Oct 2013 22:08:33 -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: Lou Berger <lberger@labn.net>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <5252AD9D.6010408@labn.net>
In-Reply-To: <5252AD9D.6010408@labn.net>
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 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, 11 Oct 2013 03:08:46 -0000

On 10/7/13 7:48 AM, Lou Berger wrote:
> I think it misses two
> important points that should be addressed prior to publication:
>
> 1)  The role WG/IETF mailing lists play in building and
>       gauging consensus
>    

Yeah, as I just replied to Tom, I think this is worth adding, probably 
in section 2 or 3.

> 2) That some participants/chairs/I*s like seeing hands, and that's okay
>    

Yes, this is directly said in section 4, paragraphs 4 & 5. What do you 
think is missing?

> There are different ways to achieve and determine consensus.  As stated
> in RFC2418:
>     Consensus
>     can be determined by a show of hands, humming, or any other means on
>     which the WG agrees (by rough consensus, of course).  Note that 51%
>     of the working group does not qualify as "rough consensus" and 99% is
>     better than rough.  It is up to the Chair to determine if rough
>     consensus has been reached.
>    

As I said in my reply to Dave, there's part of the above that I disagree 
with, or at least think is an oversimplification. But it definitely need 
citing.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From lars@netapp.com  Fri Oct 11 00:40: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 8F10C21E815F for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 00:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.353
X-Spam-Level: 
X-Spam-Status: No, score=-9.353 tagged_above=-999 required=5 tests=[AWL=1.246,  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 zEC8J6J4UaEg for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 00:40:21 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 84C9421F9978 for <ietf@ietf.org>; Fri, 11 Oct 2013 00:40:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1078,1371106800";  d="asc'?scan'208";a="98962289"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx12-out.netapp.com with ESMTP; 11 Oct 2013 00:40:03 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Fri, 11 Oct 2013 00:40:02 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Topic: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Index: AQHOxeuIoizTad4yck6szZA2fNTvZZnvk7OA
Date: Fri, 11 Oct 2013 07:40:02 +0000
Message-ID: <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.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=_20CDA380-A1CE-44B4-92D9-351744F92CB6"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
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, 11 Oct 2013 07:40:25 -0000

--Apple-Mail=_20CDA380-A1CE-44B4-92D9-351744F92CB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

I'm part of the design team. SM has written this document to begin a =
discussion with the broader IETF.

The document does not have the consensus of the design team, and it is =
therefore obviously not a recommendation by the design team.

Lars

On Oct 10, 2013, at 20:10, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Jari,
>=20
> Here's is a draft about improving the ISOC Fellowship programme to =
attract people from under-represented regions into the IETF.  The draft =
builds upon the ISOC work, proposing adjustments and additional efforts, =
with the goal of enabling more sustained and active participation by =
contributors from under-represented regions.
>=20
> In a blog article ( http://www.ietf.org/blog/2013/04/diversity/ ), it =
is mentioned that:
>=20
> "The design team will present their recommendations to the community,
>  and engage in the discussion.  Recommendations with community support
>  will be taken forward."
>=20
> The draft only makes suggestions instead of recommendations.  I am =
copying this message to ietf@ietf.org so that the community can comment =
about the draft.
>=20
> Regards,
> S. Moonesamy<draft-ddt-fellowship-03.txt>


--Apple-Mail=_20CDA380-A1CE-44B4-92D9-351744F92CB6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUlerU9ZcnpRveo1xAQIhcAP/QlfOofnr2DGCD06pRH9FVnBN/TAMUxmK
r2nQy+RBe/xO5s05/zMa1E2/D9PBrN2MwhXo8DiPMgqTrDTvyBc6mfDHU6O9PT+/
VAHFgtCL4zId9rhhIJsk3hyXIQJlbhuevmj6cnaD99CAWyLn2phFmh/0XSSNowdV
BjePtwRwkxE=
=1Sl2
-----END PGP SIGNATURE-----

--Apple-Mail=_20CDA380-A1CE-44B4-92D9-351744F92CB6--

From fgont@si6networks.com  Fri Oct 11 01:36:14 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 E99D921E80C7; Fri, 11 Oct 2013 01:36: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 UvEwTaGLwDdB; Fri, 11 Oct 2013 01:36:14 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7B021E80C1; Fri, 11 Oct 2013 01:36:13 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.193]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VUYCb-0007iu-Dz; Fri, 11 Oct 2013 10:36:05 +0200
Message-ID: <5257B870.1060003@si6networks.com>
Date: Fri, 11 Oct 2013 05:36:00 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>,  "Templin, Fred L" <Fred.L.Templin@boeing.com>, brian.e.carpenter@gmail.com
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>
In-Reply-To: <5257AD5E.9090806@globis.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@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, 11 Oct 2013 08:36:15 -0000

On 10/11/2013 04:48 AM, Ray Hunter wrote:
> 
> I think the draft does what it can in a pragmatic manner, but might
> benefit from some acknowledgement that this security approach of
> applying parsing at a single perimeter can never ever catch all variants
> of transporting FOO over BAR.

FWIW, my idea of the I-D is that it says "look, if you don't put all
this info into the first fragment, it's extremely likely that your
packets will be dropped". That doesn't mean that a middle-box may want
to look further. But looking further might imply
reassemble-inspect-and-refragment... or even reassemble the TCP stream
(e.g. think about a SSL/TCP-based VPN...)

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From abdussalambaryun@gmail.com  Fri Oct 11 01:41: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 C6B9311E817D for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 01:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, 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 Tp6pnY9IREH1 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 01:41:48 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9A111E818E for <ietf@ietf.org>; Fri, 11 Oct 2013 01:41:47 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id r10so3920966pdi.28 for <ietf@ietf.org>; Fri, 11 Oct 2013 01:41: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=JpQ9PTj1Zjl+0gt2z3DVbUbu7UXbd0Eq5kA24xTRywc=; b=mSETPklwUuVcXdR7vRlzv3XXbCQieKDHZkRmsDM6clyODQxy6WQuWQwJzVijQs0ZEf 6iRYxrXZK/Y7rHX3P2XQHYpNAvcnrC8QhClJwloyr2+Lz6RRJ4U3UkB79MvpPHlJz8v1 IllqplrcL6pheh6Qp7bZFEl6Qlxeb3LfrN9dVQF8MY6n6lm7hBI+2NTAaqCcIu4/W4fn ZEVQW45tM1XiBcFoG4gCDpWvlvP+JDiBaqJBeEin3qTTP6qq0aKMm+V6or8Gp20/7wiK rtUpGr4PQiLknGCuoQGe9N3HVOoUyH/SPx7hW2FoFPNleJ2mCQfSUaC4xqMGjzt2Hwti D20A==
MIME-Version: 1.0
X-Received: by 10.68.229.2 with SMTP id sm2mr18671279pbc.68.1381480907716; Fri, 11 Oct 2013 01:41:47 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 11 Oct 2013 01:41:47 -0700 (PDT)
In-Reply-To: <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>
Date: Fri, 11 Oct 2013 09:41:47 +0100
Message-ID: <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=047d7b162fd7c4bf0804e873169f
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 11 Oct 2013 08:41:48 -0000

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

I am part of the community design team as well because I participate with
community more than the private hidden groups. I think that the draft is a
true work open to IETF. I still did not get a reply to my request to know
what is the DT authority, very strange name without any procedure in IETF,
please explain,

AB


On Fri, Oct 11, 2013 at 8:40 AM, Eggert, Lars <lars@netapp.com> wrote:

> Hi,
>
> I'm part of the design team. SM has written this document to begin a
> discussion with the broader IETF.
>
> The document does not have the consensus of the design team, and it is
> therefore obviously not a recommendation by the design team.
>
> Lars
>
> On Oct 10, 2013, at 20:10, S Moonesamy <sm+ietf@elandsys.com> wrote:
> > Hi Jari,
> >
> > Here's is a draft about improving the ISOC Fellowship programme to
> attract people from under-represented regions into the IETF.  The draft
> builds upon the ISOC work, proposing adjustments and additional efforts,
> with the goal of enabling more sustained and active participation by
> contributors from under-represented regions.
> >
> > In a blog article ( http://www.ietf.org/blog/2013/04/diversity/ ), it
> is mentioned that:
> >
> > "The design team will present their recommendations to the community,
> >  and engage in the discussion.  Recommendations with community support
> >  will be taken forward."
> >
> > The draft only makes suggestions instead of recommendations.  I am
> copying this message to ietf@ietf.org so that the community can comment
> about the draft.
> >
> > Regards,
> > S. Moonesamy<draft-ddt-fellowship-03.txt>
>
>

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

<div dir=3D"ltr"><div>I am part of the community design team as well becaus=
e I participate with community more than the private hidden=A0groups. I thi=
nk that the draft is a true work open to IETF. I still did not get a reply =
to my request to know what is the DT authority, very strange name without a=
ny procedure in IETF, please explain,</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Oct 11, 2013 at 8:40 AM, Eggert, Lars <span dir=
=3D"ltr">&lt;<a href=3D"mailto:lars@netapp.com" target=3D"_blank">lars@neta=
pp.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">Hi,<br>
<br>
I&#39;m part of the design team. SM has written this document to begin a di=
scussion with the broader IETF.<br>
<br>
The document does not have the consensus of the design team, and it is ther=
efore obviously not a recommendation by the design team.<br>
<br>
Lars<br>
<div><div class=3D"h5"><br>
On Oct 10, 2013, at 20:10, S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elan=
dsys.com">sm+ietf@elandsys.com</a>&gt; wrote:<br>
&gt; Hi Jari,<br>
&gt;<br>
&gt; Here&#39;s is a draft about improving the ISOC Fellowship programme to=
 attract people from under-represented regions into the IETF. =A0The draft =
builds upon the ISOC work, proposing adjustments and additional efforts, wi=
th the goal of enabling more sustained and active participation by contribu=
tors from under-represented regions.<br>

&gt;<br>
&gt; In a blog article ( <a href=3D"http://www.ietf.org/blog/2013/04/divers=
ity/" target=3D"_blank">http://www.ietf.org/blog/2013/04/diversity/</a> ), =
it is mentioned that:<br>
&gt;<br>
&gt; &quot;The design team will present their recommendations to the commun=
ity,<br>
&gt; =A0and engage in the discussion. =A0Recommendations with community sup=
port<br>
&gt; =A0will be taken forward.&quot;<br>
&gt;<br>
&gt; The draft only makes suggestions instead of recommendations. =A0I am c=
opying this message to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> s=
o that the community can comment about the draft.<br>
&gt;<br>
&gt; Regards,<br>
</div></div>&gt; S. Moonesamy&lt;draft-ddt-fellowship-03.txt&gt;<br>
<br>
</blockquote></div><br></div>

--047d7b162fd7c4bf0804e873169f--

From abdussalambaryun@gmail.com  Fri Oct 11 01:50:18 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 7B2B821E80C7 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 01:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[AWL=-0.111,  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 PdM60oaC87lH for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 01:50:17 -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 1127D11E8144 for <ietf@ietf.org>; Fri, 11 Oct 2013 01:50:17 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so3884961pbb.41 for <ietf@ietf.org>; Fri, 11 Oct 2013 01:50: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=v+gj0kxA/iTy4M+j8hz/d4rOGY+eK0bFYIkZdAlG7ns=; b=RnTamcli/E9xLpFFue3LQ1u+VSjFF75/EKw3PhG5vt/NO/t8iS9hLovGxFC8Hni364 LAd9HPduozul2iXmE5LgQxYzB0hSwPELHIfcFX2zNqz+CsIhdsnoU5oWSKBV4itTtQqw kEKsS034bVS90jgC4qkUtZxSDhOjETVldRZMd4xzy2m8YCUIxWpxDrGXhjHo4AkqqTF/ 39ds+sRHpBURyCf44GsuW/t5Bdo6Vr58ut1cRCykJvuRNUo3kS/SH7lZxBdAFIiy6pnB WkXQRdZ/uJOQTDNK/Dg4iLYUWA5HzESFudpdOwbvKU0ugFqjoM9Ed8a4K7ZWCrAPE8/h mRcA==
MIME-Version: 1.0
X-Received: by 10.66.162.167 with SMTP id yb7mr20550589pab.16.1381481416775; Fri, 11 Oct 2013 01:50:16 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 11 Oct 2013 01:50:16 -0700 (PDT)
In-Reply-To: <52576A52.8030002@qti.qualcomm.com>
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net> <52524A68.7040800@qti.qualcomm.com> <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net> <52576A52.8030002@qti.qualcomm.com>
Date: Fri, 11 Oct 2013 09:50:16 +0100
Message-ID: <CADnDZ88iuXJ94Apjqq3j6szbwOCj_9-MvBp36=6+Q2TWgVViig@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=047d7bacbe701c5eac04e8733560
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, 11 Oct 2013 08:50:18 -0000

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

Hi Pete,

I object if the draft excludes remote participants opinions/feedbacks, the
IETF WG list is the main place for measuring consensus not a physical
limited room located in a region. Some WGs' Chair just follow room's
consensus, or f2f participants arguments, which is not best practice
relating to IETF procedures. The most important facility of IETF is that it
works/decides remotely with individuals signatures/confirmations.

AB


On Fri, Oct 11, 2013 at 4:02 AM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 10/8/13 8:56 AM, t.p. wrote:
>
>> 1) It does not state its target audience until, perhaps, the reference
>> in the Conclusions, to WG Chairs.  [...]  Are
>>
>> ADs assumed to be above and beyond the considerations in this I-D:-(
>>
>>
>
> An excellent point. No, *every* consensus caller in the IETF should in my
> view be taking these points into consideration, ADs and chairs alike. The
> examples are full of WG/chair stories, but exactly the same kinds of things
> should happen, IMO, when ADs make consensus calls.
>
> As I said elsewhere, my primary (though not sole) audience is IETF
> leadership (ADs, chairs, editors, secretaries, etc.) and experienced
> IETFers who already understand the basics of our process and/or might some
> day wish to be in such roles. Hopefully the document is somewhat accessible
> to newer or once-in-a-blue-moon participants, but I hope the main consumers
> of this document are folks who need to make consensus calls or might some
> day.
>
>
>  2)  There is an extensive discussion on the show of hands and the hum.
>> What technology allows you to conduct those on a mailing list?
>>
>>
>
> I don't really talk about mailing lists, and I think you're right that
> it's worth spending at least a bit of time on in the document. In fact,
> neither a "hum" or a show of "hands" (messages?) on a mailing list makes a
> bunch of sense. Methodologically, I think the best way for chairs (or ADs)
> to deal with a mailing list is to checkpoint every so often, summarizing
> issues and perhaps even keeping an issues list, and then explicitly calling
> the consensus: "I hear that people are in favor of X and I haven't heard
> strong objections. Unless there's anyone who can't live with X, I am going
> to say that we have consensus for it." It's the same sort of thing I
> describe for f2f conclusions of consensus. I think that's worth pointing
> out.
>
>
>  3) References to working groups with 100 active participants sound like
>> a chimera.
>>
>>
>
> The only place where there's mention of large groups is in the last two
> sections, which are specifically the extreme examples. They are
> illustrative examples of the worst case scenario, not meant to be
> representational of the common case.
>
>
>  4)  "Five people for and one hundred people against might still be rough
>>      consensus".  Can you see the presumption in that?  Read on and the
>> following text makes it clear that five are 'right' and one hundred
>> 'wrong', but you are presuming that "for" is the right answer.
>>
>
> Yes, that's the example I've used. In this example, the five people have
> made their case for a technical solution, one person has made an objection,
> the five people fully address the objection, and therefore there is rough
> consensus. So in this case consensus was "for". The example is meant to
> show that 100 people blindly piling on the "against" side does not make
> them "right" and does not change the consensus.
>
>
>  The
>> right answer to a consensus call is a consensus,which can be "against",
>> as much as "for", something that does not seem to be contemplated here.
>>
>>
>
> Sure. But that would be a different example.
>
> I don't understand your concern here.
>
>
>  5) Good WG chairs, and happily there are plenty of them, make their
>> presumptions plain, as in asking for information about implementations
>> at or around judging consensus.  The views of someone who has
>> independently produced rough code is then likely to outweigh those of a
>> dozen people who have not, so three such expressing a view in one
>> direction will prevail over several dozen who have not in the opposite
>> direction.  (This is all right as far as it goes, but I would like the
>> views of users and operators to count for even more, since it is they
>> who have the most to gain or lose; but sadly, their representation here
>> is small and often not apparent).  You quote Dave Clark's aphorism but
>> then ignore half of it.
>>
>>
>
> Two things about this:
>
> 1. This document is about how we can come to consensus, not about the
> criteria around which we get that consensus (of which running code is one).
> And interesting document could be written about how we do (and sometimes
> don't) take running code into account, but it's not this document.
>
> 2. I take issue with one thing you do say above: "The views of someone who
> has independently produced rough code is then likely to outweigh those of a
> dozen people who have not". I think this is actually wrong: It is not that
> the implementer's view is given more weight *because it came from the
> implementer*; that would be an ad hominem judgement. The implementer's view
> is given more weight when it contains a solid technical case based on
> implementation experience. If an implementer says, "I've implemented this
> code and I can tell you that the way you are proposing won't interoperate",
> and someone with no implementation experience is able to say, "I can point
> you to implementations X Y and Z that implemented it my way and do
> interoperate", the fact that it's an implementer should make no difference
> at all. It is the existence of the implementation and how well it works
> that's the trump card, not who talks about it.
>
>
>  6)  The document is strangely silent about what the vast mass of the
>> IETF who are not WG Chairs might do to help reach a consensus,
>> such as express an opinion, clearly, technically; else, perhaps, keep
>> quiet.
>>
>>
>
> I think the document is useful without this discussion. I certainly would
> not object to adding such a section in the future, but I don't think it's
> necessary in this version. Again, this is mostly aimed at discussions of
> how leaders can facilitate getting to consensus.
>
>
>  7) As has been said before when documents like this are up for
>> discussion, the IETF is an organisation of engineers and, for the most
>> part, we do it rather well.  Managing and leading loose and diverse
>> groups of people is more psychology or sociology  than technology, at
>> which we are mostly amateurs.  We then go beyond our capabilities and
>> get it wrong.  As here.
>>
>>
>
> I'm not clear on how the discussions of how to manage and lead consensus
> discussion that are presented in the document you think "gets it wrong".
> Quite a few folks have found it useful and productive. More specifics
> welcome.
>
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.**com/~presnick/<http://www.qualcomm.com/~presnick/>
> >
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div>Hi Pete,</div><div>=A0</div><div>I object if the draf=
t excludes remote participants opinions/feedbacks, the IETF WG list is the =
main place for measuring consensus not a physical limited room located in a=
 region. Some WGs&#39; Chair just follow room&#39;s consensus, or f2f parti=
cipants arguments, which is not best practice relating to IETF procedures. =
The most important facility of IETF is that it works/decides remotely with =
individuals signatures/confirmations.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Oct 11, 2013 at 4:02 AM, Pete Resnick <span dir=
=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank"=
>presnick@qti.qualcomm.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 10/8/13 8:56 AM, t.p. w=
rote:<br>
</div><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"><div class=3D"im">
1) It does not state its target audience until, perhaps, the reference<br><=
/div>
in the Conclusions, to WG Chairs. =A0[...] =A0Are<div class=3D"im"><br>
ADs assumed to be above and beyond the considerations in this I-D:-(<br>
=A0 =A0<br>
</div></blockquote>
<br>
An excellent point. No, *every* consensus caller in the IETF should in my v=
iew be taking these points into consideration, ADs and chairs alike. The ex=
amples are full of WG/chair stories, but exactly the same kinds of things s=
hould happen, IMO, when ADs make consensus calls.<br>

<br>
As I said elsewhere, my primary (though not sole) audience is IETF leadersh=
ip (ADs, chairs, editors, secretaries, etc.) and experienced IETFers who al=
ready understand the basics of our process and/or might some day wish to be=
 in such roles. Hopefully the document is somewhat accessible to newer or o=
nce-in-a-blue-moon participants, but I hope the main consumers of this docu=
ment are folks who need to make consensus calls or might some day.<div clas=
s=3D"im">
<br>
<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">
2) =A0There is an extensive discussion on the show of hands and the hum.<br=
>
What technology allows you to conduct those on a mailing list?<br>
=A0 =A0<br>
</blockquote>
<br></div>
I don&#39;t really talk about mailing lists, and I think you&#39;re right t=
hat it&#39;s worth spending at least a bit of time on in the document. In f=
act, neither a &quot;hum&quot; or a show of &quot;hands&quot; (messages?) o=
n a mailing list makes a bunch of sense. Methodologically, I think the best=
 way for chairs (or ADs) to deal with a mailing list is to checkpoint every=
 so often, summarizing issues and perhaps even keeping an issues list, and =
then explicitly calling the consensus: &quot;I hear that people are in favo=
r of X and I haven&#39;t heard strong objections. Unless there&#39;s anyone=
 who can&#39;t live with X, I am going to say that we have consensus for it=
.&quot; It&#39;s the same sort of thing I describe for f2f conclusions of c=
onsensus. I think that&#39;s worth pointing out.<div class=3D"im">
<br>
<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">
3) References to working groups with 100 active participants sound like<br>
a chimera.<br>
=A0 =A0<br>
</blockquote>
<br></div>
The only place where there&#39;s mention of large groups is in the last two=
 sections, which are specifically the extreme examples. They are illustrati=
ve examples of the worst case scenario, not meant to be representational of=
 the common case.<div class=3D"im">
<br>
<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">
4) =A0&quot;Five people for and one hundred people against might still be r=
ough<br>
=A0 =A0 =A0consensus&quot;. =A0Can you see the presumption in that? =A0Read=
 on and the<br>
following text makes it clear that five are &#39;right&#39; and one hundred=
<br>
&#39;wrong&#39;, but you are presuming that &quot;for&quot; is the right an=
swer.<br>
</blockquote>
<br></div>
Yes, that&#39;s the example I&#39;ve used. In this example, the five people=
 have made their case for a technical solution, one person has made an obje=
ction, the five people fully address the objection, and therefore there is =
rough consensus. So in this case consensus was &quot;for&quot;. The example=
 is meant to show that 100 people blindly piling on the &quot;against&quot;=
 side does not make them &quot;right&quot; and does not change the consensu=
s.<div class=3D"im">
<br>
<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">
The<br>
right answer to a consensus call is a consensus,which can be &quot;against&=
quot;,<br>
as much as &quot;for&quot;, something that does not seem to be contemplated=
 here.<br>
=A0 =A0<br>
</blockquote>
<br></div>
Sure. But that would be a different example.<br>
<br>
I don&#39;t understand your concern here.<div class=3D"im"><br>
<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">
5) Good WG chairs, and happily there are plenty of them, make their<br>
presumptions plain, as in asking for information about implementations<br>
at or around judging consensus. =A0The views of someone who has<br>
independently produced rough code is then likely to outweigh those of a<br>
dozen people who have not, so three such expressing a view in one<br>
direction will prevail over several dozen who have not in the opposite<br>
direction. =A0(This is all right as far as it goes, but I would like the<br=
>
views of users and operators to count for even more, since it is they<br>
who have the most to gain or lose; but sadly, their representation here<br>
is small and often not apparent). =A0You quote Dave Clark&#39;s aphorism bu=
t<br>
then ignore half of it.<br>
=A0 =A0<br>
</blockquote>
<br></div>
Two things about this:<br>
<br>
1. This document is about how we can come to consensus, not about the crite=
ria around which we get that consensus (of which running code is one). And =
interesting document could be written about how we do (and sometimes don&#3=
9;t) take running code into account, but it&#39;s not this document.<br>

<br>
2. I take issue with one thing you do say above: &quot;The views of someone=
 who has independently produced rough code is then likely to outweigh those=
 of a dozen people who have not&quot;. I think this is actually wrong: It i=
s not that the implementer&#39;s view is given more weight *because it came=
 from the implementer*; that would be an ad hominem judgement. The implemen=
ter&#39;s view is given more weight when it contains a solid technical case=
 based on implementation experience. If an implementer says, &quot;I&#39;ve=
 implemented this code and I can tell you that the way you are proposing wo=
n&#39;t interoperate&quot;, and someone with no implementation experience i=
s able to say, &quot;I can point you to implementations X Y and Z that impl=
emented it my way and do interoperate&quot;, the fact that it&#39;s an impl=
ementer should make no difference at all. It is the existence of the implem=
entation and how well it works that&#39;s the trump card, not who talks abo=
ut it.<div class=3D"im">
<br>
<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">
6) =A0The document is strangely silent about what the vast mass of the<br>
IETF who are not WG Chairs might do to help reach a consensus,<br>
such as express an opinion, clearly, technically; else, perhaps, keep<br>
quiet.<br>
=A0 =A0<br>
</blockquote>
<br></div>
I think the document is useful without this discussion. I certainly would n=
ot object to adding such a section in the future, but I don&#39;t think it&=
#39;s necessary in this version. Again, this is mostly aimed at discussions=
 of how leaders can facilitate getting to consensus.<div class=3D"im">
<br>
<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">
7) As has been said before when documents like this are up for<br>
discussion, the IETF is an organisation of engineers and, for the most<br>
part, we do it rather well. =A0Managing and leading loose and diverse<br>
groups of people is more psychology or sociology =A0than technology, at<br>
which we are mostly amateurs. =A0We then go beyond our capabilities and<br>
get it wrong. =A0As here.<br>
=A0 =A0<br>
</blockquote>
<br></div>
I&#39;m not clear on how the discussions of how to manage and lead consensu=
s discussion that are presented in the document you think &quot;gets it wro=
ng&quot;. Quite a few folks have found it useful and productive. More speci=
fics welcome.<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" targ=
et=3D"_blank" value=3D"+18586514478">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div>

--047d7bacbe701c5eac04e8733560--

From lars@netapp.com  Fri Oct 11 02:07:20 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 75FEF21E8168 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:07:20 -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=[AWL=-2.708, 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 tbCjIADX1eqN for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:07:15 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id CB83E21E80DF for <ietf@ietf.org>; Fri, 11 Oct 2013 02:07:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1079,1371106800";  d="asc'?scan'208";a="58691952"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 11 Oct 2013 02:07:04 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Fri, 11 Oct 2013 02:07:04 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Topic: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Index: AQHOxl25TnWHqJt3hkCSo8I+sKIrxZnvqx4A
Date: Fri, 11 Oct 2013 09:07:03 +0000
Message-ID: <CF65E851-FD58-4798-A7A7-C45EFB03F8EF@netapp.com>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com> <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com>
In-Reply-To: <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.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=_FB413303-0070-4240-82BF-03DC2730425B"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Bob Hinden <bob.hinden@gmail.com>, 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: Fri, 11 Oct 2013 09:07:20 -0000

--Apple-Mail=_FB413303-0070-4240-82BF-03DC2730425B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On Oct 11, 2013, at 10:41, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
> I am part of the community design team as well because I participate =
with
> community more than the private hidden groups. I think that the draft =
is a
> true work open to IETF.

I haven't said that anything to the contrary. I am simply pointing out =
that the draft is not a recommendation by the design team (which we will =
still make at some point in the near future, hopefully.)

> I still did not get a reply to my request to know
> what is the DT authority, very strange name without any procedure in =
IETF,
> please explain,

Jari formed the design team in order to collect the issues that people =
have raised, organize them and then propose a few recommendations to the =
broader community. The design team has no authority, all we will do is =
propose some actions to the broader community, which will then need to =
get consensus there. Nothing is stopping anyone outside the design team =
from also thinking about these issues and making proposals.

Also, the IETF has a long history of using design teams in working =
groups. We also use small, focused groups for other purposes, such as =
BOF planning. Whatever these groups still needs to get consensus in the =
broader community.

Lars

--Apple-Mail=_FB413303-0070-4240-82BF-03DC2730425B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUle/uNZcnpRveo1xAQKx5AQAlBtsavFJEF2EHpzgN3pVsedoAPthRpq3
kWGS1gQs3Q+bs0eEeDLd4qCGVGAPrgRLHREpF9/MyBGR/dCoDR+U5ZtvMzG0fnsP
NWZ/icOhm7xMqmAcheQHZ6RkWQuVbFIj/GITayg8dqwdpQsZqgiJx9BCb1pP4m5h
PABRaZTKEjU=
=cV8t
-----END PGP SIGNATURE-----

--Apple-Mail=_FB413303-0070-4240-82BF-03DC2730425B--

From daedulus@btconnect.com  Fri Oct 11 02:35:03 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 F28A111E8183 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[AWL=-1.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 Zy5h02MhuSil for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:34:56 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) by ietfa.amsl.com (Postfix) with ESMTP id 68A7811E818A for <ietf@ietf.org>; Fri, 11 Oct 2013 02:34:49 -0700 (PDT)
Received: from mail127-db9-R.bigfish.com (10.174.16.237) by DB9EHSOBE023.bigfish.com (10.174.14.86) with Microsoft SMTP Server id 14.1.225.22; Fri, 11 Oct 2013 09:34:48 +0000
Received: from mail127-db9 (localhost [127.0.0.1])	by mail127-db9-R.bigfish.com (Postfix) with ESMTP id 8889460155; Fri, 11 Oct 2013 09:34:48 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: PS-13(z569dh2b68kzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275bh8275dhz2dh2a8h5a9h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail127-db9 (localhost.localdomain [127.0.0.1]) by mail127-db9 (MessageSwitch) id 1381484086388070_27063; Fri, 11 Oct 2013 09:34:46 +0000 (UTC)
Received: from DB9EHSMHS003.bigfish.com (unknown [10.174.16.242])	by mail127-db9.bigfish.com (Postfix) with ESMTP id 523673C0084; Fri, 11 Oct 2013 09:34:46 +0000 (UTC)
Received: from AMSPRD0710HT004.eurprd07.prod.outlook.com (157.56.249.85) by DB9EHSMHS003.bigfish.com (10.174.14.13) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 11 Oct 2013 09:34:46 +0000
Received: from DB3PRD0411HT005.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.160.167) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 11 Oct 2013 09:34:43 +0000
Message-ID: <020801cec664$de3ea600$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu> <52570222.5090601@gmail.com>
Subject: Re: leader statements
Date: Fri, 11 Oct 2013 10:32:44 +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.53]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 11 Oct 2013 09:35:03 -0000

----- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "Noel Chiappa" <jnc@mercury.lcs.mit.edu>
Cc: <ietf@ietf.org>
Sent: Thursday, October 10, 2013 8:38 PM
> On 11/10/2013 07:52, Noel Chiappa wrote:
> >     > From: Arturo Servin <arturo.servin@gmail.com>
> >     > Then we have a big problem as organization, we are then
leaderless.
> >
> > I'm not sure this is true. The IETF worked quite well (and produced
a lot of
> > good stuff) back in, e.g. the Phill Gross era, when I am pretty sure
Phill's
> > model of his job was indeed as a 'facilitator', not a 'leader' in
the sense
> > you seem to be thinking of. So why do we now need a 'leader'?
>
> We have a collective leadership, which is quite a good system as long
as
> it avoids groupthink, and I think the IETF community is talkative
enough
> to reduce (not eliminate) that risk. But when we're invited to wider
> inter-organisation meetings, we can't all go, and the ones who do go
> are certain to be viewed as our leaders by the other organisations.

And that for me is the point.  Regardless of how we view ourselves, it
is also a question of how others view us and, almost without exception,
organisations have leaders and will expect us to be the same.  If we
want to be perceived as leaderless, we are going to have to work a lot
harder at promulgating that point of view; and even then, I expect we
would fail.

Tom Petch


> Inevitably, it's the Chairs who get invited; up to them to delegate
> if they want.
>
>   Brian
>



From simon.perreault@viagenie.ca  Fri Oct 11 02:40:47 2013
Return-Path: <simon.perreault@viagenie.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 F3E1A21E80E4 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:40:46 -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 W4jQWfcnpJCY for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:40:46 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9011821E80F7 for <ietf@ietf.org>; Fri, 11 Oct 2013 02:40:44 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:41c9:83f1:e70a:4e62]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C9561403BE for <ietf@ietf.org>; Fri, 11 Oct 2013 05:40:43 -0400 (EDT)
Message-ID: <5257C79A.9090004@viagenie.ca>
Date: Fri, 11 Oct 2013 11:40:42 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type (see <draft-hausenblas-csv-fragment-06.txt>)
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
In-Reply-To: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
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, 11 Oct 2013 09:40:47 -0000

This draft's premise is interesting, but the implementation leaves to be
desired. That is, I like the idea of fragment identifiers for CSV, but
row/column/cell-based selection doesn't address my need.

My need is based on the CSV files generated from IANA registries. Here's
one:

https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.csv

Here's an excerpt:

2001:0200::/23,APNIC,1999-07-01,whois.apnic.net,ALLOCATED,
2001:0400::/23,ARIN,1999-07-01,whois.arin.net,ALLOCATED,
2001:0600::/23,RIPE NCC,1999-07-01,whois.ripe.net,ALLOCATED,

In general, for IANA registries, what would be useful would be fragments
pointing to a particular record or a set of records. It seems like
row-based selection would accomplish that purpose, right? Well, yes, but
not in a useful way, because the row *index* is used in the fragment.
The problem is that when IANA inserts new records, all records that come
after the new one are moved one row down, and the URL containing the
fragment is no longer valid and needs to be updated. That's not cool.
What we need is a fragment that points to the record without needing to
be updated when new records are added. That is, I want to be able to say
something like this:

.../ipv6-unicast-address-assignments.csv#2001:0200::/23

I think this is an important use case, and I would like the draft to be
updated to address it.

Thanks,
Simon

From cabo@tzi.org  Fri Oct 11 02:42:51 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 BC23921F8FAC for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.145
X-Spam-Level: 
X-Spam-Status: No, score=-106.145 tagged_above=-999 required=5 tests=[AWL=0.104, 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 xwPKX1ZatrNC for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:42: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 0CE3621F9D1E for <ietf@ietf.org>; Fri, 11 Oct 2013 02:42:46 -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 r9B9ggsA013042 for <ietf@ietf.org>; Fri, 11 Oct 2013 11:42:42 +0200 (CEST)
Received: from [192.168.217.105] (p54890CAC.dip0.t-ipconnect.de [84.137.12.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EE9D5925; Fri, 11 Oct 2013 11:42:41 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: "The core Internet institutions abandon the US Government" 
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
Date: Fri, 11 Oct 2013 11:42:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7220D9C-E465-4532-B9AE-3F9233989A5B@tzi.org>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Oct 2013 09:42:51 -0000

> =
http://www.internetsociety.org/news/montevideo-statement-future-internet-c=
ooperation


=
http://www.internetgovernance.org/2013/10/11/the-core-internet-institution=
s-abandon-the-us-government/?
"The core Internet institutions abandon the US Government | IGP Blog"

I'm not quite sure I read the Montevideo statement the way this headline =
suggests.
(The US government must feel so abandoned these days...)
But that is the danger of saying anything at all.

Gr=FC=DFe, Carsten


From loa@pi.nu  Fri Oct 11 02:55:41 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 2C66B21F9A57 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:55: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 XlQZnTlRPDx3 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:55:36 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 56C0B21E81B2 for <ietf@ietf.org>; Fri, 11 Oct 2013 02:55:33 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.84.108]) (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 8B32218033E5; Fri, 11 Oct 2013 11:55:31 +0200 (CEST)
Message-ID: <5257CB10.6030603@pi.nu>
Date: Fri, 11 Oct 2013 17:55:28 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <6D6D0B71-EA7A-430E-BCC1-16BEF2BD98D4@mnot.net> <52524A68.7040800@qti.qualcomm.com> <022201cec42e$4825ce60$4001a8c0@gateway.2wire.net> <52576A52.8030002@qti.qualcomm.com> <CADnDZ88iuXJ94Apjqq3j6szbwOCj_9-MvBp36=6+Q2TWgVViig@mail.gmail.com>
In-Reply-To: <CADnDZ88iuXJ94Apjqq3j6szbwOCj_9-MvBp36=6+Q2TWgVViig@mail.gmail.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, 11 Oct 2013 09:55:41 -0000

AB,

I'm very close to take offense by the statement "...WGs' Chair just
follow room's consensus, or f2f participants arguments".

We have maybe 200+ working group chairs, ADs and other people that
need at a rate, from several times a week to maybe once a months make a
"consensus calls". I'm certain that all of does "just" consider the
meeting room  when doing so. I believe that we have a fairly good view
of what rough consensus is, the method to get there and that we are
consistently successful in making the consensus calls, the entire
working group included.

What Pete very successfully and carefully does is that he, investigates
a number of parameters that wg chairs and others need to consider
before/when making a consensus call. Not discussing "the room" would
be a bad thing, but I can't find that anyone is "excluded". You are
here discussing, aren't you?

One thing that I could have a concern about with Pete's document is
that the wg mailing lists are only mentioned twice, but I don't
consider that a proposal from Pete to move away from doing most of
our work on the mailing lists.

/Loa

On 2013-10-11 16:50, Abdussalam Baryun wrote:
> Hi Pete,
> I object if the draft excludes remote participants opinions/feedbacks,
> the IETF WG list is the main place for measuring consensus not a
> physical limited room located in a region. Some WGs' Chair just follow
> room's consensus, or f2f participants arguments, which is not best
> practice relating to IETF procedures. The most important facility of
> IETF is that it works/decides remotely with individuals
> signatures/confirmations.
> AB
>
>
> On Fri, Oct 11, 2013 at 4:02 AM, Pete Resnick <presnick@qti.qualcomm.com
> <mailto:presnick@qti.qualcomm.com>> wrote:
>
>     On 10/8/13 8:56 AM, t.p. wrote:
>
>         1) It does not state its target audience until, perhaps, the
>         reference
>         in the Conclusions, to WG Chairs.  [...]  Are
>
>         ADs assumed to be above and beyond the considerations in this I-D:-(
>
>
>     An excellent point. No, *every* consensus caller in the IETF should
>     in my view be taking these points into consideration, ADs and chairs
>     alike. The examples are full of WG/chair stories, but exactly the
>     same kinds of things should happen, IMO, when ADs make consensus calls.
>
>     As I said elsewhere, my primary (though not sole) audience is IETF
>     leadership (ADs, chairs, editors, secretaries, etc.) and experienced
>     IETFers who already understand the basics of our process and/or
>     might some day wish to be in such roles. Hopefully the document is
>     somewhat accessible to newer or once-in-a-blue-moon participants,
>     but I hope the main consumers of this document are folks who need to
>     make consensus calls or might some day.
>
>
>         2)  There is an extensive discussion on the show of hands and
>         the hum.
>         What technology allows you to conduct those on a mailing list?
>
>
>     I don't really talk about mailing lists, and I think you're right
>     that it's worth spending at least a bit of time on in the document.
>     In fact, neither a "hum" or a show of "hands" (messages?) on a
>     mailing list makes a bunch of sense. Methodologically, I think the
>     best way for chairs (or ADs) to deal with a mailing list is to
>     checkpoint every so often, summarizing issues and perhaps even
>     keeping an issues list, and then explicitly calling the consensus:
>     "I hear that people are in favor of X and I haven't heard strong
>     objections. Unless there's anyone who can't live with X, I am going
>     to say that we have consensus for it." It's the same sort of thing I
>     describe for f2f conclusions of consensus. I think that's worth
>     pointing out.
>
>
>         3) References to working groups with 100 active participants
>         sound like
>         a chimera.
>
>
>     The only place where there's mention of large groups is in the last
>     two sections, which are specifically the extreme examples. They are
>     illustrative examples of the worst case scenario, not meant to be
>     representational of the common case.
>
>
>         4)  "Five people for and one hundred people against might still
>         be rough
>               consensus".  Can you see the presumption in that?  Read on
>         and the
>         following text makes it clear that five are 'right' and one hundred
>         'wrong', but you are presuming that "for" is the right answer.
>
>
>     Yes, that's the example I've used. In this example, the five people
>     have made their case for a technical solution, one person has made
>     an objection, the five people fully address the objection, and
>     therefore there is rough consensus. So in this case consensus was
>     "for". The example is meant to show that 100 people blindly piling
>     on the "against" side does not make them "right" and does not change
>     the consensus.
>
>
>         The
>         right answer to a consensus call is a consensus,which can be
>         "against",
>         as much as "for", something that does not seem to be
>         contemplated here.
>
>
>     Sure. But that would be a different example.
>
>     I don't understand your concern here.
>
>
>         5) Good WG chairs, and happily there are plenty of them, make their
>         presumptions plain, as in asking for information about
>         implementations
>         at or around judging consensus.  The views of someone who has
>         independently produced rough code is then likely to outweigh
>         those of a
>         dozen people who have not, so three such expressing a view in one
>         direction will prevail over several dozen who have not in the
>         opposite
>         direction.  (This is all right as far as it goes, but I would
>         like the
>         views of users and operators to count for even more, since it is
>         they
>         who have the most to gain or lose; but sadly, their
>         representation here
>         is small and often not apparent).  You quote Dave Clark's
>         aphorism but
>         then ignore half of it.
>
>
>     Two things about this:
>
>     1. This document is about how we can come to consensus, not about
>     the criteria around which we get that consensus (of which running
>     code is one). And interesting document could be written about how we
>     do (and sometimes don't) take running code into account, but it's
>     not this document.
>
>     2. I take issue with one thing you do say above: "The views of
>     someone who has independently produced rough code is then likely to
>     outweigh those of a dozen people who have not". I think this is
>     actually wrong: It is not that the implementer's view is given more
>     weight *because it came from the implementer*; that would be an ad
>     hominem judgement. The implementer's view is given more weight when
>     it contains a solid technical case based on implementation
>     experience. If an implementer says, "I've implemented this code and
>     I can tell you that the way you are proposing won't interoperate",
>     and someone with no implementation experience is able to say, "I can
>     point you to implementations X Y and Z that implemented it my way
>     and do interoperate", the fact that it's an implementer should make
>     no difference at all. It is the existence of the implementation and
>     how well it works that's the trump card, not who talks about it.
>
>
>         6)  The document is strangely silent about what the vast mass of the
>         IETF who are not WG Chairs might do to help reach a consensus,
>         such as express an opinion, clearly, technically; else, perhaps,
>         keep
>         quiet.
>
>
>     I think the document is useful without this discussion. I certainly
>     would not object to adding such a section in the future, but I don't
>     think it's necessary in this version. Again, this is mostly aimed at
>     discussions of how leaders can facilitate getting to consensus.
>
>
>         7) As has been said before when documents like this are up for
>         discussion, the IETF is an organisation of engineers and, for
>         the most
>         part, we do it rather well.  Managing and leading loose and diverse
>         groups of people is more psychology or sociology  than
>         technology, at
>         which we are mostly amateurs.  We then go beyond our
>         capabilities and
>         get it wrong.  As here.
>
>
>     I'm not clear on how the discussions of how to manage and lead
>     consensus discussion that are presented in the document you think
>     "gets it wrong". Quite a few folks have found it useful and
>     productive. More specifics welcome.
>
>
>     pr
>
>     --
>     Pete Resnick<http://www.qualcomm.__com/~presnick/
>     <http://www.qualcomm.com/~presnick/>>
>     Qualcomm Technologies, Inc. - +1 (858)651-4478
>     <tel:%2B1%20%28858%29651-4478>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From daedulus@btconnect.com  Fri Oct 11 02:56:38 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 A722C21E81BA for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=-0.850, 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 UxhpKRQ1+UnN for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 02:56:33 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0252.outbound.messaging.microsoft.com [213.199.154.252]) by ietfa.amsl.com (Postfix) with ESMTP id 9288A21E81BB for <ietf@ietf.org>; Fri, 11 Oct 2013 02:56:17 -0700 (PDT)
Received: from mail193-db9-R.bigfish.com (10.174.16.251) by DB9EHSOBE023.bigfish.com (10.174.14.86) with Microsoft SMTP Server id 14.1.225.22; Fri, 11 Oct 2013 09:56:16 +0000
Received: from mail193-db9 (localhost [127.0.0.1])	by mail193-db9-R.bigfish.com (Postfix) with ESMTP id 84E2130005E; Fri, 11 Oct 2013 09:56:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I542I1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah1de097h186068h8275bh8275dhz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail193-db9 (localhost.localdomain [127.0.0.1]) by mail193-db9 (MessageSwitch) id 1381485375238396_897; Fri, 11 Oct 2013 09:56:15 +0000 (UTC)
Received: from DB9EHSMHS020.bigfish.com (unknown [10.174.16.228])	by mail193-db9.bigfish.com (Postfix) with ESMTP id 301F54E00D2; Fri, 11 Oct 2013 09:56:15 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by DB9EHSMHS020.bigfish.com (10.174.14.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 11 Oct 2013 09:56:14 +0000
Received: from DB3PRD0411HT005.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 11 Oct 2013 09:56:13 +0000
Message-ID: <028201cec667$deb5a360$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, <dcrocker@bbiw.net>
References: <5251FA64.7020205@dcrocker.net> <52572EA9.4030807@qti.qualcomm.com>
Subject: Re: Review of:   draft-resnick-on-consensus-05
Date: Fri, 11 Oct 2013 10:53:03 +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.53]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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: Fri, 11 Oct 2013 09:56:38 -0000

A minor point inline, rest snipped

Tom Petch

----- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: <dcrocker@bbiw.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, October 10, 2013 11:48 PM


> Finally back to this original review.
>
> On 10/6/13 7:03 PM, Dave Crocker wrote:
<snip>

>
> >>    Note that this portrays rough consensus as an "exception".
> >
> > I don't understand this first sentence.  How is it an exception?
Even
> > with the following text, I don't see the basis for claiming that it
> > might/would be seen as exceptional.
>
> Maybe I need a different word. I didn't mean "exceptional" in the
sense
> of "extraordinary" or "atypical". I simply meant it in the "exception
> handling" sense: We work toward full agreement, but if there's still
> disagreement, we undertake an alternative path. I'm open to
suggestions
> for text.
>
> >>    Now, a conclusion of having only rough consensus relies heavily
on
> >>    the good judgement of the consensus caller.  The group must
truly
> >>    consider and weigh an issue before the objection can be
dismissed as
> >>    being "in the rough".  The chair of the working group in one of
these
> >
> > In spite of being appealing to use here, I think that the phrase "in
> > the rough" is actually distracting
>
> As I mentioned earlier, I think it is worth defining as the golf term,
> since it is used quite frequently among IETFers nowadays.

I just saw this term used by an AD in a DISCUSS for the first time that
I can recall, and I have not a clue what he means (yes, I understand
golf but do not see the relevance).  My guess is that the AD is flying a
kite, but would not expect that to be any more widely understood:-(

Tom Petch


<snip>
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>



From cdel@firsthand.net  Fri Oct 11 03:25:37 2013
Return-Path: <cdel@firsthand.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 4828021E8093 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 03:25: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S272NQmaKkSW for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 03:25:36 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id 0046421E81B8 for <ietf@ietf.org>; Fri, 11 Oct 2013 03:25:34 -0700 (PDT)
Received: (qmail 17946 invoked from network); 11 Oct 2013 10:25:22 +0100
Received: from host-2-99-231-133.as13285.net (HELO orionlocal.local) (2.99.231.133) by mail.firsthand.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Oct 2013 10:25:21 +0100
Message-ID: <5257D21A.7090602@firsthand.net>
Date: Fri, 11 Oct 2013 11:25:30 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: leader statements
References: <20131010185255.3BE2A18C118@mercury.lcs.mit.edu> <52574D45.7060002@gmail.com> <m2wqlky0w4.wl%randy@psg.com>
In-Reply-To: <m2wqlky0w4.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Arturo Servin <arturo.servin@gmail.com>, 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: Fri, 11 Oct 2013 10:25:37 -0000

Randy Bush wrote:
>> What I am saying is that if we that we want our leaders to only
>> moderate discussion we are in a big problem.
> 
> we are in a big problem, and this is one major part.  two decades of
> lack of coherent architectural oversight is another symptom of this.
> i'm surprised that we are not overwhelmed with focus groups.
> 
> randy


Maybe it is time for a Draft from our signatories so community can
consider the statement from an "architectural" perspective?

It would be useful to understand  "architectural" roots to the statement
bearing in Dave's analysis that the call to globalise IANA /ICANN is
essentially political. It is likely to have political ramifications but
was it driven politically or from some deeper engineering drivers?



Christian

From abdussalambaryun@gmail.com  Fri Oct 11 03: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 02D2221E8113 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 03:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 A7ZW5apBwbpo for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 03:40:24 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 50CEE21E813C for <ietf@ietf.org>; Fri, 11 Oct 2013 03:40:23 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kp14so4139662pab.20 for <ietf@ietf.org>; Fri, 11 Oct 2013 03:40:23 -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=4fMz/efcX35n3z8BzyeKSeQSTEViLC9mx8TP7amp13k=; b=EJBM8uwcEwq4caS+bJhgSPSBCY+zUWnlOsN7qDopyHafiPX9JQJR3rbkUyTaq7LVNi kVLaBigUjddPrDcXfiuIOpfckTDQ4ivbdZ2TdFMClpN0UfnIdpXRht/y/y19ebq54gk0 C7gWg5SdUIPq22f8a+wauQhrzHG9NesdQAe3l/bK4fUqm3oNAU2HQGWJoQdHKeP/Hs9W kqct0x4Yv3l5wZH/TfTj5OH7opGG630ouX3wReWVKxcoZPG3Z9OsDwV/jwzRmcUTg6rV g2YyptD4EOLazpmfTifj3/iOvBVOhofC8s5ErcS8FlcttUdxtsExZT/Ae0zT8p0ZI/MC qKmA==
MIME-Version: 1.0
X-Received: by 10.66.196.168 with SMTP id in8mr20499916pac.18.1381488023106; Fri, 11 Oct 2013 03:40:23 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 11 Oct 2013 03:40:23 -0700 (PDT)
Date: Fri, 11 Oct 2013 11:40:23 +0100
Message-ID: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7bdca8a4e0fdf104e874be93
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "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, 11 Oct 2013 10:40:26 -0000

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

Reviewer: Abdussalam Baryun
Date: 11.10.2013
Last Call For the General Area
I-D reviewed: draft-resnick-on-consensus-05
++++++++++++++++++++++++++++++++++
Hi Pete and Jari,
The documents provide important examples which are real within IETF, and
needs to be studied/analysed more as case studies. Such real examples
should be documented by historical documents which will help future work
like this to refer to as real incidents. However, I support the idea of the
draft subject to the below five requirements (the sixth is recommendation):
1) The draft should include remote participants input to the consensus
process or path. The mailing list should be the main place for consensus
measuring its roughness in the Internet community (not in only rooms or in
hidden design teams).
2) The document does not mention the editor's task and how to work with
discussions or chairs. If the editors are 5 most active participants in the
WG then they are ruling the WG, and they can even discourage inputs by just
disagreeing. I in MANET WG experienced many examples mentioned in your
document, which I think will help future new participants to make better
impacts on ietf WGs. I request explaining editors input and Chair's in such
examples/situations. Editors and Chair are the ones facilitating on the
path (i.e. consensus, as mentioned in draft).
3) The document does not mention the destinations of *consensus paths*
within IETF. What you mean by destination? For me the destination is to
submit the best document to IESG, or to Adopt an interesting document as WG
document. Many individuals may not get to thoes destinations because of
IETF WG Chair's methods. I recommend as you solve the *path* as it is
consensus, but also correcting the path to get to correct destination only
if we identify the destination. I request to define the destination and to
define what is engineering reasons in agreeing and disagreeing (in IETF
some times discussions are only politics not engineering, which makes
problems in document qualities).
4) In the abstract you use *WE*, I object to use that word only if defined;
do you mean all community or you mean majority, or minority, or management,
or f2f participants or remote participants, or WG chairs, or ADs, etc. In
my thoughts the meeting humming majority are the North America participants
(i.e. check ietf statistics), but if you include remote participants of
IETF in the draft then becomes diversified majority. Humming is used only
in meetings not on lists, you may think of another way to do it on the
list. Suggest/request to add in the abstract that this document should be
as information to the training of WG Chairs. Also the abstract should
include what is mentioned in the conclusion of *the way of thinking to get
to participation decisions*.
Please amend the abstract:
draft-05>Abstract:
The IETF has had a long tradition of doing its technical work through
a consensus process, taking into account the different views among
IETF participants and coming to (at least rough) consensus on
technical matters. In particular, the IETF is supposed not to be run
by a "majority rule" philosophy. This is why we engage in rituals
like "humming" instead of voting. However, more and more of our
actions are now indistinguishable from voting, and quite often we are
letting the majority win the day, without consideration of minority
concerns. This document is a collection of thoughts on what rough
consensus is, how we have gotten away from it, and the things we can
do in order to really achieve rough consensus.

Note (to be removed before publication): This document is quite
consciously being put forward as Informational. It does not
propose to change any IETF processes and is therefore not a BCP.
It is simply a collection of principles, hopefully around which
the IETF can come to (at least rough) consensus.
AB>amend>
The IETF has had a long tradition of doing its technical work through
a WG consensus process [reference], taking into account the different views
among
IETF participants and coming to better (at least rough) consensus on
technical and procedural matters. In particular, the IETF is supposed not
to be run
by a "majority rule" philosophy but an engineering community rule
philosophy. This is why particpants engage in rituals
like "humming" instead of voting within meetings. The results of consensus
should have good engineering reasons. However, more and more of the IETF
discussions/actions are now indistinguishable from voting, and quite often
Chairs are
letting the majority win the day, without much consideration of minority
concerns. This document is a collection of thoughts on what a fair rough
consensus is like, how IETF participants have gotten away from it, and the
things they should do in order to really friendly guide for rough consensus
achievement. The point of this document is to get all community to
think about how IETF community is coming to better decisions in the IETF,
to make sure participants avoid the dangers of "majority rule" and actually
get to friendly rough consensus decisions with the best technical outcomes.

Note (to be removed before publication): This document is quite
consciously being put forward as Informational that can be used for WG
chairs training. It does not
propose to change any IETF processes and is therefore not a BCP.
It is simply a collection of principle understandings, hopefully around
which
the IETF can come to better (at least rough) consensus.
5) I request to see the word *polite*, *friendly*, *encourage*, and other
positive ways of thinking that helps (i.e. don't mean formal or informal
writting on the list) , because I see some negative thinking in some
participations of IETF WGs, so I request the draft to mention friendly
efforts. For example, many of my experience while getting negative
posts made me positive because our ADs are very positive and friendly when
solving issues, and they do advise nicely, so we need more
friendly/positive thinkings in the IETF among f2f participants, remote
participants, and old-comer participants.

6) Not understood the information on the draft's ideas on process of
consensus path or paths or the number of its practices, and how the Chair
should use different paths or methods to get to better consensus (i.e. each
time measures consensus the chair tries to gain a better one not worse
one). People think of what will happen if some disagree with our draft, so
they think how to use such path, so your draft makes me think of what are
my friendly or informal options. I recommend to make more work if possible
of solutions/guidances for the consensus facilitators (editors, chairs,
ADs).
++++++++++++++++++
Best Regards
AB


On Sun, Oct 6, 2013 at 10:03 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> The document talks about ways in which consensus processes can be
> successfully run in the IETF. After the last few rounds of versions, I
> believe this document is ready to move forward.
>
> My goal is to publish it as an Informational RFC. It is an explanation of
> principles and how they can be applied to productively move IETF
> discussions forward. While there is no change to IETF processes or any
> presumption that guidance from this document must be followed, I have found
> the document very useful. It has been referred to numerous times in IETF
> and IESG discussions. Consensus is hard and many WG discussions have
> complex trade-offs and differing opinions. I believe having this document
> become an RFC would help us apply the useful principles even more widely
> than we are doing today.
>
> The abstract says:
>
>    The IETF has had a long tradition of doing its technical work through
>    a consensus process, taking into account the different views among
>    IETF participants and coming to (at least rough) consensus on
>    technical matters.  In particular, the IETF is supposed not to be run
>    by a "majority rule" philosophy.  This is why we engage in rituals
>    like "humming" instead of voting.  However, more and more of our
>    actions are now indistinguishable from voting, and quite often we are
>    letting the majority win the day, without consideration of minority
>    concerns.  This document is a collection of thoughts on what rough
>    consensus is, how we have gotten away from it, and the things we can
>    do in order to really achieve rough consensus.
>
>       Note (to be removed before publication): This document is quite
>       consciously being put forward as Informational.  It does not
>       propose to change any IETF processes and is therefore not a BCP.
>       It is simply a collection of principles, hopefully around which
>       the IETF can come to (at least rough) consensus.
>
> The draft can be obtained from
> http://tools.ietf.org/html/draft-resnick-on-consensus
>
> You should see a last call announcement soon, and both me and Pete look
> forward to your feedback.
>
> Jari
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">Reviewer: Abdussalam Baryun</di=
v><div class=3D"gmail_extra">Date: 11.10.2013</div><div class=3D"gmail_extr=
a">Last Call For the General Area </div><div class=3D"gmail_extra">I-D revi=
ewed: draft-resnick-on-consensus-05</div>
<div class=3D"gmail_extra">++++++++++++++++++++++++++++++++++</div><div cla=
ss=3D"gmail_extra"> </div><div class=3D"gmail_extra">Hi Pete and Jari,</div=
><div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">The documents=
 provide important examples which are real within IETF, and needs to be stu=
died/analysed more as case studies. Such real examples should be documented=
 by historical documents which will help future work like this to refer to =
as real incidents. However, I support the idea of the draft subject to the =
below five requirements (the sixth is recommendation):</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">1) The draft s=
hould include remote participants input to the consensus process or path. T=
he mailing list should be the main place for consensus measuring its roughn=
ess in the Internet community (not in only rooms or in hidden=A0design team=
s).</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">2) The documen=
t does not mention the editor&#39;s task and how to work with discussions o=
r chairs. If the editors are 5 most active participants in the WG then they=
 are ruling the WG, and they can even discourage inputs by just disagreeing=
. I in MANET WG experienced many examples mentioned in your document, which=
 I think will help future new participants to make better impacts on ietf W=
Gs. I request explaining editors input and Chair&#39;s in such examples/sit=
uations. Editors and Chair are the ones facilitating on the path (i.e. cons=
ensus, as mentioned in draft).</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">3) The documen=
t does not mention the destinations of *consensus paths* within IETF. What =
you mean by destination? For me the destination is to submit the best docum=
ent to IESG, or to Adopt an interesting document as WG document. Many indiv=
iduals may not get to thoes destinations because of IETF WG Chair&#39;s met=
hods. I recommend as you solve the *path* as it is consensus, but also corr=
ecting the path to get to correct destination only if we identify the desti=
nation. I request to define the destination and to define what is engineeri=
ng reasons in agreeing and disagreeing (in IETF some times discussions are =
only politics not engineering, which makes problems in document qualities).=
</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">4) In the abst=
ract you use *WE*, I object to use that word only if defined; do you mean a=
ll community or you mean majority, or minority, or management, or f2f parti=
cipants or remote participants, or WG chairs, or ADs, etc. In my thoughts t=
he meeting humming majority are the North America participants (i.e. check =
ietf statistics), but if you=A0include remote participants of IETF in the d=
raft then=A0becomes diversified majority. Humming is used only in meetings =
not on lists, you may think of another way to do it on the list. Suggest/re=
quest to add in the abstract=A0that this document should be as information =
to the training of WG Chairs. Also the abstract should include what is ment=
ioned in the conclusion of *the way of thinking to get to participation dec=
isions*.</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">Please amend t=
he abstract:</div><div class=3D"gmail_extra"> </div><div class=3D"gmail_ext=
ra">draft-05&gt;Abstract:</div><div class=3D"gmail_extra">The IETF has had =
a long tradition of doing its technical work through<br>
   a consensus process, taking into account the different views among<br>  =
 IETF participants and coming to (at least rough) consensus on<br>   techni=
cal matters.  In particular, the IETF is supposed not to be run<br>   by a =
&quot;majority rule&quot; philosophy.  This is why we engage in rituals<br>
   like &quot;humming&quot; instead of voting.  However, more and more of o=
ur<br>   actions are now indistinguishable from voting, and quite often we =
are<br>   letting the majority win the day, without consideration of minori=
ty<br>
   concerns.  This document is a collection of thoughts on what rough<br>  =
 consensus is, how we have gotten away from it, and the things we can<br>  =
 do in order to really achieve rough consensus.<br><br>      Note (to be re=
moved before publication): This document is quite<br>
      consciously being put forward as Informational.  It does not<br>     =
 propose to change any IETF processes and is therefore not a BCP.<br>      =
It is simply a collection of principles, hopefully around which<br>      th=
e IETF can come to (at least rough) consensus.<br>
</div><div class=3D"gmail_extra">AB&gt;amend&gt;</div><div class=3D"gmail_e=
xtra"> </div><div class=3D"gmail_extra">The IETF has had a long tradition o=
f doing its technical work through<br>   a WG consensus process [reference]=
, taking into account the different views among<br>
   IETF participants and coming to better (at least rough) consensus on<br>=
   technical and procedural matters.  In particular, the IETF is supposed n=
ot to be run<br>   by a &quot;majority rule&quot; philosophy but an enginee=
ring community rule philosophy.  This is why particpants engage in rituals<=
br>
   like &quot;humming&quot; instead of voting within meetings.  The results=
 of consensus should have good engineering reasons. However, more and more =
of the IETF discussions/actions are now indistinguishable from voting, and =
quite often Chairs are<br>
   letting the majority win the day, without much consideration of minority=
<br>   concerns.  This document is a collection of thoughts on what a fair =
rough<br>   consensus is like, how IETF participants have gotten away from =
it, and the things they should=A0do in order to really friendly guide for r=
ough consensus achievement. The point of this document is to get all commun=
ity to</div>
<div class=3D"gmail_extra">think about how=A0IETF community=A0is coming to =
better decisions in the IETF, to make sure=A0participants avoid the dangers=
 of &quot;majority rule&quot;=A0and actually get to friendly rough=A0consen=
sus decisions with the best technical outcomes.</div>
<div class=3D"gmail_extra">=A0</div><div class=3D"gmail_extra">Note (to be =
removed before publication): This document is quite<br>      consciously be=
ing put forward as Informational that can be used for WG chairs training.  =
It does not<br>
      propose to change any IETF processes and is therefore not a BCP.<br> =
     It is simply a collection of principle understandings, hopefully aroun=
d which<br>      the IETF can come to better (at least rough) consensus.</d=
iv>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">5) I request t=
o see the word *polite*, *friendly*, *encourage*, and other positive ways o=
f thinking that helps=A0(i.e. don&#39;t mean formal or informal writting on=
 the list)=A0, because I see some negative thinking in=A0some participation=
s of IETF WGs, so I request the draft to mention friendly efforts. For exam=
ple, many of my experience while=A0getting negative posts=A0made me positiv=
e because our ADs are very positive and friendly when solving issues, and t=
hey do advise nicely, so we need more friendly/positive thinkings in the IE=
TF among f2f participants, remote participants, and old-comer participants.=
</div>
<div class=3D"gmail_extra">=A0</div><div class=3D"gmail_extra">6) Not under=
stood the information on the draft&#39;s ideas on process of consensus path=
 or paths or the number of its practices, and how the Chair should use diff=
erent paths or methods to get to better consensus (i.e. each time measures =
consensus the chair tries to gain a better one not worse one). People think=
 of what will happen if some disagree with our draft, so they think how to =
use such path, so your draft makes me think of what are my friendly or info=
rmal=A0options.=A0I recommend to make more work if possible of solutions/gu=
idances for the consensus facilitators (editors, chairs, ADs).</div>
<div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">++++++++++++++=
++++</div><div class=3D"gmail_extra"> </div><div class=3D"gmail_extra">Best=
 Regards</div><div class=3D"gmail_extra">AB<br></div><div class=3D"gmail_ex=
tra"><br>
<br><div class=3D"gmail_quote">On Sun, Oct 6, 2013 at 10:03 PM, Jari Arkko =
<span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_bl=
ank">jari.arkko@piuha.net</a>&gt;</span> wrote:<br><blockquote style=3D"mar=
gin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);b=
order-left-width:1px;border-left-style:solid" class=3D"gmail_quote">
The document talks about ways in which consensus processes can be successfu=
lly run in the IETF. After the last few rounds of versions, I believe this =
document is ready to move forward.<br>
<br>
My goal is to publish it as an Informational RFC. It is an explanation of p=
rinciples and how they can be applied to productively move IETF discussions=
 forward. While there is no change to IETF processes or any presumption tha=
t guidance from this document must be followed, I have found the document v=
ery useful. It has been referred to numerous times in IETF and IESG discuss=
ions. Consensus is hard and many WG discussions have complex trade-offs and=
 differing opinions. I believe having this document become an RFC would hel=
p us apply the useful principles even more widely than we are doing today.<=
br>

<br>
The abstract says:<br>
<br>
=A0 =A0The IETF has had a long tradition of doing its technical work throug=
h<br>
=A0 =A0a consensus process, taking into account the different views among<b=
r>
=A0 =A0IETF participants and coming to (at least rough) consensus on<br>
=A0 =A0technical matters. =A0In particular, the IETF is supposed not to be =
run<br>
=A0 =A0by a &quot;majority rule&quot; philosophy. =A0This is why we engage =
in rituals<br>
=A0 =A0like &quot;humming&quot; instead of voting. =A0However, more and mor=
e of our<br>
=A0 =A0actions are now indistinguishable from voting, and quite often we ar=
e<br>
=A0 =A0letting the majority win the day, without consideration of minority<=
br>
=A0 =A0concerns. =A0This document is a collection of thoughts on what rough=
<br>
=A0 =A0consensus is, how we have gotten away from it, and the things we can=
<br>
=A0 =A0do in order to really achieve rough consensus.<br>
<br>
=A0 =A0 =A0 Note (to be removed before publication): This document is quite=
<br>
=A0 =A0 =A0 consciously being put forward as Informational. =A0It does not<=
br>
=A0 =A0 =A0 propose to change any IETF processes and is therefore not a BCP=
.<br>
=A0 =A0 =A0 It is simply a collection of principles, hopefully around which=
<br>
=A0 =A0 =A0 the IETF can come to (at least rough) consensus.<br>
<br>
The draft can be obtained from <a href=3D"http://tools.ietf.org/html/draft-=
resnick-on-consensus" target=3D"_blank">http://tools.ietf.org/html/draft-re=
snick-on-consensus</a><br>
<br>
You should see a last call announcement soon, and both me and Pete look for=
ward to your feedback.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div></div>

--047d7bdca8a4e0fdf104e874be93--

From jmamodio@gmail.com  Fri Oct 11 04:06:10 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 DE82821E81B2 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 04:06:10 -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 95vUSUQIvR-w for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 04:06:10 -0700 (PDT)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 03EAB21E81C1 for <ietf@ietf.org>; Fri, 11 Oct 2013 04:06:06 -0700 (PDT)
Received: by mail-vc0-f177.google.com with SMTP id hv10so2602203vcb.8 for <ietf@ietf.org>; Fri, 11 Oct 2013 04:06: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=VOA5+vAj50H0ntm256fCDbRViJsewFTborvCeZ9fh/E=; b=NaMVMr/4TjJV3Nmml2OS5cySaVRUNReSXIUGKXmkKeOmNusDCxkY0sIoN6XyyF3wgF PTcTpuVmkvBUbdIQGttTTwc6QQokfFwV6Ob6R15lGr8+uqwSe4ErZnmVOh6KaE3fYdl8 bw6Tj+y53ZrWj7FsZc/2dcrCIcFEWf3Hh8XpXzjs9QkkKEgmSXxn3lDL6akeNc+K41Sa byTBgI8uKvyyk4QU6o0q7PUP1Jjyy97GoH5sCKQDvJ00exrxxkMvAYDHLAGOz0zeOaLn tTxTxU6hrzLAPc4i16uCJp0D88OSQjg5ZKLIPYBhiq2wa9eaSesx6ncMGo24QJbHN4zC bSrQ==
MIME-Version: 1.0
X-Received: by 10.220.164.202 with SMTP id f10mr20954081vcy.25.1381489566314;  Fri, 11 Oct 2013 04:06:06 -0700 (PDT)
Received: by 10.52.229.74 with HTTP; Fri, 11 Oct 2013 04:06:06 -0700 (PDT)
In-Reply-To: <E7220D9C-E465-4532-B9AE-3F9233989A5B@tzi.org>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <E7220D9C-E465-4532-B9AE-3F9233989A5B@tzi.org>
Date: Fri, 11 Oct 2013 06:06:06 -0500
Message-ID: <CAMzo+1bjzpWOVNUqzZMfgBDoZ76Zdr_CyXfhovh_pnKEE-aB-Q@mail.gmail.com>
Subject: Re: "The core Internet institutions abandon the US Government"
From: Jorge Amodio <jmamodio@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a11c1e980dc75a804e8751a57
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, 11 Oct 2013 11:06:11 -0000

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

Just few quick questions,

In what part of Fadi Chehad=E9 mandate at ICANN this falls ? And who
sanctified him as representative of the Internet Community ?

He is just an employee of ICANN and these actions go way beyond ICANN's
mission and responsibilities.

Cheers
Jorge



On Fri, Oct 11, 2013 at 4:42 AM, Carsten Bormann <cabo@tzi.org> wrote:

> >
> http://www.internetsociety.org/news/montevideo-statement-future-internet-=
cooperation
>
>
>
> http://www.internetgovernance.org/2013/10/11/the-core-internet-institutio=
ns-abandon-the-us-government/
> ?
> "The core Internet institutions abandon the US Government | IGP Blog"
>
> I'm not quite sure I read the Montevideo statement the way this headline
> suggests.
> (The US government must feel so abandoned these days...)
> But that is the danger of saying anything at all.
>
> Gr=FC=DFe, Carsten
>
>

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

<div dir=3D"ltr"><div>Just few quick questions,=A0</div><div><br></div><div=
>In what part of=A0<span style=3D"font-family:arial,sans-serif;font-size:13=
px">Fadi Chehad=E9 mandate at ICANN this falls ? And who sanctified him as =
representative of the Internet Community ?</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><font face=3D"arial, sans-serif">He is just an employee of ICAN=
N and these actions go way beyond ICANN&#39;s mission and=A0responsibilitie=
s.</font></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">Che=
ers</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:=
13px">Jorge</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">=
On Fri, Oct 11, 2013 at 4:42 AM, Carsten Bormann <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; <a href=3D"http://www.internetsociety.o=
rg/news/montevideo-statement-future-internet-cooperation" target=3D"_blank"=
>http://www.internetsociety.org/news/montevideo-statement-future-internet-c=
ooperation</a><br>

<br>
<br>
<a href=3D"http://www.internetgovernance.org/2013/10/11/the-core-internet-i=
nstitutions-abandon-the-us-government/" target=3D"_blank">http://www.intern=
etgovernance.org/2013/10/11/the-core-internet-institutions-abandon-the-us-g=
overnment/</a>?<br>

&quot;The core Internet institutions abandon the US Government | IGP Blog&q=
uot;<br>
<br>
I&#39;m not quite sure I read the Montevideo statement the way this headlin=
e suggests.<br>
(The US government must feel so abandoned these days...)<br>
But that is the danger of saying anything at all.<br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br></div>

--001a11c1e980dc75a804e8751a57--

From l.wood@surrey.ac.uk  Fri Oct 11 04:15:31 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 0247C21E80E7 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 04:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.023
X-Spam-Level: 
X-Spam-Status: No, score=-4.023 tagged_above=-999 required=5 tests=[AWL=-0.425, 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 qcBDd28W-mJ6 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 04:15:24 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id DD83321F9C81 for <ietf@ietf.org>; Fri, 11 Oct 2013 04:15:14 -0700 (PDT)
Received: from [85.158.137.99:19025] by server-12.bemta-3.messagelabs.com id 56/C0-11891-1CDD7525; Fri, 11 Oct 2013 11:15:13 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-217.messagelabs.com!1381490112!17686056!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1921 invoked from network); 11 Oct 2013 11:15:13 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-10.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 11 Oct 2013 11:15:13 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.148]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 11 Oct 2013 12:15:12 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>
Date: Fri, 11 Oct 2013 12:11:22 +0100
Subject: RE: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Topic: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Index: Ac7GXctjqsicJzXjRLCLq8wu+YUVFQAFNLiE
Message-ID: <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>, <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com>
In-Reply-To: <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@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: Fri, 11 Oct 2013 11:15:31 -0000

> I am part of the community design team as well

... as being the coauthor of a MANET RFC!


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




From sob@sobco.com  Fri Oct 11 05:16:07 2013
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0217821E81A5 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.203
X-Spam-Level: 
X-Spam-Status: No, score=0.203 tagged_above=-999 required=5 tests=[AWL=0.698,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  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 OCeEVhBSmlXk for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:16:01 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 1B16821E80FB for <ietf@ietf.org>; Fri, 11 Oct 2013 05:16:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 6460832FADA for <ietf@ietf.org>; Fri, 11 Oct 2013 08:15:59 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5TDOqAR4-pP for <ietf@ietf.org>; Fri, 11 Oct 2013 08:15:59 -0400 (EDT)
Received: from newdev.cadm.harvard.edu (newdev.cadm.harvard.edu [128.103.229.199]) by sobco.sobco.com (Postfix) with ESMTPSA id 05A9032FACC for <ietf@ietf.org>; Fri, 11 Oct 2013 08:15:58 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.gmail.com>
Date: Fri, 11 Oct 2013 08:15:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B17EA9B-42B3-4C09-9D34-C4ABFB8A4B77@sobco.com>
References: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.gmail.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Oct 2013 12:16:07 -0000

As Dave Crocker pointed out, this document is, at best, revisionist =
history.  Dave's original RFC 1603 text (that I carried forward into RFC =
2418) bears little resemblance to the process/considerations described =
in this ID.
=20
This ID may be describing how we should start to view the meaning of the =
term "rough consensus" , but I do wish that the ID took care to propose =
it as new concept rather than pretend that it has always been what the =
IETF has done.  The process in the ID is not what was followed when I =
was an AD and it not what I have described by the meaning of the term =
"rough consensus" in my newcomers tutorials (which I have been giving =
since at least IETF 57 in 2003).=20
=20
Thus I do not consider this ID ready for publication and call for it to =
be revised to clearly state that it is proposing a redefinition of the =
concept and term "rough consensus" then re-last called.
=20
Scott
=20=

From jnc@mercury.lcs.mit.edu  Fri Oct 11 05:24:42 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 841F921E81B5 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:24:42 -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.000,  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 Qry7nqMyZc35 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:24:37 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id ACC6721E8180 for <ietf@ietf.org>; Fri, 11 Oct 2013 05:24:36 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8FDB118C13C; Fri, 11 Oct 2013 08:24:24 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: leader statements
Message-Id: <20131011122424.8FDB118C13C@mercury.lcs.mit.edu>
Date: Fri, 11 Oct 2013 08:24:24 -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, 11 Oct 2013 12:24:42 -0000

    > From: Randy Bush <randy@psg.com>

    > we are in a big problem, and this is one major part. two decades of
    > lack of coherent architectural oversight is another symptom of this.

I have two issues with your observation.

First, while I agree we've been deficient in architecture, from personal
experience I can tell you that the I* community is remarkably resistant to
architectural guidance (which necessarily involves a rather long time-frame,
the kind of time-frame to which many engineers are inherently resistant,
focused as they are on the practical, here-and-now).

I don't know much about the other levels of the stack, but I can assure you
that at the internetworking level, the community has been remarkably
resistant to architectural guidance over the last 20 years - and I have the
arrows in my back to prove it (the lack of separation of location and
identity in IPv6 being only one of the largest).

Would attempting to push the I* down a particular path, different to the one
that the one it wants to take, have any different result than Kobe? I am not
sure.

Second, it's not at all clear to me that the people who are best suited to
provide architectural guidance are the same people who are best suited to be
facilitating leaders. They are very different skills, and to find both in one
person, at the kind of high level needed in the I* now that it is responsible
for a major part of the world's communication infrastructure, would seem to
me to be rather unlikely.

	Noel

From jari.arkko@piuha.net  Fri Oct 11 05:43:14 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 6EADD21F93BF for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:43:14 -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 rDflYOP-cZuC for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 05:43:09 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1687E11E8118 for <ietf@ietf.org>; Fri, 11 Oct 2013 05:43:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EF26A2CC64; Fri, 11 Oct 2013 15:43:07 +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 XhANUYiaxoDu; Fri, 11 Oct 2013 15:43:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 817542CC5D; Fri, 11 Oct 2013 15:43:07 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk>
Date: Fri, 11 Oct 2013 15:43:07 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>, <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1510)
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: Fri, 11 Oct 2013 12:43:14 -0000

First, lets keep the discussion on topic and not at personal level. =
Thank you. (This isn't addressed to you SM or Lars; it is a general =
comment based on some of the mails that I see.)

Secondly, this is an interesting and important topic, thank you SM for =
writing a draft. I do agree with at least the recommendation that for =
returning fellows their participation and contribution in the IETF is a =
key objective. I have some question marks about some of the other ones; =
not sure ADs in general have time to evaluate (even more) drafts, for =
instance. But then again I think the quality of the work is likely =
fairly apparent to anyone looking more closely, so not sure ADs are =
needed.

I do have a question for Lars though. What are your opinions on this? =
(You said that there is no consensus, but I'd like to hear also your =
thoughts.)

Jari


From lars@netapp.com  Fri Oct 11 06:23:05 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 15C6821F9C0D for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 06:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.156
X-Spam-Level: 
X-Spam-Status: No, score=-5.156 tagged_above=-999 required=5 tests=[AWL=-2.557, 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 c6qeYQBOY7by for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 06:23:00 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1162921F9B91 for <ietf@ietf.org>; Fri, 11 Oct 2013 06:22:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1080,1371106800";  d="asc'?scan'208";a="58756826"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 11 Oct 2013 06:22:58 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Fri, 11 Oct 2013 06:22:59 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Topic: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Thread-Index: AQHOxn92Rnj3YxgZmUCucHSH1VVlzZnv8lmA
Date: Fri, 11 Oct 2013 13:22:57 +0000
Message-ID: <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>, <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk> <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net>
In-Reply-To: <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net>
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=_B4296C19-00B3-483A-ACD8-67038BFC02B4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, "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, 11 Oct 2013 13:23:05 -0000

--Apple-Mail=_B4296C19-00B3-483A-ACD8-67038BFC02B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Oct 11, 2013, at 14:43, Jari Arkko <jari.arkko@piuha.net> wrote:
> I do have a question for Lars though. What are your opinions on this? =
(You said that there is no consensus, but I'd like to hear also your =
thoughts.)

so one key question is what influence the IETF actually has on an ISOC =
program. We can certainly state our wishes, but my belief is that it's =
ISOC's program in the end, and they can basically chose to run it as =
they see fit. That doesn't come out in the draft at all.

Another issue I have with the the draft is written with the implied =
understanding that the program should fund the repeated attendance of =
residents of under-represented regions who are actively participating in =
some sort of way. It's not clear to me that this is really what would be =
best in terms of increasing organizational diversity over time. I =
wouldn't want to fund the same people over and over; I'd much rather =
bring in new people all the time in the hopes of spreading the word =
about the IETF widely and hoping that some folks will end up in roles =
where they can occasionally attend on their own dime. I'd like to be =
able to bring in other under-represented groups (students, academics, =
women, etc.) We can certainly have a discussion about what is best; my =
point is that the draft has already decided that one approach is the way =
to go.

I also have a few issues with the suggestions it makes:

Section 4.1 requires that an applicant needs to already have been a =
participant in the IETF. That seems excessive. For returning fellows, =
some sort of engagement in the IETF after a while would be nice, but I =
can see valid cases for supporting someone's repeated attendance who =
isn't contributing in a very visible role. Also, I question the =
possibility to quantify and compare someone's impact of IETF =
involvement. And again, there are others than "resident of a country in =
an under-represented region" who we might want to bring in, and we =
probably don't need to fund the attendance of employees of large vendors =
who happen to be residents of under-represented regions.

The evaluation panel in Section 4.2 is therefore also problematic. And I =
wouldn't want to blindly "prioritize people who have been contributing =
over time to real IETF work" - we need to keep the flexibility of =
bringing in someone new who has high potential even if it means that =
someone who has been funded to attend in the past isn't going to be =
covered.

But my main issue is that the draft sounds like its trying to take over =
and redefine an ISOC program, which I don't think the IETF can or should =
do. The ISOC program has a purpose, a history and at least from my =
perspective is working pretty well with the budget it has available. I'm =
not sure we can actually improve it much.

Lars

--Apple-Mail=_B4296C19-00B3-483A-ACD8-67038BFC02B4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUlf7sdZcnpRveo1xAQJPOgP9F6P1xpQBeiY656wLV5IARmocV4xs5Mgy
1i3L8tOgYDV2N/SDoemWA5xvjnCe0qy+7vRn1XxjWHwK7Hmxe0F+YlmLDcJ2XtRp
HCJXffhlIEct7HLqAAwZ+Hz4LkfLpUJaWuhdiHsdSwRnbFhPJbui9rZwtkPeRZLK
d4DvXdsL9vE=
=Ar0g
-----END PGP SIGNATURE-----

--Apple-Mail=_B4296C19-00B3-483A-ACD8-67038BFC02B4--

From jari.arkko@piuha.net  Fri Oct 11 06:38:24 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 4BBE321E80FA for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 06:38:24 -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 Z-jNRZNSCqXO for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 06:38:19 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1514C21E80FF for <ietf@ietf.org>; Fri, 11 Oct 2013 06:38:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 553FD2CC6C; Fri, 11 Oct 2013 16:38:17 +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 B1rCC0EH2XB7; Fri, 11 Oct 2013 16:38:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E18652CC5D; Fri, 11 Oct 2013 16:38:16 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
Date: Fri, 11 Oct 2013 16:38:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <48424340-BED2-47C2-80B8-3697E7286518@piuha.net>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>, <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk> <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net> <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1510)
Cc: SM <sm@resistor.net>, "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, 11 Oct 2013 13:38:24 -0000

> we need to keep the flexibility of bringing in someone new=20

agree

> But my main issue is that the draft sounds like its trying to take =
over and redefine an ISOC program, which I don't think the IETF can or =
should do. The ISOC program has a purpose, a history and at least from =
my perspective is working pretty well with the budget it has available. =
I'm not sure we can actually improve it much.

agree, of course. at best we can provide input. but it really is an ISOC =
program.

Jari


From lberger@labn.net  Fri Oct 11 07:14:09 2013
Return-Path: <lberger@labn.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 F2A3A11E81DB for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 07:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.914
X-Spam-Level: 
X-Spam-Status: No, score=-100.914 tagged_above=-999 required=5 tests=[AWL=-1.209, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_35=0.6, RCVD_IN_BL_SPAMCOP_NET=1.96, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8L-hrwcqBqx for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 07:14:04 -0700 (PDT)
Received: from outbound-ss-874.bluehost.com (outbound-ss-874.bluehost.com [69.89.29.198]) by ietfa.amsl.com (Postfix) with SMTP id AB39E11E80E3 for <ietf@ietf.org>; Fri, 11 Oct 2013 07:14:03 -0700 (PDT)
Received: (qmail 30002 invoked by uid 0); 11 Oct 2013 14:14:00 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy4.mail.unifiedlayer.com with SMTP; 11 Oct 2013 14:14:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=h4GpWjNYorkGEjqxGumuKYTb8cWBShYvoySywrgZKCQ=;  b=jjB1Tdb6NaGgbpHv4KW0F1MdKI58Sts0lY+0W6FtlByk9QYB3D0+e/zigDv2wF09/TNh6jgy+P7BiFZfSz5yEuvPJV++vOL9fG9/ojNLoy/BACSE5HuWv82QOFG/gyes;
Received: from box313.bluehost.com ([69.89.31.113]:38094 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1VUdTc-0006PD-3i; Fri, 11 Oct 2013 08:14:00 -0600
Message-ID: <525807A7.7070809@labn.net>
Date: Fri, 11 Oct 2013 10:13:59 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last calling draft-resnick-on-consensus
References: <508943C8-BE40-4128-9B70-6CB568FC82D3@piuha.net> <5252AD9D.6010408@labn.net> <52576BB1.6040708@qti.qualcomm.com>
In-Reply-To: <52576BB1.6040708@qti.qualcomm.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
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: Fri, 11 Oct 2013 14:14:09 -0000

Pete,

On 10/10/2013 11:08 PM, Pete Resnick wrote:
> On 10/7/13 7:48 AM, Lou Berger wrote:
>> I think it misses two
>> important points that should be addressed prior to publication:
>>
>> 1)  The role WG/IETF mailing lists play in building and
>>       gauging consensus
>>    
> 
> Yeah, as I just replied to Tom, I think this is worth adding, probably
> in section 2 or 3.

great.

> 
>> 2) That some participants/chairs/I*s like seeing hands, and that's okay
>>    
> 
> Yes, this is directly said in section 4, paragraphs 4 & 5. What do you
> think is missing?

It says hum+hands. My point is hands-only is okay and can be essentially
equivalent to the "humming" described in your document.  I think it
would be valuable to make this point explicitly, as I essentially
everything else you say in the document.  And I completely agree with
your point that a show of hands (& a poll on the list) are not votes.

> 
>> There are different ways to achieve and determine consensus.  As stated
>> in RFC2418:
>>     Consensus
>>     can be determined by a show of hands, humming, or any other means on
>>     which the WG agrees (by rough consensus, of course).  Note that 51%
>>     of the working group does not qualify as "rough consensus" and 99% is
>>     better than rough.  It is up to the Chair to determine if rough
>>     consensus has been reached.
>>    
> 
> As I said in my reply to Dave, there's part of the above that I disagree
> with, or at least think is an oversimplification. But it definitely need
> citing.

got it, but as you say this document is Informational and doesn't
propose any change to IETF process, while RFC2418 is a BCP which does
define process.

Lou

> 
> pr
> 


From hartmans@mit.edu  Fri Oct 11 07:48:44 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 DC11D21E81B2; Fri, 11 Oct 2013 07:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.577
X-Spam-Level: 
X-Spam-Status: No, score=-101.577 tagged_above=-999 required=5 tests=[AWL=1.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 YeVakfZamSwK; Fri, 11 Oct 2013 07:48:39 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D688A21F9B4B; Fri, 11 Oct 2013 07:48:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 23EAB204E1; Fri, 11 Oct 2013 10:47: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 4LtmncORN0QO; Fri, 11 Oct 2013 10:47:08 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-136-31-107.hsd1.ma.comcast.net [50.136.31.107]) (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; Fri, 11 Oct 2013 10:47:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8731A82B26; Fri, 11 Oct 2013 10:48:34 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-karp-ops-model-07
References: <F0728D4E-4DEA-47B4-BA75-CCDB9C562924@nostrum.com> <5224A352.6050007@cisco.com> <tsl1u4n9ua6.fsf@mit.edu> <94891A49-8E45-44AF-B971-8A21DEFFB464@nostrum.com>
Date: Fri, 11 Oct 2013 10:48:34 -0400
In-Reply-To: <94891A49-8E45-44AF-B971-8A21DEFFB464@nostrum.com> (Ben Campbell's message of "Tue, 24 Sep 2013 17:46:40 -0500")
Message-ID: <tsl8uxzyibh.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: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, karp@ietf.org, 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, 11 Oct 2013 14:48:45 -0000

>>>>> "Ben" == Ben Campbell <ben@nostrum.com> writes:

    Ben> Hi, thanks for the response. Comments inline. I've removed
    Ben> sections that do not appear to need further comment.
    Ben> On Sep 17, 2013, at 1:29 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
    >> 
    genart> -- This abstract claims that this draft is a discussion of
    genart> issues. From that per spective, I don't think the use of
    genart> 2119 language is appropriate. There are some specific areas
    genart> (mentioned below) where 2119 language is used in imprecis
    genart> ways, and may do harm to the reader's understanding. There
    genart> are other uses that may be more reasonable. But I think the
    genart> draft would be better off dispensing with 2119 language
    genart> altogether.
    Ben> If you think 2119 language is appropriate, then it might be
    Ben> helpful to update the abstract and intro to make it more clear
    Ben> that the draft offers normative guidance, and make it clear
    Ben> when and to whom it applies. For example, section 3 says
    Ben> "Implementations of this model MUST..." It's not clear to me
    Ben> what "this model" means when the abstract and intro make it
    Ben> sound like this draft is early work towards eventually
    Ben> developing such a model.

Having re-read the abstract and your comments I have a better
understanding of what you mean.
I've updated the abstract.
I think this should help a lot.
Sorry that I didn't get the version published last time; will upload
today.

    >> 
    genart> This seems like a place where descriptive language would be
    genart> better than 2119 lan guage. In particular, "and so on"
    genart> leaves things too open ended and imprecise. Al so, the use
    genart> of 2119 language in an example seems a bit off.
    >> 
    >> So, the requirement is stated in the first clause using 2119
    >> language:
    >> 
    >> Operational Requirements: implementations of this model MUST
    >> support configuration of keys at the most general scope for the
    >> underlying protocol;
    >> 
    >> The sentence goes on to apply that requirement to some common
    >> cases: protocols supporting per-peer keys MUST permit
    >> configuration of per-peer keys, protocols supporting
    >> per-interface keys MUST support configuration of per-interface
    >> keys, and so on.
    >> 
    >> You might prefer different style rules; you might prefer that the
    >> restatements of the general requirement to specific situations
    >> not use 2119 language.  I think the right approach for that is to
    >> try and build community consensus on those style rules and not to
    >> apply those rules until such a consensus is achieved.  I do agree
    >> that care should be used when using 2119 in a restatement, but in
    >> this instance believe it is OK.
    >> 
    >> I've removed the 2119 language from the example, although I think
    >> it was harmless.

    Ben> Ok.

    Ben> My concern was that it is open ended. The words "and so on"
    Ben> tells me that there may be more normative requirements that the
    Ben> reader is left to infer. That could make it hard to know if an
    Ben> implementation fully complies.

Ah,
how about replacing "and so on," with "and so on for  any additional
scopes?"
My hope is to make it clear that the additional requiresments are
related to any configuration scopes the  protocol has.

    genart> -- section 4, 2nd to last paragraph:
    >> 
    genart> Seems like other disadvantages are worth mentioning. For
    genart> example, the potential impact of a compromised CA.
    >> 
    >> I spent a few minutes trying to come up with an argument whether
    >> CA compromise was better or worse than other systems compromise
    >> profile, particularly focusing on central management system
    >> compromise in the preshared key case.  I think it's difficult to
    >> come up with an argument about whether that's actually a
    >> disadvantage of CAs in this case and I think getting consensus
    >> would be non-trivial.  I also think that managing CA compromise
    >> can either be handled on the cost axis (secure offline CA) or the
    >> complexity axis (push out new CA certs and end-entity certs on
    >> compromise).  So, I think the current text is accurate.  If there
    >> are specific disadvantages that can easily be verified, I'm open
    >> to revisions.
    >> 

    Ben> The previous paragraph listed an advantage that the fact that a
    Ben> server only has it's on key material limits the scope. The idea
    Ben> of a compromised CA having a potentially very large scope of
    Ben> damage is pretty well known, and it's a very real concern given
    Ben> the news of late. How that compares to the compromise of a
    Ben> central management system depends on whether the CA is a "third
    Ben> party" (or as in the web browser case, many third parties) vs
    Ben> the operator itself. (I guess the central management system
    Ben> could also be a third party, but that may be less typical.)

Ah,
I don't think a third-party CA would make sense for KARP.
Which is why I find evaluating the tradeoff to be hard: I expect the CA
and central management systems would control the same machines.

    genart> -- 4.1:
    >> 
    genart> I understand why one might choose not to include a
    genart> real-world example here, but is there something that can be
    genart> referenced?
    >> 
    >> Real wmorld example of what?

    Ben> Sorry, that was for section 4.1.2: "This hypothetical example
    Ben> is overly simplistic; real-world attacks exploiting key
    Ben> separation weaknesses tend to be complicated..."

Agreed.
For others following the conversation, I'd appreciate a reference.
I'm finding good e-mail discussions, class-notes, etc, but nothing that
I can cite in an RFC.
I'd love to have a reference here.

From v6ops@globis.net  Fri Oct 11 00:48:53 2013
Return-Path: <v6ops@globis.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 F1E1121E809C; Fri, 11 Oct 2013 00:48: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 mJPt+iWMOpul; Fri, 11 Oct 2013 00:48:53 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id AB32D21E8190; Fri, 11 Oct 2013 00:48:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 986BF870077; Fri, 11 Oct 2013 09:48:47 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22SVJ3o5CgrH; Fri, 11 Oct 2013 09:48:47 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 63527870056; Fri, 11 Oct 2013 09:48:47 +0200 (CEST)
Message-ID: <5257AD5E.9090806@globis.net>
Date: Fri, 11 Oct 2013 09:48:46 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, brian.e.carpenter@gmail.com
Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 11 Oct 2013 08:28:33 -0700
Cc: 6man Mailing List <ipv6@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, 11 Oct 2013 07:48:54 -0000

Templin, Fred L wrote:
> Hi Brian,
>
> Responding in a slightly re-arranged order:
>
>> The problem is that you are asserting that middleboxes that a tunnel
>> passes through are expected to examine the complete header chain of
>> the encapsulated packet even if the encapsulated packet is a fragment.
> Yes, but change "are expected to" to "should be able to".

I personally don't see this going anywhere.

Unless you specifically define what is a "tunnel" and you specifically
define a maximum depth of nesting.

The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
since the value of the "IPv6 next header" is taken from the same code
space as the ULP header values, and there's no specific marker or
"header length" field in IPv6 that explicitly marks a point as "This is
the end of the IPv6 header chain in all circumstances: stop header
parsing here."

Ok, there's a bunch of current code-points that are today considered as
valid ULP's or next-header values, but that is neither time invariant
nor exhaustive, so solving this issue via a registry means there will
always be middlebox code in the wild that lags any updates.

These middleboxes won't be able to differentiate between an unknown ULP,
and an unknown IPv6 next-header. That potentially makes a default pass
or drop decision awkward.

If it's so important to be able to differentiate between what is an ULP
and what is a next header, and we can't reliably do that today, maybe
that's a fundamental flaw in IPv6 that should be addressed.


>
>> I think that's an unreasonable expectation. A reasonable expectation
>> is that middleboxes should identify the encapsulated packet as
>> a payload that they cannot analyse, and let it go (unless they
>> have a policy setting to drop tunnelled packets, which is a
>> different discussion).
> But why? If headers beyond the first IPv6 encapsulation header are
> available in the clear, the middlebox should be able to parse them
> if it wants to. Wireshark already does exactly that - it keeps on
> parsing beyond the first encapsulation header up to and including
> the true ULP header. And, if Wireshark can do it, so can any other
> middlebox that believes security would be improved by continuing
> to parse the entire chain - whether or not there is a standard
> saying it must not do so.

Because it leaves open the possibility for an attacker to apply the
obfuscation we seek to limit.


> Parsing the additional headers beyond the first encapsulation header
> provides defense-in-depth. Perimeter middleboxes can then weed out
> the bad stuff without either allowing the bad stuff to penetrate more
> deeply into the organization or dropping good stuff that should be
> allowed through.


There's also a myriad of tunneling technology out there.

Again, what is an ULP? Where do you stop parsing?

Is GRE a tunnel or an ULP? (GRE can run over almost anything)
Is SSH an ULP or a tunnel? (port tunneling)
Is Teredo a tunnel or is it an ULP (UDP) or both?
GRE/ LT2P over HTTP anyone?

The notion of "perimeter" is moveable in the presence of such tunnels.

Presumably there comes a point where the tunnel is terminated and the
transported packet is de-encapsulated, and that IMHO forms another
perimeter where you'd anyway have to apply further security checks.

I think the draft does what it can in a pragmatic manner, but might
benefit from some acknowledgement that this security approach of
applying parsing at a single perimeter can never ever catch all variants
of transporting FOO over BAR.

IMHO It's only at the moment of de-encapsulation that the full semantics
of the payload are revealed in these modern times of "everything
transported over HTTP".




>> Since the problem recurses as we tunnel tunnels, I don't see how any
>> finite limit can solve the problem. 1280 itself is a pragmatic choice
>> of "a bit shorter than 1500".

Agreed.

> The 1280 is assuming that all links in the path have a 1500 MTU and
> so RFC2460 allowed (1500 - 1280) = 220 bytes for additional IPv6
> headers added by nested tunnels without incurring fragmentation.
> I am asserting instead that we have to allow for paths that include
> links with a 1280 MTU and so tunnels will have to fragment over
> such paths.
>
> That means that the first fragmenting tunnel would have room for
> 1240 in the first fragment, the second fragmenting tunnel would
> have room for 1200 in the first fragment, etc. That is why I would
> prefer that hosts limit the size of their header chains to 1024; so
> that nested tunnels that fragment will still be highly likely to
> have the entire header chain in the first fragment.
>  
>> I understood that to be the basis on which the WG reached consensus.
> Maybe the WG didn't understand that such a consensus would make
> tunnels less reliable and less secure.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>>     Brian
>  


-- 
Regards,
RayH


From woolf@isc.org  Thu Oct 10 11:58:53 2013
Return-Path: <woolf@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 8374121E805F for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:58:09 -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 4tMml4b7qIwL for <ietf@ietfa.amsl.com>; Thu, 10 Oct 2013 11:57:48 -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 2795F21F9C99 for <ietf@ietf.org>; Thu, 10 Oct 2013 11:56:54 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 9A00EC9497; Thu, 10 Oct 2013 18:56:25 +0000 (UTC) (envelope-from woolf@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1381431400; bh=k4No4fehoNRnOHTtwD7FulU0Je4FnOjxMgkC2TkEBBE=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=vIUkp6/paO4u17SamUgbMtfb0zw1ButIWg5jWL6nFeBU7BEPJentNiCaC17LcaCDc z+iSTJM9MXjFtJ+0Gl+ED7amF/JlpKMWtNJ0ryVJ5f4gyRy7t32cazXfoEQ1rXqhRa 6k6RPDOZ4RuJTzqEpNVPkdAcuLbCZpOTBiIvQq/c=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 10 Oct 2013 18:56:25 +0000 (UTC) (envelope-from woolf@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8513D160435; Thu, 10 Oct 2013 19:00:15 +0000 (UTC)
Received: from dhcp-220-114.meetings.nanog.org (dhcp-220-114.meetings.nanog.org [199.187.220.114]) by zmx1.isc.org (Postfix) with ESMTPSA id 6F04B16004C; Thu, 10 Oct 2013 19:00:15 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: leader statements
From: Suzanne Woolf <woolf@isc.org>
In-Reply-To: <5256F239.1000400@gmail.com>
Date: Thu, 10 Oct 2013 14:56:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4B573F5-DA6E-4504-AB9A-CB8615030628@isc.org>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org>	<20131007225129.GA572@laperouse.bortzmeyer.org>	<6.2.5.6.2.20131008213432.0c1e4b30@resistor.net>	<20131009064438.GA47673@mx1.yitter.info>	<E003D3DC4E4B3208CF14E8E0@JcK-HP8200.jck.com> <20131009192715.GG49231@mx1.yitter.info> <5255B647.4090103@gmail.com> <93D54BF0-FFE6-4A3D-ADDE-7EC2FC3AFBC0@isi.edu> <5256F239.1000400@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-DCC--Metrics: post.isc.org; whitelist
X-Mailman-Approved-At: Fri, 11 Oct 2013 08:28:50 -0700
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, 10 Oct 2013 18:58:53 -0000

On Oct 10, 2013, at 2:30 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> I really think we need to stop behaving as if the IETF is a
> small group of people who know each other well.  Consensus
> decision-making does not scale well with the number of
> participants, and if we're going to require consensus on
> every leadership decision we're not going to get anything
> done.  Now, being frozen and inactive may be preferable to
> having Jari and Russ go off and make a cooperative public
> statement about internet governance, but it seems to me that
> as long as we have recall and appeals processes we have
> incentives for IETF and IAB chairs, and IESG and IAB members,
> not to go off and do controversial things unilaterally, as
> well as a remedy if they do.

This seems exactly right to me, with the additional observation that =
even if we're=20
insisting that the leadership get consensus on such issues as the =
Montevideo=20
statement, we're still trusting them to find, frame, and bring us the =
right issues.=20

In other words, it's trust all the way down, and if we don't trust the =
leadership to=20
identify relevant issues and address them sanely, obtaining that =
all-but-impossible=20
consensus is just going to leave us with the same problem that people =
will want
consensus first on what questions are worth addressing and how the =
consensus=20
is to be expressed.

Among other weaknesses, this doesn't seem to be a way to demonstrate to =
the
interested participant/observer that we know how to manage the =
challenges of
scaling things.

Suzanne=

From Fred.L.Templin@boeing.com  Fri Oct 11 08:33:28 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B7311E81CE; Fri, 11 Oct 2013 08:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.365
X-Spam-Level: 
X-Spam-Status: No, score=-6.365 tagged_above=-999 required=5 tests=[AWL=0.234,  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 1+MSz2AHkRZr; Fri, 11 Oct 2013 08:33:22 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id E03DA11E820C; Fri, 11 Oct 2013 08:33:20 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BFXJvI003282; Fri, 11 Oct 2013 10:33:20 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BFXI7a003278 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:33:19 -0500
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 08:33:18 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 08:33:17 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlZjF9Ic7sRuGU+T9Pt4WN8/H5nvmo2Q
Date: Fri, 11 Oct 2013 15:33:17 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>
In-Reply-To: <5257AD5E.9090806@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 15:33:28 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Friday, October 11, 2013 12:49 AM
> To: Templin, Fred L; brian.e.carpenter@gmail.com
> Cc: ietf@ietf.org; 6man Mailing List
> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
>=20
> Templin, Fred L wrote:
> > Hi Brian,
> >
> > Responding in a slightly re-arranged order:
> >
> >> The problem is that you are asserting that middleboxes that a tunnel
> >> passes through are expected to examine the complete header chain of
> >> the encapsulated packet even if the encapsulated packet is a
> fragment.
> > Yes, but change "are expected to" to "should be able to".
>=20
> I personally don't see this going anywhere.
>=20
> Unless you specifically define what is a "tunnel" and you specifically
> define a maximum depth of nesting.
>=20
> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
> since the value of the "IPv6 next header" is taken from the same code
> space as the ULP header values, and there's no specific marker or
> "header length" field in IPv6 that explicitly marks a point as "This is
> the end of the IPv6 header chain in all circumstances: stop header
> parsing here."
>=20
> Ok, there's a bunch of current code-points that are today considered as
> valid ULP's or next-header values, but that is neither time invariant
> nor exhaustive, so solving this issue via a registry means there will
> always be middlebox code in the wild that lags any updates.
>=20
> These middleboxes won't be able to differentiate between an unknown
> ULP,
> and an unknown IPv6 next-header. That potentially makes a default pass
> or drop decision awkward.
>=20
> If it's so important to be able to differentiate between what is an ULP
> and what is a next header, and we can't reliably do that today, maybe
> that's a fundamental flaw in IPv6 that should be addressed.
>=20
>=20
> >
> >> I think that's an unreasonable expectation. A reasonable expectation
> >> is that middleboxes should identify the encapsulated packet as
> >> a payload that they cannot analyse, and let it go (unless they
> >> have a policy setting to drop tunnelled packets, which is a
> >> different discussion).
> > But why? If headers beyond the first IPv6 encapsulation header are
> > available in the clear, the middlebox should be able to parse them
> > if it wants to. Wireshark already does exactly that - it keeps on
> > parsing beyond the first encapsulation header up to and including
> > the true ULP header. And, if Wireshark can do it, so can any other
> > middlebox that believes security would be improved by continuing
> > to parse the entire chain - whether or not there is a standard
> > saying it must not do so.
>=20
> Because it leaves open the possibility for an attacker to apply the
> obfuscation we seek to limit.
>=20
>=20
> > Parsing the additional headers beyond the first encapsulation header
> > provides defense-in-depth. Perimeter middleboxes can then weed out
> > the bad stuff without either allowing the bad stuff to penetrate more
> > deeply into the organization or dropping good stuff that should be
> > allowed through.
>=20
>=20
> There's also a myriad of tunneling technology out there.
>=20
> Again, what is an ULP? Where do you stop parsing?

The middlebox stops parsing when it decides it has seen enough. With
Wireshark at least, it blasts right through encapsulating IP headers
and continues up to and including the ultimate TCP/UDP/ICMP etc.
header inserted by the original host. The goal is to give the
middlebox enough information so that it can parse as deeply into
the headers as it wants to.

> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
> Is SSH an ULP or a tunnel? (port tunneling)
> Is Teredo a tunnel or is it an ULP (UDP) or both?
> GRE/ LT2P over HTTP anyone?
>=20
> The notion of "perimeter" is moveable in the presence of such tunnels.

We will want for middleboxes at outer perimeters to be able to parse
as many headers as they want to before releasing the packet to
middleboxes at inner perimenters. Otherwise, bad stuff can get past
the outermost perimeters and waste bandwidth and/or cause havoc
within the protected zone.=20

> Presumably there comes a point where the tunnel is terminated and the
> transported packet is de-encapsulated, and that IMHO forms another
> perimeter where you'd anyway have to apply further security checks.

Nested tunnels give you perimeters within perimeters, yes. But, we
will want the outer perimeters to be able to parse as deeply as
they want to before passing on to an inner perimeter.

> I think the draft does what it can in a pragmatic manner, but might
> benefit from some acknowledgement that this security approach of
> applying parsing at a single perimeter can never ever catch all
> variants
> of transporting FOO over BAR.
>=20
> IMHO It's only at the moment of de-encapsulation that the full
> semantics
> of the payload are revealed in these modern times of "everything
> transported over HTTP".
>=20
>=20
>=20
>=20
> >> Since the problem recurses as we tunnel tunnels, I don't see how any
> >> finite limit can solve the problem. 1280 itself is a pragmatic
> choice
> >> of "a bit shorter than 1500".
>=20
> Agreed.

I guess I will have to repeat myself from what I said several
months ago. The 1280 came from a desire to have multiple nested
tunnels without requiring the tunnels to fragment since the
underlying links presumably all configure a 1500 MTU. But, what
would that look like in real life?

- The first tunnel would have to configure a 1280 MTU so that its
  encapsulated packets emerged as 1320
- the second tunnel would have to configure a 1320 MTU so that its
  encapsulated  packets emerged as 1360
- the third tunnel would have to configure a 1360 MTU so that its
  encapsulated packets emerged as 1400
- etc.

But, in real life, it is not possible to assume that we can lay
hands on all tunnel endpoints so as to carefully set MTUs that
satisfy the nesting level - and, when multiple administrative
domains are involved, it can't be done at all.

Please go back in the archives to where I posted the derivation
of the 1280 minMTU (circa 1997):

http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html

My conclusion is that the 1280/1500 was well intentioned, but
unfortunately not very well thought out.

Thanks - Fred
fred.l.templin@boeing.com

> > The 1280 is assuming that all links in the path have a 1500 MTU and
> > so RFC2460 allowed (1500 - 1280) =3D 220 bytes for additional IPv6
> > headers added by nested tunnels without incurring fragmentation.
> > I am asserting instead that we have to allow for paths that include
> > links with a 1280 MTU and so tunnels will have to fragment over
> > such paths.
> >
> > That means that the first fragmenting tunnel would have room for
> > 1240 in the first fragment, the second fragmenting tunnel would
> > have room for 1200 in the first fragment, etc. That is why I would
> > prefer that hosts limit the size of their header chains to 1024; so
> > that nested tunnels that fragment will still be highly likely to
> > have the entire header chain in the first fragment.
> >
> >> I understood that to be the basis on which the WG reached consensus.
> > Maybe the WG didn't understand that such a consensus would make
> > tunnels less reliable and less secure.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >>     Brian
> >
>=20
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Fri Oct 11 08:36:11 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB0B11E8235; Fri, 11 Oct 2013 08:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.388
X-Spam-Level: 
X-Spam-Status: No, score=-6.388 tagged_above=-999 required=5 tests=[AWL=0.211,  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 XQQCUfrh1Zty; Fri, 11 Oct 2013 08:36:05 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id EFF8011E821F; Fri, 11 Oct 2013 08:36:04 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BFa3O7009490; Fri, 11 Oct 2013 10:36:04 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BFZu2i009356 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:36:03 -0500
Received: from XCH-BLV-305.nw.nos.boeing.com (130.247.25.217) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 08:36:00 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-305.nw.nos.boeing.com ([169.254.5.85]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 08:36:00 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlzzebc9KTehbEGO6mhunuAlj5nvofSw
Date: Fri, 11 Oct 2013 15:36:00 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com>
In-Reply-To: <5257B870.1060003@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 15:36:11 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, October 11, 2013 1:36 AM
> To: Ray Hunter; Templin, Fred L; brian.e.carpenter@gmail.com
> Cc: 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/11/2013 04:48 AM, Ray Hunter wrote:
> >
> > I think the draft does what it can in a pragmatic manner, but might
> > benefit from some acknowledgement that this security approach of
> > applying parsing at a single perimeter can never ever catch all
> variants
> > of transporting FOO over BAR.
>=20
> FWIW, my idea of the I-D is that it says "look, if you don't put all
> this info into the first fragment, it's extremely likely that your
> packets will be dropped". That doesn't mean that a middle-box may want
> to look further. But looking further might imply
> reassemble-inspect-and-refragment... or even reassemble the TCP stream
> (e.g. think about a SSL/TCP-based VPN...)

We definitely don't want that. That is why we would prefer for
the entire header chain (starting from the outermost IP header
up to and including the headers inserted by the original host)
to fit within the first fragment even if there are multiple
encapsulations on the path.

Thanks - Fred
fred.l.templin@boeing.com

> Cheers,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20


From barryleiba.mailing.lists@gmail.com  Fri Oct 11 08:52:29 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 8ECD521E8120 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 08:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Level: 
X-Spam-Status: No, score=-101.995 tagged_above=-999 required=5 tests=[AWL=-0.017, 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 LcyXp-idavkA for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 08:52:28 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0D921E8114 for <ietf@ietf.org>; Fri, 11 Oct 2013 08:52:24 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id c11so3555045lbj.41 for <ietf@ietf.org>; Fri, 11 Oct 2013 08:52:23 -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:message-id:subject :from:to:cc:content-type; bh=aTXmm2mFqWxLmDBsF+j/Vh/XeR8fRjKr37um3RxlHzM=; b=Dsj7v5nIIEAUsMjqAqIk9rXHp7QbOTuJRW3uyh8TDQ+onrQB8tYKHXW3ra97rSwCRr +sxK+7ToPgN2/GreV5BCKFq9uxn4jCj3p35xhOlDTh4tdHLiVqqUgGAtg7jzR9HGnW8a NfD3MdIA28oGrpE3J3iGQFhLWa4aGLKNMq9sCpp/eiLwodSrHNkzBsQ7exdlSl2e9ajY uPrJ2HO+KyHfWyqrDsaNBHDKf9fzSjrlX11jDwJ3598WVeolkCnA8RSzdkhaInZt/xZx A0moqXL+hh3TGVlww/yBCMU9yE0TYqcM4npgklDApsa6uXUdwbFBYT8Nt2OIfvMBgGOr MG1Q==
MIME-Version: 1.0
X-Received: by 10.112.28.109 with SMTP id a13mr17343160lbh.3.1381506743260; Fri, 11 Oct 2013 08:52:23 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Fri, 11 Oct 2013 08:52:23 -0700 (PDT)
In-Reply-To: <5257C79A.9090004@viagenie.ca>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <5257C79A.9090004@viagenie.ca>
Date: Fri, 11 Oct 2013 11:52:23 -0400
X-Google-Sender-Auth: ARHVKGSYdFJKZ2brfchgSr59rX4
Message-ID: <CAC4RtVBEfUmpodWQ+55XDKiz3+B7Ua6QDyT7hER4DiK2Jkst4g@mail.gmail.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type (see <draft-hausenblas-csv-fragment-06.txt>)
From: Barry Leiba <barryleiba@computer.org>
To: Simon Perreault <simon.perreault@viagenie.ca>
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: Fri, 11 Oct 2013 15:52:29 -0000

> This draft's premise is interesting, but the implementation leaves to be
> desired. That is, I like the idea of fragment identifiers for CSV, but
> row/column/cell-based selection doesn't address my need.

This is an Independent stream document, and the IETF doesn't have
change control of the document.

The authors can certainly accept your comments at their discretion.
But this last call isn't for comments on the *document*.  It's only to
assess whether there are objections to the IESG's allowing the change
to the media types registry.

Barry, Applications AD

From simon.perreault@viagenie.ca  Fri Oct 11 09:00:59 2013
Return-Path: <simon.perreault@viagenie.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 B3BF821F9E9F for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:00: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 k0JjYxGXHp2T for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:00:59 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A1DFA21F9E7E for <ietf@ietf.org>; Fri, 11 Oct 2013 09:00:44 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:41c9:83f1:e70a:4e62]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 9A1E4401FA; Fri, 11 Oct 2013 12:00:41 -0400 (EDT)
Message-ID: <525820A8.70000@viagenie.ca>
Date: Fri, 11 Oct 2013 18:00:40 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type (see <draft-hausenblas-csv-fragment-06.txt>)
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com>	<5257C79A.9090004@viagenie.ca> <CAC4RtVBEfUmpodWQ+55XDKiz3+B7Ua6QDyT7hER4DiK2Jkst4g@mail.gmail.com>
In-Reply-To: <CAC4RtVBEfUmpodWQ+55XDKiz3+B7Ua6QDyT7hER4DiK2Jkst4g@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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, 11 Oct 2013 16:01:00 -0000

Le 2013-10-11 17:52, Barry Leiba a écrit :
> This is an Independent stream document, and the IETF doesn't have
> change control of the document.
> 
> The authors can certainly accept your comments at their discretion.
> But this last call isn't for comments on the *document*.  It's only to
> assess whether there are objections to the IESG's allowing the change
> to the media types registry.

Ah, right, I didn't notice that in my enthusiasm.

No objection then. But I hope the authors are listening! :)

Thanks,
Simon

From jcurran@istaff.org  Fri Oct 11 09:02:33 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 51A2411E81BB for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:02:33 -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 CYBHNgKgbb2X for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:02:27 -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 7F90621F9EAF for <ietf@ietf.org>; Fri, 11 Oct 2013 09:02:27 -0700 (PDT)
Received: from dhcp-220-43.meetings.nanog.org ([199.187.220.43]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1VUfAY-000NWs-TE for ietf@ietf.org; Fri, 11 Oct 2013 16:02:26 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 199.187.220.43
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/FAV2t+hNl/ZDj3RP84WS4
From: John Curran <jcurran@istaff.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Of governments and representation (was: Montevideo Statement)
Message-Id: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
Date: Fri, 11 Oct 2013 09:02:25 -0700
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Oct 2013 16:02:33 -0000

Folks -=20

As a result of the Internet's growing social and economic importance, =
the underlying=20
Internet structures are receiving an increasing level of attention by =
both governments=20
and civil society.  The recent revelations regarding US government =
surveillance of=20
the Internet are now greatly accelerating government attention on all of =
the Internet=20
institutions, the IETF included.  All of this attention is likely bring =
about significant
changes in the Internet ecosystem, potentially including how the IETF =
interacts with
governments, civil society, and other Internet organizations globally.

In my personal view, it is a very important for the IETF to select =
leadership who can
participate in any discussions that occur, and it would further be =
prudent for the IETF
leaders to be granted a sufficient level of support by the community to =
take positions=20
in those discussions and make related statements, to the extent the =
positions and
the statements are aligned with established IETF positions and/or =
philosophy.  =20

The most interesting part of the myriad of Internet Governance =
discussions is that=20
multiple organizations are all pushing ahead independently from one =
another, which
results in a very dynamic situation where we often don't even know that =
there will be
a conference or meeting until after its announced, do not know auspices =
under which=20
it will be held, nor what the scope of the discussions held will =
ultimately be.  However,=20
the failure of any of the Internet organizations to participate will not =
actually prevent=20
consideration of a variety of unique and colorful proposals for =
improving the Internet=20
and/or the IETF, nor will it preclude adoption even in the absence of =
IETF input...

The IETF is a very important Internet institution, and it deserves to be =
represented
in any discussions which might propose changes to the fundamental =
mechanisms of=20
Internet cooperation.  It would be a wonderful world indeed if all of =
these discussions=20
started with submission of an Internet Draft and discussion on open =
mailing lis, but=20
that hasn't been the modus operandi of governments and is probably too =
much to=20
realistically expect.

/John=

From johnl@iecc.com  Fri Oct 11 09:25:44 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 400CD21E81D3 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.348
X-Spam-Level: 
X-Spam-Status: No, score=-102.348 tagged_above=-999 required=5 tests=[AWL=0.251, 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 oA4cokhEjN1x for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:25:30 -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 8025821E812F for <ietf@ietf.org>; Fri, 11 Oct 2013 09:25:26 -0700 (PDT)
Received: (qmail 60138 invoked from network); 11 Oct 2013 16:25:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Oct 2013 16:25:25 -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=52582675.xn--hew.k1309; i=johnl@user.iecc.com; bh=2sgfvo4CCXDaPSk6NdrdYgQXNAeFJnWUU9/uEPN2WOg=; b=g2yVqdY83kADZYYlRY+D9MPep3jpJBSrqXJcFq6oKI978t+JLwZwtnKl5qCOVb7CDTeYfVaQ1UCyHM5iEkQhavHFUDk/lCaYJRLsbYzdDBLAB93gEqc6SeMhOOZAKln8f45W0DbAnRJXdSc+JugBls3tqTUO0/GDYHy8B2pnGbJXX2HpjZKZcvL7ccT5HUHLr3bYunRedX4F1+T1WOpZ4CKUGvNF4/sGN5sINZmRSMSVej676nHDqNTbbLquS6vc
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=52582675.xn--hew.k1309; olt=johnl@user.iecc.com; bh=2sgfvo4CCXDaPSk6NdrdYgQXNAeFJnWUU9/uEPN2WOg=; b=Ujb1p+Hz28DyiX3xgYBIdpQhVBcYNxTi33Ric6KjmMJPYe+vTtq2vR4x5BqHMFIWgNQaFu0RCApJ8Y44xQwPnlOxqp1pdmmwV/cWIwNWQCow5fMoR8PBe2tc9RSPe6Q2uXyWTAq5U4aPCc8TbwJAsDSuxoUO77vGIFcKw/EWpOBLUsJwaYVtFGmaXULo6q0N+xhyJpeP7ox1MyvROSZC5bb4451LrkY6ezPzyCoDIhLdBi9EcmQtcryPf6oWOB0a
Date: 11 Oct 2013 16:25:03 -0000
Message-ID: <20131011162503.23599.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: "The core Internet institutions abandon the US Government"
In-Reply-To: <CAMzo+1bjzpWOVNUqzZMfgBDoZ76Zdr_CyXfhovh_pnKEE-aB-Q@mail.gmail.com>
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: Fri, 11 Oct 2013 16:25:44 -0000

>Just few quick questions,
>
>In what part of Fadi Chehadé mandate at ICANN this falls ? And who
>sanctified him as representative of the Internet Community ?
>
>He is just an employee of ICANN and these actions go way beyond ICANN's
>mission and responsibilities.

ICANN has a long running fantasy that they are a global
multi-stakeholder organization floating above mere politics, and not a
US government contractor incorporated as a California non-profit.
This will never change, and everyone familiar with the situation knows
it, but for internal political reasons ICANN likes to pretend
otherwise.

I suppose in the current political situation about the NSA there's no
harm in the other groups going along with it for a while.

R's,
John

From housley@vigilsec.com  Fri Oct 11 09:28: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 22B4721E812E; Fri, 11 Oct 2013 09:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 4fEuXC9sQIQw; Fri, 11 Oct 2013 09:28:09 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id CBB6321E81B0; Fri, 11 Oct 2013 09:28:08 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id C7436F2409F; Fri, 11 Oct 2013 12:28:10 -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 cXF2ATBcNx2F; Fri, 11 Oct 2013 12:27:38 -0400 (EDT)
Received: from [192.168.2.107] (pool-71-191-197-233.washdc.fios.verizon.net [71.191.197.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DF9E3F240B7; Fri, 11 Oct 2013 12:27:43 -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-resnick-on-consensus-05
Date: Fri, 11 Oct 2013 12:27:30 -0400
Message-Id: <9EBBA597-AA12-44AE-9096-9D1DC88260EB@vigilsec.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@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, 11 Oct 2013 16:28:14 -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-resnick-on-consensus-05
Reviewer: Russ Housley
Review Date: 11-October-2013
IETF LC End Date: 11-November-2013
IESG Telechat date: Unknown

Summary: This draft is ready for publication as an Informational RFC.


Major issues:

Section 4 says: "... members of any given working group ..."  Working
groups do not have members; they have participants.  Please reword to
avoid confusion on this point.


Minor issues:

Section 4 says that humming should be the start of a conversation, not
the end.  However, it can be either.  Using the document's example, the
chair could ask, "Hum now if you cannot live with choice A."  Silence
confirms that rough consensus has been reached.

So, I guess I do not agree with the last sentence in Section 5.

Section 6 tells about some pitfalls to avoid, but the hum can still be
a very valuable tool to help a chair determine if the group has reached
consensus.

Further, a hum in a BOF is different.  The topic of consensus on
procedural matter comes up in Section 5, but it does not get much
attention.  For example in a BOF the hum might ask: "Hum now if
you think that the IETF should take on this work... Hum now if you
think the IETF should not take on this work..."  The BOF Chair or AD
is trying to figure out if there is enough support for the work to
go forward.  This type of of hum is quite different than judging rough
consensus on a technical issue.  Yes, it can be the beginning of a
conversation, and it must allow for participants to explain why they
believe the IETF taking on the work might be harmful.  However, this
difference should be explained in the document.


Nits:

In section 2, the document says "... not appealing to some others."
When I read it the firs time, the RFC 2026 definition of "appeal"
jumped into my mind.  That is not the intent here.  Maybe it is just
me.  Please consider rewording, especially since the RFC 2026 meaning
is used in Section 3.


From abdussalambaryun@gmail.com  Fri Oct 11 09:28:41 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 7558B21E8130 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level: 
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5 tests=[AWL=-0.016, 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 z0eK5L+NyY5f for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:28:41 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 02F5E21E812E for <ietf@ietf.org>; Fri, 11 Oct 2013 09:28:36 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id v10so4513621pde.10 for <ietf@ietf.org>; Fri, 11 Oct 2013 09:28: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=23YsfmGZDnhyQ96T+kgy1Y9fqmjAiA7oplknnTgjAUI=; b=t3biBExvmCZwZNqWzOOyvGxCvEkY/93jTtkED9UXzG2Hxm7W6CF801sH5tBzJK2edH HNQwQlhy730Z9M1PvX0ypp7aB8m1iblnj/uZmWTx8I7DzmATRDnTOOf4kUzgXmJhy5cu Xy8YbQtQIfsfBwK1UbT4btVFp3vN2fnswPkY2If/Y/baPIEfspMRyev5WhnNlg7wvlfT rewkvQiqefF2KWug5aqocAdfQuRRcRQNGOHgb7NXjV/PP0cTMG/MZD5rj+Cz7pSWOMxL axLliarG1YKsDyvTC8HTSs7SbO04uYdPVX3DzAgckLlqXtjQ4CN8tTeCYXCkVpopA8wC Z0DQ==
MIME-Version: 1.0
X-Received: by 10.66.165.106 with SMTP id yx10mr22070641pab.159.1381508916458;  Fri, 11 Oct 2013 09:28:36 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 11 Oct 2013 09:28:36 -0700 (PDT)
In-Reply-To: <48424340-BED2-47C2-80B8-3697E7286518@piuha.net>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com> <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk> <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net> <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com> <48424340-BED2-47C2-80B8-3697E7286518@piuha.net>
Date: Fri, 11 Oct 2013 17:28:36 +0100
Message-ID: <CADnDZ882uTVuf72BBqcMWpBB2EELR+Oqq_6VvRhDnWKtLfj3-w@mail.gmail.com>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b86c342383d2704e8799cba
Cc: SM <sm@resistor.net>, "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, 11 Oct 2013 16:28:41 -0000

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

I did not like the change of the title which was suggested in diversity
list. the first title was related to IETF, because we need to attract more
other regions in IETF or to facilitate the improve of other region's
participation. The draft's solution was to recommend fellowship (should not
be the only marketing way), which made it distract its real value. I
suggest to see how this fellowship is coordinated with IETF and how much it
attracts (real results needed), this will help the program managers to know
how IETF sees the program from the community point of view (not management
of ietf or management of the program).

AB

On Friday, October 11, 2013, Jari Arkko wrote:

> > we need to keep the flexibility of bringing in someone new
>
> agree
>
> > But my main issue is that the draft sounds like its trying to take over
> and redefine an ISOC program, which I don't think the IETF can or should
> do. The ISOC program has a purpose, a history and at least from my
> perspective is working pretty well with the budget it has available. I'm
> not sure we can actually improve it much.
>
> agree, of course. at best we can provide input. but it really is an ISOC
> program.
>
> Jari
>
>

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

I did not like the change of the title which was suggested in diversity lis=
t.=A0the first title=A0was related to IETF, because we need to attract more=
 other regions in IETF=A0or to facilitate the=A0improve of=A0other region&#=
39;s participation. The draft&#39;s solution was to recommend fellowship (s=
hould not be the only marketing way), which made it distract its real value=
. I suggest to see how this fellowship is coordinated with IETF and how muc=
h it attracts (real results needed), this will help the program managers to=
 know how IETF sees the program from the community point of view (not manag=
ement of ietf or management of the program).<div>
<div><div><div><br></div><div>AB<br><div><br>On Friday, October 11, 2013, J=
ari Arkko  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; we need to keep th=
e flexibility of bringing in someone new<br>

<br>
agree<br>
<br>
&gt; But my main issue is that the draft sounds like its trying to take ove=
r and redefine an ISOC program, which I don&#39;t think the IETF can or sho=
uld do. The ISOC program has a purpose, a history and at least from my pers=
pective is working pretty well with the budget it has available. I&#39;m no=
t sure we can actually improve it much.<br>

<br>
agree, of course. at best we can provide input. but it really is an ISOC pr=
ogram.<br>
<br>
Jari<br>
<br>
</blockquote></div></div></div></div></div>

--047d7b86c342383d2704e8799cba--

From jmamodio@gmail.com  Fri Oct 11 09:33:28 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 E2CDF21E8121 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5, 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 V-sXEzkK3nK4 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:33:28 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E580D21F9E1D for <ietf@ietf.org>; Fri, 11 Oct 2013 09:32:58 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so2827047wgg.24 for <ietf@ietf.org>; Fri, 11 Oct 2013 09:32: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=WrJtp/LEwkmf70msh7oGs8D+d4LaYv2j7mkqEzv5AvU=; b=C/14POxRXE1tI/yssN/AErM/+FJ54LxssxEgFzpAylZ/PjRYdzod4EMuzD+GchdHBz Qbv06i6rZlU6nk1c8T24q0oljCHAk1ud6Epm9teXJuUSt9yFlv4kA7+B8q3YIZaIBC9p tFJFVGXEwnDLIV2i8d1kLJPu3wUU4SQLa+o/Lcw5BZTzjsewnQ7YE21Ph8gu3uzQuyug Cuseym9pdYih78ospobcBpDOLizIsAKPdvHObXlFAgfrjJyVdR47KZgLKdZUwptJWLdE q8JOmCxYy5sy0yTfnwfY2mnWzlNlGg0QZ1hFNHlj1XR4QIOmleHLaAc/HYZ7CKtbG6Wo LkpQ==
MIME-Version: 1.0
X-Received: by 10.180.198.77 with SMTP id ja13mr3573328wic.34.1381509178073; Fri, 11 Oct 2013 09:32:58 -0700 (PDT)
Received: by 10.180.84.38 with HTTP; Fri, 11 Oct 2013 09:32:57 -0700 (PDT)
In-Reply-To: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
Date: Fri, 11 Oct 2013 11:32:57 -0500
Message-ID: <CAMzo+1Yo-z1YH698kPctRoaWauaFirCjw0b=HA2dyf5WGEVa_w@mail.gmail.com>
Subject: Re: Of governments and representation (was: Montevideo Statement)
From: Jorge Amodio <jmamodio@gmail.com>
To: John Curran <jcurran@istaff.org>
Content-Type: multipart/alternative; boundary=047d7b604a68d026fd04e879ab42
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: Fri, 11 Oct 2013 16:33:29 -0000

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

Just to start, there is no clear consensus of what "Internet Governance"
means and entails.

Several organizations just as ICANN, ISOC, ARIN, etc, play a specific role
in the development and operations of the Internet, but by no means are
"representative" of the Internet as a whole, even if you claim that
organizations such as ICANN are muti stakeholders.

Each of the the "leaders" are leading each organization and the sum of the
"leaders" does not make them "leaders of the Internet"

No doubt each institution is important and has to play the role it has to
play, but when you get into governance matters (which again is not clearly
defined what "governance" of the Internet means) some institutions could be
stepping out of their mission and role. Clear example is ICANN, I don't
know who authorized or delegated any sort of mandate to Fadi to get into
conversations about Internet Governance with the Government of Brazil. Yes
he leads ICANN, but as such, he is just and administrative/executive
employee.

In your particular case as President and CEO of ARIN, clearly you "lead"
that organization but it does not make you representative of the Internet
or its users. I can't find anywhere in the Bylaws and Articles of
Incorporation of ARIN the word "Governance."

Nobody will deny any of the alleged "leaders" to participate in any
meeting, conference, event, in their individual capacities, but NONE has
any representation of the whole Internet.

About NSA/Snowden/etc, mixing this matter with Internet Governance make
things more complicated. It would be nice for all governments to come out
clear of what kind of surveillance they do on the Internet (including the
Brazilian Government). IMHO this is a complete separate discussion.

Do we really want to create a "government" for the Internet ? How do you
propose to select people to be representatives for all the sectors ?

And in particular how do you propose to select an IETF representative and
who/how it's going to give her/him its mandate to represent the
organization on other forums ?

My 0.02
Jorge

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

<div dir=3D"ltr"><br><div>Just to start, there is no clear consensus of wha=
t &quot;Internet Governance&quot; means and entails.</div><div><br></div><d=
iv>Several organizations just as ICANN, ISOC, ARIN, etc, play a specific ro=
le in the development and operations of the Internet, but by no means are &=
quot;representative&quot; of the Internet as a whole, even if you claim tha=
t organizations such as ICANN are muti stakeholders.=A0</div>
<div><br></div><div>Each of the the &quot;leaders&quot; are leading each or=
ganization and the sum of the &quot;leaders&quot; does not make them &quot;=
leaders of the Internet&quot;</div><div><br></div><div>No doubt each instit=
ution is important and has to play the role it has to play, but when you ge=
t into governance matters (which again is not clearly defined what &quot;go=
vernance&quot; of the Internet means) some institutions could be stepping o=
ut of their mission and role. Clear example is ICANN, I don&#39;t know who =
authorized or delegated any sort of mandate to Fadi to get into conversatio=
ns about Internet Governance with the Government of Brazil. Yes he leads IC=
ANN, but as such, he is just and administrative/executive employee.</div>
<div><br></div><div>In your particular case as President and CEO of ARIN, c=
learly you &quot;lead&quot; that organization but it does not make you repr=
esentative of the Internet or its users. I can&#39;t find anywhere in the B=
ylaws and Articles of Incorporation of ARIN the word &quot;Governance.&quot=
;</div>
<div><br></div><div>Nobody will deny any of the alleged &quot;leaders&quot;=
 to participate in any meeting, conference, event, in their individual capa=
cities, but NONE has any representation of the whole Internet.</div><div>
<br></div><div>About NSA/Snowden/etc, mixing this matter with Internet Gove=
rnance make things more complicated. It would be nice for all governments t=
o come out clear of what kind of surveillance they do on the Internet (incl=
uding the Brazilian Government). IMHO this is a complete separate discussio=
n.</div>
<div><br></div><div>Do we really want to create a &quot;government&quot; fo=
r the Internet ? How do you propose to select people to be representatives =
for all the sectors ?=A0</div><div><br></div><div>And in particular how do =
you propose to select an IETF representative and who/how it&#39;s going to =
give her/him its mandate to represent the organization on other forums ?</d=
iv>
<div><br></div><div>My 0.02</div><div>Jorge</div><div><br></div></div>

--047d7b604a68d026fd04e879ab42--

From jmamodio@gmail.com  Fri Oct 11 09:37:21 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 E48B021F9C40 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.349
X-Spam-Level: 
X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5 tests=[AWL=1.250,  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 qzTsJGEB4BjR for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:37:21 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 74DE021E805D for <ietf@ietf.org>; Fri, 11 Oct 2013 09:37:20 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so674393wgh.22 for <ietf@ietf.org>; Fri, 11 Oct 2013 09:37:19 -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=Wrt+KtHBGi6fzIra9zhHkRS6mb9T65dtAnG22fp7Pdk=; b=pac5KweXnwOgErzizpo2YqY7Snamf5bd+VuK2USwz0bmpzR0D49bzwE2/taO/FlST1 Nox495E1CR8FIq6bt6TZB2l5bsOBHsKs5GQPrKjMLSj3UNPkmiMQ5PT49jWtM/zSc48R 0KwZcqdD7ieAA34cG3Mir5hDqN5wuHjbxh9GnlRnQAVkLaH4ATyVtfMR8T0Vujnr0gBV WIl3Z+7rDJEkCCr0Dw6rTjrXX8F6gu+uHbVAZXXFosUpKm+GkUjwbS82t5a1pnsr+cez Gq9evbOR/LuV9VZKzMxvvZKW+qDpuelpOygCKcxMPQke9kO64/7uXG8VPQZV4NhHna5I yQ4Q==
MIME-Version: 1.0
X-Received: by 10.180.12.243 with SMTP id b19mr3986181wic.18.1381509439599; Fri, 11 Oct 2013 09:37:19 -0700 (PDT)
Received: by 10.180.84.38 with HTTP; Fri, 11 Oct 2013 09:37:19 -0700 (PDT)
In-Reply-To: <20131011162503.23599.qmail@joyce.lan>
References: <CAMzo+1bjzpWOVNUqzZMfgBDoZ76Zdr_CyXfhovh_pnKEE-aB-Q@mail.gmail.com> <20131011162503.23599.qmail@joyce.lan>
Date: Fri, 11 Oct 2013 11:37:19 -0500
Message-ID: <CAMzo+1YZNPirmCmgqRjxTgcdXXUfO=8ujoqwf8QCbDNYOncn0A@mail.gmail.com>
Subject: Re: "The core Internet institutions abandon the US Government"
From: Jorge Amodio <jmamodio@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a11c351ac66bcec04e879bbba
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, 11 Oct 2013 16:37:22 -0000

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

Until ICANN becomes a "member" based organization where you have real
constituents that can fire a director, the organization is only
representative of itself and its ecosystem.

-J


On Fri, Oct 11, 2013 at 11:25 AM, John Levine <johnl@taugh.com> wrote:

> >Just few quick questions,
> >
> >In what part of Fadi Chehad=E9 mandate at ICANN this falls ? And who
> >sanctified him as representative of the Internet Community ?
> >
> >He is just an employee of ICANN and these actions go way beyond ICANN's
> >mission and responsibilities.
>
> ICANN has a long running fantasy that they are a global
> multi-stakeholder organization floating above mere politics, and not a
> US government contractor incorporated as a California non-profit.
> This will never change, and everyone familiar with the situation knows
> it, but for internal political reasons ICANN likes to pretend
> otherwise.
>
> I suppose in the current political situation about the NSA there's no
> harm in the other groups going along with it for a while.
>
> R's,
> John
>

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

<div dir=3D"ltr"><br><div>Until ICANN becomes a &quot;member&quot; based or=
ganization where you have real constituents that can fire a director, the o=
rganization is only representative of itself and its ecosystem.</div><div>
<br></div><div>-J</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Fri, Oct 11, 2013 at 11:25 AM, John Levine <span dir=3D=
"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.=
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">&gt;Just few quick questio=
ns,<br>
&gt;<br>
&gt;In what part of Fadi Chehad=E9 mandate at ICANN this falls ? And who<br=
>
&gt;sanctified him as representative of the Internet Community ?<br>
&gt;<br>
&gt;He is just an employee of ICANN and these actions go way beyond ICANN&#=
39;s<br>
&gt;mission and responsibilities.<br>
<br>
</div>ICANN has a long running fantasy that they are a global<br>
multi-stakeholder organization floating above mere politics, and not a<br>
US government contractor incorporated as a California non-profit.<br>
This will never change, and everyone familiar with the situation knows<br>
it, but for internal political reasons ICANN likes to pretend<br>
otherwise.<br>
<br>
I suppose in the current political situation about the NSA there&#39;s no<b=
r>
harm in the other groups going along with it for a while.<br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br></div>

--001a11c351ac66bcec04e879bbba--

From dhc@dcrocker.net  Fri Oct 11 09:48: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 7502611E81F9 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:48: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=[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 c-dSB4doRl+m for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 09:48:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2C88221F9223 for <ietf@ietf.org>; Fri, 11 Oct 2013 09:47:46 -0700 (PDT)
Received: from [10.100.255.252] ([203.167.240.58]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9BGlfKK003437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 Oct 2013 09:47:45 -0700
Message-ID: <52582BA0.5040703@dcrocker.net>
Date: Sat, 12 Oct 2013 05:47:28 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: "The core Internet institutions abandon the US Government"
References: <20131011162503.23599.qmail@joyce.lan>
In-Reply-To: <20131011162503.23599.qmail@joyce.lan>
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]); Fri, 11 Oct 2013 09:47:45 -0700 (PDT)
Cc: 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: Fri, 11 Oct 2013 16:48:37 -0000

On 10/12/2013 5:25 AM, John Levine wrote:
> ICANN has a long running fantasy that they are a global
> multi-stakeholder organization floating above mere politics, and not a
> US government contractor incorporated as a California non-profit.


What's most interesting about your sentence is that both parts are 
phrased in a manner that mostly misses any of the interesting issues 
about ICANN, and tends to focus the reader on misperceptions and 
irrelevancies.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From fgont@si6networks.com  Fri Oct 11 10:04:24 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 A76B421E80E2; Fri, 11 Oct 2013 10:04:24 -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 CcVze5dbSgqo; Fri, 11 Oct 2013 10:04:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0183821E80F1; Fri, 11 Oct 2013 10:04:23 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.193]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VUg8O-0002s1-G2; Fri, 11 Oct 2013 19:04:17 +0200
Message-ID: <52582F8B.8040306@si6networks.com>
Date: Fri, 11 Oct 2013 14:04:11 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 17:04:24 -0000

On 10/11/2013 12:36 PM, Templin, Fred L wrote:
>> FWIW, my idea of the I-D is that it says "look, if you don't put all
>> this info into the first fragment, it's extremely likely that your
>> packets will be dropped". That doesn't mean that a middle-box may want
>> to look further. But looking further might imply
>> reassemble-inspect-and-refragment... or even reassemble the TCP stream
>> (e.g. think about a SSL/TCP-based VPN...)
> 
> We definitely don't want that. That is why we would prefer for
> the entire header chain (starting from the outermost IP header
> up to and including the headers inserted by the original host)
> to fit within the first fragment even if there are multiple
> encapsulations on the path.

The problem is that if you have multiple encapsulations, you can always
hit the MTU limit and fail to comply with this requirement.

That's why this I-D says what it says.

P.S.: Reegarding enforcing a limit on the length of the header chain, I
must say I symphatize with that (for instance, check the last individual
version of this I-D, and you'll find exactly that). But the wg didn't
want that in -- and I did raise the issue a few times. So what we have
is what the 6man wg had consensus on.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From hallam@gmail.com  Fri Oct 11 10:07:07 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 25B5821E8118 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 10:07:07 -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.018,  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 cdWIAvXvBsSx for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 10:07:05 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D1FBC21E80FA for <ietf@ietf.org>; Fri, 11 Oct 2013 10:06:52 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id x18so3760066lbi.3 for <ietf@ietf.org>; Fri, 11 Oct 2013 10:06: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=YNhUIBQmx2N35WIKhpPgzYKT1mVamLUPyx2O+qsV0g0=; b=0ryTnY3krP3Sb9Q4h+oDTBoYvMEAXv0x4YyHdKiFTEBxHqS6rgnaSa1U/0ZR2RrXcI ZXFAyCG8PW9nTavgk3CO4HBPXWIWCNisef64Ai1L5sklREIiD8tw2P9KmSNyRUd/osVt M5q/pxosQwi2ev9GgaJQdBe9CW2JZoNxrtgXUnOXq9qnwWwQiaeHrVAm/3UGWB1ABAMn BCS5irXGLT3ltBI74BB1HUTbN7Nv7LOJMS9I6XMkXYHbsIG3YTta0FajZDi8xnKyPD0K QhfmpMdoljTqjlULQZ3e/QWEsdwI4vN4tHrA+DHY5EQYkzlENLqMe2SF+jnAnxdETX3g E9Mg==
MIME-Version: 1.0
X-Received: by 10.112.64.36 with SMTP id l4mr17274516lbs.15.1381511208546; Fri, 11 Oct 2013 10:06:48 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Fri, 11 Oct 2013 10:06:48 -0700 (PDT)
In-Reply-To: <52582BA0.5040703@dcrocker.net>
References: <20131011162503.23599.qmail@joyce.lan> <52582BA0.5040703@dcrocker.net>
Date: Fri, 11 Oct 2013 13:06:48 -0400
Message-ID: <CAMm+LwhWrBABSHiNXU3_gXpuOTeyWy50xEwFz-jEBaR41pKSDQ@mail.gmail.com>
Subject: Re: "The core Internet institutions abandon the US Government"
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c3eee4d6b77604e87a241c
Cc: John Levine <johnl@taugh.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: Fri, 11 Oct 2013 17:07:07 -0000

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

On Fri, Oct 11, 2013 at 12:47 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 10/12/2013 5:25 AM, John Levine wrote:
>
>> ICANN has a long running fantasy that they are a global
>> multi-stakeholder organization floating above mere politics, and not a
>> US government contractor incorporated as a California non-profit.
>>
>
>
> What's most interesting about your sentence is that both parts are phrased
> in a manner that mostly misses any of the interesting issues about ICANN,
> and tends to focus the reader on misperceptions and irrelevancies.


You know there is absolutely nothing in the above that could not be stated
as '-1'.

If you can't give a proof point or an explanation then don't bother to say
it. John made a factual statement that is true in every important respect.
If you disagree with those fact then explain why.

When people try to slap others down in that fashion, I get annoyed.

And I get really annoyed when people talk about important issues that they
don't state. Which suggests that the writer is too important to explain
them to the lesser beings he is talking at.


The view from the establishment is that ICANN is US property and that is
both the US establishment and Russia, China, Brazil and pretty much
everywhere else.

The reason that quite a few folk don't want to move ICANN functions into
the UN instead is that nobody trusts them either. In fact the group that
would be in charge is a bit like the old human rights committee which used
to be populated with representatives of the worst abusers because they were
the ones who cared most.


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

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

<div dir=3D"ltr">On Fri, Oct 11, 2013 at 12:47 PM, Dave Crocker <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcro=
cker.net</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 10/12/2013 5:25 AM, Joh=
n Levine wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
ICANN has a long running fantasy that they are a global<br>
multi-stakeholder organization floating above mere politics, and not a<br>
US government contractor incorporated as a California non-profit.<br>
</blockquote>
<br>
<br></div>
What&#39;s most interesting about your sentence is that both parts are phra=
sed in a manner that mostly misses any of the interesting issues about ICAN=
N, and tends to focus the reader on misperceptions and irrelevancies.</bloc=
kquote>
<div><br></div><div>You know there is absolutely nothing in the above that =
could not be stated as &#39;-1&#39;.</div><div><br></div><div>If you can&#3=
9;t give a proof point or an explanation then don&#39;t bother to say it. J=
ohn made a factual statement that is true in every important respect. If yo=
u disagree with those fact then explain why.</div>
<div>=A0</div></div><div>When people try to slap others down in that fashio=
n, I get annoyed.=A0</div><div><br></div><div>And I get really annoyed when=
 people talk about important issues that they don&#39;t state. Which sugges=
ts that the writer is too important to explain them to the lesser beings he=
 is talking at.</div>
<div><br></div><div><br></div><div>The view from the establishment is that =
ICANN is US property and that is both the US establishment and Russia, Chin=
a, Brazil and pretty much everywhere else.</div><div><br></div><div>The rea=
son that quite a few folk don&#39;t want to move ICANN functions into the U=
N instead is that nobody trusts them either. In fact the group that would b=
e in charge is a bit like the old human rights committee which used to be p=
opulated with representatives of the worst abusers because they were the on=
es who cared most.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c3eee4d6b77604e87a241c--

From rdroms.ietf@gmail.com  Fri Oct 11 10:09:36 2013
Return-Path: <rdroms.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 3B97D21E80E9; Fri, 11 Oct 2013 10:09: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 znMu2jV1l7H3; Fri, 11 Oct 2013 10:09:35 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA5B21E8063; Fri, 11 Oct 2013 10:09:35 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n4so3245892qcx.13 for <multiple recipients>; Fri, 11 Oct 2013 10:09: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; bh=GSwF6PDFlaM7QEWzCmdd3b8F04nblBjhhCsRrRa1C6c=; b=uwH1VE3EqFhD5zqnEh9XW1OlukURDcAQp3cjQIVL7AWkfgqSdntWjTvDyUf8yD+A0d 97GiwN+bwufA/tHhcMW92wRV1TnO9549pEjIXPtiv/9ZKG9AEVbFpsgYHH7rPl18vHv6 kdy9McTp0LfZjxeIJkST+005KvsdG+gaIsTnj+piofzYOHsDmSYjTw4diVkqU9fm6bTL 7tlqy0O3DDNCIMmRS1YmGtAMlLUBpTfDqD7AZQ5RKkXO5QJgcpjbL0JbMhzEK8eGguLb QVmFrIobidfeRA9M4b/3l24lo4BhyCYqqM8Lt4b5vLYPIDySfBSNFJUFxRwo8/acM51s JhZg==
X-Received: by 10.49.81.237 with SMTP id d13mr9066694qey.44.1381511371579; Fri, 11 Oct 2013 10:09:31 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:90c2:cb2c:7e7a:2470? ([2001:420:2481:20:90c2:cb2c:7e7a:2470]) by mx.google.com with ESMTPSA id g2sm112348856qaf.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 10:09:28 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <20131010221713.891.32620.idtracker@ietfa.amsl.com>
Date: Fri, 11 Oct 2013 13:09:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B594A37B-51F9-44FD-9E45-56D273657E89@gmail.com>
References: <20131010221713.891.32620.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: roll@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Oct 2013 17:09:36 -0000

draft-ietf-roll-trickle-mcast-05 and draft-ietf-6man-multicast-scopes-00 =
are in conflict with each other.

=46rom draft-ietf-roll-trickle-mcast-05:

   When
   used with MPL, Realm-Local scope is administratively defined and used
   to define the boundaries of multicast message dissemination by MPL.

=46rom draft-ietf-6man-multicast-scopes-00:

   Realm-Local scope is the largest scope that is automatically
   configured, i.e., automatically derived from physical
   connectivity or other, non-multicast-related configuration.

Specifically, "administratively defined" seems to me to be in direct
conflict with "automatically configured".=20

I suggest fixing the problem with two updates.  First, the definition
of "scop 3" in an IP-over-IEEE802.15.4 needs to be published, based on
this text from draft-ietf-6man-multicast-scopes-00:=20

   The definition of any Realm-Local scope for a particular network
   technology should be published in an RFC.

I suggest:

   When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined
   to include all interfaces sharing a PAN ID.

This text could be added to draft-ietf-roll-trickle-mcast-05, or to
draft-ietf-6man-multicast-scopes-00 or published separately in yet
another "world's shortest RFC".

Second, draft-ietf-roll-trickle-mcast-05 should be changed to read:

   When used with MPL, Realm-local scope is defined according to the
   underlying network technology; for example, [cite the
   IP-over-IEEE802.15.4 definition].

As a further refinement, I suggest text be added to
draft-ietf-roll-trickle-mcast-05 to the effect of:

   "scop 4" can also be used with MPL to cover deployments that use
   administratively defined scopes that cover, for example, subnets
   based on different underlying network technologies.

- Ralph

PS I originally posted about this issue to the rool WG mailing list:
http://www.ietf.org/mail-archive/web/roll/current/msg08188.html.
After a discussion with Kerry Lynn, I made a change to the definition
of scop 3 for IEEE802.15.4.=

From Ted.Lemon@nominum.com  Fri Oct 11 10:11:52 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 B4B6A11E8143 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 10:11:52 -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 od-4HQKNT4Za for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 10:11:46 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 37B4211E8142 for <ietf@ietf.org>; Fri, 11 Oct 2013 10:11:46 -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 DSNKUlgxUTSbyxjcCwru+Yy1dKm1sJ+A25wf@postini.com; Fri, 11 Oct 2013 10:11: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 B509F1B82E8 for <ietf@ietf.org>; Fri, 11 Oct 2013 10:11:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 AF17119005C; Fri, 11 Oct 2013 10:11:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 11 Oct 2013 10:11:45 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Last calling draft-resnick-on-consensus
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <3B17EA9B-42B3-4C09-9D34-C4ABFB8A4B77@sobco.com>
Date: Fri, 11 Oct 2013 13:11:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <2B0CBE7C-B279-4D2D-877A-14869A406B0E@nominum.com>
References: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.gmail.com> <3B17EA9B-42B3-4C09-9D34-C4ABFB8A4B77@sobco.com>
To: Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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: Fri, 11 Oct 2013 17:11:52 -0000

On Oct 11, 2013, at 8:15 AM, Scott O Bradner <sob@sobco.com> wrote:
> The process in the ID is not what was followed when I was an AD and it =
not what I have described by the meaning of the term "rough consensus" =
in my newcomers tutorials (which I have been giving since at least IETF =
57 in 2003).=20

Perhaps I should be embarrassed to ask this question, but how _do_ you =
describe the meaning of the term "rough consensus?"


From Fred.L.Templin@boeing.com  Fri Oct 11 10:35:55 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B93821E80ED; Fri, 11 Oct 2013 10:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.437
X-Spam-Level: 
X-Spam-Status: No, score=-6.437 tagged_above=-999 required=5 tests=[AWL=0.162,  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 R7zckJrfdfcg; Fri, 11 Oct 2013 10:35:49 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id CC82221E8090; Fri, 11 Oct 2013 10:35:49 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BHZmfE005894; Fri, 11 Oct 2013 10:35:49 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BHZkm7005378 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:35:48 -0700
Received: from XCH-BLV-308.nw.nos.boeing.com (130.247.25.220) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 10:35:47 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-308.nw.nos.boeing.com ([169.254.8.40]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 10:35:46 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxqMeebc9KTehbEGO6mhunuAlj5nvvDEg
Date: Fri, 11 Oct 2013 17:35:46 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C36A@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com> <52582E39.6030109@globis.net>
In-Reply-To: <52582E39.6030109@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 17:35:55 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Friday, October 11, 2013 9:59 AM
> To: Templin, Fred L
> Cc: brian.e.carpenter@gmail.com; ietf@ietf.org; 6man Mailing List
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 11 October 2013 17:33
> > Hi Ray,
> >
> >> -----Original Message-----
> >> From: Ray Hunter [mailto:v6ops@globis.net]
> >> Sent: Friday, October 11, 2013 12:49 AM
> >> To: Templin, Fred L; brian.e.carpenter@gmail.com
> >> Cc: ietf@ietf.org; 6man Mailing List
> >> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
> >> Standard
> >>
> >> Templin, Fred L wrote:
> >>> Hi Brian,
> >>>
> >>> Responding in a slightly re-arranged order:
> >>>
> >>>> The problem is that you are asserting that middleboxes that a
> tunnel
> >>>> passes through are expected to examine the complete header chain
> of
> >>>> the encapsulated packet even if the encapsulated packet is a
> >> fragment.
> >>> Yes, but change "are expected to" to "should be able to".
> >> I personally don't see this going anywhere.
> >>
> >> Unless you specifically define what is a "tunnel" and you
> specifically
> >> define a maximum depth of nesting.
> >>
> >> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
> >> since the value of the "IPv6 next header" is taken from the same
> code
> >> space as the ULP header values, and there's no specific marker or
> >> "header length" field in IPv6 that explicitly marks a point as "This
> is
> >> the end of the IPv6 header chain in all circumstances: stop header
> >> parsing here."
> >>
> >> Ok, there's a bunch of current code-points that are today considered
> as
> >> valid ULP's or next-header values, but that is neither time
> invariant
> >> nor exhaustive, so solving this issue via a registry means there
> will
> >> always be middlebox code in the wild that lags any updates.
> >>
> >> These middleboxes won't be able to differentiate between an unknown
> >> ULP,
> >> and an unknown IPv6 next-header. That potentially makes a default
> pass
> >> or drop decision awkward.
> >>
> >> If it's so important to be able to differentiate between what is an
> ULP
> >> and what is a next header, and we can't reliably do that today,
> maybe
> >> that's a fundamental flaw in IPv6 that should be addressed.
> >>
> >>
> >>>> I think that's an unreasonable expectation. A reasonable
> expectation
> >>>> is that middleboxes should identify the encapsulated packet as
> >>>> a payload that they cannot analyse, and let it go (unless they
> >>>> have a policy setting to drop tunnelled packets, which is a
> >>>> different discussion).
> >>> But why? If headers beyond the first IPv6 encapsulation header are
> >>> available in the clear, the middlebox should be able to parse them
> >>> if it wants to. Wireshark already does exactly that - it keeps on
> >>> parsing beyond the first encapsulation header up to and including
> >>> the true ULP header. And, if Wireshark can do it, so can any other
> >>> middlebox that believes security would be improved by continuing
> >>> to parse the entire chain - whether or not there is a standard
> >>> saying it must not do so.
> >> Because it leaves open the possibility for an attacker to apply the
> >> obfuscation we seek to limit.
> >>
> >>
> >>> Parsing the additional headers beyond the first encapsulation
> header
> >>> provides defense-in-depth. Perimeter middleboxes can then weed out
> >>> the bad stuff without either allowing the bad stuff to penetrate
> more
> >>> deeply into the organization or dropping good stuff that should be
> >>> allowed through.
> >> There's also a myriad of tunneling technology out there.
> >>
> >> Again, what is an ULP? Where do you stop parsing?
> >
> > The middlebox stops parsing when it decides it has seen enough.
>=20
> Which AFAIK is undefined in practical terms. Especially in the presence
> of jumbo payload extension headers or fragments.

Middleboxes should be able to parse as far as they want to
without hitting a hard stop as is the case if the header
chain extends into multiple packets.

> So are you saying the current draft has no value?

I am saying that it is unfriendly to tunnels that fragment, and a
simple fix is for the host to limit its header chain length to
1024 bytes.

> >  With
> > Wireshark at least, it blasts right through encapsulating IP headers
> > and continues up to and including the ultimate TCP/UDP/ICMP etc.
> > header inserted by the original host.
>=20
> I like wireshark.
>=20
> But how would that parsing model work in a live network without
> maintaining state between frames (and leaving your middlebox open to
> DoS
> or other resource depletion abuse)?

I don't understand the "maintaining state between frames". I am
talking about examining individual header chains within a single
packet independently of any other packets.

We may not yet know how smart middleboxes may become in this
regards. But, they will certainly never become smart enough if
they don't have the entire header chain in the first fragment.=20

> IMHO "ultimate TCP/UDP/ICMP etc." is not defined. The IETF does not
> define standard protocol stacks as a totality. HTTP over TCP over IPv6
> over L2TP over GRE over PPTP VPN over IPv6 over IPv6 is not illegal. So
> this would seem to require far tighter specs on packet formats than the
> IETF would ever publish (and rightly so).

Not at all. This is about allowing middleboxes to parse through all
of the headers included by the host and any tunnel endpoints that
may have interposed themselves between the host and the middlebox.
How the middlebox parses is its own business.
=20
> >  The goal is to give the
> > middlebox enough information so that it can parse as deeply into
> > the headers as it wants to.
>=20
> If that is the goal then we probably need to deprecate IPv6
> fragmentation as well as a whole bunch of tunnel / encryption protocols
> IMHO, and specify that the entire packet has to fit in a single frame.
> Which I feel is unrealistic.

Not at all. The proposal is to ask the host to limit its header
chain to 1024 bytes to allow for up to 256 bytes of encapsulation
headers before the header chain would be susceptible to
fragmentation.

> >> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
> >> Is SSH an ULP or a tunnel? (port tunneling)
> >> Is Teredo a tunnel or is it an ULP (UDP) or both?
> >> GRE/ LT2P over HTTP anyone?
> >>
> >> The notion of "perimeter" is moveable in the presence of such
> tunnels.
> >
> > We will want for middleboxes at outer perimeters to be able to parse
> > as many headers as they want to before releasing the packet to
> > middleboxes at inner perimenters. Otherwise, bad stuff can get past
> > the outermost perimeters and waste bandwidth and/or cause havoc
> > within the protected zone.
>=20
> Right. But if your firewall (which now has to maintain state, or which
> is forced to parse right to the end of a packet) itself becomes the
> bottleneck and the DoS target, what have you gained?

No inter-packet state - I never said or implied that. And, no one
is *forcing* the middlebox to do anything. This is about *allowing*
the middlebox to do whatever it wants.
=20
> >> Presumably there comes a point where the tunnel is terminated and
> the
> >> transported packet is de-encapsulated, and that IMHO forms another
> >> perimeter where you'd anyway have to apply further security checks.
> >
> > Nested tunnels give you perimeters within perimeters, yes. But, we
> > will want the outer perimeters to be able to parse as deeply as
> > they want to before passing on to an inner perimeter.
>=20
> I think my customers will have to start thinking in terms of an onion
> skin model, rather than a single outer perimeter and a single "trusted"
> zone.
> Maintaining state, or full-packet-depth parsing, at the point where the
> enterprise hits the Internet is probably not going to fly.

Onion skin, yes, with each layer of the onion doing what it can
to enhance security. That is what I mean by defense in depth.

> >> I think the draft does what it can in a pragmatic manner, but might
> >> benefit from some acknowledgement that this security approach of
> >> applying parsing at a single perimeter can never ever catch all
> >> variants
> >> of transporting FOO over BAR.
> >>
> >> IMHO It's only at the moment of de-encapsulation that the full
> >> semantics
> >> of the payload are revealed in these modern times of "everything
> >> transported over HTTP".
> >>
> >>
> >>
> >>
> >>>> Since the problem recurses as we tunnel tunnels, I don't see how
> any
> >>>> finite limit can solve the problem. 1280 itself is a pragmatic
> >> choice
> >>>> of "a bit shorter than 1500".
> >> Agreed.
> >
> > I guess I will have to repeat myself from what I said several
> > months ago. The 1280 came from a desire to have multiple nested
> > tunnels without requiring the tunnels to fragment since the
> > underlying links presumably all configure a 1500 MTU. But, what
> > would that look like in real life?
> >
> > - The first tunnel would have to configure a 1280 MTU so that its
> >   encapsulated packets emerged as 1320
> > - the second tunnel would have to configure a 1320 MTU so that its
> >   encapsulated  packets emerged as 1360
> > - the third tunnel would have to configure a 1360 MTU so that its
> >   encapsulated packets emerged as 1400
> > - etc.
> >
> > But, in real life, it is not possible to assume that we can lay
> > hands on all tunnel endpoints so as to carefully set MTUs that
> > satisfy the nesting level - and, when multiple administrative
> > domains are involved, it can't be done at all.
> >
> > Please go back in the archives to where I posted the derivation
> > of the 1280 minMTU (circa 1997):
> >
> > http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html
> >
> > My conclusion is that the 1280/1500 was well intentioned, but
> > unfortunately not very well thought out.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
>=20
> It doesn't matter what number you pick, and 1280 is probably as good as
> it gets. The point from Brian (if I understood it correctly) was that
> any fixed number can never be sufficient, as there's no dedicated
> portion of the IPv6 MTU specifically assigned to tunneling, and no
> defined max tunnel nesting depth.

A fixed number does not limit the number of tunnel nestings, but
it does limit how many nestings can be applied before the header
chain might wrap into a second fragment. But, how many nestings
do you want? If you want up to 6 or so, then the 1024 gives adequate
space. If you want something like 10 or more, then the extension
header chain could theoretically wrap into second fragments.

Remember that the 1280/1500 was to "allow extra room" for tunnels
to add encapsulation headers without causing fragmentation. That
goal also had a fixed upper bound of 220 bytes of room so the
number of nested tunnels was limited by that action as well
(even assuming you could get the tunnel endpoints to cooperate
and make efficient use of the 220). For better or worse, 1280
gave us a fixed number that we will be stuck with forever.

Thanks - Fred
fred.l.templin@boeing.com

> >>> The 1280 is assuming that all links in the path have a 1500 MTU and
> >>> so RFC2460 allowed (1500 - 1280) =3D 220 bytes for additional IPv6
> >>> headers added by nested tunnels without incurring fragmentation.
> >>> I am asserting instead that we have to allow for paths that include
> >>> links with a 1280 MTU and so tunnels will have to fragment over
> >>> such paths.
> >>>
> >>> That means that the first fragmenting tunnel would have room for
> >>> 1240 in the first fragment, the second fragmenting tunnel would
> >>> have room for 1200 in the first fragment, etc. That is why I would
> >>> prefer that hosts limit the size of their header chains to 1024; so
> >>> that nested tunnels that fragment will still be highly likely to
> >>> have the entire header chain in the first fragment.
> >>>
> >>>> I understood that to be the basis on which the WG reached
> consensus.
> >>> Maybe the WG didn't understand that such a consensus would make
> >>> tunnels less reliable and less secure.
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>>     Brian
> >> --
> >> Regards,
> >> RayH
> >
> > ---------------------------------------------------------------------
> ---
>=20
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Fri Oct 11 10:51:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D232E21E81A5; Fri, 11 Oct 2013 10:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level: 
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.151,  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 oQUH2E8MAcPX; Fri, 11 Oct 2013 10:51:33 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 6C89E21E81E9; Fri, 11 Oct 2013 10:51:21 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BHpIJO020921; Fri, 11 Oct 2013 10:51:19 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BHpHxC020869 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 10:51:18 -0700
Received: from XCH-BLV-306.nw.nos.boeing.com (130.247.25.218) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 10:51:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.22]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 10:51:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ray Hunter <v6ops@globis.net>, "brian.e.carpenter@gmail.com" <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxqPnebc9KTehbEGO6mhunuAlj5nvxCJQ
Date: Fri, 11 Oct 2013 17:51:12 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C3B9@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>
In-Reply-To: <52582F8B.8040306@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 17:51:41 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, October 11, 2013 10:04 AM
> To: Templin, Fred L; Ray Hunter; brian.e.carpenter@gmail.com
> Cc: 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/11/2013 12:36 PM, Templin, Fred L wrote:
> >> FWIW, my idea of the I-D is that it says "look, if you don't put all
> >> this info into the first fragment, it's extremely likely that your
> >> packets will be dropped". That doesn't mean that a middle-box may
> want
> >> to look further. But looking further might imply
> >> reassemble-inspect-and-refragment... or even reassemble the TCP
> stream
> >> (e.g. think about a SSL/TCP-based VPN...)
> >
> > We definitely don't want that. That is why we would prefer for
> > the entire header chain (starting from the outermost IP header
> > up to and including the headers inserted by the original host)
> > to fit within the first fragment even if there are multiple
> > encapsulations on the path.
>=20
> The problem is that if you have multiple encapsulations, you can always
> hit the MTU limit and fail to comply with this requirement.

Yes you can, which is what I just said to Ray. But, I am not talking
about a *requirement* - I am talking about a best practice that works
in most cases.

The question is how many layers of encapsulation do you need? Let's
say you want 5 layers of encapsulation. That would still allow enough
room for all of the hosts headers to fit in the first fragment if the
host limits its header chain to 1024 bytes. But, now let's say that
you want 10 layers of encapsulation. That means that the first 5
middleboxes that examine the outermost encapsulations will not be
able to see the entire header chain, but the last 5 middleboxes that
examine the innermost encapsulations will. So, there is a limit to
the levels of defense-in-depth. But, that limit is greater than 1.

Remember also that the 1280/1500 also assumed that there would be
"just a few" layers of nested encapsulations. What I am suggesting
allows for endless recursion but limited (and reasonable) defense
in depth.=20
=20
> That's why this I-D says what it says.

I'm not sure this discussion was taken into account, and what the
draft says now is not friendly to tunnels.

> P.S.: Reegarding enforcing a limit on the length of the header chain, I
> must say I symphatize with that (for instance, check the last
> individual
> version of this I-D, and you'll find exactly that). But the wg didn't
> want that in -- and I did raise the issue a few times. So what we have
> is what the 6man wg had consensus on.

It is not too late to get this right, and to give reasonable
treatment to tunnels that the current draft does not give.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks!
>=20
> Cheers,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20


From adrian@olddog.co.uk  Fri Oct 11 12:04:12 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 67D8421F853A for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045,  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 W3ydrf6HsuuH for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:04:06 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 52A7D21E808E for <ietf@ietf.org>; Fri, 11 Oct 2013 12:04:04 -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 r9BJ435U024160;  Fri, 11 Oct 2013 20:04:03 +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 r9BJ42SI024151 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Oct 2013 20:04:03 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Subject: RE: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
Date: Fri, 11 Oct 2013 20:04:01 +0100
Message-ID: <04bd01cec6b4$a5e5d940$f1b18bc0$@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: Ac7Gs/m0O0z7wOjUSFWNTS230IDz2w==
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: Fri, 11 Oct 2013 19:04:12 -0000

Hi Pete,

At this point, a working week through the four week last call, I am wondering
whether the volume of comments and changes merit waiting for a revised version
before I do a last call review, or whether I should dive in with the current
version and risk raising a number of points already covered by others.

What do you think?

Thanks,
Adrian


From presnick@qti.qualcomm.com  Fri Oct 11 12:26:13 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 4BACA11E8155 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.67
X-Spam-Level: 
X-Spam-Status: No, score=-106.67 tagged_above=-999 required=5 tests=[AWL=-0.071, 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 LArwzqZMSQDb for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:26:09 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 6B61911E817F for <ietf@ietf.org>; Fri, 11 Oct 2013 12:26:02 -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=1381519562; x=1413055562; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=4LtCZwlYn+smQOILcGJ+Kx9xp42uXxaA/g3/aHr18xk=; b=G4xlXQDmhOFwrfF13ke0shTDFivB7PgR6BbWUm1f3J4TOtU7RQ82VBc2 a76mvI3rU2FHThTYvgxeaMvO6J6buipz2C5URPAEfCmZ2nbkO7mzmi22N G7onkjvWG6ym0ZkjhS8P+Pa4LFgrHvHesKOrNJQ54wLo0yWDGAsP3DxiX 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,7225"; a="80396490"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 11 Oct 2013 12:25:55 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7225"; a="567490556"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 11 Oct 2013 12:25:55 -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.3.158.1; Fri, 11 Oct 2013 12:25:54 -0700
Message-ID: <525850C1.7070600@qti.qualcomm.com>
Date: Fri, 11 Oct 2013 14:25: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: <adrian@olddog.co.uk>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and	Humming in the IETF) to Informational RFC
References: <04bd01cec6b4$a5e5d940$f1b18bc0$@olddog.co.uk>
In-Reply-To: <04bd01cec6b4$a5e5d940$f1b18bc0$@olddog.co.uk>
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: Fri, 11 Oct 2013 19:26:13 -0000

On 10/11/13 2:04 PM, Adrian Farrel wrote:
> At this point, a working week through the four week last call, I am wondering
> whether the volume of comments and changes merit waiting for a revised version
> before I do a last call review, or whether I should dive in with the current
> version and risk raising a number of points already covered by others.
>
> What do you think?
>    

Half of one, six dozen of the other. :-)

There's no doubt in my mind that there will be a revision coming to 
address a bunch of comments, and you'll notice that I haven't even 
started to tackle the comments in the thread that Ted started. (That's 
in my edit buffer and is next on my list.) I certainly wouldn't mind 
hearing comments that haven't been brought up yet, or hearing 
disagreements with comments already made, but I certainly wouldn't be 
distressed if you waited for the next go-round either.

My sense is that the revision is going to have a lot of little changes 
(sorting the "actual history" from the "what's new" is going to require 
a bunch of smallish edits), and I need to adjust some of the framing of 
some of the bigger points, but I don't see drastic thematic changes 
coming. (Obviously I've got some 'xplaining to do on some of the themes, 
and it's always possible that Ted convinces me that I'm completely 
wrongheaded on one or more of them, but that's my current assessment.) 
I've got a bunch of airplane time in the next 4 days, so I might even 
get this out by sometime next week.

And remember, the Last Call ends during Vancouver, so there's certainly 
going to be longer than average time at the end to deal with comments.

Does that help you decide?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From brian.e.carpenter@gmail.com  Fri Oct 11 12:29:16 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 7F63A21F86BE for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 QkpFLJ1kitTU for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 12:29:16 -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 0BE1821E80FA for <ietf@ietf.org>; Fri, 11 Oct 2013 12:29:08 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so4700173pdi.13 for <ietf@ietf.org>; Fri, 11 Oct 2013 12:29:07 -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=8rYkTo90NI7gDwYAlzvAQozqKmrdZ/aJz+xKwW/UR+A=; b=Q5hL/YnWaPwJLy8jK6L43+gA/3q7CZZbM80SXytVty7UfvCfq5FfPD5P0g+l/j7sIW FIgkg8bbyAiRBqWRXzU+U/Qn6cg9CO0bcv2/waD5oudpxC2SMLpAw33XiKpBWxhIch2O dWS4Hc/BrMAED/bAXDgyaZ+mQCFQ4qgQPGQ93+HhJ3dL+X3p/JTJBK0OWCllZdfhc/GH 2p+cWLQCCkWxSugHc7A3w68e1wF3FZuZdKPxhIqqgh76sG55BqMgRhRVvi0iVrpa2CLX 3oQ2BhQ7CJaG53GdZanxRhm/CnLTPrpII0KXmrhVIfbM6atB1rB934pvSKtSovSfdHKI HVnw==
X-Received: by 10.68.232.3 with SMTP id tk3mr21730440pbc.121.1381519747694; Fri, 11 Oct 2013 12:29:07 -0700 (PDT)
Received: from [192.168.178.20] (164.195.69.111.dynamic.snap.net.nz. [111.69.195.164]) by mx.google.com with ESMTPSA id qw8sm61572150pbb.27.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 12:29:06 -0700 (PDT)
Message-ID: <52585188.6020408@gmail.com>
Date: Sat, 12 Oct 2013 08:29:12 +1300
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 Curran <jcurran@istaff.org>
Subject: Re: Of governments and representation (was: Montevideo Statement)
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
In-Reply-To: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 11 Oct 2013 19:29:16 -0000

Hi John,

On 12/10/2013 05:02, John Curran wrote:
...
> In my personal view, it is a very important for the IETF to select leadership who can
> participate in any discussions that occur,

Without obsessing about the word "leadership", but following up on a comment
made by Noel Chiappa on the "leader statements" thread, I think we have
to recognise that nothing in the NomCom process, the IAB Charter, or
the IESG Charter, would cause us to select IAB or IETF Chairs who are
particularly suited to this role.

In fact I think that the plan of record is to leave such matters to
ISOC.

Reality is different - the outside world expects to hear from us.

     Brian

From brian.e.carpenter@gmail.com  Fri Oct 11 12:49:43 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 05EC111E8155; Fri, 11 Oct 2013 12:49:43 -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 AMhE8My0nHFQ; Fri, 11 Oct 2013 12:49:42 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3235511E8185; Fri, 11 Oct 2013 12:49:37 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id q10so4729449pdj.34 for <multiple recipients>; Fri, 11 Oct 2013 12:49: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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=URymMGHE3n5kLFeBo5RXtIiIee/MtyM5fngcgsTMzuA=; b=TiTXVs2R7CoCdbwFih5Qo7VGp1cEqf763ZmcrBY4zC9+ssX2ZM6mi4mjEHcfiu470r o+PpN/8S3xjV2DPkgJjlOd8mcAsKkRbq2/qblgGvrgS1Ej+QtKhjl4e3ZoLbq3qfaVXG +8NZSLujS5lMr7A4b9WdwInoezdvS4vsNl3DfSZU9R3CljDd5hJHWzKjZ8AGmYDs1kSc 5hifaLRI2wg95nKC/r3vPp2fimFMMwIfxePLaMP4b4UeUfA5NX6TTmRARezqbCNKoajd +6LDMERx9WOOHycQvds8w0jtrgl7zcjbXeKE8Bu4iOOUZ1CQzgyvjv++y4ueJIN+qIP9 ANkQ==
X-Received: by 10.66.216.129 with SMTP id oq1mr23875322pac.75.1381520976796; Fri, 11 Oct 2013 12:49:36 -0700 (PDT)
Received: from [192.168.178.20] (164.195.69.111.dynamic.snap.net.nz. [111.69.195.164]) by mx.google.com with ESMTPSA id va8sm61654062pbc.16.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 12:49:35 -0700 (PDT)
Message-ID: <52585658.50205@gmail.com>
Date: Sat, 12 Oct 2013 08:49:44 +1300
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: Fernando Gont <fgont@si6networks.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>
In-Reply-To: <52582F8B.8040306@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 19:49:43 -0000

On 12/10/2013 06:04, Fernando Gont wrote:
...
> P.S.: Reegarding enforcing a limit on the length of the header chain, I
> must say I symphatize with that (for instance, check the last individual
> version of this I-D, and you'll find exactly that). But the wg didn't
> want that in -- and I did raise the issue a few times. So what we have
> is what the 6man wg had consensus on.

I agree that this was the WG consensus after considerable discussion,
which included Fred, so I'm not sure why we're discussing it again
during IETF LC.

   Brian

From Fred.L.Templin@boeing.com  Fri Oct 11 12:57:37 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664B421E808E; Fri, 11 Oct 2013 12:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.458
X-Spam-Level: 
X-Spam-Status: No, score=-6.458 tagged_above=-999 required=5 tests=[AWL=0.141,  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 NzpIQM1PU3SN; Fri, 11 Oct 2013 12:57:26 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id A43FB11E818F; Fri, 11 Oct 2013 12:56:55 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9BJupbI025335; Fri, 11 Oct 2013 14:56:52 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9BJuOel024378 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 11 Oct 2013 14:56:51 -0500
Received: from XCH-BLV-202.nw.nos.boeing.com (10.57.37.69) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Fri, 11 Oct 2013 12:56:46 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-202.nw.nos.boeing.com ([169.254.2.10]) with mapi id 14.03.0158.001; Fri, 11 Oct 2013 12:56:45 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxrsIebc9KTehbEGO6mhunuAlj5nv6Nlw
Date: Fri, 11 Oct 2013 19:56:44 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com>
In-Reply-To: <52585658.50205@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 19:57:38 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAxMjo1MCBQTQ0KPiBUbzogRmVybmFuZG8gR29udA0K
PiBDYzogVGVtcGxpbiwgRnJlZCBMOyBSYXkgSHVudGVyOyA2bWFuIE1haWxpbmcgTGlzdDsgaWV0
ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi02bWFuLW92
ZXJzaXplZC1oZWFkZXItY2hhaW4tMDgudHh0Pg0KPiAoSW1wbGljYXRpb25zIG9mIE92ZXJzaXpl
ZCBJUHY2IEhlYWRlciBDaGFpbnMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBPbiAxMi8x
MC8yMDEzIDA2OjA0LCBGZXJuYW5kbyBHb250IHdyb3RlOg0KPiAuLi4NCj4gPiBQLlMuOiBSZWVn
YXJkaW5nIGVuZm9yY2luZyBhIGxpbWl0IG9uIHRoZSBsZW5ndGggb2YgdGhlIGhlYWRlciBjaGFp
biwNCj4gSQ0KPiA+IG11c3Qgc2F5IEkgc3ltcGhhdGl6ZSB3aXRoIHRoYXQgKGZvciBpbnN0YW5j
ZSwgY2hlY2sgdGhlIGxhc3QNCj4gaW5kaXZpZHVhbA0KPiA+IHZlcnNpb24gb2YgdGhpcyBJLUQs
IGFuZCB5b3UnbGwgZmluZCBleGFjdGx5IHRoYXQpLiBCdXQgdGhlIHdnIGRpZG4ndA0KPiA+IHdh
bnQgdGhhdCBpbiAtLSBhbmQgSSBkaWQgcmFpc2UgdGhlIGlzc3VlIGEgZmV3IHRpbWVzLiBTbyB3
aGF0IHdlDQo+IGhhdmUNCj4gPiBpcyB3aGF0IHRoZSA2bWFuIHdnIGhhZCBjb25zZW5zdXMgb24u
DQo+IA0KPiBJIGFncmVlIHRoYXQgdGhpcyB3YXMgdGhlIFdHIGNvbnNlbnN1cyBhZnRlciBjb25z
aWRlcmFibGUgZGlzY3Vzc2lvbiwNCj4gd2hpY2ggaW5jbHVkZWQgRnJlZCwgc28gSSdtIG5vdCBz
dXJlIHdoeSB3ZSdyZSBkaXNjdXNzaW5nIGl0IGFnYWluDQo+IGR1cmluZyBJRVRGIExDLg0KDQpU
ZWNobmljYWwgbWF0dGVycyBzaG91bGQgYmUgZGlzY3Vzc2VkIGFzIHRoZXkgY29tZSB0byBsaWdo
dDsgbm90DQpkaXNtaXNzZWQgYmVjYXVzZSBvZiBzb21lIHJlYWwgb3IgcGVyY2VpdmVkIGRlYWRs
aW5lLiBUaGF0IHdhcyB3aGF0DQpnb3QgdXMgdGhlIDEyODAgTVRVIGluIHRoZSBmaXJzdCBwbGFj
ZS4gUXVvdGluZyBmcm9tIFN0ZXZlIERlZXJpbmc6DQoNCiAgIiBXZSB3b3VsZCBsaWtlIHRvIGdl
dCB0aGlzIGlzc3VlIHNldHRsZWQgYXMNCiAgICBzb29uIGFzIHBvc3NpYmxlLCBzaW5jZSB0aGlz
IGlzIHRoZSBvbmx5IHRoaW5nIGhvbGRpbmcgdXAgdGhlIHB1YmxpY2F0aW9uDQogICAgb2YgdGhl
IHVwZGF0ZWQgUHJvcG9zZWQgU3RhbmRhcmQgSVB2NiBzcGVjICh0aGUgdmVyc2lvbiB3ZSBleHBl
Y3QgdG8gYWR2YW5jZQ0KICAgIHRvIERyYWZ0IFN0YW5kYXJkKSwgc28gbGV0J3Mgc2VlIGlmIHdl
IGNhbiBjb21lIHRvIGEgZGVjaXNpb24gYmVmb3JlIHRoZSBJRA0KICAgIGRlYWRsaW5lIGF0IHRo
ZSBlbmQgb2YgbmV4dCB3ZWVrIChob3BpbmcgdGhlcmUgaXNuJ3QgYW55IGNvbmZsaWN0IGJldHdl
ZW4NCiAgICAidGhvdWdodGZ1bCBhbmFseXNpcyIgYW5kICJsZXQncyBkZWNpZGUgcXVpY2tseSIg
Oi0pLiINCg0KU28sIGl0IHdhc24ndCBuZWNlc3NhcmlseSB0aGUgY2FzZSB0aGF0IDEyODAgd2Fz
IGEgcHJvZHVjdCBvZiAidGhvdWdodGZ1bA0KYW5hbHlzaXMiIHNvIG11Y2ggYXMgdGhlIGZhY3Qg
dGhhdCAqKnRoZXkgd2VyZSBydXNoaW5nIHRvIGdldCBhIHNwZWMgb3V0DQp0aGUgZG9vcioqLiBT
byBub3csIDE2IHllYXJzIGxhdGVyLCB3ZSBnZXQgdG8gcHV0IGl0IGJhY2sgb24gdGhlIDZtYW4N
CmNoYXJ0ZXIgbWlsZXN0b25lIGxpc3QuDQoNCg0KVGhhbmtzIC0gRnJlZA0KZnJlZC5sLnRlbXBs
aW5AYm9laW5nLmNvbQ0K

From jcurran@istaff.org  Fri Oct 11 13:19:05 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 9F17221F9C6B for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 13:19:05 -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 umzoRA89NkR5 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 13:19:00 -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 1A41121F9E1A for <ietf@ietf.org>; Fri, 11 Oct 2013 13:18:57 -0700 (PDT)
Received: from dhcp-220-43.meetings.nanog.org ([199.187.220.43]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1VUjAl-000GoF-FC; Fri, 11 Oct 2013 20:18:55 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 199.187.220.43
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/9RUmP4BRflrfgfq3Hmi1s
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Of governments and representation (was: Montevideo Statement)
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAMzo+1Yo-z1YH698kPctRoaWauaFirCjw0b=HA2dyf5WGEVa_w@mail.gmail.com>
Date: Fri, 11 Oct 2013 13:18:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <130D5133-01F5-49C6-92F7-5F706E7B8340@istaff.org>
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <CAMzo+1Yo-z1YH698kPctRoaWauaFirCjw0b=HA2dyf5WGEVa_w@mail.gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>
X-Mailer: Apple Mail (2.1510)
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: Fri, 11 Oct 2013 20:19:05 -0000

On Oct 11, 2013, at 9:32 AM, Jorge Amodio <jmamodio@gmail.com> wrote:

> Just to start, there is no clear consensus of what "Internet =
Governance" means and entails.

You are correct.  The term "Internet Governance" is a term of art, and a =
poor one
at that.  It is the term that governments like to use, and in fact, in =
2005 several of=20
them got together at the United Nations-initiated World Summit on the =
Information=20
Society (WSIS) and came up with the following definition:

"Internet governance is the development and application by Governments, =
the private sector and civil society, in their respective roles, of =
shared principles, norms, rules, decision-making procedures, and =
programmes that shape the evolution and use of the Internet." =20
<http://www.wgig.org/docs/WGIGREPORT.pdf>

I happen to hate the term "Internet Governance", but its use has become =
a common=20
as shorthand for the discussions of governments expressing their needs =
and desires=20
with respect to the Internet, its related institutions, and civil =
society.

It might not be necessary for the IETF to be involved (if it so =
chooses), but I'm not
certain that leaving it to ISOC would make sense if/when the discussion =
moves into=20
areas such as structures for managing delegated registries of =
IETF-defined protocols
(i.e. protocols, names, numbers)

> In your particular case as President and CEO of ARIN, clearly you =
"lead" that organization but it does not make you representative of the =
Internet or its users. I can't find anywhere in the Bylaws and Articles =
of Incorporation of ARIN the word "Governance."
>=20
> Nobody will deny any of the alleged "leaders" to participate in any =
meeting, conference, event, in their individual capacities, but NONE has =
any representation of the whole Internet.

Full agreement there...  No one has any representation of the entire =
Internet, and=20
we should oppose the establishment of any structures that might aspire =
to such.

> Do we really want to create a "government" for the Internet ? How do =
you propose to select people to be representatives for all the sectors ?=20=


I do not, and expect others on this list feel the same.  However, it is =
likely that more
folks need to participate to make sure that such things don't happen.

> And in particular how do you propose to select an IETF representative =
and who/how it's going to give her/him its mandate to represent the =
organization on other forums ?

That is the essential question of this discussion, and hence the reason =
for my email.

I'd recommend that the IETF select leaders whose integrity you trust, =
you provide them=20
with documents of whatever principles the IETF considers important and =
how it views=20
it relations with other Internet institutions (could be developed via =
Internet Drafts) and=20
ask them to report back as frequently as possible.   Alternatively, the =
IETF could opt
to not participate in such discussions at all, and deal with any =
developments after the=20
fact (an option only if there is sufficient faith that the current =
models, structures, and=20
relationships of the IETF are inviolate.)

FYI,
/John=

From brian.e.carpenter@gmail.com  Fri Oct 11 15:41:53 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 0B2AB21E80DE; Fri, 11 Oct 2013 15:41:53 -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 WgfES4c1ZEFN; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 81AFD21E8095; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id rd3so5025884pab.18 for <multiple recipients>; Fri, 11 Oct 2013 15:41:52 -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=UYox1/C8ABBzIqlCaq2B0Syu+Li2UoNBsausiO4TVH0=; b=Yhbb2mbo7fofWghGuRYiNdx8vtmkO204sR06PXVAkI6iThmdTBjTYpaWOaGNHVS+UH PXjqZBcKRuWeR53PWFlRrnTm/aUVmLi4MdIspGSV2OULmlwPFM1NrKH1y/f7ZuLAqWSr O250rWx5Mxztc5z4BzJ0grGN97FuqrFA9MAdJKkehtRCCgkn5YY7Zx8+shL2s1LQYfxM bqq1/REyejyHV8M4cxP1YPoc66RGCJGbTZP+oES98w60f6KYoYkLTO8ROHGZluV5lCCL fZSw6baCpnYRkdusjqBAXJDV777mFawAGxe4b1ahl6vDcG0Wpoh8xUgxPwTo4nh7gOQI 0Scg==
X-Received: by 10.68.203.195 with SMTP id ks3mr22261289pbc.83.1381531312164; Fri, 11 Oct 2013 15:41:52 -0700 (PDT)
Received: from [192.168.178.20] (164.195.69.111.dynamic.snap.net.nz. [111.69.195.164]) by mx.google.com with ESMTPSA id xn12sm72900503pac.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 15:41:51 -0700 (PDT)
Message-ID: <52587EB8.4020506@gmail.com>
Date: Sat, 12 Oct 2013 11:42:00 +1300
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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Fri, 11 Oct 2013 22:41:53 -0000

Fred,

On 12/10/2013 08:56, Templin, Fred L wrote:
> Hi Brian,
> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: Friday, October 11, 2013 12:50 PM
>> To: Fernando Gont
>> Cc: Templin, Fred L; Ray Hunter; 6man Mailing List; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> On 12/10/2013 06:04, Fernando Gont wrote:
>> ...
>>> P.S.: Reegarding enforcing a limit on the length of the header chain,
>> I
>>> must say I symphatize with that (for instance, check the last
>> individual
>>> version of this I-D, and you'll find exactly that). But the wg didn't
>>> want that in -- and I did raise the issue a few times. So what we
>> have
>>> is what the 6man wg had consensus on.
>> I agree that this was the WG consensus after considerable discussion,
>> which included Fred, so I'm not sure why we're discussing it again
>> during IETF LC.
> 
> Technical matters should be discussed as they come to light; not
> dismissed because of some real or perceived deadline. That was what
> got us the 1280 MTU in the first place. Quoting from Steve Deering:
> 
>   " We would like to get this issue settled as
>     soon as possible, since this is the only thing holding up the publication
>     of the updated Proposed Standard IPv6 spec (the version we expect to advance
>     to Draft Standard), so let's see if we can come to a decision before the ID
>     deadline at the end of next week (hoping there isn't any conflict between
>     "thoughtful analysis" and "let's decide quickly" :-)."
> 
> So, it wasn't necessarily the case that 1280 was a product of "thoughtful
> analysis" so much as the fact that **they were rushing to get a spec out
> the door**. So now, 16 years later, we get to put it back on the 6man
> charter milestone list.

We could have that discussion in 6man, sure, but I don't believe that it's
relevant to the question of whether draft-ietf-6man-oversized-header-chain
is ready. This draft mitigates a known problem in terms of the current
IPv6 standards.

    Brian

From agenda@ietf.org  Fri Oct 11 17:12:30 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 892D511E81A1; Fri, 11 Oct 2013 17:12:30 -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 D4Y9082Ep-RM; Fri, 11 Oct 2013 17:12:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE5611E81A8; Fri, 11 Oct 2013 17:12:28 -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 88 Final Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131012001228.16052.32974.idtracker@ietfa.amsl.com>
Date: Fri, 11 Oct 2013 17:12:28 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 12 Oct 2013 00:12:30 -0000

88th IETF Meeting - Vancouver, BC, Canada
November 3 - 8, 2013

The final agenda has been posted.

https://datatracker.ietf.org/meeting/88/agenda.html
https://datatracker.ietf.org/meeting/88/agenda.txt

While this is considered the final agenda for printing, changes may
be made to the agenda up until and during the meeting. Updates will be refl=
ected on the web version of the agenda. =


Information about the 88th IETF meeting in Vancouver, BC, Canada can be fou=
nd here: https://www.ietf.org/meeting/88/index.html

Thank you and see you in Vancouver!

Sincerely,

The IETF Secretariat

From jmamodio@gmail.com  Fri Oct 11 17:52:31 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 01E0321E8119 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 17:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.068
X-Spam-Level: 
X-Spam-Status: No, score=-1.068 tagged_above=-999 required=5 tests=[AWL=0.135,  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 vJNfZxyLl+D4 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 17:52:26 -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 2967521E809A for <ietf@ietf.org>; Fri, 11 Oct 2013 17:52:22 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l20so2474052oag.31 for <ietf@ietf.org>; Fri, 11 Oct 2013 17:52:22 -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:from:subject:date:to; bh=aL47+lM/pADdvo7tMryhPjFyRINhA/I9qRB1JPnjico=; b=muZaZFF3Kngio3QD2F/+r+EhtQLgzcvcWj8kCXCD13vkyM+7ff+FZ7OEYiyJNKpc3D vhvUudYkco43vk+peRw0tQ9UH6ZLpXKmSmxEotoAcJiPmchJuHhNKG2eeWlBSztgE0u9 UJQKig5UsRxNY6Mo2j6WKxyo6cOK3i+ikBXHlmbceDgR1/w46TDbffZulr2sbVX5uZZE Mt7VW3yOWvX2q8+k3eO/IPhmPVRxz4Xre/y4dLxEp9R11ibY1qnrJe9k7ggSHLwdZgpO 2kmA9RdQTdsp/ExoAyG3ws9LBlymW7xekfgiY9YjMtnfjdN702IE/z+n/7ggjyfpLS3I jg+Q==
X-Received: by 10.60.52.1 with SMTP id p1mr12471887oeo.41.1381539142430; Fri, 11 Oct 2013 17:52:22 -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 s9sm27072445obu.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 17:52:21 -0700 (PDT)
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <CAMzo+1Yo-z1YH698kPctRoaWauaFirCjw0b=HA2dyf5WGEVa_w@mail.gmail.com> <130D5133-01F5-49C6-92F7-5F706E7B8340@istaff.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <130D5133-01F5-49C6-92F7-5F706E7B8340@istaff.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <84748636-D71E-441E-A394-9FFAE1B0323A@gmail.com>
X-Mailer: iPad Mail (11A501)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Of governments and representation (was: Montevideo Statement)
Date: Fri, 11 Oct 2013 19:52:21 -0500
To: John Curran <jcurran@istaff.org>
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: Sat, 12 Oct 2013 00:52:32 -0000

Thank you for your frank and honest response John.

-Jorge

> On Oct 11, 2013, at 3:18 PM, John Curran <jcurran@istaff.org> wrote:
>=20
>> On Oct 11, 2013, at 9:32 AM, Jorge Amodio <jmamodio@gmail.com> wrote:
>>=20
>> Just to start, there is no clear consensus of what "Internet Governance" m=
eans and entails.
>=20
> You are correct.  The term "Internet Governance" is a term of art, and a p=
oor one
> at that.  It is the term that governments like to use, and in fact, in 200=
5 several of=20
> them got together at the United Nations-initiated World Summit on the Info=
rmation=20
> Society (WSIS) and came up with the following definition:
>=20
> "Internet governance is the development and application by Governments, th=
e private sector and civil society, in their respective roles, of shared pri=
nciples, norms, rules, decision-making procedures, and programmes that shape=
 the evolution and use of the Internet." =20
> <http://www.wgig.org/docs/WGIGREPORT.pdf>
>=20
> I happen to hate the term "Internet Governance", but its use has become a c=
ommon=20
> as shorthand for the discussions of governments expressing their needs and=
 desires=20
> with respect to the Internet, its related institutions, and civil society.=

>=20
> It might not be necessary for the IETF to be involved (if it so chooses), b=
ut I'm not
> certain that leaving it to ISOC would make sense if/when the discussion mo=
ves into=20
> areas such as structures for managing delegated registries of IETF-defined=
 protocols
> (i.e. protocols, names, numbers)
>=20
>> In your particular case as President and CEO of ARIN, clearly you "lead" t=
hat organization but it does not make you representative of the Internet or i=
ts users. I can't find anywhere in the Bylaws and Articles of Incorporation o=
f ARIN the word "Governance."
>>=20
>> Nobody will deny any of the alleged "leaders" to participate in any meeti=
ng, conference, event, in their individual capacities, but NONE has any repr=
esentation of the whole Internet.
>=20
> Full agreement there...  No one has any representation of the entire Inter=
net, and=20
> we should oppose the establishment of any structures that might aspire to s=
uch.
>=20
>> Do we really want to create a "government" for the Internet ? How do you p=
ropose to select people to be representatives for all the sectors ?
>=20
> I do not, and expect others on this list feel the same.  However, it is li=
kely that more
> folks need to participate to make sure that such things don't happen.
>=20
>> And in particular how do you propose to select an IETF representative and=
 who/how it's going to give her/him its mandate to represent the organizatio=
n on other forums ?
>=20
> That is the essential question of this discussion, and hence the reason fo=
r my email.
>=20
> I'd recommend that the IETF select leaders whose integrity you trust, you p=
rovide them=20
> with documents of whatever principles the IETF considers important and how=
 it views=20
> it relations with other Internet institutions (could be developed via Inte=
rnet Drafts) and=20
> ask them to report back as frequently as possible.   Alternatively, the IE=
TF could opt
> to not participate in such discussions at all, and deal with any developme=
nts after the=20
> fact (an option only if there is sufficient faith that the current models,=
 structures, and=20
> relationships of the IETF are inviolate.)
>=20
> FYI,
> /John

From mcr@sandelman.ca  Fri Oct 11 19:01:12 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 D409821F9D2C for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 19:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[AWL=0.397,  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 vehT2go+GSlb for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 19:01:12 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id E689921E80DA for <ietf@ietf.org>; Fri, 11 Oct 2013 19:01:11 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 667FC20273; Fri, 11 Oct 2013 23:11:22 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 325BB63B88; Fri, 11 Oct 2013 22:01:03 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 21DB463AEF; Fri, 11 Oct 2013 22:01:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Montevideo statement
In-Reply-To: <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@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: Fri, 11 Oct 2013 22:01:03 -0400
Message-ID: <18100.1381543263@sandelman.ca>
Sender: mcr@sandelman.ca
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: Sat, 12 Oct 2013 02:01:13 -0000

--=-=-=


Phillip Hallam-Baker <hallam@gmail.com> wrote:
    > I think that is a better approach actually. The CC TLDs are in effect
    > members of a bridge CA and ICANN is merely the bridge administrator.

It is an interesting way to say it, and put that way, I like it.

One activity that I believe is an NSA attack on good crypto is the whole
Certificate Signing Policy thing.  Nobody has a clue what it means, or how
the computer systems are supposed to interpret it anyway, but it scares the
lawyers, and so they would rather having nothing.

However, it the root of the trust in country X is the government of country
X, then government can essentially internalize/nationalize all the liability
associated with trusting them.  It would be much like governments do with
nuclear power: it only works out because the governments provide the
insurance in the form of legislation...

    mcr>     Better they do this using good crypto, than that they do this by
    mcr> trying to subvert the (US-controlled) crypto.

    > Its not all US controlled, you can use GOST...

That's not what I meant.

I didn't mean that the algorithms will be subverted, I meant that the trust
paths will be subverted.

Whether this is by legislating filters against DNS(sec) that ISPs have to
implement, or having an official mitm SSL cert that all desktops must trust,
or just blocking port-443.

--
]               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)

iQCVAwUBUlitXoqHRg3pndX9AQJeAAP/SRTUVlhU9y9jCYBa27BcLBLzTmN7pLq+
jV4wZhj91v5bMZ1vRNmxrwcSa5S+vqczidxyQLfnY7b1qzSmd3yenrdc/SA06rHH
z8u0mZvbxmjbADsUO2Ebf3WqFxmp3iTQeixoZcZEuYeoFpT/YlgJJuiito2pO/N6
TAQ1q1frFZ0=
=Ocvs
-----END PGP SIGNATURE-----
--=-=-=--

From jari.arkko@piuha.net  Fri Oct 11 23:32:05 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 4EC8B21E80D0 for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 23:32:05 -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 Pvgfg9x4eCTo for <ietf@ietfa.amsl.com>; Fri, 11 Oct 2013 23:32:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 007C121E80BE for <ietf@ietf.org>; Fri, 11 Oct 2013 23:31:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 996902CC5F; Sat, 12 Oct 2013 09:31: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 hHAeQIO6Wdho; Sat, 12 Oct 2013 09:31:56 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0C1862CC48; Sat, 12 Oct 2013 09:31:56 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Montevideo statement
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <63FC31E7-840D-44C0-96F8-A046889CCF71@piuha.net>
Date: Sat, 12 Oct 2013 09:31:55 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5A10BE7-4F7F-4960-B249-FFCD74190E90@piuha.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <5256DE72.4010705@dcrocker.net> <BD554473-CD9D-4795-A125-A4E52EAEC68D@piuha.net> <5256F68D.7020509@dcrocker.net> <63FC31E7-840D-44C0-96F8-A046889CCF71@piuha.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
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, 12 Oct 2013 06:32:05 -0000

It was pointed out that I got the RFC numbers wrong. Sorry. I should =
have RFC 6220 (role of IETF protocol parameters operators) and RFC 2850 =
(IAB charter).

Jari


From jnc@mercury.lcs.mit.edu  Sat Oct 12 05:02:48 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 3062111E8193 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 05:02:48 -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 A-+vDANeiyxr for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 05:02:43 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 248D811E8146 for <ietf@ietf.org>; Sat, 12 Oct 2013 05:02:43 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2BF7118C0C3; Sat, 12 Oct 2013 08:02:42 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Of governments and representation (was: Montevideo Statement)
Message-Id: <20131012120242.2BF7118C0C3@mercury.lcs.mit.edu>
Date: Sat, 12 Oct 2013 08:02: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: Sat, 12 Oct 2013 12:02:48 -0000

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > Reality is different - the outside world expects to hear from us.

I would guess that nobody (almost nobody?)in the IETF objects to I*
leadership representing our views at such things; in fact, I suspect most of
us would find it positively very desirable for the I* to be represented
there. (I certainly do.)

The thing is that I (and I suspect much of the IETF) feel that such I*
leadership attendees need to make it _very_ clear at such events that they are
there to present (as best they can) the views of the IETF as a whole, but they
cannot _commit_ the IETF to anything: only the IETF acting as a whole can do
that.

So, for instance, in signing a statement, they need to say "John Smith,
current Ixx chair, signing as an individual", or something like that - to make
it clear to readers that their signature does not bind the organization as a
whole.

	Noel

From stephen.farrell@cs.tcd.ie  Sat Oct 12 05:23:52 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 3FC9621F9DD6 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 05:23: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=[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 Jy5VzyZA9djF for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 05:23:46 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1EDB821F9E0B for <ietf@ietf.org>; Sat, 12 Oct 2013 05:23:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9F231BE77; Sat, 12 Oct 2013 13:23:40 +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 m+0qcL70rp73; Sat, 12 Oct 2013 13:23:39 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.46.27.78]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9932EBE76; Sat, 12 Oct 2013 13:23:39 +0100 (IST)
Message-ID: <52593F4B.9070904@cs.tcd.ie>
Date: Sat, 12 Oct 2013 13:23:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Of governments and representation (was: Montevideo Statement)
References: <20131012120242.2BF7118C0C3@mercury.lcs.mit.edu>
In-Reply-To: <20131012120242.2BF7118C0C3@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.5.2
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, 12 Oct 2013 12:23:52 -0000

Hiya,

On 10/12/2013 01:02 PM, Noel Chiappa wrote:

> The thing is that I (and I suspect much of the IETF) feel that such I*
> leadership attendees need to make it _very_ clear at such events that they are
> there to present (as best they can) the views of the IETF as a whole, but they
> cannot _commit_ the IETF to anything: only the IETF acting as a whole can do
> that.

So fwiw I was there as Jari's sidekick-de-jour and I can confirm
that both Jari and Russ repeatedly made it clear that anything
substantive needed IETF community consensus. I realise that's not
as good as a recording or set of minutes, but there ya go.

Cheers,
S.

From arturo.servin@gmail.com  Sat Oct 12 06:29:53 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 C978011E8242 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 06:29:53 -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 Y5TkaDkzgHis for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 06:29:48 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id AD94F11E8136 for <ietf@ietf.org>; Sat, 12 Oct 2013 06:29:48 -0700 (PDT)
Received: by mail-gg0-f172.google.com with SMTP id a5so992560ggn.31 for <ietf@ietf.org>; Sat, 12 Oct 2013 06:29:33 -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=77Ifg9QaET/usob/fjr6WYH7kAC/FGOGquXBGeYQCqk=; b=PxW7reZ5wPDujq/bqH71Xc2MjBzI4C0bJpsJgz8AWxtiuynRp4LcXYG1scl1BJa4LD hE0zFDtx8RGFd/h9PgZimD6+RVM4KTEo9edqDvK5Lp7v5X1Xo8GCPyau5L8ydFpYI311 IDAROCNIk62441reQn5MtSMtkbk7dtGBiDh6sglWjaB9pwBEnf8oWQwNWeDMLJ8MWDrz m5FHmXajhx2vg5lUmV6bnRjLk4f0F8MTNj3N06Ag5EKzQX52cS4ipZ6fCfb3W1rrnbb9 2yneIzRXmJljk+fPMWjSvMQs3tgvHwAqH/M9h+dbtGHsViftmhvFcbvG47xmxlR4XIbb lkpg==
X-Received: by 10.236.129.20 with SMTP id g20mr17092170yhi.10.1381584573164; Sat, 12 Oct 2013 06:29:33 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:c88b:cccb:9fd:1b63:4171]) by mx.google.com with ESMTPSA id r1sm87073151yhf.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Oct 2013 06:29:32 -0700 (PDT)
Message-ID: <52594EB8.4000702@gmail.com>
Date: Sat, 12 Oct 2013 11:29:28 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Of governments and representation (was: Montevideo Statement)
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <52585188.6020408@gmail.com>
In-Reply-To: <52585188.6020408@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, 12 Oct 2013 13:29:53 -0000

	It is clear to me that the IETF cannot be away from Internet Governance
discussions. Yes, it is politics and we do not like politics, but that
is the way the Internet is these days.

	It is also appears that we do not have consensus of how to participate
and what to say in those discussions (I do not mind the way it is today
but it seems that some folk -and I understand them- prefer other ways).

	Inevitably, as John said we are in times of change and we need to
figure out how to interact with other Internet ecosystem organizations,
we like or not.

	By means of our current bodies (IAB, IESG), individual submissions or
working groups we need to find a way to what say, where, and how.

Regards,
as


On 10/11/13 5:29 PM, Brian E Carpenter wrote:
> Hi John,
> 
> On 12/10/2013 05:02, John Curran wrote:
> ...
>> In my personal view, it is a very important for the IETF to select leadership who can
>> participate in any discussions that occur,
> 
> Without obsessing about the word "leadership", but following up on a comment
> made by Noel Chiappa on the "leader statements" thread, I think we have
> to recognise that nothing in the NomCom process, the IAB Charter, or
> the IESG Charter, would cause us to select IAB or IETF Chairs who are
> particularly suited to this role.
> 
> In fact I think that the plan of record is to leave such matters to
> ISOC.
> 
> Reality is different - the outside world expects to hear from us.
> 
>      Brian
> 

From adrian@olddog.co.uk  Sat Oct 12 07:51: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 EBF8621E8176 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 07:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045,  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 1JEa9pvZHcci for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 07:51:04 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id D269D21E8175 for <ietf@ietf.org>; Sat, 12 Oct 2013 07:51:00 -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 r9CEoXut011014;  Sat, 12 Oct 2013 15:50:34 +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 r9CEoWw4010998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 12 Oct 2013 15:50:33 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, "'Eggert, Lars'" <lars@netapp.com>
Subject: RE: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
Date: Sat, 12 Oct 2013 15:50:30 +0100
Message-ID: <002c01cec75a$66381aa0$32a84fe0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7HWcdq+wTtu4i6TL6OHEQ2gUGy7g==
Content-Language: en-gb
Cc: 'Bob Hinden' <bob.hinden@gmail.com>, 'S Moonesamy' <sm+ietf@elandsys.com>, 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, 12 Oct 2013 14:51:10 -0000

Abdussalam Baryun said:

> I am part of the community design team as well because
> I participate with community more than the private hidden
>=A0groups. I think that the draft is a true work open to IETF. I
> still did not get a reply to my request to know what is the
> DT authority, very strange name without any procedure
> in IETF, please explain,
=A0
I don't understand your assertion that there is no procedure in the IETF =
to
support the existence of a Design Team.

Please read section 6.5 of RFC 2418 and the email from Lars and respond =
if you
still believe that there is no procedure in the IETF to support the =
existence of
a Design Team.

Adrian


From melinda.shore@gmail.com  Sat Oct 12 12:35:21 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 8F24D21E8085 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 12:35: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, 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 gX0ap-ZrPDu1 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 12:35:21 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id A391D21E8106 for <ietf@ietf.org>; Sat, 12 Oct 2013 12:35:17 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id q59so5650761wes.9 for <ietf@ietf.org>; Sat, 12 Oct 2013 12:35:14 -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=eVpFLZ0A8eybbBi4NLcw2yey9DvmVd6t0bGLnTJMAWY=; b=a80XVIV4v4JOi8K/E1JrTg6Iy8mu0EpK2DFm4BjPR9H6HANjSPWhhacr3OD3zRWorS +j/oCfsQYE5IX/AO4miHmxWV2BA3sOYh0KaX6UqKod41QXHglJsQR8azEUcfnSub6Elc pZCpLXaa4tKdRw+k54hCIsNfrYLrpHrN8b6brqmVN4XOjvF6/U4zYeTYfKryahUA/s+R rGHTa3jYxzEM20XLjLPQYXJb5QekyZOEcCw7V4xusIFgpopiYPBB3lrXKbZvOnkFCEnz xut1V0KcQkt/GnK82sJMIQGK6rMzHdpL8Cnj5pN64LIL6JAbBzWMU+1YoRKdxFyxG71g GDow==
MIME-Version: 1.0
X-Received: by 10.180.104.34 with SMTP id gb2mr8350731wib.3.1381606514614; Sat, 12 Oct 2013 12:35:14 -0700 (PDT)
Received: by 10.227.132.198 with HTTP; Sat, 12 Oct 2013 12:35:14 -0700 (PDT)
Received: by 10.227.132.198 with HTTP; Sat, 12 Oct 2013 12:35:14 -0700 (PDT)
In-Reply-To: <002c01cec75a$66381aa0$32a84fe0$@olddog.co.uk>
References: <002c01cec75a$66381aa0$32a84fe0$@olddog.co.uk>
Date: Sat, 12 Oct 2013 11:35:14 -0800
Message-ID: <CAKRbAfDbZWENX3VF1TF8PEJA+-D047QGzDsZ8GrQwLoJqxkniw@mail.gmail.com>
Subject: RE: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Melinda Shore <melinda.shore@gmail.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary=f46d044271b085e8d904e890553a
Cc: ietf@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, Bob Hinden <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: Sat, 12 Oct 2013 19:35:21 -0000

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

On Oct 12, 2013 6:51 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
> I don't understand your assertion that there is no procedure in the IETF
to
> support the existence of a Design Team.

I'd be sorry to see this discussion dragged down a procedural rathole.

Melinda

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

<p>On Oct 12, 2013 6:51 AM, &quot;Adrian Farrel&quot; &lt;<a href="mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; wrote:<br>
&gt; I don&#39;t understand your assertion that there is no procedure in the IETF to<br>
&gt; support the existence of a Design Team.</p>
<p>I&#39;d be sorry to see this discussion dragged down a procedural rathole.</p>
<p>Melinda <br>
</p>

--f46d044271b085e8d904e890553a--

From dhc@dcrocker.net  Sat Oct 12 13:04: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 89A9B21E80FD for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 13:04:26 -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 E5L7Eq7P8AEF for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 13:04:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C63E821F9AB4 for <ietf@ietf.org>; Sat, 12 Oct 2013 13:04:21 -0700 (PDT)
Received: from [10.100.255.252] ([203.167.240.58]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9CK4FIe000751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 12 Oct 2013 13:04:20 -0700
Message-ID: <5259AB31.7080200@dcrocker.net>
Date: Sun, 13 Oct 2013 09:04:01 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Of governments and representation (was: Montevideo Statement)
References: <20131012120242.2BF7118C0C3@mercury.lcs.mit.edu>
In-Reply-To: <20131012120242.2BF7118C0C3@mercury.lcs.mit.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]); Sat, 12 Oct 2013 13:04:20 -0700 (PDT)
Cc: 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: Sat, 12 Oct 2013 20:04:26 -0000

On 10/13/2013 1:02 AM, Noel Chiappa wrote:
>      > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>
>      > Reality is different - the outside world expects to hear from us.
>
> I would guess that nobody (almost nobody?)in the IETF objects to I*
> leadership representing our views at such things;

For at least one of the items in the signed statement, there is no basis 
for claiming to know what the IETF's views are.

When the IETF's views are clear, then of course having folks accurately 
represent those views publicly is dandy.


> The thing is that I (and I suspect much of the IETF) feel that such I*
> leadership attendees need to make it _very_ clear at such events that they are
> there to present (as best they can) the views of the IETF as a whole, but they
> cannot _commit_ the IETF to anything: only the IETF acting as a whole can do
> that.

Here's where reality runs over theory.  For mass-market public 
statements, such nuance is entirely lost.  It is therefore misguided to 
believe that careful qualification will alter what is perceived by the 
public.

Lest anyone dismiss this concern with something along the lines of "we 
can't be responsible for other people's failure to listen carefully," 
I'll note that proactively anticipating and dealing with such likely 
failures is exactly the responsibility of anyone claiming to speak for 
an organization publicly.

There's even professional media relations training typically given to 
executives, for just this purpose.


> So, for instance, in signing a statement, they need to say "John Smith,
> current Ixx chair, signing as an individual", or something like that - to make
> it clear to readers that their signature does not bind the organization as a
> whole.

Yeah, but the likely benefit of that isn't very high, given the strong 
predilection some folk have for stoking the political fires when the 
topic is already highly politicized.  For example:

 
http://www.internetgovernance.org/2013/10/11/the-core-internet-institutions-abandon-the-us-government/ 


Again, the nature of playing in such a sandbox -- as the Montevideo 
Statement attempts to do -- requires robust effort both to be accurate 
in what is said, but also to protect against misinterpretation.

Montevideo Statement seems to have accomplished neither.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From randy@psg.com  Sat Oct 12 16:49:13 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 0FDB311E80F1 for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 16:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  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 jJEpHHTzXBOm for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 16:49:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6A211E80ED for <ietf@ietf.org>; Sat, 12 Oct 2013 16:49:12 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VV8vm-0005Dl-TB; Sat, 12 Oct 2013 23:49:11 +0000
Date: Sun, 13 Oct 2013 08:49:38 +0900
Message-ID: <m2txgmrqwd.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: new draft needed
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, 12 Oct 2013 23:49:13 -0000

pete,

since you did such an excellent draft capturing our local customs on
rough consensus, could we convince you to now do one on second guessing,
micro-management, and creation of petty bureaucracy, which seem to be
even more prevalent than rough consensus?  thanks.

randy

From rbonica@juniper.net  Sat Oct 12 19:07:12 2013
Return-Path: <rbonica@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 5B39011E8106; Sat, 12 Oct 2013 19:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.699
X-Spam-Level: 
X-Spam-Status: No, score=-104.699 tagged_above=-999 required=5 tests=[AWL=1.900, 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 s6TIpIacj1jr; Sat, 12 Oct 2013 19:06:53 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1981E11E80FE; Sat, 12 Oct 2013 19:06:52 -0700 (PDT)
Received: from mail220-co9-R.bigfish.com (10.236.132.242) by CO9EHSOBE009.bigfish.com (10.236.130.72) with Microsoft SMTP Server id 14.1.225.22; Sun, 13 Oct 2013 02:06:52 +0000
Received: from mail220-co9 (localhost [127.0.0.1])	by mail220-co9-R.bigfish.com (Postfix) with ESMTP id E54D62600B5; Sun, 13 Oct 2013 02:06:51 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: VPS1(zz1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzzz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail220-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(189002)(199002)(51704005)(69226001)(80022001)(66066001)(65816001)(63696002)(56816003)(77096001)(46102001)(74706001)(33646001)(74876001)(83072001)(51856001)(76482001)(53806001)(56776001)(54316002)(81816001)(54356001)(74366001)(4396001)(47446002)(74502001)(74662001)(59766001)(79102001)(77982001)(81686001)(81542001)(47976001)(50986001)(49866001)(85306002)(47736001)(31966008)(81342001)(80976001)(74316001)(76786001)(76796001)(83322001)(76576001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail220-co9 (localhost.localdomain [127.0.0.1]) by mail220-co9 (MessageSwitch) id 1381630010253315_13970; Sun, 13 Oct 2013 02:06:50 +0000 (UTC)
Received: from CO9EHSMHS014.bigfish.com (unknown [10.236.132.234])	by mail220-co9.bigfish.com (Postfix) with ESMTP id 2E90980040; Sun, 13 Oct 2013 02:06:50 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS014.bigfish.com (10.236.130.24) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sun, 13 Oct 2013 02:06:49 +0000
Received: from CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Sun, 13 Oct 2013 02:06:48 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.0.785.10; Sun, 13 Oct 2013 02:06:45 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.14]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.50]) with mapi id 15.00.0785.001; Sun, 13 Oct 2013 02:06:45 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxlz+2A8NgSbtr0yOE+fNSkVMX5nvonIAgAAYo4CAAC5BAIAAAfUAgAAuLACAAcruIA==
Date: Sun, 13 Oct 2013 02:06:44 +0000
Message-ID: <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com>
In-Reply-To: <52587EB8.4020506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0998671D02
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Sun, 13 Oct 2013 02:07:12 -0000

+1

Is there a way to decouple this discussion from draft-ietf-6man-oversized-h=
eader-chain? I would be glad to discuss it in the context of a separate dra=
ft.

                                                             Ron


> >
> > So, it wasn't necessarily the case that 1280 was a product of
> > "thoughtful analysis" so much as the fact that **they were rushing to
> > get a spec out the door**. So now, 16 years later, we get to put it
> > back on the 6man charter milestone list.
>=20
> We could have that discussion in 6man, sure, but I don't believe that
> it's relevant to the question of whether draft-ietf-6man-oversized-
> header-chain
> is ready. This draft mitigates a known problem in terms of the current
> IPv6 standards.
>=20



From sm@resistor.net  Sat Oct 12 22:06:29 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 858FE11E810A for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 22:06: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 o+B47LUq9rYk for <ietf@ietfa.amsl.com>; Sat, 12 Oct 2013 22:06:28 -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 BB96911E8114 for <ietf@ietf.org>; Sat, 12 Oct 2013 22:06: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 r9D56EWP005046 for <ietf@ietf.org>; Sat, 12 Oct 2013 22:06:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381640779; bh=Sdptrbr8VveFxYfGiQffUF7HEmntAYXAhhF4GRY9lTw=; h=Date:To:From:Subject:In-Reply-To:References; b=DVxh0rp0MtSNEwe5GAKbI7K7sbhhAYRdymPHPdlacOfeK6fbkhWp24ukM7Vv33URN IYFAqSQstHOWGyXMMjX2Gy1VSPNWmVQt31Upy0+Z6woS0tFX5ltcPmyqvdgLyvuGMW in6r5537tDGVzbWgNxEdp2RzgzaWdcRGrQmLkqMo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381640779; i=@resistor.net; bh=Sdptrbr8VveFxYfGiQffUF7HEmntAYXAhhF4GRY9lTw=; h=Date:To:From:Subject:In-Reply-To:References; b=GYJKxzUwX/QkfWLoGOceRCWbdMbYrBlj0HlEj9SSpqaTvQYkIo35OjmQlkQnYkR+m w2WgoGywBVbkc6gXyT6aAt3cID3RpDLkidCNTMeyhhsNSNA4G+rvu3SHen/0qMt87s iz8YvgyQaFK4fvSpcL7XbiL457WhD/Y0k+RLR+As=
Message-Id: <6.2.5.6.2.20131012194048.0c92f558@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 12 Oct 2013 22:00:00 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
In-Reply-To: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>
References: <20131002185522.20697.96027.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: Sun, 13 Oct 2013 05:06:29 -0000

At 11:55 02-10-2013, The IESG wrote:
>The IESG has received a request from the IPv6 Maintenance WG (6man) to
>consider the following document:
>- 'Implications of Oversized IPv6 Header Chains'
>   <draft-ietf-6man-oversized-header-chain-08.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

This document intends to update the IPv6 specification.  I looked 
into some code (host) which would be affected by the RFC 2119 
requirement in Section 5.  The code is complex as it is.  I am not 
sure whether the requirement can be implemented without too much 
difficulty.  I have not looked into the code which processes inbound packets.

Regards,
-sm
    


From ron.even.tlv@gmail.com  Sun Oct 13 01:03:57 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 8D7F321F99E7; Sun, 13 Oct 2013 01:03:57 -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 ihrVfyqltPMt; Sun, 13 Oct 2013 01:03:56 -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 CE98921F92DA; Sun, 13 Oct 2013 01:03:56 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so6264594pad.33 for <multiple recipients>; Sun, 13 Oct 2013 01:03:56 -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 :thread-index:content-language; bh=EzwYQlEjs+EHMTN1xhKrgED9NKuUPLvcPVWu0ABvT94=; b=Tq1L4uX5ZJ1Wu4S4lxlGeXOPByC1znxcx+0fe3mEUztz9bp9hrf0jgzYRMJUy3Y44k bqXxxHrce8sZE+NSDn0EZLII2bh12+26UOKFanOvKYJKgOaouP8pAe/swXl6rEmjuBU2 fwfJl+kOKJHwBJNVxx7hXKZik7FYSE1Gv+667lBvK0nvWcv17N+MgDaLS0M2crRoj/FT VyumGw+K0kwxnwNHiNtLniisKqRrKwVzmLXU1PUEp53lTtVzL3zbDMVKQYlE4bBJo7Q9 TS2OIzJa2c0aFDIyfxx4qU4GiphcO1S4heNOJuvS9bO8tSfFUQmYtU0Er85suxjSTFKQ 0TXA==
X-Received: by 10.68.163.132 with SMTP id yi4mr111529pbb.158.1381651436491; Sun, 13 Oct 2013 01:03:56 -0700 (PDT)
Received: from RoniE (static-ip-194-129-66-202.rev.dyxnet.com. [202.66.129.194]) by mx.google.com with ESMTPSA id xv2sm70544816pbb.39.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 13 Oct 2013 01:03:55 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
Date: Sun, 13 Oct 2013 11:00:46 +0300
Message-ID: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002B_01CEC803.7BDA8A60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7H6k6ts2OfT/B1SHS+cC5qNEg+Qw==
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, 13 Oct 2013 08:03:57 -0000

This is a multipart message in MIME format.

------=_NextPart_000_002B_01CEC803.7BDA8A60
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-mpls-tp-rosetta-stone-12

Reviewer: Roni Even

Review Date:2013-10-12

IETF LC End Date: 2013-10-16

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

Minor issues:

 

Nits/editorial comments:

 

 


------=_NextPart_000_002B_01CEC803.7BDA8A60
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;}
--></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-mpls-tp-rosetta-stone-12</span><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;10&#8211;12<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-10&#8211;16<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 ready for publication as an Informational 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=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_002B_01CEC803.7BDA8A60--


From abdussalambaryun@gmail.com  Sun Oct 13 02:39:43 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 4473E11E812D for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 02:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level: 
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5 tests=[AWL=-0.014, 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 vlPCJJDFeG5i for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 02:39:42 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4E05711E81A3 for <ietf@ietf.org>; Sun, 13 Oct 2013 02:39:42 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id rd3so6311428pab.18 for <ietf@ietf.org>; Sun, 13 Oct 2013 02:39: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=xtmHx1whPJ4WJBgAmMRhTDyyGksCFpR7OB8qe7KMc/s=; b=Ty8Tmbij2XnINbNiYimG38ZT/zOXeuTx9DdmpqwI8/MVF7mbPdJm2cGlCyXFhHb3IW rHlTSnfl2cj2b4jvM+J2lp4UNE/dqpruIR5Db1uJcLqsyXRYAXb46aosUWqUJhwg01FK iu7O74mV/fM8e23XEqeAUZ4OgCZ1Hv0vmotk03qno2X9zywfoLly4pioauGvgOyhw/xl SS3R7LWM/Kg8IooAvLXfhuLP6lSMiy92cbLn/ejU7OW0hhJjHXQX1cu6UlUTt3w5wD1n MBd8YCnFpE34Z6+cfBJfQE+RRryNIMkFAm7a62Tq7VkZGKPAhxbhrAwJ7Zz7d6052tQQ DqTA==
MIME-Version: 1.0
X-Received: by 10.66.149.231 with SMTP id ud7mr32182473pab.8.1381657173624; Sun, 13 Oct 2013 02:39:33 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 13 Oct 2013 02:39:33 -0700 (PDT)
In-Reply-To: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com>
Date: Sun, 13 Oct 2013 11:39:33 +0200
Message-ID: <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b6d95d0090f5004e89c2193
Cc: "draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org" <draft-ietf-mpls-tp-rosetta-stone.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: Sun, 13 Oct 2013 09:39:43 -0000

--047d7b6d95d0090f5004e89c2193
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The draft does not list ITU in abbreviation, there are many terminology not
clear but more general definition. I prefer specific defining. Also many
times refers to references to define without mentioning what was that
definition, is that defined only in ITU and IETF cannot define its
technology, or is it agreeing on a joint definition so IETF is just
following ITU in some terms.

AB

On Sunday, October 13, 2013, Roni Even 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-ietf-mpls-tp-rosetta-stone-12****
>
> Reviewer: Roni Even****
>
> Review Date:2013=9610=9612****
>
> IETF LC End Date: 2013-10=9616****
>
> IESG Telechat date: ****
>
> ** **
>
> Summary: This draft is ready for publication as an Informational RFC.****
>
> ** **
>
> ** **
>
> Major issues:****
>
> Minor issues:****
>
> ** **
>
> Nits/editorial comments:****
>
> ** **
>
> ** **
>

--047d7b6d95d0090f5004e89c2193
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The draft does not list ITU in abbreviation, there are many terminology not=
 clear but more general definition. I prefer specific defining. Also many t=
imes refers to references to define without mentioning what was that defini=
tion, is that defined only in ITU and IETF cannot define its technology, or=
 is it agreeing on a joint definition so IETF is just following ITU in some=
 terms.<div>
<br></div><div>AB<br><div><div><br>On Sunday, October 13, 2013, Roni Even  =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" =
vlink=3D"purple">
<div><p class=3D"MsoNormal"><a name=3D"141b0d87253b0c4b_OLE_LINK1"></a><a n=
ame=3D"141b0d87253b0c4b_OLE_LINK2">I am the assigned Gen-ART reviewer for t=
his 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"_bla=
nk">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<u></u>=
<u></u></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<u></u><u></u></p><p><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Documen=
t: </span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-mp=
ls-tp-rosetta-stone-12</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">Reviewer: Roni Even<u></u><u></u></span></p><p><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
">Review Date:2013=9610=9612<u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">IETF LC End Date: 2013-10=9616<u></u><u></u></span></p><p><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;">IESG Telechat date: <u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary: This d=
raft is ready for publication as an Informational RFC</span><span style=3D"=
font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<=
u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=A0<u></=
u></span></p>
<p class=3D"MsoNormal">Major issues:<u></u><u></u></p><p class=3D"MsoNormal=
">Minor issues:<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></=
p><p class=3D"MsoNormal">Nits/editorial comments:<u></u><u></u></p><p class=
=3D"MsoNormal">
<u></u>=A0<u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></di=
v></blockquote></div></div></div>

--047d7b6d95d0090f5004e89c2193--

From loa@pi.nu  Sun Oct 13 02:45:55 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 07DD811E81A3 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 02:45:55 -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 mN64xlDh+lAG for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 02:45:50 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 68EEA21F9AD2 for <ietf@ietf.org>; Sun, 13 Oct 2013 02:45:50 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.84.108]) (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 939FE1802039; Sun, 13 Oct 2013 11:45:48 +0200 (CEST)
Message-ID: <525A6BC9.4040701@pi.nu>
Date: Sun, 13 Oct 2013 17:45:45 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org, "abdussalambaryun@gmail.com >> Abdussalam Baryun" <abdussalambaryun@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com>
In-Reply-To: <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
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: Sun, 13 Oct 2013 09:45:55 -0000

AB,

ITU and ITU-T are both in 
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt listed as 
one of the well-known acronyms we
can use without expanding it; all the specific definition you need :) !

/Loa

On 2013-10-13 17:39, Abdussalam Baryun wrote:
> The draft does not list ITU in abbreviation, there are many terminology
> not clear but more general definition. I prefer specific defining. Also
> many times refers to references to define without mentioning what was
> that definition, is that defined only in ITU and IETF cannot define its
> technology, or is it agreeing on a joint definition so IETF is just
> following ITU in some terms.
>
> AB
>
> On Sunday, October 13, 2013, Roni Even 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-ietf-mpls-tp-rosetta-stone-12____
>
>     Reviewer: Roni Even____
>
>     Review Date:2013–10–12____
>
>     IETF LC End Date: 2013-10–16____
>
>     IESG Telechat date: ____
>
>     __ __
>
>     Summary: This draft is ready for publication as an Informational
>     RFC.____
>
>     __ __
>
>     __ __
>
>     Major issues:____
>
>     Minor issues:____
>
>     __ __
>
>     Nits/editorial comments:____
>
>     __ __
>
>     __ __
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From daedulus@btconnect.com  Sun Oct 13 03:45:39 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 5699521E80AF for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 03:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.866
X-Spam-Level: 
X-Spam-Status: No, score=-2.866 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_00=-2.599, J_CHICKENPOX_43=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 zxevMnmo9Qsg for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 03:45:32 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0189.outbound.messaging.microsoft.com [213.199.154.189]) by ietfa.amsl.com (Postfix) with ESMTP id B995521F9A1C for <ietf@ietf.org>; Sun, 13 Oct 2013 03:45:24 -0700 (PDT)
Received: from mail131-db8-R.bigfish.com (10.174.8.244) by DB8EHSOBE015.bigfish.com (10.174.4.78) with Microsoft SMTP Server id 14.1.225.22; Sun, 13 Oct 2013 10:45:23 +0000
Received: from mail131-db8 (localhost [127.0.0.1])	by mail131-db8-R.bigfish.com (Postfix) with ESMTP id F20B94E0142	for <ietf@ietf.org>; Sun, 13 Oct 2013 10:45:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -6
X-BigFish: PS-6(zz9371I542Idc59ozz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah1de097h186068h8275dhz2dh2a8h5a9h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail131-db8 (localhost.localdomain [127.0.0.1]) by mail131-db8 (MessageSwitch) id 138166112149041_18887; Sun, 13 Oct 2013 10:45:21 +0000 (UTC)
Received: from DB8EHSMHS028.bigfish.com (unknown [10.174.8.236])	by mail131-db8.bigfish.com (Postfix) with ESMTP id 074A2380047	for <ietf@ietf.org>; Sun, 13 Oct 2013 10:45:21 +0000 (UTC)
Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by DB8EHSMHS028.bigfish.com (10.174.4.38) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sun, 13 Oct 2013 10:45:21 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.371.2; Sun, 13 Oct 2013 10:45:18 +0000
Message-ID: <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
Date: Sun, 13 Oct 2013 11:42: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
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: Sun, 13 Oct 2013 10:45:39 -0000

I find the security considerations in this registration rather weak.
What might have sufficed in 2005 seems to me inadequate for 2013.  I
would expect a clearer statement of what are or are not considered
threats or attacks and what mitigations there then are for them.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: <iana@iana.org>
Sent: Thursday, October 10, 2013 7:50 PM

The IESG has received a request to update the IANA registration of
the text/csv media type, adding an optional fragment identifier.
The request comes from a document in the Independent stream, and the
IESG is the change controller for the text/csv media type.

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-10-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.

The document making the request can be obtained via
http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/



From adrian@olddog.co.uk  Sun Oct 13 06:06: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 3C60C11E8140 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 06:06: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.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 932yCQOy4pRK for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 06:06:47 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id E9FB611E8146 for <ietf@ietf.org>; Sun, 13 Oct 2013 06:06:41 -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 r9DD6aNY031492;  Sun, 13 Oct 2013 14:06:36 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9DD6WU3031430 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 13 Oct 2013 14:06:33 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, "'ietf'" <ietf@ietf.org>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com>
In-Reply-To: <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
Date: Sun, 13 Oct 2013 14:06:31 +0100
Message-ID: <009701cec815$0b5b6310$22122930$@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: AQJso3IqFZUdNipH5JplInSoSAgAygFuTN3pmKtut2A=
Content-Language: en-gb
Cc: draft-ietf-mpls-tp-rosetta-stone.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, 13 Oct 2013 13:06:55 -0000

Hi,

I am having sever difficulty parsing all of the information from your comment.
And currently cannot see anything actionable by the authors.

> The draft does not list ITU in abbreviation,

Loa has answered why this is not necessary.

> there are many terminology not clear but more general definition.  I 
> prefer specific defining. 

This comment gives us nothing to go on! Which terminology do you find not clear
but is a more general definition? And why is this a problem?

You cannot expect the authors to fix or even discuss something if you do not
show them what you are talking about.

> Also many times refers to references to define without mentioning
> what was that definition,

What do you mean? Can you give an example and say how you think it should be?

> is that defined only in ITU and IETF cannot define its technology, or
> is it agreeing on a joint definition so IETF is just following ITU in some
> terms.

*This* document is seeking IETF consensus. If that consensus is reached all
definitions will be IETF definitions. If those definitions originate in ITU-T
documents, they are also ITU-T definitions. If ITU-T documents make normative
reference to IETF documents that contain definitions, those definitions are
ITU-T definitions.

Maybe I have missed the point of your comment.

Adrian


From sm@resistor.net  Sun Oct 13 07:22:51 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 631F111E8145 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:22: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 vI+EAGTUDqFI for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:22: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 7495C11E8152 for <ietf@ietf.org>; Sun, 13 Oct 2013 07:22:47 -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 r9DEMbFR004430 for <ietf@ietf.org>; Sun, 13 Oct 2013 07:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381674166; bh=qdFRdEofvhQCfhhg4RjQtY9RfqfpWCKMxHQ3Y3i4tIg=; h=Date:To:From:Subject:In-Reply-To:References; b=hydyhlsQIBr8fBy42DLwc9tMeo69esfZ+VcJQQbRrv3ivcT9t43cmMHC6+l+AVLo9 Rg4ZXBCc2Hle/5wb49qf0R88y6dU6n7MQH4RAlMHImMQ5mtOyYoz/6OzXnuY/jn+si M1H0UgQgE0K1COpIuB4Xduo8OKvecDgYj1WtQ22U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381674166; i=@resistor.net; bh=qdFRdEofvhQCfhhg4RjQtY9RfqfpWCKMxHQ3Y3i4tIg=; h=Date:To:From:Subject:In-Reply-To:References; b=DeWy2V1iqK80+BFRvT2v34c8/DSfo0T4B+AcAz4OHBbo27mnnYUWglyIaXTIrjyGV OiVHUL8DBk6qSfWzXJSGcjzvu5B0OUxw5Y3lIPL5FxNmluf+IkyXHcOGrSjh2Fb7tK o1VpaMoZWNltIh4X8/SK+14Jr0R6Ejg+u+maBNv4=
Message-Id: <6.2.5.6.2.20131013071335.0b673978@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 13 Oct 2013 07:20:58 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: WG Review: IPv6 Maintenance (6man)
In-Reply-To: <20131011163832.4882.45248.idtracker@ietfa.amsl.com>
References: <20131011163832.4882.45248.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: Sun, 13 Oct 2013 14:22:51 -0000

At 09:38 11-10-2013, The IESG wrote:
>The IPv6 Maintenance (6man) working group in the Internet Area of the
>IETF is undergoing rechartering. The IESG has not made any determination
>yet. The following draft charter was submitted, and is provided for

[snip]

>   Jul 2014 - Advance IPv6 core specifications to Internet standard

Which RFCs does the above refer to?  Is the milestone about 
delivering the work item(s) to the IESG?

Regards,
-sm 


From abdussalambaryun@gmail.com  Sun Oct 13 07:32:53 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 1AC8F21E8064 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level: 
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[AWL=-0.013, 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 ZWgQnZaN+i6i for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:32:52 -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 C6E2211E815B for <ietf@ietf.org>; Sun, 13 Oct 2013 07:32:44 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id lf10so6486213pab.17 for <ietf@ietf.org>; Sun, 13 Oct 2013 07:32: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:date:message-id:subject:from:to :cc:content-type; bh=SF7aWZlLD3puYQfmmChEedqskGR2gAuGgo7L+uS+MbE=; b=Xr3tGN+KM9m2yQPQ4unF8J33lSACiu1NL86JomrSEZsuYM1TloWkbuBUl3NcZ0VIEM uVQWSkdXqthY7JvqL2ORHUoyy7u9mqhok4THq7xkE3cjwKS5MPoJvuIc08x/3EeOKTRv WD53toJ/yq1UXUvM7+qwDwtuWB9sL8YsS6ylo/9/2NAEmEKbZYoi7i3jdvXkzCslhg8T E549q809ZbHsIlZzj5Fev4IfSZmERPfsev6LVzc5MMEHArjBGTxO1EKIIZiqSbUd/668 IGxt1F6jOoM6jxChQw+LCreeVGDHYowGdKJCwsGJycA+y5cV4DmeNblnh6rU8AvqF8rg xLAw==
MIME-Version: 1.0
X-Received: by 10.66.162.167 with SMTP id yb7mr33020821pab.16.1381674764428; Sun, 13 Oct 2013 07:32:44 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 13 Oct 2013 07:32:44 -0700 (PDT)
In-Reply-To: <009701cec815$0b5b6310$22122930$@olddog.co.uk>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com> <009701cec815$0b5b6310$22122930$@olddog.co.uk>
Date: Sun, 13 Oct 2013 16:32:44 +0200
Message-ID: <CADnDZ8_KKhj1_g-31b7SVuc=AuZwzZ3UrC2QOMx6R0jNrGW1NA@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7bacbe70876b2704e8a039bd
Cc: "draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org" <draft-ietf-mpls-tp-rosetta-stone.all@tools.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: Sun, 13 Oct 2013 14:32:53 -0000

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

Yes, my comment meant that it is a reply to the review message that there
may be not clear definition from other participant point of view. Sorry
my review is still not complete, I will send it. Do you mean my reply is
not right, if I like to give a short comment before my full review.

AB

On Sunday, October 13, 2013, Adrian Farrel wrote:

> Hi,
>
> I am having sever difficulty parsing all of the information from your
> comment.
> And currently cannot see anything actionable by the authors.
>
> > The draft does not list ITU in abbreviation,
>
> Loa has answered why this is not necessary.


You mean that IETF agrees to do that as per a RFC xxxx passed or community
awareness.

>
> > there are many terminology not clear but more general definition.  I
> > prefer specific defining.
>
> This comment gives us nothing to go on! Which terminology do you find not
> clear
> but is a more general definition? And why is this a problem?
>
> You cannot expect the authors to fix or even discuss something if you do
> not
> show them what you are talking about.

I am talking about the draft in overall, I will do my review if time is
available.

>
> > Also many times refers to references to define without mentioning
> > what was that definition,
>
> What do you mean? Can you give an example and say how you think it should
> be?

Will be shown in a full review message, this was a comment message, but
thanks for your advise

>
> > is that defined only in ITU and IETF cannot define its technology, or
> > is it agreeing on a joint definition so IETF is just following ITU in
> some
> > terms.
>
> *This* document is seeking IETF consensus. If that consensus is reached all
> definitions will be IETF definitions. If those definitions originate in
> ITU-T
> documents, they are also ITU-T definitions. If ITU-T documents make
> normative
> reference to IETF documents that contain definitions, those definitions are
> ITU-T definitions.
>
> Maybe I have missed the point of your comment.


The point is why do we need other organisation definitions, or why did the
author use those definitions, my point is any definition should relate to
internet technology not references of other org, we may use other
definitions for ours.

>
> Adrian
>
>

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

Yes, my comment meant that it is a reply to the review message that there m=
ay be not clear definition from other participant point of view. Sorry my=
=A0review is still not complete, I=A0will send it. Do you mean my reply is =
not right, if I like to give a short comment before my full review.<div>
<br></div><div>AB<br><br>On Sunday, October 13, 2013, Adrian Farrel  wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am having sever difficulty parsing all of the information from your comme=
nt.<br>
And currently cannot see anything actionable by the authors.<br>
<br>
&gt; The draft does not list ITU in abbreviation,<br>
<br>
Loa has answered why this is not necessary.</blockquote><div><br></div><div=
>You mean that IETF agrees to do that as per a RFC xxxx=A0passed or communi=
ty awareness.=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
&gt; there are many terminology not clear but more general definition. =A0I=
<br>
&gt; prefer specific defining.<br>
<br>
This comment gives us nothing to go on! Which terminology do you find not c=
lear<br>
but is a more general definition? And why is this a problem?<br>
<br>
You cannot expect the authors to fix or even discuss something if you do no=
t<br>
show them what you are talking about.</blockquote><div>I am talking about t=
he draft in overall, I will do my review if time is available.</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">

<br>
&gt; Also many times refers to references to define without mentioning<br>
&gt; what was that definition,<br>
<br>
What do you mean? Can you give an example and say how you think it should b=
e?</blockquote><div>Will be shown in a full review message, this was a comm=
ent message, but thanks for your advise=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

<br>
&gt; is that defined only in ITU and IETF cannot define its technology, or<=
br>
&gt; is it agreeing on a joint definition so IETF is just following ITU in =
some<br>
&gt; terms.<br>
<br>
*This* document is seeking IETF consensus. If that consensus is reached all=
<br>
definitions will be IETF definitions. If those definitions originate in ITU=
-T<br>
documents, they are also ITU-T definitions. If ITU-T documents make normati=
ve<br>
reference to IETF documents that contain definitions, those definitions are=
<br>
ITU-T definitions.<br>
<br>
Maybe I have missed the point of your comment.</blockquote><div><br></div><=
div>The point is why do we need other organisation definitions, or why did =
the author use those definitions, my point is any definition should relate =
to internet=A0technology not references of other org, we may use other defi=
nitions for ours.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Adrian<br>
<br>
</blockquote></div>

--047d7bacbe70876b2704e8a039bd--

From abdussalambaryun@gmail.com  Sun Oct 13 07:42: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 7B50211E8156 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[AWL=-0.012, 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 XWHb4ClqYaoP for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 07:42:30 -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 C872B21F9E68 for <ietf@ietf.org>; Sun, 13 Oct 2013 07:42:26 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so6286641pbc.37 for <ietf@ietf.org>; Sun, 13 Oct 2013 07:42: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=8iavlVhE0rggTZo3pkDT57KuYtudPGsci+IbhyXy4Vg=; b=fhled1zZERXkwb/aLYajf1o+Ecmv0YFwTMRiBM7yiIQpPwbrURicLdTcjlUsrZM9Wf R7z68Og1rJYW2xlqlx14rgtwggHpLxZldKzlsfAQ1DgwgZ00Cpxa6RvOsXzwfY0B2TY/ 3yKQ5uPzHpLUwjTKD7GUvQSlfhmiYYTU9S8by3lGiQ3pszv7l2ExQPzpX7nKqIdjJM/k nj52ABkvc7iHcvRqcdh8yQUKKAXEgHhhHHKq4o+uDSG1Ndrx/DQ7+c4tlG7Zh+AnvEwN x4kqF9ENkInJvRdiruCjtFMBwnsCfT4dZpZxNx9EikqU8N48st8tmLmsUYLy3e/tmlXY +Rxw==
MIME-Version: 1.0
X-Received: by 10.66.162.73 with SMTP id xy9mr819241pab.172.1381675346603; Sun, 13 Oct 2013 07:42:26 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 13 Oct 2013 07:42:26 -0700 (PDT)
In-Reply-To: <CAKRbAfDbZWENX3VF1TF8PEJA+-D047QGzDsZ8GrQwLoJqxkniw@mail.gmail.com>
References: <002c01cec75a$66381aa0$32a84fe0$@olddog.co.uk> <CAKRbAfDbZWENX3VF1TF8PEJA+-D047QGzDsZ8GrQwLoJqxkniw@mail.gmail.com>
Date: Sun, 13 Oct 2013 16:42:26 +0200
Message-ID: <CADnDZ8-Rn++armXDCEOU7osBgiZLf5ek5if4QGmHvF93=NX1uw@mail.gmail.com>
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bacc3ca3ab45f04e8a05c82
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, S Moonesamy <sm+ietf@elandsys.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, 13 Oct 2013 14:42:30 -0000

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

The DT I am discussing has no clear problem to solve, the appointment is
not clear, I have been asking for a WG but only DT was done. The DT has no
milestones and no clear objectives, is it a DT or a WG. We don't need the
DT to adopt or agree on any real draft effort submitted, it is the
community that adopt or disagrees the output of any DT.

AB

On Saturday, October 12, 2013, Melinda Shore wrote:

> On Oct 12, 2013 6:51 AM, "Adrian Farrel" <adrian@olddog.co.uk<javascript:_e({}, 'cvml', 'adrian@olddog.co.uk');>>
> wrote:
> > I don't understand your assertion that there is no procedure in the IETF
> to
> > support the existence of a Design Team.
>
> I'd be sorry to see this discussion dragged down a procedural rathole.
>
> Melinda
>

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

The DT I am discussing has no clear problem to solve, the appointment is no=
t clear, I have been asking for a WG but only DT was done. The DT has no mi=
lestones and no clear objectives, is it a DT or a WG. We don&#39;t need the=
 DT to adopt or agree on any real draft effort submitted, it is the communi=
ty that adopt or disagrees the output of any DT.<div>
<br></div><div>AB<br><div><br>On Saturday, October 12, 2013, Melinda Shore =
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><p>On Oct 12, 2013 6:51 AM, &quot=
;Adrian Farrel&quot; &lt;<a href=3D"javascript:_e({}, &#39;cvml&#39;, &#39;=
adrian@olddog.co.uk&#39;);" target=3D"_blank">adrian@olddog.co.uk</a>&gt; w=
rote:<br>

&gt; I don&#39;t understand your assertion that there is no procedure in th=
e IETF to<br>
&gt; support the existence of a Design Team.</p>
<p>I&#39;d be sorry to see this discussion dragged down a procedural rathol=
e.</p>
<p>Melinda <br>
</p>
</blockquote></div></div>

--047d7bacc3ca3ab45f04e8a05c82--

From joelja@bogus.com  Sun Oct 13 11:36:11 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 47B8921E80D4 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 11:36:11 -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 VYdl+-wI6rVj for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 11:36:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C0B4721F93E4 for <ietf@ietf.org>; Sun, 13 Oct 2013 11:36:10 -0700 (PDT)
Received: from [192.168.1.13] (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9DIa7HC096320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 13 Oct 2013 18:36:08 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_275C85D6-5C81-4FDA-BF0A-8CCCFE848F50"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <CADnDZ8_KKhj1_g-31b7SVuc=AuZwzZ3UrC2QOMx6R0jNrGW1NA@mail.gmail.com>
Date: Sun, 13 Oct 2013 11:36:04 -0700
Message-Id: <C2D323B2-9910-4417-8AD0-9073B7A1414F@bogus.com>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com> <009701cec815$0b5b6310$22122930$@olddog.co.uk> <CADnDZ8_KKhj1_g-31b7SVuc=AuZwzZ3UrC2QOMx6R0jNrGW1NA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 13 Oct 2013 18:36:09 +0000 (UTC)
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org" <draft-ietf-mpls-tp-rosetta-stone.all@tools.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: Sun, 13 Oct 2013 18:36:11 -0000

--Apple-Mail=_275C85D6-5C81-4FDA-BF0A-8CCCFE848F50
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 13, 2013, at 7:32 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Yes, my comment meant that it is a reply to the review message that =
there may be not clear definition from other participant point of view. =
Sorry my review is still not complete, I will send it. Do you mean my =
reply is not right, if I like to give a short comment before my full =
review.
>=20
> AB
>=20
> On Sunday, October 13, 2013, Adrian Farrel wrote:
> Hi,
>=20
> I am having sever difficulty parsing all of the information from your =
comment.
> And currently cannot see anything actionable by the authors.
>=20
> > The draft does not list ITU in abbreviation,
>=20
> Loa has answered why this is not necessary.
>=20
> You mean that IETF agrees to do that as per a RFC xxxx passed or =
community awareness.=20
>=20
> > there are many terminology not clear but more general definition.  I
> > prefer specific defining.
>=20
> This comment gives us nothing to go on! Which terminology do you find =
not clear
> but is a more general definition? And why is this a problem?
>=20
> You cannot expect the authors to fix or even discuss something if you =
do not
> show them what you are talking about.
> I am talking about the draft in overall, I will do my review if time =
is available.
>=20

Insubstantial comments during the last call by someone who claims to =
have not reviewed the document are rather condescending. If you were the =
author what would you do with this "feedback"?=20

Expectations of collegiality require a certain respect for common =
purpose, and the purpose of the last call is to surface remaining issues =
of substance, test for consensus and move on. (2418 section 8)

> > Also many times refers to references to define without mentioning
> > what was that definition,
>=20
> What do you mean? Can you give an example and say how you think it =
should be?
> Will be shown in a full review message, this was a comment message, =
but thanks for your advise=20
>=20
> > is that defined only in ITU and IETF cannot define its technology, =
or
> > is it agreeing on a joint definition so IETF is just following ITU =
in some
> > terms.
>=20
> *This* document is seeking IETF consensus. If that consensus is =
reached all
> definitions will be IETF definitions. If those definitions originate =
in ITU-T
> documents, they are also ITU-T definitions. If ITU-T documents make =
normative
> reference to IETF documents that contain definitions, those =
definitions are
> ITU-T definitions.
>=20
> Maybe I have missed the point of your comment.
>=20
> The point is why do we need other organisation definitions, or why did =
the author use those definitions, my point is any definition should =
relate to internet technology not references of other org, we may use =
other definitions for ours.
>=20
> Adrian
>=20


--Apple-Mail=_275C85D6-5C81-4FDA-BF0A-8CCCFE848F50
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJa6BQACgkQ8AA1q7Z/VrKW3ACfXSVD+GtK1lnkLctcyEb2Ccur
Uy4AnjtAn4Fl5qqRRpBbbsoocj9jFfZn
=0h8/
-----END PGP SIGNATURE-----

--Apple-Mail=_275C85D6-5C81-4FDA-BF0A-8CCCFE848F50--

From brian.e.carpenter@gmail.com  Sun Oct 13 12:16: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 ACD1C21E811D for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 12:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 Y12ib7a6xHAr for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 12:16:17 -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 EE1B421E8090 for <ietf@ietf.org>; Sun, 13 Oct 2013 12:16:14 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so6448370pbb.34 for <ietf@ietf.org>; Sun, 13 Oct 2013 12:16:14 -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=bRZBNRE3rESaQBgXX2D6cpTZB/pyXlCR7Ba6Eneu7zA=; b=riFxW/l7YPYeJdVFYEVFb76sM7vmtS1EjRdsOvcch9hg8UMpjU7l9Bre0dV5QOOgro 3TzWkbm/LoLpJqppfhHmgc8M6f5Fkv3ifr3FdbjGk6pyrwk8USo2/9FyoeRx5vzR6jcC 21OYFp1Hl5QInPyV0W/r8eAQGpZgsuJzy9Tj4Wjx6qGkcYip6VO+RsKmQqT7Ox7ncO9S i/XkjVPNyI7FwSzDl637Sy64Z5BD9GKGP4lF1mQ7adRaHTO0Q097lxuRlRdi17FZts2y 8n0PCfl4nSTz4Gd/aM39R73HGyDnYLeLB2TyZq97WQZkqaROmdnha5iJHewgORybwW7W brXA==
X-Received: by 10.68.229.167 with SMTP id sr7mr30608pbc.159.1381691774600; Sun, 13 Oct 2013 12:16:14 -0700 (PDT)
Received: from [192.168.178.20] (172.200.69.111.dynamic.snap.net.nz. [111.69.200.172]) by mx.google.com with ESMTPSA id ed3sm73424768pbc.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Oct 2013 12:16:13 -0700 (PDT)
Message-ID: <525AF17A.6090806@gmail.com>
Date: Mon, 14 Oct 2013 08:16:10 +1300
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: Terms and Conditions May Apply
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, 13 Oct 2013 19:16:17 -0000

I know we don't normally do movie plugs on this list, but anyone
who's planning to attend the technical plenary in Vancouver
could do worse than watch "Terms and Conditions May Apply".
It covers both commercial and governmental invasions of privacy,
and how they are interlinked.

http://www.imdb.com/title/tt2084953/

or

http://tacma.net/ (but you might not want to click
on the 'I agree' button until you've seen the movie...)

   Brian

From abdussalambaryun@gmail.com  Sun Oct 13 13:00:54 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 C553721E811D for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 13:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[AWL=-0.012, 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 mcQZI9dL6BOj for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 13:00:53 -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 A337621E8129 for <ietf@ietf.org>; Sun, 13 Oct 2013 13:00:51 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un15so6497971pbc.1 for <ietf@ietf.org>; Sun, 13 Oct 2013 13:00:51 -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=wLbxTHxaLLldiBLLYjDlg6NAPn653izC031oCr5gPc4=; b=MeUoZ9H0JoS0u98t+Z4l//36bKIMmUfWftmc6rbktd7xc54CgNTmtHnSvNuI9vfbBg B90KogfFCToia2H+iufH7/cenhDhlc2uVnULDQg78B5ZBsQYG0z4SG1U6ocsbIvrFzDX RlaHblGIUgmSSIe3Z36Vru0st7u999ZkQTZwBnWu3kyN8NPtehB5YM1umwiYZACAFXMd TxVLyr2iO1sQCz5eKPt8ZNAu0P2xbuR+YRZvXzSNbNoKuaE9Ev/1sr1yi7nlfYWOItM5 8WMBDTN/Lw3hEvw2U7fjD3ut20Su7OwvWB3QDzMEM8nWNSmEjaJB2doJakYmiFppo1yU V3PA==
MIME-Version: 1.0
X-Received: by 10.66.175.133 with SMTP id ca5mr34353821pac.40.1381694451328; Sun, 13 Oct 2013 13:00:51 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 13 Oct 2013 13:00:51 -0700 (PDT)
In-Reply-To: <C2D323B2-9910-4417-8AD0-9073B7A1414F@bogus.com>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com> <009701cec815$0b5b6310$22122930$@olddog.co.uk> <CADnDZ8_KKhj1_g-31b7SVuc=AuZwzZ3UrC2QOMx6R0jNrGW1NA@mail.gmail.com> <C2D323B2-9910-4417-8AD0-9073B7A1414F@bogus.com>
Date: Sun, 13 Oct 2013 22:00:51 +0200
Message-ID: <CADnDZ8_aJg3ZAh9_vsdVUXyvgyf4PbCp=3Mf1VQmv-K75nQY-Q@mail.gmail.com>
Subject: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=047d7bdca3fef5ab6504e8a4cea7
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org" <draft-ietf-mpls-tp-rosetta-stone.all@tools.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: Sun, 13 Oct 2013 20:00:54 -0000

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

 A comment can be a discussion/opinion for the draft that is at the IETF
level, I did review but not completed writing the output. However, my
comment may influenced comments today at WG level (usually the draft passed
such review of WG LC) which did not send there comments  to the IETF list,
but the authors are gaining so far. I prefer that all comments should be at
the IETF list after the IETF LC to give chance for discussion if needed (as
a community DISCUSS position).

AB

On Sunday, October 13, 2013, joel jaeggli wrote:

>
> On Oct 13, 2013, at 7:32 AM, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
> > Yes, my comment meant that it is a reply to the review message that
> there may be not clear definition from other participant point of view.
> Sorry my review is still not complete, I will send it. Do you mean my reply
> is not right, if I like to give a short comment before my full review.
> >
> > AB
> >
> > On Sunday, October 13, 2013, Adrian Farrel wrote:
> > Hi,
> >
> > I am having sever difficulty parsing all of the information from your
> comment.
> > And currently cannot see anything actionable by the authors.
> >
> > > The draft does not list ITU in abbreviation,
> >
> > Loa has answered why this is not necessary.
> >
> > You mean that IETF agrees to do that as per a RFC xxxx passed or
> community awareness.
> >
> > > there are many terminology not clear but more general definition.  I
> > > prefer specific defining.
> >
> > This comment gives us nothing to go on! Which terminology do you find
> not clear
> > but is a more general definition? And why is this a problem?
> >
> > You cannot expect the authors to fix or even discuss something if you do
> not
> > show them what you are talking about.
> > I am talking about the draft in overall, I will do my review if time is
> available.
> >
>
> Insubstantial comments during the last call by someone who claims to have
> not reviewed the document are rather condescending. If you were the author
> what would you do with this "feedback"?
>
> Expectations of collegiality require a certain respect for common purpose,
> and the purpose of the last call is to surface remaining issues of
> substance, test for consensus and move on. (2418 section 8)
>
> > > Also many times refers to references to define without mentioning
> > > what was that definition,
> >
> > What do you mean? Can you give an example and say how you think it
> should be?
> > Will be shown in a full review message, this was a comment message, but
> thanks for your advise
> >
> > > is that defined only in ITU and IETF cannot define its technology, or
> > > is it agreeing on a joint definition so IETF is just following ITU in
> some
> > > terms.
> >
> > *This* document is seeking IETF consensus. If that consensus is reached
> all
> > definitions will be IETF definitions. If those definitions originate in
> ITU-T
> > documents, they are also ITU-T definitions. If ITU-T documents make
> normative
> > reference to IETF documents that contain definitions, those definitions
> are
> > ITU-T definitions.
> >
> > Maybe I have missed the point of your comment.
> >
> > The point is why do we need other organisation definitions, or why did
> the author use those definitions, my point is any definition should relate
> to internet technology not references of other org, we may use other
> definitions for ours.
> >
> > Adrian
> >
>
>

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

=A0A comment can be a discussion/opinion=A0for the draft=A0that is at=A0the=
 IETF level, I did review but not completed writing the output. However, my=
 comment may influenced comments today at=A0WG level (usually the draft pas=
sed such review of WG LC)=A0which did not send there comments =A0to=A0the I=
ETF list, but the authors are gaining so far. I prefer that all comments sh=
ould be at the IETF list after the IETF LC to give chance for discussion if=
 needed (as a community DISCUSS position).<div>
<span></span><div>
<br></div><div>AB<br><br>On Sunday, October 13, 2013, joel jaeggli  wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><br>
On Oct 13, 2013, at 7:32 AM, Abdussalam Baryun &lt;<a>abdussalambaryun@gmai=
l.com</a>&gt; wrote:<br>
<br>
&gt; Yes, my comment meant that it is a reply to the review message that th=
ere may be not clear definition from other participant point of view. Sorry=
 my review is still not complete, I will send it. Do you mean my reply is n=
ot right, if I like to give a short comment before my full review.<br>


&gt;<br>
&gt; AB<br>
&gt;<br>
&gt; On Sunday, October 13, 2013, Adrian Farrel wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; I am having sever difficulty parsing all of the information from your =
comment.<br>
&gt; And currently cannot see anything actionable by the authors.<br>
&gt;<br>
&gt; &gt; The draft does not list ITU in abbreviation,<br>
&gt;<br>
&gt; Loa has answered why this is not necessary.<br>
&gt;<br>
&gt; You mean that IETF agrees to do that as per a RFC xxxx passed or commu=
nity awareness.<br>
&gt;<br>
&gt; &gt; there are many terminology not clear but more general definition.=
 =A0I<br>
&gt; &gt; prefer specific defining.<br>
&gt;<br>
&gt; This comment gives us nothing to go on! Which terminology do you find =
not clear<br>
&gt; but is a more general definition? And why is this a problem?<br>
&gt;<br>
&gt; You cannot expect the authors to fix or even discuss something if you =
do not<br>
&gt; show them what you are talking about.<br>
&gt; I am talking about the draft in overall, I will do my review if time i=
s available.<br>
&gt;<br>
<br>
Insubstantial comments during the last call by someone who claims to have n=
ot reviewed the document are rather condescending. If you were the author w=
hat would you do with this &quot;feedback&quot;?<br>
<br>
Expectations of collegiality require a certain respect for common purpose, =
and the purpose of the last call is to surface remaining issues of substanc=
e, test for consensus and move on. (2418 section 8)<br>
<br>
&gt; &gt; Also many times refers to references to define without mentioning=
<br>
&gt; &gt; what was that definition,<br>
&gt;<br>
&gt; What do you mean? Can you give an example and say how you think it sho=
uld be?<br>
&gt; Will be shown in a full review message, this was a comment message, bu=
t thanks for your advise<br>
&gt;<br>
&gt; &gt; is that defined only in ITU and IETF cannot define its technology=
, or<br>
&gt; &gt; is it agreeing on a joint definition so IETF is just following IT=
U in some<br>
&gt; &gt; terms.<br>
&gt;<br>
&gt; *This* document is seeking IETF consensus. If that consensus is reache=
d all<br>
&gt; definitions will be IETF definitions. If those definitions originate i=
n ITU-T<br>
&gt; documents, they are also ITU-T definitions. If ITU-T documents make no=
rmative<br>
&gt; reference to IETF documents that contain definitions, those definition=
s are<br>
&gt; ITU-T definitions.<br>
&gt;<br>
&gt; Maybe I have missed the point of your comment.<br>
&gt;<br>
&gt; The point is why do we need other organisation definitions, or why did=
 the author use those definitions, my point is any definition should relate=
 to internet technology not references of other org, we may use other defin=
itions for ours.<br>


&gt;<br>
&gt; Adrian<br>
&gt;<br>
<br>
</blockquote></div>
</div>

--047d7bdca3fef5ab6504e8a4cea7--

From huubatwork@gmail.com  Sun Oct 13 14:24:02 2013
Return-Path: <huubatwork@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 E8DEC21F8A84 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 14:24: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 T3L78UpiP8qD for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 14:24:02 -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 EE93B21F9950 for <ietf@ietf.org>; Sun, 13 Oct 2013 14:24:00 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id h14so3015584eak.29 for <ietf@ietf.org>; Sun, 13 Oct 2013 14:24:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=qcoFXsvKXeGVR7A3UV/LDfBk9lcTQuRuwV2RPGFJKs0=; b=JtUZDdEMD3lB7/gdN5g9L9k4tJ3nq9xnyNezOZh4FGLKGCXKqSN1qaYin4yEB3ULKp +ya+VNdjHnG9D5//ZX0ZsgqQkKl0n5uVJ9aOtNCa39AiFkrViZkrHd7ndz2Ebv8013d7 jUUVMykHOJrhyXHQVT47Qtn1l5QuJsT2Btz0ta9kCXbRBtHQzZkTN3htbUytO4U9RORP 0aIylhuNUuXPXF0Afc2Ul5wc383N5bJEFOQ/LoJTkYa8uuzZTBSt8G04PxjJsfThsOHN 12i0wXain6DwSyqFUCmU7DB8TxPoGYwjjozXt8TRqZx+p+Zj6HpWw0ZfONmLtrmLTT9R rMgg==
X-Received: by 10.14.180.73 with SMTP id i49mr126487eem.55.1381699440165; Sun, 13 Oct 2013 14:24:00 -0700 (PDT)
Received: from McAsterix.local (g215085.upc-g.chello.nl. [80.57.215.85]) by mx.google.com with ESMTPSA id n48sm145123052eeg.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Oct 2013 14:23:59 -0700 (PDT)
Message-ID: <525B0F6D.7080900@gmail.com>
Date: Sun, 13 Oct 2013 23:23:57 +0200
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com> <CADnDZ89Foc_FY4=GXxModh5v=3JEtEJoJq0Q+WF0so-2kJt9eQ@mail.gmail.com> <009701cec815$0b5b6310$22122930$@olddog.co.uk> <CADnDZ8_KKhj1_g-31b7SVuc=AuZwzZ3UrC2QOMx6R0jNrGW1NA@mail.gmail.com> <C2D323B2-9910-4417-8AD0-9073B7A1414F@bogus.com> <CADnDZ8_aJg3ZAh9_vsdVUXyvgyf4PbCp=3Mf1VQmv-K75nQY-Q@mail.gmail.com>
In-Reply-To: <CADnDZ8_aJg3ZAh9_vsdVUXyvgyf4PbCp=3Mf1VQmv-K75nQY-Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org" <draft-ietf-mpls-tp-rosetta-stone.all@tools.ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@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: Sun, 13 Oct 2013 21:24:03 -0000

AB,

You wrote:

> but the authors are gaining so far.

That may be your opinion.
But it is absolutely not my opinion.

As the author of this draft I have worked four years to
address all the comments received, and improve the quality
of the document.

So you had four years to review and comment.
Yet you wait until four days before the deadline set by IESG
to announce that you have substantial comments.

I am now completely lost, and have lost too.

/Huub.


-- 
*****************************************************************
               čŻ·č®°ä˝ŹďĽŚä˝ ć�Żç‹¬ä¸€ć— äşŚçš„ďĽŚĺ°±ĺ�Źĺ…¶ä»–ćŻŹä¸€ä¸Şäşşä¸€ć ·

From rbonica@juniper.net  Sun Oct 13 16:55:42 2013
Return-Path: <rbonica@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 74DF621E80A3 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 16:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.016
X-Spam-Level: 
X-Spam-Status: No, score=-103.016 tagged_above=-999 required=5 tests=[AWL=-0.417, 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 1jK4wtHXBUIZ for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 16:55:36 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) by ietfa.amsl.com (Postfix) with ESMTP id CD46721E814A for <ietf@ietf.org>; Sun, 13 Oct 2013 16:55:29 -0700 (PDT)
Received: from mail68-db9-R.bigfish.com (10.174.16.245) by DB9EHSOBE033.bigfish.com (10.174.14.96) with Microsoft SMTP Server id 14.1.225.22; Sun, 13 Oct 2013 23:55:28 +0000
Received: from mail68-db9 (localhost [127.0.0.1])	by mail68-db9-R.bigfish.com (Postfix) with ESMTP id C18B9360145; Sun, 13 Oct 2013 23:55:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(zz98dI9371I936eI542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail68-db9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(199002)(189002)(51704005)(13464003)(377424004)(377454003)(24454002)(47446002)(74502001)(83072001)(54356001)(31966008)(19580395003)(83322001)(53806001)(19580405001)(51856001)(74662001)(33646001)(85306002)(66066001)(80022001)(65816001)(80976001)(79102001)(74316001)(63696002)(46102001)(4396001)(76482001)(81686001)(56776001)(49866001)(54316002)(74366001)(47736001)(74876001)(81542001)(74706001)(47976001)(50986001)(81816001)(81342001)(77982001)(59766001)(76786001)(76796001)(76576001)(56816003)(77096001)(69226001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB444; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail68-db9 (localhost.localdomain [127.0.0.1]) by mail68-db9 (MessageSwitch) id 1381708526807622_2038; Sun, 13 Oct 2013 23:55:26 +0000 (UTC)
Received: from DB9EHSMHS010.bigfish.com (unknown [10.174.16.228])	by mail68-db9.bigfish.com (Postfix) with ESMTP id B6A6D160063; Sun, 13 Oct 2013 23:55:26 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS010.bigfish.com (10.174.14.20) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sun, 13 Oct 2013 23:55:26 +0000
Received: from CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.371.2; Sun, 13 Oct 2013 23:55:26 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.0.785.10; Sun, 13 Oct 2013 23:55:23 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.14]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.50]) with mapi id 15.00.0785.001; Sun, 13 Oct 2013 23:55:23 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOv6KsdJvRhXd90UuLWVq4yr1RsZnyIt4AgAE9DsA=
Date: Sun, 13 Oct 2013 23:55:21 +0000
Message-ID: <42ae3f3e73f840e2b40e62430cf8f7d7@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131012194048.0c92f558@resistor.net>
In-Reply-To: <6.2.5.6.2.20131012194048.0c92f558@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0998671D02
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
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: Sun, 13 Oct 2013 23:55:42 -0000

SM,

Are you suggesting that we don't address the problem because the code is to=
o complex to touch?

                                         Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> SM
> Sent: Sunday, October 13, 2013 1:00 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> At 11:55 02-10-2013, The IESG wrote:
> >The IESG has received a request from the IPv6 Maintenance WG (6man) to
> >consider the following document:
> >- 'Implications of Oversized IPv6 Header Chains'
> >   <draft-ietf-6man-oversized-header-chain-08.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
>=20
> This document intends to update the IPv6 specification.  I looked into
> some code (host) which would be affected by the RFC 2119 requirement in
> Section 5.  The code is complex as it is.  I am not sure whether the
> requirement can be implemented without too much difficulty.  I have not
> looked into the code which processes inbound packets.
>=20
> Regards,
> -sm
>=20
>=20
>=20



From gem@rellim.com  Sun Oct 13 18:28:50 2013
Return-Path: <gem@rellim.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D84EC21E8094 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 18:28:50 -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 LtZhLwS9xIG6 for <ietf@ietfa.amsl.com>; Sun, 13 Oct 2013 18:28:50 -0700 (PDT)
Received: from catbert.rellim.com (gem-1-pt.tunnel.tserv14.sea1.ipv6.he.net [IPv6:2001:470:a:48::2]) by ietfa.amsl.com (Postfix) with ESMTP id C847E21E8098 for <ietf@ietf.org>; Sun, 13 Oct 2013 18:28:47 -0700 (PDT)
Received: from localhost (spidey.rellim.com [IPv6:2001:470:e815::8]) (authenticated bits=0) by catbert.rellim.com (8.14.7/8.14.7) with ESMTP id r9E1SgTs026183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 13 Oct 2013 18:28:43 -0700
X-DKIM: OpenDKIM Filter v2.6.7 catbert.rellim.com r9E1SgTs026183
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=rellim.com; s=catbert; t=1381714124; bh=N/X+IJf/ZyKejmFIgUHCzuw2uGwlGdnDLTNKTTvsRAA=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=jgqFU1V1658yn4t/JJTL/IqVu0YE/p1MUzazJQo7qO7UXTLoUzI5l0lMSThkFdAo5 HH4/rkwefAXCvyEqsvovA==
Date: Sun, 13 Oct 2013 18:28:36 -0700
From: "Gary E. Miller" <gem@rellim.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Terms and Conditions May Apply
Message-ID: <20131013182836.054d2290.gem@rellim.com>
In-Reply-To: <525AF17A.6090806@gmail.com>
References: <525AF17A.6090806@gmail.com>
Organization: Rellim
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/shBDzr.nyxrkLmxv5eoLLRp"; protocol="application/pgp-signature"
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, 14 Oct 2013 01:28:51 -0000

--Sig_/shBDzr.nyxrkLmxv5eoLLRp
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Yo Brian!

On Mon, 14 Oct 2013 08:16:10 +1300
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> I know we don't normally do movie plugs on this list, but anyone
> who's planning to attend the technical plenary in Vancouver
> could do worse than watch "Terms and Conditions May Apply".

+1.  I just saw it at the Bend Film Festival.  Good overview of
the state of privacy in the USA, pre-Snowden.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

--Sig_/shBDzr.nyxrkLmxv5eoLLRp
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJSW0jKAAoJEA0O2UlB0XnYn/YH/3jdwo0B/bJQ05BQ52r/9uPF
o64cITaQKjxTVAX7vnIGiSoUgW3BNrCzJaD4I7NhaWX8JttX6vBHvmWODKvES+Ic
O+w9nFKRWGEg+oQeym6+MTm8sKXYB+MsuxgqSck3gkZt/9AM6n5K0VlKKx6MkPFc
cqg2XZmZtQNw2x0hpMtkTnHfE3sJOXE6pg10iYzYa06sBZaYS+3FD6ocxl20RvAe
osSnnolqCwy0bKWL92i0qADqRBgBgoB6Q6yfrTcy1HQOrl/UCYBcPgTfpCSPHcR2
TRii1xUadOLIjLP5rBKmirkuHFgbauKQQloKuAbA5Xe/zHRkH+zI1Fyxdtj0XWY=
=2SRH
-----END PGP SIGNATURE-----

--Sig_/shBDzr.nyxrkLmxv5eoLLRp--

From v6ops@globis.net  Fri Oct 11 09:59:02 2013
Return-Path: <v6ops@globis.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 8DAB421F9E9F; Fri, 11 Oct 2013 09:59: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 l8Pc0PoXEmdv; Fri, 11 Oct 2013 09:59:01 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C29F811E8143; Fri, 11 Oct 2013 09:58:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 73114870085; Fri, 11 Oct 2013 18:58:35 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AiIKfe4VVWVu; Fri, 11 Oct 2013 18:58:35 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 3AF11870077; Fri, 11 Oct 2013 18:58:35 +0200 (CEST)
Message-ID: <52582E39.6030109@globis.net>
Date: Fri, 11 Oct 2013 18:58:33 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812C105@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 13 Oct 2013 18:28:55 -0700
Cc: 6man Mailing List <ipv6@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: Fri, 11 Oct 2013 16:59:02 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 11 October 2013 17:33
> Hi Ray,
>
>> -----Original Message-----
>> From: Ray Hunter [mailto:v6ops@globis.net]
>> Sent: Friday, October 11, 2013 12:49 AM
>> To: Templin, Fred L; brian.e.carpenter@gmail.com
>> Cc: ietf@ietf.org; 6man Mailing List
>> Subject: Re: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed
>> Standard
>>
>> Templin, Fred L wrote:
>>> Hi Brian,
>>>
>>> Responding in a slightly re-arranged order:
>>>
>>>> The problem is that you are asserting that middleboxes that a tunnel
>>>> passes through are expected to examine the complete header chain of
>>>> the encapsulated packet even if the encapsulated packet is a
>> fragment.
>>> Yes, but change "are expected to" to "should be able to".
>> I personally don't see this going anywhere.
>>
>> Unless you specifically define what is a "tunnel" and you specifically
>> define a maximum depth of nesting.
>>
>> The term Upper-Layer Protocol (ULP) is also itself a vague term IMHO
>> since the value of the "IPv6 next header" is taken from the same code
>> space as the ULP header values, and there's no specific marker or
>> "header length" field in IPv6 that explicitly marks a point as "This is
>> the end of the IPv6 header chain in all circumstances: stop header
>> parsing here."
>>
>> Ok, there's a bunch of current code-points that are today considered as
>> valid ULP's or next-header values, but that is neither time invariant
>> nor exhaustive, so solving this issue via a registry means there will
>> always be middlebox code in the wild that lags any updates.
>>
>> These middleboxes won't be able to differentiate between an unknown
>> ULP,
>> and an unknown IPv6 next-header. That potentially makes a default pass
>> or drop decision awkward.
>>
>> If it's so important to be able to differentiate between what is an ULP
>> and what is a next header, and we can't reliably do that today, maybe
>> that's a fundamental flaw in IPv6 that should be addressed.
>>
>>
>>>> I think that's an unreasonable expectation. A reasonable expectation
>>>> is that middleboxes should identify the encapsulated packet as
>>>> a payload that they cannot analyse, and let it go (unless they
>>>> have a policy setting to drop tunnelled packets, which is a
>>>> different discussion).
>>> But why? If headers beyond the first IPv6 encapsulation header are
>>> available in the clear, the middlebox should be able to parse them
>>> if it wants to. Wireshark already does exactly that - it keeps on
>>> parsing beyond the first encapsulation header up to and including
>>> the true ULP header. And, if Wireshark can do it, so can any other
>>> middlebox that believes security would be improved by continuing
>>> to parse the entire chain - whether or not there is a standard
>>> saying it must not do so.
>> Because it leaves open the possibility for an attacker to apply the
>> obfuscation we seek to limit.
>>
>>
>>> Parsing the additional headers beyond the first encapsulation header
>>> provides defense-in-depth. Perimeter middleboxes can then weed out
>>> the bad stuff without either allowing the bad stuff to penetrate more
>>> deeply into the organization or dropping good stuff that should be
>>> allowed through.
>> There's also a myriad of tunneling technology out there.
>>
>> Again, what is an ULP? Where do you stop parsing?
>
> The middlebox stops parsing when it decides it has seen enough.

Which AFAIK is undefined in practical terms. Especially in the presence
of jumbo payload extension headers or fragments.

So are you saying the current draft has no value?

>  With
> Wireshark at least, it blasts right through encapsulating IP headers
> and continues up to and including the ultimate TCP/UDP/ICMP etc.
> header inserted by the original host.

I like wireshark.

But how would that parsing model work in a live network without
maintaining state between frames (and leaving your middlebox open to DoS
or other resource depletion abuse)?

IMHO "ultimate TCP/UDP/ICMP etc." is not defined. The IETF does not
define standard protocol stacks as a totality. HTTP over TCP over IPv6
over L2TP over GRE over PPTP VPN over IPv6 over IPv6 is not illegal. So
this would seem to require far tighter specs on packet formats than the
IETF would ever publish (and rightly so).



>  The goal is to give the
> middlebox enough information so that it can parse as deeply into
> the headers as it wants to.

If that is the goal then we probably need to deprecate IPv6
fragmentation as well as a whole bunch of tunnel / encryption protocols
IMHO, and specify that the entire packet has to fit in a single frame.
Which I feel is unrealistic.
>> Is GRE a tunnel or an ULP? (GRE can run over almost anything)
>> Is SSH an ULP or a tunnel? (port tunneling)
>> Is Teredo a tunnel or is it an ULP (UDP) or both?
>> GRE/ LT2P over HTTP anyone?
>>
>> The notion of "perimeter" is moveable in the presence of such tunnels.
>
> We will want for middleboxes at outer perimeters to be able to parse
> as many headers as they want to before releasing the packet to
> middleboxes at inner perimenters. Otherwise, bad stuff can get past
> the outermost perimeters and waste bandwidth and/or cause havoc
> within the protected zone. 

Right. But if your firewall (which now has to maintain state, or which
is forced to parse right to the end of a packet) itself becomes the
bottleneck and the DoS target, what have you gained?

>> Presumably there comes a point where the tunnel is terminated and the
>> transported packet is de-encapsulated, and that IMHO forms another
>> perimeter where you'd anyway have to apply further security checks.
>
> Nested tunnels give you perimeters within perimeters, yes. But, we
> will want the outer perimeters to be able to parse as deeply as
> they want to before passing on to an inner perimeter.

I think my customers will have to start thinking in terms of an onion
skin model, rather than a single outer perimeter and a single "trusted"
zone.
Maintaining state, or full-packet-depth parsing, at the point where the
enterprise hits the Internet is probably not going to fly.
>
>> I think the draft does what it can in a pragmatic manner, but might
>> benefit from some acknowledgement that this security approach of
>> applying parsing at a single perimeter can never ever catch all
>> variants
>> of transporting FOO over BAR.
>>
>> IMHO It's only at the moment of de-encapsulation that the full
>> semantics
>> of the payload are revealed in these modern times of "everything
>> transported over HTTP".
>>
>>
>>
>>
>>>> Since the problem recurses as we tunnel tunnels, I don't see how any
>>>> finite limit can solve the problem. 1280 itself is a pragmatic
>> choice
>>>> of "a bit shorter than 1500".
>> Agreed.
>
> I guess I will have to repeat myself from what I said several
> months ago. The 1280 came from a desire to have multiple nested
> tunnels without requiring the tunnels to fragment since the
> underlying links presumably all configure a 1500 MTU. But, what
> would that look like in real life?
>
> - The first tunnel would have to configure a 1280 MTU so that its
>   encapsulated packets emerged as 1320
> - the second tunnel would have to configure a 1320 MTU so that its
>   encapsulated  packets emerged as 1360
> - the third tunnel would have to configure a 1360 MTU so that its
>   encapsulated packets emerged as 1400
> - etc.
>
> But, in real life, it is not possible to assume that we can lay
> hands on all tunnel endpoints so as to carefully set MTUs that
> satisfy the nesting level - and, when multiple administrative
> domains are involved, it can't be done at all.
>
> Please go back in the archives to where I posted the derivation
> of the 1280 minMTU (circa 1997):
>
> http://www.ietf.org/mail-archive/web/ipv6/current/msg18462.html
>
> My conclusion is that the 1280/1500 was well intentioned, but
> unfortunately not very well thought out.
>
> Thanks - Fred
> fred.l.templin@boeing.com

It doesn't matter what number you pick, and 1280 is probably as good as
it gets. The point from Brian (if I understood it correctly) was that
any fixed number can never be sufficient, as there's no dedicated
portion of the IPv6 MTU specifically assigned to tunneling, and no
defined max tunnel nesting depth.
>>> The 1280 is assuming that all links in the path have a 1500 MTU and
>>> so RFC2460 allowed (1500 - 1280) = 220 bytes for additional IPv6
>>> headers added by nested tunnels without incurring fragmentation.
>>> I am asserting instead that we have to allow for paths that include
>>> links with a 1280 MTU and so tunnels will have to fragment over
>>> such paths.
>>>
>>> That means that the first fragmenting tunnel would have room for
>>> 1240 in the first fragment, the second fragmenting tunnel would
>>> have room for 1200 in the first fragment, etc. That is why I would
>>> prefer that hosts limit the size of their header chains to 1024; so
>>> that nested tunnels that fragment will still be highly likely to
>>> have the entire header chain in the first fragment.
>>>
>>>> I understood that to be the basis on which the WG reached consensus.
>>> Maybe the WG didn't understand that such a consensus would make
>>> tunnels less reliable and less secure.
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>>     Brian
>> --
>> Regards,
>> RayH
>
> ------------------------------------------------------------------------


-- 
Regards,
RayH


From alexey.melnikov@isode.com  Mon Oct 14 03:52:54 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 30DD221F8263 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 03:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=-0.800, 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 PayX2Ps1xeHm for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 03:52:49 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id DFC8A21F9473 for <ietf@ietf.org>; Mon, 14 Oct 2013 03:34:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1381746856; d=isode.com; s=selector; i=@isode.com; bh=p2i8xUQXTYZj3SPtF9OWnmWS+S0rp0/BwaDUvRl7vy4=; 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=St4B+iREeaY6r39ihJuB9u5y1FWY30y/fQbtMVxuDErkvFKk8VrAujm7mRDeNedH7isd3+ WpruEKpjtFqFcYMGHod2IHQ4i7HOnqE8Ge+ZZC8Q0HHsIWbYUpftmKq0F4mWU8HKXN6kzc 0yJIYqjTeLyN9zOSo9a9Q0x7d8rl9OA=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UlvIpwB8l5fi@statler.isode.com>; Mon, 14 Oct 2013 11:34:15 +0100
Message-ID: <525BC8A6.6080204@isode.com>
Date: Mon, 14 Oct 2013 11:34:14 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
To: ietf@ietf.org
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type (see <draft-hausenblas-csv-fragment-06.txt>)
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
In-Reply-To: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
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: Mon, 14 Oct 2013 10:52:55 -0000

On 10/10/2013 19:50, The IESG wrote:
> The IESG has received a request to update the IANA registration of
> the text/csv media type, adding an optional fragment identifier.
> The request comes from a document in the Independent stream, and the
> IESG is the change controller for the text/csv media type.
>
> 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-10-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.
>
> The document making the request can be obtained via
> http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/
This looks like a good addition, so I am personally in favour of this.




From jmamodio@gmail.com  Mon Oct 14 06:07: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 F09AC11E8184 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.102
X-Spam-Level: 
X-Spam-Status: No, score=-1.102 tagged_above=-999 required=5 tests=[AWL=0.102,  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 DDRLI+daduBY for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:07:57 -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 62D7C21F9C1D for <ietf@ietf.org>; Mon, 14 Oct 2013 06:07:42 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id n2so4472050oag.39 for <ietf@ietf.org>; Mon, 14 Oct 2013 06:07:41 -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:from:subject:date:to; bh=r5Io3Ffq2QA01zjWSsrrT31XprEWbdlFWn5GddvuGHg=; b=U6rtZ5u5DRU3AeclG0WN7HWr7SRgGobVcn2Qe7p1R4wzUe19j8QbW0bEvK7jUG7TRY Q6zoADZ4kBRs9vVVIkQN5ZGnkjENg5u8SaUXyvw3OGjXYjP126tfPSqBjZBbkRzD4jt5 5M7ScFmatxGVjh0eaDMC5VA4Vp7DyIvpnAq1k1kdv7xitmGpvFJXK3ZTjVRcU3wWcxrE 1OTAwYvWDvpx3eSzf/nZzi35DeT6WhcIKMd+bXRW8JdMXEA+j2HOLgINFBZl7SpCNWjy B5L9PP6lb/MvgseKpnRs489a8dD9CErE9kLGOTQNlCDZASOPUQ2vcayKcm1Vnef2IXxw w/Fw==
X-Received: by 10.182.137.231 with SMTP id ql7mr207799obb.75.1381756061794; Mon, 14 Oct 2013 06:07:41 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id bq4sm41685535obb.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 06:07:40 -0700 (PDT)
References: <20131012120242.2BF7118C0C3@mercury.lcs.mit.edu> <52593F4B.9070904@cs.tcd.ie>
Mime-Version: 1.0 (1.0)
In-Reply-To: <52593F4B.9070904@cs.tcd.ie>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A9AA5B3-D2D6-478D-8882-847E710A4994@gmail.com>
X-Mailer: iPad Mail (11A501)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Of governments and representation (was: Montevideo Statement)
Date: Mon, 14 Oct 2013 08:07:38 -0500
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "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, 14 Oct 2013 13:07:58 -0000

The problem is not what actually each person said but what "they" say it was=
 said and gets recorded into a statement that has no weight and it is not re=
presentative of the entire community.


-Jorge

> On Oct 12, 2013, at 7:23 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> w=
rote:
>=20
>=20
> Hiya,
>=20
>> On 10/12/2013 01:02 PM, Noel Chiappa wrote:
>>=20
>> The thing is that I (and I suspect much of the IETF) feel that such I*
>> leadership attendees need to make it _very_ clear at such events that the=
y are
>> there to present (as best they can) the views of the IETF as a whole, but=
 they
>> cannot _commit_ the IETF to anything: only the IETF acting as a whole can=
 do
>> that.
>=20
> So fwiw I was there as Jari's sidekick-de-jour and I can confirm
> that both Jari and Russ repeatedly made it clear that anything
> substantive needed IETF community consensus. I realise that's not
> as good as a recording or set of minutes, but there ya go.
>=20
> Cheers,
> S.

From jmamodio@gmail.com  Mon Oct 14 06:32:23 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 B494921F856A for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:32: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, 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 kLje7qc4EVpo for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:32:22 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 23F8A21F90AC for <ietf@ietf.org>; Mon, 14 Oct 2013 06:32:13 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id w61so6905431wes.24 for <ietf@ietf.org>; Mon, 14 Oct 2013 06:32: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=bjuiMCaJoWWeBBDj9QHVdmCQMNTd1H3waixEFbvgm+M=; b=T4SzkKaD3FNKVjBZATkyFuq8YCcHZabb9B3LSouL9kNbfs0jNqRq0wAod4xqy5RnuE zwfIOkiSAQADjXAD80Zk59UtvaQNINNuLf9vo0g9W9CdS0dChcEqq6+RM8ES5OcJ2aKN 4pdffPkm4+M1QJgGHMSFCc7BZU093eo3Glfj9gorSENrJGQ5Hmaqv03CiUGCiCD3FzrH 7/bECTSWrscgJe6B/lkAyh9qeDgPWBXnfXLtxTY7hBW6P6QhCTnTK10ZnkoAYOyZzm58 N71m9MhPt9r5+ulmaIRhjmoBM6GUh+ehxmKxeuDggAo4uxE5uv/Tzc4+BZlV+L3wHPN7 B06w==
MIME-Version: 1.0
X-Received: by 10.180.75.232 with SMTP id f8mr14894212wiw.26.1381757532999; Mon, 14 Oct 2013 06:32:12 -0700 (PDT)
Received: by 10.180.84.38 with HTTP; Mon, 14 Oct 2013 06:32:12 -0700 (PDT)
In-Reply-To: <52594EB8.4000702@gmail.com>
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <52585188.6020408@gmail.com> <52594EB8.4000702@gmail.com>
Date: Mon, 14 Oct 2013 08:32:12 -0500
Message-ID: <CAMzo+1Yt6B_e4etqpKcCgiMqJo2QMxV1Z238N_OjmbRtVYymiA@mail.gmail.com>
Subject: Re: Of governments and representation (was: Montevideo Statement)
From: Jorge Amodio <jmamodio@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043890adeb991804e8b37ecf
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, 14 Oct 2013 13:32:23 -0000

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

There is an important difference between policy and politics. Promoting a
politics discussion within the IETF arena will become the demise of the
IETF.

-J


On Sat, Oct 12, 2013 at 8:29 AM, Arturo Servin <arturo.servin@gmail.com>wrote:

>
>         It is clear to me that the IETF cannot be away from Internet
> Governance
> discussions. Yes, it is politics and we do not like politics, but that
> is the way the Internet is these days.
>
>         It is also appears that we do not have consensus of how to
> participate
> and what to say in those discussions (I do not mind the way it is today
> but it seems that some folk -and I understand them- prefer other ways).
>
>         Inevitably, as John said we are in times of change and we need to
> figure out how to interact with other Internet ecosystem organizations,
> we like or not.
>
>         By means of our current bodies (IAB, IESG), individual submissions
> or
> working groups we need to find a way to what say, where, and how.
>
> Regards,
> as
>
>
> On 10/11/13 5:29 PM, Brian E Carpenter wrote:
> > Hi John,
> >
> > On 12/10/2013 05:02, John Curran wrote:
> > ...
> >> In my personal view, it is a very important for the IETF to select
> leadership who can
> >> participate in any discussions that occur,
> >
> > Without obsessing about the word "leadership", but following up on a
> comment
> > made by Noel Chiappa on the "leader statements" thread, I think we have
> > to recognise that nothing in the NomCom process, the IAB Charter, or
> > the IESG Charter, would cause us to select IAB or IETF Chairs who are
> > particularly suited to this role.
> >
> > In fact I think that the plan of record is to leave such matters to
> > ISOC.
> >
> > Reality is different - the outside world expects to hear from us.
> >
> >      Brian
> >
>

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

<div dir=3D"ltr"><br><div>There is an important difference between policy a=
nd politics. Promoting a politics discussion within the IETF arena will bec=
ome the demise of the IETF.</div><div><br></div><div>-J</div></div><div cla=
ss=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Sat, Oct 12, 2013 at 8:29 AM, Arturo =
Servin <span dir=3D"ltr">&lt;<a href=3D"mailto:arturo.servin@gmail.com" tar=
get=3D"_blank">arturo.servin@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<br>
=A0 =A0 =A0 =A0 It is clear to me that the IETF cannot be away from Interne=
t Governance<br>
discussions. Yes, it is politics and we do not like politics, but that<br>
is the way the Internet is these days.<br>
<br>
=A0 =A0 =A0 =A0 It is also appears that we do not have consensus of how to =
participate<br>
and what to say in those discussions (I do not mind the way it is today<br>
but it seems that some folk -and I understand them- prefer other ways).<br>
<br>
=A0 =A0 =A0 =A0 Inevitably, as John said we are in times of change and we n=
eed to<br>
figure out how to interact with other Internet ecosystem organizations,<br>
we like or not.<br>
<br>
=A0 =A0 =A0 =A0 By means of our current bodies (IAB, IESG), individual subm=
issions or<br>
working groups we need to find a way to what say, where, and how.<br>
<br>
Regards,<br>
as<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 10/11/13 5:29 PM, Brian E Carpenter wrote:<br>
&gt; Hi John,<br>
&gt;<br>
&gt; On 12/10/2013 05:02, John Curran wrote:<br>
&gt; ...<br>
&gt;&gt; In my personal view, it is a very important for the IETF to select=
 leadership who can<br>
&gt;&gt; participate in any discussions that occur,<br>
&gt;<br>
&gt; Without obsessing about the word &quot;leadership&quot;, but following=
 up on a comment<br>
&gt; made by Noel Chiappa on the &quot;leader statements&quot; thread, I th=
ink we have<br>
&gt; to recognise that nothing in the NomCom process, the IAB Charter, or<b=
r>
&gt; the IESG Charter, would cause us to select IAB or IETF Chairs who are<=
br>
&gt; particularly suited to this role.<br>
&gt;<br>
&gt; In fact I think that the plan of record is to leave such matters to<br=
>
&gt; ISOC.<br>
&gt;<br>
&gt; Reality is different - the outside world expects to hear from us.<br>
&gt;<br>
&gt; =A0 =A0 =A0Brian<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--f46d043890adeb991804e8b37ecf--

From stbryant@cisco.com  Mon Oct 14 06:37:45 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 D251E21E816A for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.512
X-Spam-Level: 
X-Spam-Status: No, score=-110.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 hQ7a4cinqnjJ for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 06:37:40 -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 BF3BF21E8162 for <ietf@ietf.org>; Mon, 14 Oct 2013 06:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=631; q=dns/txt; s=iport; t=1381757859; x=1382967459; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=h8NWSDP64mJT4vAMg29ao5Icm4h1nldFbeLrH4WQ5SM=; b=HtemFXBXueO/NvsvnSZalpFNoWrkJWmuKDySPX1iXeBH454ra0TF6e/P ccvamtg/tulCvEnH7RCrrHyKdJpUZeYe9eNksWTLqniXSYoFIOoeMDi9c BHtzPcFuMkbC+ggqd6MmSgvb4R++2Rp9TToowkuyfdLKV0rK+sZdRn7Mt 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAFPzW1KQ/khR/2dsb2JhbABZgwc4g3u+RYEiFnSCJQEBAQQjFUABEAsYAgIFFgsCAgkDAgECAUUGDQEHAQGIAgyrLJIzgSmOKQeCaoE5A5gFgS+QU4Ml
X-IronPort-AV: E=Sophos;i="4.93,492,1378857600"; d="scan'208";a="18744295"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 14 Oct 2013 13:37:38 +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 r9EDbWDj031376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Oct 2013 13:37:34 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r9EDbUJU001607; Mon, 14 Oct 2013 14:37:31 +0100 (BST)
Message-ID: <525BF39A.9080009@cisco.com>
Date: Mon, 14 Oct 2013 14:37:30 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Terms and Conditions May Apply
References: <525AF17A.6090806@gmail.com>
In-Reply-To: <525AF17A.6090806@gmail.com>
Content-Type: text/plain; charset=UTF-8; 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
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: Mon, 14 Oct 2013 13:37:45 -0000

On 13/10/2013 20:16, Brian E Carpenter wrote:
> I know we don't normally do movie plugs on this list, but anyone
> who's planning to attend the technical plenary in Vancouver
> could do worse than watch "Terms and Conditions May Apply".
> It covers both commercial and governmental invasions of privacy,
> and how they are interlinked.
>
> http://www.imdb.com/title/tt2084953/
>
> or
>
> http://tacma.net/ (but you might not want to click
> on the 'I agree' button until you've seen the movie...)
>
>     Brian
>
Seeming terms and conditions means that terms and conditions
is not available in the UK.

Stewart

From harald@alvestrand.no  Mon Oct 14 07:20:56 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD4C11E813A for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 07:20:56 -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 X6Zj83ZVT0gM for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 07:20:51 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 93E0711E8140 for <ietf@ietf.org>; Mon, 14 Oct 2013 07:20:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 1F5C439E371 for <ietf@ietf.org>; Mon, 14 Oct 2013 16:20:46 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8uo9PF0SnbRA for <ietf@ietf.org>; Mon, 14 Oct 2013 16:20:45 +0200 (CEST)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:7646:a0ff:fe90:e2bb]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 4EBEA39E10F for <ietf@ietf.org>; Mon, 14 Oct 2013 16:20:45 +0200 (CEST)
Message-ID: <525BFDBC.2080400@alvestrand.no>
Date: Mon, 14 Oct 2013 16:20:44 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Of governments and representation (was: Montevideo Statement)
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
In-Reply-To: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org>
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: Mon, 14 Oct 2013 14:20:56 -0000

For what it's worth, I think Russ and Jari did the right thing in 
signing the statement the way they did, at the time they did it, with 
the prior consultation they did.

I was not consulted. And I'm glad they are capable of acting at this 
level without consulting me.



On 10/11/2013 06:02 PM, John Curran wrote:
> Folks -
>
> As a result of the Internet's growing social and economic importance, the underlying
> Internet structures are receiving an increasing level of attention by both governments
> and civil society.  The recent revelations regarding US government surveillance of
> the Internet are now greatly accelerating government attention on all of the Internet
> institutions, the IETF included.  All of this attention is likely bring about significant
> changes in the Internet ecosystem, potentially including how the IETF interacts with
> governments, civil society, and other Internet organizations globally.
>
> In my personal view, it is a very important for the IETF to select leadership who can
> participate in any discussions that occur, and it would further be prudent for the IETF
> leaders to be granted a sufficient level of support by the community to take positions
> in those discussions and make related statements, to the extent the positions and
> the statements are aligned with established IETF positions and/or philosophy.
>
> The most interesting part of the myriad of Internet Governance discussions is that
> multiple organizations are all pushing ahead independently from one another, which
> results in a very dynamic situation where we often don't even know that there will be
> a conference or meeting until after its announced, do not know auspices under which
> it will be held, nor what the scope of the discussions held will ultimately be.  However,
> the failure of any of the Internet organizations to participate will not actually prevent
> consideration of a variety of unique and colorful proposals for improving the Internet
> and/or the IETF, nor will it preclude adoption even in the absence of IETF input...
>
> The IETF is a very important Internet institution, and it deserves to be represented
> in any discussions which might propose changes to the fundamental mechanisms of
> Internet cooperation.  It would be a wonderful world indeed if all of these discussions
> started with submission of an Internet Draft and discussion on open mailing lis, but
> that hasn't been the modus operandi of governments and is probably too much to
> realistically expect.
>
> /John


From barryleiba.mailing.lists@gmail.com  Mon Oct 14 08:31:48 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 808BB11E81A5 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 08:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.689
X-Spam-Level: 
X-Spam-Status: No, score=-101.689 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_43=0.6, 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 tDhLxNv+ynXu for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 08:31:48 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id BBD6711E81E8 for <ietf@ietf.org>; Mon, 14 Oct 2013 08:31:23 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id u14so5691294lbd.40 for <ietf@ietf.org>; Mon, 14 Oct 2013 08:31:22 -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:message-id:subject :from:to:cc:content-type; bh=Owux5Aa+j7ZeWPQ/CW4kSlmo2uDsHsftnnawKUooddc=; b=hHBnmZCkfMXYySz2amtVaijCwu9BwfcC/WQOF3NkbQotkhAj7yIsV5ZMRZY5Pg01C6 93bgmJuZ+U/4cKLAdlD1IeQiuClfTo+rohQqmA9LoEqy5l3rE2q7EWQ5Abj3y7St6YzO YvLb2LG2Ulsm2fImiOAE828Y8ut12GF4lgWiY76KyFaHKl1JDy9QqnG1Ys5sy+Fvr1Mq R9JaL+OJgGK7T8V4P1Uf7d/1alKtFdXqnzwPpp5mIQ3D4uNhFnp+FDYI5QGIo2Z2j7fD GwIj2BIaaYuPtXuR8vDBCriPcUR6NR3Bvf5FNVnoh3yFUK7MoCtPslu6MQ+IXy5R1rBI wMOg==
MIME-Version: 1.0
X-Received: by 10.112.190.1 with SMTP id gm1mr6724467lbc.30.1381764682559; Mon, 14 Oct 2013 08:31:22 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Mon, 14 Oct 2013 08:31:22 -0700 (PDT)
In-Reply-To: <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net>
Date: Mon, 14 Oct 2013 11:31:22 -0400
X-Google-Sender-Auth: gWogs-Mu_k26QSZGtuYduwzhPRY
Message-ID: <CAC4RtVCsrRguE8LOkKOV-v7C=hU7Soi+h_Dq8=CwjW6rDW44XA@mail.gmail.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
From: Barry Leiba <barryleiba@computer.org>
To: "t.p." <daedulus@btconnect.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: Mon, 14 Oct 2013 15:31:48 -0000

> I find the security considerations in this registration rather weak.
> What might have sufficed in 2005 seems to me inadequate for 2013.  I
> would expect a clearer statement of what are or are not considered
> threats or attacks and what mitigations there then are for them.

Tom, do you have specific suggestions for the authors in this regard.

Barry

From hsantos@isdg.net  Mon Oct 14 09:10:43 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 140A611E8156 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 09:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=0.199,  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 rynk44frfgfR for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 09:10:39 -0700 (PDT)
Received: from groups.winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC1911E8189 for <ietf@ietf.org>; Mon, 14 Oct 2013 09:10:29 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=607; t=1381767018; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=klETizZqE5fLy78f/wvm9ej9b2Y=; b=ELSPQFpMapS9Tt76Fjni wKWaPVj3qcMt7U100gCmn8Z+hfK4vXBog+cGsoQ+AbSsP/sbkJ/tfEn75FMknf6F jLL+it3TxGAlTXD56mPHZC5gtly5HI5KeM4MYYO5yJLuxxNjN9K6gdpXHl6Q0B0w awrDxAc76YwcmcJBAYRWNww=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Oct 2013 12:10:18 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3934513106.17297.1640; Mon, 14 Oct 2013 12:10:17 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=607; t=1381766612; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=2E0eFbU rBVVS3l9F0cUbwKBLA8O4Wu1iY9MpVVcD7Lo=; b=nlGqTQolsvzdusrU/PZTXSh OOi1q/jzFk7Xs1/Az+jfjXgMsfjma1tywKXxNONvQ3Wp12mE/QHXmN8P9V5uF1cV bcapo+aW0EmpA5Sl8SPyvwmJuDpd0laFoYbpCdXIE/vzlA+10dFF3PEN8fDDdxcd Ow7JtMI834KSb8FzE7gU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Oct 2013 12:03:32 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3380892331.9.8692; Mon, 14 Oct 2013 12:03:30 -0400
Message-ID: <525C1764.2010101@isdg.net>
Date: Mon, 14 Oct 2013 12:10:12 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: Terms and Conditions May Apply
References: <525AF17A.6090806@gmail.com>
In-Reply-To: <525AF17A.6090806@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Oct 2013 16:10:43 -0000

Youtube URL.

http://www.youtube.com/watch?v=2UWRuIXXzYs



On 10/13/2013 3:16 PM, Brian E Carpenter wrote:
> I know we don't normally do movie plugs on this list, but anyone
> who's planning to attend the technical plenary in Vancouver
> could do worse than watch "Terms and Conditions May Apply".
> It covers both commercial and governmental invasions of privacy,
> and how they are interlinked.
>
> http://www.imdb.com/title/tt2084953/
>
> or
>
> http://tacma.net/ (but you might not want to click
> on the 'I agree' button until you've seen the movie...)
>
>     Brian
>
>

-- 
HLS



From daedulus@btconnect.com  Mon Oct 14 09:33:59 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 DFBE621E80E0 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 09:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_00=-2.599, J_CHICKENPOX_43=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 ESEaZ8FyKQ-R for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 09:33:53 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0188.outbound.messaging.microsoft.com [213.199.154.188]) by ietfa.amsl.com (Postfix) with ESMTP id 9977521E8192 for <ietf@ietf.org>; Mon, 14 Oct 2013 09:33:10 -0700 (PDT)
Received: from mail130-db8-R.bigfish.com (10.174.8.236) by DB8EHSOBE039.bigfish.com (10.174.4.102) with Microsoft SMTP Server id 14.1.225.22; Mon, 14 Oct 2013 16:33:08 +0000
Received: from mail130-db8 (localhost [127.0.0.1])	by mail130-db8-R.bigfish.com (Postfix) with ESMTP id BDD44802CB; Mon, 14 Oct 2013 16:33:08 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275bh8275dhz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail130-db8 (localhost.localdomain [127.0.0.1]) by mail130-db8 (MessageSwitch) id 1381768338399964_3065; Mon, 14 Oct 2013 16:32:18 +0000 (UTC)
Received: from DB8EHSMHS004.bigfish.com (unknown [10.174.8.251])	by mail130-db8.bigfish.com (Postfix) with ESMTP id 5DE60204F7; Mon, 14 Oct 2013 16:32:18 +0000 (UTC)
Received: from AM2PRD0710HT001.eurprd07.prod.outlook.com (157.56.249.213) by DB8EHSMHS004.bigfish.com (10.174.4.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 14 Oct 2013 16:32:18 +0000
Received: from DBXPRD0611HT004.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.165.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 14 Oct 2013 16:32:16 +0000
Message-ID: <00d601cec8fa$afa61740$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com><000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <CAC4RtVCsrRguE8LOkKOV-v7C=hU7Soi+h_Dq8=CwjW6rDW44XA@mail.gmail.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
Date: Mon, 14 Oct 2013 17:21:36 +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.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 14 Oct 2013 16:34:00 -0000

----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "t.p." <daedulus@btconnect.com>
Cc: "IETF discussion list" <ietf@ietf.org>
Sent: Monday, October 14, 2013 4:31 PM

> > I find the security considerations in this registration rather weak.
> > What might have sufficed in 2005 seems to me inadequate for 2013.  I
> > would expect a clearer statement of what are or are not considered
> > threats or attacks and what mitigations there then are for them.
>
> Tom, do you have specific suggestions for the authors in this regard.

Looking at an unrelated media/type RFC, it starts with
The main security considerations for the ....
   payload format defined within this memo are confidentiality,
   integrity, and source authenticity.
which is the sort of beginning I expect a Security Considerations to
have in 2013, then going on to say which are relevant here and
how they might be mitigated - CMS, IPsec, TLS; or not as the case
may be.

I see this type as one for database data and so requiring more
careful consideration than, eg, text/plain, as used for messages
like this one.

Tom Petch




>
> Barry
>



From tbray@textuality.com  Mon Oct 14 10:28:41 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE7821E8177 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.882
X-Spam-Level: 
X-Spam-Status: No, score=-2.882 tagged_above=-999 required=5 tests=[AWL=0.094,  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 sLEiqCMlNDAA for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:28:34 -0700 (PDT)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id 190B621E8171 for <ietf@ietf.org>; Mon, 14 Oct 2013 10:28:30 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id id10so4125926vcb.40 for <ietf@ietf.org>; Mon, 14 Oct 2013 10:28:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=UZPqETmoPOgL4qa8n3mTuZhiU/6ZiVYt3UGPgCoY1qE=; b=mHdSYGaf4B6jDg2Ejm9hVx1X5bHSAHSIzUCBx1/txy5zZq0m03saly+XGxNRyi8UQm F2/JV/SWm998pLnJ87+Ox7wRG4Cq1IwI+zUC9ZOikITITbWdM1KlJW0vUKbTpbdG8ep9 qBu0W7EwQXA/2TAxJYsD7j1nTFqwpFV1r0w4U5gmGQRLrSd5+dwMQ2P8XpD5FQ08AvPS zNvMjuFHNQI/Elpbojhm6qYdn7NHCVOGxJttO5vU7j/V7OL4QtwTQp8xpbRlidFfCMLy M7v8eH/RKE1iQ/Av/jRGYBQj4m0n/zXxV6+wd/TR0ejqTPsPIUPE3dOEDgZ3tdbmMlM6 0AMg==
X-Gm-Message-State: ALoCoQlqQzzQlBigLkQX/vzFoHHHs1RNYxVCS6uzNW7v9Lyd4A7w6pvypCmwTsvm9pt2jNm6fe18
MIME-Version: 1.0
X-Received: by 10.58.215.135 with SMTP id oi7mr80783vec.27.1381771710372; Mon, 14 Oct 2013 10:28:30 -0700 (PDT)
Received: by 10.220.174.197 with HTTP; Mon, 14 Oct 2013 10:28:30 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com>
Date: Mon, 14 Oct 2013 10:28:30 -0700
Message-ID: <CAHBU6iu3dmahxgaqSLTXQ0s3vaDgn87CV8WCV+nrwa=70M41fw@mail.gmail.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type (see <draft-hausenblas-csv-fragment-06.txt>)
From: Tim Bray <tbray@textuality.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c39f24f52a9304e8b6cbf0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Oct 2013 17:28:41 -0000

--001a11c39f24f52a9304e8b6cbf0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think this is sensible, could be useful, won=E2=80=99t break anything, an=
d
probably hits a huge 80/20 points for the ways people might want to address
inside spreadsheets.  Go ahead and publish it.


On Thu, Oct 10, 2013 at 11:50 AM, The IESG <iesg@ietf.org> wrote:

> The IESG has received a request to update the IANA registration of
> the text/csv media type, adding an optional fragment identifier.
> The request comes from a document in the Independent stream, and the
> IESG is the change controller for the text/csv media type.
>
> 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-10-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.
>
> The document making the request can be obtained via
> http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/
>

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

<div dir=3D"ltr">I think this is sensible, could be useful, won=E2=80=99t b=
reak anything, and probably hits a huge 80/20 points for the ways people mi=
ght want to address inside spreadsheets.=C2=A0 Go ahead and publish it.<br>=
</div><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Oct 10, 2013 at 11:50 AM, The IE=
SG <span dir=3D"ltr">&lt;<a href=3D"mailto:iesg@ietf.org" target=3D"_blank"=
>iesg@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The IESG has received a request to update the IANA registration of<br>
the text/csv media type, adding an optional fragment identifier.<br>
The request comes from a document in the Independent stream, and the<br>
IESG is the change controller for the text/csv media type.<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-10=
-24. Exceptionally, comments may<br>
be sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In e=
ither case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
The document making the request can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/" =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-hausenblas-csv-frag=
ment/</a><br>
</blockquote></div><br></div>

--001a11c39f24f52a9304e8b6cbf0--

From sm@resistor.net  Mon Oct 14 10:32:13 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 6093921E818B for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:32: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 vNjYmVcGwsdf for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:32:12 -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 76A1621E8177 for <ietf@ietf.org>; Mon, 14 Oct 2013 10:32: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 r9EHW5JJ004562; Mon, 14 Oct 2013 10:32:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381771931; bh=U1NpqPAmYSeb98MT9FDg0sH0JyCo139gtfBMuHEWveA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sVihSJoZmb3V2HUNT+TYUXFl/YhfYS9DN8JYt/pueYbXk7j0oh/Gku4rknSvzxDS/ ZEZ9eqPIbIAi42ussH40sOd7IuJ9MFv9SPRr2qR8/3mGz854HQa4/JUwZ8HnSLKNEw 1D2RZOyN4Hr0ICcfp7rzndPvRh+eal/THgcz9k9A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381771931; i=@resistor.net; bh=U1NpqPAmYSeb98MT9FDg0sH0JyCo139gtfBMuHEWveA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ww0YZZy5x1Ukxpg0rlPs/o6hCIVGR0MDfZYlV0weEOmobwjg/lNQk7bFXGhqVdI69 pUQhk9XmAyNkfd+xcC+ejPc1ZlPubeC1Em1pL5yUlGJpFyuXdVmj4QGdS6nmhiPl+o zcf/iwAPt3tEI6G3UaeOgVlw1zRulP0kP2KWNUpA=
Message-Id: <6.2.5.6.2.20131014072334.0d217aa8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Oct 2013 08:19:48 -0700
To: Ronald Bonica <rbonica@juniper.net>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
In-Reply-To: <42ae3f3e73f840e2b40e62430cf8f7d7@CO1PR05MB442.namprd05.pro d.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131012194048.0c92f558@resistor.net> <42ae3f3e73f840e2b40e62430cf8f7d7@CO1PR05MB442.namprd05.prod.outlook.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, 14 Oct 2013 17:32:13 -0000

Hi Ron,
At 16:55 13-10-2013, Ronald Bonica wrote:
>Are you suggesting that we don't address the problem because the 
>code is too complex to touch?

It's a known problem since at least seven years.  Given that the 
problem is labelled as a security issue there would have to be some 
changes to the specification at some point.  There were design 
decisions to implement the specification and the code has been 
deployed.  The proposed outbound change is one sentence.  The code 
change to implement that one sentence requires reviewing some 
implementation decisions (re. encapsulation, etc.).  Please note that 
I am not arguing for or against a change in the RFC 2119 key 
words.  The write-up only mentions that the draft has been 
implemented on stateless firewalls.  I am curious about whether there 
are any implementations for a host.

Regards,
-sm  


From Fred.L.Templin@boeing.com  Mon Oct 14 10:38:13 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555BD21E8197; Mon, 14 Oct 2013 10:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.467
X-Spam-Level: 
X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.132,  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 Dm1SBu8l9hs5; Mon, 14 Oct 2013 10:38:06 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5D821E8192; Mon, 14 Oct 2013 10:38:05 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EHc4qV000711; Mon, 14 Oct 2013 12:38:04 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EHbx4e000617 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 12:38:03 -0500
Received: from XCH-BLV-302.nw.nos.boeing.com (130.247.25.214) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 10:38:02 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-302.nw.nos.boeing.com ([169.254.2.227]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 10:38:01 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOxtMYebc9KTehbEGO6mhunuAlj5n0eZ8A
Date: Mon, 14 Oct 2013 17:38:00 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com>
In-Reply-To: <52587EB8.4020506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Mon, 14 Oct 2013 17:38:13 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAzOjQyIFBNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEwN
Cj4gQ2M6IEZlcm5hbmRvIEdvbnQ7IFJheSBIdW50ZXI7IDZtYW4gTWFpbGluZyBMaXN0OyBpZXRm
QGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLTZtYW4tb3Zl
cnNpemVkLWhlYWRlci1jaGFpbi0wOC50eHQ+DQo+IChJbXBsaWNhdGlvbnMgb2YgT3ZlcnNpemVk
IElQdjYgSGVhZGVyIENoYWlucykgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IEZyZWQsDQo+
IA0KPiBPbiAxMi8xMC8yMDEzIDA4OjU2LCBUZW1wbGluLCBGcmVkIEwgd3JvdGU6DQo+ID4gSGkg
QnJpYW4sDQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTog
QnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+
ID4+IFNlbnQ6IEZyaWRheSwgT2N0b2JlciAxMSwgMjAxMyAxMjo1MCBQTQ0KPiA+PiBUbzogRmVy
bmFuZG8gR29udA0KPiA+PiBDYzogVGVtcGxpbiwgRnJlZCBMOyBSYXkgSHVudGVyOyA2bWFuIE1h
aWxpbmcgTGlzdDsgaWV0ZkBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8
ZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC1oZWFkZXItY2hhaW4tDQo+IDA4LnR4dD4NCj4gPj4g
KEltcGxpY2F0aW9ucyBvZiBPdmVyc2l6ZWQgSVB2NiBIZWFkZXIgQ2hhaW5zKSB0byBQcm9wb3Nl
ZCBTdGFuZGFyZA0KPiA+Pg0KPiA+PiBPbiAxMi8xMC8yMDEzIDA2OjA0LCBGZXJuYW5kbyBHb250
IHdyb3RlOg0KPiA+PiAuLi4NCj4gPj4+IFAuUy46IFJlZWdhcmRpbmcgZW5mb3JjaW5nIGEgbGlt
aXQgb24gdGhlIGxlbmd0aCBvZiB0aGUgaGVhZGVyDQo+IGNoYWluLA0KPiA+PiBJDQo+ID4+PiBt
dXN0IHNheSBJIHN5bXBoYXRpemUgd2l0aCB0aGF0IChmb3IgaW5zdGFuY2UsIGNoZWNrIHRoZSBs
YXN0DQo+ID4+IGluZGl2aWR1YWwNCj4gPj4+IHZlcnNpb24gb2YgdGhpcyBJLUQsIGFuZCB5b3Un
bGwgZmluZCBleGFjdGx5IHRoYXQpLiBCdXQgdGhlIHdnDQo+IGRpZG4ndA0KPiA+Pj4gd2FudCB0
aGF0IGluIC0tIGFuZCBJIGRpZCByYWlzZSB0aGUgaXNzdWUgYSBmZXcgdGltZXMuIFNvIHdoYXQg
d2UNCj4gPj4gaGF2ZQ0KPiA+Pj4gaXMgd2hhdCB0aGUgNm1hbiB3ZyBoYWQgY29uc2Vuc3VzIG9u
Lg0KPiA+PiBJIGFncmVlIHRoYXQgdGhpcyB3YXMgdGhlIFdHIGNvbnNlbnN1cyBhZnRlciBjb25z
aWRlcmFibGUNCj4gZGlzY3Vzc2lvbiwNCj4gPj4gd2hpY2ggaW5jbHVkZWQgRnJlZCwgc28gSSdt
IG5vdCBzdXJlIHdoeSB3ZSdyZSBkaXNjdXNzaW5nIGl0IGFnYWluDQo+ID4+IGR1cmluZyBJRVRG
IExDLg0KPiA+DQo+ID4gVGVjaG5pY2FsIG1hdHRlcnMgc2hvdWxkIGJlIGRpc2N1c3NlZCBhcyB0
aGV5IGNvbWUgdG8gbGlnaHQ7IG5vdA0KPiA+IGRpc21pc3NlZCBiZWNhdXNlIG9mIHNvbWUgcmVh
bCBvciBwZXJjZWl2ZWQgZGVhZGxpbmUuIFRoYXQgd2FzIHdoYXQNCj4gPiBnb3QgdXMgdGhlIDEy
ODAgTVRVIGluIHRoZSBmaXJzdCBwbGFjZS4gUXVvdGluZyBmcm9tIFN0ZXZlIERlZXJpbmc6DQo+
ID4NCj4gPiAgICIgV2Ugd291bGQgbGlrZSB0byBnZXQgdGhpcyBpc3N1ZSBzZXR0bGVkIGFzDQo+
ID4gICAgIHNvb24gYXMgcG9zc2libGUsIHNpbmNlIHRoaXMgaXMgdGhlIG9ubHkgdGhpbmcgaG9s
ZGluZyB1cCB0aGUNCj4gcHVibGljYXRpb24NCj4gPiAgICAgb2YgdGhlIHVwZGF0ZWQgUHJvcG9z
ZWQgU3RhbmRhcmQgSVB2NiBzcGVjICh0aGUgdmVyc2lvbiB3ZSBleHBlY3QNCj4gdG8gYWR2YW5j
ZQ0KPiA+ICAgICB0byBEcmFmdCBTdGFuZGFyZCksIHNvIGxldCdzIHNlZSBpZiB3ZSBjYW4gY29t
ZSB0byBhIGRlY2lzaW9uDQo+IGJlZm9yZSB0aGUgSUQNCj4gPiAgICAgZGVhZGxpbmUgYXQgdGhl
IGVuZCBvZiBuZXh0IHdlZWsgKGhvcGluZyB0aGVyZSBpc24ndCBhbnkgY29uZmxpY3QNCj4gYmV0
d2Vlbg0KPiA+ICAgICAidGhvdWdodGZ1bCBhbmFseXNpcyIgYW5kICJsZXQncyBkZWNpZGUgcXVp
Y2tseSIgOi0pLiINCj4gPg0KPiA+IFNvLCBpdCB3YXNuJ3QgbmVjZXNzYXJpbHkgdGhlIGNhc2Ug
dGhhdCAxMjgwIHdhcyBhIHByb2R1Y3Qgb2YNCj4gInRob3VnaHRmdWwNCj4gPiBhbmFseXNpcyIg
c28gbXVjaCBhcyB0aGUgZmFjdCB0aGF0ICoqdGhleSB3ZXJlIHJ1c2hpbmcgdG8gZ2V0IGEgc3Bl
Yw0KPiBvdXQNCj4gPiB0aGUgZG9vcioqLiBTbyBub3csIDE2IHllYXJzIGxhdGVyLCB3ZSBnZXQg
dG8gcHV0IGl0IGJhY2sgb24gdGhlIDZtYW4NCj4gPiBjaGFydGVyIG1pbGVzdG9uZSBsaXN0Lg0K
PiANCj4gV2UgY291bGQgaGF2ZSB0aGF0IGRpc2N1c3Npb24gaW4gNm1hbiwgc3VyZSwgYnV0IEkg
ZG9uJ3QgYmVsaWV2ZSB0aGF0DQo+IGl0J3MNCj4gcmVsZXZhbnQgdG8gdGhlIHF1ZXN0aW9uIG9m
IHdoZXRoZXIgZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC1oZWFkZXItDQo+IGNoYWluDQo+IGlz
IHJlYWR5Lg0KDQpJZiBpdCBtZXNzZXMgdXAgdHVubmVscywgdGhlbiBpdCdzIG5vdCByZWFkeS4N
Cg0KPiBUaGlzIGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gaW4gdGVybXMgb2YgdGhl
IGN1cnJlbnQNCj4gSVB2NiBzdGFuZGFyZHMuDQoNCklmIHRoYXQgcHJvYmxlbSBpcyBhbHNvIG1p
dGlnYXRlZCBieSBhIG1lYXN1cmUgdGhhdCBkb2VzIG5vdCBtZXNzDQp1cCB0dW5uZWxzLCB0aGVu
IHdvdWxkbid0IHRoYXQgYmUgd29ydGggY29uc2lkZXJpbmcgYmVmb3JlDQpmaW5hbGl6aW5nIHRo
aXMgcHVibGljYXRpb24uDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50ZW1wbGluQGJvZWluZy5j
b20NCg0KPiAgICAgQnJpYW4NCg==

From Fred.L.Templin@boeing.com  Mon Oct 14 10:39:49 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27C221F923D; Mon, 14 Oct 2013 10:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124,  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 mgXh+3ftqz6l; Mon, 14 Oct 2013 10:39:41 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id C9BF321F8EC3; Mon, 14 Oct 2013 10:39:32 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EHdV5H003302; Mon, 14 Oct 2013 12:39:32 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EHdSoO003242 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 12:39:31 -0500
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 10:39:30 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 10:39:29 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOx7jqJAvRrWBwLEyOc1cqWuOOX5n0dmTg
Date: Mon, 14 Oct 2013 17:39:29 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Mon, 14 Oct 2013 17:39:49 -0000

Hi Ron,

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Saturday, October 12, 2013 7:07 PM
> To: Brian E Carpenter; Templin, Fred L
> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> +1
>=20
> Is there a way to decouple this discussion from draft-ietf-6man-
> oversized-header-chain? I would be glad to discuss it in the context of
> a separate draft.

I don't know if there is a way to decouple it. I believe I have shown
a way to not mess up tunnels while at the same time not messing up your
draft. That should be a win-win. In what way would imposing a 1K limit
on the IPv6 header chain not satisfy the general case?

Thanks - Fred
fred.l.templin@boeing.com
=20
>                                                              Ron
>=20
>=20
> > >
> > > So, it wasn't necessarily the case that 1280 was a product of
> > > "thoughtful analysis" so much as the fact that **they were rushing
> to
> > > get a spec out the door**. So now, 16 years later, we get to put it
> > > back on the 6man charter milestone list.
> >
> > We could have that discussion in 6man, sure, but I don't believe that
> > it's relevant to the question of whether draft-ietf-6man-oversized-
> > header-chain
> > is ready. This draft mitigates a known problem in terms of the
> current
> > IPv6 standards.
> >
>=20


From rbonica@juniper.net  Mon Oct 14 10:48:27 2013
Return-Path: <rbonica@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 1DC5E11E8145 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.956
X-Spam-Level: 
X-Spam-Status: No, score=-104.956 tagged_above=-999 required=5 tests=[AWL=1.643, 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 J+t4sFzk-IwO for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 10:48:20 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9455B21E80D8 for <ietf@ietf.org>; Mon, 14 Oct 2013 10:48:17 -0700 (PDT)
Received: from mail123-co9-R.bigfish.com (10.236.132.246) by CO9EHSOBE002.bigfish.com (10.236.130.65) with Microsoft SMTP Server id 14.1.225.22; Mon, 14 Oct 2013 17:48:17 +0000
Received: from mail123-co9 (localhost [127.0.0.1])	by mail123-co9-R.bigfish.com (Postfix) with ESMTP id 643718C0107; Mon, 14 Oct 2013 17:48:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(zz98dI9371I936eI542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL1de097h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail123-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(13464003)(377424004)(24454002)(51704005)(189002)(199002)(377454003)(81542001)(79102001)(77096001)(56816003)(80022001)(66066001)(76482001)(65816001)(74366001)(81342001)(74706001)(74662001)(80976001)(31966008)(83072001)(83322001)(47446002)(19580395003)(74502001)(81816001)(63696002)(54316002)(54356001)(77982001)(85306002)(53806001)(56776001)(59766001)(33646001)(69226001)(50986001)(49866001)(4396001)(19580405001)(47736001)(47976001)(74876001)(81686001)(76786001)(74316001)(76796001)(51856001)(76576001)(46102001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail123-co9 (localhost.localdomain [127.0.0.1]) by mail123-co9 (MessageSwitch) id 1381772812407517_8204; Mon, 14 Oct 2013 17:46:52 +0000 (UTC)
Received: from CO9EHSMHS027.bigfish.com (unknown [10.236.132.228])	by mail123-co9.bigfish.com (Postfix) with ESMTP id 5103534006D; Mon, 14 Oct 2013 17:46:43 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS027.bigfish.com (10.236.130.37) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 14 Oct 2013 17:46:42 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 14 Oct 2013 17:46:39 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.0.785.10; Mon, 14 Oct 2013 17:46:37 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.14]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.50]) with mapi id 15.00.0785.001; Mon, 14 Oct 2013 17:46:37 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyQOIKSuxn2+ZEkq4SpL/yVDcZJn0eIRg
Date: Mon, 14 Oct 2013 17:46:37 +0000
Message-ID: <f8b40eaa8cf441409e7a53fa212bcd33@CO1PR05MB442.namprd05.prod.outlook.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131012194048.0c92f558@resistor.net> <42ae3f3e73f840e2b40e62430cf8f7d7@CO1PR05MB442.namprd05.prod.outlook.com> <6.2.5.6.2.20131014072334.0d217aa8@resistor.net>
In-Reply-To: <6.2.5.6.2.20131014072334.0d217aa8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0999136621
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 14 Oct 2013 17:48:27 -0000

Not that I am aware of.....

> -----Original Message-----
> From: SM [mailto:sm@resistor.net]
> Sent: Monday, October 14, 2013 11:20 AM
> To: Ronald Bonica
> Cc: ietf@ietf.org
> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Hi Ron,
> At 16:55 13-10-2013, Ronald Bonica wrote:
> >Are you suggesting that we don't address the problem because the code
> >is too complex to touch?
>=20
> It's a known problem since at least seven years.  Given that the
> problem is labelled as a security issue there would have to be some
> changes to the specification at some point.  There were design
> decisions to implement the specification and the code has been
> deployed.  The proposed outbound change is one sentence.  The code
> change to implement that one sentence requires reviewing some
> implementation decisions (re. encapsulation, etc.).  Please note that I
> am not arguing for or against a change in the RFC 2119 key words.  The
> write-up only mentions that the draft has been implemented on stateless
> firewalls.  I am curious about whether there are any implementations
> for a host.
>=20
> Regards,
> -sm
>=20
>=20



From chair@ietf.org  Mon Oct 14 11:21:33 2013
Return-Path: <chair@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 AF34711E8152; Mon, 14 Oct 2013 11:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, 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 exmsHM6lw5mx; Mon, 14 Oct 2013 11:21:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D69311E816D; Mon, 14 Oct 2013 11:21:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Invitation to request an IETF mentor
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131014182123.11455.88441.idtracker@ietfa.amsl.com>
Date: Mon, 14 Oct 2013 11:21:23 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: mentoring-coordinators@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, 14 Oct 2013 18:21:33 -0000

All,

If you are new to the IETF, we would like to invite you to participate in t=
he new IETF Mentoring Program at the upcoming IETF 88 in Vancouver. The goa=
l of the IETF Mentoring Program is to match people new to the IETF (people =
who have participated in three or fewer face-to-face meetings or anyone reg=
istering as a student) with experienced IETF mentors. As a mentoring partic=
ipant, your mentor will personally introduce you to the IETF community, hel=
p you find your way around the IETF & the meeting, explain things, and intr=
oduce you to other attendees you might like to meet. Basically, your mentor=
 will be your personal buddy during the meeting week, and possibly afterwar=
ds.

The IETF Mentoring Program was created to help new IETF participants to get=
 up to speed rapidly and help them begin to contribute to the IETF quickly =
and easily.  If you wish to participate in the IETF Mentoring Program, you =
can follow the sign-up procedures described in the program FAQ:

https://www.ietf.org/resources/mentoring-program.html

After you follow the sign-up procedure, we will then introduce you to each =
other by email, and invite you to meet up in person at the IETF Meet & Gree=
t event on Sunday afternoon in Vancouver. From there on, you and your mento=
r decide on when and where to meet during the rest of the week and afterwar=
ds.

You are of course free to withdraw from the program at any time and for any=
 reason, no questions asked, should a need arise. But I sincerely believe t=
he IETF Mentoring Program will be a great way for new participants to get i=
ntroduced to the IETF by an experienced participant with matching interest.

Regards,
Jari Arkko
IETF Chair

From brian.e.carpenter@gmail.com  Mon Oct 14 12:34:25 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 7200211E8185; Mon, 14 Oct 2013 12:34:25 -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 d3PsYrB5lfAc; Mon, 14 Oct 2013 12:34:25 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 09C5011E816D; Mon, 14 Oct 2013 12:34:24 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id kq14so7895355pab.40 for <multiple recipients>; Mon, 14 Oct 2013 12:34:24 -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=8ZoHiqL+wyDVPOVKRnhhHFDz8PWbpaFU2tS5d3owDxs=; b=j5ckgXsE/OtiFuyKNhIOCZtKFmbyk/Ylw/3wfsu614o1wgqGkcPvzge2cEKgy9wJHr yLU/dk4jJkKP1mP8EQKJwNo/CS4sorhQDQfZBesQQrZmRjkvILB+gKojHg874pkM/95+ HFM8IqZSMIY7c/1F77aSgyrrLDzSlx1zMQ3NrLZHANhqYBfcDauTnYMUq0X2IIY5CEUB iTUw31EA0d+LTiwqzq2bbSu7C4srmeqxXppyEQmRZLL+ig+SfxHZIJ1fIlE/5mm/UHjP YNA9+W1MB/Pmp7XXWz+F+hwOnIFl8SnbO++wRzoE9mgiDH8/rBftSoTQAnmMNY3v8aJp SN9w==
X-Received: by 10.68.134.133 with SMTP id pk5mr37696138pbb.89.1381779264762; Mon, 14 Oct 2013 12:34:24 -0700 (PDT)
Received: from [192.168.178.20] (19.202.69.111.dynamic.snap.net.nz. [111.69.202.19]) by mx.google.com with ESMTPSA id a6sm33043717pbr.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 12:34:23 -0700 (PDT)
Message-ID: <525C473D.4080403@gmail.com>
Date: Tue, 15 Oct 2013 08:34:21 +1300
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: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Mon, 14 Oct 2013 19:34:25 -0000

Fred,

On 15/10/2013 06:38, Templin, Fred L wrote:
...
>> We could have that discussion in 6man, sure, but I don't believe that
>> it's
>> relevant to the question of whether draft-ietf-6man-oversized-header-
>> chain
>> is ready.
> 
> If it messes up tunnels, then it's not ready.

That doesn't follow. See below.

>> This draft mitigates a known problem in terms of the current
>> IPv6 standards.
> 
> If that problem is also mitigated by a measure that does not mess
> up tunnels, then wouldn't that be worth considering before
> finalizing this publication.

The draft mitigates a known problem with communication paths that
do not include nested tunnels requiring nested fragmentation,
where the nested tunnel has to deal with an MTU <1280 *and* where
the nested tunnel goes through a firewall that wants to analyse
the complete header chain of the innermost packet.

No, I don't think it's worth considering that case before specifying
this mitigation.

     Brian

From presnick@qti.qualcomm.com  Mon Oct 14 12:45:39 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 BB29511E818E for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 12:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.355
X-Spam-Level: 
X-Spam-Status: No, score=-106.355 tagged_above=-999 required=5 tests=[AWL=-0.356, BAYES_00=-2.599, J_CHICKENPOX_43=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 QKqQZbsFb734 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 12:45:35 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6792521E80DC for <ietf@ietf.org>; Mon, 14 Oct 2013 12:45:34 -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=1381779934; x=1413315934; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=t/NysL/l+KnzcMgBT7jS3hxmzyuI8ICR6jQsvh7yIjg=; b=NGe5XK5+GWoEYWwY7SmTRemC5g10Pa6DEMpWTeMC8QjJOLFKspSD+xVT cjVpB5IGIbvPP0pNDTrLdK0wqkd00fHpPZx+igqCWYznd/BoK2dKXuYBU oOVaT9zGn1bOtf99lTnfwjkooHo8Lqyb9P5yOHxCkGy6S+ycMk8BqDIXD Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,7228"; a="81087780"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 14 Oct 2013 12:45:34 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7228"; a="568789881"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Oct 2013 12:45:33 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 14 Oct 2013 12:45:33 -0700
Message-ID: <525C49DC.9090102@qti.qualcomm.com>
Date: Mon, 14 Oct 2013 14:45:32 -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: t.p. <daedulus@btconnect.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net>
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: Mon, 14 Oct 2013 19:45:39 -0000

On 10/13/13 5:42 AM, t.p. wrote:
> I find the security considerations in this registration rather weak.
> What might have sufficed in 2005 seems to me inadequate for 2013.  I
> would expect a clearer statement of what are or are not considered
> threats or attacks and what mitigations there then are for them.
>    

I don't know that everyone is really understanding the request that is 
being made here. It is a bit unusual.

RFC 4180 <http://tools.ietf.org/html/rfc4180> contains the current 
registration for text/csv. That registration has the "Change Controller" 
as "IESG", which is to say it's a registration from an IETF document. 
Barring any change, that registration would remain exactly as it is 
(including its current Security Considerations).

Someone outside of the IETF is publishing a document describing how to 
use fragment identifiers with text/csv. That document is being published 
in the Independent Stream by the RFC Editor. Since the publication of 
RFC 4180, "fragment identifier" was added to the media type registration 
procedures. <http://tools.ietf.org/html/rfc6838#section-4.11> The 
present document (draft-hausenblas) wants to update the existing IETF 
registration to include it's idea of fragment identifiers (which was 
absent from the RFC 4180 registration), though it will leave the IETF 
(via the IESG) as "Change Controller".

This Last Call is to find out if the IETF is OK with a non-IETF document 
updating an IETF registration. If the answer is "no", then we leave the 
4180 registration in place, or we tell the ISE that draft-hausenblas is 
not conforming to IETF processes and that we want it to be an 
IETF-stream document. If the answer is "yes", we go ahead with the 
registration change based on whatever the ISE publishes. We can send 
comments to the author and to the ISE asking for changes, but it's not 
an IETF document; IETF consensus is not required and the ISE can publish 
it anyway.

So, your Last Call comments are *simply* on the registration update. The 
document is not ours on which to comment.

pr

> ----- Original Message -----
> From: "The IESG"<iesg@ietf.org>
> To: "IETF Announcement List"<ietf-announce@ietf.org>
> Cc:<iana@iana.org>
> Sent: Thursday, October 10, 2013 7:50 PM
>
> The IESG has received a request to update the IANA registration of
> the text/csv media type, adding an optional fragment identifier.
> The request comes from a document in the Independent stream, and the
> IESG is the change controller for the text/csv media type.
>
> 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-10-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.
>
> The document making the request can be obtained via
> http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/
>    

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From Fred.L.Templin@boeing.com  Mon Oct 14 12:55:44 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80311E81A3; Mon, 14 Oct 2013 12:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.482
X-Spam-Level: 
X-Spam-Status: No, score=-6.482 tagged_above=-999 required=5 tests=[AWL=0.117,  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 RJrnivfBp7yA; Mon, 14 Oct 2013 12:55:26 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 179E611E816D; Mon, 14 Oct 2013 12:55:10 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9EJt5Eb001824; Mon, 14 Oct 2013 14:55:05 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9EJt4eX001804 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 14 Oct 2013 14:55:05 -0500
Received: from XCH-BLV-207.nw.nos.boeing.com (10.57.37.63) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 14 Oct 2013 12:55:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-207.nw.nos.boeing.com ([10.57.37.63]) with mapi id 14.03.0158.001; Mon, 14 Oct 2013 12:55:03 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyRRhebc9KTehbEGO6mhunuAlj5n0mDGA
Date: Mon, 14 Oct 2013 19:55:02 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812D8F7@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com> <525C473D.4080403@gmail.com>
In-Reply-To: <525C473D.4080403@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Mon, 14 Oct 2013 19:55:44 -0000

SGkgQnJpYW4sDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQnJpYW4g
RSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb21dDQo+IFNlbnQ6
IE1vbmRheSwgT2N0b2JlciAxNCwgMjAxMyAxMjozNCBQTQ0KPiBUbzogVGVtcGxpbiwgRnJlZCBM
DQo+IENjOiBGZXJuYW5kbyBHb250OyBSYXkgSHVudGVyOyA2bWFuIE1haWxpbmcgTGlzdDsgaWV0
ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi02bWFuLW92
ZXJzaXplZC1oZWFkZXItY2hhaW4tMDgudHh0Pg0KPiAoSW1wbGljYXRpb25zIG9mIE92ZXJzaXpl
ZCBJUHY2IEhlYWRlciBDaGFpbnMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBGcmVkLA0K
PiANCj4gT24gMTUvMTAvMjAxMyAwNjozOCwgVGVtcGxpbiwgRnJlZCBMIHdyb3RlOg0KPiAuLi4N
Cj4gPj4gV2UgY291bGQgaGF2ZSB0aGF0IGRpc2N1c3Npb24gaW4gNm1hbiwgc3VyZSwgYnV0IEkg
ZG9uJ3QgYmVsaWV2ZQ0KPiB0aGF0DQo+ID4+IGl0J3MNCj4gPj4gcmVsZXZhbnQgdG8gdGhlIHF1
ZXN0aW9uIG9mIHdoZXRoZXIgZHJhZnQtaWV0Zi02bWFuLW92ZXJzaXplZC0NCj4gaGVhZGVyLQ0K
PiA+PiBjaGFpbg0KPiA+PiBpcyByZWFkeS4NCj4gPg0KPiA+IElmIGl0IG1lc3NlcyB1cCB0dW5u
ZWxzLCB0aGVuIGl0J3Mgbm90IHJlYWR5Lg0KPiANCj4gVGhhdCBkb2Vzbid0IGZvbGxvdy4gU2Vl
IGJlbG93Lg0KPiANCj4gPj4gVGhpcyBkcmFmdCBtaXRpZ2F0ZXMgYSBrbm93biBwcm9ibGVtIGlu
IHRlcm1zIG9mIHRoZSBjdXJyZW50DQo+ID4+IElQdjYgc3RhbmRhcmRzLg0KPiA+DQo+ID4gSWYg
dGhhdCBwcm9ibGVtIGlzIGFsc28gbWl0aWdhdGVkIGJ5IGEgbWVhc3VyZSB0aGF0IGRvZXMgbm90
IG1lc3MNCj4gPiB1cCB0dW5uZWxzLCB0aGVuIHdvdWxkbid0IHRoYXQgYmUgd29ydGggY29uc2lk
ZXJpbmcgYmVmb3JlDQo+ID4gZmluYWxpemluZyB0aGlzIHB1YmxpY2F0aW9uLg0KPiANCj4gVGhl
IGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gd2l0aCBjb21tdW5pY2F0aW9uIHBhdGhz
IHRoYXQNCj4gZG8gbm90IGluY2x1ZGUgbmVzdGVkIHR1bm5lbHMgcmVxdWlyaW5nIG5lc3RlZCBm
cmFnbWVudGF0aW9uLA0KPiB3aGVyZSB0aGUgbmVzdGVkIHR1bm5lbCBoYXMgdG8gZGVhbCB3aXRo
IGFuIE1UVSA8MTI4MCAqYW5kKiB3aGVyZQ0KPiB0aGUgbmVzdGVkIHR1bm5lbCBnb2VzIHRocm91
Z2ggYSBmaXJld2FsbCB0aGF0IHdhbnRzIHRvIGFuYWx5c2UNCj4gdGhlIGNvbXBsZXRlIGhlYWRl
ciBjaGFpbiBvZiB0aGUgaW5uZXJtb3N0IHBhY2tldC4NCg0KQnV0IHR1bm5lbHMgLSBhbmQgdHVu
bmVscyB3aXRoaW4gdHVubmVscyAtIG5lZWQgdG8gYmUgY29uc2lkZXJlZA0KYXMgcGFydCBvZiB0
aGUgYXJjaGl0ZWN0dXJlLiBJIGhhdmUgdmlzaWJpbGl0eSBpbnRvIHRoZSBuZXR3b3JrDQpvcGVy
YXRpb25zIG9mIGEgbWFqb3IgbXVsdGktbmF0aW9uYWwgY29ycG9yYXRpb24sIGFuZCBJIGNhbiB0
ZWxsDQp5b3UgdGhhdCBJIHNlZSB0dW5uZWxzIHdpdGhpbiB0dW5uZWxzIGluIG9wZXJhdGlvbmFs
IHByYWN0aWNlIHRvZGF5Lg0KSSBhbHNvIGhhdmUgdmlzaWJpbGl0eSBpbnRvIGNpdmlsIGF2aWF0
aW9uIGFuZCBEb0QgbmV0d29ya3MsIGFuZA0KSSBzZWUgYW4gZW1lcmdpbmcgdHJlbmQgZm9yIG1v
YmlsZSBuZXR3b3Jrcy4gQ29uc2lkZXIgYSBtb2JpbGUNCm5ldHdvcmsgQiB0aGF0IGNvbWVzIG9u
dG8gYSBsaW5rIG9mZmVyZWQgYnkgbW9iaWxlIG5ldHdvcmsgQS4NClRoZW4sIG1vYmlsZSBuZXR3
b3JrIEMgY29tZXMgb250byBhIGxpbmsgb2ZmZXJlZCBieSBCLiBUaGVuLCBldGMuDQpUaGVuLCB0
aGUgbmV4dCB0aGluZyB5b3Uga25vdywgaXQncyB0dXJ0bGVzIGFsbCB0aGUgd2F5IGRvd24uDQoN
CkZyYWdtZW50YXRpb24gaXMgdGhlIHRvb2wgdGhhdCBlbmFibGVzIGVuZGxlc3MgcmVjdXJzaW9u
LiBPciwgYXQNCmxlYXN0LCByZWN1cnNpb24gdXAgdG8gc29tZSBkZWZpbmVkIGxpbWl0LiBBdCBs
ZWFzdCBmb3IgdGhlIGZpcnN0DQpzZXZlcmFsIGxldmVscyBvZiByZWN1cnNpb24sIG1pZGRsZWJv
eGVzIHNob3VsZCBiZSBhYmxlIHRvIHNlZSBhbGwNCmhvc3QtaW5zZXJ0ZWQgaGVhZGVycyB3aXRo
aW4gdGhlIGZpcnN0IGZyYWdtZW50Lg0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBi
b2VpbmcuY29tDQoNCg0KPiBObywgSSBkb24ndCB0aGluayBpdCdzIHdvcnRoIGNvbnNpZGVyaW5n
IHRoYXQgY2FzZSBiZWZvcmUgc3BlY2lmeWluZw0KPiB0aGlzIG1pdGlnYXRpb24uDQo+IA0KPiAg
ICAgIEJyaWFuDQo=

From paf@frobbit.se  Mon Oct 14 22:31:31 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 1FA1C21E81A5 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 22:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level: 
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 LLVitpuhaoFL for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 22:31:30 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 271F621F9635 for <ietf@ietf.org>; Mon, 14 Oct 2013 22:31:25 -0700 (PDT)
Received: from dhcp-24-112.ripemtg.ripe.net (dhcp-24-112.ripemtg.ripe.net [193.0.24.112]) by mail.frobbit.se (Postfix) with ESMTPSA id 257AA24013; Tue, 15 Oct 2013 07:31:22 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_4C68F51C-0EB7-41FA-A1E5-D7650CC4DA66"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Of governments and representation (was: Montevideo Statement)
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <525BFDBC.2080400@alvestrand.no>
Date: Mon, 14 Oct 2013 23:37:19 +0300
Message-Id: <DB526877-8459-497F-873D-B1C3678371C9@frobbit.se>
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <525BFDBC.2080400@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1510)
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, 15 Oct 2013 05:31:31 -0000

--Apple-Mail=_4C68F51C-0EB7-41FA-A1E5-D7650CC4DA66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

+1

On 14 okt 2013, at 17:20, Harald Alvestrand <harald@alvestrand.no> =
wrote:

> For what it's worth, I think Russ and Jari did the right thing in =
signing the statement the way they did, at the time they did it, with =
the prior consultation they did.
>=20
> I was not consulted. And I'm glad they are capable of acting at this =
level without consulting me.
>=20
>=20
>=20
> On 10/11/2013 06:02 PM, John Curran wrote:
>> Folks -
>>=20
>> As a result of the Internet's growing social and economic importance, =
the underlying
>> Internet structures are receiving an increasing level of attention by =
both governments
>> and civil society.  The recent revelations regarding US government =
surveillance of
>> the Internet are now greatly accelerating government attention on all =
of the Internet
>> institutions, the IETF included.  All of this attention is likely =
bring about significant
>> changes in the Internet ecosystem, potentially including how the IETF =
interacts with
>> governments, civil society, and other Internet organizations =
globally.
>>=20
>> In my personal view, it is a very important for the IETF to select =
leadership who can
>> participate in any discussions that occur, and it would further be =
prudent for the IETF
>> leaders to be granted a sufficient level of support by the community =
to take positions
>> in those discussions and make related statements, to the extent the =
positions and
>> the statements are aligned with established IETF positions and/or =
philosophy.
>>=20
>> The most interesting part of the myriad of Internet Governance =
discussions is that
>> multiple organizations are all pushing ahead independently from one =
another, which
>> results in a very dynamic situation where we often don't even know =
that there will be
>> a conference or meeting until after its announced, do not know =
auspices under which
>> it will be held, nor what the scope of the discussions held will =
ultimately be.  However,
>> the failure of any of the Internet organizations to participate will =
not actually prevent
>> consideration of a variety of unique and colorful proposals for =
improving the Internet
>> and/or the IETF, nor will it preclude adoption even in the absence of =
IETF input...
>>=20
>> The IETF is a very important Internet institution, and it deserves to =
be represented
>> in any discussions which might propose changes to the fundamental =
mechanisms of
>> Internet cooperation.  It would be a wonderful world indeed if all of =
these discussions
>> started with submission of an Internet Draft and discussion on open =
mailing lis, but
>> that hasn't been the modus operandi of governments and is probably =
too much to
>> realistically expect.
>>=20
>> /John
>=20


--Apple-Mail=_4C68F51C-0EB7-41FA-A1E5-D7650CC4DA66
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSXFX/rMabGguI180RAofOAJ4jC7ebGdzLZt7M5c9wYmX4ldtwPgCfaeQc
gixQd1nlLHl/cYO+NQTwrh0=
=Mt9y
-----END PGP SIGNATURE-----

--Apple-Mail=_4C68F51C-0EB7-41FA-A1E5-D7650CC4DA66--

From mohta@necom830.hpcl.titech.ac.jp  Mon Oct 14 23:32: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 16FB011E815F for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 23:32: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 MZgu8gl-ITPh for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 23:32: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 83F5E11E8174 for <ietf@ietf.org>; Mon, 14 Oct 2013 23:32:45 -0700 (PDT)
Received: (qmail 19930 invoked from network); 15 Oct 2013 06:27:06 -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; 15 Oct 2013 06:27:06 -0000
Message-ID: <525CE134.1040608@necom830.hpcl.titech.ac.jp>
Date: Tue, 15 Oct 2013 15:31:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com> <2134F8430051B64F815C691A62D9831811BDD3@XCH-BLV-504.nw.nos.boeing.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811DF44@XCH-BLV-504.nw.nos.boeing.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: Tue, 15 Oct 2013 06:32:51 -0000

Templin, Fred L wrote:

> Take the simplest case when the host assumes a path MTU of 1280.
> If there is a tunnel in the path that crosses another 1280 link,
> then the tunnel has to fragment, and the header chain might not
> all fit within the first fragment if the host does not allow
> headspace room. If the host limits the size of its header chain
> to 1280 - 512 = 1024 bytes, then the entire chain should fit
> within the first fragment even if there are multiple nested
> tunnel ingresses on the path and each one of them fragments.

Why do you think the first fragment is considerably longer
than 1024B?

As is specified in rfc791:

      In the above procedure each fragment (except the last) was made
      the maximum allowable size.  An alternative might produce less
      than the maximum size datagrams.  For example, one could implement
      a fragmentation procedure that repeatly divided large datagrams in
      half until the resulting fragments were less than the maximum
      transmission unit size.

it is allowed (and is better) to fragment a 1300B packet into two
mostly equally sized (about 700B) packets than two packets of a
1280B (or 1276B) one and a much shorter one.

It is especially so when tunnels with outer MTU of 1280B, which
can carry 700B (but not 1276B/1280B) packets without further
fragmentation, are used.

You should also assume that outer IP of a tunnel may also have
its own lengthy extension headers, length of which must also
be restricted (much below 1280B).

Note also that DNS requires each UDP packet carry a 512B message,
header chain (including UDP header) must be shorter than 989B
(minimum reassembly buffer size of IPv6 is 1500B).

Worse, as some extension headers are inserted without application
control, e.g.:

   In that case, the IPv6 node
   is not required to reduce the size of subsequent packets to less than
   1280, but must include a Fragment header in those packets so that the
   IPv6-to-IPv4 translating router can obtain a suitable Identification
   value to use in resulting IPv4 fragments. [rfc2460]

and

   The Home Address option is carried by the Destination Option
   extension header (Next Header value = 60).  It is used in a packet
   sent by a mobile node while away from home, to inform the recipient
   of the mobile node's home address. [rfc3775]

it is really hard, if not impossible, to let transport/application
protocols (such as DNS and TCP) adjust payload size to avoid
fragmentation. As noted above, even with fragmentation, DNS can't
adjust payload size below 512B.

						Masataka Ohta


From mohta@necom830.hpcl.titech.ac.jp  Mon Oct 14 23:52:10 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 94F9A11E8102 for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 23:52:10 -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 pCT2QF0LRztb for <ietf@ietfa.amsl.com>; Mon, 14 Oct 2013 23:52: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 24CBE11E810A for <ietf@ietf.org>; Mon, 14 Oct 2013 23:52:04 -0700 (PDT)
Received: (qmail 20028 invoked from network); 15 Oct 2013 06:46:27 -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; 15 Oct 2013 06:46:27 -0000
Message-ID: <525CE5BD.7020208@necom830.hpcl.titech.ac.jp>
Date: Tue, 15 Oct 2013 15:50:37 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831811AEFC@XCH-BLV-504.nw.nos.boeing.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: Tue, 15 Oct 2013 06:52:11 -0000

Templin, Fred L wrote:

> This means that stateless firewalls are being directed to discontinue
> extension header parsing when a first encapsulated IPv6 header is
> encountered - even though there may be many more parsable (inner)
> headers that follow.

Even without tunnels, firewalls MUST be able to parse ICMPv6 error
messages generated behind it, even though ICMPv6 is explicitly
allowed to have its own lengthy header chain:

   Every ICMPv6 message is preceded by an IPv6 header and zero or more
   IPv6 extension headers. [rfc2463]

Even without firewalls, ICMPv6 still causes a problem because:

           As much of invoking packet
       as will fit without the ICMPv6 packet
       exceeding the minimum IPv6 MTU [IPv6] [rfc2463]

a host sending the original packet can not identify which packet
sent by it caused the error, if tail part of header-chain of
inner packet is omitted.

						Masataka Ohta


From dirkx@webweaving.org  Tue Oct 15 01:12:39 2013
Return-Path: <dirkx@webweaving.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 C8E1521F999B for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 01:12: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 k90kPudwMMPD for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 01:12:33 -0700 (PDT)
Received: from ibiza.webweaving.org (ibiza.webweaving.org [204.109.56.32]) by ietfa.amsl.com (Postfix) with ESMTP id 2C02011E811D for <ietf@ietf.org>; Tue, 15 Oct 2013 01:12:31 -0700 (PDT)
Received: from pikmeer.webweaving.org (pikmeer.webweaving.org [178.18.23.51]) by ibiza.webweaving.org (8.14.7/8.14.7) with ESMTP id r9F8CSgv074350; Tue, 15 Oct 2013 08:12:28 GMT (envelope-from dirkx@webweaving.org)
Received: from acorn.leiden.webweaving.org (a83-163-239-115.adsl.xs4all.nl [83.163.239.115]) (authenticated bits=0) by pikmeer.webweaving.org (8.14.7/8.14.7) with ESMTP id r9F8CQrw059468 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Oct 2013 08:12:27 GMT (envelope-from dirkx@webweaving.org)
X-Authentication-Warning: pikmeer.webweaving.org: Host a83-163-239-115.adsl.xs4all.nl [83.163.239.115] claimed to be acorn.leiden.webweaving.org
Content-Type: multipart/signed; boundary="Apple-Mail=_58421007-98E8-492E-9BFC-957433FB8373"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Of governments and representation (was: Montevideo Statement)
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
In-Reply-To: <525BFDBC.2080400@alvestrand.no>
Date: Tue, 15 Oct 2013 10:12:23 +0200
Message-Id: <5D559B60-FC6E-42B2-B288-C2A879786C1D@webweaving.org>
References: <7B8B67FC-E0CD-4CE2-BF97-DF01630E1C1E@istaff.org> <525BFDBC.2080400@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (ibiza.webweaving.org [204.109.56.32]); Tue, 15 Oct 2013 08:12:29 +0000 (UTC)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (pikmeer.webweaving.org [178.18.23.51]); Tue, 15 Oct 2013 08:12:27 +0000 (UTC)
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, 15 Oct 2013 08:12:39 -0000

--Apple-Mail=_58421007-98E8-492E-9BFC-957433FB8373
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hear, Hear !

Thanks Harold. This is exactly why in-person representation of =
sufficiently empowered wise people is so valuable.

Dw.

Op 14 okt. 2013, om 16:20 heeft Harald Alvestrand <harald@alvestrand.no> =
het volgende geschreven:

> For what it's worth, I think Russ and Jari did the right thing in =
signing the statement the way they did, at the time they did it, with =
the prior consultation they did.
>=20
> I was not consulted. And I'm glad they are capable of acting at this =
level without consulting me.
>=20
>=20
>=20
> On 10/11/2013 06:02 PM, John Curran wrote:
>> Folks -
>>=20
>> As a result of the Internet's growing social and economic importance, =
the underlying
>> Internet structures are receiving an increasing level of attention by =
both governments
>> and civil society.  The recent revelations regarding US government =
surveillance of
>> the Internet are now greatly accelerating government attention on all =
of the Internet
>> institutions, the IETF included.  All of this attention is likely =
bring about significant
>> changes in the Internet ecosystem, potentially including how the IETF =
interacts with
>> governments, civil society, and other Internet organizations =
globally.
>>=20
>> In my personal view, it is a very important for the IETF to select =
leadership who can
>> participate in any discussions that occur, and it would further be =
prudent for the IETF
>> leaders to be granted a sufficient level of support by the community =
to take positions
>> in those discussions and make related statements, to the extent the =
positions and
>> the statements are aligned with established IETF positions and/or =
philosophy.
>>=20
>> The most interesting part of the myriad of Internet Governance =
discussions is that
>> multiple organizations are all pushing ahead independently from one =
another, which
>> results in a very dynamic situation where we often don't even know =
that there will be
>> a conference or meeting until after its announced, do not know =
auspices under which
>> it will be held, nor what the scope of the discussions held will =
ultimately be.  However,
>> the failure of any of the Internet organizations to participate will =
not actually prevent
>> consideration of a variety of unique and colorful proposals for =
improving the Internet
>> and/or the IETF, nor will it preclude adoption even in the absence of =
IETF input...
>>=20
>> The IETF is a very important Internet institution, and it deserves to =
be represented
>> in any discussions which might propose changes to the fundamental =
mechanisms of
>> Internet cooperation.  It would be a wonderful world indeed if all of =
these discussions
>> started with submission of an Internet Draft and discussion on open =
mailing lis, but
>> that hasn't been the modus operandi of governments and is probably =
too much to
>> realistically expect.
>>=20
>> /John
>=20


--Apple-Mail=_58421007-98E8-492E-9BFC-957433FB8373
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: This message is encrypted and/or signed with PGP (gnu-pg, gpg). Contact dirkx@webweaving.org if you cannot read it.

iQCVAwUBUlz46jGmPZbsFAuBAQJNWgP/e7jCT/Y340WsrBYcSX5C2BZtddizoAM8
v6OrHvG9uUtYdBgpbWwiYviiW+OTf5Y3Bdde1ofBYHiFJVY6+3RbztI9B/UotZY0
zUAvFQHUjWAO3/1icMrhpTPD/1Agegi0Oq+dTROJPLo9YKiFGllBuKJQYoL81jiY
k7wH42W70wI=
=UaXO
-----END PGP SIGNATURE-----

--Apple-Mail=_58421007-98E8-492E-9BFC-957433FB8373--

From john-ietf@jck.com  Tue Oct 15 01:54: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 02EE521F9CA4 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 01:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.424
X-Spam-Level: 
X-Spam-Status: No, score=-103.424 tagged_above=-999 required=5 tests=[AWL=-0.425, BAYES_00=-2.599, J_CHICKENPOX_43=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 YLX4AhYLNxeo for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 01:54:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D5D7711E8120 for <ietf@ietf.org>; Tue, 15 Oct 2013 01:54: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 1VW0Oy-000OGm-5p; Tue, 15 Oct 2013 04:54:52 -0400
Date: Tue, 15 Oct 2013 04:54:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media	type(see <draft-hausenblas-csv-fragment-06.txt>)
Message-ID: <102BC46338B27611350C249D@JcK-HP8200.jck.com>
In-Reply-To: <525C49DC.9090102@qti.qualcomm.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.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, 15 Oct 2013 08:54:58 -0000

--On Monday, October 14, 2013 14:45 -0500 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> I don't know that everyone is really understanding the request
> that is being made here. It is a bit unusual.
> 
> RFC 4180 <http://tools.ietf.org/html/rfc4180> contains the
> current registration for text/csv. That registration has the
> "Change Controller" as "IESG", which is to say it's a
> registration from an IETF document. Barring any change, that
> registration would remain exactly as it is (including its
> current Security Considerations).
>...
> This Last Call is to find out if the IETF is OK with a
> non-IETF document updating an IETF registration. If the answer
> is "no", then we leave the 4180 registration in place, or we
> tell the ISE that draft-hausenblas is not conforming to IETF
> processes and that we want it to be an IETF-stream document.
> If the answer is "yes", we go ahead with the registration
> change based on whatever the ISE publishes. We can send
> comments to the author and to the ISE asking for changes, but
> it's not an IETF document; IETF consensus is not required and
> the ISE can publish it anyway.
>...

In a slightly broader interpretation of that question, I believe
that having Independent (or even IAB) stream documents modify
registrations that are required, either by the registration
procedure or the registration itself, to be under IETF change
control is a bad idea.  If we don't like that constrain, we
should modify the registration, not conduct odd Last Calls.  I
would strongly support processing this document in the IETF
Stream as an individual submission (and, while that slips over
into the substantive part, approving it for publication and
modification of the registration on that basis).  

My reasoning is that, while the change seems fine, the precedent
seems atrocious.  If this is approved via Independent Stream
publication and the next case that comes along is, unlike this
one, generally hated by the community, the amount of
hair-splitting required to deny that one having approved this
one would be impressive.. and bad for the IETF.

Of course, the ISE could go ahead and publish this document and
the IESG could block the registration, leading to a confusing
situation.  I hope we don't have to go there.

       john

p.s. W3C is circulating a draft charter for a WG that might
affect CSV on the web.  Because having a hard-to-change
Informational RFC and IANA registration that was inconsistent
with W3C recommendations would be a generally bad idea, some
coordination may be in order, especially to verify that the
current draft is not an end run around W3C efforts.



From klensin@jck.com  Tue Oct 15 02:20:36 2013
Return-Path: <klensin@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 BCC3621F9ED1 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 02:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.427
X-Spam-Level: 
X-Spam-Status: No, score=-3.427 tagged_above=-999 required=5 tests=[AWL=0.172,  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 Co9cQ5JUhIiI for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 02:20:31 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E0E2321F9D0E for <ietf@ietf.org>; Tue, 15 Oct 2013 02:20:25 -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 <klensin@jck.com>) id 1VW0nZ-000OIj-Mq; Tue, 15 Oct 2013 05:20:17 -0400
Date: Tue, 15 Oct 2013 05:20:12 -0400
From: John C Klensin <klensin@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Montevideo statement
Message-ID: <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.com>
In-Reply-To: <18100.1381543263@sandelman.ca>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com> <18100.1381543263@sandelman.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: 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, 15 Oct 2013 09:20:36 -0000

--On Friday, October 11, 2013 22:01 -0400 Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

> Phillip Hallam-Baker <hallam@gmail.com> wrote:
>     > I think that is a better approach actually. The CC TLDs
> are in effect     > members of a bridge CA and ICANN is merely
> the bridge administrator.
> 
> It is an interesting way to say it, and put that way, I like
> it.
>...
> However, it the root of the trust in country X is the
> government of country X, then government can essentially
> internalize/nationalize all the liability associated with
> trusting them.  It would be much like governments do with
> nuclear power: it only works out because the governments
> provide the insurance in the form of legislation...

Without taking a position on the idea, one observation about
possible unintended side effects:

The ccTLD system grew up at a time when many governments were
fairly hostile to the Internet and/or the DNS (that is different
from being hostile to, e.g., free and private flow of
information over the Internet).  The ccTLD environment still
supports ccTLD administrations that are independent of the local
government unless that government is so hostile to them that it
is willing to use national law to force them out.  One
consequence of that model is that, for the ccTLD system to
function, neither IANA nor anyone else needs to figure out who
is the actual, legitimate, government of a country.  Governments
have a tendency to be quite jealous of their rights to
"recognize" other governments (or not).  Keeping IANA out of
that business was an explicit goal at the time RFC 1591 was
written, for multiple reasons.

If the government of a country is the required root of trust in
that country's ccTLD, we take ourselves several steps closer to
requiring that governments approve ccTLD administrations (not
merely not being actively opposed to them).  We create an attack
vector from the government on the ccTLD and registrations in it.
Unlike shutting down a ccTLD administration by offering to throw
its membership in jail, the control and mechanisms that implies
may not require whatever passes for due process in that country.
And such trust authority can provide a vector for required
government approval of individual registrations and registrants,
just as the US Government has turned a general IANA oversight
requirement into case-by-case approval of root entries.

Be careful what you wish for.
    best,
      john


From daedulus@btconnect.com  Tue Oct 15 02:37:19 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 5590B21E80B4 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 02:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.519
X-Spam-Level: 
X-Spam-Status: No, score=-4.519 tagged_above=-999 required=5 tests=[AWL=1.480,  BAYES_00=-2.599, J_CHICKENPOX_43=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 P9cEDzlNEWi0 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 02:37:14 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 177FA11E817D for <ietf@ietf.org>; Tue, 15 Oct 2013 02:37:14 -0700 (PDT)
Received: from mail20-co9-R.bigfish.com (10.236.132.244) by CO9EHSOBE002.bigfish.com (10.236.130.65) with Microsoft SMTP Server id 14.1.225.22; Tue, 15 Oct 2013 09:37:13 +0000
Received: from mail20-co9 (localhost [127.0.0.1])	by mail20-co9-R.bigfish.com (Postfix) with ESMTP id 8950D3200AE; Tue, 15 Oct 2013 09:37:13 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah1de097h186068h8275bh8275dhz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail20-co9 (localhost.localdomain [127.0.0.1]) by mail20-co9 (MessageSwitch) id 1381829830731213_11666; Tue, 15 Oct 2013 09:37:10 +0000 (UTC)
Received: from CO9EHSMHS006.bigfish.com (unknown [10.236.132.250])	by mail20-co9.bigfish.com (Postfix) with ESMTP id ADE8E4C006C; Tue, 15 Oct 2013 09:37:10 +0000 (UTC)
Received: from DBXPRD0710HT001.eurprd07.prod.outlook.com (157.56.253.197) by CO9EHSMHS006.bigfish.com (10.236.130.16) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 15 Oct 2013 09:37:10 +0000
Received: from DB3PRD0411HT003.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.79.164) with Microsoft SMTP Server (TLS) id 14.16.371.2; Tue, 15 Oct 2013 09:36:48 +0000
Message-ID: <007501cec989$cf76e060$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
Date: Tue, 15 Oct 2013 10:34:47 +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.53]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 15 Oct 2013 09:37:19 -0000

----- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "t.p." <daedulus@btconnect.com>
Cc: <ietf@ietf.org>
Sent: Monday, October 14, 2013 8:45 PM
> On 10/13/13 5:42 AM, t.p. wrote:
> > I find the security considerations in this registration rather weak.
> > What might have sufficed in 2005 seems to me inadequate for 2013.  I
> > would expect a clearer statement of what are or are not considered
> > threats or attacks and what mitigations there then are for them.
>
> I don't know that everyone is really understanding the request that is
> being made here. It is a bit unusual.
>
> RFC 4180 <http://tools.ietf.org/html/rfc4180> contains the current
> registration for text/csv. That registration has the "Change
Controller"
> as "IESG", which is to say it's a registration from an IETF document.
> Barring any change, that registration would remain exactly as it is
> (including its current Security Considerations).
>
> Someone outside of the IETF is publishing a document describing how to
> use fragment identifiers with text/csv. That document is being
published
> in the Independent Stream by the RFC Editor. Since the publication of
> RFC 4180, "fragment identifier" was added to the media type
registration
> procedures. <http://tools.ietf.org/html/rfc6838#section-4.11> The
> present document (draft-hausenblas) wants to update the existing IETF
> registration to include it's idea of fragment identifiers (which was
> absent from the RFC 4180 registration), though it will leave the IETF
> (via the IESG) as "Change Controller".
>
> This Last Call is to find out if the IETF is OK with a non-IETF
document
> updating an IETF registration. If the answer is "no", then we leave
the
> 4180 registration in place, or we tell the ISE that draft-hausenblas
is
> not conforming to IETF processes and that we want it to be an
> IETF-stream document. If the answer is "yes", we go ahead with the
> registration change based on whatever the ISE publishes. We can send
> comments to the author and to the ISE asking for changes, but it's not
> an IETF document; IETF consensus is not required and the ISE can
publish
> it anyway.
>
> So, your Last Call comments are *simply* on the registration update.
The
> document is not ours on which to comment.

Indeed, I fully understand that.  It is the new registration for this
media type that I am commenting on, nothing else, that the new
registration, if approved, will cause the IANA entry to point to the
text from this 2013 (more likely 2014) RFC for which I would expect the
Security Considerations, an integral part of this registration
regardless of what else is in this I-D, to be up to the standards that
the IETF impose on work carried out in 2013, which are higher than those
that were in place 10 years ago.  As I know from having been part of the
process of producing RFC over the past 10 years.

So I regard this registration as unsuitable as it stands and would
expect the IESG to ask for an updated Security Considerations.

I am not commenting on any aspect of this I-D except insofar as it
provides text that will form the registration as it will appear in the
IANA reference.

Tom Petch

>
> pr
>
> > ----- Original Message -----
> > From: "The IESG"<iesg@ietf.org>
> > To: "IETF Announcement List"<ietf-announce@ietf.org>
> > Cc:<iana@iana.org>
> > Sent: Thursday, October 10, 2013 7:50 PM
> >
> > The IESG has received a request to update the IANA registration of
> > the text/csv media type, adding an optional fragment identifier.
> > The request comes from a document in the Independent stream, and the
> > IESG is the change controller for the text/csv media type.
> >
> > 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-10-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.
> >
> > The document making the request can be obtained via
> > http://datatracker.ietf.org/doc/draft-hausenblas-csv-fragment/
> >
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>



From randy@psg.com  Tue Oct 15 04:20: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 6379221F9FFF for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 04:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 VhDVaogQYyv4 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 04:20:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 4850321F9DE1 for <ietf@ietf.org>; Tue, 15 Oct 2013 04:20:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VW2fo-0001Qi-ME; Tue, 15 Oct 2013 11:20:24 +0000
Date: Tue, 15 Oct 2013 14:20:24 +0300
Message-ID: <m2eh7mpypz.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <klensin@jck.com>
Subject: Re: Montevideo statement
In-Reply-To: <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com> <18100.1381543263@sandelman.ca> <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.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: Tue, 15 Oct 2013 11:20:29 -0000

> The ccTLD system grew up at a time when many governments were
> fairly hostile to the Internet and/or the DNS (that is different
> from being hostile to, e.g., free and private flow of
> information over the Internet).  The ccTLD environment still
> supports ccTLD administrations that are independent of the local
> government unless that government is so hostile to them that it
> is willing to use national law to force them out.  One
> consequence of that model is that, for the ccTLD system to
> function, neither IANA nor anyone else needs to figure out who
> is the actual, legitimate, government of a country.  Governments
> have a tendency to be quite jealous of their rights to
> "recognize" other governments (or not).  Keeping IANA out of
> that business was an explicit goal at the time RFC 1591 was
> written, for multiple reasons.
> 
> If the government of a country is the required root of trust in
> that country's ccTLD, we take ourselves several steps closer to
> requiring that governments approve ccTLD administrations (not
> merely not being actively opposed to them).  We create an attack
> vector from the government on the ccTLD and registrations in it.
> Unlike shutting down a ccTLD administration by offering to throw
> its membership in jail, the control and mechanisms that implies
> may not require whatever passes for due process in that country.
> And such trust authority can provide a vector for required
> government approval of individual registrations and registrants,
> just as the US Government has turned a general IANA oversight
> requirement into case-by-case approval of root entries.
> 
> Be careful what you wish for.

+1

From warren@kumari.net  Tue Oct 15 05:19:56 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 32D2321F9DBD for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 05:19:56 -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 p5okLGwK7ny6 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 05:19:50 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D17A21F9FB9 for <ietf@ietf.org>; Tue, 15 Oct 2013 05:19:46 -0700 (PDT)
Received: from dhcp-25-116.ripemtg.ripe.net (dhcp-25-116.ripemtg.ripe.net [193.0.25.116]) by vimes.kumari.net (Postfix) with ESMTPSA id 5A8661B401D1; Tue, 15 Oct 2013 08:19:44 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [IETF] Re: Montevideo statement
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m2eh7mpypz.wl%randy@psg.com>
Date: Tue, 15 Oct 2013 15:19:43 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <ED522F58-5AD6-415B-B30D-2EFF7BF39FD4@kumari.net>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com> <18100.1381543263@sandelman.ca> <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.com> <m2eh7mpypz.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1510)
Cc: John C Klensin <klensin@jck.com>, 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, 15 Oct 2013 12:19:56 -0000

On Oct 15, 2013, at 2:20 PM, Randy Bush <randy@psg.com> wrote:

>> The ccTLD system grew up at a time when many governments were
>> fairly hostile to the Internet and/or the DNS (that is different
>> from being hostile to, e.g., free and private flow of
>> information over the Internet).  The ccTLD environment still
>> supports ccTLD administrations that are independent of the local
>> government unless that government is so hostile to them that it
>> is willing to use national law to force them out.  One
>> consequence of that model is that, for the ccTLD system to
>> function, neither IANA nor anyone else needs to figure out who
>> is the actual, legitimate, government of a country.  Governments
>> have a tendency to be quite jealous of their rights to
>> "recognize" other governments (or not).  Keeping IANA out of
>> that business was an explicit goal at the time RFC 1591 was
>> written, for multiple reasons.
>> 
>> If the government of a country is the required root of trust in
>> that country's ccTLD, we take ourselves several steps closer to
>> requiring that governments approve ccTLD administrations (not
>> merely not being actively opposed to them).  We create an attack
>> vector from the government on the ccTLD and registrations in it.
>> Unlike shutting down a ccTLD administration by offering to throw
>> its membership in jail, the control and mechanisms that implies
>> may not require whatever passes for due process in that country.
>> And such trust authority can provide a vector for required
>> government approval of individual registrations and registrants,
>> just as the US Government has turned a general IANA oversight
>> requirement into case-by-case approval of root entries.
>> 
>> Be careful what you wish for.
> 
> +1
> 


Dislike doing this, but:
+1

W

-- 
American Non-Sequitur Society; 
we don't make sense, but we do like pizza!



From jmamodio@gmail.com  Tue Oct 15 05:53:15 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 0D38D11E813B for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 05:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level: 
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[AWL=-1.110,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, TVD_SPACE_RATIO=2.219]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJBhTQyxa+az for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 05:53:14 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 395BC11E81E2 for <ietf@ietf.org>; Tue, 15 Oct 2013 05:53:14 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id n12so3800079wgh.5 for <ietf@ietf.org>; Tue, 15 Oct 2013 05:53: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=4D8hv6g0EE3R+B6Jm/aMvAGxNjq/Mrs1hFwCA7WvTjE=; b=d7ykhh6uWeTTR26GmBcqq9vfqvcPPRriBBA8EJvIAe0pDTDLk64Ti3XDtJ6URWXCoS zrmbi895M/oFqIsrpQQZgeO9lVZKzYi78noQkKi7YqsVlWGoDImlup6eoxzz4NVZ+h2L NCmDmUnXtpdTKWEJSK8GfWncTOdTgYkhEoBhsMN3g82Qnse2Kk5c8eDundBLv3HTzoUm /gUJCBPGMN1RcrvBJv57G+lCm9UqeaxqywzEBt9UPELfJ0dSHMFCAQpDnaMzdML5k5Ec xMRtk3PxUCYLxSAwcpcLdiRqCc75SYffdysnu7yOCf7x3HgY0bE8sNVexZFsBsd+HglJ k9FA==
MIME-Version: 1.0
X-Received: by 10.180.100.33 with SMTP id ev1mr16397047wib.18.1381841593392; Tue, 15 Oct 2013 05:53:13 -0700 (PDT)
Received: by 10.180.84.38 with HTTP; Tue, 15 Oct 2013 05:53:13 -0700 (PDT)
In-Reply-To: <m2eh7mpypz.wl%randy@psg.com>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com> <18100.1381543263@sandelman.ca> <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.com> <m2eh7mpypz.wl%randy@psg.com>
Date: Tue, 15 Oct 2013 07:53:13 -0500
Message-ID: <CAMzo+1YZYhX8A_Vr49t3whwgd_-EaP3Gj7SZzpcrRfAsjiJsQA@mail.gmail.com>
Subject: Re: Montevideo statement
From: Jorge Amodio <jmamodio@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=f46d044402664f655704e8c711b6
Cc: John C Klensin <klensin@jck.com>, 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, 15 Oct 2013 12:53:15 -0000

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

+2

-J

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

<div dir="ltr">+2<div><br></div><div>-J</div><div class="gmail_extra"><br></div></div>

--f46d044402664f655704e8c711b6--

From barryleiba.mailing.lists@gmail.com  Tue Oct 15 06:31:52 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 0242E11E81DE for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 06:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.688
X-Spam-Level: 
X-Spam-Status: No, score=-101.688 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_43=0.6, 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 1+WVUGUZkGri for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 06:31:51 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1092611E81DB for <ietf@ietf.org>; Tue, 15 Oct 2013 06:31:50 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id x18so6966035lbi.3 for <ietf@ietf.org>; Tue, 15 Oct 2013 06:31:50 -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:message-id:subject :from:to:cc:content-type; bh=laaO96zRFizFQdGkuYmjRhjhzJVG+lFp1mtVYRns1fc=; b=MG0O+NbsF4JsdwJsxQCkZK2ay8vbgN4PBjugQpGUbHfxBV5956Gz4l3PuvYzBmZm1A exia9goynqNUsnbfoBg0Bo/IF22B0hQwcijiwEehEC9ziutfr8mQXMqjGNBYLlZymdwt ow87GyWV/2Dkxs7i11SkYIAoiACIvsA2/SR4PNTHy7hgemk6IhbHSWz5jdBpbM7wmQRt 8JMzpwUX2FKGqgBhfPkohAR9/Lb286XqMwEDmPXRTTbLVOeOg8BPxUoJcZjiGuOz8MWS ES7V5i60VV3lMnObFHf4L/ij6Ji9DFKgMenbL3ImX+LHq4pKJEUsyjBYlFIkynwZbpK2 cPbg==
MIME-Version: 1.0
X-Received: by 10.112.53.130 with SMTP id b2mr35286973lbp.6.1381843909984; Tue, 15 Oct 2013 06:31:49 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Tue, 15 Oct 2013 06:31:49 -0700 (PDT)
In-Reply-To: <102BC46338B27611350C249D@JcK-HP8200.jck.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.com> <102BC46338B27611350C249D@JcK-HP8200.jck.com>
Date: Tue, 15 Oct 2013 09:31:49 -0400
X-Google-Sender-Auth: uEn95TnQlFGm6OIkWECDYi8taCU
Message-ID: <CAC4RtVAeTGpHFA01YX=PS7CYeOfYFS0Sc-g3wb05USnoWyUJMQ@mail.gmail.com>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qti.qualcomm.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: Tue, 15 Oct 2013 13:31:52 -0000

> In a slightly broader interpretation of that question, I believe
> that having Independent (or even IAB) stream documents modify
> registrations that are required, either by the registration
> procedure or the registration itself, to be under IETF change
> control is a bad idea.  If we don't like that constrain, we
> should modify the registration, not conduct odd Last Calls.  I
> would strongly support processing this document in the IETF
> Stream as an individual submission (and, while that slips over
> into the substantive part, approving it for publication and
> modification of the registration on that basis).

I understand your comment about precedent.  To that, I'll note that
RFC 6838 says this in Section 3.1, related to Standards Tree
registrations:

   Registrations published in non-IETF RFC streams are also allowed and
   require IESG approval.

That is, it explicitly allows Independent stream documents to register
in the Standards Tree.  It would seem odd to at the same time forbid
them from modifying registrations (with, of course, the same IESG
approval).

Also, this document was offered to the IETF community, and the
community was not interested in taking it up.  But there's a need for
it in some circles, and we've seen no expression of objection.  That's
why I sent the authors to the ISE back in May.  I think this document
is a good example of what the Independent stream is for, and I think
that RFC 6838 allows us to approve these sorts of things case by case.

As to precedent, if another document should come along and do a
similar thing, we would do a similar analysis and have a similar
discussion.  If that one should garner significant objections, its
path would be different.

> p.s. W3C is circulating a draft charter for a WG that might
> affect CSV on the web.  Because having a hard-to-change
> Informational RFC and IANA registration that was inconsistent
> with W3C recommendations would be a generally bad idea, some
> coordination may be in order, especially to verify that the
> current draft is not an end run around W3C efforts.

Thanks for bringing that up.  I'll be sure to send this to the
liaisons, and make sure we're not interfering with their plans for
text/csv.

Barry

From Fred.L.Templin@boeing.com  Tue Oct 15 06:56:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E795211E8128; Tue, 15 Oct 2013 06:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.488
X-Spam-Level: 
X-Spam-Status: No, score=-6.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 97SLGiOri6Wk; Tue, 15 Oct 2013 06:56:19 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id BDD2F11E8138; Tue, 15 Oct 2013 06:55:41 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FDtZU8027597; Tue, 15 Oct 2013 08:55:35 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FDsT4b025711 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 08:55:34 -0500
Received: from XCH-BLV-208.nw.nos.boeing.com (10.57.37.5) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 06:55:24 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.27]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 06:55:24 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOySFFebc9KTehbEGO6mhunuAlj5n1xs+A
Date: Tue, 15 Oct 2013 13:55:23 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net>
In-Reply-To: <525C5CDE.3000604@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Oct 2013 13:56:29 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Monday, October 14, 2013 2:07 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
> ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 14 October 2013 19:39
> > Hi Ron,
> >
> >> -----Original Message-----
> >> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >> Sent: Saturday, October 12, 2013 7:07 PM
> >> To: Brian E Carpenter; Templin, Fred L
> >> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> >> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >> +1
> >>
> >> Is there a way to decouple this discussion from draft-ietf-6man-
> >> oversized-header-chain? I would be glad to discuss it in the context
> of
> >> a separate draft.
> >
> > I don't know if there is a way to decouple it. I believe I have shown
> > a way to not mess up tunnels while at the same time not messing up
> your
> > draft. That should be a win-win. In what way would imposing a 1K
> limit
> > on the IPv6 header chain not satisfy the general case?
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
>=20
> This draft may not go as far as you'd like (e.g. specifying a hard
> limit
> on header length as some proportion of MTU), and I'm also aware of the
> issue of MTU fragmentation and nested tunnels, but I'm still not clear
> on how this draft specifically "messes up tunnels."
>
> Can you explain what specific text in the current draft you consider
> harmful?

That hosts would be permitted to send MTU-sized header chains.

> And why that couldn't be dealt with in a later draft (that imposes
> additional limits on header chains in specific scenarios)?

Once a spec says that a host is permitted to send MTU-sized header
chains the die is cast and no later draft will be able to undo it.
The host has no idea that there may be one or more tunnels in the
path, and so has no way of knowing to alter its behavior to be
kind to tunnels.

That, plus the fact that attackers will be able to craft packets
intended to fool middleboxes by sending a fragmented tunneled
packet with the "good" part of the header chain in the first
fragment and the "bad" part of the header chain in the second
fragment.

Thanks - Fred
fred.l.templin@boeing.com


> Thanks.
>=20
>=20
> >
> >>                                                              Ron
> >>
> >>
> >>>> So, it wasn't necessarily the case that 1280 was a product of
> >>>> "thoughtful analysis" so much as the fact that **they were rushing
> >> to
> >>>> get a spec out the door**. So now, 16 years later, we get to put
> it
> >>>> back on the 6man charter milestone list.
> >>> We could have that discussion in 6man, sure, but I don't believe
> that
> >>> it's relevant to the question of whether draft-ietf-6man-oversized-
> >>> header-chain
> >>> is ready. This draft mitigates a known problem in terms of the
> >> current
> >>> IPv6 standards.
> >>>
> >
> >
>=20
> --
> Regards,
> RayH


From Fred.L.Templin@boeing.com  Tue Oct 15 07:04:14 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8E311E817B; Tue, 15 Oct 2013 07:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 21RlHvLRm-0w; Tue, 15 Oct 2013 07:04:07 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id E234521F9E1A; Tue, 15 Oct 2013 07:04:07 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FE47b1029286; Tue, 15 Oct 2013 07:04:07 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FE3x8h029115 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 07:04:07 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (130.247.25.213) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 07:04:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.164]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 07:04:04 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyRRhebc9KTehbEGO6mhunuAlj5n1ypVw
Date: Tue, 15 Oct 2013 14:04:03 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812E381@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <9300F272-E282-41C3-9DA8-59134B975FC7@employees.org> <9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com> <525C473D.4080403@gmail.com>
In-Reply-To: <525C473D.4080403@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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, 15 Oct 2013 14:04:14 -0000

SGkgQnJpYW4sDQoNCj4gVGhlIGRyYWZ0IG1pdGlnYXRlcyBhIGtub3duIHByb2JsZW0gd2l0aCBj
b21tdW5pY2F0aW9uIHBhdGhzIHRoYXQNCj4gZG8gbm90IGluY2x1ZGUgbmVzdGVkIHR1bm5lbHMg
cmVxdWlyaW5nIG5lc3RlZCBmcmFnbWVudGF0aW9uLA0KPiB3aGVyZSB0aGUgbmVzdGVkIHR1bm5l
bCBoYXMgdG8gZGVhbCB3aXRoIGFuIE1UVSA8MTI4MCAqYW5kKiB3aGVyZQ0KPiB0aGUgbmVzdGVk
IHR1bm5lbCBnb2VzIHRocm91Z2ggYSBmaXJld2FsbCB0aGF0IHdhbnRzIHRvIGFuYWx5c2UNCj4g
dGhlIGNvbXBsZXRlIGhlYWRlciBjaGFpbiBvZiB0aGUgaW5uZXJtb3N0IHBhY2tldC4NCg0KSSB3
YW50IHRvIHNheSBvbmUgbW9yZSB3b3JkIG9uIHRoaXMuIFlvdSBzZWVtIHRvIGJlIGluZGljYXRp
bmcgdGhhdA0KeW91IHNlZSB3aGF0IEkgaGF2ZSBiZWVuIGV4cGxhaW5pbmcgYXMgYSBjb3JuZXIg
Y2FzZS4gQnV0LCBJIGJlbGlldmUNCnRoYXQgaW4gb3JkZXIgdG8gZml4IHRoZSB0dW5uZWwgTVRV
IGlzc3VlIHdlIHdpbGwgbmVlZCBTRUFMIG9yDQpzb21ldGhpbmcgdmVyeSBtdWNoIGxpa2UgaXQu
DQoNClNFQUwgdXNlcyBmcmFnbWVudGF0aW9uIG9uIHRoZSBmaXJzdCBmZXcgcGFja2V0cyByZWdh
cmRsZXNzIG9mIHRoZQ0KcGF0aCBNVFUgdG8gZW5zdXJlIHRoYXQgIm1pZGRsZSBzaXplZCIgcGFj
a2V0cyBiZXR3ZWVuIDEyODAtMTUwMA0KZ2V0IHRocm91Z2guIEl0IHRoZW4gdHVybnMgb2ZmIHRo
ZSBmcmFnbWVudGF0aW9uIHVzaW5nIGEgcHJvYmluZw0Kc2NoZW1lIGluIHRoZSBzcGlyaXQgb2Yg
UkZDNDgyMS4gU28sIHRob3NlIGZpcnN0IGZldyBwYWNrZXRzIHRoYXQNCmNvdWxkIGNvbnRhaW4g
YSBoZWFkZXIgY2hhaW4gdGhhdCBzcGlsbHMgb3ZlciBpbnRvIHRoZSBzZWNvbmQNCmZyYWdtZW50
IGFyZSB3aGF0IGNvbmNlcm5zIG1lLiBBbmQsIHRoaXMgd2lsbCBub3QgYmUgYSBjb3JuZXINCmNh
c2Ugd2hlbiBTRUFMIGlzIHVzZWQgaW4gd2lkZXIgZGVwbG95bWVudC4NCg0KVGhhbmtzIC0gRnJl
ZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KDQo=

From sm@resistor.net  Tue Oct 15 08:19:54 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 8A3B821F9C05 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 08:19:54 -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, J_CHICKENPOX_43=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 qVKTuqGYY7RB for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 08:19:53 -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 766C721F9BAD for <ietf@ietf.org>; Tue, 15 Oct 2013 08:19:52 -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 r9FFJj8I010088; Tue, 15 Oct 2013 08:19:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1381850391; bh=KwCM7SBLjdbkpk2GWe+wL2x+nABxGp1x3rjLa8N9T0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BezTvPduvn7rAaeZmtx0/VydLtQcf57SqCO4iZHqtNK+5pZi2cLIPOx/ca+jRjdEr gLDb1pkXYzbTxsmj2We7JDzXYAVRfuVbxSrdGAaQ+/owlXavUh6Ndk5vCuRRuAPZbE Mqo0o0Uahjcq9ASz/2jmoFKbq6aULgY9SW0EeMNA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1381850391; i=@resistor.net; bh=KwCM7SBLjdbkpk2GWe+wL2x+nABxGp1x3rjLa8N9T0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=m0+H6eRo0OJwL7uWfZggEjz1WXdLEgyFGopKZCJMmwsRq5E5EDZPegrYaw5ibFGjF CFFmE/FBHggm9fE4wrBYXhv/SLVa826KfKRkIbH55BfbTJ//nJHRiDSP7TDJd1VjV8 4RoCbLQepVcaauuDPhFvffuELpBXiemEwl34Qi8s=
Message-Id: <6.2.5.6.2.20131015072115.0c8e4d40@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Oct 2013 08:03:50 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media	type(see <draft-hausenblas-csv-fragment-06.txt>)
In-Reply-To: <102BC46338B27611350C249D@JcK-HP8200.jck.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.com> <102BC46338B27611350C249D@JcK-HP8200.jck.com>
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: Tue, 15 Oct 2013 15:19:54 -0000

At 01:54 15-10-2013, John C Klensin wrote:
>My reasoning is that, while the change seems fine, the precedent
>seems atrocious.  If this is approved via Independent Stream
>publication and the next case that comes along is, unlike this
>one, generally hated by the community, the amount of
>hair-splitting required to deny that one having approved this
>one would be impressive.. and bad for the IETF.

I was unable to see whether this specification would be of use to 
data.gov as the site is still unaccessible.  There is an opendata 
site in Brazil ( http://dados.gov.br/), France ( 
http://www.data.gouv.fr/ ) and several other countries.  The 
specification may be relevant to opendata which is something of 
interests to governments.  It would have been better if the 
specification was processed in the IETF Stream but the community was 
not interested in taking it up (see msg-id: 
CAC4RtVAeTGpHFA01YX=PS7CYeOfYFS0Sc-g3wb05USnoWyUJMQ@mail.gmail.com).

The draft updates a specification in the IETF Stream.  It also 
updates a registration in the standards tree.  This has the hallmarks 
of "not a good idea" as it will be a problem down the line.  If it 
takes a minimal effort to avoid a small problem it is worth the 
effort.  This is the list of persons who commented on the Last Call:

   Tom Petch
   John Klensin
   Alexey Melnikov
   Simon Perreault
   Tim Bray

It's not like the expertise or experience is not there.  In fact, 
there's much more than the average IETF Last Call.  I remember filing 
the minority report against the attempt to kill the Independent 
Submissions Stream. :-)

Regards,
-sm  


From shogunx@sleekfreak.ath.cx  Tue Oct 15 09:14:29 2013
Return-Path: <shogunx@sleekfreak.ath.cx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A3611E8191 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 09:14:28 -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 Fv9fB8-ttFnb for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 09:14:28 -0700 (PDT)
Received: from sleekfreak.ath.cx (cl-23.chi-02.us.sixxs.net [IPv6:2001:4978:f:16::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4362611E8140 for <ietf@ietf.org>; Tue, 15 Oct 2013 09:14:26 -0700 (PDT)
Received: from shogunx (helo=localhost) by sleekfreak.ath.cx with local-esmtp (Exim 4.80) (envelope-from <shogunx@sleekfreak.ath.cx>) id 1VW7Fc-0002F9-9q; Tue, 15 Oct 2013 16:13:40 +0000
Date: Tue, 15 Oct 2013 16:13:40 +0000 (UTC)
From: shogunx@sleekfreak.ath.cx
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Montevideo statement
In-Reply-To: <ED522F58-5AD6-415B-B30D-2EFF7BF39FD4@kumari.net>
Message-ID: <alpine.DEB.2.10.1310151613080.20496@sleekfreak.ath.cx>
References: <ABCF1EB7-3437-4EC3-B0A8-0EDB2EDEA538@ietf.org> <20131007225129.GA572@laperouse.bortzmeyer.org> <4B3BF00B-0916-4EED-A73C-A0EB8B2A78FD@piuha.net> <CAMm+LwjqEX8XUM2RcLWGS0ZR8Ax=wHJjQhnSAoYbntWVeqNgAA@mail.gmail.com> <11948.1381238349@sandelman.ca> <CAMm+Lwgr2PM-pKyeRZW40mdsj12aydmP1cGj+FhxtW2Rpzg7TQ@mail.gmail.com> <18100.1381543263@sandelman.ca> <B61A7F9F00D5C2C2055E7B74@JcK-HP8200.jck.com> <m2eh7mpypz.wl%randy@psg.com> <ED522F58-5AD6-415B-B30D-2EFF7BF39FD4@kumari.net>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: John C Klensin <klensin@jck.com>, 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, 15 Oct 2013 16:14:29 -0000

When did we change the list from IETF Discuss to IETF Disgust?
Classic, BTW.  Kudos.


On Tue, 15 Oct 2013, Warren Kumari wrote:

>
> On Oct 15, 2013, at 2:20 PM, Randy Bush <randy@psg.com> wrote:
>
>>> The ccTLD system grew up at a time when many governments were
>>> fairly hostile to the Internet and/or the DNS (that is different
>>> from being hostile to, e.g., free and private flow of
>>> information over the Internet).  The ccTLD environment still
>>> supports ccTLD administrations that are independent of the local
>>> government unless that government is so hostile to them that it
>>> is willing to use national law to force them out.  One
>>> consequence of that model is that, for the ccTLD system to
>>> function, neither IANA nor anyone else needs to figure out who
>>> is the actual, legitimate, government of a country.  Governments
>>> have a tendency to be quite jealous of their rights to
>>> "recognize" other governments (or not).  Keeping IANA out of
>>> that business was an explicit goal at the time RFC 1591 was
>>> written, for multiple reasons.
>>>
>>> If the government of a country is the required root of trust in
>>> that country's ccTLD, we take ourselves several steps closer to
>>> requiring that governments approve ccTLD administrations (not
>>> merely not being actively opposed to them).  We create an attack
>>> vector from the government on the ccTLD and registrations in it.
>>> Unlike shutting down a ccTLD administration by offering to throw
>>> its membership in jail, the control and mechanisms that implies
>>> may not require whatever passes for due process in that country.
>>> And such trust authority can provide a vector for required
>>> government approval of individual registrations and registrants,
>>> just as the US Government has turned a general IANA oversight
>>> requirement into case-by-case approval of root entries.
>>>
>>> Be careful what you wish for.
>>
>> +1
>>
>
>
> Dislike doing this, but:
> +1
>
> W
>
> -- 
> American Non-Sequitur Society;
> we don't make sense, but we do like pizza!
>
>
>

From john-ietf@jck.com  Tue Oct 15 09:20: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 7C05211E8191 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 09:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.077
X-Spam-Level: 
X-Spam-Status: No, score=-103.077 tagged_above=-999 required=5 tests=[AWL=-0.678, BAYES_00=-2.599, J_CHICKENPOX_24=0.6, J_CHICKENPOX_43=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 WLbfNpWgvMt1 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 09:20:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7162011E8128 for <ietf@ietf.org>; Tue, 15 Oct 2013 09:20: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 1VW7Lz-000OkN-U1; Tue, 15 Oct 2013 12:20:15 -0400
Date: Tue, 15 Oct 2013 12:20:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: Adding a fragment identifier to the text/csv media type(see <draft-hausenblas-csv-fragment-06.txt>)
Message-ID: <6C308BD4BA235737E57A02E8@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVAeTGpHFA01YX=PS7CYeOfYFS0Sc-g3wb05USnoWyUJMQ@mail.gmail.com>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.com> <102BC46338B27611350C249D@JcK-HP8200.jck.com> <CAC4RtVAeTGpHFA01YX=PS7CYeOfYFS0Sc-g3wb05USnoWyUJMQ@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: Pete Resnick <presnick@qti.qualcomm.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: Tue, 15 Oct 2013 16:20:51 -0000

--On Tuesday, October 15, 2013 09:31 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> In a slightly broader interpretation of that question, I
>> believe that having Independent (or even IAB) stream
>> documents modify registrations that are required, either by
>> the registration procedure or the registration itself, to be
>> under IETF change control is a bad idea.  If we don't like
>> that constrain, we should modify the registration, not
>> conduct odd Last Calls.  I would strongly support processing
>> this document in the IETF Stream as an individual submission
>> (and, while that slips over into the substantive part,
>> approving it for publication and modification of the
>> registration on that basis).
> 
> I understand your comment about precedent.  To that, I'll note
> that RFC 6838 says this in Section 3.1, related to Standards
> Tree registrations:
> 
>    Registrations published in non-IETF RFC streams are also
> allowed and    require IESG approval.
> 
> That is, it explicitly allows Independent stream documents to
> register in the Standards Tree.  It would seem odd to at the
> same time forbid them from modifying registrations (with, of
> course, the same IESG approval).

Yeah, I know.  I am somewhat acquainted with the authors.

We probably need to agree to disagree on this, but I don't see
the distinction as odd at all.  The text/* namespace is
essentially unlimited.  If someone wants to create a new one,
the key issue is whether it is fundamentally harmful in some
way, even if it is ignored in the marketplace.  "Standards Tree"
implies some level of endorsement, but not very much, and the
ISE process is (we hope) pretty good at determining whether a
document is competent as a document.   The bar for such new
registrations should be reasonably low and, a snit or two about
parameter relationships (like "charset=")  generally has been.

But a parameter-adding modification is different.  It should be
evaluated for whether or not it could have bad effects on
existing uses of the registration or in combination with other
parameters.  As an example for this particular case and drawing
on my long-ago experience with data format conversion systems,
some systems that convert CSV files to matrix (or ER)form use
named columns, either inventing names or taking them from the
first line of the CSV file (for this case, "text/csv;
header=present").  For some of those systems, the separation
occurs right after the data are received or as they are
streaming in, so processing of a fragment with row selection
using this approach requires that one preserve the information
needed to decrement row numbers in the fragment specification.
That example is actually about two things: a comment to the ISE
that the draft needs to have an explicit discussion about
interactions between row numbers and headers (or at least a
Security Considerations warning) and a comment to the IESG about
the dangers of this type of registration modification.

Other interactions with other registration extensions could be
much more serious.   I note, without recommending it, that a new
registration for text/csv-with-fragments that recommended the
gradual retirement of text/csv would have none of these problems
and, if successful, would have the potential to eliminate many
of the issues with different CSV interpretations that are noted
in both this spec and RFC 4180 itself.  I don't know that would
be an especially good idea, but it would eliminate the multiple
issues raised by modifying an existing spec.

> Also, this document was offered to the IETF community, and the
> community was not interested in taking it up.  But there's a
> need for it in some circles, and we've seen no expression of
> objection.  That's why I sent the authors to the ISE back in
> May.  I think this document is a good example of what the
> Independent stream is for, and I think that RFC 6838 allows us
> to approve these sorts of things case by case.

At the risk of hair-splitting, Section 3.1 of RFC 6838 is
entirely about new registrations.  Section 5.5 is applicable in
this case.  First, if the IESG, as the representative of the
relevant standards body, is assumed to be the "owner" of RFC
4180 and the existing registration, then the IESG needs to take
responsibility for the evaluation discussed above.  If Yakov
Shafranovich is the owner as author of 4180, then he has a
significant voice in any decision here.   More important,
Section 5.5 says 

	"Significant changes to a media type's definition should
	be requested only when there are serious omissions or
	errors in the published specification."

Presumably this is a "significant change".  Whether the absence
of fragments is a "serious omission" or not is debatable and we
have heard little debate on the subject.   Again, this would be
a much more comfortable situation if the document were handed as
an individual submission in the IETF Stream (on which the
community could give advice during Last Call that had to be
considered) rather than as an independent submission (on which
the community could give advice and hope the authors are
interested).

> As to precedent, if another document should come along and do a
> similar thing, we would do a similar analysis and have a
> similar discussion.  If that one should garner significant
> objections, its path would be different.

Again, I agree with your analysis for new registrations.  What
is giving me pause is the notion of modifying an existing one to
add features.

>> p.s. W3C is circulating a draft charter for a WG that might
>> affect CSV on the web.  Because having a hard-to-change
>> Informational RFC and IANA registration that was inconsistent
>> with W3C recommendations would be a generally bad idea, some
>> coordination may be in order, especially to verify that the
>> current draft is not an end run around W3C efforts.
> 
> Thanks for bringing that up.  I'll be sure to send this to the
> liaisons, and make sure we're not interfering with their plans
> for text/csv.

If the IETF is uninterested in text/csv (as you imply above) and
W3C is interested (the media type is apparently intertwined
with their "web data" and "semantic web" efforts), another
possibility would be for the IESG to take the action described
in the last paragraph of Section 5.4 of RFC 6838, reassign
responsibility for text/csv to W3C (which I assume is a
"recognized standards-related organization") and let them sort
it out.  That would presumably even allow replacement of RFC
4180 with a reference to a stable W3C spec.

That solution would, of course, not automatically generalize to
other cases.

best,
   john




From john-ietf@jck.com  Tue Oct 15 10:30:10 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 0CF5011E815A for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 10:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.309
X-Spam-Level: 
X-Spam-Status: No, score=-103.309 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, J_CHICKENPOX_43=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 jLS183Ecf7nE for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 10:30:05 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEAE11E8116 for <ietf@ietf.org>; Tue, 15 Oct 2013 10:30:05 -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 1VW8RK-000OpZ-JI; Tue, 15 Oct 2013 13:29:50 -0400
Date: Tue, 15 Oct 2013 13:29:45 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, ietf@ietf.org
Subject: CSV, subsetting, and searching (was: Re: Last Call: Adding a fragment identifier to the text/csv  media type(see <draft-hausenblas-csv-fragment-06.txt>))
Message-ID: <37BA330184AB2E25369BE7CB@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20131015072115.0c8e4d40@resistor.net>
References: <20131010185009.971.99426.idtracker@ietfa.amsl.com> <000f01cec801$0d8ba0a0$4001a8c0@gateway.2wire.net> <525C49DC.9090102@qti.qualcomm.com> <102BC46338B27611350C249D@JcK-HP8200.jck.com> <6.2.5.6.2.20131015072115.0c8e4d40@resistor.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: ise@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Oct 2013 17:30:10 -0000

--On Tuesday, October 15, 2013 08:03 -0700 SM <sm@resistor.net>
wrote:

> At 01:54 15-10-2013, John C Klensin wrote:
>> My reasoning is that, while the change seems fine, the
>> precedent seems atrocious.  If this is approved via
>> Independent Stream publication and the next case that comes
>> along is, unlike this one, generally hated by the community,
>> the amount of hair-splitting required to deny that one having
>> approved this one would be impressive.. and bad for the IETF.

> I was unable to see whether this specification would be of use
> to data.gov as the site is still unaccessible.  There is an
> opendata site in Brazil ( http://dados.gov.br/), France (
> http://www.data.gouv.fr/ ) and several other countries.  The
> specification may be relevant to opendata which is something
> of interests to governments.  It would have been better if the
> specification was processed in the IETF Stream but the
> community was not interested in taking it up (see msg-id:
> CAC4RtVAeTGpHFA01YX=PS7CYeOfYFS0Sc-g3wb05USnoWyUJMQ@mail.gmail
> .com).
>...

As long as the question is "should the IETF approve registration
of an extension whose documentation is published via the ISE",
most of the above is massively irrelevant.  Hence the change in
subject line and the copy to Nevil (and I'm not likely to
discuss it further on this list).

>From the standpoint of retrieval of information from a database
(opendata or otherwise), my experience suggests that CSV
fragments, especially as specified here, are going to be fairly
irrelevant.  Not harmful, probably ok for those who think they
have a use for them, just useless for lots of retrieval
functions.  The problem is that, in general and with a dataset
of any real size, people don't think of things in terms of row
and column numbers (getting them to think that way is quite
error-prone).   Especially when there are _lots_ of columns,
retrieval by column number is usually a bad idea.

Using an example from the I-D to construct a different one,
  http://example.com/data.csv#col="temperature"
would make a lot more sense in many cases than
  http://example.com/data.csv#col=2
But the spec doesn't allow that and it is perhaps better handled
with a query rather than a fragment (although that opens the
problem of where queries are processed that has tied the URNbis
WG in knots).

It is also not unusual with statistical and scientific databases
(especially non-relational ones) to have named rows as well as
named columns, but, while RFC 4180 allows for ";
header=present", it makes no provision for 'rowNames="present"',
much less what many data analysis packages would really like to
see, which would be something like 'rowNames="present, col=NN"'
with the latter designating the "column" (or columns) of the CSV
file in which those names appeared, perhaps borrowing from
regular expressions and allowing "$" and "$-1" instead of NN.

There is no reason why one couldn't have those sorts of
arrangements with a CSV format and some systems do, but is isn't
the text/csv of RFC 4180.

For datasets of non-trivial size and complexity, fragments as
specified here are going to be really useful only when the
application retrieves what used to be called a "codebook" and
first, uses it to change row and column identifiers or other
query-supporting information into row and column numbers, and
then constructs the URI with this fragment ID.  I suspect that
won't be common for lots of reasons starting from the
observation that many modern database management and database
access technologies discourage detached codebooks.   

Those types of application situations also lead to another
problem with the fragment approach.  Again going back to the
example in the draft, if one had, instead of 

   date,temperature,place
   2011-01-01,1,Galway

one had 
   date, time,observed-melting-point
   2011-01-01,0900.3, 0.001
   2011-01-01,0901.2, 0.002
   2011-01-01,0901.8, -0.09

Then many systems would do the conversions if the last column to
floating point as the data were being read (and might convert
times or dates as well).  Depending on how much information was
kept, responding to 
    http://www.example.com/melting-points.csv#col=3
with
  0.001
  0.002
  -0.09
rather than 
  0.001
  0.002
  -0.090
or
  0.1 x10**-2
etc., as the spec seems to require, might require significant
work.  Some processors would care, others wouldn't, but you see
the problem.

Again, I don't see a big problem with this addition although
there are a number of things I'd like to see either more clear
or explicitly warned about.   I don't see arguments about what
problems it doesn't solve as relevant unless extravagant claims
are made for it, and the current draft avoids such claims.  But
those issues are quite separate from the issue of the IESG
passing responsibility for documentation and evaluation of a
registration modification request (for a registration for which
I believe the IESG to be the "owner") off to the ISE.

best,
     john



From Fred.L.Templin@boeing.com  Tue Oct 15 11:50:23 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F390921F9C05; Tue, 15 Oct 2013 11:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  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 lCsXckJmxtBB; Tue, 15 Oct 2013 11:50:16 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 6074021F9E6B; Tue, 15 Oct 2013 11:50:15 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9FIoELC001350; Tue, 15 Oct 2013 11:50:14 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9FIoCPa001300 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 Oct 2013 11:50:14 -0700
Received: from XCH-BLV-201.nw.nos.boeing.com (10.57.37.66) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 15 Oct 2013 11:50:12 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-201.nw.nos.boeing.com ([169.254.1.140]) with mapi id 14.03.0158.001; Tue, 15 Oct 2013 11:50:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOycPBebc9KTehbEGO6mhunuAlj5n2GPgQ
Date: Tue, 15 Oct 2013 18:50:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812EA05@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net> <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com> <525D6D78.5040907@globis.net>
In-Reply-To: <525D6D78.5040907@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Oct 2013 18:50:23 -0000

Hi Ray,

> -----Original Message-----
> From: Ray Hunter [mailto:v6ops@globis.net]
> Sent: Tuesday, October 15, 2013 9:30 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
> ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> > Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> > 15 October 2013 15:55
> > Hi Ray,
> >
> >> -----Original Message-----
> >> From: Ray Hunter [mailto:v6ops@globis.net]
> >> Sent: Monday, October 14, 2013 2:07 PM
> >> To: Templin, Fred L
> >> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing
> List;
> >> ietf@ietf.org
> >> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-
> 08.txt>
> >> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
> >>
> >>> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> >>> 14 October 2013 19:39
> >>> Hi Ron,
> >>>
> >>>> -----Original Message-----
> >>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
> >>>> Sent: Saturday, October 12, 2013 7:07 PM
> >>>> To: Brian E Carpenter; Templin, Fred L
> >>>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
> >>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
> >> 08.txt>
> >>>> (Implications of Oversized IPv6 Header Chains) to Proposed
> Standard
> >>>>
> >>>> +1
> >>>>
> >>>> Is there a way to decouple this discussion from draft-ietf-6man-
> >>>> oversized-header-chain? I would be glad to discuss it in the
> context
> >> of
> >>>> a separate draft.
> >>> I don't know if there is a way to decouple it. I believe I have
> shown
> >>> a way to not mess up tunnels while at the same time not messing up
> >> your
> >>> draft. That should be a win-win. In what way would imposing a 1K
> >> limit
> >>> on the IPv6 header chain not satisfy the general case?
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >> This draft may not go as far as you'd like (e.g. specifying a hard
> >> limit
> >> on header length as some proportion of MTU), and I'm also aware of
> the
> >> issue of MTU fragmentation and nested tunnels, but I'm still not
> clear
> >> on how this draft specifically "messes up tunnels."
> >>
> >> Can you explain what specific text in the current draft you consider
> >> harmful?
> >
> > That hosts would be permitted to send MTU-sized header chains.
>=20
> They can do that today. In fact they can legally send n* MTU-sized
> header chains, as long as the total length of an IPv6 packet is not
> exceeded.

Sure, but this draft is about setting healthy limits where there were
previously none.

> >> And why that couldn't be dealt with in a later draft (that imposes
> >> additional limits on header chains in specific scenarios)?
> >
> > Once a spec says that a host is permitted to send MTU-sized header
> > chains the die is cast and no later draft will be able to undo it.
>=20
> Why not? If this is a "maximum", there may always be scenarios where
> less than a maximum is appropriate.

This draft is intending to update RFC2460. Once updated, the
maximum header size requirements are cast in stone.

> > The host has no idea that there may be one or more tunnels in the
> > path, and so has no way of knowing to alter its behavior to be
> > kind to tunnels.
>=20
> RFC 2473 is pretty explicit about how to handle fragmentation (in the
> presence of nested IPv6 tunnels).
>=20
> Once a packet is encapsulated in a tunnel it becomes a new "original
> packet" for the next tunnel in any nested tunnel scenario.
>=20
> And PMTUD on the originating host (whether that's the original host, or
> the tunnel entry point at the previous nesting level) should receive a
> signal if the current tunnel entry node cannot handle encapsulation due
> to MTU issues (Section 7 of RFC 2473). So the originating host should
> always be informed of the MTU issue, and be able to alter its behavior
> accordingly.

We would have to go back into the long discussions on PMTUD brokenness
to show why you can't always rely on it. Hosts are *guaranteed* 1280,
but they *expect* 1500. Absent signaling from the network, that is
all they know.=20

> So again, I don't see what's new in this draft.
> > That, plus the fact that attackers will be able to craft packets
> > intended to fool middleboxes by sending a fragmented tunneled
> > packet with the "good" part of the header chain in the first
> > fragment and the "bad" part of the header chain in the second
> > fragment.
> IMHO They can do that today (and worse).

Sure. That's because there are currently no healthy limits set. This
draft is about setting healthy limits; I am saying that as long as
we are making the effort we should get it right.

Thanks - Fred
fred.l.templin@boeing.com

> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >
> >> Thanks.
> >>
> >>
> >>>>                                                              Ron
> >>>>
> >>>>
> >>>>>> So, it wasn't necessarily the case that 1280 was a product of
> >>>>>> "thoughtful analysis" so much as the fact that **they were
> rushing
> >>>> to
> >>>>>> get a spec out the door**. So now, 16 years later, we get to put
> >> it
> >>>>>> back on the 6man charter milestone list.
> >>>>> We could have that discussion in 6man, sure, but I don't believe
> >> that
> >>>>> it's relevant to the question of whether draft-ietf-6man-
> oversized-
> >>>>> header-chain
> >>>>> is ready. This draft mitigates a known problem in terms of the
> >>>> current
> >>>>> IPv6 standards.
> >>>>>
> >> --
> >> Regards,
> >> RayH
> >


From v6ops@globis.net  Mon Oct 14 14:06:48 2013
Return-Path: <v6ops@globis.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 547A621F9B21; Mon, 14 Oct 2013 14:06: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=[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 wuW21UDweU3Z; Mon, 14 Oct 2013 14:06:47 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id CA4E821E80F8; Mon, 14 Oct 2013 14:06:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 5F79C870098; Mon, 14 Oct 2013 23:06:40 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icorFUAm68iL; Mon, 14 Oct 2013 23:06:40 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 2513B87008A; Mon, 14 Oct 2013 23:06:40 +0200 (CEST)
Message-ID: <525C5CDE.3000604@globis.net>
Date: Mon, 14 Oct 2013 23:06:38 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 15 Oct 2013 13:42:57 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Oct 2013 21:06:48 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 14 October 2013 19:39
> Hi Ron,
>
>> -----Original Message-----
>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>> Sent: Saturday, October 12, 2013 7:07 PM
>> To: Brian E Carpenter; Templin, Fred L
>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>> +1
>>
>> Is there a way to decouple this discussion from draft-ietf-6man-
>> oversized-header-chain? I would be glad to discuss it in the context of
>> a separate draft.
>
> I don't know if there is a way to decouple it. I believe I have shown
> a way to not mess up tunnels while at the same time not messing up your
> draft. That should be a win-win. In what way would imposing a 1K limit
> on the IPv6 header chain not satisfy the general case?
>
> Thanks - Fred
> fred.l.templin@boeing.com

This draft may not go as far as you'd like (e.g. specifying a hard limit
on header length as some proportion of MTU), and I'm also aware of the
issue of MTU fragmentation and nested tunnels, but I'm still not clear
on how this draft specifically "messes up tunnels."

Can you explain what specific text in the current draft you consider
harmful?

And why that couldn't be dealt with in a later draft (that imposes
additional limits on header chains in specific scenarios)?

Thanks.


>  
>>                                                              Ron
>>
>>
>>>> So, it wasn't necessarily the case that 1280 was a product of
>>>> "thoughtful analysis" so much as the fact that **they were rushing
>> to
>>>> get a spec out the door**. So now, 16 years later, we get to put it
>>>> back on the 6man charter milestone list.
>>> We could have that discussion in 6man, sure, but I don't believe that
>>> it's relevant to the question of whether draft-ietf-6man-oversized-
>>> header-chain
>>> is ready. This draft mitigates a known problem in terms of the
>> current
>>> IPv6 standards.
>>>
>
>

-- 
Regards,
RayH


From v6ops@globis.net  Tue Oct 15 09:29:56 2013
Return-Path: <v6ops@globis.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 98B1021F9D0C; Tue, 15 Oct 2013 09:29: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 YB6AxTk-1dUq; Tue, 15 Oct 2013 09:29:56 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 46CA321F9E8D; Tue, 15 Oct 2013 09:29:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B505187007E; Tue, 15 Oct 2013 18:29:45 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjwgqsZjCcsl; Tue, 15 Oct 2013 18:29:45 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 66D34870076; Tue, 15 Oct 2013 18:29:45 +0200 (CEST)
Message-ID: <525D6D78.5040907@globis.net>
Date: Tue, 15 Oct 2013 18:29:44 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525C5CDE.3000604@globis.net> <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812E34F@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 15 Oct 2013 13:43:15 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Oct 2013 16:29:56 -0000

> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
> 15 October 2013 15:55
> Hi Ray,
>
>> -----Original Message-----
>> From: Ray Hunter [mailto:v6ops@globis.net]
>> Sent: Monday, October 14, 2013 2:07 PM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; Brian E Carpenter; Fernando Gont; 6man Mailing List;
>> ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>
>>> Templin, Fred L <mailto:Fred.L.Templin@boeing.com>
>>> 14 October 2013 19:39
>>> Hi Ron,
>>>
>>>> -----Original Message-----
>>>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>>>> Sent: Saturday, October 12, 2013 7:07 PM
>>>> To: Brian E Carpenter; Templin, Fred L
>>>> Cc: Fernando Gont; 6man Mailing List; ietf@ietf.org; Ray Hunter
>>>> Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-
>> 08.txt>
>>>> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>>>>
>>>> +1
>>>>
>>>> Is there a way to decouple this discussion from draft-ietf-6man-
>>>> oversized-header-chain? I would be glad to discuss it in the context
>> of
>>>> a separate draft.
>>> I don't know if there is a way to decouple it. I believe I have shown
>>> a way to not mess up tunnels while at the same time not messing up
>> your
>>> draft. That should be a win-win. In what way would imposing a 1K
>> limit
>>> on the IPv6 header chain not satisfy the general case?
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>> This draft may not go as far as you'd like (e.g. specifying a hard
>> limit
>> on header length as some proportion of MTU), and I'm also aware of the
>> issue of MTU fragmentation and nested tunnels, but I'm still not clear
>> on how this draft specifically "messes up tunnels."
>>
>> Can you explain what specific text in the current draft you consider
>> harmful?
>
> That hosts would be permitted to send MTU-sized header chains.

They can do that today. In fact they can legally send n* MTU-sized
header chains, as long as the total length of an IPv6 packet is not
exceeded.
>> And why that couldn't be dealt with in a later draft (that imposes
>> additional limits on header chains in specific scenarios)?
>
> Once a spec says that a host is permitted to send MTU-sized header
> chains the die is cast and no later draft will be able to undo it.

Why not? If this is a "maximum", there may always be scenarios where
less than a maximum is appropriate.
> The host has no idea that there may be one or more tunnels in the
> path, and so has no way of knowing to alter its behavior to be
> kind to tunnels.

RFC 2473 is pretty explicit about how to handle fragmentation (in the
presence of nested IPv6 tunnels).

Once a packet is encapsulated in a tunnel it becomes a new "original
packet" for the next tunnel in any nested tunnel scenario.

And PMTUD on the originating host (whether that's the original host, or
the tunnel entry point at the previous nesting level) should receive a
signal if the current tunnel entry node cannot handle encapsulation due
to MTU issues (Section 7 of RFC 2473). So the originating host should
always be informed of the MTU issue, and be able to alter its behavior
accordingly.

So again, I don't see what's new in this draft.
> That, plus the fact that attackers will be able to craft packets
> intended to fool middleboxes by sending a fragmented tunneled
> packet with the "good" part of the header chain in the first
> fragment and the "bad" part of the header chain in the second
> fragment.
IMHO They can do that today (and worse).
> Thanks - Fred
> fred.l.templin@boeing.com
>
>
>> Thanks.
>>
>>
>>>>                                                              Ron
>>>>
>>>>
>>>>>> So, it wasn't necessarily the case that 1280 was a product of
>>>>>> "thoughtful analysis" so much as the fact that **they were rushing
>>>> to
>>>>>> get a spec out the door**. So now, 16 years later, we get to put
>> it
>>>>>> back on the 6man charter milestone list.
>>>>> We could have that discussion in 6man, sure, but I don't believe
>> that
>>>>> it's relevant to the question of whether draft-ietf-6man-oversized-
>>>>> header-chain
>>>>> is ready. This draft mitigates a known problem in terms of the
>>>> current
>>>>> IPv6 standards.
>>>>>
>> --
>> Regards,
>> RayH
>


From fgont@si6networks.com  Tue Oct 15 17:09:24 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 574F511E823A; Tue, 15 Oct 2013 17:09:24 -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 awKjWJ4qmE2x; Tue, 15 Oct 2013 17:09:23 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 98A4111E8228; Tue, 15 Oct 2013 17:09:15 -0700 (PDT)
Received: from [186.134.32.156] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWEfj-0002vv-FG; Wed, 16 Oct 2013 02:09:07 +0200
Message-ID: <525DCF12.9020804@si6networks.com>
Date: Tue, 15 Oct 2013 20:26:10 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<9300F272-E282-41C3-9DA8-59134B975FC7@employees.org>	<9e33a47bb2834c15ba4269ae8c79c46f@BLUPR05MB433.namprd05.prod.outlook.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D718@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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, 16 Oct 2013 00:09:24 -0000

On 10/14/2013 02:38 PM, Templin, Fred L wrote:
>>
>> We could have that discussion in 6man, sure, but I don't believe that
>> it's
>> relevant to the question of whether draft-ietf-6man-oversized-header-
>> chain
>> is ready.
> 
> If it messes up tunnels, then it's not ready.

FWIW I disagree with this statement. From this perspectie, you'd also
expect middleboxes (e.g. load-balancers) to get deep into any layers of
tunnelling to decide on which link packets should be forwarded. -- and
this is clearly unrealistic (if at all desirable).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Tue Oct 15 17:09:25 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 E0C7111E8228; Tue, 15 Oct 2013 17:09:24 -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 SGmMW+bAz0jG; Tue, 15 Oct 2013 17:09:24 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8CE6111E8235; Tue, 15 Oct 2013 17:09:17 -0700 (PDT)
Received: from [186.134.32.156] (helo=[192.168.123.126]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWEfp-0002vz-HJ; Wed, 16 Oct 2013 02:09:13 +0200
Message-ID: <525DD007.8030100@si6networks.com>
Date: Tue, 15 Oct 2013 20:30:15 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com>	<D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org>	<2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com>	<E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org>	<2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com>	<5255D6EE.4050300@gmail.com>	<2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com>	<5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com>	<2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com>	<52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com>	<2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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, 16 Oct 2013 00:09:25 -0000

On 10/14/2013 02:39 PM, Templin, Fred L wrote:
>
>> Is there a way to decouple this discussion from draft-ietf-6man-
>> oversized-header-chain? I would be glad to discuss it in the context of
>> a separate draft.
> 
> I don't know if there is a way to decouple it. I believe I have shown
> a way to not mess up tunnels while at the same time not messing up your
> draft. That should be a win-win. In what way would imposing a 1K limit
> on the IPv6 header chain not satisfy the general case?

6man had consensus multiple times on *not* to impose this sort of limits
in this document (that's why the original limit of 1280 bytes was
removed from earlier versions of this I-D in the first place).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From peter@akayla.com  Tue Oct 15 19:49:16 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 C84BC11E822E; Tue, 15 Oct 2013 19:49: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 zGCTx+r9S7oM; Tue, 15 Oct 2013 19:49:12 -0700 (PDT)
Received: from p3plsmtpa09-03.prod.phx3.secureserver.net (p3plsmtpa09-03.prod.phx3.secureserver.net [173.201.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 5186111E8227; Tue, 15 Oct 2013 19:49:07 -0700 (PDT)
Received: from [172.17.72.240] ([71.248.111.164]) by p3plsmtpa09-03.prod.phx3.secureserver.net with  id deow1m00G3YsDkf01ep1XB; Tue, 15 Oct 2013 19:49:03 -0700
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Date: Tue, 15 Oct 2013 19:48:55 -0700
Subject: Gen-ART LC review of draft-kolkman-proposed-standards-clarified-03
From: Peter Yee <peter@akayla.com>
To: <draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>
Message-ID: <CE834CA6.6EE3%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-kolkman-proposed-standards-clarified-03
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: gen-art@ietf.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: Wed, 16 Oct 2013 02:49:16 -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>

Document: draft-kolkman-proposed-standards-clarified-03
Reviewer: Peter Yee
Review Date: Oct-15-2013
IETF LC End Date: Oct-16-2013
IESG Telechat date: TBD

Summary: This draft is basically ready for  publication, but has nits that
should be fixed before publication. [Ready with nits.]

This draft updates the description of the Proposed Standard maturity
level previously defined in RFC 2026.  The update reflects the reality
of greater maturity embodied in Proposed Standards than is given in
RFC 2026.

Page 1, Abstract, last sentence: insert "of" between "characterization"
and "Proposed".

Page 2, Section 2 title: change "Reveiew" to "Review".

Page 3, 1st paragraph, 5th sentence: insert "the" between "IESG at"
and "last stage".

Page 4, Acknowledgements: change "Jari Arko" to "Jari Arkko".

Page 4, Acknowledgements: append a comma after "input".



From fgont@si6networks.com  Tue Oct 15 21:14:15 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 D751511E8214 for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 21:14:15 -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 wBS0fDHgUEUr for <ietf@ietfa.amsl.com>; Tue, 15 Oct 2013 21:14:15 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5442721F9CA9 for <ietf@ietf.org>; Tue, 15 Oct 2013 21:14:14 -0700 (PDT)
Received: from [2001:5c0:1000:a::3cb] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWIUk-0001JG-Pd; Wed, 16 Oct 2013 06:14:03 +0200
Message-ID: <525E118F.8050208@si6networks.com>
Date: Wed, 16 Oct 2013 01:09:51 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: SM <sm@resistor.net>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20131012194048.0c92f558@resistor.net>	<42ae3f3e73f840e2b40e62430cf8f7d7@CO1PR05MB442.namprd05.prod.outlook.com> <6.2.5.6.2.20131014072334.0d217aa8@resistor.net>
In-Reply-To: <6.2.5.6.2.20131014072334.0d217aa8@resistor.net>
X-Enigmail-Version: 1.5.2
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, 16 Oct 2013 04:14:16 -0000

On 10/14/2013 12:19 PM, SM wrote:
> It's a known problem since at least seven years.  Given that the problem
> is labelled as a security issue there would have to be some changes to
> the specification at some point.  There were design decisions to
> implement the specification and the code has been deployed.  The
> proposed outbound change is one sentence.  The code change to implement
> that one sentence requires reviewing some implementation decisions (re.
> encapsulation, etc.).  Please note that I am not arguing for or against
> a change in the RFC 2119 key words.  The write-up only mentions that the
> draft has been implemented on stateless firewalls.  I am curious about
> whether there are any implementations for a host.

There can't be implementations for hosts because this spec uses an
ICMPv6 type/code that is to be assigned by IANA upong approval of this
document.

That aside, I don't follow your reasoning. If you think the code
required for this spec is complex, take a look at e.g. the TCP code.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From Fred.L.Templin@boeing.com  Wed Oct 16 08:08:35 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D01B611E82B0; Wed, 16 Oct 2013 08:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 4FO6ia-QcJ2a; Wed, 16 Oct 2013 08:08:27 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0C511E8138; Wed, 16 Oct 2013 08:08:24 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GF8Jpr010244; Wed, 16 Oct 2013 10:08:19 -0500
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GF8Bnn009660 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 10:08:18 -0500
Received: from XCH-BLV-404.nw.nos.boeing.com (130.247.25.157) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 08:08:13 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-404.nw.nos.boeing.com ([130.247.25.157]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 08:08:12 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, Ronald Bonica <rbonica@juniper.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyf6Aebc9KTehbEGO6mhunuAlj5n3bUGg
Date: Wed, 16 Oct 2013 15:08:11 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F4CA@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com>
In-Reply-To: <525DD007.8030100@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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, 16 Oct 2013 15:08:35 -0000

Hi Fernando,

To repeat what has already been said many times (and hopefully for
just one final time), if the host is permitted to include an MTU-sized
header chain and if there is a tunnel on the path that needs to fragment
for whatever reason, then that header chain is going to spill into a
second fragment. Then, middleboxes that wish to examine the entire
header chain in the first fragment for whatever reason will be unable
to do so. Consensus or no, those are the facts.

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Tuesday, October 15, 2013 4:30 PM
> To: Templin, Fred L; Ronald Bonica; Brian E Carpenter
> Cc: 6man Mailing List; ietf@ietf.org; Ray Hunter; 6man-
> chairs@tools.ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On 10/14/2013 02:39 PM, Templin, Fred L wrote:
> >
> >> Is there a way to decouple this discussion from draft-ietf-6man-
> >> oversized-header-chain? I would be glad to discuss it in the context
> of
> >> a separate draft.
> >
> > I don't know if there is a way to decouple it. I believe I have shown
> > a way to not mess up tunnels while at the same time not messing up
> your
> > draft. That should be a win-win. In what way would imposing a 1K
> limit
> > on the IPv6 header chain not satisfy the general case?
>=20
> 6man had consensus multiple times on *not* to impose this sort of
> limits
> in this document (that's why the original limit of 1280 bytes was
> removed from earlier versions of this I-D in the first place).
>=20
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20


From otroan@employees.org  Wed Oct 16 08:28:58 2013
Return-Path: <otroan@employees.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 7BC4A11E82D9; Wed, 16 Oct 2013 08:28: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 Sb7eTdJmPvaH; Wed, 16 Oct 2013 08:28:57 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id 8291711E813A; Wed, 16 Oct 2013 08:28:57 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id F41D35F68; Wed, 16 Oct 2013 08:28:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=selector1; bh=X3Ps8OuUulRCNLuJRt0OK Q88N+8=; b=WMFbI56VSPZrlcpiKgQM7N0yz5xtr+WQprYCJeN+8e0dzci4CV+bb 0odAokdVrXGqSwBGRjNLDDM3S2+sOHZ9dJS5yVmWkdRWM37Xhi3xvDR3O4J+rwhd FDG89KbcT5zKKxquGxnuC4oKXxAO7OWsqtJrAZ4qJDcICE7KBKhN9U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; q=dns; s=selector1; b=oWy2Bfko4cK5QPY X2cUHLiQeM2i1/c1As3M3qJIDlDldFdcfkiCRGBMj4AQe8quouVRYlcRySh7qK7P si5e0qPCEHkZsNjz6QBWXvOYilXfHAIJFd5F3sUJlFkjP+3jmGBmwn4iChKbBvtf 8qSqYUCmOCVn2d1ux8MRlHAejGEI=
Received: from dhcp-10-61-106-123.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 16CB75F46; Wed, 16 Oct 2013 08:28:54 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Ole Troan <otroan@employees.org>
In-Reply-To: <2134F8430051B64F815C691A62D9831812F4CA@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 17:28:52 +0200
Message-Id: <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <2134F8430051B64F815C691A62 D9831812 F4CA@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 15:28:58 -0000

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

> To repeat what has already been said many times (and hopefully for
> just one final time), if the host is permitted to include an MTU-sized
> header chain and if there is a tunnel on the path that needs to =
fragment
> for whatever reason, then that header chain is going to spill into a
> second fragment. Then, middleboxes that wish to examine the entire
> header chain in the first fragment for whatever reason will be unable
> to do so. Consensus or no, those are the facts.

absolutely.

the outer IPv6 header is a new datalink for the inner IPv6 header. there =
is no architectural difference if that L2 is IPv6, IPv4 or PPP. take =
IPv4 or PPP as an example, if PPP provides fragmentation, then there is =
no expectation that the PPP or IPv4 layer keeps the payload IPv6 header =
chain in one PPP or IPv4 fragment.

the rules in this document are not recursive. the header chain =
terminates as soon as another IPv6 header is encountered.

does that clarification help?
I'm not quite sure if the document is clear enough on this point.

Best regards,
Ole

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSXrC0AAoJEFuJXizso86gtm4H/3KRIsq5161t/jzpNQR2CC+O
fLGl8vC57ntMjXbv0NR72DI6F83HtX5cLgVimCYJF+bne+KJQwqVufedqnk/iANS
irxBnhdWWBHXU53KZpfIxKS0opxLN90W5u1IEja+0DLWSOQ8S39rvbxbDJOXXSFw
DL/kkrX/h9kyEjHJgFxWx9EKp+xShGsqza1cbkb6kM1rDTAm3QLJkcc4AC6ZNnw+
M0xeseBHdz5VNQ2B/hm25X9T2BzNygJJDc6gvJPAxOyIqer096xLKsVs4Q35bWo3
5kpqy0LW16DId2neGITNAkt29vCucQrV2L65E6pp5j1JcwPiC8Hsj6invzwaowA=
=+4kr
-----END PGP SIGNATURE-----

--Apple-Mail=_D90E7994-AC9C-4D8C-8234-D377D47CD6B4--

From Fred.L.Templin@boeing.com  Wed Oct 16 08:45:38 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4347A11E8318; Wed, 16 Oct 2013 08:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 NSNxkJotu5im; Wed, 16 Oct 2013 08:45:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id D414F11E82B3; Wed, 16 Oct 2013 08:45:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GFjL75011680; Wed, 16 Oct 2013 08:45:22 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GFjJtO011633 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 08:45:19 -0700
Received: from XCH-BLV-208.nw.nos.boeing.com (10.57.37.5) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 08:45:09 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.27]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 08:45:08 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyoRrebc9KTehbEGO6mhunuAlj5n3duEg
Date: Wed, 16 Oct 2013 15:45:07 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <2134F8430051B64F815C691A6! 2D9831812 F4CA@XCH-BLV-504.nw.nos.boeing.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
In-Reply-To: <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 15:45:38 -0000

Hi Ole,

> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Wednesday, October 16, 2013 8:29 AM
> To: Templin, Fred L
> Cc: Fernando Gont; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> Fred,
>=20
> > To repeat what has already been said many times (and hopefully for
> > just one final time), if the host is permitted to include an MTU-
> sized
> > header chain and if there is a tunnel on the path that needs to
> fragment
> > for whatever reason, then that header chain is going to spill into a
> > second fragment. Then, middleboxes that wish to examine the entire
> > header chain in the first fragment for whatever reason will be unable
> > to do so. Consensus or no, those are the facts.
>=20
> absolutely.
>=20
> the outer IPv6 header is a new datalink for the inner IPv6 header.
> there is no architectural difference if that L2 is IPv6, IPv4 or PPP.
> take IPv4 or PPP as an example, if PPP provides fragmentation, then
> there is no expectation that the PPP or IPv4 layer keeps the payload
> IPv6 header chain in one PPP or IPv4 fragment.
>=20
> the rules in this document are not recursive. the header chain
> terminates as soon as another IPv6 header is encountered.

I disagree with the header chain terminating as soon as another IPv6
header is encounter. That defeats defense-in-depth, since outer
perimeter middleboxes would be forced to admit packets with unexamined
header chains inward to inner perimeter middleboxes. And, if the
unexamined header chains contain bad stuff inserted by an attacker,
the attack is successful.

That requirement is also not observed by common middlebox systems
such as Wireshark and tcpdump. Both will blast past encapsulating
IPv6 headers through to the header chain inserted by the original
host without stopping at the outermost IPv6 header.

Thanks - Fred
fred.l.templin@boeing.com
=20
> does that clarification help?
> I'm not quite sure if the document is clear enough on this point.
>=20
> Best regards,
> Ole

From fernando.gont.netbook@gmail.com  Wed Oct 16 09:09:07 2013
Return-Path: <fernando.gont.netbook@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 85BE511E82FE; Wed, 16 Oct 2013 09:09:07 -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 qothIjMHhAiO; Wed, 16 Oct 2013 09:09:06 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC6C21F9FC3; Wed, 16 Oct 2013 09:09:06 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so1143906pdj.17 for <multiple recipients>; Wed, 16 Oct 2013 09:09:05 -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:message-id:subject :from:to:cc:content-type; bh=3hwUh9nA2FaR+Z+wtkJxmZfwtOtH+aswk8l22UbGYuQ=; b=wBbkqxpxw2R98dLotN/l6UAqqPoDUKwFoYYgCE/FY+yEzatk/mxbsXveXfcTpSdbFy B4qGboYAm39QHxYXQ5L5DSJKhgWf50n5hTTp7h6f53vi7P50mgO1Rhyy5liY3WbFVZMY u5BEjH8nGpAR0HDynoywwqkJUOHM37pSbXkcffHrLdzj28Fx8+TiReBBac0z3xmpKB0v F6XV0xvvEWT0stdYyae31q6ZsINTxDn3tXDDMyQ2xxTbolJoG4234mzQsfvnwUVPnTzO 4b+BHMHgdu3AdHyqahMeoUvUmOFhUoQXkofW7aIxv6t4nx0Iqe1wB+NFK0q5EgSmUL/C 10YQ==
MIME-Version: 1.0
X-Received: by 10.68.197.129 with SMTP id iu1mr3628345pbc.139.1381939745742; Wed, 16 Oct 2013 09:09:05 -0700 (PDT)
Sender: fernando.gont.netbook@gmail.com
Received: by 10.70.119.38 with HTTP; Wed, 16 Oct 2013 09:09:05 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 13:09:05 -0300
X-Google-Sender-Auth: TjNstjMBIgbkP_Z1hFM-w3kpeqc
Message-ID: <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fernando@gont.com.ar>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cce4a568e204e8ddeb7d
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 16:09:07 -0000

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

Hi, Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L <Fred.L.Templin@boeing.com
> wrote:

> I disagree with the header chain terminating as soon as another IPv6
> header is encounter. That defeats defense-in-depth, since outer
> perimeter middleboxes would be forced to admit packets with unexamined
> header chains inward to inner perimeter middleboxes. And, if the
> unexamined header chains contain bad stuff inserted by an attacker,
> the attack is successful.
>

The same is true if the underlying encapsulation layer is IPv4. Once you're
encapsulating, all bets are off in that respect. You should do
defense-in-depth at the tunnel ingress or egress points. Or, if you wish, a
middle-box could reassemble-inspect/filter-re-fragment

Note that no matter what hardcoded limit you enforce, an attacker willing
to evade you're security controls can always add an extra-layer of
encapsulation (assuming he controls that). Also, common security policy is
"default deny" -- so if the attacker plays dirty, his packets will be
dropped.



> That requirement is also not observed by common middlebox systems
> such as Wireshark and tcpdump. Both will blast past encapsulating
> IPv6 headers through to the header chain inserted by the original
> host without stopping at the outermost IPv6 header.
>

They do what a middle-box would do in this case: whatever part of the
header chain is there, it's up to you to inspect it. As noted by Ole, when
you tunnel over IP, IP becomes a link layer... so whatever "defense in
depth" techniques you're using, they should be prepared to deal with
scenarios in which a tunneled packet does not contain the entire IPv6
header chain, since not all "link layers" (as IPv4 when IPv6 is tuneled
over IPv4) guarantee a minimum MTU of 1280 bytes.

Thanks,
Fernando

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

<div dir=3D"ltr"><div class=3D"gmail_extra">Hi, Fred,<br></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Oct 16, 2013 at 12:=
45 PM, Templin, Fred L <span dir=3D"ltr">&lt;<a href=3D"mailto:Fred.L.Templ=
in@boeing.com" target=3D"_blank">Fred.L.Templin@boeing.com</a>&gt;</span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I disagree with the header chain terminating=
 as soon as another IPv6<br>
header is encounter. That defeats defense-in-depth, since outer<br>
perimeter middleboxes would be forced to admit packets with unexamined<br>
header chains inward to inner perimeter middleboxes. And, if the<br>
unexamined header chains contain bad stuff inserted by an attacker,<br>
the attack is successful.<br></blockquote><div><br></div><div>The same is t=
rue if the underlying encapsulation layer is IPv4. Once you&#39;re encapsul=
ating, all bets are off in that respect. You should do defense-in-depth at =
the tunnel ingress or egress points. Or, if you wish, a middle-box could re=
assemble-inspect/filter-re-fragment<br>
<br></div><div>Note that no matter what hardcoded limit you enforce, an att=
acker willing to evade you&#39;re security controls can always add an extra=
-layer of encapsulation (assuming he controls that). Also, common security =
policy is &quot;default deny&quot; -- so if the attacker plays dirty, his p=
ackets will be dropped.<br>
<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">

That requirement is also not observed by common middlebox systems<br>
such as Wireshark and tcpdump. Both will blast past encapsulating<br>
IPv6 headers through to the header chain inserted by the original<br>
host without stopping at the outermost IPv6 header.<br></blockquote><div>=
=A0</div>They do what a middle-box would do in this case: whatever part of =
the header chain is there, it&#39;s up to you to inspect it. As noted by Ol=
e, when you tunnel over IP, IP becomes a link layer... so whatever &quot;de=
fense in depth&quot; techniques you&#39;re using, they should be prepared t=
o deal with scenarios in which a tunneled packet does not contain the entir=
e IPv6 header chain, since not all &quot;link layers&quot; (as IPv4 when IP=
v6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.<br>
<br></div><div class=3D"gmail_quote">Thanks,<br></div><div class=3D"gmail_q=
uote">Fernando<br><br><br><br><br></div></div></div>

--e89a8ff1cce4a568e204e8ddeb7d--

From Fred.L.Templin@boeing.com  Wed Oct 16 09:20:31 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F4511E8304; Wed, 16 Oct 2013 09:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.511
X-Spam-Level: 
X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.087,  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 se3QiwC1zaMV; Wed, 16 Oct 2013 09:20:25 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC7411E8146; Wed, 16 Oct 2013 09:20:24 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GGKMfi000676; Wed, 16 Oct 2013 11:20:23 -0500
Received: from XCH-PHX-211.sw.nos.boeing.com (xch-phx-211.sw.nos.boeing.com [130.247.25.140]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GGKLFu000665 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 16 Oct 2013 11:20:21 -0500
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-211.sw.nos.boeing.com ([169.254.11.248]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 09:20:20 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fernando@gont.com.ar>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyooJebc9KTehbEGO6mhunuAlj5n3gcJg
Date: Wed, 16 Oct 2013 16:20:19 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F7BD@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
In-Reply-To: <CANej4=jeYpEm89n6mTzv+vEdhOrXjG9Da3XMgtPp7eS+oa+jDg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 16:20:31 -0000
X-List-Received-Date: Wed, 16 Oct 2013 16:20:31 -0000

--_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Fernando,

Can you please re-send in plaintext, as all of the other messages in this t=
hread
have been? Richly formatted text makes annotation impossible.

Thanks - Fred

From: fernando.gont.netbook@gmail.com [mailto:fernando.gont.netbook@gmail.c=
om] On Behalf Of Fernando Gont
Sent: Wednesday, October 16, 2013 9:09 AM
To: Templin, Fred L
Cc: Ole Troan; 6man-chairs@tools.ietf.org; 6man Mailing List; ietf@ietf.org=
; Ray Hunter; Fernando Gont
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Im=
plications of Oversized IPv6 Header Chains) to Proposed Standard

Hi, Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L <Fred.L.Templin@boeing.co=
m<mailto:Fred.L.Templin@boeing.com>> wrote:
I disagree with the header chain terminating as soon as another IPv6
header is encounter. That defeats defense-in-depth, since outer
perimeter middleboxes would be forced to admit packets with unexamined
header chains inward to inner perimeter middleboxes. And, if the
unexamined header chains contain bad stuff inserted by an attacker,
the attack is successful.

The same is true if the underlying encapsulation layer is IPv4. Once you're=
 encapsulating, all bets are off in that respect. You should do defense-in-=
depth at the tunnel ingress or egress points. Or, if you wish, a middle-box=
 could reassemble-inspect/filter-re-fragment
Note that no matter what hardcoded limit you enforce, an attacker willing t=
o evade you're security controls can always add an extra-layer of encapsula=
tion (assuming he controls that). Also, common security policy is "default =
deny" -- so if the attacker plays dirty, his packets will be dropped.


That requirement is also not observed by common middlebox systems
such as Wireshark and tcpdump. Both will blast past encapsulating
IPv6 headers through to the header chain inserted by the original
host without stopping at the outermost IPv6 header.

They do what a middle-box would do in this case: whatever part of the heade=
r chain is there, it's up to you to inspect it. As noted by Ole, when you t=
unnel over IP, IP becomes a link layer... so whatever "defense in depth" te=
chniques you're using, they should be prepared to deal with scenarios in wh=
ich a tunneled packet does not contain the entire IPv6 header chain, since =
not all "link layers" (as IPv4 when IPv6 is tuneled over IPv4) guarantee a =
minimum MTU of 1280 bytes.
Thanks,
Fernando




--_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_
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 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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Fernando,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Can you please re-send in=
 plaintext, as all of the other messages in this thread<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">have been? Richly formatt=
ed text makes annotation impossible.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks - Fred<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&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;"> fernando=
.gont.netbook@gmail.com [mailto:fernando.gont.netbook@gmail.com]
<b>On Behalf Of </b>Fernando Gont<br>
<b>Sent:</b> Wednesday, October 16, 2013 9:09 AM<br>
<b>To:</b> Templin, Fred L<br>
<b>Cc:</b> Ole Troan; 6man-chairs@tools.ietf.org; 6man Mailing List; ietf@i=
etf.org; Ray Hunter; Fernando Gont<br>
<b>Subject:</b> Re: Last Call: &lt;draft-ietf-6man-oversized-header-chain-0=
8.txt&gt; (Implications of Oversized IPv6 Header Chains) to Proposed Standa=
rd<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Hi, Fred,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L &l=
t;<a href=3D"mailto:Fred.L.Templin@boeing.com" target=3D"_blank">Fred.L.Tem=
plin@boeing.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I disagree with the header chain terminating as soon=
 as another IPv6<br>
header is encounter. That defeats defense-in-depth, since outer<br>
perimeter middleboxes would be forced to admit packets with unexamined<br>
header chains inward to inner perimeter middleboxes. And, if the<br>
unexamined header chains contain bad stuff inserted by an attacker,<br>
the attack is successful.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The same is true if t=
he underlying encapsulation layer is IPv4. Once you're encapsulating, all b=
ets are off in that respect. You should do defense-in-depth at the tunnel i=
ngress or egress points. Or, if you
 wish, a middle-box could reassemble-inspect/filter-re-fragment<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">Note that no matter what hardcoded limit you enforce=
, an attacker willing to evade you're security controls can always add an e=
xtra-layer of encapsulation (assuming he controls that). Also, common secur=
ity policy is &quot;default deny&quot; -- so
 if the attacker plays dirty, his packets will be dropped.<br>
<br>
&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">That requirement is also not observed by common midd=
lebox systems<br>
such as Wireshark and tcpdump. Both will blast past encapsulating<br>
IPv6 headers through to the header chain inserted by the original<br>
host without stopping at the outermost IPv6 header.<o:p></o:p></p>
</blockquote>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">They do what a middle=
-box would do in this case: whatever part of the header chain is there, it'=
s up to you to inspect it. As noted by Ole, when you tunnel over IP, IP bec=
omes a link layer... so whatever &quot;defense
 in depth&quot; techniques you're using, they should be prepared to deal wi=
th scenarios in which a tunneled packet does not contain the entire IPv6 he=
ader chain, since not all &quot;link layers&quot; (as IPv4 when IPv6 is tun=
eled over IPv4) guarantee a minimum MTU of 1280
 bytes.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Fernando<br>
<br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_2134F8430051B64F815C691A62D9831812F7BDXCHBLV504nwnosboe_--


From fgont.si6networks@gmail.com  Wed Oct 16 09:34:50 2013
Return-Path: <fgont.si6networks@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 F38EF11E8316; Wed, 16 Oct 2013 09:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=-0.311, 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 N83h5UGiYBi0; Wed, 16 Oct 2013 09:34:49 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id EB9F011E8329; Wed, 16 Oct 2013 09:34:48 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id n12so984854wgh.23 for <multiple recipients>; Wed, 16 Oct 2013 09:34:47 -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:message-id:subject :from:to:cc:content-type; bh=2A0KJ4SxFmBQUJSpwP7L2rz/0MP4NMuUqlY0CXkJ6x4=; b=Xga+QjvQUsb+nvK3YqYbT6KQ+wQNyWeS1A+IpUgVOzrBlOg2szRxVTr/SAfkWfyGk6 fjwJ4PpryuKH8zTfGT6UTel6mGcke5d/uSZzOjsifXoj1uG+hwuUxRwiSbywlaJYU3SB +SKSFCs/AI6Vl8BC8aYWvMfhouVBKpwIBweVrsxzsc01NxYsbHUjjLkPqr422sbAeAGB J4QHKG7S0dXGW+Dt2N+D796/bVnrcrgapgkHKiTDo/+EmmoE1BojQLZTd1JBN/JKQMah AnbNUZOwBV3NlLELwNokEPyyTbgwJowNi357b9FnMFRaPfa3vB7RtxZB+lTnUCUjm54f feeQ==
MIME-Version: 1.0
X-Received: by 10.194.89.233 with SMTP id br9mr3192125wjb.15.1381941287134; Wed, 16 Oct 2013 09:34:47 -0700 (PDT)
Sender: fgont.si6networks@gmail.com
Received: by 10.217.46.198 with HTTP; Wed, 16 Oct 2013 09:34:47 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 13:34:47 -0300
X-Google-Sender-Auth: cWKPFPFDJm9DLHeoAQ4ENQ3a4wQ
Message-ID: <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fgont@si6networks.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 16:40:38 -0000

[Resending in plain-txt -- my apologies... I was using a web interface...]

Fred,

On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
> I disagree with the header chain terminating as soon as another IPv6
> header is encounter. That defeats defense-in-depth, since outer
> perimeter middleboxes would be forced to admit packets with unexamined
> header chains inward to inner perimeter middleboxes. And, if the
> unexamined header chains contain bad stuff inserted by an attacker,
> the attack is successful.

The same is true if the underlying encapsulation layer is IPv4. Once
you're encapsulating, all bets are off in that respect. You should do
defense-in-depth at the tunnel ingress or egress points. Or, if you
wish, a middle-box could reassemble-inspect/filter-re-fragment

Note that no matter what hardcoded limit you enforce, an attacker
willing to evade you're security controls can always add an
extra-layer of encapsulation (assuming he controls that). Also, common
security policy is "default deny" -- so if the attacker plays dirty,
his packets will be dropped.


> That requirement is also not observed by common middlebox systems
> such as Wireshark and tcpdump. Both will blast past encapsulating
> IPv6 headers through to the header chain inserted by the original
> host without stopping at the outermost IPv6 header.

They do what a middle-box would do in this case: whatever part of the
header chain is there, it's up to you to inspect it. As noted by Ole,
when you tunnel over IP, IP becomes a link layer... so whatever
"defense in depth" techniques you're using, they should be prepared to
deal with scenarios in which a tunneled packet does not contain the
entire IPv6 header chain, since not all "link layers" (as IPv4 when
IPv6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.

Thanks,
Fernando

From Fred.L.Templin@boeing.com  Wed Oct 16 09:54:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7836B11E8138; Wed, 16 Oct 2013 09:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.515
X-Spam-Level: 
X-Spam-Status: No, score=-6.515 tagged_above=-999 required=5 tests=[AWL=0.084,  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 iSYL2mZ96G9v; Wed, 16 Oct 2013 09:54:23 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 4960511E82C3; Wed, 16 Oct 2013 09:54:21 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GGsKmc007963; Wed, 16 Oct 2013 09:54:20 -0700
Received: from XCH-PHX-110.sw.nos.boeing.com (xch-phx-110.sw.nos.boeing.com [130.247.25.39]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GGsJAv007928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 16 Oct 2013 09:54:19 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-PHX-110.sw.nos.boeing.com ([169.254.10.89]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 09:54:18 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOyo2gebc9KTehbEGO6mhunuAlj5n3hyjw
Date: Wed, 16 Oct 2013 16:54:17 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
In-Reply-To: <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 16:54:29 -0000

Hi Fernando,

> -----Original Message-----
> From: fgont.si6networks@gmail.com [mailto:fgont.si6networks@gmail.com]
> On Behalf Of Fernando Gont
> Sent: Wednesday, October 16, 2013 9:35 AM
> To: Templin, Fred L
> Cc: Ole Troan; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org;
> Fernando Gont
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> [Resending in plain-txt -- my apologies... I was using a web
> interface...]
>=20
> Fred,
>=20
> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
> <Fred.L.Templin@boeing.com> wrote:
> > I disagree with the header chain terminating as soon as another IPv6
> > header is encounter. That defeats defense-in-depth, since outer
> > perimeter middleboxes would be forced to admit packets with
> unexamined
> > header chains inward to inner perimeter middleboxes. And, if the
> > unexamined header chains contain bad stuff inserted by an attacker,
> > the attack is successful.
>=20
> The same is true if the underlying encapsulation layer is IPv4.

We should not default to doing as badly as IPv4.

> Once
> you're encapsulating, all bets are off in that respect. You should do
> defense-in-depth at the tunnel ingress or egress points. Or, if you
> wish, a middle-box could reassemble-inspect/filter-re-fragment

If an outer perimeter middlebox connects to a 10Gbps link on its
outward facing interface and a 64Kbps link on its inward facing
interface, then the middlebox can allow a successful DOS attack
against its protected domain if it does not look at headers beyond
the outermost IPv6 header.

> Note that no matter what hardcoded limit you enforce, an attacker
> willing to evade you're security controls can always add an
> extra-layer of encapsulation (assuming he controls that).

Yes. With a 1024 limit on the amount of extension headers a
host can add, approximately 5-6 encapsulations can be added
before the tunnel headers cause the header chain to overflow
the IPv6 minMTU. But, that means that there would still be
5-6 protected perimeters to penetrate before an attack could
penetrate through to the innermost protected domain. This is
considerable defense-in-depth.

> Also, common
> security policy is "default deny" -- so if the attacker plays dirty,
> his packets will be dropped.

Without looking past the outermost IP header, there is no way
to discern the good stuff from the bad stuff. So, default
deny will potentially drop good stuff.

> > That requirement is also not observed by common middlebox systems
> > such as Wireshark and tcpdump. Both will blast past encapsulating
> > IPv6 headers through to the header chain inserted by the original
> > host without stopping at the outermost IPv6 header.
>=20
> They do what a middle-box would do in this case: whatever part of the
> header chain is there, it's up to you to inspect it. As noted by Ole,
> when you tunnel over IP, IP becomes a link layer... so whatever
> "defense in depth" techniques you're using, they should be prepared to
> deal with scenarios in which a tunneled packet does not contain the
> entire IPv6 header chain, since not all "link layers" (as IPv4 when
> IPv6 is tuneled over IPv4) guarantee a minimum MTU of 1280 bytes.

The 1024 proposal gives 256 bytes of room for encapsulation headers
and still fit within the IPv6 minMTU - enough for 5-6 layers of defense
in depth. This is part of the analysis I believe was missing when the
IPv6 minMTU of 1280 was established.

One clarification I would like to make is that I *like* the 1280
IPv6 minMTU and do not think it was a mistake. It was the missing
analysis of what it means for tunnels that I think we are only
now exploring.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> Fernando

From fgont.si6networks@gmail.com  Wed Oct 16 10:04:57 2013
Return-Path: <fgont.si6networks@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 8C52211E8109; Wed, 16 Oct 2013 10:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.834
X-Spam-Level: 
X-Spam-Status: No, score=-1.834 tagged_above=-999 required=5 tests=[AWL=-0.456, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=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 zwc5hxEXBql1; Wed, 16 Oct 2013 10:04:56 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 5292711E8191; Wed, 16 Oct 2013 10:04:51 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so1039591wgg.12 for <multiple recipients>; Wed, 16 Oct 2013 10:04:47 -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:message-id:subject :from:to:cc:content-type; bh=M0nFWF45OUKsK1gdV7vlOUSaDrRrONlqohKpx5La+B4=; b=Bjd1QJ+sEJGSx7d/XxaZPlv6s7zBIHlozJ5P3QnYfS9dC4Rzzyr85Xf2c9aOUox6uG l/cm2ypTmqbZPH6I6YlVcHZpPv40C4ipGztgru4RvJ0LNkq1g5kHyffYyh3Im2dNwzIS yIKnhsa4mKRVp1qME1Y5UNPDzBVe/wfafwce9Q2k6IfXBxdnH/9Ii876I1HyL6KOl68f 7R4/Nn240l2En6i8t22mBLVW7/xHupT8e521o8KvTfTdQ0JnSrK5K5u1/ehT2umrGc8s SU1lZy+qCdxkh+NrwWjUGa/cPhCNTELVxEqn3Dn+dv0WrMMlRmm4YVXKgXjMv4fljE7w Lfyg==
MIME-Version: 1.0
X-Received: by 10.180.198.5 with SMTP id iy5mr15621028wic.45.1381943086490; Wed, 16 Oct 2013 10:04:46 -0700 (PDT)
Sender: fgont.si6networks@gmail.com
Received: by 10.217.46.198 with HTTP; Wed, 16 Oct 2013 10:04:46 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net> <5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com> <52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com>
Date: Wed, 16 Oct 2013 14:04:46 -0300
X-Google-Sender-Auth: OA63yt7cPR5bGiC6snn3uARP8HM
Message-ID: <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
From: Fernando Gont <fgont@si6networks.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 17:04:57 -0000

On Wed, Oct 16, 2013 at 1:54 PM, Templin, Fred L
<Fred.L.Templin@boeing.com> wrote:
>> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
>> <Fred.L.Templin@boeing.com> wrote:
>> > I disagree with the header chain terminating as soon as another IPv6
>> > header is encounter. That defeats defense-in-depth, since outer
>> > perimeter middleboxes would be forced to admit packets with
>> unexamined
>> > header chains inward to inner perimeter middleboxes. And, if the
>> > unexamined header chains contain bad stuff inserted by an attacker,
>> > the attack is successful.
>>
>> The same is true if the underlying encapsulation layer is IPv4.
>
> We should not default to doing as badly as IPv4.

The point is that this is no worse than IPv4. And it is very likely
that one of underlying encapsulations will be IPv4.


>> Once
>> you're encapsulating, all bets are off in that respect. You should do
>> defense-in-depth at the tunnel ingress or egress points. Or, if you
>> wish, a middle-box could reassemble-inspect/filter-re-fragment
>
> If an outer perimeter middlebox connects to a 10Gbps link on its
> outward facing interface and a 64Kbps link on its inward facing
> interface, then the middlebox can allow a successful DOS attack
> against its protected domain if it does not look at headers beyond
> the outermost IPv6 header.

Is it me, or there are actually a plethora of attack vectors an
attacker would use (instead of this one) in such scenario?



>> Note that no matter what hardcoded limit you enforce, an attacker
>> willing to evade you're security controls can always add an
>> extra-layer of encapsulation (assuming he controls that).
>
> Yes. With a 1024 limit on the amount of extension headers a
> host can add, approximately 5-6 encapsulations can be added
> before the tunnel headers cause the header chain to overflow
> the IPv6 minMTU.

That depends on whether extension headers are employed in different
layer of encapsulation.

Besides, what's the different between an attacker exceeding your
hardcoded limit and traffic resulting in tunnling packets failing to
include the entire header chain?

As noted off-list, this hard limit becomes a BCP, rather than a std
update: the larger your extension header chain, the higher the chances
that your packets get dropped. For instance, your harcoded 1000 (or
whatever) value means that there are still *lots* of boxes that will
not be able to handle those packets properly, and hence will get
dropped (check the 6man and/or v6ops discussions).

Thanks,
Fernando

From Fred.L.Templin@boeing.com  Wed Oct 16 10:23:10 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80421F8EC3; Wed, 16 Oct 2013 10:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.218
X-Spam-Level: 
X-Spam-Status: No, score=-6.218 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, J_CHICKENPOX_13=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 xBwNLNuzTfwl; Wed, 16 Oct 2013 10:23:01 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 5E15A11E8191; Wed, 16 Oct 2013 10:23:01 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9GHN0QA016043; Wed, 16 Oct 2013 10:23:00 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9GHMxhQ016021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Wed, 16 Oct 2013 10:22:59 -0700
Received: from XCH-BLV-405.nw.nos.boeing.com (130.247.25.158) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Wed, 16 Oct 2013 10:22:58 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-BLV-405.nw.nos.boeing.com ([169.254.5.227]) with mapi id 14.03.0158.001; Wed, 16 Oct 2013 10:22:58 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOypHQebc9KTehbEGO6mhunuAlj5n3j5QA
Date: Wed, 16 Oct 2013 17:22:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
In-Reply-To: <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, 6man Mailing List <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Ray Hunter <v6ops@globis.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: Wed, 16 Oct 2013 17:23:11 -0000

Hi Fernando,

> -----Original Message-----
> From: fgont.si6networks@gmail.com [mailto:fgont.si6networks@gmail.com]
> On Behalf Of Fernando Gont
> Sent: Wednesday, October 16, 2013 10:05 AM
> To: Templin, Fred L
> Cc: Ole Troan; Ronald Bonica; Brian E Carpenter; 6man-
> chairs@tools.ietf.org; Ray Hunter; 6man Mailing List; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt>
> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
>=20
> On Wed, Oct 16, 2013 at 1:54 PM, Templin, Fred L
> <Fred.L.Templin@boeing.com> wrote:
> >> On Wed, Oct 16, 2013 at 12:45 PM, Templin, Fred L
> >> <Fred.L.Templin@boeing.com> wrote:
> >> > I disagree with the header chain terminating as soon as another
> IPv6
> >> > header is encounter. That defeats defense-in-depth, since outer
> >> > perimeter middleboxes would be forced to admit packets with
> >> unexamined
> >> > header chains inward to inner perimeter middleboxes. And, if the
> >> > unexamined header chains contain bad stuff inserted by an
> attacker,
> >> > the attack is successful.
> >>
> >> The same is true if the underlying encapsulation layer is IPv4.
> >
> > We should not default to doing as badly as IPv4.
>=20
> The point is that this is no worse than IPv4. And it is very likely
> that one of underlying encapsulations will be IPv4.

If an underlying encapsulation is IPv4, there is a very good
chance that the IPv4 path MTU is at least 1280. Else, the
underlying link with MTU smaller than 1280 is very likely to
be low speed. That being the case, the middlebox would have to
perform IPv4 reassembly, yes. But, that is truly a corner case,
and only when IPv4 is involved. Again, we should be striving
to do better than IPv4.

> >> Once
> >> you're encapsulating, all bets are off in that respect. You should
> do
> >> defense-in-depth at the tunnel ingress or egress points. Or, if you
> >> wish, a middle-box could reassemble-inspect/filter-re-fragment
> >
> > If an outer perimeter middlebox connects to a 10Gbps link on its
> > outward facing interface and a 64Kbps link on its inward facing
> > interface, then the middlebox can allow a successful DOS attack
> > against its protected domain if it does not look at headers beyond
> > the outermost IPv6 header.
>=20
> Is it me, or there are actually a plethora of attack vectors an
> attacker would use (instead of this one) in such scenario?

Please don't discount this scenario as contrived or unlikely; there
are certainly such low-end data links in real deployments (civil
aviation networks, DoD networks, etc.) that need DOS protection.

> >> Note that no matter what hardcoded limit you enforce, an attacker
> >> willing to evade you're security controls can always add an
> >> extra-layer of encapsulation (assuming he controls that).
> >
> > Yes. With a 1024 limit on the amount of extension headers a
> > host can add, approximately 5-6 encapsulations can be added
> > before the tunnel headers cause the header chain to overflow
> > the IPv6 minMTU.
>=20
> That depends on whether extension headers are employed in different
> layer of encapsulation.

Most tunneling protocols I am aware of do not specify that additional
extension headers can be added (one exception is the Encapsulation Limit
option specified by RFC2473). So, it should be reasonable for a middlebox=20
to drop an encapsulated packet with an unusually long encapsulation
extension header chain inserted by the purported tunnel ingress.=20
=20
> Besides, what's the different between an attacker exceeding your
> hardcoded limit and traffic resulting in tunnling packets failing to
> include the entire header chain?

The hard-coded limit is 5-6 layers of encapsulation headers fitting
within the IPv6 minMTU but that does not stop tunnels from recursing
indefinitely. What it does do is provide a healthy number of layers
of defense in depth.

> As noted off-list, this hard limit becomes a BCP, rather than a std
> update: the larger your extension header chain, the higher the chances
> that your packets get dropped. For instance, your harcoded 1000 (or
> whatever) value means that there are still *lots* of boxes that will
> not be able to handle those packets properly, and hence will get
> dropped (check the 6man and/or v6ops discussions).

That's OK. Let the BCP for hosts be 1024, and I am happy.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> Fernando

From adrian@olddog.co.uk  Wed Oct 16 13:50:54 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 B9C0621F9985; Wed, 16 Oct 2013 13:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  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 uuUP1mVyyQ62; Wed, 16 Oct 2013 13:50:42 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 319B221F995B; Wed, 16 Oct 2013 13:50:41 -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 r9GKoeVZ030581;  Wed, 16 Oct 2013 21:50:40 +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 r9GKocFn030500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Oct 2013 21:50:39 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-pim-explicit-tracking-08.txt>	(IGMP/MLD-Based	Explicit Membership Tracking Function for	Multicast Routers) to	Proposed Standard
Date: Wed, 16 Oct 2013 21:50:37 +0100
Message-ID: <01a101cecab1$5ee6f6e0$1cb4e4a0$@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: Ac7KsVqD5Pwz8Vn0TmSmjwGpaJrDqw==
Content-Language: en-gb
Cc: pim@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: Wed, 16 Oct 2013 20:50:54 -0000

I have a few small comments that I collected during my review as responsible AD.
Please address them as part of the IETF last call.

Thanks,
Adrian

===

I think your core reference [6] is supposed to refer to RFC 2236 for the
core definition of IGMPv2. That RFC certainly matches the name of the
document you have given.

[Hint: idnits is your friend!]

---

idnits complains about the 2119 boiler plate because you are missing a
space in
  "RECOMMENDED","MAY",

---

Section 1 contains a clumsy sentence

   To alleviate the problem, unsolicited
   report messages are transmitted the [Robustness Variable] times
   (defined in [2][3]).

How about

   To alleviate this problem, unsolicited
   report messages are retransmitted a number of times according to the
   value of the [Robustness Variable] defined in [2] and [3].

---

Section 3

While *everyone* knows what S and G stand for, you should still say.

> -----Original Message-----
> From: pim-bounces@ietf.org [mailto:pim-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 16 October 2013 21:46
> To: IETF-Announce
> Cc: pim@ietf.org
> Subject: [pim] Last Call: <draft-ietf-pim-explicit-tracking-08.txt> (IGMP/MLD-
> Based Explicit Membership Tracking Function for Multicast Routers) to Proposed
> Standard
> 
> The IESG has received a request from the Protocol Independent Multicast
> WG (pim) to consider the following document:
> - 'IGMP/MLD-Based Explicit Membership Tracking Function for Multicast
>    Routers'
>   <draft-ietf-pim-explicit-tracking-08.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-11-06 (this is a 3 week last call to allow
> extra time as people are preparing for IETF-88). 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.


From peter@akayla.com  Wed Oct 16 21:15:18 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 1F7AB11E8144; Wed, 16 Oct 2013 21: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 fUPktV-BNX0Z; Wed, 16 Oct 2013 21:15:13 -0700 (PDT)
Received: from p3plsmtpa08-09.prod.phx3.secureserver.net (p3plsmtpa08-09.prod.phx3.secureserver.net [173.201.193.110]) by ietfa.amsl.com (Postfix) with ESMTP id F35E411E816F; Wed, 16 Oct 2013 21:15:04 -0700 (PDT)
Received: from [172.17.72.240] ([71.248.111.164]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id e4Ew1m00G3YsDkf014EyX2; Wed, 16 Oct 2013 21:15:02 -0700
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Date: Wed, 16 Oct 2013 21:14:58 -0700
Subject: Gen-ART LC review of draft-ietf-6man-oversized-header-chain-08
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-6man-oversized-header-chain.all@tools.ietf.org>
Message-ID: <CE84AB92.6F47%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-ietf-6man-oversized-header-chain-08
In-Reply-To: <CE834CA6.6EE3%peter@akayla.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.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: Thu, 17 Oct 2013 04:15:18 -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>

Document: draft-ietf-6man-oversized-header-chain-08
Reviewer: Peter Yee
Review Date: Oct-16-2013
IETF LC End Date: Oct-16-2013
IESG Telechat date: TBD

Summary: This draft is almost ready for publication as a proposed
standard but has open issues, described in the review.
[Ready with issues]

This draft attempts to overcome a potential problem caused by the
fragmentation of IPv6 header chains by limiting such chains to
fitting within the first fragment.  This permits stateless
packet filtering firewalls to make an appropriate decision based
on a single fragment rather than having to rely on incomplete
information that might be present in a first fragment if the
header were split across more than one fragment.

Major issues: None

Minor issues:

Page 10, 1st paragraph: the term "improperly-fragmented" is
used.  Are these truly improperly-fragmented packets or simply
ones that are unfriendly to stateless packet filtering?  It seems
more like the lengthy headers were within spec to date and are now
being prohibited to solve a specific problem.

Nits:

General: use a comma after the terms "e.g." or "i.e" throughout the
document.  Usage is inconsistent.

Page 3, 3rd paragraph: insert "the" between "from" and "IPv6".

Page 8, 1st paragraph: replace "a" with "an" before "IPv6
datagram".

Page 8, 2nd paragraph: the parenthetical example does not appear
to be a good match for the preceding text.  It is written as a
mechanism that allows the possible maintenance of the status quo
rather than giving an example of how the preceding SHOULD might
be implemented.  E.g., indicates an example of something.

Page 8, paragraph 3, 1st sentence: change "requirements" to
"requirement".  Only one requirement was given and that was
that the entire header chain be in the first fragment.

Page 8, 3rd paragraph, 2nd sentence: delete the parenthetical
statement and the "or not".  They are redundant.

Page 8, 4th paragraph, 1st sentence: change "requirements" to
"requirement" for the same reason given above.

Page 8, 5th paragraph, 1st sentence: change "requirements" to
"requirement" for the same reason given above.

Page 10, 1st paragraph: append a comma after "traditional".




From fgont@si6networks.com  Wed Oct 16 22:04:41 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 3D77321F9EC4; Wed, 16 Oct 2013 22:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level: 
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.062, 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 qru0lRueEO3E; Wed, 16 Oct 2013 22:04:40 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5549E21F9EB0; Wed, 16 Oct 2013 22:04:39 -0700 (PDT)
Received: from 17-153-16-190.fibertel.com.ar ([190.16.153.17] helo=[192.168.1.166]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1VWfl9-0004JD-9b; Thu, 17 Oct 2013 07:04:34 +0200
Message-ID: <525F6FDA.9000402@si6networks.com>
Date: Thu, 17 Oct 2013 02:04:26 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>,  draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-6man-oversized-header-chain-08
References: <CE84AB92.6F47%peter@akayla.com>
In-Reply-To: <CE84AB92.6F47%peter@akayla.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.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: Thu, 17 Oct 2013 05:04:41 -0000

Hi, Peter,

Thanks so much for your feedback! Please find my comments in-line....

On 10/17/2013 01:14 AM, Peter Yee wrote:
> Minor issues:
> 
> Page 10, 1st paragraph: the term "improperly-fragmented" is
> used.  Are these truly improperly-fragmented packets or simply
> ones that are unfriendly to stateless packet filtering?

The later. (Yep, th wording could be improved). How about:

"  This document describes how undesirably-fragmented packets can
   prevent traditional stateless packet filtering."



> It seems
> more like the lengthy headers were within spec to date and are now
> being prohibited to solve a specific problem.

I deem this as a corner case that wasn't expected to happen, but yet was
allowed (other might correct me if I'm wrong).


> Nits:
> 
> General: use a comma after the terms "e.g." or "i.e" throughout the
> document.  Usage is inconsistent.

Remove or add?



> Page 3, 3rd paragraph: insert "the" between "from" and "IPv6".

Done.



> Page 8, 1st paragraph: replace "a" with "an" before "IPv6
> datagram".

Done.


> Page 8, 2nd paragraph: the parenthetical example does not appear
> to be a good match for the preceding text.  It is written as a
> mechanism that allows the possible maintenance of the status quo
> rather than giving an example of how the preceding SHOULD might
> be implemented.  E.g., indicates an example of something.

mm.. not sure what you mean. Could you please elaborate?



> Page 8, paragraph 3, 1st sentence: change "requirements" to
> "requirement".  Only one requirement was given and that was
> that the entire header chain be in the first fragment.

Done.



> Page 8, 3rd paragraph, 2nd sentence: delete the parenthetical
> statement and the "or not".  They are redundant.

Done.



> Page 8, 4th paragraph, 1st sentence: change "requirements" to
> "requirement" for the same reason given above.

Done



> Page 8, 5th paragraph, 1st sentence: change "requirements" to
> "requirement" for the same reason given above.
Done



> Page 10, 1st paragraph: append a comma after "traditional".

Done.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From alejandroacostaalamo@gmail.com  Thu Oct 17 00:50:32 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 C501F21F9A71 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 00:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OxlFCwa5SxO7 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 00:50:32 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0982B11E80F5 for <ietf@ietf.org>; Thu, 17 Oct 2013 00:50:29 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id y13so2297181pdi.40 for <ietf@ietf.org>; Thu, 17 Oct 2013 00:50:29 -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=KxIzOX2Q7Rn6IOPCge0zVJr8dzmCGP1GwA2OYNXdnsA=; b=xBzGO5Oc38zYvfN42zcR2vsiixcWKR0ls4Q+BWE/IWU4nZ5cfxVkueHNZLO13L0lON zjh4aHuXSQ01cgSkDW9WAO18oSQwYfIlIaEbb08AfMxhtGJlKtyZhFEiiRXQ17lXGacN yI075PWdjAUuOwuwkWqfo2rNTa8nAnI1kdx/AptDX6qw8sIbLb8kPWFAiCeXW3k9kv3l 8in0wnqjWtPs9WW4ommrNOCuHmOyNStlvZBsMUy/i9f3XO9jFEfuOlT9jEtOMXWqGoYv b9qi2d/0GV2GGssF5bYFDsPJrH20kNjGvdXlg6nMaLA3SO/g6h1LLrbayNrjSrwLakD0 ohMw==
X-Received: by 10.68.137.138 with SMTP id qi10mr1885282pbb.113.1381996229645;  Thu, 17 Oct 2013 00:50:29 -0700 (PDT)
Received: from [10.80.24.247] ([103.14.185.10]) by mx.google.com with ESMTPSA id dq3sm95909750pbc.35.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 00:50:28 -0700 (PDT)
Message-ID: <525F33B2.3070506@gmail.com>
Date: Wed, 16 Oct 2013 20:17:46 -0430
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com>
X-Enigmail-Version: 1.5.2
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, 17 Oct 2013 07:50:32 -0000

Hello,
  I just read the new version of the draft, it's nice to see that most
suggestion/comments were added to the draft.
  First, I would like to say I do support your draft.
  Second, I noticed you changed the title of your draft from:
  "Improving the ISOC Fellowship programme to Attracting people from
under-represented regions into
the IETF"

  to

  "Improving the ISOC Fellowship programme to attract people from
under-represented regions into the IETF"

  IMHO opinion -and not being native English speaker- you improved it a
little bit but I think the previous comments suggested even something
more generic, like just improving the ISOC fellowship programme and not
only "attack" people to the IETF. I mean, it's very true you mention
several other things in your draft besides attracting people.


Thanks,

Alejandro,



On 10/10/13 13:40, S Moonesamy wrote:
> Hi Jari,
> 
> Here's is a draft about improving the ISOC Fellowship programme to
> attract people from under-represented regions into the IETF.  The draft
> builds upon the ISOC work, proposing adjustments and additional efforts,
> with the goal of enabling more sustained and active participation by
> contributors from under-represented regions.
> 
> In a blog article ( http://www.ietf.org/blog/2013/04/diversity/ ), it is
> mentioned that:
> 
>  "The design team will present their recommendations to the community,
>   and engage in the discussion.  Recommendations with community support
>   will be taken forward."
> 
> The draft only makes suggestions instead of recommendations.  I am
> copying this message to ietf@ietf.org so that the community can comment
> about the draft.
> 
> Regards,
> S. Moonesamy


From alejandroacostaalamo@gmail.com  Thu Oct 17 00:50:43 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 ED13211E825C for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 00:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTZA+Bb1Kted for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 00:50:42 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E324111E825A for <ietf@ietf.org>; Thu, 17 Oct 2013 00:50:40 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y13so2285292pdi.5 for <ietf@ietf.org>; Thu, 17 Oct 2013 00:50:37 -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=GaKXG6QlnezW0JhnjTDVjSB9RNZ3FmliI+AoO7+SVJs=; b=LfXnbHgOs4d6WC/T1lFt29ozt5jYsCfEWky7aZN+6NkW2xHCOAYKLyU/MS5UEnX8vb YPP+YoFCwVgTKQDwLzxRoPMA6fgrfg0OIB/IvcZvts/rZcHlfIjY5WEmrSFRU0+poVg2 oX1go7jvRzNclYrzXBKxMD3UmiQXon0DBSn0k494Am2iuzi3JsRxcpCPCuW+U6Ls2VlV yGh+AcbpYblWvw3E5w7bEALJlPnqrmbDGDjnVZXFGaR53xIdB+ZQtSDcWQpy4YCofbxO XIyRQVn9tiPpK8EDXcd7BhfYECCksAK4DJ6VnJmL8TUvRMyNzFpmVQNCerKEdussmCY3 /8GQ==
X-Received: by 10.66.249.134 with SMTP id yu6mr7755689pac.37.1381996237777; Thu, 17 Oct 2013 00:50:37 -0700 (PDT)
Received: from [10.80.24.247] ([103.14.185.10]) by mx.google.com with ESMTPSA id gg10sm95897361pbc.46.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 00:50:36 -0700 (PDT)
Message-ID: <525F3486.1000108@gmail.com>
Date: Wed, 16 Oct 2013 20:21:18 -0430
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com>	<E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com>, <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com>	<290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk>	<93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net> <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
In-Reply-To: <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
X-Enigmail-Version: 1.5.2
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, 17 Oct 2013 07:50:43 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

On 11/10/13 08:52, Eggert, Lars wrote:
> Hi,
> 
> On Oct 11, 2013, at 14:43, Jari Arkko <jari.arkko@piuha.net> wrote:
>> I do have a question for Lars though. What are your opinions on this? (You said that there is no consensus, but I'd like to hear also your thoughts.)
> 
> so one key question is what influence the IETF actually has on an ISOC program. We can certainly state our wishes, but my belief is that it's ISOC's program in the end, and they can basically chose to run it as they see fit. That doesn't come out in the draft at all.
> 
> Another issue I have with the the draft is written with the implied understanding that the program should fund the repeated attendance of residents of under-represented regions who are actively participating in some sort of way. It's not clear to me that this is really what would be best in terms of increasing organizational diversity over time. I wouldn't want to fund the same people over and over; I'd much rather bring in new people all the time in the hopes of spreading the word about the IETF widely and hoping that some folks will end up in roles where they can occasionally attend on their own dime. I'd like to be able to bring in other under-represented groups (students, academics, women, etc.) We can certainly have a discussion about what is best; my point is that the draft has already decided that one approach is the way to go.

I wonder if the draft should mention % of new & returning fellows.
Should it be a fixed %?.

> 
> I also have a few issues with the suggestions it makes:
> 
> Section 4.1 requires that an applicant needs to already have been a participant in the IETF. That seems excessive. For returning fellows, some sort of engagement in the IETF after a while would be nice, but I can see valid cases for supporting someone's repeated attendance who isn't contributing in a very visible role. Also, I question the possibility to quantify and compare someone's impact of IETF involvement. And again, there are others than "resident of a country in an under-represented region" who we might want to bring in, and we probably don't need to fund the attendance of employees of large vendors who happen to be residents of under-represented regions.
> 
> The evaluation panel in Section 4.2 is therefore also problematic. And I wouldn't want to blindly "prioritize people who have been contributing over time to real IETF work" - we need to keep the flexibility of bringing in someone new who has high potential even if it means that someone who has been funded to attend in the past isn't going to be covered.
> 
> But my main issue is that the draft sounds like its trying to take over and redefine an ISOC program, which I don't think the IETF can or should do. The ISOC program has a purpose, a history and at least from my perspective is working pretty well with the budget it has available. I'm not sure we can actually improve it much.
> 
> Lars
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSXzR8AAoJEPLWfIhsIf1k0t4IAKK83ur1EopuBZ/Wi7/EudZc
fBY2JnvDkenhBtkxa2xPYECFLJeDhelHA4NMHYiRUcEpdeTrc2K1JmZ6KRb93iw5
W5MSadOIkukjEp40DVyB2ZCJP015YupNzqIWp7mQOkcEfeqD009Bt32eLkixVKsG
zAFHVAVoctQOLiEzOlWSD1e/xpnAx3QHugjt414zvvgM7rDFh3JldiaJxa5PBK+E
Pulhh5kNlNXfax7pOOn2pVHaggIdDQWyOIE6S0aC9OmH9EGSkQY6F9VDe2NYMJtH
s9usWMAbYFonrx2jg+sKETcT6QUOQ6Uw2Vh1+0M2FlPq6rRZvCwIC56rFGN9rOg=
=nqEC
-----END PGP SIGNATURE-----

From adrian@olddog.co.uk  Thu Oct 17 03:25: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 8F78921F9BF3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 03:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wi2MvmTYo-kF for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 03:25:07 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 753E121F9C7A for <ietf@ietf.org>; Thu, 17 Oct 2013 03:25:03 -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 r9HAOqvW004202;  Thu, 17 Oct 2013 11:24:52 +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 r9HAOn9o004138 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Oct 2013 11:24:49 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <rjsparks@nostrum.com>, <daedulus@btconnect.com>, <erosen@cisco.com>, <loa@pi.nu>
References: <018401cecaae$12979f90$37c6deb0$@olddog.co.uk> <CE84510F.E91F3%michelle.cotton@icann.org>
In-Reply-To: <CE84510F.E91F3%michelle.cotton@icann.org>
Subject: FW: Changes to complete draft-cotton-rfc4020bis
Date: Thu, 17 Oct 2013 11:24:48 +0100
Message-ID: <02b801cecb23$1d04f0c0$570ed240$@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: AQGORTsaYgEJ7a4bNn8AHIQeEmdA15p5tm1g
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, 17 Oct 2013 10:25:14 -0000

Michelle writes...

> I have just submitted a new version of draft-cotton-rfc4020bis.
> 
> The below changes were made and now appear in version 02.
> (see all instances of "MC" for my comments)
> 
> Robert Sparks
> General Area Review Team review
> 
>> Issue : Section 2 is very confusing. It starts out listing 4 things that
>> look like they all have to be met. But then the last sentence confuses
>> things.
>> Is just reinforcing that both a and b have to be met (if so, then
>> wouldn't things also stop if c and d weren't met? (see 3.1 step2)).
>> I suggest replacing "If conditions (a) or (b)" with "If any of the above
>> conditions"
> 
> MC: 
> Deleted the whole paragraph. 
> The text at the top of the section already completely covers this.
> 
>> Nit 1: Section 3.1 reads harshly at the transition from step 4 to
>> step 5. It leaves it implicit that the AD has to approve.
>> Step 3 has  "if steps 2 and 3 are satisfied". 4020 said "with the
>> approval of the Area Director(s)". Adding that text  to step 5 
>> would address the nit.
> 
> MC: 
> OLD
>    5.  The WG chairs request IANA to make an early allocation.
> NEW
>    5.  If the Area Directors approve step 4., the WG chairs request IANA to
>     make an early allocation.
> END
> 
>> Nit 2: The introduction contains a bit of text that it carried 
>> forward, slightly modified, from 4020 for which I suggest
>> further modification:
>> replace
>> "the IETF community wishes to retain tight control of the protocol"
>> with
>> "the IETF community has consensus to retain tight control of the
>> registry content"
> 
> MC: DONE
> 
>> Nit 3: Several reviewers have pointed to a lack of clarity in section
>> 2 a.
>> I suggest taking the change John Klensin proposed (with tweaks as
>> below)
>> 
>> 	The code points must normally be from a space designated
>> 	as "RFC Required", "IETF Review", or "Standards Action".
>> 	In addition, code points from a "Specification
>> 	Required" space are allowed if the specification will be
>> 	published as an RFC.
> 
> MC: 
> OLD
>    a.  The code points must be from a space designated as "Specification
>        Required" (where an RFC will be used as the stable reference),
>        "RFC Required", "IETF Review", or "Standards Action".
> NEW
>    a.  The code points must be from a space designated as  "RFC
>         Required", "IETF Review", or "Standards Action". Additionally
>         code points from a "Specification Required" space are
>         allowed if the specification will be published as an RFC.
> END
> 
> 
> ---
> 
> Tom Petch (et al.)
> 
>> Clarification of "deprecation".
>
> MC:
> 
> Section 3.2
> No change needed: it already points at 3.3 for a definition.
> 
> Section 3.3, replacement text
>
>    As described in Section 3.1, each Temporary assignment is recorded in
>    the registry with the date of expiry of the assignment. If an early
>    allocation expires before the document progresses to the point where
>    IANA normally makes allocations, the authors and WG chairs may repeat
>    the process in section 3.1 to request renewal of the code points.  At
>    most, one renewal request may be made; thus, authors should choose
>    carefully when the original request is to be made.
> 
>    As an exception to the above rule, under rare circumstances, more
>    than one allocation renewal may be justified.  All such further
>    renewal requests must be reviewed by the IESG.  The renewal request
>    to the IESG must include the reasons why such further renewal is
>    necessary, and the WG's plans regarding the specification.
> 
>    If a follow-up request is not made, or the document fails to progress
>    to an RFC, the assignment will remain visible in the registry but the
>    temporary assignment will be shown to have expired as indicated by
>    the expiry date.  The WG chairs are responsible for informing IANA
>    that the expired assignments are not required and that the code
>    points are to be marked "deprecated".
> 
>    A deprecated code point is not marked as allocated for use as
>    described in any document (that is, it is not allocated), and is not
>    available for allocation in a future document.
> 
>    The WG chairs may inform IANA that a deprecated code point can be
>    completely de-allocated (i.e., made available for new allocations) at
>    any time after it has been deprecated. Factors influencing this
>    decision will include whether there may be implementations using the
>    previous temporary allocation, and the availability of other
>    unallocated code points in the registry.
> 
>    Implementers and deployers need to be aware that this deprecation and
>    de-allocation could take place at any time after expiry, and an
>    expired early allocation is therefore best considered as deprecated.
> 
>    It is not IANA's responsibility to track the status of allocations,
>    their expiration, or when they may be re-allocated.
> 
>    Note that if a document is submitted for review to the IESG and at
>    the time of submission some early allocations are valid (not
>    expired), these allocations must not be consider to have expired
>    while the document is under IESG consideration or waiting in the RFC
>    Editor's queue after approval by the IESG.
> 
> 
> ---
> 
> Eric Rosen
> 
> MC: see continued discussion on mailing list.
>
> Section 2
> OLD
>    d.  There is sufficient interest in early (pre-RFC) implementation
>        and deployment in the community as judged by working group chairs
>        or ADs.
> NEW
>    d.  The working group chairs and ADs judge that there is sufficient
>        interest in the community for early (pre-RFC) implementation and
>        deployment, or that failure to make an early allocation might
>        lead to contention for the code point in the field.
> END
> 
> Section 3.1
> OLD
>    Note that Internet-Drafts should not include a specific value of a
>    code point until this value has been formally allocated by IANA.
> NEW
>    Note that Internet-Drafts should not include a specific value of a
>    code point until IANA has completed the early allocation for this
>    value.
> END
> 
> 
> ---
> 
> Loa Andersson
> Routing Directorate review
> 
> MC: The whole point is that all registries that comply with 2a support
> early allocation.
>
> Section 4
> NEW
>    This document removes the need for registries to be marked as
>    specifically allowing early allocation. IANA is requested to clean up
>    the registries by removing any such markings.
> END
> 
> 
> With the conversion of the registries to XML as the source, it is our
> intention to have a script run to alert us of expired temporary
> allocations.  We are not quite there yet, so I don't want to document
> that the assignments will be removed automatically by IANA.  What
> we do want to do is when IANA finds an assignment that has expired,
> we will contact the assignee to find out if it should be removed or if 
> the document is close to publication so that the date can be extended
> with AD/WG Chair approval.
> 
> He also struggled a bit with terminology. "
" I don't struggle (but I also don't speak Swedish). Perhaps 5026bis
> could
> sort out these terms and include them in a glossary?
> 
> 5226bis will be enhanced to include clarification of the terms "registry", 
> "name space", and "code point space."
> 
> 
> ---
> 
> Adrian Farrel
> 
> MC:
>
> Section 3.1
> OLD
>    6.  IANA makes an allocation from the appropriate registry, marking
>        it as "Temporary", valid for a period of one year from the date
>        of allocation.  The date of first allocation the date of expiry
>        should also be recorded in the registry and made visible to the
>        public.
> NEW
>    6.  IANA makes an allocation from the appropriate registry, marking
>        it as "Temporary", valid for a period of one year from the date
>        of allocation.  The date of first allocation and the date of expiry
>        are also be recorded in the registry and made visible to the
>        public.
> END
> 
> Section 3.2
> OLD
>     Allocation is then just a matter of removing the
>    "temporary" tag from the allocation description.
> NEW
>     Allocation is then just a matter of removing the
>    "Temporary" tag from the allocation description.
> END



From abdussalambaryun@gmail.com  Thu Oct 17 04:14:45 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 18C5211E8102; Thu, 17 Oct 2013 04:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[AWL=-1.210, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_75=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 QdhwwEqeXAbT; Thu, 17 Oct 2013 04:14:43 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C5C1021F9C3A; Thu, 17 Oct 2013 04:14:43 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so2558014pdj.3 for <multiple recipients>; Thu, 17 Oct 2013 04:14: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:content-transfer-encoding; bh=0oqUEiYEmtD4Sie39WTR80xEOY0h4edt7nAge1N2XHg=; b=QmFP6NfT5d8s/NDihjd0uw/He0b85g0d92iABWEOlmbdPfQheT8J4dGNuSFR5ozBo4 wCQvE7O0P++2So0JVt3sExGMDFD6MCAEgMnSJN7jGBl1BTsFuEtwpWGz6sDfjxlN8VcY 9zb/01cYaQMNc167LOAkIZ0iMVUKBoOVpUHq6w/ZYmIQBTj5bgu/+x0UklhC9NBjhc07 4UoX7DlsnKfvPfybnfZ4mzyKdO9q6k7A5C0YsqiRbxYmO56IY+iUxfwx9ByfkX6IT3Y1 YKjE3X1CHqtQR0f4TZQF3ZMNCGopD9ekhj9Oq0H8LsKileffZLZ2BPKFtLeIOrx+iuyI 5N+g==
MIME-Version: 1.0
X-Received: by 10.68.189.5 with SMTP id ge5mr7985018pbc.42.1382008483503; Thu, 17 Oct 2013 04:14:43 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Thu, 17 Oct 2013 04:14:43 -0700 (PDT)
In-Reply-To: <20131002214515.20697.31622.idtracker@ietfa.amsl.com>
References: <20131002214515.20697.31622.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 13:14:43 +0200
Message-ID: <CADnDZ88_kszW0hfhf8XGNhVFVzzKv2KOp=RJ3mVVVmi3YGKPqA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) 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, 17 Oct 2013 11:14:45 -0000

Reviewer: Abdussalam Baryun (AB)
I-D name: draft-ietf-mpls-tp-rosetta-stone-12
Date: 17.10.2013
Reply to IETF LC message dated 02.10.2013
+++++++++++++++++++++++++++++++++

Overall Review:
The reviewer decision is that the I-D is not ready to be publish
because it does not achieve clearly its aim and objectives and subject
to additional information and structure. This thesaurus is difficult
to trace and gather information related to MPLS, even though it is
informational draft. This draft's terminology section is not done in a
methodology similar to RFC4397 in terms of showing separate resources
in each subsection and relating to the document aim. The title seems
like the terminology of both documentations are made as thesaurus, but
when we go into the I-D the reviewer feels it is not organised as a
thesaurus to simplify search and relating terms or issues of MPLS-TP.
There are many terminology not clear but more general definition. I
prefer specific defining to clarify to ALL Internet-Community not only
specific readers (otherwise should mention that it is not for ALL
community to understand). Also many times refers to references to
define without mentioning what was that definition, is that defined
only in ITU? is there an agreement that some one defines parts and
other org defines other parts? why IETF draft cannot define its
technology developed MPLS-TP? or is this draft agreeing on a joint
definitions of many documents without clear methodology or IETF is
just following ITU in some terms? The answers to these questions are
very important to make the thesaurus easy to trace.

Draft methodology of definition and terminology:
The way the draft starts a definition should not be refering to a
reference, this makes the reader leave the document and distracted,
and does not know where to go which page in such reference. In ITU-T
documents we find more organised which it defines and then refers to
the location of such definition but not the page which the reviewer
prefers in such situation. Therefore, it is better for an IETF
partcipant to understand the context and even get thesaurus-of-terms
when going through the some ITU-T documents (e.g. ITU-T G.8101/Y1355
(10/12) ) better than this ietf-draft, which means the IESG needs to
compare between this draft and ITU-T way of representing terms and
defining them, to make a better draft representation facing other
organisations, otherwise, people stop using this draft in future.

AB>Question to authors>
Who is the reader: is this document only designed for IETF familiar
RFCs readers or if someone from ITU refered by one document wants to
read this doc could he/she understand? (please note that ITU does
refer people to this draft as this draft is defining some terms and
they acknowledge).
In the reviewer's opinion it should mention this issue or who can read
or what are the documents that should be read, because it was
mentioned that this I-D is for IETF to get the ITU context.

I-D> Scope and Applicability:
++++++++++++++++++++
AB> The scope is not clear because in the draft says:-

I-D>page 2> in Abstract>
This document provides a thesaurus for the interpretation of MPLS-TP
terminology within the context of the ITU-T Transport Network
recommendations.

I-D>page 4> in Introduction>
This document provides a thesaurus for the interpretation of ITU-T
Transport Network terminology within the context of the MPLS-TP.

I-D>page 17> Section 4>
As discussed in the introduction to this document, this thesaurus is
intended to bring the concepts and terms associated with MPLS-TP
into the context of the ITU-T=92s Transport Network architecture.

AB> The above objectives are not consistent scoped or not explained
how and which context and terms are related and interpreted. The
methodology of doing both is not clear, or even how they relate within
the draft. The reviewer thinks there may be an editorial mistake, but
still the scope was confused by that because terms were referenced to
both RFCs and ITU-Gs.

AB> suggest adding> The motivation of the scope is nice to mention as
done in RFC4397. However, it is easier to write scope/motivation of
RFC4397 but not this draft because we want our participants to be
familiar with other organisation's documents or concepts. I hope we
don't loose our participants to go work for ITU and stop participating
in our IETF :-)

I-D> page 4> This document provides a thesaurus for the interpretation of I=
TU-T
Transport Network terminology within the context of the MPLS-TP.
This allows MPLS-TP documents to be generally understood by those
familiar with MPLS RFCs.
AB>not clear why it allows understanding> the reviewer thinks that the
draft's thesaurus does show pointers to ITU documents but does not
deliver the specific definitions of thoes terminologies within the ITU
nor within Transport Network context.

AB> to strengthen the scope of the draft to make both ITU and IETF
participant work on similar terminologies> Add info:
In past ITU-T developed extensions to MPLS developed by IETF to
address the requirements of the transport network (T-MPLS). However,
concerns were raised by the IETF that the approach taken by the ITU-T
was incompatible with widely deployed - MPLS - technology. Now both
ITU and IETF have work together to set a next generation transport
network technologies compatible with MPLS-TP.

AB> Question> Is there a discussion with the ITU Group responsible
about defining terms, because in one document of theirs they mention
something like some terms listed defined by IETF and some listed
defined by ITU-T? (yes it is mentioned in acknowledgement about ITU
and designe team, but not reflected or shown in the document scope).
Why is there different in concepts between MPLS-TP and the ITU
Transport Network, if the MPLS-TP was developed to facilitate
technologies within ITU transport Network context?

AB> Questions> Are the ITU documents under normative referencing the
last documents as up to date? and what are the affects of amendment of
ITU documents are they like our RFCs. Therefore, the reviewer request
all normative to be in force documents and  including any amendments
if related to this I-D.

AB> suggest> Some documents of amendments are related but not
referenced, such as amendments to ITU-T G.8101/Y1355 as [ITU-T
G.8101/Y1355 (10/12)] in 2012. Please consider adding and refering to
it.


I-D> Introduction Section>
+++++++++++++++++++
I-D>Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
   developed by the IETF to facilitate the Operation, Administration
   and Management of Label Switched Paths (LSPs) in a Transport Network
   environment as defined by the ITU-T.

AB> the MPLS-TP is defined by IETF not by ITU-T, so prefer to make it
clear in the paragraph. It can be understood: the IETF developed it as
defined by ITU-T.

AB> amend to:
Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
   developed and defined by the IETF to facilitate the Operation, Administr=
ation
   and Management of Label Switched Paths (LSPs) for interoperability
in a Transport Network environment as defined by the ITU-T.

AB> please add>
MPLS-TP is a connection-oriented packet-switched transport layer
network technology, is a profile of the MPLS that supports deployment
in transport networks and allows operations in a manner consistent
with other transport technologies.

AB> add> please mention that this definition of MPLS-TP by IETF will
allow consistent with other transport technologies defined by ITU-T.

AB>In Section 1.2> please explain or add info:
In the document there are many abbreviations as CC, CE, ME, etc., but
not mentioned if these abbreviations are used in ITU-T as a common
abbreviation or are not, the IETF participant would like to know such
information in this thesaurus. Also the section prefered to say this
is the documents abbreviation (e.g. wondering why some have abbrv and
others have not within the thesaurus).

Why authors used CC why not CCh as in other RFC? or does the CC has
been used in the ITU? please clarify why.

AB> suggest> CC to be changed to MPLS-TP Comm Channel (MTCC) and also
all others related terms.

AB> some words are not clear related to terminologies and MPLS and ITU
concepts. As there are words not defined but abbreviated as: Network
Element (NE). Other words not defined as : Channel, path, point,
connection, .etc. The reviewer wants to know it under the context of
MPLS-TP and Transport Network concept as the draft aims to do but not
found by reviewer.

In ITU documents in abbreviation section, it mentions as this
recommendation abbreviation, this draft needs to mention that this is
its abbreviation as well.

Please refer to below editor abbreviation in section 2:
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

The draft makes in its first page an abbreviation of IETF even though
it is mentioned in the webpage above of RFC editor.

AB>no consistency> The ITU-T has no abbreviation but still document
mentions the IETF abbreviation while the IETF is our organisation and
ITU is not and both are in RFC editor as no need abbreviation. Also
MPLS is similar abbreviated in the document and the editor signals it
as known, but in document mentioned more than one time. The ITU
documents mentions the ITU abbreviation.

I-D>Page 1>
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF)

AB> the document uses the word * see * to refer to document that has
the definition, but not refers to pages that has the definition. I
prefer not to refer, because this is a thesaurus so it is better to
explain with words and refer in the end of sentence as for example
pointing page in ref as [ITU-T_G.806, p4].

I-D> Section 2> Terminology:
++++++++++++++++++++
AB>Discuss>
Section 2 needs an introduction, the reader does not know what is the
document terminology, we have two organisations IETF and ITU, two
sources of terminology and concepts that this document is considering
but it seems that is not clear mentioned in the section in details.
For example, Is the terms in the thesaurus taken from ITU documents or
from IETF? or both? and then are they defined in the context of ITU-T
or of Transport Network?

AB> the sections 2.1 and 2.2 has references that are repeated in 2-3
which is confusing because it was thought that these sections show
distinction where references are for MPLS-TP terms and others for  ITU
and others references having common terms. Please clarify and
rephrase.

I-D>Section 3> Thesaurus:
++++++++++++++++++

AB>The section needs an introduction to explain these terms and their
relationships, I get confused when I see a thesaurus terms without
good relationship based on a model or methodology. It seems that the
draft is more referencing where are definitions than giving a clear
thesaurus and guidance/interpretation.

The concept of Transport Network should be defined, and also the
MPLS-TP concept.

The Network Elements are defined in ITU with deep specification but in
this draft seems general, also in ITU-T it related NE as in concept
MPLS-TP Network Element (MT.NE), why this is not reflected in this
draft.

This I-D's name is mentioned in the reference [ITU-T G.8101/Y1355
(10/12)], and that ITU reference is not mentioned in this I-D, why.
The [ITU-T G.8101/Y1355 (10/12)] explains better than this I-D that
there are definitions defined in this I-D and there are definition
defined by ITU documents and they list them all. Why does this I-D not
explain in similar clarifications to readers to distinguish and avoid
conflict in understandnings.

I-D> 3.1  Associated bidirectional path:
AB>Question> how can a path defined as a path without mentioning its
between what and through what? this is not specific definition, but
general, or too general.

I-D> 3.2 Bidirectional path:
AB>Question> how can a path defined as a path without mentioning its
between what and through what? this is not specific definition, but
general, or too general.
How does it differ from the 3.1 definition?

I-D> 3.3 Client layer network:
AB> it is a network but not defined under the MPLS-TP concept, to show
what is these layers or layer-network, and not distinguished from the
server layer network, please clarify.

I-D> 3.4 Communication Channel
AB> what is this channel? it cannot be defined as a path, as you say
between NEs, the reviewer thinks a channel is bandwidth of the
communication path. You must relate the channel to the path or paths
and connections, etc. This section is very poor in information
delivering.

I-D>3.6 Control Plane:
AB> not defined, and the reviewer though we are looking into MPLS-TP
under ITU-T context not the scope of RFC5654, please rephrase.

AB> In general> The above are examples of confusion not all
confusions. In the opinion of the reviewer that the definitions and
thesaurus is week represented to easily find the specific definition
related to draft objectives.

****Nits*****

AB> Question> the I-D uses words differently *end point* and
*endpoint* why? please amend to consistentancy. Relate it in the draft
interpretation to *connection point*, and/or NEs.

I-D> customer=92s (individual or bundled)
AB> amend to : customer=92s (i.e. individual or bundled)

AB> RFC3031 wrong title and not complete authors>amend reference in
sec 9.1 to:

[RFC3031]  Rosen, E., Viswanathan, A., and Callon, R., "Multiprotocol
Label Switching Architecture", January, 2000.

AB> RFC5654 not complete authors>amend reference in sec 9.1 to:

[RFC5645]  Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
and Ueno, S., "Requirements of an MPLS Transport Profile", September,
2009.

AB> RFC5860 not in order authors and title not same>amend reference in
sec 9.1 to:

[RFC5860] Vigoureux, M., Ward, D., and Betts, M., "Requirements for
Operations, Administration, and Maintenance (OAM) in MPLS Transport
Networks", May, 2010.

AB> RFC5860 not complete authors>amend reference in sec 9.1 to:

[RFC5921] Bocci, M., Frost, D., Bryant, S., Levrau, L., and Berger,
L., "A Framework for MPLS in Transport Networks", July, 2010.

AB> RFC5951 not complete authors and wrong title>amend reference in
sec 9.1 to:

[RFC5951] Lam, K., Gray, E., and Mansfield, S., "Network Management
Requirements for MPLS-based Transport Networks", September 2010.

++++++++++  The End ++++++++++

Sorry for the delay,

Best Regards
AB

On 10/2/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'A Thesaurus for the Terminology used in Multiprotocol Label Switching
>    Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport
>    Network Recommendations.'
>   <draft-ietf-mpls-tp-rosetta-stone-12.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-10-16. 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
>
>    MPLS-TP is based on a profile of the MPLS and PW procedures as
>    specified in the MPLS-TE and (MS-)PW architectures developed by the
>    IETF.  The ITU-T has specified a Transport Network architecture.
>
>    This document provides a thesaurus for the interpretation of MPLS-TP
>    terminology within the context of the ITU-T Transport Network
>    recommendations.
>
>    It is important to note that MPLS-TP is applicable in a wider set of
>    contexts than just Transport Networks.  The definitions presented in
>    this document do not provide exclusive nor complete interpretations
>    of MPLS-TP concepts.  This document simply allows the MPLS-TP terms
>    to be applied within the Transport Network context.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-rosetta-stone/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-rosetta-stone/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>

From jari.arkko@piuha.net  Thu Oct 17 06:03:27 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 461C621F9A8C for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:03:27 -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 Dy5ZYBLor8wH for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:03:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7139211E81C0 for <ietf@ietf.org>; Thu, 17 Oct 2013 06:03:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C79842CCC1; Thu, 17 Oct 2013 16:03:12 +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 q02wc185MtKc; Thu, 17 Oct 2013 16:03:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 234842CC48; Thu, 17 Oct 2013 16:03:12 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-kolkman-proposed-standards-clarified-03.txt> (Characterization of Proposed Standards) to Best Current Practice
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CBFBF6D6-5984-4564-9123-AE14405DB80D@NLnetLabs.nl>
Date: Thu, 17 Oct 2013 16:03:12 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B80AE246-25AE-4E69-AF5E-ADA4F65DB308@piuha.net>
References: <20130918181807.14400.46970.idtracker@ietfa.amsl.com> <5242BE97.7030501@cisco.com> <CBFBF6D6-5984-4564-9123-AE14405DB80D@NLnetLabs.nl>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
X-Mailer: Apple Mail (2.1510)
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, 17 Oct 2013 13:03:27 -0000

Based on the discussion, I believe the draft is ready to move forward. I =
will take it to the next IESG telechat for approval and/or discussion.

Olaf says that he has accumulated a few corrections from the discussion =
that he will post as -04 soon.

Jari


From arturo.servin@gmail.com  Thu Oct 17 06:23:18 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 EC6F111E818F for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:23:17 -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 liDVG0KdQZT4 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:23:17 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5D05621F9FA4 for <ietf@ietf.org>; Thu, 17 Oct 2013 06:23:17 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id v1so530811yhn.16 for <ietf@ietf.org>; Thu, 17 Oct 2013 06:23:16 -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=AB060OTPaKLP09JLj8kDa/B3AY7a3FcYH4xd61oMYDE=; b=MN9ENJPMLI7TYyXny/JLRNsl8LeVr7ZmJqslUkxKUk0F4w9UiLNWl9PyqEx5f3GKrW ft74sI9isQpclaBD1XXx6BraPheKBNDZQiAcxVl9jZq8VbOTFINT4aARcX3cmT1eD+Yt 0E/83ev6pWQxyCBzu7ooYgCFvhKT+edKSNHGR0goorvKYv+pkGdadWucfvARIIdQh8Ev rrqHgr4xBzwHe3pT+8bIe9M9nniXMAhzlBahxT2gw/nP8LKr4sy4fIOrKzmkZA2o1I6U 4KUAZ4ZZZ7CTpPdxHJtN9UHr39Hv4B7uRKZTCn5+E7/EePHKihkTeLz1ifXxlH3LlPPe Tl/Q==
X-Received: by 10.236.90.114 with SMTP id d78mr862984yhf.94.1382016196579; Thu, 17 Oct 2013 06:23:16 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([200.7.87.33]) by mx.google.com with ESMTPSA id o27sm46248261yhb.19.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 06:23:15 -0700 (PDT)
Message-ID: <525FE4C5.2000902@gmail.com>
Date: Thu, 17 Oct 2013 11:23:17 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>, ietf@ietf.org
Subject: Re: Improving the ISOC Fellowship programme to attract people from under-represented regions into the IETF
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <525F33B2.3070506@gmail.com>
In-Reply-To: <525F33B2.3070506@gmail.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, 17 Oct 2013 13:23:18 -0000

	I suggested the change in the DT-list because I think that the draft
was to focused in the ISOC program to give a clear guidance in how to
attract more people to the IETF.

	In order to provide a broader guiadance we need to consider much more
things that are not yet in the draft. Also, some sections would need to
be re-written.

/as

On 10/16/13 10:47 PM, Alejandro Acosta wrote:
> Hello,
>   I just read the new version of the draft, it's nice to see that most
> suggestion/comments were added to the draft.
>   First, I would like to say I do support your draft.
>   Second, I noticed you changed the title of your draft from:
>   "Improving the ISOC Fellowship programme to Attracting people from
> under-represented regions into
> the IETF"
> 
>   to
> 
>   "Improving the ISOC Fellowship programme to attract people from
> under-represented regions into the IETF"
> 
>   IMHO opinion -and not being native English speaker- you improved it a
> little bit but I think the previous comments suggested even something
> more generic, like just improving the ISOC fellowship programme and not
> only "attack" people to the IETF. I mean, it's very true you mention
> several other things in your draft besides attracting people.
> 
> 
> Thanks,
> 
> Alejandro,
> 
> 
> 
> On 10/10/13 13:40, S Moonesamy wrote:
>> Hi Jari,
>>
>> Here's is a draft about improving the ISOC Fellowship programme to
>> attract people from under-represented regions into the IETF.  The draft
>> builds upon the ISOC work, proposing adjustments and additional efforts,
>> with the goal of enabling more sustained and active participation by
>> contributors from under-represented regions.
>>
>> In a blog article ( http://www.ietf.org/blog/2013/04/diversity/ ), it is
>> mentioned that:
>>
>>  "The design team will present their recommendations to the community,
>>   and engage in the discussion.  Recommendations with community support
>>   will be taken forward."
>>
>> The draft only makes suggestions instead of recommendations.  I am
>> copying this message to ietf@ietf.org so that the community can comment
>> about the draft.
>>
>> Regards,
>> S. Moonesamy

From Fred.L.Templin@boeing.com  Thu Oct 17 06:44:20 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2190621F93E4; Thu, 17 Oct 2013 06:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 6nOgeNDZUx4x; Thu, 17 Oct 2013 06:44:13 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9B96921F88BA; Thu, 17 Oct 2013 06:44:13 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r9HDiCj9022493; Thu, 17 Oct 2013 06:44:13 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r9HDiB5o022485 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 17 Oct 2013 06:44:11 -0700
Received: from XCH-EXCO-102.nw.nos.boeing.com (130.247.25.34) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 17 Oct 2013 06:44:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.85]) by XCH-EXCO-102.nw.nos.boeing.com ([fe80::452:98ce:3aa6:3fe9%15]) with mapi id 14.03.0158.001; Thu, 17 Oct 2013 06:44:10 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-6man-oversized-header-chain-08.txt> (Implications of Oversized IPv6 Header Chains) to Proposed Standard
Thread-Index: AQHOypHQJAvRrWBwLEyOc1cqWuOOX5n3j5QAgAFTCZA=
Date: Thu, 17 Oct 2013 13:44:09 +0000
Message-ID: <2134F8430051B64F815C691A62D98318131522@XCH-BLV-504.nw.nos.boeing.com>
References: <20131002185522.20697.96027.idtracker@ietfa.amsl.com> <2134F8430051B64F815C691A62D9831811EB23@XCH-BLV-504.nw.nos.boeing.com> <D1F5CE61-253E-4F07-AED1-4A4AB4C4AB68@employees.org> <2134F8430051B64F815C691A62D9831811EE66@XCH-BLV-504.nw.nos.boeing.com> <E29381FD-C839-4DBA-8711-3A4EBA83E379@employees.org> <2134F8430051B64F815C691A62D9831811EF1C@XCH-BLV-504.nw.nos.boeing.com> <5255D6EE.4050300@gmail.com> <2134F8430051B64F815C691A62D9831811F688@XCH-BLV-504.nw.nos.boeing.com> <5257AD5E.9090806@globis.net>	<5257B870.1060003@si6networks.com> <2134F8430051B64F815C691A62D9831812C120@XCH-BLV-504.nw.nos.boeing.com> <52582F8B.8040306@si6networks.com>	<52585658.50205@gmail.com> <2134F8430051B64F815C691A62D9831812C654@XCH-BLV-504.nw.nos.boeing.com> <52587EB8.4020506@gmail.com> <f0df0113f68045a1bdadf0155eae5e34@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D9831812D72D@XCH-BLV-504.nw.nos.boeing.com> <525DD007.8030100@si6networks.com> <57E5A58E-0DAF-4545-8580-ACDB59475F46@employees.org> <2134F8430051B64F815C691A62D9831812F69E@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJ+-4SdUdoku_on0YX9rTHMPBJQ-Yz7e+Rbb_PoFt1+TjA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F8C5@XCH-BLV-504.nw.nos.boeing.com> <CAFQ9LJJVqV0q-br5wsSCpUgH=M1BXMitohExh7-MQhsWjVABJA@mail.gmail.com> <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831812F95C@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ray Hunter <v6ops@globis.net>, 6man Mailing List <ipv6@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, 17 Oct 2013 13:44:20 -0000

Hi Fernando,

I want to revisit a point that needs to be corrected:

> The point is that this is no worse than IPv4.

Why should it be as bad as IPv4 when it can be better? IPv4
middleboxes that wish to do deep packet inspection may need to
gather the fragments of a fragmented datagram before deciding
whether to let them pass through. IPv6 middleboxes shouldn't
have to do that, but they will if the host is permitted to
include MTU-sized header chains and there is a tunnel on the
path that has to fragment for whatever reason.

> And it is very likely
> that one of underlying encapsulations will be IPv4.

That is not necessarily true. Tunnels are used for many reasons
other than IPv6/IPv4 transition, including routing control,
mobility, traffic engineering, multihoming, security etc.
Tunnels will be part of the IPv6 architecture long after IPv4
has faded into the sunset, so let's get this right now so we
don't have to live with legacy behavior.

Thanks - Fred
fred.l.templin@boeing.com



From john@jck.com  Thu Oct 17 06:50:05 2013
Return-Path: <john@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 575AF11E8267 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:50:05 -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 zyl7g1A+zUrn for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 06:49:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5A69E11E8249 for <ietf@ietf.org>; Thu, 17 Oct 2013 06:49:58 -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@jck.com>) id 1VWnwv-000379-Gh; Thu, 17 Oct 2013 09:49:13 -0400
Date: Thu, 17 Oct 2013 09:49:08 -0400
From: John C Klensin <john@jck.com>
To: "Eggert, Lars" <lars@netapp.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Improving the ISOC Fellowship programme to attract people from	under-represented regions into the IETF
Message-ID: <24026E5EA57D50D4BC50D900@JcK-HP8200.jck.com>
In-Reply-To: <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@netapp.com>
References: <6.2.5.6.2.20131010103928.0c9ce568@elandnews.com> <E3A50792-0DBF-4B0E-9BDA-6C527C3074A9@netapp.com> , <CADnDZ88oGeimRdVjUPiB7pcyvFq4_DkgK+A7sDjheAOiz0AVog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408374274D58B@EXMB01CMS.surrey.ac.uk> <93389294-36BE-4B7D-9E3B-DEAE99B6833D@piuha.net> <36C6E1AA-A268-4AA7-AB48-0D23CD2BC202@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: SM <sm+ietf@elandsys.com>, "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, 17 Oct 2013 13:50:05 -0000

--On Friday, October 11, 2013 13:22 +0000 "Eggert, Lars"
<lars@netapp.com> wrote:

> Hi,
> 
> On Oct 11, 2013, at 14:43, Jari Arkko <jari.arkko@piuha.net>
> wrote:
>> I do have a question for Lars though. What are your opinions
>> on this? (You said that there is no consensus, but I'd like
>> to hear also your thoughts.)
> 
> so one key question is what influence the IETF actually has on
> an ISOC program. We can certainly state our wishes, but my
> belief is that it's ISOC's program in the end, and they can
> basically chose to run it as they see fit. That doesn't come
> out in the draft at all.

Yes.  But discussion of an I-D may help understand what the IETF
thinks would help.  Perhaps someone should propose a meeting in
Vancouver with the relevant ISOC people to exchange views about
their agenda and "ours".  Such discussions in the past (on a
completely informal, rather than "IETF position" basis, have
contributed to the evolution of the program to be more friendly
to people who are likely to actually do work in the IETF and to
some of the "returning fellows" arrangements.

> Another issue I have with the the draft is written with the
> implied understanding that the program should fund the
> repeated attendance of residents of under-represented regions
> who are actively participating in some sort of way. It's not
> clear to me that this is really what would be best in terms of
> increasing organizational diversity over time. I wouldn't want
> to fund the same people over and over; I'd much rather bring
> in new people all the time in the hopes of spreading the word
> about the IETF widely and hoping that some folks will end up
> in roles where they can occasionally attend on their own dime.

This is, to me, the essential tension in the program (or, now,
pair of programs that we often don't think of as separate).  One
can optimize it for any of at least three different categories:

(i) Bringing people in to see what the IETF is all about in the
hope that will be beneficial in other ways.  While there may be
happy exceptions, the assumption behind this category is that,
while people brought in this way may help with the IETF's role
in  various policy contexts, actual contributions to the IETF
are not expected.

(ii) Bringing people in with the hope they will participate in
and contribute to the IETF, but with no realistic expectation
that they will ever show up at a meeting again unless it it
local to them.  IMO, this is just wishful thinking unless we
really clean up our acts about remote participation, including
both full remote participation in training activities and
educational materials about IETF participation and procedures
tailored to remote participants, probably to the degree that
people who are almost entirely remote can realistically take on
leadership and WG editorial roles.  I don't believe it strikes
the right balance, but Subramanian's draft about Nomcom
participation identifies many of those issues. 

(iii) Bringing people in whom we expect to turn into active
participants, with some expectation of support for additional
meetings when that is appropriate for some reason.  If nothing
else, it is at least somewhat more realistic in the absence of
significant changes in the IETF to make it much more remote
participant-friendly (and less dependent on personal
relationships and hallway chats).

The current draft seems to be mostly focused on extending and
enhancing the third category.  I don't see it as addressing, or
calling for the elimination of, the other two.

> I'd like to be able to bring in other under-represented groups
> (students, academics, women, etc.) We can certainly have a
> discussion about what is best; my point is that the draft has
> already decided that one approach is the way to go.

Although I think the draft would benefit from clarification, I
read it differently, as noted above.  Of course, one of the
questions becomes resources -- both budgetary and mentoring and
other types of education and support.  Given that they are not
unlimited, there may ultimately have to be choices between
bringing in more likely participants and bringing in a wider
range of people to look around and understand what we do,
perhaps with the possibility that they might show up at
convenient subsequent meetings on other funding.

By the way, while I've never actively participated in an IRTF
RG, I suspect that effective mostly-remote participation there
would be a lot more practical than it is today in the IETF.

> I also have a few issues with the suggestions it makes:
> 
> Section 4.1 requires that an applicant needs to already have
> been a participant in the IETF. That seems excessive. For
> returning fellows, some sort of engagement in the IETF after a
> while would be nice, but I can see valid cases for supporting
> someone's repeated attendance who isn't contributing in a very
> visible role. Also, I question the possibility to quantify and
> compare someone's impact of IETF involvement. And again, there
> are others than "resident of a country in an under-represented
> region" who we might want to bring in, and we probably don't
> need to fund the attendance of employees of large vendors who
> happen to be residents of under-represented regions.
>...

I think that may generalize into "we have never been good at
developing over-specific rules that don't end up being
constraints when something obviously reasonable needs to be
done".

> But my main issue is that the draft sounds like its trying to
> take over and redefine an ISOC program, which I don't think
> the IETF can or should do. The ISOC program has a purpose, a
> history and at least from my perspective is working pretty
> well with the budget it has available. I'm not sure we can
> actually improve it much.

See above, even though we might disagree about the possibility
of improvements.

best,
     john


> 
> Lars





From nomcom-chair-2013@ietf.org  Thu Oct 17 07:09:15 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 5570E21F8BFD; Thu, 17 Oct 2013 07:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.747
X-Spam-Level: 
X-Spam-Status: No, score=-100.747 tagged_above=-999 required=5 tests=[AWL=-1.853, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dt7nAwNYvy2D; Thu, 17 Oct 2013 07:09:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7F321F9ED1; Thu, 17 Oct 2013 07:09:05 -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 - Time-Critical - Final Call for Nominations
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 07:09:05 -0700
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: Nomcom@ietfa.amsl.com, Chair@ietfa.amsl.com, "2013 <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, 17 Oct 2013 14:09:15 -0000

A critically low number of people have accepted nominations for some of the =

IESG open positions.  There is only one nominee per slot in APP, OPS and TS=
V, =

only two in INT and RAI.  Many folks have declined nominations.  =


While the Nomcom appreciates that support for two years of intense service =

is hard to assure, and while we are aware that there is much support for th=
e =

incumbents who are standing, the IETF should continually be considering
which new talent is available for our leadership, and the Nomcom process =

needs for there to be some review and deliberation. =


Therefore, we urgently request that more nominees come forward.  =


DEADLINES
Nominations - October 18 =

Questionnaires from nominees - October 25

Not coincidentally, this is a good time to think over and send your comment=
s =

about the current statements of desired expertise of positions - this is pa=
rt of =

the Nomcom's annual review process as well.  Send them to nomcom13@ietf.org.

Definitive location [*] of the current statements on desired expertise:
      https://datatracker.ietf.org/nomcom/2013/expertise/

Instructions and details on nomination [**]:
      https://datatracker.ietf.org/ann/nomcom/60602/

Thanks, everyone,

Allison for the Nomcom

[*] This year the Nomcom tools were recoded, and also transitioned into the =

datatracker.  Apologies for a number of places where we didn't catch refere=
nce =

errors.

[**] Yes, alas, the previous call for nominations used "OAM" instead of "OP=
S," but =

we have* corrected this (chair's pilot) error where it occurred in the Nomc=
om =

pages.

From nomcom-chair-2013@ietf.org  Thu Oct 17 07:24:48 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 CC87021F992B; Thu, 17 Oct 2013 07:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.821
X-Spam-Level: 
X-Spam-Status: No, score=-99.821 tagged_above=-999 required=5 tests=[AWL=-0.927, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0S2lXTnHSe1h; Thu, 17 Oct 2013 07:24:47 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A979A21F994A; Thu, 17 Oct 2013 07:24:34 -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 - Critical shortage of nominees for multiple areas
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131017142434.21877.63746.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 07:24:34 -0700
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: Nomcom@ietfa.amsl.com, Chair@ietfa.amsl.com, "2013 <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, 17 Oct 2013 14:24:48 -0000

[Catchier Subject line - apologies to those offended by a duplicate]

A critically low number of people have accepted nominations for some of the =

IESG open positions.  There is only one nominee per slot in APP, OPS and TS=
V, =

only two in INT and RAI.  Many folks have declined nominations.  =


While the Nomcom appreciates that support for two years of intense service =

is hard to assure, and while we are aware that there is much support for th=
e =

incumbents who are standing, the IETF should continually be considering
which new talent is available for our leadership, and the Nomcom process =

needs for there to be some review and deliberation. =


Therefore, we urgently request that more nominees come forward.  =


DEADLINES
Nominations - October 18 =

Questionnaires from nominees - October 25

Not coincidentally, this is a good time to think over and send your comment=
s =

about the current statements of desired expertise of positions - this is pa=
rt of =

the Nomcom's annual review process as well.  Send them to nomcom13@ietf.org.

Definitive location [*] of the current statements on desired expertise:
      https://datatracker.ietf.org/nomcom/2013/expertise/

Instructions and details on nomination [**]:
      https://datatracker.ietf.org/ann/nomcom/60602/

Thanks, everyone,

Allison for the Nomcom

[*] This year the Nomcom tools were recoded, and also transitioned into the =

datatracker.  Apologies for a number of places where we didn't catch refere=
nce =

errors.

[**] Yes, alas, the previous call for nominations used "OAM" instead of "OP=
S," but =

we have* corrected this (chair's pilot) error where it occurred in the Nomc=
om =

pages.

From tjc@ecs.soton.ac.uk  Thu Oct 17 07:54:23 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 2706D11E8242 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 07:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.214
X-Spam-Level: 
X-Spam-Status: No, score=-2.214 tagged_above=-999 required=5 tests=[AWL=0.385,  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 PeX0bkuxLlkZ for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 07:54:21 -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 DE03D11E80F9 for <ietf@ietf.org>; Thu, 17 Oct 2013 07:54:15 -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 r9HEsEle008919 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:54:14 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9HEsEle008919
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382021654; bh=RRiGeCGmIpJDeoLaw3cAq4wOV30=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=PRc1b/rKNe2Bkr0i+Yndu0ip682fhMlfjYC1jih1S/OPe+RVpmuynU9/7ksuTG7+F mBFPPYXYSXh7pTjibWv865VyXWQ0Snf9eSFvGOE6WRt8Ew1v4aEatpmbObyZ8MSyU4 7dY2sjQ9oQQ8iwvo2vYWTRs9ut0wC8fu1d6H2tBQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9GFsE0959634668jE ret-id none; Thu, 17 Oct 2013 15:54:14 +0100
Received: from dhcp-23-145.wireless.soton.ac.uk (dhcp-23-145.wireless.soton.ac.uk [152.78.23.145] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9HEsCck021568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 17 Oct 2013 15:54:12 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>
Date: Thu, 17 Oct 2013 15:54:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
To: IETF Discuss <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9GFsE095963466800; tid=p9GFsE0959634668jE; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9HEsEle008919
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: Thu, 17 Oct 2013 14:54:23 -0000

Hi,

On 17 Oct 2013, at 15:09, NomCom Chair 2013 <nomcom-chair-2013@ietf.org> =
wrote:

> A critically low number of people have accepted nominations for some =
of the=20
> IESG open positions.  There is only one nominee per slot in APP, OPS =
and TSV,=20
> only two in INT and RAI.  Many folks have declined nominations. =20
>=20
> While the Nomcom appreciates that support for two years of intense =
service=20
> is hard to assure, and while we are aware that there is much support =
for the=20
> incumbents who are standing, the IETF should continually be =
considering
> which new talent is available for our leadership, and the Nomcom =
process=20
> needs for there to be some review and deliberation.=20

I believe the "intense service" you mention is a significant deterrent =
for many.

I'm sure it's been suggested before, but is there mileage in rethinking =
the=20
AD roles, and either the number of ADs per area, or whether introducing=20=

Assistant ADs or similar might allow people who can contribute less time =
to=20
do so, while easing the burden on the main ADs?

Just a thought anyway. Personally, I'd assume that some people would be=20=

more willing to help if deemed to have the skills required, but the time=20=

constraints are, as many ADs will confirm if you chat with them, the =
blocking
factor.

Tim=

From cmasango@unog.ch  Wed Oct 16 18:29:48 2013
Return-Path: <cmasango@unog.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330CA11E8211 for <ietf@ietfa.amsl.com>; Wed, 16 Oct 2013 18:29:48 -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 XPwyuEsya6tn for <ietf@ietfa.amsl.com>; Wed, 16 Oct 2013 18:29:27 -0700 (PDT)
Received: from michigan.vervehosting.com (michigan.vervehosting.com [209.212.145.163]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5FB11E81B0 for <ietf@ietf.org>; Wed, 16 Oct 2013 18:29:24 -0700 (PDT)
Received: from [36.87.0.25] (port=53163) by michigan.vervehosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <cmasango@unog.ch>) id 1VWcOv-0006Mb-7s for ietf@ietf.org; Wed, 16 Oct 2013 21:29:22 -0400
From: Chengetai Masango <cmasango@unog.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Opening session
Message-Id: <CE1EEDDF-F172-44B2-AD03-2CBD3B3B5948@unog.ch>
Date: Thu, 17 Oct 2013 09:28:51 +0800
To: ietf@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - michigan.vervehosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - unog.ch
X-Get-Message-Sender-Via: michigan.vervehosting.com: authenticated_id: igfunogmail+masango.net/only user confirmed/virtual account not confirmed
X-Mailman-Approved-At: Thu, 17 Oct 2013 08:16:58 -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, 17 Oct 2013 01:29:48 -0000

Hei Jari,

Will you be able to give a 5 min speech at the IGF opening session ?

Best regards,

Chengetai 



From john-ietf@jck.com  Thu Oct 17 08:51:57 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 854E111E8285 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 08:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level: 
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 tGh6walDExSr for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 08:51:51 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E5B4C11E8244 for <ietf@ietf.org>; Thu, 17 Oct 2013 08:51:41 -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 1VWprM-0003EY-UZ; Thu, 17 Oct 2013 11:51:36 -0400
Date: Thu, 17 Oct 2013 11:51:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
Message-ID: <FDDC3EF96422A0625A822E07@JcK-HP8200.jck.com>
In-Reply-To: <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
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, 17 Oct 2013 15:51:57 -0000

--On Thursday, October 17, 2013 15:54 +0100 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

> Hi,
> 
> On 17 Oct 2013, at 15:09, NomCom Chair 2013
> <nomcom-chair-2013@ietf.org> wrote:
> 
>> A critically low number of people have accepted nominations
>> for some of the  IESG open positions.  There is only one
>> nominee per slot in APP, OPS and TSV,  only two in INT and
>> RAI.  Many folks have declined nominations.  
>> 
>> While the Nomcom appreciates that support for two years of
>> intense service  is hard to assure, and while we are aware
>> that there is much support for the  incumbents who are
>> standing, the IETF should continually be considering which
>> new talent is available for our leadership, and the Nomcom
>> process  needs for there to be some review and deliberation. 
> 
> I believe the "intense service" you mention is a significant
> deterrent for many.
> 
> I'm sure it's been suggested before, but is there mileage in
> rethinking the  AD roles, and either the number of ADs per
> area, or whether introducing  Assistant ADs or similar might
> allow people who can contribute less time to  do so, while
> easing the burden on the main ADs?

You could add the economic costs to the time costs on that list.
Worse, unless something intervenes or one really hates the job,
it is really a four year commitment if only because it takes a
year or more to really settle into the job and leaving after two
years feels like a bad return on that investment (to both the AD
and the community).

> Just a thought anyway. Personally, I'd assume that some people
> would be  more willing to help if deemed to have the skills
> required, but the time  constraints are, as many ADs will
> confirm if you chat with them, the blocking factor.

A few observations, fwiw...

(1) The time and resource commitment required of ADs is largely,
but not entirely, of the IESG's own making.  People get selected
who have the time and resources and the job and/or perception of
things for which IESG members need to take personal
responsibility tend to expand to more than fill the available
time.  I've given the opinion to a number of Nomcoms that the
problem will just get worse unless they select people who see
that expansion of the role as a problem and have plans for how
to fix it (or at least a good-faith intent to support such
plans).   My impression is that it hasn't ranked high in Nomcom
priorities so, if it is important to others, more people need to
say it.

At the same time, it is hard to blame the IESG for a lot of the
problem.  The community has not been supportive of efforts to
push back on formation of WGs nor of shutting down ones that are
unproductive or that cannot reach reasonable levels of consensus
about their work.  The "chief representative of the IETF
community to external communities" has shifted from the IAB
Chair to the IETF one.  Whether that is a good thing or a bad
one, it inevitably means that more of the consultation burden
falls on IESG members, increasing workload.   Many documents
reach IETF Last Call and get almost no comments, so we expect
IESG members to be responsible for doing the evaluations (or
evaluations of "area reports" from people who may not know the
technology being proposed) themselves.  Perhaps we should be
firing ADs for letting those documents go into Last Call in the
first place but, unless we are going to cut off the WG that
produce them, it is hard to believe that would be sensible (even
if there were lots of spare candidates).

(2) The Nomcom doesn't have a lot of control in this space.  The
number of ADs per area is set by the IESG, not the Nomcom, and
the Nomcom has little choice other that to try to fill the
positions (there have been debates over the years as to whether
a Nomcom could actually refuse to fill a position but certainly
it should not consider trying except in the most dire of
circumstances).  ADs have tremendous flexibility about how they
manage their areas and several of your suggestions could be
adopted unilaterally by a sitting AD (or the ADs in one area)
with no formal community or even IESG approval needed.  If it is
important enough, we could tell Nomcoms to start firing (or
refusing to appoint) ADs who don't show good management and
delegation skills but, if we did that any they listened, they
might have to prioritize management skills over technical skills
and understanding and it is possible that wouldn't work out well
(and would give us even more professional standardizers and
process folks rather than technical experts who are willing and
able to devote a few years to community service on the IESG).

In other words, while I mostly agree with you, it is too late
for most of the issues and remedies by the time the Nomcom
issues a call for Nominations.

just my (very jaded) opinion.
    john



From dave@cridland.net  Thu Oct 17 09:04:21 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 7437411E8283 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:04:17 -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=[AWL=-0.000, 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 7rfLqIcczTH7 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:04:14 -0700 (PDT)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id ECA4B11E827B for <ietf@ietf.org>; Thu, 17 Oct 2013 09:02:48 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id ec20so2047609lab.14 for <ietf@ietf.org>; Thu, 17 Oct 2013 09:02:45 -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=eTlTcXrQ6a8GJ5u916Zj4n+AEBAxDJ5ZFlTiwcnE5Cs=; b=FFQDVNIYjiksRVi0ye4l3pHrRduIiZvxgTqNgh+XCQfO0epaYjWjH+5VEnMB/CuWDu 0jlLjUNfjHBBNzUCj9Q0jwmliDYc6bYSqeNjcQOyR3pLmsLo5Zdnvf4X98rUWvIfTFRd OrwSazFrb9mGpKe/kQYRjHsfS0V20DbemtspM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=eTlTcXrQ6a8GJ5u916Zj4n+AEBAxDJ5ZFlTiwcnE5Cs=; b=d5rmWBTJ9JE/SazIqlfXaX1j6wS8VCxfkU201pyL/UkKEcOzKvPoFjSoUMQOfYZh1n lEY7V0meBFBGrKDXLEFWMIYYLpB/inAdfJkfOtwNXq8AVu2QhSgyBP6ydqXljIYOsLvt e6HOpQlXCs1AY8QT+I5vCQCPT6gMKUOU7ayLyZvQk/v2gfHRTPj9nLf5ByasJG3O75yQ 2BsJJouxZvwdjAMc2HYOfzYGEjPGm8a4GkTglRG1ZflAgzW8GAY2iGSMb5fB2UfqKaNx ln15OWNVPuWjfmB3r6SaV1s0aW9gbu58Wr1lXB1VeHpZCIrdKagADBv1OZ/8lSzx86Ly dYnA==
X-Gm-Message-State: ALoCoQkvWp3bablxZiWyykbqnq1fKqFRNEu8Z1iAwwlVBTvWjEr8IoD4r1ASWhJyufFtw2hfd1RJ
MIME-Version: 1.0
X-Received: by 10.112.210.197 with SMTP id mw5mr2223900lbc.42.1382025765514; Thu, 17 Oct 2013 09:02:45 -0700 (PDT)
Received: by 10.114.183.47 with HTTP; Thu, 17 Oct 2013 09:02:45 -0700 (PDT)
In-Reply-To: <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
Date: Thu, 17 Oct 2013 17:02:45 +0100
Message-ID: <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Dave Cridland <dave@cridland.net>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c3c7dcd2fa4c04e8f1f252
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 16:04:21 -0000

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

On Thu, Oct 17, 2013 at 3:54 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> I believe the "intense service" you mention is a significant deterrent for
> many.
>
> I'm sure it's been suggested before, but is there mileage in rethinking the
> AD roles, and either the number of ADs per area, or whether introducing
> Assistant ADs or similar might allow people who can contribute less time to
> do so, while easing the burden on the main ADs?
>
> Just a thought anyway. Personally, I'd assume that some people would be
> more willing to help if deemed to have the skills required, but the time
> constraints are, as many ADs will confirm if you chat with them, the
> blocking
> factor.
>

I think the blocking factor may be primarily a financial one.

I'd like to nominate one person, but I know that as they are self-employed
as a consultant, they would forfeit essentially all income in order to
satisfy the time demands. Indeed that's more or less what they said to me.

The only solution allowing independents to become an AD that I can see
would be for larger companies to partially or wholly sponsor slots and/or
particular individuals. If this were to happen, I think we'd get both more,
and more diverse, nominations; but I appreciate that like John's
suggestions, mine is unlikely to solve the problem this time around.

Dave.

--001a11c3c7dcd2fa4c04e8f1f252
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 Thu, Oct 17, 2013 at 3:54 PM, Tim Chown <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk<=
/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">I believe the &quot;intense service&quot; yo=
u mention is a significant deterrent for many.<br>
<br>
I&#39;m sure it&#39;s been suggested before, but is there mileage in rethin=
king the<br>
AD roles, and either the number of ADs per area, or whether introducing<br>
Assistant ADs or similar might allow people who can contribute less time to=
<br>
do so, while easing the burden on the main ADs?<br>
<br>
Just a thought anyway. Personally, I&#39;d assume that some people would be=
<br>
more willing to help if deemed to have the skills required, but the time<br=
>
constraints are, as many ADs will confirm if you chat with them, the blocki=
ng<br>
factor.<br>
<span class=3D"HOEnZb"></span></blockquote><div><br></div><div>I think the =
blocking factor may be primarily a financial one.<br><br></div><div>I&#39;d=
 like to nominate one person, but I know that as they are self-employed as =
a consultant, they would forfeit essentially all income in order to satisfy=
 the time demands. Indeed that&#39;s more or less what they said to me.<br>
<br></div><div>The only solution allowing independents to become an AD that=
 I can see would be for larger companies to partially or wholly sponsor slo=
ts and/or particular individuals. If this were to happen, I think we&#39;d =
get both more, and more diverse, nominations; but I appreciate that like Jo=
hn&#39;s suggestions, mine is unlikely to solve the problem this time aroun=
d.</div>
<div><br></div><div>Dave.<br></div></div></div></div>

--001a11c3c7dcd2fa4c04e8f1f252--

From joelja@bogus.com  Thu Oct 17 09:26:51 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 AC34411E8278 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:26: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 hcrIh3r0-ZSY for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:26:51 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E8E0111E827E for <ietf@ietf.org>; Thu, 17 Oct 2013 09:26:50 -0700 (PDT)
Received: from 03056a-kadolfo.corp.zynga.com ([72.5.115.169]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9HGQG3F014472 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 17 Oct 2013 16:26:16 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_E113D080-1164-4ECE-BD3A-6933DE0D11FE"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
Date: Thu, 17 Oct 2013 09:26:11 -0700
Message-Id: <F2FD96A5-F26F-481B-AC9C-7A2EE16DD665@bogus.com>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 17 Oct 2013 16:26:16 +0000 (UTC)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 16:26:51 -0000

--Apple-Mail=_E113D080-1164-4ECE-BD3A-6933DE0D11FE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 17, 2013, at 9:02 AM, Dave Cridland <dave@cridland.net> wrote:

>=20
>=20
>=20
> On Thu, Oct 17, 2013 at 3:54 PM, Tim Chown <tjc@ecs.soton.ac.uk> =
wrote:
> I believe the "intense service" you mention is a significant deterrent =
for many.
>=20
> I'm sure it's been suggested before, but is there mileage in =
rethinking the
> AD roles, and either the number of ADs per area, or whether =
introducing
> Assistant ADs or similar might allow people who can contribute less =
time to
> do so, while easing the burden on the main ADs?
>=20
> Just a thought anyway. Personally, I'd assume that some people would =
be
> more willing to help if deemed to have the skills required, but the =
time
> constraints are, as many ADs will confirm if you chat with them, the =
blocking
> factor.
>=20
> I think the blocking factor may be primarily a financial one.
>=20
> I'd like to nominate one person, but I know that as they are =
self-employed as a consultant, they would forfeit essentially all income =
in order to satisfy the time demands. Indeed that's more or less what =
they said to me.
>=20
> The only solution allowing independents to become an AD that I can see =
would be for larger companies to partially or wholly sponsor slots =
and/or particular individuals. If this were to happen, I think we'd get =
both more, and more diverse, nominations; but I appreciate that like =
John's suggestions, mine is unlikely to solve the problem this time =
around.

At the point where we pay people to occupy the role the nature of it =
changes dramatically.=20

> Dave.


--Apple-Mail=_E113D080-1164-4ECE-BD3A-6933DE0D11FE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJgD6MACgkQ8AA1q7Z/VrJzmQCdEQ+KO5qU0CndMUhZloCdKeN/
AN4AoIOej5paQ5nQ4Rli3QQyPI3rMgzD
=vnAA
-----END PGP SIGNATURE-----

--Apple-Mail=_E113D080-1164-4ECE-BD3A-6933DE0D11FE--

From chaitanyabd@gmail.com  Thu Oct 17 09:27:32 2013
Return-Path: <chaitanyabd@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 53B8F11E8278 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:27: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, 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 bsrE4hfBQAJy for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 09:27:31 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 40C4C11E827E for <ietf@ietf.org>; Thu, 17 Oct 2013 09:27:30 -0700 (PDT)
Received: by mail-qc0-f169.google.com with SMTP id x12so1705394qcv.0 for <ietf@ietf.org>; Thu, 17 Oct 2013 09:27:28 -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=eH2h2RW+YykA6jXVltNkzt7yjbzr/Lp1RWBV2T7R65c=; b=vCKNW+/6fJNQ7YkZIuuyR22FRENQ0IZ825coqQynXGI8ZaEzY0Pug69jM0qNMdfMKz iplemUa+o5g7PqD5okMGoB/o6hVPafE9fRp5Q+wGhfcd7w2t9//1pXBhQNdQhBX08dSB 3L2j06NEpB6DUA0cf1OyBZibvHNA/7kPJDPRmfNHdCpv4D34+ygzUCV0eE+N2mgZcfaL 7dpRax4rVck7Y/l+ab7IjVSA5y62ynXrq65OLWDftzDOoDIgI3Wg2l70oKsEb7Lyuuzu +6GfG2vu/EnTlHucuKlJELLe17BUkx497V5NTyAqmB8UxRD730LLZoNqmfnf0GjrAOqw BqFQ==
MIME-Version: 1.0
X-Received: by 10.49.35.144 with SMTP id h16mr5273062qej.35.1382027248832; Thu, 17 Oct 2013 09:27:28 -0700 (PDT)
Received: by 10.224.130.132 with HTTP; Thu, 17 Oct 2013 09:27:28 -0700 (PDT)
In-Reply-To: <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
Date: Thu, 17 Oct 2013 21:57:28 +0530
Message-ID: <CAEP5zKTj4tAv=zJEfdPwhbVkh_uUKC3rwi3SZMWy4i-gp8KPJA@mail.gmail.com>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=047d7b5d5af43c94d204e8f24bae
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 16:27:32 -0000

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

Makes sense Dave. I know having a possible solution named out does not
solve the problem this time around - but that the current nominees would
have naturally considered the expense ($+time). If a sponsorship scheme it
worked out before the next round it could not only benefit the current AD
but also set a positive interest factor in motion.

On Thu, Oct 17, 2013 at 9:32 PM, Dave Cridland <dave@cridland.net> wrote:

> I can see would be for larger companies to partially or wholly sponsor
> slots and/or particular individuals




*Chaitanya Dhareshwar*
**
Linkedin <http://in.linkedin.com/in/chaitanyabd> | Blog <http://cbd.vcio.in> |
Skype: chaitanyabd
Mobile: +91.9820760253

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_default" st=
yle=3D"font-family:tahoma,sans-serif">Makes sense Dave. I know having a pos=
sible solution named out does not solve the problem this time around - but =
that the current nominees would have naturally considered the expense ($+ti=
me). If a sponsorship scheme it worked out before the next round it could n=
ot only benefit the current AD but also set a positive interest factor in m=
otion. </div>
<br><div class=3D"gmail_quote">On Thu, Oct 17, 2013 at 9:32 PM, Dave Cridla=
nd <span dir=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_bl=
ank">dave@cridland.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" 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">
 I can see would be for larger companies to partially or wholly sponsor slo=
ts and/or particular individuals</blockquote></div><br><br><br clear=3D"all=
"><div><div dir=3D"ltr"><div><font face=3D"tahoma,sans-serif"><strong><font=
 color=3D"#3d85c6">Chaitanya Dhareshwar</font></strong></font></div>
<div><strong><font color=3D"#3d85c6" face=3D"Tahoma"></font></strong><font =
face=3D"tahoma,sans-serif"><br><a href=3D"http://in.linkedin.com/in/chaitan=
yabd" target=3D"_blank"><font color=3D"#3d85c6">Linkedin</font></a></font><=
font face=3D"tahoma,sans-serif"> | </font><a href=3D"http://cbd.vcio.in" ta=
rget=3D"_blank"><font color=3D"#3d85c6">Blog</font></a><font> <font face=3D=
"tahoma,sans-serif">| </font><font face=3D"tahoma,sans-serif">Skype: <font =
color=3D"#3d85c6">chaitanyabd</font></font></font></div>
<div><font face=3D"Tahoma"><font>Mobile: <font color=3D"#3d85c6">+91.982076=
0253</font></font></font></div></div></div>
</div></div>

--047d7b5d5af43c94d204e8f24bae--

From melinda.shore@gmail.com  Thu Oct 17 10:12: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 5DFA611E82A2 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:12:03 -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 CoLxIYXqPBzt for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:12:00 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 39E0B11E829C for <ietf@ietf.org>; Thu, 17 Oct 2013 10:11:57 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id y10so335751pdj.38 for <ietf@ietf.org>; Thu, 17 Oct 2013 10:11:57 -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=xbALoTR+Ac9+h2hDiFrtp9DPeGdBD8XQgS4ZNfEEzKs=; b=L6LCCaE4IV4ceHcbaSgvbpS68KpEfgBsTZ+PYRaSQ5O/+GJNYmRJlwiAGHRHFBlKe0 oWnQ7JdGI3EBCyoc6Ca4w0QL3lTKiW8bfojMFm0OVYw0yv4dzlUrUWEuhv/GtkaibwQl FeXU1qL19Q6bicNGOiu8ia6MsjD5vsf3dEGDLBIL4JduVaCWEky7IMs0/DGUY12o3mxW i0667pHoIIYRIsZTzBNokqGxko5egl66iOvZDGaqg8y4h0glPFdBZlGuK1QrMIJUmm+t dMr7JusyAVTdiM/VnTlYNj9VCta3k4SeYpy2oFnGlUV4MQWlneOo3Vn5I3x1MzQB86qx nV1g==
X-Received: by 10.66.162.195 with SMTP id yc3mr10203123pab.64.1382029916933; Thu, 17 Oct 2013 10:11:56 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id ja5sm99057992pbc.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 10:11:55 -0700 (PDT)
Message-ID: <52601A58.2050803@gmail.com>
Date: Thu, 17 Oct 2013 09:11:52 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
In-Reply-To: <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 17:12:03 -0000

On 10/17/13 8:02 AM, Dave Cridland wrote:
> The only solution allowing independents to become an AD that I can
> see would be for larger companies to partially or wholly sponsor
> slots and/or particular individuals. 

I suspect that there are companies out there who would view
this as giving them better "access" (i.e. the ability to apply
political pressure).  Not really very fond of this idea.

Melinda

From Ted.Lemon@nominum.com  Thu Oct 17 10:16:38 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 286DF11E817E for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 F7zrdB23fLwW for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:16:31 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5BB11E828A for <ietf@ietf.org>; Thu, 17 Oct 2013 10:16:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUmAbZsLl/6m0bH74LrstIvaT6s8KaY3v@postini.com; Thu, 17 Oct 2013 10:16: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 85F3D1B82E3 for <ietf@ietf.org>; Thu, 17 Oct 2013 10:16:22 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 6CB7519005C; Thu, 17 Oct 2013 10:16:22 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Oct 2013 10:16:22 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52601A58.2050803@gmail.com>
Date: Thu, 17 Oct 2013 13:16:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F6E2854E-5453-41B6-BED6-F79DA2B36BFA@nominum.com>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com> <52601A58.2050803@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 17:16:38 -0000

On Oct 17, 2013, at 1:11 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
> I suspect that there are companies out there who would view
> this as giving them better "access" (i.e. the ability to apply
> political pressure).  Not really very fond of this idea.

It would have to be a formal commitment of resources that couldn't be =
rescinded for the duration of the AD's term.   I suppose there would =
still be the possibility of the AD doing something to try to retain the =
position after the end of the term, but I think the job is not so much =
fun that this would be a real issue.   I think the current funding =
mechanism creates a much more substantial possibility of companies =
thinking they will get "access," because in fact they do.   I have heard =
of at least one former AD being influenced in this way (no, I won't tell =
you which one, and I don't have proof that it happened, just hearsay).


From mcr@sandelman.ca  Thu Oct 17 10:22:32 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 973F011E828E for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=1.094,  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 NB1jgWawHY8h for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:22:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 10C7911E82AF for <ietf@ietf.org>; Thu, 17 Oct 2013 10:22:19 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7C56020168 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:32:52 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4297B63B88; Thu, 17 Oct 2013 13:22:12 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2E68063AEF for <ietf@ietf.org>; Thu, 17 Oct 2013 13:22:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discuss <ietf@ietf.org>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
In-Reply-To: <FDDC3EF96422A0625A822E07@JcK-HP8200.jck.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <FDDC3EF96422A0625A822E07@JcK-HP8200.jck.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, 17 Oct 2013 13:22:12 -0400
Message-ID: <14877.1382030532@sandelman.ca>
Sender: 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, 17 Oct 2013 17:22:32 -0000

--=-=-=


John C Klensin <john-ietf@jck.com> wrote:
    > (1) The time and resource commitment required of ADs is largely, but
    > not entirely, of the IESG's own making.  People get selected who have
    > the time and resources and the job and/or perception of things for
    > which IESG members need to take personal responsibility tend to expand
    > to more than fill the available time.  I've given the opinion to a
    > number of Nomcoms that the problem will just get worse unless they
    > select people who see that expansion of the role as a problem and have
    > plans for how to fix it (or at least a good-faith intent to support
    > such plans).  My impression is that it hasn't ranked high in Nomcom
    > priorities so, if it is important to others, more people need to say

Perhaps some people who feel this way ought to write an open letter saying
so.

    > (2) The Nomcom doesn't have a lot of control in this space.  The number
    > of ADs per area is set by the IESG, not the Nomcom, and the Nomcom has
    > little choice other that to try to fill the positions (there have been
    > debates over the years as to whether a Nomcom could actually refuse to
    > fill a position but certainly it should not consider trying except in
    > the most dire of circumstances).  ADs have tremendous flexibility about

sadly, 3777 doesn't provide a way for the nomcom to "fail"

    > enough, we could tell Nomcoms to start firing (or refusing to appoint)
    > ADs who don't show good management and delegation skills but, if we did
    > that any they listened, they might have to prioritize management skills
    > over technical skills and understanding and it is possible that
    > wouldn't work out well (and would give us even more professional

And don't forget that the confirming body has to agree.
So, if you want to fix IESG problems, you have to pick IAB people who
agree that there is a problem.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUmAcv4qHRg3pndX9AQLeogQA37kpWRcADOQ6YvBnsch6k5h9Hs2O9IXR
MjGnVdOCXGUPPTuJQWfJ4L4RtEnUoVxYar4nNmzlfsK42oftju+UeWhjccA+W5jz
gAXjnm9t63cm6nHqjSYvZLhXKUbb/aQJM4QfKEcY9Ire7+DyrSPY7+ClKn8/zOMa
0TGMsm0Db+Y=
=o7bp
-----END PGP SIGNATURE-----
--=-=-=--

From hgs@cs.columbia.edu  Thu Oct 17 10:24:13 2013
Return-Path: <hgs@cs.columbia.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 35DDA11E82A4 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:24:13 -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 JjdVxBUPDLiZ for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 10:24:06 -0700 (PDT)
Received: from millet.cc.columbia.edu (millet.cc.columbia.edu [128.59.72.250]) by ietfa.amsl.com (Postfix) with ESMTP id F28B511E81A2 for <ietf@ietf.org>; Thu, 17 Oct 2013 10:23:53 -0700 (PDT)
Received: from hazelnut (hazelnut.cc.columbia.edu [128.59.213.250]) by millet.cc.columbia.edu (8.13.8/8.13.8) with ESMTP id r9HHIrkp020360;  Thu, 17 Oct 2013 13:23:15 -0400
Received: from hazelnut (localhost.localdomain [127.0.0.1]) by hazelnut (Postfix) with ESMTP id 4F55D6C; Thu, 17 Oct 2013 13:23:15 -0400 (EDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by hazelnut (Postfix) with ESMTP id 447BB6C; Thu, 17 Oct 2013 13:23:15 -0400 (EDT)
Received: from [172.19.131.166] ([12.130.122.206]) (user=hgs10 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r9HHNBxp007965 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 17 Oct 2013 13:23:13 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <52601A58.2050803@gmail.com>
Date: Thu, 17 Oct 2013 13:23:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5DA60AA-3F54-4CF8-B43F-37102E772564@cs.columbia.edu>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com> <52601A58.2050803@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 17:24:13 -0000

As long as the external funding is not tied to a specific person or =
position, but a general support fund to be administered by the IETF, =
there's probably no more pressure than (say) sponsoring an IETF meeting.

The notion that a nearly full-time position with lots of travel can be a =
"volunteer" is clearly make-believe. There are three possibilities:

(1) Only people employed by large corporations can realistically be =
candidates. The same "access" issues you mention apply, presumably.

(2) There is a way to financially support other candidates via a =
stipend, similar to what (say) the Federal government does when they =
"borrow" faculty for the NSF, DARPA or the FCC.

(3) The workload of the IESG members is reduced and distributed to =
return it to a volunteer position (i.e., probably no more than ten hours =
a week).

Henning

On Oct 17, 2013, at 1:11 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> On 10/17/13 8:02 AM, Dave Cridland wrote:
>> The only solution allowing independents to become an AD that I can
>> see would be for larger companies to partially or wholly sponsor
>> slots and/or particular individuals.=20
>=20
> I suspect that there are companies out there who would view
> this as giving them better "access" (i.e. the ability to apply
> political pressure).  Not really very fond of this idea.
>=20
> Melinda
>=20



From dhc@dcrocker.net  Thu Oct 17 11:36: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 4A97911E819E for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level: 
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5 tests=[AWL=0.646,  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 L-HnParJ6Vyx for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:36:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6141521F8FD2 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:36:00 -0700 (PDT)
Received: from [10.100.255.252] ([122.56.34.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9HIZtv0026122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 17 Oct 2013 11:36:00 -0700
Message-ID: <52602DF7.3030207@dcrocker.net>
Date: Fri, 18 Oct 2013 07:35:35 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: IETF Discuss <ietf@ietf.org>
Subject: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@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.0 (sbh17.songbird.com [72.52.113.66]); Thu, 17 Oct 2013 11:36:00 -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, 17 Oct 2013 18:36:05 -0000

On 10/18/2013 3:54 AM, Tim Chown wrote:
> I believe the "intense service" you mention is a significant deterrent for many.
>
> I'm sure it's been suggested before, but is there mileage in rethinking the
> AD roles,


It has been suggested many times.  The suggestion has been ignored.

We have been having some very serious recruitment problems for a number 
of years now.  This year's crisis was entirely predictable.

The only way the situation will change meaningfully is to make the job 
less onerous, and especially make it possible for the AD to continue 
doing real work for their company.

ADs are senior folk.  That makes them a strategic resource for their 
company.  Or, at least, they'd better be.  Only very large companies can 
afford to lose a strategic resource for years.

Looking for alternative funding does not make the job less onerous and 
does not permit the AD to continue doing real work for their company.

Re-define the bloody job.  At a minimum, make the workload realistically 
no more than 50%, but I actually suggest trying for 25%, given that 
reality will increase the actual amount above that.

This means taking the current list of AD tasks and deciding on the ones 
that absolutely cannot be done by others, and specifying other ways to 
do the remainder.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ietfdbh@comcast.net  Thu Oct 17 11:37:44 2013
Return-Path: <ietfdbh@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 30D1711E82A1 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.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 OZzh0U3Q+CIT for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:37:39 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 624D511E8140 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:37:39 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta09.westchester.pa.mail.comcast.net with comcast id eEKq1m0070vyq2s59JdflW; Thu, 17 Oct 2013 18:37:39 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta05.westchester.pa.mail.comcast.net with comcast id eJde1m00u2yZEBF3RJdewx; Thu, 17 Oct 2013 18:37:39 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: <ietf@ietf.org>, "'IETF Announcement List'" <ietf-announce@ietf.org>
References: <20131017180905.32613.52312.idtracker@ietfa.amsl.com>
In-Reply-To: <20131017180905.32613.52312.idtracker@ietfa.amsl.com>
Subject: RE: [BEHAVE] WG Action: Conclusion of Behavior Engineering for	Hindrance Avoidance	(behave)
Date: Thu, 17 Oct 2013 14:37:37 -0400
Message-ID: <03a501cecb67$f4671770$dd354650$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDe/3fBukWW5KwzDp8YLSsRkgfvBJvY0LoQ
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382035059; bh=9HXP1FpOv40guVM71EiZ/A586UZAa6ulOxMxN7r/5mc=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=B2pZ58bKI8ILgnOFcBv2ls5mZIlnPyEt2Bf1YZs8GWujLHCZam1SythsgNzYjZxy6 eaaXR/qod6ZgRSg20BNmJrwOR9whNiJq//08l6CQVpmra/FegctIdDopAEdvyslbio x5VBDab9tByC0wxY8gfL2GKhnGBR6cj2UTtbLI+u+2ccDkfveRYo4t079cxGIdj9sG f99cZDbT53MD8RVW+CNAq5Cj3FEwb95sQd10zKXGZvxXL4Vwxlq04btqAI+x1zAFYi DSyAXoa7KpWv6h5ESVVFvQY4uvllf/+IJWUJ29SrL8b7lSeXgLaeEM0u52emGhx4qz Ami5C1kN08Efw==
Cc: behave@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 18:37:44 -0000

I would like to personally thank Dave and Dan for their efforts chairing
this WG.
I found them excellent to work with.

David Harrington
ietfdbh@comcast.net
+1-603-828-1401

> -----Original Message-----
> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
> Behalf Of IESG Secretary
> Sent: Thursday, October 17, 2013 2:09 PM
> To: IETF Announcement List
> Cc: behave@ietf.org; dthaler@microsoft.com; dwing@cisco.com
> Subject: [BEHAVE] WG Action: Conclusion of Behavior Engineering for
> Hindrance Avoidance (behave)
> 
> The Behavior Engineering for Hindrance Avoidance (behave) Working Group
> in the Transport Area has concluded. The IESG contact persons are
> Spencer Dawkins and Martin Stiemerling.
> 
> BEHAVE has five working group drafts in progress:
> 
> draft-ietf-behave-ipfix-nat-logging
> draft-ietf-behave-nat-mib
> draft-ietf-behave-syslog-nat-logging
> draft-ietf-behave-requirements-update
> draft-ietf-behave-sctpnat
> 
> These will be converted to individual submissions.
> 
> The BEHAVE mailing list will remain open to support further discussions
> on these drafts, as necessary, and for review of relevant documents in
> other WGs.
> 
> BEHAVE has done substantial work and has produced 24 RFCs over nearly
> a decade, with two more in the RFC Editor queue.
> 
> Our thanks to Dan Wing and to Dave Thaler as chairs, and to all of the
> authors and working group participants.
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave


From john-ietf@jck.com  Thu Oct 17 11:42: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 91E4A11E8116 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.582
X-Spam-Level: 
X-Spam-Status: No, score=-103.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 93swUlHz7uWx for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:42:15 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 62AFA11E8192 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:42:15 -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 1VWsWR-0003Pm-Ke; Thu, 17 Oct 2013 14:42:11 -0400
Date: Thu, 17 Oct 2013 14:42:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: joel jaeggli <joelja@bogus.com>, Dave Cridland <dave@cridland.net>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
Message-ID: <C2A98025F2BEAB137396BBE2@JcK-HP8200.jck.com>
In-Reply-To: <F2FD96A5-F26F-481B-AC9C-7A2EE16DD665@bogus.com>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com> <F2FD96A5-F26F-481B-AC9C-7A2EE16DD665@bogus.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: Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 18:42:24 -0000

--On Thursday, October 17, 2013 09:26 -0700 joel jaeggli
<joelja@bogus.com> wrote:

>> The only solution allowing independents to become an AD that
>> I can see would be for larger companies to partially or
>> wholly sponsor slots and/or particular individuals. If this
>> were to happen, I think we'd get both more, and more diverse,
>> nominations; but I appreciate that like John's suggestions,
>> mine is unlikely to solve the problem this time around.
> 
> At the point where we pay people to occupy the role the nature
> of it changes dramatically. 

Joel,

Yes.

At the same time, having positions that can predominantly only
be filled by those who work for, or can scrounge long-term
funding commitments from, large companies, governments, or
organizations that see particular benefits to themselves to
having someone on the IESG (or IAB) changes things dramatically
too.  And I suggest we are already very far down that slippery
slope.

Speaking as one of those independents who, in recent years, has
had to weigh the costs of every meeting against whether there is
really sufficient benefit to being there (if I hadn't already
made several commitments and missed Berlin, I wouldn't be coming
to Vancouver), I think it might be possible to do three things
without causing more harm than we have done to ourselves already:

(i) We could try to get broad support for the marginal expenses
associated with leadership positions.  Not salary or equivalent
(that would cross over into "paying people to occupy the role")
and probably not even the basic costs of attending IETF
meetings, but it might help if the extra costs associated with
retreats, extra days of meetings, etc., became community
expenses rather than additional burdens on people who volunteer
for leadership roles.   It would still leave most independents
with the problem of giving up actual income to participate
because a day spent on IETF work is a day or no pay while most
company-sponsored participants continue to draw salaries while
working on IETF things, but, for at least some of us, there is a
large psychological difference between forgone income and out of
pocket expenses.

(ii) We could try to trim these roles back to the 1/4 to 1/2
time they represented 15 or 20 years ago.  For many people,
there is a huge difference between "full time commitment for a
couple of years" and "you may need to work hard, long, hours but
can expect to continue to do your day job with real design,
product, implementation, or management responsibilities while
serving as an AD".

Again, the Nomcom can't do much about either of these things
other than trying to recruit and select people who think the
issues are important (if the community actually believes that
they are).  However, I think that those of us who are concerned
should remember that these sorts of issues are unlikely to be
personal priorities for any seated IESG member -- after all,
they, by definition, have the time and support needed to do the
job and the Nomcom has yet to fail to fill a position because no
one could be found who was reasonably qualified and willing to
do it.

   john







From john-ietf@jck.com  Thu Oct 17 11:47:48 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 A361411E82A8 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.584
X-Spam-Level: 
X-Spam-Status: No, score=-103.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 cZlUK-WKZOjy for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:47:42 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 43E7B11E8287 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:47:40 -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 1VWsbi-0003QE-U4; Thu, 17 Oct 2013 14:47:38 -0400
Date: Thu, 17 Oct 2013 14:47:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, IETF Discuss <ietf@ietf.org>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for	Nominations)
Message-ID: <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>
In-Reply-To: <52602DF7.3030207@dcrocker.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 18:47:48 -0000

--On Friday, October 18, 2013 07:35 +1300 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 10/18/2013 3:54 AM, Tim Chown wrote:
>> I believe the "intense service" you mention is a significant
>> deterrent for many.
>> 
>> I'm sure it's been suggested before, but is there mileage in
>> rethinking the AD roles,
> 
> 
> It has been suggested many times.  The suggestion has been
> ignored.
> 
> We have been having some very serious recruitment problems for
> a number of years now.  This year's crisis was entirely
> predictable.
> 
> The only way the situation will change meaningfully is to make
> the job less onerous, and especially make it possible for the
> AD to continue doing real work for their company.
> 
> ADs are senior folk.  That makes them a strategic resource for
> their company.  Or, at least, they'd better be.  Only very
> large companies can afford to lose a strategic resource for
> years.
> 
> Looking for alternative funding does not make the job less
> onerous and does not permit the AD to continue doing real work
> for their company.
> 
> Re-define the bloody job.  At a minimum, make the workload
> realistically no more than 50%, but I actually suggest trying
> for 25%, given that reality will increase the actual amount
> above that.
> 
> This means taking the current list of AD tasks and deciding on
> the ones that absolutely cannot be done by others, and
> specifying other ways to do the remainder.

Agree completely (our notes crossed in the mail).

But, again, the Nomcom can't fix this, at least for this year's
selections.   And one thing that has prevented the job from
being trimmed back is resistance from sitting ADs (sometimes
public and vigorous and sometimes passive refusal to consider
procedural changes or discuss them with the community, but
nonetheless blocking resistance).   I would support advising the
Nomcom that no one should be placed on, or returned to, the IESG
unless the Nomcom members were convinced that the candidates
considered reducing the size of the role both appropriate and a
high priority.  

I don't believe there has ever been sufficient community
consensus for that.  I'd be delighted to be wrong.

    john




From Tina.Tsou.Zouting@huawei.com  Thu Oct 17 11:47:56 2013
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D0D11E81FF; Thu, 17 Oct 2013 11:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.314
X-Spam-Level: 
X-Spam-Status: No, score=-6.314 tagged_above=-999 required=5 tests=[AWL=0.285,  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 cFQWE1ku5GVH; Thu, 17 Oct 2013 11:47:52 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E5F7311E8146; Thu, 17 Oct 2013 11:47:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AWX05603; Thu, 17 Oct 2013 18:47:42 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 17 Oct 2013 19:46:44 +0100
Received: from SJCEML401-HUB.china.huawei.com (10.212.94.42) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 17 Oct 2013 19:47:40 +0100
Received: from SJCEML501-MBS.china.huawei.com ([169.254.2.123]) by sjceml401-hub.china.huawei.com ([::1]) with mapi id 14.03.0158.001; Thu, 17 Oct 2013 11:47:34 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: ietfdbh <ietfdbh@comcast.net>
Subject: Re: [BEHAVE] WG Action: Conclusion of Behavior Engineering	for Hindrance Avoidance	(behave)
Thread-Topic: [BEHAVE] WG Action: Conclusion of Behavior Engineering	for Hindrance Avoidance	(behave)
Thread-Index: AQHOy2ga9ABOikvi2UawUev4JSrqdpn5O952
Date: Thu, 17 Oct 2013 18:47:33 +0000
Message-ID: <E20F5CF4-B2D4-45AD-A2D1-F41FDDA92963@huawei.com>
References: <20131017180905.32613.52312.idtracker@ietfa.amsl.com>, <03a501cecb67$f4671770$dd354650$@comcast.net>
In-Reply-To: <03a501cecb67$f4671770$dd354650$@comcast.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 18:47:56 -0000

Dear all,
WG behave tremendously helps our way to IPv6 and IPv4 service continuity in=
 the industry. There is good memory of discussions, meetings, laugh, learn,=
 and grow.
Thank you everyone.

Thank you,
Tina

On Oct 17, 2013, at 11:38 AM, "ietfdbh" <ietfdbh@comcast.net> wrote:

> I would like to personally thank Dave and Dan for their efforts chairing
> this WG.
> I found them excellent to work with.
>=20
> David Harrington
> ietfdbh@comcast.net
> +1-603-828-1401
>=20
>> -----Original Message-----
>> From: behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] On
>> Behalf Of IESG Secretary
>> Sent: Thursday, October 17, 2013 2:09 PM
>> To: IETF Announcement List
>> Cc: behave@ietf.org; dthaler@microsoft.com; dwing@cisco.com
>> Subject: [BEHAVE] WG Action: Conclusion of Behavior Engineering for
>> Hindrance Avoidance (behave)
>>=20
>> The Behavior Engineering for Hindrance Avoidance (behave) Working Group
>> in the Transport Area has concluded. The IESG contact persons are
>> Spencer Dawkins and Martin Stiemerling.
>>=20
>> BEHAVE has five working group drafts in progress:
>>=20
>> draft-ietf-behave-ipfix-nat-logging
>> draft-ietf-behave-nat-mib
>> draft-ietf-behave-syslog-nat-logging
>> draft-ietf-behave-requirements-update
>> draft-ietf-behave-sctpnat
>>=20
>> These will be converted to individual submissions.
>>=20
>> The BEHAVE mailing list will remain open to support further discussions
>> on these drafts, as necessary, and for review of relevant documents in
>> other WGs.
>>=20
>> BEHAVE has done substantial work and has produced 24 RFCs over nearly
>> a decade, with two more in the RFC Editor queue.
>>=20
>> Our thanks to Dan Wing and to Dave Thaler as chairs, and to all of the
>> authors and working group participants.
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave

From dhc@dcrocker.net  Thu Oct 17 11:59:33 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 5F21F11E82AF for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.276
X-Spam-Level: 
X-Spam-Status: No, score=-6.276 tagged_above=-999 required=5 tests=[AWL=0.323,  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 pMe9r0YGip5x for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:59:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0456F11E82A2 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:58:47 -0700 (PDT)
Received: from [10.100.255.252] ([122.56.34.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9HIwegX027117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Oct 2013 11:58:45 -0700
Message-ID: <5260334D.10806@dcrocker.net>
Date: Fri, 18 Oct 2013 07:58:21 +1300
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>
In-Reply-To: <DC59B10837C9CD235DD98438@JcK-HP8200.jck.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]); Thu, 17 Oct 2013 11:58:46 -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, 17 Oct 2013 18:59:43 -0000

On 10/18/2013 7:47 AM, John C Klensin wrote:
> But, again, the Nomcom can't fix this, at least for this year's
> selections.   And one thing that has prevented the job from
> being trimmed back is resistance from sitting ADs (sometimes
> public and vigorous and sometimes passive refusal to consider
> procedural changes or discuss them with the community, but
> nonetheless blocking resistance).   I would support advising the
> Nomcom that no one should be placed on, or returned to, the IESG
> unless the Nomcom members were convinced that the candidates
> considered reducing the size of the role both appropriate and a
> high priority.


The IESG defines the job and the IESG 'operates' the model.  So yes, 
formally the IESG controls this issue.

However...

Nomcom can apply pretty much whatever criteria it wants to the selection 
process and Nomcom has been know to have some private negotiations with 
the IESG.  Nothing as profound as the change we are suggesting, but still...

So yes, an example of how Nomcom might independently deal with the 
current crisis is to announce a policy of looking for ADs who are 
willing to work no more than X% and then making a point of selecting 
such folk.

(Note that I'm saying something different from John.  He's caling for 
new folk who would "support" a change; I'm calling for new folk who are 
firm that they won't do more than X%.)

It would be better for the IESG to take the initiative here and formally 
and publicly re-define the job, but it has so far ignored such requests.

So Nomcom could start things towards that change on its own.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From abdussalambaryun@gmail.com  Thu Oct 17 11:59:56 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 5721111E82A2 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  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 waBcSfbwOAUc for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 11:59:52 -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 5F9CA11E82A4 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:59:30 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id bj1so3239507pad.35 for <ietf@ietf.org>; Thu, 17 Oct 2013 11:59:27 -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=F+/QoZq7ucEijaQC4oKKp5jjNKeqnpkMLSqtOIe/KPI=; b=SvI3Xn7c59+tBoBX8tlTKkLTOfGyX57puh9WR39yhwfcZRLJlFm2A8k/Yi5ep1jk69 JdcBqqW8U5kWhn9Z8DZXi/OJR23EE9CTTSF1cKYYAzSNKebKWXTrJCUobExlPithG0qE eBY+oioA1gFf5wDG43vSMK35T1+rIoi+puPstkmA5ybES8TQ7VbDTsBUf4sdrRDE/xN2 77M8kQa81HuNxkrRD8Id/nanpiGbyHZxNcIFIdXg+lbNYA0/hVfJnoAdqAhZvBHrLawR L3ej0gCUN8yE75NjQE0iEWhBDQnpiPRdHTs1dtBT0GvvBaBNOSA4OzkFOU3QdDIN787U +K+w==
MIME-Version: 1.0
X-Received: by 10.66.148.97 with SMTP id tr1mr4556288pab.163.1382036367795; Thu, 17 Oct 2013 11:59:27 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Thu, 17 Oct 2013 11:59:27 -0700 (PDT)
In-Reply-To: <52602DF7.3030207@dcrocker.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net>
Date: Thu, 17 Oct 2013 20:59:27 +0200
Message-ID: <CADnDZ89X_8za_x8CqjHPbiXiQSLq=7GAhbYQOSV+91ECMQbwgA@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b6d9fa2c56aab04e8f46a0a
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 18:59:57 -0000

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

I suggest not to change AD tasks, efforts, and responsibilities but to add
a new position for each area as assistant AD position that has less
qualification and attendance (can be done by remote participants). I think
the ignorance is on remote participants not on reducing responsibilities.

IMHO, If we reduce job output of AD and  responsibilities we will get low
quality Processes. By having assistant ADs we reduce only ADs input hours
in IETF.

AB

On Thursday, October 17, 2013, Dave Crocker wrote:

> On 10/18/2013 3:54 AM, Tim Chown wrote:
>
>> I believe the "intense service" you mention is a significant deterrent
>> for many.
>>
>> I'm sure it's been suggested before, but is there mileage in rethinking
>> the
>> AD roles,
>>
>
>
> It has been suggested many times.  The suggestion has been ignored.
>
> We have been having some very serious recruitment problems for a number of
> years now.  This year's crisis was entirely predictable.
>
> The only way the situation will change meaningfully is to make the job
> less onerous, and especially make it possible for the AD to continue doing
> real work for their company.
>
> ADs are senior folk.  That makes them a strategic resource for their
> company.  Or, at least, they'd better be.  Only very large companies can
> afford to lose a strategic resource for years.
>
> Looking for alternative funding does not make the job less onerous and
> does not permit the AD to continue doing real work for their company.
>
> Re-define the bloody job.  At a minimum, make the workload realistically
> no more than 50%, but I actually suggest trying for 25%, given that reality
> will increase the actual amount above that.
>
> This means taking the current list of AD tasks and deciding on the ones
> that absolutely cannot be done by others, and specifying other ways to do
> the remainder.
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

I suggest not to change AD tasks, efforts, and responsibilities but to add =
a new position for each area as assistant AD position that has less qualifi=
cation and attendance (can be done by remote participants). I think the ign=
orance is on remote participants not on reducing responsibilities.<div>
<br></div><div>IMHO, If we reduce job output of=A0AD and=A0=A0responsibilit=
ies we will get low quality Processes. By having assistant ADs we reduce on=
ly ADs input hours in IETF.</div><div><br></div><div>AB</div><div><div><br>=
On Thursday, October 17, 2013, Dave Crocker  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 10/18/2013 3:54 AM, Tim Chown wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I believe the &quot;intense service&quot; you mention is a significant dete=
rrent for many.<br>
<br>
I&#39;m sure it&#39;s been suggested before, but is there mileage in rethin=
king the<br>
AD roles,<br>
</blockquote>
<br>
<br>
It has been suggested many times. =A0The suggestion has been ignored.<br>
<br>
We have been having some very serious recruitment problems for a number of =
years now. =A0This year&#39;s crisis was entirely predictable.<br>
<br>
The only way the situation will change meaningfully is to make the job less=
 onerous, and especially make it possible for the AD to continue doing real=
 work for their company.<br>
<br>
ADs are senior folk. =A0That makes them a strategic resource for their comp=
any. =A0Or, at least, they&#39;d better be. =A0Only very large companies ca=
n afford to lose a strategic resource for years.<br>
<br>
Looking for alternative funding does not make the job less onerous and does=
 not permit the AD to continue doing real work for their company.<br>
<br>
Re-define the bloody job. =A0At a minimum, make the workload realistically =
no more than 50%, but I actually suggest trying for 25%, given that reality=
 will increase the actual amount above that.<br>
<br>
This means taking the current list of AD tasks and deciding on the ones tha=
t absolutely cannot be done by others, and specifying other ways to do the =
remainder.<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>
</blockquote></div></div>

--047d7b6d9fa2c56aab04e8f46a0a--

From sm@elandsys.com  Thu Oct 17 12:04:01 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 8D73E11E813D for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level: 
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=0.537, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 XN2eFyP63bnn for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:03:56 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id B7DB611E812A for <ietf@ietf.org>; Thu, 17 Oct 2013 12:03:55 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.243]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9HJ1eEw012896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Oct 2013 12:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382036583; bh=Ac4KM7v1D+yqOEdF+F9bf2lEUh/svx5O0rGrdMOrJQA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YQM2h3JZswTDmPMiJ58TqzN+uxkoWYt1oy1ym846YVM4cACvgelCphiAfYrJ6dRUW dhkE+EhJUyDjWZOKTGWZSthj7pkNatmpx6NOvt9R2CESTOMSOKNlwq4lcKFgkJqCal 6qiP5iJJJs6INX6wmyzjG0YRfYYG+Qr3WSnUAXDs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382036583; i=@elandsys.com; bh=Ac4KM7v1D+yqOEdF+F9bf2lEUh/svx5O0rGrdMOrJQA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fHRrJc4AUjaZ0L/SldSgQtoZ/gdmLl30drF3vCOLHQnXEDCrpEg0acncUa0ZIUBuj iHp5NI0fdx/yIz0U/0XWBwCL2w5fKNCVG5esXsI1iPX9iduVtPhS2ze8H72gq2aOMR /N5WNrCbBt0XRm96QqoeLrnvn+e3CORWKzideP+g=
Message-Id: <6.2.5.6.2.20131017085827.0cd9aa98@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Oct 2013 11:55:56 -0700
To: Tim Chown <tjc@ecs.soton.ac.uk>, John C Klensin <john-ietf@jck.com>, Henning Schulzrinne <hgs@cs.columbia.edu>, Dave Crocker <dhc@dcrocker.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
In-Reply-To: <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soto n.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.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, 17 Oct 2013 19:04:01 -0000

At 07:54 17-10-2013, Tim Chown wrote:
>I believe the "intense service" you mention is a significant 
>deterrent for many.

Yes.

>I'm sure it's been suggested before, but is there mileage in rethinking the
>AD roles, and either the number of ADs per area, or whether introducing
>Assistant ADs or similar might allow people who can contribute less time to
>do so, while easing the burden on the main ADs?

My guess is that it is possible to reduce the time requirement to 20 
hours per week.  It is not possible to get there within a short 
timespan.  There is a chance that the person attempting that might be 
recalled before being able to do anything substantive.

Introducing Assistant ADS might alleviate the problem instead of 
being a long-term solution.  Please note that I am taking into 
consideration the 11-year IETF cycle.

At 08:51 17-10-2013, John C Klensin wrote:
>time.  I've given the opinion to a number of Nomcoms that the
>problem will just get worse unless they select people who see
>that expansion of the role as a problem and have plans for how
>to fix it (or at least a good-faith intent to support such
>plans).   My impression is that it hasn't ranked high in Nomcom

Yes.

>At the same time, it is hard to blame the IESG for a lot of the
>problem.  The community has not been supportive of efforts to
>push back on formation of WGs nor of shutting down ones that are
>unproductive or that cannot reach reasonable levels of consensus
>about their work.  The "chief representative of the IETF

Yes.

>In other words, while I mostly agree with you, it is too late
>for most of the issues and remedies by the time the Nomcom
>issues a call for Nominations.

Yes.

Adding to the above, the next year, there will be a new NomCom which 
has to face the same issues and cannot do much about it as it is too late.

At 10:23 17-10-2013, Henning Schulzrinne wrote:
>The notion that a nearly full-time position with lots of travel can 
>be a "volunteer" is clearly make-believe. There are three possibilities:
>
>(1) Only people employed by large corporations can realistically be 
>candidates. The same "access" issues you mention apply, presumably.

Yes.

>(3) The workload of the IESG members is reduced and distributed to 
>return it to a volunteer position (i.e., probably no more than ten 
>hours a week).

The IESG would have to review less documents.  There would have to be 
less working groups under the responsibility of the Area Director.  A 
controversial working group can easily take around ten hours of work 
a week.  The amount of time can be cut down by sharing the 
workload.  There would have to be some training if one believes that 
it would be inconsiderate to ask a person to volunteer and let the 
person hang himself/herself.

At 11:35 17-10-2013, Dave Crocker wrote:
>We have been having some very serious recruitment problems for a 
>number of years now.  This year's crisis was entirely predictable.

Yes.

>Re-define the bloody job.  At a minimum, make the workload 
>realistically no more than 50%, but I actually suggest trying for 
>25%, given that reality will increase the actual amount above that.
>
>This means taking the current list of AD tasks and deciding on the 
>ones that absolutely cannot be done by others, and specifying other 
>ways to do the remainder.

Yes.

Regards,
S. Moonesamy  


From stpeter@stpeter.im  Thu Oct 17 12:10:48 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 61C7B11E826B for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.333
X-Spam-Level: 
X-Spam-Status: No, score=-102.333 tagged_above=-999 required=5 tests=[AWL=0.266, 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 aKPJMIYiAw6A for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:10:43 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2D96E11E815A for <ietf@ietf.org>; Thu, 17 Oct 2013 12:10:34 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8DF464100F; Thu, 17 Oct 2013 13:16:58 -0600 (MDT)
Message-ID: <52603628.1080007@stpeter.im>
Date: Thu, 17 Oct 2013 13:10:32 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net>
In-Reply-To: <5260334D.10806@dcrocker.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:10:48 -0000

On 10/17/13 12:58 PM, Dave Crocker wrote:
> On 10/18/2013 7:47 AM, John C Klensin wrote:
>> But, again, the Nomcom can't fix this, at least for this year's
>> selections.   And one thing that has prevented the job from
>> being trimmed back is resistance from sitting ADs (sometimes
>> public and vigorous and sometimes passive refusal to consider
>> procedural changes or discuss them with the community, but
>> nonetheless blocking resistance).   I would support advising the
>> Nomcom that no one should be placed on, or returned to, the IESG
>> unless the Nomcom members were convinced that the candidates
>> considered reducing the size of the role both appropriate and a
>> high priority.
> 
> 
> The IESG defines the job and the IESG 'operates' the model.  So yes,
> formally the IESG controls this issue.
> 
> However...
> 
> Nomcom can apply pretty much whatever criteria it wants to the selection
> process and Nomcom has been know to have some private negotiations with
> the IESG.  Nothing as profound as the change we are suggesting, but
> still...
> 
> So yes, an example of how Nomcom might independently deal with the
> current crisis is to announce a policy of looking for ADs who are
> willing to work no more than X% and then making a point of selecting
> such folk.
> 
> (Note that I'm saying something different from John.  He's caling for
> new folk who would "support" a change; I'm calling for new folk who are
> firm that they won't do more than X%.)
> 
> It would be better for the IESG to take the initiative here and formally
> and publicly re-define the job, but it has so far ignored such requests.
> 
> So Nomcom could start things towards that change on its own.

I agree that the job needs to change.

It might be helpful to talk about what could change, such as:

1. Less/no time on document reviews.
2. Less time managing working groups.
3. Fewer working groups to manage.
4. Fewer "extra" tasks (e.g., interfacing with other SDOs).
5. Less/no involvement with BoFs and other early-stage efforts.
6. Less/no involvement with creating the schedule.

Perhaps some time and motion studies are in order to figure out how ADs
spend their time. In my experience, document reviews required a major
time commitment.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ogud@ogud.com  Thu Oct 17 12:26:35 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 B695E11E8242 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 GL7CoqMATDhC for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:26:25 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id 7F36811E8141 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:26:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 9CB2B140B80; Thu, 17 Oct 2013 15:26:23 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 54FB7140B63;  Thu, 17 Oct 2013 15:26:23 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <52602DF7.3030207@dcrocker.net>
Date: Thu, 17 Oct 2013 15:26:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:26:36 -0000

On Oct 17, 2013, at 2:35 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 10/18/2013 3:54 AM, Tim Chown wrote:
>> I believe the "intense service" you mention is a significant =
deterrent for many.
>>=20
>> I'm sure it's been suggested before, but is there mileage in =
rethinking the
>> AD roles,
>=20
>=20
> It has been suggested many times.  The suggestion has been ignored.
>=20
> We have been having some very serious recruitment problems for a =
number of years now.  This year's crisis was entirely predictable.
>=20
> The only way the situation will change meaningfully is to make the job =
less onerous, and especially make it possible for the AD to continue =
doing real work for their company.
>=20
> ADs are senior folk.  That makes them a strategic resource for their =
company.  Or, at least, they'd better be.  Only very large companies can =
afford to lose a strategic resource for years.
>=20
> Looking for alternative funding does not make the job less onerous and =
does not permit the AD to continue doing real work for their company.
>=20
> Re-define the bloody job.  At a minimum, make the workload =
realistically no more than 50%, but I actually suggest trying for 25%, =
given that reality will increase the actual amount above that.
>=20
> This means taking the current list of AD tasks and deciding on the =
ones that absolutely cannot be done by others, and specifying other ways =
to do the remainder.
>=20
> d/
>=20


Hear hear +1=20
some ideas to decrease the work load=20
	1) Limit on working groups in each area=20
	2) Less review of documents our outsource reviews
	3) Lower the voting threshold for document to pass
	4) Reduce hurdles in processing
	5) Assign tasks to different bodies=20
	6) More competent WG chairs=20
	7) Pick AD's that are less likely to nit pick documents
	8) ignore process nazi's and streamline process.=20
	9) Ignore external bodies=20
      10) Cut the number of AD's fewer people fewer arguments=20
     =20

	Olafur
PS: disclaimer I'm on NOMCOM so please volunteer=20
 =20=

From ajs@anvilwalrusden.com  Thu Oct 17 12:27:55 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 BFF1111E823D for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:27:55 -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 QwfyJ+7dhxBd for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:27:50 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 46F2E11E81A4 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:27:49 -0700 (PDT)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B3F9B8A031 for <ietf@ietf.org>; Thu, 17 Oct 2013 19:27:48 +0000 (UTC)
Date: Thu, 17 Oct 2013 15:27:47 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Message-ID: <20131017192747.GL1674@mx1.yitter.info>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5260334D.10806@dcrocker.net>
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, 17 Oct 2013 19:27:55 -0000

Dear colleagues,

Emphatically no hat.  

Dave,

On Fri, Oct 18, 2013 at 07:58:21AM +1300, Dave Crocker wrote:

> Nomcom can apply pretty much whatever criteria it wants to the
> selection process and Nomcom has been know to have some private
> negotiations with the IESG.  Nothing as profound as the change we
> are suggesting, but still...

I agree that the Nomcom can undertake such negotiations.  I wonder,
however, whether you really are suggesting that the Nomcom could make
this decision on its own, without even telling anyone it is using such
private criteria, and without the community breaking out the tar and
feathers on the future date when that news somehow comes out.  (More
succinctly, I guess, "Are you serious, or merely exaggerating?")

> So Nomcom could start things towards that change on its own.

As I read you, you're not saying "start change", but "implement a
change".  No?

Best, 

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From adrian@olddog.co.uk  Thu Oct 17 12:37:01 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 A9BB211E8152 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:37:00 -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.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 9Rh2QBbZdUbR for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:36:50 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 187C811E8191 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:36:44 -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 r9HJaYVB031130;  Thu, 17 Oct 2013 20:36:35 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9HJaXVj031118 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Oct 2013 20:36:33 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Peter Saint-Andre'" <stpeter@stpeter.im>, <dcrocker@bbiw.net>
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Date: Thu, 17 Oct 2013 20:36:31 +0100
Message-ID: <047e01cecb70$2f271830$8d754890$@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: Ac7LcCuQolnkf8FoSCunI18blkQaxg==
Content-Language: en-gb
Cc: 'John C Klensin' <john-ietf@jck.com>, 'IETF Discuss' <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, 17 Oct 2013 19:37:01 -0000

Hello,

> > The IESG defines the job and the IESG 'operates' the model.  So yes,
> > formally the IESG controls this issue.

Mutter.
I suppose the seated IESG defines what it does.
Or more precisely, each member of the IESG decides what (sadly) he should do to
best serve in the role.

But don't see the "job requirements" put out by NomCom as the IESG placing
requirements. 
The NomCom asks the IESG what skills and tasks are needed in the view of the
current IESG.
The IESG serves up this information and NomCom can do with it as it likes.

More important, the community can and should tell the NomCom what it wants the
IESG to do and not do.

> > However...
> >
> > Nomcom can apply pretty much whatever criteria it wants to the selection
> > process and Nomcom has been know to have some private negotiations with
> > the IESG.  Nothing as profound as the change we are suggesting, but
> > still...

Exactly.

> > It would be better for the IESG to take the initiative here and formally
> > and publicly re-define the job, but it has so far ignored such requests.

Which cuts into what Peter says since from where I sit there are many calls on
the time of an AD and it would be useful to know which tasks the community would
like me to not do (I think that I and my chief sponsor would both be happy if I
spent more time working for them and less working as an AD).
 
> It might be helpful to talk about what could change, such as:
> 
> 1. Less/no time on document reviews.

Right. Ask:
Do the reviews currently done by ADs make a difference to the quality of
individual documents or the overall canon?
Would we be happy to publish RFCs with lower quality?
Are there other ways to reliably improve the quality (like, for example, the
community doing proper reviews of their own work)?
Could discussions of Discusses go more smoothly and take less effort?

Note:
I spend more time (factor of more than 2) reviewing I-Ds when publication is
requested (from a WG) than I do reviewing at IESG evaluation.

> 2. Less time managing working groups.

Right. Ask:
Does the management of working groups improve the output?
Would we be happy to allow WGs to "muddle through"?
Could WG chairs somehow (magically?) take more responsibility and get stuff done
(some chairs do)?

Note:
A few of my WGs/chairs take most of my management time.
I don't put a lot of time into managing WGs unless something goes badly wrong.

> 3. Fewer working groups to manage.

Right. Ask:
Should an AD close a WG with a small number of people doing productive work
slowly?
Should we refuse to open new WGs until we have finished other work?
Could we reduce the number of WGs per AD by increasing the number of ADs?

Note:
Even if management of the WG is not issue, each WG produces documents to be
managed, so reducing the number does have a direct impact.

> 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).

Not sure that interfacing with SDOs is a big time drag.
But other things do eat into time.  These are mainly IETF management tasks.
Arguably this is what the IESG is for. If it isn't you had better tell us!

> 5. Less/no involvement with BoFs and other early-stage efforts.

Right. Ask:
Should BoF proponents be left to flounder or should an AD help them to get their
work going?
Is a BoF shepherd from the IAB enough?
Could other people from the community fill this role?

> 6. Less/no involvement with creating the schedule.

Frankly, with the new tooling, this doesn't take more than a few hours per IETF
meeting cycle.
And that does point up a good question to ask the IESG in general - what
additional tools could significantly reduce your work load?

> Perhaps some time and motion studies are in order to figure out how ADs
> spend their time. In my experience, document reviews required a major
> time commitment.

And, since I do track my time at quite a fine granularity...

Email takes up a large lump.
Got to skim the mailing lists for each of my WGs every week.
Got to skim the mailing lists for other WGs in my area every month.
Got to skim IETF-announce and IETF-disgust daily.
Another 15 or so IETF lists that I skim weekly.
A few related lists (such as NANOG) that I skim when I can.
Emails directed to me that need attention "at once".


Please don't assume we ADs want this to be full time work.
Please do tell us what you don't want us to do, and what you would like us to do
less.

Consider whether the "IETF management" could be separated from the "document
quality".

Cheers,
Adrian


From brian.e.carpenter@gmail.com  Thu Oct 17 12:37:59 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 1D93511E82E3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:37:59 -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 kGKzEb-g+Cz8 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:37:58 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id B566211E82C6 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:37:52 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id y13so3310067pdi.26 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:37:52 -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=TaI1RGJAtmZ4iwKlpnXloCD0b8mW3cxNJstnUQi6VME=; b=Cy+BeWFbB0l/ytgtG8ftmu9bcny5kKqnOE8uSEghysyVSOGJW4Yn9CWm6Mu69ibqAX TelBsfosUItxprin7T5kW96FQwCMqAhCjj8g7YKTzC4lHFUW/yq9fSegOkEZfoLDSpQO ReWd2nWR6vNMPBpKBgy9TNM6/T7cWmUbX1z5G2+xVX53Opbsdm+VBnDiD4WvCTnICULs /VAkegr1/FgDIX4j9G6YUaj9BHrPZlTLTztJ9hNc0bYeh5ZtWVyyF2yFpBebcxxN8QcK oSPNFdzhbwOpRf+Yma+2l91qp9/fh1Irb0RoDY8BwEb3amtP+MIirDAjKBpTMB/+hw/h 0oBw==
X-Received: by 10.66.139.100 with SMTP id qx4mr3184730pab.177.1382038672258; Thu, 17 Oct 2013 12:37:52 -0700 (PDT)
Received: from [192.168.178.20] (170.202.69.111.dynamic.snap.net.nz. [111.69.202.170]) by mx.google.com with ESMTPSA id q4sm99620414pba.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 12:37:51 -0700 (PDT)
Message-ID: <52603C96.2030409@gmail.com>
Date: Fri, 18 Oct 2013 08:37:58 +1300
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: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im>
In-Reply-To: <52603628.1080007@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:37:59 -0000

On 18/10/2013 08:10, Peter Saint-Andre wrote:
...
> It might be helpful to talk about what could change, such as:

I've inserted some ideas about how to make such changes possible.

> 1. Less/no time on document reviews.

1A. All WGs do a near-perfect job on their drafts, including
complete management of cross-area reviews.

1B. Lower the current bar of near-perfection for document approval.

1C. IESG is allowed to reject a document as "Not ready" without
detailed explanation.

> 2. Less time managing working groups.

2A. All WG Chairs to do a near-perfect job.

2B. Quickly replace failing WG Chairs.

2C. Summary closure of failing WGs.

> 3. Fewer working groups to manage.

3A. IESG refuses the majority of proposed WGs.

3B. See 2C.

> 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).

4A. Leave liaisons entirely to the designated liaison managers.

4B. Replace failing liaison managers. (IAB job)

4C. Simply refuse other extra tasks.

> 5. Less/no involvement with BoFs and other early-stage efforts.

5A. IAB spends less time on admin/politics and more time on Architecture,
including BOFs. Also see 3A.

> 6. Less/no involvement with creating the schedule.

[I'm not sure that will work. ADs are uniquely placed to
identify clashes and overlaps.]

   Brian

From john-ietf@jck.com  Thu Oct 17 12:41:38 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 E0FCD11E8191 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.585
X-Spam-Level: 
X-Spam-Status: No, score=-103.585 tagged_above=-999 required=5 tests=[AWL=0.014, 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 ZM1ltDIlGPcM for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:41:32 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 974DD11E8136 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:41:31 -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 1VWtRr-0003UV-F7; Thu, 17 Oct 2013 15:41:31 -0400
Date: Thu, 17 Oct 2013 15:41:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, IETF Discuss <ietf@ietf.org>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Message-ID: <69F14482F24C4FE7C4F58BDE@JcK-HP8200.jck.com>
In-Reply-To: <5260334D.10806@dcrocker.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:41:38 -0000

--On Friday, October 18, 2013 07:58 +1300 Dave Crocker
<dhc@dcrocker.net> wrote:

>...
> Nomcom can apply pretty much whatever criteria it wants to the
> selection process and Nomcom has been know to have some
> private negotiations with the IESG.  Nothing as profound as
> the change we are suggesting, but still...
> 
> So yes, an example of how Nomcom might independently deal with
> the current crisis is to announce a policy of looking for ADs
> who are willing to work no more than X% and then making a
> point of selecting such folk.
> 
> (Note that I'm saying something different from John.  He's
> caling for new folk who would "support" a change; I'm calling
> for new folk who are firm that they won't do more than X%.)

I am guessing that this problem, which took years to create,
would take some time to untangle and the effect of half the IESG
with a firm X% and "work to rule" commitment would either be
overloading the other half of the ADs and burning them out or
massive disruption as various groups jockeyed for priority.  So
I thought more in terms of firm commitments to start winding the
level of effort down to some future target rather than an
immediate limit (this is faintly reminiscent of different
proposals many years ago to put ceilings on the number of WGs --
agreement in principle, difference in methods for making the
transition).  

It occurs to me that, if X were pegged at a number much higher
than the ultimate target but somewhat lower then what we think
is going on today with the intention of lowering it further in
subsequent years, the two approaches might differ more in
principle than in practice.  

I note that the IESG has told the Nomcom (see the "A Few
Comments on the IESG Role" section of the "Desired Expertise"
sections on the Nomcom pages) that the "basic" activities
consume between 25 and 40 hours per week and then goes on to
talk about "approximately full-time" and "additional activities"
that "further increase the time commitment".   I also note that
three IETF meetings a year with travel and arrival a couple of
days early, plus a couple of retreats and associated travel, is
already 15-19% of a nominal FTE (circa 200 days a year) annual
commitment before any document reviews or other out-of-meeting
work is added in, so the "day a week or so" level that some of
us would like to see would require a _lot_ of changes and
adjustments.

My guess is that some current and recent IESG members would
consider a 40 hour a week average to be a significant reduction
in time commitment.  That is clearly much too high to also
expect someone to hold down serious day-job responsibilities,
but it might suggest 35-40 hours (whatever that is deemed to
mean in percentages) as an initial target under your X% proposal.

> It would be better for the IESG to take the initiative here
> and formally and publicly re-define the job, but it has so far
> ignored such requests.

Yes, although "ignored" might be too charitable.

> So Nomcom could start things towards that change on its own.

And there we agree, although I think that a responsible Nomcom
(and I hope all of them are and have been) would want to see a
significant show of support from the community for doing
something that might cause serious disruptions (and which I'm
sure some previous IESGs would insist _would_ cause serious
disruptions).

best,
   john


From Ted.Lemon@nominum.com  Thu Oct 17 12:46:25 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 5245F11E82E3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 KeM2mkqmOdq3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:46:13 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id E811811E81E1 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:46:11 -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 DSNKUmA+g0VE2DariAEjRnupIzEt1cTT8YNn@postini.com; Thu, 17 Oct 2013 12:46:12 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 AA4C91B82E4 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:46:11 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 8977019005C; Thu, 17 Oct 2013 12:46:11 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Oct 2013 12:46:11 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52603C96.2030409@gmail.com>
Date: Thu, 17 Oct 2013 15:46:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <5D67FA87-1789-4E0A-B241-03BA0A27E893@nominum.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:46:25 -0000

On Oct 17, 2013, at 3:37 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> 2B. Quickly replace failing WG Chairs.

You forgot "from a magical pool of better qualified WG chairs who have =
the time and inclination to take on the work."   This is actually very =
similar to the AD acquisition problem.

The IESG is actively interested in improving the situation (that is, =
reducing the workload).   We'd like document shepherds to take on more =
responsibility at the start, in the middle, and during the review =
process.   Sometimes we see glimmerings of this happening.

But the bottom line is that the IETF is an all-volunteer organization.   =
ADs wind up doing all the work because we've managed to convince our =
managers to let us do IETF work full-time-ish.   Finding people onto who =
to offload work who are both willing to do it and competent to do it is =
nontrivial.   Either one or the other isn't so hard; both is hard.


From brian.e.carpenter@gmail.com  Thu Oct 17 12:50: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 E8AAB11E8191 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:50:34 -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 Jj81BMJK8XyG for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:50:34 -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 B50D911E8150 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:50:30 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so2756333pbc.35 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:50:28 -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=2Q1y6MCV+uSbF6HsSUVuUMgN8rB9wCOmvgQIo3qVa/w=; b=STGwC9FVuRARvjIaEOXSyCw1fIZRvqzrabC+Ybz/jqfiN6zvx79/HgQmxiPkgA/Hv/ HjLuejy4DwvfuqfT2O/GlDC30A6xcBW3TD5HjpJuYJTrzOR1XkONpqzmYx8dPZa6dn3v XvtQtIM0TU3+pG1G0/ynOsHOh+bRTO0s8qXRrsBqF3SHM5A9JTxfVcrU7V2TkW9hbOXu K6mZ+7Ti6BpBe+Fs9siHQmOmf6NmSSqdOMHJ3qUGtOigFTcfELvmoS3fOzVcymTPETw8 5g6rBzWm4juKS8/O/a4faRfq1KPG1IUGBZT4Wz1WosCqhExRknueua93MOgUz9Sq0kSm PlrQ==
X-Received: by 10.68.225.164 with SMTP id rl4mr10358592pbc.100.1382039428728;  Thu, 17 Oct 2013 12:50:28 -0700 (PDT)
Received: from [192.168.178.20] (170.202.69.111.dynamic.snap.net.nz. [111.69.202.170]) by mx.google.com with ESMTPSA id tz3sm99649244pbc.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 12:50:28 -0700 (PDT)
Message-ID: <52603F8B.4060606@gmail.com>
Date: Fri, 18 Oct 2013 08:50:35 +1300
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: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net> <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com>
In-Reply-To: <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:50:35 -0000

On 18/10/2013 08:26, Olafur Gudmundsson wrote:
...
> some ideas to decrease the work load 
> 	1) Limit on working groups in each area 
> 	2) Less review of documents our outsource reviews
> 	3) Lower the voting threshold for document to pass

It's already pretty low, considering that one valid meaning
of 'No objection' is 'I trust the sponsoring AD'. That
option should perhaps be used more often.

> 	4) Reduce hurdles in processing

Please be specific.

> 	5) Assign tasks to different bodies

The problem with that is that more bodies need more volunteers,
so the problem is not guaranteed to go away. But as we've said
*many* times, truly delegating document review would make a big
difference.

> 	6) More competent WG chairs 
> 	7) Pick AD's that are less likely to nit pick documents
> 	8) ignore process nazi's and streamline process. 

Again, please be specific. For example, ignoring dissent and consensus
forming will generally speaking increase the workload in the long run.

> 	9) Ignore external bodies 

We can't. But we can insist that liaison is handled by the
liaison managers.

>       10) Cut the number of AD's fewer people fewer arguments 

You really can't do that without dramatically cutting the number
of WGs. If we had 50 WGs we'd have fewer ADs, or their workloads
would be much less.

     Brian

From stpeter@stpeter.im  Thu Oct 17 12:57:25 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 2A44911E82DB for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.345
X-Spam-Level: 
X-Spam-Status: No, score=-102.345 tagged_above=-999 required=5 tests=[AWL=0.254, 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 M+-GWq24u6MT for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:57:19 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 147CE11E82D3 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:57:19 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DE7394100F; Thu, 17 Oct 2013 14:03:42 -0600 (MDT)
Message-ID: <5260411C.1070403@stpeter.im>
Date: Thu, 17 Oct 2013 13:57:16 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net> <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com> <52603F8B.4060606@gmail.com>
In-Reply-To: <52603F8B.4060606@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>, 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, 17 Oct 2013 19:57:25 -0000

On 10/17/13 1:50 PM, Brian E Carpenter wrote:
> On 18/10/2013 08:26, Olafur Gudmundsson wrote:
> ...
>>       10) Cut the number of AD's fewer people fewer arguments 
> 
> You really can't do that without dramatically cutting the number
> of WGs. If we had 50 WGs we'd have fewer ADs, or their workloads
> would be much less.

I'm of the opinion that we have too many working groups. However, it's
hard for IETF participants (in which I include ADs) to build the
discipline to close non-performing WGs, reject proposals from folks who
earnestly want to do work (sometimes quite interesting work) at the
IETF, etc.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From brian.e.carpenter@gmail.com  Thu Oct 17 12:57: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 B815811E82DB for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 PXcEiMTH1uYb for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 12:57:28 -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 B3A5811E82D3 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:57:25 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ld10so891072pab.24 for <ietf@ietf.org>; Thu, 17 Oct 2013 12:57:25 -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=BE5z2MEECsEKIt0CIjenS4nd44rIO5tFvX1mIYBkpLc=; b=wnQDqiwf+NpNg/FlZ6vP6lnT/qvKBlcO/nD8g6SSW3a12fWpi25uhSQ7eaqNZt+N5o M9fda6sImpImOqGv/XgevuBJVudsL1O+NCcAEnvONxbPX7ft0SikcWjXesJn1wyXoE7t c4+OjCsURMxHK4j6Dv55W4gcLdSsOfTsopuLFks/Lu2RjO2nb3UNXezKz9ZTF7nI9Ccz FDjnaKkF9ao24XA/w9BlEdsjmJbmH9mbgZtfXIVMjNmq/EPtye9USSU9RlJTYId2Qvge WxW2//vdA9pSrpOwCU/VLSEvrdZIn8zTg2FFx5nyPa6GCKG4BOlk/kxYUZ7HsdfSzR7B CLEw==
X-Received: by 10.68.182.3 with SMTP id ea3mr10313745pbc.124.1382039845690; Thu, 17 Oct 2013 12:57:25 -0700 (PDT)
Received: from [192.168.178.20] (170.202.69.111.dynamic.snap.net.nz. [111.69.202.170]) by mx.google.com with ESMTPSA id lm2sm116636538pab.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 12:57:25 -0700 (PDT)
Message-ID: <5260412B.5070905@gmail.com>
Date: Fri, 18 Oct 2013 08:57:31 +1300
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: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com> <5D67FA87-1789-4E0A-B241-03BA0A27E893@nominum.com>
In-Reply-To: <5D67FA87-1789-4E0A-B241-03BA0A27E893@nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 19:57:28 -0000

On 18/10/2013 08:46, Ted Lemon wrote:
> On Oct 17, 2013, at 3:37 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 2B. Quickly replace failing WG Chairs.
> 
> You forgot "from a magical pool of better qualified WG chairs who have the time and inclination to take on the work."   This is actually very similar to the AD acquisition problem.
> 
> The IESG is actively interested in improving the situation (that is, reducing the workload).   We'd like document shepherds to take on more responsibility at the start, in the middle, and during the review process.   Sometimes we see glimmerings of this happening.
> 
> But the bottom line is that the IETF is an all-volunteer organization.   ADs wind up doing all the work because we've managed to convince our managers to let us do IETF work full-time-ish.   Finding people onto who to offload work who are both willing to do it and competent to do it is nontrivial.   Either one or the other isn't so hard; both is hard.

Yes, of course you're right. But if we're going to actually solve this
problem before we encounter a NomCom that says "Unfortunately we have
no willing nominees for the following seven positions", or maybe
"We have one nominee for each position, all employees of Foofle Inc.",
we really need to get a bit drastic.

"I have decided that since the Boofah WG has missed all milestones for
the past year and no alternative chairs are available, the WG will
now be closed."

   Brian

From Ted.Lemon@nominum.com  Thu Oct 17 13:05: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 7861D21F942D for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 UubnMloMpIsa for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:05:52 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8E13411E8104 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:05:51 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUmBDH5PRwYJF7hZeKxpGSeYsAtPwhJ1K@postini.com; Thu, 17 Oct 2013 13:05: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 1E2071B82B9 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:05:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 1546019005C; Thu, 17 Oct 2013 13:05:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Oct 2013 13:05:50 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5260412B.5070905@gmail.com>
Date: Thu, 17 Oct 2013 16:05:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7DCFBB7C-F983-4C53-A71B-A7BF84BED2B1@nominum.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com> <5D67FA87-1789-4E0A-B241-03BA0A27E893@nominum.com> <5260412B.5070905@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:05:58 -0000

On Oct 17, 2013, at 3:57 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> "I have decided that since the Boofah WG has missed all milestones for
> the past year and no alternative chairs are available, the WG will
> now be closed."

Yes, actually I think closing working groups is one of the knobs that =
needs to be turned more.   But it's not always simple, and it's not =
clear that that would get rid of enough work.

The knob that I most need to turn is my tendency to respond on mailing =
lists.   But people have told me that they appreciate it that I do (and =
other people have flamed me to a crisp for it).   What's the right =
answer?


From john-ietf@jck.com  Thu Oct 17 13:20:21 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 4A1F411E8180 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.586
X-Spam-Level: 
X-Spam-Status: No, score=-103.586 tagged_above=-999 required=5 tests=[AWL=0.013, 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 bh5zOUbqltCE for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:20:15 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EB03311E8188 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:20: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 1VWu3G-0003XI-7g; Thu, 17 Oct 2013 16:20:10 -0400
Date: Thu, 17 Oct 2013 16:20:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'Peter Saint-Andre' <stpeter@stpeter.im>, dcrocker@bbiw.net
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Message-ID: <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
In-Reply-To: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
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 Discuss' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:20:21 -0000

--On Thursday, October 17, 2013 20:36 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

>...
> But don't see the "job requirements" put out by NomCom as the
> IESG placing requirements. 
> The NomCom asks the IESG what skills and tasks are needed in
> the view of the current IESG.
> The IESG serves up this information and NomCom can do with it
> as it likes.
> 
> More important, the community can and should tell the NomCom
> what it wants the IESG to do and not do.
>...

Adrian,

First, we fundamentally agree, especially about the community
needing to prioritize what it is willing to have not done.

But that is where the comment that Dave, myself, and others have
made about the fate of earlier proposals to trim the job have
come in.  For example, either of the following would, I believe
and your note implies, significantly reduce the workload:

* Many years ago, there were some proposals to limit the number
of WGs to what could be effectively managed without growing the
IESG or turning it into a full-time job.  Those proposals had
some differences in the decision-making process and way of
imposing limits, but the basic ideas involved a higher creation
threshold, a ceiling on numbers,  and a fairly brutal attitude
toward non-performing WGs.  My recollection is that the fate of
both proposals is that the IESG simply refused to consider them
(but I could be wrong -- it has been a long time)

* Somewhat more recently, there were some proposals to take the
formal approval role away from the IESG and assign it to some
other body.  That would have eliminated the "review every
document and vote" part of the job description and the small
conflict involved in an AD being expected to both advocate for a
WG to the rest of the IESG and be the technical evaluator its
work of its work, replacing it with much more of a WG
management, oversight, and steering role.  That change would
also significantly reduce the requirement (or preference) that
each IESG member have significant expertise in two or three
areas in addition to her own and permit a tad more emphasis on
IESG management skills.  At least for the one of those proposals
I remember best, the IESG simply refused to consider it.

If the IESG thought those proposals were interesting at this
stage, I think the old I-Ds could be dug out, updated and
polished slightly, and posted before Monday's cutoff (I can make
that commitment for the two or three that have my name on them;
can't speak for Dave or others, but the IPR policy would, in
principle, permit anyone to retrieve those drafts and repost
them).  That would, at least in principle, permit some
discussion (perhaps even during the plenary) early enough to do
the Nomcom some good if the community and IESG actually seemed
interested.

To save an extra note...

--On Thursday, October 17, 2013 15:46 -0400 Ted Lemon
<ted.lemon@nominum.com> wrote:

> On Oct 17, 2013, at 3:37 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> 2B. Quickly replace failing WG Chairs.
> 
> You forgot "from a magical pool of better qualified WG chairs
> who have the time and inclination to take on the work."   This
> is actually very similar to the AD acquisition problem.

Actually, it isn't.  If the Nomcom can't find a satisfactory
person to serve as AD, we have a constitutional crisis of some
flavor.   If there isn't a candidate (or, if necessary two) who
is able to satisfactorily lead and manage a WG, that is, at
least IMO, _extremely_ strong evidence that there isn't
sufficient community interest in the WG and its work.    Lack of
available leadership is actually an easier criterion for
deciding to cut off a WG than considerations about milestones or
other differences between expectations about progress and
delivery.  I don't know how much work it would get rid of in
today's environment, but it would be a very effective way of
getting rid of situations in which the AD basically had to fill
in for disfunctional WG leadership.

In addition, at least as things are now formulated, an AD is
required to have the knowledge and interest to review documents
across areas and to manage multiple groups with different tasks
and objectives (more like departmental management skills than
project management ones) as well as to make commitments in
two-year units.  WG Chairs don't have any of those requirements:
unless the WG has been permitted to explode into a many-task,
many-document, virtual subarea, they should be able to finish a
set of closely related tasks and move on.

best,
   john


From ogud@ogud.com  Thu Oct 17 13:22:01 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 A52E721F9346 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:22:01 -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 EFdLdLuOZVMd for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:21:56 -0700 (PDT)
Received: from smtp118.ord1c.emailsrvr.com (smtp118.ord1c.emailsrvr.com [108.166.43.118]) by ietfa.amsl.com (Postfix) with ESMTP id F253911E8151 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:21:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id E32051B8297; Thu, 17 Oct 2013 16:21:49 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BB5781B8250;  Thu, 17 Oct 2013 16:21:48 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <52603F8B.4060606@gmail.com>
Date: Thu, 17 Oct 2013 16:21:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6535F401-9B6D-4C9B-B938-661CF325578E@ogud.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net> <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com> <52603F8B.4060606@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:22:01 -0000

On Oct 17, 2013, at 3:50 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 18/10/2013 08:26, Olafur Gudmundsson wrote:
> ...
>> some ideas to decrease the work load=20
>> 	1) Limit on working groups in each area=20
>> 	2) Less review of documents our outsource reviews
>> 	3) Lower the voting threshold for document to pass
>=20
> It's already pretty low, considering that one valid meaning
> of 'No objection' is 'I trust the sponsoring AD'. That
> option should perhaps be used more often.
>=20

idea: 3 Yes votes overwrite 1 Discuss=20

>> 	4) Reduce hurdles in processing
>=20
> Please be specific.

Charter updates take too long and take strange turns.=20
Easier to kill bad documents by outright=20
rejection of Publication Requests.=20
=20

>=20
>> 	5) Assign tasks to different bodies
>=20
> The problem with that is that more bodies need more volunteers,
> so the problem is not guaranteed to go away. But as we've said
> *many* times, truly delegating document review would make a big
> difference.

Well we have GenArt and Security review teams, they and similar bodies=20=

could do initial processing of Publication requests.=20

>=20
>> 	6) More competent WG chairs=20
>> 	7) Pick AD's that are less likely to nit pick documents
>> 	8) ignore process nazi's and streamline process.=20
>=20
> Again, please be specific. For example, ignoring dissent and consensus
> forming will generally speaking increase the workload in the long run.

We had the long standing down-ref problem, it went away, but something =
like that
keeps creeping up again and again. Someone say we can not do "X" because =
document "Y" says so.=20

>=20
>> 	9) Ignore external bodies=20
>=20
> We can't. But we can insist that liaison is handled by the
> liaison managers.

>=20
>>      10) Cut the number of AD's fewer people fewer arguments=20
>=20
> You really can't do that without dramatically cutting the number
> of WGs. If we had 50 WGs we'd have fewer ADs, or their workloads
> would be much less.

For example last years Nomcom had hard time to find a Transport AD,
why do all area's have to have 2 other than balance?=20

	Olafur



From Ted.Lemon@nominum.com  Thu Oct 17 13:48: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 E62E611E81EB for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 0v0VKpE8wlbi for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:48:45 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 472D611E814B for <ietf@ietf.org>; Thu, 17 Oct 2013 13:48:45 -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 DSNKUmBNLJZ5asMcI1ZV8LXfp8pLtIXfr/bI@postini.com; Thu, 17 Oct 2013 13:48:45 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 C25271B82B9 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:48:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 B76BD19005C; Thu, 17 Oct 2013 13:48:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Oct 2013 13:48:44 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
Date: Thu, 17 Oct 2013 16:48:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7CB5C492-AEAB-4542-8305-0C86ACDCA765@nominum.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:48:52 -0000

On Oct 17, 2013, at 4:20 PM, John C Klensin <john-ietf@jck.com> wrote:
> If there isn't a candidate (or, if necessary two) who
> is able to satisfactorily lead and manage a WG, that is, at
> least IMO, _extremely_ strong evidence that there isn't
> sufficient community interest in the WG and its work. =20

No, it's extremely weak evidence.   Being a good working group chair is =
a very different problem than being a technology proponent.   You might =
have a hundred technology proponents for a particular working group, =
none of whom would do a really good job as chair.   Or you might have =
five proponents, one of whom would be a fantastic chair.

Working group chairs are not raw material.   They are the result of =
growing in the organization, and they are an extremely valuable part of =
the organization.   Growing more working group chairs should be a =
serious priority of the IETF, and our failure to do this well is very =
much part of the AD overwork problem.


From Ted.Lemon@nominum.com  Thu Oct 17 13:50:22 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 BF3F721F8CCB for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 fYKbSkLcC++3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:50:16 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 293F811E828E for <ietf@ietf.org>; Thu, 17 Oct 2013 13:50:12 -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 DSNKUmBNfOWvc8Yfeb7nLIxBmE/A3cHM/DoQ@postini.com; Thu, 17 Oct 2013 13:50:12 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 423A91B82B9 for <ietf@ietf.org>; Thu, 17 Oct 2013 13:50:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 3B51F19005C; Thu, 17 Oct 2013 13:50:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Oct 2013 13:50:04 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <6535F401-9B6D-4C9B-B938-661CF325578E@ogud.com>
Date: Thu, 17 Oct 2013 16:50:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <503A9313-2961-4681-A449-BE00D5C9D53B@nominum.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net> <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com> <52603F8B.4060606@gmail.com> <6535F401-9B6D-4C9B-B938-661CF325578E@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:50:22 -0000

On Oct 17, 2013, at 4:21 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
> idea: 3 Yes votes overwrite 1 Discuss=20

Right now we block a document if there's an unaddressed comment the =
sponsoring AD thinks is important.   The idea that the IESG is voting is =
mistaken=97like the IETF, we operate on consensus.   And a DISCUSS is =
not a no, or shouldn't be.


From bclaise@cisco.com  Thu Oct 17 13:51:11 2013
Return-Path: <bclaise@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 ECD9711E8185 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.577
X-Spam-Level: 
X-Spam-Status: No, score=-10.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 cw8uACaWySdG for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 13:51:06 -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 8873421F995E for <ietf@ietf.org>; Thu, 17 Oct 2013 13:51:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1618; q=dns/txt; s=iport; t=1382043066; x=1383252666; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=HA5YUPOZlHur4iq9WA2D8P9HZM0bjIEsCwdVeOjiQ1A=; b=SVnk1GB3fk5/C+misIzX0mxtNj29pYydmdkRcp4j5ShFraFrpO76flXb 92qj8aMeUsZEbF5PN2GePrh4MHXPywREp5MYku3JqBUTBEGEt+L/8rnUT ShJN9+Qh+tjNf+twDF7nbronXy8YCqcMI/OgukCswGCy7QoFbbM0WiEAI w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkkFAMpMYFKQ/khN/2dsb2JhbABbgwe8GIJ6gSoWdIIlAQEBBB0bQAEQCxgJFg8JAwIBAgFFEwEHAQGIAsB0j1EHFoQQA5gGhjiLTIFmgUA6
X-IronPort-AV: E=Sophos;i="4.93,517,1378857600"; d="scan'208";a="87479985"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 17 Oct 2013 20:51:05 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9HKp0eu002741; Thu, 17 Oct 2013 20:51:02 GMT
Message-ID: <52604DB4.2050004@cisco.com>
Date: Thu, 17 Oct 2013 22:51:00 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net>
In-Reply-To: <52602DF7.3030207@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 20:51:12 -0000

On 17/10/2013 20:35, Dave Crocker wrote:
> On 10/18/2013 3:54 AM, Tim Chown wrote:
>> I believe the "intense service" you mention is a significant 
>> deterrent for many.
>>
>> I'm sure it's been suggested before, but is there mileage in 
>> rethinking the
>> AD roles,
>
>
> It has been suggested many times.  The suggestion has been ignored.
>
> We have been having some very serious recruitment problems for a 
> number of years now.  This year's crisis was entirely predictable.
>
> The only way the situation will change meaningfully is to make the job 
> less onerous, and especially make it possible for the AD to continue 
> doing real work for their company.
>
> ADs are senior folk.  That makes them a strategic resource for their 
> company.  Or, at least, they'd better be.  Only very large companies 
> can afford to lose a strategic resource for years.
>
> Looking for alternative funding does not make the job less onerous and 
> does not permit the AD to continue doing real work for their company.
>
> Re-define the bloody job.  At a minimum, make the workload 
> realistically no more than 50%, but I actually suggest trying for 25%, 
> given that reality will increase the actual amount above that.
Agreed.
One positive initiative implemented a few months ago is the addition of 
the document shepherd to the IESG telechat.
Personally, this helps me a lot.

Regards, Benoit
>
> This means taking the current list of AD tasks and deciding on the 
> ones that absolutely cannot be done by others, and specifying other 
> ways to do the remainder.
>
> d/
>
>


From john-ietf@jck.com  Thu Oct 17 14:00:47 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 8879111E8121 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.587
X-Spam-Level: 
X-Spam-Status: No, score=-103.587 tagged_above=-999 required=5 tests=[AWL=0.013, 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 VRyX3PzVobP1 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:00:41 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D01BD11E8188 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:00:31 -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 1VWugH-0003ag-FQ; Thu, 17 Oct 2013 17:00:29 -0400
Date: Thu, 17 Oct 2013 17:00:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for	Nominations)
Message-ID: <6F871969D968C37C37EB79F2@JcK-HP8200.jck.com>
In-Reply-To: <52603F8B.4060606@gmail.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <6C855D8B-AA25-4C4C-8E23-ADB693577785@ogud.com> <52603F8B.4060606@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 Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 21:00:47 -0000

--On Friday, October 18, 2013 08:50 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 18/10/2013 08:26, Olafur Gudmundsson wrote:
> ...
>> some ideas to decrease the work load 
>> 	1) Limit on working groups in each area 
>> 	2) Less review of documents our outsource reviews
>> 	3) Lower the voting threshold for document to pass
> 
> It's already pretty low, considering that one valid meaning
> of 'No objection' is 'I trust the sponsoring AD'. That
> option should perhaps be used more often.

Not if we think that careful, competent, cross-area review is
important.  If we were ever to decide that we didn't, there are
a whole lot of ways to reduce the workload, starting with
eliminating IETF Last Call and the need to read all of those
often-noisy and repetitious messages.

   john




From jari.arkko@piuha.net  Thu Oct 17 14:17: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 6A59611E81BD for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.318
X-Spam-Level: 
X-Spam-Status: No, score=-101.318 tagged_above=-999 required=5 tests=[AWL=-1.251, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 2XCMAoiiz574 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:16:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F33C611E81DC for <ietf@ietf.org>; Thu, 17 Oct 2013 14:16:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 44CD02CC64 for <ietf@ietf.org>; Fri, 18 Oct 2013 00:16: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 BwRCRt-SsS8n for <ietf@ietf.org>; Fri, 18 Oct 2013 00:16:56 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 992D62CC48 for <ietf@ietf.org>; Fri, 18 Oct 2013 00:16:56 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52602DF7.3030207@dcrocker.net>
Date: Fri, 18 Oct 2013 00:16:56 +0300
Cc: IETF Discuss <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 21:17:03 -0000

I have some opinions about this, not to the mistaken for the IESG's or =
IETF's official opinions.

First off, I think we should be very careful when thinking about funding =
models. I like an IETF where people come to do stuff (write docs for =
themselves and others, chair WGs, work as ADs, =85) because it is useful =
for themselves and their employers - directly or indirectly, short term =
or long term, but there needs to be a reason we all are here. A =
desirable feature of a funding model is to help direct efforts to =
directions that are actually useful for the world. This is not to say =
that it would be the only desirable feature of a funding model, we have =
serious problems with academic participation, for instance. And we have =
too many situations where we only have large companies involved. But I =
could also imagine funding models that would support ADs but would move =
IETF towards doing things that are not tied to real world and real =
Internet problems. But it is possible there is a useful middle ground.=20=


Secondly, we've talked about this in the IESG and the community last =
spring when we had only one TSV AD for a while. My read of the situation =
is that reducing the task to a better manageable one is the most =
reasonable course of action. It would also solve many of the undesirable =
aspects of the funding model. I can only agree with Adrian who said:

> Please don't assume we ADs want this to be full time work.

Thirdly, if you are considering volunteering for an AD task, please do =
not feel that you need to be limited by current operating models. The AD =
is a management position, and we expect managers to have an idea how to =
run things, often better than what has been done previously. For =
instance, several ADs make extensive use of directorates in their review =
tasks, for instance several Gen ADs have traditionally relied almost =
entirely on directorate help (at least unless problems show up in review =
of a document). Other ADs do this too, though to a lesser extent due to =
a different type of their task. But for all of these positions, if you =
have an idea how to run it best - please volunteer and expect to get a =
lot of latitude to run your area how you see best!

Fourth, the IESG's desirable qualifications are just our opinions, and =
the nomcom needs to decide what type of people the IETF really needs. =
Hopefully that is the kind of people that I referred to above that know =
how to organise their and others work in an efficient manner! And the =
areas are largely run by the ADs very independently. The IESG does =
control things like how we run the common things, the tele chats, and we =
do control how many areas there are. If it helped to increase or reduce =
the number of ADs, we'd do it in a heartbeat. However, the quick =
solution of getting additional ADs to share tasks more widely is not =
necessarily good either, because the overall team size would grow, with =
the inter-IESG coordination becoming harder. I think we are already at a =
practical limit. Shrinking the IESG might make us think harder about =
what tasks really are absolutely necessary :-)

Finally, I'll agree with Ted:

> You forgot "from a magical pool of better qualified WG chairs who have =
the time and inclination to take on the work."   This is actually very =
similar to the AD acquisition problem.

My conclusion is that (a) IETF that does useful things on a timely basis =
will naturally attract people to do the work and (b) a big part of the =
responsibility is in the IESG's and individual AD's hands - if the =
manager doesn't manage his or hers work efficiently, then it is the =
manager's fault.

As to how to implement (b): I think it is natural that as organisations =
do more (and we do quite a bit, and have been for a long time) the =
management needs to give up on managing all details, and have to spend =
more of their time in finding the good coders than fixing the bugs in =
the code themselves :-) Delegate. Focus on the strategic things. Yeah, =
maybe easier said than done.

Jari


From barryleiba.mailing.lists@gmail.com  Thu Oct 17 14:47:41 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 5763711E81DE for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level: 
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=-0.007, BAD_CREDIT=0.001, 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 JdAm44JJ8PC3 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:47:41 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A47A111E8188 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:47:40 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id ev20so2609lab.39 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=y9+zZLOAWNrw3mnDqkdHtA0RxZW6dEk/f3XeOfA3IK8=; b=NQnzqfxHEm6iLQiBcJa53bSG9J3cDfetEuQa6QjxPEAX3DXLlK5JOCYpc8z8QiWI6E 3cKjfzzOO2ojjjRbpTAzDU4qF3Foeohhb4aipdFl3NHgukjFhYoGprJyyG230kBF2Lx8 w2HKPepgrQDvbk5A5oK5MSggpmV4gKouhazeVKoTpIIGXJbxqINqQXMLRNqZHs4aJiXO PzCWPhC/DqaCRlPgEAHXJ8JmKbGI/LFSI5spLiEkw6GbXuH54daDGBlOng/HOummLWkq zi7st4LTuVAKQFvYm3F/7J+3OM2Lr5PsMmF61rwMngEDXTALKay95NpNqJMsNSZdcQ+D j+1Q==
MIME-Version: 1.0
X-Received: by 10.112.132.70 with SMTP id os6mr78788lbb.38.1382046454060; Thu, 17 Oct 2013 14:47:34 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Thu, 17 Oct 2013 14:47:34 -0700 (PDT)
Date: Thu, 17 Oct 2013 17:47:34 -0400
X-Google-Sender-Auth: 16jaXZ4eRyrNHNkGZ-DDjFgeEF8
Message-ID: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Barry Leiba <barryleiba@computer.org>
To: IETF Discuss <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, 17 Oct 2013 21:47:41 -0000

Ted says, with respect to "Quickly replace failing WG Chairs":
> You forgot "from a magical pool of better qualified WG chairs who
> have the time and inclination to take on the work."

Let me tell you about a conversation I had when I was trying to fill a
chair position: I asked someone I thought could and would do a good
job as chair.  She was also a proponent of the technology, and wanted
to be a document author.  In response to, "Why not be a chair, and
lead the effort?", part of her answer was something like this:

"I work for a small company.  Whatever work I do on this takes away
from what I do for them, and they want to see something tangible from
it.  If I'm (co-)author on a document, my name, and my company's is at
the top of the document.  I get credit for the work.  My company gets
credit for the work.

"If I'm a working group chair, I do more work, overall.  And, in the
end, I get no credit for it -- my name is not on any of the documents.
 And, significantly, my company gets no credit for it whatsoever, not
even listed in the datatracker.

"When I go to my boss and give him the alternatives, I know which he'll pick."

Barry

From brian.e.carpenter@gmail.com  Thu Oct 17 14:49:31 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 8C3D111E8192 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 kR-TQn7pSHDM for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:49:31 -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 7785711E8188 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:49:30 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so2890169pbc.31 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:49:20 -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=t+Elt+vW9gW3uR7OGlOyj3md4wq4dRYv1I4v7Fc8hb0=; b=PWGAiZ7FkbN9xB9hToukd7fnKR9oVgj3tUSgGiUpByCGwSaWtlPY8vu/MXQ+A8c/bK /OOeB6EdyJUtmvK+wHgo6sit8G5eHb+WuFrN51oHPUxTZHVJuzDSRda7IG+qEoldnKaE 1+qWMSibDO9UJ/K8tJyl/dW9NftpPK1c4T2Tsynm7l47gaSbFVVzV6CY6g+fTepBWCtD sYj5ggzNkp6BQkvkcsSOZgb/nYDkxB/2KC0yDT/Rn2K15xQ2dmSEfFo3Vfa+Vscp3IuB oT2rqiCgAjDrAhjXlqSUhOQ+ryPj/lUXTbVC6ds1iQGFHnDaSADVVkwjzkGEwZaHI8py lmHQ==
X-Received: by 10.68.25.170 with SMTP id d10mr10797399pbg.78.1382046560647; Thu, 17 Oct 2013 14:49:20 -0700 (PDT)
Received: from [192.168.178.20] (170.202.69.111.dynamic.snap.net.nz. [111.69.202.170]) by mx.google.com with ESMTPSA id sb9sm100049742pbb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Oct 2013 14:49:19 -0700 (PDT)
Message-ID: <52605B68.10406@gmail.com>
Date: Fri, 18 Oct 2013 10:49:28 +1300
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 Discuss <ietf@ietf.org>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com>
In-Reply-To: <52603C96.2030409@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: Thu, 17 Oct 2013 21:49:31 -0000

It's been suggested to me off list that this message came across as
sarcastic. That was absolutely not my intention. I though Peter's list
was thoughtful and I think that only drastic changes of how we work
can seriously tackle the problem.

I've been quite shocked recently by the number of substantive and
important comments the IESG has made on a couple of drafts I've been
involved in. The documents will be much better as a result, but all
these points really should have been picked up earlier. See 1A
and 1C below, or 1B if you prefer.

Regards
   Brian

On 18/10/2013 08:37, Brian E Carpenter wrote:
> On 18/10/2013 08:10, Peter Saint-Andre wrote:
> ...
>> It might be helpful to talk about what could change, such as:
> 
> I've inserted some ideas about how to make such changes possible.
> 
>> 1. Less/no time on document reviews.
> 
> 1A. All WGs do a near-perfect job on their drafts, including
> complete management of cross-area reviews.
> 
> 1B. Lower the current bar of near-perfection for document approval.
> 
> 1C. IESG is allowed to reject a document as "Not ready" without
> detailed explanation.
> 
>> 2. Less time managing working groups.
> 
> 2A. All WG Chairs to do a near-perfect job.
> 
> 2B. Quickly replace failing WG Chairs.
> 
> 2C. Summary closure of failing WGs.
> 
>> 3. Fewer working groups to manage.
> 
> 3A. IESG refuses the majority of proposed WGs.
> 
> 3B. See 2C.
> 
>> 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).
> 
> 4A. Leave liaisons entirely to the designated liaison managers.
> 
> 4B. Replace failing liaison managers. (IAB job)
> 
> 4C. Simply refuse other extra tasks.
> 
>> 5. Less/no involvement with BoFs and other early-stage efforts.
> 
> 5A. IAB spends less time on admin/politics and more time on Architecture,
> including BOFs. Also see 3A.
> 
>> 6. Less/no involvement with creating the schedule.
> 
> [I'm not sure that will work. ADs are uniquely placed to
> identify clashes and overlaps.]
> 
>    Brian
> 

From cabo@tzi.org  Thu Oct 17 14:59:37 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 A879311E827B for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.166
X-Spam-Level: 
X-Spam-Status: No, score=-106.166 tagged_above=-999 required=5 tests=[AWL=0.082, BAD_CREDIT=0.001, 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 BK88j7nNydNC for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 14:59:31 -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 12BB811E82B0 for <ietf@ietf.org>; Thu, 17 Oct 2013 14:59:25 -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 r9HLxNT3028505; Thu, 17 Oct 2013 23:59:23 +0200 (CEST)
Received: from [192.168.217.105] (p54892BCF.dip0.t-ipconnect.de [84.137.43.207]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 1D7BED9D; Thu, 17 Oct 2013 23:59:23 +0200 (CEST)
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
Date: Thu, 17 Oct 2013 23:59:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1510)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 21:59:37 -0000

On Oct 17, 2013, at 23:47, Barry Leiba <barryleiba@computer.org> wrote:

> "If I'm a working group chair, I do more work, overall.  And, in the
> end, I get no credit for it -- my name is not on any of the documents.
> And, significantly, my company gets no credit for it whatsoever, not
> even listed in the datatracker.

This.

(Fortunately for me, in the WGs I have chaired, I actually did =
(co-)write some of the documents.
But it often was an uphill battle to get my name on them, because WG =
chairs are not supposed to do that.  Even when there are multiple =
chairs, who could very well watch each other.  Well, RFC 3095 had both =
chairs on the document... and 14 more authors.)

Other groups, such as IEEE, list the chairs of a group prominently (as =
such); they are worse in identifying the authors though.

Gr=FC=DFe, Carsten


From stephen.farrell@cs.tcd.ie  Thu Oct 17 15:08:27 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 28D1711E8192 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:08:27 -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.031, BAD_CREDIT=0.001, 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 Lnf8Y3V8dEfY for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:08:21 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6B21A11E81EB for <ietf@ietf.org>; Thu, 17 Oct 2013 15:08:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4C059BE87; Thu, 17 Oct 2013 23:08:15 +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 0gbFrYxIranF; Thu, 17 Oct 2013 23:08:14 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.42.23.232]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6C780BE88; Thu, 17 Oct 2013 23:08:13 +0100 (IST)
Message-ID: <52605FCD.8000709@cs.tcd.ie>
Date: Thu, 17 Oct 2013 23:08:13 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>
In-Reply-To: <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 22:08:27 -0000

On 10/17/2013 10:59 PM, Carsten Bormann wrote:
> On Oct 17, 2013, at 23:47, Barry Leiba <barryleiba@computer.org>
> wrote:
> 
>> "If I'm a working group chair, I do more work, overall.  And, in
>> the end, I get no credit for it -- my name is not on any of the
>> documents. And, significantly, my company gets no credit for it
>> whatsoever, not even listed in the datatracker.
> 
> This.
> 
> (Fortunately for me, in the WGs I have chaired, I actually did
> (co-)write some of the documents. But it often was an uphill battle
> to get my name on them, because WG chairs are not supposed to do
> that.  Even when there are multiple chairs, who could very well watch
> each other.  Well, RFC 3095 had both chairs on the document... and 14
> more authors.)
> 
> Other groups, such as IEEE, list the chairs of a group prominently
> (as such); they are worse in identifying the authors though.

Chairs, shepherds, wg secretaries etc etc. I don't think
attribution in RFCs is a great way to do that unless its
done as acks the authors decide themselves they want to
include.

And I also think chairs being authors is a bad plan for
any controlversial wg.

I do agree that some credit for chairs in particular would
be a fine thing if we could figure a way to do it though.

For example, I'd encourage authors to include acks as per
the above, in particular for cases of 'difficult' wgs.

Any other ideas?

S.


> 
> Grüße, Carsten
> 
> 
> 

From dave@cridland.net  Thu Oct 17 15:09:38 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 1835B11E82B0 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:09:36 -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 CxEMH0GzH7bq for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:09:35 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4B13B11E8285 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:09:30 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id y6so2410059lbh.7 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:09: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=1TCH9ai4ajQrRPAlWXYD+MZ+nO/DLoMV9rzMNnAfjmo=; b=GxxH3waXVXnAdzvozENgmekm9fCna5Ia/nBdrrof8zRf/jFu27rH2R8pr0qyYd5VvQ 1/JBUr51PRpKg2npndl5rA1dxFaWRBT3M8AF6lIEC+TWQuLSBZqVKcS2LDbtQy6ozVyh 4TP5qaKZ0bdoNhiGL/XAU5gDR3oMNAeD243nk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1TCH9ai4ajQrRPAlWXYD+MZ+nO/DLoMV9rzMNnAfjmo=; b=ErC6ynXKZYR7XNMapqCD02GMgZ9xPavY4GpqWmQieOuDoLgVgiB96exB2NMCKVZdFH QHA6/ikyhSWL8Ry6zieNzkAuW9UyhtxBHPCpexAQ7gQMp/MXgL+kvUBoni7H9Q9yxlES 9bscv0NDXIfxC2VY/nMN4Ttf7Gd4F0Vf5JyQtSmoVuByZ9nlOSRNiZDT2TZSjEmAHlQq 8OeA1l3QA1atuJy7b4wCjqvOi4G/mBOmrldsTPvdMZi/WOybyXXHBo9Al6eTGxZ3njAa eCjCA9JwJ7QbcVxWO+Z440vz8fUK+zhmXQGRiu7RPQHGK0i7MfeRac9jvdtteGyrx8qo zcJA==
X-Gm-Message-State: ALoCoQkyxtEbgfsW7XhEiV4chcXZfMwfXu3Rw8k/moFnk8xvUb0zajU1jDBx3D7hHpwrU1q5EbuK
MIME-Version: 1.0
X-Received: by 10.152.28.7 with SMTP id x7mr29362lag.26.1382047769165; Thu, 17 Oct 2013 15:09:29 -0700 (PDT)
Received: by 10.114.183.47 with HTTP; Thu, 17 Oct 2013 15:09:29 -0700 (PDT)
Received: by 10.114.183.47 with HTTP; Thu, 17 Oct 2013 15:09:29 -0700 (PDT)
In-Reply-To: <F2FD96A5-F26F-481B-AC9C-7A2EE16DD665@bogus.com>
References: <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <CAKHUCzy3tVnxkU8k-i=VtvBt9ze4d8o6bx_a=eu29UjdHLWvVw@mail.gmail.com> <F2FD96A5-F26F-481B-AC9C-7A2EE16DD665@bogus.com>
Date: Thu, 17 Oct 2013 23:09:29 +0100
Message-ID: <CAKHUCzy5FFR6kQiCCxNBr6x3toEz_RsoVe9mqpTDdVV76b9OXQ@mail.gmail.com>
Subject: Re: NOMCOM - Time-Critical - Final Call for Nominations
From: Dave Cridland <dave@cridland.net>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=089e0160bf705811f904e8f712c1
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "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, 17 Oct 2013 22:09:38 -0000

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

On 17 Oct 2013 12:26, "joel jaeggli" <joelja@bogus.com> wrote:
>
>
> On Oct 17, 2013, at 9:02 AM, Dave Cridland <dave@cridland.net> wrote:
> > The only solution allowing independents to become an AD that I can see
would be for larger companies to partially or wholly sponsor slots and/or
particular individuals. If this were to happen, I think we'd get both more,
and more diverse, nominations; but I appreciate that like John's
suggestions, mine is unlikely to solve the problem this time around.
>
> At the point where we pay people to occupy the role the nature of it
changes dramatically.

I hadn't thought about "we" paying, but I did think that organizations
sponsoring a slot, rather than an individual, would be better. That would
involve no influence over who was picked, even.

That said, I've no evidence that this would solve the problem anyway; it's
merely guesswork on my part, knowing that there exist good candidates who
are either self employed, or who do not have their employer's consent to
remain employed while being an AD.

Dave.

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

<p dir=3D"ltr"><br>
On 17 Oct 2013 12:26, &quot;joel jaeggli&quot; &lt;<a href=3D"mailto:joelja=
@bogus.com">joelja@bogus.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2013, at 9:02 AM, Dave Cridland &lt;<a href=3D"mailto:dave@=
cridland.net">dave@cridland.net</a>&gt; wrote:<br>
&gt; &gt; The only solution allowing independents to become an AD that I ca=
n see would be for larger companies to partially or wholly sponsor slots an=
d/or particular individuals. If this were to happen, I think we&#39;d get b=
oth more, and more diverse, nominations; but I appreciate that like John&#3=
9;s suggestions, mine is unlikely to solve the problem this time around.<br=
>

&gt;<br>
&gt; At the point where we pay people to occupy the role the nature of it c=
hanges dramatically.</p>
<p dir=3D"ltr">I hadn&#39;t thought about &quot;we&quot; paying, but I did =
think that organizations sponsoring a slot, rather than an individual, woul=
d be better. That would involve no influence over who was picked, even.</p>

<p dir=3D"ltr">That said, I&#39;ve no evidence that this would solve the pr=
oblem anyway; it&#39;s merely guesswork on my part, knowing that there exis=
t good candidates who are either self employed, or who do not have their em=
ployer&#39;s consent to remain employed while being an AD.</p>

<p dir=3D"ltr">Dave.</p>

--089e0160bf705811f904e8f712c1--

From cabo@tzi.org  Thu Oct 17 15:14:34 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 E2FE821F9A59 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.169
X-Spam-Level: 
X-Spam-Status: No, score=-106.169 tagged_above=-999 required=5 tests=[AWL=0.080, 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 xRQsKLzEB5yT for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:14: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 1AE2A21F9A45 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:14:26 -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 r9HMDkK3027594; Fri, 18 Oct 2013 00:13:46 +0200 (CEST)
Received: from [192.168.217.105] (p54892BCF.dip0.t-ipconnect.de [84.137.43.207]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C22FCDA9; Fri, 18 Oct 2013 00:13:45 +0200 (CEST)
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <52605FCD.8000709@cs.tcd.ie>
Date: Fri, 18 Oct 2013 00:13:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E28ED248-5176-40DA-AC5F-162B80A74309@tzi.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1510)
Cc: Barry Leiba <barryleiba@computer.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 22:14:35 -0000

On Oct 18, 2013, at 00:08, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

> Any other ideas?

Sure. =20

Create memento pages for each chair that lists the RFCs that chair was =
responsible for.

Like Jari's authorstats.
(Probably even harder to mine from the data we have.)

Gr=FC=DFe, Carsten


From sm@elandsys.com  Thu Oct 17 15:15:31 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 29FD611E81C7 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.234
X-Spam-Level: 
X-Spam-Status: No, score=-102.234 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 eTFrmCS5msIp for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:15:22 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id 76F2C21F83E2 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:15:19 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.142.243]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9HMEk7Q016568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Oct 2013 15:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382048110; bh=1O9nLuZGJTRDao003vs0wyvZvrUccwyhWGmunzi71co=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SrNOpKU9WHqv2gx0gREM/7IJGJSqFNJkfiXjtuzoi+8MFdjHx9osEXFCMj+IbgMkW Q8B0RuFNjCfAQ1fup7z9LGHQao2vr8Or1LoniczPQmDWCBdwmwXYEVv+9CAsR1Iixi oWo4Cdf0n7X3+j1L4fgKUGVuYudw87FK+a+DsB/8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382048110; i=@elandsys.com; bh=1O9nLuZGJTRDao003vs0wyvZvrUccwyhWGmunzi71co=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZHKpLBeAirimKizVmzWcgFypY94Gk3fngwfcbiJZ442K4IDnvNsN0xA13dIxvX2Ky Uj70iZx1hbBts2HgkOPTyus/mJny8QfYidr2BAPdTl2+1kzjA6dvUXoFeAv9g6Wfyb mPKeNro15FW8gvaklVANvlkZFm35NQtwQrtfazmY=
Message-Id: <6.2.5.6.2.20131017133143.06d48790@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Oct 2013 15:14:05 -0700
To: adrian@olddog.co.uk, Ted Lemon <ted.lemon@nominum.com>, Olafur Gudmundsson <ogud@ogud.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
In-Reply-To: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, 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: Thu, 17 Oct 2013 22:15:31 -0000

At 12:36 17-10-2013, Adrian Farrel wrote:
>Right. Ask:
>Do the reviews currently done by ADs make a difference to the quality of
>individual documents or the overall canon?

The short answer is yes.  It also ends up as more work for the Area Director.

>Would we be happy to publish RFCs with lower quality?

Yes.

>Are there other ways to reliably improve the quality (like, for example, the
>community doing proper reviews of their own work)?

Yes, there is a DISCUSS position which can be invoked. :-)

>Could discussions of Discusses go more smoothly and take less effort?

Yes.  A discussion of a DISCUSS should not generate more mail to iesg@.

>Could WG chairs somehow (magically?) take more responsibility and 
>get stuff done
>(some chairs do)?

If I was a working group chair under your responsibility and you did 
not expect me to get stuff done, I don't have any reason to get stuff done.

>Note:
>A few of my WGs/chairs take most of my management time.

There was a very good WG secretary in your area.  If it was my call I 
would have him doing an EDU tutorial.

>Should an AD close a WG with a small number of people doing productive work
>slowly?

Yes.

>Should we refuse to open new WGs until we have finished other work?

Yes, as it affects scheduling.

>Could we reduce the number of WGs per AD by increasing the number of ADs?

No, that would generate too many DISCUSSes. :-)

>Should BoF proponents be left to flounder or should an AD help them 
>to get their
>work going?

Somebody would have to help them.  It does not have to be an Area Director.

>Is a BoF shepherd from the IAB enough?

No, see above.

>Could other people from the community fill this role?

Yes.  Note that taking the same people and giving them more work is a 
good reason not to volunteer.

>Please do tell us what you don't want us to do, and what you would 
>like us to do
>less.

I would like you to work 20 hours a week instead of 80 hours a 
week.  If you ask me whether you can work 21 hours a week because the 
fate of the free world depends on it, my answer would be "no".

At 12:46 17-10-2013, Ted Lemon wrote:
>workload).   We'd like document shepherds to take on more 
>responsibility at the start, in the middle, and during the review 
>process.   Sometimes we see glimmerings of this happening.

Area Directors can do something about the above. :-)

At 13:21 17-10-2013, Olafur Gudmundsson wrote:
>For example last years Nomcom had hard time to find a Transport AD,
>why do all area's have to have 2 other than balance?

There is a wide breath of technologies for an area.  There is a low 
probability that a person can have the area-wide expertise.  Having 
two persons also means that if one person misses the issue the other 
person might catch it.

At 13:48 17-10-2013, Ted Lemon wrote:
>Working group chairs are not raw material.   They are the result of 
>growing in the organization, and they are an extremely valuable part 
>of the organization.   Growing more working group chairs should be a 
>serious priority of the IETF, and our failure to do this well is 
>very much part of the AD overwork problem.

Yes.  It is not possible to grow people overnight.  The educational 
efforts would benefit from a serious review.

Regards,
S. Moonesamy 


From l.wood@surrey.ac.uk  Thu Oct 17 15:19:55 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 95BAB21F8FE5 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.938
X-Spam-Level: 
X-Spam-Status: No, score=-3.938 tagged_above=-999 required=5 tests=[AWL=-0.341, BAD_CREDIT=0.001, 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 4YqpDFF4qFLp for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:19:50 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.166]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB2E11E8192 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:19:47 -0700 (PDT)
Received: from [195.245.230.131:6572] by server-6.bemta-3.messagelabs.com id EA/7F-23777-28260625; Thu, 17 Oct 2013 22:19:46 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-78.messagelabs.com!1382048386!25944102!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9625 invoked from network); 17 Oct 2013 22:19:46 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-16.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 17 Oct 2013 22:19:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.148]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 17 Oct 2013 23:19:45 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <cabo@tzi.org>, <barryleiba@computer.org>
Date: Thu, 17 Oct 2013 23:15:27 +0100
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Thread-Topic: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Thread-Index: Ac7LhYKowMG+jaAlRnakzRuW7zRxmQAAN/Bc
Message-ID: <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>, <52605FCD.8000709@cs.tcd.ie>
In-Reply-To: <52605FCD.8000709@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="iso-8859-1"
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, 17 Oct 2013 22:19:55 -0000

Taking it a step further, as far as getting credit goes, being on the IESG =
is pretty much the same as not
participating in the IETF at all. But it's a lot more work. No-one gets cre=
dit for reviewing; that's why academia
leaves it to grad students.

Chairs being authors, and thus taking a detailed technical position, can of=
ten be very bad for workgroup output.


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: 17 October 2013 23:08
To: Carsten Bormann; Barry Leiba
Cc: IETF Discuss
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE  =
     THE JOB)

On 10/17/2013 10:59 PM, Carsten Bormann wrote:
> On Oct 17, 2013, at 23:47, Barry Leiba <barryleiba@computer.org>
> wrote:
>
>> "If I'm a working group chair, I do more work, overall.  And, in
>> the end, I get no credit for it -- my name is not on any of the
>> documents. And, significantly, my company gets no credit for it
>> whatsoever, not even listed in the datatracker.
>
> This.
>
> (Fortunately for me, in the WGs I have chaired, I actually did
> (co-)write some of the documents. But it often was an uphill battle
> to get my name on them, because WG chairs are not supposed to do
> that.  Even when there are multiple chairs, who could very well watch
> each other.  Well, RFC 3095 had both chairs on the document... and 14
> more authors.)
>
> Other groups, such as IEEE, list the chairs of a group prominently
> (as such); they are worse in identifying the authors though.

Chairs, shepherds, wg secretaries etc etc. I don't think
attribution in RFCs is a great way to do that unless its
done as acks the authors decide themselves they want to
include.

And I also think chairs being authors is a bad plan for
any controlversial wg.

I do agree that some credit for chairs in particular would
be a fine thing if we could figure a way to do it though.

For example, I'd encourage authors to include acks as per
the above, in particular for cases of 'difficult' wgs.

Any other ideas?

S.


>
> Gr=FC=DFe, Carsten
>
>
>

From stpeter@stpeter.im  Thu Oct 17 15:20:49 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 2B5A111E82B4 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.355
X-Spam-Level: 
X-Spam-Status: No, score=-102.355 tagged_above=-999 required=5 tests=[AWL=0.244, 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 zNmVqXG64kL4 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:20:44 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 321FE11E82C7 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:20:21 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 630594100F; Thu, 17 Oct 2013 16:26:45 -0600 (MDT)
Message-ID: <526062A2.2030801@stpeter.im>
Date: Thu, 17 Oct 2013 16:20: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/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie>
In-Reply-To: <52605FCD.8000709@cs.tcd.ie>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, Barry Leiba <barryleiba@computer.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 22:20:49 -0000

On 10/17/13 4:08 PM, Stephen Farrell wrote:

> I do agree that some credit for chairs in particular would
> be a fine thing if we could figure a way to do it though.
> 
> For example, I'd encourage authors to include acks as per
> the above, in particular for cases of 'difficult' wgs.

I've started acknowledging also the directorate reviewers, as well as
the chairs and AD. A few examples:

http://tools.ietf.org/html/rfc6120#appendix-E

http://tools.ietf.org/html/rfc6993#section-5

It's not that hard to add a few lines at the end of your document. (Yet
sometimes I still forget, so thanks for the reminder!)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stephen.farrell@cs.tcd.ie  Thu Oct 17 15:21:49 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 C025311E82BC for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 6C2DqObMkh-0 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:21:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A829D11E82CE for <ietf@ietf.org>; Thu, 17 Oct 2013 15:20:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 92777BE88 for <ietf@ietf.org>; Thu, 17 Oct 2013 23:20: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 NmBmZFSgSQb2 for <ietf@ietf.org>; Thu, 17 Oct 2013 23:20:55 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.42.23.232]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 21C97BE87 for <ietf@ietf.org>; Thu, 17 Oct 2013 23:20:55 +0100 (IST)
Message-ID: <526062C6.9030703@cs.tcd.ie>
Date: Thu, 17 Oct 2013 23:20:54 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: IETF Discuss <ietf@ietf.org>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net> <D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net>
In-Reply-To: <D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net>
X-Enigmail-Version: 1.5.2
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, 17 Oct 2013 22:21:49 -0000

On 10/17/2013 10:16 PM, Jari Arkko wrote:
> Shrinking the IESG might make us think harder about what tasks really
> are absolutely necessary :-)

FWIW, having thought a bit about this my conclusion was that
shrinking the IESG to the point where its not actually feasible
to do all that's asked/expected by ADs/the-IETF-generally
is the only way to get the AD role down to ~1 day a week
between IETF meetings. I also have no clue how we mght get
there from here;-)

And as a factoid, for me, it was very much near full time
at first, but after a year was closer to 50-60% of my time
when nothing much special is going on, which is mostly, but
not always. However my hours-per-week are noticeably higher
than before being an AD, so it is more than 50-60% of my
pre-AD working week. So I do agree that changes that reduce
the load are very desirable if we could find a way to do
that. OTOH, I know a lot of other people who's hours per
week are growing thanks to be able to work outside of the
office so maybe that's a factor too.

S.


From stpeter@stpeter.im  Thu Oct 17 15:22:47 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 9DE4B21F92B5 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:22:47 -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.234, 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 4bHzmrrqs-Tp for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:22:42 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 37F6711E82C7 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:22:17 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 35D684100F; Thu, 17 Oct 2013 16:28:40 -0600 (MDT)
Message-ID: <52606316.8070406@stpeter.im>
Date: Thu, 17 Oct 2013 16:22: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/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com> <52605B68.10406@gmail.com>
In-Reply-To: <52605B68.10406@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 22:22:47 -0000

On 10/17/13 3:49 PM, Brian E Carpenter wrote:
> It's been suggested to me off list that this message came across as
> sarcastic. That was absolutely not my intention. I though Peter's list
> was thoughtful and I think that only drastic changes of how we work
> can seriously tackle the problem.

Brian, I didn't take your comments that way, but as an illustration of
the signficant cultural and personal changes required here.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From cabo@tzi.org  Thu Oct 17 15:35:24 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 1AAFF11E8200 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.171
X-Spam-Level: 
X-Spam-Status: No, score=-106.171 tagged_above=-999 required=5 tests=[AWL=0.078, 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 UAcwKeEC8aDA for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:35:11 -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 6C80911E8160 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:35:09 -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 r9HMYaNb007840; Fri, 18 Oct 2013 00:34:36 +0200 (CEST)
Received: from [192.168.217.105] (p54892BCF.dip0.t-ipconnect.de [84.137.43.207]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EBBC5DB0; Fri, 18 Oct 2013 00:34:35 +0200 (CEST)
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>
Date: Fri, 18 Oct 2013 00:34:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>, <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1510)
Cc: barryleiba@computer.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, 17 Oct 2013 22:35:24 -0000

On Oct 18, 2013, at 00:15, <l.wood@surrey.ac.uk> wrote:

> Chairs being authors, and thus taking a detailed technical position, =
can often be very bad for workgroup output.

Chairs understanding the technology also can be very good for WG output.

If you understand the technology in a dynamic field, it is simply =
unnatural to abstain from writing documents.

(I'm not saying there is no problem with mixing chair and author roles, =
just that it is inappropriate to "solve" it with simplistic rules.)

Gr=FC=DFe, Carsten


From john-ietf@jck.com  Thu Oct 17 15:52:24 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 D979B11E823D for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.587
X-Spam-Level: 
X-Spam-Status: No, score=-103.587 tagged_above=-999 required=5 tests=[AWL=0.012, 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 UYfQrxX7iSGJ for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:52:19 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DF32D11E81DE for <ietf@ietf.org>; Thu, 17 Oct 2013 15:52: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 1VWwQS-0003hV-LL; Thu, 17 Oct 2013 18:52:16 -0400
Date: Thu, 17 Oct 2013 18:52:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: barryleiba@computer.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Message-ID: <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
In-Reply-To: <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> ,	<52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Oct 2013 22:52:25 -0000

I had promised I was through for today, but I just had a wild,
crazy, suggestion that follows on the retirement of the xx99 and
xx00 subseries of RFCs.

I wonder if we should be publishing, at regular intervals, RFCs
with explicit acknowledgements and maybe contact information for
Areas and ADs, WG Chairs, and, if appropriate, other IETF
functionaries, probably including document reviewers and Nomcom
members.  It would provide both a snapshot of what has been
going on and who has been contributing to keeping the process
working that is more permanent/ archival and accessible than a
collection of web pages.  It would also provide a type of
formally-published acknowledgement for those sorts of work to
which people and their organizations could point.

It might have rather high payoff in comparison to the cost of
the bits.  And I'd think that most of the data could be pulled
out of existing sources with a few tools and a little
secretariat effort (i.e., little or no additional work for ADs).

Or maybe I'm missing a serious downside.

best,
   john



From steve@shinkuro.com  Thu Oct 17 15:56:15 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556D211E81DE for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, 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 Tix-galKxNhV for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 15:56:10 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 31A6D11E8202 for <ietf@ietf.org>; Thu, 17 Oct 2013 15:56:07 -0700 (PDT)
Received: from dummy.name; Thu, 17 Oct 2013 22:56:05 +0000
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
In-Reply-To: <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <F9682E20-B7CD-42F8-96C2-6D1D3B407916@shinkuro.com>
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (9B206)
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Date: Fri, 18 Oct 2013 09:56:10 +1100
To: John C Klensin <john-ietf@jck.com>
Cc: "barryleiba@computer.org" <barryleiba@computer.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, 17 Oct 2013 22:56:15 -0000

+1

Sent from my iPhone

On Oct 18, 2013, at 9:52 AM, John C Klensin <john-ietf@jck.com> wrote:

> I had promised I was through for today, but I just had a wild,
> crazy, suggestion that follows on the retirement of the xx99 and
> xx00 subseries of RFCs.
> 
> I wonder if we should be publishing, at regular intervals, RFCs
> with explicit acknowledgements and maybe contact information for
> Areas and ADs, WG Chairs, and, if appropriate, other IETF
> functionaries, probably including document reviewers and Nomcom
> members.  It would provide both a snapshot of what has been
> going on and who has been contributing to keeping the process
> working that is more permanent/ archival and accessible than a
> collection of web pages.  It would also provide a type of
> formally-published acknowledgement for those sorts of work to
> which people and their organizations could point.
> 
> It might have rather high payoff in comparison to the cost of
> the bits.  And I'd think that most of the data could be pulled
> out of existing sources with a few tools and a little
> secretariat effort (i.e., little or no additional work for ADs).
> 
> Or maybe I'm missing a serious downside.
> 
> best,
>   john
> 
> 

From petithug@acm.org  Thu Oct 17 16:55:26 2013
Return-Path: <petithug@acm.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 8738421F8616 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 16:55:26 -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 kBSrD5LNgzec for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 16:55:25 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC7311E81E2 for <ietf@ietf.org>; Thu, 17 Oct 2013 16:55:17 -0700 (PDT)
Received: from [IPv6:2001:5c0:1000:b::1bb5] (petithug.broker.freenet6.net [IPv6:2001:5c0:1000:b::1bb5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 3057920454; Fri, 18 Oct 2013 01:55:14 +0200 (CEST)
Message-ID: <526078DF.9040207@acm.org>
Date: Thu, 17 Oct 2013 16:55:11 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131005 Icedove/17.0.9
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <6.2.5.6.2.20131017133143.06d48790@resistor.net>
In-Reply-To: <6.2.5.6.2.20131017133143.06d48790@resistor.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, adrian@olddog.co.uk, 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, 17 Oct 2013 23:55:26 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 10/17/2013 03:14 PM, S Moonesamy wrote:
> At 12:36 17-10-2013, Adrian Farrel wrote:
>> Right. Ask: Do the reviews currently done by ADs make a difference to the
>> quality of individual documents or the overall canon?
> 
> The short answer is yes.  It also ends up as more work for the Area
> Director.
> 
>> Would we be happy to publish RFCs with lower quality?
> 
> Yes.
> 

As someone who implements RFCs and regularly find problems in them: No.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJSYHjdAAoJECnERZXWan7EzTEQANcOBVe9IJGcRfMqErPkhCAx
1DJI66HiCC2w4xYzIEFR6hHI2vsDK0pHXpQZiKnYsJq1NmDA6PMGf7kjO0bPPP3K
XoXFkhl9EKs/ba6lJWsM0tA+1wEpWYj4mGxkrHuSK8Z7GuiVuhPbWvgA4fjp+MMj
NmzWEJ0A5YKaL7pj90QJp88RbnLY8jfJgfV4bzcLZ96bc4LHSigpuqOGU93k8Clj
VkyGCF1JOv2ySf2RqAKboL30eGev5n8u31pdBQiQ8qVDFkaqgstW+xQ5omwcBXVc
glvYjv1qOYkVOLAqVezLRnaJEO74s92xkvPtJfSbaOAW7kyNRHKzkopGjDnEGtCX
CJBG4gXbUpHGqlbYE6CVLSr1BezKh26GlQ1kq+dIjfCfgW8uNQioQr1wg/vvoXVu
CVPYs8BDINlg+w3Y+U/pTh9rRfXbkbTKPqG9Y121pUpuicbBpF9iiw+2hngyPAD6
P13q55dybBpJikOYgT7jhuiCzhhl95nkteLAS6QZwo91ztzx97D3v2Dv1CCoLKHF
i3R9z7qkVghttbtqoZeGMLuarDcr2sopGN/PrAo/NaGQhQeQidrov0NOev1AojxN
zM7RYPEYJ3jhgz5BJNLLQzk8vtvh/utG4LP54D5shsDx7SHtO84gB4L7L6CcQvCE
oPB97vZVTH6FLZht3xHg
=S7DJ
-----END PGP SIGNATURE-----

From kathleen.moriarty@emc.com  Thu Oct 17 18:03:54 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 F195311E82EE for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 18:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level: 
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[AWL=-0.223, BAD_CREDIT=0.001, 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 Dj4Noseu1soo for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 18:03:49 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 298BE11E8202 for <ietf@ietf.org>; Thu, 17 Oct 2013 18:03:48 -0700 (PDT)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9I13jPH029457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Oct 2013 21:03:46 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r9I13jPH029457
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1382058226; bh=p5AnmHyE+O+8JuC6ZlBcw8vxWQM=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=ssRjoD0XjBHcu1EPQeLisLUOm7yR9NMNjPKhp0B4WLN1PMNj306JqoSW0SxQShQSm yPqfGhNgBHcLoBA80JJQkMZ4VF54C4T/HO+x8Lwq8vsItaMyprlyOVXS0NXn/bCFrh bv8INEGV9smRwzdDi/wu84Xq08U5aDotwUtJ0iJ0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r9I13jPH029457
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd54.lss.emc.com (RSA Interceptor); Thu, 17 Oct 2013 21:03:34 -0400
Received: from mxhub40.corp.emc.com (mxhub40.corp.emc.com [128.222.70.107]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9I13XRI025453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Oct 2013 21:03:33 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Thu, 17 Oct 2013 21:03:33 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Barry Leiba <barryleiba@computer.org>, IETF Discuss <ietf@ietf.org>
Date: Thu, 17 Oct 2013 21:03:31 -0400
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Topic: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Index: Ac7LgprbSRbtuHHfQmGmbU/ZFE3I5wAF42eg
Message-ID: <F5063677821E3B4F81ACFB7905573F24049E8BCC07@MX15A.corp.emc.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
In-Reply-To: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@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-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: DLM_1, public
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 01:03:54 -0000

Interesting, although I'll counter the point that your company is not promo=
ted. =20

As a chair now, because there is a lot of interest in information sharing, =
I am asked to speak quite often either on panels or talks.  Through these a=
ctivities, my company, the IETF, and the WG are all promoted.  This does ad=
d extra work, but if promoting your organization is important, it could be =
possible.

Best regards,
Kathleen


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Bar=
ry Leiba
Sent: Thursday, October 17, 2013 5:48 PM
To: IETF Discuss
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE T=
HE JOB)

Ted says, with respect to "Quickly replace failing WG Chairs":
> You forgot "from a magical pool of better qualified WG chairs who have=20
> the time and inclination to take on the work."

Let me tell you about a conversation I had when I was trying to fill a chai=
r position: I asked someone I thought could and would do a good job as chai=
r.  She was also a proponent of the technology, and wanted to be a document=
 author.  In response to, "Why not be a chair, and lead the effort?", part =
of her answer was something like this:

"I work for a small company.  Whatever work I do on this takes away from wh=
at I do for them, and they want to see something tangible from it.  If I'm =
(co-)author on a document, my name, and my company's is at the top of the d=
ocument.  I get credit for the work.  My company gets credit for the work.

"If I'm a working group chair, I do more work, overall.  And, in the end, I=
 get no credit for it -- my name is not on any of the documents.
 And, significantly, my company gets no credit for it whatsoever, not even =
listed in the datatracker.

"When I go to my boss and give him the alternatives, I know which he'll pic=
k."

Barry


From prvs=0996d6599b=johnl@iecc.com  Thu Oct 17 18:34:16 2013
Return-Path: <prvs=0996d6599b=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 B48DB11E8202 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 18:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 e6rGam5RP5oP for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 18:34:12 -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 7039411E812F for <ietf@ietf.org>; Thu, 17 Oct 2013 18:34:10 -0700 (PDT)
Received: (qmail 60482 invoked from network); 18 Oct 2013 01:34:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Oct 2013 01:34:09 -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=52609010.xn--i8sz2z.k1310; i=johnl@user.iecc.com; bh=UxzT/0wGADHJpES3rD+QzHOwUgHh6Rw5SWP4jH0TQUI=; b=bfyZY0BpZlS0xI5lui1JjNiGVC4awA9LSdMAKuH1eqEhmKBsfo8oDKKUYXftILrvlnz/4n+VSBzZMoEQ5GpF1uIvb7v0Szh/NScJxLXWB1+yjsUi+1tpBcG+jvvq25jFUy69s89DCXuBIxzCqtVTgUtrDqaqEmp9izsDFoNf3eQV+BGJZLfuJybLQsiUl3Vh9kj5CRNGqIXN+IimLFsPJfFj8g0pbdNN6Q+i9PCM3p/3ROT7O3WWfi4XNxf38OmR
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=52609010.xn--i8sz2z.k1310; olt=johnl@user.iecc.com; bh=UxzT/0wGADHJpES3rD+QzHOwUgHh6Rw5SWP4jH0TQUI=; b=gaSSZ0sPAOKa4unYmpKdSrzjqGUhk2ddvtIWiUWunUZsymvuacMV5yaX3WRr6Yd8KlDBehtfijk+yAaeE8CBMdeJg1MECnOQuamxNfhSv93lh8DK+seyffwo40JG/A7Lx5vr6xU4dm8J6LBP6bvctWuoa1K+Cyr4lUZOwMxR6imV62JUb0UcdVYTnUXUAWuUJqAxO7cMs5h+mrjROG3Wi5GBItLY3TUUzOxKibffifHLXwOLelft7z2e04sEpK5Y
Date: 18 Oct 2013 01:33:46 -0000
Message-ID: <20131018013346.37035.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs
In-Reply-To: <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: 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: Fri, 18 Oct 2013 01:34:16 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>I wonder if we should be publishing, at regular intervals, RFCs
>with explicit acknowledgements and maybe contact information for
>Areas and ADs, WG Chairs, and, if appropriate, other IETF ...

I don't think it would solve the problem.  If your boss, or your
tenure committee, or your salary review committee is inclined to count
IETF work, they're going to look at how many documents have your name
as author.  I very much doubt that explanations that being mentioned
in RFC9900 as a WG chair or reviewer is just as good, even if true,
will help much.

In areas of scientific research where large teams do the work, it's
common to have papers with 50 or more co-authors, probably for exactly
this reason.  I realize we have a tradition of only five authors on an
RFC, but I've never seen a reason beyond that the first page looks
ugly if there's a long author list.  If more author credit will help
people persuade the powers that be that spending time on IETF work
is worth it, we should give more author credit, no matter how ugly
those first pages look*, to anyone who provided signficant text or
othewise provided some significant part of the document's contents.

If the AD provides oversight and direction, that includes the AD. It's
no worse than listing a professor as a co-author of all of her
students' papers.

R's,
John

* - although I expect some twiddles to xml2rfc might help
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iEYEARECAAYFAlJgkA8ACgkQkEiFRdeC/kU/UQCfca2w7bOlZlh5oZeHZYCyZhQc
TcUAnitXOHCJJlvYObUJe5ttr5hj0MVq
=nihW
-----END PGP SIGNATURE-----

From mstjohns@comcast.net  Thu Oct 17 19:31: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 C36F911E80EE for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 19:31:24 -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 h0Kw1a+9JDx0 for <ietf@ietfa.amsl.com>; Thu, 17 Oct 2013 19:31:18 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id CDD3321F9CF7 for <ietf@ietf.org>; Thu, 17 Oct 2013 19:31:16 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta13.westchester.pa.mail.comcast.net with comcast id eSKV1m0070bG4ec5DSXG9P; Fri, 18 Oct 2013 02:31:16 +0000
Received: from sz0152.wc.mail.comcast.net ([68.87.26.137]) by omta03.westchester.pa.mail.comcast.net with comcast id eSXG1m0062xV5no3PSXGJV; Fri, 18 Oct 2013 02:31:16 +0000
Date: Fri, 18 Oct 2013 02:31:16 +0000 (UTC)
From: <mstjohns@comcast.net>
To: barryleiba <barryleiba@computer.org>, John <john-ietf@jck.com>
Message-ID: <1666967396.3522867.1382063476256.JavaMail.root@sz0152a.westchester.pa.mail.comcast.net>
Subject: Re: Proper credit for work done -- on finding chairs	(was CHANGE THE	JOB)
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_3522866_1463868604.1382063476256"
X-Originating-IP: [::ffff:69.252.207.139]
X-Mailer: Zimbra 6.0.13_GA_2944 (ComcastOTT /1.0)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382063476; bh=MVVerFxSyHwegsLM1NbxOhIsHL1VaQVWQTBrniMzHMQ=; h=Received:Received:Date:From:To:Message-ID:Subject:MIME-Version: Content-Type; b=bfAMgdnJXGkXfP4q3C3EN9OBkYQdklGUXWR3kBFPGA05SKR8yN70vPbBsQkLcnowB wJiNyoP1ei7/j4WuNS5Oa6sH7TCxmGmLykiLGSFNZE+uGoEi844AE8kO1rzZh3NiDX OUbxAFA1fFQbwOG69YHaDpqh1l4Wwb3rVYCVRuPWmS5EUfcAvGPry+AIjvLUVfYcGA b4Sti0XxroVy1BOeNcsvpxN6GfacOStZdpB3S+x6xMytsL5h5gGIVdl3uvRhUs6xuj tvd7pvBaDQTkd1Bsz5ao1q4zVisuHD2NHDNLJ9R5/MDpgzeZ7GFcBJGGalBK+aM9NM qpmt9MZ6TDmNg==
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, 18 Oct 2013 02:31:24 -0000

------=_Part_3522866_1463868604.1382063476256
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

-1. I can't think of a single instance I which this would be useful to me unless I were I recruiting mode.  I'd ask if this is meant to be a document that's useful when published or more of a digital tombstone ala Who's Who type books.  I.e., who is the target audience and why?

I don't think this passes even a modest cost benefits analysis.  

Mike


Sent from Comcast mobile

-----Original Message-----
From: John C Klensin
To: barryleiba
Cc: ietf
Sent: October 17, 2013, 15:53
Subject: Re: Proper credit for work done -- on finding chairs	(was CHANGE THE	JOB)

I had promised I was through for today, but I just had a wild,
crazy, suggestion that follows on the retirement of the xx99 and
xx00 subseries of RFCs.

I wonder if we should be publishing, at regular intervals, RFCs
with explicit acknowledgements and maybe contact information for
Areas and ADs, WG Chairs, and, if appropriate, other IETF
functionaries, probably including document reviewers and Nomcom
members.  It would provide both a snapshot of what has been
going on and who has been contributing to keeping the process
working that is more permanent/ archival and accessible than a
collection of web pages.  It would also provide a type of
formally-published acknowledgement for those sorts of work to
which people and their organizations could point.

It might have rather high payoff in comparison to the cost of
the bits.  And I'd think that most of the data could be pulled
out of existing sources with a few tools and a little
secretariat effort (i.e., little or no additional work for ADs).

Or maybe I'm missing a serious downside.

best,
   john



------=_Part_3522866_1463868604.1382063476256--

From trammell@tik.ee.ethz.ch  Fri Oct 18 00:06:00 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF0221F9AD2 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 00:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.466
X-Spam-Level: 
X-Spam-Status: No, score=-6.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 2NRyzgKSCp8E for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 00:05:49 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id E84FC21F960E for <ietf@ietf.org>; Fri, 18 Oct 2013 00:05:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 6FE62D9303; Fri, 18 Oct 2013 09:05:43 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WMgKCrabuW3y; Fri, 18 Oct 2013 09:05:43 +0200 (MEST)
Received: from [10.0.27.100] (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 1F111D9300; Fri, 18 Oct 2013 09:05:43 +0200 (MEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_64FEB46C-C792-42C7-B070-E85EA9CD6D0B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: On reviews was Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <52603628.1080007@stpeter.im>
Date: Fri, 18 Oct 2013 09:05:42 +0200
Message-Id: <F409BC2F-74B6-4799-B94A-9D65F0DBC43E@tik.ee.ethz.ch>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1510)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 07:06:00 -0000

--Apple-Mail=_64FEB46C-C792-42C7-B070-E85EA9CD6D0B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

hi Peter, all,

On Oct 17, 2013, at 9:10 PM, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:

> I agree that the job needs to change.
>=20
> It might be helpful to talk about what could change, such as:
>=20
> 1. Less/no time on document reviews.

There are two broad purposes to review:=20

(1) quality, both technical and editorial: does the document describe a =
real working thing in an interoperably implementable way -- without =
necessarily considering the wider context in which it must function.

(2) consistency: does the document fit with the "Internet architecture" =
-- how does it interact with other documents in the same working group, =
in the same area; how does it interact with other ongoing work in other =
areas; how does it interact with past work across the IETF; and most =
importantly, how does it interact with what's actually deployed in each =
of the relevant contexts.

We already have directorates which -- with a fair amount of variability =
in scope from area to area -- handle first-pass reviews of most of this. =
The roles of the directorates could be significantly expanded; however: =
one important aspect of this problem is that quality review is much more =
scalable and parallelizes much better than consistency review. All a =
reviewer needs to evaluate the quality of the document is some facility =
with the language (and jargon) in which it is written and a relatively =
good understanding of the problem it's trying to solve.

Consistency review is harder in that one must additionally have fairly =
deep and current knowledge of essentially everything going on =
everywhere. Cross-area _quality_ review can reduce this workload =
somewhat, at the cost of requiring each area directorate to have =
qualified reviewers who are conversant in at least one or two other =
areas. So these will necessarily be rarer and more difficult, but they =
can be made significantly easier by more, better, and earlier quality =
review -- a consistency review should only be checking consistency, not =
chasing down ambiguities or errors wholly within the document itself.

Academia uses grad students for reviews. One, they're cheap, two, it's =
also a way for the grad students to learn. The hope (and it is a hope) =
is that for any given paper there is a diversity of expertise in the =
multiple reviews such that a review written by someone hopelessly =
unqualified doesn't result in a bad decision. We don't want to rely on =
hope for document quality, but we can learn something from the diversity =
side of this arrangement: if we have more, earlier reviews, focused on =
quality aspects more than consistency aspects, then the AD's review of =
the document can (1) draw from the outputs of more diverse earlier =
reviews and (2) benefit from a document of higher quality. A side =
benefit is that reviewers who do cross-area reviews get more visibility =
into the workings of other areas.

It seems that tool support could be useful here -- a document could be =
associated in the datatracker with a set of reviewers (either appointed =
by the ADs, directorates, or WG chairs, or volunteer reviewers), and =
those reviews tracked along with the document throughout its lifecycle, =
along with profiles of the reviewers (including other documents they've =
reviewed and authored) from which their areas of expertise can be =
deduced.  Doing this would allow us to track which areas have already =
reviewed; reviewers who have only looked at certain sections of the =
document in detail could indicate so, giving both an area-coverage and =
text-coverage view of where more work is needed.

To the extent that these reviews require human coordination and =
oversight (i.e., someone to ratify a review in the datatracker as of =
sufficient quality itself), I'd see this as primarily the job of the =
document shepherd.

It also needs more reviewers, but we've got a couple of thousand =
volunteers. This asks for a bit of a culture shift, to be slightly more =
formal about how reviews are done, but I think it would go a long way to =
making the AD position a viable choice for more people.

Cheers,

Brian

--Apple-Mail=_64FEB46C-C792-42C7-B070-E85EA9CD6D0B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJSYN3GAAoJENt3nsOmbNJcLEsH/jfz9IFoTG78iZbuDgWWRsll
Ltx6bng+kHCoD4J6cuaj3DbtiJkf4q1PC9f1MnCoaov+8A3kYr7y4wxP+fH0mHuJ
pGrNAXfoc5NA2sSApO+9L4+TPvsHZt97jk/H6if1zGml/eIV3qjlGdr9ZiK6jzhd
msE/xsuYChCLmL7ZHiv/sObaxFcPTcT4vY/IdKWnKCsyuwythykv4n+EkHcJMgtG
pyu5hofkC5AJwbzziyfAFfAfY4oMzPtvWB6kCS0iFHBRk0v1+GHrDjbYzFjys01B
aO5hZ2MOb0SJWkYvOrduTvi1lfT9amllT2ElgtREbqi4muWBfQhSwzygRa6Bz9g=
=LGNZ
-----END PGP SIGNATURE-----

--Apple-Mail=_64FEB46C-C792-42C7-B070-E85EA9CD6D0B--

From daedulus@btconnect.com  Fri Oct 18 01:26:36 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 9697221F9ED2 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 01:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level: 
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033,  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 YgQsviBM7VTQ for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 01:26:30 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 1267F21F91F2 for <ietf@ietf.org>; Fri, 18 Oct 2013 01:25:57 -0700 (PDT)
Received: from mail221-va3-R.bigfish.com (10.7.14.227) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.22; Fri, 18 Oct 2013 08:25:56 +0000
Received: from mail221-va3 (localhost [127.0.0.1])	by mail221-va3-R.bigfish.com (Postfix) with ESMTP id 3A2BDC022D; Fri, 18 Oct 2013 08:25:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(z551bizbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail221-va3 (localhost.localdomain [127.0.0.1]) by mail221-va3 (MessageSwitch) id 1382084754499586_3959; Fri, 18 Oct 2013 08:25:54 +0000 (UTC)
Received: from VA3EHSMHS036.bigfish.com (unknown [10.7.14.254])	by mail221-va3.bigfish.com (Postfix) with ESMTP id 6CFB244004B; Fri, 18 Oct 2013 08:25:54 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS036.bigfish.com (10.7.99.46) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 18 Oct 2013 08:25:54 +0000
Received: from DB3PRD0210HT003.eurprd02.prod.outlook.com (157.56.253.69) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 18 Oct 2013 08:25:47 +0000
Message-ID: <007301cecbdb$5fed8100$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF Discuss <ietf@ietf.org>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net><D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net> <526062C6.9030703@cs.tcd.ie>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call forNominations)
Date: Fri, 18 Oct 2013 09:23:38 +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.69]
X-OriginatorOrg: btconnect.com
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: Fri, 18 Oct 2013 08:26:36 -0000

----- Original Message -----
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "IETF Discuss" <ietf@ietf.org>
Sent: Thursday, October 17, 2013 11:20 PM
>
> On 10/17/2013 10:16 PM, Jari Arkko wrote:
> > Shrinking the IESG might make us think harder about what tasks
really
> > are absolutely necessary :-)
>
> FWIW, having thought a bit about this my conclusion was that
> shrinking the IESG to the point where its not actually feasible
> to do all that's asked/expected by ADs/the-IETF-generally
> is the only way to get the AD role down to ~1 day a week
> between IETF meetings. I also have no clue how we mght get
> there from here;-)
>
> And as a factoid, for me, it was very much near full time
> at first, but after a year was closer to 50-60% of my time
> when nothing much special is going on, which is mostly, but
> not always. However my hours-per-week are noticeably higher
> than before being an AD, so it is more than 50-60% of my
> pre-AD working week. So I do agree that changes that reduce
> the load are very desirable if we could find a way to do
> that. OTOH, I know a lot of other people who's hours per
> week are growing thanks to be able to work outside of the
> office so maybe that's a factor too.

I like to solve a problem by first knowing what the problem is.  Yes,
ADs have too much to do, and I regularly include comments to the effect
that ADs are the most valuable resource in the IETF, but where does the
time go?  To suggest what could be done, by myself and others, requires
first an understanding of that.

I recall a Canadian initiative of some 30 years ago, when I was given an
egg timer and a sheet of paper (it's probably in the App store nowadays)
and every time the timer went off, I reset it and wrote down what I was
doing.  At the end of a week, I had 70 samples of my activities and
could build up a picture of what I was doing to benefit my employer (or
myself), where I was frittering time away, where technology could
improve my productivity and so on.  So simple so effective.

So where does an AD's time go?  I need some concrete data, from whatever
means is appropriate.  Then I might be able to help.

Tom Petch









>
> S.
>
>



From hannes.tschofenig@gmx.net  Fri Oct 18 02:06:27 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 D0ADA21F9D7D for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:06: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 FrOQ6v1Ninu6 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:06:21 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 74B9A21F9A50 for <ietf@ietf.org>; Fri, 18 Oct 2013 02:06:03 -0700 (PDT)
Received: from [172.16.254.200] ([80.92.116.76]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Mg3h3-1VLBkt0o6P-00NUfp for <ietf@ietf.org>; Fri, 18 Oct 2013 11:06:02 +0200
Message-ID: <5260FA18.4030504@gmx.net>
Date: Fri, 18 Oct 2013 11:06:32 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
Subject: Re: [TLS] Last Call: <draft-ietf-tls-oob-pubkey-09.txt> (Out-of-Band Public Key Validation for Transport Layer Security (TLS)) to Proposed Standard
References: <20130802072350.14846.84073.idtracker@ietfa.amsl.com> <5203B8BC.9080108@isode.com>
In-Reply-To: <5203B8BC.9080108@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:AYokqV/svMUx/efrTBnNz4EeBhYFN6Yy0ikzhSKWGO2LNPIxmNt RzicOcLjYen2QzPiHNI77wqfHlSNLEEwiBj+2Am9QLOVfJyH/Zc9/6GgKloaJh9rlaBwpBF LeLbKX89t2F0BKV9vk/kA1ZWLYX4PIcP8fEhHbjNQmMwYferUMNfnlkdEggu1o4EGq3jNiq ANOBP91h/pyVG5mvC1mUg==
Cc: tls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 09:06:27 -0000

Hi Alexey,

the first example indeed has a copy-and-paste error. I fixed it.

Ciao
Hannes

On 08/08/2013 05:26 PM, Alexey Melnikov wrote:
> On 02/08/2013 08:23, The IESG wrote:
>> The IESG has received a request from the Transport Layer Security WG
>> (tls) to consider the following document:
>> - 'Out-of-Band Public Key Validation for Transport Layer Security (TLS)'
>>    <draft-ietf-tls-oob-pubkey-09.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-08-16. 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 a new certificate type and two TLS
>>     extensions, one for the client and one for the server, for exchanging
>>     raw public keys in Transport Layer Security (TLS) and Datagram
>>     Transport Layer Security (DTLS) for use with out-of-band public key
>>     validation.
> Hi,
> I just read the document and support its publication.
>
> I think I found one minor issue:
>
> Section 4.1 says:
>
>     In order to indicate the support of out-of-band raw public keys,
>     clients MUST include the 'client_certificate_type' and
>     'server_certificate_type' extensions in an extended client hello
>     message.  The hello extension mechanism is described in TLS 1.2
>     [RFC5246].
>
> In Section 5 (the first example):
>
> client_hello,
>     server_certificate_type=(RawPublicKey) -> // [1]
>
> So it looks like the example doesn't comply with the MUST requirement in
> the Section 4.1 ("client_certificate_type" is missing) or the
> requirement stated in Section 4.1 is incorrect. I suspect you meant
> "'client_certificate_type' and/or 'server_certificate_type'" in Section
> 4.1.
>
> Best Regards,
> Alexey
>
>
>
>


From abdussalambaryun@gmail.com  Fri Oct 18 02:06:38 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 AE29B11E816B for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=-0.558, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qwFZzMIZ8Mz for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:06:37 -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 A6F2B21F995A for <ietf@ietf.org>; Fri, 18 Oct 2013 02:06:16 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id bj1so4209018pad.21 for <ietf@ietf.org>; Fri, 18 Oct 2013 02:06:14 -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=07x1Wcy3Lv70V0sJUKQRXvEjSLGdms80gRbHApfk+1E=; b=tWF9akzcLO8HLaJU2OoPRcO81H1Vqj+seCwwj0vYXYxONShYQdMvLxN+ET7HGZRBrE fpGG8QZsW3cHJjCa0zd0VAHoaAFOQjfmyjK6A5E5nxuY3XnRbO5YdhUq1ykDDVwkfU7r 1u2KXQBCJA2H51SuVV1L2qm5t8ApshrZCnIXkT3ommmT7omFWIgwif6IuWfmF8+KKLyT XuQJCA8rOcgGb7R/HRb/iDAuztHiimD+3fLHo+ZdbePkXx2kyekuFGORhygGhZ2oAcKn wyuWjqRodK2DCV/UgBMB3KqlfA5CfoUfq99/+4L+Fv1dpq0jRsApWLPtV/EofC1DIZL/ mA1w==
MIME-Version: 1.0
X-Received: by 10.68.239.225 with SMTP id vv1mr2039850pbc.126.1382087174801; Fri, 18 Oct 2013 02:06:14 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 18 Oct 2013 02:06:14 -0700 (PDT)
In-Reply-To: <D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <D5CC58E1-17D8-46DA-9AEB-9CEA8536C01D@piuha.net>
Date: Fri, 18 Oct 2013 10:06:14 +0100
Message-ID: <CADnDZ88VNVuJSzn9AxbpFEafG4oATEq4-ESwAKgBDL6grjJ-bg@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b33cf661a51b804e9003fde
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 09:06:38 -0000

--047d7b33cf661a51b804e9003fde
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I recommend that IESG consider discussing this problem more deeper for
future disasters and know why we have this problem today (maybe because of
our IETF managments in the past did not think of this problem that it might
come real) of short ADs or very low interest in taking such
responsibilities. In my opinion there is something wrong with the IESG or
NOMCOM, their system maybe old and needs to encourage
participants/new-comers in these positions, and make awareness.
 The solution is always encouraging diversity of participants into thoes
positions, why does not IESG and NOMCOM find new ways to market IETF-Jobs.
If we are doing more than 2 meetings every year in one region of majority
participants, it is strange that we cannot get an AD ready to do the full
job for even one year. This problem can be blamed easily on IESG or/and
NOMCOM but not the community that follows its few leaders, but if we have
more diversified community we may blame the community of such problem.

AB

On Thu, Oct 17, 2013 at 10:16 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I have some opinions about this, not to the mistaken for the IESG's or
> IETF's official opinions.
>
> First off, I think we should be very careful when thinking about funding
> models. I like an IETF where people come to do stuff (write docs for
> themselves and others, chair WGs, work as ADs, =85) because it is useful =
for
> themselves and their employers - directly or indirectly, short term or lo=
ng
> term, but there needs to be a reason we all are here. A desirable feature
> of a funding model is to help direct efforts to directions that are
> actually useful for the world. This is not to say that it would be the on=
ly
> desirable feature of a funding model, we have serious problems with
> academic participation, for instance. And we have too many situations whe=
re
> we only have large companies involved. But I could also imagine funding
> models that would support ADs but would move IETF towards doing things th=
at
> are not tied to real world and real Internet problems. But it is possible
> there is a useful middle ground.
>
> Secondly, we've talked about this in the IESG and the community last
> spring when we had only one TSV AD for a while. My read of the situation =
is
> that reducing the task to a better manageable one is the most reasonable
> course of action. It would also solve many of the undesirable aspects of
> the funding model. I can only agree with Adrian who said:
>
> > Please don't assume we ADs want this to be full time work.
>
> Thirdly, if you are considering volunteering for an AD task, please do no=
t
> feel that you need to be limited by current operating models. The AD is a
> management position, and we expect managers to have an idea how to run
> things, often better than what has been done previously. For instance,
> several ADs make extensive use of directorates in their review tasks, for
> instance several Gen ADs have traditionally relied almost entirely on
> directorate help (at least unless problems show up in review of a
> document). Other ADs do this too, though to a lesser extent due to a
> different type of their task. But for all of these positions, if you have
> an idea how to run it best - please volunteer and expect to get a lot of
> latitude to run your area how you see best!
>
> Fourth, the IESG's desirable qualifications are just our opinions, and th=
e
> nomcom needs to decide what type of people the IETF really needs. Hopeful=
ly
> that is the kind of people that I referred to above that know how to
> organise their and others work in an efficient manner! And the areas are
> largely run by the ADs very independently. The IESG does control things
> like how we run the common things, the tele chats, and we do control how
> many areas there are. If it helped to increase or reduce the number of AD=
s,
> we'd do it in a heartbeat. However, the quick solution of getting
> additional ADs to share tasks more widely is not necessarily good either,
> because the overall team size would grow, with the inter-IESG coordinatio=
n
> becoming harder. I think we are already at a practical limit. Shrinking t=
he
> IESG might make us think harder about what tasks really are absolutely
> necessary :-)
>
> Finally, I'll agree with Ted:
>
> > You forgot "from a magical pool of better qualified WG chairs who have
> the time and inclination to take on the work."   This is actually very
> similar to the AD acquisition problem.
>
> My conclusion is that (a) IETF that does useful things on a timely basis
> will naturally attract people to do the work and (b) a big part of the
> responsibility is in the IESG's and individual AD's hands - if the manage=
r
> doesn't manage his or hers work efficiently, then it is the manager's fau=
lt.
>
> As to how to implement (b): I think it is natural that as organisations d=
o
> more (and we do quite a bit, and have been for a long time) the managemen=
t
> needs to give up on managing all details, and have to spend more of their
> time in finding the good coders than fixing the bugs in the code themselv=
es
> :-) Delegate. Focus on the strategic things. Yeah, maybe easier said than
> done.
>
> Jari
>
>

--047d7b33cf661a51b804e9003fde
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I recommend that IESG consider discussing this proble=
m more deeper for future disasters=A0and know why we have this problem toda=
y (maybe because of our IETF managments in the past did not think of this p=
roblem that it might come real) of short ADs or very low interest in taking=
 such responsibilities. In my opinion there is something wrong with the IES=
G or NOMCOM, their system maybe old and needs to encourage participants/new=
-comers in these positions, and make awareness.</div>
<div>=A0The solution is always encouraging diversity of participants into t=
hoes positions, why does not IESG and NOMCOM find new ways to market IETF-J=
obs. If we are doing more than 2 meetings every year in=A0one region of maj=
ority participants,=A0it is strange that we cannot get an AD ready to do th=
e full job for even one year. This problem can be blamed easily on IESG or/=
and NOMCOM but=A0not the community that=A0follows its few leaders, but if w=
e have more diversified community we may blame the community of such proble=
m.</div>
<div>=A0</div><div>AB</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Thu, Oct 17, 2013 at 10:16 PM, Jari Arkko <span dir=3D"ltr">&l=
t;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuh=
a.net</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">I have some opinions about this, not to the mistaken for t=
he IESG&#39;s or IETF&#39;s official opinions.<br>

<br>
First off, I think we should be very careful when thinking about funding mo=
dels. I like an IETF where people come to do stuff (write docs for themselv=
es and others, chair WGs, work as ADs, =85) because it is useful for themse=
lves and their employers - directly or indirectly, short term or long term,=
 but there needs to be a reason we all are here. A desirable feature of a f=
unding model is to help direct efforts to directions that are actually usef=
ul for the world. This is not to say that it would be the only desirable fe=
ature of a funding model, we have serious problems with academic participat=
ion, for instance. And we have too many situations where we only have large=
 companies involved. But I could also imagine funding models that would sup=
port ADs but would move IETF towards doing things that are not tied to real=
 world and real Internet problems. But it is possible there is a useful mid=
dle ground.<br>

<div class=3D"im"><br>
Secondly, we&#39;ve talked about this in the IESG and the community last sp=
ring when we had only one TSV AD for a while. My read of the situation is t=
hat reducing the task to a better manageable one is the most reasonable cou=
rse of action. It would also solve many of the undesirable aspects of the f=
unding model. I can only agree with Adrian who said:<br>

<br>
&gt; Please don&#39;t assume we ADs want this to be full time work.<br>
<br>
</div>Thirdly, if you are considering volunteering for an AD task, please d=
o not feel that you need to be limited by current operating models. The AD =
is a management position, and we expect managers to have an idea how to run=
 things, often better than what has been done previously. For instance, sev=
eral ADs make extensive use of directorates in their review tasks, for inst=
ance several Gen ADs have traditionally relied almost entirely on directora=
te help (at least unless problems show up in review of a document). Other A=
Ds do this too, though to a lesser extent due to a different type of their =
task. But for all of these positions, if you have an idea how to run it bes=
t - please volunteer and expect to get a lot of latitude to run your area h=
ow you see best!<br>

<br>
Fourth, the IESG&#39;s desirable qualifications are just our opinions, and =
the nomcom needs to decide what type of people the IETF really needs. Hopef=
ully that is the kind of people that I referred to above that know how to o=
rganise their and others work in an efficient manner! And the areas are lar=
gely run by the ADs very independently. The IESG does control things like h=
ow we run the common things, the tele chats, and we do control how many are=
as there are. If it helped to increase or reduce the number of ADs, we&#39;=
d do it in a heartbeat. However, the quick solution of getting additional A=
Ds to share tasks more widely is not necessarily good either, because the o=
verall team size would grow, with the inter-IESG coordination becoming hard=
er. I think we are already at a practical limit. Shrinking the IESG might m=
ake us think harder about what tasks really are absolutely necessary :-)<br=
>

<br>
Finally, I&#39;ll agree with Ted:<br>
<div class=3D"im"><br>
&gt; You forgot &quot;from a magical pool of better qualified WG chairs who=
 have the time and inclination to take on the work.&quot; =A0 This is actua=
lly very similar to the AD acquisition problem.<br>
<br>
</div>My conclusion is that (a) IETF that does useful things on a timely ba=
sis will naturally attract people to do the work and (b) a big part of the =
responsibility is in the IESG&#39;s and individual AD&#39;s hands - if the =
manager doesn&#39;t manage his or hers work efficiently, then it is the man=
ager&#39;s fault.<br>

<br>
As to how to implement (b): I think it is natural that as organisations do =
more (and we do quite a bit, and have been for a long time) the management =
needs to give up on managing all details, and have to spend more of their t=
ime in finding the good coders than fixing the bugs in the code themselves =
:-) Delegate. Focus on the strategic things. Yeah, maybe easier said than d=
one.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div></div>

--047d7b33cf661a51b804e9003fde--

From jmh@joelhalpern.com  Fri Oct 18 02:31:04 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7B121F8427; Fri, 18 Oct 2013 02:31: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 VkYgHqalluoh; Fri, 18 Oct 2013 02:30:59 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF2021F9CB0; Fri, 18 Oct 2013 02:30:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 443ED1BC96F1; Fri, 18 Oct 2013 02:30:49 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [192.165.183.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 33DB11BC96D5; Fri, 18 Oct 2013 02:30:48 -0700 (PDT)
Message-ID: <5260FFC8.7090602@joelhalpern.com>
Date: Fri, 18 Oct 2013 05:30:48 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: [Gen-art] Review: draft-ietf-mpls-ldp-multi-topology-09.txt
References: <526056C6.7060007@nostrum.com>
In-Reply-To: <526056C6.7060007@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, 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, 18 Oct 2013 09:31: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-ietf-mpls-ldp-multi-topology-09.txt
     LDP Extensions for Multi Topology Routing
Reviewer: Joel M. Halpern
Review Date: 18-October-2013
IETF LC End Date: 6-November-2013
IESG Telechat date: N/A

Summary: This document is nearly ready for publication as a Proposed 
Standard RFC.  I believe there is one major issue that is easily addressed.

Major issues:
     I may have simply missed this reviewing the document, but as far as 
I can tell there is no specification of the relationship between the 
MT-IDs in this document and the MT-IDs used elsewhere.  Yes, I can take 
a guess at the intent.  But is it stated somewhere that these are the 
same IDs negotiated in the relevant IGP?  Or is there some other intent?

Minor issues:

Nits/editorial comments:
     I find it odd that the MT-ID follows the IP prefix in the various 
formats.  Yes, the computer can parse both.  But since we tend to think 
in Network byte order, I expect more significant information (MT-ID) to 
occur before less significant information (IP prefix within topology.)

From scott.brim@gmail.com  Fri Oct 18 02:59:29 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 9EA5611E811D for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:59: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=[AWL=0.000, 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 gzfd2aYzIXaa for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 02:59:29 -0700 (PDT)
Received: from mail-ea0-x22f.google.com (mail-ea0-x22f.google.com [IPv6:2a00:1450:4013:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C96DB11E81B2 for <ietf@ietf.org>; Fri, 18 Oct 2013 02:59:25 -0700 (PDT)
Received: by mail-ea0-f175.google.com with SMTP id m14so1788542eaj.6 for <ietf@ietf.org>; Fri, 18 Oct 2013 02:59:25 -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=iXYyrTyEC/qTsA6HVo2gGzzgXQYSEqRUwd32eJ908ZQ=; b=YY19MSCCuQ4dc4WdYFuKTm/VEN+E9QeUdpxT3SYnM0K5AQg+Y8wvAfpws+CgLRHLzI FzSif7g79bIkCxkUdCM7gJHBnfL9D9vLLUnlb47s3pBKlbIpaLq/lNdOGGE/22cK/WkN 9kBlSyoYBote+vZnVUJY99u/aNXiacTdwW3SYkbCl84q6qYeTJMT6Kn308SpFrx1t+tY lcjxC1ndXrZ8k+gxS1qp9wd0aZy6VQcV2X8gLbu+AYlazQZJFBL+vgFxMnWSTBUe72XF sNd121aqrQiJlsfeeCf21q+qy3zbwfahuxRS8cXR8HnqfD9P8CdnEQ2FHqnOzJlNfLQm bakA==
MIME-Version: 1.0
X-Received: by 10.14.93.132 with SMTP id l4mr1266513eef.119.1382090364944; Fri, 18 Oct 2013 02:59:24 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Fri, 18 Oct 2013 02:59:24 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Fri, 18 Oct 2013 02:59:24 -0700 (PDT)
In-Reply-To: <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
Date: Fri, 18 Oct 2013 05:59:24 -0400
Message-ID: <CAPv4CP8TCcuWWjG=QWKM9tNKjktVi84TK3yO1XocO0J-BD2oxg@mail.gmail.com>
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Scott Brim <scott.brim@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c288fa40061e04e900fd8b
Cc: Adrian Ferrell <adrian@olddog.co.uk>, IETF Discuss <ietf@ietf.org>, 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: Fri, 18 Oct 2013 09:59:29 -0000

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

On Oct 17, 2013 4:20 PM, "John C Klensin" <john-ietf@jck.com> wrote:
> * Many years ago, there were some proposals to limit the number
> of WGs to what could be effectively managed without growing the
> IESG or turning it into a full-time job.

Fyi for historical perspective: the idea of limiting the number of working
groups arose within hours of the idea of working groups itself.

There has never been an accepted way to decide whose work should be denied
except popularity, and as the IETF 's popularity swelled it became possible
to get enough people to work on almost anything.

It would be great if the IETF had a _strategy_ under which priorities and
action items could be determined.

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

<p dir=3D"ltr"><br>
On Oct 17, 2013 4:20 PM, &quot;John C Klensin&quot; &lt;<a href=3D"mailto:j=
ohn-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br>
&gt; * Many years ago, there were some proposals to limit the number<br>
&gt; of WGs to what could be effectively managed without growing the<br>
&gt; IESG or turning it into a full-time job. =A0</p>
<p dir=3D"ltr">Fyi for historical perspective: the idea of limiting the num=
ber of working groups arose within hours of the idea of working groups itse=
lf. </p>
<p dir=3D"ltr">There has never been an accepted way to decide whose work sh=
ould be denied except popularity, and as the IETF &#39;s popularity swelled=
 it became possible to get enough people to work on almost anything. </p>

<p dir=3D"ltr">It would be great if the IETF had a _strategy_ under which p=
riorities and action items could be determined.=A0 </p>

--001a11c288fa40061e04e900fd8b--

From abdussalambaryun@gmail.com  Fri Oct 18 03:03:06 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 792BA11E81CA for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 03:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 XAhLyT8oQcrn for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 03:03:05 -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 2121311E81AB for <ietf@ietf.org>; Fri, 18 Oct 2013 03:03:05 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fa1so4291972pad.9 for <ietf@ietf.org>; Fri, 18 Oct 2013 03:03: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=M0+8qoqU4W/Qsv2VcdlYnNASDIwx9nVkm8tPXa06qH4=; b=fCyXNC4+APjA5UpJZdRyChjC5NG3eD4kBXKw48gj+jj4cUmDQUm/oatR4wsgUfptkA noAWH5W4/eWlG/ItpGrvBi96Dj8XvFeBw4hpzYSYoPf9K8aS/7uWLgHsPI17RodXQW3R e+aJLbOCl2GWXmhnJ+UEZE21cQAGFpLFD03emYcjB+5/+KnLmya17yJyl9OZ3Ry98DK4 VL9wSQTT71M2KpHOfQE2u2LchFPTYJ4xm3WJwbMmHCyrL8xyAm/MgzDgwBXlW7Z0kZnl QM7GnPMJzOcOvhE+BfSeUwwRZO4M67TZf1q1cgfep9CYZXcbmPEVYFPz3FKJ5DVgkUOK zHxA==
MIME-Version: 1.0
X-Received: by 10.66.196.168 with SMTP id in8mr2737049pac.18.1382090584763; Fri, 18 Oct 2013 03:03:04 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 18 Oct 2013 03:03:04 -0700 (PDT)
In-Reply-To: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
Date: Fri, 18 Oct 2013 11:03:04 +0100
Message-ID: <CADnDZ8-QQMMChCmAdi8dOxDtGOMJfzXKgKM_YOt8QtfbOPEyhg@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7bdca8a45a342a04e9010a48
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 10:03:06 -0000

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

On Thu, Oct 17, 2013 at 8:36 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hello,
>
> > > The IESG defines the job and the IESG 'operates' the model.  So yes,
> > > formally the IESG controls this issue.
>
> Mutter.
> I suppose the seated IESG defines what it does.
> Or more precisely, each member of the IESG decides what (sadly) he should
> do to
> best serve in the role.
>
> But don't see the "job requirements" put out by NomCom as the IESG placing
> requirements.
> The NomCom asks the IESG what skills and tasks are needed in the view of
> the
> current IESG.
> The IESG serves up this information and NomCom can do with it as it likes.
>
> More important, the community can and should tell the NomCom what it wants
> the
> IESG to do and not do.
>

How can the community know what is happening on the table of NomCom or on
the table of IESG. They need to announce information of such requirements,
opportunities, questions, decisions,

I don't know what I want IESG/NomCom to do or not to do if I don't know
(i.e. receive announcements) why they are doing things in such way and why
they are not doing things in such way. We need good statistics information
of the past history (community discussions and IESG decisions and reasons),
we have a week history documentations but still we have old participants
discussing and can be good advisers (will take longer time in process than
documenting issues) today but not  sure of tomorrow. The General Area has
no WG, that means the IETF is weak in documentations of its decisions
reason history.

>
>
> > > It would be better for the IESG to take the initiative here and
> formally
> > > and publicly re-define the job, but it has so far ignored such
> requests.
>
> Which cuts into what Peter says since from where I sit there are many
> calls on
> the time of an AD and it would be useful to know which tasks the community
> would
> like me to not do (I think that I and my chief sponsor would both be happy
> if I
> spent more time working for them and less working as an AD).
>

I don't think I want to distroy few tasks of ADs, it is better to know what
makes them do what they are doing, did the past community ask them to do it
or it is the need of the job nature. We should be careful if we start to
think to reduce tasks, because there may be many consequences, I prefer
delegating tasks and AD just reviews and signs outputs,


>
> > It might be helpful to talk about what could change, such as:
> >
> > 1. Less/no time on document reviews.
>
> Right. Ask:
> Do the reviews currently done by ADs make a difference to the quality of
> individual documents or the overall canon?
>

Yes, IMHO, the ADs review is a MUST in the process.


> Would we be happy to publish RFCs with lower quality?
>

NO, any low quality output means low number of users/trusts, which will
distroy the IETF future,


> Are there other ways to reliably improve the quality (like, for example,
> the
> community doing proper reviews of their own work)?
>

This is true, the community SHOULD do more work, but don't forget that we
need more leaders, to direct the community which means we need more
diversity and quality.


> Could discussions of Discusses go more smoothly and take less effort?
>

Yes, but if every one respects each other, and if each WG chair never
ignores inputs to meetings/WG-list, and if ADs never ignore comments on
documents.

>
> Note:
> I spend more time (factor of more than 2) reviewing I-Ds when publication
> is
> requested (from a WG) than I do reviewing at IESG evaluation.
>

That is the key of IETF good quality and quality of Area outputs, so each
AD reviews all related Area documents.


>
> > 2. Less time managing working groups.
>
> Right. Ask:
> Does the management of working groups improve the output?
>
Yes, they SHOULD be responsible, as does the AD select the Chairs and can
fire them,


> Would we be happy to allow WGs to "muddle through"?
>
The WG is already responsible, so they should always comment on related
issues. I was always commenting in MANET WG, but some day I got a message
from the Chair saying that my messages on the list are very high and it is
disturbing the WG, which I think is reducing efforts and discouraging me to
add value. Some Lists in IETF still have personal response and some WG
documents are not acknowledging efforts, because their editors still think
the document is theirs not owned by WG.


> Could WG chairs somehow (magically?) take more responsibility and get
> stuff done
> (some chairs do)?
>

I think there should be more chairs if possible, but that depends on the
AD strategy or management,


>
> Note:
> A few of my WGs/chairs take most of my management time.
> I don't put a lot of time into managing WGs unless something goes badly
> wrong.
>

Things go wrong when the manager/Chair responsible ignores issues, and
leaves things for the future,


>
> > 3. Fewer working groups to manage.
>
> Right. Ask:
> Should an AD close a WG with a small number of people doing productive work
> slowly?
>

No, but a warning is good to encourage them to bring more people into the
WG. There is not person that cannot bring more interests in the IETF,
because IETF is a friendly environment and accepts remote participants, not
only f2f participants. Please note I understood that you mean small number
of all participants not only f2f participants.


> Should we refuse to open new WGs until we have finished other work?
>

No we never SHOULD discourage work for the Internet community, but
recharters of old WGs SHOULD not happen often, I prefer changing old names
and making joints between WGs when the time of charter expiry comes. I
prefer reducing numbers of individual documents not WGs, because don't
forget if you stop new WGs you may get many individual work into IETF.


> Could we reduce the number of WGs per AD by increasing the number of ADs?
>

Yes that might be but needs a good reason, this depends on IESG decisions.
I prefer creating assistant ADs and leaving only two ADs per Area.


>
> Note:
> Even if management of the WG is not issue, each WG produces documents to be
> managed, so reducing the number does have a direct impact.
>
Agree

>
>
> > 6. Less/no involvement with creating the schedule.
>
> Frankly, with the new tooling, this doesn't take more than a few hours per
> IETF
> meeting cycle.
> And that does point up a good question to ask the IESG in general - what
> additional tools could significantly reduce your work load?
>
Agree

>
> > Perhaps some time and motion studies are in order to figure out how ADs
> > spend their time. In my experience, document reviews required a major
> > time commitment.
>
> And, since I do track my time at quite a fine granularity...
>
> Email takes up a large lump.
> Got to skim the mailing lists for each of my WGs every week.
> Got to skim the mailing lists for other WGs in my area every month.
> Got to skim IETF-announce and IETF-disgust daily.
> Another 15 or so IETF lists that I skim weekly.
> A few related lists (such as NANOG) that I skim when I can.
> Emails directed to me that need attention "at once".
>
That is a good list of tasks, and I encourage not only ADs to do that but
ALL participants to do that,

>
>
> Please don't assume we ADs want this to be full time work.
> Please do tell us what you don't want us to do, and what you would like us
> to do
> less.
>

The AD SHOULD do less job in managing WGs, because WGs should not fight in
arguments, but they should be responsible to find the way without
directions from an AD. All participants should behave like the Chair in the
WG, this make the AD happy.


>
> Consider whether the "IETF management" could be separated from the
> "document
> quality".
>

That will be great if it is possible, but still the IETF SHOULD work harder
on its mentoring and marketing to get to that stage. Having participants
acting working hard like ADs will make WG quality which will make that
separation true ( separate of managment quality from document quality).

AB

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Thu, Oct 17, 2013 at 8:36 PM, Adrian Farrel <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk<=
/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">Hello,<br>
<div class=3D"im"><br>
&gt; &gt; The IESG defines the job and the IESG &#39;operates&#39; the mode=
l. =A0So yes,<br>
&gt; &gt; formally the IESG controls this issue.<br>
<br>
</div>Mutter.<br>
I suppose the seated IESG defines what it does.<br>
Or more precisely, each member of the IESG decides what (sadly) he should d=
o to<br>
best serve in the role.<br>
<br>
But don&#39;t see the &quot;job requirements&quot; put out by NomCom as the=
 IESG placing<br>
requirements.<br>
The NomCom asks the IESG what skills and tasks are needed in the view of th=
e<br>
current IESG.<br>
The IESG serves up this information and NomCom can do with it as it likes.<=
br>
<br>
More important, the community can and should tell the NomCom what it wants =
the<br>
IESG to do and not do.<br></blockquote><div>=A0</div><div>How can the commu=
nity know what is happening on the table of NomCom or on the table of IESG.=
 They=A0need to announce information of such requirements, opportunities, q=
uestions, decisions, </div>
<div>=A0</div><div>I don&#39;t=A0know what I want IESG/NomCom to do or not =
to do if I don&#39;t know (i.e. receive announcements)=A0why they are doing=
 things in such way and why they are not doing things in such way. We need =
good statistics information of the past history (community discussions and =
IESG decisions and reasons), we have a week history documentations but stil=
l we have old participants discussing and can be good advisers (will take l=
onger time in process than documenting issues) today but not=A0 sure of tom=
orrow. The General Area has no WG, that means the IETF is weak in documenta=
tions of its decisions reason history.</div>
<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">
<br>
<div class=3D"im"><br>
&gt; &gt; It would be better for the IESG to take the initiative here and f=
ormally<br>
&gt; &gt; and publicly re-define the job, but it has so far ignored such re=
quests.<br>
<br>
</div>Which cuts into what Peter says since from where I sit there are many=
 calls on<br>
the time of an AD and it would be useful to know which tasks the community =
would<br>
like me to not do (I think that I and my chief sponsor would both be happy =
if I<br>
spent more time working for them and less working as an AD).<br></blockquot=
e><div>=A0</div><div>I don&#39;t think=A0I want to distroy few tasks of ADs=
, it is better to know what makes them do what they are doing, did the past=
 community ask them to do it or it is the need of the job nature. We should=
 be careful if we start to think to reduce tasks, because there may be many=
 consequences, I prefer delegating tasks and AD just reviews and signs outp=
uts,</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
<div class=3D"im"><br>
&gt; It might be helpful to talk about what could change, such as:<br>
&gt;<br>
&gt; 1. Less/no time on document reviews.<br>
<br>
</div>Right. Ask:<br>
Do the reviews currently done by ADs make a difference to the quality of<br=
>
individual documents or the overall canon?<br></blockquote><div>=A0</div><d=
iv>Yes, IMHO, the ADs review is a MUST in the process.</div><div>=A0</div><=
blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-c=
olor:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">

Would we be happy to publish RFCs with lower quality?<br></blockquote><div>=
=A0</div><div>NO, any low quality output=A0means low number of users/trusts=
, which will distroy the IETF future,</div><div>=A0</div><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">

Are there other ways to reliably improve the quality (like, for example, th=
e<br>
community doing proper reviews of their own work)?<br></blockquote><div>=A0=
</div><div>This is true, the community SHOULD do more work, but=A0don&#39;t=
 forget that we need more leaders,=A0to direct the community which means we=
 need more diversity and quality.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
Could discussions of Discusses go more smoothly and take less effort?<br></=
blockquote><div>=A0</div><div>Yes, but if every one respects each other,=A0=
and if each WG chair=A0never ignores inputs to meetings/WG-list, and if ADs=
 never ignore comments on documents.</div>
<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">
<br>
Note:<br>
I spend more time (factor of more than 2) reviewing I-Ds when publication i=
s<br>
requested (from a WG) than I do reviewing at IESG evaluation.<br></blockquo=
te><div>=A0</div><div>That is the key of IETF good quality and quality of A=
rea outputs, so each AD=A0reviews=A0all related Area documents.</div><div>=
=A0</div>
<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">
<div class=3D"im"><br>
&gt; 2. Less time managing working groups.<br>
<br>
</div>Right. Ask:<br>
Does the management of working groups improve the output?<br></blockquote><=
div>Yes, they SHOULD be responsible, as does the AD select the Chairs and c=
an fire them,</div><div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.=
8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1=
px;border-left-style:solid" class=3D"gmail_quote">

Would we be happy to allow WGs to &quot;muddle through&quot;?<br></blockquo=
te><div>The WG is already responsible, so they should always comment on rel=
ated issues. I was always commenting in MANET WG, but some day I got a mess=
age from=A0the Chair saying that my messages on the list=A0are very high an=
d it is disturbing the WG, which I think is reducing efforts and discouragi=
ng me to add value.=A0Some Lists in IETF still have personal response and s=
ome WG documents are not acknowledging efforts, because their editors still=
 think the document is theirs not owned by WG.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
Could WG chairs somehow (magically?) take more responsibility and get stuff=
 done<br>
(some chairs do)?<br></blockquote><div>=A0</div><div>I think there should b=
e more chairs if possible, but that depends on the AD=A0strategy or managem=
ent,=A0</div><div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;pa=
dding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;bor=
der-left-style:solid" class=3D"gmail_quote">

<br>
Note:<br>
A few of my WGs/chairs take most of my management time.<br>
I don&#39;t put a lot of time into managing WGs unless something goes badly=
 wrong.<br></blockquote><div>=A0</div><div>Things go wrong when the manager=
/Chair responsible=A0ignores issues, and leaves things for the future,</div=
>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
<div class=3D"im"><br>
&gt; 3. Fewer working groups to manage.<br>
<br>
</div>Right. Ask:<br>
Should an AD close a WG with a small number of people doing productive work=
<br>
slowly?<br></blockquote><div>=A0</div><div>No, but a warning is good to enc=
ourage them to bring more people into the WG. There is not person that cann=
ot bring more=A0interests in the IETF, because IETF is a friendly environme=
nt and accepts remote participants, not only f2f participants. Please note =
I understood that you mean small number of all participants not only f2f pa=
rticipants.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
Should we refuse to open new WGs until we have finished other work?<br></bl=
ockquote><div>=A0</div><div>No we never SHOULD discourage work for the Inte=
rnet community, but recharters of old WGs SHOULD not happen often, I prefer=
 changing old names and making joints between WGs when the time of charter=
=A0expiry comes. I prefer reducing numbers of individual documents not WGs,=
 because don&#39;t forget if you stop new WGs you may get many individual w=
ork into IETF.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
Could we reduce the number of WGs per AD by increasing the number of ADs?<b=
r></blockquote><div>=A0</div><div>Yes that might be but needs a good reason=
, this depends on IESG decisions. I prefer creating assistant ADs and leavi=
ng only two ADs per Area.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
<br>
Note:<br>
Even if management of the WG is not issue, each WG produces documents to be=
<br>
managed, so reducing the number does have a direct impact.<br></blockquote>=
<div>Agree=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-le=
ft:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left=
-style:solid" class=3D"gmail_quote">

<div class=3D"im"><br>
<br>
&gt; 6. Less/no involvement with creating the schedule.<br>
<br>
</div>Frankly, with the new tooling, this doesn&#39;t take more than a few =
hours per IETF<br>
meeting cycle.<br>
And that does point up a good question to ask the IESG in general - what<br=
>
additional tools could significantly reduce your work load?<br></blockquote=
><div>Agree=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-l=
eft:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-lef=
t-style:solid" class=3D"gmail_quote">

<div class=3D"im"><br>
&gt; Perhaps some time and motion studies are in order to figure out how AD=
s<br>
&gt; spend their time. In my experience, document reviews required a major<=
br>
&gt; time commitment.<br>
<br>
</div>And, since I do track my time at quite a fine granularity...<br>
<br>
Email takes up a large lump.<br>
Got to skim the mailing lists for each of my WGs every week.<br>
Got to skim the mailing lists for other WGs in my area every month.<br>
Got to skim IETF-announce and IETF-disgust daily.<br>
Another 15 or so IETF lists that I skim weekly.<br>
A few related lists (such as NANOG) that I skim when I can.<br>
Emails directed to me that need attention &quot;at once&quot;.<br></blockqu=
ote><div>That is a good list of tasks, and I encourage not only ADs to do t=
hat but ALL participants to do that, </div><blockquote style=3D"margin:0px =
0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-le=
ft-width:1px;border-left-style:solid" class=3D"gmail_quote">

<br>
<br>
Please don&#39;t assume we ADs want this to be full time work.<br>
Please do tell us what you don&#39;t want us to do, and what you would like=
 us to do<br>
less.<br></blockquote><div>=A0</div><div>The AD SHOULD do less job in manag=
ing WGs, because WGs should not fight in arguments, but they should be resp=
onsible to find the way without directions from an AD. All participants sho=
uld behave like the Chair in the WG, this make the AD happy.</div>
<div>=A0</div><blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1e=
x;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-styl=
e:solid" class=3D"gmail_quote">
<br>
Consider whether the &quot;IETF management&quot; could be separated from th=
e &quot;document<br>
quality&quot;.<br></blockquote><div>=A0</div><div>That will be great if it =
is possible, but still the IETF SHOULD work harder on its mentoring and mar=
keting to get to that stage.=A0Having participants acting=A0working hard li=
ke=A0ADs will make WG quality which will make=A0that separation true ( sepa=
rate of managment quality from document quality).</div>
<div>=A0</div><div>AB=A0</div></div><br></div></div>

--047d7bdca8a45a342a04e9010a48--

From mehmet.ersue@nsn.com  Fri Oct 18 03:36:31 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 5D78611E817A for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 03:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.444
X-Spam-Level: 
X-Spam-Status: No, score=-105.444 tagged_above=-999 required=5 tests=[AWL=-1.155, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fa0NSBa1sLkP for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 03:36:24 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id DAFD311E8120 for <ietf@ietf.org>; Fri, 18 Oct 2013 03:36:23 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r9IAaLqP016923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 18 Oct 2013 12:36:21 +0200
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r9IAaKgQ032010 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Oct 2013 12:36:21 +0200
Received: from DEMUHTC011.nsn-intra.net (10.159.42.42) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 18 Oct 2013 12:36:20 +0200
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.164]) by DEMUHTC011.nsn-intra.net ([10.159.42.42]) with mapi id 14.03.0123.003; Fri, 18 Oct 2013 12:36:20 +0200
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ietf@ietf.org" <ietf@ietf.org>, "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.com>
Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Topic: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Index: AQHOy0TyEXSOOfxdYECGejerVLbJzJn6Q11Q
Date: Fri, 18 Oct 2013 10:36:19 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com>
In-Reply-To: <20131017142434.21877.63746.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.159.42.106]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
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: 3236
X-purgate-ID: 151667::1382092581-00005753-B54E3A7B/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: Fri, 18 Oct 2013 10:36:40 -0000

SGkgQWxsaXNvbiwNCg0KaW4geW91ciBtb2RlbCB5b3UgZG9uJ3QgY291bnQgdGhvc2UgcGVvcGxl
IHdobyBoYXZlIGJlZW4gcmVqZWN0aW5nIHRvIGEgbm9taW5hdGlvbiwgDQpqdXN0IGJlY2F1c2Ug
dGhleSBiZWxpZXZlIHRoZSBjdXJyZW50IEFEIGRpZCBhIHZlcnkgZ29vZCBqb2IgYW5kIGhlL3No
ZSBzaG91bGQgYmUgcmVlbGVjdGVkLg0KDQpTbyB0aGUgc2l0dWF0aW9uIGlzIG5vdCB0aGF0IGJh
ZCwgaWYgdGhlcmUgaXMgb25seSB0aGUgY3VycmVudCBBRCBvbiB0aGUgbm9taW5lZSBsaXN0Lg0K
DQpDaGVlcnMsIA0KTWVobWV0IA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZy
b206IGlldGYtYW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYW5ub3VuY2Ut
Ym91bmNlc0BpZXRmLm9yZ10gT24NCj4gQmVoYWxmIE9mIGV4dCBOb21Db20gQ2hhaXIgMjAxMw0K
PiBTZW50OiBUaHVyc2RheSwgT2N0b2JlciAxNywgMjAxMyA0OjI1IFBNDQo+IFRvOiBJRVRGIEFu
bm91bmNlbWVudCBMaXN0DQo+IENjOiBJRVRGIERpc2N1c3MNCj4gU3ViamVjdDogTk9NQ09NIC0g
Q3JpdGljYWwgc2hvcnRhZ2Ugb2Ygbm9taW5lZXMgZm9yIG11bHRpcGxlIGFyZWFzDQo+IA0KPiBb
Q2F0Y2hpZXIgU3ViamVjdCBsaW5lIC0gYXBvbG9naWVzIHRvIHRob3NlIG9mZmVuZGVkIGJ5IGEg
ZHVwbGljYXRlXQ0KPiANCj4gQSBjcml0aWNhbGx5IGxvdyBudW1iZXIgb2YgcGVvcGxlIGhhdmUg
YWNjZXB0ZWQgbm9taW5hdGlvbnMgZm9yIHNvbWUgb2YgdGhlDQo+IElFU0cgb3BlbiBwb3NpdGlv
bnMuICBUaGVyZSBpcyBvbmx5IG9uZSBub21pbmVlIHBlciBzbG90IGluIEFQUCwgT1BTIGFuZCBU
U1YsDQo+IG9ubHkgdHdvIGluIElOVCBhbmQgUkFJLiAgTWFueSBmb2xrcyBoYXZlIGRlY2xpbmVk
IG5vbWluYXRpb25zLg0KPiANCj4gV2hpbGUgdGhlIE5vbWNvbSBhcHByZWNpYXRlcyB0aGF0IHN1
cHBvcnQgZm9yIHR3byB5ZWFycyBvZiBpbnRlbnNlIHNlcnZpY2UNCj4gaXMgaGFyZCB0byBhc3N1
cmUsIGFuZCB3aGlsZSB3ZSBhcmUgYXdhcmUgdGhhdCB0aGVyZSBpcyBtdWNoIHN1cHBvcnQgZm9y
IHRoZQ0KPiBpbmN1bWJlbnRzIHdobyBhcmUgc3RhbmRpbmcsIHRoZSBJRVRGIHNob3VsZCBjb250
aW51YWxseSBiZSBjb25zaWRlcmluZw0KPiB3aGljaCBuZXcgdGFsZW50IGlzIGF2YWlsYWJsZSBm
b3Igb3VyIGxlYWRlcnNoaXAsIGFuZCB0aGUgTm9tY29tIHByb2Nlc3MNCj4gbmVlZHMgZm9yIHRo
ZXJlIHRvIGJlIHNvbWUgcmV2aWV3IGFuZCBkZWxpYmVyYXRpb24uDQo+IA0KPiBUaGVyZWZvcmUs
IHdlIHVyZ2VudGx5IHJlcXVlc3QgdGhhdCBtb3JlIG5vbWluZWVzIGNvbWUgZm9yd2FyZC4NCj4g
DQo+IERFQURMSU5FUw0KPiBOb21pbmF0aW9ucyAtIE9jdG9iZXIgMTgNCj4gUXVlc3Rpb25uYWly
ZXMgZnJvbSBub21pbmVlcyAtIE9jdG9iZXIgMjUNCj4gDQo+IE5vdCBjb2luY2lkZW50YWxseSwg
dGhpcyBpcyBhIGdvb2QgdGltZSB0byB0aGluayBvdmVyIGFuZCBzZW5kIHlvdXIgY29tbWVudHMN
Cj4gYWJvdXQgdGhlIGN1cnJlbnQgc3RhdGVtZW50cyBvZiBkZXNpcmVkIGV4cGVydGlzZSBvZiBw
b3NpdGlvbnMgLSB0aGlzIGlzIHBhcnQgb2YNCj4gdGhlIE5vbWNvbSdzIGFubnVhbCByZXZpZXcg
cHJvY2VzcyBhcyB3ZWxsLiAgU2VuZCB0aGVtIHRvIG5vbWNvbTEzQGlldGYub3JnLg0KPiANCj4g
RGVmaW5pdGl2ZSBsb2NhdGlvbiBbKl0gb2YgdGhlIGN1cnJlbnQgc3RhdGVtZW50cyBvbiBkZXNp
cmVkIGV4cGVydGlzZToNCj4gICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9ub21j
b20vMjAxMy9leHBlcnRpc2UvDQo+IA0KPiBJbnN0cnVjdGlvbnMgYW5kIGRldGFpbHMgb24gbm9t
aW5hdGlvbiBbKipdOg0KPiAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Fubi9u
b21jb20vNjA2MDIvDQo+IA0KPiBUaGFua3MsIGV2ZXJ5b25lLA0KPiANCj4gQWxsaXNvbiBmb3Ig
dGhlIE5vbWNvbQ0KPiANCj4gWypdIFRoaXMgeWVhciB0aGUgTm9tY29tIHRvb2xzIHdlcmUgcmVj
b2RlZCwgYW5kIGFsc28gdHJhbnNpdGlvbmVkIGludG8gdGhlDQo+IGRhdGF0cmFja2VyLiAgQXBv
bG9naWVzIGZvciBhIG51bWJlciBvZiBwbGFjZXMgd2hlcmUgd2UgZGlkbid0IGNhdGNoIHJlZmVy
ZW5jZQ0KPiBlcnJvcnMuDQo+IA0KPiBbKipdIFllcywgYWxhcywgdGhlIHByZXZpb3VzIGNhbGwg
Zm9yIG5vbWluYXRpb25zIHVzZWQgIk9BTSIgaW5zdGVhZCBvZiAiT1BTLCIgYnV0DQo+IHdlIGhh
dmUqIGNvcnJlY3RlZCB0aGlzIChjaGFpcidzIHBpbG90KSBlcnJvciB3aGVyZSBpdCBvY2N1cnJl
ZCBpbiB0aGUgTm9tY29tDQo+IHBhZ2VzLg0K

From andrew.hutton@unify.com  Fri Oct 18 03:59:35 2013
Return-Path: <andrew.hutton@unify.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 165BA21F89F7; Fri, 18 Oct 2013 03:59: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 ThDa+cufE9Hw; Fri, 18 Oct 2013 03:59:30 -0700 (PDT)
Received: from senmx12-mx.siemens-enterprise.com (senmx12-mx.siemens-enterprise.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id AA75911E81EC; Fri, 18 Oct 2013 03:59:26 -0700 (PDT)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by senmx12-mx.siemens-enterprise.com (Server) with ESMTP id C26F823F0599; Fri, 18 Oct 2013 12:59:25 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.31]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Fri, 18 Oct 2013 12:58:43 +0200
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Russ Housley <housley@vigilsec.com>
Subject: RE: Gen-ART review of draft-ietf-siprec-architecture-08
Thread-Topic: Gen-ART review of draft-ietf-siprec-architecture-08
Thread-Index: AQHOuKgtbshaq01LM0O5TvFDNdoaaJn6cKjQ
Date: Fri, 18 Oct 2013 10:59:24 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17BF97F7@MCHP04MSX.global-ad.net>
References: <D9D05CBD-95E0-4CB1-99AF-53AA6E0EAA1D@vigilsec.com>
In-Reply-To: <D9D05CBD-95E0-4CB1-99AF-53AA6E0EAA1D@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-siprec-architecture.all@tools.ietf.org" <draft-ietf-siprec-architecture.all@tools.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: Fri, 18 Oct 2013 10:59:35 -0000

Hi Russ,

An update to this draft has been posted and I believe it addresses your com=
ments.

See http://www.ietf.org/internet-drafts/draft-ietf-siprec-architecture-09.t=
xt=20

Regards
Andy


> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: 23 September 2013 23:00
> To: draft-ietf-siprec-architecture.all@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-siprec-architecture-08
>=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>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-siprec-architecture-08
> Reviewer: Russ Housley
> Review Date: 2013-09-23
> IETF LC End Date: 2013-10-01
> IESG Telechat date: Unknown
>=20
> Summary:
>=20
> Major Concerns:
>=20
> The use of "required" in Section 3.2.4 is confusing to me.  It says:
>=20
>    In a basic session involving only audio there are typically two
> audio
>    /RTP streams between the two UAs involved transporting media in each
>    direction.  When recording this media the two streams may be mixed
> at
>    the SRC before being transmitted to the SRS or it may be required
>    that the media streams are not mixed and are sent to the SRS as two
>    separate streams.
>=20
> Is this a requirement that the SRC imposes on the SRS?  Please clarify.
>=20
>=20
> Minor Concerns:
>=20
> The definitions include:
>=20
>    Recording unaware User Agent (UA): A SIP User Agent that is unaware
>    of SIP extensions associated with the Communication Session.  Such
>    Recording unaware UA will be notified that a session is being
>    recorded or express preferences as to whether a recording should be
>    started, paused, resumed or stopped via some other means that is out
>    of scope of SIPREC.
>=20
> There is no definition of SIPREC.  Perhaps it could simply say:
>=20
>    ... is out of scope for the SIP media recording architecture.
>=20
> Note that "SIPREC" does occur a few other places in the document, and
> this approach to the replacement seems to work for them too.
>=20
> Of course, the alternative it to define SIPREC.
>=20
>=20
> Section 5 talks about encryption of the media stream, but it does not
> offer any suggestions about the protection of the stored media.  I
> doubt that there is a simple bit of advice, but implementers should
> be warned against strong protection of the media during transmission
> and then providing no protection to the stored media.
>=20
>=20
> Other Comments:
>=20
> The introduction defines these two acronyms: Session Recording
> Client (SRC) and the Session Recording Server (SRS).  However, they are
> spelled out many times throughout the introduction.  These acronyms are
> not really used until after the definitions section.  I suggest using
> them throughout the document.
>=20
>=20
> There is a period missing at the end of the first sentence in
> Section 3.1.2.
>=20
> In Section 	3.2.2, it says:
>=20
>    o Identifies the sessions that is to be recorded. ...
>=20
> This should say "sessions that are to be recorded".
>=20
>=20
> There is a period missing at the end of the last bullet in
> Section 3.2.2.
>=20


From kathleen.moriarty@emc.com  Fri Oct 18 05:40:58 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 A387111E822E for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 05:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.369
X-Spam-Level: 
X-Spam-Status: No, score=-1.369 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_00=-2.599, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzKr19Fco-mi for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 05:40:53 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id EACA611E8276 for <ietf@ietf.org>; Fri, 18 Oct 2013 05:40:30 -0700 (PDT)
Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9ICeMar022150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Oct 2013 08:40:24 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r9ICeMar022150
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1382100024; bh=3Io0zwH62TXTkwRLwgXdV3M6Rws=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=Mu+QVMumbFPFicP7kqzcCQTr6sDSgB52Rstsr57993Ae2ylpe5+tJqKnXXDZZFI+z 1KNuAFLfjUdoBXHKMXKO5WOvMOOSEP1uTBpfFR+XNJrD3mZ5H/pr807hUayqVeY7Ac DTRloehjeRkQCFKGFus0yja9KRpO0bgji0RVKHrw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com r9ICeMar022150
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd51.lss.emc.com (RSA Interceptor); Fri, 18 Oct 2013 08:40:07 -0400
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9ICe667017159 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Oct 2013 08:40:07 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub34.corp.emc.com ([::1]) with mapi; Fri, 18 Oct 2013 08:40:06 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, "ietf@ietf.org" <ietf@ietf.org>, "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.com>
Date: Fri, 18 Oct 2013 08:40:04 -0400
Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Topic: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Index: AQHOy0TyEXSOOfxdYECGejerVLbJzJn6Q11QgAAiFWA=
Message-ID: <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net>
In-Reply-To: <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: DLM_1, public
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 12:40:59 -0000

SXQgaXMgaW1wb3J0YW50IGZvciBtdWx0aXBsZSBwZW9wbGUgdG8gcnVuIGV2ZW4gd2hlbiB0aGVy
ZSBpcyBhbiBpbmN1bWJlbnQgZm9yIGEgZmFpciBwcm9jZXNzLiAgV2hlbiBTdGVwaGVuIEZhcnJl
bGwgcmFuIGZvciBTZWMgQUQgYWdhaW4gbGFzdCB5ZWFyLCBoZSBlbmNvdXJhZ2VkIG1lIHRvIGFj
Y2VwdCB0aGUgbm9taW5hdGlvbiBhbmQgcnVuIGFnYWluc3QgaGltIHNvIHRoYXQgdGhlcmUgd2Fz
IGEgZ29vZCBjYW5kaWRhdGUgdG8gbWFrZSB0aGUgcHJvY2VzcyBhIGJpdCBtb3JlIGZhaXIuICBJ
ZiBlaXRoZXIgU3RlcGhlbiBvZiBTZWFuIHdvbiB0aGUgbG90dGVyeSwgdGhlIE5vbmNvbSB3b3Vs
ZCBhdCBsZWFzdCBoYXZlIGdvbmUgdGhyb3VnaCB0aGUgaW50ZXJ2aWV3IGFuZCByZXZpZXcgcHJv
Y2VzcyB3aXRoIG90aGVyIGNhbmRpZGF0ZXMgaW4gYWR2YW5jZS4gIFRoZSBjYW5kaWRhdGUgd291
bGQgaGF2ZSB3b3JrZWQgdGhyb3VnaCB0aGUgcG9zc2liaWxpdHkgb2Ygd2hhdCB0aGlzIG1lYW50
IHdpdGggdGhlaXIgam9iIGFuZCB0aGF0IGl0IHdhcyBwb3NzaWJsZSBmb3IgdGhlbSB0byB0YWtl
IG9uIHRoaXMgcm9sZSAobm90IGluc2lnbmlmaWNhbnQgZm9yIG1hbnkgb2YgdXMpLiAgRm9yIG1l
LCBJIHRob3VnaHQgU3RlcGhlbiB3YXMgZG9pbmcgYSBmaW5lIGpvYiBhbmQgYW0gZ2xhZCBoZSB3
YXMgcHV0IGJhY2sgb24gdGhlIElFU0csIGJ1dCBpdCBpcyBnb29kIGZvciB0aGUgTm9uY29tIHRv
IGhhdmUgb3B0aW9ucyBhbmQgYmFja3VwIHBsYW5zLiAgSSByZWNlaXZlZCBhcHByb3ZhbCBmcm9t
IG15IGNvbXBhbnksIGJ1dCBsZXQgbXkgbWFuYWdlbWVudCBrbm93IHRoYXQgaXQgd2FzIHVubGlr
ZWx5IHRoYXQgSSB3b3VsZCBiZSBzZWxlY3RlZCBzaW5jZSBpbmN1bWJlbnRzIHVzdWFsbHkgcmV0
dXJuLiANCg0KTWF5YmUgZm9sa3Mgc2hvdWxkIGNvbnNpZGVyIHJ1bm5pbmcgYWdhaW5zdCBhbiBp
bmN1bWJlbnQuICBZb3UgbGVhcm4gdGhlIHByb2Nlc3MgYW5kIGl0IGZvcmNlcyB5b3UgdG8gZmln
dXJlIG91dCBpZiB5b3UgYXJlIGludGVyZXN0ZWQgaW4gdGhlIHJvbGUgYW5kIGNvdWxkIGFsbG9j
YXRlIHRoYXQgdGltZSB0byB0aGUgSUVURi4gIEkgZ2F2ZSBhIHBvc2l0aXZlIHJldmlldyBvZiBT
dGVwaGVuIHdoZW4gcnVubmluZyBhZ2FpbnN0IGhpbS4NCg0KVGhhbmtzLA0KS2F0aGxlZW4NCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBb
bWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEVyc3VlLCBNZWhtZXQg
KE5TTiAtIERFL011bmljaCkNClNlbnQ6IEZyaWRheSwgT2N0b2JlciAxOCwgMjAxMyA2OjM2IEFN
DQpUbzogaWV0ZkBpZXRmLm9yZzsgTm9tY29tQGlldGZhLmFtc2wuY29tOyBDaGFpckBpZXRmYS5h
bXNsLmNvbQ0KU3ViamVjdDogUkU6IE5PTUNPTSAtIENyaXRpY2FsIHNob3J0YWdlIG9mIG5vbWlu
ZWVzIGZvciBtdWx0aXBsZSBhcmVhcw0KDQpIaSBBbGxpc29uLA0KDQppbiB5b3VyIG1vZGVsIHlv
dSBkb24ndCBjb3VudCB0aG9zZSBwZW9wbGUgd2hvIGhhdmUgYmVlbiByZWplY3RpbmcgdG8gYSBu
b21pbmF0aW9uLCBqdXN0IGJlY2F1c2UgdGhleSBiZWxpZXZlIHRoZSBjdXJyZW50IEFEIGRpZCBh
IHZlcnkgZ29vZCBqb2IgYW5kIGhlL3NoZSBzaG91bGQgYmUgcmVlbGVjdGVkLg0KDQpTbyB0aGUg
c2l0dWF0aW9uIGlzIG5vdCB0aGF0IGJhZCwgaWYgdGhlcmUgaXMgb25seSB0aGUgY3VycmVudCBB
RCBvbiB0aGUgbm9taW5lZSBsaXN0Lg0KDQpDaGVlcnMsDQpNZWhtZXQgDQoNCj4gLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3Jn
IA0KPiBbbWFpbHRvOmlldGYtYW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m
IGV4dCBOb21Db20gQ2hhaXIgDQo+IDIwMTMNCj4gU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMTcs
IDIwMTMgNDoyNSBQTQ0KPiBUbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdA0KPiBDYzogSUVURiBE
aXNjdXNzDQo+IFN1YmplY3Q6IE5PTUNPTSAtIENyaXRpY2FsIHNob3J0YWdlIG9mIG5vbWluZWVz
IGZvciBtdWx0aXBsZSBhcmVhcw0KPiANCj4gW0NhdGNoaWVyIFN1YmplY3QgbGluZSAtIGFwb2xv
Z2llcyB0byB0aG9zZSBvZmZlbmRlZCBieSBhIGR1cGxpY2F0ZV0NCj4gDQo+IEEgY3JpdGljYWxs
eSBsb3cgbnVtYmVyIG9mIHBlb3BsZSBoYXZlIGFjY2VwdGVkIG5vbWluYXRpb25zIGZvciBzb21l
IA0KPiBvZiB0aGUgSUVTRyBvcGVuIHBvc2l0aW9ucy4gIFRoZXJlIGlzIG9ubHkgb25lIG5vbWlu
ZWUgcGVyIHNsb3QgaW4gDQo+IEFQUCwgT1BTIGFuZCBUU1YsIG9ubHkgdHdvIGluIElOVCBhbmQg
UkFJLiAgTWFueSBmb2xrcyBoYXZlIGRlY2xpbmVkIG5vbWluYXRpb25zLg0KPiANCj4gV2hpbGUg
dGhlIE5vbWNvbSBhcHByZWNpYXRlcyB0aGF0IHN1cHBvcnQgZm9yIHR3byB5ZWFycyBvZiBpbnRl
bnNlIA0KPiBzZXJ2aWNlIGlzIGhhcmQgdG8gYXNzdXJlLCBhbmQgd2hpbGUgd2UgYXJlIGF3YXJl
IHRoYXQgdGhlcmUgaXMgbXVjaCANCj4gc3VwcG9ydCBmb3IgdGhlIGluY3VtYmVudHMgd2hvIGFy
ZSBzdGFuZGluZywgdGhlIElFVEYgc2hvdWxkIA0KPiBjb250aW51YWxseSBiZSBjb25zaWRlcmlu
ZyB3aGljaCBuZXcgdGFsZW50IGlzIGF2YWlsYWJsZSBmb3Igb3VyIA0KPiBsZWFkZXJzaGlwLCBh
bmQgdGhlIE5vbWNvbSBwcm9jZXNzIG5lZWRzIGZvciB0aGVyZSB0byBiZSBzb21lIHJldmlldyBh
bmQgZGVsaWJlcmF0aW9uLg0KPiANCj4gVGhlcmVmb3JlLCB3ZSB1cmdlbnRseSByZXF1ZXN0IHRo
YXQgbW9yZSBub21pbmVlcyBjb21lIGZvcndhcmQuDQo+IA0KPiBERUFETElORVMNCj4gTm9taW5h
dGlvbnMgLSBPY3RvYmVyIDE4DQo+IFF1ZXN0aW9ubmFpcmVzIGZyb20gbm9taW5lZXMgLSBPY3Rv
YmVyIDI1DQo+IA0KPiBOb3QgY29pbmNpZGVudGFsbHksIHRoaXMgaXMgYSBnb29kIHRpbWUgdG8g
dGhpbmsgb3ZlciBhbmQgc2VuZCB5b3VyIA0KPiBjb21tZW50cyBhYm91dCB0aGUgY3VycmVudCBz
dGF0ZW1lbnRzIG9mIGRlc2lyZWQgZXhwZXJ0aXNlIG9mIA0KPiBwb3NpdGlvbnMgLSB0aGlzIGlz
IHBhcnQgb2YgdGhlIE5vbWNvbSdzIGFubnVhbCByZXZpZXcgcHJvY2VzcyBhcyB3ZWxsLiAgU2Vu
ZCB0aGVtIHRvIG5vbWNvbTEzQGlldGYub3JnLg0KPiANCj4gRGVmaW5pdGl2ZSBsb2NhdGlvbiBb
Kl0gb2YgdGhlIGN1cnJlbnQgc3RhdGVtZW50cyBvbiBkZXNpcmVkIGV4cGVydGlzZToNCj4gICAg
ICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9ub21jb20vMjAxMy9leHBlcnRpc2UvDQo+
IA0KPiBJbnN0cnVjdGlvbnMgYW5kIGRldGFpbHMgb24gbm9taW5hdGlvbiBbKipdOg0KPiAgICAg
ICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Fubi9ub21jb20vNjA2MDIvDQo+IA0KPiBU
aGFua3MsIGV2ZXJ5b25lLA0KPiANCj4gQWxsaXNvbiBmb3IgdGhlIE5vbWNvbQ0KPiANCj4gWypd
IFRoaXMgeWVhciB0aGUgTm9tY29tIHRvb2xzIHdlcmUgcmVjb2RlZCwgYW5kIGFsc28gdHJhbnNp
dGlvbmVkIA0KPiBpbnRvIHRoZSBkYXRhdHJhY2tlci4gIEFwb2xvZ2llcyBmb3IgYSBudW1iZXIg
b2YgcGxhY2VzIHdoZXJlIHdlIA0KPiBkaWRuJ3QgY2F0Y2ggcmVmZXJlbmNlIGVycm9ycy4NCj4g
DQo+IFsqKl0gWWVzLCBhbGFzLCB0aGUgcHJldmlvdXMgY2FsbCBmb3Igbm9taW5hdGlvbnMgdXNl
ZCAiT0FNIiBpbnN0ZWFkIA0KPiBvZiAiT1BTLCIgYnV0IHdlIGhhdmUqIGNvcnJlY3RlZCB0aGlz
IChjaGFpcidzIHBpbG90KSBlcnJvciB3aGVyZSBpdCANCj4gb2NjdXJyZWQgaW4gdGhlIE5vbWNv
bSBwYWdlcy4NCg==

From hallam@gmail.com  Fri Oct 18 05:47:40 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 7C3E811E822E for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 05:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5 tests=[AWL=-1.148, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZk097Ma4G+J for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 05:47:39 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 65E1A11E82A4 for <ietf@ietf.org>; Fri, 18 Oct 2013 05:47:36 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id el20so547470lab.2 for <ietf@ietf.org>; Fri, 18 Oct 2013 05:47: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=HmzngGwsvlQVBY31I7GXd0bScX3VvvqbkmpoD/9rN6Q=; b=WO79advi0r3Ke6QtmLcW6FVc9wsDvtAmqQGv5f6ezDt4w/sZpm0xutvGnw9lvNYZLa 2cF6dHRpxfKDwgOBSWYEEc0bywQG8K40Ijv/1U4/loLxFBTisqChP1k5k13ghjdWDfcX RIS4IuMt5S7OU2BQaiy7rszioVEYspSn5G+tlaxsAZTNm9JPCnwxwRj8Zx0IhTjSrBUa a4tfYIQseLc2CPxay+5E5slh87EG8mEVBnO5QMHeXApjifLjANhkCCphO/UKwVgMAVEk cvE1NrRwU5PJZqq8AjnCFn3RETC3kuAJNIw/i9J9q5CojVM2YFhm41ApY9NrGp1zIHGF gZ4Q==
MIME-Version: 1.0
X-Received: by 10.112.51.227 with SMTP id n3mr154775lbo.54.1382100455235; Fri, 18 Oct 2013 05:47:35 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Fri, 18 Oct 2013 05:47:35 -0700 (PDT)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com>
Date: Fri, 18 Oct 2013 08:47:35 -0400
Message-ID: <CAMm+Lwgd_G8ZajwnCqT=OESS3J9vb4h0MdpwYLUPTYKNEmOHGw@mail.gmail.com>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: multipart/alternative; boundary=001a1133c2d2ada7d304e9035677
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "ietf@ietf.org" <ietf@ietf.org>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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, 18 Oct 2013 12:47:40 -0000

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

Or look back to a previous Security AD appointment when the incumbent
became unavailable because he was appointed IETF Chair.


On Fri, Oct 18, 2013 at 8:40 AM, Moriarty, Kathleen <
kathleen.moriarty@emc.com> wrote:

> It is important for multiple people to run even when there is an incumbent
> for a fair process.  When Stephen Farrell ran for Sec AD again last year,
> he encouraged me to accept the nomination and run against him so that there
> was a good candidate to make the process a bit more fair.  If either
> Stephen of Sean won the lottery, the Noncom would at least have gone
> through the interview and review process with other candidates in advance.
>  The candidate would have worked through the possibility of what this meant
> with their job and that it was possible for them to take on this role (not
> insignificant for many of us).  For me, I thought Stephen was doing a fine
> job and am glad he was put back on the IESG, but it is good for the Noncom
> to have options and backup plans.  I received approval from my company, but
> let my management know that it was unlikely that I would be selected since
> incumbents usually return.
>
> Maybe folks should consider running against an incumbent.  You learn the
> process and it forces you to figure out if you are interested in the role
> and could allocate that time to the IETF.  I gave a positive review of
> Stephen when running against him.
>
> Thanks,
> Kathleen
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Ersue, Mehmet (NSN - DE/Munich)
> Sent: Friday, October 18, 2013 6:36 AM
> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
>
> Hi Allison,
>
> in your model you don't count those people who have been rejecting to a
> nomination, just because they believe the current AD did a very good job
> and he/she should be reelected.
>
> So the situation is not that bad, if there is only the current AD on the
> nominee list.
>
> Cheers,
> Mehmet
>
> > -----Original Message-----
> > From: ietf-announce-bounces@ietf.org
> > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair
> > 2013
> > Sent: Thursday, October 17, 2013 4:25 PM
> > To: IETF Announcement List
> > Cc: IETF Discuss
> > Subject: NOMCOM - Critical shortage of nominees for multiple areas
> >
> > [Catchier Subject line - apologies to those offended by a duplicate]
> >
> > A critically low number of people have accepted nominations for some
> > of the IESG open positions.  There is only one nominee per slot in
> > APP, OPS and TSV, only two in INT and RAI.  Many folks have declined
> nominations.
> >
> > While the Nomcom appreciates that support for two years of intense
> > service is hard to assure, and while we are aware that there is much
> > support for the incumbents who are standing, the IETF should
> > continually be considering which new talent is available for our
> > leadership, and the Nomcom process needs for there to be some review and
> deliberation.
> >
> > Therefore, we urgently request that more nominees come forward.
> >
> > DEADLINES
> > Nominations - October 18
> > Questionnaires from nominees - October 25
> >
> > Not coincidentally, this is a good time to think over and send your
> > comments about the current statements of desired expertise of
> > positions - this is part of the Nomcom's annual review process as well.
>  Send them to nomcom13@ietf.org.
> >
> > Definitive location [*] of the current statements on desired expertise:
> >       https://datatracker.ietf.org/nomcom/2013/expertise/
> >
> > Instructions and details on nomination [**]:
> >       https://datatracker.ietf.org/ann/nomcom/60602/
> >
> > Thanks, everyone,
> >
> > Allison for the Nomcom
> >
> > [*] This year the Nomcom tools were recoded, and also transitioned
> > into the datatracker.  Apologies for a number of places where we
> > didn't catch reference errors.
> >
> > [**] Yes, alas, the previous call for nominations used "OAM" instead
> > of "OPS," but we have* corrected this (chair's pilot) error where it
> > occurred in the Nomcom pages.
>



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

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

<div dir=3D"ltr">Or look back to a previous Security AD appointment when th=
e incumbent became unavailable because he was appointed IETF Chair.<br><div=
 class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Oct 18, 2=
013 at 8:40 AM, Moriarty, Kathleen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
kathleen.moriarty@emc.com" target=3D"_blank">kathleen.moriarty@emc.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">It is important for multiple people to run e=
ven when there is an incumbent for a fair process. =A0When Stephen Farrell =
ran for Sec AD again last year, he encouraged me to accept the nomination a=
nd run against him so that there was a good candidate to make the process a=
 bit more fair. =A0If either Stephen of Sean won the lottery, the Noncom wo=
uld at least have gone through the interview and review process with other =
candidates in advance. =A0The candidate would have worked through the possi=
bility of what this meant with their job and that it was possible for them =
to take on this role (not insignificant for many of us). =A0For me, I thoug=
ht Stephen was doing a fine job and am glad he was put back on the IESG, bu=
t it is good for the Noncom to have options and backup plans. =A0I received=
 approval from my company, but let my management know that it was unlikely =
that I would be selected since incumbents usually return.<br>

<br>
Maybe folks should consider running against an incumbent. =A0You learn the =
process and it forces you to figure out if you are interested in the role a=
nd could allocate that time to the IETF. =A0I gave a positive review of Ste=
phen when running against him.<br>

<br>
Thanks,<br>
Kathleen<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] O=
n Behalf Of Ersue, Mehmet (NSN - DE/Munich)<br>
Sent: Friday, October 18, 2013 6:36 AM<br>
To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"mailto:N=
omcom@ietfa.amsl.com">Nomcom@ietfa.amsl.com</a>; <a href=3D"mailto:Chair@ie=
tfa.amsl.com">Chair@ietfa.amsl.com</a><br>
Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas<br>
<br>
Hi Allison,<br>
<br>
in your model you don&#39;t count those people who have been rejecting to a=
 nomination, just because they believe the current AD did a very good job a=
nd he/she should be reelected.<br>
<br>
So the situation is not that bad, if there is only the current AD on the no=
minee list.<br>
<br>
Cheers,<br>
Mehmet<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:ietf-announce-bounces@ietf.org">ietf-announce-=
bounces@ietf.org</a><br>
&gt; [mailto:<a href=3D"mailto:ietf-announce-bounces@ietf.org">ietf-announc=
e-bounces@ietf.org</a>] On Behalf Of ext NomCom Chair<br>
&gt; 2013<br>
&gt; Sent: Thursday, October 17, 2013 4:25 PM<br>
&gt; To: IETF Announcement List<br>
&gt; Cc: IETF Discuss<br>
&gt; Subject: NOMCOM - Critical shortage of nominees for multiple areas<br>
&gt;<br>
&gt; [Catchier Subject line - apologies to those offended by a duplicate]<b=
r>
&gt;<br>
&gt; A critically low number of people have accepted nominations for some<b=
r>
&gt; of the IESG open positions. =A0There is only one nominee per slot in<b=
r>
&gt; APP, OPS and TSV, only two in INT and RAI. =A0Many folks have declined=
 nominations.<br>
&gt;<br>
&gt; While the Nomcom appreciates that support for two years of intense<br>
&gt; service is hard to assure, and while we are aware that there is much<b=
r>
&gt; support for the incumbents who are standing, the IETF should<br>
&gt; continually be considering which new talent is available for our<br>
&gt; leadership, and the Nomcom process needs for there to be some review a=
nd deliberation.<br>
&gt;<br>
&gt; Therefore, we urgently request that more nominees come forward.<br>
&gt;<br>
&gt; DEADLINES<br>
&gt; Nominations - October 18<br>
&gt; Questionnaires from nominees - October 25<br>
&gt;<br>
&gt; Not coincidentally, this is a good time to think over and send your<br=
>
&gt; comments about the current statements of desired expertise of<br>
&gt; positions - this is part of the Nomcom&#39;s annual review process as =
well. =A0Send them to <a href=3D"mailto:nomcom13@ietf.org">nomcom13@ietf.or=
g</a>.<br>
&gt;<br>
&gt; Definitive location [*] of the current statements on desired expertise=
:<br>
&gt; =A0 =A0 =A0 <a href=3D"https://datatracker.ietf.org/nomcom/2013/expert=
ise/" target=3D"_blank">https://datatracker.ietf.org/nomcom/2013/expertise/=
</a><br>
&gt;<br>
&gt; Instructions and details on nomination [**]:<br>
&gt; =A0 =A0 =A0 <a href=3D"https://datatracker.ietf.org/ann/nomcom/60602/"=
 target=3D"_blank">https://datatracker.ietf.org/ann/nomcom/60602/</a><br>
&gt;<br>
&gt; Thanks, everyone,<br>
&gt;<br>
&gt; Allison for the Nomcom<br>
&gt;<br>
&gt; [*] This year the Nomcom tools were recoded, and also transitioned<br>
&gt; into the datatracker. =A0Apologies for a number of places where we<br>
&gt; didn&#39;t catch reference errors.<br>
&gt;<br>
&gt; [**] Yes, alas, the previous call for nominations used &quot;OAM&quot;=
 instead<br>
&gt; of &quot;OPS,&quot; but we have* corrected this (chair&#39;s pilot) er=
ror where it<br>
&gt; occurred in the Nomcom pages.<br>
</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></div>

--001a1133c2d2ada7d304e9035677--

From adrian@olddog.co.uk  Fri Oct 18 06:06: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 7761711E81D2 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:06:46 -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.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 3iU7u-2TgszF for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:06:40 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 98E8511E8164 for <ietf@ietf.org>; Fri, 18 Oct 2013 06:06:27 -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 r9ID6JAe001592;  Fri, 18 Oct 2013 14:06:19 +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 r9ID6HYi001554 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 18 Oct 2013 14:06:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Peter Saint-Andre'" <stpeter@stpeter.im>, <dcrocker@bbiw.net>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
In-Reply-To: <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Date: Fri, 18 Oct 2013 14:06:16 +0100
Message-ID: <061e01cecc02$d5685af0$803910d0$@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: AQKeEwxHUYFX0tsT0+sgxGiVQhU94wF3doq2mFAiTMA=
Content-Language: en-gb
Cc: 'IETF Discuss' <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: Fri, 18 Oct 2013 13:06:46 -0000

John,

> At least for the one of those proposals
> I remember best, the IESG simply refused to consider it.

One of the benefits of the way the IESG turns over is that tomorrow's IESG is
not today's.

On the other hand, the IESG serves the community as well as providing a modicum
of leadership.

If the community is insistent on some point, the IESG had better wake up. In
other words, if you can build a rough consensus in the community for some change
whether technical or procedural, what the IESG thinks is not significant beyond
pointing out flaws and providing polish. 

I am not convinced by "the IESG refused to consider."  Change the IESG to one
that will consider, or better yet, bring fully formed consensus for change to
the IESG and have it happen.

Adrian (optimist today - medication must be working)


From narten@us.ibm.com  Fri Oct 18 06:15:23 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 7748021F9DB4 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:15:23 -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 tuoYN+eoOExv for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:15:16 -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 4544121F9DA8 for <ietf@ietf.org>; Fri, 18 Oct 2013 06:15:16 -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, 18 Oct 2013 09:15:14 -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, 18 Oct 2013 09:15:11 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id B3320C9005E for <ietf@ietf.org>; Fri, 18 Oct 2013 09:15:04 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp22035.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9IDF52750266212 for <ietf@ietf.org>; Fri, 18 Oct 2013 13:15:05 GMT
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r9IDF4ud023140 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:15:04 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r9IDF0C2022805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 18 Oct 2013 10:15:00 -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 r9IDExGr017761 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:14:59 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r9IDExMd017694 for ietf@ietf.org; Fri, 18 Oct 2013 09:14:59 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201310181314.r9IDExMd017694@rotala.raleigh.ibm.com>
Date: Fri, 18 Oct 2013 09:14:58 -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: 13101813-7182-0000-0000-000008CB43D3
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 13:15:23 -0000

Total of 192 messages in the last 7 days.
 
script run at: Fri Oct 18 09:14:58 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.85% |   17 | 11.71% |   178842 | fred.l.templin@boeing.com
  5.21% |   10 |  9.12% |   139279 | abdussalambaryun@gmail.com
  5.21% |   10 |  5.39% |    82249 | john-ietf@jck.com
  4.69% |    9 |  4.24% |    64728 | brian.e.carpenter@gmail.com
  4.17% |    8 |  3.71% |    56600 | fgont@si6networks.com
  3.65% |    7 |  3.78% |    57752 | jmamodio@gmail.com
  3.12% |    6 |  3.03% |    46354 | adrian@olddog.co.uk
  3.12% |    6 |  2.59% |    39556 | ted.lemon@nominum.com
  2.60% |    5 |  2.67% |    40759 | daedulus@btconnect.com
  2.08% |    4 |  2.88% |    44033 | v6ops@globis.net
  2.60% |    5 |  2.08% |    31698 | jari.arkko@piuha.net
  2.08% |    4 |  1.68% |    25699 | dhc@dcrocker.net
  2.08% |    4 |  1.68% |    25684 | barryleiba@computer.org
  2.08% |    4 |  1.64% |    25013 | sm@resistor.net
  2.08% |    4 |  1.55% |    23614 | stpeter@stpeter.im
  2.08% |    4 |  1.49% |    22723 | cabo@tzi.org
  1.56% |    3 |  1.83% |    27984 | rbonica@juniper.net
  1.56% |    3 |  1.51% |    23092 | lars@netapp.com
  1.56% |    3 |  1.20% |    18306 | stephen.farrell@cs.tcd.ie
  1.04% |    2 |  1.34% |    20443 | loa@pi.nu
  1.04% |    2 |  1.19% |    18218 | dave@cridland.net
  1.04% |    2 |  1.17% |    17830 | sm+ietf@elandsys.com
  1.04% |    2 |  1.08% |    16451 | alejandroacostaalamo@gmail.com
  1.04% |    2 |  1.05% |    16057 | joelja@bogus.com
  1.04% |    2 |  1.05% |    16006 | presnick@qti.qualcomm.com
  1.04% |    2 |  0.98% |    14982 | jcurran@istaff.org
  1.04% |    2 |  0.96% |    14690 | mcr+ietf@sandelman.ca
  1.04% |    2 |  0.95% |    14490 | arturo.servin@gmail.com
  1.04% |    2 |  0.93% |    14176 | ogud@ogud.com
  1.04% |    2 |  0.88% |    13513 | l.wood@surrey.ac.uk
  1.04% |    2 |  0.86% |    13179 | johnl@taugh.com
  1.04% |    2 |  0.86% |    13134 | mohta@necom830.hpcl.titech.ac.jp
  1.04% |    2 |  0.81% |    12387 | melinda.shore@gmail.com
  1.04% |    2 |  0.80% |    12197 | peter@akayla.com
  1.04% |    2 |  0.79% |    12029 | nomcom-chair-2013@ietf.org
  1.04% |    2 |  0.74% |    11239 | simon.perreault@viagenie.ca
  1.04% |    2 |  0.72% |    10977 | randy@psg.com
  1.04% |    2 |  0.69% |    10562 | jnc@mercury.lcs.mit.edu
  0.52% |    1 |  0.73% |    11135 | hartmans-ietf@mit.edu
  0.52% |    1 |  0.73% |    11077 | fernando@gont.com.ar
  0.52% |    1 |  0.71% |    10847 | john@jck.com
  0.52% |    1 |  0.68% |    10324 | ron.even.tlv@gmail.com
  0.52% |    1 |  0.62% |     9493 | hallam@gmail.com
  0.52% |    1 |  0.60% |     9183 | dirkx@webweaving.org
  0.52% |    1 |  0.57% |     8763 | otroan@employees.org
  0.52% |    1 |  0.54% |     8224 | chaitanyabd@gmail.com
  0.52% |    1 |  0.54% |     8218 | tbray@textuality.com
  0.52% |    1 |  0.53% |     8042 | kathleen.moriarty@emc.com
  0.52% |    1 |  0.53% |     8020 | paf@frobbit.se
  0.52% |    1 |  0.50% |     7595 | rdroms.ietf@gmail.com
  0.52% |    1 |  0.50% |     7571 | harald@alvestrand.no
  0.52% |    1 |  0.49% |     7533 | tina.tsou.zouting@huawei.com
  0.52% |    1 |  0.48% |     7379 | tjc@ecs.soton.ac.uk
  0.52% |    1 |  0.48% |     7363 | woolf@isc.org
  0.52% |    1 |  0.48% |     7274 | klensin@jck.com
  0.52% |    1 |  0.47% |     7164 | bclaise@cisco.com
  0.52% |    1 |  0.47% |     7140 | lberger@labn.net
  0.52% |    1 |  0.47% |     7123 | mstjohns@comcast.net
  0.52% |    1 |  0.46% |     7039 | ietfdbh@comcast.net
  0.52% |    1 |  0.46% |     6989 | housley@vigilsec.com
  0.52% |    1 |  0.46% |     6966 | shogunx@sleekfreak.ath.cx
  0.52% |    1 |  0.45% |     6864 | hgs@cs.columbia.edu
  0.52% |    1 |  0.44% |     6751 | warren@kumari.net
  0.52% |    1 |  0.44% |     6676 | huubatwork@gmail.com
  0.52% |    1 |  0.43% |     6535 | hsantos@isdg.net
  0.52% |    1 |  0.42% |     6372 | petithug@acm.org
  0.52% |    1 |  0.42% |     6344 | gem@rellim.com
  0.52% |    1 |  0.41% |     6249 | stbryant@cisco.com
  0.52% |    1 |  0.39% |     5940 | alexey.melnikov@isode.com
  0.52% |    1 |  0.39% |     5930 | steve@shinkuro.com
  0.52% |    1 |  0.39% |     5929 | chair@ietf.org
  0.52% |    1 |  0.39% |     5927 | sob@sobco.com
  0.52% |    1 |  0.38% |     5767 | ajs@anvilwalrusden.com
  0.52% |    1 |  0.35% |     5376 | cdel@firsthand.net
  0.52% |    1 |  0.32% |     4915 | cmasango@unog.ch
  0.52% |    1 |  0.31% |     4797 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |  192 |100.00% |  1527359 | Total


From andy@yumaworks.com  Fri Oct 18 06:45: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 A9A2611E8287 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level: 
X-Spam-Status: No, score=-2.812 tagged_above=-999 required=5 tests=[AWL=0.164,  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 ozB2lUh1jibL for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 06:45:01 -0700 (PDT)
Received: from mail-qe0-f50.google.com (mail-qe0-f50.google.com [209.85.128.50]) by ietfa.amsl.com (Postfix) with ESMTP id 53CE411E8278 for <ietf@ietf.org>; Fri, 18 Oct 2013 06:45:01 -0700 (PDT)
Received: by mail-qe0-f50.google.com with SMTP id 1so1773590qee.23 for <ietf@ietf.org>; Fri, 18 Oct 2013 06:45:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DMYWaEqtG7Wiki3HbRqLzvaa2nkj4k4urfJKrUwwPms=; b=VXbSRONLyyNQyKKnD9kXSiQuhGLusyXtQ7kJOmy3n8A6NLjTEFQfvR307WizQIMV3i IiQpGEVNGc6EM8v5REnvwIRv5HDMmwyrjTQNkJLTVCXGaNYGa+RfhWoQVH2jRZtkH8bR MctRanXFFtaM8iU9n+rBu/Wt7SLhyWcaZekbdzIPIWHDncS9922QTfgRM65TZ6ci1kxd BSeXJdGKh22yQutQwd73trBjNmCQ4nSa9TCjG2y1gkVZnuKBipjKi+RJXgjxsGINcx6k rejzHPsS+K1TWEAOQywwfSQCLZFlPOY+m1GSXhq3ctLZfoGus+XB9FV/Xv4Zb5TvzwNo wQew==
X-Gm-Message-State: ALoCoQm0azoNW2Gk7jA2PCGZuif/8hoSWzf25AthcqIdm/GCvJv+LdQHPfScAulj/Gd0RoXWYbyo
MIME-Version: 1.0
X-Received: by 10.224.131.133 with SMTP id x5mr3594984qas.70.1382103900701; Fri, 18 Oct 2013 06:45:00 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Fri, 18 Oct 2013 06:45:00 -0700 (PDT)
In-Reply-To: <061e01cecc02$d5685af0$803910d0$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk>
Date: Fri, 18 Oct 2013 06:45:00 -0700
Message-ID: <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Andy Bierman <andy@yumaworks.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a11c2d3860b5b6404e90424a4
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 13:45:06 -0000

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

Hi Adrian,

I have asked you and other ADs several times if Assistant ADs would help.
The answer I got was "not really, but a well run directorate really helps.".

I think the IESG does an excellent job of reviewing documents.
I would not want to increase throughput by simply reducing quality.
But I know ADs who have said they wish the job was only 40 hours/week,
because it can be more than that.

Staffing critical-path full-time positions with the best people
in the industry for free isn't as easy at it used to be.

Why not double the number of ADs in each area and instead of
every AD reviewing every draft, have 2 ADs from each area
review each draft? (Cut the AD hours in half somehow)


Andy

On Fri, Oct 18, 2013 at 6:06 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> John,
>
> > At least for the one of those proposals
> > I remember best, the IESG simply refused to consider it.
>
> One of the benefits of the way the IESG turns over is that tomorrow's IESG
> is
> not today's.
>
> On the other hand, the IESG serves the community as well as providing a
> modicum
> of leadership.
>
> If the community is insistent on some point, the IESG had better wake up.
> In
> other words, if you can build a rough consensus in the community for some
> change
> whether technical or procedural, what the IESG thinks is not significant
> beyond
> pointing out flaws and providing polish.
>
> I am not convinced by "the IESG refused to consider."  Change the IESG to
> one
> that will consider, or better yet, bring fully formed consensus for change
> to
> the IESG and have it happen.
>
> Adrian (optimist today - medication must be working)
>
>

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

<div dir=3D"ltr">Hi Adrian,<div><br></div><div>I have asked you and other A=
Ds several times if Assistant ADs would help.</div><div>The answer I got wa=
s &quot;not really, but a well run directorate really helps.&quot;.</div><d=
iv>
<br></div><div>I think the IESG does an excellent job of reviewing document=
s.</div><div>I would not want to increase throughput by simply reducing qua=
lity.</div><div><div class=3D"gmail_extra">But I know ADs who have said the=
y wish the job was only 40 hours/week,</div>
<div class=3D"gmail_extra">because it can be more than that.</div><div clas=
s=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Staffing critical-pa=
th full-time positions with the best people</div><div class=3D"gmail_extra"=
>in the industry for free isn&#39;t as easy at it used to be.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Why not dou=
ble the number of ADs in each area and instead of</div><div class=3D"gmail_=
extra">every AD reviewing every draft, have 2 ADs from each area</div><div =
class=3D"gmail_extra">
review each draft? (Cut the AD hours in half somehow)</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gma=
il_extra">Andy</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Fri, Oct 18, 2013 at 6:06 AM, Adrian Farrel <span dir=3D"ltr">&lt;<a =
href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">adrian@olddog.co.uk</=
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">John,<br>
<br>
&gt; At least for the one of those proposals<br>
&gt; I remember best, the IESG simply refused to consider it.<br>
<br>
One of the benefits of the way the IESG turns over is that tomorrow&#39;s I=
ESG is<br>
not today&#39;s.<br>
<br>
On the other hand, the IESG serves the community as well as providing a mod=
icum<br>
of leadership.<br>
<br>
If the community is insistent on some point, the IESG had better wake up. I=
n<br>
other words, if you can build a rough consensus in the community for some c=
hange<br>
whether technical or procedural, what the IESG thinks is not significant be=
yond<br>
pointing out flaws and providing polish.<br>
<br>
I am not convinced by &quot;the IESG refused to consider.&quot; =A0Change t=
he IESG to one<br>
that will consider, or better yet, bring fully formed consensus for change =
to<br>
the IESG and have it happen.<br>
<br>
Adrian (optimist today - medication must be working)<br>
<br>
</blockquote></div><br></div></div></div>

--001a11c2d3860b5b6404e90424a4--

From ajs@anvilwalrusden.com  Fri Oct 18 07:13:29 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 4D86F11E81D9 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:13:29 -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 UJo15txYCqzU for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:13:24 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id B272611E81CF for <ietf@ietf.org>; Fri, 18 Oct 2013 07:13:21 -0700 (PDT)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 969D58A031 for <ietf@ietf.org>; Fri, 18 Oct 2013 14:13:20 +0000 (UTC)
Date: Fri, 18 Oct 2013 10:13:22 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Message-ID: <20131018141322.GI4003@mx1.yitter.info>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <68E38B413DEA2B7C139A155A@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: Fri, 18 Oct 2013 14:13:29 -0000

No hat.

On Thu, Oct 17, 2013 at 06:52:11PM -0400, John C Klensin wrote:
> I wonder if we should be publishing, at regular intervals, RFCs
> with explicit acknowledgements and maybe contact information for
> Areas and ADs, WG Chairs, and, if appropriate, other IETF
> functionaries, probably including document reviewers and Nomcom
> members.

I'm not keen on adding this cruft to the RFC series.  I note that the
tools pages are now archived, so if you go to
http://tools.ietf.org/wg/dnsext you will find that it's concluded and
that Olafur and I were chair at the end.  What you _won't_ find is
the history of other chairs.  Maybe that's an issue?

On the other hand, isn't this what resumes are for?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From allison.mankin@gmail.com  Fri Oct 18 07:19:41 2013
Return-Path: <allison.mankin@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 AE6D411E81CF for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:19:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.087
X-Spam-Level: 
X-Spam-Status: No, score=-1.087 tagged_above=-999 required=5 tests=[AWL=-0.797, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKcAHWSTjw6X for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:19:41 -0700 (PDT)
Received: from mail-ea0-x232.google.com (mail-ea0-x232.google.com [IPv6:2a00:1450:4013:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id CB7C711E819D for <ietf@ietf.org>; Fri, 18 Oct 2013 07:19:39 -0700 (PDT)
Received: by mail-ea0-f178.google.com with SMTP id a15so2009217eae.37 for <ietf@ietf.org>; Fri, 18 Oct 2013 07:19:38 -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=QiQMs742PrmXgJ62NfNHK1Tl3OegAzQCWECGUiLtcnY=; b=GS1QLjTE5wrA1FV9535lLHFhO7g3hSpDSCVG09Q6yNc1lgtTWwsY8hbPU0U+LPnJcX WqxFlHHvTyMn3FOxZlK16Zn1wr6vgqr01sRMqSPurTjt5qa9Q5jZZuD19K4RpP7ysav5 M8vJ5zNazMqeIguzdM6IbCwPTZjRYWlfTOeWZi6piUU0T2CDSE3cQGSynjztGNEAhgNe yCCBwunH+81ngUo7eTr6cfApm8TULUODd4eUKcUSx1L5t61ug9GYvZobtMhyrUfdaZO2 LXVboucl1WInqRTIMR9Dxi066n2FhMgnY5gl89VQqgPPeZQOkE/wO2HydsBZAjU6JZfX N1Pw==
MIME-Version: 1.0
X-Received: by 10.204.103.199 with SMTP id l7mr575228bko.11.1382105978569; Fri, 18 Oct 2013 07:19:38 -0700 (PDT)
Received: by 10.205.14.68 with HTTP; Fri, 18 Oct 2013 07:19:38 -0700 (PDT)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com>
Date: Fri, 18 Oct 2013 10:19:38 -0400
Message-ID: <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
From: Allison Mankin <allison.mankin@gmail.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "ietf@ietf.org" <ietf@ietf.org>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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, 18 Oct 2013 14:19:41 -0000

Kathleen,

Thanks for the perfect explanation of why it's reasonable to run
against the incumbent, even if you want that person to be selected
again.

Allison (for the Nomcom)

On Fri, Oct 18, 2013 at 8:40 AM, Moriarty, Kathleen
<kathleen.moriarty@emc.com> wrote:
> It is important for multiple people to run even when there is an incumben=
t for a fair process.  When Stephen Farrell ran for Sec AD again last year,=
 he encouraged me to accept the nomination and run against him so that ther=
e was a good candidate to make the process a bit more fair.  If either Step=
hen of Sean won the lottery, the Noncom would at least have gone through th=
e interview and review process with other candidates in advance.  The candi=
date would have worked through the possibility of what this meant with thei=
r job and that it was possible for them to take on this role (not insignifi=
cant for many of us).  For me, I thought Stephen was doing a fine job and a=
m glad he was put back on the IESG, but it is good for the Noncom to have o=
ptions and backup plans.  I received approval from my company, but let my m=
anagement know that it was unlikely that I would be selected since incumben=
ts usually return.
>
> Maybe folks should consider running against an incumbent.  You learn the =
process and it forces you to figure out if you are interested in the role a=
nd could allocate that time to the IETF.  I gave a positive review of Steph=
en when running against him.
>
> Thanks,
> Kathleen
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of E=
rsue, Mehmet (NSN - DE/Munich)
> Sent: Friday, October 18, 2013 6:36 AM
> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
>
> Hi Allison,
>
> in your model you don't count those people who have been rejecting to a n=
omination, just because they believe the current AD did a very good job and=
 he/she should be reelected.
>
> So the situation is not that bad, if there is only the current AD on the =
nominee list.
>
> Cheers,
> Mehmet
>
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org
>> [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair
>> 2013
>> Sent: Thursday, October 17, 2013 4:25 PM
>> To: IETF Announcement List
>> Cc: IETF Discuss
>> Subject: NOMCOM - Critical shortage of nominees for multiple areas
>>
>> [Catchier Subject line - apologies to those offended by a duplicate]
>>
>> A critically low number of people have accepted nominations for some
>> of the IESG open positions.  There is only one nominee per slot in
>> APP, OPS and TSV, only two in INT and RAI.  Many folks have declined nom=
inations.
>>
>> While the Nomcom appreciates that support for two years of intense
>> service is hard to assure, and while we are aware that there is much
>> support for the incumbents who are standing, the IETF should
>> continually be considering which new talent is available for our
>> leadership, and the Nomcom process needs for there to be some review and=
 deliberation.
>>
>> Therefore, we urgently request that more nominees come forward.
>>
>> DEADLINES
>> Nominations - October 18
>> Questionnaires from nominees - October 25
>>
>> Not coincidentally, this is a good time to think over and send your
>> comments about the current statements of desired expertise of
>> positions - this is part of the Nomcom's annual review process as well. =
 Send them to nomcom13@ietf.org.
>>
>> Definitive location [*] of the current statements on desired expertise:
>>       https://datatracker.ietf.org/nomcom/2013/expertise/
>>
>> Instructions and details on nomination [**]:
>>       https://datatracker.ietf.org/ann/nomcom/60602/
>>
>> Thanks, everyone,
>>
>> Allison for the Nomcom
>>
>> [*] This year the Nomcom tools were recoded, and also transitioned
>> into the datatracker.  Apologies for a number of places where we
>> didn't catch reference errors.
>>
>> [**] Yes, alas, the previous call for nominations used "OAM" instead
>> of "OPS," but we have* corrected this (chair's pilot) error where it
>> occurred in the Nomcom pages.

From allison.mankin@gmail.com  Fri Oct 18 07:24:13 2013
Return-Path: <allison.mankin@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 9E6F411E82B4 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.987
X-Spam-Level: 
X-Spam-Status: No, score=-0.987 tagged_above=-999 required=5 tests=[AWL=-0.697, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGEVgNFv7+SU for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:24:12 -0700 (PDT)
Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABFD11E82B3 for <ietf@ietf.org>; Fri, 18 Oct 2013 07:24:10 -0700 (PDT)
Received: by mail-ee0-f45.google.com with SMTP id c50so2081064eek.32 for <ietf@ietf.org>; Fri, 18 Oct 2013 07:24:09 -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=hZOIOz4b6Ddp1YeKpBT9OHQY3VwbyEZx4CGFpYCeeks=; b=ZUHQgvhqf5zCuRf4bFJj8aQJGF/cbitbH9D76PP0s/8Eh5vZJz57sp8Jka83a84edk TqqFRy3AHZgjW4JhQBAThTwUhpLPRT96F01XVdWXsOC+CcK4l9YAYxmGNOOYG1B8NrXZ CnPn2wb1gbsfAGiN5CGZ/nFCZglxaQsD9EM12y9cQXUwt2yPtGeSFRVadpKUjEhi70hE A3bKwVJbrrs0LoOvebI5ltqzieyTyHeFre2CFUY+vstKvp2pS0XIB+CMt8p1EbqL9aNZ VJGVzCrI4ItmGFnZlfWcjZsluSSUqVduRE7Saio1AEImnBl6ow72MMxPoBBqvkUYPHa9 26Fw==
MIME-Version: 1.0
X-Received: by 10.204.69.12 with SMTP id x12mr582050bki.12.1382106249209; Fri, 18 Oct 2013 07:24:09 -0700 (PDT)
Received: by 10.205.14.68 with HTTP; Fri, 18 Oct 2013 07:24:09 -0700 (PDT)
In-Reply-To: <CAMm+Lwgd_G8ZajwnCqT=OESS3J9vb4h0MdpwYLUPTYKNEmOHGw@mail.gmail.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com> <CAMm+Lwgd_G8ZajwnCqT=OESS3J9vb4h0MdpwYLUPTYKNEmOHGw@mail.gmail.com>
Date: Fri, 18 Oct 2013 10:24:09 -0400
Message-ID: <CAP8yD=tAXKEaYsaUTFmxAk_pO-pzRKVYRh96nm490SfW+cuFGQ@mail.gmail.com>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
From: Allison Mankin <allison.mankin@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "ietf@ietf.org" <ietf@ietf.org>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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, 18 Oct 2013 14:24:13 -0000

Phillip,

Thank you very much as well - this is a great reminder of why there
need to be some people for backup or pipelined.

Allison (for the Nomcom)

On Fri, Oct 18, 2013 at 8:47 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> Or look back to a previous Security AD appointment when the incumbent became
> unavailable because he was appointed IETF Chair.
>
>
> On Fri, Oct 18, 2013 at 8:40 AM, Moriarty, Kathleen
> <kathleen.moriarty@emc.com> wrote:
>>
>> It is important for multiple people to run even when there is an incumbent
>> for a fair process.  When Stephen Farrell ran for Sec AD again last year, he
>> encouraged me to accept the nomination and run against him so that there was
>> a good candidate to make the process a bit more fair.  If either Stephen of
>> Sean won the lottery, the Noncom would at least have gone through the
>> interview and review process with other candidates in advance.  The
>> candidate would have worked through the possibility of what this meant with
>> their job and that it was possible for them to take on this role (not
>> insignificant for many of us).  For me, I thought Stephen was doing a fine
>> job and am glad he was put back on the IESG, but it is good for the Noncom
>> to have options and backup plans.  I received approval from my company, but
>> let my management know that it was unlikely that I would be selected since
>> incumbents usually return.
>>
>> Maybe folks should consider running against an incumbent.  You learn the
>> process and it forces you to figure out if you are interested in the role
>> and could allocate that time to the IETF.  I gave a positive review of
>> Stephen when running against him.
>>
>> Thanks,
>> Kathleen
>>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Ersue, Mehmet (NSN - DE/Munich)
>> Sent: Friday, October 18, 2013 6:36 AM
>> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
>> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
>>
>> Hi Allison,
>>
>> in your model you don't count those people who have been rejecting to a
>> nomination, just because they believe the current AD did a very good job and
>> he/she should be reelected.
>>
>> So the situation is not that bad, if there is only the current AD on the
>> nominee list.
>>
>> Cheers,
>> Mehmet
>>
>> > -----Original Message-----
>> > From: ietf-announce-bounces@ietf.org
>> > [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair
>> > 2013
>> > Sent: Thursday, October 17, 2013 4:25 PM
>> > To: IETF Announcement List
>> > Cc: IETF Discuss
>> > Subject: NOMCOM - Critical shortage of nominees for multiple areas
>> >
>> > [Catchier Subject line - apologies to those offended by a duplicate]
>> >
>> > A critically low number of people have accepted nominations for some
>> > of the IESG open positions.  There is only one nominee per slot in
>> > APP, OPS and TSV, only two in INT and RAI.  Many folks have declined
>> > nominations.
>> >
>> > While the Nomcom appreciates that support for two years of intense
>> > service is hard to assure, and while we are aware that there is much
>> > support for the incumbents who are standing, the IETF should
>> > continually be considering which new talent is available for our
>> > leadership, and the Nomcom process needs for there to be some review and
>> > deliberation.
>> >
>> > Therefore, we urgently request that more nominees come forward.
>> >
>> > DEADLINES
>> > Nominations - October 18
>> > Questionnaires from nominees - October 25
>> >
>> > Not coincidentally, this is a good time to think over and send your
>> > comments about the current statements of desired expertise of
>> > positions - this is part of the Nomcom's annual review process as well.
>> > Send them to nomcom13@ietf.org.
>> >
>> > Definitive location [*] of the current statements on desired expertise:
>> >       https://datatracker.ietf.org/nomcom/2013/expertise/
>> >
>> > Instructions and details on nomination [**]:
>> >       https://datatracker.ietf.org/ann/nomcom/60602/
>> >
>> > Thanks, everyone,
>> >
>> > Allison for the Nomcom
>> >
>> > [*] This year the Nomcom tools were recoded, and also transitioned
>> > into the datatracker.  Apologies for a number of places where we
>> > didn't catch reference errors.
>> >
>> > [**] Yes, alas, the previous call for nominations used "OAM" instead
>> > of "OPS," but we have* corrected this (chair's pilot) error where it
>> > occurred in the Nomcom pages.
>
>
>
>
> --
> Website: http://hallambaker.com/

From daedulus@btconnect.com  Fri Oct 18 07:26: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 9BA2E11E8232 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.07
X-Spam-Level: 
X-Spam-Status: No, score=-5.07 tagged_above=-999 required=5 tests=[AWL=1.529,  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 dx6irpBQk-OJ for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:25:54 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 516B811E81CD for <ietf@ietf.org>; Fri, 18 Oct 2013 07:25:54 -0700 (PDT)
Received: from mail128-tx2-R.bigfish.com (10.9.14.227) by TX2EHSOBE013.bigfish.com (10.9.40.33) with Microsoft SMTP Server id 14.1.225.22; Fri, 18 Oct 2013 14:25:53 +0000
Received: from mail128-tx2 (localhost [127.0.0.1])	by mail128-tx2-R.bigfish.com (Postfix) with ESMTP id B05F2200C2; Fri, 18 Oct 2013 14:25:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(z551biz9371I542I1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275dh1de097h8275bhz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail128-tx2 (localhost.localdomain [127.0.0.1]) by mail128-tx2 (MessageSwitch) id 1382106352194211_14919; Fri, 18 Oct 2013 14:25:52 +0000 (UTC)
Received: from TX2EHSMHS011.bigfish.com (unknown [10.9.14.250])	by mail128-tx2.bigfish.com (Postfix) with ESMTP id 1C7F5360041; Fri, 18 Oct 2013 14:25:52 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by TX2EHSMHS011.bigfish.com (10.9.99.111) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 18 Oct 2013 14:25:51 +0000
Received: from DB3PRD0210HT001.eurprd02.prod.outlook.com (157.56.253.69) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 18 Oct 2013 14:25:38 +0000
Message-ID: <01e601cecc0d$a510b5e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Adrian Farrel <adrian@olddog.co.uk>, 'Peter Saint-Andre' <stpeter@stpeter.im>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call forNominations)
Date: Fri, 18 Oct 2013 15:23:03 +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.69]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: 'IETF Discuss' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 14:26:00 -0000

----- Original Message -----
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Peter Saint-Andre'" <stpeter@stpeter.im>; <dcrocker@bbiw.net>
Cc: "'John C Klensin'" <john-ietf@jck.com>; "'IETF Discuss'"
<ietf@ietf.org>
Sent: Thursday, October 17, 2013 8:36 PM

> > > The IESG defines the job and the IESG 'operates' the model.  So
yes,
> > > formally the IESG controls this issue.
>
> Mutter.
> I suppose the seated IESG defines what it does.
> Or more precisely, each member of the IESG decides what (sadly) he
should do to
> best serve in the role.
>
> But don't see the "job requirements" put out by NomCom as the IESG
placing
> requirements.
> The NomCom asks the IESG what skills and tasks are needed in the view
of the
> current IESG.
> The IESG serves up this information and NomCom can do with it as it
likes.
>
> More important, the community can and should tell the NomCom what it
wants the
> IESG to do and not do.
>
> > > However...
> > >
> > > Nomcom can apply pretty much whatever criteria it wants to the
selection
> > > process and Nomcom has been know to have some private negotiations
with
> > > the IESG.  Nothing as profound as the change we are suggesting,
but
> > > still...
>
> Exactly.
>
> > > It would be better for the IESG to take the initiative here and
formally
> > > and publicly re-define the job, but it has so far ignored such
requests.
>
> Which cuts into what Peter says since from where I sit there are many
calls on
> the time of an AD and it would be useful to know which tasks the
community would
> like me to not do (I think that I and my chief sponsor would both be
happy if I
> spent more time working for them and less working as an AD).
>
> > It might be helpful to talk about what could change, such as:
> >
> > 1. Less/no time on document reviews.
>
> Right. Ask:
> Do the reviews currently done by ADs make a difference to the quality
of
> individual documents or the overall canon?

Adrian

Depends on the AD!  I do not know if you are aware of it but yours do; I
think that what you have done on the MPLS list has improved the quality
almost beyond measure but of the lists I track, you do stand out as a
shining beacon (so much so that I do worry sometimes that you will be
unable to keep it up).  On other lists, the AD review is less, sometimes
much less; perhaps they looked and found the I-D already to
be of good quality but then IETF Last Call comes along and the I-D
is found wanting.

I think that as a general engineering rule, the earlier things are got
right, the lower the overall cost, however the last is measured, so
could the comments you make have been made earlier, e.g. prior to WGLC,
by someone else, then I think that the IETF would be in a stronger place
(but how to do that I do not know).

Tom Petch

><snip>



From allison.mankin@gmail.com  Fri Oct 18 07:43:39 2013
Return-Path: <allison.mankin@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 E236621F9D0D for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level: 
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=0.593,  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 Hwdblbl49EdK for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 07:43:39 -0700 (PDT)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5402521F9C9A for <ietf@ietf.org>; Fri, 18 Oct 2013 07:43:33 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e52so2076755eek.16 for <ietf@ietf.org>; Fri, 18 Oct 2013 07:43:32 -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=BsDNUQcKBgcdH72/niXchicN4FGIJv3+9P4dZiVTrmg=; b=Zl50VduYgcvgVo7v72yr0C3tClXXt6bsqzJnGh0aVETCu1zua4HPwyXw03AKm5AaFr VjMcEVHPyhNUp+OZTICTEM74wAXk//5LNxRgVpxLG4bTy37EJifkAG9jUwWBCLMioP4w kHH5ZwiVvKk276YZJUb6HhDNAdp6wFAoOh3YnrBvJ2qM4KBs3xJ6mI+2Es5KasHOzcZ4 WgWBjnd2nLR/F1u9JHZWtdEOarHevT/R0OJbl1j6xzul46GB3esS1ZkGY9wPrZrBjXNQ jsiMcYrakX8fkMnpZLE7Bs/HkrpoSoa+oN2ADDTarmNrDq8m9CguJXdZxw285P1ZPQC8 EX1w==
MIME-Version: 1.0
X-Received: by 10.205.22.71 with SMTP id qv7mr600681bkb.20.1382107412420; Fri, 18 Oct 2013 07:43:32 -0700 (PDT)
Received: by 10.205.14.68 with HTTP; Fri, 18 Oct 2013 07:43:32 -0700 (PDT)
In-Reply-To: <20131018141322.GI4003@mx1.yitter.info>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info>
Date: Fri, 18 Oct 2013 10:43:32 -0400
Message-ID: <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Allison Mankin <allison.mankin@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
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: Fri, 18 Oct 2013 14:43:40 -0000

Adding to Andrew's suggestion on this thread, there does now exist a
photo gallery of current WG chairs:

http://www.ietf.org/wg/chair-photos.html

I'd consider it useful and a nice thing if there were a corresponding
photo gallery of past chairs (maybe or maybe not to the beginning of
the IETF), and also if the information on the current WG chairs had a
bullet for previous chairships.  I put in a suggestion about this in
relation to Nomcom support this past week.

Yes, resumes are good too, but there's something to be said for our
institution keeping an easy way to see where we've been, who's been
working.

Nomcom hat on, though mine is far less cool than Matt Lepinski's from Orlando...

Allison

On Fri, Oct 18, 2013 at 10:13 AM, Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:
> No hat.
>
> On Thu, Oct 17, 2013 at 06:52:11PM -0400, John C Klensin wrote:
>> I wonder if we should be publishing, at regular intervals, RFCs
>> with explicit acknowledgements and maybe contact information for
>> Areas and ADs, WG Chairs, and, if appropriate, other IETF
>> functionaries, probably including document reviewers and Nomcom
>> members.
>
> I'm not keen on adding this cruft to the RFC series.  I note that the
> tools pages are now archived, so if you go to
> http://tools.ietf.org/wg/dnsext you will find that it's concluded and
> that Olafur and I were chair at the end.  What you _won't_ find is
> the history of other chairs.  Maybe that's an issue?
>
> On the other hand, isn't this what resumes are for?
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com

From john@jlc.net  Fri Oct 18 08:05:32 2013
Return-Path: <john@jlc.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 5D62D11E82F2 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level: 
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=0.178, 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 50SPeMnvkTzv for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:05:22 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 799D511E82F1 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:05:19 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 041ACC94C3; Fri, 18 Oct 2013 11:05:17 -0400 (EDT)
Date: Fri, 18 Oct 2013 11:05:17 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Message-ID: <20131018150516.GA67188@verdi>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52602DF7.3030207@dcrocker.net>
User-Agent: Mutt/1.4.1i
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:05:32 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> 
> We have been having some very serious recruitment problems for a number 
> of years now.  This year's crisis was entirely predictable.
> 
> The only way the situation will change meaningfully is to make the job 
> less onerous...

<hat="Senior Narrative Scribe">

   Having followed a strong majority of formal telechats for five years,
it is blindingly obvious to me that

- there are too many documents to review, and
- there are too many Working Groups to manage;

and it keeps getting worse. :^(

   The fact that the IESG gets through the agendas for these telechats
fools some folks into believing the job is possible -- but the rest of
us aren't fooled.

> Re-define the bloody job...

   Here I part ways with Dave. (It never seems to take long... :^)

   There is nothing wrong with reviewing documents. There is nothing
wrong with managing Working Groups. There are just too many of both!

   I can't very well name a WG that shouldn't be on the list for an
AD to manage (I'll cover that issue in a separate email); but we have
a perfect example right now of a document that the IESG shouldn't be
responsible to review.

   Pete Resnick's draft-resnick-on-consensus is an individual submission
seeking Informational status. From its Abstract:
] 
] This document is a collection of thoughts on what rough consensus is,
] how we have gotten away from it, and the things we can do in order to
] really achieve rough consensus.

   Yet, if it is published as an Informational RFC, it will have
boilerplate saying:
] 
] This document is a product of the Internet Engineering Task Force
] (IETF).  It represents the consensus of the IETF community.  It has
] received public review and has been approved for publication by the
] Internet Engineering Steering Group (IESG).  Not all documents
] approved by the IESG are a candidate for any level of Internet
] Standard; see Section 2 of RFC 5741.

   Thus some folks have quite understandably objected to it being
published, even as Informational.

   IESG review of it is really redundant (and I'd be surprised if any
AD puts a DISCUSS on it once Pete is satisfied with it). Pete will do
any appropriate consensus-seeking before he signs off an it.

   But there's that boilerplate!

   There's just no way a document like this can get genuine "consensus
of the IETF community". Yet it most truly deserves an IETF-wide Last
Call.

   IMHO there are _many_ documents being published as Informational
which deserve an IETF-wide Last Call, but don't deserve to go before
an IESG telechat and ask ADs to sign off on "consensus of the IETF
community".

   Documents such as this should represent the _author's_ opinions
after a Last Call process -- claiming "IETF community" consensus
detracts from that, and even _formal_ IESG review without that
boilerplate would detract from it.

</hat>

   Can we get there from here? I don't know. :^(

   Removing the IESG review would be a process change; and we've had
very poor luck with those recently...

   But even changing the boilerplate would help...

--
John Leslie <john@jlc.net>

From Ted.Lemon@nominum.com  Fri Oct 18 08:10:27 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 CD6AD11E82C6 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 7kbjtRfa9deL for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:10:21 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 294B211E8232 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:10:20 -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 DSNKUmFPWkHxBfI7ortyQ8zsQRfD+5YoYV95@postini.com; Fri, 18 Oct 2013 08:10:20 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 C33A51B82C3 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:10:18 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 A358519005C for <ietf@ietf.org>; Fri, 18 Oct 2013 08:10:18 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 08:10:18 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>
Date: Fri, 18 Oct 2013 11:10:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:10:28 -0000

The most useful comment I've heard on this thread is that it makes sense =
to credit the working group chairs as well as the authors of a document =
in the document at the same level of emphasis.   And possibly the ADs as =
well.   I don't know if this would make a difference, but it's =
interesting, and might be worth the experiment.

But really, the main thing to say about this conversation is that it's a =
classic example of why the AD's job is so time consuming.   We have to =
monitor these conversations, because otherwise we aren't doing the part =
of our job that involves listening to the IETF.   Having long bikeshed =
discussions about the woeful brokenness of the AD's job over and over =
again without any action proposed is expensive.

Most of what's been discussed here has been discussed by the ADs during =
the recent IESG retreat, and substantial action was taken as a result of =
the discussion at that retreat.   It might be interesting to see if any =
of what we discussed actually changes anything.


From spencerdawkins.ietf@gmail.com  Fri Oct 18 08:11:09 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 DB8E721F9C3A for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:11:09 -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 jbGLf-gUmI6r for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:11:08 -0700 (PDT)
Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 27C9421F9C40 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:10:55 -0700 (PDT)
Received: by mail-ee0-f53.google.com with SMTP id t10so2137493eei.12 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:10: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 :cc:content-type; bh=qUQq+ddrhhw38aYBzlT56eIR4hQM3jLaprHftzc94zU=; b=i71+amxp3C1mQz/PshqUJy15yf6jc7yhcIaKsBn5VObzSfn6fLPYzojtQtNC/c7Z1L OYd+17ZpF/q1VPW77KttT+/ghhyv7yTOWbr2WuxhpdbupHhRteLI6/xF5uVRoCTOi0dn kGSIuW5Xn/aB6FQ0+GcTbF0unmXThPd7+flrMDew1NrFTL7Tz50SnHiM8jONNY1Z7Tbi 2AU7rCHKgkU9iq/X6lFxMj5DY4bveigYtfi+lSPCLjajF2+AgUNGGitBUE2JRRX1luHq UIiqrV3MA95Iudtdb6iaJPFD2kyqnTrUjlrrL6Ci1xgUDeIGRQ5x3M8FXs/GBcIfKI7d RsFQ==
MIME-Version: 1.0
X-Received: by 10.14.2.200 with SMTP id 48mr3598653eef.88.1382109054996; Fri, 18 Oct 2013 08:10:54 -0700 (PDT)
Received: by 10.223.196.9 with HTTP; Fri, 18 Oct 2013 08:10:54 -0700 (PDT)
In-Reply-To: <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
Date: Fri, 18 Oct 2013 10:10:54 -0500
Message-ID: <CAKKJt-ftRqQeg3iGq9kZc+G08VdCembhLYzFs+hUXEy+po=4xQ@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Content-Type: multipart/alternative; boundary=047d7b67030f4399b404e9055733
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:11:10 -0000

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

Andy, thank you for posting something I think I know how to reply to :-)

On Friday, October 18, 2013, Andy Bierman wrote:

> Hi Adrian,
>
> I have asked you and other ADs several times if Assistant ADs would help.
> The answer I got was "not really, but a well run directorate really
> helps.".
>
> I think the IESG does an excellent job of reviewing documents.
> I would not want to increase throughput by simply reducing quality.
> But I know ADs who have said they wish the job was only 40 hours/week,
> because it can be more than that.
>
> Staffing critical-path full-time positions with the best people
> in the industry for free isn't as easy at it used to be.
>
> Why not double the number of ADs in each area and instead of
> every AD reviewing every draft, have 2 ADs from each area
> review each draft? (Cut the AD hours in half somehow)
>
>
> Andy
>

Speaking as a TSV AD, and we all know what that means :-)

What I said pretty openly in the Orlando TSVAREA discussions about ways to
make the AD responsibilities more manageable, and what I told last year's
Nomcom privately, was that I really want to try SOMETHING, rather than just
keep doing what we've always done.

Let me be clear that I've talked about this with Martin, and with other
ADs, but I'm only speaking for mysel, and I'm not proposing that this
year's Nomcom do anything differently - I'm thinking about next year, when
we'll also be reviewing the leadership positions.

The suggestion to add ADs is one that's plausible to me (unless one really
believes that no matter how many WGs are in an area, and no matter how many
docs they produce, "2" is always the perfect number, except for GEN).

The devil is in the details, of course. Let's start with whether you could
do that when the Nomcom process to add an AD because of a workload spike
takes the better part of nine months, but there =E1re other devilish detail=
s
that even I can think of.

What I would ask, is that people who care about this start by cataloging
proposals that have been made previously, so we don't start from ground
zero. I'm remembering, off the top of my head, a proposal to two-level the
IESG (add ADs until the task is manageable in each area, but only one AD
sits in the telechats), and a proposal to separate the charter and
management responsibilities from the document approval responsibilities
(so, something like a formal cross-area review steering group that Nomcom
would likely be in charge of staffing). I'm sure there were others.

I'm seeing many folks expressing interest in this who I didn't notice
during previous discussions, and think level-setting would be helpful.

To be clear, I'm very conscious that I'm still learning my job, and I don't
think I'm competent to evaluate what WOULD be helpful yet. But I'm also
optimistic(*) that SOMEthing would be helpful.

My plane is boarding, but best wishes as you think about suggestions.

Spencer

(*) happily, my medication is working as well as Adrian's. Perhaps we
should add "being appropriately medicated" to the position descriptions we
send to Nomcom :-)

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

Andy, thank you for posting something I think I know how to reply to :-)<br=
><br>On Friday, October 18, 2013, Andy Bierman  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr">Hi Adrian,<div><br></div><div>I have asked you and other A=
Ds several times if Assistant ADs would help.</div><div>The answer I got wa=
s &quot;not really, but a well run directorate really helps.&quot;.</div>
<div>
<br></div><div>I think the IESG does an excellent job of reviewing document=
s.</div><div>I would not want to increase throughput by simply reducing qua=
lity.</div><div><div class=3D"gmail_extra">But I know ADs who have said the=
y wish the job was only 40 hours/week,</div>

<div class=3D"gmail_extra">because it can be more than that.</div><div clas=
s=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Staffing critical-pa=
th full-time positions with the best people</div><div class=3D"gmail_extra"=
>in the industry for free isn&#39;t as easy at it used to be.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Why not dou=
ble the number of ADs in each area and instead of</div><div class=3D"gmail_=
extra">every AD reviewing every draft, have 2 ADs from each area</div><div =
class=3D"gmail_extra">

review each draft? (Cut the AD hours in half somehow)</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gma=
il_extra">Andy</div></div></div></blockquote><div><br></div><div>Speaking a=
s a TSV AD, and we all know what that means :-)</div>
<div><br></div><div>What I said pretty openly in the Orlando TSVAREA discus=
sions about ways to make the AD responsibilities more manageable, and what =
I told last year&#39;s Nomcom privately, was that I really want to try SOME=
THING, rather than just keep doing what we&#39;ve always done.=A0</div>
<div><br></div><div>Let me be clear that I&#39;ve talked about this with Ma=
rtin, and with other ADs, but I&#39;m only speaking for mysel, and I&#39;m =
not proposing that this year&#39;s Nomcom do anything differently - I&#39;m=
 thinking about next year, when we&#39;ll also be reviewing the leadership =
positions.</div>
<div><br></div><div>The suggestion to add ADs is one that&#39;s plausible t=
o me=A0(unless one really believes=A0that no matter how many WGs are in an =
area, and no matter how many docs they produce, &quot;2&quot; is always the=
 perfect number, except for GEN).=A0</div>
<div><br></div><div>The devil is in the details, of course. Let&#39;s start=
 with whether you could do that when the Nomcom process to add an AD becaus=
e of a workload spike takes the better part of nine months, but there =E1re=
 other devilish details that even I can=A0think of.</div>
<div><br></div><div>What I would ask, is that people who care about this st=
art by cataloging proposals that have been made previously, so we don&#39;t=
 start from ground zero. I&#39;m remembering, off the top of my head, a pro=
posal to two-level the IESG (add ADs until the task is manageable in each a=
rea, but only one AD sits in the telechats), and a proposal to separate the=
 charter and management responsibilities from the document approval respons=
ibilities (so, something like a formal cross-area review steering group tha=
t Nomcom would likely be in charge of staffing). I&#39;m sure there were ot=
hers.=A0</div>
<div><br></div><div>I&#39;m seeing many folks expressing interest in this w=
ho I didn&#39;t notice during previous discussions, and think level-setting=
 would be helpful.</div><div><br></div><div>To be clear, I&#39;m very consc=
ious that I&#39;m still learning my job, and I don&#39;t think I&#39;m comp=
etent to evaluate what WOULD be helpful yet. But I&#39;m also optimistic(*)=
 that SOMEthing would be helpful.</div>
<div><br></div><div>My plane is boarding, but best wishes as you think abou=
t suggestions.</div><div><br></div><div>Spencer</div><div><br></div>(*) hap=
pily, my medication is working as well as Adrian&#39;s. Perhaps we should a=
dd &quot;being appropriately medicated&quot;=A0to the position descriptions=
 we send to Nomcom :-)

--047d7b67030f4399b404e9055733--

From mcr@sandelman.ca  Fri Oct 18 08:15:18 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 CC49E11E81B5 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:15:17 -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 2I-Cs3tShzfg for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:15:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 9F50411E8232 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:15:08 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 925992026F; Fri, 18 Oct 2013 12:25:42 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id AC64263B88; Fri, 18 Oct 2013 11:14:58 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9842963AEF; Fri, 18 Oct 2013 11:14:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
In-Reply-To: <52603C96.2030409@gmail.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <52603C96.2030409@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: Fri, 18 Oct 2013 11:14:58 -0400
Message-ID: <19497.1382109298@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:15:18 -0000

--=-=-=


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > 1A. All WGs do a near-perfect job on their drafts, including complete
    > management of cross-area reviews.

    > 2A. All WG Chairs to do a near-perfect job.

...

    > 2C. Summary closure of failing WGs.

    >> 3. Fewer working groups to manage.

    > 3A. IESG refuses the majority of proposed WGs.

..
    >> 6. Less/no involvement with creating the schedule.

    > [I'm not sure that will work. ADs are uniquely placed to identify
    > clashes and overlaps.]

Well, if one applies the above suggestions, then the schedule becomes much
easier to deal with.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUmFQb4qHRg3pndX9AQJ7WQP/TOfe+7AUNP1Ed4hTeziddD/jH0XRp+ep
zWEh2eyBQVQsDTvQCiWFNWXjaBcRoDI7oF4BpICd88WzOvB01aTGN5lOFu8RwyHb
mVxmAZDH+1Y41/jFrYqsB8Uq6iv2LVy0hjcu7KYmjI+zTUCZO+m8zT00t4o5w8DF
npAjZ0l9O4Y=
=nQqL
-----END PGP SIGNATURE-----
--=-=-=--

From adrian@olddog.co.uk  Fri Oct 18 08:33:36 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 625F81F0ED0 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:33:36 -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.037,  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 NXEH8f++gkDD for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:33:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9E11F0CF8 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:33:29 -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 r9IFXN7k005298;  Fri, 18 Oct 2013 16:33:23 +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 r9IFXKr0005262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 18 Oct 2013 16:33:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Andy Bierman'" <andy@yumaworks.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
In-Reply-To: <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
Subject: RE: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Date: Fri, 18 Oct 2013 16:33:18 +0100
Message-ID: <067601cecc17$60613320$21239960$@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: AQKeEwxHUYFX0tsT0+sgxGiVQhU94wF3doq2A3VtCXgB/VJM8JgkralA
Content-Language: en-gb
Cc: 'John C Klensin' <john-ietf@jck.com>, 'Dave Crocker' <dcrocker@bbiw.net>, 'IETF Discuss' <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: Fri, 18 Oct 2013 15:33:36 -0000

> I have asked you and other ADs several times if Assistant ADs would help.
> The answer I got was "not really, but a well run directorate really helps.".

OK. Doesn't sound like refusing to consider. Sounds like answering your
question.

So let's take it to the next step because it may be that the current IESG cannot
conceive of how an assistant AD would work.

Can you put up a strawman of the job tasks of an assistant AD that we can work
with to discuss whether this has legs? 
Would assistant ADs be appointed and work for sitting ADs, or would they be
NomCom appointments?
Can't an AD already delegate anything they want (except the responsibility)?

> Why not double the number of ADs in each area and instead of
> every AD reviewing every draft, have 2 ADs from each area
> review each draft? (Cut the AD hours in half somehow)

There is mileage in that. I don't think every AD reviews every document. Some
pairs of ADs consciously split the load. Some ADs don't do detailed reviews of
documents in other areas or just focus on specific topics.

But we must get off the idea that document review is the whole of the AD load. I
think it is only around 15-20%. Maybe that rises with pursuit of Discusses
(moral: don't raise Discusses). That doesn't mean that other parts of the load
couldn't be shifted.

Cheers,
Adrian


From mcr@sandelman.ca  Fri Oct 18 08:34:27 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 182D91F0ED5 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level: 
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.008,  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 5MuaQCienjXf for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:34:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id C45991F0D55 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:34:21 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 614162026F; Fri, 18 Oct 2013 12:44:57 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 86E3463B88; Fri, 18 Oct 2013 11:34:13 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7152063AEF; Fri, 18 Oct 2013 11:34:13 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
In-Reply-To: <7CB5C492-AEAB-4542-8305-0C86ACDCA765@nominum.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <7CB5C492-AEAB-4542-8305-0C86ACDCA765@nominum.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: Fri, 18 Oct 2013 11:34:13 -0400
Message-ID: <23406.1382110453@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:34:27 -0000

--=-=-=


Ted Lemon <ted.lemon@nominum.com> wrote:
    > Working group chairs are not raw material.  They are the result of
    > growing in the organization, and they are an extremely valuable part of
    > the organization.  Growing more working group chairs should be a
    > serious priority of the IETF, and our failure to do this well is very
    > much part of the AD overwork problem.

Ironically, having fewer working groups would mean having fewer working group
chairs, which would mean a smaller pool of people from which to pick ADs.

A reason we need more slots in the WG page for names (such as secretary,
key document author, issue triage expert, minutes tzar, etc.) is so that
  a) people can be recognized
  b) and the "re" (again) part of recognized means that they can be found
     again and their expertize leveraged.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUmFU84qHRg3pndX9AQJJaAP+JZOFOAoKhYiueigJnJLCjApXNlbbKAXA
LZl11bdz0WHM0YW1pzuzNbw+hKWfbLGIY6yVyBMBjq7ny9VS74upQTrqTi0fBK+K
yKiobWKfMhc1+tx+345EPENoMXDtQJlFu2p/sQ2Q1/Lja/LLkVCXC0j/3xJa+zjK
GO9Ls9SGBDE=
=3UgY
-----END PGP SIGNATURE-----
--=-=-=--

From Ted.Lemon@nominum.com  Fri Oct 18 08:45:36 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 80DD211E81C8 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 0atbRaGLKH6G for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:45:30 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id D3D0511E8263 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:45:29 -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 DSNKUmFXmZao+nh3AnnKumPkzQ0Z9YXYWwEl@postini.com; Fri, 18 Oct 2013 08:45:29 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 086801B82C6 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:45:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 E2502190060; Fri, 18 Oct 2013 08:45:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 08:45:29 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
Date: Fri, 18 Oct 2013 11:45:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <700D01D8-5C93-4BDF-AC8E-B9520E1CB60E@nominum.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 15:45:36 -0000

On Oct 18, 2013, at 9:45 AM, Andy Bierman <andy@yumaworks.com> wrote:
> Why not double the number of ADs in each area and instead of
> every AD reviewing every draft, have 2 ADs from each area
> review each draft? (Cut the AD hours in half somehow)

I don't review every draft (you can see which ones I didn't review on =
the record because I don't state a position if I didn't review the =
draft).   But there's a limit to how useful this is=97e.g., Brian =
Haberman has a very different history and set of experiences in the IETF =
than I do, so it's not necessarily the case that we would see the same =
things in reading the same document (and, indeed, we usually don't).

So I base my decision to review on more of a triage approach: I review =
the ones that I think are most important and most likely to be =
understandable to me first, and then branch out from there; if I have =
time to read them all, I do, but if I don't, I don't guilt trip about =
it.   I will almost certainly miss something important at some point, =
but that would be true even if I reviewed every document.

So the problem is that increasing the number of ADs per area might help, =
but I don't think it would be linear, so it's an expensive approach.


From mcr@sandelman.ca  Fri Oct 18 08:52:56 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 129CA21F9C20 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  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 4veDVnpTc1JY for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 08:52:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 2110E11E8257 for <ietf@ietf.org>; Fri, 18 Oct 2013 08:52:55 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7B0E22026F for <ietf@ietf.org>; Fri, 18 Oct 2013 13:03:30 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 8C1E863B88; Fri, 18 Oct 2013 11:52:46 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 77EA763AEF for <ietf@ietf.org>; Fri, 18 Oct 2013 11:52:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discuss <ietf@ietf.org>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
In-Reply-To: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@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: Fri, 18 Oct 2013 11:52:46 -0400
Message-ID: <27131.1382111566@sandelman.ca>
Sender: 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: Fri, 18 Oct 2013 15:52:56 -0000

--=-=-=


The question of credit for WG chairs (and IESG AD members) has become
important for two reasons:

1) the Internet community has grown sufficiently that many significant
   people do not know many other significant people.
   A template acknowledgement section that mentions the chairs and AD
   would be useful.  Maybe the RFC-editor should simply put it in.
   (The orcid would be useful here)

2) the IETF has gotten younger as it has grown, and there has been
   attrition at the top.  Until very recently, most of the people occupying
   the roles of AD or even WG chair, were in the middle to end of careers
   that started in 1987.  The younger people need to have the
   credits for their next job.

I think that we should change things.  We have the data in the datatracker.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUmFZTIqHRg3pndX9AQKiyAQAjElngkKVUV6kuiAIQaD2Zx3nqCuSgOAE
nf30Z7y5oMPo4F8yvBFCnUEyhQByhUBT9bNREQRbtb/0WNuCscuNz1PFUCF+iEZp
2F2ApuSj1E6y03KoPCCWDt4rkPf+Uz7OuUDW4v45W1BhgMx+JbbpmR7Vx1oTLZmh
B9LBEEzI8ic=
=tQQk
-----END PGP SIGNATURE-----
--=-=-=--

From mary.h.barnes@gmail.com  Fri Oct 18 09:13:10 2013
Return-Path: <mary.h.barnes@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 633EA11E81CB for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:13:10 -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.000, 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 gGPVAsZXhFiC for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:13:09 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFC211E8264 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:13:06 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id pa12so2095561veb.20 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:13:05 -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=sQN2ZzJ/5VLlBHoR52UD8ZQ4rfXlie8PQ0aG6uhhIz8=; b=TUWDFYgilV8rSv7KlNGNV2MkawJIWewEY+gx6cM+MMtGo8QF7g4XSuS/PaE2E+Na+b 1uUaAJ1sw6ZE8cbaKXbn32eP4Alsfb3BXCQwoe12JKCoO5VFt1/KNksESBMVUjwOjl7f LBAeI0A4G0W2dD2Sf0GN8S6e+jhLz5Mz3o0qIkw1wueiacRP62dxgxGk9ZudyVQlx36V TLG4R6Nq0oy6vOzeIQ7On3zEcHUULyVNbnuvNX2dlJeT0+fpLu1VRO6H8jWUnQQi1ucA 0ljO54Vy/DOzs27I3btOkufxzX6eFEEOIzPNzbcrURq7J54gsHvFaWHxOERKhUW7hqkt cIIw==
MIME-Version: 1.0
X-Received: by 10.58.207.15 with SMTP id ls15mr1996922vec.17.1382112785860; Fri, 18 Oct 2013 09:13:05 -0700 (PDT)
Received: by 10.58.44.226 with HTTP; Fri, 18 Oct 2013 09:13:05 -0700 (PDT)
In-Reply-To: <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>
Date: Fri, 18 Oct 2013 11:13:05 -0500
Message-ID: <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b6dc6eea40f3304e906353d
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: Fri, 18 Oct 2013 16:13:10 -0000

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

On Fri, Oct 18, 2013 at 10:10 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> The most useful comment I've heard on this thread is that it makes sense
> to credit the working group chairs as well as the authors of a document in
> the document at the same level of emphasis.   And possibly the ADs as well.
>   I don't know if this would make a difference, but it's interesting, and
> might be worth the experiment.
>
> But really, the main thing to say about this conversation is that it's a
> classic example of why the AD's job is so time consuming.   We have to
> monitor these conversations, because otherwise we aren't doing the part of
> our job that involves listening to the IETF.   Having long bikeshed
> discussions about the woeful brokenness of the AD's job over and over again
> without any action proposed is expensive.
>
> Most of what's been discussed here has been discussed by the ADs during
> the recent IESG retreat, and substantial action was taken as a result of
> the discussion at that retreat.   It might be interesting to see if any of
> what we discussed actually changes anything.
>
> [MB] Can you clue us in as to what "substantial action" has been taken?
[/MB]

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra">On Fri, Oct 18, 2013 at 10:=
10 AM, 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><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">The most useful comment I&#39;ve heard on th=
is thread is that it makes sense to credit the working group chairs as well=
 as the authors of a document in the document at the same level of emphasis=
. =A0 And possibly the ADs as well. =A0 I don&#39;t know if this would make=
 a difference, but it&#39;s interesting, and might be worth the experiment.=
<br>

<br>
But really, the main thing to say about this conversation is that it&#39;s =
a classic example of why the AD&#39;s job is so time consuming. =A0 We have=
 to monitor these conversations, because otherwise we aren&#39;t doing the =
part of our job that involves listening to the IETF. =A0 Having long bikesh=
ed discussions about the woeful brokenness of the AD&#39;s job over and ove=
r again without any action proposed is expensive.<br>

<br>
Most of what&#39;s been discussed here has been discussed by the ADs during=
 the recent IESG retreat, and substantial action was taken as a result of t=
he discussion at that retreat. =A0 It might be interesting to see if any of=
 what we discussed actually changes anything.<br>

<br></blockquote><div>[MB] Can you clue us in as to what &quot;substantial =
action&quot; has been taken? =A0 [/MB]=A0</div></div><br></div></div>

--047d7b6dc6eea40f3304e906353d--

From scott.brim@gmail.com  Fri Oct 18 09:15:32 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 227FE11E82F0 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:15: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=[AWL=0.000, 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 fokOwx5SHwB3 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:15:31 -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 42D7D11E82CB for <ietf@ietf.org>; Fri, 18 Oct 2013 09:15:31 -0700 (PDT)
Received: by mail-ee0-f49.google.com with SMTP id d41so2128373eek.8 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:15: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=5hqtACLQZlW5gaPyMLKnwelPUh+K0/sv0wyrH4FtuvE=; b=yizcXIqcD2vUWnZ7Z32+TjK4P2ap9wuvopBsXIw4q3PZK1+dkABdMBaZt9eph5qpqa AEDOsF+jfSiycitdsJe9nhkLVpFD+MIrKhWtUfMXeg3+5tG5uMzP5t/rOSAqO19R376q COETOgf9YELgn93VZHT+o0FG+W18ahABuRyhMwXmn82poXhej4zdrera+045Hqy9rtbP uZDj+Ww1K9lXFDSRRURd1k7mQeSz2+eHs2ZxonJTqSuU/2z4T98pjrINnUqkfmPb6iQy jOFOlGUNCtuUtIqteghctRkW8Pz25gXSxxoMLUWf38Kb0gc9OUyaWEd7FBvFVJwcImPk QMjA==
MIME-Version: 1.0
X-Received: by 10.14.93.132 with SMTP id l4mr223367eef.119.1382112929786; Fri, 18 Oct 2013 09:15:29 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Fri, 18 Oct 2013 09:15:29 -0700 (PDT)
Received: by 10.14.205.7 with HTTP; Fri, 18 Oct 2013 09:15:29 -0700 (PDT)
In-Reply-To: <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com>
Date: Fri, 18 Oct 2013 12:15:29 -0400
Message-ID: <CAPv4CP8iA-ZiWsNBGWd0CA6OZPCtAAKhuPf5x42ortQ=kxU-fQ@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Scott Brim <scott.brim@gmail.com>
To: Andy Bierman <andy@yumaworks.com>
Content-Type: multipart/alternative; boundary=001a11c288fa38303b04e9063ea6
Cc: John C Klensin <john-ietf@jck.com>, Adrian Ferrell <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 16:15:32 -0000

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

On Oct 18, 2013 9:45 AM, "Andy Bierman" <andy@yumaworks.com> wrote:
>
> Hi Adrian,
>
> I have asked you and other ADs several times if Assistant ADs would help.
> The answer I got was "not really, but a well run directorate really
helps.".

I don't see much difference between an assistant AD and a good member of a
good directorate.

> Why not double the number of ADs in each area and instead of
> every AD reviewing every draft, have 2 ADs from each area
> review each draft? (Cut the AD hours in half somehow)

The problem is you don't know where cross-area insight is going to come
from.

Scott

--001a11c288fa38303b04e9063ea6
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr">On Oct 18, 2013 9:45 AM, &quot;Andy Bierman&quot; &lt;<a href="mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Adrian,<br>
&gt;<br>
&gt; I have asked you and other ADs several times if Assistant ADs would help.<br>
&gt; The answer I got was &quot;not really, but a well run directorate really helps.&quot;.</p>
<p dir="ltr">I don&#39;t see much difference between an assistant AD and a good member of a good directorate. </p>
<p dir="ltr">&gt; Why not double the number of ADs in each area and instead of<br>
&gt; every AD reviewing every draft, have 2 ADs from each area<br>
&gt; review each draft? (Cut the AD hours in half somehow)</p>
<p dir="ltr">The problem is you don&#39;t know where cross-area insight is going to come from. </p>
<p dir="ltr">Scott </p>

--001a11c288fa38303b04e9063ea6--

From Ted.Lemon@nominum.com  Fri Oct 18 09:38:10 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 3878E11E8271 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 pKKVmaBsKlvT for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:38:03 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id AAC1911E825D for <ietf@ietf.org>; Fri, 18 Oct 2013 09:38:03 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUmFj69WFSt0+PRrw518CnIjVNiR/1Moo@postini.com; Fri, 18 Oct 2013 09:38:03 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 076BC1B8274 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:38:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 013BC190060; Fri, 18 Oct 2013 09:38:03 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 09:38:02 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com>
Date: Fri, 18 Oct 2013 12:38:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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: Fri, 18 Oct 2013 16:38:10 -0000

On Oct 18, 2013, at 12:13 PM, Mary Barnes <mary.h.barnes@gmail.com> =
wrote:
> [MB] Can you clue us in as to what "substantial action" has been =
taken?   [/MB]=20

I thought we sent something around about that.   ADs and WG chairs are =
encouraged to ask for directorate reviews for certain directorates =
(possibly all directorates, I can't remember) prior to working group =
last call.   This is in the form of an experiment, not a new policy; =
we'll see how it goes.

We've done a number of other things in the same vein=97e.g., document =
shepherds are now being invited onto telechats, so that they can do the =
work of tracking action items for the authors rather than the AD doing =
it.

I think there were other items on the list, but I don't remember them =
off the top of my head.   The point is, if anybody thinks the IESG is a =
deer in the headlights on this issue, that's not the case=97we are =
actively trying to do things to ameliorate the situation.


From joelja@bogus.com  Fri Oct 18 09:45:14 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 D479F11E82F9 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:45: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 sZOafJBankkf for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:45:13 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 10BCF11E82E7 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:45:13 -0700 (PDT)
Received: from 00698a-hsutim.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9IGj728030950 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 18 Oct 2013 16:45:07 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_3A5ED4FE-7D12-44FF-AA53-32241D9DC9F3"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com>
Date: Fri, 18 Oct 2013 09:45:03 -0700
Message-Id: <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 18 Oct 2013 16:45:07 +0000 (UTC)
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: Fri, 18 Oct 2013 16:45:14 -0000

--Apple-Mail=_3A5ED4FE-7D12-44FF-AA53-32241D9DC9F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 18, 2013, at 9:38 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 18, 2013, at 12:13 PM, Mary Barnes <mary.h.barnes@gmail.com> =
wrote:
>> [MB] Can you clue us in as to what "substantial action" has been =
taken?   [/MB]=20
>=20
> I thought we sent something around about that.   ADs and WG chairs are =
encouraged to ask for directorate reviews for certain directorates =
(possibly all directorates, I can't remember) prior to working group =
last call.   This is in the form of an experiment, not a new policy; =
we'll see how it goes.
>=20
> We've done a number of other things in the same vein=97e.g., document =
shepherds are now being invited onto telechats, so that they can do the =
work of tracking action items for the authors rather than the AD doing =
it.
>=20
> I think there were other items on the list, but I don't remember them =
off the top of my head.   The point is, if anybody thinks the IESG is a =
deer in the headlights on this issue, that's not the case=97we are =
actively trying to do things to ameliorate the situation.

The revision of the qualifications provided to the nomcom was =
signficant.

experiments with narrative shepherds reports.

experiments with post-ietf working-group summaries performed by chairs.

>=20


--Apple-Mail=_3A5ED4FE-7D12-44FF-AA53-32241D9DC9F3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJhZY8ACgkQ8AA1q7Z/VrIpXQCbB2A1abdjebspSBmr93ghZV5w
2RcAn35pXXhogRT93yx04/FKYYt8yzcY
=AkHl
-----END PGP SIGNATURE-----

--Apple-Mail=_3A5ED4FE-7D12-44FF-AA53-32241D9DC9F3--

From mary.h.barnes@gmail.com  Fri Oct 18 09:51:00 2013
Return-Path: <mary.h.barnes@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 4AD1521F9C83 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:51:00 -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, 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 yPRZ5xFq-VJc for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 09:50:59 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 166ED21F9C8B for <ietf@ietf.org>; Fri, 18 Oct 2013 09:50:54 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id jz11so2181444veb.35 for <ietf@ietf.org>; Fri, 18 Oct 2013 09:50: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=fV0vBiWVf7Tb21khpAKK/Ng7WhqfMMyEWH8O9gv+F1E=; b=ETkg97Qohx3HeAgU1dAXlKLoI+3V+VaGt5Zs/h96xbGz4Q5nOL2J24KC/nahPNSJ4W aqmLxeURWLUT0EOPGPWL7I9V8KU5NlgJdesuzI+2ht1Z7YSsAtSCmurZPyROwPDcps/Z JsdoBx98ifClG5pJldPwUjl3o6lcanxq1crPPAqx/UO5SuPm+F/LtvKxDTypwGN99e/5 pJJOZJJLGZtPf89L8P1Ftu4+wDYmIXe/wI6O1Xb1u7sFkVbVvcM1wK1RVa52rYtjDOVY a9i8x+qdvLlMDtVo50Gbc0GZ2sjQ3V+xccpQCF+YJxBsRtVSWJRd4cljop2VzmUfUcWE CJcQ==
MIME-Version: 1.0
X-Received: by 10.52.243.138 with SMTP id wy10mr2379505vdc.2.1382115054387; Fri, 18 Oct 2013 09:50:54 -0700 (PDT)
Received: by 10.58.44.226 with HTTP; Fri, 18 Oct 2013 09:50:54 -0700 (PDT)
In-Reply-To: <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com>
Date: Fri, 18 Oct 2013 11:50:54 -0500
Message-ID: <CABmDk8mqhVvQK97XtbrTLS5WQ-JVvaFOTxr-xhbUwa2FRZRJ3Q@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c1c4a6db07ef04e906bcea
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: Fri, 18 Oct 2013 16:51:00 -0000

--001a11c1c4a6db07ef04e906bcea
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 18, 2013 at 11:38 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 18, 2013, at 12:13 PM, Mary Barnes <mary.h.barnes@gmail.com> wrote=
:
> > [MB] Can you clue us in as to what "substantial action" has been taken?
>   [/MB]
>
> I thought we sent something around about that.   ADs and WG chairs are
> encouraged to ask for directorate reviews for certain directorates
> (possibly all directorates, I can't remember) prior to working group last
> call.   This is in the form of an experiment, not a new policy; we'll see
> how it goes.
>
[MB]  Okay. I remember this one, but I thought that was more around
improving quality than reducing workload.  [ /MB]

>
> We've done a number of other things in the same vein=97e.g., document
> shepherds are now being invited onto telechats, so that they can do the
> work of tracking action items for the authors rather than the AD doing it=
.
>
[MB] I'm assuming this is on a case by case basis as I've not been invited
to any telechats.  And, I'm not aware that the shepherds of my own
documents have been on telechats.  For my recent docs, I've been dealing
directly with the issues via email and the not shepherd or ADs.
Certainly, the past, I worked more closely with the AD on issues from the
telechat, but I had thought that was more working style than
intentional.[/MB]

>
> I think there were other items on the list, but I don't remember them off
> the top of my head.   The point is, if anybody thinks the IESG is a deer =
in
> the headlights on this issue, that's not the case=97we are actively tryin=
g to
> do things to ameliorate the situation.

--001a11c1c4a6db07ef04e906bcea
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Fri, Oct 18, 2013 at 11:38 AM, Ted Lemon <span dir=3D"ltr">&lt;<a hr=
ef=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">On Oct 18, 2013, at 12:13 =
PM, Mary Barnes &lt;<a href=3D"mailto:mary.h.barnes@gmail.com">mary.h.barne=
s@gmail.com</a>&gt; wrote:<br>

&gt; [MB] Can you clue us in as to what &quot;substantial action&quot; has =
been taken? =A0 [/MB]<br>
<br>
</div>I thought we sent something around about that. =A0 ADs and WG chairs =
are encouraged to ask for directorate reviews for certain directorates (pos=
sibly all directorates, I can&#39;t remember) prior to working group last c=
all. =A0 This is in the form of an experiment, not a new policy; we&#39;ll =
see how it goes.<br>
</blockquote><div>[MB] =A0Okay. I remember this one, but I thought that was=
 more around improving quality than reducing workload. =A0[ /MB]=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">

<br>
We&#39;ve done a number of other things in the same vein=97e.g., document s=
hepherds are now being invited onto telechats, so that they can do the work=
 of tracking action items for the authors rather than the AD doing it.<br>
</blockquote><div>[MB] I&#39;m assuming this is on a case by case basis as =
I&#39;ve not been invited to any telechats. =A0And, I&#39;m not aware that =
the shepherds of my own documents have been on telechats. =A0For my recent =
docs, I&#39;ve been dealing directly with the issues via email and the not =
shepherd or ADs. =A0 Certainly, the past, I worked more closely with the AD=
 on issues from the telechat, but I had thought that was more working style=
 than intentional.[/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I think there were other items on the list, but I don&#39;t remember them o=
ff the top of my head. =A0 The point is, if anybody thinks the IESG is a de=
er in the headlights on this issue, that&#39;s not the case=97we are active=
ly trying to do things to ameliorate the situation.=A0</blockquote>
<div>=A0</div></div><br></div></div>

--001a11c1c4a6db07ef04e906bcea--

From daedulus@btconnect.com  Fri Oct 18 10:11:11 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 8F20311E8291 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.761
X-Spam-Level: 
X-Spam-Status: No, score=-3.761 tagged_above=-999 required=5 tests=[AWL=-0.162, 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 t6FVij6dXDeL for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:11:05 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id 790B811E8293 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:11:01 -0700 (PDT)
Received: from mail55-ch1-R.bigfish.com (10.43.68.242) by CH1EHSOBE022.bigfish.com (10.43.70.79) with Microsoft SMTP Server id 14.1.225.22; Fri, 18 Oct 2013 17:10:58 +0000
Received: from mail55-ch1 (localhost [127.0.0.1])	by mail55-ch1-R.bigfish.com (Postfix) with ESMTP id 7D5B44600FF; Fri, 18 Oct 2013 17:10:58 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(z551bizbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275dh1de097h8275bhz2dh2a8h5a9h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail55-ch1 (localhost.localdomain [127.0.0.1]) by mail55-ch1 (MessageSwitch) id 1382116256190230_29418; Fri, 18 Oct 2013 17:10:56 +0000 (UTC)
Received: from CH1EHSMHS005.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.233])	by mail55-ch1.bigfish.com (Postfix) with ESMTP id 207B0C0033; Fri, 18 Oct 2013 17:10:56 +0000 (UTC)
Received: from AM2PRD0710HT002.eurprd07.prod.outlook.com (157.56.249.213) by CH1EHSMHS005.bigfish.com (10.43.70.5) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 18 Oct 2013 17:10:55 +0000
Received: from DBXPRD0411HT001.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.255.165.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 18 Oct 2013 17:10:29 +0000
Message-ID: <000d01cecc24$ac95a3e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com>	<27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk>	<52602DF7.3030207@dcrocker.net>	<DC59B10837C9CD235DD98438@JcK-HP8200.jck.com>	<5260334D.10806@dcrocker.net><52603628.1080007@stpeter.im> <52603C96.2030409@gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call forNominations)
Date: Fri, 18 Oct 2013 18:08:22 +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
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 17:11:11 -0000

---- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
Cc: "John C Klensin" <john-ietf@jck.com>; <dcrocker@bbiw.net>; "IETF
Discuss" <ietf@ietf.org>
Sent: Thursday, October 17, 2013 8:37 PM
> On 18/10/2013 08:10, Peter Saint-Andre wrote:
> ...
> > It might be helpful to talk about what could change, such as:
>
> I've inserted some ideas about how to make such changes possible.
>
> > 1. Less/no time on document reviews.
>
> 1A. All WGs do a near-perfect job on their drafts, including
> complete management of cross-area reviews.
>
> 1B. Lower the current bar of near-perfection for document approval.
>
> 1C. IESG is allowed to reject a document as "Not ready" without
> detailed explanation.
>
> > 2. Less time managing working groups.
>
> 2A. All WG Chairs to do a near-perfect job.
>
> 2B. Quickly replace failing WG Chairs.
>
> 2C. Summary closure of failing WGs.
>
> > 3. Fewer working groups to manage.
>
> 3A. IESG refuses the majority of proposed WGs.
>
> 3B. See 2C.

I have thought for some time that this is the way that the IETF will go,
that the effort available within the IETF is declining and so the work
that can be done must also decline.  Experience tells me that it
takes a disaster or two for this to become apparent; perhaps a
shortage of ADs is such an event.

I do think that there are some 'limping' WGs, ones which perhaps cost
proportionately more in terms of AD time, that should not have been
formed or not be allowed to run on.

Tom Petch




> > 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).
>
> 4A. Leave liaisons entirely to the designated liaison managers.
>
> 4B. Replace failing liaison managers. (IAB job)
>
> 4C. Simply refuse other extra tasks.
>
> > 5. Less/no involvement with BoFs and other early-stage efforts.
>
> 5A. IAB spends less time on admin/politics and more time on
Architecture,
> including BOFs. Also see 3A.
>
> > 6. Less/no involvement with creating the schedule.
>
> [I'm not sure that will work. ADs are uniquely placed to
> identify clashes and overlaps.]
>
>    Brian
>



From andy@yumaworks.com  Fri Oct 18 10:39:40 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 A5FCE11E82C6 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level: 
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[AWL=0.159,  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 TzoxgdqMj7IL for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:39:35 -0700 (PDT)
Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6294111E8267 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:39:35 -0700 (PDT)
Received: by mail-qe0-f45.google.com with SMTP id 8so2069297qea.4 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:39:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1XxIGWeN1modYLy9pEV3md1hTA1sQfBjuqPObu25mXU=; b=VTLnMdW7hC2xb8FdRyZIQuBpT2hdCAibc5gV1t5+K9Ffi4nuhEB6ruEgdrMd8z++a7 ODYI4L2O8bmT88rLqN3TRZbSlyRb0tBbgBXs5Za2RKNZVObwv0dJzol9ZaPqVXh0aIIu 9F1/N5jpUqbvsdwYP6TRYGjVEMhWlQCnWLiH6eD49pvXwiE/QKiGTXas0i/082ApEzvx OJjKRWOcZd0I3d18yLzh74imh21pjl8O0rt7TlZaOZmszz35TXJuuCV0tzX1MyS+IHHB 2woukQwjo/i1EEo1B1g8sDyKPAx7P5xH8+MABZsjk8DCFNznUXzoP91/+qaLd9AmrYJm TUAQ==
X-Gm-Message-State: ALoCoQnxn3DhjUQp3vo8JlgBeRgydSbCOmxzfNfmW6LVqC7ZqpFAFr3AXY4rHqzdnBvVJ1n4rO2L
MIME-Version: 1.0
X-Received: by 10.49.35.15 with SMTP id d15mr5736340qej.16.1382117974717; Fri, 18 Oct 2013 10:39:34 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Fri, 18 Oct 2013 10:39:34 -0700 (PDT)
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
Date: Fri, 18 Oct 2013 10:39:34 -0700
Message-ID: <CABCOCHSLmDx_-ofQsvrEhJi_A6nbWJRqdYrn6gHOpRaMuEG6XQ@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Andy Bierman <andy@yumaworks.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7b6dcbe0ebe6dd04e9076ab5
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 17:39:40 -0000

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

Hi,

I don't think the Assistant AD job would be easy to define
or even the right approach.  IMO doubling the number of ADs
would probably work better, although at an increased cost
wrt/ managing the review process. I do not agree that
every AD needs to review every draft. The review
and WG management tasks should be shared by 4 people
instead of 2 people.

The problem I see is that few people are both qualified
and able to do full-time volunteer work for the IESG.
There is a disconnect between the official job requirements
and the real job requirements that is being ignored here.

Perhaps if the AD job really was only 20 hours a week
there would be a lot more people willing and able to
accept a nomination.


Andy

On Fri, Oct 18, 2013 at 8:33 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> > I have asked you and other ADs several times if Assistant ADs would help.
> > The answer I got was "not really, but a well run directorate really
> helps.".
>
> OK. Doesn't sound like refusing to consider. Sounds like answering your
> question.
>
> So let's take it to the next step because it may be that the current IESG
> cannot
> conceive of how an assistant AD would work.
>
> Can you put up a strawman of the job tasks of an assistant AD that we can
> work
> with to discuss whether this has legs?
> Would assistant ADs be appointed and work for sitting ADs, or would they be
> NomCom appointments?
> Can't an AD already delegate anything they want (except the
> responsibility)?
>
> > Why not double the number of ADs in each area and instead of
> > every AD reviewing every draft, have 2 ADs from each area
> > review each draft? (Cut the AD hours in half somehow)
>
> There is mileage in that. I don't think every AD reviews every document.
> Some
> pairs of ADs consciously split the load. Some ADs don't do detailed
> reviews of
> documents in other areas or just focus on specific topics.
>
> But we must get off the idea that document review is the whole of the AD
> load. I
> think it is only around 15-20%. Maybe that rises with pursuit of Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of the
> load
> couldn't be shifted.
>
> Cheers,
> Adrian
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>I don&#39;t think the Assistant AD =
job would be easy to define</div><div>or even the right approach. =A0IMO do=
ubling the number of ADs</div><div>would probably work better, although at =
an increased cost</div>
<div>wrt/ managing the review process. I do not agree that</div><div>every =
AD needs to review every draft. The review</div><div>and WG management task=
s should be shared by 4 people</div><div>instead of 2 people.</div><div>
<br></div><div>The problem I see is that few people are both qualified</div=
><div>and able to do full-time volunteer work for the IESG.</div><div>There=
 is a disconnect between the official job requirements</div><div>and the re=
al job requirements that is being ignored here.</div>
<div><br></div><div>Perhaps if the AD job really was only 20 hours a week</=
div><div>there would be a lot more people willing and able to</div><div>acc=
ept a nomination.<br><div class=3D"gmail_extra"><br><br>Andy</div><div clas=
s=3D"gmail_extra">
<br><div class=3D"gmail_quote">On Fri, Oct 18, 2013 at 8:33 AM, Adrian Farr=
el <span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_=
blank">adrian@olddog.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
&gt; I have asked you and other ADs several times if Assistant ADs would he=
lp.<br>
&gt; The answer I got was &quot;not really, but a well run directorate real=
ly helps.&quot;.<br>
<br>
OK. Doesn&#39;t sound like refusing to consider. Sounds like answering your=
<br>
question.<br>
<br>
So let&#39;s take it to the next step because it may be that the current IE=
SG cannot<br>
conceive of how an assistant AD would work.<br>
<br>
Can you put up a strawman of the job tasks of an assistant AD that we can w=
ork<br>
with to discuss whether this has legs?<br>
Would assistant ADs be appointed and work for sitting ADs, or would they be=
<br>
NomCom appointments?<br>
Can&#39;t an AD already delegate anything they want (except the responsibil=
ity)?<br>
<br>
&gt; Why not double the number of ADs in each area and instead of<br>
&gt; every AD reviewing every draft, have 2 ADs from each area<br>
&gt; review each draft? (Cut the AD hours in half somehow)<br>
<br>
There is mileage in that. I don&#39;t think every AD reviews every document=
. Some<br>
pairs of ADs consciously split the load. Some ADs don&#39;t do detailed rev=
iews of<br>
documents in other areas or just focus on specific topics.<br>
<br>
But we must get off the idea that document review is the whole of the AD lo=
ad. I<br>
think it is only around 15-20%. Maybe that rises with pursuit of Discusses<=
br>
(moral: don&#39;t raise Discusses). That doesn&#39;t mean that other parts =
of the load<br>
couldn&#39;t be shifted.<br>
<br>
Cheers,<br>
Adrian<br>
<br>
</blockquote></div><br></div></div></div>

--047d7b6dcbe0ebe6dd04e9076ab5--

From kathleen.moriarty@emc.com  Fri Oct 18 10:45:07 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 5E90711E80F9 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level: 
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=-0.166, 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 Zn2Fdg-kZnrU for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:45:01 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EB93111E8109 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:44:55 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9IHinek009754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Oct 2013 13:44:52 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r9IHinek009754
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1382118292; bh=75WlUiTviSFVJFnztJOH198xWO8=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=rnEODPHtKpAeTrlfUMoN7TN6JOXr5wULyiPWVRqGZ4ErNWNX0nd+HLngsE7GdLmBh Wqxnqx+2KAezpXyO4YU2l8gFPA6kio6s2OgwYnq5zns1x9PArggBMOqjclnMydp3GG ckhTGrgrE+uWaOWWJGPPw6AbEPROtWOBU21LOAvg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r9IHinek009754
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd06.lss.emc.com (RSA Interceptor); Fri, 18 Oct 2013 10:44:34 -0700
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9IHiXPG000522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Oct 2013 13:44:33 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Fri, 18 Oct 2013 13:44:33 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: joel jaeggli <joelja@bogus.com>, Ted Lemon <ted.lemon@nominum.com>
Date: Fri, 18 Oct 2013 13:44:31 -0400
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Topic: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Index: Ac7MIXVaNwkEtc/vRWyqomSyucf8YwACCKpg
Message-ID: <F5063677821E3B4F81ACFB7905573F24049E8BCCBE@MX15A.corp.emc.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com> <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.com>
In-Reply-To: <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.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-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
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: Fri, 18 Oct 2013 17:45:07 -0000

How about implementation reports that are done by the chairs or one chair? =
 Content has to come from a mix of implementers.

-Kathleen

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of joe=
l jaeggli
Sent: Friday, October 18, 2013 12:45 PM
To: Ted Lemon
Cc: IETF Discussion
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE T=
HE JOB)


On Oct 18, 2013, at 9:38 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Oct 18, 2013, at 12:13 PM, Mary Barnes <mary.h.barnes@gmail.com> wrote=
:
>> [MB] Can you clue us in as to what "substantial action" has been taken? =
  [/MB]=20
>=20
> I thought we sent something around about that.   ADs and WG chairs are en=
couraged to ask for directorate reviews for certain directorates (possibly =
all directorates, I can't remember) prior to working group last call.   Thi=
s is in the form of an experiment, not a new policy; we'll see how it goes.
>=20
> We've done a number of other things in the same vein-e.g., document sheph=
erds are now being invited onto telechats, so that they can do the work of =
tracking action items for the authors rather than the AD doing it.
>=20
> I think there were other items on the list, but I don't remember them off=
 the top of my head.   The point is, if anybody thinks the IESG is a deer i=
n the headlights on this issue, that's not the case-we are actively trying =
to do things to ameliorate the situation.

The revision of the qualifications provided to the nomcom was signficant.

experiments with narrative shepherds reports.

experiments with post-ietf working-group summaries performed by chairs.

>=20


From Ted.Lemon@nominum.com  Fri Oct 18 10:54:17 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 A58D221F9CFB for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 4-CLyDxCMKX5 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:54:05 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id E046F21F9433 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:54:04 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUmF1u4D2sb4bAms1VK02QtuDDVPN3lPy@postini.com; Fri, 18 Oct 2013 10:54:04 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 DA7751B82C3 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:54:02 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 AF3AA190060; Fri, 18 Oct 2013 10:54:02 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 10:54:02 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24049E8BCCBE@MX15A.corp.emc.com>
Date: Fri, 18 Oct 2013 13:54:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <65B5267E-7841-49C0-9302-559B4BA41506@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com> <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.com> <F5063677821E3B4F81ACFB7905573F24049E8BCCBE@MX15A.corp.emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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: Fri, 18 Oct 2013 17:54:18 -0000

On Oct 18, 2013, at 1:44 PM, Moriarty, Kathleen =
<kathleen.moriarty@emc.com> wrote:
> How about implementation reports that are done by the chairs or one =
chair?  Content has to come from a mix of implementers.

Implementation reports are certainly worth doing=97they're absolutely =
the best form of review for basic completeness of a specification, =
although they don't catch cross-area issues, and can give people a false =
sense of confidence that what they have is the right solution.   But I =
don't see how they would play into the problem of reducing AD workload.


From john-ietf@jck.com  Fri Oct 18 10:57:08 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 4DE5311E827A for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.588
X-Spam-Level: 
X-Spam-Status: No, score=-103.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 XAKc2qT7OS1b for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 10:57:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9051211E81F3 for <ietf@ietf.org>; Fri, 18 Oct 2013 10:57:02 -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 1VXEIF-00056t-WC; Fri, 18 Oct 2013 13:57:00 -0400
Date: Fri, 18 Oct 2013 13:56:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Message-ID: <FB1186A6C0EA33FEE71FF584@JcK-HP8200.jck.com>
In-Reply-To: <20131018141322.GI4003@mx1.yitter.info>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 17:57:08 -0000

--On Friday, October 18, 2013 10:13 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> No hat.
> 
> On Thu, Oct 17, 2013 at 06:52:11PM -0400, John C Klensin wrote:
>> I wonder if we should be publishing, at regular intervals,
>> RFCs with explicit acknowledgements and maybe contact
>> information for Areas and ADs, WG Chairs, and, if
>> appropriate, other IETF functionaries, probably including
>> document reviewers and Nomcom members.

Hi.

I'm not going to spend much energy defending that idea.  If it
seems useful, fine.  If not, drop it.  

So one comment-message and then I'll stop

> I'm not keen on adding this cruft to the RFC series.  I note
> that the tools pages are now archived, so if you go to
> http://tools.ietf.org/wg/dnsext you will find that it's
> concluded and that Olafur and I were chair at the end.  What
> you _won't_ find is the history of other chairs.  Maybe that's
> an issue?

> On the other hand, isn't this what resumes are for?

It depends on one's purpose.  If you put in your resume that you
chaired that WG, and some wants to verify that, the tools pages
are fine.  If Olaf does, he is probably in trouble and that is
one of several reasons why one might want a back trace (but
doesn't justify an RFC).  On the other hand, if someone wanted
to know which WGs you had chaired since you started
participating in the IETF, that had better be in your resume
because trying to find it from the tools pages (even with Chair
history as well as Charter history) would be a little tedious.
(I just noticed that information isn't in my CV; maybe it should
be.)

If I'm working for a company than is credit-happy, or if I have
a boss who wants to see my name in print to justify my job,
salary, or next meeting costs, I'm perhaps likely to prefer
something a little more solid and archival.

As far as academic, etc., credit is concerned, part of what
stimulated the idea was the practice in several journals of
publishing an annual list of reviewers, partially to give credit
while keeping the reviewer-article binding confidential.   The
analogy isn't terribly good, but...

Could we do the same job by making sure that WG Chairs,
Shepherds, ADs, and other folks who move the work along are
acknowledged?  I don't know, although I agree that being
somewhat better about those sorts of acknowledgements would be a
good idea (and I just modified the template I use to remind me
to do that).  Barry might go ask whomever raised the issue what
would or would not help.

As to simply listing everyone as a co-author or otherwise on the
front page, first of all, the reason for the "tradition" was a
strong conviction that the listed person should be a real
author, document consolidator/ editor, and/or what we sometimes
call the "holder of the pen" _and_ the primary contact
person(s).   For a given document, the number of those people is
rarely more than one or two.  In that context, "five" was a
concession and everyone else goes either into Acknowledgments or
a "Contributors" section (another concession).  Do we want to go
to listing everyone in sight, including people's managers, their
managers, and perhaps their kindergarten teachers, as authors?
I hope not, but that is just my personal bias.  If nothing else,
we are doing (largely) standards and protocol specifications
here, not scientific papers and the accountability issues are
entirely different.

Or maybe there is an entirely different problem.  I was vastly
amused by a recent posting in a different thread that suggested
that much of the IETF's leadership started their professional
careers around 1987.  I've got a couple of decades on that as
does Steve Crocker who was the first person who posted a note
endorsing the RFC idea.  If the IETF conclusion is that the idea
appeals only to elderly types who didn't grow up with the web
and other modern media, then drop it.  On the other hand, Steve
and I have a tad more experience dealing with these sorts of
issue at a senior management and promotion and budget
justification level than the IETF average, so maybe it is not
_just_ a geriatric reaction.

     john



From joelja@bogus.com  Fri Oct 18 11:07: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 1C8B611E8297 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 11:07:36 -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 LbnRW61XsENO for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 11:07:35 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 78E3A11E8288 for <ietf@ietf.org>; Fri, 18 Oct 2013 11:07:35 -0700 (PDT)
Received: from 00698a-hsutim.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9II7Lu1031986 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 18 Oct 2013 18:07:21 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_1C76910A-19EB-4B29-8ED6-DBCED3392C8A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <CABCOCHSLmDx_-ofQsvrEhJi_A6nbWJRqdYrn6gHOpRaMuEG6XQ@mail.gmail.com>
Date: Fri, 18 Oct 2013 11:07:17 -0700
Message-Id: <A14E3A9C-C46E-47DE-A20F-473416B6CA15@bogus.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <CABCOCHSLmDx_-ofQsvrEhJi_A6nbWJRqdYrn6gHOpRaMuEG6XQ@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 18 Oct 2013 18:07:22 +0000 (UTC)
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 18:07:36 -0000

--Apple-Mail=_1C76910A-19EB-4B29-8ED6-DBCED3392C8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 18, 2013, at 10:39 AM, Andy Bierman <andy@yumaworks.com> wrote:

> Hi,
>=20
> I don't think the Assistant AD job would be easy to define
> or even the right approach.  IMO doubling the number of ADs
> would probably work better, although at an increased cost
> wrt/ managing the review process. I do not agree that
> every AD needs to review every draft. The review
> and WG management tasks should be shared by 4 people
> instead of 2 people.
>=20
> The problem I see is that few people are both qualified
> and able to do full-time volunteer work for the IESG.
> There is a disconnect between the official job requirements
> and the real job requirements that is being ignored here.
>=20
> Perhaps if the AD job really was only 20 hours a week
> there would be a lot more people willing and able to
> accept a nomination.
>=20

For better or worse I told the nomcom that I only have 2 hours a day (7 =
days a  week) for this=85 They took me anyway. The load is unevenly =
distributed. The internet and routing and Apps ADs appear to have more  =
drafts to process and more complex working group interactions, then does =
the ops side of ops and management.

That said, this is not a not a full time job for me and I am not =
compensated for doing it. If my level of available commitment isn't =
adequate, I guess we'll find out between now and the 2 year mark.  My =
contribution to the things that bring me to the IETF as on operator have =
dropped off because I don't have time for them.

joel

>=20
> Andy
>=20
> On Fri, Oct 18, 2013 at 8:33 AM, Adrian Farrel <adrian@olddog.co.uk> =
wrote:
> > I have asked you and other ADs several times if Assistant ADs would =
help.
> > The answer I got was "not really, but a well run directorate really =
helps.".
>=20
> OK. Doesn't sound like refusing to consider. Sounds like answering =
your
> question.
>=20
> So let's take it to the next step because it may be that the current =
IESG cannot
> conceive of how an assistant AD would work.
>=20
> Can you put up a strawman of the job tasks of an assistant AD that we =
can work
> with to discuss whether this has legs?
> Would assistant ADs be appointed and work for sitting ADs, or would =
they be
> NomCom appointments?
> Can't an AD already delegate anything they want (except the =
responsibility)?
>=20
> > Why not double the number of ADs in each area and instead of
> > every AD reviewing every draft, have 2 ADs from each area
> > review each draft? (Cut the AD hours in half somehow)
>=20
> There is mileage in that. I don't think every AD reviews every =
document. Some
> pairs of ADs consciously split the load. Some ADs don't do detailed =
reviews of
> documents in other areas or just focus on specific topics.
>=20
> But we must get off the idea that document review is the whole of the =
AD load. I
> think it is only around 15-20%. Maybe that rises with pursuit of =
Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of =
the load
> couldn't be shifted.
>=20
> Cheers,
> Adrian
>=20
>=20


--Apple-Mail=_1C76910A-19EB-4B29-8ED6-DBCED3392C8A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJheNUACgkQ8AA1q7Z/VrJTvQCfUeGQD4OVAq8x1JN7vhFiW1Xf
1WcAn0CC5utEsvuvrnao/Iux0ms/n3j6
=++wK
-----END PGP SIGNATURE-----

--Apple-Mail=_1C76910A-19EB-4B29-8ED6-DBCED3392C8A--

From abdussalambaryun@gmail.com  Fri Oct 18 12:23:02 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 5EFC311E81FF for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  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 1tJlmxxpv1t7 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:23:01 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id DD84011E8299 for <ietf@ietf.org>; Fri, 18 Oct 2013 12:22:58 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id p10so2744062pdj.11 for <ietf@ietf.org>; Fri, 18 Oct 2013 12:22: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=lZv6tEWnsbKqd+PQpC2m+wIUUZchI6G+QNwi6+qJPXA=; b=luQKDeYkjZUUl81SUf9MvlfWn9neUu78WKNqL/QHVVvrYN/npiHM+A/pNed/bTkBkr US+DL9Klu/5L0BDBNPYPs36ojBkDe2TCI8ElxlUbJTqYEmF8I8rhLUDIH8ep6xX/wlUe rCHpTcqTxDtXxBm5Q0XF5RtHeOcEdIuwFJNS12mhshUd1GVxbvjUIGlWIJ/P62/oEZwU yZe5+gEp1osr/V1t/d6Y5CSz+VTGoRSBeNLV5zvDpWZGTgsNuwOzX73WuvgfkGaNS2DY Vtps4ad9IKRAj70ECAhmJBmJ7p5/VZ0lsxQnMpCm/QGaMLkNuXoGJjP5Rge0vyHXDQLe je8A==
MIME-Version: 1.0
X-Received: by 10.68.129.99 with SMTP id nv3mr4696605pbb.40.1382124178745; Fri, 18 Oct 2013 12:22:58 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 18 Oct 2013 12:22:58 -0700 (PDT)
In-Reply-To: <A14E3A9C-C46E-47DE-A20F-473416B6CA15@bogus.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <CABCOCHSLmDx_-ofQsvrEhJi_A6nbWJRqdYrn6gHOpRaMuEG6XQ@mail.gmail.com> <A14E3A9C-C46E-47DE-A20F-473416B6CA15@bogus.com>
Date: Fri, 18 Oct 2013 20:22:58 +0100
Message-ID: <CADnDZ8994nq74cnMxtYRUmMpHEXfr8-=yZc2dGkv4+_VVAhPag@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ffbab13b5acc704e908dcb1
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Fri, 18 Oct 2013 19:23:02 -0000

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

I support that any assistant to the AD should be assigned and supervised by
that AD, in this way we create experience and may be train a new AD for
future.

The AD is free to assign/delegate tasks to those announced in the area site
or he/she free to do tasks all alone, we may call it AD team or group
(similar to design team work for WG but team has no authority). I always
work thinking that I am assistant to AD and WG within IETF, because we all
share volunteering and team work.

We don't have to name the assistant position as assistant AD, it is the job
what matters which reduces AD time of input, but that assistant should not
have AD authorities or even partial, this way many people will like to do
without responsibility pressure, and gain experience with AD task(s) and
working under AD management/ team.

AB


> On Fri, Oct 18, 2013 at 8:33 AM, Adrian Farrel <adrian@olddog.co.uk<javascript:;>>
> wrote:
> > > I have asked you and other ADs several times if Assistant ADs would
> help.
> > > The answer I got was "not really, but a well run directorate really
> helps.".
> >
> > OK. Doesn't sound like refusing to consider. Sounds like answering your
> > question.
> >
> > So let's take it to the next step because it may be that the current
> IESG cannot
> > conceive of how an assistant AD would work.
> >
> > Can you put up a strawman of the job tasks of an assistant AD that we
> can work
> > with to discuss whether this has legs?
> > Would assistant ADs be appointed and work for sitting ADs, or would they
> be
> > NomCom appointments?
> > Can't an AD already delegate anything they want (except the
> responsibility)?
> >
> > > Why not double the number of ADs in each area and instead of
> > > every AD reviewing every draft, have 2 ADs from each area
> > > review each draft? (Cut the AD hours in half somehow)
> >
> > There is mileage in that. I don't think every AD reviews every document.
> Some
> > pairs of ADs consciously split the load. Some ADs don't do detailed
> reviews of
> > documents in other areas or just focus on specific topics.
> >
> > But we must get off the idea that document review is the whole of the AD
> load. I
> > think it is only around 15-20%. Maybe that rises with pursuit of
> Discusses
> > (moral: don't raise Discusses). That doesn't mean that other parts of
> the load
> > couldn't be shifted.
> >
> > Cheers,
> > Adrian
> >
> >
>
>

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

<div>I support that any assistant to the AD should be assigned and supervis=
ed by that AD, in this way we create experience and may be train a new AD f=
or future.=A0</div><div><br></div><div>The AD is free to assign/delegate=A0=
tasks to those announced in the area site or he/she free to=A0do tasks=A0al=
l alone, we may call it AD team or group (similar to design team work for W=
G but team has no authority). I always work thinking that I am assistant to=
 AD and WG within IETF, because we all share volunteering and team work.</d=
iv>
<div><br></div><div>We don&#39;t have to name the assistant position as ass=
istant AD, it is the job what matters=A0which reduces AD time of input,=A0b=
ut that assistant should not have AD authorities or=A0even partial, this wa=
y many people will like to do without responsibility pressure, and gain exp=
erience with AD task(s) and working under AD management/ team.</div>
<div><br></div><div>AB</div><div><br></div><br><div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
&gt; On Fri, Oct 18, 2013 at 8:33 AM, Adrian Farrel &lt;<a href=3D"javascri=
pt:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;adrian@olddog.co.uk&#39;)">=
adrian@olddog.co.uk</a>&gt; wrote:<br>
&gt; &gt; I have asked you and other ADs several times if Assistant ADs wou=
ld help.<br>
&gt; &gt; The answer I got was &quot;not really, but a well run directorate=
 really helps.&quot;.<br>
&gt;<br>
&gt; OK. Doesn&#39;t sound like refusing to consider. Sounds like answering=
 your<br>
&gt; question.<br>
&gt;<br>
&gt; So let&#39;s take it to the next step because it may be that the curre=
nt IESG cannot<br>
&gt; conceive of how an assistant AD would work.<br>
&gt;<br>
&gt; Can you put up a strawman of the job tasks of an assistant AD that we =
can work<br>
&gt; with to discuss whether this has legs?<br>
&gt; Would assistant ADs be appointed and work for sitting ADs, or would th=
ey be<br>
&gt; NomCom appointments?<br>
&gt; Can&#39;t an AD already delegate anything they want (except the respon=
sibility)?<br>
&gt;<br>
&gt; &gt; Why not double the number of ADs in each area and instead of<br>
&gt; &gt; every AD reviewing every draft, have 2 ADs from each area<br>
&gt; &gt; review each draft? (Cut the AD hours in half somehow)<br>
&gt;<br>
&gt; There is mileage in that. I don&#39;t think every AD reviews every doc=
ument. Some<br>
&gt; pairs of ADs consciously split the load. Some ADs don&#39;t do detaile=
d reviews of<br>
&gt; documents in other areas or just focus on specific topics.<br>
&gt;<br>
&gt; But we must get off the idea that document review is the whole of the =
AD load. I<br>
&gt; think it is only around 15-20%. Maybe that rises with pursuit of Discu=
sses<br>
&gt; (moral: don&#39;t raise Discusses). That doesn&#39;t mean that other p=
arts of the load<br>
&gt; couldn&#39;t be shifted.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Adrian<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div>

--e89a8ffbab13b5acc704e908dcb1--

From mcr@sandelman.ca  Fri Oct 18 12:29:30 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 D41E311E814C for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[AWL=-0.740, BAYES_00=-2.599, NO_DNS_FOR_FROM=1.496]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjiEdKH67MMT for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:29: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 9108211E819E for <ietf@ietf.org>; Fri, 18 Oct 2013 12:29:22 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9327420188 for <ietf@ietf.org>; Fri, 18 Oct 2013 16:39:57 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 12EE063B88; Fri, 18 Oct 2013 15:29:12 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0107763848 for <ietf@ietf.org>; Fri, 18 Oct 2013 15:29:13 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
In-Reply-To: <FB1186A6C0EA33FEE71FF584@JcK-HP8200.jck.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <FB1186A6C0EA33FEE71FF584@JcK-HP8200.jck.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: Fri, 18 Oct 2013 15:29:12 -0400
Message-ID: <6148.1382124552@sandelman.ca>
Sender: 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: Fri, 18 Oct 2013 19:29:30 -0000

--=-=-=


John C Klensin <john-ietf@jck.com> wrote:
    > Or maybe there is an entirely different problem.  I was vastly amused
    > by a recent posting in a different thread that suggested that much of
    > the IETF's leadership started their professional careers around 1987.

I have no scientific data to defend 1987 vs 1980 vs 1970.
I think that this is a reasonable guess at an *average* year.
An average with a nice distribution would have 50% before the average,
and 50% above.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUmGMBoqHRg3pndX9AQLLDgQA1qWEziWdDK1FdxCdvkNG5AHotpAgR8sI
w1od3gTBymEwSz3eVHkqqyuIfsYy++hD94DhVi08WWRIZHK2wxJx1VhPCjnbrELO
XmyPNMuodij4KYcKntdWJd3vcaXGXTM3moSAWcaFle0CyZiKArrciMPdEPrxMeGK
Wa9JV/oEI0g=
=1LdS
-----END PGP SIGNATURE-----
--=-=-=--

From brian.e.carpenter@gmail.com  Fri Oct 18 12:48:09 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 1034011E82B9 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 EVy1x25PTZvv for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 12:48:08 -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 128E911E82A8 for <ietf@ietf.org>; Fri, 18 Oct 2013 12:48:03 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc17so4275282pbc.18 for <ietf@ietf.org>; Fri, 18 Oct 2013 12:47:52 -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=ySK1geffeohhr35ZCMu+Dd6RLpedCNKdHd96HEZUaKs=; b=MgFrGnaTmc2YGW81B1jII0CN5G1JH16yuxejIyDRepetSlZb4llu71qgJqDArsfRDT Udid584MAQUOrKYJQ6f1Q2CaoHhN1r42aYCkXRmOG530hIGM73fi9jtYAxhLpUnyvRGk Y3HcsbOmxNgwsOblDWou68YCy0tGrdLsZIJY3br0VKG17UhS9tt8uSzlpJHtd9wafiZr ZfUlVv8kNDc1s3bUtYsb+yJRoksYxsmEyxOUXu8I82be1f2avZoPmLGjm+wTE0y2FpxB LDfOtprY2uWTuR7rrVEgy7WKnRCYZr1NdmtkRviTMgzY63dgvf60O/Fsf9YXeCsZ65cU N+0Q==
X-Received: by 10.68.232.132 with SMTP id to4mr4572119pbc.141.1382125672600; Fri, 18 Oct 2013 12:47:52 -0700 (PDT)
Received: from [192.168.178.20] (163.199.69.111.dynamic.snap.net.nz. [111.69.199.163]) by mx.google.com with ESMTPSA id xv2sm4106552pbb.39.2013.10.18.12.47.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Oct 2013 12:47:51 -0700 (PDT)
Message-ID: <5261906B.8080303@gmail.com>
Date: Sat, 19 Oct 2013 08:47:55 +1300
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: adrian@olddog.co.uk
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk>	<CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'John C Klensin' <john-ietf@jck.com>, 'IETF Discuss' <ietf@ietf.org>, 'Andy Bierman' <andy@yumaworks.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: Fri, 18 Oct 2013 19:48:09 -0000

On 19/10/2013 04:33, Adrian Farrel wrote:
>> I have asked you and other ADs several times if Assistant ADs would help.
>> The answer I got was "not really, but a well run directorate really helps.".
> 
> OK. Doesn't sound like refusing to consider. Sounds like answering your
> question.
> 
> So let's take it to the next step because it may be that the current IESG cannot
> conceive of how an assistant AD would work.
> 
> Can you put up a strawman of the job tasks of an assistant AD that we can work
> with to discuss whether this has legs? 

This was discussed quite a bit within the IESG in ~2005 and there was some
discussion of Assistant Area Managers in ~2003. In practice, the result
was the strengthening of various directorates and review teams.

> Would assistant ADs be appointed and work for sitting ADs, or would they be
> NomCom appointments?

Definitely not NomCom, for a whole raft of reasons.

> Can't an AD already delegate anything they want (except the responsibility)?

Yes. Just try to find a willing assistant. We'll be looking in the same
pool as we do for WG Chairs and ADs, so it can't just be a matter of
delegating scut work.

>> Why not double the number of ADs in each area and instead of
>> every AD reviewing every draft, have 2 ADs from each area
>> review each draft? (Cut the AD hours in half somehow)
> 
> There is mileage in that. 

I don't think so. Adding ADs was another approach we discussed
in the 2005/7 timeframe. The problem is that it's hard enough to keep
a 15 member IESG cohesive. I can't imagine how a 29 member IESG
would "steer" anything. Frankly, I think you'd get squabbling.
(As Scott Brim said, we need a strategy. You won't get that from a
group of 29 people.)

> I don't think every AD reviews every document. Some
> pairs of ADs consciously split the load. Some ADs don't do detailed reviews of
> documents in other areas or just focus on specific topics.
> 
> But we must get off the idea that document review is the whole of the AD load. I
> think it is only around 15-20%. Maybe that rises with pursuit of Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of the load
> couldn't be shifted.

Reviewing *in itself* may or may not be the dominant load, but it
generates other work, such as arbitration between the reviewing AD
and the authors - which is definitely not always undertaken by the
shepherd. That's why pushing reviewing back to the WG would tend to
reduce the IESG's overall workload (IMNSHO).

I rather like Brian Trammell's suggestion to formalise the reviewer
role more and to improve the tools. If I was an AD today, I'd be delighted
if the tracker pointed me to various reviews (and the author's
responses).

   Brian

From andy@yumaworks.com  Fri Oct 18 13:57:34 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 7AD5811E8330 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 13:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.817
X-Spam-Level: 
X-Spam-Status: No, score=-2.817 tagged_above=-999 required=5 tests=[AWL=0.159,  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 p44ycg0HAOZ5 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 13:57:29 -0700 (PDT)
Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2F00711E80E3 for <ietf@ietf.org>; Fri, 18 Oct 2013 13:57:29 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id w7so2286239qeb.39 for <ietf@ietf.org>; Fri, 18 Oct 2013 13:57:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ALZUlX3ByGnmXLRgEjEpdcLssRoajcW8mrp1UYIRqjg=; b=EPT+t85N6WkWLQSu0PwvVxwn3hO7iRZOg/aJmtKBBM7281aYVo8h9YPm6ydRJVpM12 OAM6bOT0FXYTr366mZY4FVRFRtlLFrdEPsoWBZSaZhcfmrk91aoS873T7diY2SSZjssR aK+OEN1NCVS5z5SVWPucyBJsMBzlo3/aef6A6P3k6zf5yzoLZDh3cMcgJDLRRtPPSdbY AnMrwu+z5fDn1rN4MY3tColh0atKATTxWT9WhhG0HCMqHgacDmF+E5Em5EvAMYhUP5Oj AjLKLSnKo6rFRf5zKYsUv7WehcicJ2kmTedrgLFxKxX+mv/Fdqz8XArJCMfbHfA5MFJI 8+zg==
X-Gm-Message-State: ALoCoQm8+y1fuMQ0Zrvg4ntkti2smrKGTUN8+xAwADzEzxm7jo3cjiALcnDH0k3VtaIv95Ss1A3p
MIME-Version: 1.0
X-Received: by 10.224.169.8 with SMTP id w8mr7380611qay.96.1382129839765; Fri, 18 Oct 2013 13:57:19 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Fri, 18 Oct 2013 13:57:19 -0700 (PDT)
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
Date: Fri, 18 Oct 2013 13:57:19 -0700
Message-ID: <CABCOCHTM7Gv3c4yEFSvG7NTt5FOvRmUhgs71Nfj3YwOJXmkSFA@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Andy Bierman <andy@yumaworks.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=089e01494f4822082604e90a2eb3
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 20:57:34 -0000

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

Hi,

...

But we must get off the idea that document review is the whole of the AD
> load. I
> think it is only around 15-20%. Maybe that rises with pursuit of Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of the
> load
> couldn't be shifted.
>
>
I meant to add that the number of WGs managed would be cut in
half too -- that seems easier than splitting reviews. The number of ADs
has not really scaled to the number of WGs in recent years. I would
rather try adding ADs than shutting down WGs.

IMO it is an implementation detail how the IETG divides its work.
I agree with Brian that just delegating the undesrable work
to an assistant volunteer is not a real plan.  But if NOMCOM thinks there
is a critical shortage of IESG candidates, then the IESG better fix it,
or perhaps the NOMCOM should mandate a solution.


Cheers,
> Adrian
>
>
Andy

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

<div dir=3D"ltr">Hi,<div><br></div><div>...</div><div><br><div class=3D"gma=
il_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But we must get off the idea that document review is the whole of the AD lo=
ad. I<br>
think it is only around 15-20%. Maybe that rises with pursuit of Discusses<=
br>
(moral: don&#39;t raise Discusses). That doesn&#39;t mean that other parts =
of the load<br>
couldn&#39;t be shifted.<br>
<br></blockquote><div><br></div><div>I meant to add that the number of WGs =
managed would be cut in</div><div>half too -- that seems easier than splitt=
ing reviews. The number of ADs</div><div>has not really scaled to the numbe=
r of WGs in recent years. I would</div>
<div>rather try adding ADs than shutting down WGs.</div><div><br></div><div=
>IMO it is an implementation detail how the IETG divides its work.</div><di=
v>I agree with Brian that just delegating the undesrable work</div><div>
to an assistant volunteer is not a real plan. =A0But if NOMCOM thinks there=
</div><div>is a critical shortage of IESG candidates, then the IESG better =
fix it,</div><div>or perhaps the NOMCOM should mandate a solution.</div><di=
v>
<br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
Adrian<br>
<br>
</blockquote></div><br></div></div><div class=3D"gmail_extra">Andy</div><di=
v class=3D"gmail_extra"><br></div></div>

--089e01494f4822082604e90a2eb3--

From brian.e.carpenter@gmail.com  Fri Oct 18 15:47:59 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 A4B8A21F9C6C for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 15:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 K7GKvy4gBRLq for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 15:47:59 -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 0D4B221F9C6B for <ietf@ietf.org>; Fri, 18 Oct 2013 15:47:58 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so5202200pad.5 for <ietf@ietf.org>; Fri, 18 Oct 2013 15:47:56 -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=oNyWhu3Mobh2jShjjssh3g3D7MYPxc6PzWVKrtARrYs=; b=M/AOY8kFBQut51+Ur0qgVAYyD2jZgrUl5eh5X6+ZUtjJG/gMZpFvHIepZIx4UmDj7A 6ygcDGRxKnrDdaEKnt3v9oEopy0h7fOzDhGqc4odfrYcR92fX60HNSyl13idyi+emnfj M7q4T5b95YX2vpFRbB3cwp2xrAqm18C1+kXYIfCsfGzJ+aSdxRPTWWqkPW9auUhasSc8 sGurWZCYDVcNHQIWNkZdFQWU0l9o3v2hHkvbucIAZvHS8aMiF/G9X1NZChzuBKBV0YKD Po5KonfO7EnBLIR08of8lyUdvheiEtihZX/Uqg6xCQ0zd8FRncCUaYaoKbrJ+cb+z71L t9Ag==
X-Received: by 10.69.0.228 with SMTP id bb4mr5294209pbd.66.1382136476631; Fri, 18 Oct 2013 15:47:56 -0700 (PDT)
Received: from [192.168.178.20] (163.199.69.111.dynamic.snap.net.nz. [111.69.199.163]) by mx.google.com with ESMTPSA id qn1sm4663474pbc.34.2013.10.18.15.47.54 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Oct 2013 15:47:55 -0700 (PDT)
Message-ID: <5261BAA6.7090603@gmail.com>
Date: Sat, 19 Oct 2013 11:48:06 +1300
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 Discuss' <ietf@ietf.org>
Subject: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk>	<CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
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, 18 Oct 2013 22:47:59 -0000

I just rooted out a graph of IESG size over a number of years
that I created for a similar discussion 7 years ago.
As far as I know, today's numbers are identical to 2006, since
no Areas have been created or deleted and we have two ADs/Area.

http://www.cs.auckland.ac.nz/~brian/IESGsize.pdf

At that time about 125 WGs were chartered. Today we still have
about 125 WGs.

Regards
   Brian

From andy@yumaworks.com  Fri Oct 18 15:59: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 9D2B011E80E7 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 15:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.822
X-Spam-Level: 
X-Spam-Status: No, score=-2.822 tagged_above=-999 required=5 tests=[AWL=0.154,  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 Y2wZYn0eBkgf for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 15:59:22 -0700 (PDT)
Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by ietfa.amsl.com (Postfix) with ESMTP id 68E4711E80EA for <ietf@ietf.org>; Fri, 18 Oct 2013 15:59:21 -0700 (PDT)
Received: by mail-qe0-f46.google.com with SMTP id s14so2351414qeb.19 for <ietf@ietf.org>; Fri, 18 Oct 2013 15:59:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qdKQheJDVOgjvrtRYz8/kicdIWaTY4/o9aBIO5x/hio=; b=HZ8u7N4BUdDZ6JNrge0SS9e439UGNR81aMb0OQX8/whuo9myjnzS7c6fj7BEIdiUKh 8zdN4c4opURROYk039PVnfhsUs6i929h43uhj/x3V/UT2cMRdxlDgj4Fh6ms9nxnm/YZ yEDhDBPYgmNvhWEXM01BgC+FZVTdMc+22Inp0RKC7ufwE7q+FcmuB/yzqLjkaUlKhozp AKLVZjkg46DTCA3HDeo5KSCT/UcXbRPsOcyDWUyqTSJ3CXbbYyNynUHo8wfnOHtIkGQb BcZQO5yT0Yyijevj2L9KwSEcN+DnO22W0cTE1z5isJ+OyfnQcYrpc3IGFlaLElTfuWwH crtA==
X-Gm-Message-State: ALoCoQmxVWNdxr0Z7CUUlQr/cM8VDJbpiSGJLSsyHn/wTlo+2viLoYFxB6/MpundZ5tSY5BVirXA
MIME-Version: 1.0
X-Received: by 10.49.96.225 with SMTP id dv1mr7243082qeb.89.1382137160918; Fri, 18 Oct 2013 15:59:20 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Fri, 18 Oct 2013 15:59:20 -0700 (PDT)
In-Reply-To: <5261BAA6.7090603@gmail.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com>
Date: Fri, 18 Oct 2013 15:59:20 -0700
Message-ID: <CABCOCHTa9oG0C6tp_AuG=5ONSvnx_oJrH1Rq2vF8+uUbTVLZZw@mail.gmail.com>
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
From: Andy Bierman <andy@yumaworks.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bb0494681f8f304e90be2f2
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Oct 2013 22:59:26 -0000

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

On Fri, Oct 18, 2013 at 3:48 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> I just rooted out a graph of IESG size over a number of years
> that I created for a similar discussion 7 years ago.
> As far as I know, today's numbers are identical to 2006, since
> no Areas have been created or deleted and we have two ADs/Area.
>
> http://www.cs.auckland.ac.nz/~brian/IESGsize.pdf
>
> At that time about 125 WGs were chartered. Today we still have
> about 125 WGs.
>
>
Hmm,  very interesting data.  So perhaps there is
no process problem at all. Perhaps economic conditions
are just reducing the candidate pool.

What if project and WG management administrative tasks
could be off-loaded to paid assistants? There must be some
tasks done by ADs that can be delegated or assisted.  The IETF
pays for RFC Editor services.  Perhaps professional project management
services would help (a ton!)


Regards
>    Brian
>


Andy

--047d7bb0494681f8f304e90be2f2
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 Fri, Oct 18, 2013 at 3:48 PM, Brian E Carpenter <span dir=3D"ltr=
">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">bria=
n.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">I just rooted out a graph of IESG size over =
a number of years<br>
that I created for a similar discussion 7 years ago.<br>
As far as I know, today&#39;s numbers are identical to 2006, since<br>
no Areas have been created or deleted and we have two ADs/Area.<br>
<br>
<a href=3D"http://www.cs.auckland.ac.nz/~brian/IESGsize.pdf" target=3D"_bla=
nk">http://www.cs.auckland.ac.nz/~brian/IESGsize.pdf</a><br>
<br>
At that time about 125 WGs were chartered. Today we still have<br>
about 125 WGs.<br>
<br></blockquote><div><br></div><div>Hmm, =A0very interesting data. =A0So p=
erhaps there is</div><div>no process problem at all. Perhaps economic condi=
tions</div><div>are just reducing the candidate pool.</div><div><br></div>
<div>What if project and WG management administrative tasks</div><div>could=
 be off-loaded to paid assistants? There must be some</div><div>tasks done =
by ADs that can be delegated or assisted. =A0The IETF</div><div>pays for RF=
C Editor services. =A0Perhaps professional project management</div>
<div>services would help (a ton!)</div><div><br></div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">=A0 =A0Brian<br>
</font></span></blockquote></div><br></div><div class=3D"gmail_extra"><br><=
/div><div class=3D"gmail_extra">Andy</div><div class=3D"gmail_extra"><br></=
div></div>

--047d7bb0494681f8f304e90be2f2--

From randy_presuhn@mindspring.com  Fri Oct 18 17:27:10 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 2F78C21F9C52 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 17:27: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 QG5zNzK2HTWr for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 17:27:04 -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 2F85121F9BD5 for <ietf@ietf.org>; Fri, 18 Oct 2013 17:27:03 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=PlO3PXSIZ5bcJOBmHiPzLPyPlGN6aSEXYTciU1xkFl1rE4Ur6r6KNCL6GV6AjRAB; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.49.146] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1VXKNi-0007OH-U5 for ietf@ietf.org; Fri, 18 Oct 2013 20:27:03 -0400
Message-ID: <000a01cecc62$55457640$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "'IETF Discuss'" <ietf@ietf.org>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk>	<CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com><067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com>
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
Date: Fri, 18 Oct 2013 17:29:53 -0700
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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edb7564dc19b17279bdb4b48a1a37312f7e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.49.146
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 00:27:10 -0000

Hi -

> From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> To: "'IETF Discuss'" <ietf@ietf.org>
> Sent: Friday, October 18, 2013 3:48 PM
> Subject: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
>
> I just rooted out a graph of IESG size over a number of years
> that I created for a similar discussion 7 years ago.
> As far as I know, today's numbers are identical to 2006, since
> no Areas have been created or deleted and we have two ADs/Area.
...

I wonder whether in this discussion we've been neglecting
a significant aspect of how the workload has changed.  In
reviewing and DISCUSSing work, the ADs (and directorates)
need to take into account a corpus of work (not just RFCs)
which grows ever larger.  For example, a MIB review seems
to be a lot more work now than it was twenty years ago, in
large part because there is a much larger body of established
practice to be checked for potential conflicts.

If indeed a large time sink is the time needed to DISCUSS
work, increasing the size of the IESG won't help.  Having
multiple IESGs might give better scalability.  Even splitting
the current IESG into two (one AD from each area into each
IESG) might provide better parallelism.  Of course, doing
this would require us to finally disabuse ourselves of any
notions that "the" IESG really understands everything or is
in total control of anything.

Just a thought.

Randy


From loa@pi.nu  Fri Oct 18 20:10:51 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 30E4311E8136 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 20:10: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 YYMXIBQ64IGb for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 20:10:45 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9811A11E814D for <ietf@ietf.org>; Fri, 18 Oct 2013 20:10:42 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 B3E7E1802039; Sat, 19 Oct 2013 05:10:40 +0200 (CEST)
Message-ID: <5261F82E.7030800@pi.nu>
Date: Sat, 19 Oct 2013 11:10:38 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, ietf <ietf@ietf.org>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>
In-Reply-To: <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.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: Sat, 19 Oct 2013 03:10:51 -0000

Ted,


On 2013-10-18 23:10, Ted Lemon wrote:
> The most useful comment I've heard on this thread is that it makes sense to credit the working group chairs as well as the authors of a document in the document at the same level of emphasis.   And possibly the ADs as well.   I don't know if this would make a difference, but it's interesting, and might be worth the experiment.

Would this be an implementation of what you say (example built on
one of our recent RFCs)

Internet Engineering Task Force (IETF)                           M. Chen
Request for Comments: 6829                  Huawei Technologies Co., Ltd
Updates: 4379                                                     P. Pan
Category: Standards Track                                       Infinera
ISSN: 2070-1721                                             C. Pignataro
Responsible AD: A. Farrel, Juniper                              R. Asati
WG Chair/Shepherd: L. Andersson, Huawei                            Cisco
                                                             January 2013

                    Label Switched Path (LSP) Ping for
  Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6

Note: This is not a suggestion, just a question for clarification. And
if we want to do it "this way" it is not a layout proposal. If we do it
like this we would have a second level effect in capturing the
shepeherds, wg chairs and responsible ADs addresses in separate section
following the Authors Addresses.

/Loa


>
> But really, the main thing to say about this conversation is that it's a classic example of why the AD's job is so time consuming.   We have to monitor these conversations, because otherwise we aren't doing the part of our job that involves listening to the IETF.   Having long bikeshed discussions about the woeful brokenness of the AD's job over and over again without any action proposed is expensive.
>
> Most of what's been discussed here has been discussed by the ADs during the recent IESG retreat, and substantial action was taken as a result of the discussion at that retreat.   It might be interesting to see if any of what we discussed actually changes anything.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From loa@pi.nu  Fri Oct 18 20:20:05 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 A23A611E8141 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 20:20: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 e5GBRA59rlWm for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 20:19:59 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id B27B511E8140 for <ietf@ietf.org>; Fri, 18 Oct 2013 20:19:57 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 CCD4B1802039; Sat, 19 Oct 2013 05:19:55 +0200 (CEST)
Message-ID: <5261FA59.30009@pi.nu>
Date: Sat, 19 Oct 2013 11:19:53 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.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: Sat, 19 Oct 2013 03:20:05 -0000

Folks,

I should probably keep my mouth shat about this :) ! Looking tot he RTG
area don't we have an Assistant AD, only that we call it the
RTG Directorate Chair? A very proper place to delegate work and assign
responsibility.

/Loa

On 2013-10-18 23:33, Adrian Farrel wrote:
>> I have asked you and other ADs several times if Assistant ADs would help.
>> The answer I got was "not really, but a well run directorate really helps.".
>
> OK. Doesn't sound like refusing to consider. Sounds like answering your
> question.
>
> So let's take it to the next step because it may be that the current IESG cannot
> conceive of how an assistant AD would work.
>
> Can you put up a strawman of the job tasks of an assistant AD that we can work
> with to discuss whether this has legs?
> Would assistant ADs be appointed and work for sitting ADs, or would they be
> NomCom appointments?
> Can't an AD already delegate anything they want (except the responsibility)?
>
>> Why not double the number of ADs in each area and instead of
>> every AD reviewing every draft, have 2 ADs from each area
>> review each draft? (Cut the AD hours in half somehow)
>
> There is mileage in that. I don't think every AD reviews every document. Some
> pairs of ADs consciously split the load. Some ADs don't do detailed reviews of
> documents in other areas or just focus on specific topics.
>
> But we must get off the idea that document review is the whole of the AD load. I
> think it is only around 15-20%. Maybe that rises with pursuit of Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of the load
> couldn't be shifted.
>
> Cheers,
> Adrian
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From Ted.Lemon@nominum.com  Fri Oct 18 21:07:57 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 12EC411E8162 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 28wyvrhCh0M2 for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:07:50 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 72D8311E8159 for <ietf@ietf.org>; Fri, 18 Oct 2013 21:07:50 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUmIFlqXQXeoXtsimjZC8PFYn9jrpI//8@postini.com; Fri, 18 Oct 2013 21:07:50 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 04BA41B82C6 for <ietf@ietf.org>; Fri, 18 Oct 2013 21:07:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 D912A190060; Fri, 18 Oct 2013 21:07:49 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 21:07:49 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CABCOCHTa9oG0C6tp_AuG=5ONSvnx_oJrH1Rq2vF8+uUbTVLZZw@mail.gmail.com>
Date: Sat, 19 Oct 2013 00:07:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F31C975B-B9EE-448F-9418-B512CA30E3DB@nominum.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com> <CABCOCHTa9oG0C6tp_AuG=5ONSvnx_oJrH1Rq2vF8+uUbTVLZZw@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 04:07:57 -0000

On Oct 18, 2013, at 6:59 PM, Andy Bierman <andy@yumaworks.com> wrote:
> There must be some
> tasks done by ADs that can be delegated or assisted.  The IETF
> pays for RFC Editor services.  Perhaps professional project management
> services would help (a ton!)

Having a skilled personal secretary would make my life a lot easier, but =
in principle the things I'd want that person to do are things that we're =
asking document shepherds to do.   They just aren't generally doing =
them.



From Ted.Lemon@nominum.com  Fri Oct 18 21:17:10 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 67ED911E816B for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 t0MtoEPY9OEg for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:16:54 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id CDDB611E814F for <ietf@ietf.org>; Fri, 18 Oct 2013 21:16:54 -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 DSNKUmIHtm6MGUB9TJV9TGY5WtAg7SPHpky/@postini.com; Fri, 18 Oct 2013 21:16:54 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 58AFB1B82C3 for <ietf@ietf.org>; Fri, 18 Oct 2013 21:16:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 524F1190060; Fri, 18 Oct 2013 21:16:54 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 21:16:54 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5261F82E.7030800@pi.nu>
Date: Sat, 19 Oct 2013 00:16:49 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <5261F82E.7030800@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
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, 19 Oct 2013 04:17:10 -0000

On Oct 18, 2013, at 11:10 PM, Loa Andersson <loa@pi.nu> wrote:
> Would this be an implementation of what you say (example built on
> one of our recent RFCs)
> 
> Internet Engineering Task Force (IETF)                           M. Chen
> Request for Comments: 6829                  Huawei Technologies Co., Ltd
> Updates: 4379                                                     P. Pan
> Category: Standards Track                                       Infinera
> ISSN: 2070-1721                                             C. Pignataro
> Responsible AD: A. Farrel, Juniper                              R. Asati
> WG Chair/Shepherd: L. Andersson, Huawei                            Cisco

Something like that, yes.


From Ted.Lemon@nominum.com  Fri Oct 18 21:24: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 B5E9211E814F for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 uxMQ34cpUgfM for <ietf@ietfa.amsl.com>; Fri, 18 Oct 2013 21:23:56 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 78FFB11E8167 for <ietf@ietf.org>; Fri, 18 Oct 2013 21:23:52 -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 DSNKUmIJWF+EhmWIIVZ3qeyKTo9JnEvGQswa@postini.com; Fri, 18 Oct 2013 21:23:52 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 D8C561B82C3 for <ietf@ietf.org>; Fri, 18 Oct 2013 21:23:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 D2586190060; Fri, 18 Oct 2013 21:23:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 18 Oct 2013 21:23:51 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F31C975B-B9EE-448F-9418-B512CA30E3DB@nominum.com>
Date: Sat, 19 Oct 2013 00:23:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <94D32E51-BEDC-4F4C-83A9-722D87A81F20@nominum.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com> <CABCOCHTa9oG0C6tp_AuG=5ONSvnx_oJrH1Rq2vF8+uUbTVLZZw@mail.gmail.com> <F31C975B-B9EE-448F-9418-B512CA30E3DB@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 04:24:02 -0000

On Oct 19, 2013, at 12:07 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> Having a skilled personal secretary would make my life a lot easier, =
but in principle the things I'd want that person to do are things that =
we're asking document shepherds to do.   They just aren't generally =
doing them.

(To be clear, this has more to do with me not having gotten my act =
together to formally ask them to do these things than that they have =
been shirking=97sorry to any of my document shepherds who may have read =
this and felt ill done by!)


From john-ietf@jck.com  Sat Oct 19 00:39: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 E3F9611E8179 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 00:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.588
X-Spam-Level: 
X-Spam-Status: No, score=-103.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 NjoRNgSlOv2W for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 00:39:51 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 51E9C21F9DF3 for <ietf@ietf.org>; Sat, 19 Oct 2013 00:39: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 1VXR8X-0006Df-VM; Sat, 19 Oct 2013 03:39:49 -0400
Date: Sat, 19 Oct 2013 03:39:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, 'IETF Discuss' <ietf@ietf.org>
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
Message-ID: <B6CA7B6510D7C4AAE58C849E@JcK-HP8200.jck.com>
In-Reply-To: <000a01cecc62$55457640$6b01a8c0@oemcomputer>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com> <000a01cecc62$55457640$6b01a8c0@oemcomputer>
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: Sat, 19 Oct 2013 07:39:59 -0000

--On Friday, October 18, 2013 17:29 -0700 Randy Presuhn
<randy_presuhn@mindspring.com> wrote:

>...
> If indeed a large time sink is the time needed to DISCUSS
> work, increasing the size of the IESG won't help.  Having
> multiple IESGs might give better scalability.  Even splitting
> the current IESG into two (one AD from each area into each
> IESG) might provide better parallelism.  Of course, doing
> this would require us to finally disabuse ourselves of any
> notions that "the" IESG really understands everything or is
> in total control of anything.

Whether on this hypothesis or most others, it seems to me that
splitting up the IESG horizontally (each Area represented in
each IETF) or vertically (half the Areas to one, half to the
other), with or without a significant increase in the number of
total IESG members, would almost certainly create several new
problems (some of these have been mentioned by others):

* The ability for the IESG to work as a team (and, fwiw, to be
held accountable as a team) would be much reduced.  For that
purpose, the IESG is probably very close to the maximum size.
Doubling it would fundamentally change the nature of the
process, with or without horizontal or vertical splits.  As two
obvious examples, its size is probably already above the maximum
for real conversations with the community in plenaries. Now
imagine something over 32 people on the stage in a plenary and,
if there were either split, figure out whether we need one IESG
Chair or two, which IESG the IAB Chair participates in, and so
on.  Or perhaps we should have three plenaries instead of two?

* Cross-area review would probably be weakened. It is rare for
even two ADs in an Area to have the same perspectives and
knowledge.  When they do, it is, IMO, a failure elsewhere in the
system -- diversity of perspectives, even within an Area, is a
strength.  A vertical split would mean little contact between
top and bottom layer ADs and some "interesting" questions about
what to do about, e.g., Security.

* A horizontal split would make ADs in an Area filling in for
each other in the event of illness or overload and moving WGs
back and forth to compensate for changes in load much more
difficult.  

* Any split (or even a significant growth in size) would create
(or enhance) a management nightmare around the issues that the
IESG really needs to reach agreement on as a group.  We probably
don't want different review or "voting" policies based on
semi-random decisions about where a WG or Area falls.  The issue
of what to do about Chairs and Liaisons is mentioned above.

In addition, shifting more review burden and responsibility to
directorates, etc., rather that having those reviews be advisory
to relevant ADs about issues to which they need to pay special
attention blows up accountability because decision-making
authority would effectively shift from people selected by the
Nomcom to self-selected community members.  That could easily
lead to more appeals (appeals are usually an incredibly
time-consuming process) or having the IETF in a very difficult
position if there were ever a claim of impropriety in the
decision-making about at standard.

If a split is wanted, there is another way to do it, one that
would introduce a different set of new or more complex issues
than the above and address the scaling problem differently.  See
https://datatracker.ietf.org/doc/draft-klensin-stds-review-panel/
for an example of one such proposal.  Disclaimer: I haven't
looked at that document in years and don't know whether I would
still support it,

best,
    john






From abdussalambaryun@gmail.com  Sat Oct 19 01:01: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 328CF21F8424 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 01:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.519
X-Spam-Level: 
X-Spam-Status: No, score=-2.519 tagged_above=-999 required=5 tests=[AWL=0.081,  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 UeKSjOm6Z9Hp for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 01:01:50 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE0411E8136 for <ietf@ietf.org>; Sat, 19 Oct 2013 01:01:47 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id y13so5864286pdi.12 for <ietf@ietf.org>; Sat, 19 Oct 2013 01:01: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=i7zYxdb4Z2Obx+JkzGN5o34Lr/2ZoMESQsIxllXcedc=; b=MVm8g3wxkvCmbcjWDbDGmoOiVV5xLt+/2HrGuJe+yNuEG614+UtcLOcgnPhKLMP/dx z2VnWfLu13j1PYi1cWPrLRTPIFqVUOVE0BjB4e3aO3HNGckITztkx3eZI9uJVlc+WDtx mNBXkLIWw9wEz01faSBmy1vJW2X0JljgabKL9nwl+54o5bVbQptT4qzghrKw7cMhB9vI sxV8S2qYqhAINVbzeEd2fpZqNey2pndwcveWnwfmERgVkWESPvMu79SoECe53zEiNsFd I4+PZXbKA+0GeZaQm0MPwJB3UothcRvGBuZaltawe55zIZSnwJ9444CjocF6YZV3l4xv n/sQ==
MIME-Version: 1.0
X-Received: by 10.68.225.164 with SMTP id rl4mr7192892pbc.100.1382169707690; Sat, 19 Oct 2013 01:01:47 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sat, 19 Oct 2013 01:01:47 -0700 (PDT)
In-Reply-To: <5261BAA6.7090603@gmail.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <5261BAA6.7090603@gmail.com>
Date: Sat, 19 Oct 2013 10:01:47 +0200
Message-ID: <CADnDZ89kFd78YehXS6NZEJRZz+NnpNZN5-MBqtDxQJVMK4LvhA@mail.gmail.com>
Subject: Re: Size of IESG, Number of Areas (Was: CHANGE THE JOB)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 08:01:51 -0000

Thanks for this important graph information (it should be listed in
one of the IETF web pages), I think it should be documented in a I-D
for General Area works, still our IETF General Area outputs is weak in
my opinion which makes our/my decisions/ideas not final of what
happend and what should happen, I would blame management of not
encouraging WGs in the General Area for this problem.

However, IMHO, the number of WGs is not the important cause of problem
for AD, it is the WGs' behavior, performance, re-chartering,
milestones/output (i.e. are they in the authorised milestones) and
management, that makes the larger input-time problem for any AD or
even any IETF participant. Some IETF WGs still need more efficiency to
do their job independently on time.

AB

On 10/19/13, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> I just rooted out a graph of IESG size over a number of years
> that I created for a similar discussion 7 years ago.
> As far as I know, today's numbers are identical to 2006, since
> no Areas have been created or deleted and we have two ADs/Area.
>
> http://www.cs.auckland.ac.nz/~brian/IESGsize.pdf
>
> At that time about 125 WGs were chartered. Today we still have
> about 125 WGs.
>
> Regards
>    Brian
>

From john-ietf@jck.com  Sat Oct 19 01:37:49 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 AEEF711E818D for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 01:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.589
X-Spam-Level: 
X-Spam-Status: No, score=-103.589 tagged_above=-999 required=5 tests=[AWL=0.010, 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 8t7iaUl-sXW7 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 01:37:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 71A7211E8189 for <ietf@ietf.org>; Sat, 19 Oct 2013 01:37: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 1VXS2R-0006Hf-Nd; Sat, 19 Oct 2013 04:37:35 -0400
Date: Sat, 19 Oct 2013 04:37:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andy Bierman <andy@yumaworks.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Message-ID: <EBBFDF12F62597328F94BF95@JcK-HP8200.jck.com>
In-Reply-To: <CABCOCHTM7Gv3c4yEFSvG7NTt5FOvRmUhgs71Nfj3YwOJXmkSFA@mail.gmail.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <CABCOCHTM7Gv3c4yEFSvG7NTt5FOvRmUhgs71Nfj3YwOJXmkSFA@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: Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 08:37:49 -0000

--On Friday, October 18, 2013 13:57 -0700 Andy Bierman
<andy@yumaworks.com> wrote:

>...
> IMO it is an implementation detail how the IETG divides its
> work. I agree with Brian that just delegating the undesrable
> work to an assistant volunteer is not a real plan.  But if
> NOMCOM thinks there is a critical shortage of IESG candidates,
> then the IESG better fix it, or perhaps the NOMCOM should
> mandate a solution.

In practical terms, I don't understand this paragraph.  You have
suggested increasing the number of ADs.  But, if there were a
critical shortage of IESG candidates (and it is clear that has
been the case in some areas in the recent past), then increasing
the number of slots to be filled can't solve that problem
(indeed can only make it worse), even if it held out the
possibility of a lower workload in the long run.   I'd also like
to understand what solutions you propose the Nomcom might
"mandate" and how.  As far as I can tell, they can do only three
things.  Of those, the second is unclear because it has been
much-discussed, never actually attempted, and whether or not it
is possible depends on interpretations of an edge case in the
relevant procedures.

	(1) Fill a position.  In theory and in the absence of
	other candidates, they could fill a position with a dead
	body or someone's pet rock, but I assume the IAB would
	find those candidates unqualified.
	
	(2) Decide to not fill a position.  Whatever that would
	accomplish, it would _increase_ the workload on the
	surviving AD in the area (if any) and/or paralyze the
	area.   I assume the Transport area got an adequate
	preview of that effect earlier this year.
	
	(3) Make recommendations that might or might not be
	acted on and that certainly cannot affect the current
	year's slots or candidates.

So what would you propose they "mandate" and how?

    john




From tjc@ecs.soton.ac.uk  Sat Oct 19 04:19:28 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 8216A21F9E95 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:19: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 4TpvzWLN28G7 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:19:27 -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 3050911E80E7 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:19:26 -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 r9JBJOQY011566 for <ietf@ietf.org>; Sat, 19 Oct 2013 12:19:24 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9JBJOQY011566
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382181565; bh=B8790nk+BLGCWPS8DHanYtkqXD8=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=S66DAeyex43OCzUFaqyVwEIjiyBTIXzpSzJBzuVKJfAOiYx2yJ0nTtCh+aqCoJlzQ /RtMGv0JsOFwe8xvCG2YAO0RJH3Vszf5yWFpmgAuvegcNiXUyxOdJWAyUaN4JEDrWR jjxNPDe/Y/4lAV5YAtvAU8I8NSFUIeO8ar1aMY1I=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9ICJO09596570838v ret-id none; Sat, 19 Oct 2013 12:19:24 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9JBJKcR000792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 19 Oct 2013 12:19:21 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>
Date: Sat, 19 Oct 2013 12:19:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <5261F82E.7030800@pi.nu> <B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com> <1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>
To: IETF Discuss <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9ICJO095965708300; tid=p9ICJO09596570838v; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9JBJOQY011566
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: Sat, 19 Oct 2013 11:19:28 -0000

On 19 Oct 2013, at 05:16, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Oct 18, 2013, at 11:10 PM, Loa Andersson <loa@pi.nu> wrote:
>> Would this be an implementation of what you say (example built on
>> one of our recent RFCs)
>>=20
>> Internet Engineering Task Force (IETF)                           M. =
Chen
>> Request for Comments: 6829                  Huawei Technologies Co., =
Ltd
>> Updates: 4379                                                     P. =
Pan
>> Category: Standards Track                                       =
Infinera
>> ISSN: 2070-1721                                             C. =
Pignataro
>> Responsible AD: A. Farrel, Juniper                              R. =
Asati
>> WG Chair/Shepherd: L. Andersson, Huawei                            =
Cisco
>=20
> Something like that, yes.

Worth considering, perhaps as part of improving access to the provenance =
of RFCs in general.  The tools area is great for tracing back the =
evolutuion of the document, for example.

Tim


From andy@yumaworks.com  Sat Oct 19 04:27:35 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 D18D611E81B2 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.829
X-Spam-Level: 
X-Spam-Status: No, score=-2.829 tagged_above=-999 required=5 tests=[AWL=0.147,  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 Pssim1ayJWO1 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:27:30 -0700 (PDT)
Received: from mail-qc0-f178.google.com (mail-qc0-f178.google.com [209.85.216.178]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF6211E81A7 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:27:29 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id x19so3377506qcw.9 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:27:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=1KzHL4ohztyDYO28Dg9pWKiLXA3lbyjG9L5FORodMjI=; b=GgfAmnR8KinU3x49wixgNywtmtRGQnBJ9+Wek2KeL2obIwRUICn1tbWTCEyL6i5qLA Ln/YlFqdA7ZhpZky+o4e4Chjn4ikDMJi/nuKIrbf15lOZCe9/apUHxXfeu453IjNOlry g5/cH+jEsq0rQ41lr8wyrRqEIE7pMdx2gYTwjuBOwey80ZA3jsqBzpg+JsBy7z41UNc7 654R5GM67627K/SF70wL7EvUFKCL/3Ducz+iUx5wCfE8cGtdV2h+pr+xzyGDeJlQ39+K X3/HoXUNLyF25ffywTP7u0ldSNW52JE6BDRrOLPREIj4b3oobYHcFZfi1xzIRNGX6IH+ YX7g==
X-Gm-Message-State: ALoCoQnpt4lbQdPVxaDfZTDwF2+6WOjrC0vyVXWpND/sLB84V5kZrMLtfsY1n3Wj7AnvbgE0Oqb2
MIME-Version: 1.0
X-Received: by 10.49.50.7 with SMTP id y7mr9989199qen.45.1382182048703; Sat, 19 Oct 2013 04:27:28 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Sat, 19 Oct 2013 04:27:28 -0700 (PDT)
In-Reply-To: <EBBFDF12F62597328F94BF95@JcK-HP8200.jck.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <CABCOCHTM7Gv3c4yEFSvG7NTt5FOvRmUhgs71Nfj3YwOJXmkSFA@mail.gmail.com> <EBBFDF12F62597328F94BF95@JcK-HP8200.jck.com>
Date: Sat, 19 Oct 2013 04:27:28 -0700
Message-ID: <CABCOCHT-mry1EMV8ORypc6FzVbbp-gr2neBex3Eypt3f938DpQ@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Andy Bierman <andy@yumaworks.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=047d7bdc1a80073b7a04e91656c1
Cc: Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 11:27:35 -0000

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

Hi,

I guess I don't know (or care) too much the proper chain of command to
fix this problem.  It seems that there is a job position to
be filled.  If there are not enough candidates for that job, then what?
Does the IETF adapt the job so there are more people
interested in doing it? Is this just an internal IESG decision?

If the current management structure is already optimal
and the workload is only 14 hours a week then it should be easy
to find people willing to accept IESG nominations.


Andy


On Sat, Oct 19, 2013 at 1:37 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Friday, October 18, 2013 13:57 -0700 Andy Bierman
> <andy@yumaworks.com> wrote:
>
> >...
> > IMO it is an implementation detail how the IETG divides its
> > work. I agree with Brian that just delegating the undesrable
> > work to an assistant volunteer is not a real plan.  But if
> > NOMCOM thinks there is a critical shortage of IESG candidates,
> > then the IESG better fix it, or perhaps the NOMCOM should
> > mandate a solution.
>
> In practical terms, I don't understand this paragraph.  You have
> suggested increasing the number of ADs.  But, if there were a
> critical shortage of IESG candidates (and it is clear that has
> been the case in some areas in the recent past), then increasing
> the number of slots to be filled can't solve that problem
> (indeed can only make it worse), even if it held out the
> possibility of a lower workload in the long run.   I'd also like
> to understand what solutions you propose the Nomcom might
> "mandate" and how.  As far as I can tell, they can do only three
> things.  Of those, the second is unclear because it has been
> much-discussed, never actually attempted, and whether or not it
> is possible depends on interpretations of an edge case in the
> relevant procedures.
>
>         (1) Fill a position.  In theory and in the absence of
>         other candidates, they could fill a position with a dead
>         body or someone's pet rock, but I assume the IAB would
>         find those candidates unqualified.
>
>         (2) Decide to not fill a position.  Whatever that would
>         accomplish, it would _increase_ the workload on the
>         surviving AD in the area (if any) and/or paralyze the
>         area.   I assume the Transport area got an adequate
>         preview of that effect earlier this year.
>
>         (3) Make recommendations that might or might not be
>         acted on and that certainly cannot affect the current
>         year's slots or candidates.
>
> So what would you propose they "mandate" and how?
>
>     john
>
>
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>I guess I don&#39;t know (or care) =
too much the proper chain of command to</div><div>fix this problem. =A0It s=
eems that there is a job position to</div><div>be filled. =A0If there are n=
ot enough candidates for that job, then what?</div>
<div>Does the IETF adapt the job so there are more people</div><div>interes=
ted in doing it? Is this just an internal IESG decision?</div><div><br></di=
v><div>If the current management structure is already optimal</div><div>
and the workload is only 14 hours a week then it should be easy</div><div>t=
o find people willing to accept IESG nominations.</div><div><br></div><div>=
<br></div><div>Andy</div><div><br></div><div><div class=3D"gmail_extra"><br=
>
<div class=3D"gmail_quote">On Sat, Oct 19, 2013 at 1:37 AM, John C Klensin =
<span dir=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank=
">john-ietf@jck.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
<br>
--On Friday, October 18, 2013 13:57 -0700 Andy Bierman<br>
&lt;<a href=3D"mailto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:=
<br>
<br>
&gt;...<br>
&gt; IMO it is an implementation detail how the IETG divides its<br>
&gt; work. I agree with Brian that just delegating the undesrable<br>
&gt; work to an assistant volunteer is not a real plan. =A0But if<br>
&gt; NOMCOM thinks there is a critical shortage of IESG candidates,<br>
&gt; then the IESG better fix it, or perhaps the NOMCOM should<br>
&gt; mandate a solution.<br>
<br>
In practical terms, I don&#39;t understand this paragraph. =A0You have<br>
suggested increasing the number of ADs. =A0But, if there were a<br>
critical shortage of IESG candidates (and it is clear that has<br>
been the case in some areas in the recent past), then increasing<br>
the number of slots to be filled can&#39;t solve that problem<br>
(indeed can only make it worse), even if it held out the<br>
possibility of a lower workload in the long run. =A0 I&#39;d also like<br>
to understand what solutions you propose the Nomcom might<br>
&quot;mandate&quot; and how. =A0As far as I can tell, they can do only thre=
e<br>
things. =A0Of those, the second is unclear because it has been<br>
much-discussed, never actually attempted, and whether or not it<br>
is possible depends on interpretations of an edge case in the<br>
relevant procedures.<br>
<br>
=A0 =A0 =A0 =A0 (1) Fill a position. =A0In theory and in the absence of<br>
=A0 =A0 =A0 =A0 other candidates, they could fill a position with a dead<br=
>
=A0 =A0 =A0 =A0 body or someone&#39;s pet rock, but I assume the IAB would<=
br>
=A0 =A0 =A0 =A0 find those candidates unqualified.<br>
<br>
=A0 =A0 =A0 =A0 (2) Decide to not fill a position. =A0Whatever that would<b=
r>
=A0 =A0 =A0 =A0 accomplish, it would _increase_ the workload on the<br>
=A0 =A0 =A0 =A0 surviving AD in the area (if any) and/or paralyze the<br>
=A0 =A0 =A0 =A0 area. =A0 I assume the Transport area got an adequate<br>
=A0 =A0 =A0 =A0 preview of that effect earlier this year.<br>
<br>
=A0 =A0 =A0 =A0 (3) Make recommendations that might or might not be<br>
=A0 =A0 =A0 =A0 acted on and that certainly cannot affect the current<br>
=A0 =A0 =A0 =A0 year&#39;s slots or candidates.<br>
<br>
So what would you propose they &quot;mandate&quot; and how?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 john<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div></div>

--047d7bdc1a80073b7a04e91656c1--

From adrian@olddog.co.uk  Sat Oct 19 04:38:12 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 F190911E81B6 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 P5eHXAlbZLyi for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:38:06 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF6C21F9F62 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:38:02 -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 r9JBc1ut027674 for <ietf@ietf.org>; Sat, 19 Oct 2013 12:38:01 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9JBbxP6027657 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 19 Oct 2013 12:38:00 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF Discuss'" <ietf@ietf.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Date: Sat, 19 Oct 2013 12:37:58 +0100
Message-ID: <079d01ceccbf$a9b9f7c0$fd2de740$@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: AQHEaQq0Qoy4PUvSiHjXO1ZKzsoNrwKcP8NTAlQkXLgCnaEbsQHVD6VWApRxHQcB0sYI1gJTaxOEASxJmNYCOD3fNQGUnDSaAiMVxbEBzbjMAZlIb1gQ
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: Sat, 19 Oct 2013 11:38:12 -0000

I am struggling to see why name an AD on the front page.
There is already a way in the Data Tracker to find out which AD "responsible" at
the time of IESG approval.
I do not want or see value in being patted on the head for the publication of an
RFC.

What is the purpose?
What would be the implication?

Adrian

> > On Oct 18, 2013, at 11:10 PM, Loa Andersson <loa@pi.nu> wrote:
> >> Would this be an implementation of what you say (example built on
> >> one of our recent RFCs)
> >>
> >> Internet Engineering Task Force (IETF)                           M. Chen
> >> Request for Comments: 6829                  Huawei Technologies Co., Ltd
> >> Updates: 4379                                                     P. Pan
> >> Category: Standards Track                                       Infinera
> >> ISSN: 2070-1721                                             C. Pignataro
> >> Responsible AD: A. Farrel, Juniper                              R. Asati
> >> WG Chair/Shepherd: L. Andersson, Huawei                            Cisco


From cabo@tzi.org  Sat Oct 19 04:42:17 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 8F9DD11E80E7 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.341
X-Spam-Level: 
X-Spam-Status: No, score=-104.341 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_ILLEGAL_IP=1.908, 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 1AtsNvSXtGyM for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:42:08 -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 40CFF11E81B6 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:42:04 -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 r9JBfxQu010003; Sat, 19 Oct 2013 13:42:00 +0200 (CEST)
Received: from [172.20.10.5] (ip-2-203-46-172.web.vodafone.de [2.203.46.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id A341A3C4; Sat, 19 Oct 2013 13:41:59 +0200 (CEST)
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>
Date: Sat, 19 Oct 2013 13:41:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
Cc: 'IETF Discuss' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 11:42:17 -0000

On Oct 19, 2013, at 13:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> I am struggling to see why name an AD on the front page.

Yeah, sounds dangerous.  Will further increase the threshold for getting =
an RFC out :-)

Seriously: The discussion was about WG chairs, and there it might make =
more sense.

(But my original idea was not about changing the RFC process at all, but =
about adding accessible information to the IETF web site.)

Gr=FC=DFe, Carsten


From alexey.melnikov@isode.com  Sat Oct 19 04:53: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 7D15711E81C3 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:53:35 -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 KijtMeRmDJOh for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 04:53:30 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id D5AE611E81C4 for <ietf@ietf.org>; Sat, 19 Oct 2013 04:53:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1382183608; d=isode.com; s=selector; i=@isode.com; bh=nL5LCJKFmjXzF+/99PiOWCsN4IROFsSvs2cwtEnUA1A=; 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=NV6QTUHgvxk/PUWQGpZhjFhRxMjOgFOWkt4wW8ntCthJdP+VbCBBtuDo4m8BsMNVE5+V3e hf9bq3mry5w+Yle79rWdtwA+gWRfY6fLbu+RecV58hJlUN9CWgNUOpTR0cBAe3ADLE7ddl e4640GGnIUsKsHLUOIe3jS2ABvD+Oz8=;
Received: from [188.29.41.51] (188.29.41.51.threembb.co.uk [188.29.41.51])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UmJytAB8l5ld@statler.isode.com>; Sat, 19 Oct 2013 12:53:27 +0100
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <5261F82E.7030800@pi.nu> <B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com> <1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>
In-Reply-To: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>
Message-Id: <C91F8290-621C-48CC-A9A9-4CBDCB707C8C@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Proper credit for work done -- on finding chairs  (was CHANGE THE JOB)
Date: Sat, 19 Oct 2013 13:02:03 +0100
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Heather Flanagan <rse@rfc-editor.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 11:53:35 -0000

On 19 Oct 2013, at 12:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> I am struggling to see why name an AD on the front page.
> There is already a way in the Data Tracker to find out which AD "responsib=
le" at
> the time of IESG approval.

Unless another AD reassigns it before AUTH48. But your general point is vali=
d.

> I do not want or see value in being patted on the head for the publication=
 of an
> RFC.
>=20
> What is the purpose?
> What would be the implication?
>=20
> Adrian
>=20
>>> On Oct 18, 2013, at 11:10 PM, Loa Andersson <loa@pi.nu> wrote:
>>>> Would this be an implementation of what you say (example built on
>>>> one of our recent RFCs)
>>>>=20
>>>> Internet Engineering Task Force (IETF)                           M. Che=
n
>>>> Request for Comments: 6829                  Huawei Technologies Co., Lt=
d
>>>> Updates: 4379                                                     P. Pa=
n
>>>> Category: Standards Track                                       Infiner=
a
>>>> ISSN: 2070-1721                                             C. Pignatar=
o
>>>> Responsible AD: A. Farrel, Juniper                              R. Asat=
i
>>>> WG Chair/Shepherd: L. Andersson, Huawei                            Cisc=
o
>=20

RFC Editor website already have web pages with supplementary information (ob=
soleted, errata, etc). Can this information be shown there?=

From loa@pi.nu  Sat Oct 19 05:48:32 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 AC3F211E81A9 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 05:48: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 60vaLjkMCcgW for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 05:48:26 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 95A8A11E8176 for <ietf@ietf.org>; Sat, 19 Oct 2013 05:48:26 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 5B22A1802039 for <ietf@ietf.org>; Sat, 19 Oct 2013 14:48:25 +0200 (CEST)
Message-ID: <52627F96.7060808@pi.nu>
Date: Sat, 19 Oct 2013 20:48:22 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org>
In-Reply-To: <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 19 Oct 2013 12:48:32 -0000

All,

Please misunderstand me correctly!

I'm not proposing adding AD's or wg chairs on the first page of RFCs,
just trying to figure out what Ted had in mind.

Don't say I that i succeeded in that. But Ted at least nodded slightly.
Ted and Carsten approached this from  a credit perspective; I guess that
is valid. I'm more thinking about from a public "right to know"
respective - "How was that lousy wg chair that let this through?"

I admit that there are other ways to this, but the most public product
we have are the RFCs.

I think it should be discussed from both perspectives. I know that my
ADs, myself and my co-chairs and others, put enough effort into an RFCs
from end of wglc to AUTH48 to be mentioned e.g. in Acknowledgement
section, but I want to keep this strictly at the authors leisure.

So the combination giving credit and making responsibility clearly
visible makes this at least worth to discuss,

On the other hand a less more public way would be to what IAB on
their RFCs, add a section "IAB Members at the Time of Approval"!
Maybe and Appendix "WG Chairs, Shepherd and responsible AD at the
time of the Approval".

Sorry for meandering, but I feel that there is something worth
capturing in that part of the discussion.

On 2013-10-19 19:41, Carsten Bormann wrote:
> On Oct 19, 2013, at 13:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>
>> I am struggling to see why name an AD on the front page.
>
> Yeah, sounds dangerous.  Will further increase the threshold for getting an RFC out :-)
>
> Seriously: The discussion was about WG chairs, and there it might make more sense.
>
> (But my original idea was not about changing the RFC process at all, but about adding accessible information to the IETF web site.)
>
> Grüße, Carsten
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From stephen.farrell@cs.tcd.ie  Sat Oct 19 06:59:13 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 3730311E81BE for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 06:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.341
X-Spam-Level: 
X-Spam-Status: No, score=-102.341 tagged_above=-999 required=5 tests=[AWL=0.258, 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 rUNIFiFmrbKx for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 06:59: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 4DAA111E81AF for <ietf@ietf.org>; Sat, 19 Oct 2013 06:59:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1ECAFBE74; Sat, 19 Oct 2013 14:59:06 +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 u0rv-73gYoXe; Sat, 19 Oct 2013 14:59:05 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.45.50.37]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 17B7EBE6F; Sat, 19 Oct 2013 14:59:05 +0100 (IST)
Message-ID: <52629028.8000901@cs.tcd.ie>
Date: Sat, 19 Oct 2013 14:59:04 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>, ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>	<493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org> <52627F96.7060808@pi.nu>
In-Reply-To: <52627F96.7060808@pi.nu>
X-Enigmail-Version: 1.5.2
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, 19 Oct 2013 13:59:13 -0000

On 10/19/2013 01:48 PM, Loa Andersson wrote:
> 
> On the other hand a less more public way would be to what IAB on
> their RFCs, add a section "IAB Members at the Time of Approval"!
> Maybe and Appendix "WG Chairs, Shepherd and responsible AD at the
> time of the Approval".

Keep it informal - authors can do this now if they want. (And
we can stop discussing it:-)

Personallly, I'd encourage authors to not add ADs unless there's
a specific reason. Within an IETF context, ADs get enough ego
boosting already.

But WG chairs do deserve more acks than they're getting I think
so if authors ack'd them frequently that'd be good.

S.

From mars.techno.cat@gmail.com  Sat Oct 19 08:27:39 2013
Return-Path: <mars.techno.cat@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 8190B11E81D1 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 08:27: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, 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 Md+pGU+bNjSm for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 08:27:39 -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 BC4FB11E81E0 for <ietf@ietf.org>; Sat, 19 Oct 2013 08:27:38 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id db12so2935780veb.1 for <ietf@ietf.org>; Sat, 19 Oct 2013 08:27: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=VloTCWwl+o31zWqdrqkDcAKbQaFZmV6WyGS05Otbjdg=; b=L/zhUg0VRvSOAcKCH5H81c5LQZVomqRIvi5jx/hq8Rww4hcVRVT2viAeKJy0uJ8Gci d1TLTUQSeVYBO/8WPmR3QAs7Hyw/BYTR9crMQZMphjs/yrKAi+9rHx+yzZk4METky7q/ iBbta2g1JpUm4og/1h8U7/G079SHWr/YMV+h9dtBDWau3o13ARRyLwhX5KtAmeycgKDZ e0LpXkXKhOYScLEh+k8S4cNVYWE51IaFvxrV6CZRKRGAsUDvg7Pf+rv85xBRwodODSOn LbUhRFy4MEfyEU5DZO4k01AgpSsVeJWPKOWlPiDo+Csa0FAKrZv36WUnP1pvinLhLheo 6bIQ==
MIME-Version: 1.0
X-Received: by 10.58.11.73 with SMTP id o9mr5639858veb.8.1382196457425; Sat, 19 Oct 2013 08:27:37 -0700 (PDT)
Received: by 10.58.44.106 with HTTP; Sat, 19 Oct 2013 08:27:37 -0700 (PDT)
In-Reply-To: <CE1EEDDF-F172-44B2-AD03-2CBD3B3B5948@unog.ch>
References: <CE1EEDDF-F172-44B2-AD03-2CBD3B3B5948@unog.ch>
Date: Sat, 19 Oct 2013 10:27:37 -0500
Message-ID: <CAK41CSQaZBJPXZDYc3d-+y3HmF_95K6RTs+Mw-cnSa0zSEt6Ag@mail.gmail.com>
Subject: Re: Opening session
From: Techno CAT <mars.techno.cat@gmail.com>
To: Chengetai Masango <cmasango@unog.ch>
Content-Type: multipart/alternative; boundary=047d7b2ed341dad35804e919b03e
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, 19 Oct 2013 15:27:39 -0000

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

On Wed, Oct 16, 2013 at 8:28 PM, Chengetai Masango <cmasango@unog.ch> wrote:

> Hei Jari,
>
> Will you be able to give a 5 min speech at the IGF opening session ?
>
> Best regards,
>
> Chengetai
>
>
> We charge $250,000 for a ONE Day Event.
We supply our own Security Force in addition to your "I* Task Force"

It appears the ISOC (IETF) CEO is paid $890,000 per year.
The ISOC likely has additional fees for their Security Force.

http://3DNB.COM
-- 

@Techno_CAT_r
http://Twitter.com/Techno_CAT_r

--047d7b2ed341dad35804e919b03e
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 Wed, Oct 16, 2013 at 8:28 PM, Chengetai Masango <span dir=3D"ltr=
">&lt;<a href=3D"mailto:cmasango@unog.ch" target=3D"_blank">cmasango@unog.c=
h</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">Hei Jari,<br>
<br>
Will you be able to give a 5 min speech at the IGF opening session ?<br>
<br>
Best regards,<br>
<br>
Chengetai<br>
<br>
<br>
</blockquote></div>We charge $250,000 for a ONE Day Event.<br></div><div cl=
ass=3D"gmail_extra">We supply our own Security Force in addition to your &q=
uot;I* Task Force&quot;<br><br></div><div class=3D"gmail_extra">It appears =
the ISOC (IETF) CEO is paid $890,000 per year.<br>
</div><div class=3D"gmail_extra">The ISOC likely has additional fees for th=
eir Security Force.<br></div><div class=3D"gmail_extra"><br></div><div clas=
s=3D"gmail_extra"><a href=3D"http://3DNB.COM">http://3DNB.COM</a><br>-- <br=
><div dir=3D"ltr">
<br>@Techno_CAT_r<br><a href=3D"http://Twitter.com/Techno_CAT_r" target=3D"=
_blank">http://Twitter.com/Techno_CAT_r</a><br></div>
</div></div>

--047d7b2ed341dad35804e919b03e--

From prvs=0997c54d95=johnl@iecc.com  Sat Oct 19 09:52:14 2013
Return-Path: <prvs=0997c54d95=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 0F4F911E821B for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.472
X-Spam-Level: 
X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.127,  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 a0a8poo+FvUP for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:52:09 -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 9B07611E8214 for <ietf@ietf.org>; Sat, 19 Oct 2013 09:52:09 -0700 (PDT)
Received: (qmail 62104 invoked from network); 19 Oct 2013 16:52:08 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Oct 2013 16:52:08 -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=5262b8b8.xn--30v786c.k1310; i=johnl@user.iecc.com; bh=tCRa270TzN7oeJWA2/4BjDyBaPXSuPP0H98NX/ygy0g=; b=QDVbHMZtM6BMzw5IbPaciYanJsz8+SU4VSCEJmalXWR09X0Gu0BNjH0YVWKeUNV38ceP8OxatGdZIoQkAZ3IqKng/B2OsznJN4wi9HDSPJJdCJZkS1XBonEYuVlH4r6iLOS9nLP8Hqj/S94GKJK25ZhX+YervzBWn+xgaFK38k3Px5dmAw4uKohgLcJaGq6Mha7o3NNTFSTIKUu2OMaJMld8275KG4h8NMCf/fXT+1qXTqnRdlaAb1P6EAzL617G
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=5262b8b8.xn--30v786c.k1310; olt=johnl@user.iecc.com; bh=tCRa270TzN7oeJWA2/4BjDyBaPXSuPP0H98NX/ygy0g=; b=LyA32DMEOoDNvSRgmxktDqlvgDitpdit0iV2nsW7O9EkXA96RCo0NKuzW4uSjqSa2Kb2y/duK82OujjwctBVdCWlUJHowrMG6DmRwEwNrp0iijHnFKXat+Zmzd2q2WhEwCI6KzfVj7TQDFajJoaeqw7DjmyDy8xWsId7DyIFZ5S8lgm6JXsDPqNBbw8RwBH+02QfZK8YBnoy1pk9Ih9foMmBIUFNqO4sLqipHU/pT941AniiW/LxLjRuezoqPWaU
Date: 19 Oct 2013 16:51:46 -0000
Message-ID: <20131019165146.12433.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
In-Reply-To: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: adrian@olddog.co.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: Sat, 19 Oct 2013 16:52:14 -0000

>What is the purpose?
>What would be the implication?

If you go back to my original message on this topic, the issue was
that in many organizations, for better or worse, they measure your
productivity by the amount of author credit you get, which is why we
see scientific papers with 50 or more co-authors.

So if more author credit to WG chairs and ADs would help them persuade
their management or tenure committee or whatever that they've been
doing work that is worth supporting, we should give more author
credit.

If we think this would help, my inclination would be to put them in
the author list, and if we have a big ugly author list that runs
halfway down the page, so what? 

R's,
John

PS: In case it's not obvious, the document format is a nit.  The issue
is what will help people get funding for key IETF jobs.


Internet Engineering Task Force (IETF)                           M. Chen
Request for Comments: 6829                  Huawei Technologies Co., Ltd
Updates: 4379                                                     P. Pan
Category: Standards Track                                       Infinera
ISSN: 2070-1721                                             C. Pignataro
                                                                R. Asati
                                                                   Cisco
						          A. Farrel (AD)
							         Juniper
						      L. Andersson (WGC)
						                  Huawei

From melinda.shore@gmail.com  Sat Oct 19 09:55:33 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 7B4AD11E821C for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:55:33 -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 DpTeZiSl5DrR for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:55:33 -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 002D411E8217 for <ietf@ietf.org>; Sat, 19 Oct 2013 09:55:32 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb1so3450572pad.3 for <ietf@ietf.org>; Sat, 19 Oct 2013 09:55: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Bu37NpUumPLaCqXkTpR2TlcVD2Gj4XYoGqrArle44C0=; b=XYymjt3wp41fCRX47CkqsMDHPGNuG79KYdHEghAuz9uXmR6KuFRPzI7ID2Kk5+JicC 4aQC3Ass4z2Ox+DRt6EL2DSoOBVYWsbI12JDk2TruFw8ySFIH11OXSkljjAsEocB7Ltg 4trLp7pTmHTnffXWSvPcQbcYg1ynmjQ/COMrF2XlCfqODPnxevrZaPHSZfQv46PrPxxL DA4h5DGzPAjkho2LcEiGZWm7CEHRqQG72ndj3pGFrqJhc8YnhDGSufODemDa+lcu4kuN TDViD6WAtTCi+IGiKNuKTSuiEmnvwSs/Sqp5n1jd6+FMEIQkDvLA8tuGNxpNi7PwO5Ti ukXg==
X-Received: by 10.68.52.231 with SMTP id w7mr4958787pbo.19.1382201732412; Sat, 19 Oct 2013 09:55:32 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id gg10sm9770318pbc.46.2013.10.19.09.55.30 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Oct 2013 09:55:31 -0700 (PDT)
Message-ID: <5262B980.9050802@gmail.com>
Date: Sat, 19 Oct 2013 08:55:28 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <20131019165146.12433.qmail@joyce.lan>
In-Reply-To: <20131019165146.12433.qmail@joyce.lan>
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, 19 Oct 2013 16:55:33 -0000

On 10/19/13 8:51 AM, John Levine wrote:
> PS: In case it's not obvious, the document format is a nit.  The issue
> is what will help people get funding for key IETF jobs.

That seems unlikely to me in the extreme, but I don't see a real
downside to it.

Melinda


From adrian@olddog.co.uk  Sat Oct 19 09:55:39 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 DB32B11E8225 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 9JHmzVxjX+Kf for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 09:55:33 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id C3CB021F8424 for <ietf@ietf.org>; Sat, 19 Oct 2013 09:55:32 -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 r9JGtUcR012873;  Sat, 19 Oct 2013 17:55:31 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9JGtTpi012864 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 19 Oct 2013 17:55:29 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John Levine'" <johnl@taugh.com>, <ietf@ietf.org>
References: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <20131019165146.12433.qmail@joyce.lan>
In-Reply-To: <20131019165146.12433.qmail@joyce.lan>
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Date: Sat, 19 Oct 2013 17:55:27 +0100
Message-ID: <07cc01ceccec$03f77420$0be65c60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHhmf/ZbHMMhI2S11VK10Z8eY6KIZnWo7HA
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: Sat, 19 Oct 2013 16:55:39 -0000

> If we think this would help, my inclination would be to put them in
> the author list, and if we have a big ugly author list that runs
> halfway down the page, so what?

Ack.
Presume that it is not an issue for existing ADs (else they wouldn't =
have got there).
Maybe anyone who was thinking of standing who would find this helpful =
could speak up?


From abdussalambaryun@gmail.com  Sat Oct 19 10:04:53 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 47FEB11E8215 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 10:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  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 bppVbwqadp3A for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 10:04:52 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A93A711E822C for <ietf@ietf.org>; Sat, 19 Oct 2013 10:04:50 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id v10so554480pde.1 for <ietf@ietf.org>; Sat, 19 Oct 2013 10:04: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 :content-type; bh=bo9IV7G63g8uWiQ9YlTxNfdo0S5WSV/7BmyWbiRprb8=; b=c8T5/xCuKMpkBNpbSrVDXeeHTyOC6g00okrQWeIJgQ+P2H8D9kttxGxVjIW3bmLuio 0CEtlr0gc8jen8TXHRGE7/9gb47wLN5WyyHoHPev3lW/nyQQM3kJVESjKOwrtlMm8eRu KY6IUb6UVGVtzryyvB/X+l5rI1DeBi6gXdbaOqiWNSprr1mhgvvSzh+3+ajCF4p8FbpR 4kio+JVYMFITt9NOeT+DEGAYM+UanPdalUt4VNfhrtpoZ+t7I1NHYmHpgt6DA9+8k7QF DNuhFP/wmLZPuHZ0sKW3meZJJg7k0wcSVt3Yq72nh98Hw5AJQBJap5wg34Q6fYkQuFTM Wz5A==
MIME-Version: 1.0
X-Received: by 10.68.44.33 with SMTP id b1mr8814334pbm.53.1382202290232; Sat, 19 Oct 2013 10:04:50 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sat, 19 Oct 2013 10:04:50 -0700 (PDT)
In-Reply-To: <5261F82E.7030800@pi.nu>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <5261F82E.7030800@pi.nu>
Date: Sat, 19 Oct 2013 19:04:50 +0200
Message-ID: <CADnDZ8_gkZvrxeVPSUa256f8OLhUGzRP8n-v2Q4cwkT-8FgqLw@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec530513584648104e91b0c0f
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 17:04:53 -0000

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

I don't think credit for assisting work should be out of acknowledge
section, and don't give credit in work for responsible duties given by
organisation in titles/position, preferred to give credit to full title
duties not per work/task. Preferred to give credit per work mostly to whom
made efforts without given titles but their only intention is better
document/work but still IESG may not acknowledge them or not understand the
vision :(

AB

On 10/19/13, Loa Andersson <loa@pi.nu <javascript:;>> wrote:
> Ted,
>
>
> On 2013-10-18 23:10, Ted Lemon wrote:
>> The most useful comment I've heard on this thread is that it makes sense
>> to credit the working group chairs as well as the authors of a document
in
>> the document at the same level of emphasis.   And possibly the ADs as
>> well.   I don't know if this would make a difference, but it's
>> interesting, and might be worth the experiment.
>
> Would this be an implementation of what you say (example built on
> one of our recent RFCs)
>
> Internet Engineering Task Force (IETF)                           M. Chen
> Request for Comments: 6829                  Huawei Technologies Co., Ltd
> Updates: 4379                                                     P. Pan
> Category: Standards Track                                       Infinera
> ISSN: 2070-1721                                             C. Pignataro
> Responsible AD: A. Farrel, Juniper                              R. Asati
> WG Chair/Shepherd: L. Andersson, Huawei                            Cisco
>                                                              January 2013
>
>                     Label Switched Path (LSP) Ping for
>   Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6
>
> Note: This is not a suggestion, just a question for clarification. And
> if we want to do it "this way" it is not a layout proposal. If we do it
> like this we would have a second level effect in capturing the
> shepeherds, wg chairs and responsible ADs addresses in separate section
> following the Authors Addresses.
>
> /Loa
>
>
>>
>> But really, the main thing to say about this conversation is that it's a
>> classic example of why the AD's job is so time consuming.   We have to
>> monitor these conversations, because otherwise we aren't doing the part
of
>> our job that involves listening to the IETF.   Having long bikeshed
>> discussions about the woeful brokenness of the AD's job over and over
>> again without any action proposed is expensive.
>>
>> Most of what's been discussed here has been discussed by the ADs during
>> the recent IESG retreat, and substantial action was taken as a result of
>> the discussion at that retreat.   It might be interesting to see if any
of
>> what we discussed actually changes anything.
>>
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com<javascript:;>
> Senior MPLS Expert                          loa@pi.nu <javascript:;>
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>

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

<div>I don&#39;t think credit for assisting work should be out of acknowled=
ge section, and don&#39;t give credit in work for responsible duties=A0give=
n by organisation in titles/position,=A0preferred to=A0give credit to full =
title duties not per work/task. Preferred to give credit per work=A0mostly=
=A0to whom made efforts without given titles but their only intention is=A0=
better document/work=A0but still IESG may not acknowledge=A0them or not und=
erstand the vision :(</div>
<div><br></div>
AB<br>
<br>
On 10/19/13, Loa Andersson &lt;<a href=3D"javascript:;" onclick=3D"_e(event=
, &#39;cvml&#39;, &#39;loa@pi.nu&#39;)">loa@pi.nu</a>&gt; wrote:<br>
&gt; Ted,<br>
&gt;<br>
&gt;<br>
&gt; On 2013-10-18 23:10, Ted Lemon wrote:<br>
&gt;&gt; The most useful comment I&#39;ve heard on this thread is that it m=
akes sense<br>
&gt;&gt; to credit the working group chairs as well as the authors of a doc=
ument in<br>
&gt;&gt; the document at the same level of emphasis. =A0 And possibly the A=
Ds as<br>
&gt;&gt; well. =A0 I don&#39;t know if this would make a difference, but it=
&#39;s<br>
&gt;&gt; interesting, and might be worth the experiment.<br>
&gt;<br>
&gt; Would this be an implementation of what you say (example built on<br>
&gt; one of our recent RFCs)<br>
&gt;<br>
&gt; Internet Engineering Task Force (IETF) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 M. Chen<br>
&gt; Request for Comments: 6829 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Huawei T=
echnologies Co., Ltd<br>
&gt; Updates: 4379 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 P. Pan<br>
&gt; Category: Standards Track =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Infinera<br>
&gt; ISSN: 2070-1721 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 C. Pignataro<br>
&gt; Responsible AD: A. Farrel, Juniper =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0R. Asati<br>
&gt; WG Chair/Shepherd: L. Andersson, Huawei =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0Cisco<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0January 2013<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Label Switched Path (LSP) Ping=
 for<br>
&gt; =A0 Pseudowire Forwarding Equivalence Classes (FECs) Advertised over I=
Pv6<br>
&gt;<br>
&gt; Note: This is not a suggestion, just a question for clarification. And=
<br>
&gt; if we want to do it &quot;this way&quot; it is not a layout proposal. =
If we do it<br>
&gt; like this we would have a second level effect in capturing the<br>
&gt; shepeherds, wg chairs and responsible ADs addresses in separate sectio=
n<br>
&gt; following the Authors Addresses.<br>
&gt;<br>
&gt; /Loa<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; But really, the main thing to say about this conversation is that =
it&#39;s a<br>
&gt;&gt; classic example of why the AD&#39;s job is so time consuming. =A0 =
We have to<br>
&gt;&gt; monitor these conversations, because otherwise we aren&#39;t doing=
 the part of<br>
&gt;&gt; our job that involves listening to the IETF. =A0 Having long bikes=
hed<br>
&gt;&gt; discussions about the woeful brokenness of the AD&#39;s job over a=
nd over<br>
&gt;&gt; again without any action proposed is expensive.<br>
&gt;&gt;<br>
&gt;&gt; Most of what&#39;s been discussed here has been discussed by the A=
Ds during<br>
&gt;&gt; the recent IESG retreat, and substantial action was taken as a res=
ult of<br>
&gt;&gt; the discussion at that retreat. =A0 It might be interesting to see=
 if any of<br>
&gt;&gt; what we discussed actually changes anything.<br>
&gt;&gt;<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt;<br>
&gt; Loa Andersson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0email: <a=
 href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;loa@mail01=
.huawei.com&#39;)">loa@mail01.huawei.com</a><br>
&gt; Senior MPLS Expert =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;loa@pi.n=
u&#39;)">loa@pi.nu</a><br>
&gt; Huawei Technologies (consultant) =A0 =A0 phone: +46 739 81 21 64<br>
&gt;<br>

--bcaec530513584648104e91b0c0f--

From melinda.shore@gmail.com  Sat Oct 19 10:05: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 8AE8311E8236 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 10:05: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 wKvrAAlSM+wV for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 10:05:47 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id F2ECC11E8239 for <ietf@ietf.org>; Sat, 19 Oct 2013 10:05:43 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z10so6234039pdj.30 for <ietf@ietf.org>; Sat, 19 Oct 2013 10:05: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=dE1xW9fyUD7UWX45q72h2B0xqaE9cELBq8qRes3WAmM=; b=e09F5AwCtDHhZeJOcPop56b20M2VBpdTy4mgMoY82jg2fF3zPsgDkWQS/CRiIBXZlG tq7aFhR9K/aPl8EKK/pDTdapm38l+DD8okBWtFqr348r6qWHRWYmPFuaxK0Z5z3dRSKf DQWwplaex7cJJNHGZIpj3HbG5Uoohczo3hWjqMK23cd9gRrOBnBtOXXOQchU8LIBuG9c bjYdPrvfL28L2F/3zkeuipqNUa4dhMex0MlDjg9evDrM9Y4Bs+u4uYlDAYZs78x/935a +dLYBTf4V1AHGKBFMSwyQyklLptuNQl/OGkLszdjx4JQyMJLfAiWhyPOa4kaSfKByhax MgLw==
X-Received: by 10.66.66.202 with SMTP id h10mr9529380pat.70.1382202343359; Sat, 19 Oct 2013 10:05:43 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id ve9sm9864841pbc.19.2013.10.19.10.05.41 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Oct 2013 10:05:42 -0700 (PDT)
Message-ID: <5262BBE4.6060202@gmail.com>
Date: Sat, 19 Oct 2013 09:05:40 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <20131019165146.12433.qmail@joyce.lan> <07cc01ceccec$03f77420$0be65c60$@olddog.co.uk>
In-Reply-To: <07cc01ceccec$03f77420$0be65c60$@olddog.co.uk>
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, 19 Oct 2013 17:05:47 -0000

On 10/19/13 8:55 AM, Adrian Farrel wrote:
> Presume that it is not an issue for existing ADs (else they wouldn't have got there).
> Maybe anyone who was thinking of standing who would find this helpful could speak up?

It's drifted back and forth across my radar for a number of years
and I have to say that it would make no difference whatsoever.  I
can't imagine that it would make any difference to academic
candidates, either, as it would not contribute to a tenure decision
(it's not that the document is only arguably refereed for
publication, but that the chair or AD isn't even an author.  Some
universities are quite picky about what counts and what doesn't
(refereed journal articles count, textbooks don't).  I did my
graduate work at the University of Chicago, where what were called
"How we do it good here" papers were held in very high disregard.

At any rate, no, it would make no difference to me.  Might to someone
else but I'm having a hard time imagining who (the issue when I was
with the networking behemoth was time taken away from what they
hired me for, not recognition or lack thereof).

But, as I just posted in another note, I don't see a real downside
to adding it, and as someone else pointed out it may be useful for
answering provenance-type questions.


Melinda


From hallam@gmail.com  Sat Oct 19 11:03: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 9158411E8248 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 11:03:43 -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, 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 YdlbQ8J06a5z for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 11:03:43 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6D411E823B for <ietf@ietf.org>; Sat, 19 Oct 2013 11:03:41 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id p9so4175584lbv.38 for <ietf@ietf.org>; Sat, 19 Oct 2013 11:03:41 -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=3564Ms1EKPDWCNiIyEhZHXu7ZZddJApJE/UJvrFFOy4=; b=BciNtKlpnbOj7ytkd0gMPPoRh5p9+2eK6R4NreR3rctBw69kGMSJV4ecfbGrR4rd38 TYcdP0iC8cvRRkN/A+AEb9EbqPzZFOoRgyQfuUXN9bN1BlN5Cdn+XvuWioxEgHXwc/k5 DIW1ZDZKDPf1nhpdyB2H5z08fiJjh0GDBASrnk4uZY0LD90lk4sYSFz+Lkq/s8xuO416 LW/qSdlevsQSrcREM2siGKzStrS8AhQKy4otH3+oI5Sz7JpRlQug0UxztFPTBWo+nInp nC+5DzRmy0L9RMlqsBs/zFs1jQiOEI4xwXQOxCdDBh8Us6FrncxvXbc0+Jozdy4KbuM+ NTVg==
MIME-Version: 1.0
X-Received: by 10.112.57.49 with SMTP id f17mr6290274lbq.26.1382205820943; Sat, 19 Oct 2013 11:03:40 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Sat, 19 Oct 2013 11:03:40 -0700 (PDT)
In-Reply-To: <5262BBE4.6060202@gmail.com>
References: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <20131019165146.12433.qmail@joyce.lan> <07cc01ceccec$03f77420$0be65c60$@olddog.co.uk> <5262BBE4.6060202@gmail.com>
Date: Sat, 19 Oct 2013 14:03:40 -0400
Message-ID: <CAMm+Lwgy2_pyXrpAXxe+3DyApwOBaX7GfQWGhtNAywe8iQeD6g@mail.gmail.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133eacaf6c36004e91bde78
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: Sat, 19 Oct 2013 18:03:43 -0000

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

For what it is worth, I get consulting business because my name is on RFCs.
It is not a sufficient qualification of course but it one of the ways the
search firms find me.

I don't think that we need to worry too much about the inanities of the
academic publication game. Back in the 1980s the universities were the only
places that had the computing power. That isn't a constraint any more and
they don't pay a tenth of what consulting work pays.

That game is going to be very different in a decades time in any case. The
Web is only just starting to nibble the edges of the academic publishing
racket. It takes decades for major social changes to be felt but the
transitions can be swift. The Web will do for that game what Amazon did for
book of the month club and EBay for classified ads.

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

<div dir=3D"ltr">For what it is worth, I get consulting business because my=
 name is on RFCs. It is not a sufficient qualification of course but it one=
 of the ways the search firms find me.<div><br></div><div>I don&#39;t think=
 that we need to worry too much about the inanities of the academic publica=
tion game. Back in the 1980s the universities were the only places that had=
 the computing power. That isn&#39;t a constraint any more and they don&#39=
;t pay a tenth of what consulting work pays.=A0</div>
<div><br></div><div>That game is going to be very different in a decades ti=
me in any case. The Web is only just starting to nibble the edges of the ac=
ademic publishing racket. It takes decades for major social changes to be f=
elt but the transitions can be swift. The Web will do for that game what Am=
azon did for book of the month club and EBay for classified ads.</div>
<div><br></div></div>

--001a1133eacaf6c36004e91bde78--

From turners@ieca.com  Sat Oct 19 11:40:14 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 4420411E827A for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 11:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.01
X-Spam-Level: 
X-Spam-Status: No, score=-100.01 tagged_above=-999 required=5 tests=[AWL=-2.015, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZES-gLaEWbJs for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 11:40:09 -0700 (PDT)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.44.15]) by ietfa.amsl.com (Postfix) with ESMTP id 4575111E8268 for <ietf@ietf.org>; Sat, 19 Oct 2013 11:40:05 -0700 (PDT)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id B1796AD284CF3; Sat, 19 Oct 2013 13:40:04 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 9022EAD284C95 for <ietf@ietf.org>; Sat, 19 Oct 2013 13:40:04 -0500 (CDT)
Received: from [96.231.225.44] (port=59600 helo=thunderfish.local) by gator3286.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1VXbRT-0003JS-O6; Sat, 19 Oct 2013 13:40:03 -0500
Message-ID: <5262D202.1020501@ieca.com>
Date: Sat, 19 Oct 2013 14:40:02 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Allison Mankin <allison.mankin@gmail.com>,  "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com>	<E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net>	<F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com> <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com>
In-Reply-To: <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030302080304040304080202"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.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) [96.231.225.44]:59600
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 13
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "ietf@ietf.org" <ietf@ietf.org>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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, 19 Oct 2013 18:40:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms030302080304040304080202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Instead of the lottery I think Stephen and I worried more about what=20
happens if one of us got hit by a bus ;)

spt

On 10/18/13 10:19 AM, Allison Mankin wrote:
> Kathleen,
>
> Thanks for the perfect explanation of why it's reasonable to run
> against the incumbent, even if you want that person to be selected
> again.
>
> Allison (for the Nomcom)
>
> On Fri, Oct 18, 2013 at 8:40 AM, Moriarty, Kathleen
> <kathleen.moriarty@emc.com> wrote:
>> It is important for multiple people to run even when there is an incum=
bent for a fair process.  When Stephen Farrell ran for Sec AD again last =
year, he encouraged me to accept the nomination and run against him so th=
at there was a good candidate to make the process a bit more fair.  If ei=
ther Stephen of Sean won the lottery, the Noncom would at least have gone=
 through the interview and review process with other candidates in advanc=
e.  The candidate would have worked through the possibility of what this =
meant with their job and that it was possible for them to take on this ro=
le (not insignificant for many of us).  For me, I thought Stephen was doi=
ng a fine job and am glad he was put back on the IESG, but it is good for=
 the Noncom to have options and backup plans.  I received approval from m=
y company, but let my management know that it was unlikely that I would b=
e selected since incumbents usually return.
>>
>> Maybe folks should consider running against an incumbent.  You learn t=
he process and it forces you to figure out if you are interested in the r=
ole and could allocate that time to the IETF.  I gave a positive review o=
f Stephen when running against him.
>>
>> Thanks,
>> Kathleen
>>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf O=
f Ersue, Mehmet (NSN - DE/Munich)
>> Sent: Friday, October 18, 2013 6:36 AM
>> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
>> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas=

>>
>> Hi Allison,
>>
>> in your model you don't count those people who have been rejecting to =
a nomination, just because they believe the current AD did a very good jo=
b and he/she should be reelected.
>>
>> So the situation is not that bad, if there is only the current AD on t=
he nominee list.
>>
>> Cheers,
>> Mehmet
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org
>>> [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair=

>>> 2013
>>> Sent: Thursday, October 17, 2013 4:25 PM
>>> To: IETF Announcement List
>>> Cc: IETF Discuss
>>> Subject: NOMCOM - Critical shortage of nominees for multiple areas
>>>
>>> [Catchier Subject line - apologies to those offended by a duplicate]
>>>
>>> A critically low number of people have accepted nominations for some
>>> of the IESG open positions.  There is only one nominee per slot in
>>> APP, OPS and TSV, only two in INT and RAI.  Many folks have declined =
nominations.
>>>
>>> While the Nomcom appreciates that support for two years of intense
>>> service is hard to assure, and while we are aware that there is much
>>> support for the incumbents who are standing, the IETF should
>>> continually be considering which new talent is available for our
>>> leadership, and the Nomcom process needs for there to be some review =
and deliberation.
>>>
>>> Therefore, we urgently request that more nominees come forward.
>>>
>>> DEADLINES
>>> Nominations - October 18
>>> Questionnaires from nominees - October 25
>>>
>>> Not coincidentally, this is a good time to think over and send your
>>> comments about the current statements of desired expertise of
>>> positions - this is part of the Nomcom's annual review process as wel=
l.  Send them to nomcom13@ietf.org.
>>>
>>> Definitive location [*] of the current statements on desired expertis=
e:
>>>        https://datatracker.ietf.org/nomcom/2013/expertise/
>>>
>>> Instructions and details on nomination [**]:
>>>        https://datatracker.ietf.org/ann/nomcom/60602/
>>>
>>> Thanks, everyone,
>>>
>>> Allison for the Nomcom
>>>
>>> [*] This year the Nomcom tools were recoded, and also transitioned
>>> into the datatracker.  Apologies for a number of places where we
>>> didn't catch reference errors.
>>>
>>> [**] Yes, alas, the previous call for nominations used "OAM" instead
>>> of "OPS," but we have* corrected this (chair's pilot) error where it
>>> occurred in the Nomcom pages.
>


--------------ms030302080304040304080202
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEgDCC
BHwwggJkoAMCAQICCQCdWMxKNutUeTANBgkqhkiG9w0BAQsFADAiMQswCQYDVQQGEwJVUzET
MBEGA1UEChMKSUVDQSwgSW5jLjAeFw0xMzA0MDMxNDUxMThaFw0xNDA0MDMxNDUxMThaMDgx
CzAJBgNVBAYTAlVTMRMwEQYDVQQKEwpJRUNBLCBJbmMuMRQwEgYDVQQDEwtTZWFuIFR1cm5l
cjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOpCGCRptT1m+bIpLTmbahZLZ0Qe
4X99f8SgTQ7QISvUfpmntfOD1oA1AttXlOULEERYubzvDnUTXvstFomQx0XTA67IaV+mw9OD
RtG1hPN/erdKX6sU6rH4tsEbba3Drr/I0HT3YVvD3SjWtGXjF12XLvTP6+LfMIIDTCAPiEd9
KPG23D7skVu/4BvvmdLFI96OARhgwQ86M+lTIn83KRJlbbfAeIevbRx/rUB7D+uvMdWxOzR0
KZJhd6dEeTXVwBXZG4rnQ4uFM+mRSiD4rxDCyOuIuOzR07tnOyCRio6sRipOZvwQUWttdsgM
Es6IxLdWsaTXcs1HjCsxrdedovMCAwEAAaOBnjCBmzAOBgNVHQ8BAf8EBAMCBeAwHwYDVR0j
BBgwFoAUAHRsSeXJUmFxTVY4q2HJ8uHl+w0wGwYDVR0RBBQwEoEQVHVybmVyU0BpZWNhLmNv
bTAyBgNVHR8EKzApMCegJaAjhiFodHRwOi8vd3d3LmllY2EuY29tL2NybHMvaWVjYS5jcmww
FwYDVR0gBBAwDjAMBgorBgEEAYHXAAAAMA0GCSqGSIb3DQEBCwUAA4ICAQAimDYm77ppTi4v
K6qJSUhyvCDMGb8mngiEXEYKxsfdHPWoDO7+06j7dAZ8sDD9/FtEkiUMyoNGSUmKHR+tGper
VnNiM/Zk6WwCJv8dYZwhGXNQeEGzeys/UkFv7CFX7uDSn8GQeB8sOAZ1N1hxV/TvT8qXvcRx
P5+aWTAGAq3TKtCQxZjuU74L3st2hZiOhJlhjhqz0K5FIwWzXUK9uwhZe1thGUpDbRustVgm
KN2Xa0pzwqI1VUO0jnWt24A4u59xo6DJQXzQVMhCx0xhpemuT9BrsBDTX8eJdI1iWv9wp3iv
SrfHjKXp8y8OGD+usiG40HCjj0W9C+dH0VfbgrB6QOI4vA9+kTg4mANth1cxyxwPYOSJv0zi
1qR0eDIGI//2v2/s6TmGuNqbnRa26Ldv5gGqS7xj32Fiaby6UOXs4+aAIWGZEOH+BXjozcvE
eGBwjU/VRQYu6itR28PaNhNVji4D5ITaGxWWiycqK1EUaFraWHtk7W100ROX69xTeFVZP86D
2ymi/aohl5Vb1vlYHdqlbgqjDRl9dPbTxVCXEHf+jkexcuwlLTvr7F+5DIN6c/EbCpRqQx3e
dy193L48OGyRDh1/Wmzpew0VWWAWOSXGl/P9VzXf3Z6GPt7flN/V9iEJAa3Mo+w+eIdzJkHB
WR+yJcqQcCRMMSyishMwLDGCAqcwggKjAgEBMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoT
CklFQ0EsIEluYy4CCQCdWMxKNutUeTAJBgUrDgMCGgUAoIIBTTAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzEwMTkxODQwMDJaMCMGCSqGSIb3DQEJBDEW
BBQWydTX9iGwu22SFhw24aNkT7yd4TA+BgkrBgEEAYI3EAQxMTAvMCIxCzAJBgNVBAYTAlVT
MRMwEQYDVQQKEwpJRUNBLCBJbmMuAgkAnVjMSjbrVHkwQAYLKoZIhvcNAQkQAgsxMaAvMCIx
CzAJBgNVBAYTAlVTMRMwEQYDVQQKEwpJRUNBLCBJbmMuAgkAnVjMSjbrVHkwbAYJKoZIhvcN
AQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3
DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG
9w0BAQEFAASCAQBcuK93I1aoS0tyQ0kS5WaywfyJvtLnZUtpuSu0EHIDAEDSd9/ujxLZUQ/1
XLVtj+baCl7UtZEB7GOD92vKaOXUJK57aW6pTwxAR8YiUYDz/yXDDnse2KGxzYyETBL+nn1H
GU7EGN9P0QDYJ6ANVBFNmCTo/bbFoAuREcTWzQ8HcxhMNUMlk5xmL4QjJO5rCIrRjiUsG7QK
Z3wtS7J8qHt1OFnNtcuCG1FhVY1g+tWgj1CCItqeYYpbuasdLiriFep6cgetEpodX2It83oV
wQStyp+K++0zE4cRBWMNomj6K/E+MG7vfDqrH5eXaQOjmQiZkgBko7zcd4qgvH2qOwJ8AAAA
AAAA
--------------ms030302080304040304080202--

From sm@resistor.net  Sat Oct 19 12:04: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 22E4B11E827A for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.704
X-Spam-Level: 
X-Spam-Status: No, score=-102.704 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 tgQzbnLv5DxH for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:04:37 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id 2978521F9F7F for <ietf@ietf.org>; Sat, 19 Oct 2013 12:04:34 -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 r9JIo2gS017859; Sat, 19 Oct 2013 11:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382208634; bh=2WVvcixZUADHAaWwj0lIJdj1VpQMwA03YECerawhG1U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=m3u99gwsyDIiH4uzV3AOXVwg3nomi4xNLxlNj3QiBxMci90xOWhKMTPyvvZ2WaYpa xMSRmtGY4+Xm0+SzSGhF6z189ttmFngRuD1kSLuuL/iIRXAqHaMHG5uBsb0QKAuLHb amiAaF7m97xGIK48lIbBclgHPxUsOy6zasdHk9X0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382208634; i=@resistor.net; bh=2WVvcixZUADHAaWwj0lIJdj1VpQMwA03YECerawhG1U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SFOT8QvEjCjGkqpTIsSuJX2lzX2vsD9zkpFpSMlwcAQuzwJxfEB/qUreB1cz0R26T wAmn0geJKp7YjYuseRwZDuac2b5YxFia/iODmqyjkL/QyJuGa0jWbiBWmFLD2Jxqjd lS2sxvGjhazSt+os9RbnQDJ3gIxkHfxoSaLowupI=
Message-Id: <6.2.5.6.2.20131019101221.0cad59b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 19 Oct 2013 11:40:08 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Outstanding reviewers (was: Proper credit for work done -- on finding chairs)
In-Reply-To: <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>
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, 19 Oct 2013 19:04:41 -0000

At 15:52 17-10-2013, John C Klensin wrote:
>I had promised I was through for today, but I just had a wild,
>crazy, suggestion that follows on the retirement of the xx99 and
>xx00 subseries of RFCs.

I missed the above the first time I read the message.  Fortunately, I 
read the message again and I noticed "wild, crazy". :-)

RFC authors get credit in the IETF system.  Reviewers don't get much 
credit in the IETF system even though the system would not work 
without reviewers.  The American Physical Society has an Outstanding 
Referee program to express its appreciation to reviewers.  The 
reviewers are selected based on the quality, number, and timeliness 
of their reviews.

There was a comment from Loa Andersson: the public has a "right to 
know" who reviewed a document.  There are times when I wondered who 
let a draft through as I was not comfortable asking a person to 
review a draft if there hasn't been any effort to review it 
previously.  Some of that information may be available in the 
datatracker but it is freeform text.  Some changes would have to be 
done for the document shepherd to be able to add who reviewed a draft 
and a link to where the review was posted.

It may be possible to use the data (see previous paragraph) to 
identify outstanding reviewers by area.  The IETF can express its 
appreciation by publishing a yearly list or an xx99 list (see comment 
from John Klensin).

Regards,
-sm 


From jabley@hopcount.ca  Sat Oct 19 12:17:41 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 8EA3111E8264 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.075, 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 rys0ILJGApOq for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:17:41 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6421711E8275 for <ietf@ietf.org>; Sat, 19 Oct 2013 12:17:37 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id i18so352421oag.6 for <ietf@ietf.org>; Sat, 19 Oct 2013 12:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-type; bh=rsXdKnjeBkpChn2mz/Nv2MclIdanlk4PE/i5k0oRWz0=; b=amNadKErLiBf2NZa7upVchBx/VAmLct/ti0wz5aYjqABNljVlCoT+YacK3+Fnkk7DE +Sfa6eZ7rDRPQfRgLrxq/z1blKbp1z8KpZJIi1/cOJW1X0pOic7f6N0bKyxmUBMsB0+B C/B1YlmW7V6Hn3ouOb51QOonL3JpWIaRNzQCc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-type; bh=rsXdKnjeBkpChn2mz/Nv2MclIdanlk4PE/i5k0oRWz0=; b=Gj5Qor7+UlwH04sFoTFJ71/A8/UgpObmYJPMXQ90qJc+HSz7B84kp8H7zq5L1Bg9kd Uv3JfL9mTRxoCvSCiOwbGheUOzXlYurmPKwHtGYBRFMkSJ+TFCHmxJY4VN+sFY8jI4dd E80UvwBpRH2W/Nh49eFX1GkRBGO4Rde6ftN8QQO84FMakHKV7CDV/8qhMIyZuIZY9ojm 19aGvfcIOw/DZzWEQmbLTE2rDwi1SugyuE4SGXm6lUiNXOtWUu7xSV7Lat695bzgC6YR KtdRBVuqMD6rpPqtVIqdDVcHZSfVLJ4NQ/xBXY3pOsTaSqKNTYPMCm7xsOgHfXXaDGAU EQZw==
X-Gm-Message-State: ALoCoQkckRm4Avsa8Zijeq1SVn+6CDXIF2+JG6wndeNEoA0KvaK5RgkA6HOiwHHjRy4pugIvZRf8
X-Received: by 10.182.71.82 with SMTP id s18mr13333397obu.9.1382210248333; Sat, 19 Oct 2013 12:17:28 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <6.2.5.6.2.20131019101221.0cad59b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20131019101221.0cad59b8@resistor.net>
Date: Sat, 19 Oct 2013 15:17:29 -0400
Message-ID: <3277055073421470007@unknownmsgid>
Subject: Re: Outstanding reviewers (was: Proper credit for work done -- on finding chairs)
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@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: Sat, 19 Oct 2013 19:17:41 -0000

> On Oct 19, 2013, at 15:04, SM <sm@resistor.net> wrote:
>
> RFC authors get credit in the IETF system.  Reviewers don't get much credit in the IETF system even though the system would not work without reviewers.

Not to contradict you at all (I like where you're going with this) but
I've noticed that the diligence with which authors maintain the
acknowledgements sections if their documents is quite variable.

I realise it's not structured data, but it's what we have; it would be
good, I think, if working group chairs, document shepherds and
responsible ADs asked specifically about the text in that section and
encouraged/reminded authors to make sure it is complete.

This does not get us where you infer we might be aiming, but I think
it would be a step in the right direction.


Joe

From trammell@tik.ee.ethz.ch  Sat Oct 19 12:36:07 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5916711E821D for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.329
X-Spam-Level: 
X-Spam-Status: No, score=-5.329 tagged_above=-999 required=5 tests=[AWL=-1.030, BAYES_00=-2.599, MANGLED_SMALL=2.3, 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 ky5+abkQPW7E for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:36:02 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 443CC11E81DB for <ietf@ietf.org>; Sat, 19 Oct 2013 12:36:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 985DAD9303; Sat, 19 Oct 2013 21:36:01 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id diZqNOLgpR-r; Sat, 19 Oct 2013 21:36:01 +0200 (MEST)
Received: from Zephyr.local (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 283B0D9302; Sat, 19 Oct 2013 21:36:01 +0200 (MEST)
Message-ID: <5262DF1E.2050606@tik.ee.ethz.ch>
Date: Sat, 19 Oct 2013 21:35:58 +0200
From: Brian Trammell <trammell@tik.ee.ethz.ch>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Outstanding reviewers
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <6.2.5.6.2.20131019101221.0cad59b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20131019101221.0cad59b8@resistor.net>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig365E97FAA9D321BECA8D1A27"
Cc: John C Klensin <john-ietf@jck.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: Sat, 19 Oct 2013 19:36:07 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig365E97FAA9D321BECA8D1A27
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

hi SM, all,

In my previous message on the subject
(http://www.ietf.org/mail-archive/web/ietf/current/msg83204.html) I'd
considered using the datatracker to improve the "assignment" or at least
tracking the of coverage of reviews of documents. I'd thought of this
primarily as a method to reduce final review workload (in the context of
CHANGING THE JOB), but this would be another very good reason to add
reviewer information to the datatracker.

More inline.

SM wrote:
> At 15:52 17-10-2013, John C Klensin wrote:
>> I had promised I was through for today, but I just had a wild,
>> crazy, suggestion that follows on the retirement of the xx99 and
>> xx00 subseries of RFCs.
>=20
> I missed the above the first time I read the message.  Fortunately, I
> read the message again and I noticed "wild, crazy". :-)
>=20
> RFC authors get credit in the IETF system.  Reviewers don't get much
> credit in the IETF system even though the system would not work without=

> reviewers.  The American Physical Society has an Outstanding Referee
> program to express its appreciation to reviewers.  The reviewers are
> selected based on the quality, number, and timeliness of their reviews.=

>=20
> There was a comment from Loa Andersson: the public has a "right to know=
"
> who reviewed a document.=20

This is a very good point.

> There are times when I wondered who let a
> draft through as I was not comfortable asking a person to review a draf=
t
> if there hasn't been any effort to review it previously.  Some of that
> information may be available in the datatracker but it is freeform
> text.=20

This is a problem with any approach to review tracking using the
datatracker -- if it's not done consistently nobody will come to rely on
it. More automated tool support would help with consistency.

> Some changes would have to be done for the document shepherd to
> be able to add who reviewed a draft and a link to where the review was
> posted.

A first pass at this would simply note reviewer, date, document
revision, and sections covered, along with the content of the review
(which, if incoming references to mailing list archives are considered
to be stable, which they should, could in most cases simply be a URL).
That would be sufficient for identifying reviewers, and would probably
do a lot to support triage of well-reviewed from poorly-reviewed
documents before they get sent up to the IESG.

> It may be possible to use the data (see previous paragraph) to identify=

> outstanding reviewers by area.=20

Yep.

> The IETF can express its appreciation by
> publishing a yearly list or an xx99 list (see comment from John Klensin=
).

Regardless of how the recognition gets disseminated, there's a lot of
value in starting to collect the data.

Cheers,

Brian


--------------enig365E97FAA9D321BECA8D1A27
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCgAGBQJSYt8fAAoJENt3nsOmbNJcMYcH/2XmMql2NQaRJy9IzD0pBAcz
lT4u//6AUS4FP4vBX6CLo74RwQf/UOYt+bn7FJZUx+ICwR0Vl/t2o+Ac4ZbCJJhX
30CSGHKYIzwpqeZJ3FB+XZine6tcLPbERhbLDgNV+OmyOLF3+bVNau31aINNpoiw
SHx80VsH5N7+eGlCa8vJANvKV2HSIf/FENJqdXmSKiNDEt6reUh0uETjW5iFyKbu
YnJK1cpJ4dSzpStlG/7BiG2dAerR1ABK96551PMm+vh/sF1aii2Pq13ln4zXHJ4z
M0LnsAMBz0C/BHLFkn4Gc2LUxm+AL+nGsWN+rRvwElb+MncIBVAAJOs0KBfmT2Y=
=ntKY
-----END PGP SIGNATURE-----

--------------enig365E97FAA9D321BECA8D1A27--

From tjc@ecs.soton.ac.uk  Sat Oct 19 12:38:37 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 A2CC811E827F for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:38:37 -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=[AWL=-0.000, 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 BxW0NOG7Utx3 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 12:38:36 -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 A836E11E81DB for <ietf@ietf.org>; Sat, 19 Oct 2013 12:38:28 -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 r9JJcMV5008513 for <ietf@ietf.org>; Sat, 19 Oct 2013 20:38:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9JJcMV5008513
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382211503; bh=JvNJn47Wb28mUOWCPFy/pEIXuTQ=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=u/SKjoRqiOX7+chts5dgm9IQBJJuXRG3woYMo/HkTe9lPKnGynp6I1t7y4jXELQIm ZjK6IYE0ZykoyO6fej+Lo1H4V6OFuc/mdV3J0KLCOKDRqsc8C4gUAQXn4NjRfyOznO x3dKzcZgm/ktu+GEUvj0u1dXVm/jldxvrE7JVixU=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9IKcM0959659443Vc ret-id none; Sat, 19 Oct 2013 20:38:23 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9JJb1RN015040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 19 Oct 2013 20:37:02 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AB7392BD-1975-40B8-8411-A1109C888DC0"
Message-ID: <EMEW3|20da4629afd47147898de376481d9bfcp9IKcM03tjc|ecs.soton.ac.uk|1B63544C-7A13-4C91-9C70-CEF9A9436F73@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Date: Sat, 19 Oct 2013 20:37:02 +0100
References: <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <20131019165146.12433.qmail@joyce.lan> <07cc01ceccec$03f77420$0be65c60$@olddog.co.uk> <5262BBE4.6060202@gmail.com> <1B63544C-7A13-4C91-9C70-CEF9A9436F73@ecs.soton.ac.uk>
To: ietf@ietf.org
In-Reply-To: <5262BBE4.6060202@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9IKcM095965944300; tid=p9IKcM0959659443Vc; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9JJcMV5008513
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: Sat, 19 Oct 2013 19:38:37 -0000

--Apple-Mail=_AB7392BD-1975-40B8-8411-A1109C888DC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 19 Oct 2013, at 18:05, Melinda Shore <melinda.shore@gmail.com> wrote:

> On 10/19/13 8:55 AM, Adrian Farrel wrote:
>> Presume that it is not an issue for existing ADs (else they wouldn't =
have got there).
>> Maybe anyone who was thinking of standing who would find this helpful =
could speak up?
>=20
> It's drifted back and forth across my radar for a number of years
> and I have to say that it would make no difference whatsoever.  I
> can't imagine that it would make any difference to academic
> candidates, either, as it would not contribute to a tenure decision
> (it's not that the document is only arguably refereed for
> publication, but that the chair or AD isn't even an author.  Some
> universities are quite picky about what counts and what doesn't
> (refereed journal articles count, textbooks don't).  I did my
> graduate work at the University of Chicago, where what were called
> "How we do it good here" papers were held in very high disregard.

It's a bit different in the UK. Things are driven by the REF exercise =
every few years, and there it's the quality of your best publications =
and any impact case studies that are a large part of the contribution. =
The universities have to meet the REF requirements. See =
http://en.wikipedia.org/wiki/Research_Excellence_Framework.

RFCs can't be used for REF, as they are not considered as academic =
publications (though the rigour applied to many RFCs can be greater than =
many conference/journals!). I suppose it *might* be possible to include =
the work done from an AD position as part of an impact case study, but I =
know of noone who has done so - I think Mark and Jon served on the IAB =
not the IESG.=20

And I expect many countries are different, e.g. not all countries have =
tenure for academics.

> At any rate, no, it would make no difference to me.  Might to someone
> else but I'm having a hard time imagining who (the issue when I was
> with the networking behemoth was time taken away from what they
> hired me for, not recognition or lack thereof).

The reason I like naming the AD/WG chair on an RFC is not for their =
credit, but to make the document provenance more explicit. It's not a =
strong preference though.

> But, as I just posted in another note, I don't see a real downside
> to adding it, and as someone else pointed out it may be useful for
> answering provenance-type questions.


The main problem remains the time (and cost) of taking on a 40-hour a =
week "job" if you accept and succeed in a nomination for an AD position, =
and what suffers in terms of teaching and research while you do so.  It =
seems less and less people can make that committment, even if their =
employers do support them.

Tim=

--Apple-Mail=_AB7392BD-1975-40B8-8411-A1109C888DC0
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 19 Oct 2013, at 18:05, Melinda Shore &lt;<a =
href=3D"mailto:melinda.shore@gmail.com">melinda.shore@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On 10/19/13 8:55 AM, Adrian Farrel wrote:<br><blockquote =
type=3D"cite">Presume that it is not an issue for existing ADs (else =
they wouldn't have got there).<br>Maybe anyone who was thinking of =
standing who would find this helpful could speak =
up?<br></blockquote><br>It's drifted back and forth across my radar for =
a number of years<br>and I have to say that it would make no difference =
whatsoever. &nbsp;I<br>can't imagine that it would make any difference =
to academic<br>candidates, either, as it would not contribute to a =
tenure decision<br>(it's not that the document is only arguably refereed =
for<br>publication, but that the chair or AD isn't even an author. =
&nbsp;Some<br>universities are quite picky about what counts and what =
doesn't<br>(refereed journal articles count, textbooks don't). &nbsp;I =
did my<br>graduate work at the University of Chicago, where what were =
called<br>"How we do it good here" papers were held in very high =
disregard.<br></blockquote><div><br></div>It's a bit different in the =
UK. Things are driven by the REF exercise every few years, and there =
it's the quality of your best publications and any impact case studies =
that are a large part of the contribution. The universities have to meet =
the REF requirements. See&nbsp;<a =
href=3D"http://en.wikipedia.org/wiki/Research_Excellence_Framework">http:/=
/en.wikipedia.org/wiki/Research_Excellence_Framework</a>.</div><div><br></=
div><div>RFCs can't be used for REF, as they are not considered as =
academic publications (though the rigour applied to many RFCs can be =
greater than many conference/journals!). I suppose it *might* be =
possible to include the work done from an AD position as part of an =
impact case study, but I know of noone who has done so - I think Mark =
and Jon served on the IAB not the =
IESG.&nbsp;</div><div><br></div><div>And I expect many countries are =
different, e.g. not all countries have tenure for =
academics.</div><div><br><blockquote type=3D"cite">At any rate, no, it =
would make no difference to me. &nbsp;Might to someone<br>else but I'm =
having a hard time imagining who (the issue when I was<br>with the =
networking behemoth was time taken away from what they<br>hired me for, =
not recognition or lack thereof).<br></blockquote><div><br></div>The =
reason I like naming the AD/WG chair on an RFC is not for their credit, =
but to make the document provenance more explicit. It's not a strong =
preference though.</div><div><br><blockquote type=3D"cite">But, as I =
just posted in another note, I don't see a real downside<br>to adding =
it, and as someone else pointed out it may be useful for<br>answering =
provenance-type questions.<br></blockquote></div><div><br></div>The main =
problem remains the time (and cost) of taking on a 40-hour a week "job" =
if you accept and succeed in a nomination for an AD position, and what =
suffers in terms of teaching and research while you do so. &nbsp;It =
seems less and less people can make that committment, even if their =
employers do support them.<div><br><div>Tim</div></div></body></html>=

--Apple-Mail=_AB7392BD-1975-40B8-8411-A1109C888DC0--

From warren@kumari.net  Sat Oct 19 13:18:55 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 C328E11E8289 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 13:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.893
X-Spam-Level: 
X-Spam-Status: No, score=-98.893 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QlajeL0Hz7Mt for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 13:18:51 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAAEE11E8275 for <ietf@ietf.org>; Sat, 19 Oct 2013 13:18:50 -0700 (PDT)
Received: from [162.178.65.124] (unknown [172.56.28.140]) by vimes.kumari.net (Postfix) with ESMTPSA id A7C561B401B5; Sat, 19 Oct 2013 16:18:49 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [IETF] Re: NOMCOM - Critical shortage of nominees for multiple areas
From: Warren Kumari <warren@kumari.net>
X-Mailer: iPhone Mail (11A501)
In-Reply-To: <5262D202.1020501@ieca.com>
Date: Sat, 19 Oct 2013 16:18:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <58078580-C20F-4257-8915-9E37350B320E@kumari.net>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com> <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com> <5262D202.1020501@ieca.com>
To: Sean Turner <turners@ieca.com>
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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: Sat, 19 Oct 2013 20:18:55 -0000

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

> On Oct 19, 2013, at 2:40 PM, Sean Turner <turners@ieca.com> wrote:
>=20
> Instead of the lottery I think Stephen and I worried more about what happe=
ns if one of us got hit by a bus ;)
>=20

Look left, look right, look left again[0].

If you see something large approaching, don't cross.

There, I solved it for you...

W
[0]: Modify for local environment...

> spt
>=20
>> On 10/18/13 10:19 AM, Allison Mankin wrote:
>> Kathleen,
>>=20
>> Thanks for the perfect explanation of why it's reasonable to run
>> against the incumbent, even if you want that person to be selected
>> again.
>>=20
>> Allison (for the Nomcom)
>>=20
>> On Fri, Oct 18, 2013 at 8:40 AM, Moriarty, Kathleen
>> <kathleen.moriarty@emc.com> wrote:
>>> It is important for multiple people to run even when there is an incumbe=
nt for a fair process.  When Stephen Farrell ran for Sec AD again last year,=
 he encouraged me to accept the nomination and run against him so that there=
 was a good candidate to make the process a bit more fair.  If either Stephe=
n of Sean won the lottery, the Noncom would at least have gone through the i=
nterview and review process with other candidates in advance.  The candidate=
 would have worked through the possibility of what this meant with their job=
 and that it was possible for them to take on this role (not insignificant f=
or many of us).  For me, I thought Stephen was doing a fine job and am glad h=
e was put back on the IESG, but it is good for the Noncom to have options an=
d backup plans.  I received approval from my company, but let my management k=
now that it was unlikely that I would be selected since incumbents usually r=
eturn.
>>>=20
>>> Maybe folks should consider running against an incumbent.  You learn the=
 process and it forces you to figure out if you are interested in the role a=
nd could allocate that time to the IETF.  I gave a positive review of Stephe=
n when running against him.
>>>=20
>>> Thanks,
>>> Kathleen
>>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of E=
rsue, Mehmet (NSN - DE/Munich)
>>> Sent: Friday, October 18, 2013 6:36 AM
>>> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
>>> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
>>>=20
>>> Hi Allison,
>>>=20
>>> in your model you don't count those people who have been rejecting to a n=
omination, just because they believe the current AD did a very good job and h=
e/she should be reelected.
>>>=20
>>> So the situation is not that bad, if there is only the current AD on the=
 nominee list.
>>>=20
>>> Cheers,
>>> Mehmet
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org
>>>> [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair
>>>> 2013
>>>> Sent: Thursday, October 17, 2013 4:25 PM
>>>> To: IETF Announcement List
>>>> Cc: IETF Discuss
>>>> Subject: NOMCOM - Critical shortage of nominees for multiple areas
>>>>=20
>>>> [Catchier Subject line - apologies to those offended by a duplicate]
>>>>=20
>>>> A critically low number of people have accepted nominations for some
>>>> of the IESG open positions.  There is only one nominee per slot in
>>>> APP, OPS and TSV, only two in INT and RAI.  Many folks have declined no=
minations.
>>>>=20
>>>> While the Nomcom appreciates that support for two years of intense
>>>> service is hard to assure, and while we are aware that there is much
>>>> support for the incumbents who are standing, the IETF should
>>>> continually be considering which new talent is available for our
>>>> leadership, and the Nomcom process needs for there to be some review an=
d deliberation.
>>>>=20
>>>> Therefore, we urgently request that more nominees come forward.
>>>>=20
>>>> DEADLINES
>>>> Nominations - October 18
>>>> Questionnaires from nominees - October 25
>>>>=20
>>>> Not coincidentally, this is a good time to think over and send your
>>>> comments about the current statements of desired expertise of
>>>> positions - this is part of the Nomcom's annual review process as well.=
  Send them to nomcom13@ietf.org.
>>>>=20
>>>> Definitive location [*] of the current statements on desired expertise:=

>>>>       https://datatracker.ietf.org/nomcom/2013/expertise/
>>>>=20
>>>> Instructions and details on nomination [**]:
>>>>       https://datatracker.ietf.org/ann/nomcom/60602/
>>>>=20
>>>> Thanks, everyone,
>>>>=20
>>>> Allison for the Nomcom
>>>>=20
>>>> [*] This year the Nomcom tools were recoded, and also transitioned
>>>> into the datatracker.  Apologies for a number of places where we
>>>> didn't catch reference errors.
>>>>=20
>>>> [**] Yes, alas, the previous call for nominations used "OAM" instead
>>>> of "OPS," but we have* corrected this (chair's pilot) error where it
>>>> occurred in the Nomcom pages.
>=20

From mars.techno.cat@gmail.com  Sat Oct 19 13:58:50 2013
Return-Path: <mars.techno.cat@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 A515E11E8299 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 13:58:50 -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 RCcqj08acYzE for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 13:58:49 -0700 (PDT)
Received: from mail-vb0-x243.google.com (mail-vb0-x243.google.com [IPv6:2607:f8b0:400c:c02::243]) by ietfa.amsl.com (Postfix) with ESMTP id ED31F11E8297 for <ietf@ietf.org>; Sat, 19 Oct 2013 13:58:44 -0700 (PDT)
Received: by mail-vb0-f67.google.com with SMTP id x16so675509vbf.2 for <ietf@ietf.org>; Sat, 19 Oct 2013 13:58:42 -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=m+ahizcNgJxJ0zuXdphJdNp4fEZ1VxQPRom/VLJMMPs=; b=Xyf/0kosMVkHJJVlyfdgBr5dX0Fpn/PSNbKrSoeUSZmyOW9e8n9+lLVZMB3mblppob R+X1RK2wzbCJy6s86nMFQfDoUzGj0Q4CJ/xJZNdRBYwoT3qVwEBlxHMbyEjjbpuJBKor ED+HxywwsZmv6zSbNuNpwzBmeYVZKsH1YUVbqwXlpqszn8/3x4uSPRETE8Dsuorv5NUr K9Rp2UMVn6mfjKiluHLj16zFv2ZMI5kRGIEuZwH4+NDDYHjowqC0aDaMNyGy8LOMM6nd GkFKtqGpPC32eLW3+dlYpWBLrAaH+9w1cI+FO5AChkfD8f4ydYQUmAM4Znza0pwbYENz wrNA==
MIME-Version: 1.0
X-Received: by 10.221.6.195 with SMTP id ol3mr130856vcb.34.1382216321934; Sat, 19 Oct 2013 13:58:41 -0700 (PDT)
Received: by 10.58.44.106 with HTTP; Sat, 19 Oct 2013 13:58:41 -0700 (PDT)
Date: Sat, 19 Oct 2013 15:58:41 -0500
Message-ID: <CAK41CSRkAT+sN7hWaFsZebH0tTGpFLk40nNtLkaN5HeSwu2DkA@mail.gmail.com>
Subject: IETF (ISOC) Compensation for Indentured Servitude Engineering
From: Techno CAT <mars.techno.cat@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e013cbc8cdf29b804e91e501b
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Oct 2013 20:58:50 -0000

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

http://www.intgovforum.org
IETF Engineers & their heirs have legal claims for their work
They can Donate the Imputed Income
$250,000 to $365,000 per year appears to be the Internet Minimum Wage
That is about $1000 per day

It is not clear who is paid and what they do...some details are made public

Lynn St Amour President & CEO $632,064 + $257,943 = $890,007

Gregory M Kapfer $244,831 + $80,413 ~ $320,000
Chief Financial Officer

Walda Roseman
$176,019 + $44,853
Chief Operating Officer

Scott Hoyt $242,483 + $76,720
VP, Strategic Communications

Markus Kummer $322,793 + $84,455 ~ $400,000
VP, Public Policy

Leslie Daigle $207,199 + $56,264 ~ $260,000
Chief Internet Tech Officer

Peter Godwin $266,987 + $50,359
IT Director

Anne Lord $220,449 + $37,365
Director, Chapters

Lucy Lynch $202,728 + $54,38 ~ $250,000

http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_201112_990.pdf
IETF (ISOC) Compensation for Indentured Servitude Engineering
http://www.intgovforum.org
-- 

@Techno_CAT_r
http://Twitter.com/Techno_CAT_r

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

<div dir=3D"ltr"><div><a href=3D"http://www.intgovforum.org">http://www.int=
govforum.org</a><br>IETF Engineers &amp; their heirs have legal claims for =
their work<br>They can Donate the Imputed Income<br></div><div>$250,000 to =
$365,000 per year appears to be the Internet Minimum Wage<br>
</div><div>That is about $1000 per day<br><br></div>It is not clear who is =
paid and what they do...some details are made public<br><div><br>Lynn St Am=
our President &amp; CEO $632,064 + $257,943 =3D $890,007<br><br>Gregory M K=
apfer $244,831 + $80,413 ~ $320,000<br>
Chief Financial Officer<br><br>Walda Roseman<br>$176,019 + $44,853<br>Chief=
 Operating Officer<br><br>Scott Hoyt $242,483 + $76,720<br>VP, Strategic Co=
mmunications<br><br>Markus Kummer $322,793 + $84,455 ~ $400,000<br>VP, Publ=
ic Policy<br>
<br>Leslie Daigle $207,199 + $56,264 ~ $260,000<br>Chief Internet Tech Offi=
cer<br><br>Peter Godwin $266,987 + $50,359<br>IT Director<br><br>Anne Lord =
$220,449 + $37,365<br>Director, Chapters<br><br>Lucy Lynch $202,728 + $54,3=
8 ~ $250,000<br clear=3D"all">
<br><a href=3D"http://990s.foundationcenter.org/990_pdf_archive/541/5416504=
77/541650477_201112_990.pdf">http://990s.foundationcenter.org/990_pdf_archi=
ve/541/541650477/541650477_201112_990.pdf</a><br>IETF (ISOC) Compensation f=
or Indentured Servitude Engineering<br>
<a href=3D"http://www.intgovforum.org">http://www.intgovforum.org</a><br>--=
 <br><div dir=3D"ltr"><br>@Techno_CAT_r<br><a href=3D"http://Twitter.com/Te=
chno_CAT_r" target=3D"_blank">http://Twitter.com/Techno_CAT_r</a><br></div>
</div></div>

--089e013cbc8cdf29b804e91e501b--

From sm@resistor.net  Sat Oct 19 14:34:39 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 22C6F11E829E for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 14:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.706
X-Spam-Level: 
X-Spam-Status: No, score=-102.706 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, 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 vVy1MSYE0kcg for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 14:34:34 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDFD11E82A7 for <ietf@ietf.org>; Sat, 19 Oct 2013 14:34:33 -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 r9JKcq55022164; Sat, 19 Oct 2013 13:38:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382215161; bh=RWwGFIabz6oC/tlDA529G2zqMAmvQWD5Pm/4CNP4h5c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=s/t0CmdiEnfAnerU4vxts0j747yd8b4xgF5MmObb533N/Oip8q6wZeAMRa/gHV2Pc BC9q1ZoBkwUL4MoqBCmDuFsCiDPd9ESQdp0JavwOEIZECs+EeYhw1UzwrWeGBQ8fHB KVUlFKIltqoSSXKtj26fEP4S9nNnB2Zv87miywvc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382215161; i=@resistor.net; bh=RWwGFIabz6oC/tlDA529G2zqMAmvQWD5Pm/4CNP4h5c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LHypr5LDStl3MK2diJ/uo5uE2RSZbXtPIjaBsH8oETGTluC226/9x1+OAcWH8auRX 84YEmXHwosXjciFxahuK+wXN59TnuGQdhs6qxdsO7AIt5jACd5ADzgcg5+Dkx73E7q 0bO/n+QgU03TT92aj/RjkQA8UAQ+LVPO8pWiDhwc=
Message-Id: <6.2.5.6.2.20131019123925.0ce01bf8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 19 Oct 2013 13:38:05 -0700
To: Joe Abley <jabley@hopcount.ca>, Brian Trammell <trammell@tik.ee.ethz.ch>
From: SM <sm@resistor.net>
Subject: Re: Outstanding reviewers (was: Proper credit for work done -- on finding chairs)
In-Reply-To: <3277055073421470007@unknownmsgid>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <6.2.5.6.2.20131019101221.0cad59b8@resistor.net> <3277055073421470007@unknownmsgid>
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: Sat, 19 Oct 2013 21:34:39 -0000

At 12:17 19-10-2013, Joe Abley wrote:
>Not to contradict you at all (I like where you're going with this) but
>I've noticed that the diligence with which authors maintain the
>acknowledgements sections if their documents is quite variable.

Yes.

>I realise it's not structured data, but it's what we have; it would be
>good, I think, if working group chairs, document shepherds and
>responsible ADs asked specifically about the text in that section and
>encouraged/reminded authors to make sure it is complete.

Yes.

>This does not get us where you infer we might be aiming, but I think
>it would be a step in the right direction.

I was not thinking of the Acknowledgements section.  There is a 
document shepherd write-up.  That write-up can contain information 
about a draft, and among things the depth or breadth of the 
reviews.  A document shepherd can include the names of some reviewers 
and what they did.

At 12:35 19-10-2013, Brian Trammell wrote:
>In my previous message on the subject
>(http://www.ietf.org/mail-archive/web/ietf/current/msg83204.html) I'd
>considered using the datatracker to improve the "assignment" or at least
>tracking the of coverage of reviews of documents. I'd thought of this
>primarily as a method to reduce final review workload (in the context of
>CHANGING THE JOB), but this would be another very good reason to add
>reviewer information to the datatracker.

I read that message. :-)

>This is a problem with any approach to review tracking using the
>datatracker -- if it's not done consistently nobody will come to rely on
>it. More automated tool support would help with consistency.

Yes.

I think that it is better to let people decide whether they want to 
use the feature or not.

>A first pass at this would simply note reviewer, date, document
>revision, and sections covered, along with the content of the review
>(which, if incoming references to mailing list archives are considered
>to be stable, which they should, could in most cases simply be a URL).
>That would be sufficient for identifying reviewers, and would probably
>do a lot to support triage of well-reviewed from poorly-reviewed
>documents before they get sent up to the IESG.

I would keep it simple; I only need the email address and the link to 
the public message to generate a report.  The information is included 
for transparency reasons.  I did not mention sections covered to 
avoid complexity.

>Regardless of how the recognition gets disseminated, there's a lot of
>value in starting to collect the data.

Yes.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sat Oct 19 14:37:42 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 1B73511E8296 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 14:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 Fg2Y-NzPqNHE for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 14:37:41 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 7A85F11E82B7 for <ietf@ietf.org>; Sat, 19 Oct 2013 14:37:40 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id g10so5071602pdj.7 for <ietf@ietf.org>; Sat, 19 Oct 2013 14:37:33 -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:content-type:content-transfer-encoding; bh=oCwM48OgjZr0E059/7gO1LNiI48CFxChjj4gZUoVcgE=; b=i6JqVWldbXwkFyQPrYZSpM364CxMxYBsCcsbLlpD8kXuYl+nQOeEsf+htKAave8CW2 2mxut3OI6CcfqwXVpeMtlxcPNjxIztEYuZ2oJ6LPaNBOK64zVfRzyj7bU/0GXbRTkpTM GijnUb5eydo+yF4EZjLha44wLmukAyrkTobgCQjFF4dyqgHfvYlolbOWoI1kq6uUiELp OXvKoHYvNFIt7qtIjx1cQCFK3pgRsHE4PBJJRGTPYl1Cs174vV/cy4mc6as3iLfJc0Ci MOA2XL/X/4SNfAaI5pCJChWXFowciY1+9zlVyi4c7r57pUKzMXsThJFKXMlgW/dNil6/ OZaw==
X-Received: by 10.66.139.166 with SMTP id qz6mr10357624pab.88.1382218652928; Sat, 19 Oct 2013 14:37:32 -0700 (PDT)
Received: from [192.168.178.20] (122.201.69.111.dynamic.snap.net.nz. [111.69.201.122]) by mx.google.com with ESMTPSA id bt1sm10801939pbb.2.2013.10.19.14.37.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 19 Oct 2013 14:37:32 -0700 (PDT)
Message-ID: <5262FB95.8080500@gmail.com>
Date: Sun, 20 Oct 2013 10:37:25 +1300
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: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Sergeant at arms: please deal with mars.techno.cat@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, 19 Oct 2013 21:37:42 -0000

Hi Jordi,

We seem to have a new troll using the address mars.techno.cat@gmail.com

Can you deal with it appropriately, please?

Thanks

    Brian


From mohta@necom830.hpcl.titech.ac.jp  Sat Oct 19 16:44:44 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 19E9C11E82EE for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 16:44:44 -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 vIvCNQ30RDQ5 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 16:44:36 -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 2A21A21F9F19 for <ietf@ietf.org>; Sat, 19 Oct 2013 16:44:20 -0700 (PDT)
Received: (qmail 93242 invoked from network); 19 Oct 2013 23:38:37 -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; 19 Oct 2013 23:38:37 -0000
Message-ID: <526318C9.2000808@necom830.hpcl.titech.ac.jp>
Date: Sun, 20 Oct 2013 08:42:01 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>,  draft-ietf-6man-oversized-header-chain.all@tools.ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-6man-oversized-header-chain-08
References: <CE84AB92.6F47%peter@akayla.com>
In-Reply-To: <CE84AB92.6F47%peter@akayla.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.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, 19 Oct 2013 23:44:46 -0000

Peter Yee wrote:

> Summary: This draft is almost ready for publication as a proposed
> standard but has open issues, described in the review.

The draft is totally broken, because ICMPv6 PTB generated against
a 1280B packet, port numbers of which is located at very end
of the packet, lacks the port numbers, which makes transport
layer PMTUD fail.

If a firewall exists and the ICMPv6 is generated behind the
firewall, the firewall will likely drop the ICMPv6, because
it can not recognize the transport identity of the inner
packet, but that is a minor issue.

The essential problem is that transport layer PMTUD can not get
proper information from ICMPv6.

Though there are other causes to make PMTUD fail, which means
6man should obsolete PMTUD, they don't validate the draft.

						Masataka Ohta

PS

ICMPv6 error is, in a sense, IP over IP.

From hgs@cs.columbia.edu  Sat Oct 19 18:19:33 2013
Return-Path: <hgs@cs.columbia.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 EB05021F9FAB for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 18:19:33 -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, 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 B-s3yc1yIdGi for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 18:19:27 -0700 (PDT)
Received: from buckwheat.cc.columbia.edu (buckwheat.cc.columbia.edu [128.59.72.251]) by ietfa.amsl.com (Postfix) with ESMTP id D5AF221F9F80 for <ietf@ietf.org>; Sat, 19 Oct 2013 18:19:26 -0700 (PDT)
Received: from hazelnut (hazelnut.cc.columbia.edu [128.59.213.250]) by buckwheat.cc.columbia.edu (8.13.8/8.13.8) with ESMTP id r9K1HTta026948; Sat, 19 Oct 2013 21:19:25 -0400
Received: from hazelnut (localhost.localdomain [127.0.0.1]) by hazelnut (Postfix) with ESMTP id 9D4226C; Sat, 19 Oct 2013 21:19:25 -0400 (EDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by hazelnut (Postfix) with ESMTP id 7C0626C; Sat, 19 Oct 2013 21:19:25 -0400 (EDT)
Received: from upstairs-3.home (pool-74-102-30-128.nwrknj.fios.verizon.net [74.102.30.128]) (user=hgs10 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r9K1JKBO024393 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 19 Oct 2013 21:19:24 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org>
Date: Sat, 19 Oct 2013 21:19:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <91D61526-466D-4E81-9D3C-528501F3488D@cs.columbia.edu>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1510)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: adrian@olddog.co.uk, 'IETF Discuss' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 01:19:34 -0000

I don't think it makes any difference in academia, but I see no problem =
with a one sentence addition in the acknowledgements section along the =
lines of "This document is a product of the FOO working group, chaired =
by Alice and Bob, within the BAR area, with Carol as the responsible =
area director.", with a suitable free-form recognition ("Only their =
periodic public floggings of the authors caused this document to be =
finished.") added as relevant. The working group is often mentioned =
already, as far as I can tell.

I personally think this would be a good social custom, just as the =
recognition of reviewers has become reasonably standard, without being =
governed by formal rules. Shepherds might ask or suggest, as needed.

In academia, WG chair and AD responsibilities would generally be =
recognized as "professional service and leadership", similar to chairing =
academic conferences, advisory committees and other service to =
professional societies. Most US institutions expect this type of =
leadership from faculty, and are flexible in what form it takes, but it =
is probably considered a secondary criterion in most places. It can, =
however, be used by writers of recommendation letters as evidence of =
community standing and that tends to have non-trivial weight. ("Alice =
served on the prestigious IESG that manages Internet standards, and in =
this role ...") At least in US tenure cases, peer letters tend to play a =
dominant role, rather than just paper or citation counting. While the =
industrial research landscape seems to be changing (less academic-like), =
this used to be the case in places like Bell Labs and IBM Research as =
well.

[I have served as a CS department chair, so this is based on personal =
experience.]

Henning

On Oct 19, 2013, at 7:41 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Oct 19, 2013, at 13:37, "Adrian Farrel" <adrian@olddog.co.uk> =
wrote:
>=20
>> I am struggling to see why name an AD on the front page.
>=20
> Yeah, sounds dangerous.  Will further increase the threshold for =
getting an RFC out :-)
>=20
> Seriously: The discussion was about WG chairs, and there it might make =
more sense.
>=20
> (But my original idea was not about changing the RFC process at all, =
but about adding accessible information to the IETF web site.)
>=20
> Gr=FC=DFe, Carsten
>=20
>=20



From loa@pi.nu  Sat Oct 19 19:35:05 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 EB0C911E8127 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 19:35: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=[AWL=1.000, 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 8oC-tkzy3TQL for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 19:34:55 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id DA4BC11E8103 for <ietf@ietf.org>; Sat, 19 Oct 2013 19:34:54 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 0B8F81802038 for <ietf@ietf.org>; Sun, 20 Oct 2013 04:34:52 +0200 (CEST)
Message-ID: <52634149.6050006@pi.nu>
Date: Sun, 20 Oct 2013 10:34:49 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk> <079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk> <493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org> <91D61526-466D-4E81-9D3C-528501F3488D@cs.columbia.edu>
In-Reply-To: <91D61526-466D-4E81-9D3C-528501F3488D@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Sun, 20 Oct 2013 02:35:05 -0000

Folks,

I like where Henning is taking this, much more appropriate than the
first page thing. Though I think the Shepherd should be mentioned
separately.

One thing I consider important is that the Acknowledgment is a place
where author might read what they want. However adding the type of text
Henning proposes does not change that.

Yes I've the experience that talking to people that for one or another
reason want to do business with me, my name on RFC and/or ID is
important. This is not only in the academic world.

/Loa

On 2013-10-20 09:19, Henning Schulzrinne wrote:
> I don't think it makes any difference in academia, but I see no problem with a one sentence addition in the acknowledgements section along the lines of "This document is a product of the FOO working group, chaired by Alice and Bob, within the BAR area, with Carol as the responsible area director.", with a suitable free-form recognition ("Only their periodic public floggings of the authors caused this document to be finished.") added as relevant. The working group is often mentioned already, as far as I can tell.
>
> I personally think this would be a good social custom, just as the recognition of reviewers has become reasonably standard, without being governed by formal rules. Shepherds might ask or suggest, as needed.
>
> In academia, WG chair and AD responsibilities would generally be recognized as "professional service and leadership", similar to chairing academic conferences, advisory committees and other service to professional societies. Most US institutions expect this type of leadership from faculty, and are flexible in what form it takes, but it is probably considered a secondary criterion in most places. It can, however, be used by writers of recommendation letters as evidence of community standing and that tends to have non-trivial weight. ("Alice served on the prestigious IESG that manages Internet standards, and in this role ...") At least in US tenure cases, peer letters tend to play a dominant role, rather than just paper or citation counting. While the industrial research landscape seems to be changing (less academic-like), this used to be the case in places like Bell Labs and IBM Research as well.
>
> [I have served as a CS department chair, so this is based on personal experience.]
>
> Henning
>
> On Oct 19, 2013, at 7:41 AM, Carsten Bormann <cabo@tzi.org> wrote:
>
>> On Oct 19, 2013, at 13:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>>
>>> I am struggling to see why name an AD on the front page.
>>
>> Yeah, sounds dangerous.  Will further increase the threshold for getting an RFC out :-)
>>
>> Seriously: The discussion was about WG chairs, and there it might make more sense.
>>
>> (But my original idea was not about changing the RFC process at all, but about adding accessible information to the IETF web site.)
>>
>> Grüße, Carsten
>>
>>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From mnot@mnot.net  Sat Oct 19 20:03:44 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 F024711E812F for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:03:44 -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=-4.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 dzrV9fv-CNFV for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:03:39 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id C90D011E8103 for <ietf@ietf.org>; Sat, 19 Oct 2013 20:03:39 -0700 (PDT)
Received: from mnot-air.mnot.net (unknown [118.209.145.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 47FFA509B5; Sat, 19 Oct 2013 23:03:36 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20131019165146.12433.qmail@joyce.lan>
Date: Sun, 20 Oct 2013 14:03:33 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
References: <20131019165146.12433.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1510)
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 03:03:45 -0000

On 20/10/2013, at 3:51 AM, John Levine <johnl@taugh.com> wrote:

> If you go back to my original message on this topic, the issue was
> that in many organizations, for better or worse, they measure your
> productivity by the amount of author credit you get, which is why we
> see scientific papers with 50 or more co-authors.

We're not publishing academic papers here, we're creating Internet =
Standards. If a spec doesn't have enough market demand to have someone =
pony up WG chair resources to help it through the process, maybe that =
should tell us something.

Playing devil's advocate, you understand.

Cheers,

--
Mark Nottingham   http://www.mnot.net/




From loa@pi.nu  Sat Oct 19 20:19:38 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 10AA221F9E9D for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 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 lgDwpy4umm74 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:19:33 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 306CC21F9ECE for <ietf@ietf.org>; Sat, 19 Oct 2013 20:19:29 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 C04411802038; Sun, 20 Oct 2013 05:19:26 +0200 (CEST)
Message-ID: <52634BBB.8010108@pi.nu>
Date: Sun, 20 Oct 2013 11:19:23 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <20131019165146.12433.qmail@joyce.lan> <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
In-Reply-To: <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, John Levine <johnl@taugh.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: Sun, 20 Oct 2013 03:19:38 -0000

mark,

I think you underestimate the wg chair effort even it there is a
market stallion, maybe especially if there is.

/loa

On 2013-10-20 11:03, Mark Nottingham wrote:
>
> On 20/10/2013, at 3:51 AM, John Levine <johnl@taugh.com> wrote:
>
>> If you go back to my original message on this topic, the issue was
>> that in many organizations, for better or worse, they measure your
>> productivity by the amount of author credit you get, which is why we
>> see scientific papers with 50 or more co-authors.
>
> We're not publishing academic papers here, we're creating Internet Standards. If a spec doesn't have enough market demand to have someone pony up WG chair resources to help it through the process, maybe that should tell us something.
>
> Playing devil's advocate, you understand.
>
> Cheers,
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From prvs=0998cb80ff=johnl@taugh.com  Sat Oct 19 20:24:40 2013
Return-Path: <prvs=0998cb80ff=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D29D21F9FCA for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 NuCnt+0EfVFy for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 20:24:36 -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 4071A11E8131 for <ietf@ietf.org>; Sat, 19 Oct 2013 20:24:30 -0700 (PDT)
Received: (qmail 49016 invoked from network); 20 Oct 2013 03:24:29 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Oct 2013 03:24:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type:user-agent:cleverness; s=52634ced.xn--yuvv84g.k1310; i=sendmail-bs@submit.iecc.com; bh=UyYkikgWnEflcxgXP43urqGiEfG+1Ey79VGLVS/kQdw=; b=EuEX2hD8Na7FlAS4IsFmUtcESJG79j3D0kj2Jyg57QulykPSk4q79TkxcRrnWxLFgERdK1L9P70ldNJN0LanJyMXiNCDzSvVkuiurYj8aKiCNfew4+M3IMjIDV8pUMVg/PSXc0P5I5+UYYC8RIS7ecrbCoAuEVRKo0+iJOaaioB9bJ+t8eX0eGbm3JyOu/b/WJNeI/rW+/ySCQl/Pp/EOLvsv/RRcy/lcXtp6Z3ZhA4peb9px2vUPI1d+7SCktIQ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type:user-agent:cleverness; s=52634ced.xn--yuvv84g.k1310; olt=sendmail-bs@submit.iecc.com; bh=UyYkikgWnEflcxgXP43urqGiEfG+1Ey79VGLVS/kQdw=; b=i6ojVX+sod7xO1ObCeH9uisHOhqIJTJvCu8+yz04EFyjMNTRY74sW6QK0WxGLsEYhvMjsjwyK5AAEuBzR5Zudo99v9MObLCbnNxI/e6EMLaaLvkSSJyMz0J+kBz9AU2cq5/I5lSni1pZcTNrXnrzy0h+ie9j0r+LpDuRTnMh9tRYOiCTAFZTk5O89p3dwLNtJgQKO5FmDqoRW1APyqePXHa4oHNNeMRQfoFunCRtO6LblQShL5WhxLEzAB8h4vR0
Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Oct 2013 03:24:29 -0000
Date: Sat, 19 Oct 2013 23:24:29 -0400 (EDT)
From: John R Levine <johnl@taugh.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
In-Reply-To: <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
Message-ID: <alpine.BSF.2.00.1310192320280.14332@joyce.lan>
References: <20131019165146.12433.qmail@joyce.lan> <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 03:24:40 -0000

>> If you go back to my original message on this topic, the issue was
>> that in many organizations, for better or worse, they measure your
>> productivity by the amount of author credit you get, which is why we
>> see scientific papers with 50 or more co-authors.
>
> We're not publishing academic papers here, we're creating Internet Standards. If a spec doesn't have enough market demand to have someone pony up WG chair resources to help it through the process, maybe that should tell us something.
>
> Playing devil's advocate, you understand.

The problem is that as things currently stand, we're dependent on large 
institutions to pay their employees to be ADs.  Even were someone to want 
me to be an AD (I'm not holding my breath), I'm self employed, I couldn't 
afford it unless some third party paid my bills.

That means that we're at the mercy of managers and tenure committes and 
such who don't necessarily know much about the IETF.  Whatever we can do 
to help them understand that a) it's a lot of work and 2) it's worth it 
seems worthwhile to me.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From fluffy@cisco.com  Sat Oct 19 22:40:57 2013
Return-Path: <fluffy@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 EC45311E815A for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:40:56 -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, BAD_CREDIT=0.001, 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 hZqmYPGFkIjF for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:40:51 -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 B3A5911E8344 for <ietf@ietf.org>; Sat, 19 Oct 2013 22:40:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2900; q=dns/txt; s=iport; t=1382247647; x=1383457247; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=R4F93zv2GUxPtoVkeVSji5TS5avHbIn7qFqILGKaspk=; b=EpfK9r6N6Z0O5boGVXTbWcvHdX2BxZds18IcZFaoujbcGQM2Pg+5KptA k2p9xk4odZyqm4rGdEma/TdYcfcDB8KRvbkTwRaAoyhNhZiNDB6fJkZ/u yRevB8rP/E24NE1bsz6xtx3Ku+IM2yTKFYTA+mLd+ifGMhLLO9QbATM5a k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAHRsY1KtJXG9/2dsb2JhbABagweBDL4zgSAWdIIlAQEBAwFoEQULAgEIIiQyJQIEDgUIh3gGwASPKQIxB4MfgQoDiQePOJFRgySCKg
X-IronPort-AV: E=Sophos;i="4.93,532,1378857600"; d="scan'208";a="274261217"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 20 Oct 2013 05:40:45 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9K5ej7w009417 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Oct 2013 05:40:45 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Sun, 20 Oct 2013 00:40:45 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Thread-Topic: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Thread-Index: AQHOzVbrkNEjb37hi0S4uSnYCDEvkg==
Date: Sun, 20 Oct 2013 05:40:44 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C11@xmb-aln-x02.cisco.com>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
In-Reply-To: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E4ECE6351B5B55478EB23C2D385FDD65@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 05:40:57 -0000

Few random thoughts=20

I understand the perspective of the person you mention below but it may not=
 be a where the name goes issues. My boss wants to know if I am the person =
driving the direction of the industry or if I am the person that's managing=
 a process. The first is far more interesting.=20

I note that when I am working with conferences, they are often much more in=
terested in having a chair of WG speak than any participant of the WG. That=
 may be useful information for employers to consider when they are thinking=
 of about having an employee chair something.=20

I certainly hope all the people that substantial helped produce an RFC,  in=
cluding the Chairs, get mentioned in the Acknowledgments in a way that allo=
w the reader to correctly understand the scope and impact of their contribu=
tion.=20

Discussing what we do for chairs seems sort of nuts given we do not even li=
st all the authors that contributed substantial text on the front page, if =
there is a problem to solve one might start with making sure the authors ge=
t credit.=20

Most the documents I have done have required far more effort than any WG I =
have chaired. (Perhaps I just am a really slow at documents, or perhaps I a=
m a really bad chair, or perhaps both but FWIW, that's my experience).=20

All that said, I am really in favor of all the folks that provide useful co=
ntributions getting proper credit, but making it look like the credits for =
star wars is just going to dilute it to the point no one gets any credit fo=
r it.=20

=20


On Oct 17, 2013, at 2:47 PM, Barry Leiba <barryleiba@computer.org> wrote:

> Ted says, with respect to "Quickly replace failing WG Chairs":
>> You forgot "from a magical pool of better qualified WG chairs who
>> have the time and inclination to take on the work."
>=20
> Let me tell you about a conversation I had when I was trying to fill a
> chair position: I asked someone I thought could and would do a good
> job as chair.  She was also a proponent of the technology, and wanted
> to be a document author.  In response to, "Why not be a chair, and
> lead the effort?", part of her answer was something like this:
>=20
> "I work for a small company.  Whatever work I do on this takes away
> from what I do for them, and they want to see something tangible from
> it.  If I'm (co-)author on a document, my name, and my company's is at
> the top of the document.  I get credit for the work.  My company gets
> credit for the work.
>=20
> "If I'm a working group chair, I do more work, overall.  And, in the
> end, I get no credit for it -- my name is not on any of the documents.
> And, significantly, my company gets no credit for it whatsoever, not
> even listed in the datatracker.
>=20
> "When I go to my boss and give him the alternatives, I know which he'll p=
ick."
>=20
> Barry


From fluffy@cisco.com  Sat Oct 19 22:46:37 2013
Return-Path: <fluffy@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 8123311E8171 for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:46:37 -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 vU14UbAmy9fT for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:46:32 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 62A2F11E8344 for <ietf@ietf.org>; Sat, 19 Oct 2013 22:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=435; q=dns/txt; s=iport; t=1382247991; x=1383457591; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=qOMTvePDAqDp3WMaUqiqlgacB5RS9MNggdxcoOGoNBY=; b=VVMvSAe5YvZwVtvbAC+5TH3mHWFdOGIHroH7Nuk37g+gdclHhV/7kw1e 2f3PT0OAcGIlCy2PfN2Cqp5y92hifPG7Zpwt4oNzIcQ72ks0W2RmcjShL hpy7gikSKRP1YZC6oCnSdJaUAMMPc6w8nywg8L0eWfVf0dlG7SFGouOOM Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAMFsY1KtJV2b/2dsb2JhbABagweBDL4zgSAWdIIlAQEBAwEdVwUQAgEIIiQyJQIEDgUIh3gGwASPKzEHgx+BCgOJB6EJgWaBPoIq
X-IronPort-AV: E=Sophos;i="4.93,532,1378857600"; d="scan'208";a="274319655"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 20 Oct 2013 05:46:29 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9K5kTbH006202 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 20 Oct 2013 05:46:29 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.143]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sun, 20 Oct 2013 00:46:28 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Thread-Topic: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Thread-Index: AQHOzVe4Imryjf8uW0Wr+8ARJjV30w==
Date: Sun, 20 Oct 2013 05:46:28 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im>
In-Reply-To: <52603628.1080007@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F9D5249CA1C9774882267DE1554BE687@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 05:46:37 -0000

On Oct 17, 2013, at 12:10 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

>=20
> 1. Less/no time on document reviews.
> 2. Less time managing working groups.
> 3. Fewer working groups to manage.
> 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).
> 5. Less/no involvement with BoFs and other early-stage efforts.
> 6. Less/no involvement with creating the schedule.

Let me add fewer areas to find ADs for=20



From ynir@checkpoint.com  Sat Oct 19 22:52:27 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 ACE5811E834B for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.451
X-Spam-Level: 
X-Spam-Status: No, score=-10.451 tagged_above=-999 required=5 tests=[AWL=0.148, 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 V1zdP8rHjiSQ for <ietf@ietfa.amsl.com>; Sat, 19 Oct 2013 22:52:21 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7883F11E8171 for <ietf@ietf.org>; Sat, 19 Oct 2013 22:52:21 -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 r9K5qIV4008768; Sun, 20 Oct 2013 08:52:18 +0300
X-CheckPoint: {52636F2A-1A-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.92]) by DAG-EX10.ad.checkpoint.com ([169.254.3.173]) with mapi id 14.02.0347.000; Sun, 20 Oct 2013 08:52:06 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Topic: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
Thread-Index: AQHOzOuXBDYfcVk+ak+EnMttHWXskJn8tcqAgAAuyIA=
Date: Sun, 20 Oct 2013 05:52:06 +0000
Message-ID: <BC5D54AA-0ED0-47CF-BAA7-19D79FE6EAEB@checkpoint.com>
References: <20131019165146.12433.qmail@joyce.lan> <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
In-Reply-To: <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.184]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BE2DBEFEBD11B6448888A9484551DECA@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, John Levine <johnl@taugh.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, 20 Oct 2013 05:52:27 -0000

On Oct 20, 2013, at 6:03 AM, Mark Nottingham <mnot@mnot.net> wrote:

>=20
> On 20/10/2013, at 3:51 AM, John Levine <johnl@taugh.com> wrote:
>=20
>> If you go back to my original message on this topic, the issue was
>> that in many organizations, for better or worse, they measure your
>> productivity by the amount of author credit you get, which is why we
>> see scientific papers with 50 or more co-authors.
>=20
> We're not publishing academic papers here, we're creating Internet Standa=
rds. If a spec doesn't have enough market demand to have someone pony up WG=
 chair resources to help it through the process, maybe that should tell us =
something.

Does it ever work that way? Did a manager ever tell you, "the market needs =
a re-write of the HTTP documents, and being the good corporate citizens tha=
t we are, go ahead and volunteer to chair httpbis" ?

Even for the actual writing of drafts, there's multiple examples of resourc=
es being found for documents that the market does not demand, and for docum=
ents that are useful and it's hard to find people willing to edit/contribut=
e/review. Corporations would rationally prefer to wait for some other body =
to pony up their human resources. The only reason we have a relatively larg=
e pool of WG chairs is that the cost is low enough such that medium to larg=
e corporations can consider this "in the noise". Apparently the time alloca=
tion for an AD job is not that insignificant.

Yoav


From mnot@mnot.net  Sun Oct 20 01:31:50 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 814D511E8136 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 01:31:50 -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 HY-VPsI+7xCP for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 01:31:45 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 3A86711E8150 for <ietf@ietf.org>; Sun, 20 Oct 2013 01:31:45 -0700 (PDT)
Received: from mnot-air.mnot.net (unknown [118.209.145.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D5538509B5; Sun, 20 Oct 2013 04:31:42 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <BC5D54AA-0ED0-47CF-BAA7-19D79FE6EAEB@checkpoint.com>
Date: Sun, 20 Oct 2013 19:31:40 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DA7A9BA-1E4A-49D1-A267-65BB3A5BE8DF@mnot.net>
References: <20131019165146.12433.qmail@joyce.lan> <1B17D2FF-7D4F-4779-96AE-902F728F789D@mnot.net> <BC5D54AA-0ED0-47CF-BAA7-19D79FE6EAEB@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1510)
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, John Levine <johnl@taugh.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, 20 Oct 2013 08:31:50 -0000

On 20/10/2013, at 4:52 PM, Yoav Nir <ynir@checkpoint.com> wrote:

> Does it ever work that way? Did a manager ever tell you, "the market =
needs a re-write of the HTTP documents, and being the good corporate =
citizens that we are, go ahead and volunteer to chair httpbis" ?

My manager was happy to support me when I brought it up, and both they =
and the chain above them has done so through three successive employers. =
Go figure.

> Even for the actual writing of drafts, there's multiple examples of =
resources being found for documents that the market does not demand, and =
for documents that are useful and it's hard to find people willing to =
edit/contribute/review. Corporations would rationally prefer to wait for =
some other body to pony up their human resources. The only reason we =
have a relatively large pool of WG chairs is that the cost is low enough =
such that medium to large corporations can consider this "in the noise". =
Apparently the time allocation for an AD job is not that insignificant.

Like I said, devil's advocate. However, I sometimes think starting new =
work is too easy. The trick is sorting the speculative stuff that's =
important (and likely to be successful) from that which isn't.

Cheers,

--
Mark Nottingham   http://www.mnot.net/




From adrian@olddog.co.uk  Sun Oct 20 02:25:43 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 3A14611E814F for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 02:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  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 gYZcM+XfX1VG for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 02:25:37 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 8C97A11E8279 for <ietf@ietf.org>; Sun, 20 Oct 2013 02:25:31 -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 r9K9PLYV003606;  Sun, 20 Oct 2013 10:25:21 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r9K9PKFN003585 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 20 Oct 2013 10:25:21 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Subject: RE: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
Date: Sun, 20 Oct 2013 10:25:19 +0100
Message-ID: <085801cecd76$4bb76bf0$e32643d0$@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: Ac7Ndbz+sZtMICR4Qwyix/gw4vaa1A==
Content-Language: en-gb
Cc: 'IETF Discuss' <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: Sun, 20 Oct 2013 09:25:43 -0000

Henning,

Can Carol also add "Carol thinks this is a pretty dumb idea, but since it is
mostly harmless and there is some support from people in the FOO working group
and no sustained objection she did not block its publication"?

Adrian

>I see no problem with a one
> sentence addition in the acknowledgements section along the lines of "This
> document is a product of the FOO working group, chaired by Alice and Bob,
> within the BAR area, with Carol as the responsible area director.", with a
suitable
> free-form recognition ("Only their periodic public floggings of the authors
caused
> this document to be finished.") added as relevant. The working group is often
> mentioned already, as far as I can tell.


From abdussalambaryun@gmail.com  Sun Oct 20 04:37: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 B2BB211E81B0 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 04:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.074,  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 hgNVtEhyAq1u for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 04:37:25 -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 E7D1211E819D for <ietf@ietf.org>; Sun, 20 Oct 2013 04:37:24 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so5740514pbb.41 for <ietf@ietf.org>; Sun, 20 Oct 2013 04:37:24 -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=P3uKf9i2xlmP1GMKSawl7+c3bCaNzQMTylSUCJUkC+U=; b=T9HUvJk2kDK9em3MRWWE+QF4u4iVpmqWNwiEU+FWx4w9MpPiQUI3suWBBU3CkdlCQM XIcsGo1Ute5x2onEASUAXbFC820bzE9WJbGolQZv0uMDqSCO1WJHCYcJ+JK3PETeAZmf h8C5vG7uhLm61e/vku/qvyGs9lVJvMd2gJ2CW/k03DKUuFhkIOoaUuWTjH2mTmrVKLu7 iaH6UeCIiKY7I+7a6KuAWkvBnu6qKk4KfzpD1VN9xXtg73K1R0wRYYqPvIhvPAxlVYlD CRTd/a2mtu4xlrkxAJ1nEfud3B4imDx+h43KwrIsB57TTqZPQwoSElYMsTtPU5hcwmQH Hj/w==
MIME-Version: 1.0
X-Received: by 10.66.50.131 with SMTP id c3mr12557000pao.111.1382269044514; Sun, 20 Oct 2013 04:37:24 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 20 Oct 2013 04:37:24 -0700 (PDT)
Date: Sun, 20 Oct 2013 13:37:24 +0200
Message-ID: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
Subject: Separate ADs roles from IESG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: IETF Discuss <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, 20 Oct 2013 11:37:25 -0000

Refering to the Change the Job subject of AD roles:

IMHO, the weakest point in the IETF process is having ADs in the IESG,
we need different expert directors roles in there. The AD can abuse
the system in his benefits because he can do ALL types of
participations at input and output, which I never seen that in any
organisation. Some one on the IETF list suggested two paralell IESG
which is nice to separate the area-output from IESG, but I think it is
better Separate ADs from IESG to have: 1) body of ADs and 2) the body
named IESG without current ADs (it may have past ADs experts of each
area). Similar
idea of having two groups of leading but different roles.

Also I always don't like when the IESG is discussing and I see that
the AD responsible for the I-D already made his decision, I prefer
that AD should wait until all put in their decision/discussions, and
then he may say what he thinks.

The ADs SHOULD have important-things in IETF that they are not allowed
to do. I don't like this off-hat and on-hat activities, or two/three
role-images per person in one volunteer organisation.

Best Regards
AB

On 10/17/13, Dave Crocker <dhc@dcrocker.net> wrote:
> On 10/18/2013 3:54 AM, Tim Chown wrote:
>> I believe the "intense service" you mention is a significant deterrent for
>> many.
>>
>> I'm sure it's been suggested before, but is there mileage in rethinking
>> the
>> AD roles,
>
>
> It has been suggested many times.  The suggestion has been ignored.
>
> We have been having some very serious recruitment problems for a number
> of years now.  This year's crisis was entirely predictable.
>
> The only way the situation will change meaningfully is to make the job
> less onerous, and especially make it possible for the AD to continue
> doing real work for their company.
>
> ADs are senior folk.  That makes them a strategic resource for their
> company.  Or, at least, they'd better be.  Only very large companies can
> afford to lose a strategic resource for years.
>
> Looking for alternative funding does not make the job less onerous and
> does not permit the AD to continue doing real work for their company.
>
> Re-define the bloody job.  At a minimum, make the workload realistically
> no more than 50%, but I actually suggest trying for 25%, given that
> reality will increase the actual amount above that.
>
> This means taking the current list of AD tasks and deciding on the ones
> that absolutely cannot be done by others, and specifying other ways to
> do the remainder.
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

From scott.brim@gmail.com  Sun Oct 20 04:52:42 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 9E7E111E81B3 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 04:52:42 -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 vz0ttoAz2qUP for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 04:52:42 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9E33211E8164 for <ietf@ietf.org>; Sun, 20 Oct 2013 04:52:40 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id i4so4143587oah.18 for <ietf@ietf.org>; Sun, 20 Oct 2013 04:52: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:date:message-id:subject:from:to :cc:content-type; bh=b4m432cOGx7l+MIMdIzlw7bPAvGBtB1zseNAQ+zWOnY=; b=v52Ye0gM6daODbrFT9AD5FXWDyQJpgMYN6L2n6x1AUwTJSfln2FWzwN0B4NaDvjh0F iZbpqxz8/l5NFZiuyrKuikCEsSoahV/r0JhFOjPyiP/66DFICr8wYlAMesPEOPBw3jOc 7p25XGeA29TSVF+RJPqWfbc7ZKouafaTTrlEUQGc2lHYJHkE+CO7WbQLGKManLagx4Fq iuI/rEcT/SwPHz1cnuS5i8hcwM2tP87NmCO0hlDVm9jpmn/eO9kMDNYUNCvgJdvS05ex j+OcEjazKzYeVHqc3st5d3nST1lNWQfxlCZM9JKGZZr9gan8S5but7sGQ2wS//RDNi/S C54A==
MIME-Version: 1.0
X-Received: by 10.182.230.135 with SMTP id sy7mr15764341obc.24.1382269960003;  Sun, 20 Oct 2013 04:52:40 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Sun, 20 Oct 2013 04:52:39 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Sun, 20 Oct 2013 04:52:39 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com>
Date: Sun, 20 Oct 2013 07:52:39 -0400
Message-ID: <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Scott Brim <scott.brim@gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c33676f329c304e92acd3c
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, 20 Oct 2013 11:52:42 -0000

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

On Oct 20, 2013 1:46 AM, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
wrote:
>
>
> On Oct 17, 2013, at 12:10 PM, Peter Saint-Andre <stpeter@stpeter.im>
wrote:
>
> >
> > 1. Less/no time on document reviews.
> > 2. Less time managing working groups.
> > 3. Fewer working groups to manage.
> > 4. Fewer "extra" tasks (e.g., interfacing with other SDOs).
> > 5. Less/no involvement with BoFs and other early-stage efforts.
> > 6. Less/no involvement with creating the schedule.
>
> Let me add fewer areas to find ADs for

Adding more certainly doesn't help. Reducing the number could help if we
have a concomitant increase in the usefulness of directorates.  But it
doesn't solve the problem.  If we learn to adjust to having fewer ADs, and
the trend toward a smaller more homogeneous candidate pool continues, we
end up with just a Chair and maybe 1-2 ADs, plus a lot of (appointed)
"assistants".  That could work, but let's decide explicitly if that's the
trajectory we want to be on.

Scott

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

<p dir=3D"ltr"><br>
On Oct 20, 2013 1:46 AM, &quot;Cullen Jennings (fluffy)&quot; &lt;<a href=
=3D"mailto:fluffy@cisco.com">fluffy@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On Oct 17, 2013, at 12:10 PM, Peter Saint-Andre &lt;<a href=3D"mailto:=
stpeter@stpeter.im">stpeter@stpeter.im</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; 1. Less/no time on document reviews.<br>
&gt; &gt; 2. Less time managing working groups.<br>
&gt; &gt; 3. Fewer working groups to manage.<br>
&gt; &gt; 4. Fewer &quot;extra&quot; tasks (e.g., interfacing with other SD=
Os).<br>
&gt; &gt; 5. Less/no involvement with BoFs and other early-stage efforts.<b=
r>
&gt; &gt; 6. Less/no involvement with creating the schedule.<br>
&gt;<br>
&gt; Let me add fewer areas to find ADs for</p>
<p dir=3D"ltr">Adding more certainly doesn&#39;t help. Reducing the number =
could help if we have a concomitant increase in the usefulness of directora=
tes.=A0 But it doesn&#39;t solve the problem.=A0 If we learn to adjust to h=
aving fewer ADs, and the trend toward a smaller more homogeneous candidate =
pool continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot o=
f (appointed) &quot;assistants&quot;.=A0 That could work, but let&#39;s dec=
ide explicitly if that&#39;s the trajectory we want to be on. </p>

<p dir=3D"ltr">Scott <br>
</p>

--001a11c33676f329c304e92acd3c--

From ynir@checkpoint.com  Sun Oct 20 05:50: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 88DDA11E83C7 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 05:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.429
X-Spam-Level: 
X-Spam-Status: No, score=-10.429 tagged_above=-999 required=5 tests=[AWL=0.170, 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 fTB337BAnK2k for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 05:50:49 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0D211E83B8 for <ietf@ietf.org>; Sun, 20 Oct 2013 05:50:46 -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 r9KCoWhC006976; Sun, 20 Oct 2013 15:50:43 +0300
X-CheckPoint: {5263D12C-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.14]) by DAG-EX10.ad.checkpoint.com ([169.254.3.213]) with mapi id 14.03.0123.003; Sun, 20 Oct 2013 15:49:20 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Separate ADs roles from IESG
Thread-Topic: Separate ADs roles from IESG
Thread-Index: AQHOzYjG4BuTzhIUFk+7GQ0vLzw0mZn9WEWA
Date: Sun, 20 Oct 2013 12:49:19 +0000
Message-ID: <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
In-Reply-To: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.248]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9C6B6BE8367CDB439710F2ADB179D57D@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 12:50:54 -0000

Hi, AB

We don't have enough world-class experts on [insert subject here] that we c=
an delegate some of them to "administer but don't participate" roles, and s=
ome others to "review but don't participate" roles. The same goes for WG ch=
airs - if the WG is facing a contentious issue, it doesn't make sense to re=
quire the chair to shut up about it just to make the process more neutral. =
I'm afraid we'll have to live with the with-hat/without-hat thing regardles=
s of any changes to the process of the job description.

The ADs have multiple functions:
 - managing the working groups, scheduling
 - reviewing all documents
 - incubating new work - BoFs.
 - representing the IETF, "steering", community stuff.

These functions could be separated, but only at a cost of more people. And =
nobody would take any of those jobs if it means they can't speak at technic=
al meetings.

Yoav

On Oct 20, 2013, at 2:37 PM, Abdussalam Baryun <abdussalambaryun@gmail.com>=
 wrote:

> Refering to the Change the Job subject of AD roles:
>=20
> IMHO, the weakest point in the IETF process is having ADs in the IESG,
> we need different expert directors roles in there. The AD can abuse
> the system in his benefits because he can do ALL types of
> participations at input and output, which I never seen that in any
> organisation. Some one on the IETF list suggested two paralell IESG
> which is nice to separate the area-output from IESG, but I think it is
> better Separate ADs from IESG to have: 1) body of ADs and 2) the body
> named IESG without current ADs (it may have past ADs experts of each
> area). Similar
> idea of having two groups of leading but different roles.
>=20
> Also I always don't like when the IESG is discussing and I see that
> the AD responsible for the I-D already made his decision, I prefer
> that AD should wait until all put in their decision/discussions, and
> then he may say what he thinks.
>=20
> The ADs SHOULD have important-things in IETF that they are not allowed
> to do. I don't like this off-hat and on-hat activities, or two/three
> role-images per person in one volunteer organisation.
>=20
> Best Regards
> AB
>=20
> On 10/17/13, Dave Crocker <dhc@dcrocker.net> wrote:
>> On 10/18/2013 3:54 AM, Tim Chown wrote:
>>> I believe the "intense service" you mention is a significant deterrent =
for
>>> many.
>>>=20
>>> I'm sure it's been suggested before, but is there mileage in rethinking
>>> the
>>> AD roles,
>>=20
>>=20
>> It has been suggested many times.  The suggestion has been ignored.
>>=20
>> We have been having some very serious recruitment problems for a number
>> of years now.  This year's crisis was entirely predictable.
>>=20
>> The only way the situation will change meaningfully is to make the job
>> less onerous, and especially make it possible for the AD to continue
>> doing real work for their company.
>>=20
>> ADs are senior folk.  That makes them a strategic resource for their
>> company.  Or, at least, they'd better be.  Only very large companies can
>> afford to lose a strategic resource for years.
>>=20
>> Looking for alternative funding does not make the job less onerous and
>> does not permit the AD to continue doing real work for their company.
>>=20
>> Re-define the bloody job.  At a minimum, make the workload realistically
>> no more than 50%, but I actually suggest trying for 25%, given that
>> reality will increase the actual amount above that.
>>=20
>> This means taking the current list of AD tasks and deciding on the ones
>> that absolutely cannot be done by others, and specifying other ways to
>> do the remainder.
>>=20
>> d/
>>=20
>>=20
>> --
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net
>>=20


From rogerj@gmail.com  Sun Oct 20 06:05:41 2013
Return-Path: <rogerj@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 6C3DF11E81C6 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 06:05:41 -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 kQTpiuXgKQEn for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 06:05:40 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id E269611E83B8 for <ietf@ietf.org>; Sun, 20 Oct 2013 06:05:38 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id ey11so2836532wid.1 for <ietf@ietf.org>; Sun, 20 Oct 2013 06:05:38 -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=WZ8dUEeXso+BT+F0Q+9yF3/tI8AW8UbNPWY+FJlCid4=; b=CIYqr0heeivFSAJixGSP1FOSJ6HP8soXsGWUj1XDZOrtPjokLZ6ZS1qF4pv/bxixje SuN/tytMZQwKYLon730VlqyTnbvSGJuronaYupej84o0WLJLl0ZBVYeH31zffO1jnxFW G3xLSY9g4lm/Nok80mCGflJUq9DE9eKdfkSbMQkROxtsmHu2G69bHuTKMD6gbn+x3+pW aGT88+R5aKJRR5avax0vSqlwOkRNpLbBQ4WJKFx5UL2xSoIMo9Q5G9verZz2LFawI9uJ znAcUE7JGdQiupJSEKzQoIqoVRffs1KGod9pWtj5Rf3wk7ObJZEi5blQ/uXjvl3ptagj xXgA==
MIME-Version: 1.0
X-Received: by 10.194.20.202 with SMTP id p10mr1225704wje.39.1382274338052; Sun, 20 Oct 2013 06:05:38 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sun, 20 Oct 2013 06:05:37 -0700 (PDT)
In-Reply-To: <A14E3A9C-C46E-47DE-A20F-473416B6CA15@bogus.com>
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk> <94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com> <061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk> <CABCOCHSLmDx_-ofQsvrEhJi_A6nbWJRqdYrn6gHOpRaMuEG6XQ@mail.gmail.com> <A14E3A9C-C46E-47DE-A20F-473416B6CA15@bogus.com>
Date: Sun, 20 Oct 2013 15:05:37 +0200
Message-ID: <CAKFn1SGM7Xsg6eyH+u6TQr1U1w8U2Ux8V5s6wjaLzQU_eNy16A@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: joel jaeggli <joelja@bogus.com>, IETF Discuss <ietf@ietf.org>
Content-Type: text/plain; charset=windows-1252
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: Sun, 20 Oct 2013 13:05:41 -0000

On Fri, Oct 18, 2013 at 8:07 PM, joel jaeggli <joelja@bogus.com> wrote:
> On Oct 18, 2013, at 10:39 AM, Andy Bierman <andy@yumaworks.com> wrote:
>
>> Hi,
>>
>> I don't think the Assistant AD job would be easy to define
>> or even the right approach.  IMO doubling the number of ADs
>> would probably work better, although at an increased cost
>> wrt/ managing the review process. I do not agree that
>> every AD needs to review every draft. The review
>> and WG management tasks should be shared by 4 people
>> instead of 2 people.
>>
>> The problem I see is that few people are both qualified
>> and able to do full-time volunteer work for the IESG.
>> There is a disconnect between the official job requirements
>> and the real job requirements that is being ignored here.
>>
>> Perhaps if the AD job really was only 20 hours a week
>> there would be a lot more people willing and able to
>> accept a nomination.
>>
>
> For better or worse I told the nomcom that I only have 2 hours a day (7 d=
ays a  week) for this=85 They took me anyway. The load is unevenly distribu=
ted. The internet and routing and Apps ADs appear to have more  drafts to p=
rocess and more complex working group interactions, then does the ops side =
of ops and management.
>
> That said, this is not a not a full time job for me and I am not compensa=
ted for doing it. If my level of available commitment isn't adequate, I gue=
ss we'll find out between now and the 2 year mark.  My contribution to the =
things that bring me to the IETF as on operator have dropped off because I =
don't have time for them.


You're mail gave me two thoughts

1.) are our current Internet and the interconnects of thing too
complex for our current structure? Are IETF doing more than they
should in one area or another?

2.) normaly there are two reason why people stop doing things, or
don't have time for it, the normal change of interest is one thing.
The other one are probably what you're going at, no time left for
doing that.


Both of these really tell me we need to consider our structure, not
just shifting jobs or workload around. I mean, it's not the workload
alone that is causing us problems right now.
And no, I don't have any ideas right now either because I do believe
our current structure is a strength that make the quality on what we
produce to be quite high. We should not give up that quality, or lower
it...



--=20

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From loa@pi.nu  Sun Oct 20 06:48:03 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 74AE811E83F4 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 06:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.621
X-Spam-Level: 
X-Spam-Status: No, score=-102.621 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 heMiIKGqJLZo for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 06:47:58 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5AAFC11E83F3 for <ietf@ietf.org>; Sun, 20 Oct 2013 06:47:57 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 663E618014F6; Sun, 20 Oct 2013 15:47:55 +0200 (CEST)
Message-ID: <5263DF08.4090304@pi.nu>
Date: Sun, 20 Oct 2013 21:47:52 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>
In-Reply-To: <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 13:48:03 -0000

Yoav,

I was very tempted to just respond "+1", but since I often told people
that they should do more than so.

Folks,

I agree (mostly) with Yoav, but believe that we could (at least in some
cases) find people that would take these jobs. However; I'm also fairly
convinced that is also the people we don't want to have on those jobs.

I think AB demonstrates a fundamental lack of understanding of how the
IETF works; I don't think we need to discuss it further.

I wish I could set a troll-filter, but as wg chair I understand that I
can't do that.

/Loa

On 2013-10-20 20:49, Yoav Nir wrote:
> Hi, AB
>
> We don't have enough world-class experts on [insert subject here] that we can delegate some of them to "administer but don't participate" roles, and some others to "review but don't participate" roles. The same goes for WG chairs - if the WG is facing a contentious issue, it doesn't make sense to require the chair to shut up about it just to make the process more neutral. I'm afraid we'll have to live with the with-hat/without-hat thing regardless of any changes to the process of the job description.
>
> The ADs have multiple functions:
>   - managing the working groups, scheduling
>   - reviewing all documents
>   - incubating new work - BoFs.
>   - representing the IETF, "steering", community stuff.
>
> These functions could be separated, but only at a cost of more people. And nobody would take any of those jobs if it means they can't speak at technical meetings.
>
> Yoav
>
> On Oct 20, 2013, at 2:37 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>
>> Refering to the Change the Job subject of AD roles:
>>
>> IMHO, the weakest point in the IETF process is having ADs in the IESG,
>> we need different expert directors roles in there. The AD can abuse
>> the system in his benefits because he can do ALL types of
>> participations at input and output, which I never seen that in any
>> organisation. Some one on the IETF list suggested two paralell IESG
>> which is nice to separate the area-output from IESG, but I think it is
>> better Separate ADs from IESG to have: 1) body of ADs and 2) the body
>> named IESG without current ADs (it may have past ADs experts of each
>> area). Similar
>> idea of having two groups of leading but different roles.
>>
>> Also I always don't like when the IESG is discussing and I see that
>> the AD responsible for the I-D already made his decision, I prefer
>> that AD should wait until all put in their decision/discussions, and
>> then he may say what he thinks.
>>
>> The ADs SHOULD have important-things in IETF that they are not allowed
>> to do. I don't like this off-hat and on-hat activities, or two/three
>> role-images per person in one volunteer organisation.
>>
>> Best Regards
>> AB
>>
>> On 10/17/13, Dave Crocker <dhc@dcrocker.net> wrote:
>>> On 10/18/2013 3:54 AM, Tim Chown wrote:
>>>> I believe the "intense service" you mention is a significant deterrent for
>>>> many.
>>>>
>>>> I'm sure it's been suggested before, but is there mileage in rethinking
>>>> the
>>>> AD roles,
>>>
>>>
>>> It has been suggested many times.  The suggestion has been ignored.
>>>
>>> We have been having some very serious recruitment problems for a number
>>> of years now.  This year's crisis was entirely predictable.
>>>
>>> The only way the situation will change meaningfully is to make the job
>>> less onerous, and especially make it possible for the AD to continue
>>> doing real work for their company.
>>>
>>> ADs are senior folk.  That makes them a strategic resource for their
>>> company.  Or, at least, they'd better be.  Only very large companies can
>>> afford to lose a strategic resource for years.
>>>
>>> Looking for alternative funding does not make the job less onerous and
>>> does not permit the AD to continue doing real work for their company.
>>>
>>> Re-define the bloody job.  At a minimum, make the workload realistically
>>> no more than 50%, but I actually suggest trying for 25%, given that
>>> reality will increase the actual amount above that.
>>>
>>> This means taking the current list of AD tasks and deciding on the ones
>>> that absolutely cannot be done by others, and specifying other ways to
>>> do the remainder.
>>>
>>> d/
>>>
>>>
>>> --
>>> Dave Crocker
>>> Brandenburg InternetWorking
>>> bbiw.net
>>>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From john-ietf@jck.com  Sun Oct 20 07:18:38 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 7436711E81AF for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:18:38 -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 bgx0Ryz1PZnZ for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:18:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 56FFE11E817B for <ietf@ietf.org>; Sun, 20 Oct 2013 07:18:33 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VXtpr-0009TL-Ny; Sun, 20 Oct 2013 10:18:27 -0400
X-Vipre-Scanned: 0371D719002C310371D866-TDI
Date: Sun, 20 Oct 2013 10:18:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Loa Andersson <loa@pi.nu>, Yoav Nir <ynir@checkpoint.com>
Subject: Re: Separate ADs roles from IESG
Message-ID: <892B13B7BF164B38A8DB3793@[192.168.1.128]>
In-Reply-To: <5263DF08.4090304@pi.nu>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu>
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 Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 14:18:38 -0000

--On Sunday, 20 October, 2013 21:47 +0800 Loa Andersson
<loa@pi.nu> wrote:

> Yoav,
> 
> I was very tempted to just respond "+1", but since I often
> told people
> that they should do more than so.
> 
> Folks,
> 
> I agree (mostly) with Yoav, but believe that we could (at
> least in some
> cases) find people that would take these jobs. However; I'm
> also fairly
> convinced that is also the people we don't want to have on
> those jobs.

FWIW, I think a separation is plausible if that was what we
wanted to do. That is very different from endorsing Abdussalam's
suggestion or the reasoning (if "I don't like" is reasoning)
behind  it.   The advantages are clear and have been discussed
before, including both reducing the workload on any one set of
individuals enough that maybe we could get more people to serve
and eliminating the inherent conflict in loyalties between
taking the lead in establishing a WG and its charter, selecting
and overseeing its leadership, managing it in other ways, and
being expected to be its lead advocate to the rest of the IESG
on the one hand and providing a critical review of its work on
the other.  

I note that the roles of managing/steering and document review
and approval were originally separated (with the latter
belonging to the IAB under the old structure).  The problem with
that model at that time was that the IAB got out of touch.
Maybe, in retrospect, we had the right problem diagnosis but
partially the wrong solution.

Because working together with others on final document reviews
and providing a final verification that all necessary bits are
in place shouldn't require nearly the job-learning time that the
IESG/AD role does, one could consider asking members of that
review body to serve only a year or maybe six months, and
possibly relax the meeting attendance requirements, either of
which should vastly increase the pool of plausible volunteers,
including some people we would very much like to have in those
jobs but who can't take on the IESG workload or long-term
commitment.

For an earlier and somewhat different take on this issue and a
variation on a proposal, see the long-expired
draft-klensin-stds-review-panel-00.


> I think AB demonstrates a fundamental lack of understanding of
> how the
> IETF works; I don't think we need to discuss it further.

While I agree about the lack of understanding part (and even
more strongly about proposals rooted in what some individual
says he or she "...always don't like..." rather than a real
understanding of the IETF or organizational and SDO
decision-making generally), let's not fall into the trap of
dismissing an idea because of where it seemed to come from.  Not
only is a stopped clock correct twice a day, but the separation
idea is not original (it wasn't even original when the draft
mentioned above was posted in 2005).

best.
   john




From tjc@ecs.soton.ac.uk  Sun Oct 20 07:33:31 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 7EE4B11E81A2 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:33:31 -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=[AWL=-0.000, 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 1Ou-nubfcAxT for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:33:30 -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 6752A11E81AD for <ietf@ietf.org>; Sun, 20 Oct 2013 07:33:25 -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 r9KEXHBI009972 for <ietf@ietf.org>; Sun, 20 Oct 2013 15:33:17 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9KEXHBI009972
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382279598; bh=cJh9iSIPXpACqX0bLY/YJXa3EJA=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=R07zGYJdPryYReJjIauqcgU5JkWNquBOZKbMzs5UubfEzFtdB5h/4VWthzmTlzOQ2 qTUWeM5ej53yfdnN/5KNhuQZm1xJEfP7khYXhKvWMmeMBJerhF/fbI/CsIXSvkaCQD UTC1ENdrPcOH/Iwye9HaJGTOh5MjcO/lcZ3CfpmM=
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 p9JFXH09596637084U ret-id none; Sun, 20 Oct 2013 15:33:18 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9KEVvgd018389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sun, 20 Oct 2013 15:31:57 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3E168180-627E-4C9C-8547-7D02995E51B5"
Message-ID: <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
Date: Sun, 20 Oct 2013 15:31:57 +0100
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9JFXH095966370800; tid=p9JFXH09596637084U; 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: r9KEXHBI009972
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: Sun, 20 Oct 2013 14:33:31 -0000

--Apple-Mail=_3E168180-627E-4C9C-8547-7D02995E51B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On 20 Oct 2013, at 12:52, Scott Brim <scott.brim@gmail.com> wrote:
> Adding more certainly doesn't help. Reducing the number could help if =
we have a concomitant increase in the usefulness of directorates.  But =
it doesn't solve the problem.  If we learn to adjust to having fewer =
ADs, and the trend toward a smaller more homogeneous candidate pool =
continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot of =
(appointed) "assistants".  That could work, but let's decide explicitly =
if that's the trajectory we want to be on.
>=20

I suspect we may find that more people would be able to find the time =
and resource to do AD-like tasks for a handful of hours per week, rather =
than having to find support to commit for 40 hours per week. Helping on =
a directorate is, for example, not an onerous task, but it (I hope) =
helps the ADs.

As it stands, WG chairs have the option to appoint a secretary, for some =
level of help. The question I asked in the original email was whether =
ADs should have the option to appoint one or more assistants to help =
them. It seems that there's a lot to be said for such a model.  =
Potential future ADs could contribute the time they do have, and in =
doing so get a better feel for what the full AD role would be like, =
while the ADs would get some extra resource/help, which could reduce the =
amount of time they need to spend, making the role more =
attractive/feasible to them.=20

The question is how we answer Scott's last sentence above.  It could be =
a good topic to put on the admin plenary agenda in Vancouver.

Tim=

--Apple-Mail=_3E168180-627E-4C9C-8547-7D02995E51B5
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; =
"><div><div>On 20 Oct 2013, at 12:52, Scott Brim &lt;<a =
href=3D"mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&gt; =
wrote:</div><blockquote type=3D"cite"><p dir=3D"ltr">Adding more =
certainly doesn't help. Reducing the number could help if we have a =
concomitant increase in the usefulness of directorates.&nbsp; But it =
doesn't solve the problem.&nbsp; If we learn to adjust to having fewer =
ADs, and the trend toward a smaller more homogeneous candidate pool =
continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot of =
(appointed) "assistants".&nbsp; That could work, but let's decide =
explicitly if that's the trajectory we want to be =
on.</p></blockquote></div><div>I suspect we may find that more people =
would be able to find the time and resource to do AD-like tasks for a =
handful of hours per week, rather than having to find support to commit =
for 40 hours per week. Helping on a directorate is, for example, not an =
onerous task, but it (I hope) helps the ADs.</div><div><br></div><div>As =
it stands, WG chairs have the option to appoint a secretary, for some =
level of help. The question I asked in the original email was whether =
ADs should have the option to appoint one or more assistants to help =
them.&nbsp;It seems that there's a lot to be said for such a model. =
&nbsp;Potential future ADs could contribute the time they do have, and =
in doing so get a better feel for what the full AD role would be like, =
while the ADs would get some extra resource/help, which could reduce the =
amount of time they need to spend, making the role more =
attractive/feasible to them.&nbsp;</div><div><br></div><div>The question =
is how we answer Scott's last sentence above. &nbsp;It could be a good =
topic to put on the admin plenary agenda in =
Vancouver.</div><div><br></div><div>Tim</div></body></html>=

--Apple-Mail=_3E168180-627E-4C9C-8547-7D02995E51B5--

From jmh@joelhalpern.com  Sun Oct 20 07:43:09 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C0711E81D7 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:43:09 -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 BmX-Bla7-eFy for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:43:04 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 1009311E81A2 for <ietf@ietf.org>; Sun, 20 Oct 2013 07:43:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 0C828E0C7C; Sun, 20 Oct 2013 07:43:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (c213-89-137-101.bredband.comhem.se [213.89.137.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 01F54E0C7B; Sun, 20 Oct 2013 07:43:02 -0700 (PDT)
Message-ID: <5263EBF3.5050901@joelhalpern.com>
Date: Sun, 20 Oct 2013 10:42:59 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk>
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: Sun, 20 Oct 2013 14:43:10 -0000

The question to my mind is which tasks are you looking to off-load.
ADs already can ask for assistance in many ways.  Most use directorates. 
  Some use them a lot.  Some use them only a little.
[Yes, I have an opinion about how to handle an area directorate that 
tells the AD "no, we will not do more reviews for you."  But even that 
is not as easy as one would like.]

Assuming we don't want to change the basic functioning and review, the 
ADs themselves need to be sufficiently informed of issues to engage in 
discussion with the other ADs about issues.  That requires a fair amount 
of work.

Yours,
Joel

On 10/20/13 10:31 AM, Tim Chown wrote:
> On 20 Oct 2013, at 12:52, Scott Brim <scott.brim@gmail.com
> <mailto:scott.brim@gmail.com>> wrote:
>>
>> Adding more certainly doesn't help. Reducing the number could help if
>> we have a concomitant increase in the usefulness of directorates.  But
>> it doesn't solve the problem.  If we learn to adjust to having fewer
>> ADs, and the trend toward a smaller more homogeneous candidate pool
>> continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot
>> of (appointed) "assistants".  That could work, but let's decide
>> explicitly if that's the trajectory we want to be on.
>>
> I suspect we may find that more people would be able to find the time
> and resource to do AD-like tasks for a handful of hours per week, rather
> than having to find support to commit for 40 hours per week. Helping on
> a directorate is, for example, not an onerous task, but it (I hope)
> helps the ADs.
>
> As it stands, WG chairs have the option to appoint a secretary, for some
> level of help. The question I asked in the original email was whether
> ADs should have the option to appoint one or more assistants to help
> them. It seems that there's a lot to be said for such a model.
>   Potential future ADs could contribute the time they do have, and in
> doing so get a better feel for what the full AD role would be like,
> while the ADs would get some extra resource/help, which could reduce the
> amount of time they need to spend, making the role more
> attractive/feasible to them.
>
> The question is how we answer Scott's last sentence above.  It could be
> a good topic to put on the admin plenary agenda in Vancouver.
>
> Tim

From tjc@ecs.soton.ac.uk  Sun Oct 20 07:51:13 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 5EFB411E81A2 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:51:13 -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 lsts4OKXx0Xo for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:51:12 -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 316C611E8405 for <ietf@ietf.org>; Sun, 20 Oct 2013 07:51:09 -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 r9KEoxbS013311; Sun, 20 Oct 2013 15:50:59 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9KEoxbS013311
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1382280659; bh=r1bFazWL1cEntMba620BaFVmW2A=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=WB/KDR24pMMk+yx0tmfIWBPLQE7OFJxWnRcPZJp7bUV+FuMTAmJRZ4ymEa6Vo/Zeo THMjn9wiKMSNoYV82QFKEmFer7oyzBIVGvdSbsTGWcPyb0Ag8J5R72QPerEeAZGHEJ pH4Hgf1PKYDZ8yeeEv6bBbp5oMxstd53XrSgR9VY=
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 p9JFox09596637785N ret-id none; Sun, 20 Oct 2013 15:50:59 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9KEndpq021007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 20 Oct 2013 15:49:39 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5263EBF3.5050901@joelhalpern.com>
Date: Sun, 20 Oct 2013 15:49:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <5263EBF3.5050901@joelhalpern.com> <221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9JFox095966377800; tid=p9JFox09596637785N; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9KEoxbS013311
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 20 Oct 2013 14:51:13 -0000

On 20 Oct 2013, at 15:42, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

> The question to my mind is which tasks are you looking to off-load.
> ADs already can ask for assistance in many ways.  Most use =
directorates.  Some use them a lot.  Some use them only a little.
> [Yes, I have an opinion about how to handle an area directorate that =
tells the AD "no, we will not do more reviews for you."  But even that =
is not as easy as one would like.]
>=20
> Assuming we don't want to change the basic functioning and review, the =
ADs themselves need to be sufficiently informed of issues to engage in =
discussion with the other ADs about issues.  That requires a fair amount =
of work.

I think at a high level it could be as simple as ADs being able to =
appoint one or two assistants each with whom they can work closely to =
help achoeve whatever it is they need.  Just as they can with =
directorates.  But the assistant(s) might be on a more accountable =
footing, much as a WG chair is.=20

Tim

> Yours,
> Joel
>=20
> On 10/20/13 10:31 AM, Tim Chown wrote:
>> On 20 Oct 2013, at 12:52, Scott Brim <scott.brim@gmail.com
>> <mailto:scott.brim@gmail.com>> wrote:
>>>=20
>>> Adding more certainly doesn't help. Reducing the number could help =
if
>>> we have a concomitant increase in the usefulness of directorates.  =
But
>>> it doesn't solve the problem.  If we learn to adjust to having fewer
>>> ADs, and the trend toward a smaller more homogeneous candidate pool
>>> continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot
>>> of (appointed) "assistants".  That could work, but let's decide
>>> explicitly if that's the trajectory we want to be on.
>>>=20
>> I suspect we may find that more people would be able to find the time
>> and resource to do AD-like tasks for a handful of hours per week, =
rather
>> than having to find support to commit for 40 hours per week. Helping =
on
>> a directorate is, for example, not an onerous task, but it (I hope)
>> helps the ADs.
>>=20
>> As it stands, WG chairs have the option to appoint a secretary, for =
some
>> level of help. The question I asked in the original email was whether
>> ADs should have the option to appoint one or more assistants to help
>> them. It seems that there's a lot to be said for such a model.
>>  Potential future ADs could contribute the time they do have, and in
>> doing so get a better feel for what the full AD role would be like,
>> while the ADs would get some extra resource/help, which could reduce =
the
>> amount of time they need to spend, making the role more
>> attractive/feasible to them.
>>=20
>> The question is how we answer Scott's last sentence above.  It could =
be
>> a good topic to put on the admin plenary agenda in Vancouver.
>>=20
>> Tim


From john-ietf@jck.com  Sun Oct 20 07:57:33 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 19E9D11E840E for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:57:33 -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 WS+LZNzgByh1 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 07:57:28 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D7CFC11E840B for <ietf@ietf.org>; Sun, 20 Oct 2013 07:57:27 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VXuRa-0009XL-4R; Sun, 20 Oct 2013 10:57:26 -0400
X-Vipre-Scanned: 03958560002C31039586AD-TDI
Date: Sun, 20 Oct 2013 10:57:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Brim <scott.brim@gmail.com>, Cullen Jennings <fluffy@cisco.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for	Nominations)
Message-ID: <465932135530A581825568CF@[192.168.1.128]>
In-Reply-To: <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@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: Sun, 20 Oct 2013 14:57:33 -0000

--On Sunday, 20 October, 2013 07:52 -0400 Scott Brim
<scott.brim@gmail.com> wrote:

> But it
> doesn't solve the problem.  If we learn to adjust to having
> fewer ADs, and the trend toward a smaller more homogeneous
> candidate pool continues, we end up with just a Chair and
> maybe 1-2 ADs, plus a lot of (appointed) "assistants".  That
> could work, but let's decide explicitly if that's the
> trajectory we want to be on.

Most others haven't, but you, Scott, have been around long
enough to remember that is more or less where the IETF started,
in that case with an appointed Chair, Chair-appointed ADs, and
whatever help or organizational structure the latter could
muster.  That structure has the advantage of efficiency, real
accountability, and a guarantee of a group that can work
together well.  Unless the Chair is really careful (and, IMO,
Phill did a superb job) it completely loses all of the
advantages of a diversity of views and a number of other things,
including distributed accountability.

It seems to be that, whether going that route, splitting off the
management and approval processes, forcing the number of WGs
down, doubling the size of the IESG, or even reviving the
long-dead idea of breaking the IETF up into separate Area (or
cluster of Areas) organizations, we have no shortage of
proposals.  We've even had proposals for tuning the Nomcom model
that might help with some of the candidacy-availability problem
as well as other things. Each one has disadvantages.  Most have
some advantages and/or side-effect solutions to other problems.


What I haven't seen since the changes of the first half of the
1990s is real community consensus that it is time to do
something rather than agonize about particular symptoms (e.g.,
Nomcom problems getting ample good candidates for all areas),
complain or whine, and ultimately do nothing.  

Many times "do nothing" has been the result of an incumbent IESG
being happy with the status quo and effectively blocking
consideration of change proposals, but often the community just
hasn't considered the issue important enough to expend the
energy.  Perhaps this time will be different.

 best,
    john


From andy@yumaworks.com  Sun Oct 20 08:45:47 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 3465211E81E6 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 08:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.84
X-Spam-Level: 
X-Spam-Status: No, score=-2.84 tagged_above=-999 required=5 tests=[AWL=0.136,  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 Qxzjuzm5-Bvm for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 08:45:42 -0700 (PDT)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id 4D99611E81D1 for <ietf@ietf.org>; Sun, 20 Oct 2013 08:45:39 -0700 (PDT)
Received: by mail-qa0-f47.google.com with SMTP id k15so1909706qaq.6 for <ietf@ietf.org>; Sun, 20 Oct 2013 08:45:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7h8pUEBOYep/4M7KIHVJhbnC4pLffg6YSaIyn3FJreE=; b=DSo1WnFYpcbATPwg60dKNuNX4WCEWgCXv3LpLtweKWYaSQdxSXxggKXQTt+o598F+s nH8zfzsQERi66GHpvuDo6P1s2d8Kae8ezlT2uhyuua9OTuH5WF586EPFEURxJqA03trY xyEfjPdgxYTcm8wy1n5rVCvfsPn8l2/09jIEsNt6qCTfSPTwTJ/injBVXrKZ7AUCLlPF RvSNJlRwKlnySyrr74095y5iItha2sFdoYmNuzRP/FDxnp3BLk51sqmYvU0rpaQ7YBBT 0MNZjAESUwX2cGS5gkawTYHITQNPdrXCb3lfrS4wssXo3WZfnB5ToFueQkvRsj6kLra3 zRrA==
X-Gm-Message-State: ALoCoQlIBRqL6ZsRk1h2ongDJKFWs5YR/80LN64qaE5Xk9RBCwFamnxh6G3DmAIW31NUiY6id2er
MIME-Version: 1.0
X-Received: by 10.224.51.199 with SMTP id e7mr17338037qag.41.1382283936528; Sun, 20 Oct 2013 08:45:36 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Sun, 20 Oct 2013 08:45:36 -0700 (PDT)
In-Reply-To: <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <5263EBF3.5050901@joelhalpern.com> <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk>
Date: Sun, 20 Oct 2013 08:45:36 -0700
Message-ID: <CABCOCHSnxjFeWU431JXcHNDh9F03QGXYYXfQ1H5mRZ5KG7ZVUg@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Andy Bierman <andy@yumaworks.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c29f40040d6204e92e0fd3
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, 20 Oct 2013 15:45:47 -0000

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

Hi,

First it would be good to confirm (from NOMCOM?) why people are rejecting
AD nominations. IMO asking 25 - 40 hours a week for 2 years is too much,
but I am guessing that 1/2 of that is the right number to require.

I was surprised to hear that document review took only around 20%
of the time.  If so, then changing the review process won't help.
How many ADs are managers or directors in their day job?
How many have managed 15 - 30 employees before?
There is an large imbalance in the IESG between technical and management
skills.
I really think paying for professional management services would help.



Andy


On Sun, Oct 20, 2013 at 7:49 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

>
> On 20 Oct 2013, at 15:42, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:
>
> > The question to my mind is which tasks are you looking to off-load.
> > ADs already can ask for assistance in many ways.  Most use directorates.
>  Some use them a lot.  Some use them only a little.
> > [Yes, I have an opinion about how to handle an area directorate that
> tells the AD "no, we will not do more reviews for you."  But even that is
> not as easy as one would like.]
> >
> > Assuming we don't want to change the basic functioning and review, the
> ADs themselves need to be sufficiently informed of issues to engage in
> discussion with the other ADs about issues.  That requires a fair amount of
> work.
>
> I think at a high level it could be as simple as ADs being able to appoint
> one or two assistants each with whom they can work closely to help achoeve
> whatever it is they need.  Just as they can with directorates.  But the
> assistant(s) might be on a more accountable footing, much as a WG chair is.
>
> Tim
>
> > Yours,
> > Joel
> >
> > On 10/20/13 10:31 AM, Tim Chown wrote:
> >> On 20 Oct 2013, at 12:52, Scott Brim <scott.brim@gmail.com
> >> <mailto:scott.brim@gmail.com>> wrote:
> >>>
> >>> Adding more certainly doesn't help. Reducing the number could help if
> >>> we have a concomitant increase in the usefulness of directorates.  But
> >>> it doesn't solve the problem.  If we learn to adjust to having fewer
> >>> ADs, and the trend toward a smaller more homogeneous candidate pool
> >>> continues, we end up with just a Chair and maybe 1-2 ADs, plus a lot
> >>> of (appointed) "assistants".  That could work, but let's decide
> >>> explicitly if that's the trajectory we want to be on.
> >>>
> >> I suspect we may find that more people would be able to find the time
> >> and resource to do AD-like tasks for a handful of hours per week, rather
> >> than having to find support to commit for 40 hours per week. Helping on
> >> a directorate is, for example, not an onerous task, but it (I hope)
> >> helps the ADs.
> >>
> >> As it stands, WG chairs have the option to appoint a secretary, for some
> >> level of help. The question I asked in the original email was whether
> >> ADs should have the option to appoint one or more assistants to help
> >> them. It seems that there's a lot to be said for such a model.
> >>  Potential future ADs could contribute the time they do have, and in
> >> doing so get a better feel for what the full AD role would be like,
> >> while the ADs would get some extra resource/help, which could reduce the
> >> amount of time they need to spend, making the role more
> >> attractive/feasible to them.
> >>
> >> The question is how we answer Scott's last sentence above.  It could be
> >> a good topic to put on the admin plenary agenda in Vancouver.
> >>
> >> Tim
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>First it would be good to confirm (=
from NOMCOM?) why people are rejecting</div><div>AD nominations. IMO asking=
 25 - 40 hours a week for 2 years is too much,</div><div>but I am guessing =
that 1/2 of that is the right number to require.</div>
<div><br></div><div>I was surprised to hear that document review took only =
around 20%</div><div>of the time. =A0If so, then changing the review proces=
s won&#39;t help.</div><div>How many ADs are managers or directors in their=
 day job?</div>
<div>How many have managed 15 - 30 employees before?</div><div><div class=
=3D"gmail_extra">There is an large imbalance in the IESG between technical =
and management skills.<br></div><div class=3D"gmail_extra">I really think p=
aying for professional management services would help.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Andy</div><d=
iv class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">
On Sun, Oct 20, 2013 at 7:49 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D=
"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;<=
/span> wrote:<br><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-l=
eft-style:solid;padding-left:1ex">
<br>
On 20 Oct 2013, at 15:42, &quot;Joel M. Halpern&quot; &lt;<a href=3D"mailto=
:jmh@joelhalpern.com">jmh@joelhalpern.com</a>&gt; wrote:<br>
<br>
&gt; The question to my mind is which tasks are you looking to off-load.<br=
>
&gt; ADs already can ask for assistance in many ways. =A0Most use directora=
tes. =A0Some use them a lot. =A0Some use them only a little.<br>
&gt; [Yes, I have an opinion about how to handle an area directorate that t=
ells the AD &quot;no, we will not do more reviews for you.&quot; =A0But eve=
n that is not as easy as one would like.]<br>
&gt;<br>
&gt; Assuming we don&#39;t want to change the basic functioning and review,=
 the ADs themselves need to be sufficiently informed of issues to engage in=
 discussion with the other ADs about issues. =A0That requires a fair amount=
 of work.<br>

<br>
I think at a high level it could be as simple as ADs being able to appoint =
one or two assistants each with whom they can work closely to help achoeve =
whatever it is they need. =A0Just as they can with directorates. =A0But the=
 assistant(s) might be on a more accountable footing, much as a WG chair is=
.<br>

<br>
Tim<br>
<br>
&gt; Yours,<br>
&gt; Joel<br>
&gt;<br>
&gt; On 10/20/13 10:31 AM, Tim Chown wrote:<br>
&gt;&gt; On 20 Oct 2013, at 12:52, Scott Brim &lt;<a href=3D"mailto:scott.b=
rim@gmail.com">scott.brim@gmail.com</a><br>
&gt;&gt; &lt;mailto:<a href=3D"mailto:scott.brim@gmail.com">scott.brim@gmai=
l.com</a>&gt;&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Adding more certainly doesn&#39;t help. Reducing the number co=
uld help if<br>
&gt;&gt;&gt; we have a concomitant increase in the usefulness of directorat=
es. =A0But<br>
&gt;&gt;&gt; it doesn&#39;t solve the problem. =A0If we learn to adjust to =
having fewer<br>
&gt;&gt;&gt; ADs, and the trend toward a smaller more homogeneous candidate=
 pool<br>
&gt;&gt;&gt; continues, we end up with just a Chair and maybe 1-2 ADs, plus=
 a lot<br>
&gt;&gt;&gt; of (appointed) &quot;assistants&quot;. =A0That could work, but=
 let&#39;s decide<br>
&gt;&gt;&gt; explicitly if that&#39;s the trajectory we want to be on.<br>
&gt;&gt;&gt;<br>
&gt;&gt; I suspect we may find that more people would be able to find the t=
ime<br>
&gt;&gt; and resource to do AD-like tasks for a handful of hours per week, =
rather<br>
&gt;&gt; than having to find support to commit for 40 hours per week. Helpi=
ng on<br>
&gt;&gt; a directorate is, for example, not an onerous task, but it (I hope=
)<br>
&gt;&gt; helps the ADs.<br>
&gt;&gt;<br>
&gt;&gt; As it stands, WG chairs have the option to appoint a secretary, fo=
r some<br>
&gt;&gt; level of help. The question I asked in the original email was whet=
her<br>
&gt;&gt; ADs should have the option to appoint one or more assistants to he=
lp<br>
&gt;&gt; them. It seems that there&#39;s a lot to be said for such a model.=
<br>
&gt;&gt; =A0Potential future ADs could contribute the time they do have, an=
d in<br>
&gt;&gt; doing so get a better feel for what the full AD role would be like=
,<br>
&gt;&gt; while the ADs would get some extra resource/help, which could redu=
ce the<br>
&gt;&gt; amount of time they need to spend, making the role more<br>
&gt;&gt; attractive/feasible to them.<br>
&gt;&gt;<br>
&gt;&gt; The question is how we answer Scott&#39;s last sentence above. =A0=
It could be<br>
&gt;&gt; a good topic to put on the admin plenary agenda in Vancouver.<br>
&gt;&gt;<br>
&gt;&gt; Tim<br>
<br>
</blockquote></div><br></div></div></div>

--001a11c29f40040d6204e92e0fd3--

From jari.arkko@piuha.net  Sun Oct 20 08:58:58 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 AF14611E81C1 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 08:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 s0FGCx5Figar for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 08:58:53 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4942B11E81C9 for <ietf@ietf.org>; Sun, 20 Oct 2013 08:58:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6F8042CC6C for <ietf@ietf.org>; Sun, 20 Oct 2013 18:58:50 +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 4MieWWirMNVR for <ietf@ietf.org>; Sun, 20 Oct 2013 18:58:49 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id DBAEF2CC48 for <ietf@ietf.org>; Sun, 20 Oct 2013 18:58:48 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for	Nominations)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <465932135530A581825568CF@[192.168.1.128]>
Date: Sun, 20 Oct 2013 23:58:46 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <89EEB802-12BD-4D13-B35E-791B95EC91B4@piuha.net>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <465932135530A581825568CF@[192.168.1.128]>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 15:58:58 -0000

I think delegation to directorates, chairs, and document shepherds is =
more useful than creating a new assistant role. Not saying that such =
delegation is easy, but it clearly has worked well in some situations at =
least.

There's really just a couple of fundamental variables we can tweak: =
delegation (moving work around), depth (how much and how detailed we do =
it), coordination (how different pieces of work are organised as either =
separate independent processes or as something that needs more =
coordination), and scope (what work belongs in the IETF). And in every =
organisation, the roles needs to be reasonable & motivated for everyone =
in those roles.=20

In my completely person opinion: First, tweaking the scope should be off =
the table, because organisation should follow need, rather than vice =
versa. Our job (at the IESG/IETF) to fix the organisation if necessary. =
Second, I think we should look at delegation and depth of work at the =
IESG, and not merely because it would help AD work load. The better =
reason to look at that would be to empower the WGs to do their work in =
as complete fashion as possible, and be self responsible for dealing =
with the issues that arise, e.g., in cross-area reviews. This is why =
we've said that we will be sending more work back to the WGs and created =
the early directorate review experiment. Admittedly these are small =
steps. But it is my belief at least that the IESG needs to get out of =
the loop in more cases than we are today.

Finally, a couple of +1s to the following people:

Loa wrote:

> I should probably keep my mouth shat about this :) ! Looking tot he =
RTG
> area don't we have an Assistant AD, only that we call it the
> RTG Directorate Chair? A very proper place to delegate work and assign
> responsibility.

Indeed. (Which may beg the question of whether additional recognition =
for the important work by chairs and directorate folk needs more =
recognition.)

And Joel:

> For better or worse I told the nomcom that I only have 2 hours a day =
(7 days a  week) for this=85 They took me anyway. The load is unevenly =
distributed. The internet and routing and Apps ADs appear to have more  =
drafts to process and more complex working group interactions, then does =
the ops side of ops and management.
>=20
> That said, this is not a not a full time job for me and I am not =
compensated for doing it. If my level of available commitment isn't =
adequate, I guess we'll find out between now and the 2 year mark.  My =
contribution to the things that bring me to the IETF as on operator have =
dropped off because I don't have time for them.

Kudos to Joel for doing such a good job with a limited amount of time. I =
hope that this sets an example as well for others to follow! (Obviously, =
areas and situations differ, too, which people should take into =
account.)

Jari


From chair@ietf.org  Sun Oct 20 10:44:41 2013
Return-Path: <chair@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 A3B9F11E8220; Sun, 20 Oct 2013 10:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=-1.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 O3+-v5AOyqPq; Sun, 20 Oct 2013 10:44:33 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 999B211E8224; Sun, 20 Oct 2013 10:44:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 5EFE19FB43; Sun, 20 Oct 2013 10:43:09 -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 Wjif80KvdKAU; Sun, 20 Oct 2013 10:43:09 -0700 (PDT)
Received: from [192.168.100.167] (unknown [117.102.104.44]) by c9a.amsl.com (Postfix) with ESMTPSA id 6BB449FB2C; Sun, 20 Oct 2013 10:43:06 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Proposed IETF Anti-Harassment Policy
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Mon, 21 Oct 2013 01:44:23 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF discussion list <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: Sun, 20 Oct 2013 17:44:41 -0000

The IETF should be an open and accessible body in which any individual =
feels
able to participate without fear of oppression or harassment.  The IESG =
has
become aware of some incidents of concern, is aware of various incidents =
in our
industry in general, and has also observed that many similar =
organisations and
conferences have a policy on this matter.

In order to ensure the right atmosphere and to provide a suitable =
environment,
the IESG has decided that it is desirable to write a simple and =
straightforward
policy on harassment. This is not only to remind participants not to =
harass
others (something that we hope is obvious to us all), but also to let =
anyone who
it the target of harassment know that we take these matters seriously =
and that
there is something they can do to address these sorts of incidents =
should they
occur.

A small design team has looked at existing policies used by other groups =
similar
to the IETF and consulted with some of the ISOC professionals with =
expertise in
human resources and issues of workplace harassment. The design team has =
put
together what the IESG feels is a good anti-harassment policy for the =
IETF: It
is short and to the point, it is modeled on and makes heavy re-use of =
the
language of existing policies, and it sets forth reasonable procedures =
for the
IETF.

The IESG intends to put in place Ombudspersons as confidential initial =
contact
points for situations where there is a concern of harassment. The =
selection of
Ombudspersons will happen later, and the person(s) will have appropriate
training and expertise.

The IESG plans to adopt this as an IESG Statement. We solicit your =
feedback. We
understand that this is a difficult and sensitive topic to discuss, but =
we do
want your comments. If you feel more comfortable sending comments =
directly to
the IESG <iesg@ietf.org> rather than discussing them on the IETF list, =
please
feel free to do so.

Jari Arkko for the IESG

--- Draft Statement ---

IETF Anti-Harassment Policy

IETF meetings, virtual meetings, and mailing lists are intended for =
professional
collaboration and networking. The IETF strives to create and maintain an
environment in which people are treated with dignity, decency, and =
respect.
Those who participate in the IETF are expected to behave according to
professional standards and demonstrate appropriate workplace behavior. =
While
participating in the IETF, communication between participants should be
appropriate for a professional audience including people of many =
different
backgrounds.

While our processes let chairs deal with disruptive public behaviors on =
mailing
lists and in IETF face-to-face meetings, harassment is a serious problem =
that
warrants special attention. IETF participants should not engage in =
harassment
while at IETF meetings, virtual meetings, social events, or on mailing =
lists.
Harassment is unwelcome hostile or intimidating behavior, in particular =
speech
and behavior that is sexually aggressive or intimidates based on =
attributes like
race, gender, religion, age, color, national origin, ancestry, =
disability,
sexual orientation, or gender identity. Harassment of this sort will not =
be
tolerated in the IETF. Harassment includes the use of offensive language =
or
sexual imagery in public presentations and displays, degrading verbal =
comments,
deliberate intimidation, stalking, harassing photography or recording,
inappropriate physical contact, and unwelcome sexual attention.

Participants asked to stop any harassing behavior are expected to comply
immediately. If you believe you have been harassed, notice that
someone else is being harassed, or have any other concerns, you are =
encouraged
to raise your concern in confidence with one of the Ombudspersons.

If these standards are violated, appropriate action will be taken.

From hgs@cs.columbia.edu  Sun Oct 20 10:48:33 2013
Return-Path: <hgs@cs.columbia.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 70AD611E8232 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 10:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.732
X-Spam-Level: 
X-Spam-Status: No, score=-2.732 tagged_above=-999 required=5 tests=[AWL=-0.133, 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 3xVRrDixMPAY for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 10:48:27 -0700 (PDT)
Received: from buckwheat.cc.columbia.edu (buckwheat.cc.columbia.edu [128.59.72.251]) by ietfa.amsl.com (Postfix) with ESMTP id 9FEBB11E820C for <ietf@ietf.org>; Sun, 20 Oct 2013 10:48:25 -0700 (PDT)
Received: from hazelnut (hazelnut.cc.columbia.edu [128.59.213.250]) by buckwheat.cc.columbia.edu (8.13.8/8.13.8) with ESMTP id r9KHkroJ029360; Sun, 20 Oct 2013 13:48:24 -0400
Received: from hazelnut (localhost.localdomain [127.0.0.1]) by hazelnut (Postfix) with ESMTP id E38C66C; Sun, 20 Oct 2013 13:48:24 -0400 (EDT)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by hazelnut (Postfix) with ESMTP id D83E76C; Sun, 20 Oct 2013 13:48:24 -0400 (EDT)
Received: from upstairs-3.home (pool-74-102-30-128.nwrknj.fios.verizon.net [74.102.30.128]) (user=hgs10 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r9KHmM4x013072 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 20 Oct 2013 13:48:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <085801cecd76$4bb76bf0$e32643d0$@olddog.co.uk>
Date: Sun, 20 Oct 2013 13:48:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2D3363C-97B4-4CAF-81C2-201E1C57CBDA@cs.columbia.edu>
References: <085801cecd76$4bb76bf0$e32643d0$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1510)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: 'IETF Discuss' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 17:48:33 -0000

Yes, that would make the acknowledgements the most interesting part of =
the hypothetical document to read. Kind of like reading between the =
non-existing lines of the "FOO working group has terminated" =
announcement...

Henning

On Oct 20, 2013, at 5:25 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Henning,
>=20
> Can Carol also add "Carol thinks this is a pretty dumb idea, but since =
it is
> mostly harmless and there is some support from people in the FOO =
working group
> and no sustained objection she did not block its publication"?
>=20
> Adrian
>=20
>> I see no problem with a one
>> sentence addition in the acknowledgements section along the lines of =
"This
>> document is a product of the FOO working group, chaired by Alice and =
Bob,
>> within the BAR area, with Carol as the responsible area director.", =
with a
> suitable
>> free-form recognition ("Only their periodic public floggings of the =
authors
> caused
>> this document to be finished.") added as relevant. The working group =
is often
>> mentioned already, as far as I can tell.
>=20
>=20



From jari.arkko@piuha.net  Sun Oct 20 11:12:36 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 036C111E8234 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 11:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.595
X-Spam-Level: 
X-Spam-Status: No, score=-103.595 tagged_above=-999 required=5 tests=[AWL=1.004, BAYES_00=-2.599, GB_I_INVITATION=-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 lKsxOVMYKEPM for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 11:12:30 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3D611E8233 for <ietf@ietf.org>; Sun, 20 Oct 2013 11:12:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C146C2CC6C; Sun, 20 Oct 2013 21:12:23 +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 4qK-e9VQKqGq; Sun, 20 Oct 2013 21:12:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 88A852CC48; Sun, 20 Oct 2013 21:12:21 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com>
Date: Mon, 21 Oct 2013 02:12:19 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C92ECE0D-9ACA-48C0-A0DF-5A67A27C034E@piuha.net>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
X-Mailer: Apple Mail (2.1510)
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: Sun, 20 Oct 2013 18:12:36 -0000

> [MB] Can you clue us in as to what "substantial action" has been =
taken?   [/MB]=20

I'd classify our action as a good start. Working towards substantial, =
but for that we need to get these efforts in bigger scale. Anyway, based =
on the retreat discussions we've started the early directorate review =
program, started inviting shepherds to calls, and started sending =
documents more easily back to the WGs.

The shepherds get invited to calls on a case by case basis, based on, =
e.g., perceived need to discuss. The number of shepherds on calls has =
varied from 0 to 2 on recent telechats. The individual ADs make the =
invitations, but feel free to suggest joining if you think there's a =
need for that. The ADs sometimes forget they can do this. If you have =
not been invited to the telechat it may mean that you've already dealt =
with the issues on e-mail. Not a bad thing, as such :-)

Jari



From sm@resistor.net  Sun Oct 20 12:20:34 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 3E45811E8269 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:20:34 -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 ibTgDA0p0rV2 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:20:33 -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 3CE0F11E825E for <ietf@ietf.org>; Sun, 20 Oct 2013 12:20:33 -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 r9KIjaRN008678; Sun, 20 Oct 2013 11:45:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382294761; bh=sdGml2FKotvNP/e+oatnquidzA460ESz3tu+lcMAucc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cutcVikkRi3k74TaQ0hPZgs0n3byROSRAgtgJdSCRK6vep6jU8cpCnxmzbdKmXg7W r3CGvMkpMC/PiCS/Kr5LzsAo6p11cqUbOI64kTPO3TuTO6xv/ovMbWC4F/sc9oSXPk Q8aI0E+LQZOKEi0gk/arlKsShX66BAGCvJ+1kFqM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382294761; i=@resistor.net; bh=sdGml2FKotvNP/e+oatnquidzA460ESz3tu+lcMAucc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JQDtuOdnctt5GqWp3A84863Ms0m9BV/IeXxgFEWoJjlCk8Cv/Jf3iMy9WrexdGFKy IuNkEZghhs9oRJtARId8n2rt/tOYpc4gmrQGP9hkm6O+oKPK3rPTrReu2KV9Un/MzC r8NCoVATJCQ+juNXGTbcZl7k6xnbOsAg/ffCOXnk=
Message-Id: <6.2.5.6.2.20131020113717.06bd46e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 20 Oct 2013 11:45:13 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: SM <sm@resistor.net>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
In-Reply-To: <C92ECE0D-9ACA-48C0-A0DF-5A67A27C034E@piuha.net>
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <C92ECE0D-9ACA-48C0-A0DF-5A67A27C034E@piuha.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: Sun, 20 Oct 2013 19:20:34 -0000

Hi Jari,
At 11:12 20-10-2013, Jari Arkko wrote:
>I'd classify our action as a good start. Working towards 
>substantial, but for that we need to get these efforts in bigger 
>scale. Anyway, based on the retreat discussions we've started the 
>early directorate review program, started inviting shepherds to 
>calls, and started sending documents more easily back to the WGs.

The following directorates are listed on the IETF web site:

   Applications Area Directorate
   General Area Review Team
   Smart Power Directorate
   DNS Directorate
   IP Directorate
   Ops Directorate
   MIB Doctors
   YANG Doctors
   AAA Doctors
   Performance Metrics Directorate
   DNS Directorate
   IP Directorate
   RAI Area Review Directorate
   SDP Directorate
   Routing Area Directorate
   Security Directorate
   RSVP Directorate
   Transport Area Directorate

How many reviews have each of the above directorates performed as 
part of the early directorate review program?

How is the effectiveness of the early directorate review program assessed?

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sun Oct 20 12:38:56 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 C5FF711E8286 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:38:56 -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 o0nB8ZslcpPj for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:38:56 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 232C811E83CE for <ietf@ietf.org>; Sun, 20 Oct 2013 12:38:50 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id g10so5775680pdj.20 for <ietf@ietf.org>; Sun, 20 Oct 2013 12:38:50 -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=fsadbeXxFb7OkSWNlmHAm7cye7+8jJ7lTaeQdjlA69I=; b=dcHdDd9LVhPvYMevIm073RrXa5UuNzAEMKq9uRjqhbnZrX7Geb+NlnBX+fzrdT6Ojq bdXKt3Fbv2hIHWFWMEHT7Ic6ki9BoLrr220ooprlATgJkXcLTrxY1WoM/2pM+5mNfqdr DoZT58DazB9JiPTNFa6+05thh6ejQCGq4h8MH1Vq0KswysYGujyuYf1hQ2LsBWXk8mvK aMGnKVnMMvaqdNjQx4zVwryloVxlEorq9t+BGKtb69woejW5+fcC5Sp0seJHF8axoA3S jtcbNXMXj0eLwrr80xkHnqUNgltOfDpXV+bJrxDUU8+tAj3MJzYaHJXDPXzxtgE1Bejd 6gYw==
X-Received: by 10.68.171.226 with SMTP id ax2mr13806381pbc.45.1382297930642; Sun, 20 Oct 2013 12:38:50 -0700 (PDT)
Received: from [192.168.178.20] (222.195.69.111.dynamic.snap.net.nz. [111.69.195.222]) by mx.google.com with ESMTPSA id fk4sm20213389pab.23.2013.10.20.12.38.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Oct 2013 12:38:49 -0700 (PDT)
Message-ID: <52643145.8010504@gmail.com>
Date: Mon, 21 Oct 2013 08:38:45 +1300
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: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]>
In-Reply-To: <892B13B7BF164B38A8DB3793@[192.168.1.128]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 19:38:56 -0000

On 21/10/2013 03:18, John C Klensin wrote:
...
> Because working together with others on final document reviews
> and providing a final verification that all necessary bits are
> in place shouldn't require nearly the job-learning time that the
> IESG/AD role does, one could consider asking members of that
> review body to serve only a year or maybe six months, and
> possibly relax the meeting attendance requirements, 

I think we could totally remove attendance requirements. There
are cases where understanding a document requires background knowledge,
but if the document doesn't contain pointers to that knowledge, it's
a defect in the document, not in the reviewer. In fact, we can argue
that since the acid test for a document is whether a reader who has
zero IETF experience can understand it without ambiguity, at least
one reviewer should have limited background knowledge.

I don't think a time limit is the critical issue - it's how many
documents a given reviewer has to review per year, or to be more
precise, how many pages. Clearly the burden in pages/year on a
conscientious AD at the moment is silly.

> either of
> which should vastly increase the pool of plausible volunteers,
> including some people we would very much like to have in those
> jobs but who can't take on the IESG workload or long-term
> commitment.
> 
> For an earlier and somewhat different take on this issue and a
> variation on a proposal, see the long-expired
> draft-klensin-stds-review-panel-00.

The high-order bit is whether we can separate the functions of
(a) steering the work of the IETF and (b) applying final quality
control to the documents. At the moment, these two jobs are bound
up with each other in the IESG.

    Brian

From brian.e.carpenter@gmail.com  Sun Oct 20 12:52:13 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 7823711E842F for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:52:13 -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 ZpnAXlR7cQyR for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:52:13 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B3E1D11E8426 for <ietf@ietf.org>; Sun, 20 Oct 2013 12:52:07 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id lf10so3851966pab.34 for <ietf@ietf.org>; Sun, 20 Oct 2013 12:52:07 -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=eM8Jgy6FUDDlflg2/W0s50EtJf6Zi13xL9XBWuSx17Q=; b=XpgPjIRz3rqpMmf7cXlYCppUMC/jVgohgnvqQtPyIgj4+imEugw8I+fl7rWcpoyLn0 +s0Q7ajmP91/feom4Kud3iv91RoTqUsX/u95SXm0l5HBddodHlurqUeMwPslNL39vInD iGu7jxJEgMB35bK/ALQHgNP7+4xp6+P/2N/741nIb2Vg68oto0KumVxltE+BCeO9Pxnb /qFH2AaZXSkfl52p6FBJpItUyS3qgYpm9RqfVWOSEueBTe3qlcPUjCxw+MK9iaQXhtXy FGz7ddHYvIupDJOyR4Mb9n73wZo1gp/Z8ArJT9FTEeqh9CUs5dDW5i+RuZO4AIwcKWkT WZnA==
X-Received: by 10.66.190.10 with SMTP id gm10mr2828957pac.126.1382298727413; Sun, 20 Oct 2013 12:52:07 -0700 (PDT)
Received: from [192.168.178.20] (222.195.69.111.dynamic.snap.net.nz. [111.69.195.222]) by mx.google.com with ESMTPSA id qz9sm16227131pbc.3.2013.10.20.12.52.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Oct 2013 12:52:06 -0700 (PDT)
Message-ID: <52643464.8010204@gmail.com>
Date: Mon, 21 Oct 2013 08:52:04 +1300
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: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <C92ECE0D-9ACA-48C0-A0DF-5A67A27C034E@piuha.net>
In-Reply-To: <C92ECE0D-9ACA-48C0-A0DF-5A67A27C034E@piuha.net>
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: Sun, 20 Oct 2013 19:52:13 -0000

How about simply posting a neutral, alphabetical list of "IETF Service Records"?

John Doe - Foobar WG Chair, 1986-1990
Jane Doe - Tiptop AD, 2003-2007
Jack Sprat - IAB Member, 1988-2008

etc.

Regards
   Brian

From jmh@joelhalpern.com  Sun Oct 20 12:55:28 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B90011E83CE for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:55:27 -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 YDAJI6Q7hAKd for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 12:55:19 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id E0CB711E825F for <ietf@ietf.org>; Sun, 20 Oct 2013 12:55:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 55E3D1E49CE; Sun, 20 Oct 2013 12:55:12 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (c213-89-137-101.bredband.comhem.se [213.89.137.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id AAB8F1C9F95; Sun, 20 Oct 2013 12:55:10 -0700 (PDT)
Message-ID: <52643500.3010406@joelhalpern.com>
Date: Sun, 20 Oct 2013 15:54:40 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com>
In-Reply-To: <52643145.8010504@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 19:55:28 -0000

The obvious risk if one separates WG management from review is that one 
could easily get the situation where the manager, in working with the 
WG, says that the document needs X, Y, and not Z.  And then the reviewer 
says "needs Z".  And there are more extreme versions of this.
Currently, the ability for the managing AD to say "no, this won't pass 
muster" is part of his management tool.  If he is not the reviewer, he 
seems to have lost an important tool.  I hope I am missing something 
that would make this sort of approach workable.

Yours,
Joel

On 10/20/13 3:38 PM, Brian E Carpenter wrote:
> On 21/10/2013 03:18, John C Klensin wrote:
> ...
>> Because working together with others on final document reviews
>> and providing a final verification that all necessary bits are
>> in place shouldn't require nearly the job-learning time that the
>> IESG/AD role does, one could consider asking members of that
>> review body to serve only a year or maybe six months, and
>> possibly relax the meeting attendance requirements,
>
> I think we could totally remove attendance requirements. There
> are cases where understanding a document requires background knowledge,
> but if the document doesn't contain pointers to that knowledge, it's
> a defect in the document, not in the reviewer. In fact, we can argue
> that since the acid test for a document is whether a reader who has
> zero IETF experience can understand it without ambiguity, at least
> one reviewer should have limited background knowledge.
>
> I don't think a time limit is the critical issue - it's how many
> documents a given reviewer has to review per year, or to be more
> precise, how many pages. Clearly the burden in pages/year on a
> conscientious AD at the moment is silly.
>
>> either of
>> which should vastly increase the pool of plausible volunteers,
>> including some people we would very much like to have in those
>> jobs but who can't take on the IESG workload or long-term
>> commitment.
>>
>> For an earlier and somewhat different take on this issue and a
>> variation on a proposal, see the long-expired
>> draft-klensin-stds-review-panel-00.
>
> The high-order bit is whether we can separate the functions of
> (a) steering the work of the IETF and (b) applying final quality
> control to the documents. At the moment, these two jobs are bound
> up with each other in the IESG.
>
>      Brian
>

From adrian@olddog.co.uk  Sun Oct 20 13:12:45 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 9A22A11E841E for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 13:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  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 qDDGVDpfZVbY for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 13:12:39 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 7928C11E822C for <ietf@ietf.org>; Sun, 20 Oct 2013 13:12:39 -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 r9KKCXDM005378;  Sun, 20 Oct 2013 21:12:34 +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 r9KKCUV9005349 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 20 Oct 2013 21:12:30 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com>
In-Reply-To: <52643500.3010406@joelhalpern.com>
Subject: RE: Separate ADs roles from IESG
Date: Sun, 20 Oct 2013 21:12:28 +0100
Message-ID: <08b801cecdd0$b5041b80$1f0c5280$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKOtjwmxpe8bmRIy51VzqF9G03ffgHdVXGyASaLZ20Bwg7V5AJUsfOWAO1Pw8iYPfSscA==
Content-Language: en-gb
Cc: 'John C Klensin' <john-ietf@jck.com>, 'IETF Discuss' <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: Sun, 20 Oct 2013 20:12:45 -0000

A better management/technical split that I can see would be exemplified =
by the recent proposal of an anti-harassment statement (q.v.).

At the moment it is the IESG's responsibility to produce such statements =
and it is currently the IESG's responsibility to hear appeals etc.  That =
*seems* like a very different task from reviewing documents or keeping a =
WG within charter and working to its millstones.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Joel M.
> Halpern
> Sent: 20 October 2013 20:55
> To: Brian E Carpenter
> Cc: John C Klensin; IETF Discuss
> Subject: Re: Separate ADs roles from IESG
>=20
> The obvious risk if one separates WG management from review is that =
one
> could easily get the situation where the manager, in working with the
> WG, says that the document needs X, Y, and not Z.  And then the =
reviewer
> says "needs Z".  And there are more extreme versions of this.
> Currently, the ability for the managing AD to say "no, this won't pass
> muster" is part of his management tool.  If he is not the reviewer, he
> seems to have lost an important tool.  I hope I am missing something
> that would make this sort of approach workable.


From harald@alvestrand.no  Sun Oct 20 13:44:02 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2E0511E8289 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 13:44:02 -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 yA+8H5sgIolX for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 13:43:52 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 1C49A11E8278 for <ietf@ietf.org>; Sun, 20 Oct 2013 13:43:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4B3A339E085 for <ietf@ietf.org>; Sun, 20 Oct 2013 22:43:50 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bG4h80WJNEZH for <ietf@ietf.org>; Sun, 20 Oct 2013 22:43:49 +0200 (CEST)
Received: from [192.168.1.186] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 5EE7839E03A for <ietf@ietf.org>; Sun, 20 Oct 2013 22:43:49 +0200 (CEST)
Message-ID: <52644084.3040605@alvestrand.no>
Date: Sun, 20 Oct 2013 22:43:48 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com>
In-Reply-To: <52643500.3010406@joelhalpern.com>
X-Enigmail-Version: 1.5.2
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, 20 Oct 2013 20:44:02 -0000

On 10/20/2013 09:54 PM, Joel M. Halpern wrote:
> The obvious risk if one separates WG management from review is that
> one could easily get the situation where the manager, in working with
> the WG, says that the document needs X, Y, and not Z.  And then the
> reviewer says "needs Z".  And there are more extreme versions of this.
> Currently, the ability for the managing AD to say "no, this won't pass
> muster" is part of his management tool.  If he is not the reviewer, he
> seems to have lost an important tool.  I hope I am missing something
> that would make this sort of approach workable.

Without having scanned every suggestion in this thread....

In my opinion, it is critical that it is clear who's got the final say
in whether a document is approved or not. At the moment, it's the IESG,
and I think it's likely that it should remain the IESG - if approval
authority isn't in the same chain of responsibility as management
authority, one has to find a way to deal with conflicts between the two
- and I think that's not a good way to go.

When I was on the IESG, and instituted the General Area Review Team, I
chose to trust reviewers to the degree that I would not read the
document unless my reviewer said I needed to. But the final decision on
the approval call was still mine; the reason I could do this was because
I trusted my reviewers.

Placing this amount of trust also means that it must be clear what
happens if the trust is broken - such a reviewer HAS to serve at the
pleasure of the AD.

If one wishes to shuffle around the responsibility differently, the
equations change. But splitting review from the IESG doesn't have to
mean splitting the authority for approval from the IESG.


>
> Yours,
> Joel
>
> On 10/20/13 3:38 PM, Brian E Carpenter wrote:
>> On 21/10/2013 03:18, John C Klensin wrote:
>> ...
>>> Because working together with others on final document reviews
>>> and providing a final verification that all necessary bits are
>>> in place shouldn't require nearly the job-learning time that the
>>> IESG/AD role does, one could consider asking members of that
>>> review body to serve only a year or maybe six months, and
>>> possibly relax the meeting attendance requirements,
>>
>> I think we could totally remove attendance requirements. There
>> are cases where understanding a document requires background knowledge,
>> but if the document doesn't contain pointers to that knowledge, it's
>> a defect in the document, not in the reviewer. In fact, we can argue
>> that since the acid test for a document is whether a reader who has
>> zero IETF experience can understand it without ambiguity, at least
>> one reviewer should have limited background knowledge.
>>
>> I don't think a time limit is the critical issue - it's how many
>> documents a given reviewer has to review per year, or to be more
>> precise, how many pages. Clearly the burden in pages/year on a
>> conscientious AD at the moment is silly.
>>
>>> either of
>>> which should vastly increase the pool of plausible volunteers,
>>> including some people we would very much like to have in those
>>> jobs but who can't take on the IESG workload or long-term
>>> commitment.
>>>
>>> For an earlier and somewhat different take on this issue and a
>>> variation on a proposal, see the long-expired
>>> draft-klensin-stds-review-panel-00.
>>
>> The high-order bit is whether we can separate the functions of
>> (a) steering the work of the IETF and (b) applying final quality
>> control to the documents. At the moment, these two jobs are bound
>> up with each other in the IESG.
>>
>>      Brian
>>


-- 
Surveillance is pervasive. Go Dark.


From dhc@dcrocker.net  Sun Oct 20 14:02:46 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 31F4E11E843A for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 14:02: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 4cZDthcQdidt for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 14:02:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EC4DF11E828D for <ietf@ietf.org>; Sun, 20 Oct 2013 14:02:40 -0700 (PDT)
Received: from [10.3.89.85] (IP-173-231-109-130.static.fibrenoire.ca [173.231.109.130] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9KL2ZgS026667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 20 Oct 2013 14:02:39 -0700
Message-ID: <526444E9.4050308@dcrocker.net>
Date: Sun, 20 Oct 2013 17:02:33 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com>
In-Reply-To: <52643500.3010406@joelhalpern.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]); Sun, 20 Oct 2013 14:02:39 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <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, 20 Oct 2013 21:02:46 -0000

On 10/20/2013 3:54 PM, Joel M. Halpern wrote:
> The obvious risk if one separates WG management from review is that one
> could easily get the situation where the manager, in working with the
> WG, says that the document needs X, Y, and not Z.  And then the reviewer
> says "needs Z".  And there are more extreme versions of this.
> Currently, the ability for the managing AD to say "no, this won't pass
> muster" is part of his management tool.  If he is not the reviewer, he
> seems to have lost an important tool.  I hope I am missing something
> that would make this sort of approach workable.


"Manager"?

Who's that?

ADs do not 'manage' working groups, and frankly neither do Chairs.

Yes, there's quite a lot of management activity done by both, but you've 
used the term manager in a way that reflects classic hierarchical 
authority models in typical organizations.

And that really isn't appropriate for the IETF, where we say that 
working group consensus rules working group decision-making and after 
that the IETF consensus rules.

The sort of thing you probably mean is that quality control processes 
outside the working group produce concerns and recommendations that run 
contrary to, or go beyond, what the working group has done.  That's 
fine, but that's not (necessarily) done by a "manager".  And in spite of 
giving ADs a unilateral authority to (temporarily) block progress, the 
resolution of concerns is a negotiation, not further unilateral 
decision-making by a higher-authority "manager".

The model that has ADs trying to be content experts, in addition to area 
facilitators, is exactly the underlying problem here.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From barryleiba.mailing.lists@gmail.com  Sun Oct 20 14:58:10 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 3658E11E82A0 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 14:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[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 d7pDHKVRjlqw for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 14:58:09 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 19EF011E8290 for <ietf@ietf.org>; Sun, 20 Oct 2013 14:58:07 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id ep20so2094704lab.3 for <ietf@ietf.org>; Sun, 20 Oct 2013 14:58: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:message-id:subject :from:to:cc:content-type; bh=CpcwQJFXXccSaOJjzuKnq9kkeRSlNQ5rGQ4yNPWR6HU=; b=q1ScqN9ynyfl8wYMqoB3KhN0eBUR00I2OmNx+7ClxzaKlNBVzdjZAijLJUUzpicMlx dAQKdYRSCJLIl62nY7AysGQ/1hvrkK+u+fL5BhCmXPjhlNYjwbgDuYTaEZ/i/H/VZXxz PnWJWJUoqeVhGOr9iIgi8NCiILiW8ZNdP4KF/fvdBawGGrZMSAkilxSWSRXTAsk55nF9 nLl9ioB6hpI44k9gRj+kV56mRRnoUGRb0PlOMbopISwL5ue7RrHHkrSU3WCRJXWJdcWa SOLLuPa3qH4vGMkBEndLujcMIKSpV2ZdhVvUXy7UYhl9LFAiOqQ0RTJ7WHWyOG9Axluk uWhQ==
MIME-Version: 1.0
X-Received: by 10.152.243.34 with SMTP id wv2mr11226135lac.2.1382306286801; Sun, 20 Oct 2013 14:58:06 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Sun, 20 Oct 2013 14:58:06 -0700 (PDT)
In-Reply-To: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
Date: Sun, 20 Oct 2013 17:58:06 -0400
X-Google-Sender-Auth: Z1VYdCzxMuFw_E6uOTN-DsLC8j8
Message-ID: <CAC4RtVC0ETEbHY8OmTO0i_0ik3u8kyF1fsY_9p_2XrLe1Ef22w@mail.gmail.com>
Subject: Re: Separate ADs roles from IESG
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 21:58:10 -0000

Just responding to one part of this that I find interesting and that
hasn't yet sparked discussion:

> Also I always don't like when the IESG is discussing and I see that
> the AD responsible for the I-D already made his decision, I prefer
> that AD should wait until all put in their decision/discussions, and
> then he may say what he thinks.

This is a very interesting idea, but I don't know that we can do
anything along this line that would have any real effect.  To
understand this, you'll need to know how the process works on our (the
IESG's) end today:

When a document comes out of one of my working groups, I do my AD
evaluation, perhaps do a round or two of edits with the WG (or perhaps
not), then request last call.  While I do that, I prepare the "ballot"
for the IESG.  After last call, the document's status goes back into
"Ad follow-up" state, and I schedule it for a telechat and issue the
ballot.  (Some of these things can overlap, depending upon the
document, but that's not important here.)

The ballot is where ADs record their positions: "no position", "yes",
"no objection", "discuss", "abstain", or, in rare cases, "recuse" (and
all ballots can have comments associated with them).  All documents
require one "yes" ballot and no "discuss" ballots in order to be
approved.  A Standards Track or BCP document *also* requires 9 other
"yes" or "no objection" ballots (specifically, 2/3 of the non-recused
ADs).

Now, when I issue the ballot, the datatracker automatically sets *my*
ballot position to "yes", and those of all the other ADs to "no
position".  That's because a "yes" ballot is required, and it's
reasonable to assume that the sponsoring AD, the one who is bringing
the document to the IESG, will ballot "yes" -- why else would she
sponsor the document, if not?

In principle, I like AB's idea: don't have the sponsoring AD
contaminate things by pushing her "yes" in front of everyone, and let
her judge the consensus of the IESG's discussion before balloting.  It
sounds useful, and correct.

Unfortunately, in practice, what I say two paragraphs ago would get in
the way: everyone will always *assume* that the sponsoring AD supports
the document and would issue a "yes" ballot, so even if the rest of
the IESG doesn't actually *see* the "yes" ballot initially, nothing
would really change.

In fact, there are occasions when a sponsoring AD ballots "discuss",
with a clear explanation of why, and, again, the assumption that it
will become "yes" when the issue is resolved.  It's theoretically
possible for the sponsoring AD to explicitly change the ballot to
"abstain" (or, even more oddly, "no position"), but this would cause
immediate questions from the other ADs as to what was going on, and
why were they being asked to spend their time on this document when
the sponsoring AD wasn't willing to support it.

So: this sounds good, and might be worth some discussion of how it
*could* be workable.  Given the explanation above, does anyone think
we can or should do anything here?

Barry, Applications AD

From barryleiba.mailing.lists@gmail.com  Sun Oct 20 15:02:13 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 1A72D11E82A8 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[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 uDywg8gCiUb3 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:02:12 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2468211E829B for <ietf@ietf.org>; Sun, 20 Oct 2013 15:02:07 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id ec20so1509006lab.9 for <ietf@ietf.org>; Sun, 20 Oct 2013 15:02: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:message-id:subject :from:to:cc:content-type; bh=Jw9Ss/42ed7wHW4izGxUYUZvBWAiz6gKadh3hL6D3hQ=; b=QkC7BJeIeHFYPvdGFQS2Gcp2VB45qmGNiZUh006xs5KrjwxvsgvLQh60lS3NlikwHP 5ojEugUyNfoIccTd23y2R1/4gLTvasQtmcoAx/3tTWSmIPUEcVDscNmXnCTWq/8MNsvw Xwk/EaViOQD1A4XIXrbmx393Klipl1CcnSS/XQ0cFRvcme7X38UCKecQHWIbudHCUIak YFlrY8BV9EO3DXqPQqOwk4FQi5Pz/ElFm9bPrruyW6U3sO11zgTzZA2dfjLNZa5AA7Kh SGheWbHW3pin1Oll7Z1Phq7vsuVRKu9KOSjr0PyDyEIMmzLiFtj5tHY+A+YYF1uAlNIA iNsg==
MIME-Version: 1.0
X-Received: by 10.152.23.137 with SMTP id m9mr11119109laf.17.1382306527088; Sun, 20 Oct 2013 15:02:07 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Sun, 20 Oct 2013 15:02:07 -0700 (PDT)
In-Reply-To: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>
Date: Sun, 20 Oct 2013 18:02:07 -0400
X-Google-Sender-Auth: cv4XUD5NY5O3RTQL5wOcFzNUzSI
Message-ID: <CAC4RtVCh9TBkCMSu7B5k3XEMYpeyY7+nfMFaGkLWOCL8cpckmQ@mail.gmail.com>
Subject: Re: Separate ADs roles from IESG
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 22:02:13 -0000

Hitting another part of AB's message:

> The ADs SHOULD have important-things in IETF that they are not allowed
> to do. I don't like this off-hat and on-hat activities, or two/three
> role-images per person in one volunteer organisation.

This also sounds self-evident, but I'm afraid it would make people
even *less* likely to volunteer for AD positions if they were
explicitly not allowed to participate in the normal IETF discourse.  I
think most of us do choose to limit our non-AD participation, because
we are aware that even when we *say* we're speaking only as
participants, some people will give our comments more weight than they
(the comments) deserve, simply because we also have AD roles -- which
is, of course, AB's point.

But if we made an explicit rule that ADs should not participate in,
say, technical discussions in working groups, I think we'd make things
worse than they are, not better.

Barry, Applications AD

From melinda.shore@gmail.com  Sun Oct 20 15:07:34 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 AC53A11E82B1 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:07: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 oU4Fgi5SFrGs for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:07:34 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 5158511E829B for <ietf@ietf.org>; Sun, 20 Oct 2013 15:07:33 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id g10so5801499pdj.7 for <ietf@ietf.org>; Sun, 20 Oct 2013 15:07:33 -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=wOQRzc4P4NIQmE4wkXucEi9aGg7GOo7g4ZDXifbb+rI=; b=V5KhU/Hp7cJ36dDsPRFz0fhjkpFuN9LU5PH+ID3alsCO6STQUiz9Ow/CJR8fTGMwqv 190C+aH57kuIaODom9+KEB6CSOZCEMtSwpDGKCFAlAZ33jVtYmXRC727v/QO+4lbmW31 vNn9b1GaRSIA+t4T+f+upMltww+Xbz1Rp0x/KgXjJXfiyXcRLzOWG3UEvpyQVPw1NzsN XwxBIlcUZimTQ1KWAjNur+l5cWXYL+EQXKOFHbUN4uGEXNiLqD/ZE6I+Y4hYiG70m9Nv 4avZLBFEDnX3OjjaBHNYTkVd/8GijYj9t8+uTELlpSDoy4wbsqRUfKs222peVEkpb92K MqWA==
X-Received: by 10.66.136.227 with SMTP id qd3mr14623940pab.113.1382306853196;  Sun, 20 Oct 2013 15:07:33 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id iu7sm16526443pbc.45.2013.10.20.15.07.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Oct 2013 15:07:32 -0700 (PDT)
Message-ID: <52645422.8020207@gmail.com>
Date: Sun, 20 Oct 2013 14:07:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <CAC4RtVCh9TBkCMSu7B5k3XEMYpeyY7+nfMFaGkLWOCL8cpckmQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCh9TBkCMSu7B5k3XEMYpeyY7+nfMFaGkLWOCL8cpckmQ@mail.gmail.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: Sun, 20 Oct 2013 22:07:34 -0000

On 10/20/13 2:02 PM, Barry Leiba wrote:
> But if we made an explicit rule that ADs should not participate in,
> say, technical discussions in working groups, I think we'd make things
> worse than they are, not better.

Yes, excluding the most senior, most experienced people from
technical discussions is a pretty terrible idea.

Melinda


From abdussalambaryun@gmail.com  Sun Oct 20 15:23: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 B7FEC11E82A2 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.528
X-Spam-Level: 
X-Spam-Status: No, score=-2.528 tagged_above=-999 required=5 tests=[AWL=0.072,  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 bWaUAQyKURmP for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 15:23:26 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BF48311E82B0 for <ietf@ietf.org>; Sun, 20 Oct 2013 15:23:25 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so7444859pdj.17 for <ietf@ietf.org>; Sun, 20 Oct 2013 15:23:25 -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=wkJ5IvJsV4klicaiahllGY+0yaX5IjKzfhPBriS5WCM=; b=tkp44eAZrvk2L+k04Ll1W25uJecv/9lIh6s68CYFMvmSSqusdtcY1BnRCoO6ILorin sUwooIBWbTnsChdOrmKZyKKPEFm5GpAOI8ARq+mhQOmKPhIxGmeqgU+lpT/E9BCmFbRW hFLLjM+9XbPibOJ0K3F16X2Y/0O/fpVMber39QmC6N4EcR8S8r5uTy4OcntYv1N4Hk1a vvMAhluUp+rUzhENwURSoOTUijxw/uaUJfptJcaT5yZ7CwgFvwO58N1S1smFk0Ngl7qv RgA5Fw9vKw7pb5N/4C4jyOLQ3m7Rqluppkq8i3xJnAJy2omAR5Ts08nmL3gLUxR/cLw/ 3/CA==
MIME-Version: 1.0
X-Received: by 10.66.142.170 with SMTP id rx10mr15100729pab.117.1382307805606;  Sun, 20 Oct 2013 15:23:25 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 20 Oct 2013 15:23:25 -0700 (PDT)
In-Reply-To: <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>
Date: Mon, 21 Oct 2013 00:23:25 +0200
Message-ID: <CADnDZ89r3OVvX1MbM8X-g-bNOLZgAmQGtDy4jZUpGvKDR7B5oA@mail.gmail.com>
Subject: Re: Separate ADs roles from IESG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 22:23:26 -0000

Hi Yoav,

I just want the IESG to have a special hat. Any person in IETF is a
participant that edits, discusses, reviews and comments, including
managers, which I think is a good system model, but having to add
management and decision-making in the same time can create a problem
in that model. The AD has three authority-hats: one the normal
participation/part-of-community one we all have, the second is AD hat,
and the third is the IESG hat (I don't like to think titles only have
hats off-or-on, because I have a nice hat in IETF for participation).
I have no problem with WG Chair hats because they use two per document
and I prefer only two level influences on documents process.

On 10/20/13, Yoav Nir <ynir@checkpoint.com> wrote:
> Hi, AB
>
> We don't have enough world-class experts on [insert subject here] that we
> can delegate some of them to "administer but don't participate" roles, and
> some others to "review but don't participate" roles. The same goes for WG
> chairs - if the WG is facing a contentious issue, it doesn't make sense to
> require the chair to shut up about it just to make the process more neutral.
> I'm afraid we'll have to live with the with-hat/without-hat thing regardless
> of any changes to the process of the job description.
>
> The ADs have multiple functions:
>  - managing the working groups, scheduling
>  - reviewing all documents
>  - incubating new work - BoFs.
>  - representing the IETF, "steering", community stuff.

The last function is not reasoable because it is not related to the
Area needs including IETF best output and the function is related to
the IETF decisions. Why does the AD be part of that decision for his
area's documents, I think better to be separated because he can have
used the normal hat in WG and then AD hat, so only maximum two hats
used per document. IMHO, the current system is that one AD person can
be using three hats per document flow through the system.

>
> These functions could be separated, but only at a cost of more people. And
> nobody would take any of those jobs if it means they can't speak at
> technical meetings.

I agree, but we have already majority people that don't like to take
those functions together (we are short of ADs) which I reduced one
function out. All SHOULD speak equaly in any meetings and I never say
that some one should not speak/comment. I want simply that who do IESG
to not do AD works, to reduce the three authority-hats of the AD to
only two hats.

My concerns are not three level-influences in only technical
discussions but also procedural discussions.

AB
with my IETF participation hat on

From Ted.Lemon@nominum.com  Sun Oct 20 16:15: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 2A8AF11E82C1 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 16:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 H-BYj0JGG2z0 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 16:15:33 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 8792411E82CB for <ietf@ietf.org>; Sun, 20 Oct 2013 16:15:29 -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 DSNKUmRkETLFnE0Y33vjXNZjMfEVy3j9rQB7@postini.com; Sun, 20 Oct 2013 16:15:29 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 4C2751B82D6 for <ietf@ietf.org>; Sun, 20 Oct 2013 16:15:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 1E88F190052; Sun, 20 Oct 2013 16:15:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 20 Oct 2013 16:15:23 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: Separate ADs roles from IESG
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52643145.8010504@gmail.com>
Date: Sun, 20 Oct 2013 19:15:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <08590C84-2655-463F-A888-FE315A62526A@nominum.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1812)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Oct 2013 23:15:40 -0000

On Oct 20, 2013, at 3:38 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> The high-order bit is whether we can separate the functions of
> (a) steering the work of the IETF and (b) applying final quality
> control to the documents. At the moment, these two jobs are bound
> up with each other in the IESG.

It's worth noting that there is a synergy between steering, managing =
working groups and reviewing documents; if you separate out document =
review, some of what IESG members need to engage in steering and =
managing may go away.

BTW, steering doesn't mean dictating the direction the IETF goes; it =
means being aware of issues that are cropping up, identifying themes =
that are common, and trying to make people who have less of a bird's-eye =
view aware of them.   It's not clear to me that you can get this view =
without consuming a fairly significant amount of time.   Joel's two =
hours a day is probably enough, but I wouldn't want to see it go a whole =
lot less than that.


From randy@psg.com  Sun Oct 20 17:27: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 7EBC311E83C4; Sun, 20 Oct 2013 17:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 8tR5Sha2kfBF; Sun, 20 Oct 2013 17:27:36 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 809BF11E8377; Sun, 20 Oct 2013 17:27:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VY3LG-0005z5-NO; Mon, 21 Oct 2013 00:27:31 +0000
Date: Mon, 21 Oct 2013 03:27:29 +0300
Message-ID: <m2wql7tqmm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Proposed IETF Anti-Harassment Policy
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
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 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, 21 Oct 2013 00:27:36 -0000

seems an excellent start.  let's fly with it for a while and see how it
goes.  thanks for this.

randy

From l.wood@surrey.ac.uk  Sun Oct 20 19:06:22 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 C968111E8100 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 19:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.381
X-Spam-Level: 
X-Spam-Status: No, score=-5.381 tagged_above=-999 required=5 tests=[AWL=1.217,  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 XZYZLn1OMcyW for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 19:06:15 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.107]) by ietfa.amsl.com (Postfix) with ESMTP id 46CF711E8106 for <ietf@ietf.org>; Sun, 20 Oct 2013 19:06:11 -0700 (PDT)
Received: from [193.109.255.147:45239] by server-3.bemta-14.messagelabs.com id BC/50-03605-90C84625; Mon, 21 Oct 2013 02:06:01 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-72.messagelabs.com!1382321160!14223075!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9242 invoked from network); 21 Oct 2013 02:06:00 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-14.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 21 Oct 2013 02:06:00 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.2.234]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 21 Oct 2013 03:06:00 +0100
From: <l.wood@surrey.ac.uk>
To: <ted.lemon@nominum.com>, <brian.e.carpenter@gmail.com>
Date: Mon, 21 Oct 2013 03:04:03 +0100
Subject: RE: Separate ADs roles from IESG
Thread-Topic: Separate ADs roles from IESG
Thread-Index: Ac7N6mfkP1vKXRF/REKXcbpPx4MDYAAF2kPA
Message-ID: <290E20B455C66743BE178C5C84F1240847E366CE11@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com>, <08590C84-2655-463F-A888-FE315A62526A@nominum.com>
In-Reply-To: <08590C84-2655-463F-A888-FE315A62526A@nominum.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: john-ietf@jck.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: Mon, 21 Oct 2013 02:06:22 -0000

Agreed, reviewing documents can be separated out.

There's a lot of technical expertise able to review documents, but outside =
the WG chair/AD/IESG formal hierarchy (and in very different timezones) tha=
t may be able to provide document reviews. Provided they never have to go o=
n concalls.

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Ted Lemon =
[ted.lemon@nominum.com]
Sent: 21 October 2013 00:15
To: Brian E Carpenter
Cc: John C Klensin; IETF Discuss
Subject: Re: Separate ADs roles from IESG

On Oct 20, 2013, at 3:38 PM, Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
> The high-order bit is whether we can separate the functions of
> (a) steering the work of the IETF and (b) applying final quality
> control to the documents. At the moment, these two jobs are bound
> up with each other in the IESG.

It's worth noting that there is a synergy between steering, managing workin=
g groups and reviewing documents; if you separate out document review, some=
 of what IESG members need to engage in steering and managing may go away.

BTW, steering doesn't mean dictating the direction the IETF goes; it means =
being aware of issues that are cropping up, identifying themes that are com=
mon, and trying to make people who have less of a bird's-eye view aware of =
them.   It's not clear to me that you can get this view without consuming a=
 fairly significant amount of time.   Joel's two hours a day is probably en=
ough, but I wouldn't want to see it go a whole lot less than that.


From lars@netapp.com  Sun Oct 20 21:16:21 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 084AC11E8403 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 21:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.782
X-Spam-Level: 
X-Spam-Status: No, score=-8.782 tagged_above=-999 required=5 tests=[AWL=1.817,  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 H4hz-oji9Hg0 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 21:16:13 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id CBDBA11E833E for <ietf@ietf.org>; Sun, 20 Oct 2013 21:16:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.93,536,1378882800";  d="asc'?scan'208";a="103080485"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx12-out.netapp.com with ESMTP; 20 Oct 2013 21:16:09 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Sun, 20 Oct 2013 21:16:09 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Topic: NOMCOM - Critical shortage of nominees for multiple areas
Thread-Index: AQHOy0TTyFZWEwDAIU+X0yY74xviPpn6upGAgARMx4A=
Date: Mon, 21 Oct 2013 04:16:08 +0000
Message-ID: <AF1F1D53-41D2-4E1B-88E8-41D0B7FB97B7@netapp.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net>
In-Reply-To: <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_C3850605-B987-4C67-97FB-509A908380A5"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "Nomcom@ietfa.amsl.com" <Nomcom@ietfa.amsl.com>, "ietf@ietf.org" <ietf@ietf.org>, "Chair@ietfa.amsl.com" <Chair@ietfa.amsl.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: Mon, 21 Oct 2013 04:16:21 -0000

--Apple-Mail=_C3850605-B987-4C67-97FB-509A908380A5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Oct 18, 2013, at 18:36, "Ersue, Mehmet (NSN - DE/Munich)" =
<mehmet.ersue@nsn.com> wrote:
> in your model you don't count those people who have been rejecting to =
a nomination,=20
> just because they believe the current AD did a very good job and =
he/she should be reelected.

that is not a good reason to turn down a nomination!

It's normally not known whether the incumbent can/will continue. Even if =
it is known, stuff happens, sometimes late in the process, and the =
incumbent needs to drop out. If there are no other candidates, we then =
need to go into panic mode.

Please accept nominations even if you believe the incumbent should be =
returned. Make that your #1 comment to the NomCom when you accept the =
nomination. (You can of course also state this publicly, if you want the =
community to know that you support the incumbent.)

But please accept the nomination if you are interested (also to be a =
fallback) and have support!

Lars

--Apple-Mail=_C3850605-B987-4C67-97FB-509A908380A5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUmSqidZcnpRveo1xAQKQjgQAqruSx/80esgnQVcvmk86osUMPGxRzqZy
SxlVVSr2qTMsz5Voza/YM5UpEoPx1/VybnZgTQfjUPuaD14hvC6X4O3gQzGkBnGj
0jZbGeSAP0mI0bbdPk4muWpWKbKh869vGAxmY3sQS6QJ01glvDFIJu1SWAVTOhpC
T1qbH3g7Wrs=
=5ENQ
-----END PGP SIGNATURE-----

--Apple-Mail=_C3850605-B987-4C67-97FB-509A908380A5--

From randy_presuhn@mindspring.com  Sun Oct 20 21:28:03 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 70EDB11E8494 for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 21:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.185
X-Spam-Level: 
X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5GwiBhwYq4g for <ietf@ietfa.amsl.com>; Sun, 20 Oct 2013 21:27:52 -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 A1D3F11E8337 for <ietf@ietf.org>; Sun, 20 Oct 2013 21:27:51 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=ARlN6euxkPEkhuS16pQ4QuI/WaWYss6CMh1ES5dGfTI8iUidkbUuTQhCgK+4QeHE; 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.32] (helo=elwamui-cypress.atl.sa.earthlink.net) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1VY75q-0004pk-Pj for ietf@ietf.org; Mon, 21 Oct 2013 00:27:50 -0400
Received: from 99.23.162.168 by webmail.earthlink.net with HTTP; Mon, 21 Oct 2013 00:27:50 -0400
Message-ID: <11775960.1382329670750.JavaMail.root@elwamui-cypress.atl.sa.earthlink.net>
Date: Sun, 20 Oct 2013 21:27:50 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
Subject: RE: Separate ADs roles from IESG
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edbd7779ddccb840a4672d870a0653812e8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.32
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: Mon, 21 Oct 2013 04:28:03 -0000

Hi -

>From: Adrian Farrel <adrian@olddog.co.uk>
>Sent: Oct 20, 2013 1:12 PM
...
>Subject: RE: Separate ADs roles from IESG
...
>At the moment it is the IESG's responsibility to produce such
>statements and it is currently the IESG's responsibility to
>hear appeals etc.  That *seems* like a very different task
>from reviewing documents or keeping a WG within charter
>and working to its millstones.

This kind of re-factoring is the most appealing proposal
I've seen so far in these threads.  As I understand it,
it would replace the functional block currently labeled
"IESG" with multiple specialized blocks, which would be
able to process their respective workloads largely
independently.

Separating WG management, document management, appeals
management, and policy stuff would not only reduce the
workload suffered by each serving individual, but would
also allow us to make use of people with somewhat narrower
skillsets than IESG service currently demands.

Randy


From sm@resistor.net  Mon Oct 21 00:40:43 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 0B67A11E835F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 00:40:43 -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 rm1ljwJphFG3 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 00:40: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 CBA5311E8354 for <ietf@ietf.org>; Mon, 21 Oct 2013 00:40:34 -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 r9L7eTlM004401; Mon, 21 Oct 2013 00:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382341234; bh=nghT6jC4jpL0JE3B8sgYDZAoe32AXaa+kHdav4fPe/8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vog9p9AD+CPMLP4ACnpsNYPPFn4XYMCnNa1k4Wi3chb0MjukBuPTka7ieu4Zgr2fG hdi8BEEhFMNGe9JzQrZuC4VQFBJEOGeZIp9uHnLCnbrA5gEGBPFRhhjzEj23S0VG59 zIR+P1ZBVdFFRN3igZat/3xl+0fNi3FCHtE90jZA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382341234; i=@resistor.net; bh=nghT6jC4jpL0JE3B8sgYDZAoe32AXaa+kHdav4fPe/8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0KENj+lEk+GZvByO2QDp42UUAdY4iFppBWZct85mkxnYtr1mzZAT5HNWb6M9EGrq4 AYCGdg1S/jo8pRT1H8gOvpdRquHpgIUnF1RqvfCPWR9mYCSNxS/bcI/4KXzkcZPvF1 Fbr9NfI+CLHY2uuoPFcfwXzLFFqpQ9fzFSkIlpVQ=
Message-Id: <6.2.5.6.2.20131020213751.0bc83de8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Oct 2013 00:18:40 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Separate ADs roles from IESG - draft-klensin-stds-review-panel-00
In-Reply-To: <892B13B7BF164B38A8DB3793@[192.168.1.128]>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]>
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, 21 Oct 2013 07:40:43 -0000

Hi John,
At 07:18 20-10-2013, John C Klensin wrote:
>For an earlier and somewhat different take on this issue and a
>variation on a proposal, see the long-expired
>draft-klensin-stds-review-panel-00.

Some of the comments on the thread point to document review being 
less than a quarter the  time the Area Director spends weekly on the 
role.  draft-klensin-stds-review-panel-00 is a starting point to 
tackle the time commitment.

The document defines an Internet Standards Review Panel with 
responsibility for final  processing review of documents for 
standardization.  Section 2 mentions that the body would not have any 
role in negotiation the contents of documents.  It may sound like a 
hard line.  The question the Review Panel is asked is:

   Should the document be published?

It is a simple question and the answer can either be "yes" or 
"no".  The fairly hard line is better.  It is easy to lose sight of 
the specification as a whole when people focus on specific points in 
a specification.

In Section 2.1:

   "A clear shortage of competent and willing reviewers for a given
    specification should be taken as an indication that the specification
    is not of interest to the IETF community"

You and I could argue about whether the above is a good indication or 
not.  However, the fact is that if there isn't anybody to review the 
"has been reviewed by the IETF and is suitable for publication" is 
not applicable.

It is better to keep the membership (see Section 2.2) to a small 
number with people with specific (area) expertise and people with 
cross-area expertise.  It has been mentioned on the thread that some 
Area Directors only perform a detailed review when a proposal is 
relevant to their area.

Section 6.1.2.2 proposes that a Last Call can be requested for an 
Individual Submission if its proponents demonstrate that there is 
significant community support for the proposal.  It removes the 
perception of arbitrariness when the matter is subject to Area 
Director discretion.

It is worth giving some serious thought to the proposal.  Some people 
are good at steering.  Some people are good at performing technical 
reviews.  It may be easier for people to volunteer if the roles are separated.

 From a different message:

At 07:57 20-10-2013, John C Klensin wrote:
>What I haven't seen since the changes of the first half of the
>1990s is real community consensus that it is time to do
>something rather than agonize about particular symptoms (e.g.,
>Nomcom problems getting ample good candidates for all areas),
>complain or whine, and ultimately do nothing.

Yes.

Regards,
-sm 


From bclaise@cisco.com  Mon Oct 21 03:02:35 2013
Return-Path: <bclaise@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 5976B11E814D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.279
X-Spam-Level: 
X-Spam-Status: No, score=-10.279 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, J_CHICKENPOX_54=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 lh6bc+0jnp1n for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:02:30 -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 217DB11E8380 for <ietf@ietf.org>; Mon, 21 Oct 2013 03:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1511; q=dns/txt; s=iport; t=1382349692; x=1383559292; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xIX0TxiPSBY12+1OVBmfqf04ihmA9LiOzkwDo+mIfcw=; b=CywJA1sco4galwzvPppidlQxHvg3zpfjYndKFv1hre3vy+K6zGEswscy cGFmWMtWavSvqTIF/PUg6ORE6IyCyTYYYt0kx39X6w3zFXzsy5p7D4ODi hgIAWQmIx0wHiQbmvPIp5Jk2oMcXrrfaXill4ojfZeCAUoctfs35/FDLo U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAED6ZFKQ/khL/2dsb2JhbABZgwc4vwKBKRZ0giUBAQEEMgEFQAEQCxgJFg8JAwIBAgEPNgYNAQUCAQEFh2sDDw2zew2Ja4xsgTeBOQeEKQOWHoFrhjuGFYU3gyY6gTU
X-IronPort-AV: E=Sophos;i="4.93,538,1378857600"; d="scan'208";a="18897194"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 21 Oct 2013 10:01:30 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9LA1PTE023089; Mon, 21 Oct 2013 10:01:27 GMT
Message-ID: <5264FB75.6060109@cisco.com>
Date: Mon, 21 Oct 2013 12:01:25 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com> <87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org> <52605FCD.8000709@cs.tcd.ie> <290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk> <667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org> <68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com> <20131018141322.GI4003@mx1.yitter.info> <CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com> <30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com> <CABmDk8m4DRHwjCDaP5QZGsEyH2hSFqGA1QTnFwjktjsm8ZquoQ@mail.gmail.com> <F922B815-847B-4CCB-92F2-0C2EF2D3BB66@nominum.com> <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.com>
In-Reply-To: <4697AD08-FB6D-47BB-94A0-D24FCE97D59A@bogus.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: Mon, 21 Oct 2013 10:02:35 -0000

On 18/10/2013 18:45, joel jaeggli wrote:
> On Oct 18, 2013, at 9:38 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
>
>> On Oct 18, 2013, at 12:13 PM, Mary Barnes <mary.h.barnes@gmail.com> wrote:
>>> [MB] Can you clue us in as to what "substantial action" has been taken?   [/MB]
>> I thought we sent something around about that.   ADs and WG chairs are encouraged to ask for directorate reviews for certain directorates (possibly all directorates, I can't remember) prior to working group last call.   This is in the form of an experiment, not a new policy; we'll see how it goes.
>>
>> We've done a number of other things in the same vein—e.g., document shepherds are now being invited onto telechats, so that they can do the work of tracking action items for the authors rather than the AD doing it.
>>
>> I think there were other items on the list, but I don't remember them off the top of my head.   The point is, if anybody thinks the IESG is a deer in the headlights on this issue, that's not the case—we are actively trying to do things to ameliorate the situation.
> The revision of the qualifications provided to the nomcom was signficant.
>
> experiments with narrative shepherds reports.
>
> experiments with post-ietf working-group summaries performed by chairs.
See http://www.ietf.org/mail-archive/web/ietf/current/msg79194.html
Specifically the entry"Send more documents back to the WG to complete 
the necessary changes." should help in terms of AD load.

Regards, Beonit

>


From bclaise@cisco.com  Mon Oct 21 03:15:57 2013
Return-Path: <bclaise@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 9BA3E11E838A for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.576
X-Spam-Level: 
X-Spam-Status: No, score=-10.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 K-bulpq3QgS2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:15:50 -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 AB07711E8385 for <ietf@ietf.org>; Mon, 21 Oct 2013 03:15:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1377; q=dns/txt; s=iport; t=1382350508; x=1383560108; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=nkTRdSeefgZdr/UXJcpjRoqg91qhOdjnO0L2vYrv3w8=; b=j1237nm5U7/knA6Nd/bpaCn0MNH/Gb93mibJtvCJ/1rMSWdIJItXL0br Ih4SM2o8kDwFQUkUfdWhu1LraPVf8e96DLhvqQ9bQOTmToPRGOFGf+s6k estN8jKfxcfDPVCFebs7cSyLNHCtq4c7oaKDKVqNxLsUrgtDdKUNkGCKf U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAMP9ZFKQ/khR/2dsb2JhbABZgwe8PoJ8gSoWdIIlAQEBAwE4QAEQCxgJFg8JAwIBAgFFBg0BBwEBh3wGvgePXAeEKQOYCYY7i0yDJjo
X-IronPort-AV: E=Sophos;i="4.93,538,1378857600"; d="scan'208";a="18421589"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 21 Oct 2013 10:15:04 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9LAF0GF022233; Mon, 21 Oct 2013 10:15:01 GMT
Message-ID: <5264FEA3.8080802@cisco.com>
Date: Mon, 21 Oct 2013 12:14:59 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>	<493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org> <52627F96.7060808@pi.nu> <52629028.8000901@cs.tcd.ie>
In-Reply-To: <52629028.8000901@cs.tcd.ie>
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: Mon, 21 Oct 2013 10:15:57 -0000

On 19/10/2013 15:59, Stephen Farrell wrote:
>
> On 10/19/2013 01:48 PM, Loa Andersson wrote:
>> On the other hand a less more public way would be to what IAB on
>> their RFCs, add a section "IAB Members at the Time of Approval"!
>> Maybe and Appendix "WG Chairs, Shepherd and responsible AD at the
>> time of the Approval".
> Keep it informal - authors can do this now if they want. (And
> we can stop discussing it:-)
>
> Personallly, I'd encourage authors to not add ADs unless there's
> a specific reason. Within an IETF context, ADs get enough ego
> boosting already.
Agreed.
>
> But WG chairs do deserve more acks than they're getting I think
> so if authors ack'd them frequently that'd be good.
... as well as document shepherd, and directorate reviewers.
As Randy Presuhn mentioned somewhere in the conversion, MIB module 
reviews (by the MIB doctors) is a very ungrateful job. The job takes a 
lot of time, much discussions, sometimes many document iterations. Those 
MIB doctors will never appear on the author lists (sometimes they should 
when I see the huge job), or are rarely mentioned in the acknowledgment 
section.
No wonder I have some difficulties to find directorate reviewers.

I'm all in favor of properly acknowledging people.
However, having a formal set of rules would NOT be a good thing.

Regards, Benoit

>
> S.
>


From loa@pi.nu  Mon Oct 21 03:40:04 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 B3CC211E818C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.621
X-Spam-Level: 
X-Spam-Status: No, score=-102.621 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 BEa3ukYilxgp for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:39:57 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 128CF11E84F8 for <ietf@ietf.org>; Mon, 21 Oct 2013 03:37:39 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.116.3]) (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 AFCAA18014F6; Mon, 21 Oct 2013 12:37:33 +0200 (CEST)
Message-ID: <526503EA.1050109@pi.nu>
Date: Mon, 21 Oct 2013 18:37:30 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>	<493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org> <52627F96.7060808@pi.nu> <52629028.8000901@cs.tcd.ie> <5264FEA3.8080802@cisco.com>
In-Reply-To: <5264FEA3.8080802@cisco.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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 10:40:04 -0000

On 2013-10-21 18:14, Benoit Claise wrote:
<snip>
>> Personallly, I'd encourage authors to not add ADs unless there's
>> a specific reason. Within an IETF context, ADs get enough ego
>> boosting already.
> Agreed.

Sigh, while I think most the folks speaking up here agree to that,
it seems almost impossible to get the other side of this through.
Mentioning ADs/WG chairs are not only to give them credit for a
particular document that has been published as an RFC.

It is also easily find whom you need to hold accountable, a couple of
ADs and a few IESG generations later.

his is why I'm reluctant to place this in the Ack section, and prefer
some place similar (read "new section".

/Loa

>
>>
>> S.
>>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From ynir@checkpoint.com  Mon Oct 21 03:51:31 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 29A6111E814F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.435
X-Spam-Level: 
X-Spam-Status: No, score=-10.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 zhfpDMBFWPND for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 03:51:24 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 10A5D11E818C for <ietf@ietf.org>; Mon, 21 Oct 2013 03:51:23 -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 r9LApJ8X006478; Mon, 21 Oct 2013 13:51:19 +0300
X-CheckPoint: {526506AD-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.106]) by DAG-EX10.ad.checkpoint.com ([169.254.3.213]) with mapi id 14.03.0123.003; Mon, 21 Oct 2013 13:51:06 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: Separate ADs roles from IESG
Thread-Topic: Separate ADs roles from IESG
Thread-Index: AQHOzYjG4BuTzhIUFk+7GQ0vLzw0mZn9WEWAgAAQUACAAAiKAIAAWX+AgAAEcgCAAPqCAA==
Date: Mon, 21 Oct 2013 10:51:06 +0000
Message-ID: <A8F9355A-5499-4FDE-A668-E919504E900F@checkpoint.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com>
In-Reply-To: <52643500.3010406@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.16]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F9285036EB5A7549A1BD2FE44D3B0529@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 10:51:31 -0000

Hi, Joel

I think this assumes that the quality of the document set that is the outpu=
t of the IETF is the responsibility of the particular AD.

The proposal as I see it is that there is a different review body. So when =
the working group is done with a document, the AD may review it (or leave i=
t to the shepherd), call the IETF last-call, and then both AD and shepherd =
present it to the review panel. That means that the IESG no longer has bi-w=
eekly meetings to approve documents, because that is the function of the re=
view panel. The AD and shepherd join a conference call with the review pane=
l, but only for the document they are championing.

This means that the responsibility for quality control of a particular docu=
ment and for the entire body of IETF RFCs rests with the review panel, free=
ing the IESG members to set up, recharter, and close working groups, and do=
 the other things. They can still review things (like everybody else).

One advantage of this is that we can align the reviews along different line=
s from those that the areas are split along. For example, the Security area=
 deals with all kinds of security protocols, many of them related to crypto=
graphy. So there's protocols like TLS, IPsec, and Kerberos. This is a wholl=
y separate thing from the security of a particular protocol or from securit=
y considerations for its implementation. It's important for TLS to be secur=
e, but it is no less important for HTTP to be secure. And yet SecDir review=
s have become security reviews. They look at the protocol and the security =
considerations section, not in particular to how the proposal works with se=
curity area protocols. What SecDir (and the security ADs) check has only a =
tenuous relationship to what the security area works on.=20

This is even more clear with the routing area. There is a routing area beca=
use there is a lot of work on routing protocols, not because every protocol=
 out there is somehow related to routing. Is there any particular value in =
a review of some generic protocol (say, HTTP/2.0) by a routing area directo=
rate or by a routing area director? This is not a dig at Stewart and Adrian=
. They may have a lot of meaningful things to say about HTTP/2.0, but I don=
't think that has anything to do with their routing area position or expert=
ise.

Separating the review function from the IESG allows us to find reviewers al=
ong particular relevant review topics: (just off the top of my head)
 - security (both considerations for implementing and the security of the p=
rotocol itself)
 - deployability (has the working group considered interactions with all ki=
nds of middleboxes? Does it require any non-generally available infrastruct=
ure? Does it require high bandwidth to function properly?)
 - usability (when protocols have interaction with a user interface, does t=
he document cover that enough?)
 - networking impact (would it cause congestion? would it slow down other f=
lows?)

There could be more areas. The review panel could use its own permanent mem=
bers, or call in subject matter experts for particular protocols.

The question, though, is how much would that reduce the load on the IESG. I=
f all we've done is get it down from 35 hours/week to 28 hours/week, I'm no=
t sure it's worth it, because you still can't hold another full-time job.

Yoav


On Oct 20, 2013, at 10:54 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> The obvious risk if one separates WG management from review is that one c=
ould easily get the situation where the manager, in working with the WG, sa=
ys that the document needs X, Y, and not Z.  And then the reviewer says "ne=
eds Z".  And there are more extreme versions of this.
> Currently, the ability for the managing AD to say "no, this won't pass mu=
ster" is part of his management tool.  If he is not the reviewer, he seems =
to have lost an important tool.  I hope I am missing something that would m=
ake this sort of approach workable.
>=20
> Yours,
> Joel


From bclaise@cisco.com  Mon Oct 21 04:00:19 2013
Return-Path: <bclaise@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 40E7011E8279 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 04:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.577
X-Spam-Level: 
X-Spam-Status: No, score=-10.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 d0AId6DNJ5Uk for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 04:00:12 -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 880EA11E83A3 for <ietf@ietf.org>; Mon, 21 Oct 2013 03:59:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1080; q=dns/txt; s=iport; t=1382353193; x=1383562793; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=IdW/VawDneiGKMNpvcw6rgMrlQ42JjaicMWcKVoeMWI=; b=gtPFWhudOzXvKkrU82s6V1jy+0VIyapa84zkT5zZeu6OtgkZ/f1vcNi1 REiozu9NFT9Hb/y2KNbzbu4uBHAKQhnkSHKGc+p4O44rBmMI29HqQgBbR wQzTSlLz54Qcv+3oTtmv4ogiAl8q4UE4kcj7fhs/MmdcrLLLQCk1zMxbZ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUNAE4IZVKQ/khR/2dsb2JhbABZgXEGgRC8PoJ8gSwWdIIlAQEBAwE4QAEQCxgJFg8JAwIBAgFFBg0BBwEBEIdsBr1sj1wHhCkDmAmGO4tMgyY6
X-IronPort-AV: E=Sophos;i="4.93,538,1378857600"; d="scan'208";a="18422503"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 21 Oct 2013 10:59:52 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9LAxlLm002235; Mon, 21 Oct 2013 10:59:49 GMT
Message-ID: <52650923.8000101@cisco.com>
Date: Mon, 21 Oct 2013 12:59:47 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
Subject: Re: Proper credit for work done -- on finding chairs (was CHANGE THE	JOB)
References: <CAC4RtVDSFnG70g22VnpE3xGAH4kWsYCRzJTvZk-LcX3YCKkSkw@mail.gmail.com>	<87B31A55-6516-416D-94C7-407B55B9A3A8@tzi.org>	<52605FCD.8000709@cs.tcd.ie>	<290E20B455C66743BE178C5C84F12408374274D590@EXMB01CMS.surrey.ac.uk>	<667F3CD2-F7B2-4B5C-8201-F45502B18306@tzi.org>	<68E38B413DEA2B7C139A155A@JcK-HP8200.jck.com>	<20131018141322.GI4003@mx1.yitter.info>	<CAP8yD=t7V7Xt06=OVEkUU295p9k4xCDv8G8HoCyP1T4+OeXY4A@mail.gmail.com>	<30F97DC9-E780-4E03-96E8-0C7623B75C7E@nominum.com>	<5261F82E.7030800@pi.nu>	<B151A850-C8BE-4C33-B9C2-C06286129183@nominum.com>	<1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<EMEW3|1bad4ec02d631c8430f83ad5505e51c5p9ICJO03tjc|ecs.soton.ac.uk|1B0C2D25-7DBB-4BFE-8554-5D77DAC54A2B@ecs.soton.ac.uk>	<079d01ceccbf$a9b9f7c0$fd2de740$@olddog.co.uk>	<493BDF75-E4E9-4C86-96C4-4640746A90F2@tzi.org> <52627F96.7060808@pi.nu> <52629028.8000901@cs.tcd.ie> <5264FEA3.8080802@cisco.com> <526503EA.1050109@pi.nu>
In-Reply-To: <526503EA.1050109@pi.nu>
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: Mon, 21 Oct 2013 11:00:19 -0000

On 21/10/2013 12:37, Loa Andersson wrote:
>
>
> On 2013-10-21 18:14, Benoit Claise wrote:
> <snip>
>>> Personallly, I'd encourage authors to not add ADs unless there's
>>> a specific reason. Within an IETF context, ADs get enough ego
>>> boosting already.
>> Agreed.
>
> Sigh, while I think most the folks speaking up here agree to that,
> it seems almost impossible to get the other side of this through.
> Mentioning ADs/WG chairs are not only to give them credit for a
> particular document that has been published as an RFC.
My statement above was only about AD, not WG chairs.
>
> It is also easily find whom you need to hold accountable, a couple of
> ADs and a few IESG generations later.
Interesting statement about AD and WG charis being "accountable for"? My 
views are that the document authors, the WG, and the community are 
accountable for the document content.

Regards, Benoit

>
> his is why I'm reluctant to place this in the Ack section, and prefer
> some place similar (read "new section".
>
> /Loa
>
>>
>>>
>>> S.
>>>
>>
>


From hallam@gmail.com  Mon Oct 21 04:09: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 9F5D111E8270 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 04:08:59 -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 8d4NZ19PMl45 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 04:08:59 -0700 (PDT)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 36A7211E821D for <ietf@ietf.org>; Mon, 21 Oct 2013 04:08:57 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id w6so5362007lbh.33 for <ietf@ietf.org>; Mon, 21 Oct 2013 04:08: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=1NxQVnMGDzjDcT3lNkJvNfYU0B04cVWsdfiA5GLlmTA=; b=ya25mlODtP0h2ybxiUSWUssVhOo970LfVEt1LEKY6lcUihTlaFuDhtXeGYaFR2dG/W S9mRxJqy1CdXms1FA6TmOj8slE8x3PLW+3TOm5evhVx8bT8T2wWoVr/Sxl0cwXAnI2I5 9/54VsLLUJg3xl6Otoh2RS3Lo0n3PazzIh1XTH6p+82eVzg9aaNZVDjg9AaS+U58u32p mRBsMlFqBxGoexT2sECVUdBVGi2AtNfTakNWsUYJbbgSq346viJmFX8mEMCbeNTPrEL4 dCNgPORgHKQEjT6cYQ9cYUy3OJYXkcO5Uc1z6nNd/Aezw+c3Nanhrnt+7Krpu93tAF4g b48Q==
MIME-Version: 1.0
X-Received: by 10.112.158.225 with SMTP id wx1mr869623lbb.37.1382353736066; Mon, 21 Oct 2013 04:08:56 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 04:08:55 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20131020213751.0bc83de8@resistor.net>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@192.168.1.128> <6.2.5.6.2.20131020213751.0bc83de8@resistor.net>
Date: Mon, 21 Oct 2013 07:08:55 -0400
Message-ID: <CAMm+Lwj4T6o2n3_OWdesnB0E=_p=QvEQX57coo_kgJsbU72=vA@mail.gmail.com>
Subject: Re: Separate ADs roles from IESG - draft-klensin-stds-review-panel-00
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=001a11c34932646cd704e93e4fe9
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: Mon, 21 Oct 2013 11:09:00 -0000

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

The three questions of power:

1 How did you get it?
2 For whose benefit do you use it?
3 How do we get rid of you?

Unless there are satisfactory answers to 1 and 3, the answer to 2 is going
to always be unacceptable. Concentrating decision making power in yet
another unelected, unaccountable body is not viable.

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

<div dir=3D"ltr">The three questions of power:<div><br></div><div>1 How did=
 you get it?</div><div>2 For whose benefit do you use it?</div><div>3 How d=
o we get rid of you?</div><div><br></div><div>Unless there are satisfactory=
 answers to 1 and 3, the answer to 2 is going to always be unacceptable. Co=
ncentrating decision making power in yet another unelected, unaccountable b=
ody is not viable.=A0</div>
<div><br></div><div><br></div></div>

--001a11c34932646cd704e93e4fe9--

From bclaise@cisco.com  Mon Oct 21 05:49:35 2013
Return-Path: <bclaise@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 5547521F9228 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 05:49:35 -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 f+g4p04WDUKT for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 05:49:30 -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 6729621F898A for <ietf@ietf.org>; Mon, 21 Oct 2013 05:49:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1753; q=dns/txt; s=iport; t=1382359768; x=1383569368; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=p4w3S9t+IDfae0tmKkBh12Yx6VajuaLDX2bqFNJhIFs=; b=RYjEIJcoqkiUhbiNcuO1oM5M5PQK+q5jqUt/cw5oL3WGYAEAKUwQnpFr iicTFHzXz365zrEf8OHRbx9ynVf1pe8xcE1Rh8jW+M5d4EqwgsK0gAL3h jW2pa8Kt60DIgMTsqvlxd0QcAN++admTfjalZO09+jCgma9nX9jNn2vXr s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAFAJshZVKtJXHA/2dsb2JhbABZgwe8PoJ8gSwWdIIlAQEBAwEdG0EFCwsYCSUPAkYTAQcBAYd8Br1qj1wHFoQTA5gJhjuLTIFmgUA6
X-IronPort-AV: E=Sophos;i="4.93,539,1378857600"; d="scan'208";a="274587010"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 21 Oct 2013 12:49:25 +0000
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r9LCnNDM024270;  Mon, 21 Oct 2013 12:49:23 GMT
Message-ID: <526522D3.40606@cisco.com>
Date: Mon, 21 Oct 2013 14:49:23 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
References: <047e01cecb70$2f271830$8d754890$@olddog.co.uk>	<94FC4BCE7D1E7B72E40F9FE0@JcK-HP8200.jck.com>	<061e01cecc02$d5685af0$803910d0$@olddog.co.uk> <CABCOCHRsD3TOdfdpZa1WG_4BUdJsNZ9A=kXc+hC-e86Tg-XKxQ@mail.gmail.com> <067601cecc17$60613320$21239960$@olddog.co.uk>
In-Reply-To: <067601cecc17$60613320$21239960$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'John C Klensin' <john-ietf@jck.com>, 'IETF Discuss' <ietf@ietf.org>, 'Andy Bierman' <andy@yumaworks.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: Mon, 21 Oct 2013 12:49:35 -0000

On 18/10/2013 17:33, Adrian Farrel wrote:
>> I have asked you and other ADs several times if Assistant ADs would help.
>> The answer I got was "not really, but a well run directorate really helps.".
> OK. Doesn't sound like refusing to consider. Sounds like answering your
> question.
>
> So let's take it to the next step because it may be that the current IESG cannot
> conceive of how an assistant AD would work.
>
> Can you put up a strawman of the job tasks of an assistant AD that we can work
> with to discuss whether this has legs?
> Would assistant ADs be appointed and work for sitting ADs, or would they be
> NomCom appointments?
> Can't an AD already delegate anything they want (except the responsibility)?
>
>> Why not double the number of ADs in each area and instead of
>> every AD reviewing every draft, have 2 ADs from each area
>> review each draft? (Cut the AD hours in half somehow)
> There is mileage in that. I don't think every AD reviews every document. Some
> pairs of ADs consciously split the load. Some ADs don't do detailed reviews of
> documents in other areas or just focus on specific topics.
>
> But we must get off the idea that document review is the whole of the AD load. I
> think it is only around 15-20%.

For me, it's 3 days of reviewing documents and WG charters for the IESG formal telechat. Sometimes 4.
So 3/10 to 4/10 = 30 to 40%
To be fair, the more experienced an AD is, the less time it takes.

Then, there are documents from the WG, on which I spend a lot of time.

Regards, Benoit

> Maybe that rises with pursuit of Discusses
> (moral: don't raise Discusses). That doesn't mean that other parts of the load
> couldn't be shifted.
>
> Cheers,
> Adrian
>
> .
>


From bortzmeyer@nic.fr  Mon Oct 21 05:59:57 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FBD711E82DA for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 05:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DXkDMzEBTDkt for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 05:59:42 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 71AA811E83A9 for <ietf@ietf.org>; Mon, 21 Oct 2013 05:59:39 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 104A52803C2 for <ietf@ietf.org>; Mon, 21 Oct 2013 14:59:05 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 0C78A2801BF for <ietf@ietf.org>; Mon, 21 Oct 2013 14:59:05 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 00F65B38003 for <ietf@ietf.org>; Mon, 21 Oct 2013 14:58:35 +0200 (CEST)
Date: Mon, 21 Oct 2013 14:58:34 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Internet standardisation remains unilateral
Message-ID: <20131021125834.GA24167@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
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: Mon, 21 Oct 2013 12:59:57 -0000

What did they say, in the movie Apocalypse Now? "I like the smell of
the troll in the morning"?

http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf

From jason_livingood@cable.comcast.com  Mon Oct 21 06:04:29 2013
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC1811E8523; Mon, 21 Oct 2013 06:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.231
X-Spam-Level: 
X-Spam-Status: No, score=-105.231 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, 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 Kw1l5KGM6-v5; Mon, 21 Oct 2013 06:04:22 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 10E3311E850A; Mon, 21 Oct 2013 06:03:47 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.100553114; Mon, 21 Oct 2013 07:03:39 -0600
Received: from PACDCEXHUB05.cable.comcast.com (24.40.56.122) by PACDCEXHUB01.cable.comcast.com (24.40.56.114) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 21 Oct 2013 09:03:32 -0400
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.177]) by pacdcexhub05.cable.comcast.com ([fe80::3d40:bdea:7266:7f5a%18]) with mapi id 14.02.0318.001; Mon, 21 Oct 2013 09:03:32 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbwuD9g9wrKHT0SdLydQwVdIu5n+kDuAgACQMIA=
Date: Mon, 21 Oct 2013 13:03:32 +0000
Message-ID: <10229F86C86EB444898E629583FD4171E3D7313D@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <m2wql7tqmm.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [68.87.16.248]
x-wiganss: 0100000001001Epacdcexhub05.cable.comcast.com ID0048<10229F86C86EB444898E629583FD4171E3D7313D@PACDCEXMB06.cable.comcast.com>
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AF04E516B7F89740B87651B745C342F0@cable.comcast.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, 21 Oct 2013 13:04:30 -0000

+1


Looks good and similar to what many companies have been doing for some
time -- good to bring these sorts of things to the IETF as well.

Jason

On 10/20/13 8:27 PM, "Randy Bush" <randy@psg.com> wrote:

>seems an excellent start.  let's fly with it for a while and see how it
>goes.  thanks for this.
>
>randy


From scott.brim@gmail.com  Mon Oct 21 06:10:42 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 8FCD711E8571; Mon, 21 Oct 2013 06:10:42 -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 VY8EbSdVZ07O; Mon, 21 Oct 2013 06:10:41 -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 945C211E8562; Mon, 21 Oct 2013 06:08:01 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id h1so3996253oag.10 for <multiple recipients>; Mon, 21 Oct 2013 06:08:00 -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=SxwRXN3Oo3SQ5cnijuAn4QUoQ9wpIql+utHQIJyVlCE=; b=ezsWUPhiwMsYOSv0Nd0swbyJE9fvrHLbQQeXjGwAqFoLDd/EeL/cm1PmOATKqaRA8z sVvvrVSbapw1DEKpEsNSohG9fmhqXT52tB9cg1GuxG4e4sUUexMCPicgWi0+dMlt3cOV Wq1aEVPoDfPswCidzF3feUWD2d6IgjrityQNHa3AWfLJNci67TjSmVIVMSiOu9Kl5DfJ 4z/C41C8hIMpUzavo00rQ3p/1DidnpRv1/Pv6/u5boRs3UChzUzZLxsdXxvr5v+ggVtf NcUJy7LYI+T4+s4ZVs5DkEPzNcC0SOkpErUhdEU2Aw5zyf6a2gxRFknqQIxTnMk40K1z gVcw==
MIME-Version: 1.0
X-Received: by 10.60.115.164 with SMTP id jp4mr7018681oeb.19.1382360559714; Mon, 21 Oct 2013 06:02:39 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Mon, 21 Oct 2013 06:02:39 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Mon, 21 Oct 2013 06:02:39 -0700 (PDT)
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
Date: Mon, 21 Oct 2013 09:02:39 -0400
Message-ID: <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Scott Brim <scott.brim@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e01161b461d0a7b04e93fe6d1
Cc: IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 13:10:42 -0000

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

While I'm completely in favor of the goals, I don't like this sentence:
"Participants asked to stop any harassing behavior are expected to comply
immediately." The problem is that this sentence assumes a clear agreed-on
definition of harassment, while it should be based on subjective
experience. If I say "Randy, that's harassment and I want you to stop," he
may respond "No it isn't."  I propose something like: "Participants asked
to stop a behavior that is being experienced as harassment are expected to
comply immediately."

Scott

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

<p dir=3D"ltr">While I&#39;m completely in favor of the goals, I don&#39;t =
like this sentence: &quot;Participants asked to stop any harassing behavior=
 are expected to comply<br>
immediately.&quot; The problem is that this sentence assumes a clear agreed=
-on definition of harassment, while it should be based on subjective experi=
ence. If I say &quot;Randy, that&#39;s harassment and I want you to stop,&q=
uot; he may respond &quot;No it isn&#39;t.&quot;=A0 I propose something lik=
e: &quot;Participants asked to stop a behavior that is being experienced as=
 harassment are expected to comply immediately.&quot; </p>

<p dir=3D"ltr">Scott </p>

--089e01161b461d0a7b04e93fe6d1--

From dhc@dcrocker.net  Mon Oct 21 06:11:09 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 BF34B11E8539 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:11:08 -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 mYtngowgPaC1 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:11:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CC67811E8546 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:08:55 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9LD8nOo012652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 Oct 2013 06:08:52 -0700
Message-ID: <5265275B.8040105@dcrocker.net>
Date: Mon, 21 Oct 2013 09:08:43 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr>
In-Reply-To: <20131021125834.GA24167@nic.fr>
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, 21 Oct 2013 06:08:53 -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, 21 Oct 2013 13:11:09 -0000

On 10/21/2013 8:58 AM, Stephane Bortzmeyer wrote:
> What did they say, in the movie Apocalypse Now? "I like the smell of
> the troll in the morning"?
>
> http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf


Oh my.  Louis Pouzin is quite a long way from being a troll:

      http://en.wikipedia.org/wiki/Louis_Pouzin

He invented the datagram...

I think his slides do miss some essential points, but that it's a case 
of correct numbers producing incorrect recommendations.

So his suggestion to submit to national standards bodies represent a 
very reasonable desire for broader participation, albeit down a path I'd 
expect to be counter-productive.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From mcr@sandelman.ca  Mon Oct 21 06:12:43 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 D346F11E85A9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:12:42 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlmRHsrFo29I for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:12:38 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3AE11E855E for <ietf@ietf.org>; Mon, 21 Oct 2013 06:10:08 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id F30C42025A for <ietf@ietf.org>; Mon, 21 Oct 2013 10:20:49 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id DEF1963B88; Mon, 21 Oct 2013 09:10:02 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CF5BC63AED for <ietf@ietf.org>; Mon, 21 Oct 2013 09:10:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org" <ietf@ietf.org>
Subject: Re: NOMCOM - Critical shortage of nominees for multiple areas
In-Reply-To: <AF1F1D53-41D2-4E1B-88E8-41D0B7FB97B7@netapp.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <AF1F1D53-41D2-4E1B-88E8-41D0B7FB97B7@netapp.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: Mon, 21 Oct 2013 09:10:02 -0400
Message-ID: <26769.1382361002@sandelman.ca>
Sender: 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: Mon, 21 Oct 2013 13:12:43 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Eggert, Lars <lars@netapp.com> wrote:
    >> in your model you don't count those people who have been rejecting t=
o a nomination,=20
    >> just because they believe the current AD did a very good job and he/=
she should be reelected.

    > that is not a good reason to turn down a nomination!

    > It's normally not known whether the incumbent can/will continue. Even
    > if it is known, stuff happens, sometimes late in the process, and the
    > incumbent needs to drop out. If there are no other candidates, we then
    > need to go into panic mode.=20

Or, the incumbent gets moved laterally.
Or, in the case if the IAB, an existing IAB member (non-incumbent) gets
"poached" for another position.
Or, the nomcom has reasons to remove the incumbent, or limit their term.

=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)

iQCVAwUBUmUnqoqHRg3pndX9AQJfZAP/beVmzwbjVQ0m4/Ot8GCB190XUSeJemj4
iSM86wMF3syHrsE8hqYpm92PG8W+9Oh+XEZQ23v2Zk5ZyaiAV4Pudr8YgQ9zmM4Y
QSnqODJSCWwo3JrGZns8cA0pVhL4FuXVSMiOKSQ6TG3mCsYvl1v6Y8gHgo2otiS0
M9jJOvOYrgo=
=8sps
-----END PGP SIGNATURE-----
--=-=-=--

From ted.ietf@gmail.com  Mon Oct 21 06:28:57 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 4BD8411E83B7 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  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 nQo+QzMMuWNh for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:28:56 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 42DCB11E8524 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:27:52 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id u16so11243280iet.4 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:27:51 -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=1lcOvzenNQQdjYDS6jERiFTCZq69wDhLTkDTtd7ZsP8=; b=GvsRxDNeBGYy2gHO5LemetsQUCEFwTzq7GV2T0QKfhjfnRlYtRBLmaOTyh5efcUFkT 2H2pSnUMKhKsiDgzPtudjOdaOFTFb4Gv61PhNJwBzFM2euSQPPUVsd/HSCxh+dOtnoDG bZdqB/rYOBmPhDc35ZmA/VFotxmJufqY6DrJqUMo0POQezcw3pC31sQ1jkGwzoGV0vE7 f6A0YehEyCUnX4ACIkStWrKaZnppWuZyWDZCRcfM+660bvHpAyOH4bADsKrgzLA/Czp7 9TEsUtG/RhuGnhLEsWNtnjOJnHvKkRM/USpsaWZIP1WQllLjXeVcn3WqFMBBCcFwJVlm eOYg==
MIME-Version: 1.0
X-Received: by 10.50.120.10 with SMTP id ky10mr9355799igb.29.1382362071092; Mon, 21 Oct 2013 06:27:51 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Mon, 21 Oct 2013 06:27:50 -0700 (PDT)
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
Date: Mon, 21 Oct 2013 06:27:50 -0700
Message-ID: <CA+9kkMBr0g1dQzjnZp0RZG5iwpuB8CTeJr2yhSPyuRYDMMqRRQ@mail.gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7ba9823232d46e04e94040bb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 13:28:57 -0000

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

This is a good idea.  If the professionals thinking this is the right
wording, that is also fine by me.

I do note the phrase "harassing photography or recording";  I believe our
current rules say "written, audio and video records of meetings may be made
and may be available to the public."  It may be appropriate to adjust it to
something like "harassing photography or recording of individuals outside
their roles as participants" or to otherwise clarify how photography
becomes harassment.

regards,

Ted Hardie


On Sun, Oct 20, 2013 at 10:44 AM, IETF Chair <chair@ietf.org> wrote:

> The IETF should be an open and accessible body in which any individual
> feels
> able to participate without fear of oppression or harassment.  The IESG has
> become aware of some incidents of concern, is aware of various incidents
> in our
> industry in general, and has also observed that many similar organisations
> and
> conferences have a policy on this matter.
>
> In order to ensure the right atmosphere and to provide a suitable
> environment,
> the IESG has decided that it is desirable to write a simple and
> straightforward
> policy on harassment. This is not only to remind participants not to harass
> others (something that we hope is obvious to us all), but also to let
> anyone who
> it the target of harassment know that we take these matters seriously and
> that
> there is something they can do to address these sorts of incidents should
> they
> occur.
>
> A small design team has looked at existing policies used by other groups
> similar
> to the IETF and consulted with some of the ISOC professionals with
> expertise in
> human resources and issues of workplace harassment. The design team has put
> together what the IESG feels is a good anti-harassment policy for the
> IETF: It
> is short and to the point, it is modeled on and makes heavy re-use of the
> language of existing policies, and it sets forth reasonable procedures for
> the
> IETF.
>
> The IESG intends to put in place Ombudspersons as confidential initial
> contact
> points for situations where there is a concern of harassment. The
> selection of
> Ombudspersons will happen later, and the person(s) will have appropriate
> training and expertise.
>
> The IESG plans to adopt this as an IESG Statement. We solicit your
> feedback. We
> understand that this is a difficult and sensitive topic to discuss, but we
> do
> want your comments. If you feel more comfortable sending comments directly
> to
> the IESG <iesg@ietf.org> rather than discussing them on the IETF list,
> please
> feel free to do so.
>
> Jari Arkko for the IESG
>
> --- Draft Statement ---
>
> IETF Anti-Harassment Policy
>
> IETF meetings, virtual meetings, and mailing lists are intended for
> professional
> collaboration and networking. The IETF strives to create and maintain an
> environment in which people are treated with dignity, decency, and respect.
> Those who participate in the IETF are expected to behave according to
> professional standards and demonstrate appropriate workplace behavior.
> While
> participating in the IETF, communication between participants should be
> appropriate for a professional audience including people of many different
> backgrounds.
>
> While our processes let chairs deal with disruptive public behaviors on
> mailing
> lists and in IETF face-to-face meetings, harassment is a serious problem
> that
> warrants special attention. IETF participants should not engage in
> harassment
> while at IETF meetings, virtual meetings, social events, or on mailing
> lists.
> Harassment is unwelcome hostile or intimidating behavior, in particular
> speech
> and behavior that is sexually aggressive or intimidates based on
> attributes like
> race, gender, religion, age, color, national origin, ancestry, disability,
> sexual orientation, or gender identity. Harassment of this sort will not be
> tolerated in the IETF. Harassment includes the use of offensive language or
> sexual imagery in public presentations and displays, degrading verbal
> comments,
> deliberate intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, and unwelcome sexual attention.
>
> Participants asked to stop any harassing behavior are expected to comply
> immediately. If you believe you have been harassed, notice that
> someone else is being harassed, or have any other concerns, you are
> encouraged
> to raise your concern in confidence with one of the Ombudspersons.
>
> If these standards are violated, appropriate action will be taken.
>

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

<div dir=3D"ltr">This is a good idea.=A0 If the professionals thinking this=
 is the right wording, that is also fine by me.=A0 <br><br>I do note the ph=
rase &quot;harassing photography or recording&quot;;=A0 I believe our curre=
nt rules say &quot;written, audio and video records of meetings may be made=
 and may be available to the public.&quot;=A0 It may be appropriate to adju=
st it to something like &quot;harassing photography or recording of individ=
uals outside their roles as participants&quot; or to otherwise clarify how =
photography becomes harassment.<br>
<br>regards,<br><br>Ted Hardie<br></div><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Sun, Oct 20, 2013 at 10:44 AM, IETF Chair <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:chair@ietf.org" target=3D"_blank">chai=
r@ietf.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">The IETF should be an open and accessible bo=
dy in which any individual feels<br>
able to participate without fear of oppression or harassment. =A0The IESG h=
as<br>
become aware of some incidents of concern, is aware of various incidents in=
 our<br>
industry in general, and has also observed that many similar organisations =
and<br>
conferences have a policy on this matter.<br>
<br>
In order to ensure the right atmosphere and to provide a suitable environme=
nt,<br>
the IESG has decided that it is desirable to write a simple and straightfor=
ward<br>
policy on harassment. This is not only to remind participants not to harass=
<br>
others (something that we hope is obvious to us all), but also to let anyon=
e who<br>
it the target of harassment know that we take these matters seriously and t=
hat<br>
there is something they can do to address these sorts of incidents should t=
hey<br>
occur.<br>
<br>
A small design team has looked at existing policies used by other groups si=
milar<br>
to the IETF and consulted with some of the ISOC professionals with expertis=
e in<br>
human resources and issues of workplace harassment. The design team has put=
<br>
together what the IESG feels is a good anti-harassment policy for the IETF:=
 It<br>
is short and to the point, it is modeled on and makes heavy re-use of the<b=
r>
language of existing policies, and it sets forth reasonable procedures for =
the<br>
IETF.<br>
<br>
The IESG intends to put in place Ombudspersons as confidential initial cont=
act<br>
points for situations where there is a concern of harassment. The selection=
 of<br>
Ombudspersons will happen later, and the person(s) will have appropriate<br=
>
training and expertise.<br>
<br>
The IESG plans to adopt this as an IESG Statement. We solicit your feedback=
. We<br>
understand that this is a difficult and sensitive topic to discuss, but we =
do<br>
want your comments. If you feel more comfortable sending comments directly =
to<br>
the IESG &lt;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt; rather =
than discussing them on the IETF list, please<br>
feel free to do so.<br>
<br>
Jari Arkko for the IESG<br>
<br>
--- Draft Statement ---<br>
<br>
IETF Anti-Harassment Policy<br>
<br>
IETF meetings, virtual meetings, and mailing lists are intended for profess=
ional<br>
collaboration and networking. The IETF strives to create and maintain an<br=
>
environment in which people are treated with dignity, decency, and respect.=
<br>
Those who participate in the IETF are expected to behave according to<br>
professional standards and demonstrate appropriate workplace behavior. Whil=
e<br>
participating in the IETF, communication between participants should be<br>
appropriate for a professional audience including people of many different<=
br>
backgrounds.<br>
<br>
While our processes let chairs deal with disruptive public behaviors on mai=
ling<br>
lists and in IETF face-to-face meetings, harassment is a serious problem th=
at<br>
warrants special attention. IETF participants should not engage in harassme=
nt<br>
while at IETF meetings, virtual meetings, social events, or on mailing list=
s.<br>
Harassment is unwelcome hostile or intimidating behavior, in particular spe=
ech<br>
and behavior that is sexually aggressive or intimidates based on attributes=
 like<br>
race, gender, religion, age, color, national origin, ancestry, disability,<=
br>
sexual orientation, or gender identity. Harassment of this sort will not be=
<br>
tolerated in the IETF. Harassment includes the use of offensive language or=
<br>
sexual imagery in public presentations and displays, degrading verbal comme=
nts,<br>
deliberate intimidation, stalking, harassing photography or recording,<br>
inappropriate physical contact, and unwelcome sexual attention.<br>
<br>
Participants asked to stop any harassing behavior are expected to comply<br=
>
immediately. If you believe you have been harassed, notice that<br>
someone else is being harassed, or have any other concerns, you are encoura=
ged<br>
to raise your concern in confidence with one of the Ombudspersons.<br>
<br>
If these standards are violated, appropriate action will be taken.<br>
</blockquote></div><br></div>

--047d7ba9823232d46e04e94040bb--

From john-ietf@jck.com  Mon Oct 21 06:31:01 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 0C2AA11E83D2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.589
X-Spam-Level: 
X-Spam-Status: No, score=-103.589 tagged_above=-999 required=5 tests=[AWL=0.010, 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 Hec8FII7LZKA for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:30:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 225EC11E8507 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:30:37 -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 1VYFZ6-0000Qa-0h; Mon, 21 Oct 2013 09:30:36 -0400
Date: Mon, 21 Oct 2013 09:30:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
Message-ID: <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com>
In-Reply-To: <20131021125834.GA24167@nic.fr>
References: <20131021125834.GA24167@nic.fr>
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: Mon, 21 Oct 2013 13:31:01 -0000

--On Monday, October 21, 2013 14:58 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

> What did they say, in the movie Apocalypse Now? "I like the
> smell of the troll in the morning"?
> 
> http://innovation-regulation2.telecom-paristech.fr/wp-content/
> uploads/Documents/thematiques/Standardization/Pouzin-Internet_
> standardisatio.pdf

Do you have any idea what Slide 8 is about?  Some of the entries
make no sense to me at all.

    john





From bortzmeyer@nic.fr  Mon Oct 21 06:31:31 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF45811E813A for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.337
X-Spam-Level: 
X-Spam-Status: No, score=-102.337 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6E+qgF4vjsI for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:31:15 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 36D1D11E851A for <ietf@ietf.org>; Mon, 21 Oct 2013 06:31:10 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 78D1A2804BB; Mon, 21 Oct 2013 15:30:39 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 7427A2803C2; Mon, 21 Oct 2013 15:30:39 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 6739FB3800C; Mon, 21 Oct 2013 15:30:09 +0200 (CEST)
Date: Mon, 21 Oct 2013 15:30:09 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dcrocker@bbiw.net
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131021133009.GA27979@nic.fr>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5265275B.8040105@dcrocker.net>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
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, 21 Oct 2013 13:31:31 -0000

On Mon, Oct 21, 2013 at 09:08:43AM -0400,
 Dave Crocker <dhc@dcrocker.net> wrote 
 a message of 27 lines which said:

> He invented the datagram...

Some people say it is Leonard Kleinrock. I welcome any precise
references on the history of the datagram, specially if they are
accessible online (whuich is rare for scientific papers of this
time). Anyway, the fact that someone did something great X years ago
(he also wrote the first shell and built Cyclades) does not mean he
cannot troll today.

> I think his slides do miss some essential points, but that it's a
> case of correct numbers producing incorrect recommendations.

Fair summary. His remark about the use of english is a good
example. Is it a problem? Yes? Can anyone see a solution? No (and he
does not suggest one).


From jnc@mercury.lcs.mit.edu  Mon Oct 21 06:35:15 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 5491F11E837F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, 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 niOjVNZj3YZt for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:35:10 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1071411E8518 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:34:43 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 4230D18C0F6; Mon, 21 Oct 2013 09:34:43 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
Message-Id: <20131021133443.4230D18C0F6@mercury.lcs.mit.edu>
Date: Mon, 21 Oct 2013 09:34: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: Mon, 21 Oct 2013 13:35:15 -0000

    > From: Dave Crocker <dhc@dcrocker.net>

    > I think his slides do miss some essential points

For me, the biggest one is regarding non-US people (whether you measure 'US'
by citizenship, or residence) working for US-'based' multi-nationals. (That
too is a complex question, as their country of incorporation may not be where
their main nexus us, although for many tech companies it is.)  He counted such
people as 'US', but I think that's a simple gloss on a more complex reality.

And of course it goes both ways - what about, e.g. US citizens working for a
non-US company? What box do they go in? If you go by the company's country,
for US companies (even if the personnel are non-US citizens, residing in their
native country), would the same rule apply to non-US companies?

Actually, probably a bigger issue than national bias is the dominance of
vendors (who can afford to send personnel), versus users.

	Noel

From bortzmeyer@nic.fr  Mon Oct 21 06:38:28 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96FDA11E837F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.308
X-Spam-Level: 
X-Spam-Status: No, score=-102.308 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhwBzZyZGYfR for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:38:21 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 236DB11E84DD for <ietf@ietf.org>; Mon, 21 Oct 2013 06:37:54 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9D9922804CE for <ietf@ietf.org>; Mon, 21 Oct 2013 15:37:22 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 99C0A2803C2 for <ietf@ietf.org>; Mon, 21 Oct 2013 15:37:22 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 6B87DB3803C for <ietf@ietf.org>; Mon, 21 Oct 2013 15:36:25 +0200 (CEST)
Date: Mon, 21 Oct 2013 15:36:25 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131021133625.GA27768@nic.fr>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
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: Mon, 21 Oct 2013 13:38:28 -0000

On Mon, Oct 21, 2013 at 01:44:23AM +0800,
 IETF Chair <chair@ietf.org> wrote 
 a message of 104 lines which said:

> The IETF should be an open and accessible body in which any
> individual feels able to participate without fear of oppression or
> harassment.

I agree with the goal, and with the mean (having a anti-harrasment
policy). I have one question before agreeing to everything:

> IETF meetings, virtual meetings, and mailing lists are intended for
> professional collaboration and networking. The IETF strives to
> create and maintain an environment in which people are treated with
> dignity, decency, and respect.  Those who participate in the IETF
> are expected to behave according to professional standards

The (ab)use of the term "professional" seems to imply that harassement
outside of the work place is normal, and worse, it could imply that we
fight harassment, not because it is wrong or illegal, but because it
is against the standards of the corporations. Why not simply say that
"Those who participate in the IETF are expected to behave as civilized
people"?


From lear@cisco.com  Mon Oct 21 06:39:24 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 3564111E8556 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.412
X-Spam-Level: 
X-Spam-Status: No, score=-110.412 tagged_above=-999 required=5 tests=[AWL=0.187, 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 OAzNdR2EHs2a for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:39:19 -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 DC09E11E853E for <ietf@ietf.org>; Mon, 21 Oct 2013 06:38:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2765; q=dns/txt; s=iport; t=1382362720; x=1383572320; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=3YlD2Ltz05UmSQTsSyrrVEC+p9CGhjYDyzZKCLo6C5U=; b=P6sqOcP4etXEMlC8ZOZvIzPcrF5sirkKclXIbgnO5ZqnZYtf6QELRBSN N5AlxOnCrxBuH3genPblPY8XCbCZ/yzk2Ud5/zUpB98EJCzuan6KLCpq7 NGytLgk3hUipfe3OPDVFXUg9uqG2CwrhYk7FiYONBBXrPXUXrtT66yz1r M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAAcuZVKQ/khN/2dsb2JhbABQCYMHhDa7BYEsFnSCJQEBAQMBI0sKEQsYAgIFFgsCAgkDAgECAUUTCAEBh3wGqVmSI4EpjHGBSRaCVIE/A5gJkgeDJjo
X-IronPort-AV: E=Sophos;i="4.93,539,1378857600"; d="scan'208";a="18425968"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 21 Oct 2013 13:38:38 +0000
Received: from ams3-vpn-dhcp7204.cisco.com (ams3-vpn-dhcp7204.cisco.com [10.61.92.35]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r9LDcWMa005939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 21 Oct 2013 13:38:34 GMT
Message-ID: <52652E5E.2040308@cisco.com>
Date: Mon, 21 Oct 2013 15:38:38 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF Anti-Harassment Policy
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
X-Enigmail-Version: 1.5.2
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, 21 Oct 2013 13:39:24 -0000

Jari,

Overall, I think it's the right direction.  Just some minor issues:

On 10/20/13 7:44 PM, IETF Chair wrote:
> --- Draft Statement ---
>
> IETF Anti-Harassment Policy
>
> IETF meetings, virtual meetings, and mailing lists are intended for professional
> collaboration and networking. The IETF strives to create and maintain an
> environment in which people are treated with dignity, decency, and respect.
> Those who participate in the IETF are expected to behave according to
> professional standards and demonstrate appropriate workplace behavior. While
> participating in the IETF, communication between participants should be
> appropriate for a professional audience including people of many different
> backgrounds.
>
> While our processes let chairs deal with disruptive public behaviors on mailing
> lists and in IETF face-to-face meetings, harassment is a serious problem that
> warrants special attention. IETF participants should not engage in harassment
> while at IETF meetings, virtual meetings, social events, or on mailing lists.
> Harassment is unwelcome hostile or intimidating behavior, in particular speech
> and behavior that is sexually aggressive or intimidates based on attributes like
> race, gender, religion, age, color, national origin, ancestry, disability,
> sexual orientation, or gender identity. Harassment of this sort will not be
> tolerated in the IETF. Harassment includes the use of offensive language or
> sexual imagery in public presentations and displays, degrading verbal comments,
> deliberate intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, and unwelcome sexual attention.

You have broken up the definition with the declaration that "Harassment
of this sort will not be tolerated in the IETF."  My suggestion is to
move that sentence below and change "Harassment includes" to "Examples
of harassment are", as I don't think you intended that to be an
exhaustive list.

>
> Participants asked to stop any harassing behavior are expected to comply
> immediately. If you believe you have been harassed, notice that
> someone else is being harassed, or have any other concerns, you are encouraged
> to raise your concern in confidence with one of the Ombudspersons.
>
> If these standards are violated, appropriate action will be taken.
>

I would more clearly what the consequences could be.  Something like "up
to and including banning the offending individual from IETF activities,
including mailing lists and meetings".   Also explain who will take the
action and what appeals avenues the individual has.  Presumably it will
be the IESG.

Also, if it hasn't happened already, please ask counsel to review.

Eliot

From bortzmeyer@nic.fr  Mon Oct 21 06:39:30 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D5411E8556 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level: 
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAfRNkFa-dm9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:39:24 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF2A11E8545 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:38:47 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 6802B2804BB; Mon, 21 Oct 2013 15:38:16 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 6392E2803C2; Mon, 21 Oct 2013 15:38:16 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay2.nic.fr (Postfix) with ESMTP id 581BDB38003; Mon, 21 Oct 2013 15:37:46 +0200 (CEST)
Date: Mon, 21 Oct 2013 15:37:46 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131021133746.GA29267@nic.fr>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
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, 21 Oct 2013 13:39:30 -0000

On Mon, Oct 21, 2013 at 09:30:30AM -0400,
 John C Klensin <john-ietf@jck.com> wrote 
 a message of 19 lines which said:

> Do you have any idea what Slide 8 is about?

No, I don't and that's one of the reasons I used the term
"troll". Pouzin often mentions "problems with Unicode" but he never
documented them in detail.

From hannes.tschofenig@gmx.net  Mon Oct 21 06:56:22 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 BE00D11E81A7 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:56: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 5wOgH8WMUdS5 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 06:56:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id EA0A211E83C7 for <ietf@ietf.org>; Mon, 21 Oct 2013 06:55:00 -0700 (PDT)
Received: from [172.16.254.200] ([80.92.115.161]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MFdPZ-1VSR3438sP-00EZxw for <ietf@ietf.org>; Mon, 21 Oct 2013 15:54:55 +0200
Message-ID: <52653241.2090601@gmx.net>
Date: Mon, 21 Oct 2013 15:55:13 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
References: <20131021133443.4230D18C0F6@mercury.lcs.mit.edu>
In-Reply-To: <20131021133443.4230D18C0F6@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Rtrrr3B7uzME/wpZjCGASRYtrcND9efdlRcTQWNI+C2+xEUukQ+ kdGB02nEa86XrMN3V6WfJikyAnEbLkzLOt7XUiSPzj7LvEH7xdi0yIvS0Hf36iN4Mocd9Dk jq6AXAcJriX7Vru3MFT1BX7Y/2Jsd1Q+EJWyl9dUYjKJJ9LGXEgBugRFGSAGLfyftA2vpAI jMpdhQP1PneYXu5XCNOsQ==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 13:56:22 -0000

On 10/21/2013 03:34 PM, Noel Chiappa wrote:
> Actually, probably a bigger issue than national bias is the dominance of
> vendors (who can afford to send personnel), versus users.

I wonder whether Internet standardization is so different from other 
sectors.

In any case, someone needs to find the motivation to spend his/her time 
to work on specifications. Obviously, not everyone is willing to do that 
even though the barrier of entry in the IETF is fairly low.

Vendors obviously have a fairly good motivation to participate.

For example, the author of the slide deck could participate in the IETF 
rather than suggesting that the specifications should be submitted to a 
national standards body for comments. One could even argue that the 
national body (which is most likely heavily influenced by vendors) could 
send their comments directly to the IETF (if they care about a certain 
technology).

How separate efforts in national standards bodies avoids the problem of 
local deviations (as mentioned in the slides) is a mystery to me.

With regard to the strong US focus in the IETF I believe we have 
discussed this topic extensively under the umbrella of increasing diversity.

Ciao
Hannes


From jari.arkko@piuha.net  Mon Oct 21 07:18: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 D784511E85A5 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.965
X-Spam-Level: 
X-Spam-Status: No, score=-101.965 tagged_above=-999 required=5 tests=[AWL=-0.658, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ldh5CbeLdFLX for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:17:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 530BA11E85A4 for <ietf@ietf.org>; Mon, 21 Oct 2013 07:17:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 489302CC6B for <ietf@ietf.org>; Mon, 21 Oct 2013 17:17:38 +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 KEXDf5I-XugS for <ietf@ietf.org>; Mon, 21 Oct 2013 17:17:37 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id EC75B2CC48 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:17:35 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Internet standardisation remains unilateral
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20131021133746.GA29267@nic.fr>
Date: Mon, 21 Oct 2013 22:17:32 +0800
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7DA2482-F607-4DE3-A8CA-519B1AA82901@piuha.net>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 14:18:03 -0000

I'd say it is a pretty biased presentation. History of the Internet has =
an impact=85 current situation is getting more balanced=85 you should =
count continents, not individual countries from EU against all of US=85 =
most international organisations work on some language=85 in most =
organisations people need time and money to participate... and I don't =
see a lot of undue influence from any direction in our current work.

This is not to say that we shouldn't work hard on making the IETF more =
diverse and more geographically distributed, more easy for everyone to =
attend, lead by a more diverse set of people - we should. But not =
because of this presentation.

Jari


From mcr@sandelman.ca  Mon Oct 21 07:19:07 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 1AA4E11E85BA for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.221,  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 Gwm8X4QGC9Z3 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:19:06 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 6D30411E859E for <ietf@ietf.org>; Mon, 21 Oct 2013 07:18:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9AC252025A; Mon, 21 Oct 2013 11:29:40 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id EA25BA9042; Mon, 21 Oct 2013 10:18:52 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D1043B8EBE; Mon, 21 Oct 2013 10:18:52 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
In-Reply-To: <CABCOCHSnxjFeWU431JXcHNDh9F03QGXYYXfQ1H5mRZ5KG7ZVUg@mail.gmail.com>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <5263EBF3.5050901@joelhalpern.com> <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <CABCOCHSnxjFeWU431JXcHNDh9F03QGXYYXfQ1H5mRZ5KG7ZVUg@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: Mon, 21 Oct 2013 10:18:52 -0400
Message-ID: <8939.1382365132@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 21 Oct 2013 14:19:07 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Andy Bierman <andy@yumaworks.com> wrote:
    > First it would be good to confirm (from NOMCOM?) why people are rejec=
ting
    > AD nominations. IMO asking 25 - 40 hours a week for 2 years is too mu=
ch,
    > but I am guessing that 1/2 of that is the right number to require.

nomcom doesn't always hear back a reason.
I'm not sure that nomcom has the time to investigate;  while the list of
people who accepted is public according to BCP10 (rfc5680), the list of
who declined is not.

It would be nice if the list of who declined could be made available (perha=
ps
under NDA) to some researcher to do a survey.

=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)

iQCVAwUBUmU3yoqHRg3pndX9AQJq3AQAiNdlbuKp3clzEWkBArW75DhwN8pLgWb2
WruthgVXqV5+ncFeMhCeuUD52URu/F3xEDjnqF8iOW0J/lcOY8AI3b5en5wN6LU5
zZjg+T1Z5wPPnKE1wkE3XJymBNZusdGoGPZ/miEyfjzv1vH9LINCK8sBvSPWYzKw
MO0WZjKqW0s=
=m6iZ
-----END PGP SIGNATURE-----
--=-=-=--

From Jelte.Jansen@sidn.nl  Mon Oct 21 07:24:39 2013
Return-Path: <Jelte.Jansen@sidn.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C302421E808D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.715
X-Spam-Level: 
X-Spam-Status: No, score=-0.715 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RaX5lCsNIKck for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:24:35 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id DB9E511E81CE for <ietf@ietf.org>; Mon, 21 Oct 2013 07:24:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=MZJbR7iGx8y/kdAvRlljhFP9np1uPqKQkwlD2Gt23YE=; b=Ak9jSVmmuylAZkgszpDQ3OxksUxirtib7nsyaHAiidEryaJa23+RhsLzLVmDA40iM+NT/qkwfZ1RtMnQW6SVZEZFHwtSPrygBf2u7I0cJDLhQjddHL1Ag30Wio2fpq13IG4teaPJH7phj/fK3Oe3a0p8QwgNOdeIey27e0TGUo4=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by ede1-kamx.sidn.nl  with ESMTP id r9LEOFIU009442-r9LEOFIW009442 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 21 Oct 2013 16:24:15 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 21 Oct 2013 16:24:14 +0200
Message-ID: <5265390E.80307@sidn.nl>
Date: Mon, 21 Oct 2013 16:24:14 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>, <ietf@ietf.org>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com>
In-Reply-To: <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 14:24:39 -0000

On 10/21/2013 03:30 PM, John C Klensin wrote:
> 
> 
> --On Monday, October 21, 2013 14:58 +0200 Stephane Bortzmeyer
> <bortzmeyer@nic.fr> wrote:
> 
>> What did they say, in the movie Apocalypse Now? "I like the
>> smell of the troll in the morning"?
>>
>> http://innovation-regulation2.telecom-paristech.fr/wp-content/
>> uploads/Documents/thematiques/Standardization/Pouzin-Internet_
>> standardisatio.pdf
> 
> Do you have any idea what Slide 8 is about?  Some of the entries
> make no sense to me at all.
> 

It's a bit unfair to discuss the slides without the accompanying talk,
but if I'd have to guess I'd say it is an offtopic critique of the
problems of whois databases (on the one hand that they contain personal
data, on the other hand that they tend to be incomplete and not as well
maintained as one might hope), and the well-discussed problems of
unicode and IDNA.

It doesn't seem like they are examples of the original problem
statement. But, again, one would need to have the full context of the
presentation to be sure.

Jelte


From allison.mankin@gmail.com  Mon Oct 21 07:28:53 2013
Return-Path: <allison.mankin@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 0E94E11E85FB for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.069
X-Spam-Level: 
X-Spam-Status: No, score=-3.069 tagged_above=-999 required=5 tests=[AWL=1.530,  BAYES_00=-2.599, GB_I_INVITATION=-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 X4V6oZ12vRwd for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:28:52 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id E48DB21E80A1 for <ietf@ietf.org>; Mon, 21 Oct 2013 07:28:02 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id x19so4467859qcw.23 for <ietf@ietf.org>; Mon, 21 Oct 2013 07:28:00 -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=LtKh0PMWM3BundQorMSKDCDpBVW2Pjp0YNoQMCwX5Cw=; b=K8H9lKRgPTd5Ra6iIDbxQuI/CzMHqJxPRA/WPHt1kmxki5ZIpxQgRtNLm0GSYhG9SD rPivZnD0Y9EE3YIA6dZ7xA+LmjYuwGhiIoT8d5p4+fJfyEI1Yg2V+GRb/gbZXaCqCUK4 YFyN7iTTFQcF59QHgDW2CE6anvfAXjh3r5yb6O1zrLZyC7u1XsrTvodi/gzqpanNylns eOergfY+6lX5sXH2Jc7JNVCWcLEOn191ucSJYVnA7iWgsE/C8OzrahAKVUVO1BrdWOWS 2zcZ2kf4Q+jQUXiPdi1HD/M5o701em7AZEITfcOpWkNmfJtHwV34k2WABq/SkoJxh6WM 3i7Q==
MIME-Version: 1.0
X-Received: by 10.229.118.10 with SMTP id t10mr22717168qcq.5.1382365680690; Mon, 21 Oct 2013 07:28:00 -0700 (PDT)
Received: by 10.96.78.40 with HTTP; Mon, 21 Oct 2013 07:28:00 -0700 (PDT)
In-Reply-To: <8939.1382365132@sandelman.ca>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <5263EBF3.5050901@joelhalpern.com> <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <CABCOCHSnxjFeWU431JXcHNDh9F03QGXYYXfQ1H5mRZ5KG7ZVUg@mail.gmail.com> <8939.1382365132@sandelman.ca>
Date: Mon, 21 Oct 2013 10:28:00 -0400
Message-ID: <CAP8yD=tKbDFzL-TYPTgG3Rt83DjVTyu2558KOQ278t=jtaDfCg@mail.gmail.com>
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Allison Mankin <allison.mankin@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a1133099058fb6c04e9411759
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: Mon, 21 Oct 2013 14:28:53 -0000

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

On Mon, Oct 21, 2013 at 10:18 AM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Andy Bierman <andy@yumaworks.com> wrote:
>     > First it would be good to confirm (from NOMCOM?) why people are
> rejecting
>     > AD nominations. IMO asking 25 - 40 hours a week for 2 years is too
> much,
>     > but I am guessing that 1/2 of that is the right number to require.
>
> nomcom doesn't always hear back a reason.
> I'm not sure that nomcom has the time to investigate;  while the list of
> people who accepted is public according to BCP10 (rfc5680), the list of
> who declined is not.
>

We've been told a reason for decline about 10 times so far.  Half of those
cited the time commitment and uncertainty of support by their employer, the
other half cited only their support for the incumbent.  Sometimes people
say that they won't try to get the support by their employer because they
support the incumbent so they think their own candidacy isn't needed.


> It would be nice if the list of who declined could be made available
> (perhaps
> under NDA) to some researcher to do a survey.
>
> When we get a little time, we can think about auto-generating invitations
to the decliners to fill in an anonymizing online survey.

--001a1133099058fb6c04e9411759
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 Mon, Oct 21, 2013 at 10:18 AM, Michael Richardson <span dir=3D"l=
tr">&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>
Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.com">andy@yumaworks.com</=
a>&gt; wrote:<br>
=A0 =A0 &gt; First it would be good to confirm (from NOMCOM?) why people ar=
e rejecting<br>
=A0 =A0 &gt; AD nominations. IMO asking 25 - 40 hours a week for 2 years is=
 too much,<br>
=A0 =A0 &gt; but I am guessing that 1/2 of that is the right number to requ=
ire.<br>
<br>
</div>nomcom doesn&#39;t always hear back a reason.<br>
I&#39;m not sure that nomcom has the time to investigate; =A0while the list=
 of<br>
people who accepted is public according to BCP10 (rfc5680), the list of<br>
who declined is not.<br></blockquote><div><br></div><div>We&#39;ve been tol=
d a reason for decline about 10 times so far.=A0 Half of those cited the ti=
me commitment and uncertainty of support by their employer, the other half =
cited only their support for the incumbent.=A0 Sometimes people say that th=
ey won&#39;t try to get the support by their employer because they support =
the incumbent so they think their own candidacy isn&#39;t needed.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<br>
It would be nice if the list of who declined could be made available (perha=
ps<br>
under NDA) to some researcher to do a survey.<br>
<span class=3D"HOEnZb"></span><br></blockquote><div>When we get a little ti=
me, we can think about auto-generating invitations to the decliners to fill=
 in an anonymizing online survey. <br></div></div></div></div>

--001a1133099058fb6c04e9411759--

From jmamodio@gmail.com  Mon Oct 21 07:34:54 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 8581311E8523 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level: 
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[AWL=0.555,  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 XkU3XG2HUq5W for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 07:34:46 -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 EF89D11E85F3 for <ietf@ietf.org>; Mon, 21 Oct 2013 07:34:19 -0700 (PDT)
Received: by mail-vb0-f50.google.com with SMTP id x14so4014835vbb.23 for <ietf@ietf.org>; Mon, 21 Oct 2013 07:34: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=yKmlh8AevGKhuXa/3nCoC1B50fZ3nPsrPM865LA693M=; b=AoORbpvxZmL1DjJR1hSszNoa8E8T+9mCv/qpnnh+5II3inss3QasLMhvlLImcTSvrK Siw/ufwnbrom4tDzmbWq4+/WNoSbvuKCVfOQYZGayIXoy0YaU3pIpsc03JuW54TtjjLs jpa0CipRE5UaGsH4eQSaX2r8P+nDl28cYy4crDfiqzRZEkzvwettbVDppYVtUmU/fljV BUM8MiNwCo7rIFBXwyMP6Dm+h0ELmQco7SVrxkgdQljfgCDDfMy/CY9vnno8iq01uS+b lYRb+vZ20g+nNnrbvXUtGfN5k9f4SliFxb6tJ0AArvrIR9Ud/k64S2FN79FvYym5l3zg 2fdw==
MIME-Version: 1.0
X-Received: by 10.52.243.138 with SMTP id wy10mr9655779vdc.2.1382366056363; Mon, 21 Oct 2013 07:34:16 -0700 (PDT)
Received: by 10.58.209.1 with HTTP; Mon, 21 Oct 2013 07:34:16 -0700 (PDT)
In-Reply-To: <20131021125834.GA24167@nic.fr>
References: <20131021125834.GA24167@nic.fr>
Date: Mon, 21 Oct 2013 09:34:16 -0500
Message-ID: <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Jorge Amodio <jmamodio@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=001a11c1c4a6bd3eb904e9412d26
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, 21 Oct 2013 14:34:54 -0000

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

He is right that the USA and perhaps other developed countries dominate the
Internet standardization process but there is a good reason why and that
when I talk with people from developing countries like mine (Argentina)
they don't are able yet to understand that blaming the "north" is not the
solution and what they need to do is to gets hands on into the issue and
develop/implement reasonable policies to have more participation in the
process.

Obviously there is a lot of participation from people from the USA or
working for US companies, full time or almost full time participation in
the IETF process requires for the participant to have a sponsor, after all
she/he still needs to live in a decent place, feed her/his family and pay
the bills, and have some security for retirement in the long term, plus pay
for the trips, etc, etc.

US companies (and sometimes the government) know very well that it has a
lot of strategic value for the company, and the country, to sponsor such
type of individuals. I doubt that Vint Cerf, Halald Alvestrand (which btw
is from Norway not the USA), and many others, are part of the daily grind
working at Google and punching time cards, but Google recognizes and value
having such type of individuals embedded in the development of the
Internet, and they have big pockets to fund them.

The issue is that the knuckleheads in charge in other parts of the world
don't get yet to understand that if they want to be part of the process
they have to invest in it, and particularly sponsor skilled and capable
individuals so they can dedicate most of their time and brain to it and not
worry about how they will pay the bills at the end of the month or if they
will have a job next week, and for sure they will have to compete for
talent with US based companies.

So for the knuckleheads stop whining and do something ...

My .02
-J




On Mon, Oct 21, 2013 at 7:58 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>wrote:

> What did they say, in the movie Apocalypse Now? "I like the smell of
> the troll in the morning"?
>
>
> http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf
>

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

<div dir=3D"ltr"><br><div>He is right that the USA and perhaps other develo=
ped countries dominate the Internet standardization process but there is a =
good reason why and that when I talk with people from developing countries =
like mine (Argentina) they don&#39;t are able yet to understand that blamin=
g the &quot;north&quot; is not the solution and what they need to do is to =
gets hands on into the issue and develop/implement reasonable policies to h=
ave more participation in the process.</div>
<div><br></div><div>Obviously there is a lot of participation from people f=
rom the USA or working for US companies, full time or almost full time part=
icipation in the IETF process requires for the participant to have a sponso=
r, after all she/he still needs to live in a decent place, feed her/his fam=
ily and pay the bills, and have some security for retirement in the long te=
rm, plus pay for the trips, etc, etc.</div>
<div><br></div><div>US companies (and sometimes the government) know very w=
ell that it has a lot of strategic value for the company, and the country, =
to sponsor such type of individuals. I doubt that Vint Cerf, Halald Alvestr=
and (which btw is from Norway not the USA), and many others, are part of th=
e daily grind working at Google and punching time cards, but Google recogni=
zes and value having such type of individuals embedded in the development o=
f the Internet, and they have big pockets to fund them.</div>
<div><br></div><div>The issue is that the knuckleheads in charge in other p=
arts of the world don&#39;t get yet to understand that if they want to be p=
art of the process they have to invest in it, and particularly sponsor skil=
led and capable individuals so they can dedicate most of their time and bra=
in to it and not worry about how they will pay the bills at the end of the =
month or if they will have a job next week, and for sure they will have to =
compete for talent with US based companies.</div>
<div><br></div><div>So for the knuckleheads stop whining and do something .=
..</div><div><br></div><div>My .02</div><div>-J</div><div><br></div><div><b=
r></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"=
>
On Mon, Oct 21, 2013 at 7:58 AM, Stephane Bortzmeyer <span dir=3D"ltr">&lt;=
<a href=3D"mailto:bortzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</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">
What did they say, in the movie Apocalypse Now? &quot;I like the smell of<b=
r>
the troll in the morning&quot;?<br>
<br>
<a href=3D"http://innovation-regulation2.telecom-paristech.fr/wp-content/up=
loads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.=
pdf" target=3D"_blank">http://innovation-regulation2.telecom-paristech.fr/w=
p-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_sta=
ndardisatio.pdf</a><br>

</blockquote></div><br></div>

--001a11c1c4a6bd3eb904e9412d26--

From jabley@hopcount.ca  Mon Oct 21 08:06: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 D65A511E8404 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:06:09 -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 B+N6dDj0B1oU for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:06:09 -0700 (PDT)
Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D87F311E85ED for <ietf@ietf.org>; Mon, 21 Oct 2013 08:05:53 -0700 (PDT)
Received: by mail-qe0-f46.google.com with SMTP id s14so3813684qeb.19 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:05:45 -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; bh=6Jda/b1521xB+dl793EgaVc6xIONeMOCdHLRrrknDPY=; b=F5ci4VmxSgbL5pU1URcI5N3Sf87oZJb3fZ+FT26mT4J27dmM/SuPjmy9AFOQFdja46 aQMcp1j6HrLnNaIDAFnTeEGK+1463SgIG6CbJnuVZM33Jj3twUz17LbfDBS2wSeNeUqe taKc3MWGy7d9A+VDecU5Vk+rJikVKVzE4XQuU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=6Jda/b1521xB+dl793EgaVc6xIONeMOCdHLRrrknDPY=; b=BdyRzRAB48iKlS0ubN4/Oyu4q2Uw1YacWFb0zg50DCslwXZyINDpsoU0QQZWz1GCXT c0bhYxHonAYqTACHjYH4bnWc32fj+XRS42MxLlngkaf8yubcpMIb4Uj7WTIgk984msqK AccO5vwfOw3t4uQBoh+6fh2a2+00RHU7d/dsnxl/fw1u9B/4xb0JLvsvdgjjNudzNQNw bW76GwesuMNg3NctpsJAmU8/iNlVIez/8bx2d9sqf9/jn798XN0BhuQNPlgOJvFNGuMd 6/ei7FljhHTpixdSo9vWRjX//AXZe9xf8nEgOnXG6lEVeHQECfEXCJNUTpWgRnpBmeLe 0d4g==
X-Gm-Message-State: ALoCoQkTEi1K/s6NnJKU4Y9Bs4S0M+B0WJ8m6YOPfDvDWh1OLVGqqhaL80aWJs8Z0qhS1QgADoEW
X-Received: by 10.49.18.195 with SMTP id y3mr22796240qed.39.1382367944574; Mon, 21 Oct 2013 08:05:44 -0700 (PDT)
Received: from [199.212.90.58] ([135.23.68.78]) by mx.google.com with ESMTPSA id u3sm32665426qej.8.2013.10.21.08.05.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 08:05:43 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: CHANGE THE JOB (was Re: NOMCOM - Time-Critical - Final Call for Nominations)
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <CAP8yD=tKbDFzL-TYPTgG3Rt83DjVTyu2558KOQ278t=jtaDfCg@mail.gmail.com>
Date: Mon, 21 Oct 2013 11:05:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C92002F-0EFA-4300-B040-1290382DB0F9@hopcount.ca>
References: <20131017140905.21841.75117.idtracker@ietfa.amsl.com> <27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <EMEW3|bd3eab4f0a509d46ca1e7573083648c4p9GFsE03tjc|ecs.soton.ac.uk|27EC3F2F-2148-4502-9527-E0F7C500D8BB@ecs.soton.ac.uk> <52602DF7.3030207@dcrocker.net> <DC59B10837C9CD235DD98438@JcK-HP8200.jck.com> <5260334D.10806@dcrocker.net> <52603628.1080007@stpeter.im> <C5E08FE080ACFD4DAE31E4BDBF944EB123CC1C5B@xmb-aln-x02.cisco.com> <CAPv4CP_KNjwkDsxqyQ8FeycA9PXiOoK2A_mcUwchSvfAN3rgjA@mail.gmail.com> <9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <EMEW3|3c8571e8ee3e5f2690e1620d67ee4f39p9JFXH03tjc|ecs.soton.ac.uk|9EDD245A-099B-493E-A185-042A3C645E16@ecs.soton.ac.uk> <221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <5263EBF3.5050901@joelhalpern.com> <EMEW3|ab2bcd5d64166756701bee3d6b136871p9JFox03tjc|ecs.soton.ac.uk|221F89F1-7626-4DFE-A0F9-79147FBC3DD2@ecs.soton.ac.uk> <CABCOCHSnxjFeWU431JXcHNDh9F03QGXYYXfQ1H5mRZ5KG7ZVUg@mail.gmail.com> <8939.1382365132@san delman.ca> <CAP8yD=tKbDFzL-TYPTgG3Rt83DjVTyu2558KOQ278t=jtaDfCg@mail.gmail.com>
To: Allison Mankin <allison.mankin@gmail.com>
X-Mailer: Apple Mail (2.1510)
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: Mon, 21 Oct 2013 15:06:10 -0000

On 2013-10-21, at 10:28, Allison Mankin <allison.mankin@gmail.com> =
wrote:

> We've been told a reason for decline about 10 times so far.  Half of =
those cited the time commitment and uncertainty of support by their =
employer, the other half cited only their support for the incumbent.  =
Sometimes people say that they won't try to get the support by their =
employer because they support the incumbent so they think their own =
candidacy isn't needed.

My sense of the feedback I have seen so far (and it's certainly true for =
me) is quite simple:

 - the perception is that doing a good job on the IESG is pretty much a =
full-time commitment
 - I don't have enough free time to do that outside my day job. I have =
children, and the transhumanists have not produced an effective way to =
live without sleep yet.
 - My employer, although demonstrably willing and able to dedicate =
resources to the IETF for the good of the Internet, wants me working on =
other things than just "IESG" during work hours
 - I didn't volunteer

I'm not suggesting that I'd be of any use on the IESG anyway, but the =
current conversation seems to be more about the number of volunteers =
than the quality of the volunteers.

If the perception in the first ASCIIbullet above is inaccurate, then it =
makes sense to correct it. Joel's estimate of how much the Ops Area AD =
role consumes for him was different, for example.

I think the concern that the number of people available within the =
constraints above to dedicate time to the IESG is low and represents an =
institutional bias is reasonable. There's no way that a =
resource-stretched, panic-mode, regional ISP is going to be able to pull =
their top talent away from the burning routers and send them full-time =
to review drafts and push paper for the IETF, for example. This is not =
going to make the oft-cited concern about operator involvement in the =
IETF any better.


Joe


From d3e3e3@gmail.com  Mon Oct 21 08:08:09 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 522BA11E8613 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:09 -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 mvNBX3V71U2L for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:08:08 -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 14B7811E863A for <ietf@ietf.org>; Mon, 21 Oct 2013 08:07:34 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id gq1so2059098obb.17 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:07: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 :cc:content-type; bh=lbuo2s+9C2oihLRzKuLXT5iMKPNLl32QsdqbIlX2sFg=; b=wgt9cvFf5F05Dn578DE3dfQBt+sRqJwzkwWKkaLAg9DoBByRPsroj3z4YFHNnNjlNj wawzVxpIl9XT19Moj9L8uYsKE3UU0BCcy/4ImVrNE0eRxuSbrt7xDxYrg9/6J0Ba63Ib +yiIvPT6JqxXPrgFRiCL1QpuVY/wjkqdTKDwTzfF7w8fnHOee87SowRL04+A6U/+n0Bz zzl8sRJEiNHdwMjJ6eJyf50+YZIWet4I6J1QaF9MjUFyfRJptQoXrB1vDKzvfc1beXfX MQcJzjnFAYS/mwxzdDx1utQTWElyKeycnHrutzqObYK07q8Es2a18qW9AzA1KTb/KHvR 8XrQ==
X-Received: by 10.182.18.102 with SMTP id v6mr1291225obd.71.1382367714150; Mon, 21 Oct 2013 08:01:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Mon, 21 Oct 2013 08:01:34 -0700 (PDT)
In-Reply-To: <CA+9kkMBr0g1dQzjnZp0RZG5iwpuB8CTeJr2yhSPyuRYDMMqRRQ@mail.gmail.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CA+9kkMBr0g1dQzjnZp0RZG5iwpuB8CTeJr2yhSPyuRYDMMqRRQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 21 Oct 2013 11:01:34 -0400
Message-ID: <CAF4+nEH-8JanZDeaeP569jx0324FqP7NHGO-kjYsVB+YU8Am+g@mail.gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
To: Ted Hardie <ted.ietf@gmail.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: Mon, 21 Oct 2013 15:08:09 -0000

Hi,

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


On Mon, Oct 21, 2013 at 9:27 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> This is a good idea.  If the professionals thinking this is the right
> wording, that is also fine by me.
>
> I do note the phrase "harassing photography or recording";  I believe our
> current rules say "written, audio and video records of meetings may be made
> and may be available to the public."  It may be appropriate to adjust it to
> something like "harassing photography or recording of individuals outside
> their roles as participants" or to otherwise clarify how photography becomes
> harassment.

Years ago, when I was Chair of the TRADE WG, there was a participant
who had severe disagreements with me concerning procedure and some
technical issues. No one else supported them and they didn't appeal
but they started videotaping WG meetings that I chaired. This
certainly made me feel somewhat uncomfortable, although it just added
a video recording to the audio recording already being made by the
IETF, and I could argue that they were trying to harass or, perhaps
more accurately, intimidate me. Never-the-less, they had the right to
do that and I don't think they should have been stopped from doing so.

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

> regards,
>
> Ted Hardie
>
>
> On Sun, Oct 20, 2013 at 10:44 AM, IETF Chair <chair@ietf.org> wrote:
>>
>> The IETF should be an open and accessible body in which any individual
>> feels
>> able to participate without fear of oppression or harassment.  The IESG
>> has
>> become aware of some incidents of concern, is aware of various incidents
>> in our
>> industry in general, and has also observed that many similar organisations
>> and
>> conferences have a policy on this matter.
>>
>> In order to ensure the right atmosphere and to provide a suitable
>> environment,
>> the IESG has decided that it is desirable to write a simple and
>> straightforward
>> policy on harassment. This is not only to remind participants not to
>> harass
>> others (something that we hope is obvious to us all), but also to let
>> anyone who
>> it the target of harassment know that we take these matters seriously and
>> that
>> there is something they can do to address these sorts of incidents should
>> they
>> occur.
>>
>> A small design team has looked at existing policies used by other groups
>> similar
>> to the IETF and consulted with some of the ISOC professionals with
>> expertise in
>> human resources and issues of workplace harassment. The design team has
>> put
>> together what the IESG feels is a good anti-harassment policy for the
>> IETF: It
>> is short and to the point, it is modeled on and makes heavy re-use of the
>> language of existing policies, and it sets forth reasonable procedures for
>> the
>> IETF.
>>
>> The IESG intends to put in place Ombudspersons as confidential initial
>> contact
>> points for situations where there is a concern of harassment. The
>> selection of
>> Ombudspersons will happen later, and the person(s) will have appropriate
>> training and expertise.
>>
>> The IESG plans to adopt this as an IESG Statement. We solicit your
>> feedback. We
>> understand that this is a difficult and sensitive topic to discuss, but we
>> do
>> want your comments. If you feel more comfortable sending comments directly
>> to
>> the IESG <iesg@ietf.org> rather than discussing them on the IETF list,
>> please
>> feel free to do so.
>>
>> Jari Arkko for the IESG
>>
>> --- Draft Statement ---
>>
>> IETF Anti-Harassment Policy
>>
>> IETF meetings, virtual meetings, and mailing lists are intended for
>> professional
>> collaboration and networking. The IETF strives to create and maintain an
>> environment in which people are treated with dignity, decency, and
>> respect.
>> Those who participate in the IETF are expected to behave according to
>> professional standards and demonstrate appropriate workplace behavior.
>> While
>> participating in the IETF, communication between participants should be
>> appropriate for a professional audience including people of many different
>> backgrounds.
>>
>> While our processes let chairs deal with disruptive public behaviors on
>> mailing
>> lists and in IETF face-to-face meetings, harassment is a serious problem
>> that
>> warrants special attention. IETF participants should not engage in
>> harassment
>> while at IETF meetings, virtual meetings, social events, or on mailing
>> lists.
>> Harassment is unwelcome hostile or intimidating behavior, in particular
>> speech
>> and behavior that is sexually aggressive or intimidates based on
>> attributes like
>> race, gender, religion, age, color, national origin, ancestry, disability,
>> sexual orientation, or gender identity. Harassment of this sort will not
>> be
>> tolerated in the IETF. Harassment includes the use of offensive language
>> or
>> sexual imagery in public presentations and displays, degrading verbal
>> comments,
>> deliberate intimidation, stalking, harassing photography or recording,
>> inappropriate physical contact, and unwelcome sexual attention.
>>
>> Participants asked to stop any harassing behavior are expected to comply
>> immediately. If you believe you have been harassed, notice that
>> someone else is being harassed, or have any other concerns, you are
>> encouraged
>> to raise your concern in confidence with one of the Ombudspersons.
>>
>> If these standards are violated, appropriate action will be taken.
>
>

From hallam@gmail.com  Mon Oct 21 08:14:14 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 5376F11E81AD for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 Zgj6P1sR3Q5D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:14:13 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3972611E81B4 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:14:12 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id hp15so1110593lab.32 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:14:11 -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=2CT/peWUmitYEzEnOoDh0ovnKBQsrrm4c0i7iVTFlUg=; b=RTXQf3try+eoR5X8F91ZyZKAE9QyXmgpmx0zxOR1D/Luwq31Wx9agc2aRrL/GAULyx extIS9n1d+LPHeHH4a/ubXLbXC6bMAyaO7CHdU8W7eAxmmvLMXoIoMHVEofcsOW1v4vE dZIELpxC2eOFvHKWTa98v1eXerhwAR9YIi/MVKMVaLDlc0HeadJhmLxEaNdIBIioZIJQ tmf5VjCIKNiffNJRoWdFQ5l9jBCTbGJ4X/r2Cl6Z2vMmHaXWg1K1JwAlXJipwe82Ln8K t2gHEm1BrFgDNPaIKbbymQyeJymki5r4jWOXz64Y8rcCvByasDbFChslElJ3z1zAOE94 QDDg==
MIME-Version: 1.0
X-Received: by 10.112.128.166 with SMTP id np6mr13668681lbb.7.1382368451032; Mon, 21 Oct 2013 08:14:11 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 08:14:10 -0700 (PDT)
In-Reply-To: <20131021125834.GA24167@nic.fr>
References: <20131021125834.GA24167@nic.fr>
Date: Mon, 21 Oct 2013 11:14:10 -0400
Message-ID: <CAMm+LwhngSCp3BoBpVu3u09pmFAcYx0KqUrt7g5eP=5TmG2yYQ@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: multipart/alternative; boundary=047d7b343ef278fa6304e941bcca
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, 21 Oct 2013 15:14:14 -0000

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

On Mon, Oct 21, 2013 at 8:58 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr>wrote:

> What did they say, in the movie Apocalypse Now? "I like the smell of
> the troll in the morning"?
>
>
> http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf
>

I think it is counter productive to label opinions you find unpleasant
'troll'. That implies that the only reason the views are raised is to
provoke a pointless argument.

In this case the slides were directed at a different audience entirely so
accusing the author of trolling the IETF is discourteous and insulting and
the accusation should be withdraw.


The view of the IETF described is very common outside the US and the IETF.
You may disagree with that view but it is foolish to label a commonly held
view 'troll'.


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

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

<div dir=3D"ltr">On Mon, Oct 21, 2013 at 8:58 AM, Stephane Bortzmeyer <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:bortzmeyer@nic.fr" target=3D"_blank">bor=
tzmeyer@nic.fr</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">What did they say, in the movie Apocalypse N=
ow? &quot;I like the smell of<br>
the troll in the morning&quot;?<br>
<br>
<a href=3D"http://innovation-regulation2.telecom-paristech.fr/wp-content/up=
loads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.=
pdf" target=3D"_blank">http://innovation-regulation2.telecom-paristech.fr/w=
p-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_sta=
ndardisatio.pdf</a><br>

</blockquote></div><br>I think it is counter productive to label opinions y=
ou find unpleasant &#39;troll&#39;. That implies that the only reason the v=
iews are raised is to provoke a pointless argument.</div><div class=3D"gmai=
l_extra">
<br></div><div class=3D"gmail_extra">In this case the slides were directed =
at a different audience entirely so accusing the author of trolling the IET=
F is discourteous and insulting and the accusation should be withdraw.</div=
>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">The view of the IETF described is very common out=
side the US and the IETF. You may disagree with that view but it is foolish=
 to label a commonly held view &#39;troll&#39;.</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>

--047d7b343ef278fa6304e941bcca--

From jabley@hopcount.ca  Mon Oct 21 08:21:02 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 37C1111E83D2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 mgK6sePDMQqE for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:20:58 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7E911E81D3 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:20:52 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id x19so4575504qcw.37 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:20:51 -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; bh=JlTyanpdai4fKyMNZWLZ4a7Rv/zHf52okEjTW2lARPY=; b=gqBAUtkXKnm1OvOPtb/Alj2YqOR/uyZpgilGWZTUR0J/GgDxpjsILOQTAYMZzBS8wl wqSTA1bQxXlM3ywWnn1RS/DMnUY6+Xd6GXDH/zbcEXEHrsmIlRi5WYfQz8y9y54NW423 rioExeAHOIQtc6VMUG5/HZPE13tvWiIxXBSKo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=JlTyanpdai4fKyMNZWLZ4a7Rv/zHf52okEjTW2lARPY=; b=TD+IAWOk06O++o4qk9n6z0jxk7bYYzOtrIfnczDHuhfUdEAorkU3PX/2A/0MxHdSv/ zyMiWBjwaKheyV4CHh3Y2eKIipS23HUEFwh8rgFt6/63nwVrkqH69ILGz3WSd5iPXIL7 Eh8HPCtmsFSCfWDD5BtvtlX5KjQr41IoqNZvpU9gjR+OCCmpoPjCkpwb/NsSzAIr3zmg O3nrX1NBarwj/MZ60DCWsXHzTQGn7lZ7s4vWRUkZJlfWlxZ2ZsdNNg/z+7tOSE6tcxMB RXz7kcCeqghMMokjYnqMG6DUsMAafNlBxk23CncYSFzFl3uYn3bmTeheu3xIIJwsQ3y7 Skyw==
X-Gm-Message-State: ALoCoQlnHj6NAyUqu8cQQ8kkn45HgmlU9w0PzWxnZA4JTSWhV6nZ/VXD/h4YbmVpC4cLzZtCfOLu
X-Received: by 10.49.95.233 with SMTP id dn9mr23083701qeb.54.1382368850341; Mon, 21 Oct 2013 08:20:50 -0700 (PDT)
Received: from [199.212.90.58] ([135.23.68.78]) by mx.google.com with ESMTPSA id fx6sm32782893qeb.1.2013.10.21.08.20.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 08:20:49 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Internet standardisation remains unilateral
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <CAMm+LwhngSCp3BoBpVu3u09pmFAcYx0KqUrt7g5eP=5TmG2yYQ@mail.gmail.com>
Date: Mon, 21 Oct 2013 11:20:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <51234A08-1462-46DA-A179-A0823DFDD90C@hopcount.ca>
References: <20131021125834.GA24167@nic.fr> <CAMm+LwhngSCp3BoBpVu3u09pmFAcYx0KqUrt7g5eP=5TmG2yYQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1510)
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, 21 Oct 2013 15:21:03 -0000

On 2013-10-21, at 11:14, Phillip Hallam-Baker <hallam@gmail.com> wrote:

> I think it is counter productive to label opinions you find unpleasant =
'troll'. That implies that the only reason the views are raised is to =
provoke a pointless argument.

I don't think Stephane was labelling an opinion a troll. I think he was =
labelling the source of the opinions a troll.


Joe


From warren@kumari.net  Mon Oct 21 08:40:19 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 610DC11E8608; Mon, 21 Oct 2013 08:40: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=[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 UrGGES4GfsnL; Mon, 21 Oct 2013 08:40:11 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2633C11E83FC; Mon, 21 Oct 2013 08:38:52 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.93]) by vimes.kumari.net (Postfix) with ESMTPSA id 3087A1B401D1; Mon, 21 Oct 2013 11:38:52 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [IETF] Re: Proposed IETF Anti-Harassment Policy
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com>
Date: Mon, 21 Oct 2013 11:38:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF discussion list <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 15:40:20 -0000

On Oct 21, 2013, at 9:02 AM, Scott Brim <scott.brim@gmail.com> wrote:

> While I'm completely in favor of the goals, I don't like this =
sentence: "Participants asked to stop any harassing behavior are =
expected to comply
> immediately." The problem is that this sentence assumes a clear =
agreed-on definition of harassment, while it should be based on =
subjective experience. If I say "Randy, that's harassment and I want you =
to stop," he may respond "No it isn't."  I propose something like: =
"Participants asked to stop a behavior that is being experienced as =
harassment are expected to comply immediately."

Issue:  "I find all emails containing the word "comply" to be =
harassing[0], and I'd like you to stop"

Now what do you do?=20

W

[0]:=20
Mr Smoke-Too-Much: Yes, that's right. It's all due to a trauma I =
suffered when I was a sbool boy. I was attacked by a bat.
Bounder: A cat?
Mr Smoke-Too-Much: No, a bat.

>=20
> Scott
>=20

--
"I think perhaps the most important problem is that we are trying to =
understand the fundamental workings of the universe via a language =
devised for telling one another when the best fruit is." --Terry =
Prachett=20



From melinda.shore@gmail.com  Mon Oct 21 08:46:05 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 2D03311E856B for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:46:05 -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 Z1lNRnnEGn0A for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:46:04 -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 EACFF11E8591 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:42:33 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id md4so7175117pbc.2 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:42:33 -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=oCbVPgI/FDGyaf+UnkEjeaPD+4iJeuKMquWOLwzo67U=; b=TZGwnCJKlSqit0cjlU2ZUqQCragwKWxePU1FjvQ5kdh3IMUB+e5mv6GAzoAUazLfbA O0W6lfCM073puaeJXrnFyunH1DJQ8zMeN/1jygXIm400fp43jCLVguY51Hh8jv98xzfm WNqzSRNjQkABrXAuLcxZWvqU2Ui7od/5YQuNVRR+UrfrHm5W845/h9nKHk3XNXcf/vNE 79Kp5IO+cQMey2NjrEhzk03Mk7QHqVqdvf+Fw6G/SAdGBA2rmIS8omDNDb5oB7roO7q7 O3kgJZfxmP6FKkd0rRpR53vydNULe/sy0mWrgnoTNcu5cEdinlLJjTfqbm084dzx3MXt Zktg==
X-Received: by 10.69.0.228 with SMTP id bb4mr18212325pbd.66.1382370153304; Mon, 21 Oct 2013 08:42:33 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id qz9sm21727564pbc.3.2013.10.21.08.42.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 08:42:32 -0700 (PDT)
Message-ID: <52654B65.3000006@gmail.com>
Date: Mon, 21 Oct 2013 07:42:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Proposed IETF Anti-Harassment Policy
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net>
In-Reply-To: <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.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: Mon, 21 Oct 2013 15:46:05 -0000

On 10/21/13 7:38 AM, Warren Kumari wrote:
> Issue:  "I find all emails containing the word "comply" to be
> harassing[0], and I'd like you to stop"
> 
> Now what do you do?

You kick the problem over to your (trained) ombudsman.

Melinda


From jeanjour@comcast.net  Mon Oct 21 08:46:59 2013
Return-Path: <jeanjour@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 087A111E8614 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:46:58 -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 5ddQV76nd89e for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:46:52 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1F511E854F for <ietf@ietf.org>; Mon, 21 Oct 2013 08:44:15 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta15.westchester.pa.mail.comcast.net with comcast id fnzC1m00616LCl05Frk7qT; Mon, 21 Oct 2013 15:44:07 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta06.westchester.pa.mail.comcast.net with comcast id frk71m00314WE023Srk7fr; Mon, 21 Oct 2013 15:44:07 +0000
Mime-Version: 1.0
Message-Id: <a0624085ece8af60d4cd2@[10.0.1.3]>
In-Reply-To: <20131021133009.GA27979@nic.fr>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr>
Date: Mon, 21 Oct 2013 11:38:18 -0400
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dcrocker@bbiw.net
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382370248; bh=duwmDxBlsG6KoqElI64DwGEvNdIxfXzuszKBtbfh5mU=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=ahyzVA4fb4Ao983cC/Ib4zUvn/OknZfMyaZcG94einfSWzLeLZDrJQ7qw4zbgqROT bOXGUro3VXw2b6X4rcIRDlL9iolWZfMygSNXUFaFwgQ0oemqWmQ+8UYmNuTAcBlm5V KBlGxRgwAOOmwSYrtVLqWTHNcHqipV9lSjxN6W/EdKy68DMeDSCHiidAmbCKm3sgH3 aUjUAkChoV4/J2G336vhyahgBKF/L1SRX25jO4xqIdvq5jjjWJkcSRqV7Dhg4V1NPX vyl8Btn6VSElf///H8fWqa6jkTRN+PvPHa7Ij3A9pSI12uoiuQkQ7Go7X7RLct9ik/ 3H9eWL0K602kg==
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, 21 Oct 2013 15:47:04 -0000

At 3:30 PM +0200 10/21/13, Stephane Bortzmeyer wrote:
>On Mon, Oct 21, 2013 at 09:08:43AM -0400,
>  Dave Crocker <dhc@dcrocker.net> wrote
>  a message of 27 lines which said:
>
>>  He invented the datagram...
>
>Some people say it is Leonard Kleinrock. I welcome any precise
>references on the history of the datagram, specially if they are

No, Kleinrock claims to have invented packet switching, not the 
datagram.  There was an article before his death by Donald Davies, 
who looked quite closely at the claims that Kleinrock invented packet 
switching as well as Baran and Davies.  I have read Kleinrock's 
thesis which is the source of the claim and I don't see it.  Davies' 
very fair article did not see it either.

>accessible online (whuich is rare for scientific papers of this
>time). Anyway, the fact that someone did something great X years ago
>(he also wrote the first shell and built Cyclades) does not mean he
>cannot troll today.

I have contended that whether or not you see packet switching as a 
breakthrough depends largely on how old you are?  ;-)  People of the 
period from a more telecom background see the idea of breaking data 
into small pieces (remember message switching systems already 
existed) as a radical idea.  If you were a little younger and your 
background is in computing, then packet switching in obvious.  From a 
computer person's point of view, if the problem is posed of 
communicating between computers, the solutions is clear:  The data is 
in a buffer, pick it up and send it.  What else would you do?  ;-)

Pouzin's insight was that the packets should be routed independently 
and not all follow the same path.  Furthermore, Louis' reasoned that 
no matter how good the network was, the hosts would check to make 
sure that everything got there.  Hence, he reasoned the network did 
not have to do a perfect job, but only make a "best effort" and that 
an end-to-end transport protocol would ensure reliability.   You 
won't find any of this in Kleinrock's thesis.  All of this was 
implemented in CYCLADES in 1972 (and is well documented in many 
papers which are on-line and in subsequent histories).  The original 
ARPANET did not work this way, although Type 3 messages (datagrams) 
were added later.  (I have always found it interesting that every 
project taken on by Baran and Larry Roberts after 1970 were all 
connection-oriented, none were based on the datagram concept.)  The 
real revolution here is that Pouzin took communications from a 
deterministic model of connection-oriented to a stochastic model of 
datagrams.

For me, this shift in thinking comes in two stages that I liken to 
what we saw in geology:   Some people came up with a new idea, packet 
switching (continental drift) and after looking at it, it was refined 
to the datagram concept (plate tectonics).  While from a distance we 
often see these changes as sudden and complete in one big insight 
they seldom are.

Pouzin is one of the best thinkers I know.  You may not like what he 
says, but even now he is far from being a troll.  His hit rate 
exceeds most of us!  ;-)

>
>>  I think his slides do miss some essential points, but that it's a
>>  case of correct numbers producing incorrect recommendations.
>
>Fair summary. His remark about the use of english is a good
>example. Is it a problem? Yes? Can anyone see a solution? No (and he
>does not suggest one).

More on this after reading some more.

Take care,
John Day

From warren@kumari.net  Mon Oct 21 08:51:42 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 5705211E85C5 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:51:42 -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 1vBJ09iAIlg1 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:51:36 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67E5411E85D6 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:50:36 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.93]) by vimes.kumari.net (Postfix) with ESMTPSA id DFC4A1B4008B; Mon, 21 Oct 2013 11:50:35 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [IETF] Re: [IETF] Re: Proposed IETF Anti-Harassment Policy
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <52654B65.3000006@gmail.com>
Date: Mon, 21 Oct 2013 11:50:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net> <52654B65.3000006@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1510)
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, 21 Oct 2013 15:51:42 -0000

On Oct 21, 2013, at 11:42 AM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> On 10/21/13 7:38 AM, Warren Kumari wrote:
>> Issue:  "I find all emails containing the word "comply" to be
>> harassing[0], and I'd like you to stop"
>>=20
>> Now what do you do?
>=20
> You kick the problem over to your (trained) ombudsman.

Ok. Fair.=20

I wasn't trying to make light of the issue, I'm just worried that some =
folk might try and use this to stop discussions that they are not =
actually feeling harassed by.=20
I don't have any better text to suggest -- I was thinking something like =
"Participants asked to stop a behavior that a reasonable person might =
view as  harassment are expected to comply immediately." or something, =
but it feels like it is missing something...

W

>=20
> Melinda
>=20

--=20
Outside of a dog, a book is your best friend, and inside of a dog, it's =
too dark to read=20



From hannes.tschofenig@gmx.net  Mon Oct 21 08:53:41 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 4176211E864D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:53: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 fwPXnA0rqbKO for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 08:53:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 81FB521F9D18 for <ietf@ietf.org>; Mon, 21 Oct 2013 08:53:02 -0700 (PDT)
Received: from [172.16.254.200] ([80.92.115.161]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MQzUc-1V9UZu3eak-00UGdC for <ietf@ietf.org>; Mon, 21 Oct 2013 17:53:01 +0200
Message-ID: <52654DEF.7050200@gmx.net>
Date: Mon, 21 Oct 2013 17:53:19 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com>
In-Reply-To: <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:EbJnK8cqbvAft95YgEpaDPkpC5425fr5lCgmJoy+eWZO62xdxa3 RneEMYiqTChPVbUBjbb1VNC/xNh4DiMmuqsgFM+DXSp2Sx/QoD/u+iqlXx+6W4mL4Xfa+C6 98ztdNGwH6qhvvhyjIfws3WoZn3qJpmPSzCPxK7ULTnXAw2kEGE3l4itmeWY9AYru4X28q0 o0MkbcfuhDRXF8dNw8HoQ==
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, 21 Oct 2013 15:53:41 -0000

On 10/21/2013 04:34 PM, Jorge Amodio wrote:
> Halald Alvestrand (which btw is from Norway not the USA)

This illustrates part of the problem.

It depends on the type of argument you want to make and then you count 
people different. You count Harald as someone who comes from Norway. The 
author of the slide deck wanted to make a different argument and so he 
sees Harald as a person working for Google, as US-based company.

We had the same issue in the diversity discussion.

Ciao
Hannes


From jeanjour@comcast.net  Mon Oct 21 09:04:20 2013
Return-Path: <jeanjour@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 9F7FB11E8584 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:04:20 -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=[AWL=-0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, 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 8PeAIC0shoJX for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:04:15 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id DB53511E81BF for <ietf@ietf.org>; Mon, 21 Oct 2013 09:03:36 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta02.westchester.pa.mail.comcast.net with comcast id foCr1m0041swQuc51s3cEk; Mon, 21 Oct 2013 16:03:36 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta15.westchester.pa.mail.comcast.net with comcast id fs3a1m00d14WE023bs3b16; Mon, 21 Oct 2013 16:03:36 +0000
Mime-Version: 1.0
Message-Id: <a0624085fce8afbbba1ac@[10.0.1.3]>
In-Reply-To: <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com>
Date: Mon, 21 Oct 2013 11:58:44 -0400
To: Jorge Amodio <jmamodio@gmail.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: multipart/alternative; boundary="============_-829751080==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382371416; bh=CSqrLRCs3xD1nWDC+SXYYbr2PK7QyW/lDTE/oB/qqSA=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=lvQn6gE8PlJbGLkWfEOgtNKZ7SkilV7He4YZXCxfynQQlIR2ovSc80A/RmLyqxSC4 kHZBtBv3NYdQswtZL+z4/oOoFV3NQO8gVRZYdj+QnoRiF1q3TvQH2XcmuitAgN/reM idPAiBasXMvjZJi8MRDXHsnog6vabzmT9oHGmzTizLmVkPM13O7TYAQuHQDAg6/pKH Q0Vmd95NlO6ku0xRp0950zI7GjoAU+/kXduUWP+nl7ka8P4T3ZQxgpz8B5qvHyAs0+ Y1H0y234Uj8kyUdaVDvbzJ4k9+9zFPumFIxtWXx1bEskBgCWHvNj2WbrGfv6G4IPQv cpSnyBaxMt9Bw==
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, 21 Oct 2013 16:04:20 -0000

--============_-829751080==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

 From my experience over the years, I would generalize this that the 
developed world has dominated the standards process in this field, 
whether it was the IETF, ISO, ITU, or IEEE and most others.  Most of 
that has to do with the expense involved in participating.  Since the 
1990s, the ability to participate on-line has done a lot to lower 
that barrier and we see that.  At one point IEEE was considered a US 
professional organization and all of their standards were run through 
ISO.  Some still are.

It still takes time for countries to "come up to speed" and do we 
really have any idea how many are watching but contributing 
infrequently. As Jorge points out we are seeing this change, although 
perhaps not as fast as we (or they) would like.

Yes, English is a problem for all non-English speakers.   It takes a 
lot of effort to work in a foreign language even when you are fluent, 
and English isn't the easiest of languages.  ;-) I have discussed 
this with many people and there does not seem to any way around it. 
150 years ago, it would have been French.  How often do you see two 
non-English speakers conversing in English because it is the only 
common denominator?  It looks like we are stuck with it.  I know of 
no standards committee that does not operate in English, although 
some may run plenaries with translation into one or two other 
languages.  (For all of you non-English speakers, be glad that most 
of us American English speakers don't speak another language!  Lets 
you talk about us without us knowing what you are saying!)  ;-)

As with most things like this, if the problem isn't stressed progress 
against the issue will be even slower.  There are structural issues 
in the IETF that allow over representation in meetings, what some 
might call stacking meetings, but this seems to be a case more of 
companies stacking meeting rather than countries.

But as a friend said to me, it is good to see that after 40+ years, 
Pouzin is still getting people riled up!  He has a very long history 
of this!  ;-)  It got him black balled in France.

Take care,
John Day

At 9:34 AM -0500 10/21/13, Jorge Amodio wrote:
>He is right that the USA and perhaps other developed countries 
>dominate the Internet standardization process but there is a good 
>reason why and that when I talk with people from developing 
>countries like mine (Argentina) they don't are able yet to 
>understand that blaming the "north" is not the solution and what 
>they need to do is to gets hands on into the issue and 
>develop/implement reasonable policies to have more participation in 
>the process.
>
>Obviously there is a lot of participation from people from the USA 
>or working for US companies, full time or almost full time 
>participation in the IETF process requires for the participant to 
>have a sponsor, after all she/he still needs to live in a decent 
>place, feed her/his family and pay the bills, and have some security 
>for retirement in the long term, plus pay for the trips, etc, etc.
>
>US companies (and sometimes the government) know very well that it 
>has a lot of strategic value for the company, and the country, to 
>sponsor such type of individuals. I doubt that Vint Cerf, Halald 
>Alvestrand (which btw is from Norway not the USA), and many others, 
>are part of the daily grind working at Google and punching time 
>cards, but Google recognizes and value having such type of 
>individuals embedded in the development of the Internet, and they 
>have big pockets to fund them.
>
>The issue is that the knuckleheads in charge in other parts of the 
>world don't get yet to understand that if they want to be part of 
>the process they have to invest in it, and particularly sponsor 
>skilled and capable individuals so they can dedicate most of their 
>time and brain to it and not worry about how they will pay the bills 
>at the end of the month or if they will have a job next week, and 
>for sure they will have to compete for talent with US based 
>companies.
>
>So for the knuckleheads stop whining and do something ...
>
>My .02
>-J
>
>
>
>
>On Mon, Oct 21, 2013 at 7:58 AM, Stephane Bortzmeyer 
><<mailto:bortzmeyer@nic.fr>bortzmeyer@nic.fr> wrote:
>
>What did they say, in the movie Apocalypse Now? "I like the smell of
>the troll in the morning"?
>
><http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf>http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf

--============_-829751080==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: Internet standardisation remains
unilateral</title></head><body>
<div>From my experience over the years, I would generalize this that
the developed world has dominated the standards process in this field,
whether it was the IETF, ISO, ITU, or IEEE and most others.&nbsp; Most
of that has to do with the expense involved in participating.&nbsp;
Since the 1990s, the ability to participate on-line has done a lot to
lower that barrier and we see that.&nbsp; At one point IEEE was
considered a US professional organization and all of their standards
were run through ISO.&nbsp; Some still are.</div>
<div><br></div>
<div>It still takes time for countries to &quot;come up to speed&quot;
and do we really have any idea how many are watching but contributing
infrequently. As Jorge points out we are seeing this change, although
perhaps not as fast as we (or they) would like.</div>
<div><br></div>
<div>Yes, English is a problem for all non-English speakers.&nbsp;&nbsp;
It takes a lot of effort to work in a foreign language even when you
are fluent, and English isn't the easiest of languages.&nbsp; ;-) I
have discussed this with many people and there does not seem to any
way around it.&nbsp; 150 years ago, it would have been French.&nbsp;
How often do you see two non-English speakers conversing in English
because it is the only common denominator?&nbsp; It looks like we are
stuck with it.&nbsp; I know of no standards committee that does not
operate in English, although some may run plenaries with translation
into one or two other languages.&nbsp; (For all of you non-English
speakers, be glad that most of us American English speakers don't
speak another language!&nbsp; Lets you talk about us without us
knowing what you are saying!)&nbsp; ;-)</div>
<div><br></div>
<div>As with most things like this, if the problem isn't stressed
progress against the issue will be even slower.&nbsp; There are
structural issues in the IETF that allow over representation in
meetings, what some might call stacking meetings, but this seems to be
a case more of companies stacking meeting rather than countries.</div>
<div><br></div>
<div>But as a friend said to me, it is good to see that after 40+
years, Pouzin is still getting people riled up!&nbsp; He has a very
long history of this!&nbsp; ;-)&nbsp; It got him black balled in
France.</div>
<div><br></div>
<div>Take care,</div>
<div>John Day</div>
<div><br></div>
<div>At 9:34 AM -0500 10/21/13, Jorge Amodio wrote:</div>
<blockquote type="cite" cite>He is right that the USA and perhaps
other developed countries dominate the Internet standardization
process but there is a good reason why and that when I talk with
people from developing countries like mine (Argentina) they don't are
able yet to understand that blaming the &quot;north&quot; is not the
solution and what they need to do is to gets hands on into the issue
and develop/implement reasonable policies to have more participation
in the process.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Obviously there is a lot of participation
from people from the USA or working for US companies, full time or
almost full time participation in the IETF process requires for the
participant to have a sponsor, after all she/he still needs to live in
a decent place, feed her/his family and pay the bills, and have some
security for retirement in the long term, plus pay for the trips, etc,
etc.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>US companies (and sometimes the
government) know very well that it has a lot of strategic value for
the company, and the country, to sponsor such type of individuals. I
doubt that Vint Cerf, Halald Alvestrand (which btw is from Norway not
the USA), and many others, are part of the daily grind working at
Google and punching time cards, but Google recognizes and value having
such type of individuals embedded in the development of the Internet,
and they have big pockets to fund them.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The issue is that the knuckleheads in
charge in other parts of the world don't get yet to understand that if
they want to be part of the process they have to invest in it, and
particularly sponsor skilled and capable individuals so they can
dedicate most of their time and brain to it and not worry about how
they will pay the bills at the end of the month or if they will have a
job next week, and for sure they will have to compete for talent with
US based companies.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>So for the knuckleheads stop whining and
do something ...</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>My .02</blockquote>
<blockquote type="cite" cite>-J</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><br>
<br>
</blockquote>
<blockquote type="cite" cite>On Mon, Oct 21, 2013 at 7:58 AM, Stephane
Bortzmeyer &lt;<a
href="mailto:bortzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt; wrote:<br>
<blockquote>What did they say, in the movie Apocalypse Now? &quot;I
like the smell of<br>
the troll in the morning&quot;?<br>
<br>
<a
href=
"http://innovation-regulation2.telecom-paristech.fr/wp-content/uploads/Documents/thematiques/Standardization/Pouzin-Internet_standardisatio.pdf"><span
></span
>http://innovation-regulation2.telecom-paristech.fr/wp-content/upload<span
></span
>s/Documents/thematiques/Standardization/Pouzin-Internet_standardisat<span
></span>io.pdf</a></blockquote>
</blockquote>
<div><br></div>
</body>
</html>
--============_-829751080==_ma============--

From rsk@gsp.org  Mon Oct 21 09:08:55 2013
Return-Path: <rsk@gsp.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 5B39911E8265 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:08: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 rlfbyJ0VDV5g for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:08:50 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABAE11E8665 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:07:27 -0700 (PDT)
Received: from gsp.org (localhost.firemountain.net [127.0.0.1]) by taos.firemountain.net (8.14.7/8.14.7) with SMTP id r9LG7NsR007657 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:07:24 -0400 (EDT)
Date: Mon, 21 Oct 2013 12:07:23 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: [IETF] Re: [IETF] Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131021160723.GA11390@gsp.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net> <52654B65.3000006@gmail.com> <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net>
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: Mon, 21 Oct 2013 16:08:55 -0000

On Mon, Oct 21, 2013 at 11:50:35AM -0400, Warren Kumari wrote:
> Ok. Fair. 
> 
> I wasn't trying to make light of the issue, I'm just worried that
> some folk might try and use this to stop discussions that they are not
> actually feeling harassed by.

I share this concern.  Sometimes discussions get...toasty...but that's
the nature of debateXXXXXXargument among smart people with strong opinions.
I think it's a good thing: I think it helps us collectively arrive at
good decisions because the give-and-take tends to weed out the bad ones.
And I don't want to see it truncated by a bogus claim of harrassment
made by someone who's on the losing side and looking for a trump card.

That said, I second Warren's "Ok. Fair." response to Melinda ("You kick
the problem over to your (trained) ombudsman") because I think it'd be
pretty easy for the ombudsman to distinguish between minor flamage and
actual harrassment.

Also, I second the recommendation (downthread) to have counsel review
this if that hasn't already been done.

Overall: +1, and I hope we never (or rarely) have to use this.

---rsk

From sm@resistor.net  Mon Oct 21 09:14:06 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 6180211E81D1 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:14:06 -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 B16o9uHU5nPt for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:14:04 -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 F0A2C11E866E for <ietf@ietf.org>; Mon, 21 Oct 2013 09:13: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 r9LGDUVf020368; Mon, 21 Oct 2013 09:13:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382372015; bh=c1TfaqLGbc2IAHHmChJYzU03+7NKKxwLf6kDYB1NSHE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lni3NgZcfRpCb6Agyt1SQtscutF0nlpFHg4G3bda/K5UCnCjNx3BToiGoPPesfLkv gwxOtQ0qEW/rQQUqP8+gNE439Fe3U1/4Vd3LKesV/IqlIGVtCQG/HuaNSCpq8Kr/DL yb6tSngjit/516QQuKxarbDPUTSPsoZNmnIAtfpc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382372015; i=@resistor.net; bh=c1TfaqLGbc2IAHHmChJYzU03+7NKKxwLf6kDYB1NSHE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y1IFS7q48J9q8kCHSExhUmTDdDVbICK+rw/t6B9SU7G6l1FzsgZgdKacAuvJZwv9k z9ov05cBZ4GcsgDf+0T6I0h+rv8Y8SPcCWBxUfGuifgixafaxfTuAaota2X1xOUZY7 ojkwtAZ9NqI6vJ2w+xhgkuQ+5Bg18rAoeEyegvKc=
Message-Id: <6.2.5.6.2.20131021075057.0e36a248@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Oct 2013 08:31:45 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Separate ADs roles from IESG - draft-klensin-stds-review-panel-00
In-Reply-To: <CAMm+Lwj4T6o2n3_OWdesnB0E=_p=QvEQX57coo_kgJsbU72=vA@mail.g mail.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@192.168.1.128> <6.2.5.6.2.20131020213751.0bc83de8@resistor.net> <CAMm+Lwj4T6o2n3_OWdesnB0E=_p=QvEQX57coo_kgJsbU72=vA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Mon, 21 Oct 2013 16:14:06 -0000

Hi Phillip,
At 04:08 21-10-2013, Phillip Hallam-Baker wrote:
>The three questions of power:
>
>1 How did you get it?

The persons are selected by NomCom.

>2 For whose benefit do you use it?

Each person has his/her own motivation.  A person can do it for 
money.  A person can do it to look important.  A person can do it for 
other reasons.

>3 How do we get rid of you?

It could be through a Recall petition.

>Unless there are satisfactory answers to 1 and 3, the answer to 2 is 
>going to always be unacceptable. Concentrating decision making power 
>in yet another unelected, unaccountable body is not viable.

An election is a popularity contest.  It is possible to have 
accountability without resorting to popularity contests.

Regards,
-sm 


From jari.arkko@piuha.net  Mon Oct 21 09:32: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 BAF8211E853B for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.955
X-Spam-Level: 
X-Spam-Status: No, score=-101.955 tagged_above=-999 required=5 tests=[AWL=-0.648, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPjgr6F9iB7a for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:32:46 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 06E0F11E8527 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:32:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B31142CCBF for <ietf@ietf.org>; Mon, 21 Oct 2013 19:32:27 +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 J4mS7IMYlaC1 for <ietf@ietf.org>; Mon, 21 Oct 2013 19:32:27 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 6A5CC2CC48 for <ietf@ietf.org>; Mon, 21 Oct 2013 19:32:26 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [IETF] [IETF] Re: Proposed IETF Anti-Harassment Policy
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20131021160723.GA11390@gsp.org>
Date: Tue, 22 Oct 2013 00:32:24 +0800
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC707EB6-9856-4911-9B5F-C98665213F92@piuha.net>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net> <52654B65.3000006@gmail.com> <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net> <20131021160723.GA11390@gsp.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 16:32:55 -0000

Thanks for the excellent feedback so far.

I wanted to point out one thing in the continuing discussion. Despite =
the best intentions and us being engineers and all, it may not actually =
be possible to write a full spec that accurately defines what is and =
what is not harassing behaviour. E.g. photography. I think Don had it =
right in the case that he described, but it would have been hard to =
write that down before even hearing about such a case.

Hence judgment needs to be applied by the ombudsperson & the rest of the =
IETF management.

Jari


From dhc@dcrocker.net  Mon Oct 21 09:33:25 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 123F511E853B for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:33:25 -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 zTOjtImOQ0lg for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:33:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 40D9921F9DB0 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:33:08 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9LGX1WG018901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 Oct 2013 09:33:06 -0700
Message-ID: <52655738.80909@dcrocker.net>
Date: Mon, 21 Oct 2013 12:32:56 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dcrocker@bbiw.net
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr>
In-Reply-To: <20131021133009.GA27979@nic.fr>
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, 21 Oct 2013 09:33:06 -0700 (PDT)
Cc: 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, 21 Oct 2013 16:33:25 -0000

On 10/21/2013 9:30 AM, Stephane Bortzmeyer wrote:
> On Mon, Oct 21, 2013 at 09:08:43AM -0400,
>   Dave Crocker <dhc@dcrocker.net> wrote
>   a message of 27 lines which said:
>
>> He invented the datagram...
>
> Some people say it is Leonard Kleinrock. I welcome any precise

With a very strong interest in /not/ getting into the history debates, 
I'll point out that datagram is a term of art this is different from 
packet switching.  Besides the Wikipedia entry on Louis, I'll note that 
I've regularly hear him credited for influencing the work on IP.

But my main point was that he's a very senior contributor in this space.


> references on the history of the datagram, specially if they are
> accessible online (whuich is rare for scientific papers of this
> time). Anyway, the fact that someone did something great X years ago
> (he also wrote the first shell and built Cyclades) does not mean he
> cannot troll today.
>
>> I think his slides do miss some essential points, but that it's a
>> case of correct numbers producing incorrect recommendations.
>
> Fair summary. His remark about the use of english is a good
> example. Is it a problem? Yes? Can anyone see a solution? No (and he
> does not suggest one).

I thought all of his points worthy of consideration.  Of course, that's 
different from /agreeing/ with all of them.  But worthy, nonetheless.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hallam@gmail.com  Mon Oct 21 09:39:29 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 1988C21F9D56 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 BgE-eDuWffqh for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:39:28 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0225F21F9D28 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:37:12 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id c11so4949034lbj.31 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:37:11 -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=W5hIA7dySTQBrKmOsRF+J/wjsWrfDpKj+3qlDr6+GGI=; b=gray2qjz85criukMOLqw0ZdqFT/XNOS1e/ANgZ8z9x2J/XNrRTjdBSKs2SxJg+k/mS HOdU/rgZYEzyMEn8S4c6tBUggP9pIcMqJoF+7oPu7hdPxgySOeHIbx2+uuqafA1n80oS 5wLvHFtD+xBzX5HLY3dN0FvHgdB7FHAyVbInXCZFOOqkLuaJS/zvuhP6CoOjG4G2eGOd 3EQBjdBFOPCPiNr2THJgbZAYfpLdt+TX1anYE0eA17Ertq1wlK/Lk4K1rAM3T2rGESGJ Ppmp7Ne125YcG9cLgBBjSIFEQ/VC9qtLOvNLzK9BZ6XmWUFg78J3PsSakXE7l+rolKw1 mWtw==
MIME-Version: 1.0
X-Received: by 10.152.29.103 with SMTP id j7mr14023653lah.7.1382373431765; Mon, 21 Oct 2013 09:37:11 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 09:37:11 -0700 (PDT)
In-Reply-To: <51234A08-1462-46DA-A179-A0823DFDD90C@hopcount.ca>
References: <20131021125834.GA24167@nic.fr> <CAMm+LwhngSCp3BoBpVu3u09pmFAcYx0KqUrt7g5eP=5TmG2yYQ@mail.gmail.com> <51234A08-1462-46DA-A179-A0823DFDD90C@hopcount.ca>
Date: Mon, 21 Oct 2013 12:37:11 -0400
Message-ID: <CAMm+LwjY4=_+yHNrUSXzxNJpz_=4s5kW5DxGR-PB91pU5cADNg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Abley <jabley@hopcount.ca>
Content-Type: multipart/alternative; boundary=089e0160b82858f1db04e942e51f
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, 21 Oct 2013 16:39:29 -0000

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

On Mon, Oct 21, 2013 at 11:20 AM, Joe Abley <jabley@hopcount.ca> wrote:

>
> On 2013-10-21, at 11:14, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
> > I think it is counter productive to label opinions you find unpleasant
> 'troll'. That implies that the only reason the views are raised is to
> provoke a pointless argument.
>
> I don't think Stephane was labelling an opinion a troll. I think he was
> labelling the source of the opinions a troll.


That is the same thing.

It is rude.

It is bullying.

It should stop.


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

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

<div dir=3D"ltr">On Mon, Oct 21, 2013 at 11:20 AM, Joe Abley <span dir=3D"l=
tr">&lt;<a href=3D"mailto:jabley@hopcount.ca" target=3D"_blank">jabley@hopc=
ount.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"g=
mail_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>
On 2013-10-21, at 11:14, Phillip Hallam-Baker &lt;<a href=3D"mailto:hallam@=
gmail.com">hallam@gmail.com</a>&gt; wrote:<br>
<br>
&gt; I think it is counter productive to label opinions you find unpleasant=
 &#39;troll&#39;. That implies that the only reason the views are raised is=
 to provoke a pointless argument.<br>
<br>
</div>I don&#39;t think Stephane was labelling an opinion a troll. I think =
he was labelling the source of the opinions a troll.</blockquote><div><br><=
/div><div>That is the same thing.</div><div><br></div><div>It is rude.=A0</=
div>
<div><br></div><div>It is bullying.</div><div><br></div><div>It should stop=
.=A0</div></div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D=
"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0160b82858f1db04e942e51f--

From lixia@cs.ucla.edu  Mon Oct 21 09:41:25 2013
Return-Path: <lixia@cs.ucla.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 8546011E81F2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:41:25 -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=[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 7+vexaRgAneR for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:41:20 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 2D18411E85D6 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:39:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id D392939E8105; Mon, 21 Oct 2013 09:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ej2jAJWJGkke; Mon, 21 Oct 2013 09:39:57 -0700 (PDT)
Received: from cs-211-104.cs.ucla.edu (Cs-211-104.CS.UCLA.EDU [131.179.211.104]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 1632439E8100; Mon, 21 Oct 2013 09:39:57 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Internet standardisation remains unilateral
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <20131021133009.GA27979@nic.fr>
Date: Mon, 21 Oct 2013 09:39:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1510)
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 16:41:25 -0000

On Oct 21, 2013, at 6:30 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:

> On Mon, Oct 21, 2013 at 09:08:43AM -0400,
> Dave Crocker <dhc@dcrocker.net> wrote=20
> a message of 27 lines which said:
>=20
>> He invented the datagram...
>=20
> Some people say it is Leonard Kleinrock. I welcome any precise
> references on the history of the datagram, specially if they are
> accessible online (whuich is rare for scientific papers of this
> time).

Pouzin might have coined the word "datagram" in an early 70's paper =
(memory is vague now), but it seems that the concept of datagram is =
already in Paul Baran's seminal paper published in IEEE Trans. on =
Communications (March 1964).
And yes it is online (credit to David Goldberg who scanned the paper):
    http://www.cs.ucla.edu/classes/cs217/Baran64.pdf
(read pages 6 & 7)

FYI=20

> Anyway, the fact that someone did something great X years ago
> (he also wrote the first shell and built Cyclades) does not mean he
> cannot troll today.
>=20
>> I think his slides do miss some essential points, but that it's a
>> case of correct numbers producing incorrect recommendations.
>=20
> Fair summary. His remark about the use of english is a good
> example. Is it a problem? Yes? Can anyone see a solution? No (and he
> does not suggest one).
>=20


From dhc@dcrocker.net  Mon Oct 21 09:42:17 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 B647011E8671 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:42: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 V5L7Te-FKtW9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:42:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 392B611E81CC for <ietf@ietf.org>; Mon, 21 Oct 2013 09:40:53 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9LGemWZ020060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 Oct 2013 09:40:52 -0700
Message-ID: <5265590B.4070705@dcrocker.net>
Date: Mon, 21 Oct 2013 12:40:43 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr>	<67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr>
In-Reply-To: <20131021133746.GA29267@nic.fr>
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, 21 Oct 2013 09:40:53 -0700 (PDT)
Cc: 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, 21 Oct 2013 16:42:18 -0000

On 10/21/2013 9:37 AM, Stephane Bortzmeyer wrote:
> On Mon, Oct 21, 2013 at 09:30:30AM -0400,
>   John C Klensin <john-ietf@jck.com> wrote
>   a message of 19 lines which said:
>
>> Do you have any idea what Slide 8 is about?
>
> No, I don't and that's one of the reasons I used the term
> "troll". Pouzin often mentions "problems with Unicode" but he never
> documented them in detail.


Calling someone a troll is an ad hominem.  We aren't supposed to do that 
in the IETF.  At least, not publicly.

To call a very senior, very serious contributor a troll because their 
slides don't explain something is rather worse than ad hominem.

One could even imagine invoking a criterion that is that inappropriate 
as qualifying the critic as a troll...

d/


ps.  and no, this note is meant not to be responded to.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hallam@gmail.com  Mon Oct 21 09:55: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 A15EC11E8411 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  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 8x4IGGfLbkrX for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 09:55:14 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 911F711E81ED for <ietf@ietf.org>; Mon, 21 Oct 2013 09:54:36 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id eh20so771515lab.25 for <ietf@ietf.org>; Mon, 21 Oct 2013 09:54: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=HztE/K/xDjVrts+pB1bqlBuDpXbHo6Qrd/HI3TGSxd8=; b=w+Toc2JMq6Aw9BCcvDOYmvXkSousipizMqWwT/04dYPEt1TLe+9SfDQpCXk2a1BoAd uCFMUx5nTo2j8FwlkNFQoO8x23PwzyTttPNlQmDJaOPNa5WjHkQTzFxErl2X/pM/OIpa F6cZSQKdPYzfvokt/K5fG1KlnPHgZ2q+MkmxVnUD0P+u23cwShA/F/vz78EcUFcXiRnN dgURek3mkSaSeQJ3ejp0PQdyMGyxTT/O+GJcrGR7l914hlKT+5x2W0N00huHYkZxftAB ybu0XuJ4xzN7YLK2Vupn+4aO6TgB1RbvQaS/vqSumGsz8YsRoUy9YtBs28FT9gIX3opc bAcw==
MIME-Version: 1.0
X-Received: by 10.112.51.101 with SMTP id j5mr13756060lbo.17.1382374474997; Mon, 21 Oct 2013 09:54:34 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 09:54:34 -0700 (PDT)
In-Reply-To: <52655738.80909@dcrocker.net>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr> <52655738.80909@dcrocker.net>
Date: Mon, 21 Oct 2013 12:54:34 -0400
Message-ID: <CAMm+Lwi-1rVPsDCvFZ6oDyQSYL80n07DyfknX4imZBy9Zi-gOg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a1133646087665f04e943231b
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, 21 Oct 2013 16:55:16 -0000

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

On Mon, Oct 21, 2013 at 12:32 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 10/21/2013 9:30 AM, Stephane Bortzmeyer wrote:
>
>> On Mon, Oct 21, 2013 at 09:08:43AM -0400,
>>   Dave Crocker <dhc@dcrocker.net> wrote
>>   a message of 27 lines which said:
>>
>>  He invented the datagram...
>>>
>>
>> Some people say it is Leonard Kleinrock. I welcome any precise
>>
>
> With a very strong interest in /not/ getting into the history debates,
> I'll point out that datagram is a term of art this is different from packet
> switching.  Besides the Wikipedia entry on Louis, I'll note that I've
> regularly hear him credited for influencing the work on IP.
>

Giving credit for particular inventions is always problematic. I had
occasion to review the history of the invention of email. There are many
people who made important contributions and not always the ones that they
got credit for.

And sometime the contribution is not coming up with an idea but to perform
triage.


Take the Web, every part of the Web had been proposed before by Ted Nelson.
The only difference between Tim's idea and Ted's was that Tim's could be
implemented. Ted had 110% of a solution Tim stripped that down to 90% that
could be deployed and even though the Web does not have referential
transparency or universal indexicality etc., it was good enough to allow
Google etc. to add those in afterward.

That is a pattern that I see repeated again and again in Internet
development. A lot of the early pioneers were crazy guys whose ideas were
too extreme to be fully realized and had to be interpreted by someone else.

The point here is that when we are looking at security solutions to defeat
PRISM, what may be the most important choice is not which problems are
solved but which are left out. I think that what we have today in email
security is a Ted Nelson scheme that tries to do be too much and ends up
failing to be anything.

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

--001a1133646087665f04e943231b
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 Mon, Oct 21, 2013 at 12:32 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">On 10/21/2013 9:30 AM, Ste=
phane Bortzmeyer wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Mon, Oct 21, 2013 at 09:08:43AM -0400,<br>
=A0 Dave Crocker &lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">=
dhc@dcrocker.net</a>&gt; wrote<br>
=A0 a message of 27 lines which said:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
He invented the datagram...<br>
</blockquote>
<br>
Some people say it is Leonard Kleinrock. I welcome any precise<br>
</blockquote>
<br></div>
With a very strong interest in /not/ getting into the history debates, I&#3=
9;ll point out that datagram is a term of art this is different from packet=
 switching. =A0Besides the Wikipedia entry on Louis, I&#39;ll note that I&#=
39;ve regularly hear him credited for influencing the work on IP.<br>
</blockquote><div><br></div><div>Giving credit for particular inventions is=
 always problematic. I had occasion to review the history of the invention =
of email. There are many people who made important contributions and not al=
ways the ones that they got credit for.=A0</div>
<div><br></div><div>And sometime the contribution is not coming up with an =
idea but to perform triage.</div><div><br></div><div><br></div><div>Take th=
e Web, every part of the Web had been proposed before by Ted Nelson. The on=
ly difference between Tim&#39;s idea and Ted&#39;s was that Tim&#39;s could=
 be implemented. Ted had 110% of a solution Tim stripped that down to 90% t=
hat could be deployed and even though the Web does not have referential tra=
nsparency or universal indexicality etc., it was good enough to allow Googl=
e etc. to add those in afterward.</div>
<div><br></div><div>That is a pattern that I see repeated again and again i=
n Internet development. A lot of the early pioneers were crazy guys whose i=
deas were too extreme to be fully realized and had to be interpreted by som=
eone else.</div>
<div><br></div></div><div>The point here is that when we are looking at sec=
urity solutions to defeat PRISM, what may be the most important choice is n=
ot which problems are solved but which are left out. I think that what we h=
ave today in email security is a Ted Nelson scheme that tries to do be too =
much and ends up failing to be anything.=A0</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a1133646087665f04e943231b--

From michel@arneill-py.sacramento.ca.us  Mon Oct 21 10:25:33 2013
Return-Path: <michel@arneill-py.sacramento.ca.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 849AF11E8208 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:25:33 -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=[BAYES_50=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 oEgOfUjUyi8J for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:25:28 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9A99111E81DF for <ietf@ietf.org>; Mon, 21 Oct 2013 10:25:24 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Internet standardisation remains unilateral
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Oct 2013 10:25:24 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local>
x-mimeole: Produced By Microsoft Exchange V6.5
In-Reply-To: <a0624085fce8afbbba1ac@[10.0.1.3]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Internet standardisation remains unilateral
Thread-Index: Ac7OdzoTZcVFVD6sQ66EODr4SygwcQABMjYg
References: <20131021125834.GA24167@nic.fr><CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@[10.0.1.3]>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "John Day" <jeanjour@comcast.net>, "Jorge Amodio" <jmamodio@gmail.com>, "Stephane Bortzmeyer" <bortzmeyer@nic.fr>
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, 21 Oct 2013 17:25:33 -0000

> John Day wrote:
> How often do you see two non-English speakers conversing
> in English because it is the only common denominator?

All the time, and that is especially true in France; the only way to do
business across Europe is English; no one speaks all of French, Spanish,
Portuguese, Italian, German, Dutch, Danish, Swedish, Norwegian, Russian,
Polish, Romanian, Greek and yes English. The de-facto situation is that
almost everyone who steps outside their little part of the world speaks
their native language and English.

But too many French are entrenched in an anti-American culture that
refuses to learn English.

> It looks like we are stuck with it.

We are, and there is no point whining about it without actually doing
something about it.


> Jorge Amodio wrote:
> [..] but there is a good reason why and that when I talk with people
> from developing countries like mine (Argentina) they don't are able
> yet to understand that blaming the "north" is not the solution

And in this case it's even more misguided because France is not a
developing country.

Michel.


From john-ietf@jck.com  Mon Oct 21 10:42:17 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 3476F11E8108 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.538
X-Spam-Level: 
X-Spam-Status: No, score=-103.538 tagged_above=-999 required=5 tests=[AWL=0.061, 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 QwWD8SbtwAww for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:42:11 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C03A311E8126 for <ietf@ietf.org>; Mon, 21 Oct 2013 10:42: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 1VYJUT-0000nd-OC; Mon, 21 Oct 2013 13:42:05 -0400
Date: Mon, 21 Oct 2013 13:42:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Separate ADs roles from IESG
Message-ID: <EAF7FD59A9C4176F513F540E@JcK-HP8200.jck.com>
In-Reply-To: <52643500.3010406@joelhalpern.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.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 Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 17:42:17 -0000

Joel, 

While others have touched on pieces of the response I'm about to
give, I feel some obligation to respond directly to my
understanding of your point.


--On Sunday, October 20, 2013 15:54 -0400 "Joel M. Halpern"
<jmh@joelhalpern.com> wrote:

> The obvious risk if one separates WG management from review is
> that one could easily get the situation where the manager, in
> working with the WG, says that the document needs X, Y, and
> not Z.  And then the reviewer says "needs Z".  And there are
> more extreme versions of this.

Noting Dave Crocker's concern about the use of terms like
"manager", very little would change that would affect your
scenario.  The decision as to when a document was ready to go
into IETF LC would remain up to the relevant AD and IESG
(however the IESG decided to handle that which, as you know, has
varied over the years).  So, if the relevant AD said "needs X,
Y, and not Z", he or she could presumably keep the document in
the WG until either that requirement were met, he or she was
talked out of it, or the issue was appealed.  ADs would continue
to be fully aware of and to a considerable degree, accountable
for, "their" WGs and the quality of their technical work
(presumably including reviewing shepherd's reports), so that
part of the workload doesn't change.

If the IESG decided to force full IESG review and approval prior
to IETF Last Call, this family of proposals would not reduce
their workload at all and might ultimately increase it.  At the
other extreme (and preferably), if the relevant AD reviewed
materials to be sure everything was in order (procedurally and
technically), consulted other ADs, directorates, etc., as she
felt needed to be assured that things were in order, worked with
the WG and its leadership on what appeared to be outstanding or
problematic issues, and then forwarded the specification for
IETF Last Call, we would eliminate both the intensive,
word-by-word IESG reviews of documents, the need for the IESG to
take a "vote", and the requirement that ADs either perform or
arrange for extensive cross-area reviews (or carefully review
out-of-area documents themselves).  Note that also implies that
the IESG wouldn't get tied in knots over DISCUSS positions on
document approval: it would just not be their job and, if ADs,
especially ADs outside the relevant area, had concerns, their
obligations would stop when they brought those concerns to the
attention of the review body (with AD concerns presumably
carrying more weight than random comments on the IETF List
during LC, but not much more than a community LC comment that
was equally well justified).

And the responsible AD would be in a position to explain or
advocate for the WG's work/proposal to the review panel or could
delegate that job completely to a shepherd with a
slightly-revised "job" description.

Much of the management (sic) of IETF Last Call would fall on the
review body (details to be worked out).  That body could, as
others have suggested, solicit additional reviews from
individuals or groups, including asking ADs for advice on the
right people or groups to do that.  But they would bear the
final review and approval responsibility and would be directly
responsible to the community for it.    If, using your scenario,
they said "do Z", it would be no better and no worse than a
responsible AD imposing requirements X and Y before a Last Call
was conducted and then the IESG coming along and imposing
requirement Z after IETF LC completed -- modulo quibbling about
the difference between "requirements" and "comments to which
you'd better pay attention", that happens, a lot, today.

> Currently, the ability for the managing AD to say "no, this
> won't pass muster" is part of his management tool.  If he is
> not the reviewer, he seems to have lost an important tool.  I
> hope I am missing something that would make this sort of
> approach workable.

Again, the responsible AD still has to clear a specification for
IETF LC, so that doesn't change (regardless of what one thinks
about "management").

 best,
    john






From john-ietf@jck.com  Mon Oct 21 10:45:42 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 004A911E820E for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level: 
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.059, 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 cSNQVaQWKYyZ for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:45:11 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4076111E821C for <ietf@ietf.org>; Mon, 21 Oct 2013 10:45:06 -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 1VYJXN-0000oE-Dz; Mon, 21 Oct 2013 13:45:05 -0400
Date: Mon, 21 Oct 2013 13:45:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Internet standardisation remains unilateral
Message-ID: <673A097E66897B69B6C13B73@JcK-HP8200.jck.com>
In-Reply-To: <20131021133746.GA29267@nic.fr>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr>
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: Mon, 21 Oct 2013 17:45:43 -0000

--On Monday, October 21, 2013 15:37 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

> On Mon, Oct 21, 2013 at 09:30:30AM -0400,
>  John C Klensin <john-ietf@jck.com> wrote 
>  a message of 19 lines which said:
> 
>> Do you have any idea what Slide 8 is about?
> 
> No, I don't and that's one of the reasons I used the term
> "troll". Pouzin often mentions "problems with Unicode" but he
> never documented them in detail.

That was a lot of what caused me to wonder.  I certainly know of
things I consider problems with Unicode, but they aren't with
scripts he is likely to be complaining about.  We also know of
the issues that Jefsey and others have raised about majuscules,
but unless I've been misinformed, the relevant AFNOR coding
standards don't reflect the difference.   So, whatever should or
should not be done about those issues, it is hard to blame them
on Unicode (at least if there wasn't a formal request from AFNOR
to Unicode to make the distinction that was dismissed or
rejected).

I've got the same reaction to "IDN technical restrictions".  I'm
not aware of any significant ones unless one has a desire to
use, e.g., symbols, as domain name labels.  And, as far as
"visual ambiguities" are concerned, I'd love to know what he
proposes because, despite lots of dancing around (and large
collections of committees and procedures where ICANN is
involved) the only really effective fixes I can imagine are to
not try to do IDNs (and also prohibit "0" and "1" from ASCII /
LDH domain names) or to discard the DNS in favor of some system
that would apply different matching rules in different parts of
the tree. 

As Dave Crocker says, Louis is certainly no troll.  That doesn't
prevent wondering about some of his comments sometimes.

Incidentally, I consider most of those slides to be distortions,
presumably  in support of a rather specific agenda or at least
the result of a very different perspective on appropriate global
networking technology.  That agenda isn't news (nor is the
"national networks connected by gateways" model and perspective)
and the slides should probably not be dignified by a reaction
from the IETF.  But, when he says something that appears to be
substantive and relevant, I have enough respect for him and his
contributions to want to try to understand if there is anything
to it that we should be considering.

best,
     john



From john-ietf@jck.com  Mon Oct 21 10:53:30 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 D4CFB11E839E for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.543
X-Spam-Level: 
X-Spam-Status: No, score=-103.543 tagged_above=-999 required=5 tests=[AWL=0.056, 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 zxc5RSMJI6kw for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 10:53:25 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6E32911E8361 for <ietf@ietf.org>; Mon, 21 Oct 2013 10:52: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 1VYJep-0000p7-IH; Mon, 21 Oct 2013 13:52:47 -0400
Date: Mon, 21 Oct 2013 13:52:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: Separate ADs roles from IESG
Message-ID: <24CF14369F77E6876FAEDA6E@JcK-HP8200.jck.com>
In-Reply-To: <A8F9355A-5499-4FDE-A668-E919504E900F@checkpoint.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com> <A8F9355A-5499-4FDE-A668-E919504E900F@checkpoint.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 Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 17:53:31 -0000

--On Monday, October 21, 2013 10:51 +0000 Yoav Nir
<ynir@checkpoint.com> wrote:

> The question, though, is how much would that reduce the load
> on the IESG. If all we've done is get it down from 35
> hours/week to 28 hours/week, I'm not sure it's worth it,
> because you still can't hold another full-time job.

Yoav,

As others have pointed out, we don't have any large-scale
statistics about why people say "no".  But, speaking quite
anecdotally from situations I've been involved in, there is a
huge difference between allowing someone to cut productive
day-job work hours down to four or even 2 1/2 or three days a
week and having to give them up entirely for two years.  

In many situations, the choice isn't between "full time
availability for non-IETF work" and "IETF is the full time job".
It is whether someone has enough cycles left over after IETF
commitments to be substantially useful in the "day job"
environment.  

In addition and for better or worse, I don't think the IESG (or
IAB) are ever likely to become the sort of role that is suited
to someone who puts in 40 hours a week (or 35 in some countries)
and then goes home and forgets about the job or role.  In
practice, 28 hours / week might be considerably less than
half-time. 

   best,
    john




From mars.techno.cat@gmail.com  Mon Oct 21 11:04:38 2013
Return-Path: <mars.techno.cat@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 21A6E11E832F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:04: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, 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 x0Vs6yI1Soku for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:04:37 -0700 (PDT)
Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2407411E8342 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:04:29 -0700 (PDT)
Received: by mail-vb0-f51.google.com with SMTP id x16so4164328vbf.24 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:04:28 -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=7UI2JSUmTMHaHr4rrPUcb/eGRrT4VqfxqLnYcOL5XSI=; b=C+sZiBjjUkA5+CpcaauuwYpKHd2RZtv1Jp5Ctotarc6FSbTpeD6l9Ttbh+PyITAwsX oHrLHNVtJ6lfsIF0BvBF3HS6QY8UNNyOFPg9ZVAWqeCNy35lRv5q9ZqMyR2xqBdsM+Oj 3BNyAceDipbM7qnK3IJVEpG+LLGJ6XOn0SKVuJHoRnMihsSHJ8IENK8h30QN6XIoqPSt qQ71yasSpIKFSVbXRfLKvTDrOv5Wc/W/4GZmxaaDnwB8gqDJaX9ylSOnq9qm4Yk8hSvi 13b/QhccvaMda60VnfmPs5zHo1p34x2TPm63NHf1FNMueEMJxRKfpvomBtqvVfhrn/S4 F6eg==
MIME-Version: 1.0
X-Received: by 10.52.26.69 with SMTP id j5mr1662870vdg.21.1382378668387; Mon, 21 Oct 2013 11:04:28 -0700 (PDT)
Received: by 10.58.44.106 with HTTP; Mon, 21 Oct 2013 11:04:28 -0700 (PDT)
In-Reply-To: <5262FB95.8080500@gmail.com>
References: <5262FB95.8080500@gmail.com>
Date: Mon, 21 Oct 2013 13:04:28 -0500
Message-ID: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Techno CAT <mars.techno.cat@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=20cf307f324679742b04e9441dde
Cc: ietf@ietf.org, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 18:04:38 -0000

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

"Calling someone a troll is an ad hominem. We aren't supposed to do that in
the IETF. At least, not publicly."[1]

"It is rude.
It is bullying." [2]

HARASSMENT by Brian E Carpenter has been noted for the Legal Record

http://www.cs.auckland.ac.nz/~brian/
"Network Geeks - How They Built the Internet"

===========================

HARASSMENT by Stephane Bortzmeyer <bortzmeyer at
nic.fr<bortzmeyer@DOMAIN.HIDDEN>>
has been noted for the Legal Record
http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html

===========================

http://www.ietf.org/mail-archive/web/ietf/current/msg83360.html
"judgment needs to be applied by the ombudsperson & the rest of the IETF
management

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg83364.html
[2] http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html

"you are encouraged to raise your concern in confidence with one of
the Ombudspersons"
http://www.intgovforum.org
http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_201112_990.pdf



On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Hi Jordi,
>
> We seem to have a new troll using the address mars.techno.cat@gmail.com
>
> Can you deal with it appropriately, please?
>
> Thanks
>
>     Brian
>
>


-- 

@Techno_CAT_r
http://Twitter.com/Techno_CAT_r

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

<div dir=3D"ltr"><div><div><tt>&quot;Calling someone a troll is an ad homin=
em.  We aren&#39;t supposed to do that=20
</tt><tt>in the IETF.  At least, not publicly.&quot;[1]<br><br></tt>&quot;I=
t is rude.=A0</div>It is bullying.&quot; [2]<br><br>HARASSMENT by Brian E C=
arpenter has been noted for the Legal Record<br><br><a href=3D"http://www.c=
s.auckland.ac.nz/~brian/">http://www.cs.auckland.ac.nz/~brian/</a><br>
<font face=3D"Arial">&quot;Network Geeks - How They Built the Internet&quot=
;</font><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=3D=3D<br><br></div>HARASSMENT by Stephane Bortzmeyer &lt=
;<a href=3D"mailto:bortzmeyer@DOMAIN.HIDDEN">bortzmeyer at nic.fr</a>&gt; h=
as been noted for the Legal Record<br>
<div><a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg83330.=
html">http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html</a><b=
r><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=3D=3D<br><br><a href=3D"http://www.ietf.org/mail-archive/web/ietf/cu=
rrent/msg83360.html">http://www.ietf.org/mail-archive/web/ietf/current/msg8=
3360.html</a><br>
&quot;judgment needs to be applied by the ombudsperson &amp; the rest of th=
e IETF management<br><br>[1] <a href=3D"http://www.ietf.org/mail-archive/we=
b/ietf/current/msg83364.html">http://www.ietf.org/mail-archive/web/ietf/cur=
rent/msg83364.html</a><br>
[2] <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg83362.h=
tml">http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html</a><br=
><br><pre>&quot;you are encouraged to raise your concern in confidence with=
 one of the Ombudspersons&quot;<br>
<a rel=3D"nofollow" href=3D"http://www.intgovforum.org">http://www.intgovfo=
rum.org</a><br><a rel=3D"nofollow" href=3D"http://990s.foundationcenter.org=
/990_pdf_archive/541/541650477/541650477_201112_990.pdf">http://990s.founda=
tioncenter.org/990_pdf_archive/541/541650477/541650477_201112_990.pdf</a><b=
r>
</pre></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter <span dir=3D"ltr">&=
lt;<a href=3D"mailto:brian.e.carpenter@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">Hi Jordi,<br>
<br>
We seem to have a new troll using the address <a href=3D"mailto:mars.techno=
.cat@gmail.com">mars.techno.cat@gmail.com</a><br>
<br>
Can you deal with it appropriately, please?<br>
<br>
Thanks<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 Brian<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><br>-- <br><div dir=
=3D"ltr"><br>@Techno_CAT_r<br><a href=3D"http://Twitter.com/Techno_CAT_r" t=
arget=3D"_blank">http://Twitter.com/Techno_CAT_r</a><br></div>
</div>

--20cf307f324679742b04e9441dde--

From john-ietf@jck.com  Mon Oct 21 11:07:17 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 7061B11E832F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.545
X-Spam-Level: 
X-Spam-Status: No, score=-103.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 XYNXm+1TSE6d for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:06:48 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3354A11E8271 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:05:56 -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 1VYJrX-0000qN-40; Mon, 21 Oct 2013 14:05:55 -0400
Date: Mon, 21 Oct 2013 14:05:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: Separate ADs roles from IESG - draft-klensin-stds-review-panel-00
Message-ID: <36EBC3490074344C3F1B746B@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20131020213751.0bc83de8@resistor.net>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@[192.168.1.128]> <6.2.5.6.2.20131020213751.0bc83de8@resistor.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.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 18:07:17 -0000

--On Monday, October 21, 2013 00:18 -0700 SM <sm@resistor.net>
wrote:

> Hi John,
> At 07:18 20-10-2013, John C Klensin wrote:
>> For an earlier and somewhat different take on this issue and a
>> variation on a proposal, see the long-expired
>> draft-klensin-stds-review-panel-00.
> 
> Some of the comments on the thread point to document review
> being less than a quarter the  time the Area Director spends
> weekly on the role.  draft-klensin-stds-review-panel-00 is a
> starting point to tackle the time commitment.

I want to stress that it is just a starting point, that it is
now very old, and that, if I were to write up a proposal today
(including after reflecting on the discussions of the last
several days), it would almost certainly be different.

So, while I appreciate your point-by-point analysis, I think
many of those things could be adjusted as needed to meet
community needs.    One of them is specifically the "yes" or
"no" part.  Today, I would expect the panel to justify a "no"
although less in terms of "change Y" (see my response to Joel)
and more in terms of "think more about this".   Either way, a
"no" returns the document to the responsible AD who could decide
(presumably with the advice and consent of the IESG and
consultation with the WG as appropriate) to kill the document,
hand it back to the WG, better document why it should be
approved and hand it back, or, in extreme cases, to kill or
reorganize the WG and/or decide to handle the document in some
other way.

best,
    john



From andy@yumaworks.com  Mon Oct 21 11:08:21 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 E797C11E8317 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.851
X-Spam-Level: 
X-Spam-Status: No, score=-2.851 tagged_above=-999 required=5 tests=[AWL=0.125,  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 wJOi8L02moiS for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:08:14 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id D09F411E8415 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:07:20 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n7so3033523qcx.13 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:07:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hPVaS5FkyiFtZVx9KHIVJ0ZEaWCQmW9W8l7YcAaCco0=; b=JD4sv5mv5W5xjwWpD8wnjovrKCM/uMy2djjTS85yZxkiWdXYsWogEFvCuND2QKcz6U OIqCd/H538JJGkIhPTMd+tg/B+QaZLGgknfQ7bX+E3x9MFY02AovCFKnRuIFtdDec+eA 3cErK+3YW5jPG03EXF6jPvwa2p+1HKbA2mRyHbXu9TqGim/p7cEWswJpbQhiRUh/WRps jYkHGOmezhoEzGZIvLGM4hve8ByofK350Jfyy620aJwIgLmIqz43iZnLNqVh0ze1x7T9 AmDPaUx9j/eKmQplwC0TFVnnYEV2hGsI4tf4QU1tR7srE9kQBYiRtfF2i+r20irdiJmz t+8Q==
X-Gm-Message-State: ALoCoQmvbBZq5MMfTGXDQuLF40xmGldLL008+DdOS1RY0h5usDxwI6YBsp+BZlEEoJAXR9RmdM9q
MIME-Version: 1.0
X-Received: by 10.49.96.225 with SMTP id dv1mr3951503qeb.89.1382378840218; Mon, 21 Oct 2013 11:07:20 -0700 (PDT)
Received: by 10.140.21.175 with HTTP; Mon, 21 Oct 2013 11:07:20 -0700 (PDT)
In-Reply-To: <52643500.3010406@joelhalpern.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu> <892B13B7BF164B38A8DB3793@192.168.1.128> <52643145.8010504@gmail.com> <52643500.3010406@joelhalpern.com>
Date: Mon, 21 Oct 2013 11:07:20 -0700
Message-ID: <CABCOCHRPwePDdJT2feSEZL5gJgdZfbrQA0US6C59-z7pDE9k2g@mail.gmail.com>
Subject: Re: Separate ADs roles from IESG
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=047d7bb04946b76f7204e94427bf
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 18:08:21 -0000

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

Hi Joel,

Delegating authority without responsibility is a bad idea.
The question of "does an AD have too much responsibility"
seems to be the underlying issue here.

It seems the main IESG areas of responsibility are:
   1) Steer the IETF (e.g, approve BoFs, WG charters)
   2) Manage all IETF working groups (e.g., deliver milestones)
   3) Review all drafts for RFC publication

Why not have Area Managers as well as Area Directors? (split out (2))
They would be responsible for getting WGs in the area
to complete their milestones on time. (e.g, they have WG conflict
resolution authority, not the ADs). The desired skill set focus for an AM
would be
management, not technology.


Andy


On Sun, Oct 20, 2013 at 12:54 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> The obvious risk if one separates WG management from review is that one
> could easily get the situation where the manager, in working with the WG,
> says that the document needs X, Y, and not Z.  And then the reviewer says
> "needs Z".  And there are more extreme versions of this.
> Currently, the ability for the managing AD to say "no, this won't pass
> muster" is part of his management tool.  If he is not the reviewer, he
> seems to have lost an important tool.  I hope I am missing something that
> would make this sort of approach workable.
>
> Yours,
> Joel
>
> On 10/20/13 3:38 PM, Brian E Carpenter wrote:
>
>> On 21/10/2013 03:18, John C Klensin wrote:
>> ...
>>
>>> Because working together with others on final document reviews
>>> and providing a final verification that all necessary bits are
>>> in place shouldn't require nearly the job-learning time that the
>>> IESG/AD role does, one could consider asking members of that
>>> review body to serve only a year or maybe six months, and
>>> possibly relax the meeting attendance requirements,
>>>
>>
>> I think we could totally remove attendance requirements. There
>> are cases where understanding a document requires background knowledge,
>> but if the document doesn't contain pointers to that knowledge, it's
>> a defect in the document, not in the reviewer. In fact, we can argue
>> that since the acid test for a document is whether a reader who has
>> zero IETF experience can understand it without ambiguity, at least
>> one reviewer should have limited background knowledge.
>>
>> I don't think a time limit is the critical issue - it's how many
>> documents a given reviewer has to review per year, or to be more
>> precise, how many pages. Clearly the burden in pages/year on a
>> conscientious AD at the moment is silly.
>>
>>  either of
>>> which should vastly increase the pool of plausible volunteers,
>>> including some people we would very much like to have in those
>>> jobs but who can't take on the IESG workload or long-term
>>> commitment.
>>>
>>> For an earlier and somewhat different take on this issue and a
>>> variation on a proposal, see the long-expired
>>> draft-klensin-stds-review-**panel-00.
>>>
>>
>> The high-order bit is whether we can separate the functions of
>> (a) steering the work of the IETF and (b) applying final quality
>> control to the documents. At the moment, these two jobs are bound
>> up with each other in the IESG.
>>
>>      Brian
>>
>>

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

<div dir=3D"ltr">Hi Joel,<div><br></div><div>Delegating authority without r=
esponsibility is a bad idea.</div><div>The question of &quot;does an AD hav=
e too much responsibility&quot;</div><div>seems to be the underlying issue =
here.</div>
<div><br></div><div>It seems the main IESG areas of responsibility are:</di=
v><div>=A0 =A01) Steer the IETF (e.g, approve BoFs, WG charters)</div><div>=
=A0 =A02) Manage all IETF working groups (e.g., deliver milestones)</div><d=
iv>=A0 =A03) Review all drafts for RFC publication</div>
<div><br><div class=3D"gmail_extra">Why not have Area Managers as well as A=
rea Directors? (split out (2))</div><div class=3D"gmail_extra">They would b=
e responsible for getting WGs in the area</div><div class=3D"gmail_extra">t=
o complete their milestones on time. (e.g, they have WG conflict</div>
<div class=3D"gmail_extra">resolution authority, not the ADs). The desired =
skill set focus for an AM would be</div><div class=3D"gmail_extra">manageme=
nt, not technology.</div><div class=3D"gmail_extra"><br></div><div class=3D=
"gmail_extra">
<br></div><div class=3D"gmail_extra">Andy</div><div class=3D"gmail_extra"><=
br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, =
Oct 20, 2013 at 12:54 PM, Joel M. Halpern <span dir=3D"ltr">&lt;<a href=3D"=
mailto:jmh@joelhalpern.com" target=3D"_blank">jmh@joelhalpern.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">The obvious risk if one separates WG managem=
ent from review is that one could easily get the situation where the manage=
r, in working with the WG, says that the document needs X, Y, and not Z. =
=A0And then the reviewer says &quot;needs Z&quot;. =A0And there are more ex=
treme versions of this.<br>

Currently, the ability for the managing AD to say &quot;no, this won&#39;t =
pass muster&quot; is part of his management tool. =A0If he is not the revie=
wer, he seems to have lost an important tool. =A0I hope I am missing someth=
ing that would make this sort of approach workable.<br>

<br>
Yours,<br>
Joel<br>
<br>
On 10/20/13 3:38 PM, Brian E Carpenter wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 21/10/2013 03:18, John C Klensin wrote:<br>
...<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Because working together with others on final document reviews<br>
and providing a final verification that all necessary bits are<br>
in place shouldn&#39;t require nearly the job-learning time that the<br>
IESG/AD role does, one could consider asking members of that<br>
review body to serve only a year or maybe six months, and<br>
possibly relax the meeting attendance requirements,<br>
</blockquote>
<br>
I think we could totally remove attendance requirements. There<br>
are cases where understanding a document requires background knowledge,<br>
but if the document doesn&#39;t contain pointers to that knowledge, it&#39;=
s<br>
a defect in the document, not in the reviewer. In fact, we can argue<br>
that since the acid test for a document is whether a reader who has<br>
zero IETF experience can understand it without ambiguity, at least<br>
one reviewer should have limited background knowledge.<br>
<br>
I don&#39;t think a time limit is the critical issue - it&#39;s how many<br=
>
documents a given reviewer has to review per year, or to be more<br>
precise, how many pages. Clearly the burden in pages/year on a<br>
conscientious AD at the moment is silly.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
either of<br>
which should vastly increase the pool of plausible volunteers,<br>
including some people we would very much like to have in those<br>
jobs but who can&#39;t take on the IESG workload or long-term<br>
commitment.<br>
<br>
For an earlier and somewhat different take on this issue and a<br>
variation on a proposal, see the long-expired<br>
draft-klensin-stds-review-<u></u>panel-00.<br>
</blockquote>
<br>
The high-order bit is whether we can separate the functions of<br>
(a) steering the work of the IETF and (b) applying final quality<br>
control to the documents. At the moment, these two jobs are bound<br>
up with each other in the IESG.<br>
<br>
=A0 =A0 =A0Brian<br>
<br>
</blockquote>
</blockquote></div><br></div></div></div>

--047d7bb04946b76f7204e94427bf--

From wes@mti-systems.com  Mon Oct 21 11:31:50 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD1B511E844E for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:31:50 -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 6G60oSrKJAaJ for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 11:31:44 -0700 (PDT)
Received: from atl4mhob05.myregisteredsite.com (atl4mhob05.myregisteredsite.com [209.17.115.43]) by ietfa.amsl.com (Postfix) with ESMTP id A036711E8441 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:31:44 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r9LIViIV000692 for <ietf@ietf.org>; Mon, 21 Oct 2013 14:31:44 -0400
Received: (qmail 17123 invoked by uid 0); 21 Oct 2013 18:31:44 -0000
X-TCPREMOTEIP: 107.48.102.144
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.48.102.144) by 0 with ESMTPA; 21 Oct 2013 18:31:43 -0000
Message-ID: <5265730B.9080208@mti-systems.com>
Date: Mon, 21 Oct 2013 14:31:39 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: dcrocker@bbiw.net, "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com> <526444E9.4050308@dcrocker.net>
In-Reply-To: <526444E9.4050308@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 18:31:50 -0000

On 10/20/2013 5:02 PM, Dave Crocker wrote:
> On 10/20/2013 3:54 PM, Joel M. Halpern wrote:
>> The obvious risk if one separates WG management from review is that one
>> could easily get the situation where the manager, in working with the
>> WG, says that the document needs X, Y, and not Z.  And then the reviewer
>> says "needs Z".  And there are more extreme versions of this.
>> Currently, the ability for the managing AD to say "no, this won't pass
>> muster" is part of his management tool.  If he is not the reviewer, he
>> seems to have lost an important tool.  I hope I am missing something
>> that would make this sort of approach workable.
> 
> 
> "Manager"?
> 
> Who's that?
> 
> ADs do not 'manage' working groups, and frankly neither do Chairs.
> 
> Yes, there's quite a lot of management activity done by both, but you've
> used the term manager in a way that reflects classic hierarchical
> authority models in typical organizations.
> 
> And that really isn't appropriate for the IETF, where we say that
> working group consensus rules working group decision-making and after
> that the IETF consensus rules.
> 
> The sort of thing you probably mean is that quality control processes
> outside the working group produce concerns and recommendations that run
> contrary to, or go beyond, what the working group has done.  That's
> fine, but that's not (necessarily) done by a "manager".  And in spite of
> giving ADs a unilateral authority to (temporarily) block progress, the
> resolution of concerns is a negotiation, not further unilateral
> decision-making by a higher-authority "manager".
> 
> The model that has ADs trying to be content experts, in addition to area
> facilitators, is exactly the underlying problem here.
> 


I'm not fond of the word "management" to describe the job either.  The
role is Area _Director_, not Area Manager, but I do think working
group management is a fine name for the task performed, as long as it's
understood to be in line with "We reject kings, presidents, ...".

The AD *facilitates* the working groups and BoFs by being able to
provide and shuffle resources (mailing lists, webex, meeting rooms,
etc), by trying to find and keep appropriate WG chairs, and by working
with them through chartering, re-chartering, and the later stages of
document publication.

The AD *directs* the area by being able to encourage or discourage
new work (via BoFs and rechartering), to send proposals towards
particular working groups, to end working groups when they cease to
be productive, and to ballot on work in other areas being proposed
in a charter or recharter.

To the question of splitting the document reviews from the working
group "management" tasks: When I was an AD, I found the document
reviews to be very useful in figuring out what was going on in other
areas that might be related to working groups in the area I was
responsible for, and in calibrating expectations for documents to
come out of my area's working groups.

If the document review and working group management roles were
split, I don't know how the AD doing working group management
would maintain broader awareness to avoid too much overlap or
conflict between WGs, or to know what the relevant things to
look for are in a MIB document, requirements document, etc. that
their WGs are producing, before sending them to IETF LC.  Certainly
they could find other ways to do this than reviewing every document
and sitting in the entire telechat though ...

-- 
Wes Eddy
MTI Systems

From brian.e.carpenter@gmail.com  Mon Oct 21 12:00:10 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 F1A8E11E8655 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:00:09 -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 A7mLebExc7qw for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:00:08 -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 8CBFC11E858D for <ietf@ietf.org>; Mon, 21 Oct 2013 11:58:17 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo15so6056008pbc.9 for <ietf@ietf.org>; Mon, 21 Oct 2013 11:58: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=ougsLCvCSYeOgj7Py4nNFBJHblLeD3+UO66jeA5SX2E=; b=gLUtKISXlJ0bJyreBAga/7jdpCmf32vUJ5KEU6hmdpAiAYdg6YPsTLSKLOkyiMh2VC 1V2DYGTZ69zktzl+c+K1OlQCwMgwY/scPNK6DTIvou1NKCkt5lXj7U7flm51O1RiU+RX f9nWDbt7Fhsvdsjll08bJrUcCHlMmP8k5eVLCB1CIsyJJeeIPEi0CniAaD7ELwJZA362 TI4HaDgyUZN1EFmAGJC10HMsl/G1J/kaeGRSBmrScK0NZtnLFjCBGwWOFZMk1mMu/QR7 ImHc1QNfhJ4mORjD7EIkhFZkerscjSu7bsG9TjEjl6sUEODfUu5jAmoBi1Y2uBrZnA5N 8nBw==
X-Received: by 10.68.196.197 with SMTP id io5mr1417907pbc.201.1382381888131; Mon, 21 Oct 2013 11:58:08 -0700 (PDT)
Received: from [192.168.178.20] (254.194.69.111.dynamic.snap.net.nz. [111.69.194.254]) by mx.google.com with ESMTPSA id go4sm22541278pbb.15.2013.10.21.11.58.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 11:58:06 -0700 (PDT)
Message-ID: <5265793F.1070207@gmail.com>
Date: Tue, 22 Oct 2013 07:58:07 +1300
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: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@192.168.1.128>	<52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com> <CABCOCHRPwePDdJT2feSEZL5gJgdZfbrQA0US6C59-z7pDE9k2g@mail.gmail.com>
In-Reply-To: <CABCOCHRPwePDdJT2feSEZL5gJgdZfbrQA0US6C59-z7pDE9k2g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 19:00:10 -0000

On 22/10/2013 07:07, Andy Bierman wrote:
> Hi Joel,
> 
> Delegating authority without responsibility is a bad idea.
> The question of "does an AD have too much responsibility"
> seems to be the underlying issue here.
> 
> It seems the main IESG areas of responsibility are:
>    1) Steer the IETF (e.g, approve BoFs, WG charters)
>    2) Manage all IETF working groups (e.g., deliver milestones)
>    3) Review all drafts for RFC publication
> 
> Why not have Area Managers as well as Area Directors? (split out (2))
> They would be responsible for getting WGs in the area
> to complete their milestones on time. (e.g, they have WG conflict
> resolution authority, not the ADs). The desired skill set focus for an AM
> would be
> management, not technology.

We mustn't forget that although ADs almost always attempt to steer
(or manage) by persuasion and reasoning, they do have two or three
ultimate weapons - the powers to replace WG chairs, to close WGs,
and to decline to advance a document. This is what makes it hard
to split 1) from 2), and makes it plausible to separate 3) from
1)+2), IMHO.

    Brian

From d3e3e3@gmail.com  Mon Oct 21 12:07:02 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 7DB8111E865C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:07:02 -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 yTuqaEqI-RDm for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:07:01 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CACF511E86E6 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:03:17 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id i18so2396642oag.20 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:03: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:from:date:message-id:subject:to :cc:content-type; bh=ngTTxdTgNBKNTX3cu5tsE4fkydDW6qEKkAu00MiET9g=; b=guFEiIp1qv9IzHZkgq6DPeFGKaUfY11IX6Xg/twx6gCgHhjHczp9an5jIjlQYEMesp E7/UK9o/sHV+UgrUj1gyXn2IvRTnIBt1FZeg53bXvwUi7/l5MLyQjU7Vlst0VTDo++9D cAeGwaEwnEwwW9hOA7UaB86YSeklrWSloBcLQU0VABWgI+72pEdp1WuHU4/dO+P8MPjm e3me+ZUwMNYLfArhWqtzOsm+Hz+V0K4hr3TTFsTViD5YUVifWm4L2lg3EMv+OUmD3bFa yvCGYdaIw6qhfJ2YSWP7nQ00tfy+BPqbxkXBFTgQGlaFaLpU2zjI9HRMdEtFVivr0rQT tqJA==
X-Received: by 10.182.44.167 with SMTP id f7mr21950574obm.3.1382382188397; Mon, 21 Oct 2013 12:03:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Mon, 21 Oct 2013 12:02:48 -0700 (PDT)
In-Reply-To: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 21 Oct 2013 15:02:48 -0400
Message-ID: <CAF4+nEHQ_pXS7t=Smf-9QGSj2whXNfYuK8f8FAEmRyhm9HpRCg@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
To: IETF Discussion <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: Mon, 21 Oct 2013 19:07:02 -0000

And we see below a perfect illustration of the difficulties that can
be caused by codification.

Three orthogonal points:

- We should be very careful to have only "guidelines" such that it is
clear any action based on those guidelines is only taken as a
judgement call by an authorized person or group and their is no
guarantee any action at all will be taken. Having "rules" or anything
that appears to guarantee enforcement and you may find people suing
you for failure to take immediate action when the infraction was the
most minor or arguable thing.

- I am very suspicious of the word "professional". Who knows what the
hell it means? Is the previous sentence "unprofessionally" worded? If
you think so, good. I typically see "unprofesional" used as a cudgel
against the strong expression of opinions the critic does not like
when they have no real counter argument to those opinions. Is the
April 1st RFC series something a professional group would do? I think
not. I don't know that a choice is necessary but I would prefer for
the IETF to call itself an "amateur" organization rather than a
"professional" organization.

- Generally, people should be allowed to comment causticly on others
actions but not on their motivations. If I say an action is
"obstructive" or whatever, well, that could be a matter of opinion but
at least in the open IETF process, people can see the action and might
or might not agree with me. If I say an action is "intended to be
obstructive", then, unless I am commenting on my own actions or the
actor has so stated, I am claiming the ability to mind-read...

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


On Mon, Oct 21, 2013 at 2:04 PM, Techno CAT <mars.techno.cat@gmail.com> wrote:
> "Calling someone a troll is an ad hominem. We aren't supposed to do that in
> the IETF. At least, not publicly."[1]
>
> "It is rude.
> It is bullying." [2]
>
> HARASSMENT by Brian E Carpenter has been noted for the Legal Record
>
> http://www.cs.auckland.ac.nz/~brian/
> "Network Geeks - How They Built the Internet"
>
> ===========================
>
> HARASSMENT by Stephane Bortzmeyer <bortzmeyer at nic.fr> has been noted for
> the Legal Record
> http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html
>
> ===========================
>
> http://www.ietf.org/mail-archive/web/ietf/current/msg83360.html
> "judgment needs to be applied by the ombudsperson & the rest of the IETF
> management
>
> [1] http://www.ietf.org/mail-archive/web/ietf/current/msg83364.html
> [2] http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html
>
> "you are encouraged to raise your concern in confidence with one of the
> Ombudspersons"
>
> http://www.intgovforum.org
> http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_201112_990.pdf
>
>
>
> On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>
>> Hi Jordi,
>>
>> We seem to have a new troll using the address mars.techno.cat@gmail.com
>>
>> Can you deal with it appropriately, please?
>>
>> Thanks
>>
>>     Brian
>>
>
>
>
> --
>
> @Techno_CAT_r
> http://Twitter.com/Techno_CAT_r

From brian.e.carpenter@gmail.com  Mon Oct 21 12:09:09 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 1672E11E86F9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:09:09 -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 H7glCPv3HQQS for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:09:08 -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 02C2111E8497 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:05:47 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id un1so876501pbc.5 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:05:47 -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=VWqymsco8Rvio3ifcBKzKyQTsNSK46O+VOywBKfTiZ0=; b=McqN5ePnBgMVOhG80ObIFGrwgcHLkohHtLqE+aIKqgRBcoaJ4vTjYjx/HjoLiETs87 RUIOLpLymkuEZX8i7Cbo3ffuCG0CJjr5l1z94Mo7Nx0QbBSeu+0QtYYY53e1wqGDxAOC XPo89WRgI/i5G3za/zdO4TxPdQKDbF1FnEtKSBlywogPQI3kCUvrOGppyuWKTc4ff/Po KwEV7gsp2T40SyNDfKjQgDQJkgPDJSlwDD3KnCrp0PfcTlHHFHmrXVq64L+43AfYdpyN ElM1Fu2LCi39c5EMGxKwpkUiWGxLnlJXjWrfB7FJ+a/t7F+EitXnh9LbBqYyQ5478qeN EVBw==
X-Received: by 10.66.242.17 with SMTP id wm17mr19726664pac.102.1382382346926;  Mon, 21 Oct 2013 12:05:46 -0700 (PDT)
Received: from [192.168.178.20] (254.194.69.111.dynamic.snap.net.nz. [111.69.194.254]) by mx.google.com with ESMTPSA id bt1sm22597748pbb.2.2013.10.21.12.05.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 12:05:46 -0700 (PDT)
Message-ID: <52657B0B.3080701@gmail.com>
Date: Tue, 22 Oct 2013 08:05:47 +1300
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: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
In-Reply-To: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.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: Mon, 21 Oct 2013 19:09:09 -0000

Personal opinion:

1. We shouldn't tolerate anonymous postings in any case.

2. ISOC salaries are utterly irrelevant to any IETF discussion.
It's just way out of line.

Beyond that, our sergeant at arms is responsible for judging
misuse of the list.

Regards
   Brian

From prvs=0999251037=johnl@iecc.com  Mon Oct 21 12:12:54 2013
Return-Path: <prvs=0999251037=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 DD2AF11E86BA for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:12:54 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNNcnctTlqQ0 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:12:48 -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 DC96A11E8249 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:11:54 -0700 (PDT)
Received: (qmail 67881 invoked from network); 21 Oct 2013 19:11:52 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 21 Oct 2013 19:11:52 -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=52657c78.xn--yuvv84g.k1310; i=johnl@user.iecc.com; bh=2coqbAKiyB5u5bfKN1AlYpKsIQ3XaKSYQn6l53+LFhE=; b=HDPRQkddAXCqCrj/0uyw6xZ39XPz56SUib56+RN+P5ehzxgr8cKePwAcKle3A21MU8zmMhkuPeLRReb7fhi6PiXrYDyeyIahPSg3pJHudrkjSk9dra49GOZotif6riygzMCIuXPZbgDvKMHVPCnq3uT6YH5QpOh7dmptePKoJE0edwRUr7t7aJ9+Ee+KhkQ9aB1yVt9V67rCLAt8C0bQpYx2gB5h57UqUu8/B3nIPsaaAODtdpTWqT1SUORjOLYo
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=52657c78.xn--yuvv84g.k1310; olt=johnl@user.iecc.com; bh=2coqbAKiyB5u5bfKN1AlYpKsIQ3XaKSYQn6l53+LFhE=; b=pKIWYPku7AjTHDj/YgEnadJtO+N0xOTkW23DYtnEuP42gSgLsiQX3hPolKVy79F+4GvdJp9SdVpxrHmTH7Bj7EdkaclXdTuvzpeAoi9suZrMKx+p37yt13qRWYsdzdXMLv5/uh3woQ4zRNiSYmFWbIL9ZRQD5Ts5FHI9MaiCTufE4IetcIcvzPU+hY6wNmsd8fFknsyHvg3mOV5509/RiPkgBkwqf16GjfZ4sEmSI5Ex1xeJ1h45WycGK+iFivyv
Date: 21 Oct 2013 19:11:30 -0000
Message-ID: <20131021191130.11652.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [IETF] Re: Proposed IETF Anti-Harassment Policy
In-Reply-To: <52654B65.3000006@gmail.com>
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: Mon, 21 Oct 2013 19:12:55 -0000

>You kick the problem over to your (trained) ombudsman.

I have had some experience with ICANN's trained ombudsman.  To put it
mildly, he was not part of the solution.

While I certainly agree that harassment is bad, in the IETF where
nobody is in charge and authority, such as it is, flows from the
bottom up, it is surprisingly hard to create definitions that capture
the behavior we want to stop, without also enabling endless whining
and nitpickery by people with what I might call an outsized sense of
entitlement and a lot of free time.

This isn't saying to give up, but it is saying to think carefully
about the scenarios, particularly ones involving people with no
interest in playing fair.

R's,
John



From dhc@dcrocker.net  Mon Oct 21 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 1A59C11E86F7 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:14:05 -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 E4bM4uh2p-kJ for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:13:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 47AD911E86CE for <ietf@ietf.org>; Mon, 21 Oct 2013 12:13:02 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9LJCws1024901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 21 Oct 2013 12:13:01 -0700
Message-ID: <52657CB4.9070007@dcrocker.net>
Date: Mon, 21 Oct 2013 15:12:52 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: IETF Discuss <ietf@ietf.org>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@192.168.1.128>	<52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com>	<CABCOCHRPwePDdJT2feSEZL5gJgdZfbrQA0US6C59-z7pDE9k2g@mail.gmail.com> <5265793F.1070207@gmail.com>
In-Reply-To: <5265793F.1070207@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, 21 Oct 2013 12:13:02 -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, 21 Oct 2013 19:14:05 -0000

On 10/21/2013 2:58 PM, Brian E Carpenter wrote:
> We mustn't forget that although ADs almost always attempt to steer
> (or manage) by persuasion and reasoning, they do have two or three
> ultimate weapons - the powers to replace WG chairs, to close WGs,
> and to decline to advance a document. This is what makes it hard
> to split 1) from 2), and makes it plausible to separate 3) from
> 1)+2), IMHO.


Offlist, Joel reminded me of these points, which do formally qualify as 
attributes of 'managers'.  Still I think we should stop using terms like 
manager and director, because they invoke the wrong organizational tone, 
which I believe counters the underlying nature of the IETF.

That is, terms like manager or director invoke a model of daily 
hierarchical authority that does not match IETF reality.  Worse, it 
encourages ADs to think of themselves as having and being authorities, 
rather than facilitators.

Area Directors actually do not 'direct' the work in the area.  They 
almost never initiate it.  They almost never define it.  They almost 
never directly contribute to its substance.  Rather, they facilitate 
grass-root processes to integrate it into the IETF and monitor its 
progress.

The "management" functions that are classic are hiring and firing 
chairs, refining charters, and prodding chairs to make wg progress. 
That's all real, and one can cite them to justify the terms.

But this fact misses the day-to-day reality of the IETF which is a bunch 
of grass-roots volunteers who combine to solve a problem that they, the 
grass roots folk, want solved.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Mon Oct 21 12:23:30 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 6928B11E848A for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.547
X-Spam-Level: 
X-Spam-Status: No, score=-103.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 7xhTSNsNWt9C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:23:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DCF9311E85D7 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:23:20 -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 1VYL4S-0000y1-Ch; Mon, 21 Oct 2013 15:23:20 -0400
Date: Mon, 21 Oct 2013 15:23:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [IETF] [IETF] Re: Proposed IETF Anti-Harassment Policy
Message-ID: <EC6D3692A20080D1777654D5@JcK-HP8200.jck.com>
In-Reply-To: <DC707EB6-9856-4911-9B5F-C98665213F92@piuha.net>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net> <52654B65.3000006@gmail.com> <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net> <20131021160723.GA11390@gsp.org> <DC707EB6-9856-4911-9B5F-C98665213F92@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.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 19:23:30 -0000

--On Tuesday, October 22, 2013 00:32 +0800 Jari Arkko
<jari.arkko@piuha.net> wrote:

> Thanks for the excellent feedback so far.

Let me first add to the other comments that I think the draft is
an entirely reasonably first cut.
> 
> I wanted to point out one thing in the continuing discussion.
> Despite the best intentions and us being engineers and all, it
> may not actually be possible to write a full spec that
> accurately defines what is and what is not harassing
> behaviour. E.g. photography. I think Don had it right in the
> case that he described, but it would have been hard to write
> that down before even hearing about such a case.

Similar comments would apply to the mini-tempest about
photographing the in-room participants at a WG meeting to record
those who had (or had not) volunteered for a particular task.
We need to be clear that things, including photography and other
image-recording methods, can be privacy issues without being
harassment and vice versa.  Keeping them separated may be hard,
but it will be necessary.
 
> Hence judgment needs to be applied by the ombudsperson & the
> rest of the IETF management.

Yep.   And they should expect whatever judgments they make to be
very unpopular with someone.

Two additional observations:

(1) These kinds of policies are going to run into some of the
same issues as our IPR policies.  In particular, if someone
really has bad intentions (as distinct from being careless,
indifferent, accidentally ignorant or stupid), we could be
headed into another rat hole about who the policies actually
apply to and whether particular individuals have agreed to them.
It is my understanding that a voluntary organization's trying to
enforce a policy that may involve career-damaging punishments on
people who can't be demonstrated to have agreed to it can get
very messy.

So, like others, I would encourage having Counsel take a careful
look, both at the policy and at the potential interactions
between it and our "no membership" policies.

(2) With the understanding that this is a purely hypothetical
problem, any policy of this type also provides the opportunity
for spurious claims and other sorts of DoS attacks.  Equally
important, it provides the opportunity for some entity to claim
externally that the IETF or some of its participants harassed it
in violation of the policy, did nothing about it, and therefore
that our standards should be ignored and the organization
punished.  Those sorts of threats are certainly not a reason to
avoid establishing policies of this sort, but we should be aware
of possible misuses.  It is probably also useful to think, not
only about what measures can be imposed if bad behavior doesn't
stop, but also about how to ensure that someone complaining has
skin in the game.   In particular, it would be really
unattractive to have a harassment complaint brought against
figures in the IETF for repeatedly saying something unpleasant
about, e.g., a government that was restricting access to the
Internet.

best,
   john




From melinda.shore@gmail.com  Mon Oct 21 12:30:34 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 11EBA11E8242 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:30: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=[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 AA3RZE0y2GaC for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:30:33 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CB80811E8267 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:30:32 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id lf10so5096746pab.20 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:30: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AxN7kaJAPkQ+5MvRjV/VMJqb2jv0Egg4hKe2fZ+zyWk=; b=oD53RP5inTN0MxT9tTK2+GdgAwu2svwAkTyTskxnpAzPnriPCesu+NUWF0XOjkbvBA Y3FPmwWoaWLuFG+weVS+a6DNIScN58jThX5pvGixpGUoRdNKaOB26qAQFTzbvnJ4/ERa mgaBpHG6ID6jNmUm+g5QorQ6LkpucGYyTv+t0gVtR47nweVJUFxkvhzwuQbecfjU7bbq G72SdKwwv5VS3xFd+R4Ox4LY2dm1Elq70hEPruaeCcHFi00oiMi9fOT3IgJFz+qsDabD 6Tq51j+mjBCmrrkzfXovtFFxblHyBwGCXK9edJYURA2pzREGXCkhCPlPgLSWG0ew1n0i Xi8g==
X-Received: by 10.66.155.102 with SMTP id vv6mr19708284pab.89.1382383832335; Mon, 21 Oct 2013 12:30:32 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id xv2sm22609516pbb.39.2013.10.21.12.30.30 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 12:30:31 -0700 (PDT)
Message-ID: <526580D4.1050606@gmail.com>
Date: Mon, 21 Oct 2013 11:30:28 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] [IETF] Re: Proposed IETF Anti-Harassment Policy
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <CAPv4CP-gzO_dyEjzpdTC+hJMuYU36LnUWV3zdCKECqkfdAJZpg@mail.gmail.com> <B9361315-EEE3-4375-AA69-DE83D24F48A3@kumari.net> <52654B65.3000006@gmail.com> <35C37EC6-7D69-4700-A56F-69BFE4E6E055@kumari.net> <20131021160723.GA11390@gsp.org> <DC707EB6-9856-4911-9B5F-C98665213F92@piuha.net> <EC6D3692A20080D1777654D5@JcK-HP8200.jck.com>
In-Reply-To: <EC6D3692A20080D1777654D5@JcK-HP8200.jck.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, 21 Oct 2013 19:30:34 -0000

On 10/21/13 11:23 AM, John C Klensin wrote:
> (2) With the understanding that this is a purely hypothetical
> problem, any policy of this type also provides the opportunity
> for spurious claims and other sorts of DoS attacks.  Equally
> important, it provides the opportunity for some entity to claim
> externally that the IETF or some of its participants harassed it
> in violation of the policy, did nothing about it, and therefore
> that our standards should be ignored and the organization
> punished.  Those sorts of threats are certainly not a reason to
> avoid establishing policies of this sort, but we should be aware
> of possible misuses.

Absolutely, and ultimately I think that some personal
judgment on the part of *somebody* will need to be applied
should there be complaints filed.  That's not a bad
thing.

I do think that it's worth pointing out that in other
environments where organizations have taken the step of
creating and enforcing an anti-harassment policy it's
worked out well (for example, PyCon).  It's reduced the
incidence of problems *and* created an environment where
women feel both more comfortable and more welcome.
Contrast it with DefCon and it looks like a win.

Melinda


From brian.e.carpenter@gmail.com  Mon Oct 21 12:34:08 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 B96BC11E86EC for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 TKSKQRae+PxD for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:34:08 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 07D7711E86EA for <ietf@ietf.org>; Mon, 21 Oct 2013 12:34:01 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id y10so5089776pdj.10 for <ietf@ietf.org>; Mon, 21 Oct 2013 12:33:54 -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=b6VDke2qXKzIWzKN1klnqIfubT5QbOm4sRwElDoco+c=; b=KKflelHyvXJDnUQZO3FCxCssMytS756VjAYhzPAvtjvhbSyqKPRpkQtY6s0re3x7Vw p7EyavflSuckzbOYz2sxWu9koM374UgBzJm0g3BFfwYbTYW7Z0ZYI8avqW0QZprnRC7g SSFnXJjulECZzO4pZ8CY1+jLfqHjHRn8zGaAXVgHA0akherCpbsgzfHBqQ/9X4VKCGh3 OHgb7p8FFqCTnEbd46cHHeNPswk+xWxwJmmp5uPUPL2zH9fczCvVGcFzjAVfincmmMqa A0sshtndylGYNVynhe75zud5Y46oOkJeIhlFBBQ4aCYa20sW0naJvU4wDwOukHESOzOz j9/g==
X-Received: by 10.68.109.195 with SMTP id hu3mr8352365pbb.123.1382384034281; Mon, 21 Oct 2013 12:33:54 -0700 (PDT)
Received: from [192.168.178.20] (254.194.69.111.dynamic.snap.net.nz. [111.69.194.254]) by mx.google.com with ESMTPSA id xe9sm27768495pab.0.2013.10.21.12.33.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 12:33:53 -0700 (PDT)
Message-ID: <526581A1.7010100@gmail.com>
Date: Tue, 22 Oct 2013 08:33:53 +1300
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: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net>	<20131021133009.GA27979@nic.fr> <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu>
In-Reply-To: <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 19:34:08 -0000

On 22/10/2013 05:39, Lixia Zhang wrote:
> On Oct 21, 2013, at 6:30 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
>> On Mon, Oct 21, 2013 at 09:08:43AM -0400,
>> Dave Crocker <dhc@dcrocker.net> wrote 
>> a message of 27 lines which said:
>>
>>> He invented the datagram...
>> Some people say it is Leonard Kleinrock. I welcome any precise
>> references on the history of the datagram, specially if they are
>> accessible online (whuich is rare for scientific papers of this
>> time).
> 
> Pouzin might have coined the word "datagram" in an early 70's paper (memory is vague now), but it seems that the concept of datagram is already in Paul Baran's seminal paper published in IEEE Trans. on Communications (March 1964).
> And yes it is online (credit to David Goldberg who scanned the paper):
>     http://www.cs.ucla.edu/classes/cs217/Baran64.pdf
> (read pages 6 & 7)

Yes, and all that was in his RAND Corp. reports published in 1962.
Donald Davies gave him credit, too. Kleinrock, as far as I know, worked
on how queueing theory applies to packet networks - and that was
important too.

More to the point, we did try the "submission via national standards
bodies" approach. I believe it was called OSI.

   Brian

From prvs=10065ae11f=jordi.palet@consulintel.es  Mon Oct 21 12:50:27 2013
Return-Path: <prvs=10065ae11f=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB1211E8429 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.669
X-Spam-Level: 
X-Spam-Status: No, score=-105.669 tagged_above=-999 required=5 tests=[AWL=0.929, 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 kAIDmIo-tLZ2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 12:50:21 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id CBBCA11E826D for <ietf@ietf.org>; Mon, 21 Oct 2013 12:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1382384740; x=1382989540; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=QmXbr0yot8qGdvXdVS53g1cFf T+TE1vus3WR00NA6e8=; b=r7HHlqO66Fhxf2HnNTz3MAaFlgDDQMVi4jUCkoCCx Y+1FTqLB7vcIHIpaDx9knA3eodnFQ0FZS3Xk3HZfuVVJ4vZSV8LbAGZYGVR5kSWy KoQ4zaQATg0PQ9Fv3P4Ci51vxIF4r5EeAw3wLu+32ZivrLVWdImWeoPbTyLsQhdu rM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=NnRhzOjRcVJZf7osFKWnWDt7Ehqog4v9w4LHJGIfst8aNC3gVt4wxWYTa7Yh iWbbWfbGYCfZ3FrJsEGzJD7DVwOPjOvIzbeuLhH8iczG+EFL4P6YLw9nm QYTm+yKm7D9D6MPvn/Ah6fglAX/CoSrzRKGBs2blNdQu2MzBlAPH7A=;
X-MDAV-Processed: consulintel.es, Mon, 21 Oct 2013 21:45:40 +0200
Received: from [10.10.10.102] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004494843.msg for <ietf@ietf.org>; Mon, 21 Oct 2013 21:45:40 +0200
X-Spam-Processed: consulintel.es, Mon, 21 Oct 2013 21:45:40 +0200 (not processed: message from trusted or authenticated source)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:131021:md50004494843::VZVzixM1urEEOHoR:000046+z
X-MDRemoteIP: 87.216.40.21
X-Return-Path: prvs=10065ae11f=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Date: Mon, 21 Oct 2013 21:45:06 +0200
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <mars.techno.cat@gmail.com>, IETF Secretariat <ietf-secretariat@ietf.org>
Message-ID: <CE8B4F40.B9893%jordi.palet@consulintel.es>
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 19:50:27 -0000

Hi,

As Sergeant-at-arms, I agree with other previous postings and believe that
anonymous posting is not tolerable in the IETF mail exploders. Moreover, I
also believe that this the content of your emails are off-topic to the
IETF, even ISOC is the IETF umbrella, ISOC tax declaration and other
details is irrelevant to this list as well.

This is the reason why I've yesterday, instructed the secretariat to avoid
further postings from you.

If you decide to identify yourself, as the rest of the posters, and be
on-topic, you will be allowed to post again.

Meanwhile, refrain to use other anonymous emails, as the secretariat will
automatically keep banning you.

Regards,
Jordi






-----Mensaje original-----
De: Techno CAT <mars.techno.cat@gmail.com>
Responder a: <mars.techno.cat@gmail.com>
Fecha: lunes, 21 de octubre de 2013 20:04
Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Jordi Palet Martinez <jordi.palet@consulintel.es>, <ietf@ietf.org>,
<bortzmeyer@nic.fr>, Jari Arkko <jari.arkko@piuha.net>
Asunto: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

>"Calling someone a troll is an ad hominem.  We aren't supposed to do that
>in the IETF.  At least, not publicly."[1]
>
>"It is rude. 
>It is bullying." [2]
>
>HARASSMENT by Brian E Carpenter has been noted for the Legal Record
>
>http://www.cs.auckland.ac.nz/~brian/
>"Network Geeks - How They Built the Internet"
>
>===========================
>
>
>HARASSMENT by Stephane Bortzmeyer <bortzmeyer at nic.fr
><mailto:bortzmeyer@DOMAIN.HIDDEN>> has been noted for the Legal Record
>http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html
>
>===========================
>
>http://www.ietf.org/mail-archive/web/ietf/current/msg83360.html
>"judgment needs to be applied by the ombudsperson & the rest of the IETF
>management
>
>[1] http://www.ietf.org/mail-archive/web/ietf/current/msg83364.html
>[2] http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html
>
>"you are encouraged to raise your concern in confidence with one of the
>Ombudspersons"
>http://www.intgovforum.org
>http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_2
>01112_990.pdf
>
>
>
>
>On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter
><brian.e.carpenter@gmail.com> wrote:
>
>Hi Jordi,
>
>We seem to have a new troll using the address mars.techno.cat@gmail.com
>
>Can you deal with it appropriately, please?
>
>Thanks
>
>    Brian
>
>
>
>
>
>
>
>-- 
>
>@Techno_CAT_r
>http://Twitter.com/Techno_CAT_r
>
>



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From derhoermi@gmx.net  Mon Oct 21 13:12:57 2013
Return-Path: <derhoermi@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 3D3A511E86EB for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.38
X-Spam-Level: 
X-Spam-Status: No, score=-2.38 tagged_above=-999 required=5 tests=[AWL=0.219,  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 Gl5wq0aey++p for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:12:52 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 288AF11E86FF for <ietf@ietf.org>; Mon, 21 Oct 2013 13:12:43 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.27.33]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0MPlMc-1VdJeN1ddC-00506e for <ietf@ietf.org>; Mon, 21 Oct 2013 22:12:41 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Proposed IETF Anti-Harassment Policy
Date: Mon, 21 Oct 2013 22:12:41 +0200
Message-ID: <qmva691t1norfnoaeimb8ft00t2gqr1m47@hive.bjoern.hoehrmann.de>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:wufn2kHjOaJL2H7iRHQ/9gMHwX8z1KkSM1K7z11/4sLINsGiTLb AWqoodRdOdsC3GXbhBeVEuVQmZde4+Aaw9qL9sBot2an0eiVkYyiwMgNkcGciZKY+YRjORa ZlZUl9EyVt48T/Rzx1FxP7igSZbI/yMJmw9YoJOGYOwFOSGqnXX12FR2cavjQ7oOPdXeJdd cB5B8GrU+RPr59hCiE9fA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 20:12:57 -0000

* IETF Chair wrote:
>IETF Anti-Harassment Policy

So, someone who is being disciplined under this policy might want to
check it out to see how they might appeal such action, or how they can
ensure their continued access to the Standards process, or they might
simply want to make sure they are being treated fairly and within the
bounds of standard procedure. The policy contains nothing to that
effect.

A chair might find themself in a situation where they have to deal with
harassment and check out the policy to see how they should deal with it,
whether they should handle the matter on their own, or if they should
refer it to an ombudsperson, or whatever. The policy notes the existing
power granted to chairs, but then just says harassment "warrants special
attention" without elaborating.

An ombudsperson might refer to the policy to see how they can deal with 
harassment problems, or they might want to refer others to it, e.g. to
make others aware of their discretion and power, or when taking action
against someone, inform them of their rights to defend against actions
they find inappropriate. The policy just says "appropriate action will
be taken".

Instead, the policy goes to excessive lengths telling people they should
maintain behavioral norms. I think it is appropriate in such a policy to
establish some context, but going at it for too long makes it seem as if
something extraordinary is being asked of participants, as if it said
"Unlike other organisations, the IETF strives to create and maintain..."

I think the prelude should be shortened to be bare minimum, and instead
text of the nature discussed above should be added; possibly by way of
external references, e.g. if an RFC concerning the rights and responsi-
bilities of IETF ombudspersons is forthcoming, a reference to that would
address some concerns. I believe this can be done in few sentences.

>Harassment is unwelcome hostile or intimidating behavior, in particular speech
>and behavior that is sexually aggressive or intimidates based on attributes like
>race, gender, religion, age, color, national origin, ancestry, disability,
>sexual orientation, or gender identity. Harassment of this sort will not be
>tolerated in the IETF. Harassment includes the use of offensive language or
>sexual imagery in public presentations and displays, degrading verbal comments,
>deliberate intimidation, stalking, harassing photography or recording,
>inappropriate physical contact, and unwelcome sexual attention.

I strongly object to listing "sexual imagery" here unless accompanied by
a much longer list that includes violent imagery, imagery of aggressive
or otherwise dangerous animals, death, illness, medical imagery, and
whatever else people might find intimidating, say Fort Meade engulfed in
lightning in a violent thunderstorm and the eye of Sauron montaged on
top of it.

I think "use of offensive language" should not be considered harassment
without linking it to purpose, intent, and other limiting factors. It is
common that people use language considered offensive by some unknowingly
e.g. due to cultural differences, limited language skills, or youth. The
beginning of this paragraph can also easily be read to suggest that mere
"unwelcome hostile speech" falls under the definition without additional
qualifiers.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From sm@resistor.net  Mon Oct 21 13:22:16 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 5EF0C11E84EC for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 U3VstQEKKdQS for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:22:13 -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 4469111E81FF for <ietf@ietf.org>; Mon, 21 Oct 2013 13:22:13 -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 r9LKM2mt010068; Mon, 21 Oct 2013 13:22:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382386927; bh=GgaD1/pjE0KfdO3mUbx11Ys//gdecrMTIg8l5Ua6Sr4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gCAAYzNlW7WPJk32xyAS1LpmIkdP9ih5l4mJYlpsIcv03RyfGG4F5ItDaROHqWiKq /9xlbpPPOPCmPvn45x2LCjliT79TXECB/Zv/jneN5lPAp5dZJf2P/OSF2+hnN66Dtu ksCc6pCS8jjVpDq0P3KLlZ0RWg3naDJGjt65H4nI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382386927; i=@resistor.net; bh=GgaD1/pjE0KfdO3mUbx11Ys//gdecrMTIg8l5Ua6Sr4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VuVHMtUZqeueOVkWewwAO3M8b0iubiM1VmBpIIJ7eb4cmo4n8UlfcRYhrCSzvXFP+ Zk1Vpf5RIWWpZMxuEZRBH499UqDWdy1ZkgICClo8OEeSqYnhv2kS7sT71BgptlDYrO D8uy3q31dTmKEbOa6WvZAXmeaKFCccov1IuT9IHw=
Message-Id: <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Oct 2013 13:18:07 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Anonymous postings
In-Reply-To: <52657B0B.3080701@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@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: Mon, 21 Oct 2013 20:22:16 -0000

At 12:05 21-10-2013, Brian E Carpenter wrote:
>1. We shouldn't tolerate anonymous postings in any case.

There is a thread at 
http://www.ietf.org/mail-archive/web/dane/current/msg05855.html and 
one at http://www.ietf.org/mail-archive/web/ietf/current/msg81133.html

It is better to focus on the content instead of the messenger.

Regards,
-sm 


From ietf-secretariat@ietf.org  Mon Oct 21 13:27:41 2013
Return-Path: <ietf-secretariat@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 D2B7B11E842D; Mon, 21 Oct 2013 13:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.914
X-Spam-Level: 
X-Spam-Status: No, score=-103.914 tagged_above=-999 required=5 tests=[AWL=-1.314, 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 XECI-xD8qZ8b; Mon, 21 Oct 2013 13:27:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DEE11E8285; Mon, 21 Oct 2013 13:27:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Internet Draft Submission Cut-Off Today
X-Test-IDTracker: no
X-IETF-IDTracker: 4.80.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131021202741.32574.28307.idtracker@ietfa.amsl.com>
Date: Mon, 21 Oct 2013 13:27:41 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: internet-drafts@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, 21 Oct 2013 20:27:42 -0000

This is a reminder that the Internet Draft Submission cut-off is today, Mon=
day, October 21, 2013. =


All submissions are due by UTC 24:00.

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/submit/

The Internet-Draft cutoff dates as well as other significant dates for IETF=
 88 can be found at: =

https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF88

Thank you for your understanding and cooperation. If you have any  question=
s or concerns, then please send a message to internet-drafts@ietf.org.

From martin.vigoureux@alcatel-lucent.com  Mon Oct 21 13:41:12 2013
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0108011E8438 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.408
X-Spam-Level: 
X-Spam-Status: No, score=-110.408 tagged_above=-999 required=5 tests=[AWL=0.191, 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 hK-GQocnM0L2 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:40:58 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 54FF411E8214 for <ietf@ietf.org>; Mon, 21 Oct 2013 13:40:58 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r9LKetFa012568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Mon, 21 Oct 2013 15:40:57 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r9LKetgg029657 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Mon, 21 Oct 2013 22:40:55 +0200
Received: from [135.244.192.104] (135.239.27.40) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 21 Oct 2013 22:40:55 +0200
Message-ID: <52659156.2080204@alcatel-lucent.com>
Date: Mon, 21 Oct 2013 22:40:54 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr><CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@[10.0.1.3]> <392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [135.239.27.40]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Oct 2013 20:41:13 -0000

Michel

Le 21/10/2013 19:25, Michel Py a écrit :
>> John Day wrote:
>> How often do you see two non-English speakers conversing
>> in English because it is the only common denominator?
>
> All the time, and that is especially true in France; the only way to do
> business across Europe is English; no one speaks all of French, Spanish,
> Portuguese, Italian, German, Dutch, Danish, Swedish, Norwegian, Russian,
> Polish, Romanian, Greek and yes English. The de-facto situation is that
> almost everyone who steps outside their little part of the world speaks
> their native language and English.
>
> But too many French are entrenched in an anti-American culture that
> refuses to learn English.

Could you elaborate on how much is "too many"?

Merci

-m


From mansaxel@besserwisser.org  Mon Oct 21 13:50:09 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 A507411E824F for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:50:09 -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 EVD9LJd--umW for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 13:50:09 -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 8345211E823F for <ietf@ietf.org>; Mon, 21 Oct 2013 13:50:08 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id DE2D09EA5; Mon, 21 Oct 2013 22:50:01 +0200 (CEST)
Date: Mon, 21 Oct 2013 22:50:01 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131021205001.GI2783@besserwisser.org>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <52654DEF.7050200@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BWWlCdgt6QLN7tv3"
Content-Disposition: inline
In-Reply-To: <52654DEF.7050200@gmx.net>
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: 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, 21 Oct 2013 20:50:09 -0000

--BWWlCdgt6QLN7tv3
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Internet standardisation remains unilateral Date: Mon, Oct 21,=
 2013 at 05:53:19PM +0200 Quoting Hannes Tschofenig (hannes.tschofenig@gmx.=
net):
> On 10/21/2013 04:34 PM, Jorge Amodio wrote:
> >Halald Alvestrand (which btw is from Norway not the USA)
>=20
> This illustrates part of the problem.
>=20
> It depends on the type of argument you want to make and then you
> count people different. You count Harald as someone who comes from
> Norway. The author of the slide deck wanted to make a different
> argument and so he sees Harald as a person working for Google, as
> US-based company.

I know Harald. He is from Norway. There is nothing more to say than that.=
=20

( Jorge, your post was excellent! )=20
=20
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Okay ... I'm going home to write the "I HATE RUBIK's CUBE HANDBOOK FOR
DEAD CAT LOVERS" ...

--BWWlCdgt6QLN7tv3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlJlk3kACgkQ02/pMZDM1cUiswCePBIvljh8V0Zlskzw12se5Xl4
GS0An15+77x3RwTvRbs4lldyjB1aMd03
=5ZgQ
-----END PGP SIGNATURE-----

--BWWlCdgt6QLN7tv3--

From l.wood@surrey.ac.uk  Mon Oct 21 14:43:45 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 7C24011E85BA for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 14:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.935
X-Spam-Level: 
X-Spam-Status: No, score=-3.935 tagged_above=-999 required=5 tests=[AWL=-0.337, 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 SDLfsTfu+Vy3 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 14:43:37 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id 8284D11E8706 for <ietf@ietf.org>; Mon, 21 Oct 2013 14:42:29 -0700 (PDT)
Received: from [85.158.136.51:61803] by server-17.bemta-5.messagelabs.com id A6/5C-17059-4CF95625; Mon, 21 Oct 2013 21:42:28 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-49.messagelabs.com!1382391747!23256801!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14305 invoked from network); 21 Oct 2013 21:42:28 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 21 Oct 2013 21:42:28 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.216]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 21 Oct 2013 22:42:27 +0100
From: <l.wood@surrey.ac.uk>
To: <sm@resistor.net>, <brian.e.carpenter@gmail.com>
Date: Mon, 21 Oct 2013 22:37:51 +0100
Subject: RE: Anonymous postings
Thread-Topic: Anonymous postings
Thread-Index: Ac7Om2fqK5ZWZyPORKeEglAcbsIBmwACmNZy
Message-ID: <290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surrey.ac.uk>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com>, <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net>
In-Reply-To: <6.2.5.6.2.20131021130523.0c4a6db8@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: Mon, 21 Oct 2013 21:43:46 -0000

You say that, "Brian". You respond, "SM".

A persistent identifier is helpful in sustained shared multiparty conversat=
ion; whether it represents a "real" person or not does not matter.

And who are "we"?

"L."


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of SM [sm@res=
istor.net]
Sent: 21 October 2013 21:18
To: Brian E Carpenter
Cc: ietf@ietf.org
Subject: Anonymous postings

At 12:05 21-10-2013, Brian E Carpenter wrote:
>1. We shouldn't tolerate anonymous postings in any case.

There is a thread at
http://www.ietf.org/mail-archive/web/dane/current/msg05855.html and
one at http://www.ietf.org/mail-archive/web/ietf/current/msg81133.html

It is better to focus on the content instead of the messenger.

Regards,
-sm


From melinda.shore@gmail.com  Mon Oct 21 14:57:54 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 41E6821F9B28 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 14:57: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=[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 6c8GAxXKyyTr for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 14:57:53 -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 36FF811E862E for <ietf@ietf.org>; Mon, 21 Oct 2013 14:57:35 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so7603922pbc.21 for <ietf@ietf.org>; Mon, 21 Oct 2013 14:57:33 -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=PKcezlAH6hs82sNDqYyeVWYWQTcifAdWYMFqcLUtvvA=; b=yOsCEVUvr0oRpCORk3N4BpywoOiTqjItXdb7JGR1f6JaxFq+sPlBdjf+v1YmTaRjzM GKUMDfluyeQlJwAtPh6sek6ygXyq+nP6K2/hfNc7zGyqhL8tJwAGIJycLgHqXDw4cDDS wHH9mmbKX8+tWr9Sulf9Jrf2E3CJaxPfRvHblhof69NHRou9+6qPb7VgOYoQ/6NomQMI pdJiHE8eOtfsbzZk0RIfCqd1wzfCc7L6A1ycA6hNxpslT4k/79BKJKEcVaknSgbWBaZJ /RI+Bn2mXzBKyY9T/D+UG9Go9059mBZrW8QuBeS36v35uinNKVY/5WwWTf0Ni7d4u4aw V/rQ==
X-Received: by 10.67.22.67 with SMTP id hq3mr4947240pad.132.1382392653054; Mon, 21 Oct 2013 14:57:33 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id gg10sm23044409pbc.46.2013.10.21.14.57.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 14:57:32 -0700 (PDT)
Message-ID: <5265A349.6090902@gmail.com>
Date: Mon, 21 Oct 2013 13:57:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Anonymous postings
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com>, <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net> <290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surrey.ac.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, 21 Oct 2013 21:57:54 -0000

On 10/21/13 1:37 PM, l.wood@surrey.ac.uk wrote:
> A persistent identifier is helpful in sustained shared multiparty
> conversation; whether it represents a "real" person or not does not
> matter.

Right, this is clearly a problem as stated, but there's a long
history of people posting from and participating from those
addresses, while the other is some individual whose only posts
were ad hominem.  So what's of interest here probably isn't
anon-/pseudonymity, but some sort of reputation or track record.

Melinda

From hallam@gmail.com  Mon Oct 21 17:27:53 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 6273411E82B9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:27:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 U3g5rrd7zkEq for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:27:52 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4920911E80DE for <ietf@ietf.org>; Mon, 21 Oct 2013 17:27:44 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id o14so1972914lbi.0 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:27: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=jGvchiaJ/VAfmHW4LGa4oy8WNUy3/vmpfTDm9Eg5DSU=; b=IfqWhRxA0q9RTeA68z+3ErGknhK3vSkk62WuxckbkHdSpvAXP8NBMuy/DnInDJRCKv i2SZAYV6MpFJY27pTOFOiE53j2Dy5bYm2dQ4HopIh/AWa/SxVt5fFAcYkSPX/82RbJJ0 08SqzEw2VkoFyyTvu0oAQqvsRaduLEJ4jsBRDNAUpOcP78Q5gMlb1HRugT6DwaoCRFDx Tvl8C484qu6vEsmPUwtrp+N6JQZ+Jxr8/HBb3X2R3U5t35lHEnO3t7HhrPdawnD3veGY mO82hT1VV5z757y9VOf+jaJP0Xwi7Z/WQqEMUpGbyi01dQfm5rbf+stZiawvNU+tdy/f yq4g==
MIME-Version: 1.0
X-Received: by 10.112.172.137 with SMTP id bc9mr15190622lbc.21.1382401663280;  Mon, 21 Oct 2013 17:27:43 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 17:27:43 -0700 (PDT)
In-Reply-To: <526581A1.7010100@gmail.com>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr> <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu> <526581A1.7010100@gmail.com>
Date: Mon, 21 Oct 2013 20:27:43 -0400
Message-ID: <CAMm+LwgZArgYEfT6-aR0ogW_PVk3uCc6YpnBvSUzebjoxvF_hA@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2645613ac4f04e94978db
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Lixia Zhang <lixia@cs.ucla.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: Tue, 22 Oct 2013 00:27:53 -0000

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

On Mon, Oct 21, 2013 at 3:33 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

>
> More to the point, we did try the "submission via national standards
> bodies" approach. I believe it was called OSI.
>
>    Brian
>

Whether it worked is a matter of which metrics you judge it by.

They have a MUCH nicer HQ than we have. Ergo it worked in one regard
important to some people.

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

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

<div dir=3D"ltr">On Mon, Oct 21, 2013 at 3:33 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
><br></div>
More to the point, we did try the &quot;submission via national standards<b=
r>
bodies&quot; approach. I believe it was called OSI.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0Brian<br>
</font></span></blockquote></div><br>Whether it worked is a matter of which=
 metrics you judge it by.</div><div class=3D"gmail_extra"><br></div><div cl=
ass=3D"gmail_extra">They have a MUCH nicer HQ than we have. Ergo it worked =
in one regard important to some people.<br clear=3D"all">
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a11c2645613ac4f04e94978db--

From brian.e.carpenter@gmail.com  Mon Oct 21 17:28:01 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 DC2B111E87AD for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.078
X-Spam-Level: 
X-Spam-Status: No, score=-100.078 tagged_above=-999 required=5 tests=[AWL=-2.479, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQJ+yXfx1In5 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:28:01 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id DF5E011E871F for <ietf@ietf.org>; Mon, 21 Oct 2013 17:27:55 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p10so6083121pdj.22 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:27: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=29xcElW2QYlc1Xo4PTWS/eXi7rWLFxcxjh5w6oItvz0=; b=WL+hek6fOjFloWn3bH928G0DMf4aF9eFOaq0CmmzIQVgNAlJZmq1GSQ2waznnzh4aO qnrmq/3X/YjxE5FO6HrMVtPAuuiW1ufUA4W/krg1udZWkg56z8TVQHlGFbco+oo1wIqs ALNn0L1yMhuSFzlUykPaIIHKszt9ge7fcZBruLpgf16sl6YIilrHZDAvVI8Hs7eACBEc uI1N4VzcSdpcLx3TjChvaJU3oS6gW8SuAo5ef4O3YSXmIJcR++1ak9H/edVE/HCB9mnT q58YMI1nIniGO56ZXB5UDwAXQtCyy4j2oK186oU6cnIhjyqoffIg2cJQhWZqjq4SW3NO 2ocA==
X-Received: by 10.67.23.227 with SMTP id id3mr20726685pad.101.1382401675718; Mon, 21 Oct 2013 17:27:55 -0700 (PDT)
Received: from [192.168.178.20] (254.194.69.111.dynamic.snap.net.nz. [111.69.194.254]) by mx.google.com with ESMTPSA id b3sm23514822pbu.38.2013.10.21.17.27.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 17:27:55 -0700 (PDT)
Message-ID: <5265C68B.1050206@gmail.com>
Date: Tue, 22 Oct 2013 13:27:55 +1300
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: Anonymous postings
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>, <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net>	<290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surrey.ac.uk> <5265A349.6090902@gmail.com>
In-Reply-To: <5265A349.6090902@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: Tue, 22 Oct 2013 00:28:02 -0000

On 22/10/2013 10:57, Melinda Shore wrote:
> On 10/21/13 1:37 PM, l.wood@surrey.ac.uk wrote:
>> A persistent identifier is helpful in sustained shared multiparty
>> conversation; whether it represents a "real" person or not does not
>> matter.
> 
> Right, this is clearly a problem as stated, but there's a long
> history of people posting from and participating from those
> addresses, while the other is some individual whose only posts
> were ad hominem.  So what's of interest here probably isn't
> anon-/pseudonymity, but some sort of reputation or track record.

I agree, but in this case the email address was obscure, the
content was irrelevant, and the tone was, at least to my eyes,
highly provocative. It was the sum of those three aspects that
set me off.

If someone sends well argued technical comments, or comments
on IETF procedural questions, using a pseudonym, that would
be a different matter. I can certainly imagine circumstances
in which somebody might prefer to do that.

    Brian


From melinda.shore@gmail.com  Mon Oct 21 17:31: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 D5FDD11E81D6 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.099
X-Spam-Level: 
X-Spam-Status: No, score=-0.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qo52jJyXHNKi for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:31:15 -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 1AC1611E82E0 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:31:15 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id jt11so1775974pbb.15 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:31: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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LisD45UUMs9U+bEwR4FAj9Xd6JYJN118u0k4JaIZx1E=; b=T3F520LxBbgjH7LN4m4Shc5PJeCd7x7v/zX0fyvPMmTDUjhDFJWnW5RwfJlfct6BTM AvWuE6i/YIVO10MAplOanwfuI7VVCER+bldEHysLy0bo5IJ4JBYsbA/FnD5TBcmyORcG 6ItAy4nd/yVu0YR1BzF977f6ttuU5pZGYg0Xh7MlUNYul3NwDRyR4RKJm14cajhpB9iR jnBHnrPbk5aKy1dJjYHrVD+0GaXLdIQxTed5B11qIGWvYU0TbP2jDRzJ4YWz+TATGN4b qcRdQAk8342f9a2FEVTUkGXlLn6iLIJob9sJWyh0kcAbQP5sdMbdC2OQVeLAP+sfH33S eW7A==
X-Received: by 10.66.141.165 with SMTP id rp5mr20796464pab.90.1382401874739; Mon, 21 Oct 2013 17:31:14 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id ef10sm28881203pac.1.2013.10.21.17.31.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Oct 2013 17:31:13 -0700 (PDT)
Message-ID: <5265C74F.3060007@gmail.com>
Date: Mon, 21 Oct 2013 16:31:11 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Anonymous postings
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>, <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net>	<290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surrey.ac.uk> <5265A349.6090902@gmail.com> <5265C68B.1050206@gmail.com>
In-Reply-To: <5265C68B.1050206@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: Tue, 22 Oct 2013 00:31:16 -0000

On 10/21/13 4:27 PM, Brian E Carpenter wrote:
> I agree, but in this case the email address was obscure, the
> content was irrelevant, and the tone was, at least to my eyes,
> highly provocative. It was the sum of those three aspects that
> set me off.

Right, but the point (for me) is the problem isn't anonymity
or pseudonymity per se, it's that the address was completely
unfamiliar.  This was someone who was not a "regular" IETF
participant and with no track record of technical participation
who immediately popped off with some ad hominem posts.

Melinda


From hallam@gmail.com  Mon Oct 21 17:32: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 18A4D11E82B9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Level: 
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 RXre5zcXrvrf for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:32:29 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5301D11E82BC for <ietf@ietf.org>; Mon, 21 Oct 2013 17:32:23 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id ep20so3290295lab.6 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:32:22 -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=oxZffUd+qB/idkBCZAZRjKkeMivIsTlPDSGbxyKH3uY=; b=mdm9bh7j0xQzVQqpXTeh1z6nuTrNf9NHi1jKGTSzePyIH5YsMPRh24UeG8qDrM9tuE q6cTL3z5he4Vi+zRpxwYK6xqA7JSJSpuLNKUhQmL1EhuV+2P8QI7S3vJaqyxoVxETV+f jHQnqH5OmJ+joIZy7/+Z2JihnXDHFhYqMg/SlDbQsXNTbhT9qo1Wb7REkrPJ53WKxU+O KXOGW0MXREKIhe/7qukF1Bu+geUz1lpJ/hlGc0g5MRc5D4yQGk5TRdqjAVW/CqeFRvEI e4RSgwrD00Fy7mdS7ai+R2J8jIWonRTyEVouVRSUfz7fSuEwI+EycO5c9eb3h8liQaNR U23A==
MIME-Version: 1.0
X-Received: by 10.112.172.137 with SMTP id bc9mr15201961lbc.21.1382401942383;  Mon, 21 Oct 2013 17:32:22 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 17:32:22 -0700 (PDT)
In-Reply-To: <20131021205001.GI2783@besserwisser.org>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <52654DEF.7050200@gmx.net> <20131021205001.GI2783@besserwisser.org>
Date: Mon, 21 Oct 2013 20:32:22 -0400
Message-ID: <CAMm+Lwge7QwiVMYHaGWPTs7LDhB_1t7Vq_yqddeTpA6BQYx8Fg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Content-Type: multipart/alternative; boundary=001a11c26456b6722504e949881c
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, 22 Oct 2013 00:32:30 -0000

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

On Mon, Oct 21, 2013 at 4:50 PM, M=E5ns Nilsson <mansaxel@besserwisser.org>=
wrote:

> Subject: Re: Internet standardisation remains unilateral Date: Mon, Oct
> 21, 2013 at 05:53:19PM +0200 Quoting Hannes Tschofenig (
> hannes.tschofenig@gmx.net):
> > On 10/21/2013 04:34 PM, Jorge Amodio wrote:
> > >Halald Alvestrand (which btw is from Norway not the USA)
> >
> > This illustrates part of the problem.
> >
> > It depends on the type of argument you want to make and then you
> > count people different. You count Harald as someone who comes from
> > Norway. The author of the slide deck wanted to make a different
> > argument and so he sees Harald as a person working for Google, as
> > US-based company.
>
> I know Harald. He is from Norway. There is nothing more to say than that.
>

And I am a UK citizen and I work for a company where most of the senior
management are British. But from the point of view of most governments
concerned about 'Diversity' we count as US.

One of the reasons that the Web is so heavily US based is that it was the
only country with suitable existing infrastructure where most of the
pioneers could get visas to work.

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

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

<div dir=3D"ltr">On Mon, Oct 21, 2013 at 4:50 PM, M=E5ns Nilsson <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mansaxel@besserwisser.org" target=3D"_blank"=
>mansaxel@besserwisser.org</a>&gt;</span> wrote:<br><div class=3D"gmail_ext=
ra"><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">Subject: Re: Internet standardisation remain=
s unilateral Date: Mon, Oct 21, 2013 at 05:53:19PM +0200 Quoting Hannes Tsc=
hofenig (<a href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx=
.net</a>):<br>

<div class=3D"im">&gt; On 10/21/2013 04:34 PM, Jorge Amodio wrote:<br>
&gt; &gt;Halald Alvestrand (which btw is from Norway not the USA)<br>
&gt;<br>
&gt; This illustrates part of the problem.<br>
&gt;<br>
&gt; It depends on the type of argument you want to make and then you<br>
&gt; count people different. You count Harald as someone who comes from<br>
&gt; Norway. The author of the slide deck wanted to make a different<br>
&gt; argument and so he sees Harald as a person working for Google, as<br>
&gt; US-based company.<br>
<br>
</div>I know Harald. He is from Norway. There is nothing more to say than t=
hat.<br></blockquote><div><br></div><div>And I am a UK citizen and I work f=
or a company where most of the senior management are British. But from the =
point of view of most governments concerned about &#39;Diversity&#39; we co=
unt as US.</div>
<div><br></div><div>One of the reasons that the Web is so heavily US based =
is that it was the only country with suitable existing infrastructure where=
 most of the pioneers could get visas to work.<br></div></div><div><br>
</div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambake=
r.com/</a><br>
</div></div>

--001a11c26456b6722504e949881c--

From sm@resistor.net  Mon Oct 21 17:33:39 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 EA07811E868C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:33:38 -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.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 aBn2Ic4HZzaB for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:33: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 B5AD311E82E3 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:33:36 -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 r9M0XUNh001936; Mon, 21 Oct 2013 17:33:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382402016; bh=8V73Q3l6omTyEggVhkEpFhu/ipTE0/sV4rW2bPKl1+g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kB6tZ2mlZ1l39/c6pQqp+HlpuS9uqHNcXvFhnMW/7K2tL/5Jko0XHzUo2Bol+wEEj 72ut7zP80tFOTcmacVmIeYk0I2IqSbu7XvKKnXZMa2Y65IC+DpwYeZYmNvhnOp4BH/ N5Te01rQmSH+uB6Hqfgm+Szu+2Rq/E3hiOCJLRlk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382402016; i=@resistor.net; bh=8V73Q3l6omTyEggVhkEpFhu/ipTE0/sV4rW2bPKl1+g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=F/ON8Kr/YZaPMeUgvZ4hjqJ90bahab+oXxPFwr9sRCuBOp/6yf5fB5bsEm0i7DDwn c3MwARwIcST+BDD9Dow9opkK1x+qDylvGJl2H/LW96WnvQDZ5ObYfKmq+AOD7JFito 3dIxDvFhXZtJovZT16ygKUcNE2huEKvEye1q49LY=
Message-Id: <6.2.5.6.2.20131021170443.0e73d950@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Oct 2013 17:28:02 -0700
To: l.wood@surrey.ac.uk
From: SM <sm@resistor.net>
Subject: RE: Anonymous postings
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E3E25D8D@EXMB01CMS.surre y.ac.uk>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <6.2.5.6.2.20131021130523.0c4a6db8@resistor.net> <290E20B455C66743BE178C5C84F1240847E3E25D8D@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: Tue, 22 Oct 2013 00:33:39 -0000

At 14:37 21-10-2013, l.wood@surrey.ac.uk wrote:
>A persistent identifier is helpful in sustained shared multiparty 
>conversation; whether it represents a "real" person or not does not matter.

Yes.

>And who are "we"?

I read the message [1] as personal opinion.

Regards,
-sm

1. msg-id: CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com 


From jeanjour@comcast.net  Mon Oct 21 17:37:49 2013
Return-Path: <jeanjour@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 0DF9911E8460 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.436
X-Spam-Level: 
X-Spam-Status: No, score=-0.436 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  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 ER09a2-219Rg for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:37:44 -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 2319211E82E0 for <ietf@ietf.org>; Mon, 21 Oct 2013 17:37:29 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta12.westchester.pa.mail.comcast.net with comcast id g09j1m00A0xGWP85C0dUHk; Tue, 22 Oct 2013 00:37:28 +0000
Received: from [10.0.1.3] ([155.41.116.115]) by omta12.westchester.pa.mail.comcast.net with comcast id g0dA1m00n2VTZX73Y0dDdq; Tue, 22 Oct 2013 00:37:26 +0000
Mime-Version: 1.0
Message-Id: <a0624087ece8b7904914a@[10.0.1.3]>
In-Reply-To: <CAMm+LwgZArgYEfT6-aR0ogW_PVk3uCc6YpnBvSUzebjoxvF_hA@mail.gmail.com>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net>	<20131021133009.GA27979@nic.fr> <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu> <526581A1.7010100@gmail.com> <CAMm+LwgZArgYEfT6-aR0ogW_PVk3uCc6YpnBvSUzebjoxvF_hA@mail.gmail.com>
Date: Mon, 21 Oct 2013 20:37:07 -0400
To: Phillip Hallam-Baker <hallam@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: multipart/alternative; boundary="============_-829720251==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382402248; bh=54x7ZhtbkecIkV4z/3eP0idafen4gb/zFCuj8ap/vW4=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=jPIXwsrT5Lwt1H8Q1SSsDzITOeUehGQu2hcbQ7X29qsL2B/sVq6Sd/ObwEYqsflUE BxQFRbEv1OpUQeYmHlvgadI9qAPD48a9AVt6RddRqC4NFcvedM8n5KjvWxlDJkkDGY ya/05mzdTmJ6R3J2K2QPxe+ryPjZlRFg0QdtldolWIejMq3r6PoJB9pw67OERB0gig tzga9vaZeM7bZ+JoCzG2epgb/LT7+MkJEpD7sv2FDgmNxzGHSt2ZnC+9NMw5XxvmmK wi3//fmHum3Ocx+iRpM1Q4jnseT9VQzAMTI328QISmz8HlcSWCiEGO9z8gqX4aEXq2 8EfAuWRyKOP9w==
Cc: Lixia Zhang <lixia@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, 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, 22 Oct 2013 00:37:49 -0000

--============_-829720251==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I was unaware of any OSI HQ!!  Wow!  Where is it?

At 8:27 PM -0400 10/21/13, Phillip Hallam-Baker wrote:
>On Mon, Oct 21, 2013 at 3:33 PM, Brian E Carpenter 
><<mailto:brian.e.carpenter@gmail.com>brian.e.carpenter@gmail.com> 
>wrote:
>
>
>More to the point, we did try the "submission via national standards
>bodies" approach. I believe it was called OSI.
>
>    Brian
>
>
>Whether it worked is a matter of which metrics you judge it by.
>
>They have a MUCH nicer HQ than we have. Ergo it worked in one regard 
>important to some people.
>
>
>--
>Website: <http://hallambaker.com/>http://hallambaker.com/

--============_-829720251==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: Internet standardisation remains
unilateral</title></head><body>
<div>I was unaware of any OSI HQ!!&nbsp; Wow!&nbsp; Where is it?</div>
<div><br></div>
<div>At 8:27 PM -0400 10/21/13, Phillip Hallam-Baker wrote:</div>
<blockquote type="cite" cite>On Mon, Oct 21, 2013 at 3:33 PM, Brian E
Carpenter &lt;<a
href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a
>&gt; wrote:<br>
<blockquote><br></blockquote>
<blockquote>More to the point, we did try the &quot;submission via
national standards<br>
bodies&quot; approach. I believe it was called OSI.<br>
<font color="#888888"><br>
&nbsp; &nbsp;Brian</font><br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
Whether it worked is a matter of which metrics you judge it
by.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>They have a MUCH nicer HQ than we have.
Ergo it worked in one regard important to some people.<br>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>--<br>
Website: <a
href="http://hallambaker.com/">http://hallambaker.com/</a></blockquote>
<div><br></div>
</body>
</html>
--============_-829720251==_ma============--

From tytso@thunk.org  Mon Oct 21 17:52:12 2013
Return-Path: <tytso@thunk.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 A586611E80F1 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:52:12 -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 pWignlzwxj-u for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 17:52:11 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1D811E82CC for <ietf@ietf.org>; Mon, 21 Oct 2013 17:52:05 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1VYQCR-0007Wn-EL; Tue, 22 Oct 2013 00:51:55 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id B4F7E5801AB; Mon, 21 Oct 2013 20:51:51 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1382403111; bh=JCd1IFvLpjf+XtjkOHdJ+XRn93cl8EX6Q+N3osBo9Q4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=yF9GfXZkjNehSBwHQ1uTSCmYO9QZMFHlftl68OJpeeVN/MHu7/bLySVaABiBQ2pqr LVoYkwpW+FO7HPEMkYO/GxrYjNkoSAWcEsk+WrUGnTPgVgc8yHvwD5bnMvJZA86OX3 o0pD9a7vxLjn0v/cdeF5gUEMPpT8nESYQwYmIcdI=
Date: Mon, 21 Oct 2013 20:51:51 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131022005151.GA4180@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <qmva691t1norfnoaeimb8ft00t2gqr1m47@hive.bjoern.hoehrmann.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <qmva691t1norfnoaeimb8ft00t2gqr1m47@hive.bjoern.hoehrmann.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
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, 22 Oct 2013 00:52:12 -0000

On Mon, Oct 21, 2013 at 10:12:41PM +0200, Bjoern Hoehrmann wrote:
> I strongly object to listing "sexual imagery" here unless accompanied by
> a much longer list that includes violent imagery, imagery of aggressive
> or otherwise dangerous animals, death, illness, medical imagery, and
> whatever else people might find intimidating, say Fort Meade engulfed in
> lightning in a violent thunderstorm and the eye of Sauron montaged on
> top of it.

I think you will find that there would be those who would be quite
surprised by that last being considered "harassing language".  Which
is ultimately the problem with trying to define harassment.  Anyone
can be easily offended, and claim that they are offended just because
someone is wearing a "NSA: The only part of the government which
listens" T-shirt.  Do we really want to litigate each and every
instance where someone feels that something is harassment?

In some ways, it's much easier to say that "sexual harassment" shall
not be tolerated, with the observation that it's much easier to for
people to agree that there is no place for any kind of sexual imagery
or reference or analogy in a professional computing meeting/event.
(This is ignoring the use of the terms "male" and "female" in
reference to things like RS-232 adapters, but we don't use them any
more, so we're probably OK.  :-)

The moment the definition is widened to include any kind of
harassment, questions of definition start becoming very difficult.  I
remember lots of anti-OSI comments being made many years ago (some
with a technical bent, some less so).  Would that now be considered
harrassment if some ISO standardization folks were to step up and
complain?

Or how about discussions over failures of Certifying Authorities in
issuing bogus certificates, and how to fix it.  Would discussion of
past failures of various public CA's be considered intimidating by
employees of those CA's?

						- Ted

From hallam@gmail.com  Mon Oct 21 18:54:18 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 7DC9911E80F9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 18:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  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 Lb5YwPxjFQZq for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 18:54:18 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 600FF11E82F3 for <ietf@ietf.org>; Mon, 21 Oct 2013 18:54:17 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id x18so4242768lbi.40 for <ietf@ietf.org>; Mon, 21 Oct 2013 18:54: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=WX2FCCVY/Kqx4WJGu4tM1L2lh56KGw7hZd+cwGPAM3g=; b=PhXCNBVee2RMovLD45r28NqYHbeYtpIPB3tbpfmxxGxRmJBeafC2I/2gvLxVJHFbeu BqViJohshFZ5hxnGlL2XrJtx888QA1cBcZmvAv4ccZE5eaGBTQ3ZhfTXftVPFn3uujBZ 9HyMzOZTZoYugLmbeDOJQSeQrYXSemcuvMZ8X41bo+r4pdcT2ec2TezpENSiFiSyl/OY QRWn1QLEwMYFQlr1FzNUCSzcvAc0027FVT0X7BKWWVtXt1+qze/iT3+DB5kDnMFy5fgD nizlW/GB0s4x6wxhl2Y+0D0YZpx2jn7JadmADEOEpTLJhQUooJ89cWlF5j1tKx6krylK R2wA==
MIME-Version: 1.0
X-Received: by 10.112.168.3 with SMTP id zs3mr15565226lbb.2.1382406856432; Mon, 21 Oct 2013 18:54:16 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 21 Oct 2013 18:54:16 -0700 (PDT)
In-Reply-To: <a0624087ece8b7904914a@10.0.1.3>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net> <20131021133009.GA27979@nic.fr> <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu> <526581A1.7010100@gmail.com> <CAMm+LwgZArgYEfT6-aR0ogW_PVk3uCc6YpnBvSUzebjoxvF_hA@mail.gmail.com> <a0624087ece8b7904914a@10.0.1.3>
Date: Mon, 21 Oct 2013 21:54:16 -0400
Message-ID: <CAMm+Lwh-f7RZOiCKKMnyQfCtuZJ5wXdOfg1FttWYhEMOnC7oLA@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Day <jeanjour@comcast.net>
Content-Type: multipart/alternative; boundary=001a11c33fe69ce09004e94aadb3
Cc: Lixia Zhang <lixia@cs.ucla.edu>, 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: Tue, 22 Oct 2013 01:54:18 -0000

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

On Mon, Oct 21, 2013 at 8:37 PM, John Day <jeanjour@comcast.net> wrote:

> **
> I was unaware of any OSI HQ!!  Wow!  Where is it?
>

The ITU HQ is in Geneva. Quite an impressive entrance hall.


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

--001a11c33fe69ce09004e94aadb3
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 Mon, Oct 21, 2013 at 8:37 PM, John Day <span dir=3D"ltr">&lt;<a =
href=3D"mailto:jeanjour@comcast.net" target=3D"_blank">jeanjour@comcast.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"><u></u>
<div>
<div>I was unaware of any OSI HQ!!=A0 Wow!=A0 Where is it?</div></div></blo=
ckquote><div><br></div><div>The ITU HQ is in Geneva. Quite an impressive en=
trance hall.=A0</div></div><br clear=3D"all"><div><br></div>-- <br>Website:=
 <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>

</div></div>

--001a11c33fe69ce09004e94aadb3--

From fred@cisco.com  Mon Oct 21 19:38:09 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 67C5411E80FA; Mon, 21 Oct 2013 19:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.17
X-Spam-Level: 
X-Spam-Status: No, score=-110.17 tagged_above=-999 required=5 tests=[AWL=0.429, 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 d9bf+smSxB7P; Mon, 21 Oct 2013 19:38:03 -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 E4E1211E8234; Mon, 21 Oct 2013 19:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5925; q=dns/txt; s=iport; t=1382409482; x=1383619082; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=6wyKgH0hID86SqPrwLYlthtIxqXSwy/urXifGDDfjD0=; b=buhNZpnnAjXU2h6rRrdl0PLHJ+hqucx4V75f7AkshdiM/ENzJ2cxZcSk 7pxrk8mmsU1EtjUv4rDpx13HPPOlXw7ma37ex58xoC29rSEThYPQHkhin vn7X2QG3OdbdXQZOUrLmGZvu7Tk5zdGZDmrDQ82rGpenTuSKbC+sZM+tV Q=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAGTkZVKtJV2Y/2dsb2JhbABQCYMHgQy+QIEpFnSCJQEBAQMBaAMDCwULAgEIIiQyJQIEDgUIBg0Bh2QGun6OGYERMQeDH4EKA5AtgTCCTZVmgySCKg
X-IronPort-AV: E=Sophos;i="4.93,544,1378857600";  d="asc'?scan'208";a="274901071"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 22 Oct 2013 02:38:00 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9M2c0hp001617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Oct 2013 02:38:00 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Mon, 21 Oct 2013 21:38:00 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbwynqWCsfeyzkGVVMdxpmDcdZoAV7eA
Date: Tue, 22 Oct 2013 02:37:59 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.168.14]
Content-Type: multipart/signed; boundary="Apple-Mail=_C346068D-8ED1-4387-8BA1-3F16B3E97AF4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 02:38:09 -0000

--Apple-Mail=_C346068D-8ED1-4387-8BA1-3F16B3E97AF4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I support the goal, and, similar to others, think this is a good first =
cut. Others have raised difficult questions, such as the lack of a crisp =
definition of "harassment" and the need for both judgement on the part =
of the ombudsman and an appeal process in the event that the ombudsman =
is not seen as "part of the solution".=20

I wondered at the last sentence. What is the definition of an =
"appropriate" response to harassment? Does this mean that law =
enforcement might be contacted? Does it mean that an abusive poster =
might be excluded from posting to a list? If it is in the context of a =
meeting, does it mean that the aggressive party might be asked to leave, =
either the specific meeting or the meeting venue? I suspect that this =
may imply some variant on legal process (as noted in Ted's use of the =
term "litigate"), which worries me immensely. What guidance can be given =
to the ombudsman and to an appellant of an ombudsman's decisions to =
ensure the appropriateness of a counter-measure?



On Oct 20, 2013, at 9:44 PM, IETF Chair <chair@ietf.org> wrote:

> The IETF should be an open and accessible body in which any individual =
feels
> able to participate without fear of oppression or harassment.  The =
IESG has
> become aware of some incidents of concern, is aware of various =
incidents in our
> industry in general, and has also observed that many similar =
organisations and
> conferences have a policy on this matter.
>=20
> In order to ensure the right atmosphere and to provide a suitable =
environment,
> the IESG has decided that it is desirable to write a simple and =
straightforward
> policy on harassment. This is not only to remind participants not to =
harass
> others (something that we hope is obvious to us all), but also to let =
anyone who
> it the target of harassment know that we take these matters seriously =
and that
> there is something they can do to address these sorts of incidents =
should they
> occur.
>=20
> A small design team has looked at existing policies used by other =
groups similar
> to the IETF and consulted with some of the ISOC professionals with =
expertise in
> human resources and issues of workplace harassment. The design team =
has put
> together what the IESG feels is a good anti-harassment policy for the =
IETF: It
> is short and to the point, it is modeled on and makes heavy re-use of =
the
> language of existing policies, and it sets forth reasonable procedures =
for the
> IETF.
>=20
> The IESG intends to put in place Ombudspersons as confidential initial =
contact
> points for situations where there is a concern of harassment. The =
selection of
> Ombudspersons will happen later, and the person(s) will have =
appropriate
> training and expertise.
>=20
> The IESG plans to adopt this as an IESG Statement. We solicit your =
feedback. We
> understand that this is a difficult and sensitive topic to discuss, =
but we do
> want your comments. If you feel more comfortable sending comments =
directly to
> the IESG <iesg@ietf.org> rather than discussing them on the IETF list, =
please
> feel free to do so.
>=20
> Jari Arkko for the IESG
>=20
> --- Draft Statement ---
>=20
> IETF Anti-Harassment Policy
>=20
> IETF meetings, virtual meetings, and mailing lists are intended for =
professional
> collaboration and networking. The IETF strives to create and maintain =
an
> environment in which people are treated with dignity, decency, and =
respect.
> Those who participate in the IETF are expected to behave according to
> professional standards and demonstrate appropriate workplace behavior. =
While
> participating in the IETF, communication between participants should =
be
> appropriate for a professional audience including people of many =
different
> backgrounds.
>=20
> While our processes let chairs deal with disruptive public behaviors =
on mailing
> lists and in IETF face-to-face meetings, harassment is a serious =
problem that
> warrants special attention. IETF participants should not engage in =
harassment
> while at IETF meetings, virtual meetings, social events, or on mailing =
lists.
> Harassment is unwelcome hostile or intimidating behavior, in =
particular speech
> and behavior that is sexually aggressive or intimidates based on =
attributes like
> race, gender, religion, age, color, national origin, ancestry, =
disability,
> sexual orientation, or gender identity. Harassment of this sort will =
not be
> tolerated in the IETF. Harassment includes the use of offensive =
language or
> sexual imagery in public presentations and displays, degrading verbal =
comments,
> deliberate intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, and unwelcome sexual attention.
>=20
> Participants asked to stop any harassing behavior are expected to =
comply
> immediately. If you believe you have been harassed, notice that
> someone else is being harassed, or have any other concerns, you are =
encouraged
> to raise your concern in confidence with one of the Ombudspersons.
>=20
> If these standards are violated, appropriate action will be taken.


--Apple-Mail=_C346068D-8ED1-4387-8BA1-3F16B3E97AF4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSZeT3bjEdbHIsm0MRAu4uAJ9B1t7rjy8XDpOHFPreE9kW7Nn1zQCfcv0M
UXOIk8PJdBYv/VSJ4tXssRA=
=nH3R
-----END PGP SIGNATURE-----

--Apple-Mail=_C346068D-8ED1-4387-8BA1-3F16B3E97AF4--

From michel@arneill-py.sacramento.ca.us  Mon Oct 21 19:47:58 2013
Return-Path: <michel@arneill-py.sacramento.ca.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 641D311E82D9 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 19:47:58 -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.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 uKC7QI1EpQVe for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 19:47:53 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) by ietfa.amsl.com (Postfix) with ESMTP id 37C2411E80F5 for <ietf@ietf.org>; Mon, 21 Oct 2013 19:47:52 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Internet standardisation remains unilateral
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Oct 2013 19:47:51 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
x-mimeole: Produced By Microsoft Exchange V6.5
In-Reply-To: <52659156.2080204@alcatel-lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Internet standardisation remains unilateral
Thread-Index: Ac7OneQfAoQE5ROvTP6BaNQLkH8DtgALtvfg
References: <20131021125834.GA24167@nic.fr><CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com><a0624085fce8afbbba1ac@[10.0.1.3]><392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local> <52659156.2080204@alcatel-lucent.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Martin Vigoureux" <martin.vigoureux@alcatel-lucent.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, 22 Oct 2013 02:47:58 -0000

>> Michel Py wrote:
>> But too many French are entrenched in an anti-American
>> culture that refuses to learn English.

> Martin Vigoureux wrote:
> Could you elaborate on how much is "too many"?

One. Pouzin is tilting at windmills. Whatever his agenda is, he's acting
like a crying baby (or a politician) and expecting to get back some
visibility by putting the blame on the IETF, (as we all know a
subversive agent of the "Great Satan" the US). I'm with Stephane here:
I'm allergic to BS. And I'm with Jorge too: instead of whining, do
something.

Why not having standard bodies operating in Basque or Catalan (two minor
dialects in the South of France) while we're at it? This is ridiculous.

Recently on the FRnOG mailing list we had another troll whining about
the RIPE-NCC documents being in English. I say to both: get a life.
There is nothing more global than the Internet, and whether you like it
or not the language is English. Adapt or go do something else.

Michel.


From mnot@mnot.net  Mon Oct 21 19:53:09 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 A64AF11E8109 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 19:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.821
X-Spam-Level: 
X-Spam-Status: No, score=-104.821 tagged_above=-999 required=5 tests=[AWL=-2.222, 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 zqpEn7+hOLya for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 19:53:04 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 85FD211E810F for <ietf@ietf.org>; Mon, 21 Oct 2013 19:53:03 -0700 (PDT)
Received: from [192.168.1.64] (unknown [118.209.145.45]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 23DD650A73; Mon, 21 Oct 2013 22:53:01 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Internet standardisation remains unilateral
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
Date: Tue, 22 Oct 2013 13:52:55 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A22FBBB-AA0B-4BBB-AB9C-1BBBBA877FA2@mnot.net>
References: <20131021125834.GA24167@nic.fr><CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com><a0624085fce8afbbba1ac@[10.0.1.3]><392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local> <52659156.2080204@alcatel-lucent.com> <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
To: "Michel Py" <michel@arneill-py.sacramento.ca.us>
X-Mailer: Apple Mail (2.1510)
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, 22 Oct 2013 02:53:09 -0000

On 22/10/2013, at 1:47 PM, "Michel Py" =
<michel@arneill-py.sacramento.ca.us> wrote:

>  Adapt or go do something else.

Well, that's the rub, isn't it?


--
Mark Nottingham   http://www.mnot.net/




From jeanjour@comcast.net  Mon Oct 21 20:12:14 2013
Return-Path: <jeanjour@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 9A22011E8123 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 20:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.436
X-Spam-Level: 
X-Spam-Status: No, score=-0.436 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, 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 373IPiirVDoe for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 20:12:07 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF8711E8315 for <ietf@ietf.org>; Mon, 21 Oct 2013 20:12:01 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA11.westchester.pa.mail.comcast.net with comcast id g1eY1m0070bG4ec5B3C00z; Tue, 22 Oct 2013 03:12:00 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta03.westchester.pa.mail.comcast.net with comcast id g3Bz1m00814WE023P3BzBf; Tue, 22 Oct 2013 03:12:00 +0000
Mime-Version: 1.0
Message-Id: <a06240881ce8b9b23f599@[10.0.1.3]>
In-Reply-To: <CAMm+Lwh-f7RZOiCKKMnyQfCtuZJ5wXdOfg1FttWYhEMOnC7oLA@mail.gmail.com>
References: <20131021125834.GA24167@nic.fr> <5265275B.8040105@dcrocker.net>	<20131021133009.GA27979@nic.fr> <F633EFCE-3712-4608-8BAC-C46E322451F2@cs.ucla.edu> <526581A1.7010100@gmail.com> <CAMm+LwgZArgYEfT6-aR0ogW_PVk3uCc6YpnBvSUzebjoxvF_hA@mail.gmail.com> <a0624087ece8b7904914a@10.0.1.3> <CAMm+Lwh-f7RZOiCKKMnyQfCtuZJ5wXdOfg1FttWYhEMOnC7oLA@mail.gmail.com>
Date: Mon, 21 Oct 2013 23:03:34 -0400
To: Phillip Hallam-Baker <hallam@gmail.com>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: multipart/alternative; boundary="============_-829710976==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382411520; bh=b059nmISoyDGByPj6dUiyctz8YOYnV0zuq7s59i1OBk=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=iqsMb4WM61N5VmFqvcUUH2DNSL4Csgr3a6CwV1JWgLoqdHr3DLifiefC2CPz+etvG WAm/qYc4ZunHyTFITDHI1deBMPc1WHWhvj3Jv28tdxHFfBAsj0J/wgkBykQ50uKy0K U3+At908yiMIgGlm7LUnVL8bolLqbg91GCSD9Ap55PMriDMg0L9AqYyBM2G+XrvqxB 3abejbS5qLKB1r9Cwx2uJrFVGrpTnBKroH94V1j3581g+l3YDhnL87o/v2kr47XhLZ g1JjsDk0Rtyiq12rvN9iFzWBgumurnl+q+tVBpXrSyKPfxU7boxQZye9VJar1zpxLm jIilwpNzYQcbA==
Cc: Lixia Zhang <lixia@cs.ucla.edu>, 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: Tue, 22 Oct 2013 03:12:14 -0000

--============_-829710976==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Interesting.  I was deeply involved with OSI for many years and never 
went there.  I thought that OSI was one of the thousands of ISO 
projects and ITU was just tagging along.

Gosh!  Learn something every day!  Thanks!

At 9:54 PM -0400 10/21/13, Phillip Hallam-Baker wrote:
>On Mon, Oct 21, 2013 at 8:37 PM, John Day 
><<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:
>
>I was unaware of any OSI HQ!!  Wow!  Where is it?
>
>
>The ITU HQ is in Geneva. Quite an impressive entrance hall.
>
>
>--
>Website: <http://hallambaker.com/>http://hallambaker.com/

--============_-829710976==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: Internet standardisation remains
unilateral</title></head><body>
<div>Interesting.&nbsp; I was deeply involved with OSI for many years
and never went there.&nbsp; I thought that OSI was one of the
thousands of ISO projects and ITU was just tagging along.</div>
<div><br></div>
<div>Gosh!&nbsp; Learn something every day!&nbsp; Thanks!</div>
<div><br></div>
<div>At 9:54 PM -0400 10/21/13, Phillip Hallam-Baker wrote:</div>
<blockquote type="cite" cite>On Mon, Oct 21, 2013 at 8:37 PM, John Day
&lt;<a href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;
wrote:<br>
<blockquote>I was unaware of any OSI HQ!!&nbsp; Wow!&nbsp; Where is
it?<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The ITU HQ is in Geneva. Quite an
impressive entrance hall.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>--<br>
Website: <a
href="http://hallambaker.com/">http://hallambaker.com/</a></blockquote>
<div><br></div>
</body>
</html>
--============_-829710976==_ma============--

From ajs@anvilwalrusden.com  Mon Oct 21 20:57:07 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 9764D11E831C for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 20:57:07 -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 vS4BfRlQiHIs for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 20:57:02 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7870311E814B for <ietf@ietf.org>; Mon, 21 Oct 2013 20:57:02 -0700 (PDT)
Received: from mx1.yitter.info (unknown [203.83.33.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 090D28A031 for <ietf@ietf.org>; Tue, 22 Oct 2013 03:57:00 +0000 (UTC)
Date: Mon, 21 Oct 2013 23:56:41 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131022035640.GA7434@mx1.yitter.info>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <673A097E66897B69B6C13B73@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: Tue, 22 Oct 2013 03:57:07 -0000

Hi,

On Mon, Oct 21, 2013 at 01:45:00PM -0400, John C Klensin wrote:
 
> I've got the same reaction to "IDN technical restrictions".  I'm
> not aware of any significant ones unless one has a desire to
> use, e.g., symbols, as domain name labels.  And, as far as
> "visual ambiguities" are concerned, I'd love to know what he
> proposes  

Having just sat through his presentation at the IGF meeting, I think
what he proposes is roughly, "Change math so that trees don't have a
single root."  He has just advocated "multiple roots", has asserted
repeatedly that ICANN controls the entire DNS and that the DNS is
therefore controlled by the US, and that IDN is not enough because.
Happily, we have open-root (perhaps amusingly, available from
http://open-root.eu/), which is prepared to offer you this
alternate-root, not-IDN-but-internationalized, all-works-magically
solution.

I have a great deal of respect for M. Pouzin's contributions to the
technical development of the Internet.  I'm afraid, however, that I
can't tell the difference between what he just proposed and a barker's
proposal for the Medicinal Compound, "efficacious in every case".

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Mon Oct 21 22:36:17 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 B677D11E846D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 22:36:17 -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 hN9zslJcDGr8 for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 22:36:17 -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 4C05411E8464 for <ietf@ietf.org>; Mon, 21 Oct 2013 22:36:16 -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 r9M5a4iN004150; Mon, 21 Oct 2013 22:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382420169; bh=8bc2Q02CS3rroZrSvF8dYBamWEzyVeg+uPFw+SJMK0w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=X/5WrTstAYnUn2hn/WvySmvt6ew+pky+fIeLoyOMlqpjm2Jqx41jHfqspQ/9KzhuD xm14rmKCt7ntkC5StTbOzI1eZRyE+YTGQ+AqrhNUHVYxpvnl6QsVGlN1/m2nQlIBKc Mgadqo2OlvHMW+FF/Xr8TKyuf8V5TvL+KNR2fB+8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382420169; i=@resistor.net; bh=8bc2Q02CS3rroZrSvF8dYBamWEzyVeg+uPFw+SJMK0w=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QJSIae6V3koccpd9gpkh5+WBwW4twCd57/Sgxau1Z3TWWq4eHLZpqcuHiXuuP5bRY SBu2bSvklAw/Wt+GUk1gw0USC6MclrtQZCxd20NfUD3O1zbjQS4HkxPpQGA/nOTP0g lI30ASBSNH2Umes1c3XFvrjVuF2sQCvHPRCiTJ20=
Message-Id: <6.2.5.6.2.20131021202945.0e873928@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 21 Oct 2013 22:30:21 -0700
To: John Day <jeanjour@comcast.net>
From: SM <sm@resistor.net>
Subject: Re: Internet standardisation remains unilateral
In-Reply-To: <a0624085fce8afbbba1ac@[10.0.1.3]>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@[10.0.1.3]>
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: Tue, 22 Oct 2013 05:36:17 -0000

Hi John,
At 08:58 21-10-2013, John Day wrote:
> From my experience over the years, I would generalize this that the 
> developed world has dominated the standards process in this field, 
> whether it was the IETF, ISO, ITU, or IEEE and most others.  Most 
> of that has to do with the expense involved in 
> participating.  Since the 1990s, the ability to

Yes.

>participate on-line has done a lot to lower that barrier and we see 
>that.  At one point IEEE was considered a US professional organization and all

Let's assume that ietf@ is a data point for "participate on-line".  A 
scan of the mailing list archive for this month would show that the 
following IESG and IAB members have participated:

   Jari Arkko
   Benoit Claise
   Ted Lemon
   Barry Leiba
   Adrian Farrel
   Stephen Farrell
   Joel Jaeggli
   Pete Resnick
   Gonzalo Camarillo
   Stewart Bryant
   Spencer Dawkins
   Hannes Tschofenig
   Andrew Sullivan
   Eliot Lear
   Russ Housley
   Joel Halpern

All members have not participated (see above).

I would look at it this way; if I tell Person X that he/she has the 
ability to participate on-line and the person tells me: "I don't see 
everyone participating on-line", what would my response be?  If I 
give a less-than-honest response it won't be convincing.

>It still takes time for countries to "come up to speed" and do we 
>really have any idea how many are watching but contributing 
>infrequently. As Jorge points out we are seeing this change, 
>although perhaps not as fast as we (or they) would like.

I don't think that there are any numbers for "contributing 
infrequently".  It is premature to say whether there is a visible 
change (in terms of countries) or not.

>Yes, English is a problem for all non-English speakers.   It takes a 
>lot of effort to work in a foreign language even when you are 
>fluent, and English isn't the easiest of languages.  ;-) I have

Yes.

The is also the problem of culture.  Person X and I may speak the 
same language (it might not be English) but it can still be difficult 
for us to have a conversation.  Person X might not be comfortable to 
tell me what he/she thinks or that he/she has not understood what I 
said.  It might be some variation of cultural leveling.

>As with most things like this, if the problem isn't stressed 
>progress against the issue will be even slower.  There are 
>structural issues in the IETF that allow over representation in 
>meetings, what some might call stacking meetings, but this seems to 
>be a case more of companies stacking meeting rather than countries.

Yes.

There is a clash of values at some level ...

Regards,
-sm  


From ajs@anvilwalrusden.com  Mon Oct 21 23:47:53 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 C222311E849A for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 23:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.31
X-Spam-Level: 
X-Spam-Status: No, score=0.31 tagged_above=-999 required=5 tests=[AWL=-1.150,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, MANGLED_FORM=2.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 ZW-8TZMb6QbP for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 23:47:48 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id EB5B411E8477 for <ietf@ietf.org>; Mon, 21 Oct 2013 23:47:47 -0700 (PDT)
Received: from mx1.yitter.info (unknown [203.83.33.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9B98D8A031 for <ietf@ietf.org>; Tue, 22 Oct 2013 06:47:46 +0000 (UTC)
Date: Tue, 22 Oct 2013 02:47:42 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131022064340.GB7901@mx1.yitter.info>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com> <20131022035640.GA7434@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131022035640.GA7434@mx1.yitter.info>
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: Tue, 22 Oct 2013 06:47:53 -0000

I know, I know, responding to myself, but a follow-up conversation
makes me think I should be a little more charitable.

On Mon, Oct 21, 2013 at 11:56:41PM -0400, Andrew Sullivan wrote:

> He has just advocated "multiple roots"

This turns out to be a consequence of his (quite correct) observation
that, for a user, the full context isn't necessary.  We already have
this notion in the DNS -- that's what the search path function is for.
M. Pouzin thinks this ought to be much more ubiquitous, in much the
way that you don't have to dial the full phone path (or anyway, not
everywhere) every time you call a local number.  From this, he gets
alternate roots.  So he's not simply being a crank, though I don't
fully understand how he gets to the conclusion he's reached.

Now, having corrected my previous uncharitable description, I suggest
that if people want to discuss DNSng, we do it on another list.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jruohone@gmail.com  Mon Oct 21 23:58:58 2013
Return-Path: <jruohone@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 2AF4611E812D for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 23:58: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 r00VV4QxSh6N for <ietf@ietfa.amsl.com>; Mon, 21 Oct 2013 23:58:57 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5351611E8359 for <ietf@ietf.org>; Mon, 21 Oct 2013 23:58:50 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id p9so6612324lbv.27 for <ietf@ietf.org>; Mon, 21 Oct 2013 23:58:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=DNOQog9LxHfMyZplNdXbdLIiFgf3h6c9sqz6fsqLLJs=; b=N8yawXoan7g9/b3DiDBhNRBTH2De+pIsdPXe/9SrweSNPDt+XgXsHeVGGlWNjPz2IO Bf/NJyfVwak06qqx7oqZEKwcM5a3lPU5l+j6uFacDduoD86ozyO6Ce76WrHBQfZSnsDp yu3DAsEfECisFECiMOEuM2x4vHHnXfCAEqnkpNLUzUiFN8IbJ+eoyz5/pT1o2nhLx/bY W4FF9ivoTvQbTd+Ci4JDEzoyBtcOI1ZmpqkAJDPcTt6QCgrYk5qdEpLpBcu660NoiA0d UrOUFsQICjKYfUIBPHO+PJODitp3wuSCVPs0AUDVvjLbnv7oaUqo5tyY9U21BlO9uMAS ivKw==
X-Received: by 10.152.228.130 with SMTP id si2mr564444lac.32.1382425129365; Mon, 21 Oct 2013 23:58:49 -0700 (PDT)
Received: from marx.bitnet (xdsl-83-150-88-127.nebulazone.fi. [83.150.88.127]) by mx.google.com with ESMTPSA id b6sm19628938lae.0.2013.10.21.23.58.47 for <ietf@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Oct 2013 23:58:48 -0700 (PDT)
Sender: a b <jruohone@gmail.com>
Received: by marx.bitnet (Postfix, from userid 1000) id 59F4556C0; Tue, 22 Oct 2013 09:58:47 +0300 (EEST)
Date: Tue, 22 Oct 2013 09:58:47 +0300
From: Jukka Ruohonen <jruohonen@iki.fi>
To: ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
Message-ID: <20131022065847.GA13944@marx.bitnet>
Mail-Followup-To: ietf@ietf.org
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <673A097E66897B69B6C13B73@JcK-HP8200.jck.com>
User-Agent: Mutt/1.4.2.3i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jruohonen@iki.fi
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 06:58:58 -0000

On Mon, Oct 21, 2013 at 01:45:00PM -0400, John C Klensin wrote:
> Incidentally, I consider most of those slides to be distortions,
> presumably  in support of a rather specific agenda or at least
> the result of a very different perspective on appropriate global
> networking technology. 

Well, the slides are certainly somewhat provocative (like good slides often
are?). But I would guess that many of the observations are easily shown to
be empirical facts. It is hardly any news as such that there are national
and company interests embedded in the standardization processes.

Besides, IETF has of course been a popular case among the scholars of
standardization. See for instance, Gencer, M. (2012): The Evolution of
IETF Standards and their Production. International Journal of IT Standards
and Standardization Research 10(1). (Behind a paywall.)

- Jukka.

From rraszuk@gmail.com  Tue Oct 22 00:33:41 2013
Return-Path: <rraszuk@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 D4E1111E82E9 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 00:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.59
X-Spam-Level: 
X-Spam-Status: No, score=-1.59 tagged_above=-999 required=5 tests=[AWL=0.388,  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 kkXqCa6uiGse for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 00:33:41 -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 9B9D111E8359 for <ietf@ietf.org>; Tue, 22 Oct 2013 00:33:37 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id e14so1004057iej.22 for <ietf@ietf.org>; Tue, 22 Oct 2013 00:33:37 -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:message-id:subject :from:to:cc:content-type; bh=KDdHnbHFeZdpUhkZYoMG+Vp5XOHlys2C+r7XIIZCd5c=; b=dUm0MbnyhXrafUsfweH5eEB3k5OFVZ4gl3hWccoXSbLTkjfReyjLlODsd9o3GFXda0 KX9cqf76o9xM8MoD/M7PLxixKe85JPRP+kEr0tD+fahWUCEURl06tclmuVPh2xLnyo8b KoDxfXxynEubD85qHJ/ssk7ph2B1QBu3uLAY0ZBUjjmRDLS7IvlmHVupvznbyP6eVTkJ bU9XqhEplbIsqiHcM4+6kkD+C6KQa8ri8I1ynp5pxfDKXFS31xO9qESIp7BtoWx3wfOV 3RG9AIYHzK/S3NTAD8pJptzrEQ3hbr+mz4PMtAzDf1QlxBtypNBqEna5CllvDRJGexub FYyg==
MIME-Version: 1.0
X-Received: by 10.50.117.103 with SMTP id kd7mr12295418igb.4.1382427217005; Tue, 22 Oct 2013 00:33:37 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Tue, 22 Oct 2013 00:33:36 -0700 (PDT)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645BD5357@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645BD4A63@dfweml509-mbx.china.huawei.com> <2671C6CDFBB59E47B64C10B3E0BD5923043C7557D4@PRVPEXVS15.corp.twcable.com> <4A95BA014132FF49AE685FAB4B9F17F645BD5357@dfweml509-mbx.china.huawei.com>
Date: Tue, 22 Oct 2013 09:33:36 +0200
X-Google-Sender-Auth: 3PuoJTfDJYqD_5nnoKZx-h1z72A
Message-ID: <CA+b+ER=jqeJntjXMqB=OacjsJAf52vTDxsKoFj+PWD3ORia90g@mail.gmail.com>
Subject: Re: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt> (Software-Defined Networking: A Perspective From Within A Service Provider) to Informational RFC
From: Robert Raszuk <robert@raszuk.net>
To: Linda Dunbar <linda.dunbar@huawei.com>
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: Tue, 22 Oct 2013 07:33:41 -0000

Hi Linda,

You can click the web page and start number of cisco CSR or juniper
vSRX instances to create an arbitrary virtual networks. Is this SDN or
just nice web based front end which you call SDN ?

If I start the same network with few lines of python or perl script is
this still SDN or not any longer ?

Likewise I can easily provision BGP sessions and bunch of services
running on hardware routers by software .. in fact this is already the
case in vast majority of networks. It is therefor SDN too isn't it ?

Best,
R.


On Wed, Oct 9, 2013 at 8:40 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> It is true that SDN depends on automation.
>
> IMHO, "Automation" is a much bigger area than SDN.
>
> When you look at Amazon EC2 graphic interface, you can click X number of VMs, and create any kind of virtual networks among them, along with a set of service functions to dictate inter-subnet communication. That is a "Software defined network".
>
> Linda
>
>
>
>> -----Original Message-----
>> From: George, Wes [mailto:wesley.george@twcable.com]
>> Sent: Wednesday, October 09, 2013 9:18 AM
>> To: Linda Dunbar; IETF Discussion
>> Subject: RE: [Sdn] FW: Last Call: <draft-sin-sdnrg-sdn-approach-04.txt>
>> (Software-Defined Networking: A Perspective From Within A Service
>> Provider) to Informational RFC
>>
>> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of
>> > Linda Dunbar
>>
>> >
>> > - We all understand the challenges of "Full Automation". However, the
>> > SDN and Full automation are two separate angles to Carrier networks.
>> I
>> > find the Section 4.1  "Implications of full automation" actually de-
>> > rails the focus of the draft on SDN.
>>
>> [WEG] I strongly disagree. First, "we all understand..." is an
>> overgeneralization, and a dangerous and grossly inaccurate one at that.
>> Lots of SDN vendors have repeatedly demonstrated to me how little they
>> actually understand about this problem. It's not a new problem by any
>> means, but there's a really significant amount of hand-waving going on
>> around the complexities of actually doing what they're saying is
>> possible through the "magic" of SDN, when few have demonstrated how the
>> abstract concept "SDN" actually makes solving this problem easier. The
>> reality is that SDN and automation are inextricably linked. The next to
>> last sentence in section 2.3 reinforces this, and I believe that 4.1 is
>> absolutely appropriate for this draft. A truly software-defined network
>> is an automated one, and any discussion of an operator's perspective on
>> SDN is going to need to consider the same challenges that have been
>> present in prior attempts to better automate network management,
>> provisioning, and control. There are two models for managing a network
>> like this, one that is fully automated, meaning that it is quite a lot
>> more complex and susceptible to "ghost in the machine" problems, the
>> other which has a human making most of the important decisions and then
>> dictating those to the network. Even the latter model requires a
>> significant amount of automation to execute what the human has decided
>> should be done.
>> The things covered in section 4.1 mirrors a lot of the discussion that
>> I have had both internally and with other operators around the
>> challenges of separating the hype of SDN from the actual benefit, and
>> in selling this model to operations folks who are skeptical of ceding
>> control to a set of computer logic.
>>
>> Wes George
>>
>> This E-mail and any of its attachments may contain Time Warner Cable
>> proprietary information, which is privileged, confidential, or subject
>> to copyright belonging to Time Warner Cable. This E-mail is intended
>> solely for the use of the individual or entity to which it is addressed.
>> If you are not the intended recipient of this E-mail, you are hereby
>> notified that any dissemination, distribution, copying, or action taken
>> in relation to the contents of and attachments to this E-mail is
>> strictly prohibited and may be unlawful. If you have received this E-
>> mail in error, please notify the sender immediately and permanently
>> delete the original and any copy of this E-mail and any printout.

From alexandru.petrescu@gmail.com  Tue Oct 22 00:44:52 2013
Return-Path: <alexandru.petrescu@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 88F9811E8352 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 00:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.203
X-Spam-Level: 
X-Spam-Status: No, score=-10.203 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, HELO_EQ_FR=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 FlxeMCxKPvGe for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 00:44:45 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 64B3011E84BA for <ietf@ietf.org>; Tue, 22 Oct 2013 00:44:41 -0700 (PDT)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9M7ic0E005334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 22 Oct 2013 09:44:38 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by nephilia.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9M7icf5000722 for <ietf@ietf.org>; Tue, 22 Oct 2013 09:44:38 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9M7iY7W032421 for <ietf@ietf.org>; Tue, 22 Oct 2013 09:44:38 +0200
Message-ID: <52662CE2.1020709@gmail.com>
Date: Tue, 22 Oct 2013 09:44:34 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: question: ISOC Panel at IETF88 in Vancouver?
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, 22 Oct 2013 07:44:52 -0000

Hello IETFers,

Is there going to be an ISOC Panel this time at IETF 88 in Vancouver?

Alex


From rogerj@gmail.com  Tue Oct 22 01:18:27 2013
Return-Path: <rogerj@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 9168F11E817D for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 01:18:27 -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 eN2dPSNcaFt1 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 01:18:26 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1403711E8306 for <ietf@ietf.org>; Tue, 22 Oct 2013 01:18:25 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so7707387wgh.10 for <ietf@ietf.org>; Tue, 22 Oct 2013 01:18:25 -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=31zGs7KLMX79h+mJYB1onA7IIY7/y6N4CsQjpCZ/sHI=; b=qWT6l/7cTXCafNPhZIV68kzXVWHZNgllZHp4k1eWM/bf2qmx2bHx0s96lEgtaVoWBk 8z8/GxQ1cTcthwI14t69KAFsGM9dPfk4MHa+XL0U5hFl3osGWIc0oQJ8coeDhUGarMQr uV+jIz4Av/XzkhZnEOjVNrESzW9734dUBavVcUWOWgYDX4MGxAiOb0M2T8sJ+y8RreFF VzWSszMUeJNKdTGmczhLHo8r32f04R+ZQY+Ff9FvOBQ/mdbZH4oONYEchwkmKKancJQL JcqVE7IJJgcUbiiTKvcpDNCIHoe+l0vhXFLi22+50bdomP1Jn+uG/RGkqnbjimmo0QIu QdBQ==
MIME-Version: 1.0
X-Received: by 10.180.78.167 with SMTP id c7mr13215050wix.25.1382429905182; Tue, 22 Oct 2013 01:18:25 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Tue, 22 Oct 2013 01:18:25 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@10.0.1.3> <392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local> <52659156.2080204@alcatel-lucent.com> <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
Date: Tue, 22 Oct 2013 10:18:25 +0200
Message-ID: <CAKFn1SHxpbN1Q8m+LfU+MzG=Hox0DzGeTMgXmY2_80yE_HSQOg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
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: Tue, 22 Oct 2013 08:18:28 -0000

On Tue, Oct 22, 2013 at 4:47 AM, Michel Py
<michel@arneill-py.sacramento.ca.us> wrote:
>>> Michel Py wrote:
>>> But too many French are entrenched in an anti-American
>>> culture that refuses to learn English.
>
>> Martin Vigoureux wrote:
>> Could you elaborate on how much is "too many"?
>
> One. Pouzin is tilting at windmills. Whatever his agenda is, he's acting
> like a crying baby (or a politician) and expecting to get back some
> visibility by putting the blame on the IETF, (as we all know a
> subversive agent of the "Great Satan" the US). I'm with Stephane here:
> I'm allergic to BS. And I'm with Jorge too: instead of whining, do
> something.
>
> Why not having standard bodies operating in Basque or Catalan (two minor
> dialects in the South of France) while we're at it? This is ridiculous.
>
> Recently on the FRnOG mailing list we had another troll whining about
> the RIPE-NCC documents being in English. I say to both: get a life.
> There is nothing more global than the Internet, and whether you like it
> or not the language is English. Adapt or go do something else.

The current de facto standard on Internet is English yes. That might change
given time, like 10+ years.
What I personal is very sure of is that it will not changed to Norwegian
(where I'm from), or any other European language.

If it was to change it was because there was a major amount of users,
tech companies, infrastructure and activity using that language. Not to
forget backing of real money and investments. Europa don't have that,
USA alone match our size in amount of Internet users, not to forget
that we do not have just one language here, we have many.

Take a wild guess what language that might get some of that in near
future (10-20years). China.



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From cdel@firsthand.net  Tue Oct 22 02:13:02 2013
Return-Path: <cdel@firsthand.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 A6FC821F9F19 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.023
X-Spam-Level: *
X-Spam-Status: No, score=1.023 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, HTML_IMAGE_ONLY_28=1.561, 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 wrPXlJfiefMZ for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:12:57 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [212.110.188.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3EB21F9F21 for <ietf@ietf.org>; Tue, 22 Oct 2013 02:12:57 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=firsthand.net; b=jrC1BaLqvQFkCR+Ec8WGCPu4H2eXYx+Fo2iXw3VIn/QseFMk8+eX85Epp7UXml7cdybG3VC9knHPUbrTQ7RoAh/ixc+XxFD3wZJck4MIm0cmeB4aqDaJlELI8cIVPOvZ; h=X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type;
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from orionlocal.local (host-78-145-247-11.as13285.net [78.145.247.11]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id DAABDE03BA; Tue, 22 Oct 2013 09:12:41 +0100 (BST)
Message-ID: <52664198.4060502@firsthand.net>
Date: Tue, 22 Oct 2013 10:12:56 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Subject: Re: Internet standardisation remains unilateral
References: <20131021125834.GA24167@nic.fr><CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com><a0624085fce8afbbba1ac@[10.0.1.3]><392CB277BC2EAE4FB83C1206954BA6CE0100F3@newserver.arneill-py.local> <52659156.2080204@alcatel-lucent.com> <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local>
Content-Type: multipart/alternative; boundary="------------040205020109040103050800"
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, 22 Oct 2013 09:13:02 -0000

This is a multi-part message in MIME format.
--------------040205020109040103050800
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Bakailao argi dago hizkuntza unibertsala! RFCs arrantza espedizioak
dira. Ez dago?

Christian
> Michel Py <mailto:michel@arneill-py.sacramento.ca.us>
> 22 October 2013 03:47
>>> Michel Py wrote:
>>> But too many French are entrenched in an anti-American
>>> culture that refuses to learn English.
>
>> Martin Vigoureux wrote:
>> Could you elaborate on how much is "too many"?
>
> One. Pouzin is tilting at windmills. Whatever his agenda is, he's acting
> like a crying baby (or a politician) and expecting to get back some
> visibility by putting the blame on the IETF, (as we all know a
> subversive agent of the "Great Satan" the US). I'm with Stephane here:
> I'm allergic to BS. And I'm with Jorge too: instead of whining, do
> something.
>
> Why not having standard bodies operating in Basque or Catalan (two minor
> dialects in the South of France) while we're at it? This is ridiculous.
>
> Recently on the FRnOG mailing list we had another troll whining about
> the RIPE-NCC documents being in English. I say to both: get a life.
> There is nothing more global than the Internet, and whether you like it
> or not the language is English. Adapt or go do something else.
>
> Michel.
>

--------------040205020109040103050800
Content-Type: multipart/related;
 boundary="------------070306020706060900080200"


--------------070306020706060900080200
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 style="font-family: Avenir Next;" bgcolor="#FFFFFF" 
text="#000000"><div style="font-family: Avenir Next;"><span 
style="font-family: Avenir Next;">Bakailao argi dago hizkuntza 
unibertsala! RFCs arrantza espedizioak dira. Ez dago?<br><br></span>Christian<br><blockquote
 style="border: 0px none;" 
cite="mid:392CB277BC2EAE4FB83C1206954BA6CE0100F8@newserver.arneill-py.local"
 type="cite"><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
 style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="michel@arneill-py.sacramento.ca.us" photoname="Michel Py"
 src="cid:part1.06020300.06060601@firsthand.net" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" 
href="mailto:michel@arneill-py.sacramento.ca.us" style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Michel Py</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">22 October 2013 
03:47</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><blockquote type="cite"><blockquote
 type="cite"><pre wrap="">Michel Py wrote:
But too many French are entrenched in an anti-American
culture that refuses to learn English.
</pre></blockquote></blockquote><pre wrap=""><!---->
</pre><blockquote type="cite"><pre wrap="">Martin Vigoureux wrote:
Could you elaborate on how much is "too many"?
</pre></blockquote><pre wrap=""><!---->
One. Pouzin is tilting at windmills. Whatever his agenda is, he's acting
like a crying baby (or a politician) and expecting to get back some
visibility by putting the blame on the IETF, (as we all know a
subversive agent of the "Great Satan" the US). I'm with Stephane here:
I'm allergic to BS. And I'm with Jorge too: instead of whining, do
something.

Why not having standard bodies operating in Basque or Catalan (two minor
dialects in the South of France) while we're at it? This is ridiculous.

Recently on the FRnOG mailing list we had another troll whining about
the RIPE-NCC documents being in English. I say to both: get a life.
There is nothing more global than the Internet, and whether you like it
or not the language is English. Adapt or go do something else.

Michel.

</pre></div></blockquote></div></body></html>

--------------070306020706060900080200
Content-Type: image/jpeg; x-apple-mail-type=stationery;
 name="compose-unknown-contact.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.06020300.06060601@firsthand.net>
Content-Disposition: inline;
 filename="compose-unknown-contact.jpg"

/9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEC
AQEBAQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgIC
AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAAR
CAAZABkDAREAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUK
BwAAAAAAAAACAQMEBQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAA
AAAAAAAAAAADAAEEAv/EACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oA
DAMBAAIRAxEAPwDuEt+gW/ULet6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJ
VIl7eXLCaZIGwBl3TY8epPx2+jy2ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4
v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJEw/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx
+a69/JSf9alIlste0VzaNpeFrcT9KKymotyiaZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mR
UfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRDnu5azS8miKqjOTVkKqS/psG37fo1Fbab
eg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GAcpOwBeN+U8/IkGbsiS8b7ryogmbz
hbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH4hPOI0DkjZtaJtFxuVEbIUUi
yeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJnYn9dnAQWl722p4ot37y
zqnlfp6FrqbwawG8/9k=
--------------070306020706060900080200--

--------------040205020109040103050800--

From tytso@thunk.org  Tue Oct 22 02:31:02 2013
Return-Path: <tytso@thunk.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 CB2AE21F9CAD for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:31:01 -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 MkYLIacd3hFf for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:31:00 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 3157811E8325 for <ietf@ietf.org>; Tue, 22 Oct 2013 02:30:58 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1VYYIi-0001gg-Mw; Tue, 22 Oct 2013 09:30:56 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 95F5B5801AB; Tue, 22 Oct 2013 05:30:52 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1382434252; bh=zZu2Kh8ufJD3//NzDGgFqDdb7t/I43i4toA7bUbhSZw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WBp8ujzh3RwcFgO7jZHfnA3UfdpPFJVp5JFRpnFFGcdc3iKyGcGJKARvIsfeYRfX4 FcjYs60yx58NvPG/RacBGb8fD119R/nBaLjjoZiX+d7Xmi2DOkBOvR1RcK1AZLaz4J RTgtxMeEgr3FnMkvJmxMqrdAzSTgOvOYQa85LlQk=
Date: Tue, 22 Oct 2013 05:30:52 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131022093052.GF9517@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
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, 22 Oct 2013 09:31:02 -0000

On Tue, Oct 22, 2013 at 02:37:59AM +0000, Fred Baker (fred) wrote:
> 
> I wondered at the last sentence. What is the definition of an
> "appropriate" response to harassment? Does this mean that law
> enforcement might be contacted? Does it mean that an abusive poster
> might be excluded from posting to a list? If it is in the context of
> a meeting, does it mean that the aggressive party might be asked to
> leave, either the specific meeting or the meeting venue? I suspect
> that this may imply some variant on legal process (as noted in Ted's
> use of the term "litigate"), which worries me immensely. What
> guidance can be given to the ombudsman and to an appellant of an
> ombudsman's decisions to ensure the appropriateness of a
> counter-measure?

These are indeed the critical questions.  It's easy to have a
statement about what might be considered "harassment".  If however
someone tries to use this as a debating tactic during a particularly
robust technical discussion, what happens next?  Does it get raised to
the wg chair?  If the wg chair says, that's just a robust technical
discussion, does it get escalated to ombudsman?  If the ombudsman
says, "nope, sorry", does it get escalated to the AD and IESG, and do
they then have to write up carefully crafted appeal documents which
will no doubt suck up huge amounts of their time?

Should there be any cost to someone who tries to escalate disputes via
the anti-harassment process, when it is determined afterwards that it
is not harassment?  If we do, then it might deter valid plaintiffs
from coming forward.  If we don't, how do we deter people who might
try to abuse this process from using it to that end?  Historically, we
certainly had people who have been rather enthusiastic about using
whatever appeal processes we've made available.

One hint --- we should definitely try to pursuade folks not to try to
get a decision based on the specific facts of a particulate dispute
via the court of public opinion:

       "Adria Richards, PyCon, and How We All Lost"
       http://amandablumwords.wordpress.com/2013/03/21/

						- Ted

From fred@cisco.com  Tue Oct 22 02:51:39 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 82AB011E8155 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:51:39 -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 GnbZPQKcuCzv for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 02:51:34 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 52A7011E8150 for <ietf@ietf.org>; Tue, 22 Oct 2013 02:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1014; q=dns/txt; s=iport; t=1382435494; x=1383645094; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gmxwaFaL/mPOiyX8b2WuTZbckwF2X6IqBMJSvmTKZLU=; b=QUpvM04Lc66dd4QnzOPF5weJKEO/nnbwV7cS6RFQBHAPIWYSYX1YeLjj Da+DqVr3qojLp3tw4Eu8ljZDZVQz4oC1fTm4ef8IsHsuZ1m1aznV5Dxw0 7irK2leWSeVQEDA/AoLLgUCwBI9xl5mYRm/7p0alvPVkI1J/CKPHFaZz5 I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjUFAJVJZlKtJV2Z/2dsb2JhbABZDoJ5OFS+QYEmFnSCJQEBAQMBeQULAgEIIiQyJQIEDg0Gh3IGDbp4jxUxB4MfgQoDkC2BMIdbkFiCZT+CKg
X-IronPort-AV: E=Sophos;i="4.93,547,1378857600";  d="asc'?scan'208";a="274977282"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 22 Oct 2013 09:51:34 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9M9pX7Y003456 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Oct 2013 09:51:34 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Tue, 22 Oct 2013 04:51:33 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbwynqWCsfeyzkGVVMdxpmDcdZoAV7eAgABzbwCAAAW6AA==
Date: Tue, 22 Oct 2013 09:51:32 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA729BB@xmb-rcd-x09.cisco.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org>
In-Reply-To: <20131022093052.GF9517@thunk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [216.128.36.107]
Content-Type: multipart/signed; boundary="Apple-Mail=_F8D4F962-E962-4A7F-9937-40E0A0769591"; protocol="application/pgp-signature"; micalg=pgp-sha1
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, 22 Oct 2013 09:51:39 -0000

--Apple-Mail=_F8D4F962-E962-4A7F-9937-40E0A0769591
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

> One hint --- we should definitely try to pursuade folks not to try to
> get a decision based on the specific facts of a particulate dispute
> via the court of public opinion:
> 
>       "Adria Richards, PyCon, and How We All Lost"
>       http://amandablumwords.wordpress.com/2013/03/21/

Hmm. I might want to hear more from Amanda Blum.

--Apple-Mail=_F8D4F962-E962-4A7F-9937-40E0A0769591
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSZkqabjEdbHIsm0MRAnHOAJ9fcqhVwaaG0MxvgCi2cezguuGLRACfdeTt
CcbdgaZNtS8UOtnNpQyQZRw=
=oDPN
-----END PGP SIGNATURE-----

--Apple-Mail=_F8D4F962-E962-4A7F-9937-40E0A0769591--

From randy@psg.com  Tue Oct 22 04:06:10 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 D773D21F9B58 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 04:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  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 CsZe2Mh4kfhY for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 04:06:10 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 12F5C11E8143 for <ietf@ietf.org>; Tue, 22 Oct 2013 04:06:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VYZml-0000vH-Tj; Tue, 22 Oct 2013 11:06:04 +0000
Date: Tue, 22 Oct 2013 13:06:03 +0200
Message-ID: <m21u3d5zvo.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <52657B0B.3080701@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@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: Tue, 22 Oct 2013 11:06:11 -0000

> Personal opinion:
> 
> 1. We shouldn't tolerate anonymous postings in any case.
> 
> 2. ISOC salaries are utterly irrelevant to any IETF discussion.
>    It's just way out of line.

anonymity is sometimes useful

as the ietf is legally f(isoc), isoc salaries will be relevant to those
folk inclined to spend their tine on process, organization, and
omphaloskepsis.

and to judge by the message counts on this list, far more folk are
interested in process, organization, and omphaloskepsis than in
techhical subects.

randy

From l.wood@surrey.ac.uk  Tue Oct 22 05:04: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 1C68611E8257 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 05:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-1.100, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 RF2rF8ZYmHlR for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 05:04:44 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9B711E8190 for <ietf@ietf.org>; Tue, 22 Oct 2013 05:04:39 -0700 (PDT)
Received: from [85.158.136.51:29239] by server-13.bemta-5.messagelabs.com id DD/15-31104-7D966625; Tue, 22 Oct 2013 12:04:39 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-49.messagelabs.com!1382443478!17633280!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23080 invoked from network); 22 Oct 2013 12:04:38 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-2.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 22 Oct 2013 12:04:38 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.216]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 22 Oct 2013 13:04:38 +0100
From: <l.wood@surrey.ac.uk>
To: <fred@cisco.com>, <tytso@mit.edu>
Date: Tue, 22 Oct 2013 13:02:08 +0100
Subject: RE: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbwynqWCsfeyzkGVVMdxpmDcdZoAV7eAgABzbwCAAAW6AP//0LiO
Message-ID: <290E20B455C66743BE178C5C84F1240847E3E25D8F@EXMB01CMS.surrey.ac.uk>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org>, <8C48B86A895913448548E6D15DA7553BA729BB@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA729BB@xmb-rcd-x09.cisco.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, 22 Oct 2013 12:04:48 -0000

because Amanda espouses a viewpoint you agree with?

http://www.technologywoman.com/2013/03/24/digging-beneath-the-surface-that-=
amanda-blum-article-on-adria-richards-is-not-what-it-seems/

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Fred Baker=
 (fred) [fred@cisco.com]
Sent: 22 October 2013 10:51
To: Theodore Ts'o
Cc: <ietf@ietf.org>
Subject: Re: Proposed IETF Anti-Harassment Policy

> One hint --- we should definitely try to pursuade folks not to try to
> get a decision based on the specific facts of a particulate dispute
> via the court of public opinion:
>
>       "Adria Richards, PyCon, and How We All Lost"
>       http://amandablumwords.wordpress.com/2013/03/21/

Hmm. I might want to hear more from Amanda Blum.

From hallam@gmail.com  Tue Oct 22 05:08:50 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 38F7211E8190 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 05:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.557
X-Spam-Level: 
X-Spam-Status: No, score=-1.557 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_20=-0.74, 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 JtmTWHbG648s for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 05:08:48 -0700 (PDT)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 207DC11E8193 for <ietf@ietf.org>; Tue, 22 Oct 2013 05:08:47 -0700 (PDT)
Received: by mail-la0-f51.google.com with SMTP id ea20so2636744lab.24 for <ietf@ietf.org>; Tue, 22 Oct 2013 05:08: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=vxOZUXJWmeastgMGTGDepmc+Z2+jweOrYPDt9TblkGE=; b=W1VpGejDjBU/QAe93vB27CCYAEvhXTeKe7MITfhJlaD5LctXnbyLPO0lNrUZH6BjAV wsUayoZ8DOIr8F4BL5CF1UO8nXFAQlU9ZhRZYlk4R6U59r7Yp8TkuYkSf/IiR0gvXyET cZqnCFmNBO0IbNZAC2Yh0cf0O0HjDbSjIiLTS2BrzBzzMSS8vTG5ZcZZFKgXn6N0AIL/ iLUZD5+8fiBKDknxYZJLow5hreG12LwFx0cgvSVVHT3hYD6ukh4pBo2sNk6BX61U78zT ciW6A42ziA2vFbCyyTZRoXi5DOqhpKY4zKoYrS1JQlHTW1HQVK+E2b+tF+fuAORaBFMw 5dXw==
MIME-Version: 1.0
X-Received: by 10.152.26.201 with SMTP id n9mr95284lag.52.1382443727229; Tue, 22 Oct 2013 05:08:47 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 22 Oct 2013 05:08:47 -0700 (PDT)
In-Reply-To: <20131022035640.GA7434@mx1.yitter.info>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com> <20131022035640.GA7434@mx1.yitter.info>
Date: Tue, 22 Oct 2013 08:08:47 -0400
Message-ID: <CAMm+LwhvX3YyPritjkV_p7Le0pLVD5_HzuReA=vkpdBpc_4rNg@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=089e0160a706489a8a04e953436b
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, 22 Oct 2013 12:08:50 -0000

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

Combining multiple replies

On Mon, Oct 21, 2013 at 10:47 PM, Michel Py <
michel@arneill-py.sacramento.ca.us> wrote:

> >> Michel Py wrote:
> >> But too many French are entrenched in an anti-American
> >> culture that refuses to learn English.
>
> > Martin Vigoureux wrote:
> > Could you elaborate on how much is "too many"?
>
> One. Pouzin is tilting at windmills. Whatever his agenda is, he's acting
> like a crying baby (or a politician) and expecting to get back some
> visibility by putting the blame on the IETF, (as we all know a
> subversive agent of the "Great Satan" the US). I'm with Stephane here:
> I'm allergic to BS. And I'm with Jorge too: instead of whining, do
> something.
>

And what if that something is get the French government to contribute to a
rival to IETF? Or combine with the governments of Brazil and Mexico to
create a larger anti-IETF?


> Recently on the FRnOG mailing list we had another troll whining about
> the RIPE-NCC documents being in English. I say to both: get a life.
> There is nothing more global than the Internet, and whether you like it
> or not the language is English. Adapt or go do something else.


Don't complain too much about that part of his scheme. The only thing more
likely to doom the aIETF to irrelevance is to adopt ASN.1 as the mandatory
encoding.


On Mon, Oct 21, 2013 at 11:56 PM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote:

> Hi,
>
> On Mon, Oct 21, 2013 at 01:45:00PM -0400, John C Klensin wrote:
>
> > I've got the same reaction to "IDN technical restrictions".  I'm
> > not aware of any significant ones unless one has a desire to
> > use, e.g., symbols, as domain name labels.  And, as far as
> > "visual ambiguities" are concerned, I'd love to know what he
> > proposes
>
> Having just sat through his presentation at the IGF meeting, I think
> what he proposes is roughly, "Change math so that trees don't have a
> single root."  He has just advocated "multiple roots", has asserted
> repeatedly that ICANN controls the entire DNS and that the DNS is
> therefore controlled by the US, and that IDN is not enough because.
>

ICANN is a US company incorporated in California that pays its head close
to a million dollars a year. If Congress passed a law requiring it to do
so, ICANN would drop Palestine and Cuba out of the root. Have you watched
US politics recently? Care to assure me that it won't happen?

If DNSSEC and the rPKI are deployed in their current form ICANN would have
the ability to enforce control, there would be a prohibitive cost to
defections.

There are technical approaches that could preserve the structure of the DNS
naming system but remove ICANN from the equation.

For example, an alternative DNS root supported by a dozen governments could
offer registration direct into root for the same price as currently charged
for a .com. They can direct their national registrars to chain to the new
root. It would strip ICANN's ability to sell domains at $250,000 a time.

France has already driven Europe to develop and deploy its own rival to GPS
at a cost of many billions of dollars. They can do the same for the DNS.



> Happily, we have open-root (perhaps amusingly, available from
> http://open-root.eu/), which is prepared to offer you this
> alternate-root, not-IDN-but-internationalized, all-works-magically
> solution.
>

Do not assume that because a group of crackpots setting up an alternate
root in an underground bunker that doubled as a meths lab failed to set up
an alternative root that all such plans are tilting at windmills. [Yes I
know it was a different breakaway root but the principle is the same]



> I have a great deal of respect for M. Pouzin's contributions to the
> technical development of the Internet.  I'm afraid, however, that I
> can't tell the difference between what he just proposed and a barker's
> proposal for the Medicinal Compound, "efficacious in every case".
>

No, these guys are completely serious and there is an international
movement to bloody the nose of the US in response to the Snowden leaks.

They don't need to know what they are doing technically. The technical part
is easy from their point of view.


And why assume that the correct response to such an effort is to resist it?

I am quite willing to shoot other people's puppies. I think we have to
admit that the current rPKI design is dead as a parrot at this stage.
Putting that on the table merely adds the RIRs to the target list along
with ICANN. I have been pointing out that if ICANN wants independence from
the US then it needs to give up control of the DNSSEC apex signer for
several years.

The question is not what we might have to give up but what we might get in
return. When I wargame the alternatives I see one particular scheme that
any governmental attempt to break from US control is forced to place very
large bets on because making that change is the key to enabling all the
others. This is even more so when we look at routing security than in DNS
space.


The key is IPv6.


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

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

<div dir=3D"ltr">Combining multiple replies<div><br></div><div>On Mon, Oct =
21, 2013 at 10:47 PM, Michel Py=A0<span dir=3D"ltr">&lt;<a href=3D"mailto:m=
ichel@arneill-py.sacramento.ca.us" target=3D"_blank">michel@arneill-py.sacr=
amento.ca.us</a>&gt;</span>=A0wrote:<br>
<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">&gt;&gt; Michel Py wrote:<br>&gt;&gt; Bu=
t too many French are entrenched in an anti-American<br>
&gt;&gt; culture that refuses to learn English.<br><br></div><div class=3D"=
im">&gt; Martin Vigoureux wrote:<br>&gt; Could you elaborate on how much is=
 &quot;too many&quot;?<br><br></div>One. Pouzin is tilting at windmills. Wh=
atever his agenda is, he&#39;s acting<br>
like a crying baby (or a politician) and expecting to get back some<br>visi=
bility by putting the blame on the IETF, (as we all know a<br>subversive ag=
ent of the &quot;Great Satan&quot; the US). I&#39;m with Stephane here:<br>
I&#39;m allergic to BS. And I&#39;m with Jorge too: instead of whining, do<=
br>something.<br></blockquote><div><br></div><div>And what if that somethin=
g is get the French government to contribute to a rival to IETF? Or combine=
 with the governments of Brazil and Mexico to create a larger anti-IETF?</d=
iv>
<div>=A0</div><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">Recently on the FRnOG mailing list we had an=
other troll whining about<br>
the RIPE-NCC documents being in English. I say to both: get a life.<br>Ther=
e is nothing more global than the Internet, and whether you like it<br>or n=
ot the language is English. Adapt or go do something else.</blockquote>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Don&#39;t c=
omplain too much about that part of his scheme. The only thing more likely =
to doom the aIETF to irrelevance is to adopt ASN.1 as the mandatory encodin=
g.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Oct 2=
1, 2013 at 11:56 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;<=
/span> wrote:<br>
<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">Hi,<br>
<div class=3D"im"><br>
On Mon, Oct 21, 2013 at 01:45:00PM -0400, John C Klensin wrote:<br>
<br>
&gt; I&#39;ve got the same reaction to &quot;IDN technical restrictions&quo=
t;. =A0I&#39;m<br>
&gt; not aware of any significant ones unless one has a desire to<br>
&gt; use, e.g., symbols, as domain name labels. =A0And, as far as<br>
&gt; &quot;visual ambiguities&quot; are concerned, I&#39;d love to know wha=
t he<br>
&gt; proposes<br>
<br>
</div>Having just sat through his presentation at the IGF meeting, I think<=
br>
what he proposes is roughly, &quot;Change math so that trees don&#39;t have=
 a<br>
single root.&quot; =A0He has just advocated &quot;multiple roots&quot;, has=
 asserted<br>
repeatedly that ICANN controls the entire DNS and that the DNS is<br>
therefore controlled by the US, and that IDN is not enough because.<br></bl=
ockquote><div><br></div><div>ICANN is a US company incorporated in Californ=
ia that pays its head close to a million dollars a year. If Congress passed=
 a law requiring it to do so, ICANN would drop Palestine and Cuba out of th=
e root. Have you watched US politics recently? Care to assure me that it wo=
n&#39;t happen?</div>
<div><br></div><div>If DNSSEC and the rPKI are deployed in their current fo=
rm ICANN would have the ability to enforce control, there would be a prohib=
itive cost to defections.</div><div><br></div><div>There are technical appr=
oaches that could preserve the structure of the DNS naming system but remov=
e ICANN from the equation.</div>
<div><br></div><div>For example, an alternative DNS root supported by a doz=
en governments could offer registration direct into root for the same price=
 as currently charged for a .com. They can direct their national registrars=
 to chain to the new root. It would strip ICANN&#39;s ability to sell domai=
ns at $250,000 a time.</div>
<div><br></div><div>France has already driven Europe to develop and deploy =
its own rival to GPS at a cost of many billions of dollars. They can do the=
 same for the DNS.=A0</div><div><br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

Happily, we have open-root (perhaps amusingly, available from<br>
<a href=3D"http://open-root.eu/" target=3D"_blank">http://open-root.eu/</a>=
), which is prepared to offer you this<br>
alternate-root, not-IDN-but-internationalized, all-works-magically<br>
solution.<br></blockquote><div><br></div><div><div>Do not assume that becau=
se a group of crackpots setting up an alternate root in an underground bunk=
er that doubled as a meths lab failed to set up an alternative root that al=
l such plans are tilting at windmills. [Yes I know it was a different break=
away root but the principle is the same]</div>
</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
I have a great deal of respect for M. Pouzin&#39;s contributions to the<br>
technical development of the Internet. =A0I&#39;m afraid, however, that I<b=
r>
can&#39;t tell the difference between what he just proposed and a barker&#3=
9;s<br>
proposal for the Medicinal Compound, &quot;efficacious in every case&quot;.=
<br></blockquote></div><br clear=3D"all"><div>No, these guys are completely=
 serious and there is an international movement to bloody the nose of the U=
S in response to the Snowden leaks.=A0</div>
<div><br></div><div>They don&#39;t need to know what they are doing technic=
ally. The technical part is easy from their point of view.</div><div><br></=
div><div><br></div><div>And why assume that the correct response to such an=
 effort is to resist it?</div>
<div><br></div><div>I am quite willing to shoot other people&#39;s puppies.=
 I think we have to admit that the current rPKI design is dead as a parrot =
at this stage. Putting that on the table merely adds the RIRs to the target=
 list along with ICANN. I have been pointing out that if ICANN wants indepe=
ndence from the US then it needs to give up control of the DNSSEC apex sign=
er for several years.</div>
<div><br></div><div>The question is not what we might have to give up but w=
hat we might get in return. When I wargame the alternatives I see one parti=
cular scheme that any governmental attempt to break from US control is forc=
ed to place very large bets on because making that change is the key to ena=
bling all the others. This is even more so when we look at routing security=
 than in DNS space.</div>
<div><br></div><div><br></div><div>The key is IPv6.=A0</div><div><br></div>=
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div></div>

--089e0160a706489a8a04e953436b--

From hallam@gmail.com  Tue Oct 22 06:12:01 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 D4A0211E8170 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 06:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 YtpyZgyx5nBM for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 06:12:01 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1A27511E8392 for <ietf@ietf.org>; Tue, 22 Oct 2013 06:11:54 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id hp15so2164121lab.4 for <ietf@ietf.org>; Tue, 22 Oct 2013 06:11: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=64+CUbnlJ1B9hKpPI21EK97dQu/6tD+IiwojZZXzJ08=; b=d1CnvBEC6gnHpMv4xVqp7vjYTwQoR9HlOdFNUhI5HMAZc9MXE8geLI5rg2G0E+7jdx INdh5xRILaTCybOH1y9yKnPkv6Rb4HXBCb2JgkkIS6NyVZ3mWQa/dc90KM/hYLAQbD8m UPHVis7UCoFxVGi6J2oxNsj5CF5EyPMB8lZuxq/oBUj6YkWZ+KJ/xGNBjeltPbEsnl7+ CrntFpiamhu6/itZIel2p8iFil3OshLO2WCh+1RFhW9QgKf/uDsmdEagVFUYA3Iqf83S 49rwXor29BV6uYfUFKdVF+UWzPedaEDA5s9oIpIOcQZeN5NlZDj3iltSYBuOwfp2Dvj0 lTGA==
MIME-Version: 1.0
X-Received: by 10.112.136.163 with SMTP id qb3mr17124233lbb.14.1382447513885;  Tue, 22 Oct 2013 06:11:53 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 22 Oct 2013 06:11:53 -0700 (PDT)
In-Reply-To: <CAF4+nEHQ_pXS7t=Smf-9QGSj2whXNfYuK8f8FAEmRyhm9HpRCg@mail.gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <CAF4+nEHQ_pXS7t=Smf-9QGSj2whXNfYuK8f8FAEmRyhm9HpRCg@mail.gmail.com>
Date: Tue, 22 Oct 2013 09:11:53 -0400
Message-ID: <CAMm+LwhJ3aN-cfMiNSZ4R1DCfK6U3G6Ttks-dQ6GLM060g8F-A@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=089e0112c73cfc62e604e95424a7
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: Tue, 22 Oct 2013 13:12:01 -0000

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

On Mon, Oct 21, 2013 at 3:02 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> And we see below a perfect illustration of the difficulties that can
> be caused by codification.
>



> - I am very suspicious of the word "professional". Who knows what the
> hell it means? Is the previous sentence "unprofessionally" worded? If
> you think so, good. I typically see "unprofesional" used as a cudgel
> against the strong expression of opinions the critic does not like
> when they have no real counter argument to those opinions.


+1

There is a technique known as 'agenda denial' in which the way a
proposition that can't be answered is addressed is to reject attempts to
raise it.

One of the examples used in the literature has to do with water rights in
parts of Texas. There are existing homes without potable water and
developers wanting to build new homes. The only way the politicians can
achieve their desired outcome is to divide up the two questions so that
these are never seen as alternatives.

So it will never be the right day to talk about water rights for the
existing residents. They will never raise the issue in precisely the
correct form.


I frequently see someone raise an issue repeatedly in the 'professional'
way only to be dismissed or ignored or promised that something will get
done when someone has time. Then they raise the same issue in a more
aggressive way and are in effect told 'because you have behaved
unprofessionally we are never going to address it'.

Which is of course a catch 22 situation.


The salaries of ISOC staff are a completely legit topic as far as I am
concerned. It is a not for profit company and it is paying a very very
large sum to the person in charge.

Who is that person accountable to? Well, I was rather under the impression
it was us.


There are reasons to make anonymous postings and reasons to call ISOC staff
to account. But there are no good reasons to make an anonymous call for
accountability of a named person.



On Mon, Oct 21, 2013 at 2:04 PM, Techno CAT <mars.techno.cat@gmail.com>
> wrote:
> > "Calling someone a troll is an ad hominem. We aren't supposed to do that
> in
> > the IETF. At least, not publicly."[1]
>

No, it is not ad hominem. Ad hominem is an argument of the form 'Hitler was
a vegetarian, therefore vegetarians are NAZIs'

This is an argument of the form 'Hitler was a NAZI' which is a completely
valid statement of fact.




> > "It is rude.
> > It is bullying." [2]
> >
> > HARASSMENT by Brian E Carpenter has been noted for the Legal Record
>

That looks like a threat to me. Threats of legal action are certainly
harassment.


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

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

<div dir=3D"ltr">On Mon, Oct 21, 2013 at 3:02 PM, Donald Eastlake <span dir=
=3D"ltr">&lt;<a href=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@g=
mail.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">And we see below a perfect illustration of t=
he difficulties that can<br>
be caused by codification.<br></blockquote><div><br></div><div>=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
- I am very suspicious of the word &quot;professional&quot;. Who knows what=
 the<br>
hell it means? Is the previous sentence &quot;unprofessionally&quot; worded=
? If<br>
you think so, good. I typically see &quot;unprofesional&quot; used as a cud=
gel<br>
against the strong expression of opinions the critic does not like<br>
when they have no real counter argument to those opinions. </blockquote><di=
v><br></div><div>+1</div><div><br></div><div>There is a technique known as =
&#39;agenda denial&#39; in which the way a proposition that can&#39;t be an=
swered is addressed is to reject attempts to raise it.</div>
<div><br></div><div>One of the examples used in the literature has to do wi=
th water rights in parts of Texas. There are existing homes without potable=
 water and developers wanting to build new homes. The only way the politici=
ans can achieve their desired outcome is to divide up the two questions so =
that these are never seen as alternatives.</div>
<div><br></div><div>So it will never be the right day to talk about water r=
ights for the existing residents. They will never raise the issue in precis=
ely the correct form.</div><div><br></div><div><br></div><div>I frequently =
see someone raise an issue repeatedly in the &#39;professional&#39; way onl=
y to be dismissed or ignored or promised that something will get done when =
someone has time. Then they raise the same issue in a more aggressive way a=
nd are in effect told &#39;because you have behaved unprofessionally we are=
 never going to address it&#39;.</div>
<div><br></div><div>Which is of course a catch 22 situation.</div><div><br>=
</div><div><br></div><div>The salaries of ISOC staff are a completely legit=
 topic as far as I am concerned. It is a not for profit company and it is p=
aying a very very large sum to the person in charge.</div>
<div><br></div><div>Who is that person accountable to? Well, I was rather u=
nder the impression it was us.</div><div><br></div><div><br></div><div>Ther=
e are reasons to make anonymous postings and reasons to call ISOC staff to =
account. But there are no good reasons to make an anonymous call for accoun=
tability of a named person.</div>
<div><br></div><div><br></div><div><br></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"HOEnZb"><div class=3D"h5">
On Mon, Oct 21, 2013 at 2:04 PM, Techno CAT &lt;<a href=3D"mailto:mars.tech=
no.cat@gmail.com">mars.techno.cat@gmail.com</a>&gt; wrote:<br>
&gt; &quot;Calling someone a troll is an ad hominem. We aren&#39;t supposed=
 to do that in<br>
&gt; the IETF. At least, not publicly.&quot;[1]<br></div></div></blockquote=
><div><br></div><div>No, it is not ad hominem. Ad hominem is an argument of=
 the form &#39;Hitler was a vegetarian, therefore vegetarians are NAZIs&#39=
;</div>
<div><br></div><div>This is an argument of the form &#39;Hitler was a NAZI&=
#39; which is a completely valid statement of fact. =A0</div><div><br></div=
><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"HOEnZb"><div class=3D"h5">
&gt; &quot;It is rude.<br>
&gt; It is bullying.&quot; [2]<br>
&gt;<br>
&gt; HARASSMENT by Brian E Carpenter has been noted for the Legal Record<br=
></div></div></blockquote><div><br></div><div>That looks like a threat to m=
e. Threats of legal action are certainly harassment.</div><div><br></div>
</div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>
</div></div>

--089e0112c73cfc62e604e95424a7--

From jeanjour@comcast.net  Tue Oct 22 06:23:57 2013
Return-Path: <jeanjour@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 90F3A11E8390 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 06:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.713
X-Spam-Level: 
X-Spam-Status: No, score=0.713 tagged_above=-999 required=5 tests=[AWL=-1.150,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  MANGLED_FORM=2.3, 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 nm0HzbHlvZ8Z for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 06:23:51 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id ABF3E11E837C for <ietf@ietf.org>; Tue, 22 Oct 2013 06:23:47 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta01.westchester.pa.mail.comcast.net with comcast id gCLW1m0031YDfWL51DPm39; Tue, 22 Oct 2013 13:23:46 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta20.westchester.pa.mail.comcast.net with comcast id gDPm1m00C14WE023gDPmVf; Tue, 22 Oct 2013 13:23:46 +0000
Mime-Version: 1.0
Message-Id: <a06240890ce8c2a6ed20f@[10.0.1.3]>
In-Reply-To: <20131022064340.GB7901@mx1.yitter.info>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com> <20131022035640.GA7434@mx1.yitter.info> <20131022064340.GB7901@mx1.yitter.info>
Date: Tue, 22 Oct 2013 09:16:41 -0400
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382448226; bh=T7RJ0WlmDolUw1JKxXrxZg38khZOiZCfwjYZ60zG6w8=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=AjX9zqfx2PYTh8LNlBlEKjI2qeSrlbawwKbNcXs0iB29/XHjVG8fVBfrLTKSQN/uq U5aMH2aigqNCXCmAYPgGwrpvTSJ1QTZNLPjYDDX+cGp+tss359J/z4Jgvva+mJVdiJ +hpE5Rg7s7TKxncl7x5B6vA1Vji+naZyuV1v0mvoe6sjuL6Ix9S2XOfg9AVVQwzhpX V4vM18XhSzQrSj5TK+dqoKDkh8gsGgR3tj1SSnot9U1M15sLW3fS/2QDNwy7J8qedg uQALaLWMTgDoRNwsqkV1O7skfnZaycj7f+nJ2lSdv3g0aiWSeb94Ms6gjZnjY3mamz 0M99DQ/m7jLfg==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 13:23:57 -0000

I don't always agree with Louis, and he isn't always right (but who 
is?), but I can guarantee that the ensuing discussion with him is 
always enlightening.  ;-)

He has been known for riling feathers of the status quo for a very long time.


At 2:47 AM -0400 10/22/13, Andrew Sullivan wrote:
>I know, I know, responding to myself, but a follow-up conversation
>makes me think I should be a little more charitable.
>
>On Mon, Oct 21, 2013 at 11:56:41PM -0400, Andrew Sullivan wrote:
>
>>  He has just advocated "multiple roots"
>
>This turns out to be a consequence of his (quite correct) observation
>that, for a user, the full context isn't necessary.  We already have
>this notion in the DNS -- that's what the search path function is for.
>M. Pouzin thinks this ought to be much more ubiquitous, in much the
>way that you don't have to dial the full phone path (or anyway, not
>everywhere) every time you call a local number.  From this, he gets
>alternate roots.  So he's not simply being a crank, though I don't
>fully understand how he gets to the conclusion he's reached.
>
>Now, having corrected my previous uncharitable description, I suggest
>that if people want to discuss DNSng, we do it on another list.
>
>Best,
>
>A
>
>--
>Andrew Sullivan
>ajs@anvilwalrusden.com


From barryleiba.mailing.lists@gmail.com  Tue Oct 22 07:06:40 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 5E8A111E83D6 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.786
X-Spam-Level: 
X-Spam-Status: No, score=-101.786 tagged_above=-999 required=5 tests=[AWL=0.192, 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 C7VkiIwUYHdq for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:06:37 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id CCB1D11E83D4 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:06:36 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id hp15so2233843lab.4 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:06:34 -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:message-id:subject :from:to:cc:content-type; bh=aR9brgN2SMQaFAjboIv9tlfD4Lofn/vjH45no1N240M=; b=G2lw7EBaeJ+o2mzesPmaYAUgDP+rDlC57aoUtGgVwnzSDU/+IptzM7GRgdN9avD8j0 XjwtQoy8M6op8ZQ6BUH5z4e6PlZ/gMNBv6ea3wxtpFXYRIOnsNHH4OblAaOiArJAZywe AYtnzWWIBXG7/KvkV5iLypRrvZKBqpRCZo5SO48AqSawAoscEzoo8U/bIRg+Ia3dmQuG 1m7dUGFwWYZvGlYaPnJojbYvR7zaemXqvRWVx31EfmUzLItowQz/XOxD/RKFUnxAX23W KMChxT/gEmiuQLzoslzhigmf0+S37YBXDHleX0el6B+fAjHTP7D1g5IM/lPkkU2D5ptp 2AoQ==
MIME-Version: 1.0
X-Received: by 10.152.170.166 with SMTP id an6mr18164294lac.20.1382450794720;  Tue, 22 Oct 2013 07:06:34 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.134.232 with HTTP; Tue, 22 Oct 2013 07:06:34 -0700 (PDT)
In-Reply-To: <CAMm+LwhJ3aN-cfMiNSZ4R1DCfK6U3G6Ttks-dQ6GLM060g8F-A@mail.gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <CAF4+nEHQ_pXS7t=Smf-9QGSj2whXNfYuK8f8FAEmRyhm9HpRCg@mail.gmail.com> <CAMm+LwhJ3aN-cfMiNSZ4R1DCfK6U3G6Ttks-dQ6GLM060g8F-A@mail.gmail.com>
Date: Tue, 22 Oct 2013 10:06:34 -0400
X-Google-Sender-Auth: sbKvR9zbP9REHEUyiUcLzKixqng
Message-ID: <CAC4RtVCPKF1D1d4iB1r9jQ0QpEdyWPS9XF-v_-y1TqipvossCA@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Barry Leiba <barryleiba@computer.org>
To: Phillip Hallam-Baker <hallam@gmail.com>
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: Tue, 22 Oct 2013 14:06:40 -0000

>> "Calling someone a troll is an ad hominem. We aren't supposed to do that
>> in the IETF. At least, not publicly."[1]
>
> No, it is not ad hominem. Ad hominem is an argument of the form 'Hitler was
> a vegetarian, therefore vegetarians are NAZIs'

No, that's not true at all.  Your example is a different logical fallacy.

"Hitler was a vegetarian.  His idea is, therefore, wrong, because
vegetarians don't have good ideas," is an ad hominem argument --
attacking the person, rather than the content.

"This person is a troll, so we should pay no attention to what he
says," is, absolutely, an ad hominem argument.  Whether or not we
absolutely prohibit ad hominem arguments is something I'll dodge for
right now.  But let's be sure we understand the difference between
these:

1. "I don't like you, and your argument is wrong because [response
that addresses the issues]."  This might include an inappropriate
personal attack, but it's not an ad hominem argument.

2. "I don't like you, so your argument is not worth listening to."
This *is* an ad hominem argument, whether or not it includes name
calling or other unflattering characterizations.

Barry

From Ted.Lemon@nominum.com  Tue Oct 22 07:15: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 488A611E83DF for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.293
X-Spam-Level: 
X-Spam-Status: No, score=-106.293 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, J_CHICKENPOX_21=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 RNs3EuupF-Ua for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:15:25 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id EC3A411E83DA for <ietf@ietf.org>; Tue, 22 Oct 2013 07:15:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUmaIc5eWVDZa4OA3ULf8HeX7P3aeW2IY@postini.com; Tue, 22 Oct 2013 07:15:23 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 813761B82E4 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:15:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 709E5190052; Tue, 22 Oct 2013 07:15: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.03.0158.001; Tue, 22 Oct 2013 07:15:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbxVzZsUK86MhUyC7IRlHFizLZoAeVGAgABzWwCAAE9xAA==
Date: Tue, 22 Oct 2013 14:15:13 +0000
Message-ID: <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org>
In-Reply-To: <20131022093052.GF9517@thunk.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: <F6A6D352B6232840B87A0BDB9FCAC446@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, 22 Oct 2013 14:15:31 -0000

On Oct 22, 2013, at 5:30 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> These are indeed the critical questions.  It's easy to have a
> statement about what might be considered "harassment".  If however
> someone tries to use this as a debating tactic during a particularly
> robust technical discussion, what happens next?  Does it get raised to
> the wg chair?  If the wg chair says, that's just a robust technical
> discussion, does it get escalated to ombudsman?  If the ombudsman
> says, "nope, sorry", does it get escalated to the AD and IESG, and do
> they then have to write up carefully crafted appeal documents which
> will no doubt suck up huge amounts of their time?

The path is harassment->ombudsbeing, not harassment->wg chair.  I would exp=
ect the ombudsperson to push back at this point unless something inappropri=
ate was said.   If someone says "that's a stupid idea, because FOO" and "be=
cause FOO" is valid, then it would be appropriate for the ombudsperson to s=
ay to the offending party, "you know, you didn't need to say that was a stu=
pid idea=97all you needed to say was 'because FOO.'".   OTOH, if the offend=
ing party said "I'm going to cut off a deer's head and leave it in your ref=
rigerator if you don't stop denying that FOO," then that would elicit a dif=
ferent response.

> Should there be any cost to someone who tries to escalate disputes via
> the anti-harassment process, when it is determined afterwards that it
> is not harassment?  If we do, then it might deter valid plaintiffs
> from coming forward.  If we don't, how do we deter people who might
> try to abuse this process from using it to that end?  Historically, we
> certainly had people who have been rather enthusiastic about using
> whatever appeal processes we've made available.

I think if someone develops a history of engaging in this kind of tactic, i=
t might become grounds for banning from mailing list discussion, and there =
might be appeals, and that would suck.   But that's really the status quo n=
ow, so it's not like this changes anything.   It's unlikely that it would b=
e appropriate to respond to a single accusation of harassment that the ombu=
dsperson does not agree is harassment with any kind of censure.

> One hint --- we should definitely try to pursuade folks not to try to
> get a decision based on the specific facts of a particulate dispute
> via the court of public opinion:
>=20
>       "Adria Richards, PyCon, and How We All Lost"
>       http://amandablumwords.wordpress.com/2013/03/21/

What happened at PyCon is a really strong argument for having an escalation=
 path other than twitter.   We can't stop participants from doing stuff lik=
e this, but hopefully the lesson has been learned that this is a bad tactic=
 for dealing with behavior in meetings that one finds inappropriate.   So t=
here should be an incentive to try the ombudsperson tactic first, and then =
escalate to twitter only if that fails.


From packetgrrl@gmail.com  Tue Oct 22 07:16:47 2013
Return-Path: <packetgrrl@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 7A86611E83DB for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:16:47 -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 Fl1JkgRIC5RU for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:16:46 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id B21D111E83DA for <ietf@ietf.org>; Tue, 22 Oct 2013 07:16:43 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wy17so5704347pbc.39 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:16:43 -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:message-id:subject :from:to:cc:content-type; bh=WNzjIXunTmExoqY9b6gqiEKBT4qftqb4dds6O8FOSHE=; b=o9de4LWJKrlsjPkRhbcNtqcxYD0lkiydUrGGKPut7f2lZ2X95+07C0i8cCL+yVAXac 8J6L2AqFTHk+HMKBtLY9DOL3jlYpKjZrrtKJA9medZCKxX6fAZmxDHZJiyMhdkHRZixS vzwrkP2bq9noENi4Vq0JOV1OrOkMIS7oB5uPXKEaIlIbh//Hcm/wVEhRGnYONVLBoZyC 0KaJ2QRXjQrp2K3Fk1eQNKUnfl3MHycjllESpcjBQZ+xlphvKKRN7pHAi3ulFKSHFCRJ im2OKNzsmicFRn6wvfCKgyIIXoWOnHSQBJ8NcSjuzmfXcwK+CACMwe1W02xlX+wTt8Li Mjcw==
MIME-Version: 1.0
X-Received: by 10.68.134.98 with SMTP id pj2mr23174102pbb.110.1382451403304; Tue, 22 Oct 2013 07:16:43 -0700 (PDT)
Sender: packetgrrl@gmail.com
Received: by 10.70.98.232 with HTTP; Tue, 22 Oct 2013 07:16:43 -0700 (PDT)
In-Reply-To: <52662CE2.1020709@gmail.com>
References: <52662CE2.1020709@gmail.com>
Date: Tue, 22 Oct 2013 08:16:43 -0600
X-Google-Sender-Auth: JhI2uFAaF3L1tYL43DC0bAVBaVw
Message-ID: <CAMvf=7YrQuU5fARSFQFC-1_hZ7C53fUn_wT1yw82hQdb4JAn7g@mail.gmail.com>
Subject: Re: question: ISOC Panel at IETF88 in Vancouver?
From: CJ Aronson <cja@daydream.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b10cf4dd035cf04e9550cb5
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: Tue, 22 Oct 2013 14:16:47 -0000

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

http://www.internetsociety.org/internet-society-briefing-panel-ietf-88

Just found it.

----Cathy


On Tue, Oct 22, 2013 at 1:44 AM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

> Hello IETFers,
>
> Is there going to be an ISOC Panel this time at IETF 88 in Vancouver?
>
> Alex
>
>

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

<div dir=3D"ltr"><a href=3D"http://www.internetsociety.org/internet-society=
-briefing-panel-ietf-88">http://www.internetsociety.org/internet-society-br=
iefing-panel-ietf-88</a><br><div><br></div><div>Just found it. =A0</div><di=
v><br>
</div><div>----Cathy</div></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Tue, Oct 22, 2013 at 1:44 AM, Alexandru Petrescu <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:alexandru.petrescu@gmail.com" target=3D=
"_blank">alexandru.petrescu@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">Hello IETFers,<br>
<br>
Is there going to be an ISOC Panel this time at IETF 88 in Vancouver?<br>
<br>
Alex<br>
<br>
</blockquote></div><br></div>

--047d7b10cf4dd035cf04e9550cb5--

From melinda.shore@gmail.com  Tue Oct 22 07:37: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 8FA8611E83AC for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  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 NEM9oJogLRxs for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 07:37:12 -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 7508311E83D8 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:36:39 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id un1so2123503pbc.5 for <ietf@ietf.org>; Tue, 22 Oct 2013 07:36:36 -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=72WHIssZKm0MdKN6t0o+UldnJ4htgytzTe8qkgA8GLk=; b=QgzC57qED7xDvRYghoYZq41hpW16sfIeu1GPT6wa6xyImh1RxoObe7/gNviY+zdfRi 9WytSHHy0D9zqAApkEciEXSHN6lKJQv4+jXtF4u5jOCuMCCA0uuE2K3I4dqxeido1bjq vaIPdVZw4TOrCWYTKnrKWP6uFjc+H4MPdgPMk1azggI78xupLStrbB3JHO8ju73SsDno Y9CflKgOB8YlzVay6dQxtvYYa0Bs/geZVRow4AzsCX490ETDqRstZ6SWDcswbhjG3zeZ H6QW8LnmPxdnwHl1I0p4IVyCC4+OK4d2tWqTA7dq84r4Mjasv/ZhvYAcpA+3A44wtd23 ySiw==
X-Received: by 10.68.217.129 with SMTP id oy1mr23207698pbc.23.1382452596245; Tue, 22 Oct 2013 07:36:36 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id wd6sm33975274pab.3.2013.10.22.07.36.33 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 07:36:35 -0700 (PDT)
Message-ID: <52668D6F.6060006@gmail.com>
Date: Tue, 22 Oct 2013 06:36: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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF Anti-Harassment Policy
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
In-Reply-To: <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
Content-Type: text/plain; charset=windows-1252
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, 22 Oct 2013 14:37:29 -0000

On 10/22/13 6:15 AM, Ted Lemon wrote:
> What happened at PyCon is a really strong argument for having an
> escalation path other than twitter.   

That is a very, very, very good point.

Melinda


From alexandru.petrescu@gmail.com  Tue Oct 22 08:06:56 2013
Return-Path: <alexandru.petrescu@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 C8C5611E84AE for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.194
X-Spam-Level: 
X-Spam-Status: No, score=-10.194 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HELO_EQ_FR=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 snLDz+9ggqAL for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:06:51 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 5B93D11E81CF for <ietf@ietf.org>; Tue, 22 Oct 2013 08:06:51 -0700 (PDT)
Received: from nephilia.intra.cea.fr (nephilia.intra.cea.fr [132.166.88.33]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r9MF6mv0006030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Oct 2013 17:06:48 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by nephilia.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r9MF6mYp001694;  Tue, 22 Oct 2013 17:06:48 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r9MF6lsu016718; Tue, 22 Oct 2013 17:06:48 +0200
Message-ID: <52669487.2070507@gmail.com>
Date: Tue, 22 Oct 2013 17:06:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: CJ Aronson <cja@daydream.com>
Subject: Re: question: ISOC Panel at IETF88 in Vancouver?
References: <52662CE2.1020709@gmail.com> <CAMvf=7YrQuU5fARSFQFC-1_hZ7C53fUn_wT1yw82hQdb4JAn7g@mail.gmail.com>
In-Reply-To: <CAMvf=7YrQuU5fARSFQFC-1_hZ7C53fUn_wT1yw82hQdb4JAn7g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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: Tue, 22 Oct 2013 15:06:56 -0000

Le 22/10/2013 16:16, CJ Aronson a écrit :
> http://www.internetsociety.org/internet-society-briefing-panel-ietf-88
>
> Just found it.

Thanks, IPv6 success deployments is of much interest.

Alex

>
> ----Cathy
>
>
> On Tue, Oct 22, 2013 at 1:44 AM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com <mailto:alexandru.petrescu@gmail.com>> wrote:
>
>     Hello IETFers,
>
>     Is there going to be an ISOC Panel this time at IETF 88 in Vancouver?
>
>     Alex
>
>



From stephen.farrell@cs.tcd.ie  Tue Oct 22 08:15:02 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 9F31311E84D4 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level: 
X-Spam-Status: No, score=-102.676 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 HdSkB2oK0q9G for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:14:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D652B11E84C2 for <ietf@ietf.org>; Tue, 22 Oct 2013 08:14:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3F1DBBE39; Tue, 22 Oct 2013 16:14:40 +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 zwdL+WixNWm0; Tue, 22 Oct 2013 16:14:40 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1F40EBE38; Tue, 22 Oct 2013 16:14:40 +0100 (IST)
Message-ID: <52669661.1090705@cs.tcd.ie>
Date: Tue, 22 Oct 2013 16:14:41 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com>	<526444E9.4050308@dcrocker.net> <5265730B.9080208@mti-systems.com>
In-Reply-To: <5265730B.9080208@mti-systems.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 15:15:03 -0000

On 10/21/2013 07:31 PM, Wesley Eddy wrote:
> To the question of splitting the document reviews from the working
> group "management" tasks: When I was an AD, I found the document
> reviews to be very useful in figuring out what was going on in other
> areas that might be related to working groups in the area I was
> responsible for, and in calibrating expectations for documents to
> come out of my area's working groups.
> 
> If the document review and working group management roles were
> split, I don't know how the AD doing working group management
> would maintain broader awareness to avoid too much overlap or
> conflict between WGs, or to know what the relevant things to
> look for are in a MIB document, requirements document, etc. that
> their WGs are producing, before sending them to IETF LC.  Certainly
> they could find other ways to do this than reviewing every document
> and sitting in the entire telechat though ...

I think that's a point worth making. The purpose of the
IESG is not to educate ADs, but one side-effect of the
document review is just that, and it does help - I think
I'm less of a dummy about stuff that goes on elsewhere
in the IETF as a result, and I think that an IESG that's
more educated in that way is likely to be a lot better
on the whole.

S.

From dhc@dcrocker.net  Tue Oct 22 08:18:20 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 5B52F11E83C7 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:18: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 0dunX-HWFOUC for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:18:15 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6D72711E81AC for <ietf@ietf.org>; Tue, 22 Oct 2013 08:18:15 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9MFI2dR022299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Oct 2013 08:18:07 -0700
Message-ID: <52669723.2060705@dcrocker.net>
Date: Tue, 22 Oct 2013 11:17:55 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Wesley Eddy <wes@mti-systems.com>
Subject: Re: Separate ADs roles from IESG
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com>	<293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com>	<5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]>	<52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com>	<526444E9.4050308@dcrocker.net>	<5265730B.9080208@mti-systems.com> <52669661.1090705@cs.tcd.ie>
In-Reply-To: <52669661.1090705@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]); Tue, 22 Oct 2013 08:18:07 -0700 (PDT)
Cc: IETF Discuss <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, 22 Oct 2013 15:18:20 -0000

On 10/22/2013 11:14 AM, Stephen Farrell wrote:
> I think that's a point worth making. The purpose of the
> IESG is not to educate ADs, but one side-effect of the
> document review is just that, and it does help -


Yes, but...

It's late-stage education.

For doing better cross-area coordination, ADs need to know about 
activities during their formative stage, not when the activities are 
finished.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Tue Oct 22 08:25:57 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 E0F5911E8461 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 IpybfVoTfLJH for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 08:25:51 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 40E2B11E849A for <ietf@ietf.org>; Tue, 22 Oct 2013 08:25:48 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUmaY/J2ubqfpBPMR8ftRUEZupjt8rJD+@postini.com; Tue, 22 Oct 2013 08:25: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 D94901B82E5 for <ietf@ietf.org>; Tue, 22 Oct 2013 08:25:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 BEB6E190052; Tue, 22 Oct 2013 08:25:47 -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.03.0158.001; Tue, 22 Oct 2013 08:25:47 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Separate ADs roles from IESG
Thread-Topic: Separate ADs roles from IESG
Thread-Index: AQHOzYjKtJAPJYKjHUCjNa9TyTzrqZn9/9yAgAAQXACAAAiKAIAAWX+AgAAEcgCAABL4gIABaCuAgAFbTYCAAADngIAAAjOA
Date: Tue, 22 Oct 2013 15:25:47 +0000
Message-ID: <DD34ABB0-5000-4FC9-BAC2-881662CC2C6E@nominum.com>
References: <CADnDZ88vdtnSVRuA3-TEnCELYSMfu+zA2ya+_Gr80809L7hK9w@mail.gmail.com> <293D8084-3532-4632-AD20-014C66A4E9FE@checkpoint.com> <5263DF08.4090304@pi.nu>	<892B13B7BF164B38A8DB3793@[192.168.1.128]> <52643145.8010504@gmail.com>	<52643500.3010406@joelhalpern.com> <526444E9.4050308@dcrocker.net>	<5265730B.9080208@mti-systems.com> <52669661.1090705@cs.tcd.ie> <52669723.2060705@dcrocker.net>
In-Reply-To: <52669723.2060705@dcrocker.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="iso-8859-1"
Content-ID: <0549C3815245434CB3394BE148E674D1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 15:25:58 -0000

On Oct 22, 2013, at 11:17 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> For doing better cross-area coordination, ADs need to know about activiti=
es during their formative stage, not when the activities are finished.

No problem.   We'll just need to add some more to the AD review load to add=
ress this.   :)


From conte@isoc.org  Tue Oct 22 09:17:17 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 349F911E81B3 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 09:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.054
X-Spam-Level: 
X-Spam-Status: No, score=-103.054 tagged_above=-999 required=5 tests=[AWL=0.544, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 Gviocb65NlUo for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 09:17:12 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0235.outbound.protection.outlook.com [207.46.163.235]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD4B11E81AB for <ietf@ietf.org>; Tue, 22 Oct 2013 09:17:08 -0700 (PDT)
Received: from BLUPR06MB019.namprd06.prod.outlook.com (10.242.190.148) by BLUPR06MB018.namprd06.prod.outlook.com (10.242.190.141) with Microsoft SMTP Server (TLS) id 15.0.785.10; Tue, 22 Oct 2013 16:17:05 +0000
Received: from BLUPR06MB019.namprd06.prod.outlook.com ([169.254.4.126]) by BLUPR06MB019.namprd06.prod.outlook.com ([169.254.4.126]) with mapi id 15.00.0785.001; Tue, 22 Oct 2013 16:17:05 +0000
From: Steve Conte <conte@isoc.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Applications open for ISOC Fellowship to IETF 89 (London)
Thread-Topic: Applications open for ISOC Fellowship to IETF 89 (London)
Thread-Index: AQHOz0IlkSiDHrepDES2pVfOTEW7dw==
Date: Tue, 22 Oct 2013 16:17:04 +0000
Message-ID: <CE8BF30E.1C33F%conte@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.170.169.250]
x-forefront-prvs: 00073DB75F
x-forefront-antispam-report: SFV:NSPM; SFS:(13624006)(71364002)(189002)(199002)(80022001)(47976001)(4396001)(19580395003)(81542001)(47736001)(49866001)(65816001)(16236675002)(50986001)(83072001)(83322001)(19580405001)(74876001)(80976001)(66066001)(76796001)(76786001)(54316002)(77982001)(85306002)(56776001)(56816003)(77096001)(36756003)(74662001)(74502001)(47446002)(76482001)(15975445006)(81686001)(74366001)(69226001)(31966008)(76176001)(81816001)(59766001)(54356001)(63696002)(46102001)(81342001)(79102001)(53806001)(74706001)(15202345003)(51856001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR06MB018; H:BLUPR06MB019.namprd06.prod.outlook.com; CLIP:76.170.169.250; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: multipart/alternative; boundary="_000_CE8BF30E1C33Fconteisocorg_"
MIME-Version: 1.0
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: Tue, 22 Oct 2013 16:17:17 -0000

--_000_CE8BF30E1C33Fconteisocorg_
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 IETF 89=
 in London, England:

* IETF 89, March 02-07, 2014, London, England

Information and links to apply can be found at: http://www.internetsociety.=
org/ietf-fellows

Fellowship applications are due by 15 November 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, Goog=
le, Microsoft, Verisign, and NBC/Universal.

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_CE8BF30E1C33Fconteisocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <C165F1A3B9AA5B418A0F2DFF5F0DEB4B@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 IE=
TF 89 in London, England:</div>
<div><br>
</div>
<div>* IETF 89, March 02-07, 2014, London, England</div>
<div><br>
</div>
<div>Information and links to apply can be found at: http://www.internetsoc=
iety.org/ietf-fellows</div>
<div><br>
</div>
<div>Fellowship applications are due by 15 November 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,=
 Google, Microsoft, Verisign, and NBC/Universal.</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>
<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_CE8BF30E1C33Fconteisocorg_--

From dhc@dcrocker.net  Tue Oct 22 10:24:08 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 BA13611E83C0 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 10:24:07 -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.000,  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 tF9O1Yhk2AWK for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 10:24:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id ADD4811E81D1 for <ietf@ietf.org>; Tue, 22 Oct 2013 10:23:59 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9MHNtkN025383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Oct 2013 10:23:59 -0700
Message-ID: <5266B4A4.9020301@dcrocker.net>
Date: Tue, 22 Oct 2013 13:23:48 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com>
In-Reply-To: <m21u3d5zvo.wl%randy@psg.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, 22 Oct 2013 10:23:59 -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: Tue, 22 Oct 2013 17:24:08 -0000

On 10/22/2013 7:06 AM, Randy Bush wrote:
> as the ietf is legally f(isoc),


The IETF is not legally ISOC.

They are two, independent organizations, with a collection of 
collaborative arrangements.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From randy@psg.com  Tue Oct 22 10:50:38 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 DFF5D11E8404 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 10:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114,  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 8HC9o5ylwXIK for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 10:50:37 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 6967F11E81C1 for <ietf@ietf.org>; Tue, 22 Oct 2013 10:50:25 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VYg5x-0001en-NC; Tue, 22 Oct 2013 17:50:19 +0000
Date: Tue, 22 Oct 2013 19:50:15 +0200
Message-ID: <m2ob6h42lk.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dave Crocker <dhc@dcrocker.net>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <5266B4A4.9020301@dcrocker.net>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@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 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, 22 Oct 2013 17:50:38 -0000

>> as the ietf is legally f(isoc),
> The IETF is not legally ISOC.

you are correct.  legally, it is a function of isoc.  sorry about the
notational shortening.

randy

From fluffy@iii.ca  Tue Oct 22 10:56:46 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 CC2A711E81ED; Tue, 22 Oct 2013 10:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level: 
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=-0.044, 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 897YI583Gt3j; Tue, 22 Oct 2013 10:56:36 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 9C81411E81F5; Tue, 22 Oct 2013 10:56:35 -0700 (PDT)
Received: from [192.168.4.101] (unknown [128.107.239.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0119650A88; Tue, 22 Oct 2013 13:56:30 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com>
Date: Tue, 22 Oct 2013 11:58:24 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org" <dhcwg@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, 22 Oct 2013 17:56:47 -0000

Ted, one of the hallmarks of a successful protocol is people use it for =
things it's designers think are an awful idea and it ends up working =
fairly well for them. I think the heart of the issue here is that you =
don't believe that DHCP should be used to configure application-layer =
services, like SIP.  I disagree - I think the text in the draft about =
when to use this is about right=20

   It is necessary to evaluate whether it is
   reasonable for this parameter to be under the control of the
   administrator of whatever network a client is attached to at any
   given time

Furthermore, I don't understand what definition of an application layer =
service you have. Are these application layer services  DNS? NTP? SIP?=20=


I've build small battery powered sensors that use DHCP, DNS and reports =
environmental measurements periodically to a server and have a very good =
handle on the power usage of these devices. I've done ones that use =
ethernet and  802.15.4, (and also ones that don't use DNS or DHCp but =
run over satellite links). On those networks, I have concrete =
measurements that indicate for that system you are wrong about DNS =
making a significant difference to battery life. I realize there might =
be other applications where it does make a difference but so I'm having =
a hard time imagine such an system. The reason why is simple, the bulk =
of traffic a sensor sends over a 30 day period is mostly sensor data not =
DHCP or DNS.=20

On the flip side, for SIP phones we have seen that the level of =
indirection form DNS really helps make the operational issues easier. =20=


I think the draft should not say that IPs are preferred over FQDNs. I =
think it should say the choice of IP or FQDNs depends on the =
applications and factors that should be considered are size, power, =
extra RTT, if a DNS stack is available, code size, and so on. But also =
point out some of the operational management advantages of DNS.=20

Really we are talking about if you have a parameter in some new protocol =
X to control, this BCP is taking the opinion that it knows more about =
protocol X than the protocol X WG and that it thinks the parameter =
should be an IP not FQDN. I think this is wrong, DHCP should deal with =
how transport the configuration parameter that protocol X needs and if =
that is an IP or FQDN is probably a choice best left to experts of =
protocol X.  Heck, I'll go a scope further, I think it is not in charter =
of the DHC working to determine if IP or FQDN are best to configure a =
parameter in some future protocol done by some other WG. =20

bit more inline =85

On Oct 10, 2013, at 9:41 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Oct 9, 2013, at 11:49 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>>> If this argument were correct, we'd expect to see major O.S. vendors =
supporting the NTP option, but we don't=97instead, it's something that =
can be configured in the UI for situations like the one you describe, =
and that otherwise is defaulted to the preconfigured value, which of =
course can be updated when the operating system is updated.
>>=20
>> Right - I am certainly more focused on the devices that don't have an =
administrator that can configure them locally.=20
>=20
> This is great, but that's not all devices.   And devices of this type =
often wind up being very vulnerable to attack precisely because no =
usable escape mechanism is offered.   DHCP may be your only choice for =
configuring such a device, but it's a really lousy choice.

Louse choice? What exactly would you propose that would work better ?

>=20
>>> So where I would expect to see the NTP option used is in devices =
that don't _have_ user interfaces.   Your IP phone might be such a =
device.   I suspect the bias you have toward using a DHCP option has a =
lot to do with where these devices are typically installed: in corporate =
environments.
>>=20
>> Agree I am focused on the VoIP stuff but it is both SP and =
enterprises.=20
>>=20
>>> I don't even know if I could get one to use at home, or if it would =
work.
>>=20
>> They work in residential deployments (which might be a bit different =
than you mean by home) and DHCP can provide some very critical services =
for them. For example rfc5223 is a DHCP options that provides the LOST =
server that provides the mapping to locations that can be used for E911 =
calls and is applicable to residential.=20
>=20
> I challenge you to find a single commonly-used home gateway that =
supports this RFC, and that is not VoIP-specific.   If one does, it's =
hard to see any reason why it matters whether the IP address of the E911 =
location service protocol is delivered directly or through an FQDN.

There are large SPs in some countries that rolled this out across the =
NATs they provide customers. But this argument seems way off the topic =
of one should prefer use of IP addresses over FQDNs

>=20
>> Sure I believe you about what DHCP servers are capable of doing =
(which I will note might be different than how they are commonly =
deployed). I was talking about the issue here of from a protocol design =
point of view, one should prefer the use of an IP address or FQDN in the =
DHCP option for a case like this.=20
>=20
> Commonly deployed by whom?   The ISC DHCP server supported the =
functionality that I'm describing in 1997.   Nominum's DHCP server =
supported it on first release.   Cisco's server supported it back when =
it was still a separate company called American Internet, at least as =
early as 1997.   The only commonly-used server that I think does not =
support this functionality is Microsoft's.   I suppose some enterprise =
environments might use this server, which might explain why you are =
assuming that behavior, but we shouldn't decide how to do things based =
on a single implementation that, if it operates in the way you describe, =
is IMHO broken.

You are off in the weeds here - I never disagreed that there were not =
DHCP servers that implemented this.=20

>=20
>> When I said "move" I'm talking the roughly the same thing as you mean =
here of bring up a new service. So lets take a VoIP provider like AT&T =
or a large enterprise like GE. Let say that have a server called =
time.ge.com in DNS. Figuring out the TTL for that is pretty easy. =
Changing it to reduce down around the time of the move is pretty easy as =
you can chance it one place and DNS sync it to the other DNS servers. =
Now lets consider doing the same thing with DHCP. How many DHCP server =
do you think either of theses have? Consistent tools to manage all them =
from a central location? The admin know when they are moving servers =
they need to deal with the DNS - but do they all even remember to update =
the DHCP?
>>=20
>> The we have the issue of NATs that act as DHCP clients, get an =
option, then re-advertise that option as a DHCP server on the private =
side. I realize that if they advertise it for longer on the private side =
than the lease was valid on the public side is just really broken, but =
none the less I'm sure no one will be shocked to find out there are =
broken NATs.=20
>>=20
>> I've been involved with deployments bitten by every one of of the =
above. That make me prefer FQDN unless it is a case where DNS might not =
be supported or not operational, or a case where the time / power of the =
DNS query makes a significant difference to the  system.=20
>=20
> Right, and I think I already said that (a) SIP is a bad example of a =
use case for DHCP, because it's a node-specific service, not a =
network-specific service, and (b) it's probably fine, if you must use =
DHCP to configure SIP, to use an FQDN, as I already said several =
messages back.

Sure, and why does that same argument not hold for configuring similar =
services which is what I complained about in the draft.=20

>=20
>> I thought about what you wrote here for a long time. I suspect that =
is part of the issue is that people such as myself that are not DHCP =
experts don't know what services are not appropriate to use it for. We =
see it as a hammer and we are off pounding nails, or screws. I view SRV =
as an OK way to control load balancing across a set of servers that have =
different capacity - often due to be deployed on faster computers over =
time. Why would a service with that property not be someone one would =
use DHCP for.=20
>=20
> Well, for example, would you use SRV records to do load balancing on a =
DNS server?   An NTP server?   A router (which in the context of DHCPv6 =
probably means an AFTR)?   I think you would not.

Look, I am not arguing that one should not us IP address in some cases. =
I'm arguing that there are equally good cases where one should use FQDN. =
I realize they are not popular with the layer 2/3 folks but they are =
very popular with the application layer folks because of the flexibility =
and easy of managment they provide.=20

>=20
>>> I would argue that if it makes any sense at all for there to be a =
SRV record, that's a strong argument against using DHCP to configure =
that service.  =20
>>=20
>> tell me more - this one I did not get.=20
>=20
> SRV records are normally used for application-layer services, like =
SIP, which I don't think should be configured with DHCP.   Similarly, =
would you use DHCP to configure the address of an HTTP server? :)

This seems to be the heart of it. You don't think this should be used =
for application layer services but I don't think that ship sailed long =
long ago.=20

>=20
>>> Right, and at the moment they almost certainly have their NTP server =
FQDNs hard-coded, and it works, and you don't even know it's working =
this way, because it's a solid solution in a home network.  The issue =
with DNS on constrained devices is that it's another packet round trip, =
and packets burn battery.  =20
>>=20
>> Give me an example where that makes a difference. When I look at this =
as the power to do a DNS query amortized over the lifetime of the lease =
or uptime of the device I'm just having a hard time thinking of the =
right example to motivate this.=20
>=20
> Any device that has a battery and needs to run unattended for a long =
period of time will pay a penalty for doing DNS queries over and over =
again; requiring it to do so is a bad practice.   If such a device does =
use DHCP, it almost certainly wants to use very long information refresh =
timers.   Using a short TTL in DNS for a service used by such a device =
either will not work, or will cause the device to prematurely drain its =
battery.

Once again, please give me an example where the ext ran DNS traffic from =
the device forms any relevant percentage of the traffic and/or power =
usage.=20

> These devices are real, likely represent a very significant area of IP =
service growth in the coming decade or two, and need to be supported.   =
If such a device uses a service discovery protocol, and that service =
discovery protocol probably were to deliver information via FQDNs, the =
device would have to query the DNS multiple times, at least one for each =
service, in order to resolve those FQDNs, each time it does a service =
discovery refresh.   It would also be well advised to query those FQDNs =
again anytime the TTL on the record returned in the previous query =
expired.

The refresh on DNS TTL is same as refresh on DHCP lease time

>=20
> DHCP does all the queries for you at the same time and hands you a =
single packet with all the information you need to contact all the =
services offered by DHCP.   This can be expected to result in many fewer =
packet round trips, and consequently much less power spent.   This is a =
significant feature; getting rid of it in order to make life a little =
more convenient for operators who do not have to deal with these =
constraints is a poor value proposition for the protocol as a whole.
>=20
> BTW, another example of a constrained device is a network booted =
device, where despite the fact that the node itself is quite capable =
once it's booted, the boot prom is quite constrained.   I think this was =
a primary motivation for the choice of address versus FQDN back in =
DHCPv4 days; I suspect relevant in fewer cases now, but still relevant =
in some.

Again, that's a fine argument why BOOTP should use IP, however it is not =
an argument about why nothing else should use FQDN

>=20
> (I will note, by the way, that you have yet to raise a point that was =
not considered and addressed by the working group.   I think this =
discussion is useful, because it points to clarifications that should be =
made to the document, but I don't yet see anything that would suggest to =
me that the consensus call went the wrong way.)

Well, why don't you come over to RAI and do a presentation on why we =
should not use FQDN in DHCP and see what the consensus is over there. =
I'm sure the ADs could arrange some agenda time in the dispatch meeting =
which is closest things that RAI has to an area meeting at IETF 88.  The =
consensus of a particular WG does not necessarily represent the =
consensus of the IETF.=20





From fluffy@iii.ca  Tue Oct 22 11:18:19 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 49A0111E8209 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.639
X-Spam-Level: 
X-Spam-Status: No, score=-2.639 tagged_above=-999 required=5 tests=[AWL=-0.040, 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 r3igSCR2+p05 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:18:13 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 191ED11E810B for <ietf@ietf.org>; Tue, 22 Oct 2013 11:18:13 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1368E22E257; Tue, 22 Oct 2013 14:18:05 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
Date: Tue, 22 Oct 2013 12:18:07 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <449D0548-324C-4377-B87E-B8B7ECDE92CB@iii.ca>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: Theodore Ts'o <tytso@mit.edu>, "<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, 22 Oct 2013 18:18:19 -0000

On Oct 22, 2013, at 8:15 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> What happened at PyCon is a really strong argument for having an =
escalation path other than twitter.=20

+1=20


From fluffy@iii.ca  Tue Oct 22 11:21:03 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 17C3111E8232; Tue, 22 Oct 2013 11:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.635
X-Spam-Level: 
X-Spam-Status: No, score=-2.635 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 I5X3hlLjSD5Z; Tue, 22 Oct 2013 11:20:57 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 33E3211E8213; Tue, 22 Oct 2013 11:20:57 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7AD3650A73; Tue, 22 Oct 2013 14:20:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
Date: Tue, 22 Oct 2013 12:20:57 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1EAD71F-21DD-4983-A401-7550A6560951@iii.ca>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 18:21:03 -0000

Looks good good to me.

Lets run this and I really hope it it all we need. Time will tell and we =
can adjust it if needed. This is much better than the current situation =
of pretty much nothing so lets not let perfection be the enemy of =
getting this published.=20

On Oct 20, 2013, at 11:44 AM, IETF Chair <chair@ietf.org> wrote:

>=20
> The IESG plans to adopt this as an IESG Statement. We solicit your =
feedback. We
> understand that this is a difficult and sensitive topic to discuss, =
but we do
> want your comments. If you feel more comfortable sending comments =
directly to
> the IESG <iesg@ietf.org> rather than discussing them on the IETF list, =
please
> feel free to do so.
>=20
> Jari Arkko for the IESG
>=20
> --- Draft Statement ---
>=20
> IETF Anti-Harassment Policy
>=20
> IETF meetings, virtual meetings, and mailing lists are intended for =
professional
> collaboration and networking. The IETF strives to create and maintain =
an
> environment in which people are treated with dignity, decency, and =
respect.
> Those who participate in the IETF are expected to behave according to
> professional standards and demonstrate appropriate workplace behavior. =
While
> participating in the IETF, communication between participants should =
be
> appropriate for a professional audience including people of many =
different
> backgrounds.
>=20
> While our processes let chairs deal with disruptive public behaviors =
on mailing
> lists and in IETF face-to-face meetings, harassment is a serious =
problem that
> warrants special attention. IETF participants should not engage in =
harassment
> while at IETF meetings, virtual meetings, social events, or on mailing =
lists.
> Harassment is unwelcome hostile or intimidating behavior, in =
particular speech
> and behavior that is sexually aggressive or intimidates based on =
attributes like
> race, gender, religion, age, color, national origin, ancestry, =
disability,
> sexual orientation, or gender identity. Harassment of this sort will =
not be
> tolerated in the IETF. Harassment includes the use of offensive =
language or
> sexual imagery in public presentations and displays, degrading verbal =
comments,
> deliberate intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, and unwelcome sexual attention.
>=20
> Participants asked to stop any harassing behavior are expected to =
comply
> immediately. If you believe you have been harassed, notice that
> someone else is being harassed, or have any other concerns, you are =
encouraged
> to raise your concern in confidence with one of the Ombudspersons.
>=20
> If these standards are violated, appropriate action will be taken.


From jari.arkko@piuha.net  Tue Oct 22 11:40:06 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 28F4111E8215 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:40:02 -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 8+GOYbQyFIki for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:39:40 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D11C011E8217 for <ietf@ietf.org>; Tue, 22 Oct 2013 11:39:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E19882CCBE for <ietf@ietf.org>; Tue, 22 Oct 2013 21:39:06 +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 SB4yuZsPC8RV for <ietf@ietf.org>; Tue, 22 Oct 2013 21:39:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 9FC532CC48 for <ietf@ietf.org>; Tue, 22 Oct 2013 21:39:05 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: RIPE and IGF presentations
Message-Id: <5B232164-E78E-4B96-A700-8469299F16DA@piuha.net>
Date: Wed, 23 Oct 2013 02:39:03 +0800
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 18:40:06 -0000

I visited the RIPE meeting and IGF meetings recently, and wanted to post =
two presentations/speeches that I held in these events. They are =
available at http://www.ietf.org/blog/2013/10/speeches/

Comments appreciated, as always.

Jari


From melinda.shore@gmail.com  Tue Oct 22 11:42:07 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 6911821F87B7 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[AWL=0.156,  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 4dBRldwzvgJo for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:42:06 -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 2BC3621F9302 for <ietf@ietf.org>; Tue, 22 Oct 2013 11:41:27 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so10264802pad.14 for <ietf@ietf.org>; Tue, 22 Oct 2013 11:41: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=EIlqOY+arfxqTGO+e15/O+MEYonmCJcY9j1U5Hahgco=; b=Z7ha7I6r8Qb9ohqdmexgFydMUMkD4BKtEXvkUuTRvhpvwcdx0/sQbnd7ZWpsK+bdCT ZeEW/8RvGJtJl3teU/8mRgV+PkNMfcR8/pOOYZmuAZnMCcwC2k5R6qhBi0P5T2HcxUGD sgVlD28XCHezVmobCP7dk+vx8TZKpC4BH5/KYxNS1jblIqWW+lqPN3YNJetutCneRzV5 Mzi6DCwdpKLZCtn6QOpxw05hy4YsMFaxTSc7ScFFZUzkwHOQpP6y4xmAG+gzRKTykPeC bcbE5M4IsXqvVTfwfRLwnneb7kb4Fw4fpbGKD8tyW6a+V2GVLiEL6hxQRWo4yYOm7cID h92A==
X-Received: by 10.68.229.167 with SMTP id sr7mr9407042pbc.159.1382467277992; Tue, 22 Oct 2013 11:41:17 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id v4sm29152002pbq.31.2013.10.22.11.41.15 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 11:41:16 -0700 (PDT)
Message-ID: <5266C6CA.30900@gmail.com>
Date: Tue, 22 Oct 2013 10:41:14 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net>
In-Reply-To: <5266B4A4.9020301@dcrocker.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: Tue, 22 Oct 2013 18:42:07 -0000

The more I've been thinking about this the less comfortable
I am with how this was executed.  I have no disagreement
whatsoever with removing this person's posting privileges.
But, I have a huge problem with Jordi's statement:

  "As Sergeant-at-arms, I agree with other previous
  postings and believe that anonymous posting is not
  tolerable in the IETF mail exploders."

Clearly, there are non-trivial problems around making decisions
on the basis of something sort of like identity in unauthenticated
email.  We don't *really* know who other people are - we tend to
assume that they are who they say they are and evaluate their
credibility (or not) on things like content, reputation, past
performance, etc.  The problem with mars.techno.cat@gmail.com
isn't that he (and since we're pretty sure we know who this is,
we'll stick with masculine pronouns) has an email address
that doesn't look like a name (although his name could have
been Mars Techno Cat, as unlikely as that is).  The problem
is that he had no prior history of posting -as that name-
and posted nothing but off-topic rants and personal attacks.
I would hope that the attacks would be sufficient to have his
posting privileges revoked and that having an unfamiliar
email address would not be sufficient.

Additionally, let me suggest that finding anonymous posts
"not tolerable" is inconsistent with the perpass discussions
and concerns expressed *here* about privacy.
We want accountability in our documents and that means knowing
that the people who contribute to our work 1) have technical
substance, and 2) are having their comments and text evaluated
by other people of technical substance.  It does not necessarily
mean knowing their names or identities.  In many discussions
about privacy and about whether or not various cryptographic
technologies have been deliberately weakened by some US
government agency, there have been repeated assertion that
open processes and aggressive review provide protection
against that sort of problem.  That ought to apply here, as
well.

Anonymity is not a problem.  Behaving badly is a problem.
I really never want to see someone's ejection justified on
the basis of their putative "anonymity" again.  I am not
arguing that mars.techno.cat@gmail.com ought to be allowed
anywhere near an IETF mailing list but that the reason that
was given for throwing him off was not correct.  We should
be working to protect anonymity and privacy, not punishing it.

Melinda

From dhc@dcrocker.net  Tue Oct 22 11:42: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 5D43E11E8223 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:42: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 sN85Fb+sj-WO for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:42:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0456611E821F for <ietf@ietf.org>; Tue, 22 Oct 2013 11:42:22 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9MIgHv9027477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Oct 2013 11:42:21 -0700
Message-ID: <5266C703.2070704@dcrocker.net>
Date: Tue, 22 Oct 2013 14:42:11 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: IETF::ISOC (was Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com)
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <m2ob6h42lk.wl%randy@psg.com>
In-Reply-To: <m2ob6h42lk.wl%randy@psg.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, 22 Oct 2013 11:42:21 -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: Tue, 22 Oct 2013 18:42:45 -0000

On 10/22/2013 1:50 PM, Randy Bush wrote:
>>> as the ietf is legally f(isoc),
>> The IETF is not legally ISOC.
>
> you are correct.  legally, it is a function of isoc.  sorry about the
> notational shortening.


No, that's also wrong.  For example, the IETF is not a 'subsidiary' or 
'department' of ISOC.

Legally the IETF is an unincorporated, independent organization, or 
'voluntary association'[1].

ISOC is a separate corporation that provides administrative, legal and 
financial services to the IETF.

The IETF existed before ISOC.  If ISOC ceased to exist, the IETF would 
still exist, albeit with a number of administrative, legal and financial 
holes it would have to scramble to fill.

If the IETF ceased to exist, ISOC would still exist and still have a 
wide range of on-going activities, albeit a bit of a public relations 
task for filling a hole in its "story" and a financial scramble for 
finding a new recipient of a large chunk of cash.

None of this disparages either organization, but is meant to clarify the 
nature and independence of each, because folk regularly misunderstand 
the reality of the two organizations.


d/


[1] http://en.wikipedia.org/wiki/Voluntary_association
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Tue Oct 22 11:50:36 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 0C90921F9EF2 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.55
X-Spam-Level: 
X-Spam-Status: No, score=-103.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 W5OfIN+161wr for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:50:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4979821F9F2D for <ietf@ietf.org>; Tue, 22 Oct 2013 11:50: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 1VYh1s-0003Zk-MC; Tue, 22 Oct 2013 14:50:08 -0400
Date: Tue, 22 Oct 2013 14:50:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Message-ID: <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com>
In-Reply-To: <5266C6CA.30900@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@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: Tue, 22 Oct 2013 18:50:36 -0000

Although I usually object to doing this, +1.  Well stated and I
strongly concur.

    john


--On Tuesday, October 22, 2013 10:41 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> The more I've been thinking about this the less comfortable
> I am with how this was executed.  I have no disagreement
> whatsoever with removing this person's posting privileges.
> But, I have a huge problem with Jordi's statement:
> 
>   "As Sergeant-at-arms, I agree with other previous
>   postings and believe that anonymous posting is not
>   tolerable in the IETF mail exploders."
> 
> Clearly, there are non-trivial problems around making decisions
> on the basis of something sort of like identity in
> unauthenticated email.  We don't *really* know who other
> people are - we tend to assume that they are who they say they
> are and evaluate their credibility (or not) on things like
> content, reputation, past performance, etc.  The problem with
> mars.techno.cat@gmail.com isn't that he (and since we're
> pretty sure we know who this is, we'll stick with masculine
> pronouns) has an email address that doesn't look like a name
> (although his name could have been Mars Techno Cat, as
> unlikely as that is).  The problem is that he had no prior
> history of posting -as that name- and posted nothing but
> off-topic rants and personal attacks. I would hope that the
> attacks would be sufficient to have his posting privileges
> revoked and that having an unfamiliar email address would not
> be sufficient.
> 
> Additionally, let me suggest that finding anonymous posts
> "not tolerable" is inconsistent with the perpass discussions
> and concerns expressed *here* about privacy.
> We want accountability in our documents and that means knowing
> that the people who contribute to our work 1) have technical
> substance, and 2) are having their comments and text evaluated
> by other people of technical substance.  It does not
> necessarily mean knowing their names or identities.  In many
> discussions about privacy and about whether or not various
> cryptographic technologies have been deliberately weakened by
> some US government agency, there have been repeated assertion
> that open processes and aggressive review provide protection
> against that sort of problem.  That ought to apply here, as
> well.
> 
> Anonymity is not a problem.  Behaving badly is a problem.
> I really never want to see someone's ejection justified on
> the basis of their putative "anonymity" again.  I am not
> arguing that mars.techno.cat@gmail.com ought to be allowed
> anywhere near an IETF mailing list but that the reason that
> was given for throwing him off was not correct.  We should
> be working to protect anonymity and privacy, not punishing it.
> 
> Melinda





From Ted.Lemon@nominum.com  Tue Oct 22 11:56:38 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 0F8CB11E821B; Tue, 22 Oct 2013 11:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 49n3xwvJetwe; Tue, 22 Oct 2013 11:56:29 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3B61311E822A; Tue, 22 Oct 2013 11:55:46 -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 DSNKUmbKHQ/O19uo4sjbHS7wgZNmzoeFxIBr@postini.com; Tue, 22 Oct 2013 11:55:47 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 45B0C1B813B; Tue, 22 Oct 2013 11:55:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 2CB65190052; Tue, 22 Oct 2013 11:55:25 -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.03.0158.001; Tue, 22 Oct 2013 11:55:25 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Cullen Jennings <fluffy@iii.ca>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Index: AQHOxG6vvYfRrCcaWUK4N3Cm629TPZns9HaA///CyYCAAGBrgP//wqiAgACIuQD///LeAAANvZ8AAAxP5AACbNgWAAAB/XiA
Date: Tue, 22 Oct 2013 18:55:24 +0000
Message-ID: <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca>
In-Reply-To: <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca>
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: <861D4BC8E8ED4B4EA68241C262FA1520@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@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, 22 Oct 2013 18:56:38 -0000

On Oct 22, 2013, at 1:58 PM, Cullen Jennings <fluffy@iii.ca> wrote:
> Ted, one of the hallmarks of a successful protocol is people use it for t=
hings it's designers think are an awful idea and it ends up working fairly =
well for them. I think the heart of the issue here is that you don't believ=
e that DHCP should be used to configure application-layer services, like SI=
P.  I disagree - I think the text in the draft about when to use this is ab=
out right=20

Argh.   No.   The hallmark of a successful protocol is not that it attracts=
 barnacles and gets used in ways that ultimately fail, either due to a real=
ly bad security model, or a bad fit, or other reasons.

DHCP in fact has been very successful in the IETF as a place to add barnacl=
es.   There are lots of DHCP option extensions that do all kinds of really =
exciting things.   Most of them were implemented once, shortly after public=
ation, never deployed, and now, if they exist at all, exist only as an atta=
ck surface that nobody has yet exploited hard enough to cause the feature t=
o be removed from the client implementation.

The actual success of DHCP is its core ability to configure devices with th=
e information they need to get online.   If you look at a typical DHCP pack=
et from a typical host, it doesn't ask for SIP servers.   It doesn't ask fo=
r printers.   It doesn't ask about SMTP or IMAP or POP.

My DHCPv4 client asks for: Subnet Mask, Default Gateway, Domain Name Server=
, Domain Name, Domain Search List, LDAP Server Address, WPAD Proxy URL, Net=
bios Name Server and Netbios Node Type.   My DHCPv6 client requests DNS Ser=
ver address and Domain Search List.

You will notice that it doesn't ask for an NTP option, even though it uses =
NTP.   This is because asking for an NTP option will generate support calls=
.  It doesn't ask for a printer address.   This is because although DHCPv4 =
provides a way to deliver printer addresses, nobody uses it.   Bonjour is e=
asier and more convenient, and generates fewer support calls.   Even though=
 I have an email client running, it doesn't ask for IMAP server, SMTP serve=
r or POP server, because that would be ridiculous.

So yes, DHCP is a successful protocol.   And yes, application protocol desi=
gners have attempted to use it to configure their protocols.   But they hav=
en't succeeded, in the large, because it's a bad idea.   It is not a succes=
sful _applications service discovery_ protocol.   It is a successful _host =
configuration_ protocol.

> I've build small battery powered sensors that use DHCP, DNS and reports e=
nvironmental measurements periodically to a server and have a very good han=
dle on the power usage of these devices. I've done ones that use ethernet a=
nd  802.15.4, (and also ones that don't use DNS or DHCp but run over satell=
ite links). On those networks, I have concrete measurements that indicate f=
or that system you are wrong about DNS making a significant difference to b=
attery life. I realize there might be other applications where it does make=
 a difference but so I'm having a hard time imagine such an system. The rea=
son why is simple, the bulk of traffic a sensor sends over a 30 day period =
is mostly sensor data not DHCP or DNS.=20

Indeed, in this scenario, power consumed by DNS and DHCP will not be an iss=
ue.

> On the flip side, for SIP phones we have seen that the level of indirecti=
on form DNS really helps make the operational issues easier.

Yes, and SIP is a lousy example, because it's not generally configured usin=
g DHCP=97it's generally configured through a user interface.   When it _is_=
 configured using DHCP, it's done in a constrained environment.   The confi=
guration model used in that environment would be a security disaster on the=
 open internet.

> I think the draft should not say that IPs are preferred over FQDNs. I thi=
nk it should say the choice of IP or FQDNs depends on the applications and =
factors that should be considered are size, power, extra RTT, if a DNS stac=
k is available, code size, and so on. But also point out some of the operat=
ional management advantages of DNS.=20

I agree that these are all good things to mention.   However, I think the d=
ocument should steer people away from using FQDNs, because if they need to =
use FQDNs, they will regardless of what direction the document tries to ste=
er them.

> Really we are talking about if you have a parameter in some new protocol =
X to control, this BCP is taking the opinion that it knows more about proto=
col X than the protocol X WG and that it thinks the parameter should be an =
IP not FQDN. I think this is wrong, DHCP should deal with how transport the=
 configuration parameter that protocol X needs and if that is an IP or FQDN=
 is probably a choice best left to experts of protocol X.  Heck, I'll go a =
scope further, I think it is not in charter of the DHC working to determine=
 if IP or FQDN are best to configure a parameter in some future protocol do=
ne by some other WG.

It is in the charter to recommend best practices for DHCP.

> On Oct 10, 2013, at 9:41 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>> On Oct 9, 2013, at 11:49 PM, Cullen Jennings <fluffy@iii.ca> wrote:
>>>> If this argument were correct, we'd expect to see major O.S. vendors s=
upporting the NTP option, but we don't=97instead, it's something that can b=
e configured in the UI for situations like the one you describe, and that o=
therwise is defaulted to the preconfigured value, which of course can be up=
dated when the operating system is updated.
>>>=20
>>> Right - I am certainly more focused on the devices that don't have an a=
dministrator that can configure them locally.=20
>>=20
>> This is great, but that's not all devices.   And devices of this type of=
ten wind up being very vulnerable to attack precisely because no usable esc=
ape mechanism is offered.   DHCP may be your only choice for configuring su=
ch a device, but it's a really lousy choice.
>=20
> Louse choice? What exactly would you propose that would work better ?

What would be better would be a secure mechanism for configuring them.   E.=
g., going to a well-known URL and downloading a configuration signed using =
a tool that allows the device to validate the configuration.   This is what=
 e.g. Microsoft Exchange clients do.   It works quite well.

>> Right, and I think I already said that (a) SIP is a bad example of a use=
 case for DHCP, because it's a node-specific service, not a network-specifi=
c service, and (b) it's probably fine, if you must use DHCP to configure SI=
P, to use an FQDN, as I already said several messages back.
>=20
> Sure, and why does that same argument not hold for configuring similar se=
rvices which is what I complained about in the draft.=20

In general, configuring similar services using DHCP won't work.   I'm not c=
onvinced it works for SIP.   I'm fairly sure it doesn't work for configurin=
g NTP.

> Look, I am not arguing that one should not us IP address in some cases. I=
'm arguing that there are equally good cases where one should use FQDN. I r=
ealize they are not popular with the layer 2/3 folks but they are very popu=
lar with the application layer folks because of the flexibility and easy of=
 managment they provide.=20

Can you give me an example of a use case that is _not_ an APPS-area protoco=
l?

BTW, you mentioned that you think NTP and DNS are application layer, but th=
ey are in the INT area for a reason.   I mean a protocol that's in the APPS=
 area, for an equally good reason.

>> SRV records are normally used for application-layer services, like SIP, =
which I don't think should be configured with DHCP.   Similarly, would you =
use DHCP to configure the address of an HTTP server? :)
>=20
> This seems to be the heart of it. You don't think this should be used for=
 application layer services but I don't think that ship sailed long long ag=
o.=20

The ship sailed long ago, and sank out at sea, yes.   I was on it at the ti=
me=97like you, I used to think DHCP was for configuring applications.   I d=
id not arrive at my current opinion accidentally.

> Once again, please give me an example where the ext ran DNS traffic from =
the device forms any relevant percentage of the traffic and/or power usage.=
=20

Any time the frequency of reports from the device is similar in frequency t=
o refreshes required by the DNS TTL expiring.

> The refresh on DNS TTL is same as refresh on DHCP lease time

Yes, and if you have to do six DNS queries per DHCP renewal, that's six mor=
e packet exchanges.

>> DHCP does all the queries for you at the same time and hands you a singl=
e packet with all the information you need to contact all the services offe=
red by DHCP.   This can be expected to result in many fewer packet round tr=
ips, and consequently much less power spent.   This is a significant featur=
e; getting rid of it in order to make life a little more convenient for ope=
rators who do not have to deal with these constraints is a poor value propo=
sition for the protocol as a whole.
>>=20
>> BTW, another example of a constrained device is a network booted device,=
 where despite the fact that the node itself is quite capable once it's boo=
ted, the boot prom is quite constrained.   I think this was a primary motiv=
ation for the choice of address versus FQDN back in DHCPv4 days; I suspect =
relevant in fewer cases now, but still relevant in some.
>=20
> Again, that's a fine argument why BOOTP should use IP, however it is not =
an argument about why nothing else should use FQDN

I don't think you said what you meant here.   BOOTP is a predecessor to DHC=
P=97what does that have to do with this conversation?

>> (I will note, by the way, that you have yet to raise a point that was no=
t considered and addressed by the working group.   I think this discussion =
is useful, because it points to clarifications that should be made to the d=
ocument, but I don't yet see anything that would suggest to me that the con=
sensus call went the wrong way.)
>=20
> Well, why don't you come over to RAI and do a presentation on why we shou=
ld not use FQDN in DHCP and see what the consensus is over there. I'm sure =
the ADs could arrange some agenda time in the dispatch meeting which is clo=
sest things that RAI has to an area meeting at IETF 88.  The consensus of a=
 particular WG does not necessarily represent the consensus of the IETF.=20


(a) I can't.
(b) It would be useless.   Of course RAI is going to say DHCP should suppor=
t configuring application protocols.   Why not?   It's a cost-free assertio=
n from your perspective.
(c) This document is saying what the DHC working group recommends.   RAI wo=
rking groups are free to go against these recommendations.   So this docume=
nt shouldn't say what RAI recommends.   It should say what DHC recommends. =
  If a working group doesn't want to follow the advice, they don't have to,=
 because it's just advice, not a requirement.=

From randy@psg.com  Tue Oct 22 11:56:48 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 33AAB11E823E for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 P7m-ZdKHCaM9 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 11:56:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 4C32D11E8236 for <ietf@ietf.org>; Tue, 22 Oct 2013 11:56:10 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VYh7e-0001nY-GY; Tue, 22 Oct 2013 18:56:06 +0000
Date: Tue, 22 Oct 2013 20:56:05 +0200
Message-ID: <m2eh7d3zju.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <5266C6CA.30900@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@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: Tue, 22 Oct 2013 18:56:49 -0000

> Anonymity is not a problem.  Behaving badly is a problem.
> I really never want to see someone's ejection justified on
> the basis of their putative "anonymity" again.  I am not
> arguing that mars.techno.cat@gmail.com ought to be allowed
> anywhere near an IETF mailing list but that the reason that
> was given for throwing him off was not correct.  We should
> be working to protect anonymity and privacy, not punishing it.

<aol>

From brian.e.carpenter@gmail.com  Tue Oct 22 12:16: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 C45CC21F9CE8 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:16:28 -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 FF1VVzlpemZX for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:16:28 -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 F207121F9DD0 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:14:03 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id un1so2497173pbc.5 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:14:03 -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=3IfnhJwAapzF8lM5msV87+tBloGvGez3oFAEXeRzWyQ=; b=QNG3aL1hJPp4dABmBPhtW6k3hLquq9GAB7SSehN/RtXHHibY1T9xqrcxaZob4IP0sU +v6Q96LUJQFRoEBiPIT0humlypxd1HUQ0jFXBgI+wHywA95JXQQo3LihQCJWYiBLM/+a dStDeF0ON2CN8GLIjJg4HGeEpBgQB4kaZmyc/PlEOESQ0BOVFWu0KFxgBWn2FOQjx01E 0TgZsD2yBhLun5W5kyCHke9VWn190jfDMNYQVxZbOQpZbs6ROhXT0R8xnni6gF3Qrevv u5vxGPZliW933Je/WlEnqHkVgLjXHmF0TYnnQh6fmsK4cCW4yspFqofRHjvy263+eWJD 9/8A==
X-Received: by 10.67.30.70 with SMTP id kc6mr24795326pad.32.1382469243717; Tue, 22 Oct 2013 12:14:03 -0700 (PDT)
Received: from [192.168.178.20] (178.193.69.111.dynamic.snap.net.nz. [111.69.193.178]) by mx.google.com with ESMTPSA id hz10sm29263853pbc.36.2013.10.22.12.14.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 12:14:02 -0700 (PDT)
Message-ID: <5266CE7C.2020503@gmail.com>
Date: Wed, 23 Oct 2013 08:14:04 +1300
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: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com>
In-Reply-To: <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.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, 22 Oct 2013 19:16:28 -0000

Strangely enough, I concur too.

If you look at my original complaint to Jordi, anonymity was not mentioned.
I only raised it when asked  why I requested action. And I agree: anonymity
in itself is not a problem.

Anonymity + irrelevance is a problem, in my opinion.

Regards
   Brian

On 23/10/2013 07:50, John C Klensin wrote:
> Although I usually object to doing this, +1.  Well stated and I
> strongly concur.
> 
>     john
> 
> 
> --On Tuesday, October 22, 2013 10:41 -0800 Melinda Shore
> <melinda.shore@gmail.com> wrote:
> 
>> The more I've been thinking about this the less comfortable
>> I am with how this was executed.  I have no disagreement
>> whatsoever with removing this person's posting privileges.
>> But, I have a huge problem with Jordi's statement:
>>
>>   "As Sergeant-at-arms, I agree with other previous
>>   postings and believe that anonymous posting is not
>>   tolerable in the IETF mail exploders."
>>
>> Clearly, there are non-trivial problems around making decisions
>> on the basis of something sort of like identity in
>> unauthenticated email.  We don't *really* know who other
>> people are - we tend to assume that they are who they say they
>> are and evaluate their credibility (or not) on things like
>> content, reputation, past performance, etc.  The problem with
>> mars.techno.cat@gmail.com isn't that he (and since we're
>> pretty sure we know who this is, we'll stick with masculine
>> pronouns) has an email address that doesn't look like a name
>> (although his name could have been Mars Techno Cat, as
>> unlikely as that is).  The problem is that he had no prior
>> history of posting -as that name- and posted nothing but
>> off-topic rants and personal attacks. I would hope that the
>> attacks would be sufficient to have his posting privileges
>> revoked and that having an unfamiliar email address would not
>> be sufficient.
>>
>> Additionally, let me suggest that finding anonymous posts
>> "not tolerable" is inconsistent with the perpass discussions
>> and concerns expressed *here* about privacy.
>> We want accountability in our documents and that means knowing
>> that the people who contribute to our work 1) have technical
>> substance, and 2) are having their comments and text evaluated
>> by other people of technical substance.  It does not
>> necessarily mean knowing their names or identities.  In many
>> discussions about privacy and about whether or not various
>> cryptographic technologies have been deliberately weakened by
>> some US government agency, there have been repeated assertion
>> that open processes and aggressive review provide protection
>> against that sort of problem.  That ought to apply here, as
>> well.
>>
>> Anonymity is not a problem.  Behaving badly is a problem.
>> I really never want to see someone's ejection justified on
>> the basis of their putative "anonymity" again.  I am not
>> arguing that mars.techno.cat@gmail.com ought to be allowed
>> anywhere near an IETF mailing list but that the reason that
>> was given for throwing him off was not correct.  We should
>> be working to protect anonymity and privacy, not punishing it.
>>
>> Melinda
> 
> 
> 
> 
> 

From scott.brim@gmail.com  Tue Oct 22 12:26: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 0221211E8205 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, 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 C2yR2jv06lUD for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:26:44 -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 24CCB11E8220 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:26:44 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id g12so7090378oah.19 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:26:32 -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=rzIXYUThPA/7TH5SiKWpq7YsKkMk8RxsOrZzz2hJpcs=; b=VVnVNdfnLcTFZurKQ3ZHtj+lMtPsvAlk1agiIRKt70AtgGsx5QliJ0gg88pWvF3x2i InERXMmBEGzcvkTYoV95scbu4N834rnE1TH081bcW+5JOM+mDX59t/Wzu4bTZR20+rUJ I10rjUqVfSaR3cmu/uZdTPFVCmTRHO+BCRK6TeBF2u4sQe/FoY6gbZYN4jsz6EiLoF+k Cm1u6lQaW8K18+BYQQsXXWEFBKLc8Qq2UDo4qmva0Q8YXm54ez29PPFX6Oxtqm6c+spo 2rip3RbDmm00StgXPRhx5o7NKNcdlC6eujHvWMwFPem0NCsJeSU9DaQT2TSeIQpKjOnI Ojkg==
X-Received: by 10.60.96.169 with SMTP id dt9mr3208221oeb.27.1382469992692; Tue, 22 Oct 2013 12:26:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Tue, 22 Oct 2013 12:26:12 -0700 (PDT)
In-Reply-To: <5266CE7C.2020503@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 22 Oct 2013 15:26:12 -0400
Message-ID: <CAPv4CP9BQ1eHDefK0pOz4GdY7tf_1H_8Y-0ECsJtXNb-jM0HBA@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e0117601fd3c62c04e9596010
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: Tue, 22 Oct 2013 19:26:45 -0000

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

On Tue, Oct 22, 2013 at 3:14 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Anonymity + irrelevance is a problem, in my opinion.


Anonymity plus disruption.  If we can ignore it it's not a problem worth
pursuing... But note that even when identified, disruption is the central
problem with almost the same solutions.  Anonymity isn't a central issue.

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

<div dir=3D"ltr">On Tue, Oct 22, 2013 at 3:14 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anonymity + irrel=
evance is a problem, in my opinion.</blockquote><div><br></div><div>Anonymi=
ty plus disruption. =A0If we can ignore it it&#39;s not a problem worth pur=
suing... But note that even when identified, disruption is the central prob=
lem with almost the same solutions. =A0Anonymity isn&#39;t a central issue.=
=A0</div>

</div></div></div>

--089e0117601fd3c62c04e9596010--

From Ted.Lemon@nominum.com  Tue Oct 22 12:37:08 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 7CEF911E822E for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 hg7K+xP5VBd6 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:37:00 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACC221E8082 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:36:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUmbT2cXO8u0VZ/DrrsgpodF3oRvclVg+@postini.com; Tue, 22 Oct 2013 12:36:58 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 A8E381B82E1 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:36:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 888F9190052; Tue, 22 Oct 2013 12:36:57 -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.03.0158.001; Tue, 22 Oct 2013 12:36:57 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzRN5MiZjjrFfeEyJF39B90YYOZn/6ykAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAADZACAAAL/AA==
Date: Tue, 22 Oct 2013 19:36:56 +0000
Message-ID: <7AFB0AF9-807A-4374-A4FE-26F89E8652E6@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <CAPv4CP9BQ1eHDefK0pOz4GdY7tf_1H_8Y-0ECsJtXNb-jM0HBA@mail.gmail.com>
In-Reply-To: <CAPv4CP9BQ1eHDefK0pOz4GdY7tf_1H_8Y-0ECsJtXNb-jM0HBA@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: <C516CEBA9213284786DAE239766C4404@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 22 Oct 2013 19:37:08 -0000

On Oct 22, 2013, at 3:26 PM, Scott Brim <scott.brim@gmail.com> wrote:
> Anonymity plus disruption.  If we can ignore it it's not a problem worth =
pursuing... But note that even when identified, disruption is the central p=
roblem with almost the same solutions.  Anonymity isn't a central issue.=20

Yup.   I think when the first email message we see from a particular source=
 is obviously disruptive and off-topic, we do not need to wait for a larger=
 statistical sample before acting. If the disruptiveness was the result of =
a misunderstanding, we can correct that when we receive the apology.

I think Jordi misspoke, and we should not make a policy of doing what he sa=
id in his answer to Brian.   But I haven't seen anything thus far to sugges=
t to me that the action taken was the wrong one.


From sm@resistor.net  Tue Oct 22 12:46: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 3375C11E823C for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:46:48 -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 9qbZzUJ+-RQM for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:46:46 -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 91F7111E821F for <ietf@ietf.org>; Tue, 22 Oct 2013 12:46:20 -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 r9MJjwOG012340; Tue, 22 Oct 2013 12:46:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382471162; bh=OmUfgqi+TLu1XNr3+OKGwkZnQ0wl1OcvIQxnffFCy/g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZZj5lTXM+AQ8DOb2gk2VISKc56mIHfD7qOa4S/KtEUdjkzhQcDHv9/FYbs0JsUVmn H43NOGsNziFMGaDz+bYv28W+m9s/+6sBP+EJ4RsXqUF0kEY9dxGog1H3W+cqcjDtxa 4i5E2zaLh2Lf6IWGhuTDH4AHYFsTBnCfD/W5IKxY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382471162; i=@resistor.net; bh=OmUfgqi+TLu1XNr3+OKGwkZnQ0wl1OcvIQxnffFCy/g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Do4ewha5Rg7AdFcPhGU+YZfitK3PdnyEBCRhKJPDaBxbc+40XsYHOlT4Ab3kcfaYG E1nmIkCu3gjOqy22B6wc6fTSRsQmwYQfjgdVlXlNFx6pB7x97+YLGxhjmv0aFWA/Az SQz4Znl8N9ef7DfhaobcgiSbF+/Do4yk5EdNwBc8=
Message-Id: <6.2.5.6.2.20131022120147.0cf87ca8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 22 Oct 2013 12:45:01 -0700
To: Melinda Shore <melinda.shore@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Sergeant at arms: please deal with [censored]
In-Reply-To: <5266C6CA.30900@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@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: Tue, 22 Oct 2013 19:46:48 -0000

Hi Melinda,
At 11:41 22-10-2013, Melinda Shore wrote:
>The more I've been thinking about this the less comfortable
>I am with how this was executed.  I have no disagreement
>whatsoever with removing this person's posting privileges.
>But, I have a huge problem with Jordi's statement:
>
>   "As Sergeant-at-arms, I agree with other previous
>   postings and believe that anonymous posting is not
>   tolerable in the IETF mail exploders."

As a matter of individual opinion I would not remove the person's 
posting privileges.  The reason is because it can be argued that 
there is bias.  The statement could have considered the issue instead 
of what other people are saying.

>Clearly, there are non-trivial problems around making decisions
>on the basis of something sort of like identity in unauthenticated
>email.  We don't *really* know who other people are - we tend to
>assume that they are who they say they are and evaluate their
>credibility (or not) on things like content, reputation, past
>performance, etc.  The problem with [censored]

Yes.

>Additionally, let me suggest that finding anonymous posts
>"not tolerable" is inconsistent with the perpass discussions
>and concerns expressed *here* about privacy.

Agreed.

>We want accountability in our documents and that means knowing
>that the people who contribute to our work 1) have technical
>substance, and 2) are having their comments and text evaluated
>by other people of technical substance.  It does not necessarily
>mean knowing their names or identities.  In many discussions
>about privacy and about whether or not various cryptographic
>technologies have been deliberately weakened by some [censored]
>government agency, there have been repeated assertion that
>open processes and aggressive review provide protection
>against that sort of problem.  That ought to apply here, as
>well.

Yes.

>Anonymity is not a problem.  Behaving badly is a problem.

The above is well-said.

Regards,
-sm 


From jari.arkko@piuha.net  Tue Oct 22 12:47:49 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 3570E21F9D1C for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 AOTkccadAROO for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 12:47:42 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 167E921F9929 for <ietf@ietf.org>; Tue, 22 Oct 2013 12:46:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 729992CCBE; Tue, 22 Oct 2013 22:46:56 +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 dcxsqWLhx9Cq; Tue, 22 Oct 2013 22:46:55 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E9BD42CC48; Tue, 22 Oct 2013 22:46:53 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5266CE7C.2020503@gmail.com>
Date: Wed, 23 Oct 2013 03:46:51 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: John C Klensin <john-ietf@jck.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, 22 Oct 2013 19:47:49 -0000

> Strangely enough, I concur too.

Agree here as well.

FWIW and in full disclosure, I was in agreement with the suggestion that =
the mail was problematic, and told Brian and Jordi about my opinion. I =
still think so, but in retrospect I should have specified why I believed =
there was a problem (NOT due to anonymity). Had I done that, I'm sure =
Jordi's e-mail would have had a different text, even if the outcome =
would have been the same. Sorry. We'll improve communication in the =
future.

I have another observation from this case that we might try to learn =
from. If people have an issue with a posting, should they contact the =
sergeant-at-arms in public or in private?

Jari



From melinda.shore@gmail.com  Tue Oct 22 13:00: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 C9E8311E8242 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147,  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 qhDku59lzjGw for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:00: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 0C27A11E823D for <ietf@ietf.org>; Tue, 22 Oct 2013 13:00:12 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so10382680pad.0 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:00: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=lrAm2ZKF+f+gkQdAzpdBfC57Zt05cGcQKyKVF6SQTSQ=; b=gVu+STLl9oHeRm1i74YzULQ9Tzko+qOBsjwEiTjyxYINow/EvOcxC46h/MfpwXM4iK v5HEOOuPK9ZKyLXdp958c7rPaOXJGE6nuWciRC0qmxtc/4iaX0JnFGSfuPb8FZAvm1vh jHKBcV+jkX57aiQeMJF1p+XXH48CcfNuAgPxDqZrZkwFQGft2VY+Rkwwb4Pd7dwEKSGZ gCQjgEgKSMZYEveUJFMzj6rJCErAw2LsdyueGMIUCmmjyMtq5GIAT3hYUujRbgfzHJSZ 7h9zlKOxrfqlYy1xUkdAGNAoEZ+Chm3hLVi6OLCYLQUA1C3GuJfxgbTvxkjm+KyHBRR0 KglA==
X-Received: by 10.68.219.167 with SMTP id pp7mr10455462pbc.125.1382472008882;  Tue, 22 Oct 2013 13:00:08 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id qf7sm35575077pac.14.2013.10.22.13.00.06 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 13:00:07 -0700 (PDT)
Message-ID: <5266D942.1050404@gmail.com>
Date: Tue, 22 Oct 2013 12:00:02 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
In-Reply-To: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.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: Tue, 22 Oct 2013 20:00:47 -0000

On 10/22/13 11:46 AM, Jari Arkko wrote:
> I have another observation from this case that we might try to learn
> from. If people have an issue with a posting, should they contact the
> sergeant-at-arms in public or in private?

I think that either is fine, although in the interest of transparency
and the ability to file appeals, actions should be public.

Melinda


From abdussalambaryun@gmail.com  Tue Oct 22 13:42:09 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 43C7211E832A for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:42:09 -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 iYxQwbqajhRw for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:42:08 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5F54621E8099 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:40:12 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z10so11005083pdj.16 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:40: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 :content-type; bh=TgMBJTKBqvx+pNcRgaUOLN88Nd78NK2hdIWcC6r4CJg=; b=CL2HslzSunaEjlWpNom0/smQ7uklrRsCQxI05dZsOlQHXFmOFHCDID1UiBqJU7JkT8 B/Tj2apD/ZpKIfx4w/KTMaBt9IwRBuQ6zgGW+FecmBvxRvdYQ6wlwCisObiSbjjueFaA KxlMUzbod05eFqQAP9LHX1CDvWCm4w9TDwHN4ZAFgc/R+th5BdhPDYwfngvJ8P6U9pBQ wR5HVuUNKhBNeOQaQuqKJ0UIWIAyy7Z8QZSfwbkllOzdc3+pOJcG18zAsPEU+aVOXwg1 ZHIxdVhW/erXzCXs72BjS3jETvQZAGwPjA67Ivc9sdzVpci2uEnwqkA/Lz2vZY6zYpez uLzg==
MIME-Version: 1.0
X-Received: by 10.66.165.106 with SMTP id yx10mr9005047pab.159.1382474403868;  Tue, 22 Oct 2013 13:40:03 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Tue, 22 Oct 2013 13:40:03 -0700 (PDT)
In-Reply-To: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
Date: Tue, 22 Oct 2013 21:40:03 +0100
Message-ID: <CADnDZ88ZaSU=VR6-xCR5vEWXJX=VzMg9a0m7owQP5CbGeu_-RQ@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b86c342c0f5f104e95a6750
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 20:42:09 -0000

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

>
>
>
As I noticed that f2f meetings should present their name before talking so
it is good no anonymous talks. I think there is a hidden problem in
anonymous posting, how can I network with someone I cannot trust because
he/she does not trust participants by sharing identity. I post with a
known name but get some participants discredits me with that name (a reason
why some people hide real names), so they taking things to personal or
trying to make poster become change to anonymous or become with no trust of
the IETF system.

All should respect others, so we can work together with more trust. I am
against IETF allowing workers becoming anonymous because no one will trust
it or even follow it. I started to be afraid that most IETF management or
participants or authors may have registered without their real name.

An anonymous poster should go through a process with a known participant to
proof that he/she is not attacking the system. That participant may sponsor
the anonymous poster to enable the continue of anonymous remote
participation.

AB

--047d7b86c342c0f5f104e95a6750
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"><br></blockquote><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"></blockquote>
<div><br></div>As I noticed that f2f meetings should present their name bef=
ore talking so it is good no anonymous talks. I=A0think there is a hidden p=
roblem in anonymous posting, how can I network with someone I cannot trust =
because he/she does not trust participants by sharing identity.=A0I post wi=
th a known=A0name but get some participants discredits me with that=A0name =
(a reason why some=A0people hide real names), so they=A0taking things to=A0=
personal or trying to make poster=A0become change to=A0anonymous or become =
with no trust of the IETF system.=A0<div>
<br></div><div>All should respect others, so we can work together with more=
 trust. I=A0am against IETF allowing workers=A0becoming anonymous because n=
o one will trust it or even follow it. I started to be afraid that most IET=
F management or participants=A0or authors=A0may=A0have registered=A0without=
 their real name.</div>
<div><br></div><div>An=A0anonymous poster should go through a process with =
a known participant=A0to proof that he/she is not attacking the system.=A0T=
hat participant may sponsor the anonymous poster to enable the continue of =
anonymous remote participation.=A0</div>
<div><br></div><div><div><div><div>AB</div></div></div></div>

--047d7b86c342c0f5f104e95a6750--

From melinda.shore@gmail.com  Tue Oct 22 13:50:11 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 4593111E8267 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 4ryEW1QwsFCn for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:50:10 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 680E111E8272 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:50:04 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id rd3so19873pab.18 for <ietf@ietf.org>; Tue, 22 Oct 2013 13:50:00 -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=Uu7I4T+PZasszEof/w6oS0Bv3J7NuzbJ+VPqBNe91/o=; b=TZ27U/QEJ6IHI+DMehHGuNtYSrrULSQVd8qeVhzkyRrtzqnofsAr48272asEF07d81 Ndg2r1bjmWHcsstTqYHNcaeuxW/U6BAReWlrqqO2Jw/YlLU3TQ75IepdxviiPOYrnv2a IhuKT4aKgbjHqt6jIVRPbSBRgCq4P0KQS1fFoxia9B2p/1d62uz4ag70VOi9JwYETvOB 1SiR0ARYcigjQE216tyLI3yCd76q2RXEw2EIF/3WG4/wm6tZzgh/3egLqP+6eLg9SkfA GZ5bs/SxBYfhff37oUbvIeXhM1c769c8OLuvmd8qb8y8ls9bVMvDscgvjDDZgPhHGDKy fZTA==
X-Received: by 10.68.34.105 with SMTP id y9mr24946633pbi.15.1382475000564; Tue, 22 Oct 2013 13:50:00 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id xe9sm35788234pab.0.2013.10.22.13.49.58 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 13:49:59 -0700 (PDT)
Message-ID: <5266E4F5.1060801@gmail.com>
Date: Tue, 22 Oct 2013 12:49:57 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <CAPv4CP9BQ1eHDefK0pOz4GdY7tf_1H_8Y-0ECsJtXNb-jM0HBA@mail.gmail.com> <7AFB0AF9-807A-4374-A4FE-26F89E8652E6@nominum.com>
In-Reply-To: <7AFB0AF9-807A-4374-A4FE-26F89E8652E6@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, 22 Oct 2013 20:50:11 -0000

On 10/22/13 11:36 AM, Ted Lemon wrote:
> I think Jordi misspoke, and we should not make a policy of doing what
> he said in his answer to Brian.  

Right, but as a matter of public record,

  "As Sergeant-at-arms, I agree with other previous
  postings and believe that anonymous posting is not
  tolerable in the IETF mail exploders."

really should not be allowed to stand.

Melinda

From randy@psg.com  Tue Oct 22 13: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 B8D7311E8264 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 tsankR0nXnja for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 13:55:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 3429411E82AD for <ietf@ietf.org>; Tue, 22 Oct 2013 13:55:25 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VYiz3-000219-HB; Tue, 22 Oct 2013 20:55:22 +0000
Date: Tue, 22 Oct 2013 22:55:20 +0200
Message-ID: <m261sp3u13.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@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, 22 Oct 2013 20:55:30 -0000

> I have another observation from this case that we might try to learn
> from. If people have an issue with a posting, should they contact the
> sergeant-at-arms in public or in private?

if i, as a normal citizen, have an incident with someone's egregious
action in a public place, should i contact the executioner in public or
private?

wrong question, at least in the culture in which i was raised.  we pay
lip service to the concept that there should be a bit of 'due process'
between a complaint and the executioner (and then spy on you and bomb
you into democracy).

From: Ted Lemon <Ted.Lemon@nominum.com>
> I think when the first email message we see from a particular source
> is obviously disruptive and off-topic, we do not need to wait for a
> larger statistical sample before acting.

i am a bit taken aback by the vigilantism.  

it was just an email message, and a factual one at that.  the usual
example is _falsely_ shouting "fire" specifically because it can cause
*actual* *physical* *harm*.  get a delete key.  get procmail.  get a
grip.

randy

From narten@us.ibm.com  Tue Oct 22 14:12: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 1155211E8271 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:12: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 7cerZVD3EPCW for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:12:10 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 4C28511E826C for <ietf@ietf.org>; Tue, 22 Oct 2013 14:12:08 -0700 (PDT)
Received: from /spool/local by e8.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>; Tue, 22 Oct 2013 17:12:07 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 22 Oct 2013 17:12:04 -0400
Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 31BEB6E8040 for <ietf@ietf.org>; Tue, 22 Oct 2013 17:12:02 -0400 (EDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9MLC38X47579266 for <ietf@ietf.org>; Tue, 22 Oct 2013 21:12:03 GMT
Received: from d03av04.boulder.ibm.com (localhost [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r9MLC2d2004376 for <ietf@ietf.org>; Tue, 22 Oct 2013 15:12:03 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-76-22-94.mts.ibm.com [9.76.22.94]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id r9MLC0IW004112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Oct 2013 15:12:01 -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 r9MLBv30017644; Tue, 22 Oct 2013 17:11:57 -0400
Message-Id: <201310222111.r9MLBv30017644@cichlid.raleigh.ibm.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-reply-to: <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>
Comments: In-reply-to Jari Arkko <jari.arkko@piuha.net> message dated "Wed, 23 Oct 2013 03:46:51 +0800."
Date: Tue, 22 Oct 2013 17:11:57 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13102221-0320-0000-0000-00000177CB90
Cc: John C Klensin <john-ietf@jck.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, 22 Oct 2013 21:12:17 -0000

> I have another observation from this case that we might try to learn
>  from. If people have an issue with a posting, should they contact
>  the sergeant-at-arms in public or in private?

In private please, first. And maybe also cc a small number of
relevant/interested folk so there can be a private discussion.

Not every action we do should start in public. 

For starters, it's human nature 101 that resolving matters in private
is generally easier than resolving them after the stakes have been
raised. Being public about some things is by its very nature an
escalation.

There is a time for doing things in public, but we shouldn't always
start there.

Thomas


From Ted.Lemon@nominum.com  Tue Oct 22 14:13: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 7877B11E82BE for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 ONDbJTYo+Bu9 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:13:36 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id EC89511E8265 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:13:33 -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 DSNKUmbqfRyfAS6V+teuGDkrZQyBTrSe/NXr@postini.com; Tue, 22 Oct 2013 14:13:33 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 8C3021B82E1 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:13:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 67CBB190060; Tue, 22 Oct 2013 14:13:33 -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.03.0158.001; Tue, 22 Oct 2013 14:13:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzRN5MiZjjrFfeEyJF39B90YYOZn/6ykAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAADZACAAAL/AIAAFGeAgAAGlwA=
Date: Tue, 22 Oct 2013 21:13:32 +0000
Message-ID: <DD0DDB9E-0542-44FB-B4C6-1BDF86654841@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <CAPv4CP9BQ1eHDefK0pOz4GdY7tf_1H_8Y-0ECsJtXNb-jM0HBA@mail.gmail.com> <7AFB0AF9-807A-4374-A4FE-26F89E8652E6@nominum.com> <5266E4F5.1060801@gmail.com>
In-Reply-To: <5266E4F5.1060801@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: <6B51EF232C1BE8469F665BED9589EB4A@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, 22 Oct 2013 21:13:43 -0000

On Oct 22, 2013, at 4:49 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> Right, but as a matter of public record,
>=20
>  "As Sergeant-at-arms, I agree with other previous
>  postings and believe that anonymous posting is not
>  tolerable in the IETF mail exploders."
>=20
> really should not be allowed to stand.

Let's give Jordi some time to respond.   I don't think he reads the list mo=
re than once a day, so he's probably innocently wondering why his ears are =
burning.


From Ted.Lemon@nominum.com  Tue Oct 22 14:22:03 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 14ED211E824C for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.008, 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 TQNRdlxCgLIg for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:21:52 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 047DA11E81FF for <ietf@ietf.org>; Tue, 22 Oct 2013 14:21:50 -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 DSNKUmbsbkUxMSYCVwPvtemDBXTkfKu21pVf@postini.com; Tue, 22 Oct 2013 14:21: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 5042D1B82B6 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:21:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 4A451190052; Tue, 22 Oct 2013 14:21: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.03.0158.001; Tue, 22 Oct 2013 14:21:50 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzRN5MiZjjrFfeEyJF39B90YYOZn/6ykAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAAJKYCAABMiAIAAB2UA
Date: Tue, 22 Oct 2013 21:21:49 +0000
Message-ID: <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com>
In-Reply-To: <m261sp3u13.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: <EBAC8FD1A62575459F372D6A66DAC5BB@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, 22 Oct 2013 21:22:03 -0000

On Oct 22, 2013, at 4:55 PM, Randy Bush <randy@psg.com> wrote:
> i am a bit taken aback by the vigilantism. =20
>=20
> it was just an email message, and a factual one at that.  the usual
> example is _falsely_ shouting "fire" specifically because it can cause
> *actual* *physical* *harm*.  get a delete key.  get procmail.  get a
> grip.

Right, that's not the policy.   If that were the policy, a number of notori=
ous abusers of the mailing list would still have posting privileges.

If the first message had been the beginning of a conversation, I would have=
 taken it a lot differently, but the way it was dropped on the list with no=
 discussion, it just looked like an attempt to start a massive flame war.  =
 That's exactly the sort of thing that the sergeant-at-arms is supposed to =
deal with.


From envite@rolamasao.org  Tue Oct 22 14:35:56 2013
Return-Path: <envite@rolamasao.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 0D10E11E827A for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.137
X-Spam-Level: *
X-Spam-Status: No, score=1.137 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, HELO_MISMATCH_ORG=0.611, HOST_EQ_STATIC=1.172, 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 Ev0ZX8Lp2eRc for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:35:37 -0700 (PDT)
Received: from rolamasao.org (68.167.216.87.static.jazztel.es [87.216.167.68]) by ietfa.amsl.com (Postfix) with ESMTP id B23F021E8056 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:35:33 -0700 (PDT)
Received: from tochox.localnet (localhost [IPv6:::1]) by rolamasao.org (Postfix_t) with ESMTPSA id 389D111EF2 for <ietf@ietf.org>; Tue, 22 Oct 2013 22:35:29 +0100 (WEST)
From: Noel David Torres =?iso-8859-1?q?Ta=F1o?= <envite@rolamasao.org>
To: ietf@ietf.org
Subject: doubt about WG for e-mail protocol enhancement
Date: Tue, 22 Oct 2013 22:35:24 +0100
User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2417602.QqME8rqItK"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201310222235.25509.envite@rolamasao.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 21:35:56 -0000

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

Hi all

I have an idea for e-mail enhancement regading security and spam. Which Working Group should I join to?

Thanks in advance

Noel Torres
er Envite
-------------------------
A: Because it breaks the logical flow of discussion.
Q: Why is top posting bad?

--nextPart2417602.QqME8rqItK
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAlJm750ACgkQcLQA8+7Hw3JOfwCgjDjuqETrPTRTHJlZEtWhWIf+
xFoAn0oiJfCo3SVHp9ipjfqcQnL1f8Ej
=BjBy
-----END PGP SIGNATURE-----

--nextPart2417602.QqME8rqItK--

From tytso@thunk.org  Tue Oct 22 14:43:35 2013
Return-Path: <tytso@thunk.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 1D75221E8083 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:43:28 -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 9d0wVVmxepzr for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:43:12 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 3437A21F9DD6 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:43:12 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1VYjjK-0005IE-0b; Tue, 22 Oct 2013 21:43:10 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 0466758087B; Tue, 22 Oct 2013 17:43:07 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1382478188; bh=w7Hsd+r/2QRlzEHRO+iKLH0hvzjh67oGliKnii2Va9Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cgDWghZ6aErSFzsAaACPop4iQ7TnHlgz2h9C0z4nmuByCJfc9+BvjWixXhGGjw1Us HwIsQK94O1FbcgSfJWrHn6tDheT8T6ggVmfKRgHgBjEL4j+YuITJ5J8uu5hocBCOEA Aj6iA/t4hYaLzaD4kxpma4xeH1TqCFFmWQ//VQWo=
Date: Tue, 22 Oct 2013 17:43:07 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131022214307.GA2603@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
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, 22 Oct 2013 21:43:35 -0000

On Tue, Oct 22, 2013 at 02:15:13PM +0000, Ted Lemon wrote:
> 
> The path is harassment->ombudsbeing, not harassment->wg chair.  I
> would expect the ombudsperson to push back at this point unless
> something inappropriate was said.  If someone says "that's a stupid
> idea, because FOO" and "because FOO" is valid, then it would be
> appropriate for the ombudsperson to say to the offending party, "you
> know, you didn't need to say that was a stupid ideaâ€”all you needed
> to say was 'because FOO.'".  OTOH, if the offending party said "I'm
> going to cut off a deer's head and leave it in your refrigerator if
> you don't stop denying that FOO," then that would elicit a different
> response.

What about a slide presentation in a wg discussion in perpass which
included the following image?

     http://blog.chron.com/nickanderson/tag/nsa/

Bjoern Hoehrmann has already asserted he believes it would be
considered harassment.

						- Ted

From john-ietf@jck.com  Tue Oct 22 14:49: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 2A5F911E8269 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.552
X-Spam-Level: 
X-Spam-Status: No, score=-103.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 9d4XOogIiX6q for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:49:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F67111E8276 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:48:24 -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 1VYjo7-0003n5-EH; Tue, 22 Oct 2013 17:48:07 -0400
Date: Tue, 22 Oct 2013 17:48:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Randy Bush <randy@psg.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Message-ID: <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
In-Reply-To: <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.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 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, 22 Oct 2013 21:49:20 -0000

--On Tuesday, October 22, 2013 21:21 +0000 Ted Lemon
<Ted.Lemon@nominum.com> wrote:

> On Oct 22, 2013, at 4:55 PM, Randy Bush <randy@psg.com> wrote:
>> i am a bit taken aback by the vigilantism.  
>> 
>> it was just an email message, and a factual one at that.  the
>> usual example is _falsely_ shouting "fire" specifically
>> because it can cause *actual* *physical* *harm*.  get a
>> delete key.  get procmail.  get a grip.
> 
> Right, that's not the policy.   If that were the policy, a
> number of notorious abusers of the mailing list would still
> have posting privileges.
> 
> If the first message had been the beginning of a conversation,
> I would have taken it a lot differently, but the way it was
> dropped on the list with no discussion, it just looked like an
> attempt to start a massive flame war.   That's exactly the
> sort of thing that the sergeant-at-arms is supposed to deal
> with.

Ted, that is, IMO, an entirely reasonable comment about
inappropriate content, but, even then, our normal practice is
for the sergeant-at-arms or some other appropriate parties to
discuss and warn (usually and preferably in private first), not
take preemptive action.  "Discuss and warn first" may be a
first-order approximation to Randy's observation about due
process, or at least part of it.

The other thing that may make this situation special is that
several people are convinced that, despite the new address, the
person who made the posting is a serial (or, in your terms,
"notorious") abuser who has been banned from IETF lists before.
If that is actually the case, then preemptive action to prevent
further postings is appropriate, possibly including initiating
the RFC 3683 procedure and being done with this.

But none of that has anything to do with anonymity.  

I think it is reasonable to expect that, if the sergeant-at-arms
concludes that public action is necessary, that action and the
reasoning for it be carefully and precisely explained and even
adjusted for the record after the fact if the explanation wasn't
quite right.  If nothing else, getting the right documentation
in place is very important should anyone ever decide to
initiation a 3683-style global posting rights action.

I do not intend to criticize Jordi in any of this.  We
(fortunately) rarely have the provocation and need to do this.
We need to rely on good judgment rather than collections of
specific-seeming rules that would, themselves, be likely sources
of controversy and his judgment has generally been good.  We
should, however, all try to learn from experience, including
this one.

And, fwiw, I think we should try to see what can be learned that
might apply to harassment complaints.  By their nature, IMO,
those complaints are much more likely to be subjective and
difficult than whether someone has abused or improperly used a
mailing list.

   best,
   john



From prvs=00008272c5=johnl@iecc.com  Tue Oct 22 14:51:30 2013
Return-Path: <prvs=00008272c5=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 71ED811E8289 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.356
X-Spam-Level: 
X-Spam-Status: No, score=-1.356 tagged_above=-999 required=5 tests=[AWL=-1.057, BAYES_00=-2.599, MANGLED_SPAM=2.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 54Fzq-ayfJnm for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:51:25 -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 5F36F11E82C8 for <ietf@ietf.org>; Tue, 22 Oct 2013 14:50:14 -0700 (PDT)
Received: (qmail 52935 invoked from network); 22 Oct 2013 21:49:45 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Oct 2013 21:49:45 -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=5266f2f8.xn--i8sz2z.k1310; i=johnl@user.iecc.com; bh=cf3rP4f6D/NC6emsT0p/8vNqTBq59Ff82X8pN0nkRGc=; b=OzeWY9CjQn2+tY0vLbD8flLwgnxtqz8y9H5pt+quvijV3Q7iKNFYAAcMzChDc1GrFPC8BJ/dv70mDKaJS0bLWfQvCdBW8rQOTyPiLh0HlCkrEiF8tLluLcTA/f7S7qSMsFOmE+a74TOdNwh9xBw1+hlHxIXqBRILLt6bjX+q3sTD8wKuyMRJu4w6yKXSRLiTsmsAgUteeFcMC9SUSTXp6xylpbkNA8omLhKrsbxx3RqJ2Zp34ojnrPA6fWMKzNAu
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=5266f2f8.xn--i8sz2z.k1310; olt=johnl@user.iecc.com; bh=cf3rP4f6D/NC6emsT0p/8vNqTBq59Ff82X8pN0nkRGc=; b=OTejpiLDXPiG8yGDNZT0qleyTyY46FdPYW0KzegMXZ3i6HyRfcM0Cx9UxrUaPWt8AD1uDF9mXoFjAYTvMa3vUZ2DHMtXpzGVH9xgJ/iAxmI1EYpxU1CoKgq0Yurj1SGvH7ZOQwqyB1eGwRMrbY/JhRlo3KYrlsX6+nrNcUduUE1JHaeiKE9762PTvg9UpDQgdmOGpNkBWbYa+h32T91ATlhsT3uZ99+r6XQ6F9aqvc7tgZXITBK796ghJcUqucTb
Date: 22 Oct 2013 21:49:22 -0000
Message-ID: <20131022214922.3673.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: doubt about WG for e-mail protocol enhancement
In-Reply-To: <201310222235.25509.envite@rolamasao.org>
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: Tue, 22 Oct 2013 21:51:31 -0000

The appsarea list would be the appropriate place, but first you might
want to check the wiki from the former Anti-Spam Research Group and
see if we already know about it.

http://wiki.asrg.sp.am/wiki/Taxonomy_of_anti-spam_techniques

R's,
John


>I have an idea for e-mail enhancement regading security and spam. Which Working Group should I join to?
>
>Thanks in advance
>
>Noel Torres
>er Envite
>-------------------------
>A: Because it breaks the logical flow of discussion.
>Q: Why is top posting bad?


From john-ietf@jck.com  Tue Oct 22 14:57: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 BAE0811E821F for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.404
X-Spam-Level: 
X-Spam-Status: No, score=-103.404 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 8p3pf0VHb9ig for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 14:57:13 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 44F8811E827A for <ietf@ietf.org>; Tue, 22 Oct 2013 14:57: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 1VYjwp-0003nt-27; Tue, 22 Oct 2013 17:57:07 -0400
Date: Tue, 22 Oct 2013 17:57:01 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Noel_David_Torres_Ta=C3=B1o?= <envite@rolamasao.org>
Subject: Re: doubt about WG for e-mail protocol enhancement
Message-ID: <F3F1CAC8247BB39A0A968B4A@JcK-HP8200.jck.com>
In-Reply-To: <201310222235.25509.envite@rolamasao.org>
References: <201310222235.25509.envite@rolamasao.org>
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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 21:57:45 -0000

--On Tuesday, October 22, 2013 22:35 +0100 Noel David Torres
Ta=C3=B1o <envite@rolamasao.org> wrote:

> Hi all
>=20
> I have an idea for e-mail enhancement regading security and
> spam. Which Working Group should I join to?

There is no active IETF WG devoted to those topics although,
depending on what you want to propose, some might overlap.

With no disrespect intended, but with memories of seeing a lot
of messages and discussions that started out like the above,
please start by carefully reading
http://www.rhyolite.com/anti-spam/you-might-be.html.  If any of
the comments appear to apply to your idea, consider just moving
on to something else.   If not, you might investigate whether
MAAWG has some activities that overlap with your concerns and
solutions.

If the IETF is the right answer, it is often better to get an
Internet Draft posted that carefully explains the problem you
believe needs a solution and why your approach solves it before
going WG-shopping.

Speaking for myself only.
    john


From l.wood@surrey.ac.uk  Tue Oct 22 15:00:08 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 E8B5C11E8266; Tue, 22 Oct 2013 15:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.788
X-Spam-Level: 
X-Spam-Status: No, score=-3.788 tagged_above=-999 required=5 tests=[AWL=-0.190, 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 1uh5GoFRRiKM; Tue, 22 Oct 2013 15:00:05 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.176]) by ietfa.amsl.com (Postfix) with ESMTP id 6F04F21F9DA9; Tue, 22 Oct 2013 15:00:04 -0700 (PDT)
Received: from [85.158.137.99:51549] by server-16.bemta-3.messagelabs.com id 03/D7-18787-365F6625; Tue, 22 Oct 2013 22:00:03 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-217.messagelabs.com!1382479202!13413954!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2865 invoked from network); 22 Oct 2013 22:00:02 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-8.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 22 Oct 2013 22:00:02 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.216]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 22 Oct 2013 23:00:02 +0100
From: <l.wood@surrey.ac.uk>
To: <jordi.palet@consulintel.es>, <ietf-secretariat@ietf.org>
Date: Tue, 22 Oct 2013 23:00:01 +0100
Subject: RE: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: Ac7OlxV/UqskQNj+RdqCrrv/OsTi/QA2G/SH
Message-ID: <290E20B455C66743BE178C5C84F1240847E3E25D90@EXMB01CMS.surrey.ac.uk>
References: <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>, <CE8B4F40.B9893%jordi.palet@consulintel.es>
In-Reply-To: <CE8B4F40.B9893%jordi.palet@consulintel.es>
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, 22 Oct 2013 22:00:09 -0000

"Jordi" (if that is indeed your real name)

> As Sergeant-at-arms, I agree with other previous postings and believe tha=
t
> anonymous posting is not tolerable in the IETF mail exploders.

Is that IETF policy?

As sergeant-at-arms, you should be implementing previously agreed consensus=
 IETF policy, not taking the results of an opinion poll on the hoof.

You're entitled to have a personal opinion and belief on this, but you can'=
t then express that opinion as "sergeant-at-arms". It's a personal belief, =
under a different hat. Therefore, wherever you say "I believe" I read "my p=
ersonal opinion can be disregarded in and is entirely separate to previous =
consensus that my role as sergeant-at-arms enforces"

By "avoid" you mean "ban" or "censor", no?

And that blanket ban on anonymous emails suggested by your last paragraph r=
aises policy concerns. Just picking an example, "sm@resistor.net" seems qui=
te anonymous to me. I have no idea who that person is. I would therefore re=
quest that that person be banned from the IETF list under your terms, excep=
t by what you say that address is now banned automatically, along with all =
other email addresses that person attempts to use? And how does this automa=
tic identification and banning of anonymous mail addresses work, anyway?

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

thinks any discussion of ISOC is entirely appropriate for the IETF main lis=
t. Yay, transparency!


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of JORDI PALE=
T MARTINEZ [jordi.palet@consulintel.es]
Sent: 21 October 2013 20:45
To: mars.techno.cat@gmail.com; IETF Secretariat
Cc: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

Hi,

As Sergeant-at-arms, I agree with other previous postings and believe that
anonymous posting is not tolerable in the IETF mail exploders. Moreover, I
also believe that this the content of your emails are off-topic to the
IETF, even ISOC is the IETF umbrella, ISOC tax declaration and other
details is irrelevant to this list as well.

This is the reason why I've yesterday, instructed the secretariat to avoid
further postings from you.

If you decide to identify yourself, as the rest of the posters, and be
on-topic, you will be allowed to post again.

Meanwhile, refrain to use other anonymous emails, as the secretariat will
automatically keep banning you.

Regards,
Jordi






-----Mensaje original-----
De: Techno CAT <mars.techno.cat@gmail.com>
Responder a: <mars.techno.cat@gmail.com>
Fecha: lunes, 21 de octubre de 2013 20:04
Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Jordi Palet Martinez <jordi.palet@consulintel.es>, <ietf@ietf.org>,
<bortzmeyer@nic.fr>, Jari Arkko <jari.arkko@piuha.net>
Asunto: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

>"Calling someone a troll is an ad hominem.  We aren't supposed to do that
>in the IETF.  At least, not publicly."[1]
>
>"It is rude.
>It is bullying." [2]
>
>HARASSMENT by Brian E Carpenter has been noted for the Legal Record
>
>http://www.cs.auckland.ac.nz/~brian/
>"Network Geeks - How They Built the Internet"
>
>=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
>
>
>HARASSMENT by Stephane Bortzmeyer <bortzmeyer at nic.fr
><mailto:bortzmeyer@DOMAIN.HIDDEN>> has been noted for the Legal Record
>http://www.ietf.org/mail-archive/web/ietf/current/msg83330.html
>
>=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
>
>http://www.ietf.org/mail-archive/web/ietf/current/msg83360.html
>"judgment needs to be applied by the ombudsperson & the rest of the IETF
>management
>
>[1] http://www.ietf.org/mail-archive/web/ietf/current/msg83364.html
>[2] http://www.ietf.org/mail-archive/web/ietf/current/msg83362.html
>
>"you are encouraged to raise your concern in confidence with one of the
>Ombudspersons"
>http://www.intgovforum.org
>http://990s.foundationcenter.org/990_pdf_archive/541/541650477/541650477_2
>01112_990.pdf
>
>
>
>
>On Sat, Oct 19, 2013 at 4:37 PM, Brian E Carpenter
><brian.e.carpenter@gmail.com> wrote:
>
>Hi Jordi,
>
>We seem to have a new troll using the address mars.techno.cat@gmail.com
>
>Can you deal with it appropriately, please?
>
>Thanks
>
>    Brian
>
>
>
>
>
>
>
>--
>
>@Techno_CAT_r
>http://Twitter.com/Techno_CAT_r
>
>



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From prvs=1007c7129b=jordi.palet@consulintel.es  Tue Oct 22 15:02:30 2013
Return-Path: <prvs=1007c7129b=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83ED511E8284 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.289
X-Spam-Level: 
X-Spam-Status: No, score=-106.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 6xWYQJKpQgNf for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:02:26 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD1411E821F for <ietf@ietf.org>; Tue, 22 Oct 2013 15:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1382479342; x=1383084142; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=XPDZTWGiM5wfNOm99SgESumnp Qtrabna8iHo5Gn0/sE=; b=Dg+0/e22G8Z1qDby3geUfF1CMqfCTfQmbiYrEromM Cz00lirHZNcWQLl18qIDC+3CzUz4+bXtaQhtzEAOtYfkZq5IEU3oB50hCn2zm53/ LFUq0ncVo0FVkg1K4oO1SEoCMA851zt4IcamYCqj4tv6soHL0f4Yh9nnsgrpIvJr 6k=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=hrmcbUa1RQTsPRoz5SoFTD9SRaMMC5ZzcjvsN5RtRxKEmDpTePpHBReiz8bS SSr098CcfMl3KRljER1rJX1UF3A4Q0S2oe4Qp6nV1ehdVj6vdG5PnbrRX VoGaKN+2M6AeQGxL92kpLImZYUyfCQQo4tcvJ9HZNPuV1T1ER4tOPs=;
X-MDAV-Processed: consulintel.es, Wed, 23 Oct 2013 00:02:22 +0200
Received: from [10.10.10.102] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004495667.msg for <ietf@ietf.org>; Wed, 23 Oct 2013 00:02:21 +0200
X-Spam-Processed: consulintel.es, Wed, 23 Oct 2013 00:02:21 +0200 (not processed: message from trusted or authenticated source)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:131022:md50004495667::5FG4PL91wskc99LQ:000084js
X-MDRemoteIP: 87.216.40.21
X-Return-Path: prvs=1007c7129b=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Date: Wed, 23 Oct 2013 00:01:46 +0200
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <Ted.Lemon@nominum.com>, Melinda Shore <melinda.shore@gmail.com>
Message-ID: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <DD0DDB9E-0542-44FB-B4C6-1BDF86654841@nominum.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Oct 2013 22:02:30 -0000

I may have worded out too quickly my email, and actually looks like it was
more important for my decision the anonymity issue vs the off-top
question, but is still my opinion that this address must be banned.

We could take a decision on future anonymous postings, if required, I'm
always pro-privacy, but I don't think this is applicable in IETF works,
and this include exploders. Again this is my personal point of view.

Regards,
Jordi






-----Mensaje original-----
De: Ted Lemon <Ted.Lemon@nominum.com>
Responder a: <Ted.Lemon@nominum.com>
Fecha: martes, 22 de octubre de 2013 23:13
Para: Melinda Shore <melinda.shore@gmail.com>
CC: "<ietf@ietf.org>" <ietf@ietf.org>
Asunto: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

>On Oct 22, 2013, at 4:49 PM, Melinda Shore <melinda.shore@gmail.com>
>wrote:
>> Right, but as a matter of public record,
>> 
>>  "As Sergeant-at-arms, I agree with other previous
>>  postings and believe that anonymous posting is not
>>  tolerable in the IETF mail exploders."
>> 
>> really should not be allowed to stand.
>
>Let's give Jordi some time to respond.   I don't think he reads the list
>more than once a day, so he's probably innocently wondering why his ears
>are burning.
>



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From huitema@microsoft.com  Tue Oct 22 15:29:44 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53E211E827A for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:29:44 -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 HJOMhyAYPjIg for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:29:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) by ietfa.amsl.com (Postfix) with ESMTP id 4B47C11E8269 for <ietf@ietf.org>; Tue, 22 Oct 2013 15:29:37 -0700 (PDT)
Received: from BLUPR03CA037.namprd03.prod.outlook.com (10.141.30.30) by BLUPR03MB603.namprd03.prod.outlook.com (10.255.124.40) with Microsoft SMTP Server (TLS) id 15.0.800.7; Tue, 22 Oct 2013 22:29:35 +0000
Received: from BN1AFFO11FD019.protection.gbl (2a01:111:f400:7c10::185) by BLUPR03CA037.outlook.office365.com (2a01:111:e400:879::30) with Microsoft SMTP Server (TLS) id 15.0.785.10 via Frontend Transport; Tue, 22 Oct 2013 22:29:35 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD019.mail.protection.outlook.com (10.58.52.79) with Microsoft SMTP Server (TLS) id 15.0.805.12 via Frontend Transport; Tue, 22 Oct 2013 22:29:34 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.197]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.03.0158.002; Tue, 22 Oct 2013 22:28:25 +0000
From: Christian Huitema <huitema@microsoft.com>
To: John C Klensin <john-ietf@jck.com>, Ted Lemon <Ted.Lemon@nominum.com>, Randy Bush <randy@psg.com>
Subject: RE: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzROQldBHHC2H5Eu4MfQ1gxMTFJn/ddAAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAAJKYCAABMiAIAAB2aAgAAHUwCAAAroMA==
Date: Tue, 22 Oct 2013 22:28:24 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA18E5675E@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net>	<5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com>	<5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
In-Reply-To: <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.78]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51856001)(80976001)(50466002)(85306002)(4396001)(23726002)(69226001)(47976001)(77982001)(59766001)(47736001)(74706001)(49866001)(50986001)(74876001)(46102001)(54356001)(74366001)(76796001)(76786001)(77096001)(65816001)(44976005)(55846006)(85806002)(81686001)(81542001)(81342001)(80022001)(74502001)(6806004)(47446002)(66066001)(83072001)(81816001)(79102001)(56816003)(46406003)(53806001)(74662001)(31966008)(20776003)(47776003)(63696002)(54316002)(83322001)(56776001)(76482001)(33656001)(221513003)(222073002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB603; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 00073DB75F
X-OriginatorOrg: microsoft.com
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, 22 Oct 2013 22:29:44 -0000

> The other thing that may make this situation special is that several peop=
le are convinced that,=20
> despite the new address, the person who made the posting is a serial (or,=
 in your terms, "notorious")=20
> abuser who has been banned from IETF lists before.

Whoever that was, they certainly succeeded in creating a lot of noise on th=
e IETF list.

-- Christian Huitema



=20


From Ted.Lemon@nominum.com  Tue Oct 22 15:33:50 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 C2ECD11E8294 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.291
X-Spam-Level: 
X-Spam-Status: No, score=-106.291 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, J_CHICKENPOX_21=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 zM8fZG628W82 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:33:44 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0A31E11E81BA for <ietf@ietf.org>; Tue, 22 Oct 2013 15:33:44 -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 DSNKUmb9Rx4KQISDcjvygPiknOvecV/9Nqer@postini.com; Tue, 22 Oct 2013 15:33: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 85C4F1B82CE for <ietf@ietf.org>; Tue, 22 Oct 2013 15:33:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 6D6F6190052; Tue, 22 Oct 2013 15:33:43 -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.03.0158.001; Tue, 22 Oct 2013 15:33:37 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Proposed IETF Anti-Harassment Policy
Thread-Topic: Proposed IETF Anti-Harassment Policy
Thread-Index: AQHOzbxVzZsUK86MhUyC7IRlHFizLZoAeVGAgABzWwCAAE9xAIAAfSaAgAAOGoA=
Date: Tue, 22 Oct 2013 22:33:37 +0000
Message-ID: <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org>
In-Reply-To: <20131022214307.GA2603@thunk.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: <A9143CEAFEAFE44BA0DE0FAA118585D6@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, 22 Oct 2013 22:33:51 -0000

On Oct 22, 2013, at 5:43 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> What about a slide presentation in a wg discussion in perpass which
> included the following image?

My reaction to this is that it seems to trivialize types of real-world hara=
ssment that are quite common (although hopefully not common in the IETF).  =
 If this image were the worst "harassment" that our ombudsperson had to dea=
l with, that would seem to me to be very good news indeed.

But I don't work for the NSA, so maybe I'm missing something about this ima=
ge that someone who does work for the NSA would see.


From ben@nostrum.com  Tue Oct 22 15:36:38 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 61DD911E81BA; Tue, 22 Oct 2013 15:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.144
X-Spam-Level: 
X-Spam-Status: No, score=-102.144 tagged_above=-999 required=5 tests=[AWL=0.456, 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 tfyDwfmq4QyK; Tue, 22 Oct 2013 15:36:37 -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 B776B11E82A5; Tue, 22 Oct 2013 15:36:25 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r9MMaNaJ068860 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 22 Oct 2013 17:36:24 -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-ietf-ipfix-data-link-layer-monitoring-06
Date: Tue, 22 Oct 2013 17:36:25 -0500
Message-Id: <877E63A6-07D1-45C3-93EA-086871A8ADE7@nostrum.com>
To: draft-ietf-ipfix-data-link-layer-monitoring.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.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: Tue, 22 Oct 2013 22:36:38 -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-ipfix-data-link-layer-monitoring-06
Reviewer: Ben Campbell
Review Date: 2013-22-10
IETF LC End Date: 2013-23-10

Summary: Ready for publication as a proposed standard, with  one problem =
that should be easily fixed.

Major issues:

None

Minor issues:

3.2.18:

Title of the data element suggests a total, but the description sounds =
like a delta (i.e change since last report.)

-- section 4 and subsections

It looks like this draft updates at least RFC5477. If so, this should be =
indicated in the header and in the abstract.



Nits/editorial comments:

-- section , 3rd paragraph:

Do you mean to say the existing data models do not contain the elements =
needed, or that the models do not provide the right foundation for the =
needed elements? The wording seems to indicate the latter but I think =
you mean the former.

-- General:
Watch for missing articles.=

From richard@shockey.us  Tue Oct 22 15:49:59 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 B834E11E828E for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.999
X-Spam-Level: 
X-Spam-Status: No, score=-100.999 tagged_above=-999 required=5 tests=[AWL=-1.001, BAYES_50=0.001, 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 6--2W0e4NaW4 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:49:55 -0700 (PDT)
Received: from qproxy1-pub.mail.unifiedlayer.com (qproxy1-pub.mail.unifiedlayer.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 165C311E82A4 for <ietf@ietf.org>; Tue, 22 Oct 2013 15:49:53 -0700 (PDT)
Received: (qmail 28337 invoked by uid 0); 22 Oct 2013 22:49:31 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by qproxy1.mail.unifiedlayer.com with SMTP; 22 Oct 2013 22:49:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:To:From; bh=yX2mpJlyN7iJroEtJAhifyvU323YkwQ/DulOMrsnwVU=;  b=UjmOSgTyYneECLdPeebO4MoP+1KXX2A4fRiA5ttX/yrLd2aiGwy7h/OA0QzjUH+GS6XWyvdkkK8JTqvG1DFnCrMHN0Ygg+hrCDnIRGFBpZzS6FVJySfj5PW17LLYDSfz;
Received: from [71.114.100.16] (port=49567 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.80) (envelope-from <richard@shockey.us>) id 1VYklX-0005Mk-3W for ietf@ietf.org; Tue, 22 Oct 2013 16:49:31 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
Subject: International enforcement agencies join forces to thwart caller identification spoofing 
Date: Tue, 22 Oct 2013 18:49:27 -0400
Message-ID: <00a601cecf78$f799f3d0$e6cddb70$@shockey.us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A7_01CECF57.708AC4D0"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac7OqkGMSl6vo2TWRKGNfU4q0GsBDA==
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.114.100.16 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: Tue, 22 Oct 2013 22:49:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A7_01CECF57.708AC4D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

FYI .

 

http://www.crtc.gc.ca/eng/com100/2013/r131021.htm#.UmWltlN8CaU

 

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
< <mailto:richard(at)shockey.us> mailto:richard(at)shockey.us>
skype-linkedin-facebook: rshockey101
http//www.sipforum.org

"Money is the answer, what is the question?" tm 

 

 


------=_NextPart_000_00A7_01CECF57.708AC4D0
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=3DGenerator content=3D"Microsoft Word 15 =
(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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.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=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>FYI =
&#8230;<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>http://www.crtc.gc.ca/eng/com100/2013/r131021.htm#.UmWl=
tlN8CaU<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Richard =
Shockey<br>Shockey Consulting<br>Chairman of the Board of Directors SIP =
Forum<br>PSTN Mobile: +1 703.593.2683<br>&lt;<a =
href=3D"mailto:richard(at)shockey.us"><span =
style=3D'color:blue'>mailto:richard(at)shockey.us</span></a>&gt;<br>skype=
-linkedin-facebook: =
rshockey101<br>http//www.sipforum.org<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif"'>&quot;Money is the answer, what is the question?&quot; =
tm <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00A7_01CECF57.708AC4D0--


From tytso@thunk.org  Tue Oct 22 15:54:52 2013
Return-Path: <tytso@thunk.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 901B811E8289 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:54: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 GBje14aPPfxM for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 15:54:51 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id D004211E823F for <ietf@ietf.org>; Tue, 22 Oct 2013 15:54:51 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1VYkqg-0005ae-HU; Tue, 22 Oct 2013 22:54:50 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 40C2058087B; Tue, 22 Oct 2013 18:54:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1382482488; bh=deovwozaZgAjB+5zrNerMHbz0zEYO3oYJgitee49C5I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Z/zc6u8EE0bGuhqNzaiBdn+nZQszmQIuUiTgiDznOqYI3nTypc1jjLVuCUzDGC658 ucOq642TdSmmiICgi8GHbI4LVyDBtEoSzLAQCS1xCTrZ0C61TQylIZWN9EkZqFB2oC dsG3jEJlSmLUCWwh64D3yb2tQUQTfKOMhepK5Yy0=
Date: Tue, 22 Oct 2013 18:54:48 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131022225448.GA18249@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org> <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
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, 22 Oct 2013 22:54:52 -0000

On Tue, Oct 22, 2013 at 10:33:37PM +0000, Ted Lemon wrote:
> 
> My reaction to this is that it seems to trivialize types of
> real-world harassment that are quite common (although hopefully not
> common in the IETF).  If this image were the worst "harassment" that
> our ombudsperson had to deal with, that would seem to me to be very
> good news indeed.

Actually, looking at the policy more closely, I believe it shouldn't
be a problem and Bjoern Hoehrmann's assertions are specious.  To quote
from the policy:

   Harassment is unwelcome hostile or intimidating behavior, in
   particular speech and behavior that is sexually aggressive or
   intimidates based on attributes like race, gender, religion, age,
   color, national origin, ancestry, disability, sexual orientation,
   or gender identity.

People who work at the NSA are not a protected class by the above
definition, so there would be no grounds for a complaint of
harassment.  Indeed, by this strict definition, even something like,

   "Actually, X, Y, and Z, means that that making change A to the spec
   would result in failure mode B, as any idiot could see."

... might not be professional language, but it wouldn't be harassment.

    	      	 	      		    - Ted

From scott.brim@gmail.com  Tue Oct 22 16:08:19 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 A55BA11E8295 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 16:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, 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 3PQT1dx1waOq for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 16:08:19 -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 2C16F11E8291 for <ietf@ietf.org>; Tue, 22 Oct 2013 16:08:18 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id va2so24097obc.26 for <ietf@ietf.org>; Tue, 22 Oct 2013 16:08: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=g4bUnhbNVYwzEe5oiBXZW2xtVSdHA+8vGeEHWdybIjc=; b=R6dMsBfVhqEByq8gtzVrRJlxOLAcGk4rTHaBEMVkhzSvc3QaNU0AT6R2UQrK9EF1/R L6em2Cxf2MunKNS2N2yJYE6a6dgBZ8DIGwqKn6gIA8R8r3AyYA04u3Q9Csuvw2nTRgKk qPOsof4uCN0AaIz+oHBMYoOD0i+a3YptUk99DjXc2/KDAnW6HRnm/Mn8eoBstD3ynCNR mi/KVpVjdTkrqKc7pQPmi9oBjCaquVVGppe5AP0t6qjpbmvzVR9WULmKRwpYjjGDIIbH uitTZtwA2Vh7tLz6bF53z9AavJaxg/KkkkjzIz3olK78LfG/sLmx6Gx6/Ds6kWjZ7obI REsw==
MIME-Version: 1.0
X-Received: by 10.182.45.195 with SMTP id p3mr27606192obm.29.1382483297598; Tue, 22 Oct 2013 16:08:17 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Tue, 22 Oct 2013 16:08:17 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Tue, 22 Oct 2013 16:08:17 -0700 (PDT)
In-Reply-To: <20131022225448.GA18249@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org> <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com> <20131022225448.GA18249@thunk.org>
Date: Tue, 22 Oct 2013 19:08:17 -0400
Message-ID: <CAPv4CP8mwnhqSLbek0JZ0B9gqaczA1qG2_PpdY6OqWWQs9cjcw@mail.gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Scott Brim <scott.brim@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=089e01537e42dc85a404e95c79e1
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, 22 Oct 2013 23:08:19 -0000

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

Ok, we are already at the stage of "that's harassment", "no it's not".

This is why I (hurriedly) and others suggested it should be more
subjective. The purpose is productive relationships, so what's important is
how people feel. Only have a lightweight definition of harassment, and some
examples.  Give people a process by which they can tell others (directly or
through an intermediary) how they feel about what they hear and work toward
better collaboration.  Forget punishment for now.

Scott
On Oct 22, 2013 6:55 PM, "Theodore Ts'o" <tytso@mit.edu> wrote:

> On Tue, Oct 22, 2013 at 10:33:37PM +0000, Ted Lemon wrote:
> >
> > My reaction to this is that it seems to trivialize types of
> > real-world harassment that are quite common (although hopefully not
> > common in the IETF).  If this image were the worst "harassment" that
> > our ombudsperson had to deal with, that would seem to me to be very
> > good news indeed.
>
> Actually, looking at the policy more closely, I believe it shouldn't
> be a problem and Bjoern Hoehrmann's assertions are specious.  To quote
> from the policy:
>
>    Harassment is unwelcome hostile or intimidating behavior, in
>    particular speech and behavior that is sexually aggressive or
>    intimidates based on attributes like race, gender, religion, age,
>    color, national origin, ancestry, disability, sexual orientation,
>    or gender identity.
>
> People who work at the NSA are not a protected class by the above
> definition, so there would be no grounds for a complaint of
> harassment.  Indeed, by this strict definition, even something like,
>
>    "Actually, X, Y, and Z, means that that making change A to the spec
>    would result in failure mode B, as any idiot could see."
>
> ... might not be professional language, but it wouldn't be harassment.
>
>                                             - Ted
>

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

<p dir=3D"ltr">Ok, we are already at the stage of &quot;that&#39;s harassme=
nt&quot;, &quot;no it&#39;s not&quot;.=A0 </p>
<p dir=3D"ltr">This is why I (hurriedly) and others suggested it should be =
more subjective. The purpose is productive relationships, so what&#39;s imp=
ortant is how people feel. Only have a lightweight definition of harassment=
, and some examples.=A0 Give people a process by which they can tell others=
 (directly or through an intermediary) how they feel about what they hear a=
nd work toward better collaboration.=A0 Forget punishment for now.</p>

<p dir=3D"ltr">Scott </p>
<div class=3D"gmail_quote">On Oct 22, 2013 6:55 PM, &quot;Theodore Ts&#39;o=
&quot; &lt;<a href=3D"mailto:tytso@mit.edu">tytso@mit.edu</a>&gt; wrote:<br=
 type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Oct 22, 2013 at 10:33:37PM +0000, Ted Lemon wrote:<br>
&gt;<br>
&gt; My reaction to this is that it seems to trivialize types of<br>
&gt; real-world harassment that are quite common (although hopefully not<br=
>
&gt; common in the IETF). =A0If this image were the worst &quot;harassment&=
quot; that<br>
&gt; our ombudsperson had to deal with, that would seem to me to be very<br=
>
&gt; good news indeed.<br>
<br>
Actually, looking at the policy more closely, I believe it shouldn&#39;t<br=
>
be a problem and Bjoern Hoehrmann&#39;s assertions are specious. =A0To quot=
e<br>
from the policy:<br>
<br>
=A0 =A0Harassment is unwelcome hostile or intimidating behavior, in<br>
=A0 =A0particular speech and behavior that is sexually aggressive or<br>
=A0 =A0intimidates based on attributes like race, gender, religion, age,<br=
>
=A0 =A0color, national origin, ancestry, disability, sexual orientation,<br=
>
=A0 =A0or gender identity.<br>
<br>
People who work at the NSA are not a protected class by the above<br>
definition, so there would be no grounds for a complaint of<br>
harassment. =A0Indeed, by this strict definition, even something like,<br>
<br>
=A0 =A0&quot;Actually, X, Y, and Z, means that that making change A to the =
spec<br>
=A0 =A0would result in failure mode B, as any idiot could see.&quot;<br>
<br>
... might not be professional language, but it wouldn&#39;t be harassment.<=
br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 - Ted<br>
</blockquote></div>

--089e01537e42dc85a404e95c79e1--

From mohta@necom830.hpcl.titech.ac.jp  Tue Oct 22 17:03:15 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 521A111E82B3 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:03:15 -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 whSCcp7XPiJL for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:03:10 -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 C14D111E82AA for <ietf@ietf.org>; Tue, 22 Oct 2013 17:03:07 -0700 (PDT)
Received: (qmail 42107 invoked from network); 22 Oct 2013 23:57:22 -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; 22 Oct 2013 23:57:22 -0000
Message-ID: <526711D4.6010900@necom830.hpcl.titech.ac.jp>
Date: Wed, 23 Oct 2013 09:01:24 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: jordi.palet@consulintel.es, Ted.Lemon@nominum.com,  Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
In-Reply-To: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=ISO-2022-JP
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, 23 Oct 2013 00:03:15 -0000

JORDI PALET MARTINEZ wrote:

> We could take a decision on future anonymous postings, if required,

That no formal identification is required to join IETF mailing
lists nor face to face meetings means that we all are considered
to be anonymous, except that we can identify each other by one's
mail address, for which, "mars.techno.cat@gmail.com" is good
enough.

Or, do you think that "john@gmail.com" is fine but
"mars.techno.cat@gmail.com" is not?

						Masataka Ohta

From joelja@bogus.com  Tue Oct 22 17:39:33 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 8C5CD11E80DC for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:39: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 tNyNdzDtxfMv for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:39:31 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id BA88511E80E0 for <ietf@ietf.org>; Tue, 22 Oct 2013 17:39:31 -0700 (PDT)
Received: from [192.168.1.11] (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9N0dTUA002135 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 23 Oct 2013 00:39:30 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_E5456BAB-F365-4D89-AD67-42BB793CD2CE"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
Date: Tue, 22 Oct 2013 17:39:27 -0700
Message-Id: <FC2ED720-7F92-4F14-B133-4022579E8CDC@bogus.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <1812343AEDF0C2F4312AC768@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1510)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 23 Oct 2013 00:39:31 +0000 (UTC)
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, 23 Oct 2013 00:39:34 -0000

--Apple-Mail=_E5456BAB-F365-4D89-AD67-42BB793CD2CE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 22, 2013, at 2:48 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Tuesday, October 22, 2013 21:21 +0000 Ted Lemon
> <Ted.Lemon@nominum.com> wrote:
>=20
>> On Oct 22, 2013, at 4:55 PM, Randy Bush <randy@psg.com> wrote:
>>> i am a bit taken aback by the vigilantism. =20
>>>=20
>>> it was just an email message, and a factual one at that.  the
>>> usual example is _falsely_ shouting "fire" specifically
>>> because it can cause *actual* *physical* *harm*.  get a
>>> delete key.  get procmail.  get a grip.
>>=20
>> Right, that's not the policy.   If that were the policy, a
>> number of notorious abusers of the mailing list would still
>> have posting privileges.
>>=20
>> If the first message had been the beginning of a conversation,
>> I would have taken it a lot differently, but the way it was
>> dropped on the list with no discussion, it just looked like an
>> attempt to start a massive flame war.   That's exactly the
>> sort of thing that the sergeant-at-arms is supposed to deal
>> with.
>=20
> Ted, that is, IMO, an entirely reasonable comment about
> inappropriate content, but, even then, our normal practice is
> for the sergeant-at-arms or some other appropriate parties to
> discuss and warn (usually and preferably in private first), not
> take preemptive action.  "Discuss and warn first" may be a
> first-order approximation to Randy's observation about due
> process, or at least part of it.

Weirdly on last weeks' iesg informal, the issue of do we need to revisit =
the seargent at arms approach/methodology came up. RFC 3005 is a while =
ago and it not something that has had a lot of attention in the interim.=20=


I'm not personally interested in being highly proscriptive and in the =
end these things are going to come down to judgement calls with the =
potential for an appeals process. The infrequency with which they are =
applied I think says that in the general case they're not the first =
order tools for managing list discourse, but it also means when they are =
applied either the ducks really have to be in a row, or questions about =
the application will ensue.

> The other thing that may make this situation special is that
> several people are convinced that, despite the new address, the
> person who made the posting is a serial (or, in your terms,
> "notorious") abuser who has been banned from IETF lists before.
> If that is actually the case, then preemptive action to prevent
> further postings is appropriate, possibly including initiating
> the RFC 3683 procedure and being done with this.
>=20
> But none of that has anything to do with anonymity. =20
>=20
> I think it is reasonable to expect that, if the sergeant-at-arms
> concludes that public action is necessary, that action and the
> reasoning for it be carefully and precisely explained and even
> adjusted for the record after the fact if the explanation wasn't
> quite right.  If nothing else, getting the right documentation
> in place is very important should anyone ever decide to
> initiation a 3683-style global posting rights action.
>=20
> I do not intend to criticize Jordi in any of this.  We
> (fortunately) rarely have the provocation and need to do this.
> We need to rely on good judgment rather than collections of
> specific-seeming rules that would, themselves, be likely sources
> of controversy and his judgment has generally been good.  We
> should, however, all try to learn from experience, including
> this one.
>=20
> And, fwiw, I think we should try to see what can be learned that
> might apply to harassment complaints.  By their nature, IMO,
> those complaints are much more likely to be subjective and
> difficult than whether someone has abused or improperly used a
> mailing list.
>=20
>   best,
>   john
>=20
>=20


--Apple-Mail=_E5456BAB-F365-4D89-AD67-42BB793CD2CE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJnGr8ACgkQ8AA1q7Z/VrLCDwCeMAYzMrUeX4cObFriFzp5n+aE
eJYAn1I/vSPqQt77De0W4NIaDBmhrN+7
=4ckl
-----END PGP SIGNATURE-----

--Apple-Mail=_E5456BAB-F365-4D89-AD67-42BB793CD2CE--

From melinda.shore@gmail.com  Tue Oct 22 17:45:32 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 5D0A711E8164 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.132,  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 fZtI1zGfRgDk for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 17:45:31 -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 B42C211E81E3 for <ietf@ietf.org>; Tue, 22 Oct 2013 17:45:31 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so115092pbc.7 for <ietf@ietf.org>; Tue, 22 Oct 2013 17:45: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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jF9Py1PbwyGVvtyWNlv58bVEp+Aq5jkt1AuOhIyybdk=; b=HChnLp74LMsVzaKmujDqBf7evyScHRZmxH1jq4IT94HBV873Inm12D4csLr2tPByRL uTYoKnqx3BwOXe5z8R1+ldAGTVlaqp/B/1CwuQvE0JpZB/R3XLQ6Uh4qR89+8gqlXmAa gtjaFg1M58jm34t2KOZc5Wc2Ux+Y957KhN6PVS3U/HdbjHu1v5Kkka2eL1eqBY/vY+/7 oQzA+G26q+8J5t5AWo9NwNgLm4gD3AEpKT/H6DEdkzrkX1R+cVfW/Hv3L9mhgLOBgOgU kOuc8DuuMd8yXJeapZLNNUR1v++AAmA2r0K37Ep+QlmibTD/Mk0QXNZel/uFcV3eW3vB bE2A==
X-Received: by 10.68.4.232 with SMTP id n8mr447541pbn.9.1382489131413; Tue, 22 Oct 2013 17:45:31 -0700 (PDT)
Received: from spandex.local (63-140-89-93.dynamic.dsl.acsalaska.net. [63.140.89.93]) by mx.google.com with ESMTPSA id wr10sm514934pbc.17.2013.10.22.17.45.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Oct 2013 17:45:30 -0700 (PDT)
Message-ID: <52671C27.6040004@gmail.com>
Date: Tue, 22 Oct 2013 16:45: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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: jordi.palet@consulintel.es
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
In-Reply-To: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=ISO-8859-1
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, 23 Oct 2013 00:45:32 -0000

On 10/22/13 2:01 PM, JORDI PALET MARTINEZ wrote:
> We could take a decision on future anonymous postings, if required, I'm
> always pro-privacy, but I don't think this is applicable in IETF works,
> and this include exploders. Again this is my personal point of view.

Is this your personal point of view of what the IETF
has agreed to, or is this your personal point of view
of what the IETF policy ought to be?

We had that discussion of anonymity vs. pseudonymity several months
ago and I don't think that any specific policy came out of it.
Several areas of concern were identified, most notably that
there may be some IPR issues which are masked by not identifying
yourself sufficiently to be able to determine institutional
affiliation/employment.  That doesn't seem to apply here.  It
may be case that we need to establish more explicit policies
around pseudonymity in IETF participation.  I hope that's not
the case but I'd like to make sure that we aren't making a
stand for anonymity and privacy in theory while not making
one in practice.

Melinda


From michel@arneill-py.sacramento.ca.us  Tue Oct 22 20:35:20 2013
Return-Path: <michel@arneill-py.sacramento.ca.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 4ACA311E8116 for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 20:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.649
X-Spam-Level: 
X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=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 lsGHw3Xu7Kwl for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 20:35:12 -0700 (PDT)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) by ietfa.amsl.com (Postfix) with ESMTP id D3B3D11E80F5 for <ietf@ietf.org>; Tue, 22 Oct 2013 20:35:11 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: Internet standardisation remains unilateral
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Oct 2013 20:35:09 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CE0100FA@newserver.arneill-py.local>
x-mimeole: Produced By Microsoft Exchange V6.5
In-Reply-To: <CAMm+LwhvX3YyPritjkV_p7Le0pLVD5_HzuReA=vkpdBpc_4rNg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Internet standardisation remains unilateral
Thread-Index: Ac7PH3pMApu8fxD3QtyFSjkdI/3HTQAgIDtg
References: <20131021125834.GA24167@nic.fr><67E83EF109F9999F391CEC93@JcK-HP8200.jck.com><20131021133746.GA29267@nic.fr><673A097E66897B69B6C13B73@JcK-HP8200.jck.com><20131022035640.GA7434@mx1.yitter.info> <CAMm+LwhvX3YyPritjkV_p7Le0pLVD5_HzuReA=vkpdBpc_4rNg@mail.gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Phillip Hallam-Baker" <hallam@gmail.com>
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, 23 Oct 2013 03:35:20 -0000

> Phillip Hallam-Baker wrote:
> And what if that something is get the French government to
> contribute to a rival to IETF? Or combine with the governments
> of Brazil and Mexico to create a larger anti-IETF?
=20
Let them try it. It will fizzle when they lose the little traction they =
have now in the fallback of the Snowden leaks. In 2016 when Brazil (you =
picked it, not me) hosts the Olympic Games, they lose $100 million of =
per click advertizing because they have moved their stuff behind an =
alternate root or whatever pipe dream and nobody can access it? Have =
them eat their own dog food. History repeats itself; each time there is =
evidence of mismanagement from foreign powers, secessionist feelings =
flare and some smart @55 will exploit that to their own advantage.

> The key is IPv6.=20

Then you have a problem, because France is the only country that has =
remotely tried to deploy it.
Phillip, with all due respect for your very valuable past and present =
contributions, you're a dreamer. The reason you worry about the idea of =
the French government combining with Brazil and Mexico is as invalid as =
you think that IPv6 can be deployed. You believe in the dream, the =
market believes in money.

Get IPv6 deployed in the real world and then I will pay attention to the =
French threat to take over the IETF and the Internet. Otherwise it will =
get in the same state of "non-deployment" that is not to be worried =
about.


> Christian de Larrinaga wrote:
> Bakailao argi dago hizkuntza unibertsala! RFCs
> arrantza espedizioak dira. Ez dago?

I knew some Basque would step in! Thanks for playing, Christian ;-)

Let's make a deal about the official IETF language:
Mondays: Basque
Tuesdays: Catalan
Wednesdays: French
Thursdays: Norwegian
Fridays: Spanish
Saturdays: Esperanto
Sundays: English

Deal ?


> Roger J=F8rgensen wrote:
> What I personal is very sure of is that it will not changed to
> Norwegian (where I'm from), or any other European language.

+1

That being said, and back to the point I have painfully trying to make, =
I have not felt the resistance to English from people in your native =
country nearly as much as I have felt it in my native France.


> Take a wild guess what language that might get some
> of that in near future (10-20years). China.

Your logic is flawless, for a wild guess. It would be my #1 pick as =
well; size does matter. That being said, many people in the US feared =
that it would happen with India in the software development market years =
ago, and it did not happen. As Jorge put it very nicely, US-based =
corporations have managed to assimilate Indian talent, and it is no =
mystery that they are trying to assimilate Chinese talent.

Define assimilate? We are the Borg. Resistance is futile.=20

Michel.


From sm@resistor.net  Tue Oct 22 22:42: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 4D39A11E82DC for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 22:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 LCBhncXlrcLF for <ietf@ietfa.amsl.com>; Tue, 22 Oct 2013 22:42:54 -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 4386E11E80DE for <ietf@ietf.org>; Tue, 22 Oct 2013 22:42:50 -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 r9N5ggGo028569; Tue, 22 Oct 2013 22:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382506967; bh=Y4ew7XGUM5aBu0QrmKnCh6d+4MSz77eL5B2Caq1QcBo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rk7Bv+cGdPmT/GsBolw7yVd0qyYOgpTuiGQ5eZOrJdibOgEniyMOuHoYeRCh7KEUZ GVKDFggjyj8EjYXWXiclV5IWbP33PV8nV/E9BUgKm8GdwFkHJB8neq+KyPGpbQ6/s5 SrGUS1Udh9orfgCIemhYTyX1Edr4+OoO1BqIH1wg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382506967; i=@resistor.net; bh=Y4ew7XGUM5aBu0QrmKnCh6d+4MSz77eL5B2Caq1QcBo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=q8gwyLPObGRwgOeQ8RloUPF4eSpcsRoUdxqst3qwMrKtTxE/RkABlwXvhme2JLLrZ dq/RGVOOXoqOhE+GlBwhVjXKBR9VSkqX6r8QY9ga9gvHfLEAnvYObFhRTDa4oy94ZQ 6DRTZ0M5wKz99h4SdGt3r/MvBpaHxU5sbE6YKF6o=
Message-Id: <6.2.5.6.2.20131022210808.0db07578@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 22 Oct 2013 22:37:20 -0700
To: jordi.palet@consulintel.es
From: SM <sm@resistor.net>
Subject: Re: Sergeant at arms: please deal with [censored]
In-Reply-To: <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
References: <DD0DDB9E-0542-44FB-B4C6-1BDF86654841@nominum.com> <CE8CC0B9.B9B46%jordi.palet@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 23 Oct 2013 05:42:56 -0000

Hi Jordi,
At 15:01 22-10-2013, JORDI PALET MARTINEZ wrote:
>I may have worded out too quickly my email, and actually looks like it was
>more important for my decision the anonymity issue vs the off-top
>question, but is still my opinion that this address must be banned.
>
>We could take a decision on future anonymous postings, if required, I'm
>always pro-privacy, but I don't think this is applicable in IETF works,
>and this include exploders. Again this is my personal point of view.

There was a decision to ban (see above) an email address because of 
two messages sent to the mailing list.  I read the mailing list 
archive and did not find any warning.  The advice given was:

   "If you decide to identify yourself, as the rest of the posters, and be
    on-topic, you will be allowed to post again."

I read the quoted text (see above).  I cannot tell which part of it 
is a personal opinion and which part is the opinion of the 
sergeant-at-arms.  The decision comes out as "I don't like what you 
said.  The explanation for my decision might not be that good but I 
already made up my mind".  The rest of the posters do not identify 
themselves unless a person considers that [local-part]@gmail.com 
conveys any meaningful information.

Regards,
-sm 


From abdussalambaryun@gmail.com  Wed Oct 23 02:11:54 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 2B3DA11E8345 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 02:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.233
X-Spam-Level: 
X-Spam-Status: No, score=-2.233 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=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 B9KSV18QM2HF for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 02:11:53 -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 036CE21E80AC for <ietf@ietf.org>; Wed, 23 Oct 2013 02:11:40 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so643341pbc.17 for <ietf@ietf.org>; Wed, 23 Oct 2013 02:11: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:date:message-id:subject:from:to :cc:content-type; bh=+hbI903CV3HBVJraunPUVB8i6GYwmRyW6QGfMrGKoM8=; b=hNxhBISyLyYFBamGmQL/TRiAX4KQGtv6ZSskVni9vrT0nwr8EthMTq3pL1nSQfcXCm 22JG5hDuzK8kuKr7qNQmFbOZpGSgWSHdAMTg+pmC+PAptgnhpQkILXxTC90Fcn0yG6ip rY04x48kofsO1pbScFKm6MEw9SNEA/sQp62ZH+vt1dUEu8IEKN4PE68gK0b9KPD+iEJp t0hTqDq1m/ZM/5gxCIOywN//FVAffWOonl0WLb6/MB/v+ZRg/HuD2KiZsQiDyWlbGCDD 33qPhcanCZJrIuz0ziJBi+J1c4Un6Rr29pYtyV+F3b3BQsfK4DEzZqrjbvhumam3z9J9 sCag==
MIME-Version: 1.0
X-Received: by 10.68.197.36 with SMTP id ir4mr605598pbc.96.1382519500306; Wed, 23 Oct 2013 02:11:40 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 23 Oct 2013 02:11:40 -0700 (PDT)
In-Reply-To: <20131022225448.GA18249@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org> <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com> <20131022225448.GA18249@thunk.org>
Date: Wed, 23 Oct 2013 10:11:40 +0100
Message-ID: <CADnDZ89cMtiRc7+A6984oCEbd2K4XXgQEn7pPUXHWKwNMCbemQ@mail.gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=e89a8ff1c840b600d804e964e7ca
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, 23 Oct 2013 09:11:54 -0000

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

On Tue, Oct 22, 2013 at 11:54 PM, Theodore Ts'o <tytso@mit.edu> wrote:

> On Tue, Oct 22, 2013 at 10:33:37PM +0000, Ted Lemon wrote:
> >
> > My reaction to this is that it seems to trivialize types of
> > real-world harassment that are quite common (although hopefully not
> > common in the IETF).  If this image were the worst "harassment" that
> > our ombudsperson had to deal with, that would seem to me to be very
> > good news indeed.
>
> Actually, looking at the policy more closely, I believe it shouldn't
> be a problem and Bjoern Hoehrmann's assertions are specious.  To quote
> from the policy:
>
>    Harassment is unwelcome hostile or intimidating behavior, in
>    particular speech and behavior that is sexually aggressive or
>    intimidates based on attributes like race, gender, religion, age,
>    color, national origin, ancestry, disability, sexual orientation,
>    or gender identity.
>
>
How does this policy help if there is no identity known by the one who
abuses other identified people? Usually harrassment will come from people
that hide their identity, gender, religion, race, etc, because they don't
want policies to affect their behavior/future, or most important
their real-work or real-title or real-reputation in the IETF or in its WGs
(the system policy attacker likes to have more faces/addresses instead of
more hats/authorities). Therefore, IMHO, there is still a problem with this
anti-harrassment policy is not solving very much in facing the allowance of
anonymous postings without policies related to anonymous posting. I suggest
to make a policy for anonymous then this anti-harrassment will have better
value, or make them joined in one policy.

AB

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Oct 22, 2013 at 11:54 PM, Theodore Ts&#39;o <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit.edu</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"><div class=3D"im">On Tue, Oct 22, 2013 at 10:33:37PM +0000=
, Ted Lemon wrote:<br>

&gt;<br>
&gt; My reaction to this is that it seems to trivialize types of<br>
&gt; real-world harassment that are quite common (although hopefully not<br=
>
&gt; common in the IETF). =A0If this image were the worst &quot;harassment&=
quot; that<br>
&gt; our ombudsperson had to deal with, that would seem to me to be very<br=
>
&gt; good news indeed.<br>
<br>
</div>Actually, looking at the policy more closely, I believe it shouldn&#3=
9;t<br>
be a problem and Bjoern Hoehrmann&#39;s assertions are specious. =A0To quot=
e<br>
from the policy:<br>
<div class=3D"im"><br>
=A0 =A0Harassment is unwelcome hostile or intimidating behavior, in<br>
=A0 =A0particular speech and behavior that is sexually aggressive or<br>
=A0 =A0intimidates based on attributes like race, gender, religion, age,<br=
>
=A0 =A0color, national origin, ancestry, disability, sexual orientation,<br=
>
=A0 =A0or gender identity.<br>
<br></div></blockquote><div>=A0</div><div>How does this policy help if ther=
e is no identity known by the one who abuses other identified people? Usual=
ly harrassment will come from people that hide their identity, gender, reli=
gion, race,=A0etc, because they don&#39;t want policies to affect their beh=
avior/future, or most important their=A0real-work or real-title or real-rep=
utation=A0in the=A0IETF or in its=A0WGs (the system policy attacker likes t=
o have more faces/addresses instead of more hats/authorities). Therefore, I=
MHO,=A0there is still a problem with this anti-harrassment policy=A0is not =
solving very much in facing the allowance of anonymous postings without pol=
icies related to anonymous posting. I suggest to make a policy for anonymou=
s then this anti-harrassment will have better value, or make them joined in=
 one policy.</div>
<div>=A0</div><div>AB</div></div><br></div></div>

--e89a8ff1c840b600d804e964e7ca--

From tytso@thunk.org  Wed Oct 23 02:43:34 2013
Return-Path: <tytso@thunk.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 3CF1E11E8156 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 02:43:34 -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 omYklfh4I+u6 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 02:43:33 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 6273811E833C for <ietf@ietf.org>; Wed, 23 Oct 2013 02:42:25 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1VYuxM-0000MR-0p; Wed, 23 Oct 2013 09:42:24 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id C48BB580507; Wed, 23 Oct 2013 05:42:21 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1382521341; bh=8O/gehSgqzbdVOluwWANKtn05jp9q4QbPlLydcrXxBw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=J62zYSXRkJ9PxReteJpvY4g1I+LqeFSas5GanwCUoY0jOomq1phNWo3W0tWaizH8l 1l5xzA5xpRhvS6IUeBqEXTEzVHPFB9VJC5jTh+D9QcRPWqY4pydIxcA24okwOgTJPV ti5T+4hUzIxrVPVUi3wOpInsp6qvGMwflURuvQrY=
Date: Wed, 23 Oct 2013 05:42:21 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Proposed IETF Anti-Harassment Policy
Message-ID: <20131023094221.GA17772@thunk.org>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org> <284D2EAD-5557-4A3C-BCC1-DFA739816F15@nominum.com> <20131022225448.GA18249@thunk.org> <CADnDZ89cMtiRc7+A6984oCEbd2K4XXgQEn7pPUXHWKwNMCbemQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADnDZ89cMtiRc7+A6984oCEbd2K4XXgQEn7pPUXHWKwNMCbemQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
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, 23 Oct 2013 09:43:34 -0000

On Wed, Oct 23, 2013 at 10:11:40AM +0100, Abdussalam Baryun wrote:
> >    Harassment is unwelcome hostile or intimidating behavior, in
> >    particular speech and behavior that is sexually aggressive or
> >    intimidates based on attributes like race, gender, religion, age,
> >    color, national origin, ancestry, disability, sexual orientation,
> >    or gender identity.
>
> How does this policy help if there is no identity known by the one who
> abuses other identified people? Usually harrassment will come from people
> that hide their identity, gender, religion, race, etc, because they don't
> want policies to affect their behavior/future, or most important
> their real-work or real-title or real-reputation in the IETF or in its WGs
> (the system policy attacker likes to have more faces/addresses instead of
> more hats/authorities).

So, my understanding of the harassment policy is that a statement such
as "Certifying Authorities can't be trusted to be competent at
validating the entity requesting a certificate is really authorized to
speak for Certificate Subject" would not be harassment because
Certifying Authorities is not a protected class.

On the other hand, a statement such as, "I don't believe you because
you are heterosexual", or "We can't trust Joe because he is a
Pastafarian", etc., would be arrassment, because they are based on the
proctected classes listed above.

Note that in both of these examples, it does not matter what identity
class(es) the sender happens to fall into, whether he/she/it is Male,
a Pastafarian, Tibetian, wheelchair-bound, etc.

I agree with the suggestion that giving some examples of things which
would be clearly considered by an ombudsperson and those that would
not would be very useful.

					- Ted

From jmamodio@gmail.com  Wed Oct 23 03:04:39 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 18CC611E833F for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 03:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.122
X-Spam-Level: 
X-Spam-Status: No, score=-1.122 tagged_above=-999 required=5 tests=[AWL=0.081,  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 zKicWCXUr06l for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 03:04: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 58F5C11E82D5 for <ietf@ietf.org>; Wed, 23 Oct 2013 03:04:38 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id uy5so528036obc.35 for <ietf@ietf.org>; Wed, 23 Oct 2013 03:04:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; bh=Ou1V+whFGhTZXSi42pBCe3A3B4+hOdJAYpizbgq+7sk=; b=SRcC1QRw51Fcla2yqcmF7Dt6TyBqJNpmF6ReGIDU4dSxE68py3a0r4BdAMQuXlhfyJ 6N9jPej6ocq5C7u0hWpPttnkkZbGaOBkJytQHGIhmxeT9ktLUNsjflFoNfs+urBxgvbJ 0NBOifBJjP3PBwQL/i6wv8Cme6hkY5nSkoammcs6Nw0CQaU1Y7zrxIVVJllrMWQgxCiE cRw8lk3nV0nILb04fBoTSu0dbndNiM7mHsuGxHbwx8whPJA7rCVPd8L0EXOAc14BA7MM 5TsuqAZp1FfmKSn8X2O41+wy1/Di3xU7Lwkfh5yacVabbGE7H4chCXOLlfqJuAce5vuS oeKw==
X-Received: by 10.60.60.105 with SMTP id g9mr721666oer.8.1382522677905; Wed, 23 Oct 2013 03:04:37 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id s14sm15194234oeo.1.2013.10.23.03.04.36 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 03:04:36 -0700 (PDT)
Subject: Re: Sergeant at arms: please deal with [censored]
References: <DD0DDB9E-0542-44FB-B4C6-1BDF86654841@nominum.com> <CE8CC0B9.B9B46%jordi.palet@consulintel.es> <6.2.5.6.2.20131022210808.0db07578@resistor.net>
From: Jorge Amodio <jmamodio@gmail.com>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (11A501)
In-Reply-To: <6.2.5.6.2.20131022210808.0db07578@resistor.net>
Message-Id: <33DA1EEE-9559-4B0F-AF34-40009D137D9B@gmail.com>
Date: Wed, 23 Oct 2013 05:04:36 -0500
To: "ietf@ietf.org list" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (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, 23 Oct 2013 10:04:39 -0000

What part of this endless amplification of noise contributes to "make the In=
ternet work better" ?

-Jorge


From hallam@gmail.com  Wed Oct 23 04:39: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 1A88F11E8399 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 04:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level: 
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154,  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 SmG0wCC78rsL for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 04:39:35 -0700 (PDT)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4438311E8185 for <ietf@ietf.org>; Wed, 23 Oct 2013 04:39:34 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id q8so396686lbi.5 for <ietf@ietf.org>; Wed, 23 Oct 2013 04:39: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=uX6GlS0p5tTOEECFWLQtGChD1hV8tOVMOkr6KHve09w=; b=F1EweSWJoUwnHdBqxaf6Luie6CsmXXtOu8C2JxXCmzuIf4zoQHJwYfUAeZFvUOsZWX 9bZJyx8eMNTAEhtrPOgBDyxMoN3tgV4A+3+1W9eDiG6Yf0zec0lsEzPwVElonviCFlGq C1IKHqarTCxBnUTZoQXqHOrhQsnmAnBsaHMMDMpMVfKxYsm0jmzqSXsTqir0MYRCnsi6 dRI/+Cb8nUzuhtmaBfcRPowxluTOig0H7eVsl43N3D3bH2griOzHM3AZOXLn4ifJJXr4 l4aiICeORPbjm/CYxhw97K+NmgIite76T4DZpObmC9+dGrjauoSySJ/hFGpO3s6N+8UN PdCQ==
MIME-Version: 1.0
X-Received: by 10.112.138.37 with SMTP id qn5mr119087lbb.52.1382528372929; Wed, 23 Oct 2013 04:39:32 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Wed, 23 Oct 2013 04:39:32 -0700 (PDT)
In-Reply-To: <392CB277BC2EAE4FB83C1206954BA6CE0100FA@newserver.arneill-py.local>
References: <20131021125834.GA24167@nic.fr> <67E83EF109F9999F391CEC93@JcK-HP8200.jck.com> <20131021133746.GA29267@nic.fr> <673A097E66897B69B6C13B73@JcK-HP8200.jck.com> <20131022035640.GA7434@mx1.yitter.info> <CAMm+LwhvX3YyPritjkV_p7Le0pLVD5_HzuReA=vkpdBpc_4rNg@mail.gmail.com> <392CB277BC2EAE4FB83C1206954BA6CE0100FA@newserver.arneill-py.local>
Date: Wed, 23 Oct 2013 07:39:32 -0400
Message-ID: <CAMm+LwhyWTFwEVm+C3G5nPk3RXQkSdBouDQrgHDLUNTiy2uBsA@mail.gmail.com>
Subject: Re: Internet standardisation remains unilateral
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Michel Py <michel@arneill-py.sacramento.ca.us>
Content-Type: multipart/alternative; boundary=089e01160f568f7c0c04e966f83e
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, 23 Oct 2013 11:39:36 -0000

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

On Tue, Oct 22, 2013 at 11:35 PM, Michel Py <
michel@arneill-py.sacramento.ca.us> wrote:

> > Phillip Hallam-Baker wrote:
> > And what if that something is get the French government to
> > contribute to a rival to IETF? Or combine with the governments
> > of Brazil and Mexico to create a larger anti-IETF?
>
> Let them try it. It will fizzle when they lose the little traction they
> have now in the fallback of the Snowden leaks. In 2016 when Brazil (you
> picked it, not me) hosts the Olympic Games, they lose $100 million of per
> click advertizing because they have moved their stuff behind an alternate
> root or whatever pipe dream and nobody can access it? Have them eat their
> own dog food. History repeats itself; each time there is evidence of
> mismanagement from foreign powers, secessionist feelings flare and some
> smart @55 will exploit that to their own advantage.
>


I cannot imagine that dropping the new ICANN TLDs and requiring
French/Brazilian/Indian ISPs chain to a different root that includes the
ccTLDs plus the original seven TLDs would have the effect you suggest.

.com, .net and .org are essential for the running of the Internet. ICANN is
not. If it wasn't for the fact that a breakaway root would likely be under
UN control and give an opening to the countries who would like to impose
global censorship.



> > The key is IPv6.
>
> Then you have a problem, because France is the only country that has
> remotely tried to deploy it.
> Phillip, with all due respect for your very valuable past and present
> contributions, you're a dreamer. The reason you worry about the idea of the
> French government combining with Brazil and Mexico is as invalid as you
> think that IPv6 can be deployed. You believe in the dream, the market
> believes in money.
>

The reason I worry about such things is that I work with other people who
are paid to think about such things.

I saw what failing to appreciate the concerns of the French government did
in the case of RFID tags.



> Get IPv6 deployed in the real world and then I will pay attention to the
> French threat to take over the IETF and the Internet. Otherwise it will get
> in the same state of "non-deployment" that is not to be worried about.


I seem to remember that I first pointed out that NAT and middleboxes were
the technical tool for NAT deployment over ten years ago. From a technical
point of view, IPv6 must be completely plug compatible with IPv4, not as
people attempted at the time a gating factor on other technologies.

I could get IPv6 deployed if I had national level resources behind me.
Failing that, create a brand 'Internet 2.0 Ready' and set out a set of
requirements that middlebox etc. providers must meet to display the brand.
Ensure that products that are I2.0 branded are completely network agnostic
and give full service on both the old network and the new, including
mechanisms that make use of NAT-ed addresses on IPv4 fully acceptable.




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

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

<div dir=3D"ltr">On Tue, Oct 22, 2013 at 11:35 PM, Michel Py <span dir=3D"l=
tr">&lt;<a href=3D"mailto:michel@arneill-py.sacramento.ca.us" target=3D"_bl=
ank">michel@arneill-py.sacramento.ca.us</a>&gt;</span> wrote:<br><div class=
=3D"gmail_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"=
>&gt; Phillip Hallam-Baker wrote:<br>
&gt; And what if that something is get the French government to<br>
&gt; contribute to a rival to IETF? Or combine with the governments<br>
&gt; of Brazil and Mexico to create a larger anti-IETF?<br>
<br>
</div>Let them try it. It will fizzle when they lose the little traction th=
ey have now in the fallback of the Snowden leaks. In 2016 when Brazil (you =
picked it, not me) hosts the Olympic Games, they lose $100 million of per c=
lick advertizing because they have moved their stuff behind an alternate ro=
ot or whatever pipe dream and nobody can access it? Have them eat their own=
 dog food. History repeats itself; each time there is evidence of mismanage=
ment from foreign powers, secessionist feelings flare and some smart @55 wi=
ll exploit that to their own advantage.<br>
</blockquote><div><br></div><div><br></div><div>I cannot imagine that dropp=
ing the new ICANN TLDs and requiring French/Brazilian/Indian ISPs chain to =
a different root that includes the ccTLDs plus the original seven TLDs woul=
d have the effect you suggest.</div>
<div><br></div><div>.com, .net and .org are essential for the running of th=
e Internet. ICANN is not. If it wasn&#39;t for the fact that a breakaway ro=
ot would likely be under UN control and give an opening to the countries wh=
o would like to impose global censorship.</div>
<div><br></div><div>=A0<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt; The key is IPv6.<br>
<br>
Then you have a problem, because France is the only country that has remote=
ly tried to deploy it.<br>
Phillip, with all due respect for your very valuable past and present contr=
ibutions, you&#39;re a dreamer. The reason you worry about the idea of the =
French government combining with Brazil and Mexico is as invalid as you thi=
nk that IPv6 can be deployed. You believe in the dream, the market believes=
 in money.<br>
</blockquote><div><br></div><div>The reason I worry about such things is th=
at I work with other people who are paid to think about such things.</div><=
div><br></div><div>I saw what failing to appreciate the concerns of the Fre=
nch government did in the case of RFID tags.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Get IPv6 deployed in the real world and then I will pay attention to the Fr=
ench threat to take over the IETF and the Internet. Otherwise it will get i=
n the same state of &quot;non-deployment&quot; that is not to be worried ab=
out.</blockquote>
<div><br></div><div>I seem to remember that I first pointed out that NAT an=
d middleboxes were the technical tool for NAT deployment over ten years ago=
. From a technical point of view, IPv6 must be completely plug compatible w=
ith IPv4, not as people attempted at the time a gating factor on other tech=
nologies.</div>
<div><br></div><div>I could get IPv6 deployed if I had national level resou=
rces behind me. Failing that, create a brand &#39;Internet 2.0 Ready&#39; a=
nd set out a set of requirements that middlebox etc. providers must meet to=
 display the brand. Ensure that products that are I2.0 branded are complete=
ly network agnostic and give full service on both the old network and the n=
ew, including mechanisms that make use of NAT-ed addresses on IPv4 fully ac=
ceptable.=A0</div>
<div><br></div><div><br></div></div><br clear=3D"all"><div><br></div>-- <br=
>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><b=
r>
</div></div>

--089e01160f568f7c0c04e966f83e--

From scott.brim@gmail.com  Wed Oct 23 06:36: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 A579411E8410 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 06:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 8N+zGzjRVTCg for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 06:36:53 -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 75E5111E8371 for <ietf@ietf.org>; Wed, 23 Oct 2013 06:36:29 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id va2so932103obc.12 for <ietf@ietf.org>; Wed, 23 Oct 2013 06:36:10 -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=69PivVHUzgZ/ZtoBGjskQR064sAHZB5tre8K6UVsRO4=; b=lkX9wmVzT8swW1lrrI3feA4Zr8LkA98ST3GkPVYkFWBXGEvd+n6u5zeS12C/814m+L uH3/3/mTGBfMDUzYDID9h5T2eC3vxGHZAyosTdCLqANE9ef/O6jE1VFkzbtUojI9nn6t p0T/ulKihRK63vDQP8nF/UJ/7u38c2ScVrVyGIANAtFmVXnj2PcZ7YQKE+7HJptq9lIN NLvadGF8RzqqFlBj38eCAAzIZZJY0mEN9IVZK4tXXne5afq6sGaBqVfNXyr+5DWxTmDM 6iUxU8AVrVu6dgd7cwQqDe8j2E/5VZtk6Ap4it8QVWLF5ir0izL/6fT60EnX8BzWRm34 BlAw==
X-Received: by 10.182.117.164 with SMTP id kf4mr677491obb.104.1382535370708; Wed, 23 Oct 2013 06:36:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Wed, 23 Oct 2013 06:35:50 -0700 (PDT)
In-Reply-To: <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 23 Oct 2013 09:35:50 -0400
Message-ID: <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e015382b8a91e5c04e968992e
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, 23 Oct 2013 13:36:53 -0000

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

On Tue, Oct 22, 2013 at 5:21 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> If the first message had been the beginning of a conversation, I would
> have taken it a lot differently, but the way it was dropped on the list
> with no discussion, it just looked like an attempt to start a massive flame
> war.   That's exactly the sort of thing that the sergeant-at-arms is
> supposed to deal with.
>

I didn't mind the mail, but I didn't mind the request for suspension either
because he/she had been sprinkling silliness across multiple lists, and
content was becoming more disruptive.

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

<div dir=3D"ltr">On Tue, Oct 22, 2013 at 5:21 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">If the first message had been the beginning =
of a conversation, I would have taken it a lot differently, but the way it =
was dropped on the list with no discussion, it just looked like an attempt =
to start a massive flame war. =A0 That&#39;s exactly the sort of thing that=
 the sergeant-at-arms is supposed to deal with.<br>

</blockquote><div><br></div><div>I didn&#39;t mind the mail, but I didn&#39=
;t mind the request for suspension either because he/she had been sprinklin=
g silliness across multiple lists, and content was becoming more disruptive=
.=A0</div>

</div><br></div></div>

--089e015382b8a91e5c04e968992e--

From fred@cisco.com  Wed Oct 23 07:31:25 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 2984E11E83FE for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.232
X-Spam-Level: 
X-Spam-Status: No, score=-110.232 tagged_above=-999 required=5 tests=[AWL=-0.233, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 hq44GwPMKnAE for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:31:19 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 924D711E813A for <ietf@ietf.org>; Wed, 23 Oct 2013 07:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3087; q=dns/txt; s=iport; t=1382538679; x=1383748279; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=21CuJ1AN4sb1dxRxhqm8VvsY8DPV9eOq4mtJpmiMB6w=; b=RihaJqwQakZU7y+il1Dkb8b4PAautCPP+ua/pf1qN6LATFLwzLR4QCp0 82lKUq1pu35NtRr3uKU5Ph4ADPNhQIdgp6QGIxEJbxm/KBnr5+cRyxj+0 Ez54wiKqCeDyC2L4g4cVKPl9xYkAJcKI3FW8raAi1ePUgn9RDAJkafOgS 0=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAMrcZ1KtJV2Z/2dsb2JhbABTBoMHgQy7UoJ6gSoWdIIlAQEBBG4LEAIBCBgKJDIlAgQBDQ0Gh3i7OY4FHHwxB4MfgQsDkC2BMJgzgySBcTk
X-IronPort-AV: E=Sophos;i="4.93,554,1378857600";  d="asc'?scan'208";a="275732154"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 23 Oct 2013 14:31:19 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9NEVJc2013274 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Oct 2013 14:31:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.23]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 23 Oct 2013 09:31:18 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: SM <sm@resistor.net>, John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Thread-Topic: Internet standardisation remains unilateral
Thread-Index: AQHOzl2AwBbF1KdX+ka6ZSboFdEmKJn/jFMAgAAXmgCAAOLDgIACKW0A
Date: Wed, 23 Oct 2013 14:31:17 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553BA7797D@xmb-rcd-x09.cisco.com>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@[10.0.1.3]> <6.2.5.6.2.20131021202945.0e873928@resistor.net>
In-Reply-To: <6.2.5.6.2.20131021202945.0e873928@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.169.128]
Content-Type: multipart/signed; boundary="Apple-Mail=_A06BD406-6C9C-4D3B-9772-67F063030C31"; protocol="application/pgp-signature"; micalg=pgp-sha1
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, 23 Oct 2013 14:31:25 -0000

--Apple-Mail=_A06BD406-6C9C-4D3B-9772-67F063030C31
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Warning: politically incorrect statements exist in this email.

At 08:58 21-10-2013, John Day wrote:
> =46rom my experience over the years, I would generalize this that the =
developed world has dominated the standards process in this field, =
whether it was the IETF, ISO, ITU, or IEEE and most others.  Most of =
that has to do with the expense involved in participating.

The expense is a factor, but I would dispute the conclusion. To begin =
with, I would note Mark Smith, who has a draft open in v6ops but to my =
knowledge has never attended or only infrequently attended IETF =
meetings, and Vernon Schryver, who has done quite of a bit of work in =
DNS and other infrastructure but is rather proud of the fact that he =
participates only virtually. It's unusual to be entirely virtual and get =
something done - it's a lot easier for people that rub shoulders =
physically at IETF meetings and take subjects to the list - but it is =
possible and is done. People in developing countries can contribute on =
mailing lists as easily as anyone else can, and at the same level of =
travel expense and attendance fees.

I think the primary reason that the developed world dominates standards =
processes is that the developed world has a commercial interest in them. =
A network operator needs to understand how the protocols s/he depends on =
work, and needs to be able to design and debug his/her use of them. They =
don't need to know fine details like Alternate Tuesday Rules except out =
of interest. The folks who write that code absolutely have to know, and =
have to be able to ensure the correctness and completeness of the =
specifications. Hence, people worldwide consume specifications, but the =
people and companies whose livelihood depends on involvement in the =
standards creation are the ones primarily involved in creating them.=20

That's not a slam on developing countries or their capabilities - they =
have smart and capable people just like the developed world does. But =
they are, by definition, underdeveloped - they do not operate in the =
same way that developed countries do, nor do they develop the =
technologies that the world uses. As they develop economically, they =
become capable of doing that, as for example India is becoming. But then =
they are developed countries or at least further in that direction, not =
"developing".

--Apple-Mail=_A06BD406-6C9C-4D3B-9772-67F063030C31
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSZ92sbjEdbHIsm0MRAqnxAKCMgKfOFYS43jGBAkQIEB7DgUPhYgCginS4
09MjtT/IhnKGB1u5IT8jkhI=
=9NOV
-----END PGP SIGNATURE-----

--Apple-Mail=_A06BD406-6C9C-4D3B-9772-67F063030C31--

From richard@shockey.us  Wed Oct 23 07:37:31 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 50E6D11E83D6 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.189
X-Spam-Level: 
X-Spam-Status: No, score=-102.189 tagged_above=-999 required=5 tests=[AWL=0.410, 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 pTtk-kC0yzMp for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:37:25 -0700 (PDT)
Received: from outbound-ss-1669.hostmonster.com (outbound-ss-1669.hostmonster.com [74.220.206.201]) by ietfa.amsl.com (Postfix) with SMTP id 98BF911E81BD for <ietf@ietf.org>; Wed, 23 Oct 2013 07:37:25 -0700 (PDT)
Received: (qmail 19801 invoked by uid 0); 23 Oct 2013 14:37:03 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy6.mail.unifiedlayer.com with SMTP; 23 Oct 2013 14:37:02 -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=MHZYYINjvJ7FnRjr1q8VQWSIZeQ0KBnu7cdMTFhDmIc=;  b=LexFDZ/jcoiEpp+80/VZjldbXMeNbA/6uxewp7Z1EC27wX61eDDDD98Bof73M4ke6UPmbFG429333zUq7scYATBaAm8LY7CPLkNgnxu365ZLI4cmr4k1Eo3HrYm7KrYl;
Received: from [71.114.100.16] (port=50002 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.80) (envelope-from <richard@shockey.us>) id 1VYzYT-0006vQ-GA; Wed, 23 Oct 2013 08:37:01 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Melinda Shore'" <melinda.shore@gmail.com>, <ietf@ietf.org>
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com>
In-Reply-To: <5266C6CA.30900@gmail.com>
Subject: RE: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Date: Wed, 23 Oct 2013 10:36:58 -0400
Message-ID: <00c601cecffd$5517ed30$ff47c790$@shockey.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Content-Language: en-us
Thread-Index: AQB/ZWi3GKeGmYHBIHgx+qsNLGaZOAL2Q8avASRVPrUCfL2VrQHXVkVtAiLeKkucTKE6oA==
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.114.100.16 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: Wed, 23 Oct 2013 14:37:31 -0000

IN line below..

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Melinda Shore
Sent: Tuesday, October 22, 2013 2:41 PM
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com

The more I've been thinking about this the less comfortable I am with how
this was executed.  I have no disagreement whatsoever with removing this
person's posting privileges.
But, I have a huge problem with Jordi's statement:

  "As Sergeant-at-arms, I agree with other previous
  postings and believe that anonymous posting is not
  tolerable in the IETF mail exploders."

Clearly, there are non-trivial problems around making decisions on the basis
of something sort of like identity in unauthenticated email.  We don't
*really* know who other people are - we tend to assume that they are who
they say they are and evaluate their credibility (or not) on things like
content, reputation, past performance, etc.  The problem with
mars.techno.cat@gmail.com isn't that he (and since we're pretty sure we know
who this is, we'll stick with masculine pronouns) has an email address that
doesn't look like a name (although his name could have been Mars Techno Cat,
as unlikely as that is).  The problem is that he had no prior history of
posting -as that name- and posted nothing but off-topic rants and personal
attacks.
I would hope that the attacks would be sufficient to have his posting
privileges revoked and that having an unfamiliar email address would not be
sufficient.

Additionally, let me suggest that finding anonymous posts "not tolerable" is
inconsistent with the perpass discussions and concerns expressed *here*
about privacy.
We want accountability in our documents and that means knowing that the
people who contribute to our work 1) have technical substance, and 2) are
having their comments and text evaluated by other people of technical
substance.  It does not necessarily mean knowing their names or identities.
In many discussions about privacy and about whether or not various
cryptographic technologies have been deliberately weakened by some US
government agency, there have been repeated assertion that open processes
and aggressive review provide protection against that sort of problem.  That
ought to apply here, as well.

Anonymity is not a problem.  Behaving badly is a problem.

[RS> ]  That is the central issue.  Anonymity cannot be used as a shield to
protect abusive or criminal behavior.  That is an issue some of us are
struggling with in the RAI area with STIR and the global voice
communications network.  The right to privacy is also in part a "right to be
left alone".  


I really never want to see someone's ejection justified on the basis of
their putative "anonymity" again.  I am not arguing that
mars.techno.cat@gmail.com ought to be allowed anywhere near an IETF mailing
list but that the reason that was given for throwing him off was not
correct.  We should be working to protect anonymity and privacy, not
punishing it.

[RS> ] With exceptions.  Nothing is absolute here.  There are exceptions
where various actors, state or otherwise, have to be able to break the cloak
of anonymity in order to protect the safety and health of others.  Sometimes
..sometimes the needs of the many outweigh the desires of the few. 


Melinda


From jeanjour@comcast.net  Wed Oct 23 07:59:57 2013
Return-Path: <jeanjour@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 A213611E83AC for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.151
X-Spam-Level: 
X-Spam-Status: No, score=0.151 tagged_above=-999 required=5 tests=[AWL=-0.012,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  J_CHICKENPOX_13=0.6, 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 gmUW8p-4Co6R for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 07:59:51 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7A011E81AF for <ietf@ietf.org>; Wed, 23 Oct 2013 07:59:51 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta04.westchester.pa.mail.comcast.net with comcast id gcKi1m0031ei1Bg54ezrKx; Wed, 23 Oct 2013 14:59:51 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta24.westchester.pa.mail.comcast.net with comcast id gezq1m00J14WE023kezqRb; Wed, 23 Oct 2013 14:59:51 +0000
Mime-Version: 1.0
Message-Id: <a062408c7ce8d9172cf64@[10.0.1.3]>
In-Reply-To: <8C48B86A895913448548E6D15DA7553BA7797D@xmb-rcd-x09.cisco.com>
References: <20131021125834.GA24167@nic.fr> <CAMzo+1a1UxprDr+tW-X8st4oWF1hajUm=nce1G9Ci8XAjXPqRg@mail.gmail.com> <a0624085fce8afbbba1ac@[10.0.1.3]> <6.2.5.6.2.20131021202945.0e873928@resistor.net> <8C48B86A895913448548E6D15DA7553BA7797D@xmb-rcd-x09.cisco.com>
Date: Wed, 23 Oct 2013 10:55:06 -0400
To: "Fred Baker (fred)" <fred@cisco.com>, SM <sm@resistor.net>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: Internet standardisation remains unilateral
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382540391; bh=ojw2LPkw57GlKOIoqy4e6x9JLljLO/OhZsHf5OGn2NQ=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=ru1ECy/mUH5nRAj7wmivbmtkx0CjXPjHjlv0ikJWgPq7sIvKjsVcY1w98pHEC8HuT f/t7KFeDuJPNjpPHXlFDEILxjPjMZf+XFNCc639r+lcTPoJq8LsYze/00h3C1ZNWwZ jzsKCU7TBYWMx06r2QsHVbFIAZEZkTE6jn5XGkiNBE9yaASKHBuXJo5+fcPloHSsu9 BWFDziiLPBQiF+QkHGyTQbw0h9Am3mT+S+fwQLpW9K/jnXYcSZVBFe3vtKJFtlfpV+ Y2ALfbHMGnLyCkeT6Mzow42iOcL6E9BV9qiKtpzLgWZ+IK7xVWAv41VxWZCkwBb+Ae VuKK/522sh77A==
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, 23 Oct 2013 14:59:57 -0000

Couldn't agree more.  I was guessing that there were some who only 
participated on-line but since I didn't know for sure, I didn't go 
that far.  As I said, the problem of attendance has been greatly 
reduced if not eliminated.

Agreed that business interest is the primary driving factor and since 
most vendors are in the developed world, that is where the 
participation comes from.

Every standards committee I have ever had contact with found it 
difficult to get "user" participation,  Generally, those 
organizations argue that the standards work was beyond what they saw 
as their planning horizon.  Of course, this doesn't stop them from 
complaining that they had to buy what the vendors produce as opposed 
to what they might liked to have seen!  ;-)  But we all know how 
management tends to think.  ;-)

Take care,
John

At 2:31 PM +0000 10/23/13, Fred Baker (fred) wrote:
>Warning: politically incorrect statements exist in this email.
>
>At 08:58 21-10-2013, John Day wrote:
>>  From my experience over the years, I would generalize this that 
>>the developed world has dominated the standards process in this 
>>field, whether it was the IETF, ISO, ITU, or IEEE and most others. 
>>Most of that has to do with the expense involved in participating.
>
>The expense is a factor, but I would dispute the conclusion. To 
>begin with, I would note Mark Smith, who has a draft open in v6ops 
>but to my knowledge has never attended or only infrequently attended 
>IETF meetings, and Vernon Schryver, who has done quite of a bit of 
>work in DNS and other infrastructure but is rather proud of the fact 
>that he participates only virtually. It's unusual to be entirely 
>virtual and get something done - it's a lot easier for people that 
>rub shoulders physically at IETF meetings and take subjects to the 
>list - but it is possible and is done. People in developing 
>countries can contribute on mailing lists as easily as anyone else 
>can, and at the same level of travel expense and attendance fees.
>
>I think the primary reason that the developed world dominates 
>standards processes is that the developed world has a commercial 
>interest in them. A network operator needs to understand how the 
>protocols s/he depends on work, and needs to be able to design and 
>debug his/her use of them. They don't need to know fine details like 
>Alternate Tuesday Rules except out of interest. The folks who write 
>that code absolutely have to know, and have to be able to ensure the 
>correctness and completeness of the specifications. Hence, people 
>worldwide consume specifications, but the people and companies whose 
>livelihood depends on involvement in the standards creation are the 
>ones primarily involved in creating them.
>
>That's not a slam on developing countries or their capabilities - 
>they have smart and capable people just like the developed world 
>does. But they are, by definition, underdeveloped - they do not 
>operate in the same way that developed countries do, nor do they 
>develop the technologies that the world uses. As they develop 
>economically, they become capable of doing that, as for example 
>India is becoming. But then they are developed countries or at least 
>further in that direction, not "developing".
>
>Content-Transfer-Encoding: 7bit
>Content-Disposition: attachment; filename="signature.asc"
>Content-Type: application/pgp-signature; name="signature.asc"
>Content-Description: Message signed with OpenPGP using GPGMail
>
>Attachment converted: Macintosh HD:signature.asc (    /    ) (00D4056F)


From harald@alvestrand.no  Wed Oct 23 08:02:29 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D1411E8434 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.513
X-Spam-Level: 
X-Spam-Status: No, score=-110.513 tagged_above=-999 required=5 tests=[AWL=0.085, 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 7c1G0u8YJa4e for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:02:23 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 50F9C11E838F for <ietf@ietf.org>; Wed, 23 Oct 2013 08:02:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4942D39E128 for <ietf@ietf.org>; Wed, 23 Oct 2013 17:02:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UTgLmdsHzybi for <ietf@ietf.org>; Wed, 23 Oct 2013 17:02:14 +0200 (CEST)
Received: from [192.168.1.17] (unknown [188.113.88.47]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 3C16A39E116 for <ietf@ietf.org>; Wed, 23 Oct 2013 17:02:14 +0200 (CEST)
Message-ID: <5267E4FC.2010207@alvestrand.no>
Date: Wed, 23 Oct 2013 17:02:20 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Fwd: Re: Proposed IETF Anti-Harassment Policy
References: <5264ED5B.3090505@alvestrand.no>
In-Reply-To: <5264ED5B.3090505@alvestrand.no>
X-Forwarded-Message-Id: <5264ED5B.3090505@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------000009030907010908010601"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Oct 2013 15:02:30 -0000

This is a multi-part message in MIME format.
--------------000009030907010908010601
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I sent this message to the wrong address.
I must be an email newbie...

-------- Original Message --------
Subject: 	Re: Proposed IETF Anti-Harassment Policy
Date: 	Mon, 21 Oct 2013 11:01:15 +0200
From: 	Harald Alvestrand <harald@alvestrand.no>
To: 	ietf-announce@ietf.org



The decision process to conclude that harassment has taken place looks
fine to me. The existence of the process may be enough to deter some
potential harassers (or at least make reasonable people think about
whether they are getting close to the border).

The document is completely silent on what actions can be taken; we may
hope we never get there, or we may think that the actions the IESG is
already empowered to take under other policies are sufficient.

I hope that's OK.

Go for it!

On 10/20/2013 07:44 PM, IETF Chair wrote:
> The IETF should be an open and accessible body in which any individual feels
> able to participate without fear of oppression or harassment.  The IESG has
> become aware of some incidents of concern, is aware of various incidents in our
> industry in general, and has also observed that many similar organisations and
> conferences have a policy on this matter.
>
> In order to ensure the right atmosphere and to provide a suitable environment,
> the IESG has decided that it is desirable to write a simple and straightforward
> policy on harassment. This is not only to remind participants not to harass
> others (something that we hope is obvious to us all), but also to let anyone who
> it the target of harassment know that we take these matters seriously and that
> there is something they can do to address these sorts of incidents should they
> occur.
>
> A small design team has looked at existing policies used by other groups similar
> to the IETF and consulted with some of the ISOC professionals with expertise in
> human resources and issues of workplace harassment. The design team has put
> together what the IESG feels is a good anti-harassment policy for the IETF: It
> is short and to the point, it is modeled on and makes heavy re-use of the
> language of existing policies, and it sets forth reasonable procedures for the
> IETF.
>
> The IESG intends to put in place Ombudspersons as confidential initial contact
> points for situations where there is a concern of harassment. The selection of
> Ombudspersons will happen later, and the person(s) will have appropriate
> training and expertise.
>
> The IESG plans to adopt this as an IESG Statement. We solicit your feedback. We
> understand that this is a difficult and sensitive topic to discuss, but we do
> want your comments. If you feel more comfortable sending comments directly to
> the IESG <iesg@ietf.org> rather than discussing them on the IETF list, please
> feel free to do so.
>
> Jari Arkko for the IESG
>
> --- Draft Statement ---
>
> IETF Anti-Harassment Policy
>
> IETF meetings, virtual meetings, and mailing lists are intended for professional
> collaboration and networking. The IETF strives to create and maintain an
> environment in which people are treated with dignity, decency, and respect.
> Those who participate in the IETF are expected to behave according to
> professional standards and demonstrate appropriate workplace behavior. While
> participating in the IETF, communication between participants should be
> appropriate for a professional audience including people of many different
> backgrounds.
>
> While our processes let chairs deal with disruptive public behaviors on mailing
> lists and in IETF face-to-face meetings, harassment is a serious problem that
> warrants special attention. IETF participants should not engage in harassment
> while at IETF meetings, virtual meetings, social events, or on mailing lists.
> Harassment is unwelcome hostile or intimidating behavior, in particular speech
> and behavior that is sexually aggressive or intimidates based on attributes like
> race, gender, religion, age, color, national origin, ancestry, disability,
> sexual orientation, or gender identity. Harassment of this sort will not be
> tolerated in the IETF. Harassment includes the use of offensive language or
> sexual imagery in public presentations and displays, degrading verbal comments,
> deliberate intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, and unwelcome sexual attention.
>
> Participants asked to stop any harassing behavior are expected to comply
> immediately. If you believe you have been harassed, notice that
> someone else is being harassed, or have any other concerns, you are encouraged
> to raise your concern in confidence with one of the Ombudspersons.
>
> If these standards are violated, appropriate action will be taken.


-- 
Surveillance is pervasive. Go Dark.




--------------000009030907010908010601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I sent this message to the wrong address.<br>
    I must be an email newbie...<br>
    <div class="moz-forward-container"><br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>Re: Proposed IETF Anti-Harassment Policy</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Mon, 21 Oct 2013 11:01:15 +0200</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td>Harald Alvestrand <a class="moz-txt-link-rfc2396E" href="mailto:harald@alvestrand.no">&lt;harald@alvestrand.no&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>The decision process to conclude that harassment has taken place looks
fine to me. The existence of the process may be enough to deter some
potential harassers (or at least make reasonable people think about
whether they are getting close to the border).

The document is completely silent on what actions can be taken; we may
hope we never get there, or we may think that the actions the IESG is
already empowered to take under other policies are sufficient.

I hope that's OK.

Go for it!

On 10/20/2013 07:44 PM, IETF Chair wrote:
&gt; The IETF should be an open and accessible body in which any individual feels
&gt; able to participate without fear of oppression or harassment.  The IESG has
&gt; become aware of some incidents of concern, is aware of various incidents in our
&gt; industry in general, and has also observed that many similar organisations and
&gt; conferences have a policy on this matter.
&gt;
&gt; In order to ensure the right atmosphere and to provide a suitable environment,
&gt; the IESG has decided that it is desirable to write a simple and straightforward
&gt; policy on harassment. This is not only to remind participants not to harass
&gt; others (something that we hope is obvious to us all), but also to let anyone who
&gt; it the target of harassment know that we take these matters seriously and that
&gt; there is something they can do to address these sorts of incidents should they
&gt; occur.
&gt;
&gt; A small design team has looked at existing policies used by other groups similar
&gt; to the IETF and consulted with some of the ISOC professionals with expertise in
&gt; human resources and issues of workplace harassment. The design team has put
&gt; together what the IESG feels is a good anti-harassment policy for the IETF: It
&gt; is short and to the point, it is modeled on and makes heavy re-use of the
&gt; language of existing policies, and it sets forth reasonable procedures for the
&gt; IETF.
&gt;
&gt; The IESG intends to put in place Ombudspersons as confidential initial contact
&gt; points for situations where there is a concern of harassment. The selection of
&gt; Ombudspersons will happen later, and the person(s) will have appropriate
&gt; training and expertise.
&gt;
&gt; The IESG plans to adopt this as an IESG Statement. We solicit your feedback. We
&gt; understand that this is a difficult and sensitive topic to discuss, but we do
&gt; want your comments. If you feel more comfortable sending comments directly to
&gt; the IESG <a class="moz-txt-link-rfc2396E" href="mailto:iesg@ietf.org">&lt;iesg@ietf.org&gt;</a> rather than discussing them on the IETF list, please
&gt; feel free to do so.
&gt;
&gt; Jari Arkko for the IESG
&gt;
&gt; --- Draft Statement ---
&gt;
&gt; IETF Anti-Harassment Policy
&gt;
&gt; IETF meetings, virtual meetings, and mailing lists are intended for professional
&gt; collaboration and networking. The IETF strives to create and maintain an
&gt; environment in which people are treated with dignity, decency, and respect.
&gt; Those who participate in the IETF are expected to behave according to
&gt; professional standards and demonstrate appropriate workplace behavior. While
&gt; participating in the IETF, communication between participants should be
&gt; appropriate for a professional audience including people of many different
&gt; backgrounds.
&gt;
&gt; While our processes let chairs deal with disruptive public behaviors on mailing
&gt; lists and in IETF face-to-face meetings, harassment is a serious problem that
&gt; warrants special attention. IETF participants should not engage in harassment
&gt; while at IETF meetings, virtual meetings, social events, or on mailing lists.
&gt; Harassment is unwelcome hostile or intimidating behavior, in particular speech
&gt; and behavior that is sexually aggressive or intimidates based on attributes like
&gt; race, gender, religion, age, color, national origin, ancestry, disability,
&gt; sexual orientation, or gender identity. Harassment of this sort will not be
&gt; tolerated in the IETF. Harassment includes the use of offensive language or
&gt; sexual imagery in public presentations and displays, degrading verbal comments,
&gt; deliberate intimidation, stalking, harassing photography or recording,
&gt; inappropriate physical contact, and unwelcome sexual attention.
&gt;
&gt; Participants asked to stop any harassing behavior are expected to comply
&gt; immediately. If you believe you have been harassed, notice that
&gt; someone else is being harassed, or have any other concerns, you are encouraged
&gt; to raise your concern in confidence with one of the Ombudspersons.
&gt;
&gt; If these standards are violated, appropriate action will be taken.


-- 
Surveillance is pervasive. Go Dark.

</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------000009030907010908010601--

From Ted.Lemon@nominum.com  Wed Oct 23 08:17:41 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 7AD5811E8438 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.59
X-Spam-Level: 
X-Spam-Status: No, score=-106.59 tagged_above=-999 required=5 tests=[AWL=0.009, 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 ildri0qpluZy for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:17:34 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id AF2AC11E8437 for <ietf@ietf.org>; Wed, 23 Oct 2013 08:17:34 -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 DSNKUmfojvk5PhhtPELSVBTmLKA1qxewnuaK@postini.com; Wed, 23 Oct 2013 08:17:34 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 5DB6A1B82E1 for <ietf@ietf.org>; Wed, 23 Oct 2013 08:17:34 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 41DAE190052; Wed, 23 Oct 2013 08:17:34 -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.03.0158.001; Wed, 23 Oct 2013 08:17:34 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzRN5MiZjjrFfeEyJF39B90YYOZn/6ykAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAAJKYCAABMiAIAAB2UAgAEQJACAABxsgA==
Date: Wed, 23 Oct 2013 15:17:34 +0000
Message-ID: <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com>
In-Reply-To: <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@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: <C24FC16919715548A22D1CF681A0AC1E@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: Wed, 23 Oct 2013 15:17:41 -0000

On Oct 23, 2013, at 9:35 AM, Scott Brim <scott.brim@gmail.com> wrote:
> On Tue, Oct 22, 2013 at 5:21 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>> If the first message had been the beginning of a conversation, I would h=
ave taken it a lot differently, but the way it was dropped on the list with=
 no discussion, it just looked like an attempt to start a massive flame war=
.   That's exactly the sort of thing that the sergeant-at-arms is supposed =
to deal with.
> I didn't mind the mail, but I didn't mind the request for suspension eith=
er because he/she had been sprinkling silliness across multiple lists, and =
content was becoming more disruptive.=20

Seeing all the pushback from my earlier comment, I realize that there's a d=
istinction here that we aren't making explicit, but that I think is importa=
nt.   It's inappropriate to spam IETF mailing lists.   Spamming IETF mailin=
g lists isn't covered under the warn first, sanction later model, because w=
hat you want with spam is for it to stop now, not later.

To me, what's being described here is similar to situations we've seen in t=
he past where someone subscribes to all the IETF mailing lists and starts p=
osting conference invites on them.   People have tended to be pretty patien=
t about this, because it's not so utterly far off topic that it looks just =
like pill spam.   But it really is spam=97it's unsolicited, unwelcome, not =
contributing to a meaningful dialog.

Randy says we should just delete it ourselves rather than blocking it.   Gi=
ven that people can't post without subscribing or being moderated, that's n=
ot completely unreasonable=97the usual vector for spam is an unmoderated ma=
iling list, and we don't have that particular problem.   But we have in the=
 past blocked people who post conference spam, and I thought that made sens=
e at the time.   I still think it makes sense.   But I agree that in theory=
 it doesn't match the warn-first policy.

There are three ways we can deal with this, I think:

  - Keep the existing policy unchanged: in this case we should have sent a =
warning.
  - Add an AUP on subscription, and count that as a warning in the case of =
spam.
  - Change the policy to specifically say that spammers will be blocked wit=
hout warning.

My personal feeling is that the email that triggered this debate was a deli=
berate troll, and that trolls have the potential to be really disruptive.  =
 And so I think we _should_ block first and ask questions later, as a delib=
erate policy.   We have appeals, and we have debates like this one, so I th=
ink that the harm of blocking too actively is minimal.   But the various pe=
ople who have argued that this is a new policy are right, and I think it's =
worth being clear on that.=

From randy@psg.com  Wed Oct 23 08:43:54 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 5B70021F9F5B for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  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 PTCBIU2vn2pc for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:43:51 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 8C44E11E80E7 for <ietf@ietf.org>; Wed, 23 Oct 2013 08:43:04 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VZ0aM-0004CP-V7; Wed, 23 Oct 2013 15:43:03 +0000
Date: Wed, 23 Oct 2013 17:43:02 +0200
Message-ID: <m28uxkyovt.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.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, 23 Oct 2013 15:43:54 -0000

the chilling effect of vigilateism is far worse than spam or trolls.
we've been dealing with the latter for decades, and there is little
actual real harm if any.  the chilling effect of vigilanteism causes
actual harm and reduces the rich diversity of opinion, culture, and
viewpoint.

randy

From dhc@dcrocker.net  Wed Oct 23 08:47:09 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 6390111E842A for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:47:09 -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.000,  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 3tz5YgpaJvas for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 08:46:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E1B8821F9F5B for <ietf@ietf.org>; Wed, 23 Oct 2013 08:46:53 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9NFknfS022311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 23 Oct 2013 08:46:53 -0700
Message-ID: <5267EF61.2010001@dcrocker.net>
Date: Wed, 23 Oct 2013 11:46:41 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com>	<0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com>	<5266CE7C.2020503@gmail.com>	<61EE8145-2184-44C1-8163-424F97F8286C@piuha.net>	<m261sp3u13.wl%randy@psg.com>	<7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com>	<CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com>	<CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com>
In-Reply-To: <m28uxkyovt.wl%randy@psg.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, 23 Oct 2013 08:46:53 -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, 23 Oct 2013 15:47:09 -0000

On 10/23/2013 11:43 AM, Randy Bush wrote:
> the chilling effect of vigilateism is far worse than spam or trolls.
> we've been dealing with the latter for decades, and there is little
> actual real harm if any.


That's quite simply and observably wrong.

When a list is subject to high noise levels, legitimate participants 
leave.  It's true for this general IETF discussion list and it's true 
for working group lists.  And it happens regularly.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From derhoermi@gmx.net  Wed Oct 23 10:52:18 2013
Return-Path: <derhoermi@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 6B0F011E813A for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 10:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[AWL=-0.119, 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 Eklc1yyK3CB8 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 10:52:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1E511E8145 for <ietf@ietf.org>; Wed, 23 Oct 2013 10:52:14 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.39.61]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0M5r89-1VtKVh3hY9-00xoO7 for <ietf@ietf.org>; Wed, 23 Oct 2013 19:52:13 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Proposed IETF Anti-Harassment Policy
Date: Wed, 23 Oct 2013 19:52:14 +0200
Message-ID: <f3uf69151jobqjdsk4nqlqc9m3e9nqep7u@hive.bjoern.hoehrmann.de>
References: <B728B514-BC07-4D6E-899E-385C03C37430@ietf.org> <8C48B86A895913448548E6D15DA7553BA6FB41@xmb-rcd-x09.cisco.com> <20131022093052.GF9517@thunk.org> <151B3C7B-907C-494F-B5FA-2D70C93EF2B4@nominum.com> <20131022214307.GA2603@thunk.org>
In-Reply-To: <20131022214307.GA2603@thunk.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:2wQG8B11eX3dQl4ugi4NFFEeyq+tISjXt0+noBLu2mqqYuCujLC Pg5UpA0YkG+KS0vTkJheiKaHfXoDhcLsB0E0ZR+YduO7BM4GDk03ctLUeXfPG0P8cPlFZ4t 0CeRYQfMTmfZBuYbPPU0blfJUiGydjQUI6fj94GiSHBO05yyQycCAfkHRelXoywSgSF1qB6 Dan4qcKkz7RUBlD/sUt+Q==
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, 23 Oct 2013 17:52:18 -0000

* Theodore Ts'o wrote:
>What about a slide presentation in a wg discussion in perpass which
>included the following image?
>
>     http://blog.chron.com/nickanderson/tag/nsa/
>
>Bjoern Hoehrmann has already asserted he believes it would be
>considered harassment.

I think that people can legitimately feel personally threatened and
disturbed, to the point where they require protection, by imagery.

An example would be decorating the perpass meeting room with graphic
posters of extrajudicially killed surveillance victims which might
induce fear in some participants and effectively censor them. It is
fair to regulate that to ensure proper debates are possible, though
I do not think it is necessary or useful to specifically call out
imagery in this sense, and the image above obviously doesn't qualify.

The problem is that the proposed policy does not call out violence,
disease, death, poisonous animals or other things that are harmful
to people, it only mentions "sexual imagery". For the United States
http://www.supremecourt.gov/opinions/10pdf/08-1448.pdf#page=76 that
may be normal and I can live with including it in such a policy, but
certainly not in a way that suggests sexual imagery deserves special
mention.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From doug.mtview@gmail.com  Wed Oct 23 11:37:39 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 B8DAD11E8182 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 11:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 EQpclcn1+Lj5 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 11:37:33 -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 2B29111E81FB for <ietf@ietf.org>; Wed, 23 Oct 2013 11:37:26 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so1368351pbb.0 for <ietf@ietf.org>; Wed, 23 Oct 2013 11:37: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 :content-transfer-encoding:message-id:references:to; bh=iWz1qlrOAarDViNpE5AzVscTEo4I6TCQKnKB6swW8RM=; b=TpfBtOqlGQEz04dz/ZXFauOVRoQQr9Qr07LNyBTswtgLljiVcdM4bhmRfty+hcWmXZ ZECHK23jP0FuPfoVA4Dnc7zFCeraArPf/KpSlEfUHJGtoegheGFFL/IC2hUVIXd/36ee aIBHNsnn8upJgGWZaD7LKt8EexHsroCJTQklXG1jtiJaEQCJUIxvM8x2J9toaa/yorsD 2XQSs9F5wvzSxS30GSEQ6wrSwXm1sbGhfupy4K9v2/PybT6BxtW4O4oWxb/eAI2OvZVX /ugAeTir9QuSSiaRJxA72ve4GIL8nutVTQoOLfRSAH7L6+zqEsK5ys/71wmVb6+PeWJB GomA==
X-Received: by 10.68.244.2 with SMTP id xc2mr3123536pbc.58.1382553437266; Wed, 23 Oct 2013 11:37:17 -0700 (PDT)
Received: from [192.168.2.116] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id ef10sm43012756pac.1.2013.10.23.11.37.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Oct 2013 11:37:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <m28uxkyovt.wl%randy@psg.com>
Date: Wed, 23 Oct 2013 11:37:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C97F189-9748-4DCC-8BAC-AA7DAE9EF1F1@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1816)
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, 23 Oct 2013 18:37:40 -0000

On Oct 23, 2013, at 8:43 AM, Randy Bush <randy@psg.com> wrote:

> the chilling effect of vigilateism is far worse than spam or trolls.
> we've been dealing with the latter for decades, and there is little
> actual real harm if any.  the chilling effect of vigilanteism causes
> actual harm and reduces the rich diversity of opinion, culture, and
> viewpoint.

Dear Randy,

I agree. It seems some think greater progress is made by ignoring any =
definition of fair treatment. =20

Regards,
Douglas Otis


=20



From jari.arkko@piuha.net  Wed Oct 23 12:53:08 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 B9E1B11E8142; Wed, 23 Oct 2013 12:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 4H+gmPFq0a61; Wed, 23 Oct 2013 12:53:03 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0669E11E8233; Wed, 23 Oct 2013 12:53:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4CA702CECD; Wed, 23 Oct 2013 22:53:00 +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 3TjiX8l_ND1Z; Wed, 23 Oct 2013 22:52:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F24232CC48; Wed, 23 Oct 2013 22:52:52 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-tp-rosetta-stone-12
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com>
Date: Thu, 24 Oct 2013 03:52:48 +0800
Content-Transfer-Encoding: 7bit
Message-Id: <73B58FF5-B4D8-4377-A7DE-3B1505AE15EF@piuha.net>
References: <002a01cec7ea$568c8f10$03a5ad30$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art@ietf.org, draft-ietf-mpls-tp-rosetta-stone.all@tools.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, 23 Oct 2013 19:53:08 -0000

Roni: thank you very much for your review.

Jari


From randy_presuhn@mindspring.com  Wed Oct 23 18:18:51 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 334C411E8298 for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 18:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.092
X-Spam-Level: 
X-Spam-Status: No, score=-100.092 tagged_above=-999 required=5 tests=[AWL=-0.093, 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 voghhKynlBLJ for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 18:18:45 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id D701011E82A1 for <ietf@ietf.org>; Wed, 23 Oct 2013 18:18:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=Q7hFR5LqOlvb7n6gyKV47wlc9YwrmgahD4XdAdUbD5m/DTEPUK33eOi3DWXVjqq9; 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.33] (helo=elwamui-darkeyed.atl.sa.earthlink.net) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1VZ9ZM-0004lM-OE for ietf@ietf.org; Wed, 23 Oct 2013 21:18:36 -0400
Received: from 76.254.54.79 by webmail.earthlink.net with HTTP; Wed, 23 Oct 2013 21:18:36 -0400
Message-ID: <22564235.1382577516827.JavaMail.root@elwamui-darkeyed.atl.sa.earthlink.net>
Date: Wed, 23 Oct 2013 18:18:36 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
Subject: Re: Internet standardisation remains unilateral
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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8889e105617274a0edbe295e6ffcc9d254d8bf140c944ce54e1350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.33
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, 24 Oct 2013 01:18:51 -0000

Hi -

>From: John Day <jeanjour@comcast.net>
>Sent: Oct 23, 2013 7:55 AM
..
>Subject: Re: Internet standardisation remains unilateral
...
>Agreed that business interest is the primary driving factor and since 
>most vendors are in the developed world, that is where the 
>participation comes from.
>
>Every standards committee I have ever had contact with found it 
>difficult to get "user" participation,  Generally, those 
>organizations argue that the standards work was beyond what they saw 
>as their planning horizon.  Of course, this doesn't stop them from 
>complaining that they had to buy what the vendors produce as opposed 
>to what they might liked to have seen!  ;-)  But we all know how 
>management tends to think.  ;-)

My limited experience has been that this is upside-down from how
organizations were brought to the standardization trough.  If
there was management support, it tended to be because management
had been persuaded by some technical folk that participation
would make business sense.  Sometimes that persuasion was not
technical, but took the form of "if letting those engineers go
to three meetings a year will keep them from leaving us for
a competitor, it's a worthwhile expenditure."

In either case, there is a value proposition that is immediately
evident to the participant: brain candy, resume building,
cultivating contacts, or maybe even legitimate belief that
it's in the supporting organization's interest.  But in the
potential participant's mind those benefits need to outweigh
the personal and organizational cost of "persuading" management,
as well as the pain and anguish of working within a given
standardization forum.  The IETF is hard on people, and we
should not ignore the toll that it takes or the losses we
incur by driving folks away.

If users/workers from a given region have little leverage,
or if participation does little to advance their careers, or
if the financial or psychic cost of participation is too high,
we should not be surprised if they are not motivated to participate.

But this is all just guesswork until we learn *from*
*them* how participation could be made worth their while.

Randy

From peter@akayla.com  Wed Oct 23 21:08:07 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 B6AD611E8121; Wed, 23 Oct 2013 21:08:07 -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 wEp7HYHfMPE9; Wed, 23 Oct 2013 21:08:03 -0700 (PDT)
Received: from p3plsmtpa07-04.prod.phx3.secureserver.net (p3plsmtpa07-04.prod.phx3.secureserver.net [173.201.192.233]) by ietfa.amsl.com (Postfix) with ESMTP id EBE0611E8106; Wed, 23 Oct 2013 21:08:02 -0700 (PDT)
Received: from [10.8.39.2] ([173.14.120.161]) by p3plsmtpa07-04.prod.phx3.secureserver.net with  id gs7x1m0023V1fxZ01s7zdv; Wed, 23 Oct 2013 21:08:02 -0700
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Date: Wed, 23 Oct 2013 21:08:02 -0700
Subject: Gen-ART Telechat review of draft-kolkman-proposed-standards-clarified-04
From: Peter Yee <peter@akayla.com>
To: <draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>
Message-ID: <CE8DEA35.7250%peter@akayla.com>
Thread-Topic: Gen-ART Telechat review of draft-kolkman-proposed-standards-clarified-04
In-Reply-To: <CE834CA6.6EE3%peter@akayla.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "gen-art@ietf.org" <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, 24 Oct 2013 04:08:07 -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>

Document: draft-kolkman-proposed-standards-clarified-04
Reviewer: Peter Yee
Review Date: Oct-23-2013
IETF LC End Date: Oct-16-2013
IESG Telechat date: Oct-24-2013

Summary: This draft is ready for publication as a BCP. [Ready]

This draft updates the description of the Proposed Standard maturity
level previously defined in RFC 2026.  The update reflects the reality
of greater maturity embodied in Proposed Standards than is given in
RFC 2026.



From abdussalambaryun@gmail.com  Wed Oct 23 22:39:11 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 CF90111E82CC for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 22:39:11 -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.074,  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 VvQkRD5Ij9ox for <ietf@ietfa.amsl.com>; Wed, 23 Oct 2013 22:39:11 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id A356711E82D9 for <ietf@ietf.org>; Wed, 23 Oct 2013 22:39:07 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id x10so1696050pdj.9 for <ietf@ietf.org>; Wed, 23 Oct 2013 22:39: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=dLgO62I18UZR4xt+JX2qMmUSt2ukUnsz7tiG7Gvjsic=; b=aVB/jTjD+g63+Fl3JNL8pwvnV1fydWVfif8wIsv7fo18n24CQBGDh5Gx6QLvBYaj/1 S7gm2MYhlFLo43A+ng6iauRkIjutN7+cYyeTiPfB0No+tg2PYO1cCbBWzVXcHtotEFGa liFpXye+OYzfnAjOyqCR6Fz2stmNUzYxpi8c/84CCh3YjXldItGbpy1SH4WHvTQ7QLUZ P8y42ai47UehyLPKVt/FrejhEgllpUM6P6zUgWCQ9PI11aK7MKwXyrwfXgEEx0PxT4/r Xga7OeCbq5c2ljvXylM0VXIKM1IpPFf4LyAM/WFaGvUdY+HZ8/z1z+jrCgEOn+1O7ncv fjbg==
MIME-Version: 1.0
X-Received: by 10.66.161.138 with SMTP id xs10mr1559091pab.56.1382593147238; Wed, 23 Oct 2013 22:39:07 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 23 Oct 2013 22:39:07 -0700 (PDT)
In-Reply-To: <0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org>
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com> <02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org> <0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org>
Date: Thu, 24 Oct 2013 06:39:07 +0100
Message-ID: <CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com>
Subject: Re: Comments from the IAB on NIST SP 800-90A Proceeding
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b86e86468ff9204e9760dc8
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, 24 Oct 2013 05:39:12 -0000

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

Hi Russ

The comment has a statement which I am against;
IETF standards depend on NIST standards and the process by which they are
developed.

The statement contradicts the first, that IETF references also other
government algorithms.
Is this a specific or general dependence? And does IETF standards
really depend on NIST standard process and development? Is the
statement talking about all IETF security standards?

Best regards
Abdussalam


On Wednesday, October 23, 2013, IAB Chair wrote:

> Today, the IAB sent comments to the US National Institute for Standards
> and Technology (NIST) in the matter of the NIST Special Publication 800-90A
> (Recommendation for Random Number Generation Using Deterministic Random Bit
> Generators) review proceeding.  In the statement, the IAB supports
> re-opening of the comment period on NIST SP 800-90A, and the IAB also makes
> recommendations relating to the review process for cybersecurity and
> cryptographic standards to enhance transparency and openness.
>
> The full statement is available from the IAB website:
> http://www.iab.org/wp-content/IAB-uploads/2013/10/IAB-NIST-FINAL.pdf
>
> On behalf of the IAB,
>  Russ Housley
>  IAB Chair
>
>

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

Hi Russ<div><br></div><div>The comment has a statement which I am against;<=
/div><div>IETF standards depend on NIST standards and the process by which =
they are developed.</div><div><br></div><div>The statement contradicts the =
first, that IETF references also other government algorithms.</div>
<div>Is this a specific or general dependence? And=A0does IETF standards re=
ally=A0depend on NIST standard process and development? Is the statement=A0=
talking about all IETF security standards?</div><div><br></div><div>Best re=
gards</div>
<div>Abdussalam</div><div><br><br>On Wednesday, October 23, 2013, IAB Chair=
  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Today, the IAB sent comments to =
the US National Institute for Standards and Technology (NIST) in the matter=
 of the NIST Special Publication 800-90A (Recommendation for Random Number =
Generation Using Deterministic Random Bit Generators) review proceeding. =
=A0In the statement, the IAB supports re-opening of the comment period on N=
IST SP 800-90A, and the IAB also makes recommendations relating to the revi=
ew process for cybersecurity and cryptographic standards to enhance transpa=
rency and openness.<br>

<br>
The full statement is available from the IAB website: <a href=3D"http://www=
.iab.org/wp-content/IAB-uploads/2013/10/IAB-NIST-FINAL.pdf" target=3D"_blan=
k">http://www.iab.org/wp-content/IAB-uploads/2013/10/IAB-NIST-FINAL.pdf</a>=
<br>

<br>
On behalf of the IAB,<br>
=A0Russ Housley<br>
=A0IAB Chair<br>
<br>
</blockquote></div>

--047d7b86e86468ff9204e9760dc8--

From framefritti@gmail.com  Thu Oct 24 00:28:51 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 7AD5911E8166 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:28: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 JUlExL+MNdPa for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:28:51 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6A79F21E808D for <ietf@ietf.org>; Thu, 24 Oct 2013 00:28:46 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id q59so1867275wes.37 for <ietf@ietf.org>; Thu, 24 Oct 2013 00:28: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 :content-type; bh=4tyw2XlSVWsWu8gucD3cQWQI3Ao8i1rOQMlib8n8aDs=; b=uEKR7qhYwCQ36QjrD60z9jBefU2oWaeHJoNJa4ZrAiCbK4VSc/zA9ZeYCyOryzHniP jPMQ4tT0C1RxYWCIHmpbHyjV0hEMSvD023h6mCvcgdp/ZCwr5Xl4H91Y/m27juzPtoU9 wD0knLE2u6lUW51TuTozWBU0+SIweFaBwmWz5g0Y8i9eSI56VPYYP10Pb0jjZEUCpITl C4/VPLR6mERZkr9aji8uq2hz2LMZhGdw9Roz8CxovQVxm0v/jJ7BB9sWzrnGnArHOpaz TExLHuQpeVag42e+n0ylHp8ewSigdg8f4DdGhOL0VrsiM6GWIvlETXNsCwb3hZFpHe7B SKuw==
MIME-Version: 1.0
X-Received: by 10.194.94.33 with SMTP id cz1mr159964wjb.73.1382599725233; Thu, 24 Oct 2013 00:28:45 -0700 (PDT)
Received: by 10.227.207.65 with HTTP; Thu, 24 Oct 2013 00:28:45 -0700 (PDT)
In-Reply-To: <CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com>
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com> <02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org> <0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org> <CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com>
Date: Thu, 24 Oct 2013 09:28:45 +0200
Message-ID: <CABSMSPX8LcVNEfQc08Yx_73pL3DRfN_Sj09v9OdbOex7=4NNXw@mail.gmail.com>
Subject: Re: Comments from the IAB on NIST SP 800-90A Proceeding
From: Riccardo Bernardini <framefritti@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IAB <iab@iab.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, 24 Oct 2013 07:28:51 -0000

On Thu, Oct 24, 2013 at 7:39 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Hi Russ
>
> The comment has a statement which I am against;
> IETF standards depend on NIST standards and the process by which they are
> developed.
>
> The statement contradicts the first, that IETF references also other
> government algorithms.

I do not see a contradiction. I think that the sentence is to be
interpreted as "SOME IETF standards depend on SOME NIST standard."
This is true and it does not rule out that some IETF standards can
depend on other standards (or any standard at all).

Clearly the concern is that if some NIST standard is considered
"suspect" because of a loss of transparency (e.g., the PRNG based on
elliptic curves), the same loss of trustfulness will taint any IETF
standard that uses it.  IETF standards that do not use NIST products
are clearly not affected by this.

> Is this a specific or general dependence? And does IETF standards really
> depend on NIST standard process and development? Is the statement talking
> about all IETF security standards?
>
> Best regards
> Abdussalam
>
>
> On Wednesday, October 23, 2013, IAB Chair wrote:
>>
>> Today, the IAB sent comments to the US National Institute for Standards
>> and Technology (NIST) in the matter of the NIST Special Publication 800-90A
>> (Recommendation for Random Number Generation Using Deterministic Random Bit
>> Generators) review proceeding.  In the statement, the IAB supports
>> re-opening of the comment period on NIST SP 800-90A, and the IAB also makes
>> recommendations relating to the review process for cybersecurity and
>> cryptographic standards to enhance transparency and openness.
>>
>> The full statement is available from the IAB website:
>> http://www.iab.org/wp-content/IAB-uploads/2013/10/IAB-NIST-FINAL.pdf
>>
>> On behalf of the IAB,
>>  Russ Housley
>>  IAB Chair
>>
>

From jari.arkko@piuha.net  Thu Oct 24 00:35:34 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 D304E11E82FA for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:35:33 -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 ubEYnKduwZAY for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:35:28 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7524211E82EF for <ietf@ietf.org>; Thu, 24 Oct 2013 00:35:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ABBB22CC95; Thu, 24 Oct 2013 10:35:22 +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 KsKjTtO8SW8c; Thu, 24 Oct 2013 10:35:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 00F262CC48; Thu, 24 Oct 2013 10:35:18 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Comments from the IAB on NIST SP 800-90A Proceeding
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com>
Date: Thu, 24 Oct 2013 15:35:15 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4E2F776-0744-4DE2-9B0A-86CB9736C33F@piuha.net>
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com> <02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org> <0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org> <CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: IAB <iab@iab.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, 24 Oct 2013 07:35:34 -0000

Abdussalam,

> The comment has a statement which I am against;
> IETF standards depend on NIST standards and the process by which they =
are developed.
>=20
> The statement contradicts the first, that IETF references also other =
government algorithms.
> Is this a specific or general dependence? And does IETF standards =
really depend on NIST standard process and development? Is the statement =
talking about all IETF security standards?

The point was that some IETF standards do normatively refer to NIST =
standards. (Look for "NIST" in RFCs and you'll find many hits.)

Of course, IETF standards also depend on many other things, including =
algorithms developed by others :-)

Hope this clarifies,

Jari


From hannes.tschofenig@gmx.net  Thu Oct 24 00:38:04 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 1437C11E82F9 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 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 XxhMOcj2zhMb for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 00:37:59 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 2902711E82F3 for <ietf@ietf.org>; Thu, 24 Oct 2013 00:37:55 -0700 (PDT)
Received: from [172.16.254.200] ([80.92.115.161]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MH4Os-1VVRsB11oQ-00DlqE for <ietf@ietf.org>; Thu, 24 Oct 2013 09:37:53 +0200
Message-ID: <5268CE6A.3030904@gmx.net>
Date: Thu, 24 Oct 2013 09:38:18 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Riccardo Bernardini <framefritti@gmail.com>,  "ietf@ietf.org" <ietf@ietf.org>, IAB <iab@iab.org>
Subject: Re: Comments from the IAB on NIST SP 800-90A Proceeding
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com>	<02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org>	<0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org>	<CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com> <CABSMSPX8LcVNEfQc08Yx_73pL3DRfN_Sj09v9OdbOex7=4NNXw@mail.gmail.com>
In-Reply-To: <CABSMSPX8LcVNEfQc08Yx_73pL3DRfN_Sj09v9OdbOex7=4NNXw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:VzS9JRXN6yL4qJhp91taq6jtlvYhgE94kPexFCtWNcDn2r9fK47 AHt48TtIcBFm7k3B2XaQdxloK5Cis6+F4L2LzmnnPplPqDxtW7bs4QSjHWkp3rV0aGZbo+t tP5aJTOBMjIZQwQ4foNyOfT/J0eZXD+khL3JNtdH/S4WpCMWL/OvsJJVCxI9sy2dfGvIffH jVLCiMgztgIMVVuqXIQ7Q==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Oct 2013 07:38:04 -0000

On 10/24/2013 09:28 AM, Riccardo Bernardini wrote:
> does IETF standards really
>>depend on NIST standard process and development? Is the statement talking
>>about all IETF security standards?


As I tried to explain in 
http://tools.ietf.org/html/draft-tschofenig-perpass-surveillance-00 the 
IETF is currently not in the business of developing cryptographic 
primitives. This work is done outside the IETF (to a large extend).

Of course, our security protocols have to use cryptographic primitives 
and there is the question where do these come from.

It turns out that there are not that many organizations in the world who 
have the necessary level of expertise. NIST is one of them.

Ciao
Hannes


From dhc@dcrocker.net  Thu Oct 24 06:29:33 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 575D411E81A1 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 06:29: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 TG0yawXGjOcJ for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 06:29:28 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 83CB811E829B for <ietf@ietf.org>; Thu, 24 Oct 2013 06:29:25 -0700 (PDT)
Received: from [10.3.89.42] (IP-173-231-109-130.static.fibrenoire.ca [173.231.109.130] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9ODTA6l017680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Oct 2013 06:29:14 -0700
Message-ID: <5269209F.3060706@dcrocker.net>
Date: Thu, 24 Oct 2013 09:29:03 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: draft-kolkman-proposed-standards-clarified.all@tools.ietf.org
Subject: Review of:  Characterization of Proposed Standards
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, 24 Oct 2013 06:29:15 -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: Thu, 24 Oct 2013 13:29:33 -0000

Review of:    Characterization of Proposed Standards
I-D:          draft-kolkman-proposed-standards-clarified-04

Reviewed by:  D. Crocker
Date:         24 October 2013


Summary:

  This draft offers revised normative text for the criteria used to
qualify IETF drafts as entry-level Proposed Standards status. The
draft's background discussion makes a number of assertions of fact
without substantiation, at least two of which are probably not correct.
The revised normative text includes two criteria that also are likely
inaccurate.

    The draft is not ready for approval.



Detail:


> Abstract
>
> RFC 2026 describes the review performed by the IESG on IETF Proposed
> Standard RFCs and states the maturity level of those documents.
> This document clarifies those descriptions and updates RFC 2026 by
> providing a new characterization of Proposed Standards.

"those" descriptions?  As the Introduction confirms, the draft covers
only one of them.


> 2. IETF Review of Proposed Standards
>
>
> The entry-level maturity for the standards track is "Proposed
> Standard".  A specific action by the IESG is required to move a
> specification onto the standards track at the "Proposed Standard"
> level. Initially it was assumed that most IETF technical
> specifications would progress through a series of maturity stages
> starting with Proposed Standard, then progressing to Draft Standard
> then, finally, to Internet Standard (see RFC 2026 section 6). Over
> time, for a number of reasons, this progression became less common.

It was /always/ uncommon.  There was never a time when progression
through the full sequence typically happened.


> In response, the IETF strengthened its review of Proposed Standards,
> basically

It was not 'in response'.  There was never a process of discussing the
issue and changing a policy formally and with clear IETF rough consensus.

The higher bar for Proposed happened organically and mostly through many
independent decisions of those running the standards process over the
years.

Even better, it was always controversial, when discussed in public.  Or
rather, the question of how high the bar should be was always
controversial and was never subject to an explicit rough consensus process.


> operating as if the Proposed Standard was the last chance for the
> IETF to ensure the quality of the technology and the clarity of the
> Standard Track document.  The result was that IETF Proposed
> Standards approved over the last decade or more have had extensive
> reviews.

Many have.  Many have not.  It has depended upon the diligence chosen by
everyone working on the draft or doing reviews.

I'm pressing this point because the language being used for this draft
is leaning towards mixing formal process measures to raise the /effort/
needed to get approved, with actual quality assurance /results/.  In
fact we often publish drafts that have actually have very few eyes doing
deep and thoughtful review and we often publish drafts that don't work
very well.  That is, the much higher formal bar still allows quite a bit
of cruft to jump over...


> Because of this change in review assumptions, IETF Proposed
> Standards should be considered to be at least as mature as final
> standards from other standards development organizations.

An assertion like this requires some discussion detail that compares the
IETF process to specific, other SDO processes, both formally and
effectively.  I'm not disagreeing with the conclusion, but with its
being made rather casually and firmly, but without substantiation.
(Part of the real challenge in doing the comparison is looking for
alternative forms of quality assurance that other SDOs might do, other
than the explicit reviews the IETF does.)

By the way, such a comparison discussion will probably serve to greatly
strengthen the ability to explain/argue for the comparative maturity of
Proposed...


> The IETF review is possibly more extensive than that done in most
> other SDOs owing to the cross-area technical review performed by the
> IETF, exemplified by technical review by the full IESG at the last
> stage of specification development.  That position is further
> strengthened by the common presence of interoperable running code and
> implementation before publication as a Proposed Standard.

There's actually a reasonable possibility that we do /less/ pre-Proposed
interoperable implementation now than we did 20 years ago.

Consequently an assertion that implementation is 'common' needs some
objective substantiation in comparison to the time we defined the
standards labels.



> 3. Characterization of Specification
>
>
> Section 3.1 of this document replaces RFC 2026 Section 4.1.1.
> Section 3.2 is a verbatim copy of the characterization of Internet
> Standards from RFC 2026 Section 4.1.3 and is provided for convenient
> reference.
>
> 3.1. Characterization of IETF Proposed Standard Specifications
>
>
> The entry-level maturity for the standards track is "Proposed
> Standard".  A specific action by the IESG is required to move a
> specification onto the standards track at the "Proposed Standard"
> level.
>
> A Proposed Standard specification is stable, has resolved known
> design choices, is well-understood, has received significant
> community review, and appears to enjoy enough community interest to
> be considered valuable.

The text has two major flaws that serve to assert a much higher
practical maturity for the Proposed Standard documents we publish than
is very often observably true:

Well understood:

    For a specification with any interesting level of innovation or
complexity, it is almost never 'well understood' at the time it is
approved by the IETF.  That requires significant implementation,
deployment and use experience.

    The fact that many eyes might have done a static review or even that
a couple of folk have written some code or even that those folk
interoperated does not come close to qualifying the specification as
"well understood".

Enough community interest:

    We often publish specifications that actually have very little
community support.  This is evidenced by a) very low working group
participation levels, and b) failure to successfully deploy and get used.



>
> Usually, neither implementation nor operational experience is
> required for the designation of a specification as a Proposed
> Standard.  However, such experience is highly desirable, and will
> usually represent a strong argument in favor of a Proposed Standard
> designation.
>
> The IESG may require implementation and/or operational experience
> prior to granting Proposed Standard status to a specification that
> materially affects the core Internet protocols or that specifies
> behavior that may have significant operational impact on the
> Internet.
>
> A Proposed Standard will have no known technical omissions with
> respect to the requirements placed upon it.  Proposed Standards are
> of such quality that implementations can be deployed in the
> Internet.

And yet we know that this often is not true.  However, language like
this is going to cause the IESG to naturally raise the bar even higher,
for fear that a spec still is not good enough.

The real goal of the language change, here, is to give assurances that
the specification is "sufficiently" mature, in terms of concern for
market deployment.

The part that the document can't say, but has as an implicit point since
it is motivating the draft, is that the maturity is at least as good as
that produced by other SDOs.

Perhaps:

     Proposed Standards are of such quality that they are ready for the
usual market-based product development and deployment efforts into the
Internet.


> However, as with all technical specifications, Proposed Standards
> may

Remove "However".


> be revised if problems are found or better solutions are identified,
> when experiences with deploying implementations of such technologies
> at scale is gathered.



> 4. Further Considerations
>
>
> While less mature specifications will usually be published as
> Informational or Experimental RFCs, the IETF may, on occasion,

On occasion?  In fact it's quite common and possibly the norm.  Let's
not pretend otherwise.


> publish a specification that still contains areas for improvement or
> certain uncertainties about whether the best engineering choices are
> made.  In those cases that fact will be clearly and prominently
> communicated in the document e.g.  in the abstract, the
> introduction, or a separate section or statement.


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From abdussalambaryun@gmail.com  Thu Oct 24 09:09:58 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 1060111E8194 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 09:09:50 -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 OPvrtuO1G4DX for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 09:09:49 -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 9C79111E81B2 for <ietf@ietf.org>; Thu, 24 Oct 2013 09:03:39 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so2832741pbb.14 for <ietf@ietf.org>; Thu, 24 Oct 2013 09:03: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=Dbcq1PTcDM0kECO14iR6m8cOETIHtX8hINWg+hkzmf8=; b=0KPNE+DmYL8iVzEW3DMKnsGmOeAXrhe0k+++imlfpfF4roAXd9XPON4wokBrq735PF xfHJy3S7udPWnVwfh2q9HaERwT1CTuYN27itkt4rivUQ9L0QMsPyqGgwCVgW77xl4k/J mnxiHIjzjRltryTJIFXh/P/tsZoq5bmuhYvo9KtgBr8DLmgVH/TQWTcYvg6/CtKJRie+ DdITu8JFSSmndOBN8Cb5lz3O1ygoRVMtdJjiW1OJThwfHTIviSPpiEaD7timGQcAJ8u/ S+RSy1W0VEhwucgABGzJ0ozNaFsKwKg/u5U9PXZ1X7Y5bHcg8Z+g1cIPAksolRTiKjIB fLrw==
MIME-Version: 1.0
X-Received: by 10.66.148.97 with SMTP id tr1mr3905635pab.163.1382630619219; Thu, 24 Oct 2013 09:03:39 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Thu, 24 Oct 2013 09:03:39 -0700 (PDT)
In-Reply-To: <5269209F.3060706@dcrocker.net>
References: <5269209F.3060706@dcrocker.net>
Date: Thu, 24 Oct 2013 17:03:39 +0100
Message-ID: <CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.com>
Subject: Review of: Characterization of Proposed Standards
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b6d9fa2ea0fa704e97ec698
Cc: "draft-kolkman-proposed-standards-clarified.all@tools.ietf.org" <draft-kolkman-proposed-standards-clarified.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: Thu, 24 Oct 2013 16:09:58 -0000

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

I don't agree with comparing our standards with other SDO standards within
our work, or even making our work process depend on other SDO products.
IETF RFC should try its best to have normative references that are RFCs not
dependent/government oriented. We may end up with a new name for our IETF,
as dependent IETF (DIETF).

AB

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

I don&#39;t agree with comparing our standards with other SDO standards wit=
hin our work,=A0or even making our work=A0process depend on other SDO produ=
cts. IETF RFC should try its best to have normative references that are RFC=
s not dependent/government oriented. We may end up with a new name for our =
IETF, as dependent IETF (DIETF).<span></span><div>

<br></div><div>AB</div>

--047d7b6d9fa2ea0fa704e97ec698--

From housley@vigilsec.com  Thu Oct 24 09:32:50 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 C568C11E81C5 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 09:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.179
X-Spam-Level: 
X-Spam-Status: No, score=-100.179 tagged_above=-999 required=5 tests=[AWL=-2.042, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, MANGLED_AVOID=2.3, RDNS_NONE=0.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 JhtaxNfbjrqp for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 09:32:45 -0700 (PDT)
Received: from odin.smetech.net (unknown [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 050C411E81B2 for <ietf@ietf.org>; Thu, 24 Oct 2013 09:32:41 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 6D22D9A4169; Thu, 24 Oct 2013 12:32:30 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id YV7bFqw3T1Ua; Thu, 24 Oct 2013 12:32:09 -0400 (EDT)
Received: from [192.168.2.107] (pool-71-191-197-233.washdc.fios.verizon.net [71.191.197.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2F0449A416F; Thu, 24 Oct 2013 12:32:09 -0400 (EDT)
Subject: Re: [IAB] Comments from the IAB on NIST SP 800-90A Proceeding
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5268CE6A.3030904@gmx.net>
Date: Thu, 24 Oct 2013 12:31:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D085255C-3675-48B4-BE08-E3D224FBBC72@vigilsec.com>
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com>	<02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org>	<0C7687D7-CFAF-4122-950D-13DCAC6A3598@iab.org>	<CADnDZ8_Vor0ksG1Q+PU0QH1O-ViDbziBqNh72bw4eL1T2LCrKA@mail.gmail.com> <CABSMSPX8LcVNEfQc08Yx_73pL3DRfN_Sj09v9OdbOex7=4NNXw@mail.gmail.com> <5268CE6A.3030904@gmx.net>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
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, 24 Oct 2013 16:32:50 -0000

>>> depend on NIST standard process and development? Is the statement =
talking
>>> about all IETF security standards?
>=20
>=20
> As I tried to explain in =
http://tools.ietf.org/html/draft-tschofenig-perpass-surveillance-00 the =
IETF is currently not in the business of developing cryptographic =
primitives. This work is done outside the IETF (to a large extend).
>=20
> Of course, our security protocols have to use cryptographic primitives =
and there is the question where do these come from.
>=20
> It turns out that there are not that many organizations in the world =
who have the necessary level of expertise. NIST is one of them.

Indeed.

Some IETF standards normatively reference NIST cryptographic standards, =
and many of them are the mandatory to implement algorithm.  So, these =
IETF standards do depend on the NIST standards, and indirectly on the =
process by which the NIST standards were developed.

The IETF has developed it own cryptographic mechanisms when there has =
been a void.  RFC 3217 is one example.  When that work was done by the =
S/MIME WG, the group went to great lengths to get cryptographers to =
participate.  This is not the preferred approach, but sometimes there is =
a void that needs to be filled.

Russ


From kathleen.moriarty@emc.com  Thu Oct 24 10:54:40 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 DCFDB21F99DD for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 10:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.216,  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 XsIk+snYndQr for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 10:54:36 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9E17E11E81AB for <ietf@ietf.org>; Thu, 24 Oct 2013 10:54:06 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9OHs37l013451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Oct 2013 13:54:03 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r9OHs37l013451
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1382637244; bh=FcT9BoyxHw9m0L0sWDG/K2jeG+c=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=HLFlBUMLit+MDyaiSx1wXIpk25BKEfCHwg7+rKSTYRbw5p0fGy6t2wJsp1ZKtIFqD ruUwqm5jdbMPTOrrADLjzBf9UUkwhYT8tlsdrjjKpr6mOd7twIpVag0yQAaHEAE3Fa aiz32cB00o7QpXGrL5czSxE74a8V+rkReT+BkmDE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com r9OHs37l013451
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd06.lss.emc.com (RSA Interceptor); Thu, 24 Oct 2013 10:53:53 -0700
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r9OHrrTh014586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 24 Oct 2013 13:53:53 -0400
Received: from mx15a.corp.emc.com ([169.254.1.46]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Thu, 24 Oct 2013 13:53:36 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Date: Thu, 24 Oct 2013 13:53:51 -0400
Subject: RE: Review of: Characterization of Proposed Standards
Thread-Topic: Review of: Characterization of Proposed Standards
Thread-Index: Ac7Q082zattccST5Sr6yKoGx0xIA9gADclFg
Message-ID: <F5063677821E3B4F81ACFB7905573F24049EA32C49@MX15A.corp.emc.com>
References: <5269209F.3060706@dcrocker.net> <CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.com>
In-Reply-To: <CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.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_F5063677821E3B4F81ACFB7905573F24049EA32C49MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Cc: "draft-kolkman-proposed-standards-clarified.all@tools.ietf.org" <draft-kolkman-proposed-standards-clarified.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: Thu, 24 Oct 2013 17:54:41 -0000

--_000_F5063677821E3B4F81ACFB7905573F24049EA32C49MX15Acorpemcc_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I don't see how that is possible.  Different SDOs have different focus area=
s with clear interdependencies between the work.  We don't need to try to r=
eplicate the work happening elsewhere, but rather should continue to play n=
ice with other SDOs.  It would be really hard to get all of the various exp=
erts needed attend multiple forums because one SDO didn't want to reference=
 the work they did in another SDO.

Regards,
Kathleen

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Abd=
ussalam Baryun
Sent: Thursday, October 24, 2013 12:04 PM
To: ietf
Cc: draft-kolkman-proposed-standards-clarified.all@tools.ietf.org
Subject: Review of: Characterization of Proposed Standards

I don't agree with comparing our standards with other SDO standards within =
our work, or even making our work process depend on other SDO products. IET=
F RFC should try its best to have normative references that are RFCs not de=
pendent/government oriented. We may end up with a new name for our IETF, as=
 dependent IETF (DIETF).

AB

--_000_F5063677821E3B4F81ACFB7905573F24049EA32C49MX15Acorpemcc_
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=3DGenerator content=3D"Micros=
oft 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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I don&#82=
17;t see how that is possible.&nbsp; Different SDOs have different focus ar=
eas with clear interdependencies between the work.&nbsp; We don&#8217;t nee=
d to try to replicate the work happening elsewhere, but rather should conti=
nue to play nice with other SDOs. &nbsp;It would be really hard to get all =
of the various experts needed attend multiple forums because one SDO didn&#=
8217;t want to reference the work they did in another SDO.&nbsp; <o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D'>Kathleen<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><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"'> ietf-bounces@ietf.org [mailto:ietf-=
bounces@ietf.org] <b>On Behalf Of </b>Abdussalam Baryun<br><b>Sent:</b> Thu=
rsday, October 24, 2013 12:04 PM<br><b>To:</b> ietf<br><b>Cc:</b> draft-kol=
kman-proposed-standards-clarified.all@tools.ietf.org<br><b>Subject:</b> Rev=
iew of: Characterization of Proposed Standards<o:p></o:p></span></p><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I don't agree with =
comparing our standards with other SDO standards within our work,&nbsp;or e=
ven making our work&nbsp;process depend on other SDO products. IETF RFC sho=
uld try its best to have normative references that are RFCs not dependent/g=
overnment oriented. We may end up with a new name for our IETF, as dependen=
t IETF (DIETF).<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div><div><p class=3DMsoNormal>AB<o:p></o:p></p></div></div></body></htm=
l>=

--_000_F5063677821E3B4F81ACFB7905573F24049EA32C49MX15Acorpemcc_--

From dhc@dcrocker.net  Thu Oct 24 11:01:01 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 5CCF211E81DA for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 11:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Level: 
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023,  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 tCVfE9ZJcy2r for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 11:00:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4E1BA11E819A for <ietf@ietf.org>; Thu, 24 Oct 2013 11:00:56 -0700 (PDT)
Received: from [172.16.22.13] ([207.253.19.196]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9OI0nFU024720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Oct 2013 11:00:53 -0700
Message-ID: <52696048.1050701@dcrocker.net>
Date: Thu, 24 Oct 2013 14:00:40 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, ietf <ietf@ietf.org>
Subject: Re: Review of: Characterization of Proposed Standards
References: <5269209F.3060706@dcrocker.net>	<CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24049EA32C49@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24049EA32C49@MX15A.corp.emc.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.0 (sbh17.songbird.com [72.52.113.66]); Thu, 24 Oct 2013 11:00:54 -0700 (PDT)
Cc: "draft-kolkman-proposed-standards-clarified.all@tools.ietf.org" <draft-kolkman-proposed-standards-clarified.all@tools.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, 24 Oct 2013 18:01:01 -0000

On 10/24/2013 1:53 PM, Moriarty, Kathleen wrote:
> I don’t see how that is possible.  Different SDOs have different focus
> areas with clear interdependencies between the work.  We don’t need to
> try to replicate the work happening elsewhere, but rather should
> continue to play nice with other SDOs.  It would be really hard to get
> all of the various experts needed attend multiple forums because one SDO
> didn’t want to reference the work they did in another SDO.


For reference, the comment about other SDOs in my review note was 
specific to the existing draft text that compared an aspect of IETF 
documents to documents from other SDOs and my suggestion was merely to 
substantiate the claim(s) being made.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From narten@us.ibm.com  Thu Oct 24 11:17: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 1740D11E8351 for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 11:17:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.444
X-Spam-Level: 
X-Spam-Status: No, score=-109.444 tagged_above=-999 required=5 tests=[AWL=-1.155, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_URGBIZ=0.725, URG_BIZ=1.585, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZSIEE-mdIU-V for <ietf@ietfa.amsl.com>; Thu, 24 Oct 2013 11:17:08 -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 1A4CB11E829B for <ietf@ietf.org>; Thu, 24 Oct 2013 11:17:06 -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>; Thu, 24 Oct 2013 14:17:05 -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;  Thu, 24 Oct 2013 14:17:03 -0400
Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id CB11AC90050; Thu, 24 Oct 2013 14:17:01 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22036.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9OIH2mr5374442; Thu, 24 Oct 2013 18:17:02 GMT
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 r9OIH1CW001786; Thu, 24 Oct 2013 14:17:01 -0400
Received: from cichlid.raleigh.ibm.com ([9.57.78.202]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r9OIGtMZ001283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Oct 2013 14:16:56 -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 r9OIGsWe020534; Thu, 24 Oct 2013 14:16:54 -0400
Message-Id: <201310241816.r9OIGsWe020534@cichlid.raleigh.ibm.com>
To: nomcom13@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [IETF] Re: NOMCOM - Critical shortage of nominees for multiple areas
In-reply-to: <58078580-C20F-4257-8915-9E37350B320E@kumari.net>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com> <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com> <5262D202.1020501@ieca.com> <58078580-C20F-4257-8915-9E37350B320E@kumari.net>
Comments: In-reply-to Warren Kumari <warren@kumari.net> message dated "Sat, 19 Oct 2013 16:18:47 -0400."
Date: Thu, 24 Oct 2013 14:16:53 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13102418-7182-0000-0000-000008E11DB3
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Oct 2013 18:17:14 -0000

Going back to something said earlier. While I understand that it may
be good for the nomcom/ietf to develop a list of alternate candidates
even if the incumbent is strong, just for backup, etc., there is a
flip side as well.

Applying takes time. The survey isn't exactly short, and going through
the motions to get internal support can also take time. And for
someone who has applied and is waiting the results, they may find
themselves in an awkward position w.r.t. planning future work
activities (will they have time to take on new activities or will the
nomcom select them?).

All this uses resources that arguably could be spent more
productively, e.g., doing WG work.

I think it's fine to say no to the nomcom and say something like
"incumbent is doing a great job and nomcom should not waste folks'
time beating the bushes to build up a list when there is no compelling
reason not to just quickly reup the incumbent.

If the nomcom wants to build up a list of future potential nominees,
we might want to think about how to do that in ways other than
nominating them for the *current* cycle. E.g., approaching them about
applying next year, and (gasp!) maybe even mentoring them a bit...

Thomas

<kathleen.moriarty@emc.com> wrote:
> It is important for multiple people to run even when there is an
>incumbent for a fair process.  When Stephen Farrell ran for Sec AD
>again last year, he encouraged me to accept the nomination and run
>against him so that there was a good candidate to make the process
>a bit more fair.  If either Stephen of Sean won the lottery, the
>Noncom would at least have gone through the interview and review
>process with other candidates in advance.  The candidate would
>have worked through the possibility of what this meant with their
>job and that it was possible for them to take on this role (not
>insignificant for many of us).  For me, I thought Stephen was
>doing a fine job and am glad he was put back on the IESG, but it
>is good for the Noncom to have options and backup plans.  I
>received approval from my company, but let my management know that
>it was unlikely that I would be selected since incumbents usually
>return.

> >>> 
> >>> Maybe folks should consider running against an incumbent.  You learn the process and it forces you to figure out if you are interested in the role and could allocate that time to the IETF.  I gave a positive review of Stephen when running against him.
> >>> 
> >>> Thanks,
> >>> Kathleen
> >>> 
> >>> -----Original Message-----
> >>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ersue, Mehmet (NSN - DE/Munich)
> >>> Sent: Friday, October 18, 2013 6:36 AM
> >>> To: ietf@ietf.org; Nomcom@ietfa.amsl.com; Chair@ietfa.amsl.com
> >>> Subject: RE: NOMCOM - Critical shortage of nominees for multiple areas
> >>> 
> >>> Hi Allison,
> >>> 
> >>> in your model you don't count those people who have been rejecting to a nomination, just because they believe the current AD did a very good job and he/she should be reelected.
> >>> 
> >>> So the situation is not that bad, if there is only the current AD on the nominee list.
> >>> 
> >>> Cheers,
> >>> Mehmet
> >>> 
> >>>> -----Original Message-----
> >>>> From: ietf-announce-bounces@ietf.org
> >>>> [mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext NomCom Chair
> >>>> 2013
> >>>> Sent: Thursday, October 17, 2013 4:25 PM
> >>>> To: IETF Announcement List
> >>>> Cc: IETF Discuss
> >>>> Subject: NOMCOM - Critical shortage of nominees for multiple areas
> >>>> 
> >>>> [Catchier Subject line - apologies to those offended by a duplicate]
> >>>> 
> >>>> A critically low number of people have accepted nominations for some
> >>>> of the IESG open positions.  There is only one nominee per slot in
> >>>> APP, OPS and TSV, only two in INT and RAI.  Many folks have declined nominations.
> >>>> 
> >>>> While the Nomcom appreciates that support for two years of intense
> >>>> service is hard to assure, and while we are aware that there is much
> >>>> support for the incumbents who are standing, the IETF should
> >>>> continually be considering which new talent is available for our
> >>>> leadership, and the Nomcom process needs for there to be some review and deliberation.
> >>>> 
> >>>> Therefore, we urgently request that more nominees come forward.
> >>>> 
> >>>> DEADLINES
> >>>> Nominations - October 18
> >>>> Questionnaires from nominees - October 25
> >>>> 
> >>>> Not coincidentally, this is a good time to think over and send your
> >>>> comments about the current statements of desired expertise of
> >>>> positions - this is part of the Nomcom's annual review process as well.  Send them to nomcom13@ietf.org.
> >>>> 
> >>>> Definitive location [*] of the current statements on desired expertise:
> >>>>       https://datatracker.ietf.org/nomcom/2013/expertise/
> >>>> 
> >>>> Instructions and details on nomination [**]:
> >>>>       https://datatracker.ietf.org/ann/nomcom/60602/
> >>>> 
> >>>> Thanks, everyone,
> >>>> 
> >>>> Allison for the Nomcom
> >>>> 
> >>>> [*] This year the Nomcom tools were recoded, and also transitioned
> >>>> into the datatracker.  Apologies for a number of places where we
> >>>> didn't catch reference errors.
> >>>> 
> >>>> [**] Yes, alas, the previous call for nominations used "OAM" instead
> >>>> of "OPS," but we have* corrected this (chair's pilot) error where it
> >>>> occurred in the Nomcom pages.
> > 


From gonzalo.camarillo@ericsson.com  Thu Oct 24 11:33:01 2013
Return-Path: <gonzalo.camarillo@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 1BEB511E819A; Thu, 24 Oct 2013 11:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.641
X-Spam-Level: 
X-Spam-Status: No, score=-105.641 tagged_above=-999 required=5 tests=[AWL=0.608, 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 E6Pmd6A+mXpA; Thu, 24 Oct 2013 11:32:53 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7A50211E81D1; Thu, 24 Oct 2013 11:32:46 -0700 (PDT)
X-AuditID: c1b4fb25-b7eff8e000000eda-4b-526967cd28c6
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id CC.90.03802.DC769625; Thu, 24 Oct 2013 20:32:45 +0200 (CEST)
Received: from [131.160.126.161] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.65) with Microsoft SMTP Server id 14.2.328.9; Thu, 24 Oct 2013 20:32:44 +0200
Message-ID: <526967CC.4050706@ericsson.com>
Date: Thu, 24 Oct 2013 21:32:44 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Gen-ART review of draft-ietf-siprec-architecture-08
References: <D9D05CBD-95E0-4CB1-99AF-53AA6E0EAA1D@vigilsec.com> <9F33F40F6F2CD847824537F3C4E37DDF17BF97F7@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BF97F7@MCHP04MSX.global-ad.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUyM+Jvje7Z9Mwgg/adShbbNpRaXO98w2Jx 9dVnFotXL26yWzzbOJ/FgdVjyZKfTB5fLn9m89je85jFY9WdL6wBLFFcNimpOZllqUX6dglc GTOPNLIXHJep+HkgrIHxoFgXIyeHhICJxOQbh9ggbDGJC/fWA9lcHEIChxklXl+YDeWsZZT4 sqqBFaSKV0Bb4t67ncwgNouAqsSGg+8ZQWw2AQuJLbfus4DYogJREhu2X2CBqBeUODnzCZgt IqAu8Xf+BXaQocwCTxklnk//ApYQFnCQOLTsIiPEtiZGiR1b1jCBJDgF/CUer+xihrhPUmLL i3Z2EJtZQE9iytUWRghbXmL72zlgNUJA1y1/1sIygVFoFpLls5C0zELSsoCReRUje25iZk56 udEmRmB4H9zyW3UH451zIocYpTlYlMR5P7x1DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXA 6Mjit67wjJN/4N3JrMXXnEyfmVomB718tiZbKehXCtPM+fIMIt0Xjdfstd/A482TpaVU96Tg rMzMCqe2o0zPm2YvXbzDz8ysr+axj2NA78Td6+fMPp82+WnlQoby/5Ms7VNPqTRfe6pvK955 87gc3+U1eV9iNyy8x3Q40vbOlz3LFZqZm/YJK7EUZyQaajEXFScCAGYgugw9AgAA
Cc: "draft-ietf-siprec-architecture.all@tools.ietf.org" <draft-ietf-siprec-architecture.all@tools.ietf.org>, "gen-art@ietf.org" <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, 24 Oct 2013 18:33:01 -0000

Hi Russ,

could you please have a look at this new revision of the draft and let
the authors know whether or not it addresses your concerns?

Thanks,

Gonzalo

On 18/10/2013 1:59 PM, Hutton, Andrew wrote:
> Hi Russ,
> 
> An update to this draft has been posted and I believe it addresses your comments.
> 
> See http://www.ietf.org/internet-drafts/draft-ietf-siprec-architecture-09.txt 
> 
> Regards
> Andy
> 
> 
>> -----Original Message-----
>> From: Russ Housley [mailto:housley@vigilsec.com]
>> Sent: 23 September 2013 23:00
>> To: draft-ietf-siprec-architecture.all@tools.ietf.org
>> Cc: gen-art@ietf.org; ietf@ietf.org
>> Subject: Gen-ART review of draft-ietf-siprec-architecture-08
>>
>> 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-siprec-architecture-08
>> Reviewer: Russ Housley
>> Review Date: 2013-09-23
>> IETF LC End Date: 2013-10-01
>> IESG Telechat date: Unknown
>>
>> Summary:
>>
>> Major Concerns:
>>
>> The use of "required" in Section 3.2.4 is confusing to me.  It says:
>>
>>    In a basic session involving only audio there are typically two
>> audio
>>    /RTP streams between the two UAs involved transporting media in each
>>    direction.  When recording this media the two streams may be mixed
>> at
>>    the SRC before being transmitted to the SRS or it may be required
>>    that the media streams are not mixed and are sent to the SRS as two
>>    separate streams.
>>
>> Is this a requirement that the SRC imposes on the SRS?  Please clarify.
>>
>>
>> Minor Concerns:
>>
>> The definitions include:
>>
>>    Recording unaware User Agent (UA): A SIP User Agent that is unaware
>>    of SIP extensions associated with the Communication Session.  Such
>>    Recording unaware UA will be notified that a session is being
>>    recorded or express preferences as to whether a recording should be
>>    started, paused, resumed or stopped via some other means that is out
>>    of scope of SIPREC.
>>
>> There is no definition of SIPREC.  Perhaps it could simply say:
>>
>>    ... is out of scope for the SIP media recording architecture.
>>
>> Note that "SIPREC" does occur a few other places in the document, and
>> this approach to the replacement seems to work for them too.
>>
>> Of course, the alternative it to define SIPREC.
>>
>>
>> Section 5 talks about encryption of the media stream, but it does not
>> offer any suggestions about the protection of the stored media.  I
>> doubt that there is a simple bit of advice, but implementers should
>> be warned against strong protection of the media during transmission
>> and then providing no protection to the stored media.
>>
>>
>> Other Comments:
>>
>> The introduction defines these two acronyms: Session Recording
>> Client (SRC) and the Session Recording Server (SRS).  However, they are
>> spelled out many times throughout the introduction.  These acronyms are
>> not really used until after the definitions section.  I suggest using
>> them throughout the document.
>>
>>
>> There is a period missing at the end of the first sentence in
>> Section 3.1.2.
>>
>> In Section 	3.2.2, it says:
>>
>>    o Identifies the sessions that is to be recorded. ...
>>
>> This should say "sessions that are to be recorded".
>>
>>
>> There is a period missing at the end of the last bullet in
>> Section 3.2.2.
>>
> 
> 
> 


From john-ietf@jck.com  Thu Oct 24 12:20:31 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 8A95611E8346; Thu, 24 Oct 2013 12:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.55
X-Spam-Level: 
X-Spam-Status: No, score=-103.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 j3OuXWkA+d0Y; Thu, 24 Oct 2013 12:20:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4474E11E810B; Thu, 24 Oct 2013 12:20:10 -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 1VZQS0-0007q4-HW; Thu, 24 Oct 2013 15:20:08 -0400
Date: Thu, 24 Oct 2013 15:20:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [IETF] Re: NOMCOM - Critical shortage of nominees for multiple	areas
Message-ID: <F0D33337967612E19FAAD38A@JcK-HP8200.jck.com>
In-Reply-To: <201310241816.r9OIGsWe020534@cichlid.raleigh.ibm.com>
References: <20131017142434.21877.63746.idtracker@ietfa.amsl.com> <E4DE949E6CE3E34993A2FF8AE79131F81CAB89@DEMUMBX005.nsn-intra.net> <F5063677821E3B4F81ACFB7905573F24049E8BCC28@MX15A.corp.emc.com> <CAP8yD=uY=g-HeHt8HG9CLyDiprE5aJgA5nY9WWOOhrE2edNvbg@mail.gmail.com> <5262D202.1020501@ieca.com> <58078580-C20F-4257-8915-9E37350B320E@kumari.net> <201310241816.r9OIGsWe020534@cichlid.raleigh.ibm.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, nomcom13@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Oct 2013 19:20:31 -0000

--On Thursday, October 24, 2013 14:16 -0400 Thomas Narten
<narten@us.ibm.com> wrote:

> Going back to something said earlier. While I understand that
> it may be good for the nomcom/ietf to develop a list of
> alternate candidates even if the incumbent is strong, just for
> backup, etc., there is a flip side as well.
> 
> Applying takes time. The survey isn't exactly short, and going
> through the motions to get internal support can also take
> time. And for someone who has applied and is waiting the
> results, they may find themselves in an awkward position
> w.r.t. planning future work activities (will they have time to
> take on new activities or will the nomcom select them?).
> 
> All this uses resources that arguably could be spent more
> productively, e.g., doing WG work.

Not only that, but if someone has to cause an
intra-organizational fuss to get permission to volunteer for a
position that is later filled by an incumbent who turned out to
be (or appear like) a foregone conclusion, it may be much harder
to get permission later.  The "awkward position" you mention
above may apply not only to the potential candidate but her
management and organization.

> I think it's fine to say no to the nomcom and say something
> like "incumbent is doing a great job and nomcom should not
> waste folks' time beating the bushes to build up a list when
> there is no compelling reason not to just quickly reup the
> incumbent.

It seems to me that it might even be reasonable to tell the
Nomcom "incumbent is doing a great job ... but, should the
incumbent withdraw or otherwise be inappropriate, I am
reasonably sure I can get permission to volunteer within a
reasonable time after you ask" (and not spend time filling out
questionnaires, etc., unless that situation develops).
 
Of course, if it were public which incumbents were hoping to be
re-upped and which ones were not (an occasional public "I'm not
going to do it again" note notwithstanding), it would help
considerably with the approaches both of us have suggested...
and reduce the odds of a last-minute scramble somewhat.

best,
   john



From fluffy@iii.ca  Thu Oct 24 22:57:40 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 3032911E82B1; Thu, 24 Oct 2013 22:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=-0.025, 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 wyxYlUOSpOgs; Thu, 24 Oct 2013 22:57:33 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4C64511E82B0; Thu, 24 Oct 2013 22:57:31 -0700 (PDT)
Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7CABF22E2C9; Fri, 25 Oct 2013 01:57:24 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com>
Date: Thu, 24 Oct 2013 23:57:22 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca> <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: dhcwg@ietf.org, "ietf@ietf.org Discuss" <ietf@ietf.org>, The 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: Fri, 25 Oct 2013 05:57:40 -0000

On Oct 22, 2013, at 12:55 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> (c) This document is saying what the DHC working group recommends.   =
RAI working groups are free to go against these recommendations.   So =
this document shouldn't say what RAI recommends.   It should say what =
DHC recommends.   If a working group doesn't want to follow the advice, =
they don't have to, because it's just advice, not a requirement.

Ted, as an IESG member, are you really sticking to a that the meaning of =
a BCP?



From daedulus@btconnect.com  Fri Oct 25 02:03:01 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 C538C11E82FC for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.243
X-Spam-Level: 
X-Spam-Status: No, score=-5.243 tagged_above=-999 required=5 tests=[AWL=1.356,  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 Z39Q-O9Lsc43 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:02:56 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB2811E8305 for <ietf@ietf.org>; Fri, 25 Oct 2013 02:02:49 -0700 (PDT)
Received: from mail22-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.22; Fri, 25 Oct 2013 09:02:48 +0000
Received: from mail22-tx2 (localhost [127.0.0.1])	by mail22-tx2-R.bigfish.com (Postfix) with ESMTP id 8FCD5420183	for <ietf@ietf.org>; Fri, 25 Oct 2013 09:02:48 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(z54eehz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail22-tx2 (localhost.localdomain [127.0.0.1]) by mail22-tx2 (MessageSwitch) id 1382691729434927_18671; Fri, 25 Oct 2013 09:02:09 +0000 (UTC)
Received: from TX2EHSMHS011.bigfish.com (unknown [10.9.14.235])	by mail22-tx2.bigfish.com (Postfix) with ESMTP id 58ED8260170	for <ietf@ietf.org>; Fri, 25 Oct 2013 09:02:09 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by TX2EHSMHS011.bigfish.com (10.9.99.111) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 25 Oct 2013 09:02:09 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 25 Oct 2013 09:02:01 +0000
Message-ID: <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ietf <ietf@ietf.org>
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
Date: Fri, 25 Oct 2013 09:54:05 +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.254.85]
X-OriginatorOrg: btconnect.com
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: Fri, 25 Oct 2013 09:03:01 -0000

I see that we have been granted a fortnight to review eight,
inter-related, httpbis I-Ds, comprising over 300 pages, ending in the
course of IETF88 and in the run-up to a meeting when everyone comes out
of aestivation and the mailing lists are inundated.

Seems like a DoS attack to me.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <ietf-http-wg@w3.org>
Sent: Monday, October 21, 2013 2:25 PM
Subject: Last Call:
<draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext
Transfer Protocol (HTTP) AuthenticationScheme Registrations) to
Informational RFC


>
> The IESG has received a request from the Hypertext Transfer Protocol
Bis
> WG (httpbis) to consider the following document:
> - 'Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme
>    Registrations'
>   <draft-ietf-httpbis-authscheme-registrations-08.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-11-04. 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 registers Hypertext Transfer Protocol (HTTP)
>    authentication schemes which have been defined in standards-track
>    RFCs before the IANA HTTP Authentication Scheme Registry was
>    established.
>
>
> Note that this document is part of a set, which should be reviewed
together:
>
> * draft-ietf-httpbis-p1-messaging
> * draft-ietf-httpbis-p2-semantics
> * draft-ietf-httpbis-p4-conditional
> * draft-ietf-httpbis-p5-range
> * draft-ietf-httpbis-p6-cache
> * draft-ietf-httpbis-p7-auth
> * draft-ietf-httpbis-method-registrations
> * draft-ietf-httpbis-authscheme-registrations
>
> The file can be obtained via
>
http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrati
ons/
>
> Once IESG evaluation begins, IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrati
ons/ballot/
>
> No IPR declarations have been submitted directly on this I-D.
>



From abdussalambaryun@gmail.com  Fri Oct 25 02:17:12 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 467DF11E8396 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  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 YnmYXEqIj9KY for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:17:08 -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 4A52111E839B for <ietf@ietf.org>; Fri, 25 Oct 2013 02:17:00 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up7so3223427pbc.40 for <ietf@ietf.org>; Fri, 25 Oct 2013 02:17:00 -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=WnoxSpw3UYwc9yWkqQGQOgeCX4DYMuaAL4SrpIZo7EE=; b=VhBB8RHiKulTk+wsHZ1NoDPb4spYMCwJ45EW7/7xADGQuDyfn0B72hCHUenDWPKazB 2gLWf931Y8a1QNcjpQAiZrBBl2LWAZ/NRwB+TLVrridzPBm04rngKndI+3b+w7q7EEsA wZdlOWnTGcfTzEGN5SszNLkrnSEEDNJzWz+mNftuXsqm3jHmK1MZlttyyRmcsVanwfrN QHjrmbgqX0J12XOFY9sF/UAGYOI/nhte+uQsMtwX+wD3fOo5LLr0wwt51XxXrxHBp9gP oYgsiT0NHktYJl+FWoMA2O2iE7lMdKm2IgnBdGMBH64nHhRIhwc/fpLrBNU1TEykuVqw cI+Q==
MIME-Version: 1.0
X-Received: by 10.68.254.132 with SMTP id ai4mr5841452pbd.51.1382692619937; Fri, 25 Oct 2013 02:16:59 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Fri, 25 Oct 2013 02:16:59 -0700 (PDT)
In-Reply-To: <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com> <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
Date: Fri, 25 Oct 2013 10:16:59 +0100
Message-ID: <CADnDZ89Ayfg=gCC1YSW-3DrusOUobp-M+C2shUYZoNbhW-05dA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=047d7b2e0a1171ef7104e98d367c
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, 25 Oct 2013 09:17:12 -0000

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

The LC review will be very weak in terms of quality if we often do this
kind of calls (it seems not often done), but I think if reviewers that want
to review these drafts, send comments saying we need more time for such LC,
there is always the AD responsibility to make more time available if there
were people to do the job. Delaying I-Ds also is not a good process quality
while we see no much volunteering reviews from the community (less than 5
reviews per I-D). So do you mean you will want to review or you mean that
others MAY want to review but they will leave it, so this LC is attacking.

AB


On Fri, Oct 25, 2013 at 9:54 AM, t.p. <daedulus@btconnect.com> wrote:

> I see that we have been granted a fortnight to review eight,
> inter-related, httpbis I-Ds, comprising over 300 pages, ending in the
> course of IETF88 and in the run-up to a meeting when everyone comes out
> of aestivation and the mailing lists are inundated.
>
> Seems like a DoS attack to me.
>
> Tom Petch
>
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: <ietf-http-wg@w3.org>
> Sent: Monday, October 21, 2013 2:25 PM
> Subject: Last Call:
> <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext
> Transfer Protocol (HTTP) AuthenticationScheme Registrations) to
> Informational RFC
>
>
> >
> > The IESG has received a request from the Hypertext Transfer Protocol
> Bis
> > WG (httpbis) to consider the following document:
> > - 'Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme
> >    Registrations'
> >   <draft-ietf-httpbis-authscheme-registrations-08.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-11-04. 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 registers Hypertext Transfer Protocol (HTTP)
> >    authentication schemes which have been defined in standards-track
> >    RFCs before the IANA HTTP Authentication Scheme Registry was
> >    established.
> >
> >
> > Note that this document is part of a set, which should be reviewed
> together:
> >
> > * draft-ietf-httpbis-p1-messaging
> > * draft-ietf-httpbis-p2-semantics
> > * draft-ietf-httpbis-p4-conditional
> > * draft-ietf-httpbis-p5-range
> > * draft-ietf-httpbis-p6-cache
> > * draft-ietf-httpbis-p7-auth
> > * draft-ietf-httpbis-method-registrations
> > * draft-ietf-httpbis-authscheme-registrations
> >
> > The file can be obtained via
> >
> http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrati
> ons/<http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrations/>
> >
> > Once IESG evaluation begins, IESG discussion can be tracked via
> >
> http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrati
> ons/ballot/<http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-registrations/ballot/>
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
>
>
>

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

<div dir=3D"ltr"><div>The LC review will be very weak in terms of quality i=
f we often do this kind of calls (it seems not often done), but I think if =
reviewers that want to review these drafts, send=A0comments saying we need =
more time for such LC, there is always the AD responsibility to make more t=
ime available if there were people to do the job. Delaying I-Ds also is not=
 a good process quality while we see no much volunteering reviews from the =
community (less than 5 reviews per I-D). So do you mean you will want to re=
view or you mean that others MAY want to review but they will leave it, so =
this LC is attacking.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Oct 25, 2013 at 9:54 AM, t.p. <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:daedulus@btconnect.com" target=3D"_blank">daedulus@b=
tconnect.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">I see that we have been granted a fortnight =
to review eight,<br>
inter-related, httpbis I-Ds, comprising over 300 pages, ending in the<br>
course of IETF88 and in the run-up to a meeting when everyone comes out<br>
of aestivation and the mailing lists are inundated.<br>
<br>
Seems like a DoS attack to me.<br>
<br>
Tom Petch<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
----- Original Message -----<br>
From: &quot;The IESG&quot; &lt;<a href=3D"mailto:iesg-secretary@ietf.org">i=
esg-secretary@ietf.org</a>&gt;<br>
To: &quot;IETF-Announce&quot; &lt;<a href=3D"mailto:ietf-announce@ietf.org"=
>ietf-announce@ietf.org</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:ietf-http-wg@w3.org">ietf-http-wg@w3.org</a>&gt;<=
br>
Sent: Monday, October 21, 2013 2:25 PM<br>
Subject: Last Call:<br>
&lt;draft-ietf-httpbis-authscheme-registrations-08.txt&gt;(Initial Hypertex=
t<br>
Transfer Protocol (HTTP) AuthenticationScheme Registrations) to<br>
Informational RFC<br>
<br>
<br>
&gt;<br>
&gt; The IESG has received a request from the Hypertext Transfer Protocol<b=
r>
Bis<br>
&gt; WG (httpbis) to consider the following document:<br>
&gt; - &#39;Initial Hypertext Transfer Protocol (HTTP) Authentication Schem=
e<br>
&gt; =A0 =A0Registrations&#39;<br>
&gt; =A0 &lt;draft-ietf-httpbis-authscheme-registrations-08.txt&gt; as<br>
Informational<br>
&gt; RFC<br>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
13-11-04. Exceptionally, comments may<br>
be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In=
 either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0This document registers Hypertext Transfer Protocol (HTTP)<br>
&gt; =A0 =A0authentication schemes which have been defined in standards-tra=
ck<br>
&gt; =A0 =A0RFCs before the IANA HTTP Authentication Scheme Registry was<br=
>
&gt; =A0 =A0established.<br>
&gt;<br>
&gt;<br>
&gt; Note that this document is part of a set, which should be reviewed<br>
together:<br>
&gt;<br>
&gt; * draft-ietf-httpbis-p1-messaging<br>
&gt; * draft-ietf-httpbis-p2-semantics<br>
&gt; * draft-ietf-httpbis-p4-conditional<br>
&gt; * draft-ietf-httpbis-p5-range<br>
&gt; * draft-ietf-httpbis-p6-cache<br>
&gt; * draft-ietf-httpbis-p7-auth<br>
&gt; * draft-ietf-httpbis-method-registrations<br>
&gt; * draft-ietf-httpbis-authscheme-registrations<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt;<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-re=
gistrations/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-=
httpbis-authscheme-registrati<br>
ons/</a><br>
&gt;<br>
&gt; Once IESG evaluation begins, IESG discussion can be tracked via<br>
&gt;<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-httpbis-authscheme-re=
gistrations/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draf=
t-ietf-httpbis-authscheme-registrati<br>
ons/ballot/</a><br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--047d7b2e0a1171ef7104e98d367c--

From chair@ietf.org  Fri Oct 25 02:21:50 2013
Return-Path: <chair@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 C007711E8398 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:21: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 M-5ZX04t3dcI for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 02:21:50 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 2637B11E82BA for <ietf@ietf.org>; Fri, 25 Oct 2013 02:21:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id E6E98A619C; Fri, 25 Oct 2013 02:20:05 -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 7lrETrX8L6Kh; Fri, 25 Oct 2013 02:20:05 -0700 (PDT)
Received: from dynamic-37-19-igf2013.apnic.net (unknown [203.83.37.19]) by c9a.amsl.com (Postfix) with ESMTPSA id 92618A614F; Fri, 25 Oct 2013 02:19:54 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IGOVUPDATE session
Date: Fri, 25 Oct 2013 17:21:31 +0800
Message-Id: <501C806C-B95C-4604-8C7E-BDE297E554A6@ietf.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Cc: Andrew Sullivan <ajs@crankycanuck.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: Fri, 25 Oct 2013 09:21:51 -0000

In Orlando, the IAB held a session on what had been going at WCIT. While =
this was not a matter of technical work for the IETF, we all did =
recognise the impact of policies, treaties, and governance structures on =
the Internet. The feedback from the session was positive, and I have =
asked the IAB to arrange similar sessions in some upcoming meetings when =
and if there is interesting issues to hear about.

In Vancouver we have reserved a slot for "IGOVUPDATE". We had originally =
planned the topic for this time to be DNS-related policy issues, largely =
from the areas where IETF and ICANN efforts meet. However, since then =
there has been many developments and proposals in the Internet =
governance space, I think largely inspired by the recent revelations on =
pervasive monitoring. Or enabled by the discussion climate caused by =
them.

With this in mind, we'll begin the session by talking about WHOIS/WEIRDS =
and how policies discussed around them may affect the protocol design. =
But after that we will also provide a report from the IGF (Internet =
Governance Forum) meeting that is being held this week. And finally, =
discuss whether additional work is needed and if so, how that might be =
organised.

The agenda for the meeting is at =
http://www.ietf.org/proceedings/88/agenda/agenda-88-igovupdate and the =
chairs of the session are Marc Blanchet and Andrew Sullivan.

Jari


From Ted.Lemon@nominum.com  Fri Oct 25 04:04: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 C88FC11E8387; Fri, 25 Oct 2013 04:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level: 
X-Spam-Status: No, score=-106.589 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 LYIUFag65hW0; Fri, 25 Oct 2013 04:04:06 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id F0C8D11E80F8; Fri, 25 Oct 2013 04:04:05 -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 DSNKUmpQJS6+MqwzC2Em+A70QsW7IQH5eByP@postini.com; Fri, 25 Oct 2013 04:04: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 70A7AF800A; Fri, 25 Oct 2013 04:04:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 503EA190060; Fri, 25 Oct 2013 04:04:05 -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.03.0158.001; Fri, 25 Oct 2013 04:04:05 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Cullen Jennings <fluffy@iii.ca>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
Thread-Index: AQHOxG6vvYfRrCcaWUK4N3Cm629TPZns9HaA///CyYCAAGBrgP//wqiAgACIuQD///LeAAANvZ8AAAxP5AACbNgWAAAB/XiAAHuzzQAACrXQAA==
Date: Fri, 25 Oct 2013 11:04:05 +0000
Message-ID: <A4943223-ADA7-4C3E-BF18-39756F673DB3@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca> <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com> <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca>
In-Reply-To: <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca>
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: <9C122D80633319488AB4EEC497A016FC@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "ietf@ietf.org Discuss" <ietf@ietf.org>, The 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: Fri, 25 Oct 2013 11:04:12 -0000

On Oct 25, 2013, at 1:57 AM, Cullen Jennings <fluffy@iii.ca> wrote:
> Ted, as an IESG member, are you really sticking to a that the meaning of =
a BCP?

Working groups are where IETF consensus comes from.   The IETF mailing list=
 review is there to see if the IETF disagrees with the working group consen=
sus.   I'm trying to explain to you, the only (late) dissenter in the IETF =
last call, why I think the IETF should have consensus to publish the DHC wo=
rking group's advice about how to implement DHCP options as a BCP.   I'm do=
ing this because I think that it is the right thing.   If you think it's th=
e wrong thing, at least do me the courtesy of walking me through your reaso=
ning.

Can you make a clear argument for why some RAI working group, and not the D=
HC working group, should be the one to offer advice on how to do DHCP optio=
ns?   Would you, for example, want sipping to be where advice on how to do =
new DNS RRtypes comes from?


From narten@us.ibm.com  Fri Oct 25 05:05: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 5756011E83D1 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 05:05: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 4vs4D9PvQkt5 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 05:05:27 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1D411E8319 for <ietf@ietf.org>; Fri, 25 Oct 2013 05:05:20 -0700 (PDT)
Received: from /spool/local by e39.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, 25 Oct 2013 06:05:20 -0600
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 25 Oct 2013 06:05:17 -0600
Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 0D33AC9003E for <ietf@ietf.org>; Fri, 25 Oct 2013 08:05:16 -0400 (EDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r9PC5GMn6095168 for <ietf@ietf.org>; Fri, 25 Oct 2013 12:05:16 GMT
Received: from d03av04.boulder.ibm.com (localhost [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r9PC5FRl028529 for <ietf@ietf.org>; Fri, 25 Oct 2013 06:05:16 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id r9PC5Em6028302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 25 Oct 2013 06:05:15 -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 r9PC5Din012295 for <ietf@ietf.org>; Fri, 25 Oct 2013 08:05:13 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r9PC5DPb012249 for ietf@ietf.org; Fri, 25 Oct 2013 08:05:13 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201310251205.r9PC5DPb012249@rotala.raleigh.ibm.com>
Date: Fri, 25 Oct 2013 08:05:13 -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: 13102512-9332-0000-0000-000001EC181C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 12:05:38 -0000

Total of 292 messages in the last 7 days.
 
script run at: Fri Oct 25 08:05:13 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.48% |   16 |  5.47% |   123271 | ted.lemon@nominum.com
  5.14% |   15 |  4.78% |   107832 | john-ietf@jck.com
  4.11% |   12 |  5.35% |   120597 | hallam@gmail.com
  3.77% |   11 |  5.42% |   122194 | abdussalambaryun@gmail.com
  4.11% |   12 |  3.38% |    76214 | melinda.shore@gmail.com
  3.77% |   11 |  3.24% |    73085 | dhc@dcrocker.net
  3.42% |   10 |  3.08% |    69576 | sm@resistor.net
  3.42% |   10 |  3.07% |    69142 | brian.e.carpenter@gmail.com
  2.40% |    7 |  3.47% |    78323 | andy@yumaworks.com
  2.74% |    8 |  2.12% |    47836 | jari.arkko@piuha.net
  2.40% |    7 |  2.38% |    53735 | scott.brim@gmail.com
  2.40% |    7 |  2.27% |    51138 | loa@pi.nu
  2.05% |    6 |  2.50% |    56296 | jeanjour@comcast.net
  2.05% |    6 |  1.71% |    38611 | mcr+ietf@sandelman.ca
  2.05% |    6 |  1.61% |    36329 | adrian@olddog.co.uk
  2.05% |    6 |  1.35% |    30454 | randy@psg.com
  1.71% |    5 |  1.52% |    34317 | tytso@mit.edu
  1.37% |    4 |  1.78% |    40250 | tjc@ecs.soton.ac.uk
  1.37% |    4 |  1.62% |    36555 | allison.mankin@gmail.com
  1.37% |    4 |  1.33% |    30045 | l.wood@surrey.ac.uk
  1.37% |    4 |  1.32% |    29757 | bclaise@cisco.com
  1.37% |    4 |  1.14% |    25669 | johnl@taugh.com
  1.37% |    4 |  1.06% |    23923 | hannes.tschofenig@gmx.net
  1.03% |    3 |  1.33% |    30092 | fluffy@iii.ca
  1.03% |    3 |  1.33% |    29978 | kathleen.moriarty@emc.com
  1.37% |    4 |  0.96% |    21677 | bortzmeyer@nic.fr
  1.03% |    3 |  1.27% |    28701 | narten@us.ibm.com
  1.03% |    3 |  1.22% |    27519 | fred@cisco.com
  1.03% |    3 |  1.15% |    26043 | daedulus@btconnect.com
  1.03% |    3 |  1.15% |    25980 | joelja@bogus.com
  1.03% |    3 |  1.10% |    24777 | ynir@checkpoint.com
  1.03% |    3 |  1.09% |    24543 | mars.techno.cat@gmail.com
  1.03% |    3 |  0.99% |    22378 | jabley@hopcount.ca
  1.03% |    3 |  0.95% |    21469 | jmh@joelhalpern.com
  1.03% |    3 |  0.94% |    21192 | barryleiba@computer.org
  1.03% |    3 |  0.94% |    21172 | warren@kumari.net
  1.03% |    3 |  0.88% |    19908 | randy_presuhn@mindspring.com
  1.03% |    3 |  0.85% |    19213 | michel@arneill-py.sacramento.ca.us
  0.68% |    2 |  1.11% |    24958 | harald@alvestrand.no
  1.03% |    3 |  0.75% |    16942 | ajs@anvilwalrusden.com
  1.03% |    3 |  0.74% |    16596 | mnot@mnot.net
  0.68% |    2 |  0.87% |    19650 | trammell@tik.ee.ethz.ch
  0.68% |    2 |  0.86% |    19399 | d3e3e3@gmail.com
  0.68% |    2 |  0.83% |    18778 | mary.h.barnes@gmail.com
  0.68% |    2 |  0.78% |    17530 | richard@shockey.us
  0.68% |    2 |  0.73% |    16482 | jordi.palet@consulintel.es
  0.68% |    2 |  0.72% |    16262 | jmamodio@gmail.com
  0.68% |    2 |  0.69% |    15631 | fluffy@cisco.com
  0.68% |    2 |  0.69% |    15572 | rogerj@gmail.com
  0.68% |    2 |  0.65% |    14696 | hgs@cs.columbia.edu
  0.68% |    2 |  0.64% |    14517 | derhoermi@gmx.net
  0.68% |    2 |  0.56% |    12740 | stephen.farrell@cs.tcd.ie
  0.68% |    2 |  0.47% |    10702 | mohta@necom830.hpcl.titech.ac.jp
  0.68% |    2 |  0.47% |    10659 | alexandru.petrescu@gmail.com
  0.34% |    1 |  0.67% |    15083 | ted.ietf@gmail.com
  0.34% |    1 |  0.60% |    13512 | turners@ieca.com
  0.34% |    1 |  0.58% |    13093 | spencerdawkins.ietf@gmail.com
  0.34% |    1 |  0.49% |    10943 | cdel@firsthand.net
  0.34% |    1 |  0.43% |     9777 | conte@isoc.org
  0.34% |    1 |  0.43% |     9766 | robert@raszuk.net
  0.34% |    1 |  0.41% |     9299 | gonzalo.camarillo@ericsson.com
  0.34% |    1 |  0.38% |     8652 | wes@mti-systems.com
  0.34% |    1 |  0.38% |     8550 | chair@ietf.org
  0.34% |    1 |  0.37% |     8334 | andrew.hutton@unify.com
  0.34% |    1 |  0.37% |     8240 | mehmet.ersue@nsn.com
  0.34% |    1 |  0.36% |     8150 | lear@cisco.com
  0.34% |    1 |  0.34% |     7723 | john@jlc.net
  0.34% |    1 |  0.33% |     7432 | huitema@microsoft.com
  0.34% |    1 |  0.32% |     7278 | alexey.melnikov@isode.com
  0.34% |    1 |  0.32% |     7197 | framefritti@gmail.com
  0.34% |    1 |  0.30% |     6862 | lars@netapp.com
  0.34% |    1 |  0.29% |     6616 | housley@vigilsec.com
  0.34% |    1 |  0.29% |     6579 | doug.mtview@gmail.com
  0.34% |    1 |  0.29% |     6539 | cja@daydream.com
  0.34% |    1 |  0.29% |     6474 | jruohonen@iki.fi
  0.34% |    1 |  0.28% |     6363 | jelte.jansen@sidn.nl
  0.34% |    1 |  0.28% |     6324 | lixia@cs.ucla.edu
  0.34% |    1 |  0.28% |     6233 | cabo@tzi.org
  0.34% |    1 |  0.27% |     6186 | martin.vigoureux@alcatel-lucent.com
  0.34% |    1 |  0.27% |     6096 | mansaxel@besserwisser.org
  0.34% |    1 |  0.26% |     5900 | ben@nostrum.com
  0.34% |    1 |  0.25% |     5688 | rsk@gsp.org
  0.34% |    1 |  0.25% |     5598 | jason_livingood@cable.comcast.com
  0.34% |    1 |  0.23% |     5268 | envite@rolamasao.org
  0.34% |    1 |  0.23% |     5087 | peter@akayla.com
  0.34% |    1 |  0.22% |     4981 | jnc@mercury.lcs.mit.edu
  0.34% |    1 |  0.21% |     4805 | ietf-secretariat@ietf.org
--------+------+--------+----------+------------------------
100.00% |  292 |100.00% |  2255533 | Total


From barryleiba@gmail.com  Fri Oct 25 08:36:24 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 C589011E818E; Fri, 25 Oct 2013 08:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.968
X-Spam-Level: 
X-Spam-Status: No, score=-101.968 tagged_above=-999 required=5 tests=[AWL=0.010, 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 e3+eBinE4ioS; Fri, 25 Oct 2013 08:36:23 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id D6F6D11E819B; Fri, 25 Oct 2013 08:36:14 -0700 (PDT)
Received: by mail-qc0-f169.google.com with SMTP id x12so2318891qcv.0 for <multiple recipients>; Fri, 25 Oct 2013 08:36:10 -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:message-id:subject :from:to:cc:content-type; bh=gfT44Qn0ZTBcExal0hG8XrNz/AXNcqEOROLxsWbPN5M=; b=rqMx21OMCADixCWo9ccjQgzEpE1L/sw5dD0ocMI+Ma5uuwaN6Bosa554n4fGTBIB1n C1GZeK4GAgAYB79W6Av0RwNs0i5PwCquk6PHzQ6wVPU4T5mgze0VA3NwUyV9wEBHe6xS GXOulRrZAOD0jSiUOxmm9H0E3jh3QxQAY+Fb5FKuM3QL7nVYAf30Zv9b+Abm455LoLai cqXLbPeCWc4XEwcrRVCVVgKSrvLfNbIt3C/dCeOOiEMVQuAA+K626C4M0dggAPRrk1+Q YDYhQPZ+/Ed3K7jph8eq4UiDEAa5NVfGdT1vu+ZMJaJyuhr2+zPAd8kHQUWgOLXsNa0d /fBg==
MIME-Version: 1.0
X-Received: by 10.49.127.179 with SMTP id nh19mr11360766qeb.1.1382715370622; Fri, 25 Oct 2013 08:36:10 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.67.130 with HTTP; Fri, 25 Oct 2013 08:36:10 -0700 (PDT)
In-Reply-To: <A4943223-ADA7-4C3E-BF18-39756F673DB3@nominum.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca> <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com> <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca> <A4943223-ADA7-4C3E-BF18-39756F673DB3@nominum.com>
Date: Fri, 25 Oct 2013 11:36:10 -0400
X-Google-Sender-Auth: 1H6CfcFaLkFVXmJAmMwkEjICD3g
Message-ID: <CALaySJJR+XXbPGtzXEAOZKNTSy_HZFh6neGUiamjPay=J1W5pQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
From: Barry Leiba <barryleiba@computer.org>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "ietf@ietf.org Discuss" <ietf@ietf.org>, Cullen Jennings <fluffy@iii.ca>, The 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: Fri, 25 Oct 2013 15:36:24 -0000

>> Ted, as an IESG member, are you really sticking to a that the meaning of a BCP?
>
> Working groups are where IETF consensus comes from.   The IETF mailing
> list review is there to see if the IETF disagrees with the working
> group consensus.   I'm trying to explain to you, the only (late)
> dissenter in the IETF last call, why I think the IETF should have
> consensus to publish the DHC working group's advice about how to
> implement DHCP options as a BCP.   I'm doing this because I think that
> it is the right thing.   If you think it's the wrong thing, at least
> do me the courtesy of walking me through your reasoning.
>
> Can you make a clear argument for why some RAI working group, and not
> the DHC working group, should be the one to offer advice on how to do
> DHCP options?   Would you, for example, want sipping to be where
> advice on how to do new DNS RRtypes comes from?

Really, now, this is over the top.

First, BCPs have IETF consensus, and are applicable across the IETF.
When you said that "RAI working groups are free to go against these
recommendations," you were completely wrong, and the IESG should and
would slap them down if they did.

Second, anyone who participates in the IETF can bring up issues, as
IETF consensus is built.  The output of working groups doesn't have
any magical force field protecting it from challenges from others.
The working group consensus means a lot, of course, but reasonable and
reasoned arguments still have to be addressed.

Third, your second paragraph above is really out of line.  So let's
back away a bit and look at the picture we're painting.

No one has tried to say that some other working group should be
telling people how to use DHCP.

What several of us have said, and what Cullen is saying, is that
various protocols (including some in the RAI area) are using DHCP to
get their configuration information.  Nothing theoretical: they ARE.
And that use has already been approved with IETF consensus.  So IF the
DHC working group means to say that such use by those protocols in
that way is ill advised, it needs to be explicitly clear about that,
and the issue needs to be discussed and have IETF consensus.
Otherwise, the document's recommendations need to be clarified to say
that this is legitimately done to configure application-layer
protocols, and different recommendations may apply to those.  Ideally,
it would give those recommendations as well.

So, one or the other:
- say "don't do that; it's bad, and here's why," *and get IETF
consensus on that*, or
- say "different recommendations apply in those situations, and here
are those recommendations," *and get IETF consensus on that*.

Barry

From martin.thomson@gmail.com  Fri Oct 25 09:59:24 2013
Return-Path: <martin.thomson@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 720A621E808E for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 09:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.064,  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 0qKLtTCW9t5f for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 09:59:24 -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 BBF3E21E80C1 for <ietf@ietf.org>; Fri, 25 Oct 2013 09:59:20 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hn9so1441191wib.5 for <ietf@ietf.org>; Fri, 25 Oct 2013 09:59:19 -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=K/vUvBfNQx5nVlDBw/V1P7BuYZ1u3mzrRoC5i/tedvY=; b=Mz65txecfpMxtEVIBcFH8K+b2e0hfGcnIyMIJoJ+a6WLQcgvhfXruLe37haiY3qegw 2HPLjiZxgyVLS75aw9K0OUA05sF+CG3E9M8VwuwNM7Rb8eyUvF4ptv2R8/dfmMqza+z8 KVY6+AlGmPjQ5nyQzqY4WNmiTPTVMUTeuZkJy49RqnoEqMKPjhiXPB6eVQfvpL9AAlQb M09+Ecdi+FT9XbUXwBx0AW1BCtv12ms6z2o/v4YEXBa1PSQqy46nSLj035yXIoILXr0G NbuBEdgMpdAZX4jkhRI6YQeXrOYOKy3I0AKCCpjx2YY+PP44aZ0kos1iPFk+AFTQw6iP /iNQ==
MIME-Version: 1.0
X-Received: by 10.180.86.104 with SMTP id o8mr3356896wiz.64.1382720359740; Fri, 25 Oct 2013 09:59:19 -0700 (PDT)
Received: by 10.227.202.194 with HTTP; Fri, 25 Oct 2013 09:59:19 -0700 (PDT)
In-Reply-To: <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com> <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
Date: Fri, 25 Oct 2013 09:59:19 -0700
Message-ID: <CABkgnnWzVB4mGmaZhaZkQX23FoD3GQbGmC7Phu1QSjfazayAqw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
From: Martin Thomson <martin.thomson@gmail.com>
To: "t.p." <daedulus@btconnect.com>, Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
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, 25 Oct 2013 16:59:24 -0000

On 25 October 2013 01:54, t.p. <daedulus@btconnect.com> wrote:
> I see that we have been granted a fortnight to review eight,
> inter-related, httpbis I-Ds, comprising over 300 pages, ending in the
> course of IETF88 and in the run-up to a meeting when everyone comes out
> of aestivation and the mailing lists are inundated.

It's not like this work hasn't been in progress for about a decade
already.  Though I do recall discussing a 4 week LC period at the last
meeting.  Barry?

From ned+ietf@mauve.mrochek.com  Fri Oct 25 10:01:21 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 257C011E8359 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 10:01: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 bM1osMgSpffQ for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 10:01:11 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1FC11E8201 for <ietf@ietf.org>; Fri, 25 Oct 2013 10:01:08 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OZZW7U8G9S006K3A@mauve.mrochek.com> for ietf@ietf.org; Fri, 25 Oct 2013 09:56:06 -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 <01OZQXEDTQ3400004R@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 25 Oct 2013 09:56:03 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OZZW7T12OY00004R@mauve.mrochek.com>
Date: Fri, 25 Oct 2013 09:53:34 -0700 (PDT)
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-reply-to: "Your message dated Wed, 23 Oct 2013 17:43:02 +0200" <m28uxkyovt.wl%randy@psg.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
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: Fri, 25 Oct 2013 17:01:21 -0000

> the chilling effect of vigilateism is far worse than spam or trolls.
> we've been dealing with the latter for decades, and there is little
> actual real harm if any.  the chilling effect of vigilanteism causes
> actual harm and reduces the rich diversity of opinion, culture, and
> viewpoint.

I could not agree more. By condoning such measures people are damaging the
diversity they are supposedly trying to support.

				Ned

From sm@resistor.net  Fri Oct 25 10:33: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 CCB0011E81B6; Fri, 25 Oct 2013 10:33:40 -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 t22FaPaCu1B2; Fri, 25 Oct 2013 10:33:39 -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 1A11311E819F; Fri, 25 Oct 2013 10:33:39 -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 r9PHXXJs012554; Fri, 25 Oct 2013 10:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382722418; bh=2Wkhy77LY9rFbF4koa1tfjCvm84er36cGWsVSMdZ21Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HCC076MAUgaNEBby5IPbFHhsJ6I6bYHEE86x4dJXdDKlZgK6di3K7hAxq6ge16lT1 oHRzM0CORbJvWKxfgsRod70QAVY+YP5XcDY/NHsrVnNKCLzmyRm4MuZtw9BiLq6WRW QRn4p9oPhWbjE6Ld52aZvloUYjQnRBWeguzQ7xZM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382722418; i=@resistor.net; bh=2Wkhy77LY9rFbF4koa1tfjCvm84er36cGWsVSMdZ21Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=r7hE+4DTMs6bAG3SDzMfIUaYDgDl5KsEjEq4GTkS7AW80d0vHxWdCUUu4f5QKDisq hPSsqawtjHT/fpY3CrgC9Hg/1NB0Ncukqn0PF7MjU4vpjkQHFgVYEzfGXKeQjw2WCB H9Txnfyh8OsgIvnFDhxcKQymj2Bnmb2u8hToUR0g=
Message-Id: <6.2.5.6.2.20131025092401.0d13fed0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 25 Oct 2013 10:32:26 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
In-Reply-To: <CALaySJJR+XXbPGtzXEAOZKNTSy_HZFh6neGUiamjPay=J1W5pQ@mail.g mail.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca> <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com> <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca> <A4943223-ADA7-4C3E-BF18-39756F673DB3@nominum.com> <CALaySJJR+XXbPGtzXEAOZKNTSy_HZFh6neGUiamjPay=J1W5pQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: dhcwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 17:33:41 -0000

Hello,

I took a quick look at draft-ietf-dhc-option-guidelines-14.  In Section 8:

   "FQDN imposes a number of additional failure modes and issues that
    should be dealt with:

    1.  The client must have a knowledge about available DNS servers.
        That typically means that option DNS_SERVERS is mandatory.  This
        should be mentioned in the draft that defines new option.  It is
        possible that the server will return FQDN option, but not the DNS
        Servers option.  There should be a brief discussion about it;

    2.  The DNS may not be reachable;

    3.  DNS may be available, but may not have appropriate information
        (e.g. no AAAA records for specified FQDN);"

The draft recommends using IP addresses unless there is a good reason 
to use an FQDN.  I understand that everything breaks when a FQDN 
cannot be resolved.  One of the principles which is not usually 
mentioned nowadays ia that "user applications should use names rather 
than addresses".  I'll comment quickly about the above points.

The client would have to perform DNS resolution (Item 1) for the 
system to work.  There are cases where one can get away with using IP 
addresses.

When the DNS is not reachable (Item 2) people complain.  One of the 
arguments for redundancy is that the network will keep working if a 
system fails.  A person would usually see that there is some DNS 
service which is reachable.

Item 3 is odd.  The person putting in the appropriate information 
would have to think about whether the network will support, for 
example, IPv6-only hosts.

In Section 9:

   "There is no such ambiguity in DHCPv6 (with the unfortunate exception
    of [RFC5908],which was published without following the advice provided
    during the DHC working group review, and contains many errors."

This sounds like a case of a working group doing work which is not 
part of its charter (see https://datatracker.ietf.org/wg/ntp/charter/ 
).  The approval message mentioned that "This document has received 
in-depth review from both the NTP and DHC working groups and has 
strong support for advancement". Anyway, the above text does not 
sound politically correct. :-)

Section 13 discusses about chartering requirements and advice for 
Responsible ADs.  I don't think that it belongs in a document about 
guidance to prospective DHCPv6 Option developers.

Section 22 provides advice about updating existing RFCs.  I don't 
think that it belongs in a document about DHCPv6 Option guidelines.

There is advice for authors of drafts in the Security Considerations 
section.  I'll assume that authors are a security risk. :-)

Regards,
-sm


From prvs=0004b5043f=johnl@iecc.com  Fri Oct 25 19:40:32 2013
Return-Path: <prvs=0004b5043f=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 A7EFB11E8127 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=-0.640,  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 1Fi8g9tt9iDY for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:40:28 -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 3A1D011E80E6 for <ietf@ietf.org>; Fri, 25 Oct 2013 19:40:27 -0700 (PDT)
Received: (qmail 70398 invoked from network); 26 Oct 2013 02:40:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Oct 2013 02:40:26 -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=526b2b9a.xn--btvx9d.k1310; i=johnl@user.iecc.com; bh=7alfuSO/V3yXZG9RMd+4t+pu8u6/QDlOHvkZXsqCWzw=; b=DYGi/QhhFQZ8o8avP/KMVWoRrokX+9zSOVrQcwM5+Sk1EU4A6z70adDY27tebh+4YkuW2yTl29Dbd3TBu4Bh1NP2GnsOQ0b/gpkA7Zgf6UL1LgaLtWLoN8Dw2NmlsyyBhSe7DGKphynHhOpNaVsWdVaWaIgl/TT371BS+zvratAA6U3oqvWRNfvcjzaASsRioOgWP13RC865a3YB8OKtYcoLrwXnt/yhhs0dgPB1XC/v8Ak/5pCV1/mlPKRsyjZk
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=526b2b9a.xn--btvx9d.k1310; olt=johnl@user.iecc.com; bh=7alfuSO/V3yXZG9RMd+4t+pu8u6/QDlOHvkZXsqCWzw=; b=Bwwhbbx/YpO2UU2fJYpSXMeMgu5LNxY+UQdSuDaqi2FQ5CGRtl2yLRsGw/s7w7gdw/5RaEFClXK/h/w/LGuNMSsUMDOLOVk7ilwl9J+WTmgHCFgphKKXwswMoZxFmVTooK4UJkdxFHf/Ni5vDp7YfuI5EO4+p7et0pswl9guIwEAxDDrwLZ2ZocmL3kSNccEXhWSr/tEKkjq0PvwEioJ2w+NyJSXPBWF0jlUhGyWGT4jyUiCez6eWZcW9yh86UPE
Date: 26 Oct 2013 02:40:04 -0000
Message-ID: <20131026024004.3506.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
In-Reply-To: <01OZZW7T12OY00004R@mauve.mrochek.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: ned+ietf@mauve.mrochek.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, 26 Oct 2013 02:40:32 -0000

>> the chilling effect of vigilateism is far worse than spam or trolls. ...

>I could not agree more. By condoning such measures people are damaging the
>diversity they are supposedly trying to support.

I could not disagree more.  The spam and trolling create an unpleasant
environment that drives people away.  Anyone who's run mailing lists
for a while has seen this pattern over and over, in which a tiny group
(sometimes just one) of obnoxious subscribers ruins a list and most of
the useful members leave.  The ones who remain are thick skinned or
socially oblivious, and are disproportionately middle aged North
American white guys who acted like this when they were undergrads.  We
are all big boys and girls here.  It should be entirely within our
abilities to be reasonably polite and relevant in our correspondence.

In this particular case, the execution was clumsy, but the action was
entirely appropriate.  We saw messages that were utterly irrelevant,
from an address that had never sent anything else, in a style that
strongly suggested it was a sock for a chronic troublemaker.  Why
should we put up with that kind of nonsense?

I also have to laugh at "vigilanteism."  There is no government
process that vigilantes are circumventing; the sergeant at arms
kicking people off the list IS the process.

A useful kind of vigilanteism is private messages to people
encouraging them not to engage with trolls, or to back off when
they're getting too abrasive.  I have received both, and I appreciate
that people have taken the effort to give me a nudge.

R's,
John

From jmamodio@gmail.com  Fri Oct 25 19:52:54 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 2E3A311E8122 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.833
X-Spam-Level: 
X-Spam-Status: No, score=-1.833 tagged_above=-999 required=5 tests=[AWL=0.766,  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 RkBye8+sIZOU for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:52:53 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A7F6C11E80E6 for <ietf@ietf.org>; Fri, 25 Oct 2013 19:52:53 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id i1so1712129oag.20 for <ietf@ietf.org>; Fri, 25 Oct 2013 19:52:53 -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:from:subject:date:to; bh=7NdLGW8YrEjsCGAY25iunRcHYfvqXhgHP14H827fnhM=; b=RluL91nOZZFtzOpQ+YJIVs6y+4Xa5WhXXnx/NUUU+JOwVrqVXl4KEtVMuJg1B9qXPh 487NCrS8e8LuBo6sD+eQWALdQHRMAc+UI/Euecc0a+63tjJq77uclcKQ7TEjRo0l6V0e 8ZyAVC44NN2/dAPPdmNXri2GJdXU66VXm5+Df85+kvHRmKb3W9phfxwXGw/YbQDlSS46 s3zvstqZlLVobF+Wd+Q7mLZ56gLUHFE10zWt+x9tpnRQvp7s+oLpM8GBWH7zEUtX+/s/ +LCQkG4pzasLull73m482rdOSX8sgE35J2FjTnm33GUtyoxdpT3RvsR66M6P8hN1GhMS 7hig==
X-Received: by 10.182.34.194 with SMTP id b2mr5476727obj.41.1382755973125; Fri, 25 Oct 2013 19:52:53 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id ru3sm10375745obc.2.2013.10.25.19.52.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 19:52:52 -0700 (PDT)
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <m28uxkyovt.wl%randy@psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <9B7F39FD-0E6E-492D-8006-4037D3BCD502@gmail.com>
X-Mailer: iPad Mail (11A501)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Date: Fri, 25 Oct 2013 21:52:54 -0500
To: Randy Bush <randy@psg.com>
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, 26 Oct 2013 02:52:54 -0000

Amen

-Jorge

> On Oct 23, 2013, at 10:43 AM, Randy Bush <randy@psg.com> wrote:
> 
> the chilling effect of vigilateism is far worse than spam or trolls.
> we've been dealing with the latter for decades, and there is little
> actual real harm if any.  the chilling effect of vigilanteism causes
> actual harm and reduces the rich diversity of opinion, culture, and
> viewpoint.
> 
> randy

From jmamodio@gmail.com  Fri Oct 25 19:54:08 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 84D8E11E80E6 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.245
X-Spam-Level: 
X-Spam-Status: No, score=-1.245 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 qZQvV8Ugei-Q for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 19:54:08 -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 DCF2111E8183 for <ietf@ietf.org>; Fri, 25 Oct 2013 19:54:04 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id wo20so1707575obc.25 for <ietf@ietf.org>; Fri, 25 Oct 2013 19:54:04 -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:from:subject:date:to; bh=NVKqmnRVvx+E8rtWFUUJtik7JNiKUeP3/iXTae42OlU=; b=jsKHUcSCS+lgWn5eI9jwXBTR7kmjQgbjqvg9CTCCs3xjyHTkcGswRaD1kKz+KRPsqh kgyyoWExfrfsE/DhMXBZDAGe5OlomYkm/MoU9gTGN5SsEAtM/wWsoyuSqKEz2j5XXqxd 08A1H/AtDltGOHjfGaHWeW8AafFkSf4+YHlJMaxJ/zYUSCDCWgSWGenHV8WSFgw7f3J9 lM2WcjxYUNwKFGnHBJ2IlbU8BAdNaXYcaQoxz/fKPH3R4r0L831Koj+1ZyLg1kJQ5ToM WtOyJTq5VLPNxQbFxPQp6PVWIF5uU2u+pQEf0iGTWQubjYXyh0byuty8zvWRC2lJJKGW VVog==
X-Received: by 10.182.214.98 with SMTP id nz2mr5602337obc.37.1382756044526; Fri, 25 Oct 2013 19:54:04 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id bg2sm10389423obb.1.2013.10.25.19.54.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 19:54:03 -0700 (PDT)
References: <20131026024004.3506.qmail@joyce.lan>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20131026024004.3506.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <937D93BC-E9B0-4F17-B921-882EEFAE8128@gmail.com>
X-Mailer: iPad Mail (11A501)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Date: Fri, 25 Oct 2013 21:54:05 -0500
To: John Levine <johnl@taugh.com>
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.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: Sat, 26 Oct 2013 02:54:08 -0000

Feed the trolls and they will keep growing, ignore them and they will dry an=
d die

-Jorge

On Oct 25, 2013, at 9:40 PM, "John Levine" <johnl@taugh.com> wrote:

>>> the chilling effect of vigilateism is far worse than spam or trolls. ...=

>=20
>> I could not agree more. By condoning such measures people are damaging th=
e
>> diversity they are supposedly trying to support.
>=20
> I could not disagree more.  The spam and trolling create an unpleasant
> environment that drives people away.  Anyone who's run mailing lists
> for a while has seen this pattern over and over, in which a tiny group
> (sometimes just one) of obnoxious subscribers ruins a list and most of
> the useful members leave.  The ones who remain are thick skinned or
> socially oblivious, and are disproportionately middle aged North
> American white guys who acted like this when they were undergrads.  We
> are all big boys and girls here.  It should be entirely within our
> abilities to be reasonably polite and relevant in our correspondence.
>=20
> In this particular case, the execution was clumsy, but the action was
> entirely appropriate.  We saw messages that were utterly irrelevant,
> from an address that had never sent anything else, in a style that
> strongly suggested it was a sock for a chronic troublemaker.  Why
> should we put up with that kind of nonsense?
>=20
> I also have to laugh at "vigilanteism."  There is no government
> process that vigilantes are circumventing; the sergeant at arms
> kicking people off the list IS the process.
>=20
> A useful kind of vigilanteism is private messages to people
> encouraging them not to engage with trolls, or to back off when
> they're getting too abrasive.  I have received both, and I appreciate
> that people have taken the effort to give me a nudge.
>=20
> R's,
> John

From melinda.shore@gmail.com  Fri Oct 25 20:20:33 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 BB57511E80FE for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 20:20:33 -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 c0w7UJLKGOfm for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 20:20:33 -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 55D6411E815C for <ietf@ietf.org>; Fri, 25 Oct 2013 20:20:30 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro8so816186pbb.41 for <ietf@ietf.org>; Fri, 25 Oct 2013 20:20:24 -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=LR/HIwnVpKmOn7QFxGkOUdJSRekf3xYZVGSbAXQUzt0=; b=pxxABQ7w+egFeAWUZtzJeFJCWlZyT6Ja/S3QBM5jygoQ6loELB3cy/YPw+fLSck9Rk YATNevuSe9ixNUDRyow2YEdKoxduulWYi8Cv3Zmtaof5UU5p3keOcKtyE/q6zGgR+CRK pDKJdlnVbXgMjM7mlzchqv489qEOJhAL/wE3Sjuz4deUAfx8NQtvx3e8dHMLPeNvf8YT HcMNcwJRHxkygSZcc0CADUHIGvMc20nyO31KLf3AcFJW2O3IFLvPL3yDdUOb7MXLim4G Vl47gocS0qgox24so5yAKBkrMW36lc2TrRU1Fa1ofWXzCaZxmoXVzwUP5NFAF/EBwNr0 3iWg==
X-Received: by 10.66.27.173 with SMTP id u13mr13592079pag.65.1382757624697; Fri, 25 Oct 2013 20:20:24 -0700 (PDT)
Received: from spandex.local (63-140-94-250.dynamic.dsl.acsalaska.net. [63.140.94.250]) by mx.google.com with ESMTPSA id hu10sm12858850pbc.11.2013.10.25.20.20.22 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Oct 2013 20:20:23 -0700 (PDT)
Message-ID: <526B34F5.2060509@gmail.com>
Date: Fri, 25 Oct 2013 19:20:21 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com> <9B7F39FD-0E6E-492D-8006-4037D3BCD502@gmail.com>
In-Reply-To: <9B7F39FD-0E6E-492D-8006-4037D3BCD502@gmail.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: Sat, 26 Oct 2013 03:20:33 -0000

On 10/25/13 6:52 PM, Jorge Amodio wrote:
>> On Oct 23, 2013, at 10:43 AM, Randy Bush <randy@psg.com> wrote:
>> the chilling effect of vigilateism is far worse than spam or trolls.
>> we've been dealing with the latter for decades, and there is little
>> actual real harm if any.  the chilling effect of vigilanteism causes
>> actual harm and reduces the rich diversity of opinion, culture, and
>> viewpoint.
> Amen

I think John's point - that this wasn't vigilantism, it was the
agreed-upon process - is not a minor one.  I think that the lack
of clarity around Jordi's reasons for booting someone call
that into question, but we've got a process for dealing with
posters who are disruptive and not much more and that process
was invoked.

I'm still bothered by the possibility that our Sergeant-at-
Arms booted someone off the list because of his personal antipathy
towards anonymity, and I hope this is being dealt with by somebody,
somewhere.

Melinda


From drc@virtualized.org  Fri Oct 25 21:19:07 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 08CD111E8107 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 21:19:07 -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 dG+YNK84sciR for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 21:18:59 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8FC11E8102 for <ietf@ietf.org>; Fri, 25 Oct 2013 21:18:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id E01A68712C; Sat, 26 Oct 2013 00:18:55 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 48314-02; Sat, 26 Oct 2013 00:18:55 -0400 (EDT)
Received: from [192.168.124.155] (unknown [38.103.24.128]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 8610787128; Sat, 26 Oct 2013 00:18:55 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_DD9FD5B7-9035-4023-8F09-3212CF5DB94A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: David Conrad <drc@virtualized.org>
In-Reply-To: <937D93BC-E9B0-4F17-B921-882EEFAE8128@gmail.com>
Date: Sat, 26 Oct 2013 00:18:54 -0400
Message-Id: <5F803CCD-DF4F-4857-B5F5-0AB9971F31D3@virtualized.org>
References: <20131026024004.3506.qmail@joyce.lan> <937D93BC-E9B0-4F17-B921-882EEFAE8128@gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>
X-Mailer: Apple Mail (2.1510)
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, 26 Oct 2013 04:19:07 -0000

--Apple-Mail=_DD9FD5B7-9035-4023-8F09-3212CF5DB94A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Jorge,

On Oct 25, 2013, at 10:54 PM, Jorge Amodio <jmamodio@gmail.com> wrote:
> Feed the trolls and they will keep growing, ignore them and they will =
dry and die

In this particular case, the troll in question doesn't need responses to =
be fed -- he doesn't appear to care if anyone responds to his notes.  In =
the past 20+ years he's been spewing oddly capitalized nonsense to =
various lists and websites until he's been banned, ignoring him hasn't =
caused him to dry and/or die. =20

In most social situations where an individual is being a bore, most =
folks I'm aware of simply walk away. In the context of mailing lists, =
this usually translates to just unsubscribing. I'll admit being unsure =
that sacrificing potentially useful contributors just so a known =
disruptive individual can continue posting irrelevant drivel is an =
appropriate course of action.

If you have a commons and one of the users of the commons is peeing all =
over the grass so that the sheep won't eat, do you continue to allow =
that user entry into the commons?

Regards,
-drc


--Apple-Mail=_DD9FD5B7-9035-4023-8F09-3212CF5DB94A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBAgAGBQJSa0KuAAoJENV6ebf0/4rX9YEH/3l4NIi2uiMZgHWXU5z/giJ7
L3ODMGkjbeMSItY1det1oxB9pFljWOuXOemQYubrpEuCKpbrSwRXaq1g4nya9Tcb
1zulXaROCi9UHYY0556tLztqlUfmJBkMO0FBnY2rTvxwstZeflj7GgwY5IKQCKXi
mSLSn7z51yztCmxyHAnT/WLHBRGjRTQJ7NGcpzZ4htHdH44SsnwxxAg/eaKMapbf
xf+L/maZK18aJ4VE1OovCbk0U9b8/sdi+wodOZL6o6UzUOZ5lXgnbGTgAeTZ79HT
7vLoJPUEIPuQGkM55bFPMjk7LxajuPdj5lpkMv06csKU43HysIoH4z8yhupTZDQ=
=i92w
-----END PGP SIGNATURE-----

--Apple-Mail=_DD9FD5B7-9035-4023-8F09-3212CF5DB94A--

From rogerj@gmail.com  Sat Oct 26 00:58:08 2013
Return-Path: <rogerj@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 8773211E8296 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 00:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.282
X-Spam-Level: 
X-Spam-Status: No, score=-2.282 tagged_above=-999 required=5 tests=[AWL=0.018,  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 7pHEjzVMFB75 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 00:57:49 -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 B5EE211E8295 for <ietf@ietf.org>; Sat, 26 Oct 2013 00:57:43 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hn9so2036284wib.17 for <ietf@ietf.org>; Sat, 26 Oct 2013 00:57: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 :content-type; bh=CstYXhkyZpHpN4Trd7XH0UUYpU7NgnMZZfWMvKpUhfk=; b=Spk2KwXtX48wZR2216J81QIJ5xB7h8+uT46GzrBhnAgCH8BWzGDmOR7oERIcnENOja 8FswDtXayKMzewswTIL4hiooqIv/A70W/QkKLb7MOiieuzXHcFO0q8Xud6JtLlPIy9zP pbPhAiIM1csP9KSrLGd3RnSsMw+cFhcxHdSva2VqxlE+0H4kQgKfDxJJ5f8yXQHyBgr1 KxcQfRszYrfR7bHUqIcTMtoYoyjD1oGJSTqVCT7NBsgTf2v6tcKv/R54zhZBVpiA6WJk k9uNSP6DF1qG8IOiN9tWSwqtispWWu8ADZcTBLCxsZ4/lEh7MMWbNi6u1Uu3NslPJIsv GQpg==
MIME-Version: 1.0
X-Received: by 10.194.94.101 with SMTP id db5mr505322wjb.67.1382774262406; Sat, 26 Oct 2013 00:57:42 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sat, 26 Oct 2013 00:57:42 -0700 (PDT)
In-Reply-To: <20131026024004.3506.qmail@joyce.lan>
References: <01OZZW7T12OY00004R@mauve.mrochek.com> <20131026024004.3506.qmail@joyce.lan>
Date: Sat, 26 Oct 2013 09:57:42 +0200
Message-ID: <CAKFn1SEv+g1hL-TS5OpR-i+H3ednHX=TE4tQHyvxd0WtzPOr6A@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: John Levine <johnl@taugh.com>, IETF Discussion <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: Sat, 26 Oct 2013 07:58:08 -0000

On Sat, Oct 26, 2013 at 4:40 AM, John Levine <johnl@taugh.com> wrote:
<snip>
> In this particular case, the execution was clumsy, but the action was
> entirely appropriate.  We saw messages that were utterly irrelevant,
> from an address that had never sent anything else, in a style that
> strongly suggested it was a sock for a chronic troublemaker.  Why
> should we put up with that kind of nonsense?

+1 to that.

I've keept quiet in this case because it was such an obvious case of
troublemaker that showed up.

Can we let it go and move on since it seems like we actual agree but
just need something to discuss?


-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no

From julian.reschke@gmx.de  Sat Oct 26 04:31:45 2013
Return-Path: <julian.reschke@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 82FA811E8177 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 04:31: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 p4hf+g+eXOVj for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 04:31:40 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id C071521F9FDE for <ietf@ietf.org>; Sat, 26 Oct 2013 04:31:36 -0700 (PDT)
Received: from [10.5.235.154] ([79.109.233.10]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MgHHO-1VNTZw1Wek-00NfsY for <ietf@ietf.org>; Sat, 26 Oct 2013 13:31:35 +0200
Message-ID: <526BA812.90606@gmx.de>
Date: Sat, 26 Oct 2013 13:31:30 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>,  "t.p." <daedulus@btconnect.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com>	<012601ced160$93102ee0$4001a8c0@gateway.2wire.net> <CABkgnnWzVB4mGmaZhaZkQX23FoD3GQbGmC7Phu1QSjfazayAqw@mail.gmail.com>
In-Reply-To: <CABkgnnWzVB4mGmaZhaZkQX23FoD3GQbGmC7Phu1QSjfazayAqw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:gZwlwLfBi43dhanX7qrCxq0B+zruEh6ZunQDVf/TmpimLACgJSJ JuKlF2A+/fNtRZrBw3M3C8O/g5qA929OUtk10XRr/HSAJrc2J/GG7jGYUsZyhfLng650hwq sk5QyOTt3nG7tP9XUDn7TDmVRkpK6e1ZTjJs+Ctuy4fDgstOVAMOsk83bqq4YIq01QpAnE8 5db5wEMqfljMHUNegb/Og==
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, 26 Oct 2013 11:31:45 -0000

On 2013-10-25 18:59, Martin Thomson wrote:
> On 25 October 2013 01:54, t.p. <daedulus@btconnect.com> wrote:
>> I see that we have been granted a fortnight to review eight,
>> inter-related, httpbis I-Ds, comprising over 300 pages, ending in the
>> course of IETF88 and in the run-up to a meeting when everyone comes out
>> of aestivation and the mailing lists are inundated.
>
> It's not like this work hasn't been in progress for about a decade
> already.  Though I do recall discussing a 4 week LC period at the last
> meeting.  Barry?

My experience is that longer last call periods usually do not generate 
more review, but just later review.

That being said, the timing indeed isn't optimal. On the other hand, it 
would be *really* good if we actually could discuss LC issues while in 
Vancouver.

So print the drafts (from the the HTML versions at 
<http://greenbytes.de/tech/webdav/#wg-httpbis>), and have a look at them 
on your trip to Vancouver...

Best regards, Julian


From barryleiba@gmail.com  Sat Oct 26 08:36:16 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 D9FDA11E8191 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 08:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.969
X-Spam-Level: 
X-Spam-Status: No, score=-101.969 tagged_above=-999 required=5 tests=[AWL=0.009, 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 0jJnJDlb0Yfk for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 08:36:16 -0700 (PDT)
Received: from mail-qe0-x230.google.com (mail-qe0-x230.google.com [IPv6:2607:f8b0:400d:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 56C2911E8179 for <ietf@ietf.org>; Sat, 26 Oct 2013 08:36:05 -0700 (PDT)
Received: by mail-qe0-f48.google.com with SMTP id d4so3025483qej.7 for <ietf@ietf.org>; Sat, 26 Oct 2013 08:36:04 -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:message-id:subject :from:to:cc:content-type; bh=vS7v5H76oKcxwC8efx8RP3oQGvq5POAMfqNXvNf/o6Y=; b=JmVtFOGdo5+OHa2BvXBglcj5GDXH90Lo+VTYKELqI0eycM6qhEtetI+zjEhAWqCCXi O8FKz9s+WBfRGaPPg2BgPWCIVobkFw0SqzWgb5quf72kQuzWNkhQhrKmPMQQGcYCCSAg hHJ8FLT9n+T9H3jK8AP7NlnNuqk9i2avll3IquZu7CziDWgXt53wHqb56AQ3W8Y992nP qyNTlsQ6uNGXm9886rGjAeHSCkyJVM+PL5JDkFrzTpYBw6HsiJFxbsj/9pZma3EyAq0X vNC1q5qmj+5xuk83pqb+G77HXvNYD8QuP2q3bS2Iv5fkTuDY+z9oawosQ5TmZRbKF3Ke CH3g==
MIME-Version: 1.0
X-Received: by 10.49.1.230 with SMTP id 6mr18376529qep.48.1382801764716; Sat, 26 Oct 2013 08:36:04 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.67.130 with HTTP; Sat, 26 Oct 2013 08:36:04 -0700 (PDT)
In-Reply-To: <526BA812.90606@gmx.de>
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com> <012601ced160$93102ee0$4001a8c0@gateway.2wire.net> <CABkgnnWzVB4mGmaZhaZkQX23FoD3GQbGmC7Phu1QSjfazayAqw@mail.gmail.com> <526BA812.90606@gmx.de>
Date: Sat, 26 Oct 2013 11:36:04 -0400
X-Google-Sender-Auth: ntPqUfDOrwQSWABiB2XeQPdszJg
Message-ID: <CALaySJ+ZPXqjg9Ky17+aNWrV-DspgnD_ikFCVm=OaU11USVLbw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: Julian Reschke <julian.reschke@gmx.de>
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, 26 Oct 2013 15:36:17 -0000

Julian says...
> My experience is that longer last call periods usually do not generate more
> review, but just later review.

Indeed.  I find that almost all the time, last call reviews and
comments come in either in the first few days of the last call, or in
the last few days (or, unfortunately, a day or two after it's over).
It's uncommon for reviews to flow in throughout the period, and
four-week last calls mostly wind up with two weeks of quiet in the
middle.

> That being said, the timing indeed isn't optimal. On the other hand, it
> would be *really* good if we actually could discuss LC issues while in
> Vancouver.

And that is the reason we did the last call the way we did, accepting
that the suboptimal timing would give way to better use of time at the
meeting.

Clearly, important comments won't be ignored because they're late.
But, everyone, please do your best to get your comments in by the IETF
meeting, so we can discuss them in the httpbis sessions.

Barry

From sm@resistor.net  Sat Oct 26 09:53:00 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 46E3E21F9F0E for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 09:53:00 -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 G3bHi8OI0qhT for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 09:52: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 A65BA21F9EDB for <ietf@ietf.org>; Sat, 26 Oct 2013 09:52:58 -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 r9QGqcif008838; Sat, 26 Oct 2013 09:52:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382806368; bh=flJ4+Ek4Ql/2C8sS4fkaAKwFq76Cby1T3UMMxCB1xNo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Nsl+PPcsGJJw75Gqo3xY/7d/Uz+Tr2xbY9hVJOMx/4J5M53VIFwxq3sTt21PzM1ZC Cp9Ia96s8mycUcvy2fNvqNe/GWR/hETGVZYOQIpCTg4fhAH/HO06e9FobKqq6Zlg1S 7Nz6FNAvjdnTjNNy9k370QefzA1UZK1BnFek/OZA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1382806368; i=@resistor.net; bh=flJ4+Ek4Ql/2C8sS4fkaAKwFq76Cby1T3UMMxCB1xNo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GoUTXHAEu24CO6BZZSGeJv7YKgMaiorK12vhxIDnZV0wqxWZJjxbsKVacha9VxNZc 1klUT/uyLYfHzoiC2Qp79MIAVCfAOOXtPQiKfuEpMEuC0vLNhsvGfRYPJf1NcYzLpm ljrC4KaZgt9BG4uPxV+Rr39VM2pkR65NAm4qYxck=
Message-Id: <6.2.5.6.2.20131026083527.0c914ab0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 26 Oct 2013 09:51:06 -0700
To: Barry Leiba <barryleiba@computer.org>, Ted Lemon <Ted.Lemon@nominum.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-dhc-option-guidelines-14.txt> (Guidelines for Creating New DHCPv6 Options) to Best Current Practice
In-Reply-To: <CALaySJJR+XXbPGtzXEAOZKNTSy_HZFh6neGUiamjPay=J1W5pQ@mail.g mail.com>
References: <20130919215457.30925.98345.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C933B2@xmb-aln-x02.cisco.com> <EF97C65E-A58C-4076-B737-014126786442@nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB123C96CF3@xmb-aln-x02.cisco.com> <29DE3138-F0E6-4CCB-A8A0-AD5D975E0866@nominum.com> <F474FA9D-CDC4-4DB7-937E-1252E203749F@iii.ca> <F1C4B4FB-DD91-43E3-8A01-226237BA68CE@nominum.com> <140C3FBE-AADA-420D-ADFD-80C929AF8EC3@iii.ca> <96FD71CE-ED4F-4F43-A24A-BAC991455C56@nominum.com> <C57B9F23-F8A7-422F-BFC6-F2ABB899B03D@iii.ca> <96AD4029-F81B-4BC5-90EB-D232F0A95A1A@nominum.com> <F769CC42-F242-42E6-9B40-31C875EA0156@iii.ca> <44771FA3-5660-45CB-AE84-3458C7DA4D87@nominum.com> <63557975-9AE8-4C5C-A120-9E3C7E5C84A1@iii.ca> <A4943223-ADA7-4C3E-BF18-39756F673DB3@nominum.com> <CALaySJJR+XXbPGtzXEAOZKNTSy_HZFh6neGUiamjPay=J1W5pQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Cullen Jennings <fluffy@iii.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: Sat, 26 Oct 2013 16:53:00 -0000

At 08:36 25-10-2013, Barry Leiba wrote:
>Third, your second paragraph above is really out of line.  So let's
>back away a bit and look at the picture we're painting.

I looked at the Last Call comments and I found that the discussion 
has been between Cullen Jennings and Ted Lemon.  The initial message 
was addressed to OPS ADs.  It is IETF practice to watch the fireworks 
in such cases.  Joe Abley commented about the DNSSEC validation 
issue.  There was a long thread recently about that on some IETF mailing list.

The discussion then got down to process and there was a mention of 
the working group charter.  There was a comment about IETF 
Consensus.  There was then a question which was similar to a question 
on a different thread which was a little controversial.

This is the usual IETF recipe for discussions taking the wrong 
turn.  I'll step back a little.  The first version of this draft was 
posted in June 2007.  The intended status of that draft was 
Informational.  The intended status was change to Standards Track in 
December 2012.  It was changed to BCP in June 2013.

The picture being painted is that cross-area review is lacking.

Regards,
-sm 


From jmamodio@gmail.com  Sat Oct 26 18:29:38 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 D5BAE11E81CD for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 18:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level: 
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.370,  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 Vh2qNl7P-4h5 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 18:29:38 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 949ED11E81F8 for <ietf@ietf.org>; Sat, 26 Oct 2013 18:29:37 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id oz11so3918074veb.22 for <ietf@ietf.org>; Sat, 26 Oct 2013 18:29: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=wLAod8ul8h9tvD1Tc+VDqe3PLZeN+rr3XKjbdlhEMbI=; b=mSVxLjJDJN0+9rtZSMX/p11QXTQGDVEJD8XTksD+Pkcdw8S+aK43q4UlFlXnEi4btJ e52jbfF52zHWGaeDLnvGkrhMs/vhxqZNG0RefVrVJeDI838T1XT3LadSTfjabECt7Wih QjRbnJAlahgprW4xFwYo2EEzK6UlCOidTDKiAwFefzYwlE8oFX20tzPxmrrDrlbcbFEk AoOXyXw7fOOF1oRBN28aLwh8Y7LgXL/tqc4geVu6T9HfLaZQpSvcbAjK+x7zi0gqUQLt 7v3rxTXf+o7VR+r3k0kqwD3I9PKwMKWudU8pO0uUIONVKiAX5J58Pao/KzSkH4uypw68 WCbA==
MIME-Version: 1.0
X-Received: by 10.52.190.132 with SMTP id gq4mr7154vdc.48.1382837376905; Sat, 26 Oct 2013 18:29:36 -0700 (PDT)
Received: by 10.58.209.1 with HTTP; Sat, 26 Oct 2013 18:29:36 -0700 (PDT)
In-Reply-To: <5F803CCD-DF4F-4857-B5F5-0AB9971F31D3@virtualized.org>
References: <20131026024004.3506.qmail@joyce.lan> <937D93BC-E9B0-4F17-B921-882EEFAE8128@gmail.com> <5F803CCD-DF4F-4857-B5F5-0AB9971F31D3@virtualized.org>
Date: Sat, 26 Oct 2013 20:29:36 -0500
Message-ID: <CAMzo+1ayrhX5O7gXtC-YdEb2XObR5OfR6ZFFMN8CH86h-4N+uQ@mail.gmail.com>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Jorge Amodio <jmamodio@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=089e013a00dca22b1804e9aeea5a
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, 27 Oct 2013 01:29:39 -0000

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

> If you have a commons and one of the users of the commons is peeing all
> over the grass so that the sheep won't eat, do you continue to allow that
> user entry into the commons?
>

I'll get rid of the sheep :-)

Regards,
-J

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

<div dir=3D"ltr"><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">
If you have a commons and one of the users of the commons is peeing all ove=
r the grass so that the sheep won&#39;t eat, do you continue to allow that =
user entry into the commons?<br></blockquote><div><br></div><div>I&#39;ll g=
et rid of the sheep :-)</div>
<div><br></div><div>Regards,</div><div>-J</div><div>=A0</div></div></div></=
div>

--089e013a00dca22b1804e9aeea5a--

From sm@elandsys.com  Sat Oct 26 22:55:25 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 93D0911E8113 for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 22:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.69
X-Spam-Level: 
X-Spam-Status: No, score=-101.69 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6SkfVhqsN1D for <ietf@ietfa.amsl.com>; Sat, 26 Oct 2013 22:55:24 -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 8E20B11E8146 for <ietf@ietf.org>; Sat, 26 Oct 2013 22:55:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.100]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9R5ssdN004458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Oct 2013 22:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382853311; bh=EX5Gfft+u+WNUnujLMOBE7Gdql+xR64qcsi1iVwQl6U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PsB9oY1prB7+UP927x1SwmJxO+4n3WHA4PBn9JfQVz0RThZwkcidcC+Cn95dahWp6 X4GsEoTkJrV/Sak6NpGQ6yxy3G417Jp0Mq0lO0cL2uLb+xWPtCDNb4Njqvfuvqbrhb VHwGPTr5FSsVSqJACwvhQ6ncl1KPTPSyyqSf01zk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382853311; i=@elandsys.com; bh=EX5Gfft+u+WNUnujLMOBE7Gdql+xR64qcsi1iVwQl6U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AbEYdQqlYcm55JkSLNxUjGSyKO+E/x+68cliQ37zN/p7EllbBfoxDZMfA2W6bkoUb L1l0B9yDheKN98vxKXMkMY6IUsVVkc6WpaCGs6AFEWRHl5lYd4Q5fAY+O0I02QhQ/c qw7UClDP88Hcg2JyyVKsyUb4mKFw95f0tTHDgkZw=
Message-Id: <6.2.5.6.2.20131026135545.0ccefbc0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 26 Oct 2013 15:37:28 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
In-Reply-To: <20131021130716.29482.49323.idtracker@ietfa.amsl.com>
References: <20131021130716.29482.49323.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org, Julian Reschke <julian.reschke@greenbytes.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: Sun, 27 Oct 2013 05:55:25 -0000

At 06:07 21-10-2013, The IESG wrote:
>The IESG has received a request from the Hypertext Transfer Protocol Bis
>WG (httpbis) to consider the following document:
>- 'Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing'
>   <draft-ietf-httpbis-p1-messaging-24.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-11-04. Exceptionally, comments may be

In Section 1:

   'This HTTP/1.1 specification obsoletes and moves to historic status
    RFC 2616, its predecessor RFC 2068, and RFC 2145 (on HTTP
    versioning).  This specification also updates the use of CONNECT to
    establish a tunnel, previously defined in RFC 2817, and defines the
    "https" URI scheme that was described informally in RFC 2818.'

RFC 2616 is currently a Draft Standard.  According to RFC 2026:

   "A Draft Standard must be well-understood and known to be quite
    stable, both in its semantics and as a basis for developing an
    implementation."

And:

   "A Draft Standard is normally considered to be a final specification,
    and changes are likely to be made only to solve specific problems
    encountered.  In most circumstances, it is reasonable for vendors to
    deploy implementations of Draft Standards into a disruption sensitive
    environment."

Given that draft-ietf-httpbis-p1-messaging-24 and the other drafts in 
the series is an update of RFC 2616 it is appropriate to move that 
RFC to Obsolete.  The drafts in the series is a substantial revision 
(according to the Document Shepherd). I can understand moving a 
Proposed Standard to Historic.   I read the thread about Issue #254 
[1].  I didn't find much discussion about moving the specification 
(RFC 2616) which is supposed to be stable to Historic.  What are the 
implications of doing that?

RFC 2616 is updated by RFC 6266 and RFC 6585.  As a note there is 
about explanation about RFC 6266 in 
draft-ietf-httpbis-p2-semantics-24.  In my opinion it is worth 
considering whether the HTTP status codes specified in RFC 6585 
should be included in draft-ietf-httpbis-p2-semantics-24.  That RFC 
could be included in the series if it is less work.

Regards,
S. Moonesamy

1. msg-id: 4E3978E0.6040807@gmx.de 


From julian.reschke@gmx.de  Sun Oct 27 05:11:49 2013
Return-Path: <julian.reschke@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 D332F11E8131 for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 05:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.943
X-Spam-Level: 
X-Spam-Status: No, score=-102.943 tagged_above=-999 required=5 tests=[AWL=-0.344, 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 j7BWNqwpnniX for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 05:11:44 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id A2A1C11E8112 for <ietf@ietf.org>; Sun, 27 Oct 2013 05:11:43 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.96.252]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MbOrg-1VHmNU0EGi-00Ijja for <ietf@ietf.org>; Sun, 27 Oct 2013 13:11:42 +0100
Message-ID: <526D02F8.9090000@gmx.de>
Date: Sun, 27 Oct 2013 13:11:36 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>, ietf <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-httpbis-authscheme-registrations-08.txt>(Initial Hypertext Transfer Protocol (HTTP) AuthenticationScheme Registrations) to Informational RFC
References: <20131021132502.29409.87117.idtracker@ietfa.amsl.com> <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
In-Reply-To: <012601ced160$93102ee0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:c4pVaXtUoBOZIx/kBysqyvv8qIqTk+YPeupGlh2Gd/KKgRUkFYC WQ40aTwL5sYE2Q8M6g3mS8HzA7byO6uGyFMOPWEydtzYIYjNY2sGOnhMlznr7EhZRqrM4RX oMvqzz8MXVjOjt5PYywGBUKVNvMVdcabqRRy9Lskt9UdNd4qez22zX8vh433knzxRCcgPSj F4ky1MYfpNlWvs58us8PQ==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Oct 2013 12:11:49 -0000

On 2013-10-25 10:54, t.p. wrote:
> I see that we have been granted a fortnight to review eight,
> inter-related, httpbis I-Ds, comprising over 300 pages, ending in the
> ...

Of which only 250 are non-boilerplate, non-toc, non-changelogs...

Best regards, Julian

From adrian@olddog.co.uk  Sun Oct 27 05:38:06 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 8064A21F9EF0; Sun, 27 Oct 2013 05:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.029
X-Spam-Level: 
X-Spam-Status: No, score=-0.029 tagged_above=-999 required=5 tests=[AWL=-2.519, BAYES_05=-1.11, J_CHICKENPOX_22=0.6, J_CHICKENPOX_23=0.6, J_CHICKENPOX_28=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_75=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 GKyffs9dsiPN; Sun, 27 Oct 2013 05:38:01 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 97DCD11E8126; Sun, 27 Oct 2013 05:37:58 -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 r9RCbuvU005749;  Sun, 27 Oct 2013 12:37:56 GMT
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 r9RCbsiI005727 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 27 Oct 2013 12:37:55 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport	Profile	(MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.)	to Informational RFC
Date: Sun, 27 Oct 2013 12:37:54 -0000
Message-ID: <17ad01ced311$5c6cebf0$1546c3d0$@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: Ac7TEL1dyngDhyNlQk2zlotUh8Y3nw==
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, 27 Oct 2013 12:38:06 -0000

Herewith a late response to your review comments.

> Overall Review:
> The reviewer decision is that the I-D is not ready to be publish
> because it does not achieve clearly its aim and objectives and subject
> to additional information and structure. 

The objective is quoted in the Abstract as:

   This document provides a thesaurus for the interpretation of MPLS-TP
   terminology within the context of the ITU-T Transport Network
   Recommendations.

   It is important to note that MPLS-TP is applicable in a wider set of
   contexts than just Transport Networks.  The definitions presented in
   this document do not provide exclusive nor complete interpretations
   of MPLS-TP concepts.  This document simply allows the MPLS-TP terms
   to be applied within the Transport Network context.

I think the aim of "providing a thesaurus" *is* achieved by the document.
You have some suggestions below that can be considered, but the "not ready to be
publish" is an extreme reaction.

> This thesaurus is difficult
> to trace and gather information related to MPLS, even though it is
> informational draft. 

I wonder if you are using the document in the wrong way. You are supposed to use
this to look up terms, not educate yourself on MPLS.

> This draft's terminology section is not done in a
> methodology similar to RFC4397 in terms of showing separate resources
> in each subsection and relating to the document aim.

That is correct. 
But saying "I would not have done it like this" is not very helpful.
4397 presented material in a different way and for a different purpose.

> The title seems
> like the terminology of both documentations are made as thesaurus, but
> when we go into the I-D the reviewer feels it is not organised as a
> thesaurus to simplify search and relating terms or issues of MPLS-TP.

Right, the title could be changed to match the quote from the Abstract that I
gave above. Thus:

OLD
        A Thesaurus for the Terminology used in Multiprotocol Label
       Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
                    Transport Network Recommendations.
NEW
        A Thesaurus for the Interpretation of Terminology used in 
  Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs
     in the Context of the ITU-T's Transport Network Recommendations
END

> There are many terminology not clear but more general definition.

That is not actionable as it stands, but I presume that the "many" are all in
your more detailed comments below.

> I
> prefer specific defining to clarify to ALL Internet-Community not only
> specific readers (otherwise should mention that it is not for ALL
> community to understand). 

All RFCs are for ALL, but can often only be understood in the context of wider
reading.
This document is a thesaurus for people to look things up. It is not something
you read and use to get an understanding of MPLS-TP.

> Also many times refers to references to
> define without mentioning what was that definition, is that defined
> only in ITU? is there an agreement that some one defines parts and
> other org defines other parts? why IETF draft cannot define its
> technology developed MPLS-TP? or is this draft agreeing on a joint
> definitions of many documents without clear methodology or IETF is
> just following ITU in some terms? The answers to these questions are
> very important to make the thesaurus easy to trace.

The paragraphs I quoted from the Abstract explains this.
The purpose is to be able to look up a term found in an MPLS-TP draft/RFC and
understand it in the context of the ITU-T Recommendations. Thus, often, it is
sufficient to say something like:
   See also [RFC6371] section 3.1 and [ITU-T G.8113.1],
   [ITU-T G.8113.2] clause 6.1.
I repeat: the purpose is not to explain the details of MPLS-TP. For that you
must read a large set of RFCs.

> Draft methodology of definition and terminology:
> The way the draft starts a definition should not be refering to a
> reference, this makes the reader leave the document and distracted,
> and does not know where to go which page in such reference. In ITU-T
> documents we find more organised which it defines and then refers to
> the location of such definition but not the page which the reviewer
> prefers in such situation. Therefore, it is better for an IETF
> partcipant to understand the context and even get thesaurus-of-terms
> when going through the some ITU-T documents (e.g. ITU-T G.8101/Y1355
> (10/12) ) better than this ietf-draft, which means the IESG needs to
> compare between this draft and ITU-T way of representing terms and
> defining them, to make a better draft representation facing other
> organisations, otherwise, people stop using this draft in future.

Again, this misunderstands the purpose of the document. 
You cannot expect a 20 page document to explain MPLS-TP to you. For that, you
must read either the set of MPLS RFCs or the set of ITU-T Recommendations.
What this document does is help a reader who already knows the ITU-T
Recommendations to read and understand the MPLS-TP RFCs.

> AB>Question to authors>
> Who is the reader: is this document only designed for IETF familiar
> RFCs readers or if someone from ITU refered by one document wants to
> read this doc could he/she understand? (please note that ITU does
> refer people to this draft as this draft is defining some terms and
> they acknowledge).

No change from what I have already said.

> In the reviewer's opinion it should mention this issue or who can read
> or what are the documents that should be read, because it was
> mentioned that this I-D is for IETF to get the ITU context.

The paragraphs quoted from the Abstract makes this implicitly clear.

> I-D> Scope and Applicability:
> ++++++++++++++++++++
> AB> The scope is not clear because in the draft says:-
> 
> I-D>page 2> in Abstract>
> This document provides a thesaurus for the interpretation of MPLS-TP
> terminology within the context of the ITU-T Transport Network
> recommendations.
> 
> I-D>page 4> in Introduction>
> This document provides a thesaurus for the interpretation of ITU-T
> Transport Network terminology within the context of the MPLS-TP.
>
> I-D>page 17> Section 4>
> As discussed in the introduction to this document, this thesaurus is
> intended to bring the concepts and terms associated with MPLS-TP
> into the context of the ITU-T's Transport Network architecture.
> 
> AB> The above objectives are not consistent scoped or not explained
> how and which context and terms are related and interpreted. The
> methodology of doing both is not clear, or even how they relate within
> the draft. The reviewer thinks there may be an editorial mistake, but
> still the scope was confused by that because terms were referenced to
> both RFCs and ITU-Gs.

The authors fixed this in -13

> AB> suggest adding> The motivation of the scope is nice to mention as
> done in RFC4397. However, it is easier to write scope/motivation of
> RFC4397 but not this draft because we want our participants to be
> familiar with other organisation's documents or concepts. I hope we
> don't loose our participants to go work for ITU and stop participating
> in our IETF :-)

I think you have still missed the point as stated in the quote from the
Abstract.

We are happy for people to do work in the appropriate standards bodies.

> I-D> page 4> This document provides a thesaurus for the interpretation of
ITU-T
> Transport Network terminology within the context of the MPLS-TP.
> This allows MPLS-TP documents to be generally understood by those
> familiar with MPLS RFCs.
> AB>not clear why it allows understanding> the reviewer thinks that the
> draft's thesaurus does show pointers to ITU documents but does not
> deliver the specific definitions of thoes terminologies within the ITU
> nor within Transport Network context.

Fixed in -13

> AB> to strengthen the scope of the draft to make both ITU and IETF
> participant work on similar terminologies> Add info:
> In past ITU-T developed extensions to MPLS developed by IETF to
> address the requirements of the transport network (T-MPLS). However,
> concerns were raised by the IETF that the approach taken by the ITU-T
> was incompatible with widely deployed - MPLS - technology. Now both
> ITU and IETF have work together to set a next generation transport
> network technologies compatible with MPLS-TP.

This may or may not be a true statement, but I don't see the value of including
it in this document. It is far better to present a document for what it is and
leave the politics outside the door if at all possible.

> AB> Question> Is there a discussion with the ITU Group responsible
> about defining terms, because in one document of theirs they mention
> something like some terms listed defined by IETF and some listed
> defined by ITU-T? (yes it is mentioned in acknowledgement about ITU
> and designe team, but not reflected or shown in the document scope).
> Why is there different in concepts between MPLS-TP and the ITU
> Transport Network, if the MPLS-TP was developed to facilitate
> technologies within ITU transport Network context?

There is nothing that can be done in an IETF document to make any changes to the
way the rest of the world operates and thinks. This document does its best by
enabling a translation between those worlds.

Various people from within the ITU-T reviewed this document in an attempt to
ensure it is correct. That was both helpful and diligent.

If you want to understand or influence the way the ITU-T works, you need to go
there and talk with them.

> AB> Questions> Are the ITU documents under normative referencing the
> last documents as up to date? and what are the affects of amendment of
> ITU documents are they like our RFCs. Therefore, the reviewer request
> all normative to be in force documents and  including any amendments
> if related to this I-D.

The authors have cited the correct versions of the documents for the references
they needed to make.

If you wish to understand the ITU-T documentation process, you need to go to the
ITU-T not the IETF.

> AB> suggest> Some documents of amendments are related but not
> referenced, such as amendments to ITU-T G.8101/Y1355 as [ITU-T
> G.8101/Y1355 (10/12)] in 2012. Please consider adding and refering to
> it.

The citations are made to the documents that define the terms or contain the
text that is referenced.

> I-D> Introduction Section>
> +++++++++++++++++++
> I-D>Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
>    developed by the IETF to facilitate the Operation, Administration
>    and Management of Label Switched Paths (LSPs) in a Transport Network
>    environment as defined by the ITU-T.
> 
> AB> the MPLS-TP is defined by IETF not by ITU-T, so prefer to make it
> clear in the paragraph. It can be understood: the IETF developed it as
> defined by ITU-T.

The sentence is very clear, IMHO:
- MPLS-TP developed in IETF
- MPLS-TP facilitates LSPs in an environment defined by the ITU-T

While it is clear that the paragraph could be understood in a number of ways, I
do not believe that a misunderstanding can be easily achieved.

> AB> amend to:
> Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
>    developed and defined by the IETF to facilitate the Operation,
Administration
>    and Management of Label Switched Paths (LSPs) for interoperability
> in a Transport Network environment as defined by the ITU-T.

You added "and defined". That is a superfluous duplication of "developed".

You added "for interoperability". Since you don't say "interoperable with what"
I think this only clouds the text and adds no meaning.

> AB> please add>
> MPLS-TP is a connection-oriented packet-switched transport layer
> network technology, is a profile of the MPLS that supports deployment
> in transport networks and allows operations in a manner consistent
> with other transport technologies.

For what purpose?
Not every document has to include a base definition of everything it mentions.

> AB> add> please mention that this definition of MPLS-TP by IETF will
> allow consistent with other transport technologies defined by ITU-T.

Something like...
   This document provides a thesaurus for the interpretation of MPLS-TP
   terminology within the context of the ITU-T Transport Network
   Recommendations.

Oh, that text is already there.

> AB>In Section 1.2> please explain or add info:
> In the document there are many abbreviations as CC, CE, ME, etc., but
> not mentioned if these abbreviations are used in ITU-T as a common
> abbreviation or are not, the IETF participant would like to know such
> information in this thesaurus. Also the section prefered to say this
> is the documents abbreviation (e.g. wondering why some have abbrv and
> others have not within the thesaurus).

The intention is not to explain the terms used in ITU-T Recommendations. That is
out of scope.

> Why authors used CC why not CCh as in other RFC? or does the CC has
> been used in the ITU? please clarify why.

-13 has tidied this up

> AB> suggest> CC to be changed to MPLS-TP Comm Channel (MTCC) and also
> all others related terms.

That would be inventing a new term.

> AB> some words are not clear related to terminologies and MPLS and ITU
> concepts. As there are words not defined but abbreviated as: Network
> Element (NE). Other words not defined as : Channel, path, point,
> connection, .etc. The reviewer wants to know it under the context of
> MPLS-TP and Transport Network concept as the draft aims to do but not
> found by reviewer.

Again, you are not expected to read this document and magically understand all
of networking.

You are supposed to read this document if you want to understand MPLS-TP terms
in the context of ITU-T Recommendations. That implies that you possibly have
some understanding of those Recommendations.

> In ITU documents in abbreviation section, it mentions as this
> recommendation abbreviation, this draft needs to mention that this is
> its abbreviation as well.

I don't understand.
You want, "....network element (NE)..." to have some additional indication that
"NE" is an abbreviation that means "network element"? 
And the inclusion in section 1.2 "Abbreviations" of a line that says "NE
Network Element" is not enough?

> Please refer to below editor abbreviation in section 2:
> http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

Yes. You will notice that this I-D conforms to the guidance and this list of
abbreviations.

> The draft makes in its first page an abbreviation of IETF even though
> it is mentioned in the webpage above of RFC editor.

Golly, yes, so it does.
Of course, you leave me to guess which abbreviation you are referring to which
is immensely frustrating for me.

I think we can leave it to the RFC Editor to worry about this sort of nit.

> AB>no consistency> The ITU-T has no abbreviation but still document
> mentions the IETF abbreviation while the IETF is our organisation and
> ITU is not and both are in RFC editor as no need abbreviation. Also
> MPLS is similar abbreviated in the document and the editor signals it
> as known, but in document mentioned more than one time. The ITU
> documents mentions the ITU abbreviation.
>
> I-D>Page 1>
> Internet-Drafts are working documents of the Internet Engineering Task
> Force (IETF)

This is standard boilerplate and required to be present in exactly this format.
Have you not noticed it on every other document you have read?

The rule says what you do not need to expand, not what you must not expand.

> AB> the document uses the word * see * to refer to document that has
> the definition, but not refers to pages that has the definition. I
> prefer not to refer, because this is a thesaurus so it is better to
> explain with words and refer in the end of sentence as for example
> pointing page in ref as [ITU-T_G.806, p4].

It is common practice to not include the page number since electronic and
searchable documents were first made available.

> I-D> Section 2> Terminology:
> ++++++++++++++++++++
> AB>Discuss>
> Section 2 needs an introduction, the reader does not know what is the
> document terminology, we have two organisations IETF and ITU, two
> sources of terminology and concepts that this document is considering
> but it seems that is not clear mentioned in the section in details.
> For example, Is the terms in the thesaurus taken from ITU documents or
> from IETF? or both? and then are they defined in the context of ITU-T
> or of Transport Network?

You did not suggest what the introduction should say, and I don't see the need
for an introduction. True, I don't like to see empty sections like this, but I
don't think it is important or makes the document any harder to read.
 
> AB> the sections 2.1 and 2.2 has references that are repeated in 2-3
> which is confusing because it was thought that these sections show
> distinction where references are for MPLS-TP terms and others for  ITU
> and others references having common terms. Please clarify and
> rephrase.

Nope, the distinction is by category not by reference. The references show where
the terms in any one category are found.

> I-D>Section 3> Thesaurus:
> ++++++++++++++++++
> 
> AB>The section needs an introduction to explain these terms and their
> relationships, I get confused when I see a thesaurus terms without
> good relationship based on a model or methodology. It seems that the
> draft is more referencing where are definitions than giving a clear
> thesaurus and guidance/interpretation.

Right, you got it.
The draft is not about explaining the terms, it is about giving enough
information to make it possible to understand the terms. That is largely by
reference.

> The concept of Transport Network should be defined, and also the
> MPLS-TP concept.

Why should the MPLS-TP concept be defined. Does it have a different meaning in
IETF and ITU-T? Is it not already defined well in the RFCs that the reader of
this document will be trying to interpret? 3.25 gives a base anchor, the rest is
safely assumed or additionally described in this document.

You think the concept of Transport Network should be described better than it is
in section 3.44?

> The Network Elements are defined in ITU with deep specification but in
> this draft seems general, also in ITU-T it related NE as in concept
> MPLS-TP Network Element (MT.NE), why this is not reflected in this
> draft.

I think you are trying to map in the wrong direction again. This document is for
understanding the terms already in use in IETF draft/RFCs in the context of
ITU-T Recommendations.

>> This I-D's name is mentioned in the reference [ITU-T G.8101/Y1355
> (10/12)], and that ITU reference is not mentioned in this I-D, why.

Hmmm. I don't think this document needs to mention every document that mentions
it.

> The [ITU-T G.8101/Y1355 (10/12)] explains better than this I-D that
> there are definitions defined in this I-D and there are definition
> defined by ITU documents and they list them all. Why does this I-D not
> explain in similar clarifications to readers to distinguish and avoid
> conflict in understandnings.

This document does not define things. It provides a thesaurus for the
interpretation of MPLS-TP terminology within the context of the ITU-T Transport
Network Recommendations.

> I-D> 3.1  Associated bidirectional path:
> AB>Question> how can a path defined as a path without mentioning its
> between what and through what? this is not specific definition, but
> general, or too general.

The text in 3.1 looks right to me.
Maybe you are asking for an explanation of "path" to be added to the document. 
Ah, but wait. 3.32 is "Path"
I think you needed to read the whole document before typing comments (or at
least use a search).

> I-D> 3.2 Bidirectional path:
> AB>Question> how can a path defined as a path without mentioning its
> between what and through what? this is not specific definition, but
> general, or too general.

Answer as for 3.1

> How does it differ from the 3.1 definition?

You can see that yourself from the text.
A bidirectional path is a much less specific term than an associated
bidirectional path.

> I-D> 3.3 Client layer network:
> AB> it is a network but not defined under the MPLS-TP concept, to show
> what is these layers or layer-network, and not distinguished from the
> server layer network, please clarify.

You misunderstand the purpose of this document.
If you come across the term "client network" in an MPLS-TP document in the IETF,
this entry tells you how to interpret the term in the context of the ITU-T
Recommendations.

> I-D> 3.4 Communication Channel
> AB> what is this channel? it cannot be defined as a path, as you say
> between NEs, the reviewer thinks a channel is bandwidth of the
> communication path. You must relate the channel to the path or paths
> and connections, etc. This section is very poor in information
> delivering.

The reviewer is wrong.
As the text says, it is a logical channel.
It is not necessarily related to paths.
This document is not intended to explain networking from the ground up to its
readership.

> I-D>3.6 Control Plane:
> AB> not defined, and the reviewer though we are looking into MPLS-TP
> under ITU-T context not the scope of RFC5654, please rephrase.

The reviewer is still confused about the purpose of the document.
The text explains where the term arises in the MPLS-TP documents. Since "control
plan" is a very wide term in the IETF, it is appropriate to give the scoping
context within MPLS-TP.

> AB> In general> The above are examples of confusion not all
> confusions. In the opinion of the reviewer that the definitions and
> thesaurus is week represented to easily find the specific definition
> related to draft objectives.

Yes. That is because it is not intended to provide definitions.
In general, no-one is going to be able to fix text that you only point to in
general.
Judging that the items above gave rise to just two very small changes to the
text, it is not worthwhile for the authors to revisit the text hoping to find
more issues like those above.

> ****Nits*****
> 
> AB> Question> the I-D uses words differently *end point* and
> *endpoint* why? please amend to consistentancy. Relate it in the draft
> interpretation to *connection point*, and/or NEs.

Fixed in -13

 
> I-D> customer's (individual or bundled)
> AB> amend to : customer's (i.e. individual or bundled)

Rejected as incorrect meaning.

> AB> RFC3031 wrong title and not complete authors>amend reference in
> sec 9.1 to:
> 
> [RFC3031]  Rosen, E., Viswanathan, A., and Callon, R., "Multiprotocol
> Label Switching Architecture", January, 2000.

All issues with references fixed in -13 (although this is stuff the RFC Editor
reworks anyway)

Fixed in -13

> AB> RFC5654 not complete authors>amend reference in sec 9.1 to:
> 
> [RFC5645]  Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
> and Ueno, S., "Requirements of an MPLS Transport Profile", September,
> 2009.

Fixed (to say RFC5654) in -13

> AB> RFC5860 not in order authors and title not same>amend reference in
> sec 9.1 to:
> 
> [RFC5860] Vigoureux, M., Ward, D., and Betts, M., "Requirements for
> Operations, Administration, and Maintenance (OAM) in MPLS Transport
> Networks", May, 2010.

Fixed in -13

> AB> RFC5860 not complete authors>amend reference in sec 9.1 to:
> 
> [RFC5921] Bocci, M., Frost, D., Bryant, S., Levrau, L., and Berger,
> L., "A Framework for MPLS in Transport Networks", July, 2010.

Fixed (well, fixed the ref for 5921) in -13

> AB> RFC5951 not complete authors and wrong title>amend reference in
> sec 9.1 to:
> 
> [RFC5951] Lam, K., Gray, E., and Mansfield, S., "Network Management
> Requirements for MPLS-based Transport Networks", September 2010.

Fixed in -13

Adrian
(Many people have been wondering how ADs spend their time)


From presnick@qti.qualcomm.com  Sun Oct 27 08:57:50 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 B746C21F9DCA; Sun, 27 Oct 2013 08:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.852
X-Spam-Level: 
X-Spam-Status: No, score=-104.852 tagged_above=-999 required=5 tests=[AWL=-1.923, BAYES_50=0.001, DATE_IN_PAST_06_12=1.069, 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 wtDkh9flgRWl; Sun, 27 Oct 2013 08:57:45 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id D3F5E21E80D0; Sun, 27 Oct 2013 08:57:39 -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=1382889459; x=1414425459; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=2DOU5wt7+yt1y2C1DuKKilEXfZyUb30ZKGSaSZkfyLU=; b=apu+hC/q/9elwPwPCc+17cp0U1M0WzUfugPzOrgQvwTM6hHdhxbeiWt8 3+vBwkKRvwxBhZyLHOmC3Xu6x1d4n+bN58N8LXFfa7OUSf5+C+dYghpa7 kuEeq/jRiJL4WlB6gVfqiwE/7Lf2v5RBtxWTf9U4U4Hs+0CwkR7zso+2n Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="83076787"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine01.qualcomm.com with ESMTP; 27 Oct 2013 08:57:38 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="21914931"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Oct 2013 08:57:38 -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.3.158.1; Sun, 27 Oct 2013 08:57:37 -0700
Message-ID: <526CDCAF.6070600@qti.qualcomm.com>
Date: Sun, 27 Oct 2013 04:28:15 -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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and	Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
In-Reply-To: <CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030804010308000301090309"
X-Originating-IP: [172.30.39.5]
Cc: IETF <ietf@ietf.org>, 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: Sun, 27 Oct 2013 15:57:50 -0000

--------------030804010308000301090309
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Finally getting back to this. Overall, I hope that the new version which 
I'm about to submit (Jari has given clearance to post during the 
blackout given that this is not being discussed in Vancouver) addresses 
these (and others') comments. Some specifics:

On 10/8/13 3:03 AM, Ted Hardie wrote:
> First, I am always happy when folks take the time to think deeply 
> about the IETF's processes and share those thoughts with the 
> community.  I think the conversation this has already started has been 
> useful, and I hope that the last call conversation is the same.

I appreciate that.

> That said, I do not think this document is ready for publication as an 
> RFC, and I personally suspect that it wouldn't be the best fate for it 
> even it were.  On the second point, the truth is that informational 
> RFCs are treated as actual requests for comments much any more, but 
> are taken as fixed; if the points this raises are to be maintained as 
> items of conversation (which is my personal preference), then 
> incorporating pieces of it into the Tao, Edu Team documents, or WG 
> training may be appropriate instead.  That is, put this into some form 
> where folks will not take it as an item of dogma, but as the start of 
> a conversation, and the community will be better served.  Even as an 
> Informational document, if it is published as an RFC by a sitting AD 
> via the IETF stream, it may not get that treatment.

I will leave it to Jari and the other members of the IESG to make the 
call on this. However, I do think some of these points have solidified 
to the point that having a stable reference is good. I wouldn't object 
in principle to it being published in the the form of a web page a la 
the Tao, or some Edu Team documents, but I think having an Informational 
RFC does give it some wider viewing. I've already heard from people who, 
due to the Last Call, are looking at this document in other 
organizations and find the discussion useful and interesting. I also 
don't harbor the fears that Ted does about it being treated as dogma. It 
is true that people latch on to all sorts of things as dogma, but they 
already have plenty of them that disagree with the notions in this 
document, so the counterbalance doesn't seem so bad. But again, I only 
have a personal leaning at this point toward publication, and I'm 
inclined to leave it to Jari to make the call.

> If the IESG does believe that this should be published as an RFC, I 
> think it continues to need serious work before publication.  At the 
> very base, I think it needs a much stronger sense of its audience 
> (advice to WG chairs and those that deal with them? new participants 
> in the IETF? those who want to understand the workings of the IETF 
> from the outside?) and a structure which relates to that audience.

I hope I have this clarified. Here's the paragraph I've now got in the 
intro:

    This document attempts to explain some features of rough consensus,
    explain what is not rough consensus, discuss some new ways to think
    about rough consensus, and suggest ways that we might achieve rough
    consensus and judge it in the IETF. Though this document describes
    some behaviors of working groups and chairs, it does so in broad
    brushstrokes and it does not specific procedures. Rather, this
    document is intended to foster understanding of the underlying
    principles of IETF consensus processes. While it may be of general
    interest to anyone interested in the IETF consensus processes, the
    primary audience for this document is expected to be those who have
    experience working in the IETF, and it is particularly aimed at
    generating thought and discussion among those who might lead a
    consensus discussion. Although most of the examples in this document
    talk about working group chairs, these principles are meant to apply
    to any person who is trying to lead a group to rough consensus,
    whether a chair, a design team leader, a document editor, an IESG
    area director, or any community member who is facilitating a discussion.


> The document consistently describes a test for objection model of 
> document processing; that's a fair summary of how the IETF works, but 
> shoe-horning the description into "rough consensus" because we like 
> the slogan is not really helping folks understand the IETF.  The core 
> of the IETF is a participatory process which is meant to be 
> cooperative rather than adversarial; to that extent it is fair to 
> describe it in consensus terms.  Beyond that, however, we are really 
> not seeking the consent of all parties, even as an ideal.  We are 
> trying to make sure that there are no known technical issues with a 
> proposal and that there is sufficient support to believe that it will 
> be implemented and deployed to the good of the network.

Some of this is addressed by the things I have done to address Dave's 
concerns: I've tried to make it clear what is a new view of consensus 
versus what we've actually been doing. However, in one sense I actually 
believe the opposite of what Ted says here: To claim that the what we 
are "really" doing at core is simply to make sure that there are no 
known technical issues and that there is "sufficient" support is to 
reject that idea that consensus (rough or otherwise) is important at 
all. All you need to determine that things are for the "good of the 
network" is to have a (perhaps benevolent) president or king. We reject 
that. We believe that coming to a meeting of the minds (of whoever is 
participating at the moment) over the technical issues is actually 
important.

Now, at the end of the day, I don't think Ted and I are really that far 
apart. In the end, we expect everyone to be working toward no known 
technical issues and the good of the network, so putting all of those 
heads to get a consensus is pretty likely to get the right technical 
outcome. But I think more often than not it *is* the objections that 
cause a group to rethink the consensus technical decision it may have 
arrived at (in good faith), and it is the re-forming of consensus around 
the objection, or the acceptance of the objection and placing it "in the 
rough" that really should be how we view our process.

Either way, I've tried to adjust the language a bit along these lines. I 
don't know that we're going to completely agree, but see if the changes 
make things any better in your view.

> Encouraging folks to believe that the ideal is full consensus is 
> highly problematic, for exactly the reasons that Pete later raises 
> with regards to voting:  it is very difficult to determine when you 
> have the consent of all parties if you cannot limit the parties in 
> some way.  We cannot name our members, so we cannot either count votes 
> *or count all of them as consenting*.

This I disagree with. Or we might be in violent agreement: The ideal is 
to come up with a solution that *everyone who might come along* agrees 
is the right technical solution. You don't need to count heads (or know 
which heads you're counting) to do that. Of course this is a theoretical 
ideal: You can't know that you've ever satisfied everyone who might come 
along. But that's OK. The only thing we can do is say, "We've addressed 
all known technical problems and made all known correct engineering 
tradeoffs. If others come along, we'll deal with them." That's the only 
criteria we can really use. I don't see how the theoretical ideal of 
everyone agreeing is a problematic concept.

> In the section "Five people for and one hundred people against might 
> still be rough consensus", the document describes what can occur when 
> one proposal is favoured over another by a working group's active 
> participants:  one set of participants may recruit new voices to add 
> to their preferences.  The difficulty with the given description is 
> that it is a strawman compared to that actual complexity of dealing 
> with this situation, because it posits sales and marketing folks being 
> the new voices.  The far more difficult reality is that the voices 
> often come from members of an impacted technical community who 
> generally do not attend or participate in the IETF.

Yup. I've added a paragraph to talk about just that.

> Lastly, I think Pete has failed to capture that one reason for using 
> humming or hands is that it is easy for very active participants to 
> dominate a conversation but much less easy for them to pretend to be a 
> large group.  Particularly in BoFs, using those methods to indicate 
> the likely breadth of interest is critical.  The same method can be 
> used, with some of the caution Pete recommends, to gauge whether an 
> issue which appears to be contentious based on a mic line is actually 
> a problem.  It can also, in some cases, be a valuable method of 
> reinforcing the resolve a room that has already likely come to a broad 
> agreement.  That does not contravene Pete's point that this should not 
> be used to silence objections, but there are cases where it is 
> important in its own right.

I've added a bit about this. But I am also somewhat wary of going too 
far with it. As I say in the document, hums (or shows of hands) have the 
potential to sway a working group due to herd mentality: Someone may be 
dissuaded from raising what could be an essential concern if they 
somehow feel that the group is overwhelmingly for a particular position, 
or some folks may decide to "hum along with the crowd" even though 
they're not committed to the outcome. I've mentioned the positive and 
the negative of this case.

> Again, I believe this is a valuable conversation and one that ought to 
> keep going; my recommendation against publication should also be taken 
> as a recommendation both to Pete to keep working on these ideas and to 
> the General Area Director to support a forum for that discussion.

Thanks for that, and all of the comments.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


--------------030804010308000301090309
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Finally getting back to this. Overall, I hope that the new version
which I'm about to submit (Jari has given clearance to post during the
blackout given that this is not being discussed in Vancouver) addresses
these (and others') comments. Some specifics:<br>
<br>
On 10/8/13 3:03 AM, Ted Hardie wrote:
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div>
  <div>First, I am always happy when folks take the time to think
deeply about the IETF's processes and share those thoughts with the
community.&nbsp; I think the conversation this has already started has been
useful, and I hope that the last call conversation is the same.<br>
  </div>
  </div>
  </div>
</blockquote>
<br>
I appreciate that.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div>
  <div>That said, I do not think this document is ready for publication
as an RFC, and I personally suspect that it wouldn't be the best fate
for it even it were.&nbsp; On the second point, the truth is that
informational RFCs are treated as actual requests for comments much any
more, but are taken as fixed; if the points this raises are to be
maintained as items of conversation (which is my personal preference),
then incorporating pieces of it into the Tao, Edu Team documents, or WG
training may be appropriate instead.&nbsp; That is, put this into some form
where folks will not take it as an item of dogma, but as the start of a
conversation, and the community will be better served.&nbsp; Even as an
Informational document, if it is published as an RFC by a sitting AD
via the IETF stream, it may not get that treatment.<br>
  </div>
  </div>
  </div>
</blockquote>
<br>
I will leave it to Jari and the other members of the IESG to make the
call on this. However, I do think some of these points have solidified
to the point that having a stable reference is good. I wouldn't object
in principle to it being published in the the form of a web page a la
the Tao, or some Edu Team documents, but I think having an
Informational RFC does give it some wider viewing. I've already heard
from people who, due to the Last Call, are looking at this document in
other organizations and find the discussion useful and interesting. I
also don't harbor the fears that Ted does about it being treated as
dogma. It is true that people latch on to all sorts of things as dogma,
but they already have plenty of them that disagree with the notions in
this document, so the counterbalance doesn't seem so bad. But again, I
only have a personal leaning at this point toward publication, and I'm
inclined to leave it to Jari to make the call.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div>
  <div>If the IESG does believe that this should be published as an
RFC, I think it continues to need serious work before publication.&nbsp; At
the very base, I think it needs a much stronger sense of its audience
(advice to WG chairs and those that deal with them? new participants in
the IETF? those who want to understand the workings of the IETF from
the outside?) and a structure which relates to that audience.</div>
  </div>
  </div>
</blockquote>
<br>
I hope I have this clarified. Here's the paragraph I've now got in the
intro:<br>
<br>
<blockquote>This document attempts to explain some features of rough
consensus, explain what is not rough consensus, discuss some new ways
to think about rough consensus, and suggest ways that we might achieve
rough consensus and judge it in the IETF. Though this document
describes some behaviors of working groups and chairs, it does so in
broad brushstrokes and it does not specific procedures. Rather, this
document is intended to foster understanding of the underlying
principles of IETF consensus processes. While it may be of general
interest to anyone interested in the IETF consensus processes, the
primary audience for this document is expected to be those who have
experience working in the IETF, and it is particularly aimed at
generating thought and discussion among those who might lead a
consensus discussion. Although most of the examples in this document
talk about working group chairs, these principles are meant to apply to
any person who is trying to lead a group to rough consensus, whether a
chair, a design team leader, a document editor, an IESG area director,
or any community member who is facilitating a discussion.<br>
</blockquote>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div>The document consistently describes a test for objection model
of document processing; that's a fair summary of how the IETF works,
but shoe-horning the description into "rough consensus" because we like
the slogan is not really helping folks understand the IETF.&nbsp; The core
of the IETF is a participatory process which is meant to be cooperative
rather than adversarial; to that extent it is fair to describe it in
consensus terms.&nbsp; Beyond that, however, we are really not seeking the
consent of all parties, even as an ideal.&nbsp; We are trying to make sure
that there are no known technical issues with a proposal and that there
is sufficient support to believe that it will be implemented and
deployed to the good of the network.</div>
  </div>
</blockquote>
<br>
Some of this is addressed by the things I have done to address Dave's
concerns: I've tried to make it clear what is a new view of consensus
versus what we've actually been doing. However, in one sense I actually
believe the opposite of what Ted says here: To claim that the what we
are "really" doing at core is simply to make sure that there are no
known technical issues and that there is "sufficient" support is to
reject that idea that consensus (rough or otherwise) is important at
all. All you need to determine that things are for the "good of the
network" is to have a (perhaps benevolent) president or king. We reject
that. We believe that coming to a meeting of the minds (of whoever is
participating at the moment) over the technical issues is actually
important.<br>
<br>
Now, at the end of the day, I don't think Ted and I are really that far
apart. In the end, we expect everyone to be working toward no known
technical issues and the good of the network, so putting all of those
heads to get a consensus is pretty likely to get the right technical
outcome. But I think more often than not it *is* the objections that
cause a group to rethink the consensus technical decision it may have
arrived at (in good faith), and it is the re-forming of consensus
around the objection, or the acceptance of the objection and placing it
"in the rough" that really should be how we view our process.<br>
<br>
Either way, I've tried to adjust the language a bit along these lines.
I don't know that we're going to completely agree, but see if the
changes make things any better in your view.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div>Encouraging folks to believe that the ideal is full consensus is
highly problematic, for exactly the reasons that Pete later raises with
regards to voting:&nbsp; it is very difficult to determine when you have the
consent of all parties if you cannot limit the parties in some way.&nbsp; We
cannot name our members, so we cannot either count votes *or count all
of them as consenting*.<br>
  </div>
  </div>
</blockquote>
<br>
This I disagree with. Or we might be in violent agreement: The ideal is
to come up with a solution that *everyone who might come along* agrees
is the right technical solution. You don't need to count heads (or know
which heads you're counting) to do that. Of course this is a
theoretical ideal: You can't know that you've ever satisfied everyone
who might come along. But that's OK. The only thing we can do is say,
"We've addressed all known technical problems and made all known
correct engineering tradeoffs. If others come along, we'll deal with
them." That's the only criteria we can really use. I don't see how the
theoretical ideal of everyone agreeing is a problematic concept.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">In the section "Five people for and one hundred people
against might still be rough consensus", the document describes what
can occur when one proposal is favoured over another by a working
group's active participants:&nbsp; one set of participants may recruit new
voices to add to their preferences.&nbsp; The difficulty with the given
description is that it is a strawman compared to that actual complexity
of dealing with this situation, because it posits sales and marketing
folks being the new voices.&nbsp; The far more difficult reality is that the
voices often come from members of an impacted technical community who
generally do not attend or participate in the IETF.</div>
</blockquote>
<br>
Yup. I've added a paragraph to talk about just that.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr"><font>Lastly, I think Pete has failed to capture that
one reason for using humming or hands is that it is easy for very
active participants to dominate a conversation</font> but much less
easy for them to pretend to be a large group.&nbsp; Particularly in BoFs,
using those methods to indicate the likely breadth of interest is
critical.&nbsp; The same method can be used, with some of the caution Pete
recommends, to gauge whether an issue which appears to be contentious
based on a mic line is actually a problem.&nbsp; It can also, in some cases,
be a valuable method of reinforcing the resolve a room that has already
likely come to a broad agreement.&nbsp; That does not contravene Pete's
point that this should not be used to silence objections, but there are
cases where it is important in its own right.<br>
  </div>
</blockquote>
<br>
I've added a bit about this. But I am also somewhat wary of going too
far with it. As I say in the document, hums (or shows of hands) have
the potential to sway a working group due to herd mentality: Someone
may be dissuaded from raising what could be an essential concern if
they somehow feel that the group is overwhelmingly for a particular
position, or some folks may decide to "hum along with the crowd" even
though they're not committed to the outcome. I've mentioned the
positive and the negative of this case.<br>
<br>
<blockquote
 cite="mid:CA+9kkMB4VX7mABG=oZ16uNu3zOT-1-h0K5dEN68RW92X9ER59w@mail.gmail.com"
 type="cite">
  <div dir="ltr">
  <div class="gmail_extra"><font>Again, I believe this is a valuable
conversation and one that ought to keep going; my recommendation
against publication should also be taken as a recommendation both to
Pete to keep working on these ideas and to the General Area Director to
support a forum for that discussion.</font><br>
  </div>
  </div>
</blockquote>
<br>
Thanks for that, and all of the comments.<br>
<br>
pr<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - +1 (858)651-4478</pre>
</body>
</html>

--------------030804010308000301090309--

From presnick@qti.qualcomm.com  Sun Oct 27 08:58:02 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 EF2B821F9FD6 for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.103
X-Spam-Level: 
X-Spam-Status: No, score=-106.103 tagged_above=-999 required=5 tests=[AWL=-0.573, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 2LiK17zr6oeU for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:57:50 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4A58821E80DA for <ietf@ietf.org>; Sun, 27 Oct 2013 08:57:40 -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=1382889463; x=1414425463; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=3V2ONPHoxeXsVk/bPrHpOfwqfNqeLl6ifymC8SFN6Fw=; b=xcDiFMjwduJL7OHQlraIDLvvuX4pFsoaYTY9X3xKmLqmbvaozhfKQjyE TGAwSqUxbEKDhDdNfTf+YHUBQSUTdx9Q6me/2pBaygue1QMt5NK6Hq+2c 3xMqUkMVRKfmy2BeH8/D/gELQnBCbCRJyZvcmfxUs8hASfyS0xhbSC3Bm 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="83076788"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 27 Oct 2013 08:57:40 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="575422960"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Oct 2013 08:57:39 -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.3.158.1; Sun, 27 Oct 2013 08:57:39 -0700
Message-ID: <526CDCD1.3050006@qti.qualcomm.com>
Date: Sun, 27 Oct 2013 04:28:49 -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: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <52542A8B.3000901@stpeter.im>
In-Reply-To: <52542A8B.3000901@stpeter.im>
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: Sun, 27 Oct 2013 15:58:02 -0000

I believe the status of the document issue was addressed elsewhere. On 
the other point:

On 10/8/13 10:53 AM, Peter Saint-Andre wrote:

> do you think that unanimity or "full consensus" is our ideal,
> although an ideal that's not always reachable in practice? Or is our
> ideal actually rough consensus (i.e., something like general agreement
> without unanimity)?
>
> If unanimity or "full consensus" is our ideal then we might expend more
> energy to win over instransigent persons or those who are "in the rough"
> than we would if rough consensus were our ideal. So I think it's
> important to be clear on what we're aiming for.
>    

Given the context of the document, that consensus is based on whether 
all issues are addressed, I do think that unanimity is our theoretical 
ideal: We do try to convince people that we *have* answered their issues 
and give up (i.e., declare rough consensus) when we feel we have but 
they're still not convinced. If rough consensus were the ideal, I think 
it would encourage a habit of declaring things in the rough that have 
not gotten real airing. ("Well, all we're really aiming for is rough 
consensus, and I'm pretty sure Pete's issue has been addressed, so let's 
just move along.")

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From presnick@qti.qualcomm.com  Sun Oct 27 08:58:02 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 2AE3E21F9FEE; Sun, 27 Oct 2013 08:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.089
X-Spam-Level: 
X-Spam-Status: No, score=-106.089 tagged_above=-999 required=5 tests=[AWL=-0.559, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, 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 t1LRBRHlZQ+f; Sun, 27 Oct 2013 08:57:50 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id D3D1E21E80DB; Sun, 27 Oct 2013 08:57:43 -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=1382889464; x=1414425464; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RhD2v+aWr+v1qIambgfysPsmaPEXubonciLv+MwWGHM=; b=kBVHU0XiDkg4haFsDbCW14u+UdOkfcVpvuiivB8+QkvdiFrQe4tqjDkG +xu2iPAXwEyhBPbltk4zMGqmcd4WuWGCH54FKq78cGG/TMUhQWrQ33U4l y/PH3ihSsEyS/Vn28TRkmK0Li9GUNQYHsr4BWXe0g3frqgqliaRPmEJde 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="83076793"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 27 Oct 2013 08:57:43 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="629193505"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Oct 2013 08:57:42 -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.3.158.1; Sun, 27 Oct 2013 08:57:42 -0700
Message-ID: <526CDFCC.7040509@qti.qualcomm.com>
Date: Sun, 27 Oct 2013 04:41:32 -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: Russ Housley <housley@vigilsec.com>
Subject: Re: Gen-ART Review of draft-resnick-on-consensus-05
References: <9EBBA597-AA12-44AE-9096-9D1DC88260EB@vigilsec.com>
In-Reply-To: <9EBBA597-AA12-44AE-9096-9D1DC88260EB@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: IETF Gen-ART <gen-art@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: Sun, 27 Oct 2013 15:58:02 -0000

On 10/11/13 11:27 AM, Russ Housley wrote:
> Major issues:
>
> Section 4 says: "... members of any given working group ..."  Working
> groups do not have members; they have participants.  Please reword to
> avoid confusion on this point.
>    

Done.

> Minor issues:
>
> Section 4 says that humming should be the start of a conversation, not
> the end.  However, it can be either.  Using the document's example, the
> chair could ask, "Hum now if you cannot live with choice A."  Silence
> confirms that rough consensus has been reached.
>    

There was a line hidden in there about this, but I've clarified.

> Section 6 tells about some pitfalls to avoid, but the hum can still be
> a very valuable tool to help a chair determine if the group has reached
> consensus.
>    

It can be (and I've added some text along these lines), but it gets 
misused for these purposes all too often, which is a major theme of the 
document.

> Further, a hum in a BOF is different.
>    

As I said in my reply to Ted, I've made some attempt to address this, 
but also pointed out the downsides.

> Nits:
>
> In section 2, the document says "... not appealing to some others."
> When I read it the firs time, the RFC 2026 definition of "appeal"
> jumped into my mind.  That is not the intent here.  Maybe it is just
> me.  Please consider rewording, especially since the RFC 2026 meaning
> is used in Section 3.
>    

I'll see if I can drum up a better synonym.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From presnick@qti.qualcomm.com  Sun Oct 27 08:58:16 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 7A59E21E80D9 for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, 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 EvD7lqf9WWsF for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:58:02 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 66F6B21E80D5 for <ietf@ietf.org>; Sun, 27 Oct 2013 08:57:45 -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=1382889465; x=1414425465; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=NVhcbMs2VIkPtNntjovm2T7MkDKJGp0OU96KN8N9qfY=; b=DnElcKOhTK7jHhwRNqKZPysrFYvP8s6qXswHXmRBns7DXeKF0c+hZw+6 tFQBFvX2tNmhR/bIhUH8dQNfiPK9H0OYyDN0ysOex3E0moCi/cMYk/p+G 2CrRf/euGM9EibqSxO4yVUiXXwsPGYDhzo51TU92lImrHT1msPms8zCTq Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="83399765"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 27 Oct 2013 08:57:44 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="564274373"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Oct 2013 08:57:44 -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.3.158.1; Sun, 27 Oct 2013 08:57:43 -0700
Message-ID: <526CED81.2000204@qti.qualcomm.com>
Date: Sun, 27 Oct 2013 05:40:01 -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: Eliot Lear <lear@cisco.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <52552DFA.9030904@cisco.com>
In-Reply-To: <52552DFA.9030904@cisco.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: Sun, 27 Oct 2013 15:58:16 -0000

On 10/9/13 5:20 AM, Eliot Lear wrote:
> 1.  No matter how you slice the definition of rough consensus, if the
> chair does not act in a fair and balanced way, the outcome will be
> incorrect.  This is what the appeals process is for, and I would suggest
> mentioning it, perhaps in some detail.
>    

I do allude to this at the end of section 3, and I've highlighted it a 
bit better with one of the edits Dave suggested. But every time I tried 
to elaborate the "detail", I found myself talking more about the theory 
of appeals rather than the theory of consensus. I'm open to some 
suggested text if you have some.

> 2.  The case of Section 7 is, as you say, a mind bender.  I would
> suggest adding another use case: what if those 100 people write their
> own draft.  Can they use the exact same process to get the draft adopted
> and approved, so long as they answer the technical issues that arise?
> In other words, if there are multiple valid alternatives, and one suits
> one vendor group and another suits another, can there be just one
> standard?  At the neck of the hourglass, perhaps so?  What happens in
> this case, from your point of view?  What makes group (a) more special
> than group (b)?
>    

Though I think your example adds delightfully to the mind bender, I'm 
inclined to avoid it. At one level, 100 proposed drafts is no different 
than 100 proposed objections, though I would contend that if the drafts 
are actually well written, they would have to have good reasoning as to 
why the WG's original choice was not the best one. One way to sort your 
proposed mess is for the chair to go back to the charter of the WG and 
see which proposal actually meets the charter requirement. Or the chair 
can make the question about who the assigned document editor is. But 
really what your proposing is just a step worse into the "pathological 
WG" problem. And really we could do this ad infinitum. (I'm reminded of 
the old George Carlin routine about his days in Catholic school and "Ask 
the priest" day: "So, Father, say you haven't received your Easter 
communion. And it's Pentecost Sunday, the last day. And you're on a ship 
at sea. And the chaplain goes into a coma. But you wanted to receive. 
And then it's Monday, too late. And then you cross the international 
dateline...".) The fact is that though rough consensus is a resilient 
process, it's not bulletproof to every attack. This document can only go 
so far into how it deals with problems. I've added a good bit to that 
section to address Ted's comments. Hopefully you find that satisfying.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From presnick@qti.qualcomm.com  Sun Oct 27 08:58:20 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 DFB0B21E80EE for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.625
X-Spam-Level: 
X-Spam-Status: No, score=-102.625 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: 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+QojNFW5efX for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 08:58:16 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 30A5521F9CA1 for <ietf@ietf.org>; Sun, 27 Oct 2013 08:57:47 -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=1382889467; x=1414425467; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cDvm98OJ2sEbaoqv9P1WPCxA0k7DfDoc4IU2NGlpUJE=; b=gBhs/qnsI/AuplO3LG2l3Qd8WdIPBkUiPWBF14IfkEFHNXbl0Endp22D G0PBVyVlPU611PWE6+BgJevQRKotWQJLfa/4lH8TPI+Hu1kIwydHNoX4X 0s9qyq9jrcm4EC4oNOoIo8Enlf9WkMTwE2pU7ZR0OnDOy7zT3fsXgjfXw U=;
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="54612502"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 27 Oct 2013 08:57:46 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7240"; a="539769687"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Oct 2013 08:57:46 -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.3.158.1; Sun, 27 Oct 2013 08:57:45 -0700
Message-ID: <526CF7FD.8060500@qti.qualcomm.com>
Date: Sun, 27 Oct 2013 06:24:45 -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: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Last calling draft-resnick-on-consensus
References: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.gmail.com>
In-Reply-To: <CADnDZ8-Riy8khq-QkjGa_8Qzt2=g8J00_Pg=iA=naXZqQL5taw@mail.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 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, 27 Oct 2013 15:58:21 -0000

Overall, I think some of your points are well-taken and I think the 
edits I've made to address everyone's comments should address your 
comments as well. However, I think you also want this document to be 
more generally about IETF process and to require participants to to 
certain things. I think those items are beyond the purpose of the 
document. Details below.

On 10/11/13 5:40 AM, Abdussalam Baryun wrote:
> 1) The draft should include remote participants input to the consensus 
> process or path. The mailing list should be the main place for 
> consensus measuring its roughness in the Internet community (not in 
> only rooms or in hidden design teams).

I think this is a good point, and I've made sure to elaborate the 
examples that are specifically about mailing lists a bit. I don't want 
to go much further into the specific process points (e.g., that the 
mailing list is the final place for the WG taking decisions), as those 
are already addressed in other documents, and this document is really 
about the nature of consensus, not specific processes in the IETF.

> 2) The document does not mention the editor's task and how to work 
> with discussions or chairs. If the editors are 5 most active 
> participants in the WG then they are ruling the WG, and they can even 
> discourage inputs by just disagreeing. I in MANET WG experienced many 
> examples mentioned in your document, which I think will help future 
> new participants to make better impacts on ietf WGs. I request 
> explaining editors input and Chair's in such examples/situations. 
> Editors and Chair are the ones facilitating on the path (i.e. 
> consensus, as mentioned in draft).

I've certainly clarified that editors can lead consensus discussions, 
but I don't think that's what you're getting at. You seem to be 
concerned that editors can abuse their position. But if a chair does 
take seriously the notion about open unaddressed issues, this shouldn't 
happen. I don't think this document should be trying to address every 
process failing in the IETF.

> 3) The document does not mention the destinations of *consensus paths* 
> within IETF. What you mean by destination?

This is mentioned in the first sentence of section 5: The destination is 
"the best technical (and sometimes procedural) outcome when we make 
decisions."

> For me the destination is to submit the best document to IESG, or to 
> Adopt an interesting document as WG document.

This is too specific for this document. And to a certain extent it 
sounds wrong: The *document* is not the goal, and "interesting" is 
certainly not the right criteria. The deployed protocol is the goal and 
technical correctness (or at least some good engineering tradeoff) is 
the right criteria.

> 4) In the abstract you use *WE*, I object to use that word only if 
> defined; do you mean all community or you mean majority, or minority, 
> or management, or f2f participants or remote participants, or WG 
> chairs, or ADs, etc.

I definitely mean the entire IETF community, and I think that's 
perfectly clear in the document.

> Suggest/request to add in the abstract that this document should be as 
> information to the training of WG Chairs.

I have added some text about the intended audience in the introduction.

> Also the abstract should include what is mentioned in the conclusion 
> of *the way of thinking to get to participation decisions*.
> Please amend the abstract:

I've updated the abstract (and the introduction) to hopefully capture 
what you desire. Your suggested text was a bit too detailed for an 
abstract in my opinion. And again, remember that this document is *not* 
proscribing process.

> 5) I request to see the word *polite*, *friendly*, *encourage*, and 
> other positive ways of thinking that helps (i.e. don't mean formal or 
> informal writting on the list) , because I see some negative thinking 
> in some participations of IETF WGs, so I request the draft to mention 
> friendly efforts.

Again, though I certainly agree that such values are good and important 
in discussions, I think this starts to go beyond the discussion of what 
consensus is and how it works, and delves more into the general behavior 
of IETF participants.

> 6) Not understood the information on the draft's ideas on process of 
> consensus path or paths or the number of its practices, and how the 
> Chair should use different paths or methods to get to better consensus 
> (i.e. each time measures consensus the chair tries to gain a better 
> one not worse one). People think of what will happen if some disagree 
> with our draft, so they think how to use such path, so your draft 
> makes me think of what are my friendly or informal options. I 
> recommend to make more work if possible of solutions/guidances for the 
> consensus facilitators (editors, chairs, ADs).

If I understand you correctly, you are recommending that the document 
say more about how leaders can progress and get closer to consensus as 
they do their work. I hope some of the expansions and clarification I 
have put in the document do some of that.

Thanks for your feedback.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From sm@elandsys.com  Sun Oct 27 11:48:32 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 3CB3221F9F6C; Sun, 27 Oct 2013 11:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.216
X-Spam-Level: 
X-Spam-Status: No, score=-102.216 tagged_above=-999 required=5 tests=[AWL=0.383, 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 J6x+FFSQFpp7; Sun, 27 Oct 2013 11:48:30 -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 81A0911E819F; Sun, 27 Oct 2013 11:48:25 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.154.55]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9RIm6Lx012860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Oct 2013 11:48:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382899703; bh=yZ18CMOR7cvkVGqi2WKALKp3VNkv8C2TCslZxBUchSM=; h=Date:To:From:Subject:Cc; b=JTYouWhgRo3YUmhrvIcqg0z+lRCCxXKanf6lrdS3IJYlT667K8/fRa3T28D9ixF0L RyZTsBU6XNHOCD3RNZWONdi7aO+G1i9sZOjIE6u52sicsoD9ap0VPldsTwKKbAQiL1 9qdW+/kUr6qGPOZWihlgiiqyAyqZ7m/zjxMTPRYA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382899703; i=@elandsys.com; bh=yZ18CMOR7cvkVGqi2WKALKp3VNkv8C2TCslZxBUchSM=; h=Date:To:From:Subject:Cc; b=QjgQMUMEZ4+HmmY2zANoZhaqmv418/xfCA0rjNKdxSfwoMSR2bFk9ldVvag1HQvts sciWHRjD/Jw4leao1iXja6WrdNEHJ3Kl1jrhI150ylU5p2Z+epgOvOJP2LgvppBMFv ScwNJq+ccwSKxxwIDn1zu1O5pJ4QK8t6iTvePXfc=
Message-Id: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 27 Oct 2013 11:44:46 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p1-messaging.all@tools.ietf.org,  iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 27 Oct 2013 18:48:32 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p1-messaging-24
Title:

Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Reviewer: S. Moonesamy
Review Date: October 27, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft is almost ready for publication as a Proposed Standard.

This document provides an overview of HTTP architecture and its 
associated terminology, defines the "http" and "https" Uniform 
Resource Identifier (URI) schemes, defines the HTTP/1.1 message 
syntax and parsing requirements, and describes general security 
concerns for implementations.

The document is well-written and clear.  I did not verify the changes 
between this specification and RFC 2616 as the intended status is 
Proposed Standard.  This specification can affect other 
specifications in the Applications Area as there are several 
specifications which are built upon HTTP.

Major issues: None

Minor issues:

In Section 2.6:

   "Intermediaries that process HTTP messages (i.e., all intermediaries
    other than those acting as tunnels) MUST send their own HTTP-version
    in forwarded messages.  In other words, they MUST NOT blindly forward
    the first line of an HTTP message without ensuring that the protocol
    version in that message matches a version to which that intermediary
    is conformant for both the receiving and sending of messages."

The first RFC 2119 requirement (see above) states that the 
intermediary has to send its own HTTP-version while the second RFC 
2119 requirement prohibits the intermediary from blindly forwarding 
the first line of the HTTP message.  The intent of the first 
requirement seems clear to me.  I suggest having the second 
requirement as clarifying text instead of a RFC 2119 requirement.

   "A client SHOULD send a request version equal to the highest version
    to which the client is conformant and whose major version is no
    higher than the highest version supported by the server, if this is
    known."

The client would have to track the version supported by the server 
once it knows that information.  A server can be one or more HTTP 
implementations.  In practice these implementations will likely 
support HTTP 1.1.  I'll list the "and whose major version is no 
higher than the highest version supported ..." as an issue.  Is the 
intent to ensure that the client can work with HTTP 2.0?

   "A server MAY send a 505 (HTTP Version Not Supported) response if
   it cannot send a response using the major version used in the
   client's request."

Why is this a RFC 2119 "may"?

In Section 5.7:

   "An intermediary MUST NOT forward a message to itself unless it is
    protected from an infinite request loop.  In general, an intermediary
    ought to recognize its own server names, including any aliases, local
    variations, or literal IP addresses, and respond to such requests
    directly."

I don't understand why an intermediary would forward a message to 
itself.  Please note that I do not consider this prohibition as an issue.

In Section 6.1:

   "Recipients that trigger certain connection behavior based on the
    presence of connection options MUST do so based on the presence
    of the connection-option rather than only the presence of the
    optional header field.  In other words, if the connection option
    is received as a header field but not indicated within the
    Connection field-value, then the recipient MUST ignore the
    connection-specific header field because it has likely been
    forwarded by an intermediary that is only partially conformant.

I am flagging the usage of a requirement followed by the "must 
ignore" requirement as an issue as the "in other words" suggest that 
it is a clarification of the first requirement.

In Section 6.4

   "A client SHOULD limit the number of simultaneous open connections
    that it maintains to a given server."

There is an explanation about why a specific number is not included 
for this recommendation in the paragraphs following the above 
text.  I read Issue #131.  I don't see any discussion of the 
tradeoffs in Section 6.4.  The is a note about servers may reject an 
excessive number of connections from a client if they deem that it is abusive.

The HTTP Transfer Coding namespace (Section 8.4) is currently "First 
Come First Served".  The new registration procedure required IETF 
Review.  What is the reason for the change?

In Section 8.5.1:

   'The registration SHOULD name a set of expected "protocol-version"
    tokens associated with that token at the time of registration.'

Why is this a RFC 2119 "should"?

   "The IESG MAY reassign responsibility for a protocol token.  This
    will normally only be used in the case when a responsible party
    cannot be contacted."

I suggest using plain English instead of RFC 2119 key words for the 
above (and for the rest of the text in Section 8.5.1).

Nits:

For Section 8.1, the Message Header Field Names registry is at 
http://www.iana.org/assignments/message-headers/

For Section 8.2, the URI Schemes registry is at 
http://www.iana.org/assignments/uri-schemes/

In Section 8.4, the RFC 2119 key words are not needed as that section 
is about a procedure for registration.  Plain English is usually clear enough.

Regards,
S. Moonesamy


From abdussalambaryun@gmail.com  Sun Oct 27 14:13: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 00AF011E81B3; Sun, 27 Oct 2013 14:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.636
X-Spam-Level: 
X-Spam-Status: No, score=-1.636 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, J_CHICKENPOX_23=0.6, J_CHICKENPOX_28=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 9pe3pFzfgj8p; Sun, 27 Oct 2013 14:13:01 -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 748D911E8137; Sun, 27 Oct 2013 14:12:56 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro8so2184902pbb.41 for <multiple recipients>; Sun, 27 Oct 2013 14:12: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=UjBSFurMFYC10ljrTB0JLxF0L9Bt38LF2oNbiStRPMQ=; b=A/gcEAWyc36sEu+wsftRtLCjJyoW585iSLTHX1fdsRl9RUZS2ElizxY65+YXdpxsho z3bZjFGDiQv1748P2OZob+461Iinc1cx0kPKyzBgrFnUT5WivJWaOpT6fBxJotCkuV6I 8hLi61wq8AIXADEx8uW1KdUxVMWyqAs5HiioBmFebit2F/6YzMk07UY6d0YNaqov9ClG qLDHwOw2Et5uKhdPURp5eOUx4n9LD9D9MOiy3u8EuLr+9Q8qAzH+BfYzgyzvqHY5Hlso iFB8QHs7i7NltIphIdxspEtMK5LBx1JMGzQyd/d8I2JhZdTM0o59G8OyUtiW4+m8/DoA oNvg==
MIME-Version: 1.0
X-Received: by 10.68.242.4 with SMTP id wm4mr12610374pbc.77.1382908376258; Sun, 27 Oct 2013 14:12:56 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Sun, 27 Oct 2013 14:12:56 -0700 (PDT)
In-Reply-To: <17ad01ced311$5c6cebf0$1546c3d0$@olddog.co.uk>
References: <17ad01ced311$5c6cebf0$1546c3d0$@olddog.co.uk>
Date: Sun, 27 Oct 2013 21:12:56 +0000
Message-ID: <CADnDZ89Pggius+O5SnJ75fQYy96oyYb4EK6nrd30RuEAL9e2Fw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7b339c25861ffc04e9bf7202
Cc: "ietf@ietf.org" <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: Sun, 27 Oct 2013 21:13:04 -0000

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

I think authors/you did not reply to all my review dated 17 October, and
the new version 13 of the draft is dated 20 October before replying to my
review on the list. The last call was for version 12 and the authors found
my review to help to update fix without replying to the review with the
community.  I recommend always reply before submitting new drafts after LC.
I will not reply/discuss because I feel discouraged by authors.

The reply saying fixed but not mentioned that my review result was before
the discovery to fix, it seems like the reply is saying we fixed it before
you reviewed or discovered the nits.

AB

On Sunday, October 27, 2013, Adrian Farrel wrote:

> Herewith a late response to your review comments.
>
> > Overall Review:
> > The reviewer decision is that the I-D is not ready to be publish
> > because it does not achieve clearly its aim and objectives and subject
> > to additional information and structure.
>
> The objective is quoted in the Abstract as:
>
>    This document provides a thesaurus for the interpretation of MPLS-TP
>    terminology within the context of the ITU-T Transport Network
>    Recommendations.
>
>    It is important to note that MPLS-TP is applicable in a wider set of
>    contexts than just Transport Networks.  The definitions presented in
>    this document do not provide exclusive nor complete interpretations
>    of MPLS-TP concepts.  This document simply allows the MPLS-TP terms
>    to be applied within the Transport Network context.
>
> I think the aim of "providing a thesaurus" *is* achieved by the document.
> You have some suggestions below that can be considered, but the "not ready
> to be
> publish" is an extreme reaction.
>
> > This thesaurus is difficult
> > to trace and gather information related to MPLS, even though it is
> > informational draft.
>
> I wonder if you are using the document in the wrong way. You are supposed
> to use
> this to look up terms, not educate yourself on MPLS.
>
> > This draft's terminology section is not done in a
> > methodology similar to RFC4397 in terms of showing separate resources
> > in each subsection and relating to the document aim.
>
> That is correct.
> But saying "I would not have done it like this" is not very helpful.
> 4397 presented material in a different way and for a different purpose.
>
> > The title seems
> > like the terminology of both documentations are made as thesaurus, but
> > when we go into the I-D the reviewer feels it is not organised as a
> > thesaurus to simplify search and relating terms or issues of MPLS-TP.
>
> Right, the title could be changed to match the quote from the Abstract
> that I
> gave above. Thus:
>
> OLD
>         A Thesaurus for the Terminology used in Multiprotocol Label
>        Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's
>                     Transport Network Recommendations.
> NEW
>         A Thesaurus for the Interpretation of Terminology used in
>   Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs
>      in the Context of the ITU-T's Transport Network Recommendations
> END
>
> > There are many terminology not clear but more general definition.
>
> That is not actionable as it stands, but I presume that the "many" are all
> in
> your more detailed comments below.
>
> > I
> > prefer specific defining to clarify to ALL Internet-Community not only
> > specific readers (otherwise should mention that it is not for ALL
> > community to understand).
>
> All RFCs are for ALL, but can often only be understood in the context of
> wider
> reading.
> This document is a thesaurus for people to look things up. It is not
> something
> you read and use to get an understanding of MPLS-TP.
>
> > Also many times refers to references to
> > define without mentioning what was that definition, is that defined
> > only in ITU? is there an agreement that some one defines parts and
> > other org defines other parts? why IETF draft cannot define its
> > technology developed MPLS-TP? or is this draft agreeing on a joint
> > definitions of many documents without clear methodology or IETF is
> > just following ITU in some terms? The answers to these questions are
> > very important to make the thesaurus easy to trace.
>
> The paragraphs I quoted from the Abstract explains this.
> The purpose is to be able to look up a term found in an MPLS-TP draft/RFC
> and
> understand it in the context of the ITU-T Recommendations. Thus, often, it
> is
> sufficient to say something like:
>    See also [RFC6371] section 3.1 and [ITU-T G.8113.1],
>    [ITU-T G.8113.2] clause 6.1.
> I repeat: the purpose is not to explain the details of MPLS-TP. For that
> you
> must read a large set of RFCs.
>
> > Draft methodology of definition and terminology:
> > The way the draft starts a definition should not be refering to a
> > reference, this makes the reader leave the document and distracted,
> > and does not know where to go which page in such reference. In ITU-T
> > documents we find more organised which it defines and then refers to
> > the location of such definition but not the page which the reviewer
> > prefers in such situation. Therefore, it is better for an IETF
> > partcipant to understand the context and even get thesaurus-of-terms
> > when going through the some ITU-T documents (e.g. ITU-T G.8101/Y1355
> > (10/12) ) better than this ietf-draft, which means the IESG needs to
> > compare between this draft and ITU-T way of representing terms and
> > defining them, to make a better draft representation facing other
> > organisations, otherwise, people stop using this draft in future.
>
> Again, this misunderstands the purpose of the document.
> You cannot expect a 20 page document to explain MPLS-TP to you. For that,
> you
> must read either the set of MPLS RFCs or the set of ITU-T Recommendations.
> What this document does is help a reader who already knows the ITU-T
> Recommendations to read and understand the MPLS-TP RFCs.
>
> > AB>Question to authors>
> > Who is the reader: is this document only designed for IETF familiar
> > RFCs readers or if someone from ITU refered by one document wants to
> > read this doc could he/she understand? (please note that ITU does
> > refer people to this draft as this draft is defining some terms and
> > they acknowledge).
>
> No change from what I have already said.
>
> > In the reviewer's opinion it should mention this issue or who can read
> > or what are the documents that should be read, because it was
> > mentioned that this I-D is for IETF to get the ITU context.
>
> The paragraphs quoted from the Abstract makes this implicitly clear.
>
> > I-D> Scope and Applicability:
> > ++++++++++++++++++++
> > AB> The scope is not clear because in the draft says:-
> >
> > I-D>page 2> in Abstract>
> > This document provides a thesaurus for the interpretation of MPLS-TP
> > terminology within the context of the ITU-T Transport Network
> > recommendations.
> >
> > I-D>page 4> in Introduction>
> > This document provides a thesaurus for the interpretation of ITU-T
> > Transport Network terminology within the context of the MPLS-TP.
> >
> > I-D>page 17> Section 4>
> > As discussed in the introduction to this document, this thesaurus is
> > intended to bring the concepts and terms associated with MPLS-TP
> > into the context of the ITU-T's Transport Network architecture.
> >
> > AB> The above objectives are not consistent scoped or not explained
> > how and which context and terms are related and interpreted. The
> > methodology of doing both is not clear, or even how they relate within
> > the draft. The reviewer thinks there may be an editorial mistake, but
> > still the scope was confused by that because terms were referenced to
> > both RFCs and ITU-Gs.
>
> The authors fixed this in -13
>
> > AB> suggest adding> The motivation of the scope is nice to mention as
> > done in RFC4397. However, it is easier to write scope/motivation of
> > RFC4397 but not this draft because we want our participants to be
> > familiar with other organisation's documents or concepts. I hope we
> > don't loose our participants to go work for ITU and stop participating
> > in our IETF :-)
>
> I think you have still missed the point as stated in the quote from the
> Abstract.
>
> We are happy for people to do work in the appropriate standards bodies.
>
> > I-D> page 4> This document provides a thesaurus for the interpretation of
> ITU-T
> > Transport Network terminology within the context of the MPLS-TP.
> > This allows MPLS-TP documents to be generally understood by those
> > familiar with MPLS RFCs.
> > AB>not clear why it allows understanding> the reviewer thinks that the
> > draft's thesaurus does show pointers to ITU documents but does not
> > deliver the specific definitions of thoes terminologies within the ITU
> > nor within Transport Network context.
>
> Fixed in -13
>
> > AB> to strengthen the scope of the draft to make both ITU and IETF
> > participant work on similar terminologies> Add info:
> > In past ITU-T developed extensions to MPLS developed by IETF to
> > address the requirements of the transport network (T-MPLS). However,
> > concerns were raised by the IETF that the approach taken by the ITU-T
> > was incompatible with widely deployed - MPLS - technology. Now both
> > ITU and IETF have work together to set a next generation transport
> > network technologies compatible with MPLS-TP.
>
> This may or may not be a true statement, but I don't see the value of
> including
> it in this document. It is far better to present a document for what it is
> and
> leave the politics outside the door if at all possible.
>
> > AB> Question> Is there a discussion with the ITU Group responsible
> > about defining terms, because in one document of theirs they mention
> > something like some terms listed defined by IETF and some listed
> > defined by ITU-T? (yes it is mentioned in acknowledgement about ITU
> > and designe team, but not reflected or shown in the document scope).
> > Why is there different in concepts between MPLS-TP and the ITU
> > Transport Network, if the MPLS-TP was developed to facilitate
> > technologies within ITU transport Network context?
>
> There is nothing that can be done in an IETF document to make any changes
> to the
> way the rest of the world operates and thinks. This document does its best
> by
> enabling a translation between those worlds.
>
> Various people from within the ITU-T reviewed this document in an attempt
> to
> ensure it is correct. That was both helpful and diligent.
>
> If you want to understand or influence the way the ITU-T works, you need
> to go
> there and talk with them.
>
> > AB> Questions> Are the ITU documents under normative referencing the
> > last documents as up to date? and what are the affects of amendment of
> > ITU documents are they like our RFCs. Therefore, the reviewer request
> > all normative to be in force documents and  including any amendments
> > if related to this I-D.
>
> The authors have cited the correct versions of the documents for the
> references
> they needed to make.
>
> If you wish to understand the ITU-T documentation process, you need to go
> to the
> ITU-T not the IETF.
>
> > AB> suggest> Some documents of amendments are related but not
> > referenced, such as amendments to ITU-T G.8101/Y1355 as [ITU-T
> > G.8101/Y1355 (10/12)] in 2012. Please consider adding and refering to
> > it.
>
> The citations are made to the documents that define the terms or contain
> the
> text that is referenced.
>
> > I-D> Introduction Section>
> > +++++++++++++++++++
> > I-D>Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
> >    developed by the IETF to facilitate the Operation, Administration
> >    and Management of Label Switched Paths (LSPs) in a Transport Network
> >    environment as defined by the ITU-T.
> >
> > AB> the MPLS-TP is defined by IETF not by ITU-T, so prefer to make it
> > clear in the paragraph. It can be understood: the IETF developed it as
> > defined by ITU-T.
>
> The sentence is very clear, IMHO:
> - MPLS-TP developed in IETF
> - MPLS-TP facilitates LSPs in an environment defined by the ITU-T
>
> While it is clear that the paragraph could be understood in a number of
> ways, I
> do not believe that a misunderstanding can be easily achieved.
>
> > AB> amend to:
> > Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been
> >    developed and defined by the IETF to facilitate the Operation,
> Administration
> >    and Management of Label Switched Paths (LSPs) for interoperability
> > in a Transport Network environment as defined by the ITU-T.
>
> You added "and defined". That is a superfluous duplication of "developed".
>
> You added "for interoperability". Since you don't say "interoperable with
> what"
> I think this only clouds the text and adds no meaning.
>
> > AB> please add>
> > MPLS-TP is a connection-oriented packet-switched transport layer
> > network technology, is a profile of the MPLS that supports deployment
> > in transport networks and allows operations in a manner consistent
> > with other transport technologies.
>
> For what purpose?
> Not every document has to include a base definition of everything it
> mentions.
>
> > AB> add> please mention that this definition of MPLS-TP by IETF will
> > allow consistent with other transport technologies defined by ITU-T.
>
> Something like...
>    This document provides a thesaurus for the interpretation of MPLS-TP
>    terminology within the context of the ITU-T Transport Network
>    Recommendations.
>
> Oh, that text is already there.
>
> > AB>In Section 1.2> please explain or add info:
> > In the document there are many abbreviations as CC, CE, ME, etc., but
> > not mentioned if these abbreviations are used in ITU-T as a common
> > abbreviation or are not, the IETF participant would like to know such
> > information in this thesaurus. Also the section prefered to say this
> > is the documents abbreviation (e.g. wondering why some have abbrv and
> > others have not within the thesaurus).
>
> The intention is not to explain the terms used in ITU-T Recommendations.
> That is
> out of scope.
>
> > Why authors used CC why not CCh as in other RFC? or does the CC has
> > been used in the ITU? please clarify why.
>
> -13 has tidied this up
>
> > AB> suggest> CC to be changed to MPLS-TP Comm Channel (MTCC) and also
> > all others related terms.
>
> That would be inventing a new term.
>
> > AB> some words are not clear related to terminologies and MPLS and ITU
> > concepts. As there are words not defined but abbreviated as: Network
> > Element (NE). Other words not defined as : Channel, path, point,
> > connection, .etc. The reviewer wants to know it under the context of
> > MPLS-TP and Transport Network concept as the draft aims to do but not
> > found by reviewer.
>
> Again, you are not expected to read this document and magically understand
> all
> of networking.
>
> You are supposed to read this document if you want to understand MPLS-TP
> terms
> in the context of ITU-T Recommendations. That implies that you possibly
> have
> some understanding of those Recommendations.
>
> > In ITU documents in abbreviation section, it mentions as this
> > recommendation abbreviation, this draft needs to mention that this is
> > its abbreviation as well.
>
> I don't understand.
> You want, "....network element (NE)..." to have some additional indication
> that
> "NE" is an abbreviation that means "network element"?
> And the inclusion in section 1.2 "Abbreviations" of a line that says "NE
> Network Element" is not enough?
>
> > Please refer to below editor abbreviation in section 2:
> > http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>
> Yes. You will notice that this I-D conforms to the guidance and this list
> of
> abbreviations.
>
> > The draft makes in its first page an abbreviation of IETF even though
> > it is mentioned in the webpage above of RFC editor.
>
> Golly, yes, so it does.
> Of course, you leave me to guess which abbreviation you are referring to
> which
> is immensely frustrating for me.
>
> I think we can leave it to the RFC Editor to worry about this sort of nit.
>
> > AB>no consistency> The ITU-T has no abbreviation but still document
> > mentions the IETF abbreviation while the IETF is our organisation and
> > ITU is not and both are in RFC editor as no need abbreviation. Also
> > MPLS is similar abbreviated in the document and the editor signals it
> > as known, but in document mentioned more than one time. The ITU
> > documents mentions the ITU abbreviation.
> >
> > I-D>Page 1>
> > Internet-Drafts are working documents of the Internet Engineering Task
> > Force (IETF)
>
> This is standard boilerplate and required to be present in exactly this
> format.
> Have you not noticed it on every other document you have read?
>
> The rule says what you do not need to expand, not what you must not expand.
>
> > AB> the document uses the word * see * to refer to document that has
> > the definition, but not refers to pages that has the definition. I
> > prefer not to refer, because this is a thesaurus so it is better to
> > explain with words and refer in the end of sentence as for example
> > pointing page in ref as [ITU-T_G.806, p4].
>
> It is common practice to not include the page number since electronic and
> searchable documents were first made available.
>
> > I-D> Section 2> Terminology:
> > ++++++++++++++++++++
> > AB>Discuss>
> > Section 2 needs an introduction, the reader does not know what is the
> > document terminology, we have two organisations IETF and ITU, two
> > sources of terminology and concepts that this document is considering
> > but it seems that is not clear mentioned in the section in details.
> > For example, Is the terms in the thesaurus taken from ITU documents or
> > from IETF? or both? and then are they defined in the context of ITU-T
> > or of Transport Network?
>
> You did not suggest what the introduction should say, and I don't see the
> need
> for an introduction. True, I don't like to see empty sections like this,
> but I
> don't think it is important or makes the document any harder to read.
>
> > AB> the sections 2.1 and 2.2 has references that are repeated in 2-3
> > which is confusing because it was thought that these sections show
> > d

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

I think authors/you=A0did not reply to all my review dated 17 October, and =
the new version 13 of the draft is dated 20 October before replying to my r=
eview on the list. The last call was for version 12 and the authors found m=
y review to help to update=A0fix without replying=A0to the review=A0with th=
e community. =A0I recommend always reply before submitting new drafts after=
 LC. I will not reply/discuss because I feel discouraged by authors.<div>
<br></div><div>The=A0reply saying fixed but not mentioned that my review re=
sult was before the discovery to fix, it seems like the reply is saying we =
fixed it before you reviewed or discovered the nits.<div><br></div><div>AB<=
br>
<br>On Sunday, October 27, 2013, Adrian Farrel  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Herewith a late response to your review comments.<br>
<br>
&gt; Overall Review:<br>
&gt; The reviewer decision is that the I-D is not ready to be publish<br>
&gt; because it does not achieve clearly its aim and objectives and subject=
<br>
&gt; to additional information and structure.<br>
<br>
The objective is quoted in the Abstract as:<br>
<br>
=A0 =A0This document provides a thesaurus for the interpretation of MPLS-TP=
<br>
=A0 =A0terminology within the context of the ITU-T Transport Network<br>
=A0 =A0Recommendations.<br>
<br>
=A0 =A0It is important to note that MPLS-TP is applicable in a wider set of=
<br>
=A0 =A0contexts than just Transport Networks. =A0The definitions presented =
in<br>
=A0 =A0this document do not provide exclusive nor complete interpretations<=
br>
=A0 =A0of MPLS-TP concepts. =A0This document simply allows the MPLS-TP term=
s<br>
=A0 =A0to be applied within the Transport Network context.<br>
<br>
I think the aim of &quot;providing a thesaurus&quot; *is* achieved by the d=
ocument.<br>
You have some suggestions below that can be considered, but the &quot;not r=
eady to be<br>
publish&quot; is an extreme reaction.<br>
<br>
&gt; This thesaurus is difficult<br>
&gt; to trace and gather information related to MPLS, even though it is<br>
&gt; informational draft.<br>
<br>
I wonder if you are using the document in the wrong way. You are supposed t=
o use<br>
this to look up terms, not educate yourself on MPLS.<br>
<br>
&gt; This draft&#39;s terminology section is not done in a<br>
&gt; methodology similar to RFC4397 in terms of showing separate resources<=
br>
&gt; in each subsection and relating to the document aim.<br>
<br>
That is correct.<br>
But saying &quot;I would not have done it like this&quot; is not very helpf=
ul.<br>
4397 presented material in a different way and for a different purpose.<br>
<br>
&gt; The title seems<br>
&gt; like the terminology of both documentations are made as thesaurus, but=
<br>
&gt; when we go into the I-D the reviewer feels it is not organised as a<br=
>
&gt; thesaurus to simplify search and relating terms or issues of MPLS-TP.<=
br>
<br>
Right, the title could be changed to match the quote from the Abstract that=
 I<br>
gave above. Thus:<br>
<br>
OLD<br>
=A0 =A0 =A0 =A0 A Thesaurus for the Terminology used in Multiprotocol Label=
<br>
=A0 =A0 =A0 =A0Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T&=
#39;s<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Transport Network Recommendations.<=
br>
NEW<br>
=A0 =A0 =A0 =A0 A Thesaurus for the Interpretation of Terminology used in<b=
r>
=A0 Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs<b=
r>
=A0 =A0 =A0in the Context of the ITU-T&#39;s Transport Network Recommendati=
ons<br>
END<br>
<br>
&gt; There are many terminology not clear but more general definition.<br>
<br>
That is not actionable as it stands, but I presume that the &quot;many&quot=
; are all in<br>
your more detailed comments below.<br>
<br>
&gt; I<br>
&gt; prefer specific defining to clarify to ALL Internet-Community not only=
<br>
&gt; specific readers (otherwise should mention that it is not for ALL<br>
&gt; community to understand).<br>
<br>
All RFCs are for ALL, but can often only be understood in the context of wi=
der<br>
reading.<br>
This document is a thesaurus for people to look things up. It is not someth=
ing<br>
you read and use to get an understanding of MPLS-TP.<br>
<br>
&gt; Also many times refers to references to<br>
&gt; define without mentioning what was that definition, is that defined<br=
>
&gt; only in ITU? is there an agreement that some one defines parts and<br>
&gt; other org defines other parts? why IETF draft cannot define its<br>
&gt; technology developed MPLS-TP? or is this draft agreeing on a joint<br>
&gt; definitions of many documents without clear methodology or IETF is<br>
&gt; just following ITU in some terms? The answers to these questions are<b=
r>
&gt; very important to make the thesaurus easy to trace.<br>
<br>
The paragraphs I quoted from the Abstract explains this.<br>
The purpose is to be able to look up a term found in an MPLS-TP draft/RFC a=
nd<br>
understand it in the context of the ITU-T Recommendations. Thus, often, it =
is<br>
sufficient to say something like:<br>
=A0 =A0See also [RFC6371] section 3.1 and [ITU-T G.8113.1],<br>
=A0 =A0[ITU-T G.8113.2] clause 6.1.<br>
I repeat: the purpose is not to explain the details of MPLS-TP. For that yo=
u<br>
must read a large set of RFCs.<br>
<br>
&gt; Draft methodology of definition and terminology:<br>
&gt; The way the draft starts a definition should not be refering to a<br>
&gt; reference, this makes the reader leave the document and distracted,<br=
>
&gt; and does not know where to go which page in such reference. In ITU-T<b=
r>
&gt; documents we find more organised which it defines and then refers to<b=
r>
&gt; the location of such definition but not the page which the reviewer<br=
>
&gt; prefers in such situation. Therefore, it is better for an IETF<br>
&gt; partcipant to understand the context and even get thesaurus-of-terms<b=
r>
&gt; when going through the some ITU-T documents (e.g. ITU-T G.8101/Y1355<b=
r>
&gt; (10/12) ) better than this ietf-draft, which means the IESG needs to<b=
r>
&gt; compare between this draft and ITU-T way of representing terms and<br>
&gt; defining them, to make a better draft representation facing other<br>
&gt; organisations, otherwise, people stop using this draft in future.<br>
<br>
Again, this misunderstands the purpose of the document.<br>
You cannot expect a 20 page document to explain MPLS-TP to you. For that, y=
ou<br>
must read either the set of MPLS RFCs or the set of ITU-T Recommendations.<=
br>
What this document does is help a reader who already knows the ITU-T<br>
Recommendations to read and understand the MPLS-TP RFCs.<br>
<br>
&gt; AB&gt;Question to authors&gt;<br>
&gt; Who is the reader: is this document only designed for IETF familiar<br=
>
&gt; RFCs readers or if someone from ITU refered by one document wants to<b=
r>
&gt; read this doc could he/she understand? (please note that ITU does<br>
&gt; refer people to this draft as this draft is defining some terms and<br=
>
&gt; they acknowledge).<br>
<br>
No change from what I have already said.<br>
<br>
&gt; In the reviewer&#39;s opinion it should mention this issue or who can =
read<br>
&gt; or what are the documents that should be read, because it was<br>
&gt; mentioned that this I-D is for IETF to get the ITU context.<br>
<br>
The paragraphs quoted from the Abstract makes this implicitly clear.<br>
<br>
&gt; I-D&gt; Scope and Applicability:<br>
&gt; ++++++++++++++++++++<br>
&gt; AB&gt; The scope is not clear because in the draft says:-<br>
&gt;<br>
&gt; I-D&gt;page 2&gt; in Abstract&gt;<br>
&gt; This document provides a thesaurus for the interpretation of MPLS-TP<b=
r>
&gt; terminology within the context of the ITU-T Transport Network<br>
&gt; recommendations.<br>
&gt;<br>
&gt; I-D&gt;page 4&gt; in Introduction&gt;<br>
&gt; This document provides a thesaurus for the interpretation of ITU-T<br>
&gt; Transport Network terminology within the context of the MPLS-TP.<br>
&gt;<br>
&gt; I-D&gt;page 17&gt; Section 4&gt;<br>
&gt; As discussed in the introduction to this document, this thesaurus is<b=
r>
&gt; intended to bring the concepts and terms associated with MPLS-TP<br>
&gt; into the context of the ITU-T&#39;s Transport Network architecture.<br=
>
&gt;<br>
&gt; AB&gt; The above objectives are not consistent scoped or not explained=
<br>
&gt; how and which context and terms are related and interpreted. The<br>
&gt; methodology of doing both is not clear, or even how they relate within=
<br>
&gt; the draft. The reviewer thinks there may be an editorial mistake, but<=
br>
&gt; still the scope was confused by that because terms were referenced to<=
br>
&gt; both RFCs and ITU-Gs.<br>
<br>
The authors fixed this in -13<br>
<br>
&gt; AB&gt; suggest adding&gt; The motivation of the scope is nice to menti=
on as<br>
&gt; done in RFC4397. However, it is easier to write scope/motivation of<br=
>
&gt; RFC4397 but not this draft because we want our participants to be<br>
&gt; familiar with other organisation&#39;s documents or concepts. I hope w=
e<br>
&gt; don&#39;t loose our participants to go work for ITU and stop participa=
ting<br>
&gt; in our IETF :-)<br>
<br>
I think you have still missed the point as stated in the quote from the<br>
Abstract.<br>
<br>
We are happy for people to do work in the appropriate standards bodies.<br>
<br>
&gt; I-D&gt; page 4&gt; This document provides a thesaurus for the interpre=
tation of<br>
ITU-T<br>
&gt; Transport Network terminology within the context of the MPLS-TP.<br>
&gt; This allows MPLS-TP documents to be generally understood by those<br>
&gt; familiar with MPLS RFCs.<br>
&gt; AB&gt;not clear why it allows understanding&gt; the reviewer thinks th=
at the<br>
&gt; draft&#39;s thesaurus does show pointers to ITU documents but does not=
<br>
&gt; deliver the specific definitions of thoes terminologies within the ITU=
<br>
&gt; nor within Transport Network context.<br>
<br>
Fixed in -13<br>
<br>
&gt; AB&gt; to strengthen the scope of the draft to make both ITU and IETF<=
br>
&gt; participant work on similar terminologies&gt; Add info:<br>
&gt; In past ITU-T developed extensions to MPLS developed by IETF to<br>
&gt; address the requirements of the transport network (T-MPLS). However,<b=
r>
&gt; concerns were raised by the IETF that the approach taken by the ITU-T<=
br>
&gt; was incompatible with widely deployed - MPLS - technology. Now both<br=
>
&gt; ITU and IETF have work together to set a next generation transport<br>
&gt; network technologies compatible with MPLS-TP.<br>
<br>
This may or may not be a true statement, but I don&#39;t see the value of i=
ncluding<br>
it in this document. It is far better to present a document for what it is =
and<br>
leave the politics outside the door if at all possible.<br>
<br>
&gt; AB&gt; Question&gt; Is there a discussion with the ITU Group responsib=
le<br>
&gt; about defining terms, because in one document of theirs they mention<b=
r>
&gt; something like some terms listed defined by IETF and some listed<br>
&gt; defined by ITU-T? (yes it is mentioned in acknowledgement about ITU<br=
>
&gt; and designe team, but not reflected or shown in the document scope).<b=
r>
&gt; Why is there different in concepts between MPLS-TP and the ITU<br>
&gt; Transport Network, if the MPLS-TP was developed to facilitate<br>
&gt; technologies within ITU transport Network context?<br>
<br>
There is nothing that can be done in an IETF document to make any changes t=
o the<br>
way the rest of the world operates and thinks. This document does its best =
by<br>
enabling a translation between those worlds.<br>
<br>
Various people from within the ITU-T reviewed this document in an attempt t=
o<br>
ensure it is correct. That was both helpful and diligent.<br>
<br>
If you want to understand or influence the way the ITU-T works, you need to=
 go<br>
there and talk with them.<br>
<br>
&gt; AB&gt; Questions&gt; Are the ITU documents under normative referencing=
 the<br>
&gt; last documents as up to date? and what are the affects of amendment of=
<br>
&gt; ITU documents are they like our RFCs. Therefore, the reviewer request<=
br>
&gt; all normative to be in force documents and =A0including any amendments=
<br>
&gt; if related to this I-D.<br>
<br>
The authors have cited the correct versions of the documents for the refere=
nces<br>
they needed to make.<br>
<br>
If you wish to understand the ITU-T documentation process, you need to go t=
o the<br>
ITU-T not the IETF.<br>
<br>
&gt; AB&gt; suggest&gt; Some documents of amendments are related but not<br=
>
&gt; referenced, such as amendments to ITU-T G.8101/Y1355 as [ITU-T<br>
&gt; G.8101/Y1355 (10/12)] in 2012. Please consider adding and refering to<=
br>
&gt; it.<br>
<br>
The citations are made to the documents that define the terms or contain th=
e<br>
text that is referenced.<br>
<br>
&gt; I-D&gt; Introduction Section&gt;<br>
&gt; +++++++++++++++++++<br>
&gt; I-D&gt;Multiprotocol Label Switching - Transport Profile (MPLS-TP) has=
 been<br>
&gt; =A0 =A0developed by the IETF to facilitate the Operation, Administrati=
on<br>
&gt; =A0 =A0and Management of Label Switched Paths (LSPs) in a Transport Ne=
twork<br>
&gt; =A0 =A0environment as defined by the ITU-T.<br>
&gt;<br>
&gt; AB&gt; the MPLS-TP is defined by IETF not by ITU-T, so prefer to make =
it<br>
&gt; clear in the paragraph. It can be understood: the IETF developed it as=
<br>
&gt; defined by ITU-T.<br>
<br>
The sentence is very clear, IMHO:<br>
- MPLS-TP developed in IETF<br>
- MPLS-TP facilitates LSPs in an environment defined by the ITU-T<br>
<br>
While it is clear that the paragraph could be understood in a number of way=
s, I<br>
do not believe that a misunderstanding can be easily achieved.<br>
<br>
&gt; AB&gt; amend to:<br>
&gt; Multiprotocol Label Switching - Transport Profile (MPLS-TP) has been<b=
r>
&gt; =A0 =A0developed and defined by the IETF to facilitate the Operation,<=
br>
Administration<br>
&gt; =A0 =A0and Management of Label Switched Paths (LSPs) for interoperabil=
ity<br>
&gt; in a Transport Network environment as defined by the ITU-T.<br>
<br>
You added &quot;and defined&quot;. That is a superfluous duplication of &qu=
ot;developed&quot;.<br>
<br>
You added &quot;for interoperability&quot;. Since you don&#39;t say &quot;i=
nteroperable with what&quot;<br>
I think this only clouds the text and adds no meaning.<br>
<br>
&gt; AB&gt; please add&gt;<br>
&gt; MPLS-TP is a connection-oriented packet-switched transport layer<br>
&gt; network technology, is a profile of the MPLS that supports deployment<=
br>
&gt; in transport networks and allows operations in a manner consistent<br>
&gt; with other transport technologies.<br>
<br>
For what purpose?<br>
Not every document has to include a base definition of everything it mentio=
ns.<br>
<br>
&gt; AB&gt; add&gt; please mention that this definition of MPLS-TP by IETF =
will<br>
&gt; allow consistent with other transport technologies defined by ITU-T.<b=
r>
<br>
Something like...<br>
=A0 =A0This document provides a thesaurus for the interpretation of MPLS-TP=
<br>
=A0 =A0terminology within the context of the ITU-T Transport Network<br>
=A0 =A0Recommendations.<br>
<br>
Oh, that text is already there.<br>
<br>
&gt; AB&gt;In Section 1.2&gt; please explain or add info:<br>
&gt; In the document there are many abbreviations as CC, CE, ME, etc., but<=
br>
&gt; not mentioned if these abbreviations are used in ITU-T as a common<br>
&gt; abbreviation or are not, the IETF participant would like to know such<=
br>
&gt; information in this thesaurus. Also the section prefered to say this<b=
r>
&gt; is the documents abbreviation (e.g. wondering why some have abbrv and<=
br>
&gt; others have not within the thesaurus).<br>
<br>
The intention is not to explain the terms used in ITU-T Recommendations. Th=
at is<br>
out of scope.<br>
<br>
&gt; Why authors used CC why not CCh as in other RFC? or does the CC has<br=
>
&gt; been used in the ITU? please clarify why.<br>
<br>
-13 has tidied this up<br>
<br>
&gt; AB&gt; suggest&gt; CC to be changed to MPLS-TP Comm Channel (MTCC) and=
 also<br>
&gt; all others related terms.<br>
<br>
That would be inventing a new term.<br>
<br>
&gt; AB&gt; some words are not clear related to terminologies and MPLS and =
ITU<br>
&gt; concepts. As there are words not defined but abbreviated as: Network<b=
r>
&gt; Element (NE). Other words not defined as : Channel, path, point,<br>
&gt; connection, .etc. The reviewer wants to know it under the context of<b=
r>
&gt; MPLS-TP and Transport Network concept as the draft aims to do but not<=
br>
&gt; found by reviewer.<br>
<br>
Again, you are not expected to read this document and magically understand =
all<br>
of networking.<br>
<br>
You are supposed to read this document if you want to understand MPLS-TP te=
rms<br>
in the context of ITU-T Recommendations. That implies that you possibly hav=
e<br>
some understanding of those Recommendations.<br>
<br>
&gt; In ITU documents in abbreviation section, it mentions as this<br>
&gt; recommendation abbreviation, this draft needs to mention that this is<=
br>
&gt; its abbreviation as well.<br>
<br>
I don&#39;t understand.<br>
You want, &quot;....network element (NE)...&quot; to have some additional i=
ndication that<br>
&quot;NE&quot; is an abbreviation that means &quot;network element&quot;?<b=
r>
And the inclusion in section 1.2 &quot;Abbreviations&quot; of a line that s=
ays &quot;NE<br>
Network Element&quot; is not enough?<br>
<br>
&gt; Please refer to below editor abbreviation in section 2:<br>
&gt; <a href=3D"http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.=
txt" target=3D"_blank">http://www.rfc-editor.org/rfc-style-guide/abbrev.exp=
ansion.txt</a><br>
<br>
Yes. You will notice that this I-D conforms to the guidance and this list o=
f<br>
abbreviations.<br>
<br>
&gt; The draft makes in its first page an abbreviation of IETF even though<=
br>
&gt; it is mentioned in the webpage above of RFC editor.<br>
<br>
Golly, yes, so it does.<br>
Of course, you leave me to guess which abbreviation you are referring to wh=
ich<br>
is immensely frustrating for me.<br>
<br>
I think we can leave it to the RFC Editor to worry about this sort of nit.<=
br>
<br>
&gt; AB&gt;no consistency&gt; The ITU-T has no abbreviation but still docum=
ent<br>
&gt; mentions the IETF abbreviation while the IETF is our organisation and<=
br>
&gt; ITU is not and both are in RFC editor as no need abbreviation. Also<br=
>
&gt; MPLS is similar abbreviated in the document and the editor signals it<=
br>
&gt; as known, but in document mentioned more than one time. The ITU<br>
&gt; documents mentions the ITU abbreviation.<br>
&gt;<br>
&gt; I-D&gt;Page 1&gt;<br>
&gt; Internet-Drafts are working documents of the Internet Engineering Task=
<br>
&gt; Force (IETF)<br>
<br>
This is standard boilerplate and required to be present in exactly this for=
mat.<br>
Have you not noticed it on every other document you have read?<br>
<br>
The rule says what you do not need to expand, not what you must not expand.=
<br>
<br>
&gt; AB&gt; the document uses the word * see * to refer to document that ha=
s<br>
&gt; the definition, but not refers to pages that has the definition. I<br>
&gt; prefer not to refer, because this is a thesaurus so it is better to<br=
>
&gt; explain with words and refer in the end of sentence as for example<br>
&gt; pointing page in ref as [ITU-T_G.806, p4].<br>
<br>
It is common practice to not include the page number since electronic and<b=
r>
searchable documents were first made available.<br>
<br>
&gt; I-D&gt; Section 2&gt; Terminology:<br>
&gt; ++++++++++++++++++++<br>
&gt; AB&gt;Discuss&gt;<br>
&gt; Section 2 needs an introduction, the reader does not know what is the<=
br>
&gt; document terminology, we have two organisations IETF and ITU, two<br>
&gt; sources of terminology and concepts that this document is considering<=
br>
&gt; but it seems that is not clear mentioned in the section in details.<br=
>
&gt; For example, Is the terms in the thesaurus taken from ITU documents or=
<br>
&gt; from IETF? or both? and then are they defined in the context of ITU-T<=
br>
&gt; or of Transport Network?<br>
<br>
You did not suggest what the introduction should say, and I don&#39;t see t=
he need<br>
for an introduction. True, I don&#39;t like to see empty sections like this=
, but I<br>
don&#39;t think it is important or makes the document any harder to read.<b=
r>
<br>
&gt; AB&gt; the sections 2.1 and 2.2 has references that are repeated in 2-=
3<br>
&gt; which is confusing because it was thought that these sections show<br>
&gt; d</blockquote></div></div>

--047d7b339c25861ffc04e9bf7202--

From lear@cisco.com  Sun Oct 27 14:14:32 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 7E6BE11E82AA for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.428
X-Spam-Level: 
X-Spam-Status: No, score=-110.428 tagged_above=-999 required=5 tests=[AWL=0.171, 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 QsfYqRDiBKJT for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:14:27 -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 0C1FA11E82BB for <ietf@ietf.org>; Sun, 27 Oct 2013 14:14:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1427; q=dns/txt; s=iport; t=1382908464; x=1384118064; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6u7zSvJYVBut6hrMKNYrbSDNBtLpgUTqV45IFRuV5JQ=; b=ekqd6ala6CpYoBeoDHMooHE64IJG5ZShGHxz+NuKgq5ByiOsxTvPrVxu SajjB1blgCs7PwfRF26qyblXGBk7cuMiaT/N97lTvg9IaEsxIkVjkQQUv 70GBo9A+5KmKLAu4W+zDOyY5Lu1m3+neZFE2JTZrQrqUJNjQKm4AASDj9 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAHSBbVKQ/khR/2dsb2JhbABZgweEH7hRgnqBHBZ0giUBAQEDASNCEwEFCwsOCgICBRYEBwICCQMCAQIBKxoGDQEHAQGHfQaleJIXgSmOLAeCaoFCA5gKkgeBaIE/Ow
X-IronPort-AV: E=Sophos;i="4.93,581,1378857600"; d="scan'208";a="161075971"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 27 Oct 2013 21:14:22 +0000
Received: from mctiny.local ([10.61.199.95]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9RLEHim015450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Oct 2013 21:14:19 GMT
Message-ID: <526D8229.6090809@cisco.com>
Date: Sun, 27 Oct 2013 22:14:17 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <52552DFA.9030904@cisco.com> <526CED81.2000204@qti.qualcomm.com>
In-Reply-To: <526CED81.2000204@qti.qualcomm.com>
X-Enigmail-Version: 1.5.2
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, 27 Oct 2013 21:14:32 -0000

Hi Pete,

Thanks for your reply.  Please see below.

On 10/27/13 11:40 AM, Pete Resnick wrote:
> On 10/9/13 5:20 AM, Eliot Lear wrote:
>> 1.  No matter how you slice the definition of rough consensus, if the
>> chair does not act in a fair and balanced way, the outcome will be
>> incorrect.  This is what the appeals process is for, and I would suggest
>> mentioning it, perhaps in some detail.
>>    
>
> I do allude to this at the end of section 3, and I've highlighted it a
> bit better with one of the edits Dave suggested. But every time I
> tried to elaborate the "detail", I found myself talking more about the
> theory of appeals rather than the theory of consensus. I'm open to
> some suggested text if you have some.

If you've got an updated version I'd take another look.  On further
reflection, tho, detail might lead to precisely what you're concerned
about.  What I was really aiming at was this:

> The fact is that though rough consensus is a resilient process, it's
> not bulletproof to every attack. This document can only go so far into
> how it deals with problems. I've added a good bit to that section to
> address Ted's comments. Hopefully you find that satisfying.
>

Those sentences are excellent.  I think your point about looking at the
charter is key, because there is advice to area directors hidden there
about being clear on what is supposed to be done.

Eliot


From julian.reschke@gmx.de  Sun Oct 27 14:18:12 2013
Return-Path: <julian.reschke@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 A531921F9BC1 for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.909
X-Spam-Level: 
X-Spam-Status: No, score=-102.909 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 QrcvkrwRx9vP for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:18:12 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 3723311E82AA for <ietf@ietf.org>; Sun, 27 Oct 2013 14:18:09 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.109.236]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MHMRr-1VWSzv09bP-00E9t9 for <ietf@ietf.org>; Sun, 27 Oct 2013 22:18:04 +0100
Message-ID: <526D830E.60704@gmx.de>
Date: Sun, 27 Oct 2013 22:18:06 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p1-messaging.all@tools.ietf.org, iesg@ietf.org
Subject: IANA URIS, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:smUHjtbpzsvS6tCdLhD923Qh/J5Z0jo8G3oS+kM7MGv50Un0UA7 bcyxGv/MGOHIEDusTOW4vsbERlp055JTyFvfowudBKUS50m948VGgotOwWcbqCbpRlqzU8E bbIAFDisy0Jz+iaup5EfJsVAoSo0Ra1C8aKr/wi0t14c/tJ/jounjZlMJdHDDLuyWo69lWO KIyu5JdUSZrpWUwyg4sWA==
Cc: ietf-http-wg@w3.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, 27 Oct 2013 21:18:12 -0000

On 2013-10-27 19:44, S Moonesamy wrote:
> ...
> Nits:
>
> For Section 8.1, the Message Header Field Names registry is at
> http://www.iana.org/assignments/message-headers/
>
> For Section 8.2, the URI Schemes registry is at
> http://www.iana.org/assignments/uri-schemes/
> ...

Ack.

Out of curiosity: is there an obvious way to find out what the 
"canonical" URI of a registry is?

Best regards, Julian


From adrian@olddog.co.uk  Sun Oct 27 14:31:06 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 EC64011E81C1; Sun, 27 Oct 2013 14:31:06 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUNq5gsPGM3J; Sun, 27 Oct 2013 14:31:01 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id C73DA11E8142; Sun, 27 Oct 2013 14:31:00 -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 r9RLUwsY018250;  Sun, 27 Oct 2013 21:30:58 GMT
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 r9RLUuZb018230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 27 Oct 2013 21:30:57 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
References: <17ad01ced311$5c6cebf0$1546c3d0$@olddog.co.uk> <CADnDZ89Pggius+O5SnJ75fQYy96oyYb4EK6nrd30RuEAL9e2Fw@mail.gmail.com>
In-Reply-To: <CADnDZ89Pggius+O5SnJ75fQYy96oyYb4EK6nrd30RuEAL9e2Fw@mail.gmail.com>
Subject: RE: Last Call: <draft-ietf-mpls-tp-rosetta-stone-12.txt> (A Thesaurus for the Terminology used in Multiprotocol Label Switching Transport Profile (MPLS-TP) drafts/RFCs and ITU-T's Transport Network Recommendations.) to Informational RFC
Date: Sun, 27 Oct 2013 21:30:56 -0000
Message-ID: <181f01ced35b$d36bb8e0$7a432aa0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDyllSRBMHWHmgKYXoxcZ4tOKW7XgDjCYQTm7pviGA=
Content-Language: en-gb
Cc: 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: Sun, 27 Oct 2013 21:31:07 -0000

> I think authors/you=A0did not reply to all my review dated 17 October,

Really?
If you look carefully you will find that I replied at considerable =
length to
every point you made in your lengthy review.

> and the new version 13 of the draft is dated 20 October
> before replying to my review on the list.=20

Sure. And why not?
The authors saw your comments and updated the document. What more could =
you
possibly want?

> The last call was for version 12 and the authors found
> my review to help to update=A0fix without replying=A0to the
> review=A0with the community.

Right.
How wonderful for you that your comments were adopted by the authors.

>=A0I recommend always reply before submitting new drafts
> after LC.=20

An interesting recommendation that people may take at face value.

> I will not reply/discuss because I feel discouraged by authors.

That is entirely your choice.
I don't know that I could say anything that would not discourage you =
further.

> The=A0reply saying fixed but not mentioned that my review
> result was before the discovery to fix,

Frankly, I don't care about that. Your objective was to get the document
changed. The document was changed. You should be happy.

> it seems like the reply is saying we fixed it before you reviewed
> or discovered the nits.

I understand that that is how it seems to you.
But it doesn't say that.
I would positively die of boredom if every time I typed (to anyone) =
"fixed in
version -xx" I had to type "this has been fixed in version -xx, as a =
result of
your careful and most excellent review."

Some of us don't have the luxury to be discouraged by our email =
exchanges. Some
of us have the joy to be an AD and type long and painful responses to =
emails.
Some of us don't get a note saying "Thank you for responding to my =
review and
updating the document to take into account my comments."

I really must say that none of this is cultural or related to remote
participation. It is frankly annoying.

Adrian






From olaf@NLnetLabs.nl  Mon Oct 28 00:43:11 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 425C511E821E for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 00:43:11 -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=[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 N+d83MEPA98b for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 00:43:10 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8EA21F9477 for <ietf@ietf.org>; Mon, 28 Oct 2013 00:43:07 -0700 (PDT)
Received: from dhcp-64.nlnetlabs.nl (dhcp-64.nlnetlabs.nl [213.154.224.64]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r9S7gNRa033637 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 28 Oct 2013 08:42:25 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r9S7gNRa033637
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1382946182; bh=WPepOM/IDW5ilK1P+YDNplAY4bVPDhdswfog4IjrNtA=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=iSEJfE5ge0YY3pOKB24BwsrGn3UmwrGEgNvBKZ7EhLfGYZVzKcUutA7zJpDV4xW51 dOiWTTrF+4Ui9Ou8WMsK/57Z5lKvOxiHFb/2cOGwssFcfkV9ufmC9RxQFfdBPTTNDe MOinJuw9q6hYZ7M1g3T0VCFBoJMyNnzedk1SyrdA=
Content-Type: multipart/signed; boundary="Apple-Mail=_13D904EF-B63E-41A2-BFE2-F9F263166485"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: On anonymity.... (was: Sergeant at arms: please deal with mars.techno.cat@gmail.com)
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <5266CE7C.2020503@gmail.com>
Date: Mon, 28 Oct 2013 08:42:22 +0100
Message-Id: <636654F2-248D-4CEF-A4A9-24F4BAB79993@NLnetLabs.nl>
References: <5262FB95.8080500@gmail.com>	<CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com>	<52657B0B.3080701@gmail.com>	<m21u3d5zvo.wl%randy@psg.com>	<5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Mon, 28 Oct 2013 08:42:26 +0100 (CET)
Cc: John C Klensin <john-ietf@jck.com>, "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: Mon, 28 Oct 2013 07:43:11 -0000

--Apple-Mail=_13D904EF-B63E-41A2-BFE2-F9F263166485
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_9FC3A926-6051-487B-B09A-C10206FC4FE3"


--Apple-Mail=_9FC3A926-6051-487B-B09A-C10206FC4FE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 22 okt. 2013, at 21:14, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

>=20
> If you look at my original complaint to Jordi, anonymity was not =
mentioned.
> I only raised it when asked  why I requested action. And I agree: =
anonymity
> in itself is not a problem.
>=20
> Anonymity + irrelevance is a problem, in my opinion.


I=92ve raised this before, but Brian=92s mail triggered me to bring it =
up again:

IMHO, anonymity and technical contributions in the IETF are a problem =
too. The IETF policy on IPR breaks down if you do not know who to go =
after if contributions made by anonymous persons turn out to be tainted =
after standardization. =20

Anonymity in a debate that doesn=92t lead or influences a standard =
action is not a problem (the merit of the argument counts).


=97Olaf

--Apple-Mail=_9FC3A926-6051-487B-B09A-C10206FC4FE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On 22 okt. 2013, at 21:14, Brian E =
Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;">If you look at my original complaint to Jordi, anonymity =
was not mentioned.</span><br style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;">I only raised it when asked &nbsp;why I requested action. =
And I agree: anonymity</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: =
none; display: inline !important;">in itself is not a problem.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;"><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><span style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;">Anonymity + irrelevance is a =
problem, in my opinion.</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"></blockquote></div><div><br></div><div>I=92ve raised this before, =
but Brian=92s mail triggered me to bring it up =
again:</div><br><div>IMHO, anonymity and technical contributions in the =
IETF are a problem too. The IETF policy on IPR breaks down if you do not =
know who to go after if contributions made by anonymous persons turn out =
to be tainted after standardization. =
&nbsp;</div><div><br></div><div>Anonymity in a debate that doesn=92t =
lead or influences a standard action is not a problem (the merit of the =
argument =
counts).</div><div><br></div><div><br></div><div>=97Olaf</div></body></htm=
l>=

--Apple-Mail=_9FC3A926-6051-487B-B09A-C10206FC4FE3--

--Apple-Mail=_13D904EF-B63E-41A2-BFE2-F9F263166485
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBAgAGBQJSbhVeAAoJEFRqER47aqpkPPUP/2puFADQWbnMDCqksvhcwYi5
8Tgx2bfO4YW6mkCr//SNKvCDs63nQhSp2bYlJHWkHNn2wZohz6se4iDeaadVXqWY
KY965yrSFAHTL+wd33O9qsFBelPX3tnWK69SjIIJk6UdsNvpxxanhqwmYbmt83Fp
zV9wQme/+5cwZnIbj/oXdjjTS/SwK6ctDdRUQjoOu5ny76qNNE2D6coCtDKQTng7
ZGuRVq835tYaKIWhpiQPa8yK1QJCCa46/h40F5rF40E2d6j4cDjRp0mWQ3LpDBbo
+OheQUX3ri1rWDkwOInVBMX3bYd1tChoGxEFivt4L9Zw0FRaUfCRSjpLCAAFbIQw
XYCc05c8RK6aIY+okv4NMnqG2EoAU2NcKoMzh604Me8DEnvPM8rPJtW6RsALG/0+
g11DwmYD4zBiKF1Xng++cHJqmnoJLX/3Nl7zDKCAOoZ3H0sisqklqmRSlvmIS9gd
6V3VAoW9X4B2MO6uSRACLWMinHBkVk12wcIad0+t8c9aAjU0NG/GkjdAn+WIHkf9
jnYOK1sXppqPPE/Y2DiNPOSV1Su0oZAy1jkyibWaxfbYiG5oAQjZykmsXdPllbhh
d0XpA5NJALxnXIpBIPcdsz8McTdHCs7WyeriFn2UBBlJwTATmIrrBGh5yE8KsyCH
lFhuoOzwlBYDkY1K65Nq
=T4sT
-----END PGP SIGNATURE-----

--Apple-Mail=_13D904EF-B63E-41A2-BFE2-F9F263166485--

From sm@elandsys.com  Mon Oct 28 01:08:26 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 2904221F9F40; Mon, 28 Oct 2013 01:08:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.235
X-Spam-Level: 
X-Spam-Status: No, score=-102.235 tagged_above=-999 required=5 tests=[AWL=0.364, 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 gpcZ1rZvTNQF; Mon, 28 Oct 2013 01:08:25 -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 B965C11E8151; Mon, 28 Oct 2013 01:08:23 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.154.55]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9S8879B021796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Oct 2013 01:08:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382947700; bh=brm049+R5VV06af1eqFZ9hamPFoFEA6dnx7Q7QmH8ss=; h=Date:To:From:Subject:Cc; b=Va4BOaKL5W/mkUcnX/Dw4Su0UnEQ1j1DAsu+vGR9vXuVY5R8Z27D1QeH/i4v3GSAW X2KVv+hykMFBj6nsWCrrLsOsyFC2WF4U4clk9s/eBMa7L/4wxpblRNYbBmLg6Ue++u dPgEG34HBnMDLbXRTE8xIUsI0IGOpPR0RuqFTge0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382947700; i=@elandsys.com; bh=brm049+R5VV06af1eqFZ9hamPFoFEA6dnx7Q7QmH8ss=; h=Date:To:From:Subject:Cc; b=aE/7bY1UE+i/v732xpJnwchDiIUUNR/PgUs6O5nNxqn4Rw9uf3H0XZCW/R9A8Qe1/ BJ0d5I5DBXCRAJVEcYb1apsQdgjDY4EpA56nIugauEqwICLKd74An3fH4rI5SYbj+s wgba1w8QA7W7B+DdnK8myep64IBSSD0Blj8pXwkQ=
Message-Id: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Oct 2013 01:07:31 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 28 Oct 2013 08:08:26 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p2-semantics-24
Title: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Reviewer: S. Moonesamy
Review Date: October 28, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft is almost ready for publication as a Proposed Standard.

This document defines the semantics of HTTP/1.1 messages, as 
expressed by request methods, request header fields, response status 
codes, and response header fields, along with the payload of messages 
(metadata and body content) and mechanisms for content negotiation.

The draft is well-written and clear.

Major Issues:

In Section 3.1.1.5:

   'If a Content-Type header field is not present, the recipient MAY
    either assume a media type of "application/octet-stream" ([RFC2046],
    Section 4.5.1) or examine the data to determine its type.'

According to RFC 2046, the "octet-stream" subtype is used to indicate 
that a body contains arbitrary data.  The RFC 2119 "may" leaves it to 
the implementor to make an assumption.  I suggest turning this into a 
recommendation so that the assumption is clear to the 
implementor.  There is a discussion of MIME sniffing in 
draft-ietf-websec-mime-sniff-03.  There has been discussion about 
MIME or Content sniffing over the years.  I am aware that some 
browsers do MIME sniffing.  I understand that it is sometimes needed 
to make the Web work.  However, it can lead to security 
vulnerabilities.  The paragraph which follows the one quoted above 
discusses about that.  I listed this as a major issue for the 
attention of the Applications Area Directors.

Minor Issues:

In Section 5.5.1:

   'The "From" header field contains an Internet email address for a
    human user who controls the requesting user agent.  The address ought
    to be machine-usable, as defined by "mailbox" in Section 3.4 of
    [RFC5322]:'

The above text is similar to text which was in RFC 2068 and RFC 
2616.  The "mailbox" may also contain a display name whereas the 
"addr-spec" (see Section 3.4.1) is an Internet mail address.  I 
listed this issue as minor to flag it for the attention of the 
HTTPbis Working Group.

In Section 5.5.3:

   "a sender MUST NOT generate advertising or other non-essential information
    within the product identifier"

I suggest having the text as guidance together with an explanation 
instead of a RFC 2119 prohibition.

In Section 7.1.1:

   "The preferred format is a fixed-length and single-zone subset of
    the date and time specification used by the Internet Message Format
    [RFC5322]"

The ABNF imports obs-date from RFC 5322.  "GMT" is defined in 
"obs-zone" (see RFC 5322).  There is the following in the section:

   "For example, messages are occasionally forwarded over HTTP from a
    non-HTTP source that might generate any of the date and time
    specifications defined by the Internet Message Format."

I listed this as a minor issue.  I am not suggesting any change as 
"GMT" is used in other header fields.  I'll defer to the HTTPbis 
Working Group as to whether there should be a note about "GMT" with 
an explanation that although "GMT" is deprecated the use is widespread.

Section 8.1 defines a HTTP Method Registry where registration 
requires IETF Review.  I took a quick look at Issue #364.  Section 
4.2 discusses about common method properties, e.g. cacheable.  The 
fields in Section 8.1.1 does not include cacheable.

There are considerations for new methods in Section 8.1.2.  I gather 
that the working group understands that someone will have to review 
the specification and raise an issue if the considerations are not followed.

The table in Section 8.1.3 only mentions the section number.  There 
is an assumption that the specification text is in this draft.  I 
suggest also adding a reference for the RFC number.  As a note for 
the reader, draft-ietf-httpbis-method-registrations-13 also registers 
some HTTP methods.

The above assumption also applies to Section 8.2.  I suggest updating 
the existing registrations at 
http://www.iana.org/assignments/http-status-codes/ so that the
HTTP Status Code Registry is compliant with Section 8.2.1.

Nits:

In Section 5.5.2:

  "Referer allows servers to generate back-links to other resources for"

  "information disclosure in Referer ought to restrict their changes to"

I'll defer to the editors as to whether to add "header field".

I suggest changing the RFC 1305 reference in Section 7.1.1.1 to RFC 5905.

In Section 8.3.1:

   'Authors of specifications defining new fields are advised to keep the
    name as short as practical and to not prefix the name with "X-"
    unless the header field will never be used on the Internet.'

I suggest adding a reference to BCP 178.

Regards,
S. Moonesamy


From sm@elandsys.com  Mon Oct 28 02:08:47 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 1740711E823F; Mon, 28 Oct 2013 02:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.253
X-Spam-Level: 
X-Spam-Status: No, score=-102.253 tagged_above=-999 required=5 tests=[AWL=0.346, 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 ie2wYN4qJoeG; Mon, 28 Oct 2013 02:08:42 -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 169FE11E816F; Mon, 28 Oct 2013 02:08:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.154.55]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9S980lA006556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Oct 2013 02:08:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382951292; bh=RTWj+YlCGGUUF8pMLP4Xpuq4W3lahx23+PKodWDnPQ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OQpYNsCYGcXnMapOZ0GzXX1ibjsymNCBLeYFDtwT5Omd3ur7NHWev7mx8ezQNuM/Z Tva+7VTBg7KLF7uvcTmSU6Vgk/c8dPi85KzBlXatwoX25fn4Mi7893ohf4BQGhX4s6 CQgC+g3BGTFLsZa6CaLAj8ybJYI7PSwui9hvA8/s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382951292; i=@elandsys.com; bh=RTWj+YlCGGUUF8pMLP4Xpuq4W3lahx23+PKodWDnPQ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=T8uDyrvWzLkVXM3itlJ3UuIdL2hV47cKlAkR+6gfsEFyR1jNFxPrRm0WBRHZfxr4S 6UTwqYLRVEfbAsiMugCIwB2T9SYWiqlejUKJGviEFU83Ht+WHaX1Gn69cFsqKECh99 sA4n2UovYHIY7cAm1FTHy/Z7O8jZEO6A3KTs6oAQ=
Message-Id: <6.2.5.6.2.20131028015520.0d6cd4d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Oct 2013 02:06:16 -0700
To: Julian Reschke <julian.reschke@gmx.de>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IANA URIS, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
In-Reply-To: <526D830E.60704@gmx.de>
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com> <526D830E.60704@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.org, apps-discuss@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, 28 Oct 2013 09:08:47 -0000

Hi Julian,
At 14:18 27-10-2013, Julian Reschke wrote:
>Out of curiosity: is there an obvious way to find out what the 
>"canonical" URI of a registry is?

There was a comment from IANA about its intention to keep 
http://www.iana.org/assignments/example format working.  The obvious 
way is to drop the file name and extension (e.g. 
http://www.iana.org/assignments/uri-schemes ).

Regards,
S. Moonesamy 


From sm@elandsys.com  Mon Oct 28 02:23:16 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 1CC9011E8239 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.268
X-Spam-Level: 
X-Spam-Status: No, score=-102.268 tagged_above=-999 required=5 tests=[AWL=0.331, 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 8pWTJ4xu4usw for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 02:23: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 BCA4711E8254 for <ietf@ietf.org>; Mon, 28 Oct 2013 02:22:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.154.55]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9S9MY0D020347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Oct 2013 02:22:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1382952167; bh=q9T48aAMFiSgRcyLgAdxEPhbj8ThfSRG+M/eNv3E478=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RIv5zVl5WIqicCe4rZCd3lja5htOwkd+ezOEqYN3IP9/VqjJrlv97HpGtHnkRzbEN DJNK/H6PYMdQHmzhIq9Z1OgV6NzIDsqoq7dPpFOUM8tznCNzDah4zmNP/T+poomh/B gaKD2SKNROPoUMA2P1fnoPjrvjo5lrN6XVP/0vA8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1382952167; i=@elandsys.com; bh=q9T48aAMFiSgRcyLgAdxEPhbj8ThfSRG+M/eNv3E478=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ClnKWn63zaUowgZprqF+j/kfjV4OKvP22Xug/b824hPcB6AcSe4wjJpAG630FVNSE DGmNq6ffR/7p+hjeMsD+4wWcmTsO0xcN0k3nuwfUqGdAzzTu1H4C76fBlau3qyCRyB +a77VQHGvm/VpXrxogLdAdKZiTegsHzB3pF/FmGM=
Message-Id: <6.2.5.6.2.20131028020857.0d755388@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Oct 2013 02:21:24 -0700
To: Julian Reschke <julian.reschke@greenbytes.de>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
In-Reply-To: <526D804F.9080104@greenbytes.de>
References: <20131021130716.29482.49323.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131026135545.0ccefbc0@resistor.net> <526D804F.9080104@greenbytes.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.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, 28 Oct 2013 09:23:18 -0000

Hi Julian,
At 14:06 27-10-2013, Julian Reschke wrote:
>I have no preference here and will await what the IESG will say :-)

Ok. :-)

>Our charter has prohibited us from adding new things to the 
>protocol. There are many things (methods, status codes, header 
>fields) that we *could* add, but in the end, that's why we have registries.

I am okay with the above comment about the protocol.  I commented 
about the registries in another message.  Some of the registries 
might have to be updated.  In my opinion the charter would not 
prohibit registration updates.

>I believe that keeping new things in separate specs encourages 
>people to use the registries instead of relying on a specific set of 
>documents to provide the complete picture (today this already is a 
>problem - people believing that things not described on 2616 are not 
>"pure" HTTP).

I suggest using the same STD for the set of documents.  It might 
lessen the above problem over time.

Regards,
S. Moonesamy 


From julian.reschke@gmx.de  Mon Oct 28 03:31:22 2013
Return-Path: <julian.reschke@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 CDAE621F9DBA for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 03:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.397
X-Spam-Level: 
X-Spam-Status: No, score=-103.397 tagged_above=-999 required=5 tests=[AWL=-0.797, 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 1Ti4oBUF2bvK for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 03:31:15 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 97A5611E8147 for <ietf@ietf.org>; Mon, 28 Oct 2013 03:31:10 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MTeVY-1VANVj40lU-00QRby for <ietf@ietf.org>; Mon, 28 Oct 2013 11:31:09 +0100
Message-ID: <526E3CE6.2020103@gmx.de>
Date: Mon, 28 Oct 2013 11:31:02 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
References: <20131021130716.29482.49323.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131026135545.0ccefbc0@resistor.net> <526D804F.9080104@greenbytes.de> <6.2.5.6.2.20131028020857.0d755388@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131028020857.0d755388@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:PjYvXNTVTGDuP2BvEgDbkpI8lkPQppl7m7ojWG138RZ4XI6hSNT p+PxJQEY6MRu03/X8eIjouu2sy+gRIKmXatiFhMcNfqjoM/s9Ty+9iGRor8Bx2aTKIyawKk Dom0oNYfZVaqTCgRtbILf/oAz4IYgzDfrufWMzbu/VBYSQK/kMUVumiQoXgPa6uG3HrZHKe aTrxn38Ac6vcjGLP/qwiA==
Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.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, 28 Oct 2013 10:31:23 -0000

On 2013-10-28 10:21, S Moonesamy wrote:
> ...
>> I believe that keeping new things in separate specs encourages people
>> to use the registries instead of relying on a specific set of
>> documents to provide the complete picture (today this already is a
>> problem - people believing that things not described on 2616 are not
>> "pure" HTTP).
>
> I suggest using the same STD for the set of documents.  It might lessen
> the above problem over time.

-1.

We have registries for exactly that purpose. They provide much better 
control and granularity than including RFCs into document sets.

Best regards, Julian

From ron.even.tlv@gmail.com  Mon Oct 28 03:47:23 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 3914311E811A; Mon, 28 Oct 2013 03:47:23 -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.073,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pgfHzePOXkad; Mon, 28 Oct 2013 03:47:22 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B908E11E8138; Mon, 28 Oct 2013 03:47:18 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id ey11so3621775wid.6 for <multiple recipients>; Mon, 28 Oct 2013 03:47:17 -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 :thread-index:content-language; bh=CJv2Bfn0qmrBjMXI/jNp9acqK1qWu/m+H/mxQNkETG4=; b=ExyKPnMn+873p+ZQGhnClk+HpZUK1qpwdMRZDEqJTWl5XOxjEe2Cz7h7OqIfMBbfdn L9HP+GpQvo4agXbo+RoKmRRg7G5k2vLNDpl9Ct4D1Ny0dREUZkES+UWIKVynowqNq5+R CQsH+/otjTxlm+VDPBnG4UrNR/zKWSzgSLUTX0ySxuJd87/K9OREjY5vKHsup1+9ZyFU a/PygVgx1IWMwoZ4uR28pcXtlhGfq3kW4CfuOk0Nr9h+jpVcff+QdyxC4QKv5Dgi/sa9 JTRXcHfJZLyNkcsyin9HH1/Kje7skP7Q2LiyDBnqoiM27ZlDYY3cR1tx4MQr1fONsB8I ek9w==
X-Received: by 10.180.94.38 with SMTP id cz6mr8432257wib.27.1382957237799; Mon, 28 Oct 2013 03:47:17 -0700 (PDT)
Received: from RoniE (bzq-79-181-191-27.red.bezeqint.net. [79.181.191.27]) by mx.google.com with ESMTPSA id nc17sm9171940wic.1.2013.10.28.03.47.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 28 Oct 2013 03:47:17 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-nfsv4-labreqs.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-nfsv4-labreqs-04
Date: Mon, 28 Oct 2013 12:44:03 +0200
Message-ID: <017c01ced3ca$a1189380$e349ba80$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_017D_01CED3DB.64A1FFC0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac7TypsSaY7BYWH+TserRMvn+rXbGg==
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, 28 Oct 2013 10:47:23 -0000

This is a multipart message in MIME format.

------=_NextPart_000_017D_01CED3DB.64A1FFC0
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-nfsv4-labreqs-04

Reviewer: Roni Even

Review Date:2013-10-28

IETF LC End Date: 2013-11-1

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as an Informational RFC.

 

 

Major issues:

Minor issues:

The document is not a requirement document. It is a use case, requirement
and solution document so the abstract and the title are confusing.

I think it will be better to have the use case section before the
requirements in section 3. Since the use cases are the reason for the rest
of the document.

Section 3 is called requirements but it is not about requirements from a
solution but also normative text about behavior of clients and servers.

This leads to the question why is it Informational document since it has
normative recommendations for a solution.

I also think that there is a need for IANA section to discuss requirements
for new LFSs.

Nits/editorial comments:

 

 


------=_NextPart_000_017D_01CED3DB.64A1FFC0
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;}
--></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-nfsv4-labreqs-04</span><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;10&#8211;28<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-11&#8211;1<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 an Informational =
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=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>The =
document is not a requirement document. It is a use case, requirement =
and solution document so the abstract and the title are =
confusing.<o:p></o:p></p><p class=3DMsoNormal>I think it will be better =
to have the use case section before the requirements in section 3. Since =
the use cases are the reason for the rest of the =
document.<o:p></o:p></p><p class=3DMsoNormal>Section 3 is called =
requirements but it is not about requirements from a solution but also =
normative text about behavior of clients and servers.<o:p></o:p></p><p =
class=3DMsoNormal>This leads to the question why is it Informational =
document since it has normative recommendations for a =
solution.<o:p></o:p></p><p class=3DMsoNormal>I also think that there is =
a need for IANA section to discuss requirements&nbsp; for new =
LFSs.<o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_017D_01CED3DB.64A1FFC0--


From julian.reschke@gmx.de  Mon Oct 28 07:00:55 2013
Return-Path: <julian.reschke@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 C620021F9EFB for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 07:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.437
X-Spam-Level: 
X-Spam-Status: No, score=-103.437 tagged_above=-999 required=5 tests=[AWL=-0.838, 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 EG4NfIMhbmx7 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 07:00:50 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id BFB2B11E8278 for <ietf@ietf.org>; Mon, 28 Oct 2013 07:00:38 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MPlMc-1VefFF2q1K-0054MB for <ietf@ietf.org>; Mon, 28 Oct 2013 15:00:23 +0100
Message-ID: <526E6DF4.4030509@gmx.de>
Date: Mon, 28 Oct 2013 15:00:20 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: obs-date, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:ZXVOGkTI2j3w1GEu/Av7gTS8tPAtUU0a75sXjnjU8mwRepRiiYl 50rMLyqOpTNmPkMebPTCK1vmGmitQX0AWT+lQ/iXHJtcBadH/fa1TCxjzAVmWKRaQTMzkqb D1vgn+qzzAlH7o7IBxnVZxBS4kn7UwJdEkfV2eHh+Ry/lUbRQgu9aMm0EYN28U8jz0YphIz tDpOgt9wn2RHxTJe1EnGA==
Cc: ietf@ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Oct 2013 14:00:55 -0000

On 2013-10-28 09:07, S Moonesamy wrote:
> ...
> In Section 7.1.1:
>
>    "The preferred format is a fixed-length and single-zone subset of
>     the date and time specification used by the Internet Message Format
>     [RFC5322]"
>
> The ABNF imports obs-date from RFC 5322.  "GMT" is defined in "obs-zone"
> (see RFC 5322).  There is the following in the section:
>
>    "For example, messages are occasionally forwarded over HTTP from a
>     non-HTTP source that might generate any of the date and time
>     specifications defined by the Internet Message Format."
>
> I listed this as a minor issue.  I am not suggesting any change as "GMT"
> is used in other header fields.  I'll defer to the HTTPbis Working Group
> as to whether there should be a note about "GMT" with an explanation
> that although "GMT" is deprecated the use is widespread.
> ...

Actually, HTTPbis has its own obs-date:

	obs-date     = rfc850-date / asctime-date

<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-24.html#rfc.section.7.1.1.1>

So there doesn't seem to be an issue here.

Best regards, Julian

From john-ietf@jck.com  Mon Oct 28 07:22:38 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 D22B711E8306; Mon, 28 Oct 2013 07:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.553
X-Spam-Level: 
X-Spam-Status: No, score=-103.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 6d6nixOdLFLS; Mon, 28 Oct 2013 07:22:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 89B0B11E817E; Mon, 28 Oct 2013 07:22:31 -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 1Vani6-000F6i-Ds; Mon, 28 Oct 2013 10:22:26 -0400
Date: Mon, 28 Oct 2013 10:22:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review of	draft-ietf-httpbis-p2-semantics-24
Message-ID: <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com>
In-Reply-To: <526E6DF4.4030509@gmx.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de>
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-http-wg@w3.org, 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: Mon, 28 Oct 2013 14:22:38 -0000

--On Monday, October 28, 2013 15:00 +0100 Julian Reschke
<julian.reschke@gmx.de> wrote:

> On 2013-10-28 09:07, S Moonesamy wrote:
>> ...
>> In Section 7.1.1:
>> 
>>    "The preferred format is a fixed-length and single-zone
>>    subset of the date and time specification used by the
>>     Internet Message Format [RFC5322]"
>...
> Actually, HTTPbis has its own obs-date:
> 
> 	obs-date     = rfc850-date / asctime-date
> 
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semant
> ics-24.html#rfc.section.7.1.1.1>

Julian,

I've been reluctant to step into this mess, but, having had
another bad experience over the weekend, and with the
understanding that we already have multiple "obsolete" forms
floating around that implementations are supposed to recognize,
I'd like to see if it is still possible to think about moving to
an ISO-compatible "preferred form" that would eliminate the
difficulty in handling and ambiguities in month names (and the
frequent violations where they are made upper-case or translated
into local languages).   Doing so, and getting rid of "GMT"
(which about half the world's population seems to think is a
synonym for whatever time is being used around Greenwich), in
favor of UT (which no one who has any understanding at all seems
to think might change in the summer), would save a lot of
problems long-term.  That would make the preferred form

  [day-name ","] year "-" monthNumber "-" day SP time-of-day SP
"UT"

  with 
   monthNumber = 2DIGIT

  and
   	obs-date = rfc850-date / asctime-date / IMF-fixdate
if that is necessary.

I don't care whether day-name is optional or not, but there
would be some small i18n charm in saying "either write it the
way the spec says or leave it out" rather than the current rule,
which is effectively "use those English-based abbreviations no
matter how obnoxious they are in your environment".

It is obviously late to be suggesting this, but it was also late
a dozen years ago and will be a lot later five or ten years
hence.

best,
   john




From julian.reschke@gmx.de  Mon Oct 28 07:25:13 2013
Return-Path: <julian.reschke@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 7EA3211E8341 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 07:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.502
X-Spam-Level: 
X-Spam-Status: No, score=-103.502 tagged_above=-999 required=5 tests=[AWL=-0.903, 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 mTkdYngat+G7 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 07:25:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 9172711E833C for <ietf@ietf.org>; Mon, 28 Oct 2013 07:25:00 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MAQMg-1VPDxB15TO-00Bctz for <ietf@ietf.org>; Mon, 28 Oct 2013 15:24:59 +0100
Message-ID: <526E73B8.90705@gmx.de>
Date: Mon, 28 Oct 2013 15:24:56 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review of	draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com>
In-Reply-To: <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:eR1YS/+kR5/Iqm7iPi3jNH0k7t2pA4oa+81Kdtbiek/Tx2KWyqK OqKCHigtzUNY8XRq0SE3Z7oLAtm2PCKFyGGYqzvnda+huDU7hx1yBpYj3R4/CWTDjRdQ3zr 2CyQ4Y/WgesG4z0mAygKgnIfu3bcTKnoj3ekw4XdcUgHHNwJLyMTWfc5ONgXyX81rAt4OIj uWv8Ix8SdHCd8mWtcHk2g==
Cc: ietf-http-wg@w3.org, 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: Mon, 28 Oct 2013 14:25:13 -0000

On 2013-10-28 15:22, John C Klensin wrote:
> --On Monday, October 28, 2013 15:00 +0100 Julian Reschke
> <julian.reschke@gmx.de> wrote:
>
>> On 2013-10-28 09:07, S Moonesamy wrote:
>>> ...
>>> In Section 7.1.1:
>>>
>>>     "The preferred format is a fixed-length and single-zone
>>>     subset of the date and time specification used by the
>>>      Internet Message Format [RFC5322]"
>> ...
>> Actually, HTTPbis has its own obs-date:
>>
>> 	obs-date     = rfc850-date / asctime-date
>>
>> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semant
>> ics-24.html#rfc.section.7.1.1.1>
>
> Julian,
>
> I've been reluctant to step into this mess, but, having had
> another bad experience over the weekend, and with the
> understanding that we already have multiple "obsolete" forms
> floating around that implementations are supposed to recognize,
> I'd like to see if it is still possible to think about moving to
> an ISO-compatible "preferred form" that would eliminate the
> difficulty in handling and ambiguities in month names (and the
> frequent violations where they are made upper-case or translated
> into local languages).   Doing so, and getting rid of "GMT"
> (which about half the world's population seems to think is a
> synonym for whatever time is being used around Greenwich), in
> favor of UT (which no one who has any understanding at all seems
> to think might change in the summer), would save a lot of
> problems long-term.  That would make the preferred form
>
>    [day-name ","] year "-" monthNumber "-" day SP time-of-day SP
> "UT"
>
>    with
>     monthNumber = 2DIGIT
>
>    and
>     	obs-date = rfc850-date / asctime-date / IMF-fixdate
> if that is necessary.
>
> I don't care whether day-name is optional or not, but there
> would be some small i18n charm in saying "either write it the
> way the spec says or leave it out" rather than the current rule,
> which is effectively "use those English-based abbreviations no
> matter how obnoxious they are in your environment".
>
> It is obviously late to be suggesting this, but it was also late
> a dozen years ago and will be a lot later five or ten years
> hence.
> ...

John,

that change would make almost every HTTP/1.1 code ever written 
non-compliant.

And yes, it would have been nice if a same date format would have been 
chosen back then.

Best regards, Julian

From avri@ella.com  Fri Oct 25 22:16:22 2013
Return-Path: <avri@ella.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E09C121E80D8 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 22:16: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 33rF7lam6fR2 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2013 22:16:17 -0700 (PDT)
Received: from atl4mhob12.myregisteredsite.com (atl4mhob12.myregisteredsite.com [209.17.115.50]) by ietfa.amsl.com (Postfix) with ESMTP id 7743021E80CF for <ietf@ietf.org>; Fri, 25 Oct 2013 22:16:17 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob12.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r9Q5GGUl018004 for <ietf@ietf.org>; Sat, 26 Oct 2013 01:16:16 -0400
Received: (qmail 2325 invoked by uid 0); 26 Oct 2013 05:16:16 -0000
X-TCPREMOTEIP: 72.37.242.11
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO vpn-cust-10-119-1-118.witopia.net) (avri@ella.com@72.37.242.11) by 0 with ESMTPA; 26 Oct 2013 05:16:15 -0000
Subject: Re: IGOVUPDATE session
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/signed; boundary="Apple-Mail=_DB8D14DA-2F38-4796-8E28-4B1537152E57"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Avri Doria <avri@ella.com>
In-Reply-To: <501C806C-B95C-4604-8C7E-BDE297E554A6@ietf.org>
Date: Sat, 26 Oct 2013 13:16:12 +0800
Message-Id: <E7675B14-96DC-454F-8AEC-1482BE1F54BE@ella.com>
References: <501C806C-B95C-4604-8C7E-BDE297E554A6@ietf.org>
To: IETF Chair <chair@ietf.org>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Mon, 28 Oct 2013 07:55:45 -0700
Cc: Andrew Sullivan <ajs@crankycanuck.ca>, "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: Sat, 26 Oct 2013 05:16:23 -0000

--Apple-Mail=_DB8D14DA-2F38-4796-8E28-4B1537152E57
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Sounds like a good session.

I look forward to it.

avri

On 25 Oct 2013, at 17:21, IETF Chair wrote:

> In Orlando, the IAB held a session on what had been going at WCIT. =
While this was not a matter of technical work for the IETF, we all did =
recognise the impact of policies, treaties, and governance structures on =
the Internet. The feedback from the session was positive, and I have =
asked the IAB to arrange similar sessions in some upcoming meetings when =
and if there is interesting issues to hear about.
>=20
> In Vancouver we have reserved a slot for "IGOVUPDATE". We had =
originally planned the topic for this time to be DNS-related policy =
issues, largely from the areas where IETF and ICANN efforts meet. =
However, since then there has been many developments and proposals in =
the Internet governance space, I think largely inspired by the recent =
revelations on pervasive monitoring. Or enabled by the discussion =
climate caused by them.
>=20
> With this in mind, we'll begin the session by talking about =
WHOIS/WEIRDS and how policies discussed around them may affect the =
protocol design. But after that we will also provide a report from the =
IGF (Internet Governance Forum) meeting that is being held this week. =
And finally, discuss whether additional work is needed and if so, how =
that might be organised.
>=20
> The agenda for the meeting is at =
http://www.ietf.org/proceedings/88/agenda/agenda-88-igovupdate and the =
chairs of the session are Marc Blanchet and Andrew Sullivan.
>=20
> Jari
>=20
>=20


--Apple-Mail=_DB8D14DA-2F38-4796-8E28-4B1537152E57
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBAgAGBQJSa1AcAAoJEOo+L8tCe36H+3cIAK4618rT2ezbNrMzQyVlQqy7
WgU4Me9VSkc3pOEQwSPNvGSXFhoPzQy9wJUhJoLpKDAjLzxm8AfbdKqv5Lho3OMJ
KZzqh9OJ+ST8B0++KAaDBaNY6XCEpX5RIhi6+coX+Vn7ift91NVtC6ACa495/57i
h2/cIALTs6RcXhLTc094SxAjX1JcoXS7g9K1Vhg6CLN2uZfSMYwwrfiTI7WPkkjx
4qD4tvCTyFtLUFmnsqa9Q0A4YWueXBB/mhc5wnf4dSEn4+oTMxGuZPZ1950+mXkp
/NkVPmzJ4zMSep5tWGHWRtBdCzUZrq4TuNTMfVQYd5U0eEyk3nvXmbUKgpswM/0=
=R/YA
-----END PGP SIGNATURE-----

--Apple-Mail=_DB8D14DA-2F38-4796-8E28-4B1537152E57--

From julian.reschke@greenbytes.de  Sun Oct 27 14:06:44 2013
Return-Path: <julian.reschke@greenbytes.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 5A29311E82C2 for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 ONjSKPBOA3TZ for <ietf@ietfa.amsl.com>; Sun, 27 Oct 2013 14:06:38 -0700 (PDT)
Received: from central.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by ietfa.amsl.com (Postfix) with ESMTP id F352111E82B4 for <ietf@ietf.org>; Sun, 27 Oct 2013 14:06:37 -0700 (PDT)
Received: from [192.168.2.117] (unknown [93.217.109.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by central.greenbytes.de (Postfix) with ESMTPSA id D977410C00F9; Sun, 27 Oct 2013 22:06:20 +0100 (CET)
Message-ID: <526D804F.9080104@greenbytes.de>
Date: Sun, 27 Oct 2013 22:06:23 +0100
From: Julian Reschke <julian.reschke@greenbytes.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-httpbis-p1-messaging-24.txt> (Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing) to Proposed Standard
References: <20131021130716.29482.49323.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131026135545.0ccefbc0@resistor.net>
In-Reply-To: <6.2.5.6.2.20131026135545.0ccefbc0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 28 Oct 2013 07:56:03 -0700
Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Oct 2013 21:06:44 -0000

On 2013-10-27 00:37, S Moonesamy wrote:
> At 06:07 21-10-2013, The IESG wrote:
>> The IESG has received a request from the Hypertext Transfer Protocol Bis
>> WG (httpbis) to consider the following document:
>> - 'Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing'
>>   <draft-ietf-httpbis-p1-messaging-24.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-11-04. Exceptionally, comments may be
>
> In Section 1:
>
>    'This HTTP/1.1 specification obsoletes and moves to historic status
>     RFC 2616, its predecessor RFC 2068, and RFC 2145 (on HTTP
>     versioning).  This specification also updates the use of CONNECT to
>     establish a tunnel, previously defined in RFC 2817, and defines the
>     "https" URI scheme that was described informally in RFC 2818.'
>
> RFC 2616 is currently a Draft Standard.  According to RFC 2026:
>
>    "A Draft Standard must be well-understood and known to be quite
>     stable, both in its semantics and as a basis for developing an
>     implementation."
>
> And:
>
>    "A Draft Standard is normally considered to be a final specification,
>     and changes are likely to be made only to solve specific problems
>     encountered.  In most circumstances, it is reasonable for vendors to
>     deploy implementations of Draft Standards into a disruption sensitive
>     environment."
>
> Given that draft-ietf-httpbis-p1-messaging-24 and the other drafts in
> the series is an update of RFC 2616 it is appropriate to move that RFC
> to Obsolete.  The drafts in the series is a substantial revision
> (according to the Document Shepherd). I can understand moving a Proposed
> Standard to Historic.   I read the thread about Issue #254 [1].  I
> didn't find much discussion about moving the specification (RFC 2616)
> which is supposed to be stable to Historic.  What are the implications
> of doing that?

I have no preference here and will await what the IESG will say :-)

> RFC 2616 is updated by RFC 6266 and RFC 6585.  As a note there is about
> explanation about RFC 6266 in draft-ietf-httpbis-p2-semantics-24.  In my
> opinion it is worth considering whether the HTTP status codes specified
> in RFC 6585 should be included in draft-ietf-httpbis-p2-semantics-24.
> That RFC could be included in the series if it is less work.
> ...

Our charter has prohibited us from adding new things to the protocol. 
There are many things (methods, status codes, header fields) that we 
*could* add, but in the end, that's why we have registries.

I believe that keeping new things in separate specs encourages people to 
use the registries instead of relying on a specific set of documents to 
provide the complete picture (today this already is a problem - people 
believing that things not described on 2616 are not "pure" HTTP).

> ...

Best regards, Julian

From julian.reschke@greenbytes.de  Mon Oct 28 07:14:54 2013
Return-Path: <julian.reschke@greenbytes.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 6B3EB11E818C; Mon, 28 Oct 2013 07:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 o3jfRxiLuB8A; Mon, 28 Oct 2013 07:14:50 -0700 (PDT)
Received: from central.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by ietfa.amsl.com (Postfix) with ESMTP id 5CE6F11E8185; Mon, 28 Oct 2013 07:14:48 -0700 (PDT)
Received: from [192.168.1.102] (unknown [217.91.35.233]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by central.greenbytes.de (Postfix) with ESMTPSA id 9F53510C0665; Mon, 28 Oct 2013 15:14:46 +0100 (CET)
Message-ID: <526E7154.2070005@greenbytes.de>
Date: Mon, 28 Oct 2013 15:14:44 +0100
From: Julian Reschke <julian.reschke@greenbytes.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 28 Oct 2013 07:56:15 -0700
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 28 Oct 2013 14:14:54 -0000

On 2013-10-28 09:07, S Moonesamy wrote:
> ...
> Section 8.1 defines a HTTP Method Registry where registration requires
> IETF Review.  I took a quick look at Issue #364.  Section 4.2 discusses
> about common method properties, e.g. cacheable.  The fields in Section
> 8.1.1 does not include cacheable.
> ...

Yes -- this is not necessarily a problem. There are many things that 
need to be defined for a new method, and not all of these fit into the 
template.

> There are considerations for new methods in Section 8.1.2.  I gather
> that the working group understands that someone will have to review the
> specification and raise an issue if the considerations are not followed.

Yes.

> The table in Section 8.1.3 only mentions the section number.  There is
> an assumption that the specification text is in this draft.  I suggest

That's an assumption that is true for all "bare" Section references.

> also adding a reference for the RFC number.  As a note for the reader,
> draft-ietf-httpbis-method-registrations-13 also registers some HTTP
> methods.

The IANA Considerations are processed by the RFC Editor and IANA, and 
they will make sure that the registry is properly populated. There's no 
point in mentioning a still unknown RFC # here.

> The above assumption also applies to Section 8.2.  I suggest updating
> the existing registrations at
> http://www.iana.org/assignments/http-status-codes/ so that the
> HTTP Status Code Registry is compliant with Section 8.2.1.
> ...

What, precisely?

 > ...

Best regards, Julian

-- 
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782

From rdroms@cisco.com  Fri Oct 25 12:56:53 2013
Return-Path: <rdroms@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 15B6E11E81CF; Fri, 25 Oct 2013 12:56:53 -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 vM3MTXPOvVWj; Fri, 25 Oct 2013 12:56:46 -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 3B01B11E81CB; Fri, 25 Oct 2013 12:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2095; q=dns/txt; s=iport; t=1382731003; x=1383940603; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1LWoRS4K09YN3RZ7H0On+224HuK6MVj3iNgzQKwe+Hk=; b=BqUjDoZx4sOHb3825q6wt3CmmIsgrJjEzuOBm+c0Hm3siaY6vJtYPPSC +QsG+bDMC83+iNKlOQN5zUaRDkiBwmGrgP5UgAie516lLYyDds0Beab7g aJXyzRAfEGQq8YFhOPgl5Do8LpNm6kFrsEIf1QE3N0UK7ByVSWToDwoMM 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAGvMalKtJV2Z/2dsb2JhbABZgweBDL5IgSMWdIImAQEEOjQLEAIBCCIUBQsyJQIEDgUIh3+5VI4bgQUCMQeDH4ENA6oRgWiBPoIq
X-IronPort-AV: E=Sophos;i="4.93,572,1378857600"; d="scan'208";a="273781249"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 25 Oct 2013 19:56:42 +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 r9PJug6M029987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Oct 2013 19:56:42 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.229]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Fri, 25 Oct 2013 14:56:42 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-roll-trickle-mcast-05.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
Thread-Index: AQHO0bxTB8hb4i6HYEmq/bFuLj8olw==
Date: Fri, 25 Oct 2013 19:56:42 +0000
Message-ID: <4518F39EB578034D8C99A9B7776CDBA301C0651B@xmb-aln-x04.cisco.com>
References: <20131010221713.891.32620.idtracker@ietfa.amsl.com> <B594A37B-51F9-44FD-9E45-56D273657E89@gmail.com>
In-Reply-To: <B594A37B-51F9-44FD-9E45-56D273657E89@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.68.183]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7980C149C96C0545807856C9D47B5268@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 28 Oct 2013 07:57:47 -0700
Cc: "roll@ietf.org" <roll@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 19:56:53 -0000

There was a long discussion about this issue on the roll@ietf.org mailing l=
ist:

draft-ietf-roll-trickle-mcast-05 and draft-ietf-6man-multicast-scopes-00 ar=
e in conflict with each other.

>From draft-ietf-roll-trickle-mcast-05:

  When
  used with MPL, Realm-Local scope is administratively defined and used
  to define the boundaries of multicast message dissemination by MPL.

>From draft-ietf-6man-multicast-scopes-00:

  Realm-Local scope is the largest scope that is automatically
  configured, i.e., automatically derived from physical
  connectivity or other, non-multicast-related configuration.

Specifically, "administratively defined" seems to me to be in direct
conflict with "automatically configured".=20

I think I've read consensus in the various discussion threads to make the f=
ollowing change to draft-ietf-roll-trickle-mcast-05:

OLD:

   When
   used with MPL, Realm-Local scope is administratively defined and used
   to define the boundaries of multicast message dissemination by MPL.

NEW:

   When
   used with MPL, Realm-Local scope is defined according to the
   underlying network technology; for example, [cite the
   IP-over-IEEE802.15.4 definition].

where "the IP-over-IEEE802.15.4 definition" is text to be published elsewhe=
re (perhaps draft-ietf-6man-multicast-scopes) that defines scop 3 for IEEE8=
02.15.4 mesh networks.

I read less strong consensus (less discussion) of the following proposed ch=
anges:

NEW (to be added immediately following text describing the use of Realm-Loc=
al scope):

  Admin-Local scope (scop value 4) can also be used with MPL
  in deployments that use administratively defined scopes that
  cover, for example, multiple subnets based on different
  underlying network technologies.

As a side note, there is a related discussion about draft-ietf-6man-multica=
st-scopes on the 6man@ietf.org mailing list.  The term "Realm-Local scope" =
may change (should be changed for consistency with) the final published ver=
sion of draft-ietf-6man-multicast-scopes.

- Ralph


From julian.reschke@gmx.de  Mon Oct 28 08:53:48 2013
Return-Path: <julian.reschke@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 84A7311E8123 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 08:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.664
X-Spam-Level: 
X-Spam-Status: No, score=-103.664 tagged_above=-999 required=5 tests=[AWL=-1.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 BCvnTy-VoELO for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 08:53:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 96AA811E8160 for <ietf@ietf.org>; Mon, 28 Oct 2013 08:53:32 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0ME47n-1VStpU2KCN-00HRi1 for <ietf@ietf.org>; Mon, 28 Oct 2013 16:53:31 +0100
Message-ID: <526E8878.5030903@gmx.de>
Date: Mon, 28 Oct 2013 16:53:28 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p1-messaging.all@tools.ietf.org, iesg@ietf.org
Subject: Registration requirements for transfer codings, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:GtjsAsQSBG12szQraAuAVqDD6ILQ1EkUd8PodYJLAsgNbC5zuzD jPjPG7rTURE21Ttoa5xwp6GnRCMdwuLKERLoxFp7eaZ/bRCQuUyLa+ttGTJVH1U7Jgoixpy ii4zRvMx8y7+bQn5qQ+UwRzpQ9V6WmCbiIPKnd3R1rlYmPBqx4S7a6Wv84NQUzWziCS3OCL uzPmwJhqGNAsh7xeOuUpw==
Cc: ietf-http-wg@w3.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, 28 Oct 2013 15:53:48 -0000

On 2013-10-27 19:44, S Moonesamy wrote:
> ...
> The HTTP Transfer Coding namespace (Section 8.4) is currently "First
> Come First Served".  The new registration procedure required IETF
> Review.  What is the reason for the change?
> ...

My understanding is that we wanted to set a high bar because this really 
ought to happen with lots of care and review.

The related ticket is 
<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/188>, and it was 
discussed during IETF 75 
(<http://tools.ietf.org/wg/httpbis/minutes?item=minutes75.html>).

Best regards, Julian

From julian.reschke@gmx.de  Mon Oct 28 09:07:34 2013
Return-Path: <julian.reschke@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 50F6821E8087 for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 09:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.729
X-Spam-Level: 
X-Spam-Status: No, score=-103.729 tagged_above=-999 required=5 tests=[AWL=-1.130, 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 yTR7wRAnvwgl for <ietf@ietfa.amsl.com>; Mon, 28 Oct 2013 09:07:18 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 85D7E21E8093 for <ietf@ietf.org>; Mon, 28 Oct 2013 09:07:11 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MSZ6u-1V9R7W1A5E-00RZNR for <ietf@ietf.org>; Mon, 28 Oct 2013 17:06:58 +0100
Message-ID: <526E8B9E.8030006@gmx.de>
Date: Mon, 28 Oct 2013 17:06:54 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:OX2SmICE6RLyyPAUSoCDiZEiMQgMhF5A1nKL3t4M7PAG5qUq1MI E7A/VDmJvRG5rcUHlFLDX5oFyyLKrOvVNYDZSCcL1N6JMCQYhnZcrc/pVM8eODAz9kd3djk u6gIbl5BWSPBUhQybmiID0X9kWFR3WkeOLQHpCAYDgfQcds6skNmrEvKhCQ0/ILtQDXmcmw vqVb0x82Cx6/Ec2jtBviA==
Cc: ietf@ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Oct 2013 16:07:35 -0000

On 2013-10-28 09:07, S Moonesamy wrote:
> ...
> Major Issues:
>
> In Section 3.1.1.5:
>
>    'If a Content-Type header field is not present, the recipient MAY
>     either assume a media type of "application/octet-stream" ([RFC2046],
>     Section 4.5.1) or examine the data to determine its type.'
>
> According to RFC 2046, the "octet-stream" subtype is used to indicate
> that a body contains arbitrary data.  The RFC 2119 "may" leaves it to
> the implementor to make an assumption.  I suggest turning this into a
> recommendation so that the assumption is clear to the implementor.
> There is a discussion of MIME sniffing in
> draft-ietf-websec-mime-sniff-03.  There has been discussion about MIME

(which expired ~2 years ago)

> or Content sniffing over the years.  I am aware that some browsers do
> MIME sniffing.  I understand that it is sometimes needed to make the Web
> work.  However, it can lead to security vulnerabilities.  The paragraph
> which follows the one quoted above discusses about that.  I listed this
> as a major issue for the attention of the Applications Area Directors.
> ...

Could you clarify what exactly the issue is?

RFC 2616 said 
(<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1.p.4>):

> Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. If the media type remains unknown, the recipient SHOULD treat it as type "application/octet-stream".

...which isn't that different.

Best regards, Julian

From john-ietf@jck.com  Mon Oct 28 12:22:34 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 95DC511E82BD; Mon, 28 Oct 2013 12:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.652
X-Spam-Level: 
X-Spam-Status: No, score=-103.652 tagged_above=-999 required=5 tests=[AWL=-0.053, 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 R26Tm19qVgvM; Mon, 28 Oct 2013 12:22:28 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A3DEC11E81D0; Mon, 28 Oct 2013 12:22:28 -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 1VasOL-000FSQ-Qw; Mon, 28 Oct 2013 15:22:21 -0400
Date: Mon, 28 Oct 2013 15:22:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review of	draft-ietf-httpbis-p2-semantics-24
Message-ID: <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com>
In-Reply-To: <526E73B8.90705@gmx.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com> <526E73B8.90705@gmx.de>
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-http-wg@w3.org, 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: Mon, 28 Oct 2013 19:22:34 -0000

--On Monday, October 28, 2013 15:24 +0100 Julian Reschke
<julian.reschke@gmx.de> wrote:

> 
> John,
> 
> that change would make almost every HTTP/1.1 code ever written
> non-compliant.
> 
> And yes, it would have been nice if a same date format would
> have been chosen back then.

Julian,

I don't know enough of the issues in enough detail to argue
this, and won't.  My goal is only to be sure the question has
been asked.

My understanding is that the HTTPbis work is a rather major
revision with at least some cases for which "get it right" is
more important that complete backward compatibility, especially
if there is a clear migration path.  All of the usual arguments
for that are relevant, especially the ones that focus on how
many implementations and pages are likely to be created in the
future relative to those that exist today.   Here, the clear
migration path would be a narrow and restrictive "send syntax"
and a permissive "receive syntax" that requires support of all
known older forms, _especially_ those that were recommended by
HTTP 1.1.

It has been rather longer than I think we expected, but it was
clear when HTTP 1.1 was adopted (I am sure it was clear at least
to the relevant ADs) that there could be incompatible changes in
the future and that the concern should be a non-disruptive
migration path, not absolute forward compatibility.  That is one
of the several reasons why the successor to HTTP 1.0 was
identified as HTTP 1.1, not HTTP 2.

This sort of change would still make HTTP 1.1 implementations
non-compliant with HTTP 2.0, but that is ok -- they still comply
with HTTP 1.1 and I hope no one is going to claim that all HTTP
1.1 implementations are non-compliant with HTTP the day HTTP 2.0
is published.

If the WG has considered these options and rejected them after
an open discusssion, please ignore the comment/ suggestion.

> And yes, it would have been nice if a same date format would
> have been chosen back then.

Yes, even for the mail header syntax that inspired the current
form and that predates the web by more than a decade.  But that
was before there was an ISO Standard, few of us were worried
about the year 2000 transition, etc.  My practical concern is
that, as we internationalize more, those perfectly
well-specified ASCII month and day names will get mapped, by
implementations who consider the local (and sometimes paying)
customers far more important than any standard, into local names
that no one else can read.   That would be fine if the local
forms stayed local, but we have lots of experience, including
with email, to indicate that they will leak and cause at least
user confusion if not interoperability problems.

So, from my point of view, this isn't about introducing an
incompatibility with something that one merely regrets not being
done differently.  It is rather more about what might be the
last chance to get it right and, in the process, eliminate
completely predictable future confusion and interoperability
problems.

  best,
   john


   john


From sm@elandsys.com  Tue Oct 29 01:14: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 D7D8821E80E8; Tue, 29 Oct 2013 01:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.787
X-Spam-Level: 
X-Spam-Status: No, score=-101.787 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcw6fCsYsUDy; Tue, 29 Oct 2013 01:14:02 -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 D106E21E80E3; Tue, 29 Oct 2013 01:13:59 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.158.76]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9T8DiNJ027720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 01:13:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383034438; bh=6KdK3rpcs8xdhcnxt+PY1yyGglmuACeGuHczbpk1isE=; h=Date:To:From:Subject:Cc; b=pYM7aPD0/MEPUMyPxsU75C29/mmo3k+HSsbzFUbgZmeqrwK8K52ipBOelSR6pAuDt 33Wuv93dgns8gFEUQ+14NkS0OUeNQqGdnFENg/uw05SMew5QaBRZM6Hn5bYO+1mL7z YM0sBYAXbQ2iFcjzFcctADjy1oPPxCcvEV0hUa4o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383034438; i=@elandsys.com; bh=6KdK3rpcs8xdhcnxt+PY1yyGglmuACeGuHczbpk1isE=; h=Date:To:From:Subject:Cc; b=x/kcJg7ydD5/LxJXogNoulYrTEgiurksFh0YHXTO2TeQSRd6JYK4mKjEcV1Gkwx+b Yye7Hi2YBShiQ63U4YbKNOdhqMjdyfxAbo3smo1tqfpwS1RQ3OcucVg5V3MJN0rUqm 4fxFshtgOjLTDSB2f6R2u2y8+6CQ3nB/mzggIOG0=
Message-Id: <6.2.5.6.2.20131028082531.0ddd0810@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Oct 2013 10:10:30 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p4-conditional.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p4-conditional-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 29 Oct 2013 08:14:03 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p4-conditional-24
Title: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
Reviewer: S. Moonesamy
Review Date: October 28, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft is almost ready for publication as a Proposed Standard.

This document defines HTTP/1.1 conditional requests, including 
metadata header fields for indicating state changes, request header 
fields for making preconditions on such state, and rules for 
constructing the responses to a conditional request when one or more 
preconditions evaluate to false.

The document is well-written and clear.

Major Issues:

In Section 2.2:

   Last-Modified = HTTP-date

There is a note about the imported ABNF in Appendix B.  I suggest 
moving that text to Section 1.2 so that the text is part of the specification.

Minor Issues:

I will comment about the IANA Considerations section in a separate message.

Nits:

Editorial comments were not included in the review.

Regards,
S. Moonesamy


From sm@elandsys.com  Tue Oct 29 01:14:17 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 4CE3121E80FB; Tue, 29 Oct 2013 01:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.779
X-Spam-Level: 
X-Spam-Status: No, score=-101.779 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SpVzzguiNa56; Tue, 29 Oct 2013 01:14:16 -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 296E221E80E6; Tue, 29 Oct 2013 01:14:04 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.158.76]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9T8DiNL027720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 01:14:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383034443; bh=FuN3oWHkH3mXWXWvN78EMK2XYiaeFjCbWsX8+9AeOWM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4AgwH5Isfq6e4odAmWCp7KgHZp3kYFWSY+uZQPQsJZ49Q6a4l0f87BqSoN3fRzW72 wyVcfJtK5IGReZVV2OypYcEXX7wHp5c/Ggm9v2dYbl6w4igSyqjLphI/XcPyNc2h01 FmzyzqA2upfthSIPudy3rKHMmYSSwVPkHSIVEvmg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383034443; i=@elandsys.com; bh=FuN3oWHkH3mXWXWvN78EMK2XYiaeFjCbWsX8+9AeOWM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1ZV8r1TYVsBQx1VbspzW03fRQeadnRHEu9FjnGSEZUYnMYDruJo48YtPJygGejdEm KmdnhypnQ6ZrfBBvhwnEitXWSjFZv2cRBl8poOnfbkREN2dGzzLajLPGBIeHbGd8fC cvdYXcy4T6uxCETXyiVSPveuXBskyR4G7YbXXgmM=
Message-Id: <6.2.5.6.2.20131028091247.0e37b9d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Oct 2013 09:55:10 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p1-messaging.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
In-Reply-To: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 29 Oct 2013 08:14:17 -0000

Hello,

While I was reviewing other drafts in the set I noticed that Section 
3.2.4 of draft-ietf-httpbis-p1-messaging-24 has the following:

   "Historically, HTTP header field values could be extended over
    multiple lines by preceding each extra line with at least one space
    or horizontal tab (obs-fold).  This specification deprecates such
    line folding except within the message/http media type
    (Section 8.3.1).  A sender MUST NOT generate a message that includes
    line folding (i.e., that has any field-value that contains a match to
    the obs-fold rule) unless the message is intended for packaging
    within the message/http media type."

There is an IETF specification which interpreted Section 4.2 of RFC 
2616 as follows:

   "the HTTP header syntax allows extending single header values across
    multiple lines, by inserting a line break followed by whitespace"

I'll classify deprecating line folding as an issue.

Section 4.2 of RFC 2616 (and RFC 2068) follows the same generic 
format as that given in Section 3.1 of RFC 822.  Section 2.2 of RFC 
2616 states that:

   "HTTP/1.1 header field values can be folded onto multiple lines if the
    continuation line begins with a space or horizontal tab."

I suggest that implementors of specifications which have a dependency 
on RFC 2616 review the relevant section in 
draft-ietf-httpbis-p1-messaging-24 about line folding and comment if 
they consider the deprecation as a problem.

Regards,
S. Moonesamy


From sm@elandsys.com  Tue Oct 29 01:14:20 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 934C321E8107; Tue, 29 Oct 2013 01:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.268
X-Spam-Level: 
X-Spam-Status: No, score=-102.268 tagged_above=-999 required=5 tests=[AWL=0.331, 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 WudwOIDCVOa1; Tue, 29 Oct 2013 01:14:17 -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 60E1021E80FA; Tue, 29 Oct 2013 01:14:12 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.158.76]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9T8DiNN027720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 01:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383034448; bh=4DN0+871qsIPdCxIoSjsjSaGqddU7cqgySWqXuChML0=; h=Date:To:From:Subject:Cc; b=giBNlJjtb6CHlbgklspsRt0H9QavZ2dz8/mxnpeM/4gGXjvTrh6Ey8lM+TMp3ezPJ GQUy2QuYPacDoPraayOq5FhNkCd3tDsNJpxDXRMsBmWz3rmBDfkE6lGDI41cScDVUm huHyN0HrVwhJnbWNckEo6nWdgWQjyeeGURPB8iA8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383034448; i=@elandsys.com; bh=4DN0+871qsIPdCxIoSjsjSaGqddU7cqgySWqXuChML0=; h=Date:To:From:Subject:Cc; b=ImUwNbCnQxliKeDlGgCpwUoVBr8/kU10o2mmJgjc8JLRRUyZvO2/5bRFmso+l+lMX jqr8OZ2oQhkzuTtASp3KpsdzDTuHBBQIkdCvms+Aqcjbe14CyQuakVJwUIwKWphrkU LPYMfvWKvqO/BYKuvPGQYPIrDIDnNuj4iA8TEGkA=
Message-Id: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 01:13:08 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p5-range.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p5-range-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 29 Oct 2013 08:14:20 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p5-range-24
Title: Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Reviewer: S. Moonesamy
Review Date: October 29, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft requires further review.

This document defines HTTP/1.1 range requests, partial responses, and 
the multipart/byteranges media type.

This document is well-written.  The Introduction section mentions 
that the byte range feature is an optional feature of HTTP.  This 
feature can be used to, for example, resume the download of a large 
file.  The feature is part of the set of documents for the protocol 
while the feature can be considered as not being part of the base 
protocol.  The Security Consideration sections (see Part 1 and Part 
2) do not discuss about whether the feature can be misused (e.g. 
denial of service).

Major Issues:

In Section 2.3:

   'The "Accept-Ranges" header field allows a server to indicate that it
    supports range requests for the target resource.'

There isn't any recommendation or requirement for the server to send 
"Accept-Ranges: bytes"; it's a RFC 2119 "may".  It seems better if 
there is a recommendation for the server to advertise the feature if 
the server supports it.  There is the following text in Section 3.1:

   "A server MAY ignore the Range header field.  However, origin servers
    and intermediate caches ought to support byte ranges when possible,
    since Range supports efficient recovery from partially failed
    transfers and partial retrieval of large representations."

My understanding of the above is that the server can ignore the Range 
header field but it is politely recommended that origin servers and 
intermediate caches support it.  This looks like a workaround to 
avoid introducing a RFC 2119 "should".  The text explains why it is 
worthwhile to support byte ranges while the Introduction sections 
states that this feature is optional.

In Section 3.2:

"HTTP-date" is defined in the Appendix C.  I suggest importing the 
rules should be in Section 1.2.

In Section 2.1:

    "Other valid (but not canonical) specifications of the second 500
     bytes (byte offsets 500-999, inclusive):

         bytes=500-600,601-999
         bytes=500-700,601-999"

And Section 3.1:

   "A client that is requesting multiple ranges SHOULD list those ranges
    in ascending order (the order in which they would typically be
    received in a complete representation) unless there is a specific
    need to request a later part earlier."

I am trying to understand what the server should do when it receives 
one or several overlapping ranges.

In Section 4.1:

  "If multiple parts are being transferred, the server generating the
   206 response MUST generate a "multipart/byteranges" payload, as
   defined in Appendix A"

It is unusual to have a RFC 2119 requirement defined in an appendix.

   "If the selected representation would have had a Content-Type
    header field in a 200 (OK) response, the server SHOULD generate
    that same Content-Type field in the header area of each body part."

I don't understand why the RFC 2119 "should" is used in the 
above.  When can the "should" be ignored?  Is the server supposed to 
generate the same Content-Type header field in each header area if 
the selected representation would have a Content-Type header field 
for a 200 (OK) response?

   "When a multipart response payload is generated, the server SHOULD
    send the parts in the same order that the corresponding byte-range-
    spec appeared in the received Range header field, excluding those
    ranges that were deemed unsatisfiable or that were coalesced into
    other ranges."

It is recommended in the Section 3.1 that the client lists the ranges 
it requests in ascending order.  The above text recommends that the 
server should send the parts in the same order as the request.  There 
can be an interoperability issue when the two sides are told to do 
RFC 2119 "should".

In Appendix A:

   "The following definition is to be registered with IANA [BCP13]."

The request to IANA should be in the IANA Considerations section.

Minor Issues:

In Section 1:

   "Range requests are an OPTIONAL feature of HTTP, designed so that
    recipients not implementing this feature (or not supporting it
    for the target resource) can respond as if it is a normal GET
    request without impacting interoperability."

As the word "OPTIONAL" in the above is not interpreted according to 
RFC 2119 I suggest using plain English instead of a word in uppercase.

In Section 2.1:

   "In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-
    length are expressed as decimal number of octets.  Since there is no
    predefined limit to the length of a payload, recipients ought to
    anticipate potentially large decimal numerals and prevent parsing
    errors due to integer conversion overflows."

There is a RFC 2119 "should" in Section 3.3.2 of 
draft-ietf-httpbis-p1-messaging-24 about integer conversion and a 
reference to Section 9.3 of that draft.  I may have missed integer 
conversation issues in the reviews.  I suggest doing a verification 
to verify that there is adequate text where it is applicable.

Nits:

In Section 2.2:

   "Range units are intended to be extensible."

Section 3.12 of RFC 2616 states that:

   "The only range unit defined by HTTP/1.1 is "bytes".  HTTP/1.1
    implementations MAY ignore ranges specified using other units.
    HTTP/1.1 has been designed to allow implementations of applications
    that do not depend on knowledge of ranges."

I consider the creation of the registry as "it does not cost anything 
to add one more registry".  The text from RFC 2616 suggests that the 
only unit specified is "bytes" and that HTTP/1.1 does not depend upon 
the knowledge of this optional feature.  I don't see any reason to 
have other range units.

In Section 2.3:

   "A server that does not support any kind of range request for the
    target resource resource MAY send"

The word "resource" is duplicated.

Regards,
S. Moonesamy


From sm@elandsys.com  Tue Oct 29 06:49: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 A922811E824C; Tue, 29 Oct 2013 06:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.728
X-Spam-Level: 
X-Spam-Status: No, score=-102.728 tagged_above=-999 required=5 tests=[AWL=-0.129, 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 FNwgcA4QM7-W; Tue, 29 Oct 2013 06:49: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 DE80C11E8242; Tue, 29 Oct 2013 06:49:58 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9TDne3n017632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 06:49:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383054594; bh=d73n3/K2HZ/iy8R9KTgH8dYoY+Wzn/c+g2rRWgLgsL4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=muz2fkPNs62YeJ7wHV7tFWLkSdk0PmG//kVQs6OdPoCyO7VH68TqSLtsPAlkMD2zR Fjgvhce3+yKO7uZ3cUdxmwxPRIbJ0HYnkTUTern0Zn7Qg4NV0TfCyf2lBL6+B0vnmz 2IAEW0a5xmnrE2siK/IgZFjiFocZ1yE6tikujP1g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383054594; i=@elandsys.com; bh=d73n3/K2HZ/iy8R9KTgH8dYoY+Wzn/c+g2rRWgLgsL4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dJyAeT6Nz9MvtOfwXncj15YGLm9DP+Wem0bhQm3iGqzrxP96L153Ips63dECdKGkK AGxizHGLvNi+02jiHGUe2P9l7A91MJvxfIcxkVVyNUdCoLlkFHm/ybqBLJj/ymW3Nq m1XIa696fQ8cy6DUH1TDAgc3RFx0A6KZv2gSUGLI=
Message-Id: <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 06:26:34 -0700
To: Julian Reschke <julian.reschke@gmx.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
In-Reply-To: <526E8B9E.8030006@gmx.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 13:49:59 -0000

Hi Julian,
At 09:06 28-10-2013, Julian Reschke wrote:
>On 2013-10-28 09:07, S Moonesamy wrote:
>(which expired ~2 years ago)

I guess that the working group gave up.  Please note that I did not 
suggest adding a reference.

>Could you clarify what exactly the issue is?
>
>RFC 2616 said 
>(<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1.p.4>):
>
>>Any HTTP/1.1 message containing an entity-body SHOULD include a 
>>Content-Type header field defining the media type of that body. If 
>>and only if the media type is not given by a Content-Type field, 
>>the recipient MAY attempt to guess the media type via inspection of 
>>its content and/or the name extension(s) of the URI used to 
>>identify the resource. If the media type remains unknown, the 
>>recipient SHOULD treat it as type "application/octet-stream".
>
>...which isn't that different.

The 'If the media type remains unknown, the recipient SHOULD treat it 
as type "application/octet-stream' from RFC 2616 is not in 
draft-ietf-httpbis-p2-semantics-24.

The issue is the "or examine the data to determine its type".  I'll 
comment about the text (Section 3.1.1.5) again.  The server has to 
generate a Content-Type header field unless the media type is 
unknown.  There is then a RFC 2119 "may" which is applicable when the 
(previous) RFC 2119 "should" cannot be applied.  My reading of the 
"may" is that the usage is not entirely correct.  I am not raising 
that as an issue.  The issue is whether there is a security problem 
and whether there is adequate discussion of it (e.g. it is discussed 
in a Security Considerations section).

Regards,
S. Moonesamy 


From sm@elandsys.com  Tue Oct 29 06:50:04 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 4DB7F21E8127; Tue, 29 Oct 2013 06:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.723
X-Spam-Level: 
X-Spam-Status: No, score=-102.723 tagged_above=-999 required=5 tests=[AWL=-0.124, 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 s7FC-qaOTHJO; Tue, 29 Oct 2013 06:50:03 -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 44A7321E8125; Tue, 29 Oct 2013 06:50:03 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9TDne3p017632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 06:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383054599; bh=W1VKHQtS2s7E9bcsq+kjPLQ2C7ykIk7VCnCXX6ObrmY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jviLBA7T9gAftEcBSEqkg4mg+uvD7KjGOIEZfKbqeTwwXMrEccj4TmFW+2ONRokoX Sbw6Pd8dA/43uunKVx6PLk6Whcly9yDlX7ifPDLmlzoB7glnVaN4sMg1ElDHcBrVKI CuhQ4nRr5Yi8DKoaIq0/zdvEPR7jtDKc2/+OuV3k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383054599; i=@elandsys.com; bh=W1VKHQtS2s7E9bcsq+kjPLQ2C7ykIk7VCnCXX6ObrmY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k/cc7Ne+1NgR+ckEL2WC8Gv7LSE/PoxPK2BQwieoHhiqhh7p9ETXi6LMgJPWVdoLA nLgsjglbf8fXBDO4Qj+B31s+HZIsQFeJAk6Co/BPrHexieIT9OFmUDc4SdyYhhiAaJ ADWv+PA5RrAORHOHbbG54E9huva580Pk8Cyc1kNo=
Message-Id: <6.2.5.6.2.20131029062834.0c4b9f98@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 06:39:14 -0700
To: Julian Reschke <julian.reschke@gmx.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p1-messaging.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Registration requirements for transfer codings, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
In-Reply-To: <526E8878.5030903@gmx.de>
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com> <526E8878.5030903@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 29 Oct 2013 13:50:04 -0000

Hi Julian,
At 08:53 28-10-2013, Julian Reschke wrote:
>My understanding is that we wanted to set a high bar because this 
>really ought to happen with lots of care and review.
>
>The related ticket is 
><http://trac.tools.ietf.org/wg/httpbis/trac/ticket/188>, and it was 
>discussed during IETF 75 
>(<http://tools.ietf.org/wg/httpbis/minutes?item=minutes75.html>).

I'll consider this as addressed.

Regards,
S. Moonesamy


From julian.reschke@gmx.de  Tue Oct 29 07:12:40 2013
Return-Path: <julian.reschke@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 4494811E825F for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.704
X-Spam-Level: 
X-Spam-Status: No, score=-103.704 tagged_above=-999 required=5 tests=[AWL=-1.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 KIWsfnWuJyY3 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:12:35 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 61EDA11E815F for <ietf@ietf.org>; Tue, 29 Oct 2013 07:12:34 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MUHbK-1VAAy32Mjq-00Qwp4 for <ietf@ietf.org>; Tue, 29 Oct 2013 15:12:33 +0100
Message-ID: <526FC24D.7060704@gmx.de>
Date: Tue, 29 Oct 2013 15:12:29 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de> <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:6vHzeACHppkj/0q0hAgrLDAw/9V7oveMcnxN9NLU99E3hsNsNX5 6Ri8x5NM+GFLzofOZO1F1+NJ6JbsQKsF/CMqnXNgwoaHfJ+1TnSBcmxFn9TaU90P91/ZNlJ PTyEULUbez3zd7HHNygjNWce2qaDZ6xEFyJInsv9ZLtYlc1Uxtee2Jx2RoOpDDOMnruhq+c e40VRAh8oArrlTINS63JQ==
Cc: ietf@ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 14:12:40 -0000

On 2013-10-29 14:26, S Moonesamy wrote:
> Hi Julian,
> At 09:06 28-10-2013, Julian Reschke wrote:
>> On 2013-10-28 09:07, S Moonesamy wrote:
>> (which expired ~2 years ago)
>
> I guess that the working group gave up.  Please note that I did not
> suggest adding a reference.
>
>> Could you clarify what exactly the issue is?
>>
>> RFC 2616 said
>> (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1.p.4>):
>>
>>> Any HTTP/1.1 message containing an entity-body SHOULD include a
>>> Content-Type header field defining the media type of that body. If
>>> and only if the media type is not given by a Content-Type field, the
>>> recipient MAY attempt to guess the media type via inspection of its
>>> content and/or the name extension(s) of the URI used to identify the
>>> resource. If the media type remains unknown, the recipient SHOULD
>>> treat it as type "application/octet-stream".
>>
>> ...which isn't that different.
>
> The 'If the media type remains unknown, the recipient SHOULD treat it as
> type "application/octet-stream' from RFC 2616 is not in
> draft-ietf-httpbis-p2-semantics-24.

I consider that sentence to be useless - if I can't detect the type, 
what else but "treating as arbitrary data" is left as an option anyway?

> The issue is the "or examine the data to determine its type".  I'll
> comment about the text (Section 3.1.1.5) again.  The server has to
> generate a Content-Type header field unless the media type is unknown.

Yes.

> There is then a RFC 2119 "may" which is applicable when the (previous)
> RFC 2119 "should" cannot be applied.  My reading of the "may" is that
> the usage is not entirely correct.  I am not raising that as an issue.

I still don't get what the issue is :-)

> The issue is whether there is a security problem and whether there is
> adequate discussion of it (e.g. it is discussed in a Security
> Considerations section).

The subsequent text is:

"In practice, resource owners do not always properly configure their 
origin server to provide the correct Content-Type for a given 
representation, with the result that some clients will examine a 
payload's content and override the specified type. Clients that do so 
risk drawing incorrect conclusions, which might expose additional 
security risks (e.g., "privilege escalation"). Furthermore, it is 
impossible to determine the sender's intent by examining the data 
format: many data formats match multiple media types that differ only in 
processing semantics. Implementers are encouraged to provide a means of 
disabling such "content sniffing" when it is used."

Do you think this is insufficient, or that it needs to move to a 
different part of the spec?

Best regards, Julian


From jari.arkko@piuha.net  Tue Oct 29 07:39:51 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 A078711E82B2 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.706
X-Spam-Level: 
X-Spam-Status: No, score=-102.706 tagged_above=-999 required=5 tests=[AWL=-0.107, 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 M7bCTvHZO4t6 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:39:47 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC0111E82CC for <ietf@ietf.org>; Tue, 29 Oct 2013 07:38:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B3EFD2CC5D for <ietf@ietf.org>; Tue, 29 Oct 2013 16:38:22 +0200 (EET)
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 ENRFMInGcN5K for <ietf@ietf.org>; Tue, 29 Oct 2013 16:38:22 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 26C332CC48 for <ietf@ietf.org>; Tue, 29 Oct 2013 16:38:22 +0200 (EET)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: future of identifiers
Message-Id: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Date: Tue, 29 Oct 2013 16:38:22 +0200
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 14:39:51 -0000

For background, when I visited the ICANN meeting last summer, they were =
about to launch a set of panels to advice themselves about key topics in =
coming years. I promised to join one of them, on identifier technology =
innovation (along with a few other IETFers). The topic for this effort =
is future evolution of DNS and other identifiers, including relevant =
security and management aspects. The viewpoint is primarily to look at =
this from ICANN=92s angle, but of course the matter is interesting to us =
others as well.=20

And perhaps we at the IETF should also understand the same things. Hence =
this e-mail.

I have some ideas on what some of these trends might be. But what do the =
rest of you think? Where is identifier technology going, and what new =
things are on the horizon? What do we need to do with IDNs? DNSSEC? What =
will DANE lead to, and how will id-locator split techniques evolve & be =
deployed? How will applications or users think about identifiers in the =
future?

More information at http://www.ietf.org/blog/2013/10/future-identifiers/

Jari


From jmamodio@gmail.com  Tue Oct 29 07:54:23 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 75CE221F9FF0 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:54:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level: 
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[AWL=-0.036,  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 uIjHZzGuiZLJ for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 07:54:23 -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 C97E111E82B2 for <ietf@ietf.org>; Tue, 29 Oct 2013 07:52:59 -0700 (PDT)
Received: by mail-ob0-f180.google.com with SMTP id wo20so5268157obc.39 for <ietf@ietf.org>; Tue, 29 Oct 2013 07:52:59 -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:from:subject:date:to; bh=ig+485BJ0C/Q77jNsb6sAIzzFyipbkhUCPwiEEz0eO8=; b=i8xjRTK75cHiqNwpejDgi+XjY17FAefjJ/+LxJg1Hwp+C01r2EAsWn46VoyBkFrTgm INUJWU/FZZZc63/zXaPD6HyiQ0Mdu95z02BnnUacPYOczdZ5WbcxYRh4/46Xu9xyDiyJ xpPHGHLqqj679V8jQU591qUTp7RX8awpKO4gtm7uIxm5JEMPxA7xmpsucjk2mXXvc84N bF47szfa7f+khDemDyfCdYUqgSvurz9rQKJRS1jfPgOYtPdpxPcDiMAM8t7Q8dszkX9w SsvfYfGOo673s8doId133Lf1QqEwLBw7s2Eu3Q3g2jYSrqHcR+E9tZj/4W8T3PVTFxLU V0Fg==
X-Received: by 10.60.98.69 with SMTP id eg5mr27802oeb.42.1383058379229; Tue, 29 Oct 2013 07:52:59 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id bg2sm9360477obb.1.2013.10.29.07.52.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 07:52:58 -0700 (PDT)
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <932566FE-2D06-419D-B149-A81AA1CEC8BD@gmail.com>
X-Mailer: iPad Mail (11B511)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: future of identifiers
Date: Tue, 29 Oct 2013 09:53:00 -0500
To: Jari Arkko <jari.arkko@piuha.net>
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, 29 Oct 2013 14:54:23 -0000

Just think how many URLs you type on your smartphone or tablet and with wear=
able technologies like Google Glass, plus the common use of URL shorteners, i=
n a very near future the actual string will become irrelevant, which will am=
ong other reasons make the new GTLD program useless and the DNS will stop be=
ing abused as a billboard where everybody fights for the best spot and the g=
old rush of domain names will be over.

IETF should take the lead in the development of innovative ways to identify r=
esources, if not the ITU will fill the gap.

My .02

-Jorge

> On Oct 29, 2013, at 9:38 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> For background, when I visited the ICANN meeting last summer, they were ab=
out to launch a set of panels to advice themselves about key topics in comin=
g years. I promised to join one of them, on identifier technology innovation=
 (along with a few other IETFers). The topic for this effort is future evolu=
tion of DNS and other identifiers, including relevant security and managemen=
t aspects. The viewpoint is primarily to look at this from ICANN=E2=80=99s a=
ngle, but of course the matter is interesting to us others as well.=20
>=20
> And perhaps we at the IETF should also understand the same things. Hence t=
his e-mail.
>=20
> I have some ideas on what some of these trends might be. But what do the r=
est of you think? Where is identifier technology going, and what new things a=
re on the horizon? What do we need to do with IDNs? DNSSEC? What will DANE l=
ead to, and how will id-locator split techniques evolve & be deployed? How w=
ill applications or users think about identifiers in the future?
>=20
> More information at http://www.ietf.org/blog/2013/10/future-identifiers/
>=20
> Jari
>=20

From julian.reschke@gmx.de  Tue Oct 29 08:03:24 2013
Return-Path: <julian.reschke@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 A37E711E8296 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.723
X-Spam-Level: 
X-Spam-Status: No, score=-103.723 tagged_above=-999 required=5 tests=[AWL=-1.124, 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 vL0AYU9cME+O for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:03:24 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id DFB2011E8271 for <ietf@ietf.org>; Tue, 29 Oct 2013 08:03:19 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MZD0K-1VGC413kB2-00Kv1i for <ietf@ietf.org>; Tue, 29 Oct 2013 16:03:18 +0100
Message-ID: <526FCE32.8090309@gmx.de>
Date: Tue, 29 Oct 2013 16:03:14 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p5-range.all@tools.ietf.org
Subject: custom byte ranges, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:l9TaiX8QfmJpW7e/A6c5+wECzhNtUa4dUdySHkqDgcEazaz1FMu 6qSxYhLAKdDVkXm/7TQziE0O4JnI7DasIJT7E5GpEVyNv5CaFIti4QI6vyOkkbdP8E7NZfs oD+DYwbUCDl7IKE48DccL+KTJPqek8yMQwWGy/i+GKAaYb8n8TJGin7rYELka1oWCU1lDku 7DwmLsTrmHtvW9Q4TgPoA==
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 29 Oct 2013 15:03:24 -0000

On 2013-10-29 09:13, S Moonesamy wrote:
> ...
> In Section 2.2:
>
>    "Range units are intended to be extensible."
>
> Section 3.12 of RFC 2616 states that:
>
>    "The only range unit defined by HTTP/1.1 is "bytes".  HTTP/1.1
>     implementations MAY ignore ranges specified using other units.
>     HTTP/1.1 has been designed to allow implementations of applications
>     that do not depend on knowledge of ranges."
>
> I consider the creation of the registry as "it does not cost anything to
> add one more registry".  The text from RFC 2616 suggests that the only
> unit specified is "bytes" and that HTTP/1.1 does not depend upon the
> knowledge of this optional feature.  I don't see any reason to have
> other range units.
> ...

Actually, it was a case of "this is used in the wild already, and more 
use is coming up, so better document it properly and add the registry". 
See <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/85> for the history.

Best regards, Julian

From juliao@braga.eti.br  Tue Oct 29 08:16:19 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 4293611E82C7 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:16:19 -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 IGwV50kPYLNK for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:16:15 -0700 (PDT)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id E420611E82C2 for <ietf@ietf.org>; Tue, 29 Oct 2013 08:16:14 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id w8so2977053qac.15 for <ietf@ietf.org>; Tue, 29 Oct 2013 08:16:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gEuGAHyQn0cKW6HLpnyhVrkQ/ZiZcWmFKNcrupbbBaA=; b=hMPCRCZHawrg2PgnhagFkkv48xIau1IpujrnZ8QcyohXSHV/O662gS9MRXWNUVqfVm 7IwsEeQ5a3m3H5fLocdqB+PA4N7Dg97IItxDwChljsc/0cxbJCglk01YzuEhUsiPqw3+ sum174YsKS08oEQaGcSfy+2YMWySidmLPDgwH7euw26ra43JQv54jSjlmuL4KM2swYFY BkO3H+1pLteyUy+cPH8LspIS3OXCeo0dtXrnIWhPi9n8wRH4LBraDrcYb4xIX+U04L2P x01IYDCa1HRTrUZ57JBe4Lr/q0RcPW/h8UxaU7k43ByyGWL+kus0wHD4TYCWvdY17W2C BtMg==
X-Gm-Message-State: ALoCoQmJGAfqhcqZIBzKxw9xU4EDP7Rj6kQk7rCNGsAVHtZFZfUfmiYy4x4VAvqL9YAWRRK/lIHk
X-Received: by 10.224.55.80 with SMTP id t16mr1413611qag.106.1383059774032; Tue, 29 Oct 2013 08:16:14 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id n7sm66123387qai.1.2013.10.29.08.16.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 08:16:11 -0700 (PDT)
Message-ID: <526FD137.3060309@braga.eti.br>
Date: Tue, 29 Oct 2013 13:16:07 -0200
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: future of identifiers
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
In-Reply-To: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Content-Type: text/plain; charset=windows-1252
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: Tue, 29 Oct 2013 15:16:19 -0000

Jari,

I think this issue also involves the application of Semantic Web
(specifically, Linked Data and ontologies). I do not know exactly how,
just now, but my feelings are that this is a path to the future. But, in
my graduate program I am studying these issues, where the IETF
repositories and associates are the main focuses. Questions such as
vocabularies, metadata, knowledge, ownership, and other relationships
are a concern in the research.

It would be interesting to other people interested in the Semantic Web
applications on the infrastructure of the Internet, came in contact to
begin a team.

Juliăo

Em 29/10/2013 12:38, Jari Arkko escreveu:
> For background, when I visited the ICANN meeting last summer, they were about to launch a set of panels to advice themselves about key topics in coming years. I promised to join one of them, on identifier technology innovation (along with a few other IETFers). The topic for this effort is future evolution of DNS and other identifiers, including relevant security and management aspects. The viewpoint is primarily to look at this from ICANN’s angle, but of course the matter is interesting to us others as well. 
>
> And perhaps we at the IETF should also understand the same things. Hence this e-mail.
>
> I have some ideas on what some of these trends might be. But what do the rest of you think? Where is identifier technology going, and what new things are on the horizon? What do we need to do with IDNs? DNSSEC? What will DANE lead to, and how will id-locator split techniques evolve & be deployed? How will applications or users think about identifiers in the future?
>
> More information at http://www.ietf.org/blog/2013/10/future-identifiers/
>
> Jari
>
>


From chair@ietf.org  Tue Oct 29 08:19:25 2013
Return-Path: <chair@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 9B90D11E82D1; Tue, 29 Oct 2013 08:19: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 Do0qZMjo0d1A; Tue, 29 Oct 2013 08:19:20 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 762E611E82CC; Tue, 29 Oct 2013 08:19:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id F291DA61A1; Tue, 29 Oct 2013 08:17:20 -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 hH60I3i_Hh-z; Tue, 29 Oct 2013 08:17:20 -0700 (PDT)
Received: from [10.30.0.145] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 4937BA619F; Tue, 29 Oct 2013 08:17:20 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Discussions on Internet Hardening in Vancouver
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 29 Oct 2013 17:19:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <128103B5-D786-42DE-A474-6AE93D58D96F@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org Discussion" <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, 29 Oct 2013 15:19:26 -0000

I would like to provide an overview of what discussions will be =
happening in Vancouver around this topic. The main discussion is of =
course the technical plenary, for which we have also live streaming. But =
we'll also have discussions in the PERPASS, HTTPBIS, APPSAWG, TLS, SAAG =
and other sessions. More information, agendas, stream links, social =
media event subscriptions (feel free to share), and so on are here:

http://www.ietf.org/blog/2013/10/plenary-on-internet-hardening/

Jari Arkko
IETF Chair


From squid3@treenet.co.nz  Mon Oct 28 18:27:25 2013
Return-Path: <squid3@treenet.co.nz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F0911E81ED; Mon, 28 Oct 2013 18:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.631
X-Spam-Level: 
X-Spam-Status: No, score=-5.631 tagged_above=-999 required=5 tests=[AWL=-4.583, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, 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 mnP4-gdzk4zE; Mon, 28 Oct 2013 18:27:15 -0700 (PDT)
Received: from treenet.co.nz (ipv6.rio.treenetnz.com [IPv6:2002:3a1c:99e9:0:206:5bff:fe7c:b8a]) by ietfa.amsl.com (Postfix) with ESMTP id 51BDD11E81DD; Mon, 28 Oct 2013 18:26:39 -0700 (PDT)
Received: from [192.168.0.6] (unknown [121.99.144.92]) by treenet.co.nz (Postfix) with ESMTP id 14C71E7392; Tue, 29 Oct 2013 14:26:27 +1300 (NZDT)
Message-ID: <526F0EC1.7010809@treenet.co.nz>
Date: Tue, 29 Oct 2013 14:26:25 +1300
From: Amos Jeffries <squid3@treenet.co.nz>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Julian Reschke <julian.reschke@gmx.de>, S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review of	draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com> <526E73B8.90705@gmx.de> <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com>
In-Reply-To: <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 29 Oct 2013 08:20:33 -0700
Cc: ietf-http-wg@w3.org, 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: Tue, 29 Oct 2013 01:27:27 -0000

On 29/10/2013 8:22 a.m., John C Klensin wrote:
>
> --On Monday, October 28, 2013 15:24 +0100 Julian Reschke
> <julian.reschke@gmx.de> wrote:
>
>> John,
>>
>> that change would make almost every HTTP/1.1 code ever written
>> non-compliant.
>>
>> And yes, it would have been nice if a same date format would
>> have been chosen back then.
> Julian,
>
> I don't know enough of the issues in enough detail to argue
> this, and won't.  My goal is only to be sure the question has
> been asked.
>
> My understanding is that the HTTPbis work is a rather major
> revision with at least some cases for which "get it right" is
> more important that complete backward compatibility, especially
> if there is a clear migration path.

No. The focus on the WG has been to document what is actually *working*
and clarify existing HTTP behaviour in order to  encourage interoperability.

>    All of the usual arguments
> for that are relevant, especially the ones that focus on how
> many implementations and pages are likely to be created in the
> future relative to those that exist today.   Here, the clear
> migration path would be a narrow and restrictive "send syntax"
> and a permissive "receive syntax" that requires support of all
> known older forms, _especially_ those that were recommended by
> HTTP 1.1.

However it is important to note that there is no clear migration path. Many
implementations are actively *rejecting* or ignoring date formats which do
not include the "GMT" moniker.


> It has been rather longer than I think we expected, but it was
> clear when HTTP 1.1 was adopted (I am sure it was clear at least
> to the relevant ADs) that there could be incompatible changes in
> the future and that the concern should be a non-disruptive
> migration path, not absolute forward compatibility.  That is one
> of the several reasons why the successor to HTTP 1.0 was
> identified as HTTP 1.1, not HTTP 2.

Indeed. This option was considered by the WG several times as people keep
bringing up this same point. (I myself even a few  years back). The WG 
charter
is explicitly prohibiting addition of a new version number in these 
documents
so there are several things like this which have had to be left unchanged.

> This sort of change would still make HTTP 1.1 implementations
> non-compliant with HTTP 2.0, but that is ok -- they still comply
> with HTTP 1.1 and I hope no one is going to claim that all HTTP
> 1.1 implementations are non-compliant with HTTP the day HTTP 2.0
> is published.

Those existing 1.1 implementations will certainly not be compliant with 2.0
binary traffic encoding!

But mapping between 1.1 with its useless GMT / day-of-week and the new
improved 2.0 date format (whatever that may be) can be explicitly specified
for the 1.1<->2.0 gateway translations in the new 2.0 implementations
without altering 1.1 compliance for any existing or future implementations.
The WG has chosen this approach over attempting a difficult upgrade within
1.1 itself.

Amos

From Howard.Tinker@arqiva.com  Tue Oct 29 02:33:45 2013
Return-Path: <Howard.Tinker@arqiva.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A911F21E80BA for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 02:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level: 
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[AWL=1.003,  BAYES_05=-1.11, DEAR_SOMETHING=1.605, 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 wmeFuWkmTNWr for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 02:33:36 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id E465821F9E00 for <ietf@ietf.org>; Tue, 29 Oct 2013 02:33:35 -0700 (PDT)
Received: from [85.158.137.3:2965] by server-14.bemta-3.messagelabs.com id 05/07-20312-EE08F625; Tue, 29 Oct 2013 09:33:34 +0000
X-Env-Sender: Howard.Tinker@arqiva.com
X-Msg-Ref: server-15.tower-38.messagelabs.com!1383039214!301738!1
X-Originating-IP: [87.249.73.200]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=arqiva.com,-,-
X-VirusChecked: Checked
Received: (qmail 5058 invoked from network); 29 Oct 2013 09:33:34 -0000
Received: from mail5.arqiva.com (HELO PAQ-WTP-VEXHC01.Arqiva.Local) (87.249.73.200) by server-15.tower-38.messagelabs.com with AES128-SHA encrypted SMTP; 29 Oct 2013 09:33:34 -0000
Received: from paq-wtp-mail01.Arqiva.Local ([169.254.1.6]) by PAQ-WTP-VEXHC01.Arqiva.Local ([10.52.34.80]) with mapi; Tue, 29 Oct 2013 09:33:33 +0000
From: Howard Tinker <Howard.Tinker@arqiva.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 29 Oct 2013 09:33:35 +0000
Subject: Information request for Secure WiFi standards 
Thread-Topic: Information request for Secure WiFi standards 
Thread-Index: Ac7UB2i2FZ23gz8gSOWLRRDMOMvI8AAglXmw
Message-ID: <7C80DB06B1075E43B9CE655495942DDA9CF1906ECF@PAQ-WTP-MAIL01.Arqiva.Local>
Accept-Language: en-US, en-GB
Content-Language: en-US
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-Mailman-Approved-At: Tue, 29 Oct 2013 08:20:50 -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: Tue, 29 Oct 2013 09:33:45 -0000

Dear Sir / Madam,
Please can you advise if IETF have published or are planning to publish an=
y standards for a Secure WiFi product that could be potentially used by us=
ers requiring a higher level of security than the public  systems availabl=
e today (e.g. police, fire, ambulance, military, other government agencies=
 etc) ?


Kind regards
Howard
=20
=20
Howard Tinker
Product Manager - New Product Development
=20
Telecoms - Secure Solutions
=20
Mob: 07977 922684
Arqiva | Farley Lane | Romsley Hill | Halesowen | West Midlands | B62
    0LG

______________________________________________________________________

This email, its content and any files transmitted with it are for the pers=
onal attention of the addressee only, any other usage or access is unautho=
rised. It may contain information which could be confidential or privilege=
d. If you are not the intended addressee you may not copy, disclose, circu=
late or use it.

If you have received this email in error, please destroy it and notify the=
 sender by email. Any representations or commitments expressed in this ema=
il are subject to contract. =20

Although we use reasonable endeavours to virus scan all sent emails, it is=
 the responsibility of the recipient to ensure that they are virus free an=
d we advise you to carry out your own virus check before opening any attac=
hments. We cannot accept liability for any damage sustained as a result of=
 software viruses. We reserve the right to monitor email communications th=
rough our networks.

Arqiva Limited. Registered office: Crawley Court, Winchester, Hampshire SO=
21 2QA United Kingdom Registered in England and Wales number 2487597

______________________________________________________________________

From julian.reschke@gmx.de  Tue Oct 29 08:28:09 2013
Return-Path: <julian.reschke@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 9154811E82F0 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.739
X-Spam-Level: 
X-Spam-Status: No, score=-103.739 tagged_above=-999 required=5 tests=[AWL=-1.140, 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 Qzw9uZAj5dnR for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:28:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 9E57111E82CE for <ietf@ietf.org>; Tue, 29 Oct 2013 08:27:41 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MBFBB-1VR2iX0c2H-00AFRY for <ietf@ietf.org>; Tue, 29 Oct 2013 16:27:40 +0100
Message-ID: <526FD3E8.9010904@gmx.de>
Date: Tue, 29 Oct 2013 16:27:36 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p5-range.all@tools.ietf.org
Subject: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:lTQ7ihb1WqNXjyqrrUGWEdYFwl7GDMA8u4iSKBccy6X1SdbrQSt gTqhD4hYShp0A5oeURTEXIyYz1/ndT11O7xducgdnRk0rt5J9e/DCHwrxwUhOC/zmpSD3+r /YCIuJA6g4G6MWEthY0UZtVAL5uFHNE6jT309Lgrv3jc4AHRA/KAtMpu4Vv9JyginigObSE Vxf5GBx8J8PieG1S6iliQ==
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 29 Oct 2013 15:28:09 -0000

Hi SM,

thanks a lot for the incoming reviews! I'm tracking them in the WG's 
trac instance.

Below are comments on the non-editorial parts of your review.

On 2013-10-29 09:13, S Moonesamy wrote:
> ...
> Major Issues:
>
> In Section 2.3:
>
>    'The "Accept-Ranges" header field allows a server to indicate that it
>     supports range requests for the target resource.'
>
> There isn't any recommendation or requirement for the server to send
> "Accept-Ranges: bytes"; it's a RFC 2119 "may".  It seems better if there
> is a recommendation for the server to advertise the feature if the
> server supports it.  There is the following text in Section 3.1:

Well, it's optional, and we didn't want to make it a SHOULD. It adds 
overhead to GET responses, even though only few clients will make range 
requests.

>    "A server MAY ignore the Range header field.  However, origin servers
>     and intermediate caches ought to support byte ranges when possible,
>     since Range supports efficient recovery from partially failed
>     transfers and partial retrieval of large representations."
>
> My understanding of the above is that the server can ignore the Range
> header field but it is politely recommended that origin servers and
> intermediate caches support it.  This looks like a workaround to avoid
> introducing a RFC 2119 "should".  The text explains why it is worthwhile
> to support byte ranges while the Introduction sections states that this
> feature is optional.

Yes. Do you think this is a problem? Why?

> In Section 3.2:
>
> "HTTP-date" is defined in the Appendix C.  I suggest importing the rules
> should be in Section 1.2.

<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/505>

> In Section 2.1:
>
>     "Other valid (but not canonical) specifications of the second 500
>      bytes (byte offsets 500-999, inclusive):
>
>          bytes=500-600,601-999
>          bytes=500-700,601-999"
>
> And Section 3.1:
>
>    "A client that is requesting multiple ranges SHOULD list those ranges
>     in ascending order (the order in which they would typically be
>     received in a complete representation) unless there is a specific
>     need to request a later part earlier."
>
> I am trying to understand what the server should do when it receives one
> or several overlapping ranges.

"A server that supports range requests MAY ignore or reject a Range 
header field that consists of more than two overlapping ranges, or a set 
of many small ranges that are not listed in ascending order, since both 
are indications of either a broken client or a deliberate denial of 
service attack (Section 6.1). A client SHOULD NOT request multiple 
ranges that are inherently less efficient to process and transfer than a 
single range that encompasses the same data."

..or it can serve the response as multipart/byteranges as requested.

> In Section 4.1:
>
>   "If multiple parts are being transferred, the server generating the
>    206 response MUST generate a "multipart/byteranges" payload, as
>    defined in Appendix A"
>
> It is unusual to have a RFC 2119 requirement defined in an appendix.

<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/505>

>    "If the selected representation would have had a Content-Type
>     header field in a 200 (OK) response, the server SHOULD generate
>     that same Content-Type field in the header area of each body part."
>
> I don't understand why the RFC 2119 "should" is used in the above.  When
> can the "should" be ignored?  Is the server supposed to generate the

Dunno.

> same Content-Type header field in each header area if the selected
> representation would have a Content-Type header field for a 200 (OK)
> response?

That's what the above says, no?

>    "When a multipart response payload is generated, the server SHOULD
>     send the parts in the same order that the corresponding byte-range-
>     spec appeared in the received Range header field, excluding those
>     ranges that were deemed unsatisfiable or that were coalesced into
>     other ranges."
>
> It is recommended in the Section 3.1 that the client lists the ranges it
> requests in ascending order.  The above text recommends that the server
> should send the parts in the same order as the request.  There can be an
> interoperability issue when the two sides are told to do RFC 2119 "should".

Such as?

> In Appendix A:
>
>    "The following definition is to be registered with IANA [BCP13]."
>
> The request to IANA should be in the IANA Considerations section.

Right. Fixed in <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/2441>.

> Minor Issues:
>
> In Section 1:
>
>    "Range requests are an OPTIONAL feature of HTTP, designed so that
>     recipients not implementing this feature (or not supporting it
>     for the target resource) can respond as if it is a normal GET
>     request without impacting interoperability."
>
> As the word "OPTIONAL" in the above is not interpreted according to RFC
> 2119 I suggest using plain English instead of a word in uppercase.

It is supposed to be interpreted per RFC 2119.

> In Section 2.1:
>
>    "In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-
>     length are expressed as decimal number of octets.  Since there is no
>     predefined limit to the length of a payload, recipients ought to
>     anticipate potentially large decimal numerals and prevent parsing
>     errors due to integer conversion overflows."
>
> There is a RFC 2119 "should" in Section 3.3.2 of
> draft-ietf-httpbis-p1-messaging-24 about integer conversion and a
> reference to Section 9.3 of that draft.  I may have missed integer
> conversation issues in the reviews.  I suggest doing a verification to
> verify that there is adequate text where it is applicable.

Raised as <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/507>.

> ..

Best regards, Julian


From barryleiba@gmail.com  Tue Oct 29 08:28:30 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 1C5E421E8151; Tue, 29 Oct 2013 08:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.657
X-Spam-Level: 
X-Spam-Status: No, score=-101.657 tagged_above=-999 required=5 tests=[AWL=-0.279, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_63=0.6, 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 p7re7sPtN0QL; Tue, 29 Oct 2013 08:28:29 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 93EFF21E8143; Tue, 29 Oct 2013 08:28:09 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id k18so4328qcv.10 for <multiple recipients>; Tue, 29 Oct 2013 08:28:04 -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:message-id:subject :from:to:cc:content-type; bh=4tuRPMQWEaqIBoNw50thWZT41IgrR3tEmgtzAlm7cD8=; b=aYTw8gLPU3lTrYjYVV8EfkD1bVqgzwIHfb1xtYBjx2T4l7fn32dH0dF5VU1yesheIM Yo6mw6DoEVAc3rKkd8iirUv0hQF9IW14rYnry7vz9KnPjaEk95eVpxK0bitt3aqgY4Yg a8YUUpgR20bYQN+3qEBE9c78MuHD78/IEBH4OBG4KV2Uf8L0y2ds3yN6Jx1wgYZlRFTn Ul9nk17Bw1oKNGKGtkV197qoTw5679RHMbxk5+pOZvhNcmCcaObuqjAyJ2xfPSHAKWPs LK89FCORL2ESLFZZ7v8sVPNewUIYU4nLDLpUxbbXyPc3GPyrtIUTgflkGZtaTufInJ4U pVAQ==
MIME-Version: 1.0
X-Received: by 10.229.101.136 with SMTP id c8mr256228qco.17.1383060484895; Tue, 29 Oct 2013 08:28:04 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.67.130 with HTTP; Tue, 29 Oct 2013 08:28:04 -0700 (PDT)
In-Reply-To: <526FC24D.7060704@gmx.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de> <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de>
Date: Tue, 29 Oct 2013 11:28:04 -0400
X-Google-Sender-Auth: cZk9QgaywxIVRlrTabqNwy6vofs
Message-ID: <CALaySJJ-GRCCE-pXVy-mWjdSXpLs7s9k35+pyDaXKirTpt-4rg@mail.gmail.com>
Subject: Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
From: Barry Leiba <barryleiba@computer.org>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, Apps Discuss <apps-discuss@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, IESG <iesg@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 15:28:30 -0000

>> There is then a RFC 2119 "may" which is applicable when the (previous)
>> RFC 2119 "should" cannot be applied.  My reading of the "may" is that
>> the usage is not entirely correct.  I am not raising that as an issue.
>
> I still don't get what the issue is :-)

Yeh, neither do I, and I'm pretty sensitive to those SHOULD+MAY
issues.  The one in Section 3.1.1.5 seems perfectly fine: it says that
the server SHOULD do something, and that if the server has not done
that the client MAY do something to try to compensate.  A-OK to me.
The tricky bits with SHOULD+MAY occur when both key words apply to the
same entity under the same conditions.  That's not the case here.

Barry

From bmanning@isi.edu  Tue Oct 29 08:38:44 2013
Return-Path: <bmanning@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 02C5D11E8301 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:38: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 YM0YI1P0at-3 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 08:38:35 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCCB21F9DCE for <ietf@ietf.org>; Tue, 29 Oct 2013 08:38:34 -0700 (PDT)
Received: from [192.168.254.18] ([207.87.41.70]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r9TFcFLB007645 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 29 Oct 2013 08:38:19 -0700 (PDT)
Subject: Re: future of identifiers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Date: Tue, 29 Oct 2013 08:30:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B43BD48-324A-484A-AC82-802FEFDB5171@isi.edu>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 29 Oct 2013 15:38:45 -0000

I talked to Lars in Berlin about the possibility of hosting a BOF about =
this topic, but it seems to have become OBE, at least for
YVR.   This has potential for work in the IRTF.


/bill


On 29October2013Tuesday, at 7:38, Jari Arkko wrote:

> For background, when I visited the ICANN meeting last summer, they =
were about to launch a set of panels to advice themselves about key =
topics in coming years. I promised to join one of them, on identifier =
technology innovation (along with a few other IETFers). The topic for =
this effort is future evolution of DNS and other identifiers, including =
relevant security and management aspects. The viewpoint is primarily to =
look at this from ICANN=92s angle, but of course the matter is =
interesting to us others as well.=20
>=20
> And perhaps we at the IETF should also understand the same things. =
Hence this e-mail.
>=20
> I have some ideas on what some of these trends might be. But what do =
the rest of you think? Where is identifier technology going, and what =
new things are on the horizon? What do we need to do with IDNs? DNSSEC? =
What will DANE lead to, and how will id-locator split techniques evolve =
& be deployed? How will applications or users think about identifiers in =
the future?
>=20
> More information at =
http://www.ietf.org/blog/2013/10/future-identifiers/
>=20
> Jari
>=20


From julian.reschke@gmx.de  Tue Oct 29 09:03:50 2013
Return-Path: <julian.reschke@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 4AA6311E80F1 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.781
X-Spam-Level: 
X-Spam-Status: No, score=-103.781 tagged_above=-999 required=5 tests=[AWL=-1.182, 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 XgHbqxPUxOBa for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:03:44 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4A48A11E81D5 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:03:40 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LlYrb-1W8K7w05lH-00bIKp for <ietf@ietf.org>; Tue, 29 Oct 2013 17:03:39 +0100
Message-ID: <526FDC52.3030808@gmx.de>
Date: Tue, 29 Oct 2013 17:03:30 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p1-messaging.all@tools.ietf.org, iesg@ietf.org
Subject: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:G4h3ATubrBMjyxzZwFlyVEaglWv8ZrI38vsm8MZIPOM6NJd7EkS yc72/VxAh30TDSTONXJGr3lLxuVuJOCDm5GJWT6JfmJwLtc5I6DIWzpfieKqm6b4HrzksWY YW9cz5qLVv3kT/R2n8HeRugJOp5/Me5bPz9raVa+1vqo33KCWd3mRpA8VAfyUuhO2HSRZeh g8vMrvd1+5vMpxjDCE89w==
Cc: ietf-http-wg@w3.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, 29 Oct 2013 16:03:50 -0000

On 2013-10-27 19:44, S Moonesamy wrote:
> ...
> In Section 6.4
>
>    "A client SHOULD limit the number of simultaneous open connections
>     that it maintains to a given server."
>
> There is an explanation about why a specific number is not included for
> this recommendation in the paragraphs following the above text.  I read
> Issue #131.  I don't see any discussion of the tradeoffs in Section
> 6.4.  The is a note about servers may reject an excessive number of
> connections from a client if they deem that it is abusive.
> ...

I have trouble parsing this comment. Do you see an issue here?

Best regards, Julian

From paf@frobbit.se  Tue Oct 29 09:04:09 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 5CA4211E8197 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:04:09 -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 kf+8OL3vbTpL for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:04:09 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 1427C11E829B for <ietf@ietf.org>; Tue, 29 Oct 2013 09:03:57 -0700 (PDT)
Received: from rev-2001-13c7-7003.lacnicxii.lacnic.net (unknown [IPv6:2001:13c7:7003:89:412b:1f27:b2f8:c2e4]) by mail.frobbit.se (Postfix) with ESMTPSA id 9DD7420521; Tue, 29 Oct 2013 17:03:52 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_1FDC6131-323D-4BE9-9D4C-9F42DD2ECB64"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: future of identifiers
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Date: Tue, 29 Oct 2013 12:03:43 -0400
Message-Id: <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1816)
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, 29 Oct 2013 16:04:09 -0000

--Apple-Mail=_1FDC6131-323D-4BE9-9D4C-9F42DD2ECB64
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On 29 okt 2013, at 10:38, Jari Arkko <jari.arkko@piuha.net> wrote:

> I have some ideas on what some of these trends might be. But what do =
the rest of you think? Where is identifier technology going, and what =
new things are on the horizon? What do we need to do with IDNs? DNSSEC? =
What will DANE lead to, and how will id-locator split techniques evolve =
& be deployed? How will applications or users think about identifiers in =
the future?
>=20
> More information at =
http://www.ietf.org/blog/2013/10/future-identifiers/

I think it is important to not restart discussions already held =
regarding different requirements on identifiers, requirements that in =
turn lead to various alternatives on how they are allocated, managed and =
resolved. I do not think one can have one identifier that fits all. =
Instead multiple kind of identifiers are needed. Because of requirements =
on uniqueness (absolute, low risk of collisions or not needed at all), =
persistence, human readable/understandable, whether allocation and =
resolution should be designed for read (lookups) or write (allocation), =
what the identifier is to be used for (see id/loc discussions).

    Patrik


--Apple-Mail=_1FDC6131-323D-4BE9-9D4C-9F42DD2ECB64
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSb9xfrMabGguI180RAq/zAJ96qzxQXA7GHSVDZXSuZnu6exxmxACgh7yS
lDWPjsuia12Pe1gxu7G/HHg=
=Jul+
-----END PGP SIGNATURE-----

--Apple-Mail=_1FDC6131-323D-4BE9-9D4C-9F42DD2ECB64--

From paul.hoffman@vpnc.org  Tue Oct 29 09:17:05 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 6778211E8164 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:17: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 4K85C6FtElUw for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:17:05 -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 F181411E8137 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:17:02 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id r9TGGvB0010658 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 09:16:59 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: future of identifiers
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
Date: Tue, 29 Oct 2013 09:16:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1816)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 16:17:05 -0000

On Oct 29, 2013, at 9:03 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

> I think it is important to not restart discussions already held =
regarding different requirements on identifiers, requirements that in =
turn lead to various alternatives on how they are allocated, managed and =
resolved. I do not think one can have one identifier that fits all. =
Instead multiple kind of identifiers are needed. Because of requirements =
on uniqueness (absolute, low risk of collisions or not needed at all), =
persistence, human readable/understandable, whether allocation and =
resolution should be designed for read (lookups) or write (allocation), =
what the identifier is to be used for (see id/loc discussions).

Having sat through many of those discussions with Patrik 15 years ago: =
+1

If ICANN wants to create and control some additional identifier spaces, =
let them spend/waste their resources on all those questions.

--Paul Hoffman=

From lear@cisco.com  Tue Oct 29 09:23:21 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 795E611E8169 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.439
X-Spam-Level: 
X-Spam-Status: No, score=-110.439 tagged_above=-999 required=5 tests=[AWL=0.160, 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 WEvEB0xKKhHL for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:23:16 -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 23D0C11E80F1 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1039; q=dns/txt; s=iport; t=1383063796; x=1384273396; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=nmPxAOv7m02MwZZk0pa0hUnM4nOn216Gl7rocUPuxNc=; b=INqPyWlT0XDRFRQf1C7gIGQuVY6PkzWIdyw03fxWqXl5p64SeEk882Vi oFbRUoZuNHl4sWaxjriLFt7EnN9z6r8GCz3Ur7zztRI52Sp1lN1cUepFs W5/8JhYyP7EbMQpmC8x4FqgjENkYk08y+GVFncvo16Y0gNys4sei5+7v0 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAH3gb1KQ/khR/2dsb2JhbABZgweEH7wigSoWdIIlAQEBBCMPAUURCxgCAgUWCwICCQMCAQIBKxoGAQwGAgEBiAOnOpJogSmOJYJqgUIDk2iEIpIIgyc7
X-IronPort-AV: E=Sophos;i="4.93,594,1378857600"; d="scan'208";a="18627972"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 29 Oct 2013 16:23:15 +0000
Received: from mctiny.local ([10.61.200.185]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9TGNATc008854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 16:23:11 GMT
Message-ID: <526FE0EE.3000608@cisco.com>
Date: Tue, 29 Oct 2013 17:23:10 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: future of identifiers
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>	<563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>
In-Reply-To: <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>
X-Enigmail-Version: 1.6
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: Tue, 29 Oct 2013 16:23:21 -0000

On 10/29/13 5:16 PM, Paul Hoffman wrote:
> On Oct 29, 2013, at 9:03 AM, Patrik FĂ¤ltstrĂ¶m <paf@frobbit.se> wrote:
>
>> I think it is important to not restart discussions already held regarding different requirements on identifiers, requirements that in turn lead to various alternatives on how they are allocated, managed and resolved. I do not think one can have one identifier that fits all. Instead multiple kind of identifiers are needed. Because of requirements on uniqueness (absolute, low risk of collisions or not needed at all), persistence, human readable/understandable, whether allocation and resolution should be designed for read (lookups) or write (allocation), what the identifier is to be used for (see id/loc discussions).
> Having sat through many of those discussions with Patrik 15 years ago: +1

And having chaired NSRG, + 1/2.  That is- it's always fair to look at
new developments, but let's at least be aware of what was covered by
others and build on their success (or avoid their failures).

Eliot

From paf@frobbit.se  Tue Oct 29 09:30: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 E1A4E21E809E for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:30:46 -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 DuLBYknDtoX9 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:30:46 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC9011E81B9 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:30:46 -0700 (PDT)
Received: from rev-2001-13c7-7003.lacnicxii.lacnic.net (unknown [IPv6:2001:13c7:7003:89:412b:1f27:b2f8:c2e4]) by mail.frobbit.se (Postfix) with ESMTPSA id C8EB41FEA9; Tue, 29 Oct 2013 17:30:43 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_8838B33F-0D9B-48E8-A369-DD733B944368"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: future of identifiers
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <526FE0EE.3000608@cisco.com>
Date: Tue, 29 Oct 2013 12:30:36 -0400
Message-Id: <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>	<563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org> <526FE0EE.3000608@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1816)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "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, 29 Oct 2013 16:30:47 -0000

--Apple-Mail=_8838B33F-0D9B-48E8-A369-DD733B944368
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 29 okt 2013, at 12:23, Eliot Lear <lear@cisco.com> wrote:

> On 10/29/13 5:16 PM, Paul Hoffman wrote:
>> On Oct 29, 2013, at 9:03 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
>>=20
>>> I think it is important to not restart discussions already held =
regarding different requirements on identifiers, requirements that in =
turn lead to various alternatives on how they are allocated, managed and =
resolved. I do not think one can have one identifier that fits all. =
Instead multiple kind of identifiers are needed. Because of requirements =
on uniqueness (absolute, low risk of collisions or not needed at all), =
persistence, human readable/understandable, whether allocation and =
resolution should be designed for read (lookups) or write (allocation), =
what the identifier is to be used for (see id/loc discussions).
>> Having sat through many of those discussions with Patrik 15 years =
ago: +1
>=20
> And having chaired NSRG, + 1/2.  That is- it's always fair to look at
> new developments, but let's at least be aware of what was covered by
> others and build on their success (or avoid their failures).

Just to make my point clear. I absolutely do believe more thinking is =
needed. What was done 15 years ago never finished. I claim partly =
because we did not know the answers to all questions.

My only point is that I think it would be sad to restart the discussion =
from zero. We both good and bad experience if we look back in history. =
We made mistakes then, but we also have successes. I here talk about =
URI-related discussions, whois++ (etc), Dublin Core, OID and what not.

Same with the 10+(?) years of ID/Loc split discussions. Lots and lots of =
experience.=20

And of course the experience enterprises like Facebook, Twitter etc have =
from their what I would call private namespaces.

   Patrik


--Apple-Mail=_8838B33F-0D9B-48E8-A369-DD733B944368
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iD8DBQFSb+KsrMabGguI180RAl3EAJwLsaWC5aeWX9tNVeJtwOy0frDv5gCfUtZy
iLwaerOXCaQbYgO+ASs54k0=
=Ppuz
-----END PGP SIGNATURE-----

--Apple-Mail=_8838B33F-0D9B-48E8-A369-DD733B944368--

From presnick@qti.qualcomm.com  Tue Oct 29 09:33:58 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 7B34111E814D for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.645
X-Spam-Level: 
X-Spam-Status: No, score=-102.645 tagged_above=-999 required=5 tests=[AWL=-0.046, 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 TOe0hSkVLGOT for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 09:33:54 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id ABF2021F9D55 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:33:47 -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=1383064427; x=1414600427; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Vry+WgjT5QeyPuILZpT4XoxfHYrXPmDqF6zIneUUfsg=; b=t5fuvDFRPAVf/9Su3CV8LzZx44P8kfnXmrWSkCEqi8kvE+K9ulZPowcz avOmqjiqrhb6PrCvcU7jmlFcNdypPtlQWbvrUQdv0UoriTuHAS3QbYDDw qkRb3XtWhPhKOEwPrn6udDGJ4wAbockVBzJQkNs+Po3GKkvTPcIHRz0Oi k=;
X-IronPort-AV: E=McAfee;i="5400,1158,7242"; a="54684585"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth01.qualcomm.com with ESMTP; 29 Oct 2013 09:33:27 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7242"; a="630040905"
Received: from nasanexhc02.na.qualcomm.com ([172.30.48.24]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Oct 2013 09:33:27 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC02.na.qualcomm.com (172.30.48.24) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 29 Oct 2013 09:33:27 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 29 Oct 2013 09:33:26 -0700
Message-ID: <526FE354.40106@qti.qualcomm.com>
Date: Tue, 29 Oct 2013 11:33:24 -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: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net>
In-Reply-To: <6.2.5.6.2.20131008054041.0d74aa88@resistor.net>
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: Tue, 29 Oct 2013 16:33:58 -0000

Last of the messages in my list:

On 10/8/13 3:56 PM, S Moonesamy wrote:
> The intended status of draft-resnick-on-consensus-05 is 
> Informational.  What we have here is a document about consensus which 
> will reflect the consensus of the IETF.  Should the document reflect 
> the consensus of the IETF or not?

See other messages. I think the intention is to make it a consensus 
Informational document.

> ...Section 1...introduces the term "full consensus".  I took a quick 
> look and I found at least one occurrence of the term in IETF 
> discussions [3].  However, none of the IETF process documents use that 
> term.

See my reply to PSA. I don't think that there's a real need for a formal 
definition. I've thrown in the word "unanimity" to clarify.

>   "If the chair of a working group determines that a technical issue
>    brought forward by an objector has been truly considered by the
>    working group, and the working group has made an informed decision
>    that the objection has been answered or is not enough of a
>    technical problem to prevent moving forward, the chair can declare
>    that there is rough consensus to go forward, the objection
>    notwithstanding."
>
> The word "objector" emphasizes that there is one person who dissents.  
> My preference is to consider the objection and address it instead of 
> viewing the issue as dissent from one person.

That's what the example above says. It is the *objection* that is 
answered, not the objector. It is, after all, a hypothetical.

>    "This document attempts to explain some features of rough consensus,
>     explain what is not rough consensus, and suggest ways that we might
>     achieve rough consensus and judge it in the IETF."
>
> The title of the document is "on consensus and humming in the IETF".  
> According to the above sentence the document attempts to discuss about 
> rough consensus.  In my opinion there a nuance between "consensus" and 
> "rough consensus".

It's more than an nuance. It is the distinction made between sections 2 
and 3.

> As a quick reaction I would say that rough consensus provides a faster 
> path to shape up a proposal.  It helps to cut down on document 
> delivery time to the IESG.  The consensus part is sought by getting a 
> broader perspective.

I'm not clear on what if any change you intend here.

> Section 2 sounds like objection-based processing.  A binary choice 
> (re. technical question) can end up polarizing a discussion.  The 
> section provides a good discussion about lack of disagreement.

See my response to Ted on this point. I think objection-based processing 
is part of how we come to consensus (rough or otherwise). And I think 
this section does talk about the problems of posing binary choices. I've 
added text to section 5 on this.

> One of the questions I wondered about is whether the person making the 
> determination should use technical judgement or whether the person 
> should only make a determination about the comments received.  I 
> mentioned in an unrelated discussion that if it is the consensus of 
> the group that the sky is green, that's what goes in the document.  
> The person making the determination can flag it as an issue as a 
> matter of technical judgement.

I think section 3 is pretty clear that the chair must exercise technical 
judgment in many cases. Your hypothetical is the extreme case not 
mentioned in the document. If the group says that the sky is green, 
*and* nobody questions that assertion, *and* the chair suspects the sky 
is not green, I believe it is reasonable for the chair to pose the 
question to the WG: "Are we sure the sky is green?" If the working group 
simply says "Yes" without explanation, I think the chair is within 
bounds to say, just as they are if someone else had raised the issue, "I 
don't think the group has truly considered and weighed this issue such 
that I can declare (rough) consensus on this point." But this must be 
done *extremely* carefully. Chairs who insert their technical judgment 
too often or too heavy-handedly risk losing the confidence of the group 
as an impartial consensus caller. Better might be for the chair to 
(perhaps quietly) solicit a review from a sky color expert from another 
working group, asking for them to comment on this sky being green issue. 
But having the document go forward with a technical issue that the chair 
knows about but that the rest of the working group hasn't noticed is, I 
think, to shirk responsibility as a member of the community.

All that said, I wonder if it's necessary to say this in the document. 
It's a more general comment about the chair role rather than about 
consensus per se.

> I'll highlight a point from Section 3:
>
>   "Remember, if the objector feels that the issue is so essential that it
>    must be attended to, they always have the option to file an appeal."
>
> There are very few people who exercise that option.

I think (hope) that if we start thinking about consensus the way the 
document describes, appeals (at least in the early form, where it's 
simply discussing the issue with the chair or the AD) would not be 
nearly so fraught.

> According to the title of Section 4 humming should be the start of a 
> conversation, not the end.  BCP 25 states that:
>
>   "Consensus can be determined by a show of hands, humming, or any
>    other means on which the WG agrees (by rough consensus, of course)."
>
> I am not sure whether hums are for a starting point or not.  It can be 
> argued in different ways, for example, see Section 4.  Humming helps 
> to get a sense of the room without people making a decision under 
> duress.  It is a useful way to resolve a controversy.  I would say 
> that it ties in Section 5, i.e. consensus is the path, not the 
> destination.  A show of hands is a disguised way to vote [4].

Yup. See my response to Russ, and some of the changes I've made in the 
document. I think this is handled more clearly.

> Section 5 identifies a few issues with the way people talk about 
> "consensus".  I understand what Pete Resnick wrote as he has explained 
> that to me in an unrelated discussion.  The text discusses about 
> "making the call".  I don't know whether the reader will easily 
> understand the meaning of that.

I've added a bit to section 5. Send text if you think it is not sufficient.

> Section 6 and Section 7 attempt to explain that a high percentage of 
> votes in a direction does not necessarily mean that there is rough 
> consensus for that.  I agree with the conclusion in Section 8.

Excellent.

With that, I will send out a new version ASAP. As I said earlier, Jari 
has pushed the magic "please let it through" buttons so that I can post 
this week.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From bmanning@isi.edu  Tue Oct 29 10:03:28 2013
Return-Path: <bmanning@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 542EA21E8113 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 10:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.449
X-Spam-Level: 
X-Spam-Status: No, score=-104.449 tagged_above=-999 required=5 tests=[AWL=1.850, 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 SBxdzJhBGw5I for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 10:03:15 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5CA21E8186 for <ietf@ietf.org>; Tue, 29 Oct 2013 09:45:15 -0700 (PDT)
Received: from [192.168.254.18] ([207.87.41.70]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r9TGi1Ru019734 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 29 Oct 2013 09:44:12 -0700 (PDT)
Subject: Re: future of identifiers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
Date: Tue, 29 Oct 2013 09:44:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F5E4FB-2D09-42AF-ACA1-90EEC57CBA98@isi.edu>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>	<563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org> <526FE0EE.3000608@cisco.com> <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "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, 29 Oct 2013 17:03:28 -0000

On 29October2013Tuesday, at 9:30, Patrik F=E4ltstr=F6m wrote:

>=20
> On 29 okt 2013, at 12:23, Eliot Lear <lear@cisco.com> wrote:
>=20
>> On 10/29/13 5:16 PM, Paul Hoffman wrote:
>>> On Oct 29, 2013, at 9:03 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
>>>=20
>>>> I think it is important to not restart discussions already held =
regarding different requirements on identifiers, requirements that in =
turn lead to various alternatives on how they are allocated, managed and =
resolved. I do not think one can have one identifier that fits all. =
Instead multiple kind of identifiers are needed. Because of requirements =
on uniqueness (absolute, low risk of collisions or not needed at all), =
persistence, human readable/understandable, whether allocation and =
resolution should be designed for read (lookups) or write (allocation), =
what the identifier is to be used for (see id/loc discussions).
>>> Having sat through many of those discussions with Patrik 15 years =
ago: +1
>>=20
>> And having chaired NSRG, + 1/2.  That is- it's always fair to look at
>> new developments, but let's at least be aware of what was covered by
>> others and build on their success (or avoid their failures).
>=20
> Just to make my point clear. I absolutely do believe more thinking is =
needed. What was done 15 years ago never finished. I claim partly =
because we did not know the answers to all questions.
>=20
> My only point is that I think it would be sad to restart the =
discussion from zero. We both good and bad experience if we look back in =
history. We made mistakes then, but we also have successes. I here talk =
about URI-related discussions, whois++ (etc), Dublin Core, OID and what =
not.
>=20
> Same with the 10+(?) years of ID/Loc split discussions. Lots and lots =
of experience.=20
>=20
> And of course the experience enterprises like Facebook, Twitter etc =
have from their what I would call private namespaces.
>=20
>   Patrik
>=20
	lets not forget x500 and quipu & giant tortoise=85

/bill=

From cdel@firsthand.net  Tue Oct 29 10:40:09 2013
Return-Path: <cdel@firsthand.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 E842221F9DCE for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 10:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.638
X-Spam-Level: 
X-Spam-Status: No, score=-0.638 tagged_above=-999 required=5 tests=[AWL=1.661,  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 mE1LZpeyNhad for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 10:40:08 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id D637F21E8063 for <ietf@ietf.org>; Tue, 29 Oct 2013 10:39:32 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=firsthand.net; b=RWlfBG/YnBuKyUZMtt46YsKEdUVoTA5a1f8nWhoH+eXi8t/iSK3Lyv7ml8KGH/wXABrmc0dGXkF9/a9ygosJcCht7mM8hv6RVhcmthsyk1SsGtqHQJU1ORul6p0PCUjk; h=X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from orionlocal.local (host-78-145-247-11.as13285.net [78.145.247.11]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id 04193144001; Tue, 29 Oct 2013 16:39:19 +0000 (GMT)
Message-ID: <526FF2D0.4070602@firsthand.net>
Date: Tue, 29 Oct 2013 17:39:28 +0000
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: future of identifiers
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>	<563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org> <526FE0EE.3000608@cisco.com> <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
In-Reply-To: <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "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, 29 Oct 2013 17:40:09 -0000

Maybe I've misunderstood but if this discussion (which I think is valid
to do) is framed for ICANN it is likely to miss or ignore current work
stimulated because of perceived blockages in the ICANN hierarchical model.

Just saying.



C


> Patrik Fältström <mailto:paf@frobbit.se>
> 29 October 2013 16:30
>
> Just to make my point clear. I absolutely do believe more thinking is
> needed. What was done 15 years ago never finished. I claim partly
> because we did not know the answers to all questions.
>
> My only point is that I think it would be sad to restart the
> discussion from zero. We both good and bad experience if we look back
> in history. We made mistakes then, but we also have successes. I here
> talk about URI-related discussions, whois++ (etc), Dublin Core, OID
> and what not.
>
> Same with the 10+(?) years of ID/Loc split discussions. Lots and lots
> of experience.
>
> And of course the experience enterprises like Facebook, Twitter etc
> have from their what I would call private namespaces.
>
> Patrik
>
> Eliot Lear <mailto:lear@cisco.com>
> 29 October 2013 16:23
>
> And having chaired NSRG, + 1/2. That is- it's always fair to look at
> new developments, but let's at least be aware of what was covered by
> others and build on their success (or avoid their failures).
>
> Eliot
> Jari Arkko <mailto:jari.arkko@piuha.net>
> 29 October 2013 14:38
> For background, when I visited the ICANN meeting last summer, they
> were about to launch a set of panels to advice themselves about key
> topics in coming years. I promised to join one of them, on identifier
> technology innovation (along with a few other IETFers). The topic for
> this effort is future evolution of DNS and other identifiers,
> including relevant security and management aspects. The viewpoint is
> primarily to look at this from ICANN’s angle, but of course the matter
> is interesting to us others as well.
>
> And perhaps we at the IETF should also understand the same things.
> Hence this e-mail.
>
> I have some ideas on what some of these trends might be. But what do
> the rest of you think? Where is identifier technology going, and what
> new things are on the horizon? What do we need to do with IDNs?
> DNSSEC? What will DANE lead to, and how will id-locator split
> techniques evolve & be deployed? How will applications or users think
> about identifiers in the future?
>
> More information at http://www.ietf.org/blog/2013/10/future-identifiers/
>
> Jari
>

From brian.e.carpenter@gmail.com  Tue Oct 29 12:40: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 B4C8611E82A0 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.378
X-Spam-Level: 
X-Spam-Status: No, score=-102.378 tagged_above=-999 required=5 tests=[AWL=-0.079, 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 WqRqLBjpIBBJ for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:40:30 -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 AD69F11E829D for <ietf@ietf.org>; Tue, 29 Oct 2013 12:37:50 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id mc17so305270pbc.21 for <ietf@ietf.org>; Tue, 29 Oct 2013 12:37: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=IbQtqkuKbfb3GrBuYkuDIypvtefDKLNlQzCWX6n99+w=; b=QXeI/k7bMoTnMMlUl0FZhIIcvOo/A7TziuWsgKsq8kPljKGRTFCC+upIhb+uUk0BjD LKBgN+RU8Y7qFTjVNsHpfgwiIrefJr/te37otH5hCpPahBpVCCM4lz1X3ZlRTWkENSqH L7AfGl2Qe/zD8Lzh04s2D/hE1GMsdOrBLDhCFIugbz7HWmJwUqM5QuOoXcZopNJXl9Gd PwatsTcJCCSd5W4GNrvJ0Op9PZGStHL7AgwGToZhdBnuVt4s1w4zlAU6fExkOKxnpVF4 v561niofccW/JycVGohUqRAL/drTyMwdIP39cELlXUQAJRNjwVGtyhWQ8TIz2MHOSYHq MfpQ==
X-Received: by 10.68.26.202 with SMTP id n10mr1128230pbg.97.1383075433419; Tue, 29 Oct 2013 12:37:13 -0700 (PDT)
Received: from [192.168.178.20] (89.200.69.111.dynamic.snap.net.nz. [111.69.200.89]) by mx.google.com with ESMTPSA id pu5sm44386397pac.21.2013.10.29.12.37.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 12:37:12 -0700 (PDT)
Message-ID: <52700E6A.2060102@gmail.com>
Date: Wed, 30 Oct 2013 08:37:14 +1300
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: future of identifiers
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>	<563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>	<98DF3DC1-2B5E-43E5-9AE4-0213BD73F3DC@vpnc.org>	<526FE0EE.3000608@cisco.com> <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
In-Reply-To: <6B79BCF6-B899-4DA5-8A55-1D4DF15FEAF9@frobbit.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "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, 29 Oct 2013 19:40:33 -0000

On 30/10/2013 05:30, Patrik F=C3=A4ltstr=C3=B6m wrote:
> On 29 okt 2013, at 12:23, Eliot Lear <lear@cisco.com> wrote:
>=20
>> On 10/29/13 5:16 PM, Paul Hoffman wrote:
>>> On Oct 29, 2013, at 9:03 AM, Patrik F=C3=A4ltstr=C3=B6m <paf@frobbit.=
se> wrote:
>>>
>>>> I think it is important to not restart discussions already held rega=
rding different requirements on identifiers, requirements that in turn le=
ad to various alternatives on how they are allocated, managed and resolve=
d. I do not think one can have one identifier that fits all. Instead mult=
iple kind of identifiers are needed. Because of requirements on uniquenes=
s (absolute, low risk of collisions or not needed at all), persistence, h=
uman readable/understandable, whether allocation and resolution should be=
 designed for read (lookups) or write (allocation), what the identifier i=
s to be used for (see id/loc discussions).
>>> Having sat through many of those discussions with Patrik 15 years ago=
: +1
>> And having chaired NSRG, + 1/2.  That is- it's always fair to look at
>> new developments, but let's at least be aware of what was covered by
>> others and build on their success (or avoid their failures).
>=20
> Just to make my point clear. I absolutely do believe more thinking is n=
eeded. What was done 15 years ago never finished. I claim partly because =
we did not know the answers to all questions.

Indeed. I have some half-baked thoughts about some aspects at
http://www.cs.auckland.ac.nz/~brian/IPAddressesConsideredHarmful.pdf

   Brian

>=20
> My only point is that I think it would be sad to restart the discussion=
 from zero. We both good and bad experience if we look back in history. W=
e made mistakes then, but we also have successes. I here talk about URI-r=
elated discussions, whois++ (etc), Dublin Core, OID and what not.
>=20
> Same with the 10+(?) years of ID/Loc split discussions. Lots and lots o=
f experience.=20
>=20
> And of course the experience enterprises like Facebook, Twitter etc hav=
e from their what I would call private namespaces.
>=20
>    Patrik
>=20


From jnc@mercury.lcs.mit.edu  Tue Oct 29 12:57:37 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 584C621F9B65 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.497
X-Spam-Level: 
X-Spam-Status: No, score=-6.497 tagged_above=-999 required=5 tests=[AWL=0.102,  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 9S59XeW-GLdS for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 12:57:06 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 400CB11E8294 for <ietf@ietf.org>; Tue, 29 Oct 2013 12:56:35 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 4E19418C180; Tue, 29 Oct 2013 15:56:34 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: future of identifiers
Message-Id: <20131029195634.4E19418C180@mercury.lcs.mit.edu>
Date: Tue, 29 Oct 2013 15:56:34 -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: Tue, 29 Oct 2013 19:57:38 -0000

    > From: Eliot Lear <lear@cisco.com>

    > And having chaired NSRG

It might be worth observing that NSRG was focused on new namespaces for the
lower-middle part of the stack (e.g. TCP endpoint names), whereas I get
the impression from Jari's note that that was about names further up
(application, etc).

But maybe I got an incorrect impression?

	Noel

From julian.reschke@gmx.de  Tue Oct 29 13:22:42 2013
Return-Path: <julian.reschke@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 6321A11E8189 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.191
X-Spam-Level: 
X-Spam-Status: No, score=-103.191 tagged_above=-999 required=5 tests=[AWL=-0.592, 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 dHU56amAHkU4 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:22:36 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id E0BD811E8294 for <ietf@ietf.org>; Tue, 29 Oct 2013 13:22:28 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.127.91]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LiHc7-1VyEbk2mvr-00nNNH for <ietf@ietf.org>; Tue, 29 Oct 2013 21:22:23 +0100
Message-ID: <527018FD.2010405@gmx.de>
Date: Tue, 29 Oct 2013 21:22:21 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: RFC2119 keywords in registration requirements
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:UMVxHo/+Sy2Pbwj7e3nuGs6o9p2BoLKobLoMZ6ahvAMfrT9U2fc +AgkprmzDGjFkFEfieWNO1fo8gCYLyqCN1dKSzUBcBSWoWyo+EVNPId8YrGZRdP8hgSIHuv lyvxz/8X9Lu3ut2Dr+PplnJfckddpN/FtW8tXRsuCdJ37SwOkuKdA7VjjNoEigSFU5u6y4P Hi8kn+5tC2i8ojHdU/+SA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 20:22:42 -0000

So,

while getting IETF LC comment for httpbis, one reviewer complains about 
the use of RFC2119 in registration procedures, while another one 
complains about the lack of them in a different place.

Can we please clarify what's the right approach?

Best regards, Julian

/me thinks RFC2119 do not belong there.

From sob@harvard.edu  Tue Oct 29 13:29:28 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 C023521F9B35 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:29:28 -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 wBsyR-MrRWwI for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:29:19 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 49B8921E80A3 for <ietf@ietf.org>; Tue, 29 Oct 2013 13:29:14 -0700 (PDT)
Received: from ENTWEDGE0000003.university.harvard.edu (entwedge0000003.university.harvard.edu [10.35.202.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id DF6F3E9C8D; Tue, 29 Oct 2013 16:29:13 -0400 (EDT)
Received: from ENTWHUBT0000006.university.harvard.edu (192.168.236.26) by entwedge0000003.university.harvard.edu (10.35.202.50) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 29 Oct 2013 16:28:57 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.5]) by ENTWHUBT0000006.university.harvard.edu ([192.168.236.28]) with mapi id 14.03.0146.000; Tue, 29 Oct 2013 16:29:13 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OWHudKr7bkZu0OW/g/gd3uXUw==
Date: Tue, 29 Oct 2013 20:29:12 +0000
Message-ID: <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu>
References: <527018FD.2010405@gmx.de>
In-Reply-To: <527018FD.2010405@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [70.42.157.32]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0FE69B0E464F4F46BDDFC0075A7787C0@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 29 Oct 2013 20:29:29 -0000

seems to me to be completely reasonable to say MUST include the number of t=
he RFC that describes=20
the protocol being registered (for example)

Scott

On Oct 29, 2013, at 4:22 PM, Julian Reschke <julian.reschke@gmx.de> wrote:

> So,
>=20
> while getting IETF LC comment for httpbis, one reviewer complains about t=
he use of RFC2119 in registration procedures, while another one complains a=
bout the lack of them in a different place.
>=20
> Can we please clarify what's the right approach?
>=20
> Best regards, Julian
>=20
> /me thinks RFC2119 do not belong there.

Scott Bradner

Harvard University Information Technology
Innovation & Architecture
+1 617 495 3864
1350 Mass Ave., Room 760
Cambridge, MA 02138
www.harvard.edu/huit


From julian.reschke@gmx.de  Tue Oct 29 13:40:52 2013
Return-Path: <julian.reschke@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 243EE11E818D for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:40:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.145
X-Spam-Level: 
X-Spam-Status: No, score=-103.145 tagged_above=-999 required=5 tests=[AWL=-0.546, 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 N8aqKj3Tcd9Q for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:40:22 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 360C311E8187 for <ietf@ietf.org>; Tue, 29 Oct 2013 13:40:03 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.127.91]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MQdAP-1VEWYm0NGn-00U0TE for <ietf@ietf.org>; Tue, 29 Oct 2013 21:40:02 +0100
Message-ID: <52701D1D.3030004@gmx.de>
Date: Tue, 29 Oct 2013 21:39:57 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: RFC2119 keywords in registration requirements
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu>
In-Reply-To: <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:TUoH5t60iHAUZedok06JPKzEhG0EuZPWytxfyaHR/t9eLrhbNQi vcwMqlEboj25Mq4my/dgM2VhU3e9LGwWtUNWWyKBWgGmtYIsUyHj3tGHEz3MfD5wdaob2/9 rNEqCasS5e8eXCZm+/NsHK1iWle/0ZZ9wYvkkeCJbc1ZJS8BtWeuuraiNk1bdqc8MMDkawP wZjmWZLYHiEmcwN19ExaA==
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: Tue, 29 Oct 2013 20:40:52 -0000

On 2013-10-29 21:29, Bradner, Scott wrote:
> seems to me to be completely reasonable to say MUST include the number of the RFC that describes
> the protocol being registered (for example)
>
> Scott

But then:

> 6. Guidance in the use of these Imperatives
>
>    Imperatives of the type defined in this memo must be used with care
>    and sparingly.  In particular, they MUST only be used where it is
>    actually required for interoperation or to limit behavior which has
>    potential for causing harm (e.g., limiting retransmisssions)  For
>    example, they must not be used to try to impose a particular method
>    on implementors where the method is not required for
>    interoperability.

To me this indicates that we should keep them out of registrations 
procedures.

(I also note that the "MUST" in the text I quoted shouldn't been used if 
the text followed its own advice :-).

Best regards, Julian

From sob@harvard.edu  Tue Oct 29 13:46:41 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 53ED411E824C for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:46:41 -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 gt0H-4j9Wbgg for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:46:34 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id BE5B611E818D for <ietf@ietf.org>; Tue, 29 Oct 2013 13:46:27 -0700 (PDT)
Received: from ENTWEDGE0000000.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 249C0E8AFB; Tue, 29 Oct 2013 16:46:25 -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.3.146.0; Tue, 29 Oct 2013 16:45:30 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.5]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.03.0146.000; Tue, 29 Oct 2013 16:46:24 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OWHudKr7bkZu0OW/g/gd3uXU5oMZ1KAgAABywA=
Date: Tue, 29 Oct 2013 20:46:24 +0000
Message-ID: <15826A6D-1978-4501-AA83-FCD1E6B54213@harvard.edu>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de>
In-Reply-To: <52701D1D.3030004@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [70.42.157.32]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <854E17FEBEB24243A96E89DF7C42C5BD@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 29 Oct 2013 20:46:43 -0000

see rfc 2418 page 3 as well as RFC 2434 page 3 for an example of non-protoc=
ol uses of 2119 terms

fwiw - I have seen 2119 terms used in registration type RFCs for rather man=
y years=20
I think it is too late to unwind that clock

Scott

Scott Bradner

Harvard University Information Technology
Innovation & Architecture
+1 617 495 3864
1350 Mass Ave., Room 760
Cambridge, MA 02138
www.harvard.edu/huit

On Oct 29, 2013, at 4:39 PM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-10-29 21:29, Bradner, Scott wrote:
>> seems to me to be completely reasonable to say MUST include the number o=
f the RFC that describes
>> the protocol being registered (for example)
>>=20
>> Scott
>=20
> But then:
>=20
>> 6. Guidance in the use of these Imperatives
>>=20
>>   Imperatives of the type defined in this memo must be used with care
>>   and sparingly.  In particular, they MUST only be used where it is
>>   actually required for interoperation or to limit behavior which has
>>   potential for causing harm (e.g., limiting retransmisssions)  For
>>   example, they must not be used to try to impose a particular method
>>   on implementors where the method is not required for
>>   interoperability.
>=20
> To me this indicates that we should keep them out of registrations proced=
ures.
>=20
> (I also note that the "MUST" in the text I quoted shouldn't been used if =
the text followed its own advice :-).
>=20
> Best regards, Julian


From julian.reschke@gmx.de  Tue Oct 29 13:49:07 2013
Return-Path: <julian.reschke@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 3D42F11E814C for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.106
X-Spam-Level: 
X-Spam-Status: No, score=-103.106 tagged_above=-999 required=5 tests=[AWL=-0.507, 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 xSjlLHiWBSQq for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:49:01 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 18E6F11E818D for <ietf@ietf.org>; Tue, 29 Oct 2013 13:49:00 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.127.91]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M5r89-1Vr7Ao3XtR-00xpe8 for <ietf@ietf.org>; Tue, 29 Oct 2013 21:49:00 +0100
Message-ID: <52701F38.7070506@gmx.de>
Date: Tue, 29 Oct 2013 21:48:56 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: RFC2119 keywords in registration requirements
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <15826A6D-1978-4501-AA83-FCD1E6B54213@harvard.edu>
In-Reply-To: <15826A6D-1978-4501-AA83-FCD1E6B54213@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:2RuiK1crc2ePmpnHORD9Zm/f+J8rQ6V2DZVoE28q/2nxgeW2RKp JxWzDBypgKuEYQwrR6nZoEuf8h3gWGYHwjLUXbGBEo2me6FrsGjp2ScBqbmuFadXiMsQGYa Ldgmkcuut0aKQl2BOvxcnVKgpwwWr+LRDCgY5tGA7G9n+VK+au5UMpEvF6/QX+Y7pVfugQi 7iZ8MwuBwGya87MMe/BPQ==
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: Tue, 29 Oct 2013 20:49:07 -0000

On 2013-10-29 21:46, Bradner, Scott wrote:
> see rfc 2418 page 3 as well as RFC 2434 page 3 for an example of non-protocol uses of 2119 terms
>
> fwiw - I have seen 2119 terms used in registration type RFCs for rather many years
> I think it is too late to unwind that clock
>
> Scott
>
> Scott Bradner

Well yes, I've seen that too.

But there *is* confusion about whether it's the right approach, and it 
would be really cool if there was some consistency with respect to this.

Best regards, Julian


From sob@harvard.edu  Tue Oct 29 13:50:10 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 A866911E814C for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:50:10 -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 Zu3VqM+qjCiZ for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:50:04 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 93F3B11E827E for <ietf@ietf.org>; Tue, 29 Oct 2013 13:50:02 -0700 (PDT)
Received: from ENTWEDGE0000001.university.harvard.edu (entwedge0000001.university.harvard.edu [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 56628E8AFB; Tue, 29 Oct 2013 16:50:02 -0400 (EDT)
Received: from ENTWCASX0000010.university.harvard.edu (192.168.236.50) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 29 Oct 2013 16:49:17 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.5]) by ENTWCASX0000010.university.harvard.edu ([::1]) with mapi id 14.03.0146.000; Tue, 29 Oct 2013 16:50:02 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OWHudKr7bkZu0OW/g/gd3uXU5oMZ1KAgAABywCAAAC3AIAAAE0A
Date: Tue, 29 Oct 2013 20:50:01 +0000
Message-ID: <E522C252-5FC3-4917-9C9C-B59F56649759@harvard.edu>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <15826A6D-1978-4501-AA83-FCD1E6B54213@harvard.edu> <52701F38.7070506@gmx.de>
In-Reply-To: <52701F38.7070506@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [70.42.157.32]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3F247536632E004CA0A49E24B58CDC99@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 29 Oct 2013 20:50:10 -0000

yup

Scott=20

On Oct 29, 2013, at 4:48 PM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-10-29 21:46, Bradner, Scott wrote:
>> see rfc 2418 page 3 as well as RFC 2434 page 3 for an example of non-pro=
tocol uses of 2119 terms
>>=20
>> fwiw - I have seen 2119 terms used in registration type RFCs for rather =
many years
>> I think it is too late to unwind that clock
>>=20
>> Scott
>>=20
>> Scott Bradner
>=20
> Well yes, I've seen that too.
>=20
> But there *is* confusion about whether it's the right approach, and it wo=
uld be really cool if there was some consistency with respect to this.
>=20
> Best regards, Julian
>=20


From paul.hoffman@vpnc.org  Tue Oct 29 13:57:31 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 7AA7C11E81B4 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:57: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=[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 iwz3ceLZ4kdX for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 13:57:30 -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 ABA8E11E818D for <ietf@ietf.org>; Tue, 29 Oct 2013 13:57:25 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id r9TKvHvL019620 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 13:57:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: RFC2119 keywords in registration requirements
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu>
Date: Tue, 29 Oct 2013 13:57:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7064681F-4BA2-470E-A302-8E393800CA69@vpnc.org>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1816)
Cc: Julian Reschke <julian.reschke@gmx.de>, 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: Tue, 29 Oct 2013 20:57:31 -0000

On Oct 29, 2013, at 1:29 PM, Bradner, Scott <sob@harvard.edu> wrote:

> seems to me to be completely reasonable to say MUST include the number =
of the RFC that describes=20
> the protocol being registered (for example)

It is also completely reasonable to say "needs to include" as well.

--Paul Hoffman=

From barryleiba.mailing.lists@gmail.com  Tue Oct 29 14:07:08 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 5000911E81C9 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.952
X-Spam-Level: 
X-Spam-Status: No, score=-101.952 tagged_above=-999 required=5 tests=[AWL=0.025, 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 I75OgEkc9zyO for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:05 -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 1682D11E81DF for <ietf@ietf.org>; Tue, 29 Oct 2013 14:06:53 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id q12so310203vbe.27 for <ietf@ietf.org>; Tue, 29 Oct 2013 14:06:47 -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:message-id:subject :from:to:cc:content-type; bh=sMCfe7OArdgL+PXBeiazC8O//uIfZN7F7/SZl4oO03Q=; b=wUMTerilUwe11e6oEOOANFEb9U/+Lw0/AwuHQr06+ajf4XxdjSaL1FafazNwCinU0U UwUUUWzYWqF+57fp1/IwleYApQiwFJy/GCa4URdE4xhxWX9/1CPJCJO4Ibw2mjpF4bXJ GUPcMZQn8rMdQ1r7Bg6NVSSfwBAsLO1+aTMZZPSp/4Z92re2vxoHuSqtcbquYVTxdWkg eD1oFj1uauiikr+8QYb+gUK3RUVp8hLrQqgef9IqG3eDNlEwdQze47tMuD+DAZLKMqp2 xvnfOEboPW+8E7QJOaJrebKQs2LJB5MZTWLf84Z7cxWQGBv4JHykZjcAs+idyWv8c18E 5Y8Q==
MIME-Version: 1.0
X-Received: by 10.220.76.201 with SMTP id d9mr314099vck.49.1383080806919; Tue, 29 Oct 2013 14:06:46 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Tue, 29 Oct 2013 14:06:46 -0700 (PDT)
In-Reply-To: <52701D1D.3030004@gmx.de>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de>
Date: Tue, 29 Oct 2013 17:06:46 -0400
X-Google-Sender-Auth: giw2tbkMuxMRiZTD9GITUTtn8qk
Message-ID: <CAC4RtVAhNcXrOPhms=6+LNdiJZF5cj6gJUH2Kg=Pkru=g4A8bw@mail.gmail.com>
Subject: Re: RFC2119 keywords in registration requirements
From: Barry Leiba <barryleiba@computer.org>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary=001a11c2cfb03135ed04e9e7985b
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: Tue, 29 Oct 2013 21:07:08 -0000

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

First, I think we have to take the question of whether and when to use 2119
key words into the context of the document we're writing.  BCPs and
Informational documents can and do use them, but they use them in somewhat
different ways than Standards Track documents do, while still maintaining
the spirit of that text you quote from RFC 2119.

Second, I bristle when I see instructions to IANA in the form of "IANA MUST
[do this]."  We should not use 2119 key words in registration information
in that way.

Third, as instructions to registrants, I think it's absolutely fine to say
"you MUST [include this information," and "you SHOULD [include that
information]," and so on.  I think that respects the spirit of 2119, in
that things are more likely to interoperate if the documentation of
registered values is up to snuff.

Barry

On Tuesday, October 29, 2013, Julian Reschke wrote:

> On 2013-10-29 21:29, Bradner, Scott wrote:
>
>> seems to me to be completely reasonable to say MUST include the number of
>> the RFC that describes
>> the protocol being registered (for example)
>>
>> Scott
>>
>
> But then:
>
>  6. Guidance in the use of these Imperatives
>>
>>    Imperatives of the type defined in this memo must be used with care
>>    and sparingly.  In particular, they MUST only be used where it is
>>    actually required for interoperation or to limit behavior which has
>>    potential for causing harm (e.g., limiting retransmisssions)  For
>>    example, they must not be used to try to impose a particular method
>>    on implementors where the method is not required for
>>    interoperability.
>>
>
> To me this indicates that we should keep them out of registrations
> procedures.
>
> (I also note that the "MUST" in the text I quoted shouldn't been used if
> the text followed its own advice :-).
>
> Best regards, Julian
>

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

First, I think we have to take the question of whether and when to use 2119=
 key words into the context of the document we&#39;re writing. =A0BCPs and =
Informational documents can and do use them, but they use them in somewhat =
different ways than Standards Track documents do, while still maintaining t=
he spirit of that text you quote from RFC 2119.<div>
<br></div><div>Second, I bristle when I see instructions to IANA in the for=
m of &quot;IANA MUST [do this].&quot; =A0We should not use 2119 key words i=
n registration information in that way.</div><div><br></div><div>Third, as =
instructions to registrants, I think it&#39;s absolutely fine to say &quot;=
you MUST [include this information,&quot; and &quot;you SHOULD [include tha=
t information],&quot; and so on. =A0I think that respects the spirit of 211=
9, in that things are more likely to interoperate if the documentation of r=
egistered values is up to snuff.</div>
<div><br></div><div>Barry<br><br>On Tuesday, October 29, 2013, Julian Resch=
ke  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">On 2013-10-29 21:29, Bradner, =
Scott wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
seems to me to be completely reasonable to say MUST include the number of t=
he RFC that describes<br>
the protocol being registered (for example)<br>
<br>
Scott<br>
</blockquote>
<br>
But then:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
6. Guidance in the use of these Imperatives<br>
<br>
=A0 =A0Imperatives of the type defined in this memo must be used with care<=
br>
=A0 =A0and sparingly. =A0In particular, they MUST only be used where it is<=
br>
=A0 =A0actually required for interoperation or to limit behavior which has<=
br>
=A0 =A0potential for causing harm (e.g., limiting retransmisssions) =A0For<=
br>
=A0 =A0example, they must not be used to try to impose a particular method<=
br>
=A0 =A0on implementors where the method is not required for<br>
=A0 =A0interoperability.<br>
</blockquote>
<br>
To me this indicates that we should keep them out of registrations procedur=
es.<br>
<br>
(I also note that the &quot;MUST&quot; in the text I quoted shouldn&#39;t b=
een used if the text followed its own advice :-).<br>
<br>
Best regards, Julian<br>
</blockquote></div>

--001a11c2cfb03135ed04e9e7985b--

From randy@psg.com  Tue Oct 29 14:07:08 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 8A05A21F9BDB for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.449
X-Spam-Level: 
X-Spam-Status: No, score=-4.449 tagged_above=-999 required=5 tests=[AWL=-2.150, 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 Zy95yfbjM8HY for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:07:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id CF1C321F9C05 for <ietf@ietf.org>; Tue, 29 Oct 2013 14:07:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VbGVE-0000xK-1T; Tue, 29 Oct 2013 21:07:04 +0000
Date: Tue, 29 Oct 2013 14:07:03 -0700
Message-ID: <m238njss5k.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: future of identifiers
In-Reply-To: <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
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, 29 Oct 2013 21:07:08 -0000

> I think it is important to not restart discussions already held
> regarding different requirements on identifiers, requirements that in
> turn lead to various alternatives on how they are allocated, managed
> and resolved. I do not think one can have one identifier that fits
> all. Instead multiple kind of identifiers are needed. Because of
> requirements on uniqueness (absolute, low risk of collisions or not
> needed at all), persistence, human readable/understandable, whether
> allocation and resolution should be designed for read (lookups) or
> write (allocation), what the identifier is to be used for (see id/loc
> discussions).

i did not keep the tee shirts as they did not have pockets.

but i can't wait to see icann do to addressing what they did to name
strings.  real or imaginary ip addresses could be a real moneymaker
for them.

randy

From brian.e.carpenter@gmail.com  Tue Oct 29 14:12:38 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 BECE621E8087 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:12:38 -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 odXlbAySh5Wr for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 14:12:38 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C853411E81C9 for <ietf@ietf.org>; Tue, 29 Oct 2013 14:12:36 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kp14so594472pab.32 for <ietf@ietf.org>; Tue, 29 Oct 2013 14:12: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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QJfjqbgWx/rs6vjzGHgK8PEmvoinpT+aze/rTtwRKgo=; b=n74Z4Ev8EhNcFEgwmo+jVkiJ8aMnj6HmHxh3XpZssAQeH+K0wTfH20YikYAZe8gDiY X75+w4VMwwjTwgDRAoyX+x260v3IYi+/R2HCK0gAZYMXlW5/MQxY6xKjAGvE9ftLyT6X 757WH2xrfSRTOpTf1jPU3r6lh8nIEpPTFvqJriePLI8JMSUjR6XPR9XiZF/Jody9J2J+ 4Wsy9PCqrot2L83muI1jeCdGzfixOHCsTGfmZ26uAAUWIQN2W+4T3q8t8SXcltdz07NN JsvX20zfguUnvzHR0CxGUojqr1kDzxY4Kl0QXS6kd0Yw9vCL+nEq4Tig/h2h9kPae0th GZ9g==
X-Received: by 10.68.196.227 with SMTP id ip3mr1448477pbc.163.1383081156608; Tue, 29 Oct 2013 14:12:36 -0700 (PDT)
Received: from [130.216.38.108] ([130.216.38.108]) by mx.google.com with ESMTPSA id tu6sm36896372pbc.41.2013.10.29.14.12.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 14:12:36 -0700 (PDT)
Message-ID: <527024C6.5030807@gmail.com>
Date: Wed, 30 Oct 2013 10:12:38 +1300
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: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: future of identifiers
References: <20131029195634.4E19418C180@mercury.lcs.mit.edu>
In-Reply-To: <20131029195634.4E19418C180@mercury.lcs.mit.edu>
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, 29 Oct 2013 21:12:38 -0000

On 30/10/2013 08:56, Noel Chiappa wrote:
>     > From: Eliot Lear <lear@cisco.com>
> 
>     > And having chaired NSRG
> 
> It might be worth observing that NSRG was focused on new namespaces for the
> lower-middle part of the stack (e.g. TCP endpoint names), whereas I get
> the impression from Jari's note that that was about names further up
> (application, etc).
> 
> But maybe I got an incorrect impression?

I don't think so, but since we have broken the layer 3/4 namespace in various
ways, and are at severe risk of breaking the layer 7 namespace too, not
to mention the mapping between them, it's hard to separate the two
discussions.

   Brian

From doug.mtview@gmail.com  Tue Oct 29 15:43: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 305C311E81CC for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 15:43:40 -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 QWIr5zNZmL7H for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 15:43:39 -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 BBAAB21E8094 for <ietf@ietf.org>; Tue, 29 Oct 2013 15:43:38 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id wz7so491867pbc.38 for <ietf@ietf.org>; Tue, 29 Oct 2013 15:43:38 -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; bh=GjQoXRiQBqoEZ1NogV99ii1hGqM75AcWLtv1jzKC7nI=; b=MwAQ1b78ptRmmJudp2pW1iWsM9GLQmuIrozl0OcpLSX0TtepnJ3nNveKdNbyzpQ4aR 5ms/DOu3U4aT4jnysT0l0JKC+2hTfRIRRSEcU/tvVjJap7uAmp03XUaLYiOXuG5umI84 cXWXHYH0D0TexL1vyhwot4CigE+dSVcsIYGPylHeajzLtuFvSKidqTKYs/W4CDFpljJb SX4x4VXcVPHtE+u9rMSr+OFOHUk+L2qyYnZ2AfdeW1TwHd8W3oM2YpzxSGau3YpH7yZj /vFLy3+4dK16xnbeHaGxzfQ8XEpxvvuw8G49v8ubueZEXdsE9CrWvJHPf8qVBdBmU3Yt +WnA==
X-Received: by 10.66.196.168 with SMTP id in8mr2805671pac.18.1383086285138; Tue, 29 Oct 2013 15:38:05 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id dq3sm37168671pbc.35.2013.10.29.15.38.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 15:38:04 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <01OZZW7T12OY00004R@mauve.mrochek.com>
Date: Tue, 29 Oct 2013 15:38:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <74F37EA0-42CD-4805-80CB-1C060F79FEB7@gmail.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com> <01OZZW7T12OY00004R@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1510)
Cc: ietf discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Oct 2013 22:43:40 -0000

On Oct 25, 2013, at 9:53 AM, ned+ietf@mauve.mrochek.com wrote:

>> the chilling effect of vigilateism is far worse than spam or trolls.
>> we've been dealing with the latter for decades, and there is little
>> actual real harm if any.  the chilling effect of vigilanteism causes
>> actual harm and reduces the rich diversity of opinion, culture, and
>> viewpoint.
>=20
> I could not agree more. By condoning such measures people are damaging =
the
> diversity they are supposedly trying to support.

Agreed.  Not all interests will be met but each should have a voice =
within an open and transparent process.  It would be a pity to allow =
censorship or political propriety to place this process behind hidden =
barriers.

Regards,
Douglas Otis=

From jmamodio@gmail.com  Tue Oct 29 16:09:36 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 5863D11E829A for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 16:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=0.666,  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 NhrQRjXdkeme for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 16:09:36 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id A68DB11E829E for <ietf@ietf.org>; Tue, 29 Oct 2013 16:09:32 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id j10so681165oah.36 for <ietf@ietf.org>; Tue, 29 Oct 2013 16:09:32 -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:from:subject:date:to; bh=A40sG8X9oraCIF2gjsvEB9IUKLUyZ7ZbSPhr7+/WWLk=; b=Q7ShWHuTg0InLrvSvsyUg/J1kXqnu81185syJfghH9PUdSEpdMy3CWSG2ouWxTNhB1 85Mf/toMhJBS0dO5B+KKiVkREMT8IuVEOZ5pOVpC9Jjc7eQPcblL2auUFBiDNDMx/G1i Ruay0a7nhMrBFPRNBwO6C5tbYzQtFLyFMArsrROWaHpMijgaZ5hyKY60C88VPZ1Yc9rL EN2SW/adReYY4j5SPl7rIY+yL8BvSQgvM92PTuZ2ezkBi0EJF8ji9e+EicEonTVTctxs QHXTpNT3PJtiq3tp0/qu3MVwb8LNdeLJzhOAjGPNe2NqKKYvnOkH6CUi9zSoRuDcL/A/ vxJQ==
X-Received: by 10.60.134.230 with SMTP id pn6mr1680340oeb.52.1383088172014; Tue, 29 Oct 2013 16:09:32 -0700 (PDT)
Received: from [10.0.10.100] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id ee7sm48216289oeb.5.2013.10.29.16.09.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Oct 2013 16:09:31 -0700 (PDT)
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se> <m238njss5k.wl%randy@psg.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <m238njss5k.wl%randy@psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <D26E80D8-4969-43E3-8957-0D1E21ECABD0@gmail.com>
X-Mailer: iPad Mail (11B511)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: future of identifiers
Date: Tue, 29 Oct 2013 18:09:30 -0500
To: Randy Bush <randy@psg.com>
Cc: IETF Disgust <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: Tue, 29 Oct 2013 23:09:36 -0000

Hey why not ? 

We can add another three more paid vacations to exotic places per year  !!

-Jorge

On Oct 29, 2013, at 4:07 PM, Randy Bush <randy@psg.com> wrote:

> i did not keep the tee shirts as they did not have pockets.
> 
> but i can't wait to see icann do to addressing what they did to name
> strings.  real or imaginary ip addresses could be a real moneymaker
> for them.
> 
> randy

From ned+ietf@mauve.mrochek.com  Tue Oct 29 16:36:42 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 1836921E80AF for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 16:36: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 Y-BqC3FRYOvH for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 16:36:36 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2F75221E80A7 for <ietf@ietf.org>; Tue, 29 Oct 2013 16:36:33 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P05V6DMLY8006R4A@mauve.mrochek.com> for ietf@ietf.org; Tue, 29 Oct 2013 16:31:26 -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 <01OZQXEDTQ3400004R@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 29 Oct 2013 16:31:23 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P05V6C48TO00004R@mauve.mrochek.com>
Date: Tue, 29 Oct 2013 16:27:55 -0700 (PDT)
Subject: Re: RFC2119 keywords in registration requirements
In-reply-to: "Your message dated Tue, 29 Oct 2013 17:06:46 -0400" <CAC4RtVAhNcXrOPhms=6+LNdiJZF5cj6gJUH2Kg=Pkru=g4A8bw@mail.gmail.com>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <CAC4RtVAhNcXrOPhms=6+LNdiJZF5cj6gJUH2Kg=Pkru=g4A8bw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, 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: Tue, 29 Oct 2013 23:36:42 -0000

> Third, as instructions to registrants, I think it's absolutely fine to say
> "you MUST [include this information," and "you SHOULD [include that
> information]," and so on.  I think that respects the spirit of 2119, in
> that things are more likely to interoperate if the documentation of
> registered values is up to snuff.

FWIW, my experience with "running code" in this area is that this is a case
where the use of such directive does seem to help. (Assuming, of course, that
the registrant even bothers to read the procedure. Plain text capitalization is
not big enough to catch the attention of those who don't.)

				Ned

From nomcom-chair-2013@ietf.org  Tue Oct 29 19:26:40 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 5040311E8246; Tue, 29 Oct 2013 19:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.365
X-Spam-Level: 
X-Spam-Status: No, score=-101.365 tagged_above=-999 required=5 tests=[AWL=1.235, 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 SU1GvCUMkv6P; Tue, 29 Oct 2013 19:26:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7418721E805F; Tue, 29 Oct 2013 19:26:35 -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 - Community Feedback and Office Hours
X-Test-IDTracker: no
X-IETF-IDTracker: 4.81
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131030022635.20757.95263.idtracker@ietfa.amsl.com>
Date: Tue, 29 Oct 2013 19:26:35 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: nomcom13@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: Wed, 30 Oct 2013 02:26:40 -0000

The Nomcom is now receiving comments on nominees.  Per RFC 5680, the list o=
f candidates =

we are considering can be found at: https://datatracker.ietf.org/nomcom/201=
3/feedback/

Use your IETF datatracker password to access the nominees list and to enter=
 feedback.  =

Please contact ietf-action@ietf.org right away if you encounter difficulty,=
 as a few older =

datatracker accounts may have issues.

The fields will be populated automatically when you click a nominee's name.=
  You will also find =

links to click if you wish to enter feedback for multiple nominees for a po=
sition in one entry; =

these links are called APP Multiple, IAB Multiple, IAOC Multiple, INT Multi=
ple, etc.  =


Community feedback is sought as well on the desired expertise for each posi=
tion.
 If you have feedback in general or about the desired expertise, please ema=
il to =

nomcom13@ietf.org.

The Nomcom's pages (https://datatracker.ietf.org/nomcom/2013/) have backgro=
und =

information you may need, including the positions we are filling and the su=
mmaries of =

desired expertise prepared for each position. =

 =

We want to hear from you and we especially appreciate specific, concrete an=
d detailed feedback.
In order for your feedback to be useful, get it in on or before November 17=
, 2013.

If you are a nominee and submitted your questionnaire, you will shortly rec=
eive email about =

scheduling interview time.

Otherwise, if you would like to meet the Nomcom, come to our Open House in =
Vancouver.  =

The times are: 1-2 PM Mon, Tue, Thu, and 3:30-4:30 on Wed.  Contact me if t=
hese times =

aren't good for you.  =


The Nomcom Open House is in TURNER.


Thank you!

Allison for the Nomcom



From Ted.Lemon@nominum.com  Tue Oct 29 20:04:28 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 345AD11E81EC for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 1cOu2Gw-TxKs for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:04:21 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 9E77611E81F5 for <ietf@ietf.org>; Tue, 29 Oct 2013 20:04:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUnB3Ma/2dP/c/cpd3goaGoN17jZd+VOk@postini.com; Tue, 29 Oct 2013 20:04: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 E83D91B82CE for <ietf@ietf.org>; Tue, 29 Oct 2013 20:04:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-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 C441A190043; Tue, 29 Oct 2013 20:04:16 -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.03.0158.001; Tue, 29 Oct 2013 20:04:10 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OTt31k5HczOUEyidcQz8NpgJZoMlp0AgAADAYCAAAHNAIAAaYuA
Date: Wed, 30 Oct 2013 03:04:10 +0000
Message-ID: <7D634D31-6CD3-4A1E-8070-02C40088768D@nominum.com>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <15826A6D-1978-4501-AA83-FCD1E6B54213@harvard.edu>
In-Reply-To: <15826A6D-1978-4501-AA83-FCD1E6B54213@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: <D5FBB46FE577C342A67FA820DE399501@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Julian Reschke <julian.reschke@gmx.de>, 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, 30 Oct 2013 03:04:28 -0000

On Oct 29, 2013, at 4:46 PM, Bradner, Scott <sob@harvard.edu> wrote:
> fwiw - I have seen 2119 terms used in registration type RFCs for rather m=
any years=20
> I think it is too late to unwind that clock

The fact that a mistake has been made many times is no excuse to keep makin=
g it.


From Ted.Lemon@nominum.com  Tue Oct 29 20:10:11 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 B0DF521F9C99 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 XZ7+-hT0911J for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:10:06 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 53ED121E80FD for <ietf@ietf.org>; Tue, 29 Oct 2013 20:09:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUnB4ezKW4honXoWhozCVx0pqa2NgoVGM@postini.com; Tue, 29 Oct 2013 20:09:57 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 6B5EE1B82D0 for <ietf@ietf.org>; Tue, 29 Oct 2013 20:09:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 5C85A190043; Tue, 29 Oct 2013 20:09: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.03.0158.001; Tue, 29 Oct 2013 20:09:47 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: RFC2119 keywords in registration requirements
Thread-Topic: RFC2119 keywords in registration requirements
Thread-Index: AQHO1OTt31k5HczOUEyidcQz8NpgJZoMlp0AgAAH1wCAAGgSgA==
Date: Wed, 30 Oct 2013 03:09:46 +0000
Message-ID: <29A5B270-AC17-49FB-B562-4CDEB227FEB5@nominum.com>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <7064681F-4BA2-470E-A302-8E393800CA69@vpnc.org>
In-Reply-To: <7064681F-4BA2-470E-A302-8E393800CA69@vpnc.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="iso-8859-1"
Content-ID: <A19E0D33BCCBAD458156C08FF7FC70D0@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Julian Reschke <julian.reschke@gmx.de>, "Bradner, Scott" <sob@harvard.edu>, 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, 30 Oct 2013 03:10:11 -0000

On Oct 29, 2013, at 4:57 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> It is also completely reasonable to say "needs to include" as well.

Blargh.   The word you want to use there is "must."   You're saying "needs =
to" because you mean "must" but are trying to say it a different way.   "Ne=
eds to" does not mean the same thing as "must."

There has been some discussion of this topic recently in the IESG, which (A=
FAIK) has not reached consensus on the following:

http://trac.tools.ietf.org/group/iesg/trac/wiki/Draft2119BoilerplateSuggest=
ions

I'd be curious to hear reactions, bearing in mind that this is _not_ an IES=
G statement, at least at the moment.


From prvs=0008e0cf97=johnl@iecc.com  Tue Oct 29 20:43:20 2013
Return-Path: <prvs=0008e0cf97=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 4461511E81CB for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.126,  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 7-aBMpny9YDC for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:43:16 -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 CC09211E831C for <ietf@ietf.org>; Tue, 29 Oct 2013 20:43:11 -0700 (PDT)
Received: (qmail 84035 invoked from network); 30 Oct 2013 03:43:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 30 Oct 2013 03:43: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=5270804e.xn--hew.k1310; i=johnl@user.iecc.com; bh=/7WxTWEB9eZbhcHUlUx9WG/okP7ClZ9as7BVPFSCIxY=; b=R87gF4pfTbu5i8lQMQDNcPhJOm69A1KYnJdW79Rw+0tU7DUrXyitdn+nY2aIspi9kWC4vTF2T5qYTZSiMLTgPNcg4JGUPL2G8+/Xu6Dc8IcxoIoI39ti6kkIJtRW48aYPjsElU3AP6lvULpBsfu+7KSq0FaRXpIE5l6RaIutK46azpjA/bh1TKl+OrW5Wwi9qwW7G4o4HgJlgxwM4viK9SRvx/n3RWbypSQQWKRaWfD0hXb76MAOi+caCBd64c+d
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=5270804e.xn--hew.k1310; olt=johnl@user.iecc.com; bh=/7WxTWEB9eZbhcHUlUx9WG/okP7ClZ9as7BVPFSCIxY=; b=JblVPXu00psHS/Y9EHOZbUUK334MxJq9JHQMoRmION32H1XXd7wXOqcjHA6jrF0NUAN7Xs1YDyuzxGJSlDBepSKSYAMURW/42nd7zCKP2VdW34q8jHk6l/aLVhqDI9jUG+38JHIfYOS2EiK6lZ7wEjL2rtXFRsAkdw1gkUoDcbJIHUorTZnH2M/+OuGYHrMnZixvtKaka7m9G5p228P2bPkcRujuT6tTFD7TVle0V4jWZZJDRAOTqDhDneIXGLXX
Date: 30 Oct 2013 03:42:48 -0000
Message-ID: <20131030034248.23137.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RFC2119 keywords in registration requirements
In-Reply-To: <29A5B270-AC17-49FB-B562-4CDEB227FEB5@nominum.com>
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: Wed, 30 Oct 2013 03:43:20 -0000

>http://trac.tools.ietf.org/group/iesg/trac/wiki/Draft2119BoilerplateSuggestions
>
>I'd be curious to hear reactions, bearing in mind that this is _not_ an IESG statement, at least at the moment.

Ugh.  Please say that in documents that reference 2119, the words have
the magic meaning when capitalized, and authors should* refrain from
using them uncapitalized anywhere else, to avoid confusion.  I've done
this for a while, and it's not very hard.

With respect to the original question, understanding that the horse is
now three or four counties away, I'd find it useful to use 2119 words
to describe things that readers implement, so that they will
interoperate with things that other readers have implemented.

For situations where you have to provide X, Y, and Z to register a
foo, that's different, since it won't fail by not interoperating,
it'll fail by the registry sending it back and asking for the missing
pieces.

R's,
John

* - this message does not reference 2119

From hallam@gmail.com  Tue Oct 29 20:44:18 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 C207E11E831A for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:44:18 -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.149,  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 4lUCH7S-YFPe for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 20:44:17 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 171B411E831D for <ietf@ietf.org>; Tue, 29 Oct 2013 20:44:15 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id c11so764277lbj.31 for <ietf@ietf.org>; Tue, 29 Oct 2013 20:44:14 -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=KI2dx+ORyA/jInmefrbBsWnVJD8JOEIyscOtXAUjwcU=; b=dxkX2Sr07vxyAmNmYC+S9Nz99tVa3AL0LLsAPolKCKuui0vVvPb72MezyxEQgMTwze d+VK3W6KiqPX3nquELKn5abM/qxc/ZJitD4Xl4xu+rFjCJTqXF4KmNfTYTYzNYuPXYak FRTp/c7Mb0NSimS+T2dOiB3JZ7NSdGZc88LhqZoTk6AzVRb3W7NmQkFTY5u0lTRumxYd 444hDiR17mgqnkI8OylW5SeztCZuS64PcrULgBufbYs4qbQ/P+G905IfvkN5Col2f2RJ So+mt33u3ty4fiqNOspQ/BHjzBKEqR+rD17R6GgR+niSwUBaZQWcy+rGDU3CJgmGAW5D ovYg==
MIME-Version: 1.0
X-Received: by 10.112.168.105 with SMTP id zv9mr18912lbb.48.1383104654812; Tue, 29 Oct 2013 20:44:14 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 29 Oct 2013 20:44:14 -0700 (PDT)
In-Reply-To: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net>
Date: Tue, 29 Oct 2013 23:44:14 -0400
Message-ID: <CAMm+Lwih=PFukkapNZgJCz-uSkaF4sk=oj20KpFtUTNzQL8dDA@mail.gmail.com>
Subject: Re: future of identifiers
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11c259aaa32d9204e9ed2559
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, 30 Oct 2013 03:44:18 -0000

--001a11c259aaa32d9204e9ed2559
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Lets fix email addresses.

http://tools.ietf.org/html/draft-hallambaker-prismproof-key-00

A Strong email address combines an address with a security policy
indication and an optional public key identifier.

The key identifier is a hash of the publicKeyInfo block for the key (or a
PGP key fingerprint for backwards compatibility).

   KeyIdentifier: ACAIEA-FONPAC-5AC6LFA-K4ACHC-EAJWAHN-VPAM4A-COYPAO-VAA

      alice@example.com
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found and Alice has published
         the email encryption policy 'encryption preferred' or stronger.

      ?alice@example.com
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found, otherwise report an
         error.

      ACAIEA-FONPAC-5AC6LFA-K4ACHC-EAJWAHN-VPAM4A-COYPAO-
         VAA?alice@example.com
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found that is directly endorsed
         under the specified key, otherwise report an error.



Using strong email addresses allows us to address a wide range of
urgent commercial use cases. For example:


Doctor sending an email to a nurse with patient information in it


Lawyer sending a message about a client


Financial adviser sending a message to a client


Company sending a bill to a customer.


These are all valuable commercial use cases that enable paper
processes to be replaced with cheaper and more convenient electronic
processes.


I can add my strong email address to my linked in profile.


An infrastructure is required to resolve key identifiers to keys but
it can be a very simple well-known service lookup or a vcard.



We have 95% of an encrypted email solution today. This proposal adds
the missing 5%. It is a scheme that can be understood by ordinary
people.


Under the covers, the normal S/MIME and PGP can take place. But people
don't need to look under the covers.


I might need to trust a CA to find me a strong email address for a
recipient. But once I have found a strong address I don't need to do
that again.



I do have a business model etc. but its not the dopey idea of expiring
keys every year and having to pay to reissue them.




On Tue, Oct 29, 2013 at 10:38 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> For background, when I visited the ICANN meeting last summer, they were
> about to launch a set of panels to advice themselves about key topics in
> coming years. I promised to join one of them, on identifier technology
> innovation (along with a few other IETFers). The topic for this effort is
> future evolution of DNS and other identifiers, including relevant securit=
y
> and management aspects. The viewpoint is primarily to look at this from
> ICANN=92s angle, but of course the matter is interesting to us others as =
well.
>
> And perhaps we at the IETF should also understand the same things. Hence
> this e-mail.
>
> I have some ideas on what some of these trends might be. But what do the
> rest of you think? Where is identifier technology going, and what new
> things are on the horizon? What do we need to do with IDNs? DNSSEC? What
> will DANE lead to, and how will id-locator split techniques evolve & be
> deployed? How will applications or users think about identifiers in the
> future?
>
> More information at http://www.ietf.org/blog/2013/10/future-identifiers/
>
> Jari
>
>


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

--001a11c259aaa32d9204e9ed2559
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Lets fix email addresses.</div><div><br></div><a href=
=3D"http://tools.ietf.org/html/draft-hallambaker-prismproof-key-00">http://=
tools.ietf.org/html/draft-hallambaker-prismproof-key-00</a><br><div><br></d=
iv>
<div>A Strong email address combines an address with a security policy indi=
cation and an optional public key identifier.</div><div><br></div><div>The =
key identifier is a hash of the publicKeyInfo block for the key (or a PGP k=
ey fingerprint for backwards compatibility).</div>
<div><br></div><div><pre class=3D"" style=3D"font-size:1em;margin-top:0px;m=
argin-bottom:0px;color:rgb(0,0,0)">   KeyIdentifier: ACAIEA-FONPAC-5AC6LFA-=
K4ACHC-EAJWAHN-VPAM4A-COYPAO-VAA

      <a href=3D"mailto:alice@example.com">alice@example.com</a>
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found and Alice has published
         the email encryption policy &#39;encryption preferred&#39; or stro=
nger.

      ?<a href=3D"mailto:alice@example.com">alice@example.com</a>
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found, otherwise report an
         error.

      ACAIEA-FONPAC-5AC6LFA-K4ACHC-EAJWAHN-VPAM4A-COYPAO-
         VAA?<a href=3D"mailto:alice@example.com">alice@example.com</a>
         Send email to Alice using encryption if and only if an
         encryption key for Alice can be found that is directly endorsed
         under the specified key, otherwise report an error.</pre><pre clas=
s=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,=
0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margi=
n-bottom:0px;color:rgb(0,0,0)">
<br></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font =
face=3D"arial"><span style=3D"white-space:normal">Using strong email addres=
ses allows us to address a wide range of urgent commercial use cases. For e=
xample:</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">Doctor sending an email to a nurse with patie=
nt information in it</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">Lawyer sending a message about a client</span=
></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">Financial adviser sending a message to a clie=
nt</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">Company sending a bill to a customer.</span><=
/font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">These are all valuable commercial use cases t=
hat enable paper processes to be replaced with cheaper and more convenient =
electronic processes.=A0</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">I can add my strong email address to my linke=
d in profile.</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">An infrastructure is required to resolve key =
identifiers to keys but it can be a very simple well-known service lookup o=
r a vcard.=A0</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal"><br>
</span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0=
px"><font face=3D"arial"><span style=3D"white-space:normal">We have 95% of =
an encrypted email solution today. This proposal adds the missing 5%. It is=
 a scheme that can be understood by ordinary people.=A0</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">Under the covers, the normal S/MIME and PGP c=
an take place. But people don&#39;t need to look under the covers.</span></=
font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal">I might need to trust a CA to find me a stron=
g email address for a recipient. But once I have found a strong address I d=
on&#39;t need to do that again.</span></font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal"><br>
</span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0=
px"><font face=3D"arial"><span style=3D"white-space:normal">I do have a bus=
iness model etc. but its not the dopey idea of expiring keys every year and=
 having to pay to reissue them.</span></font></pre>
<pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)"><span style=3D"color:rgb(34,34,34);font-family:arial;font-si=
ze:small;white-space:normal"><br></span></pre></div></div><div class=3D"gma=
il_extra">
<br><br><div class=3D"gmail_quote">On Tue, Oct 29, 2013 at 10:38 AM, Jari A=
rkko <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=
=3D"_blank">jari.arkko@piuha.net</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
For background, when I visited the ICANN meeting last summer, they were abo=
ut to launch a set of panels to advice themselves about key topics in comin=
g years. I promised to join one of them, on identifier technology innovatio=
n (along with a few other IETFers). The topic for this effort is future evo=
lution of DNS and other identifiers, including relevant security and manage=
ment aspects. The viewpoint is primarily to look at this from ICANN=92s ang=
le, but of course the matter is interesting to us others as well.<br>

<br>
And perhaps we at the IETF should also understand the same things. Hence th=
is e-mail.<br>
<br>
I have some ideas on what some of these trends might be. But what do the re=
st of you think? Where is identifier technology going, and what new things =
are on the horizon? What do we need to do with IDNs? DNSSEC? What will DANE=
 lead to, and how will id-locator split techniques evolve &amp; be deployed=
? How will applications or users think about identifiers in the future?<br>

<br>
More information at <a href=3D"http://www.ietf.org/blog/2013/10/future-iden=
tifiers/" target=3D"_blank">http://www.ietf.org/blog/2013/10/future-identif=
iers/</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<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>

--001a11c259aaa32d9204e9ed2559--

From sm@elandsys.com  Tue Oct 29 21:47:51 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 961AD21F9A4A; Tue, 29 Oct 2013 21:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level: 
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=-0.879, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B4+lmJQ0Wr7g; Tue, 29 Oct 2013 21:47:51 -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 592F611E81CB; Tue, 29 Oct 2013 21:44:49 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U4gwbn023165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 21:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383108206; bh=jEDwl6HgFuazbOmphFeLDKl24kHI17FGzOxBa4UXlho=; h=Date:To:From:Subject:Cc; b=4BFChIctuK0lSPKushnd1+u892DT0S5fxQXZaBt+AfTH4cVM11M+3wfiZn+3GSykB ePIFD5ju49waZPuq1Ap2Pb4t8fSmByDPBhr/c7jjuvHfonjowuzEH3Z/93eofNaqaB eY51aFmtFH5XWKQ+uLvmhAHZY6aCZiqMbXSvMqZQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383108206; i=@elandsys.com; bh=jEDwl6HgFuazbOmphFeLDKl24kHI17FGzOxBa4UXlho=; h=Date:To:From:Subject:Cc; b=yAPpcd3gqeZZkoTYjiBxlF4AyuhfxPLYsRwaKomEqMxHL5Ls5V3Q5I/22ljnIGTAt I2ZRQ3fqCap1KcTasDDis9Hwz/siZuQqOh0hxTrRHNrsBXsEW5/2SlRWGoINkxxKHd lw46z188Eb+hBkHAtCJc8kFmlzhHJjbu4Wp1wGUA=
Message-Id: <6.2.5.6.2.20131029070026.0c491228@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 15:19:25 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p6-cache.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p6-cache-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 30 Oct 2013 04:47:51 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p6-cache-24
Title: Hypertext Transfer Protocol (HTTP/1.1): Caching
Reviewer: S. Moonesamy
Review Date: October 29, 2013
IETF Last Call Date: October 21, 2013

Summary:  This draft is almost ready for publication as a Proposed Standard

This document defines requirements on HTTP caches and the associated 
header fields that control cache behavior or indicate cacheable 
response messages.  Caching is an optional feature of HTTP.

The document is clear and well-written.

Major Issues: None

Minor Issues:

In Section 1:

   "Any client or server MAY employ a cache, though a cache cannot be
    used by a server that is acting as a tunnel."

I suggest not using the RFC 2119 "may" in the Introduction section.

In Section 1.2.1:

   "If a cache receives a delta-seconds value larger than the largest
    positive integer it can represent, or if any of its subsequent
    calculations overflows, the cache MUST consider the value to be
    2147483648 (2^31).  A recipient parsing a delta-seconds value MUST
    use an arithmetic type of at least 31 bits of range, and a sender
    MUST NOT generate delta-seconds with a value greater than 2147483648.."

Shouldn't the largest value be 2147483647 (see MAX_INT)?

It seems superfluous to have the second RFC 2119 "must" and the RFC 
2119 "must not".

In Section 5.2.2.2:

   "Note: This directive uses the quoted-string form of the argument
    syntax.  A sender SHOULD NOT generate the token form (even if quoting
    appears not to be needed for single-entry lists)."

I suggest not having RFC 2119 key words as part of a note.

In Section 5.2.2.3:

   'The "no-store" response directive indicates that a cache MUST NOT
    store any part of either the immediate request or response.  This
    directive applies to both private and shared caches.  "MUST NOT
    store" in this context means that the cache MUST NOT intentionally
    store the information in non-volatile storage, and MUST make a best-
    effort attempt to remove the information from volatile storage as
    promptly as possible after forwarding it.'

There is a RFC 2119 "must not" followed by an explanation of the 
requirement which includes a RFC 2119 "must not" and a "must".  I 
suggest rewriting the (first) requirement so that it is clear instead 
of explaining a requirement with another requirement.

In Section 5.2.2.6:

   "Note: This directive uses the quoted-string form of the argument
    syntax.  A sender SHOULD NOT generate the token form (even if quoting
    appears not to be needed for single-entry lists)."

I suggest not having the RFC 2119 "should not" as a part of a 
note.  This suggestion also applies to the note in Section 5.2.2.8 
and Section 5.2.2.9.

Nits:

In Section 4.2:

   "o  A cache recipient MUST NOT allow local time zones to influence the
       calculation or comparison of an age or expiration time.

    o  A cache recipient SHOULD consider a date with a zone abbreviation
       other than GMT or UTC to be invalid for calculating expiration."

Section 7.1.1.1 of draft-ietf-httpbis-p2-semantics-24 states that:

   "An HTTP-date value represents time as an instance of Coordinated
    Universal Time (UTC)."

If there is a requirement for the cache to use UTC (re. HTTP-date) 
internally the above RFC 2119 key words could be collapsed into that.

Regards,
S. Moonesamy


From sm@elandsys.com  Tue Oct 29 21:48: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 DF51621F9D22; Tue, 29 Oct 2013 21:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.896
X-Spam-Level: 
X-Spam-Status: No, score=-102.896 tagged_above=-999 required=5 tests=[AWL=-0.341, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CZzIqcyhUhy; Tue, 29 Oct 2013 21:48:02 -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 3D19F21F9D46; Tue, 29 Oct 2013 21:44:45 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U4gwbp023165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Oct 2013 21:43:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383108222; bh=nZrZ+ivyJh+jBc4JoipycAe5Kppgbh+yM+wmlYezyhU=; h=Date:To:From:Subject:Cc; b=hlptHRWikGlzJMlCeRV7HAEtgXKlSxkabxypcqcMDG1b+D/9WzkIabBTNTNmlagYx GApt7IVcMI66GFCsCFTOn92uj3vfbgUeTmQ5LoXSUewMjcuzm7/CpViII8tGyMDEiR Hy2bamS6uOYyZyXqn4sOFbgdxVTu+Gxb2WDp83uc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383108222; i=@elandsys.com; bh=nZrZ+ivyJh+jBc4JoipycAe5Kppgbh+yM+wmlYezyhU=; h=Date:To:From:Subject:Cc; b=qjgzVYN9pmGrKeTR/T1Cv0ap5fCSGcbRGkOk/hBAhyiaY8kI42zcAWuFL+7MPBe6t 9wY+3lCbABdC3lS6WdfSt3pKaQR+D2YoC1hWRLO8cJQZiDRYtpcmtYMNEDncsiusSd dQd8qt3qo2KqrPiJ/NPdYofgevB44Z9PwwOB7y4k=
Message-Id: <6.2.5.6.2.20131029152147.0c123670@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 17:48:20 -0700
To: apps-discuss@ietf.org, draft-ietf-httpbis-p7-auth.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: APPSDIR review of draft-ietf-httpbis-p7-auth-24
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, ietf-http-wg@w3.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, 30 Oct 2013 04:48:03 -0000

I have been selected as the Applications Area Directorate reviewer 
for this draft (for background on APPSDIR, please see 
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).

Please resolve these comments along with any other Last Call comments 
you may receive. Please wait for direction from your document 
shepherd or AD before posting a new version of the draft.

Document: draft-ietf-httpbis-p7-auth-24
Title: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Reviewer: S. Moonesamy
Review Date: October 29, 2013
IETF Last Call Date: October 21, 2013

Summary: This draft is almost ready for publication as a Proposed Standard.

This document defines the HTTP Authentication framework.

The document is well-written and clear.

Major Issues: None

Minor Issues:

In Section 1:

   "HTTP provides several OPTIONAL challenge-response authentication
    schemes that can be used by a server to challenge a client request
    and by a client to provide authentication information."

I suggest using RFC 2119 after Section 1.2.

Nits:

In Section 2.1:

   "Additional mechanisms MAY be used, such as encryption at the transport
   level or via message encapsulation, and with additional header fields
   specifying authentication information."

The RFC 2119 "may" is unnecessary.

Regards,
S. Moonesamy


From dharkins@lounge.org  Wed Oct 30 01:00:50 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 6E1FA11E8118 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.665
X-Spam-Level: 
X-Spam-Status: No, score=-3.665 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 clphNqDEMap2 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:00:45 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 07F8211E8211 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:00:43 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 9F6F110224008; Wed, 30 Oct 2013 01:00:41 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 30 Oct 2013 01:00:42 -0700 (PDT)
Message-ID: <d7bcb3c23d6b03fa76fab79b32987e7a.squirrel@www.trepanning.net>
In-Reply-To: <5F803CCD-DF4F-4857-B5F5-0AB9971F31D3@virtualized.org>
References: <20131026024004.3506.qmail@joyce.lan> <937D93BC-E9B0-4F17-B921-882EEFAE8128@gmail.com> <5F803CCD-DF4F-4857-B5F5-0AB9971F31D3@virtualized.org>
Date: Wed, 30 Oct 2013 01:00:42 -0700 (PDT)
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
From: "Dan Harkins" <dharkins@lounge.org>
To: "David Conrad" <drc@virtualized.org>
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: Wed, 30 Oct 2013 08:00:50 -0000

On Fri, October 25, 2013 9:18 pm, David Conrad wrote:
[snip]
> If you have a commons and one of the users of the commons is peeing all
> over the grass so that the sheep won't eat, do you continue to allow that
> user entry into the commons?

  If you don't they're not "commons" anymore. Perhaps the commons are
improved if the sheep don't eat the grass and peeing on it is the easiest way
to ensure the well-being of the commons. Regardless, this is a piss-poor
analogy. The posts in question did not amount to some kind of denial
of service attack in the way that peeing on grass resulted in the sheep
refusing to eat. And just who are the sheep here anyway? What's up with
this chattel arrangement?

  Dan.




From bortzmeyer@nic.fr  Wed Oct 30 01:15:20 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2FF11E8118 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:15:12 -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.025, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4bJyFmnz3HB for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:15:06 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id AD2E021E80F3 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:15:00 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 69DA028017C; Wed, 30 Oct 2013 09:14:27 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 6546A280052; Wed, 30 Oct 2013 09:14:27 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 58A2F4C007C; Wed, 30 Oct 2013 09:13:57 +0100 (CET)
Date: Wed, 30 Oct 2013 09:13:55 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org, IAB Chair <iab-chair@iab.org>
Subject: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Message-ID: <20131030081355.GA23990@nic.fr>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
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: Wed, 30 Oct 2013 08:15:21 -0000

On Tue, Oct 29, 2013 at 09:10:08AM -0400,
 IAB Chair <iab-chair@iab.org> wrote 
 a message of 54 lines which said:

> The Technical Plenary session is expected to be popular.  It will be
> held on Wednesday, 6 Nov 2013 at 0900 PST,

Why why why using a local timezone when announcing a live broadcast,
which will be seen by many people anywhere in the world?

Do note also that there are three different timezones in the world
which are named PST. Not everyone lives in North America!

IETF must use only UTC when announcing a worldwide event.

From cabo@tzi.org  Wed Oct 30 01:26:18 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 D6FC011E820D for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.213
X-Spam-Level: 
X-Spam-Status: No, score=-106.213 tagged_above=-999 required=5 tests=[AWL=0.036, 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 RDbSAsHbj+rr for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:26:13 -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 F071F11E8118 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:26:12 -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 r9U8Q12W008169; Wed, 30 Oct 2013 09:26:01 +0100 (CET)
Received: from [192.168.217.105] (p548911BB.dip0.t-ipconnect.de [84.137.17.187]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 04458EEB; Wed, 30 Oct 2013 09:26:00 +0100 (CET)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20131030081355.GA23990@nic.fr>
Date: Wed, 30 Oct 2013 09:25:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1816)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 08:26:19 -0000

On 30 Oct 2013, at 09:13, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:

> IETF must use only UTC when announcing a worldwide event.

I don=92t know about =93only UTC" for events that are also visited =
locally, but giving the UTC time as well would be a good idea.  Even =
more so for a event that is days from a local time zone change.

Beyond UTC, I would normally point to

	http://datatracker.ietf.org/meeting/agenda-utc

and its =93display in browser time=94 feature here as well, but the =
latter seems to be broken by a missing file right now.

Gr=FC=DFe, Carsten


From finlayson@live555.com  Wed Oct 30 01:28:44 2013
Return-Path: <finlayson@live555.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A864E11E8118; Wed, 30 Oct 2013 01:28: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mtqc88nyI77a; Wed, 30 Oct 2013 01:28:39 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) by ietfa.amsl.com (Postfix) with ESMTP id 348C611E8113; Wed, 30 Oct 2013 01:28:38 -0700 (PDT)
Received: from [127.0.0.1] (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.14.4/8.14.4) with ESMTP id r9U8SZ6C014182; Wed, 30 Oct 2013 01:28:36 -0700 (PDT) (envelope-from finlayson@live555.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Ross Finlayson <finlayson@live555.com>
In-Reply-To: <20131030081355.GA23990@nic.fr>
Date: Wed, 30 Oct 2013 01:28:35 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1812)
Cc: IAB Chair <iab-chair@iab.org>, 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, 30 Oct 2013 08:28:44 -0000

>> The Technical Plenary session is expected to be popular.  It will be
>> held on Wednesday, 6 Nov 2013 at 0900 PST,
> 
> Why why why using a local timezone when announcing a live broadcast,
> which will be seen by many people anywhere in the world?
> 
> Do note also that there are three different timezones in the world
> which are named PST. Not everyone lives in North America!
> 
> IETF must use only UTC when announcing a worldwide event.

I would prefer SHOULD rather than MUST (or must) :-)

But anyway, FYI, 0900 PST (Canada/US Pacific Standard Time) == 1700 UTC.

	Ross.


From bortzmeyer@nic.fr  Wed Oct 30 01:37:18 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B637411E8265 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.271
X-Spam-Level: 
X-Spam-Status: No, score=-102.271 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9STm+xZM9uST for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:37:13 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id D6BD411E813D for <ietf@ietf.org>; Wed, 30 Oct 2013 01:37:12 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 30BB528017C; Wed, 30 Oct 2013 09:36:42 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 2C44B280046; Wed, 30 Oct 2013 09:36:42 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 20DBF4C007E; Wed, 30 Oct 2013 09:36:12 +0100 (CET)
Date: Wed, 30 Oct 2013 09:36:12 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Message-ID: <20131030083611.GA27804@nic.fr>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 08:37:18 -0000

On Wed, Oct 30, 2013 at 09:25:59AM +0100,
 Carsten Bormann <cabo@tzi.org> wrote 
 a message of 16 lines which said:

> I donâ€™t know about â€śonly UTC" for events that are also visited
> locally, but giving the UTC time as well would be a good idea.

My experience with international organizations is that, when you
indicate the time in two zones, there is often a discrepancy. With
only one zone, there is no doubt about the real value.

From bortzmeyer@nic.fr  Wed Oct 30 01:39:22 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD7811E832E for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.267
X-Spam-Level: 
X-Spam-Status: No, score=-102.267 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FCv1+Xhwi5kq for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:39:17 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 624D511E833C for <ietf@ietf.org>; Wed, 30 Oct 2013 01:38:52 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 579C428017C; Wed, 30 Oct 2013 09:38:21 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 5254D280046; Wed, 30 Oct 2013 09:38:21 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:1348:8::7:113]) by relay1.nic.fr (Postfix) with ESMTP id 46E284C007C; Wed, 30 Oct 2013 09:37:51 +0100 (CET)
Date: Wed, 30 Oct 2013 09:37:51 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Ross Finlayson <finlayson@live555.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Message-ID: <20131030083751.GB27804@nic.fr>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com>
X-Operating-System: Debian GNU/Linux 7.1
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IAB Chair <iab-chair@iab.org>, 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, 30 Oct 2013 08:39:22 -0000

On Wed, Oct 30, 2013 at 01:28:35AM -0700,
 Ross Finlayson <finlayson@live555.com> wrote 
 a message of 16 lines which said:

> I would prefer SHOULD rather than MUST (or must) :-)

What could be a good reason to use the local time, when it is an event
broadcasted on the Internet? For a physical meeting, I can imagine
such good reasons but for a network one?

From loa@pi.nu  Wed Oct 30 01:42:30 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 1495711E8265 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, 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 bRaIeCP1TlyH for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:42:23 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id B858C11E8211 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:42:23 -0700 (PDT)
Received: from [192.168.1.6] (unknown [112.208.65.178]) (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 ACC8018014F6 for <ietf@ietf.org>; Wed, 30 Oct 2013 09:42:21 +0100 (CET)
Message-ID: <5270C66C.9070109@pi.nu>
Date: Wed, 30 Oct 2013 16:42:20 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org>	<20131030081355.GA23990@nic.fr>	<ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr>
In-Reply-To: <20131030083751.GB27804@nic.fr>
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, 30 Oct 2013 08:42:30 -0000

hmmm - I thought the "Technical Plenary" which you used as an example
actually is (partly) a physical meeting. We should have the local AND
UTC time announced.

/Loa

On 2013-10-30 16:37, Stephane Bortzmeyer wrote:
> On Wed, Oct 30, 2013 at 01:28:35AM -0700,
>   Ross Finlayson <finlayson@live555.com> wrote
>   a message of 16 lines which said:
>
>> I would prefer SHOULD rather than MUST (or must) :-)
>
> What could be a good reason to use the local time, when it is an event
> broadcasted on the Internet? For a physical meeting, I can imagine
> such good reasons but for a network one?
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From sm@elandsys.com  Wed Oct 30 01:43: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 CF60811E8102; Wed, 30 Oct 2013 01:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.171
X-Spam-Level: 
X-Spam-Status: No, score=-103.171 tagged_above=-999 required=5 tests=[AWL=-0.616, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FCq4Rx+9-TFj; Wed, 30 Oct 2013 01:43:44 -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 4A2D311E8265; Wed, 30 Oct 2013 01:43:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U8gxju013206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 01:43:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383122593; bh=4X17+HyNpu5KNKrD3oCBWVG1PxRW/lRT16i5LF6scU0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yAsUb2CYRcKeJiPQ6J12BlDmFFtMfv5PI6hJy6xWeryVZ3BI7DmgdSCbuuiY3HG5Y ckCZD8sQyW5G8FMsH9lMIVnS4t+bp2dix8UwKjKA7zgVT3f2REZUDGse1kE1MzprGz Z2aofggD6lqgjOxsN2lQFRM8/RtrvuRs5moVU0gg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383122593; i=@elandsys.com; bh=4X17+HyNpu5KNKrD3oCBWVG1PxRW/lRT16i5LF6scU0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=B49zGi320ENoliAJZaUVguLz7rsSwt6Boy0+9VC+Oe2f3TuXEhO1IsgdBxaAWPRiN tnwH+aJ3TQC0rjhADNg6JGPhCM0Ov/esLZm1yiH/BUF0Vka5IKmjhLgc4DPkhrBPTz rSX0YXRpoCiNGILG+b8AH+RRYeEtMF4pVnAww5+U=
Message-Id: <6.2.5.6.2.20131029214748.0b93d3b8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 22:24:32 -0700
To: Julian Reschke <julian.reschke@greenbytes.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
In-Reply-To: <526E7154.2070005@greenbytes.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E7154.2070005@greenbytes.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:43:45 -0000

Hi Julian,
At 07:14 28-10-2013, Julian Reschke wrote:
>Yes -- this is not necessarily a problem. There are many things that 
>need to be defined for a new method, and not all of these fit into 
>the template.

A DISCUSS about this can be easily addressed. :-)

What is the intent behind the HTTP Method Registry (Section 
8.1.3)?  What information should that registry convey to the 
reader?  For example, is it a quick way for the reader to find out 
whether POST is cacheable (re. a choice that a browser vendor made 
some time back) or should the person read the relevant specification 
text to get accurate answer?

>That's an assumption that is true for all "bare" Section references.

The problem is that people copy and paste them blindly.  I suggest 
having information in the tables as the working group would like it 
to appear in the registry

>The IANA Considerations are processed by the RFC Editor and IANA, 
>and they will make sure that the registry is properly populated. 
>There's no point in mentioning a still unknown RFC # here.

It is up to the Responsible Area Director and the the document 
shepherd to make sure that the registry is properly populated.

>What, precisely?

I suggest adding "RFC XXXX" in the tables.  I read 
draft-reschke-http-status-308-07.  The reference is similar to what 
is in draft-ietf-httpbis-p2-semantics-24.  They are two different 
drafts and that makes referencing only the sections ambiguous.  RFC 
6585 updated the HTTP Status Code registry last year.  The current 
registry format only references the RFC number.  I suggest making the 
change clear so that, in some distant future, someone working on this 
can figure out the details of the registry.

Regards,
S. Moonesamy  


From sm@elandsys.com  Wed Oct 30 01:43:46 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 69B5211E8102; Wed, 30 Oct 2013 01:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.177
X-Spam-Level: 
X-Spam-Status: No, score=-103.177 tagged_above=-999 required=5 tests=[AWL=-0.578, 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 5mmiVvGBRW8c; Wed, 30 Oct 2013 01:43: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 4A33311E8272; Wed, 30 Oct 2013 01:43:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U8gxjw013206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 01:43:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383122598; bh=e1hoBZoErs6MEj9SLtqH4TRp+V6cTqky8NNWEeQOBPk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jdr/w7MRlZs08qNk0V6NT2bQtrGTWO5AR4/8hCaMlCTzqMTdB9UsSAalAkhhRbsJv E036U6rQQSoE+WxnUqyzgIyxDNMrL18gGoprALbPl7ZtPTkLncCwRMRWNhkpGeGHnQ exTvUu84D8W042ZdJaadNm0nvNs5889JdEAzEvlY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383122598; i=@elandsys.com; bh=e1hoBZoErs6MEj9SLtqH4TRp+V6cTqky8NNWEeQOBPk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=im7v1pyPFXMX0IR8PlgiAyxowYjQ15MbBcsvktRme7X0v5hfKS2IttO0xFGAziJKM V+SxJuvvTO6/7kpMXrEAZ3Q0uybtxmuQEPL7Lv248RMWJhLXK6R1bji4oHZLV/TGwN 3O2rjVY+hGsYj9KGpJ4t+Ygb68cMupGvrqKXYYQQ=
Message-Id: <6.2.5.6.2.20131029223814.0ce8c880@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Oct 2013 23:26:12 -0700
To: John C Klensin <john-ietf@jck.com>, Amos Jeffries <squid3@treenet.co.nz>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review, etc.
In-Reply-To: <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com> <526F0EC1.7010809@treenet.co.nz>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com> <526E73B8.90705@gmx.de> <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com> <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com> <526E73B8.90705@gmx.de> <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com> <526F0EC1.7010809@treenet.co.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, ietf@ietf.org, apps-discuss@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 08:43:46 -0000

At 12:22 28-10-2013, John C Klensin wrote:
>My understanding is that the HTTPbis work is a rather major
>revision with at least some cases for which "get it right" is
>more important that complete backward compatibility, especially
>if there is a clear migration path.  All of the usual arguments
>for that are relevant, especially the ones that focus on how
>many implementations and pages are likely to be created in the
>future relative to those that exist today.   Here, the clear
>migration path would be a narrow and restrictive "send syntax"
>and a permissive "receive syntax" that requires support of all
>known older forms, _especially_ those that were recommended by
>HTTP 1.1.

Yes.

>So, from my point of view, this isn't about introducing an
>incompatibility with something that one merely regrets not being
>done differently.  It is rather more about what might be the
>last chance to get it right and, in the process, eliminate
>completely predictable future confusion and interoperability
>problems.

The argument is about code complexity versus what the working group 
charter says.  It is difficult to review a specification when the 
current specification is still referencing RFC 822.  I don't recall 
whether there are any other application-related specifications using 
"GMT".  The HTTPbis drafts discusses about "GMT" when it actually means "UTC".

At 18:26 28-10-2013, Amos Jeffries wrote:
>However it is important to note that there is no clear migration path. Many
>implementations are actively *rejecting* or ignoring date formats which do
>not include the "GMT" moniker.

That can be a problem.

>Indeed. This option was considered by the WG several times as people keep
>bringing up this same point. (I myself even a few  years back). The WG charter
>is explicitly prohibiting addition of a new version number in these documents
>so there are several things like this which have had to be left unchanged.

People usually keep bringing up the same point when a choice is not 
documented.  I read what John Klensin wrote as during each revision 
of the specification the above argument is used to avoid making a change.

Regards,
S. Moonesamy 


From sm@elandsys.com  Wed Oct 30 01:44:00 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 34E6B21E80DA for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:44:00 -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.564, 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 NW6qmFe+xmnu for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:43: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 F18BF21E80C6 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:43:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U8gxk2013206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 01:43:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383122608; bh=hpuZhCQ4L/AfhbimZ+CsWO1GWv+2yOgGF/LMxtG97Pg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TLd9SVczOxHzWyNE4/I0faM6mLK5X34Fa+0mYGfQk2zyju+lbARvHD86WjSIuqZgJ D5lkM9e2QZkaMhqF9xuXrVxMVvgOmgqVC4CTyfh3VkM5mbAdGTL8x1PBH3XezXjsIG mWwGCx9XBIPriOQYe0I8yCB8G6MDi+yKyN6FLZZU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383122608; i=@elandsys.com; bh=hpuZhCQ4L/AfhbimZ+CsWO1GWv+2yOgGF/LMxtG97Pg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4TDV0hM0Sj+x4YJ5bhp0+OoIbYbCI5jHoBIc0myqUAuGbvtCKvHJCWVWRrmFvOxa7 QDDcdBm0l7IYrrOY0eOImoTCxtsSY29uXAG0fTj/uYSWwWjWyVw2z9HqiNIYKKNjfW Pcv+8ALBuXysnipE0zZA68OLvY+KR/YKLBrMA/jY=
Message-Id: <6.2.5.6.2.20131030011734.0ce8d178@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Oct 2013 01:31:27 -0700
To: Julian Reschke <julian.reschke@gmx.de>, draft-ietf-httpbis-p1-messaging.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
In-Reply-To: <526FDC52.3030808@gmx.de>
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com> <526FDC52.3030808@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:44:01 -0000

Hi Julian,
At 09:03 29-10-2013, Julian Reschke wrote:
>I have trouble parsing this comment. Do you see an issue here?

I read the text again (Section 6.4).  It is difficult to say what is 
deemed abusive.  You could get around that with, for example:

   A client SHOULD limit the number of simultaneous open connections
   that it maintains to a given server as each connection consumes
   server resources.

Please note that I used some text from the third paragraph of that section.

Regards,
S. Moonesamy 


From sm@elandsys.com  Wed Oct 30 01:44:01 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 AA7CB21E80F0; Wed, 30 Oct 2013 01:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.15
X-Spam-Level: 
X-Spam-Status: No, score=-103.15 tagged_above=-999 required=5 tests=[AWL=-0.551, 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 5gsuwYCShZLy; Wed, 30 Oct 2013 01:43: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 CBAD021E8096; Wed, 30 Oct 2013 01:43:27 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.39]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9U8gxk0013206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 01:43:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383122603; bh=03b49fo2DAGdas52zHjPMR9PGo8yGdLB30mQ8JleKew=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sY4aJJIf8GHC1saeqv0076NyQy4FVVCdt8ff2IiJzDgOnDpQgwOAlDhfX/TWC9ARM doyso6nFH7fJey8nxLf0I5pyHddNEBIn4XNAmDPcsjDY4/aLe5xnBnGqTi2owk6hry inbzSU420J1b612ikw6W2Lxdvf/L/Cdpso5GGNeU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383122603; i=@elandsys.com; bh=03b49fo2DAGdas52zHjPMR9PGo8yGdLB30mQ8JleKew=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cB2fGEHMKtv37Dvbl3Y7ZDXJlLCxnW5pfAuQM29EJdiwbei6BRskWhEB3NMOEvrtT 2z+0OHdcQQrRNwYNkQungXVv0iQqRuNXNuEnogrigh2p7hTbFV1m6Ju4ewaj+WBcmV QRu3KmwF6hYSv6jHSGjzPmM+DHuMbjoAryrQ4IKU=
Message-Id: <6.2.5.6.2.20131029232953.0ce8cc58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Oct 2013 00:46:51 -0700
To: Julian Reschke <julian.reschke@gmx.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p5-range.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
In-Reply-To: <526FD3E8.9010904@gmx.de>
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com> <526FD3E8.9010904@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:44:01 -0000

Hi Julian,
At 08:27 29-10-2013, Julian Reschke wrote:
>thanks a lot for the incoming reviews! I'm tracking them in the WG's 
>trac instance.

Ok.  As you understand how things work I'll defer to you on the 
issues instead of tracking down what has been addressed.

>Well, it's optional, and we didn't want to make it a SHOULD. It adds 
>overhead to GET responses, even though only few clients will make 
>range requests.

Ok.

>Yes. Do you think this is a problem? Why?

It's the kind of text which generates long threads outside the 
IETF.  Some people can argue that it is a "may" written in uppercase 
while other people will argue that the plain English says something 
else.  My preference is for the intent of the text to be clear unless 
there is a good reason not to be clear.

><http://trac.tools.ietf.org/wg/httpbis/trac/ticket/505>

That's applicable to several drafts in the set.

>"A server that supports range requests MAY ignore or reject a Range 
>header field that consists of more than two overlapping ranges, or a 
>set of many small ranges that are not listed in ascending order, 
>since both are indications of either a broken client or a deliberate 
>denial of service attack (Section 6.1). A client SHOULD NOT request 
>multiple ranges that are inherently less efficient to process and 
>transfer than a single range that encompasses the same data."
>
>..or it can serve the response as multipart/byteranges as requested.

Ok.

>>    "If the selected representation would have had a Content-Type
>>     header field in a 200 (OK) response, the server SHOULD generate
>>     that same Content-Type field in the header area of each body part."
>>
>>I don't understand why the RFC 2119 "should" is used in the above.  When
>>can the "should" be ignored?  Is the server supposed to generate the
>
>Dunno.
>
>>same Content-Type header field in each header area if the selected
>>representation would have a Content-Type header field for a 200 (OK)
>>response?
>
>That's what the above says, no?

Ok.

>Such as?

What I mean is that what happens is undefined when both sides do not 
follow the RFC 2119 "should".

>Right. Fixed in <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/2441>.

Ok.

>It is supposed to be interpreted per RFC 2119.

It is better to use the uppercase words after the RFC 2119 boilerplate.

Regards,
S. Moonesamy 


From julian.reschke@gmx.de  Wed Oct 30 01:51:14 2013
Return-Path: <julian.reschke@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 820E011E81C3 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.072
X-Spam-Level: 
X-Spam-Status: No, score=-103.072 tagged_above=-999 required=5 tests=[AWL=-0.473, 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 9vesg2mwhygZ for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:51:08 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 54D3F21F9DD5 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:51:08 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.127.91]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M9wrU-1VUruP3GjQ-00B0pc for <ietf@ietf.org>; Wed, 30 Oct 2013 09:51:01 +0100
Message-ID: <5270C871.2020403@gmx.de>
Date: Wed, 30 Oct 2013 09:50:57 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>,  Julian Reschke <julian.reschke@gmx.de>, draft-ietf-httpbis-p1-messaging.all@tools.ietf.org
Subject: Re: connection limits, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p1-messaging-24
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com> <526FDC52.3030808@gmx.de> <6.2.5.6.2.20131030011734.0ce8d178@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131030011734.0ce8d178@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:zgPF9liGBG+HYUnHZX7QxMhvtUQILzpdSxNqIOoMA/6TdYkfQ7r 2MY4rQjdxedpZxyqSB3TpNqmN7umg7HOzvdRGczPeGbqlWv8Vxvo014SA/UPx4Vp3l+fYiv J0XURwJGI7ma8EcvD93fXpYV/2hWuTXDEcXU7XrbPZTzjxMxix8ojE2Ip3SYPHbA11Mr2W9 cslB6Ad1nND7XdhLero7Q==
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:51:14 -0000

On 2013-10-30 09:31, S Moonesamy wrote:
> Hi Julian,
> At 09:03 29-10-2013, Julian Reschke wrote:
>> I have trouble parsing this comment. Do you see an issue here?
>
> I read the text again (Section 6.4).  It is difficult to say what is
> deemed abusive.  You could get around that with, for example:
>
>    A client SHOULD limit the number of simultaneous open connections
>    that it maintains to a given server as each connection consumes
>    server resources.
>
> Please note that I used some text from the third paragraph of that section.

Well, there are more reasons for limiting the connection; that's why we 
have a separate paragraph about it. Just moving one of them up here 
doesn't look like an improvement to me.

Best regards, Julian

From duerst@it.aoyama.ac.jp  Wed Oct 30 01:53:07 2013
Return-Path: <duerst@it.aoyama.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 448B611E818D; Wed, 30 Oct 2013 01:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.792
X-Spam-Level: 
X-Spam-Status: No, score=-101.792 tagged_above=-999 required=5 tests=[AWL=-2.002, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 FtH1ziOPlDAz; Wed, 30 Oct 2013 01:53:01 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id B531C21F9FBA; Wed, 30 Oct 2013 01:53:00 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r9U8pmE9007965; Wed, 30 Oct 2013 17:51:48 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 6990_8e4f_833d925a_4140_11e3_b8e9_001e6722eec2; Wed, 30 Oct 2013 17:51:48 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 4477EBFF5D; Wed, 30 Oct 2013 17:51:47 +0900 (JST)
Message-ID: <5270C896.6080204@it.aoyama.ac.jp>
Date: Wed, 30 Oct 2013 17:51:34 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>	<526E8B9E.8030006@gmx.de>	<6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de>
In-Reply-To: <526FC24D.7060704@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, apps-discuss@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 08:53:07 -0000

On 2013/10/29 23:12, Julian Reschke wrote:
> On 2013-10-29 14:26, S Moonesamy wrote:
>> Hi Julian,
>> At 09:06 28-10-2013, Julian Reschke wrote:
>>> On 2013-10-28 09:07, S Moonesamy wrote:

>>> RFC 2616 said
>>> (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1.p.4>):
>>>
>>>> Any HTTP/1.1 message containing an entity-body SHOULD include a
>>>> Content-Type header field defining the media type of that body. If
>>>> and only if the media type is not given by a Content-Type field, the
>>>> recipient MAY attempt to guess the media type via inspection of its
>>>> content and/or the name extension(s) of the URI used to identify the
>>>> resource. If the media type remains unknown, the recipient SHOULD
>>>> treat it as type "application/octet-stream".
>>>
>>> ...which isn't that different.
>>
>> The 'If the media type remains unknown, the recipient SHOULD treat it as
>> type "application/octet-stream' from RFC 2616 is not in
>> draft-ietf-httpbis-p2-semantics-24.
>
> I consider that sentence to be useless - if I can't detect the type,
> what else but "treating as arbitrary data" is left as an option anyway?

I have to say that I don't consider this sentence to be useless.

As far as I remember, there are other specs (mail?) that say that 
text/plain is the default. So some implementers may be used to this, and 
apply it to http, too.

Also, while every natural language text has to assume that the reader 
uses a certain amount of rational thinking, specs are usually written 
with a somewhat reduced expectation in that respect, not because the 
average reader is particularly dumb, but because the consequences of 
interpreting something wrong are different than the consequences of 
getting something wrong when e.g. reading a novel.

So I don't see any reason for not keeping that sentence. Even if it 
doesn't help, it definitely doesn't hurt.

Regards,   Martin.

From julian.reschke@gmx.de  Wed Oct 30 01:57:15 2013
Return-Path: <julian.reschke@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 25C3811E828B for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.043
X-Spam-Level: 
X-Spam-Status: No, score=-103.043 tagged_above=-999 required=5 tests=[AWL=-0.444, 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 ot92F1EL4keh for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 01:57:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 11DFB11E8193 for <ietf@ietf.org>; Wed, 30 Oct 2013 01:57:09 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.127.91]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MAloF-1VVhDb0ftr-00Bpfl for <ietf@ietf.org>; Wed, 30 Oct 2013 09:57:08 +0100
Message-ID: <5270C9DE.3000104@gmx.de>
Date: Wed, 30 Oct 2013 09:57:02 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p5-range.all@tools.ietf.org
Subject: Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com> <526FD3E8.9010904@gmx.de> <6.2.5.6.2.20131029232953.0ce8cc58@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131029232953.0ce8cc58@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:KbfJOCibeqxkomc832Yi8vKEEGhRAJ9nJSIOYyoN7QCmAClhW7K 2SZPEPecC2iXI2KFf6z6WeoowzVwLtDZJX0mTEs8NPVvUXpUdfUIqA0cSELd0RQrsuJEsYj ZQJMnD4bFueZHZBbO1nn05XKg+K53PF0cy7qiS0hj414c86BDciXrUoXUMTlPS4o427BYP0 AkMy05WnEGyDVgZJNdNTA==
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:57:15 -0000

On 2013-10-30 08:46, S Moonesamy wrote:
> ...
>> Such as?
>
> What I mean is that what happens is undefined when both sides do not
> follow the RFC 2119 "should".

The response is self-descriptive, so it's up to the client to properly 
process it.

>> It is supposed to be interpreted per RFC 2119.
>
> It is better to use the uppercase words after the RFC 2119 boilerplate.

But then, we don't want the boilerplate to be in front of the 
Introduction. Any *concrete* suggestion how to address this?

Best regards, Julian



From duerst@it.aoyama.ac.jp  Wed Oct 30 02:02:38 2013
Return-Path: <duerst@it.aoyama.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 B1E7B21F9FF2; Wed, 30 Oct 2013 02:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.715
X-Spam-Level: 
X-Spam-Status: No, score=-103.715 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  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 dBuDNZ3Y5b3e; Wed, 30 Oct 2013 02:02:32 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 157F411E828B; Wed, 30 Oct 2013 02:02:30 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r9U926CH024750; Wed, 30 Oct 2013 18:02:06 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 6994_f8b4_f3b34056_4141_11e3_b29c_001e6722eec2; Wed, 30 Oct 2013 18:02:06 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 20E96BFF5D; Wed, 30 Oct 2013 18:02:06 +0900 (JST)
Message-ID: <5270CB01.9@it.aoyama.ac.jp>
Date: Wed, 30 Oct 2013 18:01:53 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Amos Jeffries <squid3@treenet.co.nz>
Subject: Re: obs-date, was: [apps-discuss] APPSDIR review of	draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E6DF4.4030509@gmx.de> <751EE3ED19D0A62BD858585C@JcK-HP8200.jck.com> <526E73B8.90705@gmx.de> <4F6568484E956ADBC46BEB16@JcK-HP8200.jck.com> <526F0EC1.7010809@treenet.co.nz>
In-Reply-To: <526F0EC1.7010809@treenet.co.nz>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, apps-discuss@ietf.org, Julian Reschke <julian.reschke@gmx.de>, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, iesg@ietf.org, John C Klensin <john-ietf@jck.com>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 09:02:38 -0000

On 2013/10/29 10:26, Amos Jeffries wrote:
> On 29/10/2013 8:22 a.m., John C Klensin wrote:

>> My understanding is that the HTTPbis work is a rather major
>> revision with at least some cases for which "get it right" is
>> more important that complete backward compatibility, especially
>> if there is a clear migration path.
>
> No. The focus on the WG has been to document what is actually *working*
> and clarify existing HTTP behaviour in order to encourage interoperability.

To clarify for people not too involved in the HTTPbis work:

The HTTPbis WG has two main work items:

1) Moving HTTP 1.1 to Standard. That's what all the drafts are about 
that are currently under review and discussion in apps-discuss. For 
people familiar with Internet mail, that's somewhat similar to the work 
that happened when moving from RFCs 2821,... to RFCs 5321,... As such, 
it doesn't leave much room for innovation or even fixing stuff that 
looks broken from the outside, and the HTTPbis WG was particularly 
careful to avoid any such breakage.

2) HTTP 2.0: This is a completely new protocol design, so there is quite 
a bit of room for "getting things right", and stuff like using integers 
for representing dates (because the protocol is binary) is being 
considered. This on many fronts allows cleanup similar e.g. to what 
happened in EAI (Email Address Internationalization), because there's no 
deployed base to worry about. But HTTP 2.0 is not yet ready for general 
review.

Regards,   Martin.

From julian.reschke@gmx.de  Wed Oct 30 02:48:15 2013
Return-Path: <julian.reschke@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 B6CDD21E808F for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 02:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.704
X-Spam-Level: 
X-Spam-Status: No, score=-103.704 tagged_above=-999 required=5 tests=[AWL=-1.405, 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 8LZ7GfaJv8Tl for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 02:48:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id F05C211E8102 for <ietf@ietf.org>; Wed, 30 Oct 2013 02:48:03 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M3ARX-1VuloW3vOh-00ssu1 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:48:00 +0100
Message-ID: <5270D5C9.4090004@gmx.de>
Date: Wed, 30 Oct 2013 10:47:53 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Subject: Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>	<526E8B9E.8030006@gmx.de>	<6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de> <5270C896.6080204@it.aoyama.ac.jp>
In-Reply-To: <5270C896.6080204@it.aoyama.ac.jp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:KhN8+V9LpLLH2JlYq3tEsREmtHRSdg7m+ouoIh+hsU1gbhXXO5d CuIELRxprkh5vuh3uF/KqWFdALwpF5eV/U7idms2e0w32z4IocPb1jPilD4Bsyx0tHMi2i0 vGY8O34ok8AlieoJb2nvLV5j4fJEl6bCeMQnvKBLrqROkqaDicssyt5lXcIXhjPejnwSb6e BhvzQ6dtOTVrdk+QYoWxw==
Cc: ietf@ietf.org, apps-discuss@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 09:48:15 -0000

On 2013-10-30 09:51, "Martin J. DĂĽrst" wrote:
> I have to say that I don't consider this sentence to be useless.
>
> As far as I remember, there are other specs (mail?) that say that
> text/plain is the default. So some implementers may be used to this, and
> apply it to http, too.
>
> Also, while every natural language text has to assume that the reader
> uses a certain amount of rational thinking, specs are usually written
> with a somewhat reduced expectation in that respect, not because the
> average reader is particularly dumb, but because the consequences of
> interpreting something wrong are different than the consequences of
> getting something wrong when e.g. reading a novel.
>
> So I don't see any reason for not keeping that sentence. Even if it
> doesn't help, it definitely doesn't hurt.

So what exactly does it mean in *practice* to treat something as 
"arbitrary data". What do you expect a browser to do in that case?

Best regards, Julian


From derhoermi@gmx.net  Wed Oct 30 04:11:49 2013
Return-Path: <derhoermi@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 E933411E8146 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 04:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  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 MIQg7dhJ2Yso for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 04:11:45 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 5656C11E80F9 for <ietf@ietf.org>; Wed, 30 Oct 2013 04:11:45 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.15.221]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0MNqcR-1Va72Z0GvD-007RJJ for <ietf@ietf.org>; Wed, 30 Oct 2013 12:11:44 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: RFC2119 keywords in registration requirements
Date: Wed, 30 Oct 2013 12:11:46 +0100
Message-ID: <frp179lik8p5lom3vnhrvso4d1cir0ogm5@hive.bjoern.hoehrmann.de>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de>
In-Reply-To: <52701D1D.3030004@gmx.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:LYS5wi1fqT5I1m1CoPl9lUdNCeEbVIqCzl31kSb3y6NaLyC6/9f /5iuwBDonpCUcA4TWKOrZzoTXM7p7yjVy+OomvtvjT2cI/YeL9Qz9wvB7FMiDKCkF1sA/Iw hT1Nrd+Avq4rteCFWlB5x8UDlp2u/j9FXcViE/XhGZzpHwBWq2uFzLkHAO/4tHVfp4zZ9JA poQ3QemUg12ktxLq9mmiA==
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, 30 Oct 2013 11:11:50 -0000

* Julian Reschke wrote:
>On 2013-10-29 21:29, Bradner, Scott wrote:
>> seems to me to be completely reasonable to say MUST include the number of the RFC that describes
>> the protocol being registered (for example)

>But then:
>
>> 6. Guidance in the use of these Imperatives
>>
>>    Imperatives of the type defined in this memo must be used with care
>>    and sparingly.  In particular, they MUST only be used where it is
>>    actually required for interoperation or to limit behavior which has
>>    potential for causing harm (e.g., limiting retransmisssions)  For
>>    example, they must not be used to try to impose a particular method
>>    on implementors where the method is not required for
>>    interoperability.
>
>To me this indicates that we should keep them out of registrations 
>procedures.
>
>(I also note that the "MUST" in the text I quoted shouldn't been used if 
>the text followed its own advice :-).

You think there is no potential for causing harm in inappropriately
using these imperatives? I rather think there is. And having proper
information in registries is quite often necessary to achieve inter-
operation.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From julian.reschke@gmx.de  Wed Oct 30 05:18:28 2013
Return-Path: <julian.reschke@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 DF0F211E8167 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 05:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.959
X-Spam-Level: 
X-Spam-Status: No, score=-103.959 tagged_above=-999 required=5 tests=[AWL=-1.360, 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 dbdZI1-pAAVH for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 05:18:23 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id A400C11E81F4 for <ietf@ietf.org>; Wed, 30 Oct 2013 05:18:12 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MQRZw-1VEHz50kiC-00Tp8B for <ietf@ietf.org>; Wed, 30 Oct 2013 13:18:11 +0100
Message-ID: <5270F901.8090807@gmx.de>
Date: Wed, 30 Oct 2013 13:18:09 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: RFC2119 keywords in registration requirements
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <frp179lik8p5lom3vnhrvso4d1cir0ogm5@hive.bjoern.hoehrmann.de>
In-Reply-To: <frp179lik8p5lom3vnhrvso4d1cir0ogm5@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:z7Iapb9wkBMdw6wozaWD4oNKZtajsQegWSe+GvKrSHOPHhgX/mv BLu2UW4x/R4Fk1KwhBd6sLmI0h9GjzcyNpiEy1qdZhxvZycREyLJQ8dHOk7hcSjR/MEe46I ChlWzGr+6Vhuw9v1dHyx8PkQuWbtuSEy8odlUqPntcdMACPl5dliWcD6KcFHN4B7yro2rYE /4wKYnrI1DsuEGnNAL81g==
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, 30 Oct 2013 12:18:29 -0000

On 2013-10-30 12:11, Bjoern Hoehrmann wrote:
> * Julian Reschke wrote:
>> On 2013-10-29 21:29, Bradner, Scott wrote:
>>> seems to me to be completely reasonable to say MUST include the number of the RFC that describes
>>> the protocol being registered (for example)
>
>> But then:
>>
>>> 6. Guidance in the use of these Imperatives
>>>
>>>     Imperatives of the type defined in this memo must be used with care
>>>     and sparingly.  In particular, they MUST only be used where it is
>>>     actually required for interoperation or to limit behavior which has
>>>     potential for causing harm (e.g., limiting retransmisssions)  For
>>>     example, they must not be used to try to impose a particular method
>>>     on implementors where the method is not required for
>>>     interoperability.
>>
>> To me this indicates that we should keep them out of registrations
>> procedures.
>>
>> (I also note that the "MUST" in the text I quoted shouldn't been used if
>> the text followed its own advice :-).
>
> You think there is no potential for causing harm in inappropriately
> using these imperatives? I rather think there is. And having proper
> information in registries is quite often necessary to achieve inter-
> operation.

Yes, but does using RFC2119 keywords here actually improve the 
registrations?

Anyway, I'll leave this to the IESG / our AD to make a choice.

Best regards, Julian


From dromasca@avaya.com  Wed Oct 30 06:41:30 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 A6BFF11E8125; Wed, 30 Oct 2013 06:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.294
X-Spam-Level: 
X-Spam-Status: No, score=-103.294 tagged_above=-999 required=5 tests=[AWL=0.305, 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 yLAR17omKBi6; Wed, 30 Oct 2013 06:41:25 -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 D0A9911E8174; Wed, 30 Oct 2013 06:40:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtUNAAMMcVLGmAcV/2dsb2JhbABZgmYhOFSqX5QjS4ElFm0HgiUBAQEBAwEBAQ8oNAsMBAIBCA0EBAEBCxQFBAcnCxQJCAIEDgUIGodlAQydS50FF48eMQcGgxmBDQOZOYU1iyWBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,601,1378872000"; d="scan'208";a="29658350"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Oct 2013 09:40:42 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Oct 2013 09:35:33 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0146.000; Wed, 30 Oct 2013 14:40:40 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [xrblock] Last Call: <draft-ietf-xrblock-rtcp-xr-qoe-12.txt> (RTP	Control	Protocol (RTCP) Extended Report (XR) Blocks for MOS	Metric Reporting) to Proposed Standard
Thread-Topic: [xrblock] Last Call: <draft-ietf-xrblock-rtcp-xr-qoe-12.txt> (RTP	Control	Protocol (RTCP) Extended Report (XR) Blocks for MOS	Metric Reporting) to Proposed Standard
Thread-Index: AQHO1XKq5bgEjx5v9ke5RjgTZeSejZoNPgDg
Date: Wed, 30 Oct 2013 13:40:39 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA1291D9D6@AZ-FFEXMB04.global.avaya.com>
References: <20131030131841.6969.9377.idtracker@ietfa.amsl.com>
In-Reply-To: <20131030131841.6969.9377.idtracker@ietfa.amsl.com>
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: "xrblock@ietf.org" <xrblock@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 13:41:30 -0000

As you can see this IETF Last Call is extended in time to accommodate the b=
usy period before and during the IETF meeting.=20

We shall definitely take in consideration all commets received during the w=
hole last call period. Comments received before the XRBLOCK WG meeting in V=
ancouver (scheduled for Thursday 11/7) will also be addressed by the author=
s and discussed in the f2f meeting).=20

Regards,

Dan
(WG co-chair)

> -----Original Message-----
> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
> Behalf Of The IESG
> Sent: Wednesday, October 30, 2013 3:19 PM
> To: IETF-Announce
> Cc: xrblock@ietf.org
> Subject: [xrblock] Last Call: <draft-ietf-xrblock-rtcp-xr-qoe-12.txt>
> (RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS Metric
> Reporting) to Proposed Standard
>=20
>=20
> The IESG has received a request from the Metric Blocks for use with
> RTCP's Extended Report Framework WG (xrblock) to consider the following
> document:
> - 'RTP Control Protocol (RTCP) Extended Report (XR) Blocks for MOS
> Metric
>    Reporting'
>   <draft-ietf-xrblock-rtcp-xr-qoe-12.txt> as Proposed Standard
>=20
> 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-11-27. 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.
>=20
> Abstract
>=20
>=20
>    This document defines an RTP Control Protocol (RTCP) Extended Report
>    (XR) Block including two new segment types and associated SDP
>    parameters that allow the reporting of MOS Metrics for use in a range
>    of RTP applications.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-qoe/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-qoe/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock

From julian.reschke@gmx.de  Wed Oct 30 06:53:44 2013
Return-Path: <julian.reschke@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 B9E3A11E8222 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 06:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.981
X-Spam-Level: 
X-Spam-Status: No, score=-103.981 tagged_above=-999 required=5 tests=[AWL=-1.382, 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 c-IeYoo8r7rk for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 06:53:40 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 10B2411E81DB for <ietf@ietf.org>; Wed, 30 Oct 2013 06:53:40 -0700 (PDT)
Received: from [192.168.1.102] ([217.91.35.233]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MBWIM-1VUOfN0y98-00AVoW for <ietf@ietf.org>; Wed, 30 Oct 2013 14:53:39 +0100
Message-ID: <52710F60.7060206@gmx.de>
Date: Wed, 30 Oct 2013 14:53:36 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p1-messaging.all@tools.ietf.org
Subject: deprecation of HTTP header field line folding, was: APPSDIR review of draft-ietf-httpbis-p1-messaging-24
References: <6.2.5.6.2.20131026225145.0bee7bb8@elandnews.com> <6.2.5.6.2.20131028091247.0e37b9d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20131028091247.0e37b9d0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:zrNHbRThfSbxCubESv5FOXkI7F5jO/z4B5v6mkI+755CAtO2fV/ 0e1D10CPrKUeLkBNgGkomJQ/EZAt0JLncCQyK7tLUpQPqjr8hPIK5Ho0+kcvp1g9pXSLJaM ZQDpa5cUMGHcNDDTXzlP3VDNDmzbSE0rIxLP94lIr6/DJsZcvOHuYNmZ+zbX/bCBUr+6CGr Fmt81IuDeP98iwZg8q85g==
Cc: ietf-http-wg@w3.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, 30 Oct 2013 13:53:44 -0000

On 2013-10-28 17:55, S Moonesamy wrote:
> Hello,
>
> While I was reviewing other drafts in the set I noticed that Section
> 3.2.4 of draft-ietf-httpbis-p1-messaging-24 has the following:
>
>    "Historically, HTTP header field values could be extended over
>     multiple lines by preceding each extra line with at least one space
>     or horizontal tab (obs-fold).  This specification deprecates such
>     line folding except within the message/http media type
>     (Section 8.3.1).  A sender MUST NOT generate a message that includes
>     line folding (i.e., that has any field-value that contains a match to
>     the obs-fold rule) unless the message is intended for packaging
>     within the message/http media type."
>
> There is an IETF specification which interpreted Section 4.2 of RFC 2616
> as follows:
>
>    "the HTTP header syntax allows extending single header values across
>     multiple lines, by inserting a line break followed by whitespace"

<http://tools.ietf.org/html/rfc4918#section-10.4.2>

So yes, this is a change from 2616 that we made due to security problems 
(header injection).

> I'll classify deprecating line folding as an issue.
>
> Section 4.2 of RFC 2616 (and RFC 2068) follows the same generic format
> as that given in Section 3.1 of RFC 822.  Section 2.2 of RFC 2616 states
> that:
>
>    "HTTP/1.1 header field values can be folded onto multiple lines if the
>     continuation line begins with a space or horizontal tab."
>
> I suggest that implementors of specifications which have a dependency on
> RFC 2616 review the relevant section in
> draft-ietf-httpbis-p1-messaging-24 about line folding and comment if
> they consider the deprecation as a problem.

Review is always good.

Note that the change is listed in 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-24.html#rfc.section.A.2.p.8>:

"Header fields that span multiple lines ("line folding") are deprecated. 
(Section 3.2.4)"

Best regards, Julian



From jari.arkko@piuha.net  Wed Oct 30 07:05:28 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 82F2921E80B6 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.971
X-Spam-Level: 
X-Spam-Status: No, score=-101.971 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GrxGowvBflkF for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:05:10 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 48A0721E8100 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:05:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DB22F2CCAE for <ietf@ietf.org>; Wed, 30 Oct 2013 16:05:07 +0200 (EET)
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 pMXPrHLcCyuu for <ietf@ietf.org>; Wed, 30 Oct 2013 16:05:07 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FAD12CC48 for <ietf@ietf.org>; Wed, 30 Oct 2013 16:05:07 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5270C66C.9070109@pi.nu>
Date: Wed, 30 Oct 2013 16:05:07 +0200
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@piuha.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org>	<20131030081355.GA23990@nic.fr>	<ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr> <5270C66C.9070109@pi.nu>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:05:28 -0000

There is both a local participant aspect and over-the-network aspect. I =
think giving the times both as local times and UTC is a good idea.

We'll try to do that from now on. I have changed my blog article.

Jari


From tjc@ecs.soton.ac.uk  Wed Oct 30 07:09:15 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 348BA11E8227 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257,  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 SPjWHMLcDnlm for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:09: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 6D5B011E822A for <ietf@ietf.org>; Wed, 30 Oct 2013 07:08:55 -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 r9UE8mcG021621;  Wed, 30 Oct 2013 14:08:48 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r9UE8mcG021621
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1383142128; bh=984Yb5utVkoic4hCI2daYBGrJhY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=rqcYj/fxraBjTU4CIgj49t73JKfXvaIi4nAqhNhly2H5fgCDmguhJMEOHpN1eMUxn U+4u5oEy+W+MPCN8tD9vVxyYtNLPNQEGIJLyn6CD6YHdDJ+wHy0OMPVLvoJYqdVXna g/5zxYLAPI00xSRPrvnmwsxztsj6lAGgPV/m5En0=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p9YE8m0959649989yw ret-id none; Wed, 30 Oct 2013 14:08:48 +0000
Received: from dhcp-202-90.wireless.soton.ac.uk (dhcp-202-90.wireless.soton.ac.uk [152.78.202.90]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r9UE8j30030928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Oct 2013 14:08:45 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>
Date: Wed, 30 Oct 2013 14:08:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p9YE8m095964998900; tid=p9YE8m0959649989yw; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r9UE8mcG021621
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:09:15 -0000

On 30 Oct 2013, at 08:25, Carsten Bormann <cabo@tzi.org> wrote:

> On 30 Oct 2013, at 09:13, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
>=20
>> IETF must use only UTC when announcing a worldwide event.
>=20
> I don=92t know about =93only UTC" for events that are also visited =
locally, but giving the UTC time as well would be a good idea.  Even =
more so for a event that is days from a local time zone change.
>=20
> Beyond UTC, I would normally point to
>=20
> 	http://datatracker.ietf.org/meeting/agenda-utc

This was something I suggested a couple of IETFs ago, and the tools team =
implemented it very quickly.

I think if you have constructive suggestions that can be implemented, =
the tools team is all ears :)

Tim


From ned+ietf@mauve.mrochek.com  Wed Oct 30 07:16:48 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 758C911E8171 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:16: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 mr+NGxbZAI+m for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:16:43 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA7811E8222 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:16:43 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P06PWQXSDC007OS8@mauve.mrochek.com> for ietf@ietf.org; Wed, 30 Oct 2013 07:11:41 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=utf-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P067WB5KG0004X76@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 30 Oct 2013 07:11:38 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P06PWP9XG4004X76@mauve.mrochek.com>
Date: Wed, 30 Oct 2013 07:08:03 -0700 (PDT)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-reply-to: "Your message dated Wed, 30 Oct 2013 09:36:12 +0100" <20131030083611.GA27804@nic.fr>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:16:48 -0000

> On Wed, Oct 30, 2013 at 09:25:59AM +0100,
>  Carsten Bormann <cabo@tzi.org> wrote
>  a message of 16 lines which said:

> > I donâ€™t know about â€śonly UTC" for events that are also visited
> > locally, but giving the UTC time as well would be a good idea.

> My experience with international organizations is that, when you
> indicate the time in two zones, there is often a discrepancy. With
> only one zone, there is no doubt about the real value.

And my experience is that regardless of what sort of organization you're
dealing with, if you ask them to convert a time for a future event that is
being held in a particular physical location to some other time zone, they
won't apply time zone rules correctly and the only announced time will be
wrong.

Which argues for including the local time when the event will take place. If
you want to mandate that the time also appear in UTC, great, but it's quite
important that the local time also be there.

				Ned

From rlb@ipv.sx  Wed Oct 30 07:19:05 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 E3E1321F9FBE for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.89
X-Spam-Level: 
X-Spam-Status: No, score=-2.89 tagged_above=-999 required=5 tests=[AWL=0.086,  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 S4GAMnyhj3EO for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:02 -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 7B27B21E80F9 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:18:41 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id gq1so1489501obb.32 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:18:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=42joi7AFDgXOLP0HbDV64qN6jNsXdUCZLOOVeaK4Jgg=; b=ilC1AhToefv5iVDyh023+3gB19z8/Ey2AYJ4BFqT9iEe2zoRQsco15Ycj3UCR0j3Rx JjPW4xsKctfqdMXOEi72g3vbUnYTRgidf6plN7nxZsIdyfyZkaUDWT/4adF9C1Krtozy UVcDg8tmsDgRbaQBo8H8XDOzXcBVej4ElbKTzf74s3GrtysEpjhAnTWOlm85pnUXS4WX g2X1BSZi6cdpvRhjCCy1XrB7QH7CQNkKby+YYACTJbfbYKVLgBban2XdGgCIrdI/snza TDQOu14KfOMetRklW/8vvHWgh/AzDULdcj3qNk7GStbbLRgfT4nzni9/TO7bqCdexxkC +bDA==
X-Gm-Message-State: ALoCoQklCpfYnsFzZkFeFgkQBkVF8f2QXufqMP46m/BgGOz87JuUXQ6AXxW9Nl1kp87A7sUHVdjk
MIME-Version: 1.0
X-Received: by 10.182.106.4 with SMTP id gq4mr4479843obb.4.1383142720935; Wed, 30 Oct 2013 07:18:40 -0700 (PDT)
Received: by 10.76.101.10 with HTTP; Wed, 30 Oct 2013 07:18:40 -0700 (PDT)
In-Reply-To: <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk>
Date: Wed, 30 Oct 2013 10:18:40 -0400
Message-ID: <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Richard Barnes <rlb@ipv.sx>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=e89a8fb1fa628e2dbf04e9f60249
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:19:06 -0000

--e89a8fb1fa628e2dbf04e9f60249
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I hope everyone in the IETF is familiar with sites such as:
<http://www.timeanddate.com/>
<http://www.worldtimebuddy.com/>


On Wed, Oct 30, 2013 at 10:08 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 30 Oct 2013, at 08:25, Carsten Bormann <cabo@tzi.org> wrote:
>
> > On 30 Oct 2013, at 09:13, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote=
:
> >
> >> IETF must use only UTC when announcing a worldwide event.
> >
> > I don=92t know about =93only UTC" for events that are also visited loca=
lly,
> but giving the UTC time as well would be a good idea.  Even more so for a
> event that is days from a local time zone change.
> >
> > Beyond UTC, I would normally point to
> >
> >       http://datatracker.ietf.org/meeting/agenda-utc
>
> This was something I suggested a couple of IETFs ago, and the tools team
> implemented it very quickly.
>
> I think if you have constructive suggestions that can be implemented, the
> tools team is all ears :)
>
> Tim
>
>

--e89a8fb1fa628e2dbf04e9f60249
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I hope everyone in the IETF is familiar with sites su=
ch as:<br></div>&lt;<a href=3D"http://www.timeanddate.com/">http://www.time=
anddate.com/</a>&gt;<br>&lt;<a href=3D"http://www.worldtimebuddy.com/">http=
://www.worldtimebuddy.com/</a>&gt;<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Oct 30, 2013 at 10:08 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</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 30 Oct 2013, at 08:25, =
Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tzi.org</a>&gt; wr=
ote:<br>

<br>
&gt; On 30 Oct 2013, at 09:13, Stephane Bortzmeyer &lt;<a href=3D"mailto:bo=
rtzmeyer@nic.fr">bortzmeyer@nic.fr</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; IETF must use only UTC when announcing a worldwide event.<br>
&gt;<br>
&gt; I don=92t know about =93only UTC&quot; for events that are also visite=
d locally, but giving the UTC time as well would be a good idea. =A0Even mo=
re so for a event that is days from a local time zone change.<br>
&gt;<br>
&gt; Beyond UTC, I would normally point to<br>
&gt;<br>
&gt; =A0 =A0 =A0 <a href=3D"http://datatracker.ietf.org/meeting/agenda-utc"=
 target=3D"_blank">http://datatracker.ietf.org/meeting/agenda-utc</a><br>
<br>
</div>This was something I suggested a couple of IETFs ago, and the tools t=
eam implemented it very quickly.<br>
<br>
I think if you have constructive suggestions that can be implemented, the t=
ools team is all ears :)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Tim<br>
<br>
</font></span></blockquote></div><br></div>

--e89a8fb1fa628e2dbf04e9f60249--

From iab-chair@iab.org  Wed Oct 30 07:19:23 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 C4C1721F9EBE for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19: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 KRyTIY5Ni4js for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:19:23 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 64B0221F9F7F for <ietf@ietf.org>; Wed, 30 Oct 2013 07:19:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 8BC8AA6099; Wed, 30 Oct 2013 07:17:08 -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 GO7ArxhS7ycA; Wed, 30 Oct 2013 07:17:08 -0700 (PDT)
Received: from [192.168.2.103] (pool-96-241-225-66.washdc.fios.verizon.net [96.241.225.66]) by c9a.amsl.com (Postfix) with ESMTPSA id 335FDA6087; Wed, 30 Oct 2013 07:17:08 -0700 (PDT)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <20131030081355.GA23990@nic.fr>
Date: Wed, 30 Oct 2013 10:19:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <33E29264-2B13-40F0-BE86-7A840CEEF5AA@iab.org>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
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: Wed, 30 Oct 2013 14:19:23 -0000

Stephane:

I think that the use of the local timezone make it easy for people to =
look it up on the agenda.  I do agree that inclusion of UTC as well =
would have been very helpful.  I'll try to remember to do that in the =
future.

Russ


On Oct 30, 2013, at 4:13 AM, Stephane Bortzmeyer wrote:

> On Tue, Oct 29, 2013 at 09:10:08AM -0400,
> IAB Chair <iab-chair@iab.org> wrote=20
> a message of 54 lines which said:
>=20
>> The Technical Plenary session is expected to be popular.  It will be
>> held on Wednesday, 6 Nov 2013 at 0900 PST,
>=20
> Why why why using a local timezone when announcing a live broadcast,
> which will be seen by many people anywhere in the world?
>=20
> Do note also that there are three different timezones in the world
> which are named PST. Not everyone lives in North America!
>=20
> IETF must use only UTC when announcing a worldwide event.
>=20


From scott.brim@gmail.com  Wed Oct 30 07:25:17 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 8BE9311E8222 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 aaThpbLtk+bk for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25:17 -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 CF9F721E80F3 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:25:10 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wm4so1483560obc.37 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:25:10 -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=JLKMb7ydzHzF/E1hWbEQGFQULYj61U8lBSdRUQO86VY=; b=xHvTotYkliNjoBl8cOC6PeeEnfeN46gbz/fN5P0guUw3rxds9jtaIPVi68C3cUG/1F W3BF92pQo/M1ohUPqgqdExGIp0isW5FCVsrwLBBDEGnB6UjS6rnDa8/pCYijM49qKcl8 91n7/SrS8UWsgTnxMmjc2tA9j6krlK5ej6pTdLNmtjLlh/a6mrwwNcd2RNpbjbI2O8e/ YryLis0M5N/ejYJJJcxHs3iTQI3/7KFANeo7g81Qai/M1lQz/YtawirLOf2MPYZ4w71y ljswqn21+CY8ZEWihPGKPp+EI9BnfhYkvJ5nYupJ1rrB+hNO0+0ylJQ+S1qC5Dp77lLm +YFQ==
X-Received: by 10.60.142.137 with SMTP id rw9mr64757oeb.94.1383143110268; Wed, 30 Oct 2013 07:25:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.2.134 with HTTP; Wed, 30 Oct 2013 07:24:50 -0700 (PDT)
In-Reply-To: <01P06PWP9XG4004X76@mauve.mrochek.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 30 Oct 2013 10:24:50 -0400
Message-ID: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
To: "ned+ietf" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=047d7b2e463cc2dc1004e9f619fb
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:25:17 -0000

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

One aspect of the problem is calendar apps.  Some rather popular ones don't
have a way to enter UTC, only UK time eg. BST, so you need some local time
somewhere to enter the event in your calendar.

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

<div dir=3D"ltr"><div class=3D"gmail_extra">One aspect of the problem is ca=
lendar apps. =A0Some rather popular ones don&#39;t have a way to enter UTC,=
 only UK time eg. BST, so you need some local time somewhere to enter the e=
vent in your calendar.</div>

</div>

--047d7b2e463cc2dc1004e9f619fb--

From ned+ietf@mauve.mrochek.com  Wed Oct 30 07:25:53 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 3E79C11E823B for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25: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 AXqiUS4jJg0F for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:25:41 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7246A21E80FC for <ietf@ietf.org>; Wed, 30 Oct 2013 07:25:33 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P06Q8OS2N40081MN@mauve.mrochek.com> for ietf@ietf.org; Wed, 30 Oct 2013 07:20:32 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P067WB5KG0004X76@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 30 Oct 2013 07:20:29 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P06Q8NMQJ2004X76@mauve.mrochek.com>
Date: Wed, 30 Oct 2013 07:13:34 -0700 (PDT)
Subject: Re: RFC2119 keywords in registration requirements
In-reply-to: "Your message dated Wed, 30 Oct 2013 13:18:09 +0100" <5270F901.8090807@gmx.de>
References: <527018FD.2010405@gmx.de> <A8B2401F-4EB0-4373-BA62-C9E9DF2E601D@harvard.edu> <52701D1D.3030004@gmx.de> <frp179lik8p5lom3vnhrvso4d1cir0ogm5@hive.bjoern.hoehrmann.de> <5270F901.8090807@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, 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, 30 Oct 2013 14:25:53 -0000

> On 2013-10-30 12:11, Bjoern Hoehrmann wrote:
> > * Julian Reschke wrote:
> >> On 2013-10-29 21:29, Bradner, Scott wrote:
> >>> seems to me to be completely reasonable to say MUST include the number of the RFC that describes
> >>> the protocol being registered (for example)
> >
> >> But then:
> >>
> >>> 6. Guidance in the use of these Imperatives
> >>>
> >>>     Imperatives of the type defined in this memo must be used with care
> >>>     and sparingly.  In particular, they MUST only be used where it is
> >>>     actually required for interoperation or to limit behavior which has
> >>>     potential for causing harm (e.g., limiting retransmisssions)  For
> >>>     example, they must not be used to try to impose a particular method
> >>>     on implementors where the method is not required for
> >>>     interoperability.
> >>
> >> To me this indicates that we should keep them out of registrations
> >> procedures.
> >>
> >> (I also note that the "MUST" in the text I quoted shouldn't been used if
> >> the text followed its own advice :-).
> >
> > You think there is no potential for causing harm in inappropriately
> > using these imperatives? I rather think there is. And having proper
> > information in registries is quite often necessary to achieve inter-
> > operation.

> Yes, but does using RFC2119 keywords here actually improve the
> registrations?

Of course it's impossible to be sure, but I can say that overall media type
registration quality has ticked up when we've released revised registration
procedures that make increased used of the RFC 2119 vocabulary.

> Anyway, I'll leave this to the IESG / our AD to make a choice.

Um, actually, this is not really up to the IESG. The most the IESG could
realistically say is that use of RFC 2119 language specifically is
inappropriate in current and future registration documents. That would leave
the door open to such documents specifying their own compliance vocabulary, and
I can assure you that is exactly what would happen for any document I'm
involved with. There's nothing magical about RFC 2119.

I suppose the IESG could then go so far as to say that such documents
should never use such vocabularies, but that seems rather unlikely.

				Ned

From randy@psg.com  Wed Oct 30 07:26:40 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 11BDD11E8221 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level: 
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=-0.617, 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 FDPRswWu2+kj for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:26:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 98B5811E8222 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:26:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VbWir-0002h4-U8; Wed, 30 Oct 2013 14:26:14 +0000
Date: Wed, 30 Oct 2013 07:26:13 -0700
Message-ID: <m2habyq1h6.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-Reply-To: <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@piuha.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr> <5270C66C.9070109@pi.nu> <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@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: Wed, 30 Oct 2013 14:26:40 -0000

since we were looking for a rat-hole, i can crawl in this one.

from the ops pov, uct/gmt (and let's skip that rathole) makes sense.
most of us think that way.  but it is amusing to note that i worked for
one global isp which runs on the new jersey timezone and another global
isp that runs on japanese standard time <blush>.  and i am sure there
are more.

but i suspect we all know how to convert.

randy

From dave@cridland.net  Wed Oct 30 07:30:22 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 B62C311E823D for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:30:22 -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=[AWL=-0.001, 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 JiESq+WXLflZ for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:30:18 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 67D9E11E822D for <ietf@ietf.org>; Wed, 30 Oct 2013 07:30:14 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id b13so1401774wgh.15 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=to:cc:message-id:references:in-reply-to:date:from:mime-version :subject:content-type; bh=q3nfFhKPilPM/iC6TteJ1UGQEeONnmkTkwPM2TeiFTU=; b=GEiYK80YIiX5qjHHmie1fjvAaP+RfO9GV09OQ34MtaePQ9dte0bg6s2a+vEop06nhg G6R/v95r/N15yvw37p62xAN0CcpmN+iPLrKXz7z4hfhY7PzrjwSPFuQUykNZrdREHT7b EG9Pg50GM6+yuPqzeh7cheF6NozowjohAn4Pg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:message-id:references:in-reply-to:date :from:mime-version:subject:content-type; bh=q3nfFhKPilPM/iC6TteJ1UGQEeONnmkTkwPM2TeiFTU=; b=foPukLYxa6emF28VXYxO+6MKDv026VFrymlHtFUz+evflqoxgKjz55vygnJAkTnQaT lvxlk/0GTkYKfvVDH+x07GvCKiO/zhQy1JqyrLaWSNZNRMDdf35U63OyYwNP+g4FbD7v nsN5xRsbr3fbw89aSwXJ9b36bWLH0oLPh13s5EzCKmMWXpaFPrk3LDNCyhPl8eYSgpsP kYXLJft3degDSvQHoaw7WJGyt4D0tTDc5iFM0tosZGcWDzNO09sIlL5w1uqKrm4gdTzU KYqmSEsQPHwZ+fl617aTobX+ECF9k4GlcBPnHtUukVczZ+hcqQwKOGMfTytaHLCrUMf/ 22aA==
X-Gm-Message-State: ALoCoQlLlUHFMOr0lJGn+KxvbOX4GJVnYf6PnwtbBVtsKH+jVV7tmZTGG9GG/7kbo+jktEWTTUOh
X-Received: by 10.180.187.2 with SMTP id fo2mr2993001wic.65.1383143413394; Wed, 30 Oct 2013 07:30:13 -0700 (PDT)
Received: from Mac-mini.local (peirce.dave.cridland.net. [217.155.137.61]) by mx.google.com with ESMTPSA id pi6sm16194980wic.3.2013.10.30.07.30.12 for <multiple recipients> (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Wed, 30 Oct 2013 07:30:12 -0700 (PDT)
To: Richard Barnes <rlb@ipv.sx>
Message-Id: <XyRGzVN6jOwk6F_vwEhe8OdueiPR8DgdnsPcWPmoKmbQ39LtU@smtp.gmail.com>
References: <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <20131030081355.GA23990@nic.fr> <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com>
In-Reply-To: <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com>
Date: Wed, 30 Oct 2013 14:30:11 -0000
From: Dave Cridland <dave@cridland.net>
Mime-Version: 1.0
X-Mailer: Inky (TM) v2.0.5270.DAB2 ("Ink Different")
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Content-Type: multipart/alternative; boundary="79163.1383143412.521727@Mac-mini.local"
Cc: Carsten Bormann <cabo@tzi.org>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:30:22 -0000

--79163.1383143412.521727@Mac-mini.local
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Richard Barnes wrote:
> I hope everyone in the IETF is familiar with sites such as:
> <[http://www.timeanddate.com/: <http://www.timeanddate.com/>]> 
>  
> <[http://www.worldtimebuddy.com/: <http://www.worldtimebuddy.com/>]>
>

Yes, but given we're in the throes of timezone mutilation for the purposes of 
playing a longer game of golf, I'm not sure what the offset is, nor what it 
will be by then.

If you pick the translation into local now, for most folk in Europe, it'll 
give you 1700. By Wednesday 6th November, it'll be 1800. I think.

For UK folk, it'll be 1700. (Which I get by entering Vancouver as the timezone 
in Google calendar).

Did I mention I hate daylight savings time?

Dave.
â€‹â€”
Dave Cridland -- Sent with Inky -- [http://inky.com/: <http://inky.com/>]


--79163.1383143412.521727@Mac-mini.local
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<body><div=20class=3D"inlined-message"=20id=3D"message-coda"=20name=3D"mess=
age-coda">
=09<span=20class=3D"message-attribution">Richard=20Barnes=20wrote:</span>
=09<div=20class=3D"quoted"=20style=3D"border-left:=201px=20solid=20black;=
=20margin:=200pt=200pt=200pt=200.25em;=20padding-left:=201em;=20padding-top=
:=201ex;">
=09=09<div=20class=3D"sanitized-message=20sanitized-message-TEQFYUFuEeO28xD=
dscPomQ">
=09=09=09<div=20dir=3D"ltr">
=09=09=09=09<div>
=09=09=09=09=09I=20hope=20everyone=20in=20the=20IETF=20is=20familiar=20with=
=20sites=20such=20as:</div>
=09=09=09=09&lt;<a=20href=3D"http://www.timeanddate.com/"=20target=3D"_blan=
k">http://www.timeanddate.com/</a>&gt;<br>
=09=09=09=09&lt;<a=20href=3D"http://www.worldtimebuddy.com/"=20target=3D"_b=
lank">http://www.worldtimebuddy.com/</a>&gt;</div>
=09=09=09<div=20class=3D"gmail_extra">
=09=09=09=09<p=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=09=09=09=09=C2=A0</p>
=09=09=09</div>
=09=09</div>
=09</div>
</div>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09Yes,=20but=20given=20we're=20in=20the=20throes=20of=20timezone=20mutilat=
ion=20for=20the=20purposes=20of=20playing=20a=20longer=20game=20of=20golf,=
=20I'm=20not=20sure=20what=20the=20offset=20is,=20nor=20what=20it=20will=20=
be=20by=20then.</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09If=20you=20pick=20the=20translation=20into=20local=20now,=20for=20most=
=20folk=20in=20Europe,=20it'll=20give=20you=201700.=20By=20Wednesday=206th=
=20November,=20it'll=20be=201800.=20I=20think.</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09For=20UK=20folk,=20it'll=20be=201700.=20(Which=20I=20get=20by=20entering=
=20Vancouver=20as=20the=20timezone=20in=20Google=20calendar).</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09Did=20I=20mention=20I=20hate=20daylight=20savings=20time?</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09Dave.</p>
<p=20class=3D"inline-text"=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=E2=80=8B=E2=80=94=C2=A0</p>
<div=20class=3D"message-signature"=20id=3D"signature_1383142786834-41782355=
3"=20name=3D"signature_1383142786834-417823553">
=09<p=20style=3D"text-align:=20center;=20margin:=200px;=20padding:=200px;=
=20">
=09=09<span=20style=3D"font-family:=20Arial,=20Helvetica=20Neue,=20Helvetic=
a,=20sans-serif;=20color:=20rgb(153,=20153,=20153);">Dave=20Cridland=20--=
=C2=A0Sent=20with=20Inky=20--</span><span=20style=3D"font-family:=20Arial,=
=20'Helvetica=20Neue',=20Helvetica,=20sans-serif;=20"><font=20color=3D"#339=
6c0">=C2=A0<a=20href=3D"http://inky.com/">http://inky.com/</a></font></span=
></p>
</div>
<p=20style=3D"margin:=200px;=20padding:=200px;=20">
=09=C2=A0</p>
</body>

--79163.1383143412.521727@Mac-mini.local--

From olejacobsen@me.com  Wed Oct 30 07:32:21 2013
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D10511E8296 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.646
X-Spam-Level: 
X-Spam-Status: No, score=-3.646 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 ebzLCzyj2jNX for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:32:16 -0700 (PDT)
Received: from st11p00mm-asmtp002.mac.com (st11p00mm-asmtp002.mac.com [17.172.81.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FDDD11E822D for <ietf@ietf.org>; Wed, 30 Oct 2013 07:32:09 -0700 (PDT)
Received: from 173-11-110-132-sfba.hfc.comcastbusiness.net (173-11-110-132-SFBA.hfc.comcastbusiness.net [173.11.110.132]) by st11p00mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0MVH00LIUKDJZZ00@st11p00mm-asmtp002.mac.com> for ietf@ietf.org; Wed, 30 Oct 2013 14:32:09 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-10-30_05:2013-10-30, 2013-10-30, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=7 spamscore=7 suspectscore=21 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1310300098
Date: Wed, 30 Oct 2013 07:32:02 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Randy Bush <randy@psg.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-reply-to: <m2habyq1h6.wl%randy@psg.com>
Message-id: <alpine.OSX.2.01.1310300731100.99918@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <ADB30B3C-6A91-416D-AF72-4C22A29D6C87@live555.com> <20131030083751.GB27804@nic.fr> <5270C66C.9070109@pi.nu> <0800C77D-7CA2-43DA-AE7E-E6AF7C70310B@piuha.net> <m2habyq1h6.wl%randy@psg.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
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
Reply-To: Ole Jacobsen <olejacobsen@me.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Oct 2013 14:32:21 -0000

I *strongly* recommend http://www.timescroller.com/About.html

(if you have a Mac).


Ole J. Jacobsen
Editor and Publisher
Home: +1 415-550-9427
Cell: +1 415-370-4628
E-mail: olejacobsen@me.com
URL: http://organdemo.info
Skype: organdemo



From rlb@ipv.sx  Wed Oct 30 07:34:20 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 7300E11E8242 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.891
X-Spam-Level: 
X-Spam-Status: No, score=-2.891 tagged_above=-999 required=5 tests=[AWL=0.085,  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 QTD4jm18H5lo for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:34:16 -0700 (PDT)
Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6D96511E8171 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:34:16 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id j1so1490696oag.39 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:34:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=AnS7NXlHiObg7lZp08DQF8s7UJ5evBrzll4Zp8/Wbbg=; b=H+JMERmUb8S9czSX5tyrykXBlAf1zDeZG7qzY+4YUBbG5uGlQVyi2Y4zUMIg4KBrs6 F7g/FqpGjln4osViX8ywFI9KB/4gBYe6iTSlI6oO6Dxl1Avh2QWNkaGY299rGEbxRjbS sz9dsMoQ8N0N4+oTcPlU3joMvLIJAu3KeNbopa1K8tDXC71jOvFAP8irqrItzBg8x4j/ bONGjtOTqfHYkEaya+XRJtWSw5kCePbkTbhWKzQ0kHoze4bnDXaPlIHeNzsODXmO8pmn jSZ/Ioz2GWM5kQMFAMcPuiPG04DHvJ8i2yCR+mQ2bxtZeWg/lTSvMeSAtMxU0kunJ+l0 o9XQ==
X-Gm-Message-State: ALoCoQmBghwLJorPQaMIza5DpzPWTnhU+N5dyYcEXqn++yufr8Ad+4EncWpznoWuVU0Inyr0Mcct
MIME-Version: 1.0
X-Received: by 10.182.143.103 with SMTP id sd7mr1434293obb.70.1383143655970; Wed, 30 Oct 2013 07:34:15 -0700 (PDT)
Received: by 10.76.101.10 with HTTP; Wed, 30 Oct 2013 07:34:15 -0700 (PDT)
In-Reply-To: <XyRGzVN6jOwk6F_vwEhe8OdueiPR8DgdnsPcWPmoKmbQ39LtU@smtp.gmail.com>
References: <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <20131030081355.GA23990@nic.fr> <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com> <XyRGzVN6jOwk6F_vwEhe8OdueiPR8DgdnsPcWPmoKmbQ39LtU@smtp.gmail.com>
Date: Wed, 30 Oct 2013 10:34:15 -0400
Message-ID: <CAL02cgRXBWom+0VGvqqEmw2NnBzu_wLcym1rLbAN7kLbg8tpSA@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Richard Barnes <rlb@ipv.sx>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=e89a8ff1ce9e49adb804e9f63ae4
Cc: Carsten Bormann <cabo@tzi.org>, Tim Chown <tjc@ecs.soton.ac.uk>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:34:20 -0000

--e89a8ff1ce9e49adb804e9f63ae4
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This is why these tools have an option to set the date when computing
future times.

--Richard


On Wed, Oct 30, 2013 at 10:30 AM, Dave Cridland <dave@cridland.net> wrote:

> Richard Barnes wrote:
>   I hope everyone in the IETF is familiar with sites such as:
> <http://www.timeanddate.com/>
> <http://www.worldtimebuddy.com/>
>
>
>
>
>
> Yes, but given we're in the throes of timezone mutilation for the purpose=
s
> of playing a longer game of golf, I'm not sure what the offset is, nor wh=
at
> it will be by then.
>
>
>
> If you pick the translation into local now, for most folk in Europe, it'l=
l
> give you 1700. By Wednesday 6th November, it'll be 1800. I think.
>
>
>
> For UK folk, it'll be 1700. (Which I get by entering Vancouver as the
> timezone in Google calendar).
>
>
>
> Did I mention I hate daylight savings time?
>
>
>
> Dave.
>
> =97
>
> Dave Cridland -- Sent with Inky -- http://inky.com/
>
>
>

--e89a8ff1ce9e49adb804e9f63ae4
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>This is why these tools have an option to set th=
e date when computing future times.<br></div></div><div><div><div><br>--Ric=
hard<br></div></div></div></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">
On Wed, Oct 30, 2013 at 10:30 AM, Dave Cridland <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</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><div class=3D"im"><div name=3D"message-coda">
	<span>Richard Barnes wrote:</span>
	<div style=3D"border-left:1px solid black;margin:0pt 0pt 0pt 0.25em;paddin=
g-left:1em;padding-top:1ex">
		<div>
			<div dir=3D"ltr">
				<div>
					I hope everyone in the IETF is familiar with sites such as:</div>
				&lt;<a href=3D"http://www.timeanddate.com/" target=3D"_blank">http://ww=
w.timeanddate.com/</a>&gt;<br>
				&lt;<a href=3D"http://www.worldtimebuddy.com/" target=3D"_blank">http:/=
/www.worldtimebuddy.com/</a>&gt;</div>
			<div class=3D"gmail_extra">
				<p style=3D"margin:0px;padding:0px">
					=A0</p>
			</div>
		</div>
	</div>
</div>
<p style=3D"margin:0px;padding:0px">
	=A0</p>
</div><p style=3D"margin:0px;padding:0px">
	Yes, but given we&#39;re in the throes of timezone mutilation for the purp=
oses of playing a longer game of golf, I&#39;m not sure what the offset is,=
 nor what it will be by then.</p>
<p style=3D"margin:0px;padding:0px">
	=A0</p>
<p style=3D"margin:0px;padding:0px">
	If you pick the translation into local now, for most folk in Europe, it&#3=
9;ll give you 1700. By Wednesday 6th November, it&#39;ll be 1800. I think.<=
/p>
<p style=3D"margin:0px;padding:0px">
	=A0</p>
<p style=3D"margin:0px;padding:0px">
	For UK folk, it&#39;ll be 1700. (Which I get by entering Vancouver as the =
timezone in Google calendar).</p>
<p style=3D"margin:0px;padding:0px">
	=A0</p>
<p style=3D"margin:0px;padding:0px">
	Did I mention I hate daylight savings time?</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">
	=97=A0</p>
<div name=3D"signature_1383142786834-417823553">
	<p style=3D"text-align:center;margin:0px;padding:0px">
		<span style=3D"font-family:Arial,Helvetica Neue,Helvetica,sans-serif;colo=
r:rgb(153,153,153)">Dave Cridland --=A0Sent with Inky --</span><span style=
=3D"font-family:Arial,&#39;Helvetica Neue&#39;,Helvetica,sans-serif"><font =
color=3D"#3396c0">=A0<a href=3D"http://inky.com/" target=3D"_blank">http://=
inky.com/</a></font></span></p>

</div>
<p style=3D"margin:0px;padding:0px">
	=A0</p>
</div>
</blockquote></div><br></div>

--e89a8ff1ce9e49adb804e9f63ae4--

From lear@cisco.com  Wed Oct 30 07:38:57 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 D5BB321E80F1 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.464
X-Spam-Level: 
X-Spam-Status: No, score=-110.464 tagged_above=-999 required=5 tests=[AWL=0.135, 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 DlQwajD2XiZr for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:38:51 -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 8A83D11E8253 for <ietf@ietf.org>; Wed, 30 Oct 2013 07:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1593; q=dns/txt; s=iport; t=1383143930; x=1384353530; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RQ2WQCcMXSuCtxE6nw2/MO9mRasSV0pbUGRU8zm0RBA=; b=jBZONd5Ad1tnAlyQ/axw37MXF2twkxbtOBzGUA/rj4pqxWin4ac+PS+r qShG+4EUhmJQGfdRGhmzrg2BpxJgZQ1lQYibyqbBZW6QgA6dCeqtR16mS y2IId+jSs7qj/0/JoKVhAau1Hh/xk86VQLDVDaHeH7SqRgxrWPVRplutt M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAFkZcVKQ/khL/2dsb2JhbABZgweEH7w6gSYWdIIlAQEBBCMPAUUBEAsYAgIFFgQHAgIJAwIBAgErGgYBDAEFAgEBiAOoKZJagSmMboE4B4JqgUIDmAqSCYFogT87
X-IronPort-AV: E=Sophos;i="4.93,601,1378857600"; d="scan'208";a="161202065"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 30 Oct 2013 14:38:40 +0000
Received: from mctiny.local ([10.61.171.124]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9UEcXcw017934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 14:38:36 GMT
Message-ID: <527119E9.5050407@cisco.com>
Date: Wed, 30 Oct 2013 15:38:33 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org>	<20131030081355.GA23990@nic.fr>	<7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org>	<20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com>
In-Reply-To: <01P06PWP9XG4004X76@mauve.mrochek.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:38:57 -0000

On 10/30/13 3:08 PM, ned+ietf@mauve.mrochek.com wrote:
>> On Wed, Oct 30, 2013 at 09:25:59AM +0100,
>>  Carsten Bormann <cabo@tzi.org> wrote
>>  a message of 16 lines which said:
>>> I donâ€™t know about â€śonly UTC" for events that are also visited
>>> locally, but giving the UTC time as well would be a good idea.
>> My experience with international organizations is that, when you
>> indicate the time in two zones, there is often a discrepancy. With
>> only one zone, there is no doubt about the real value.
> And my experience is that regardless of what sort of organization you're
> dealing with, if you ask them to convert a time for a future event that is
> being held in a particular physical location to some other time zone, they
> won't apply time zone rules correctly and the only announced time will be
> wrong.
>
> Which argues for including the local time when the event will take place. If
> you want to mandate that the time also appear in UTC, great, but it's quite
> important that the local time also be there.

And local time should be normative to deal with such unforeseen
circumstances as a papal visit.  From the southamerica file in the TZ
database:

# From Daniel C. Sobral (1998-02-12):
# In 1997, the DS began on October 6. The stated reason was that
# because international television networks ignored Brazil's policy on DS,
# they bought the wrong times on satellite for coverage of Pope's visit.
# This year, the ending date of DS was postponed to March 1
# to help dealing with the shortages of electric power.

;-)

Eliot

From ned+ietf@mauve.mrochek.com  Wed Oct 30 07:58:32 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 771F311E8250 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:58: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 c4q86VDFRSIx for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 07:58:22 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C08E111E823D for <ietf@ietf.org>; Wed, 30 Oct 2013 07:58:20 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P06RDBS73K007XCW@mauve.mrochek.com> for ietf@ietf.org; Wed, 30 Oct 2013 07:53:19 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=UTF-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P067WB5KG0004X76@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 30 Oct 2013 07:53:14 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P06RD9XM60004X76@mauve.mrochek.com>
Date: Wed, 30 Oct 2013 07:52:55 -0700 (PDT)
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-reply-to: "Your message dated Wed, 30 Oct 2013 15:38:33 +0100" <527119E9.5050407@cisco.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com> <527119E9.5050407@cisco.com>
To: Eliot Lear <lear@cisco.com>
Cc: ned+ietf@mauve.mrochek.com, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 14:58:32 -0000

> > Which argues for including the local time when the event will take place. If
> > you want to mandate that the time also appear in UTC, great, but it's quite
> > important that the local time also be there.

> And local time should be normative to deal with such unforeseen
> circumstances as a papal visit.  From the southamerica file in the TZ
> database:

> # From Daniel C. Sobral (1998-02-12):
> # In 1997, the DS began on October 6. The stated reason was that
> # because international television networks ignored Brazil's policy on DS,
> # they bought the wrong times on satellite for coverage of Pope's visit.
> # This year, the ending date of DS was postponed to March 1
> # to help dealing with the shortages of electric power.

> ;-)

Good point. I agree.

				Ned

From fanf2@hermes.cam.ac.uk  Wed Oct 30 08:20:13 2013
Return-Path: <fanf2@hermes.cam.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 77FBB11E825C for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 08:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020,  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 pnY3smCi-x9q for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 08:20:12 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCEB11E8250 for <ietf@ietf.org>; Wed, 30 Oct 2013 08:19:35 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:36095) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1VbXYK-00047M-0a (Exim 4.80_167-5a66dd3) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 30 Oct 2013 15:19:24 +0000
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1VbXYK-0003iP-4T (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 30 Oct 2013 15:19:24 +0000
Date: Wed, 30 Oct 2013 15:19:24 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-Reply-To: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1310301515200.3100@hermes-2.csi.cam.ac.uk>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 15:20:13 -0000

Scott Brim <scott.brim@gmail.com> wrote:

> One aspect of the problem is calendar apps.

My "favourite" is the one that uses the name GMT for the UK's time zone
all year round, even though it knows the summer time rules.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From cyrus@daboo.name  Wed Oct 30 08:24:05 2013
Return-Path: <cyrus@daboo.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 C8EB611E8199; Wed, 30 Oct 2013 08:24: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 1bGzyOmwYC5A; Wed, 30 Oct 2013 08:24:01 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 980F811E824A; Wed, 30 Oct 2013 08:23:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 4A39450B294A; Wed, 30 Oct 2013 11:23:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r5wOdUNRMifd; Wed, 30 Oct 2013 11:23:56 -0400 (EDT)
Received: from cc0102a-dhcp145.apple.com (unknown [17.212.158.145]) by daboo.name (Postfix) with ESMTPSA id 1C3A250B293F; Wed, 30 Oct 2013 11:23:54 -0400 (EDT)
Date: Wed, 30 Oct 2013 08:23:22 -0700
From: Cyrus Daboo <cyrus@daboo.name>
To: ned+ietf@mauve.mrochek.com, Eliot Lear <lear@cisco.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Message-ID: <4FBA1270FC906838EB82345F@cc0102a-dhcp145.apple.com>
In-Reply-To: <01P06RD9XM60004X76@mauve.mrochek.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com>	<527119E9.5050407@cisco.com> <01P06RD9XM60004X76@mauve.mrochek.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=2269
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>, IETF-Calsify <calsify@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 15:24:06 -0000

Hi ned+ietf@mauve.mrochek.com,

--On October 30, 2013 at 7:52:55 AM -0700 ned+ietf@mauve.mrochek.com wrote:

>> > Which argues for including the local time when the event will take
>> > place. If you want to mandate that the time also appear in UTC, great,
>> > but it's quite important that the local time also be there.
>
>> And local time should be normative to deal with such unforeseen
>> circumstances as a papal visit.  From the southamerica file in the TZ
>> database:
>
>> # From Daniel C. Sobral (1998-02-12):
>> # In 1997, the DS began on October 6. The stated reason was that
>> # because international television networks ignored Brazil's policy on
>> # DS, they bought the wrong times on satellite for coverage of Pope's
>> # visit. This year, the ending date of DS was postponed to March 1
>> # to help dealing with the shortages of electric power.
>
>> ;-)
>
> Good point. I agree.

Timezones can (and do) change at very short notice in different parts of 
the world. Typically computer systems have timezone data cached as part of 
the OS, and only get updates when the OS is itself updated - often long 
after a timezone change has occurred or long after future events were 
booked but are now out of sync for participants in different timezones. To 
address that a number of folks in the calendaring and scheduling community 
have been working om a timezone service protocol - 
<https://datatracker.ietf.org/doc/draft-douglass-timezone-service/> - our 
initial focus for that has been iCalendar (RFC5545) based VTIMEZONE 
component delivery to calendar and scheduling clients and servers. However, 
we would like to also deliver OS-style timezone data to devices to break 
out of the requirement for those to be updated only when the OS itself 
updates. For unix-based OS's that means being able to deliver "raw" 
zoneinfo" data over that protocol.

Anyway, if you are interested in that work please comment over on the 
ietf-calsify list (cc'd) - we (the authors of that draft) - intend to get 
it moving to last call soon. There are already several implementations that 
have undergone testing at the Calendaring and Scheduling Consortium 
(CalConnect) interop events, so we are happy with it, but would appreciate 
more feedback.

-- 
Cyrus Daboo


From derhoermi@gmx.net  Wed Oct 30 08:36:49 2013
Return-Path: <derhoermi@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 DEA2621E8113 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 08:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.73
X-Spam-Level: 
X-Spam-Status: No, score=-2.73 tagged_above=-999 required=5 tests=[AWL=-0.131,  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 Dy9WaHb74piT for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 08:36:32 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 3530F21E80FE for <ietf@ietf.org>; Wed, 30 Oct 2013 08:36:32 -0700 (PDT)
Received: from netb.Speedport_W_700V ([91.35.15.221]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0Lxdfb-1Vic693sHT-017DB1 for <ietf@ietf.org>; Wed, 30 Oct 2013 16:36:31 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
Date: Wed, 30 Oct 2013 16:36:32 +0100
Message-ID: <am8279ld1riuft4kjkfj4humo3u934faio@hive.bjoern.hoehrmann.de>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
In-Reply-To: <20131030081355.GA23990@nic.fr>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:vGW403iQxRyt21GjWvVPhGHIarRFNGegm/lTGtjDjLm1kXjFPAn N5sPCZ3K5X2ac6o8ENmrD7NoxXXqcpKB08b5T9Asw2rANHlR+Ki4xVRUzToD6GU2w9Fqfkp 0oQv5Q/nhXhM4DnMOHrh/HWHUF99ghjaxY8bPYvOKF8gqeb8LgxY1B9FQy5ZjHF7c+/XO/x VnYOaeosn6UqEKHrV6TZA==
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, 30 Oct 2013 15:36:50 -0000

* Stephane Bortzmeyer wrote:
>On Tue, Oct 29, 2013 at 09:10:08AM -0400,
> IAB Chair <iab-chair@iab.org> wrote 
> a message of 54 lines which said:
>
>> The Technical Plenary session is expected to be popular.  It will be
>> held on Wednesday, 6 Nov 2013 at 0900 PST,
>
>Why why why using a local timezone when announcing a live broadcast,
>which will be seen by many people anywhere in the world?
>
>Do note also that there are three different timezones in the world
>which are named PST. Not everyone lives in North America!
>
>IETF must use only UTC when announcing a worldwide event.

If it was given in a easily and umabiguously machine-readable form like 
`2013-11-06T05:00Z` we could make our computers recognise it and render
it in whatever form we prefer, including offering adding a note in the
calendar or whatever people find useful...
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From joelja@bogus.com  Wed Oct 30 09:54: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 15FE511E8164 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 09:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 lTmE19ByYasV for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 09:54:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id C538111E8169 for <ietf@ietf.org>; Wed, 30 Oct 2013 09:54:18 -0700 (PDT)
Received: from mb-aye.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r9UGsG5s016566 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 30 Oct 2013 16:54:17 GMT (envelope-from joelja@bogus.com)
Content-Type: multipart/signed; boundary="Apple-Mail=_19FC02DC-1016-459B-B28D-22EF63E1B84E"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: joel jaeggli <joelja@bogus.com>
In-Reply-To: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
Date: Wed, 30 Oct 2013 09:54:11 -0700
Message-Id: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 30 Oct 2013 16:54:18 +0000 (UTC)
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 16:54:39 -0000

--Apple-Mail=_19FC02DC-1016-459B-B28D-22EF63E1B84E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Oct 30, 2013, at 7:24 AM, Scott Brim <scott.brim@gmail.com> wrote:

> One aspect of the problem is calendar apps.  Some rather popular ones =
don't have a way to enter UTC, only UK time eg. BST, so you need some =
local time somewhere to enter the event in your calendar.

And the United Kingdom and Great Britian are not on BST all year. Ghana =
on the other hand is.

--Apple-Mail=_19FC02DC-1016-459B-B28D-22EF63E1B84E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJxObMACgkQ8AA1q7Z/VrIu+QCdHFAVyaS+WRnZgtnEfMFU7+S7
RjQAn0K7kDEERzC/6nMqzrGGvU4oLlZt
=BRVJ
-----END PGP SIGNATURE-----

--Apple-Mail=_19FC02DC-1016-459B-B28D-22EF63E1B84E--

From andrewf@plixer.com  Wed Oct 30 10:20:31 2013
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80C0421E8153 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:20: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 wpIrMcooFfoh for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:20:27 -0700 (PDT)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id D576D11E828A for <ietf@ietf.org>; Wed, 30 Oct 2013 10:18:44 -0700 (PDT)
Received: from [10.12.1.53] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 30 Oct 2013 13:18:42 -0400
Message-ID: <52713F72.9060706@plixer.com>
Date: Wed, 30 Oct 2013 13:18:42 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr>
In-Reply-To: <20131030081355.GA23990@nic.fr>
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, 30 Oct 2013 17:20:31 -0000

On 10/30/2013 04:13 AM, Stephane Bortzmeyer wrote:
> On Tue, Oct 29, 2013 at 09:10:08AM -0400,
>  IAB Chair <iab-chair@iab.org> wrote 
>  a message of 54 lines which said:
>
>> The Technical Plenary session is expected to be popular.  It will be
>> held on Wednesday, 6 Nov 2013 at 0900 PST,
> Why why why using a local timezone when announcing a live broadcast,
> which will be seen by many people anywhere in the world?
>
> Do note also that there are three different timezones in the world
> which are named PST. Not everyone lives in North America!
>
> IETF must use only UTC when announcing a worldwide event.
What, not Internet Time
(https://en.wikipedia.org/wiki/Swatch_Internet_Time)?
;-)

-Andrew

From sm@elandsys.com  Wed Oct 30 10:20:42 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 8FCE021E8135; Wed, 30 Oct 2013 10:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.479
X-Spam-Level: 
X-Spam-Status: No, score=-103.479 tagged_above=-999 required=5 tests=[AWL=-0.880, 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 5mdu+x0hSN4L; Wed, 30 Oct 2013 10:20: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 BE1E021E8144; Wed, 30 Oct 2013 10:19:25 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9UHIkA3029683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 10:19:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383153558; bh=A/n87butjfDIZlcNwmpbdRVoqtHbz8fPDDMr+9w3j7g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=f42ZCWZl821lUInpn08KzEQjz1CV8UyySIT9/PsFaO3SM5Up2a93L3PQqEc656n3b RXzDOiIJzPRC3rZweDh/bbkxTI17cqk8EksnIfkjqAFZh0y/kzCZAxCnZDjHRVo7Wo lRL0sEEupWjYIOrmkgfhyikkDUC9UFP5ojA6v+4w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383153558; i=@elandsys.com; bh=A/n87butjfDIZlcNwmpbdRVoqtHbz8fPDDMr+9w3j7g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=my0VGwurWxjiYI587ONFCZURDjsN4It3iZxegrvGnso76MmdI57gVlX/dNhCnEQp8 f6wXzeiYguI0Pbb/2MrKNexdBxBm2XfZ3kDRYJXYgH6RPDd1MTzFDo00ae88sGcmvT J+wfRaj5ZYnr7lmU9EVkLWNi99U9rqa8Qg1PBE38=
Message-Id: <6.2.5.6.2.20131030060359.0cb29068@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Oct 2013 08:49:52 -0700
To: Julian Reschke <julian.reschke@gmx.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
In-Reply-To: <526FC24D.7060704@gmx.de>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de> <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 30 Oct 2013 17:20:42 -0000

Hi Julian,
At 07:12 29-10-2013, Julian Reschke wrote:
>I consider that sentence to be useless - if I can't detect the type, 
>what else but "treating as arbitrary data" is left as an option anyway?

I'll comment below.

>I still don't get what the issue is :-)

My preference is not to generate material which create more work for 
you.  It's better not to pursue this one. :-)

>The subsequent text is:
>
>"In practice, resource owners do not always properly configure their 
>origin server to provide the correct Content-Type for a given 
>representation, with the result that some clients will examine a 
>payload's content and override the specified type. Clients that do 
>so risk drawing incorrect conclusions, which might expose additional 
>security risks (e.g., "privilege escalation"). Furthermore, it is 
>impossible to determine the sender's intent by examining the data 
>format: many data formats match multiple media types that differ 
>only in processing semantics. Implementers are encouraged to provide 
>a means of disabling such "content sniffing" when it is used."
>
>Do you think this is insufficient, or that it needs to move to a 
>different part of the spec?

The subsequent text is, to put it simply, about an operational issue 
and security considerations.  The recommendation in Section 3.1.1.5 
is to generate a Content-Type header field if the server knows the 
media type.  There are cases when the server does not know the media 
type.  In such cases the server sends the client 
"application/octet-stream".  There is where the user has to determine 
whether the server is operated by good person or a bad person (re. 
arbitrary data).  The user relies on the browser to perform some 
magic to determine that.  That magic does not always work well.

If it was my decision (and it is not) I would discuss about this 
under Security Considerations and mention that content sniffing can 
cause security problems.  Please note that there are different 
alternatives to tackle the issue.

Regards,
S. Moonesamy 


From chris.dearlove@baesystems.com  Wed Oct 30 10:24:47 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 BD0D111E8126 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=-0.168, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=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 Lu7L-dOD+64t for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:24:43 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 9D38811E81F0 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:24:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000";  d="scan'208,217";a="385227585"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 30 Oct 2013 17:24:38 +0000
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000"; d="scan'208,217";a="31416738"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 30 Oct 2013 17:24:38 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Wed, 30 Oct 2013 17:24:38 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Scott Brim <scott.brim@gmail.com>, ned+ietf <ned+ietf@mauve.mrochek.com>
Subject: RE: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Topic: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Index: AQHO1XlyRnqNofJSSkeNqjj/8b6c/JoNTKIAgAAxyeA=
Date: Wed, 30 Oct 2013 17:24:38 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438E@GLKXM0002V.GREENLNK.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr>	<01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>
In-Reply-To: <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.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: multipart/alternative; boundary="_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438EGLKXM0002VGREEN_"
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 17:24:47 -0000

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438EGLKXM0002VGREEN_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

GMT would be better than BST if you want UTC. (BST is GMT+1, used in summer=
.)

--
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 |  Fax: +44 1245 242124
chris.dearlove@baesystems.com<mailto: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

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Sco=
tt Brim
Sent: 30 October 2013 14:25
To: ned+ietf
Cc: Carsten Bormann; IETF Discuss
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streami=
ng of the IETF 88 Technical Plenary


*** WARNING ***
This message originates from outside our organisation, either from an exter=
nal partner or the internet.
Keep this in mind if you answer this message.
For information regarding Red Flags that you can look out for in emails you=
 receive, click here<http://intranet.ent.baesystems.com/howwework/security/=
spotlights/Documents/Red%20Flags.pdf>.
If you feel the email is suspicious, please follow this process<http://intr=
anet.ent.baesystems.com/howwework/security/spotlights/Documents/Dealing%20W=
ith%20Suspicious%20Emails.pdf>.
One aspect of the problem is calendar apps.  Some rather popular ones don't=
 have a way to enter UTC, only UK time eg. BST, so you need some local time=
 somewhere to enter the event in your calendar.
********************************************************************
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.
********************************************************************

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438EGLKXM0002VGREEN_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
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:0cm;
	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.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">GMT would be better than =
BST if you want UTC. (BST is GMT&#43;1, used in summer.)<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">--
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Christopher Dearlove<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: &#43;44 1245 242194&nbsp;|&nbsp; Fax: &#43;44 1245 242124<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><a href=3D"mailto:chris.dearlove@baesystems.com"><span style=3D"color:#1F=
497D;text-decoration:none">chris.dearlove@baesystems.com</span></a>
 | http://www.baesystems.com<br>
<br>
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US">BAE Systems (O=
perations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Scott Brim<br>
<b>Sent:</b> 30 October 2013 14:25<br>
<b>To:</b> ned&#43;ietf<br>
<b>Cc:</b> Carsten Bormann; IETF Discuss<br>
<b>Subject:</b> Re: IETF must use only UTC in its announcements (Was: Live =
Streaming of the IETF 88 Technical Plenary<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quo=
t;;color:black"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"text-align:center;backgrou=
nd:white"><b><span style=3D"font-size:15.0pt;font-family:&quot;Arial&quot;,=
&quot;sans-serif&quot;;color:#333972">*** WARNING ***<o:p></o:p></span></b>=
</p>
</div>
<div>
<p class=3D"MsoNormal" align=3D"center" style=3D"margin-bottom:12.0pt;text-=
align:center;background:white">
<em><span style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;san=
s-serif&quot;;color:#333972">This message originates from outside our organ=
isation, either from an external partner or the internet.</span></em><i><sp=
an style=3D"font-size:10.5pt;font-family:&quot;Arial&quot;,&quot;sans-serif=
&quot;;color:#333972"><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Ke=
ep this in mind if you answer this message.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">Fo=
r information regarding Red Flags that you can look out for in emails you r=
eceive, click
<a href=3D"http://intranet.ent.baesystems.com/howwework/security/spotlights=
/Documents/Red%20Flags.pdf">
here</a>.</span></em><br>
<em><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">If=
 you feel the email is suspicious, please follow
<a href=3D"http://intranet.ent.baesystems.com/howwework/security/spotlights=
/Documents/Dealing%20With%20Suspicious%20Emails.pdf">
this process</a>.</span></em></span></i><span style=3D"font-size:10.5pt;fon=
t-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#333972"><o:p></o:p=
></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">One aspect of the problem is calendar apps. &nbsp;So=
me rather popular ones don't have a way to enter UTC, only UK time eg. BST,=
 so you need some local time somewhere to enter the event in your calendar.=
<o:p></o:p></p>
</div>
</div>
</div>
<p>********************************************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************</p></b=
ody>
</html>

--_000_B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC0438EGLKXM0002VGREEN_--


From warren@kumari.net  Wed Oct 30 10:27:28 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 D665221E8137 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:27:28 -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 IiQP5FW-y0yo for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:27:23 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D8621E8133 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:27:22 -0700 (PDT)
Received: from [10.199.5.103] (209-82-80-116.dedicated.allstream.net [209.82.80.116]) by vimes.kumari.net (Postfix) with ESMTPSA id 9B7E81B40464; Wed, 30 Oct 2013 13:27:19 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_0885599B-B0CE-4690-9316-551BA7D90A66"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [IETF] Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
Date: Wed, 30 Oct 2013 10:27:15 -0700
Message-Id: <4F655F23-D68F-42DC-BF3B-5083EE93CB85@kumari.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr> <01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com> <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1510)
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 17:27:29 -0000

--Apple-Mail=_0885599B-B0CE-4690-9316-551BA7D90A66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 30, 2013, at 9:54 AM, joel jaeggli <joelja@bogus.com> wrote:

>=20
> On Oct 30, 2013, at 7:24 AM, Scott Brim <scott.brim@gmail.com> wrote:
>=20
>> One aspect of the problem is calendar apps.  Some rather popular ones =
don't have a way to enter UTC, only UK time eg. BST, so you need some =
local time somewhere to enter the event in your calendar.
>=20
> And the United Kingdom and Great Britian are not on BST all year. =
Ghana on the other hand is.

So the obvious solution to this issue is to hold all our meetings in =
Chana from now on.

There, I solved it for you=85

W


--=20
A. No
Q. Is it sensible to top-post?



--Apple-Mail=_0885599B-B0CE-4690-9316-551BA7D90A66
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iEYEARECAAYFAlJxQXYACgkQHSkNr4ucESezwgCeJJmp/BsMLWSC8u/T6Sbzl5V9
glgAoNOUxxrMDDa2MVzc3tNAqWBQ/V5k
=/tjn
-----END PGP SIGNATURE-----

--Apple-Mail=_0885599B-B0CE-4690-9316-551BA7D90A66--

From msweet@apple.com  Wed Oct 30 05:38:10 2013
Return-Path: <msweet@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C394621E80B7; Wed, 30 Oct 2013 05:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.053
X-Spam-Level: 
X-Spam-Status: No, score=-8.053 tagged_above=-999 required=5 tests=[AWL=2.546,  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 wrh4eFIaOnWl; Wed, 30 Oct 2013 05:38:04 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id D870F21E8064; Wed, 30 Oct 2013 05:37:57 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MVH00657F2ZZH02@mail-out.apple.com>; Wed, 30 Oct 2013 05:37:49 -0700 (PDT)
X-AuditID: 1180715a-b7f3c6d00000020e-ed-5270fd9a0d3b
Received: from [17.153.58.123] (Unknown_Domain [17.153.58.123]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id A2.27.00526.B9DF0725; Wed, 30 Oct 2013 05:37:49 -0700 (PDT)
Subject: Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
From: Michael Sweet <msweet@apple.com>
In-reply-to: <5270C9DE.3000104@gmx.de>
Date: Wed, 30 Oct 2013 08:37:46 -0400
Message-id: <A2D74D42-CF62-4D7E-8E4E-8221F80DCA1D@apple.com>
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com> <526FD3E8.9010904@gmx.de> <6.2.5.6.2.20131029232953.0ce8cc58@elandnews.com> <5270C9DE.3000104@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1812)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUiONOqWnfu34Igg4ev+CxWv1zBZnHnwC02 i8Mts5gsnm2cz2Kx+eEbVosj32ItXvXfZHVg99h68gebx703H5k8PnyM81iy5CeTx5fLn9k8 js7bzxrAFsVlk5Kak1mWWqRvl8CV0fe0i6XgHVvFpZ6ZzA2Mu1m7GDk5JARMJP6vv8QOYYtJ XLi3nq2LkYtDSKCXSeLAxKmMIAlhAQ+J44u7mUBsXgE9iSuPt7OA2MwCOhI7t95hA7HZBNQk fk/qAxvKCWRvm3WXGcRmEVCV+H+xgwlkKLPAdkaJ9z3f2SGatSWWLXzNDDHURmLLz5lMEJsX M0osv7cYbKqIgJbE7Xt7ga7gADpPVuLTYbMJjPyzkNwxC8kds5CMXcDIvIpRoCg1J7HSTC+x oCAnVS85P3cTIyiYGwqjdjA2LLc6xCjAwajEw9v5KD9IiDWxrLgy9xCjBAezkgjvqY8FQUK8 KYmVValF+fFFpTmpxYcYpTlYlMR55f2AUgLpiSWp2ampBalFMFkmDk6pBkZhdfN1hvu3ntf0 b9dR/zVVpO1ZqUv57IRWnTMGnyrP3pH8/9Nv31vxnqSIv7PO6vw5a21vIsWddn+dlWLP4ZTp U5vm+/5UZHyTUnfD+4Oiusi7Wi/+D3fO5pSuutaRFmY1c3Vh+3H/vcZHVSVC+yX3Xsvany1n /uWDcS+br53Gu4JTvEqNnkosxRmJhlrMRcWJAGu77hhiAgAA
X-Mailman-Approved-At: Wed, 30 Oct 2013 10:28:59 -0700
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, ietf@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org, draft-ietf-httpbis-p5-range.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: Wed, 30 Oct 2013 12:38:10 -0000

Add a forward reference to the boilerplate after the uppercase word?


On Oct 30, 2013, at 4:57 AM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-10-30 08:46, S Moonesamy wrote:
>> ...
>>> Such as?
>> 
>> What I mean is that what happens is undefined when both sides do not
>> follow the RFC 2119 "should".
> 
> The response is self-descriptive, so it's up to the client to properly process it.
> 
>>> It is supposed to be interpreted per RFC 2119.
>> 
>> It is better to use the uppercase words after the RFC 2119 boilerplate.
> 
> But then, we don't want the boilerplate to be in front of the Introduction. Any *concrete* suggestion how to address this?
> 
> Best regards, Julian
> 
> 
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From julian.reschke@greenbytes.de  Wed Oct 30 01:48:45 2013
Return-Path: <julian.reschke@greenbytes.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 9CFB911E8118; Wed, 30 Oct 2013 01:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.699
X-Spam-Level: 
X-Spam-Status: No, score=-5.699 tagged_above=-999 required=5 tests=[AWL=-2.450, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 PkF6Prix4aae; Wed, 30 Oct 2013 01:48:39 -0700 (PDT)
Received: from central.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by ietfa.amsl.com (Postfix) with ESMTP id 7643011E8296; Wed, 30 Oct 2013 01:48:22 -0700 (PDT)
Received: from [192.168.2.117] (unknown [93.217.127.91]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by central.greenbytes.de (Postfix) with ESMTPSA id 48C7610C06EE; Wed, 30 Oct 2013 09:48:20 +0100 (CET)
Message-ID: <5270C7D2.5010702@greenbytes.de>
Date: Wed, 30 Oct 2013 09:48:18 +0100
From: Julian Reschke <julian.reschke@greenbytes.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, apps-discuss@ietf.org,  draft-ietf-httpbis-p2-semantics.all@tools.ietf.org
Subject: Re: IANA issues, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E7154.2070005@greenbytes.de> <6.2.5.6.2.20131029214748.0b93d3b8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20131029214748.0b93d3b8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 30 Oct 2013 10:29:25 -0700
Cc: ietf-http-wg@w3.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, 30 Oct 2013 08:48:45 -0000

On 2013-10-30 06:24, S Moonesamy wrote:
> Hi Julian,
> At 07:14 28-10-2013, Julian Reschke wrote:
>> Yes -- this is not necessarily a problem. There are many things that
>> need to be defined for a new method, and not all of these fit into the
>> template.
>
> A DISCUSS about this can be easily addressed. :-)
>
> What is the intent behind the HTTP Method Registry (Section 8.1.3)?
> What information should that registry convey to the reader?  For
> example, is it a quick way for the reader to find out whether POST is
> cacheable (re. a choice that a browser vendor made some time back) or
> should the person read the relevant specification text to get accurate
> answer?

The template only contains a subset of the information, so in general, 
the reader will have to read the referenced RFC.

The entries in the template serve the purpose of shortcutting this 
lookup for considerations that can be answered with a simple "yes" or "no".

>> That's an assumption that is true for all "bare" Section references.
>
> The problem is that people copy and paste them blindly.  I suggest
> having information in the tables as the working group would like it to
> appear in the registry
>
>> The IANA Considerations are processed by the RFC Editor and IANA, and
>> they will make sure that the registry is properly populated. There's
>> no point in mentioning a still unknown RFC # here.
>
> It is up to the Responsible Area Director and the the document shepherd
> to make sure that the registry is properly populated.

And the authors during AUTH48. There is no problem here. We will make 
sure that the registry gets populated properly. Trust me.

> ...

Best regards, Julian

From avri@acm.org  Tue Oct 29 18:38:25 2013
Return-Path: <avri@acm.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 5B4F321E80C4 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 18:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.912
X-Spam-Level: 
X-Spam-Status: No, score=-109.912 tagged_above=-999 required=5 tests=[AWL=0.376, BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, 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 4tH3kuBR4vN8 for <ietf@ietfa.amsl.com>; Tue, 29 Oct 2013 18:38:20 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 97FF211E81B8 for <ietf@ietf.org>; Tue, 29 Oct 2013 18:38:14 -0700 (PDT)
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <avri@acm.org>) id 1VbKjO-000HiV-N7 for ietf@ietf.org; Wed, 30 Oct 2013 01:38:13 +0000
From: Avri Doria <avri@acm.org>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/signed; boundary="Apple-Mail=_CA1A5F79-6C0B-4464-B661-8ABF81F12F77"; protocol="application/pgp-signature"; micalg=pgp-sha1
Subject: Re: future of identifiers
Date: Tue, 29 Oct 2013 21:37:57 -0400
In-Reply-To: <932566FE-2D06-419D-B149-A81AA1CEC8BD@gmail.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <932566FE-2D06-419D-B149-A81AA1CEC8BD@gmail.com>
Message-Id: <A382A7DB-AE5F-43BF-8081-20ABFD2E4EE8@acm.org>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Wed, 30 Oct 2013 10:29:38 -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: Wed, 30 Oct 2013 01:38:25 -0000

--Apple-Mail=_CA1A5F79-6C0B-4464-B661-8ABF81F12F77
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 29 Oct 2013, at 10:53, Jorge Amodio wrote:

> IETF should take the lead in the development of innovative ways to =
identify resources,

Indeed this has been the case for a while

But IETF does create innovative way, e.g. the range of potentials in =
URIs that were never really exploited with other schema and authorities.

avri



--Apple-Mail=_CA1A5F79-6C0B-4464-B661-8ABF81F12F77
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBAgAGBQJScGL1AAoJEOo+L8tCe36HVoQH/0FBmuO05giSibCEOqdzpCLL
rfminSnOzz2OCZ+Rvfq3T1AFD4XBNkZFHEeNzDOiRbaEKSkDCWLpgj1fP/bEjxT9
PKNiTYluw2bcmVD9rNqqJDbyY787atVJiId0Yfi6iTz9Z51ds+XhkS2KvTZGyGUz
2GxhAyo8TcSlJRrY0FEziukWTvwT3JwQ7VjHDh1RWx/yUJ3GgdcUsAxSP+WhbGb0
dEi3TwRYJs3672q0ZaTpCMwG1PTWTBsMIP9KPMOd7eljxfjnwmEsUb+YAKhk4odT
AogqQNMDRfcPd25R9hDzM53arok8+RIJoLPYGhfYL5h/mIwZXGYuJ9rJitjvCDU=
=NJuj
-----END PGP SIGNATURE-----

--Apple-Mail=_CA1A5F79-6C0B-4464-B661-8ABF81F12F77--

From Chris.Dearlove@baesystems.com  Wed Oct 30 10:31:31 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 7859521E814F for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.445
X-Spam-Level: 
X-Spam-Status: No, score=-10.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 erGi83TA3dhH for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:31:27 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id DC11121E8162 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:30:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000"; d="scan'208";a="324438669"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 30 Oct 2013 17:30:34 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-IronPort-AV: E=Sophos;i="4.93,602,1378854000"; d="scan'208";a="33849025"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 30 Oct 2013 17:30:34 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.93]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0328.009; Wed, 30 Oct 2013 17:30:34 +0000
To: joel jaeggli <joelja@bogus.com>, Scott Brim <scott.brim@gmail.com>
Subject: RE: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Topic: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Index: AQHO1XlyRnqNofJSSkeNqjj/8b6c/JoNTKIAgAApu4CAAAkdMA==
Date: Wed, 30 Oct 2013 17:30:33 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DC043BD@GLKXM0002V.GREENLNK.net>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr>	<01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com> <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
In-Reply-To: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.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: ned+ietf <ned+ietf@mauve.mrochek.com>, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 17:31:31 -0000

UK and GB is a bit redundant (GB is part of - most of - the UK). Basically =
we run GMT (UTC+0) in winter and BST (UTC+1) in summer. The S is summer. [W=
e did once run an experiment to run BST - the S now standing for standard -=
 all year, but a long time ago, and not for long.]

[If - I don't know for sure either way - there's a subtle difference betwee=
n GMT and UTC, for meeting start times, it's irrelevant.)

-- =

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 joe=
l jaeggli
Sent: 30 October 2013 16:54
To: Scott Brim
Cc: ned+ietf; Carsten Bormann; IETF Discuss
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streami=
ng of the IETF 88 Technical Plenary


On Oct 30, 2013, at 7:24 AM, Scott Brim <scott.brim@gmail.com> wrote:

> One aspect of the problem is calendar apps.  Some rather popular ones don=
't have a way to enter UTC, only UK time eg. BST, so you need some local ti=
me somewhere to enter the event in your calendar.

And the United Kingdom and Great Britian are not on BST all year. Ghana on =
the other hand is.
********************************************************************
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=0008e0cf97=johnl@iecc.com  Wed Oct 30 10:50:39 2013
Return-Path: <prvs=0008e0cf97=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 748F021E80F3 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  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 0NpmA5fX4jqO for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 10:50:35 -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 3B68D11E8126 for <ietf@ietf.org>; Wed, 30 Oct 2013 10:50:28 -0700 (PDT)
Received: (qmail 94747 invoked from network); 30 Oct 2013 17:50:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 30 Oct 2013 17:50:26 -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=527146e2.xn--30v786c.k1310; i=johnl@user.iecc.com; bh=H7moMek05VpwKFZGUa0ANPmi93Gt5vBgAnuRp+CUCDk=; b=LoLeSn9vD3S9ktIx9toTbq+JWFWq/DrtgChiGsR4ltfrLKux24BtvINEaLZz4oSeNQIaktlLTRc1ElYnLxdHu/JrZ06lbtdVzE5W62zmuT8udJ1SE9mpJwvIMEQFTON88oBRa747sIrZ3tWBtebMsFdLvFU3phcacCEdh2lVtxlzLAkEs3gaG5qGZZBmhU/rFFvxeY6I08T75nI9jtlEegCiyke5NYoj+8TwjqbPsQQ3n/0yZDC1g9rZpATQDBmg
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=527146e2.xn--30v786c.k1310; olt=johnl@user.iecc.com; bh=H7moMek05VpwKFZGUa0ANPmi93Gt5vBgAnuRp+CUCDk=; b=wsXgEZ8lDg2xl5KMxN/NXDRdXHGcGp51A9tfe930n91hGqUeK74d26YNoBhysGP6SRE+jThnDXEnFzOrs3M3rbvkJujMKWcdLKXmu2QVHWeR5GPP8C/psdNeKPuqR7HLQxmSC2BnQbVVVbdcQRmiQprHlE+ifc73mpTRHsNN5U3bQ8ZHgHVObR21ojBBayV86+mol9cQwa5zCiINpqeXs+B7B/k/Ymyd1mVNqdhvsvdCbckmDctE16RFLewmiR/m
Date: 30 Oct 2013 17:50:04 -0000
Message-ID: <20131030175004.44640.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
In-Reply-To: <20131030083611.GA27804@nic.fr>
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: Wed, 30 Oct 2013 17:50:39 -0000

>My experience with international organizations is that, when you
>indicate the time in two zones, there is often a discrepancy. With
>only one zone, there is no doubt about the real value.

I've basically given up asking people what time zone their schedule is
in, because most people have no idea, and don't understand that time
offsets vary from place to place and from one time of the year to
another, so the correct zone matters.  

In San Francisco in July, they'll say PST.  Do you mean PDT?  Yes,
PST.  Or this call will be at 10:00 in New York, 11:00 in San Juan.
where the time is an hour ahead.  Uh, it's May and there's no daylight
time in Puerto Rico so the times are the same.  What?  Huh?

This problem is not helped by a widely used alleged calendar
application sold by a vendor located about 220 km south of Vancouver
that doesn't even try to get the time zones right.

The least broken approach I've found is to ask what place the time is.
If they say Vancouver, I can figure it out.

R's,
John




From vinayakh@gmail.com  Wed Oct 30 12:21:07 2013
Return-Path: <vinayakh@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 DDAF721E8088 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 12:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level: 
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=0.330,  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 ZXLMtQTyf56u for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 12:21:07 -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 D303021E8091 for <ietf@ietf.org>; Wed, 30 Oct 2013 12:21:06 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ld10so1403868pab.38 for <ietf@ietf.org>; Wed, 30 Oct 2013 12:21: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=3JqqiX+TjGtTblskHZDV+eDwMAWjEgp6LNd+MQyCeTY=; b=N9+iazdUSaaFz41u0avhnULj64jp01Hb9nmY0jkCHfoce7L/nawHXV6mLSBwFNZboh NmvZMU1zpevAH9u6B297OvJALWwg9iEYrs0W4yyOId8Br2nrfaNbN3tHllkFMXRZ42gC NB2nTJqGr2MzW5HiBS72Pd7v5WGbFKvqpfElenOG0reOfiHBcysRuLLIxtsU6XgeNJld jwq40pIO11pD56fHbWThaOMlt6N2tPTKLkZ7SxvhRk/idycndfLigKixnuVPDchyMszp rqXAx3ShKJfhKqHd1OMrncCwkCWsKBV/3rCIEQlLgX/89GQfIPulF+q2HIKOB496/OBF Ibag==
MIME-Version: 1.0
X-Received: by 10.66.141.73 with SMTP id rm9mr4748582pab.167.1383160866574; Wed, 30 Oct 2013 12:21:06 -0700 (PDT)
Received: by 10.66.26.112 with HTTP; Wed, 30 Oct 2013 12:21:06 -0700 (PDT)
In-Reply-To: <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <EMEW3|9e1becdb40bfbb97deb2f04c4b088de9p9YE8m03tjc|ecs.soton.ac.uk|3291AEDC-655D-4AD8-A60B-8D31A5C65DEA@ecs.soton.ac.uk> <CAL02cgRyC=DdwCHgmnz1oEL+5CbUehi3jbcfGfjgqO_Nkx4j1A@mail.gmail.com>
Date: Thu, 31 Oct 2013 00:51:06 +0530
Message-ID: <CAKe6YvPcYexGMFNP=LxoxKrFkynHQ7C8XsbBJE=afRTQoK1Zuw@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Vinayak Hegde <vinayakh@gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=001a11c3946c1e9e4604e9fa3c5f
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Carsten Bormann <cabo@tzi.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 19:21:08 -0000

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

On Wed, Oct 30, 2013 at 7:48 PM, Richard Barnes <rlb@ipv.sx> wrote:

> I hope everyone in the IETF is familiar with sites such as:
> <http://www.timeanddate.com/>
> <http://www.worldtimebuddy.com/>
>

All times for events should be in UTC or atleast mention UTC time in
addition to local time (especially for events such as plenaries which have
a larger number of remote participants). On one hand IETF wants more remote
participants. On the other hand, I see resistance to do some
(UI/Notification fixes) from several volunteers of IETF.

I hope you all are aware of rot-13. please use www.rot13.com to decipher
the following.
<sarcasm>
 V ubcr lbh ner njner bs ebg-13
</sarcasm>

-- Vinayak

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Oct 30, 2013 at 7:48 PM, Richard Barnes <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rlb@ipv.sx" target=3D"_blank">rlb@ipv.sx</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr"><div>I hope everyone in the IETF is familiar with sites su=
ch as:<br></div>&lt;<a href=3D"http://www.timeanddate.com/" target=3D"_blan=
k">http://www.timeanddate.com/</a>&gt;<br>&lt;<a href=3D"http://www.worldti=
mebuddy.com/" target=3D"_blank">http://www.worldtimebuddy.com/</a>&gt;<br>
</div></blockquote><div><br></div><div>All times for events should be in UT=
C or atleast mention UTC time in addition to local time (especially for eve=
nts such as plenaries which have a larger number of remote participants). O=
n one hand IETF wants more remote participants. On the other hand, I see re=
sistance to do some (UI/Notification fixes) from several volunteers of IETF=
.<br>
<br></div><div>I hope you all are aware of rot-13. please use <a href=3D"ht=
tp://www.rot13.com">www.rot13.com</a> to decipher the following.<br></div><=
div>&lt;sarcasm&gt;<br></div><div>=A0V ubcr lbh ner njner bs ebg-13<br></di=
v>
<div>&lt;/sarcasm&gt;<br><br></div><div>-- Vinayak<br></div></div></div></d=
iv>

--001a11c3946c1e9e4604e9fa3c5f--

From vinayakh@gmail.com  Wed Oct 30 12:30:13 2013
Return-Path: <vinayakh@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 19B6711E8220; Wed, 30 Oct 2013 12:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  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 bZe+pUvb7-Vg; Wed, 30 Oct 2013 12:30:12 -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 E856411E818E; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id jt11so1838077pbb.15 for <multiple recipients>; Wed, 30 Oct 2013 12:30:11 -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=0CsC63aSYj53+siI2L9UQwkcHT/LsiJfV1NPriqAKN0=; b=JV4Tgug4LOd33Em0qnBjwH0Eaa3CAUZnIxB/LCQOd79EUGqyHacrJmuEkdoZ5iDy7U QuLW9GYZ5TgzvlmvPI9Wao3QnVsKjOAJPsSaeYlRAY3Ix0LkD9Q2hbaK4kIN2wqxufai g8Iy/jtYqf1NekptX+O2PbVOH5uMqjOje+o+l/UTLF7EJJLb/8k3OwgmqiXprGUoCAOA auBvT/EurleMbi//SKwEqx0srhvR7nzEN5k4gqF6sebbDJvnHFTtqqn24pXJnoIDFdHL etUTrkwfbaUSHrFumAg+/3kL6H2lmw9qHMrpr+Gu/oZJjEcB+/yrhrhHyBCec4jm2SBu xmew==
MIME-Version: 1.0
X-Received: by 10.66.156.199 with SMTP id wg7mr4190pab.81.1383161411657; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
Received: by 10.66.26.112 with HTTP; Wed, 30 Oct 2013 12:30:11 -0700 (PDT)
In-Reply-To: <33E29264-2B13-40F0-BE86-7A840CEEF5AA@iab.org>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <33E29264-2B13-40F0-BE86-7A840CEEF5AA@iab.org>
Date: Thu, 31 Oct 2013 01:00:11 +0530
Message-ID: <CAKe6YvO=-kUVdumR3BmB_CGBcc+7_OFDhC5XrOebJ8SxzQvQeg@mail.gmail.com>
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streaming of the IETF 88 Technical Plenary
From: Vinayak Hegde <vinayakh@gmail.com>
To: IAB Chair <iab-chair@iab.org>, "diversity@ietf.org" <diversity@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b86c7489bf97704e9fa5c2e
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, 30 Oct 2013 19:30:13 -0000

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

On Wed, Oct 30, 2013 at 7:49 PM, IAB Chair <iab-chair@iab.org> wrote:

> Stephane:
>
> I think that the use of the local timezone make it easy for people to look
> it up on the agenda.  I do agree that inclusion of UTC as well would have
> been very helpful.  I'll try to remember to do that in the future.
>
> Russ
>


Why is it so hard to even mention the offset of the local time from UTC if
not anything else on the Agenda itself ? Everyone is aware of the offset
from the timezone they are in but may not be aware of the local timezone
offsets during the time of the year (think day-light savings) and the place
(several countries have different timezones so different cities within same
country can have different times).

I think the problem here is of the mindset within the IETF which looks at
IETF meetings as local physical meetings rather than a place of
congregation of people (whether physical or remote) at certain point in
time. If IETF really means to encourage wider participation (both in number
and diversity), then they need to make small changes such as these to
accommodate remote participants more. The change should start right from
the very top if this were to work.

-- Vinayak

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Oct 30, 2013 at 7:49 PM, IAB Chair <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:iab-chair@iab.org" target=3D"_blank">iab-chair@iab.org</a>&gt;</span> w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Stephane:<br>
<br>
I think that the use of the local timezone make it easy for people to look =
it up on the agenda. =A0I do agree that inclusion of UTC as well would have=
 been very helpful. =A0I&#39;ll try to remember to do that in the future.<b=
r>

<br>
Russ<br></blockquote><div>=A0</div><div><br></div><div>Why is it so hard to=
 even mention the offset of the local time from UTC if not anything else on=
 the Agenda itself ? Everyone is aware of the offset from the timezone they=
 are in but may not be aware of the local timezone offsets during the time =
of the year (think day-light savings) and the place (several countries have=
 different timezones so different cities within same country can have diffe=
rent times).<br>
<br></div><div>I think the problem here is of the mindset within the IETF w=
hich looks at IETF meetings as local physical meetings rather than a place =
of congregation of people (whether physical or remote) at certain point in =
time. If IETF really means to encourage wider participation (both in number=
 and diversity), then they need to make small changes such as these to acco=
mmodate remote participants more. The change should start right from the ve=
ry top if this were to work.<br>
<br></div><div>-- Vinayak<br></div></div></div></div>

--047d7b86c7489bf97704e9fa5c2e--

From tglassey@earthlink.net  Wed Oct 30 14:27:20 2013
Return-Path: <tglassey@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 C890711E819F for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 14:27:20 -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 kHW-yf9LMTuW for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 14:27:15 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id DFD1B11E8274 for <ietf@ietf.org>; Wed, 30 Oct 2013 14:27:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kb8O2QkMMYdRRUI17UoWzcr29/sTINFQ3LIRAx5btRa1Qm0vrJ1q0ZSOdqf9SDUd; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=localhost.localdomain) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1VbdI2-0003yg-Tl for ietf@ietf.org; Wed, 30 Oct 2013 17:26:59 -0400
Message-ID: <527179A0.3080600@earthlink.net>
Date: Wed, 30 Oct 2013 14:26:56 -0700
From: TSG - personal <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130917 Thunderbird/17.0.9
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com> <01OZZW7T12OY00004R@mauve.mrochek.com> <74F37EA0-42CD-4805-80CB-1C060F79FEB7@gmail.com>
In-Reply-To: <74F37EA0-42CD-4805-80CB-1C060F79FEB7@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79746f4282b21155170f80dc69f12cf43e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Oct 2013 21:27:20 -0000

On 10/29/2013 03:38 PM, Douglas Otis wrote:

The real issue is how after the fact you would disprove digital 
tampering with the participation process... i.e. that censorship filters 
were not installed into the mailing process to

1)    Separate any voice setup to be isolated
2)     Send that person mail to make it look like they are still 
participating...
3)    Edit their commentary back in to the history file to complete the 
covering up of the fraud.

You would have to have multiple addresses for a number of lists right?

Todd


> On Oct 25, 2013, at 9:53 AM, ned+ietf@mauve.mrochek.com wrote:
>
>>> the chilling effect of vigilateism is far worse than spam or trolls.
>>> we've been dealing with the latter for decades, and there is little
>>> actual real harm if any.  the chilling effect of vigilanteism causes
>>> actual harm and reduces the rich diversity of opinion, culture, and
>>> viewpoint.
>> I could not agree more. By condoning such measures people are damaging the
>> diversity they are supposedly trying to support.
> Agreed.  Not all interests will be met but each should have a voice within an open and transparent process.  It would be a pity to allow censorship or political propriety to place this process behind hidden barriers.
>
> Regards,
> Douglas Otis


From sm@elandsys.com  Wed Oct 30 14:51:06 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 7AC2211E81C9; Wed, 30 Oct 2013 14:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=-0.924, 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 LsVQ4zuxrlU9; Wed, 30 Oct 2013 14:51: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 80E9811E80F1; Wed, 30 Oct 2013 14:51:03 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9ULolug011263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 14:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383169860; bh=SzsIHzfjl5wKnCjtGjoohKveXMH2e1ou1Azm/qSSB40=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=L4jI5cklLhqE05M4kqp+JPjpXODyRFZqhbdRey+cvhDqqcM1Xc9LUQ0Vv7XPX7mKe bMIF8m2hTF63LFiT7X/USI09Bvjzv7dneEiyiJwL82k+v9H7SZTu/ugqKuejYRgr9f cKzkwptPENZ1eG+Jf/j/3iixZK1cbF141AlPU0ck=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383169860; i=@elandsys.com; bh=SzsIHzfjl5wKnCjtGjoohKveXMH2e1ou1Azm/qSSB40=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HX91AAsE9aN41mouJYUU8/cLF4P8ZiXfNIQFhSgOlS2phVFZc+la5pvMiN5EtyasQ lLbgFinXHPXAIHAPruE6skR4Xp1bi3x/++oGMSavn0YpjExZqqvdpFB2LQx6ix04Bh 1DHXHLRI7QhKJBgvfCvRikdMsrFGXmz/UhfoQXxc=
Message-Id: <6.2.5.6.2.20131030141311.0cf57b20@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Oct 2013 14:49:59 -0700
To: Julian Reschke <julian.reschke@gmx.de>, apps-discuss@ietf.org, draft-ietf-httpbis-p5-range.all@tools.ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: #506, was: APPSDIR review of draft-ietf-httpbis-p5-range-24
In-Reply-To: <5270C9DE.3000104@gmx.de>
References: <6.2.5.6.2.20131028101123.0e37a698@elandnews.com> <526FD3E8.9010904@gmx.de> <6.2.5.6.2.20131029232953.0ce8cc58@elandnews.com> <5270C9DE.3000104@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-http-wg@w3.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, 30 Oct 2013 21:51:06 -0000

Hi Julian,
At 01:57 30-10-2013, Julian Reschke wrote:
>But then, we don't want the boilerplate to be in front of the 
>Introduction. Any *concrete* suggestion how to address this?

The sentence about "OPTIONAL feature" can be added to Section 3 of 
draft-ietf-httpbis-p5-range-24.

I would consider adding some text to the paragraph in Section 2.5 of 
draft-ietf-httpbis-p1-messaging-24 about "considered 
conformant".  This is to make it clear which features are part of basic HTTP.

Regards,
S. Moonesamy 


From Ted.Lemon@nominum.com  Wed Oct 30 15:11:56 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 6223D11E81E9 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 15:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, 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 Gq-AsrSMEwXq for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 15:11:49 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC3F11E81DE for <ietf@ietf.org>; Wed, 30 Oct 2013 15:11:49 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUnGEJWVdUoiwvLjMVhyX2tC6lv7AUTLQ@postini.com; Wed, 30 Oct 2013 15:11:49 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 4D7AF1B82A4 for <ietf@ietf.org>; Wed, 30 Oct 2013 15:11:49 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-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 33D0A190043; Wed, 30 Oct 2013 15:11:49 -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.03.0158.001; Wed, 30 Oct 2013 15:11:49 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: TSG - personal <tglassey@earthlink.net>
Subject: Re: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Topic: Sergeant at arms: please deal with mars.techno.cat@gmail.com
Thread-Index: AQHOzRN5MiZjjrFfeEyJF39B90YYOZn/6ykAgAARIoCAAQxLgIAAaYsAgAAVogCAAAJ3gIAABrYAgAAJKYCAABMiAIAAB2UAgAEQJACAABxsgIAABx4AgALFJjmABxzKAIABfngAgAAMiQA=
Date: Wed, 30 Oct 2013 22:11:49 +0000
Message-ID: <74AFA440-524B-4E2C-A7B7-BE23B9814173@nominum.com>
References: <5262FB95.8080500@gmail.com> <CAK41CSRKhD9W5WWm3xBJeb4U8Q6TbfG1EHnY_0BN7fC1QvO=iA@mail.gmail.com> <52657B0B.3080701@gmail.com> <m21u3d5zvo.wl%randy@psg.com> <5266B4A4.9020301@dcrocker.net> <5266C6CA.30900@gmail.com> <0B5A250AE70FD6B21DD3CF4C@JcK-HP8200.jck.com> <5266CE7C.2020503@gmail.com> <61EE8145-2184-44C1-8163-424F97F8286C@piuha.net> <m261sp3u13.wl%randy@psg.com> <7F387505-3EBD-4DEC-8E9C-AB6D500F5396@nominum.com> <CAPv4CP-UPr5S8Z5PqF1bX0FWLOCZvrgjFog6-O-R8tN+ygVTCA@mail.gmail.com> <CF9872C2-828D-4C56-8A8D-836FF1BCDAA9@nominum.com> <m28uxkyovt.wl%randy@psg.com> <01OZZW7T12OY00004R@mauve.mrochek.com> <74F37EA0-42CD-4805-80CB-1C060F79FEB7@gmail.com> <527179A0.3080600@earthlink.net>
In-Reply-To: <527179A0.3080600@earthlink.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="Windows-1252"
Content-ID: <76C71496081E664BB4829F4D9E48CFAA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 30 Oct 2013 22:11:56 -0000

On Oct 30, 2013, at 5:26 PM, TSG - personal <tglassey@earthlink.net> wrote:
> 1)    Separate any voice setup to be isolated
> 2)     Send that person mail to make it look like they are still particip=
ating...
> 3)    Edit their commentary back in to the history file to complete the c=
overing up of the fraud.

In point of fact, I get the strong impression that plenty of participants i=
n IETF mailing lists block email from other specific participants, which pr=
esents a small version of the same effect.   However, in practice the tampe=
ring you are theorizing about would actually be trivial to detect=97just se=
t up two email addresses with no obvious connection between them, and subsc=
ribe them both to the same mailing list.   Send mail from one address; if t=
he other address doesn't receive it, cry foul.

Let's not be so paranoid that we all wind up crawling into our tortoise she=
lls.


From abdussalambaryun@gmail.com  Wed Oct 30 17:49: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 7E11F11E81D1 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 17:49:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 YNKWUXgw+g1d for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 17:49:29 -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 7772E11E8285 for <ietf@ietf.org>; Wed, 30 Oct 2013 17:49:29 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id kq14so1728915pab.7 for <ietf@ietf.org>; Wed, 30 Oct 2013 17:49: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=PhKssxcvVfExFsBmdUZoozMDaCqkDY1LcC5IIPEsKEI=; b=zfWn168XAKEed3of0ot0/YYr1ODDSo4kRVo9Mf33Ucxr7xslJENjrqk3o+LEDJ6RLw gGK8wOQD/rbQVkOZVhdm+f8dYv/n7xSdCd3Fbi+pD6bM4qxkya34C0+5I8ic3/gSLHAr xUITybrnfsEsTKvXE21FiNs/RyIx34xyU+Zmx2LWMrWcF4mWlr3pQ6LsEmznwXoSE6/Q 7ECa/jsdQLy52FQsfN+H1Gm3Pq1gLHp0MmT+HHW2gs/W9ZLPGuotgrxsnmGVN8iA/i7v Zd54VcWzim3rb8xZDloervodDoktAEMnuAQ9HmhSWbSHWw1U3D4U7QLluxI+5dXZjRWs 4whQ==
MIME-Version: 1.0
X-Received: by 10.67.3.3 with SMTP id bs3mr1243243pad.46.1383180566772; Wed, 30 Oct 2013 17:49:26 -0700 (PDT)
Received: by 10.69.8.5 with HTTP; Wed, 30 Oct 2013 17:49:26 -0700 (PDT)
In-Reply-To: <52696048.1050701@dcrocker.net>
References: <5269209F.3060706@dcrocker.net> <CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24049EA32C49@MX15A.corp.emc.com> <52696048.1050701@dcrocker.net>
Date: Thu, 31 Oct 2013 01:49:26 +0100
Message-ID: <CADnDZ8-KtfLSfPupzY2rDCbFpAdQ6es-birt2z3gtdoHG+iRCA@mail.gmail.com>
Subject: Review of: Characterization of Proposed Standards
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: multipart/alternative; boundary=047d7b15afd357c37204e9fed284
Cc: "draft-kolkman-proposed-standards-clarified.all@tools.ietf.org" <draft-kolkman-proposed-standards-clarified.all@tools.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: Thu, 31 Oct 2013 00:49:31 -0000

--047d7b15afd357c37204e9fed284
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Kathleen

As my understanding, this procedure update document under review allows
comparing SDO work within our IETF work, so as IETF is already open to
allow all participation of businesses and SDOs into IETF, this issue of
comparing discussions while our standards draft developing will create
longer discussions and even disagreements between businesses/companies.

Any cross-organisation standard work issues with external bodies we need an
agreement policy like our one with ITU. I don't think it is good to discuss
comparisons in IETF because the IETF is open (other May not be), and we
should focus on the development of our standards following IETF aim. The
document does not mention any agreement requirement between IETF and
other SDOs, if we want to allow such process.

IMO the IETF has special aim and different standard vision than other SDOs
, so IETF standards need to be interoperable, competitive, and not
dependant. I suggest to add a requirement of existing agreement policy when
doing work that involve other SDO.

AB

On Thursday, October 24, 2013, Moriarty, Kathleen wrote:

> I don=92t see how that is possible.  Different SDOs have different focus
> areas with clear interdependencies between the work.
>
> I suggest
Interoperable but not interdependent

> We don=92t need to try to replicate the work happening elsewhere, but rat=
her
> should continue to play nice with other SDOs.
>
> We can do better work than others so why replicate, but it is ok to build
on others sub-work.

> It would be really hard to get all of the various experts needed attend
> multiple forums because one SDO didn=92t want to reference the work they =
did
> in another SDO.  ****
>
> Referencing is always good but following without progress is not good .

> ** **
>
> Regards,****
>
> Kathleen****
>
> ** **
>
> *From:* ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] *On Behalf
> Of *Abdussalam Baryun
> *Sent:* Thursday, October 24, 2013 12:04 PM
> *To:* ietf
> *Cc:* draft-kolkman-proposed-standards-clarified.all@tools.ietf.org
> *Subject:* Review of: Characterization of Proposed Standards****
>
> ** **
>
> I don't agree with comparing our standards with other SDO standards withi=
n
> our work, or even making our work process depend on other SDO products.
> IETF RFC should try its best to have normative references that are RFCs n=
ot
> dependent/government oriented. We may end up with a new name for our IETF=
,
> as dependent IETF (DIETF).****
>
> ** **
>
> AB****
>

--047d7b15afd357c37204e9fed284
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Kathleen</div><div><br></div>As my understanding,=A0this procedure =
update=A0document under review allows comparing SDO work within=A0our IETF =
work, so as IETF is already open=A0to allow all participation=A0of business=
es and SDOs into=A0IETF,=A0this issue of comparing discussions=A0while our =
standards=A0<span></span>draft=A0developing will create longer discussions =
and even disagreements between businesses/companies.=A0<div>

<br></div><div>Any cross-organisation standard work=A0issues with external =
bodies we need an agreement policy like our one with ITU. I don&#39;t think=
 it is good to discuss comparisons in IETF because the IETF is open (other =
May not be), and=A0we should focus=A0on the development of our standards fo=
llowing IETF aim. The document does not mention any agreement requirement=
=A0between IETF and other=A0SDOs, if we want to allow such process.<div>

<br><div><div>
IMO the IETF has special aim and different standard vision=A0than other SDO=
s ,=A0so IETF standards=A0need to be interoperable, competitive, and not de=
pendant. I suggest to add a requirement of existing agreement policy when d=
oing work that involve other SDO.<span></span><div>

<div><br></div><div>AB<br><br>On Thursday, October 24, 2013, Moriarty, Kath=
leen  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">I don=92t see=
 how that is possible.=A0 Different SDOs have different focus areas with cl=
ear interdependencies between the work.=A0=A0</span></p>
<p class=3D"MsoNormal"></p></div></div></blockquote><div>I suggest=A0=A0</d=
iv><div>Interoperable but not interdependent=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d">We don=92t need to try to replicate the work=
 happening elsewhere, but rather should continue to play nice with other SD=
Os. =A0</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"></span></p></div></div></=
blockquote><div>We can do better work than others so why replicate, but it =
is ok to build on others sub-work.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"p=
urple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">It would be r=
eally hard to get all of the various experts needed attend multiple forums =
because one SDO didn=92t want to reference the work they did in another SDO=
.=A0 <u></u><u></u></span></p>
<p class=3D"MsoNormal"></p></div></div></blockquote><div>Referencing is alw=
ays good but following without progress is not good .=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,<u></u><u></u>=
</span></p>


<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Kathleen<u></u><u></u></s=
pan></p><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u>=
</span></p>


<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;"> <a>ietf-=
bounces@ietf.org</a> [mailto:<a>ietf-bounces@ietf.org</a>] <b>On Behalf Of =
</b>Abdussalam Baryun<br>


<b>Sent:</b> Thursday, October 24, 2013 12:04 PM<br><b>To:</b> ietf<br><b>C=
c:</b> <a>draft-kolkman-proposed-standards-clarified.all@tools.ietf.org</a>=
<br>
<b>Subject:</b> Review of: Characterization of Proposed Standards<u></u><u>=
</u></span></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p><p class=3D"MsoN=
ormal">I don&#39;t agree with comparing our standards with other SDO standa=
rds within our work,=A0or even making our work=A0process depend on other SD=
O products. IETF RFC should try its best to have normative references that =
are RFCs not dependent/government oriented. We may end up with a new name f=
or our IETF, as dependent IETF (DIETF).<u></u><u></u></p>


<div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div><div><p class=3D"Mso=
Normal">AB<u></u><u></u></p></div></div></div></blockquote></div></div></di=
v>
</div></div></div>

--047d7b15afd357c37204e9fed284--

From mnot@mnot.net  Wed Oct 30 20:31:47 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 D764021E80BB; Wed, 30 Oct 2013 20:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.694
X-Spam-Level: 
X-Spam-Status: No, score=-104.694 tagged_above=-999 required=5 tests=[AWL=-2.095, 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 4HrO5PMwto2O; Wed, 30 Oct 2013 20:31:41 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 65E0921F9DE9; Wed, 30 Oct 2013 20:31:41 -0700 (PDT)
Received: from [192.168.1.64] (unknown [118.209.167.85]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 39FA922E2CA; Wed, 30 Oct 2013 23:31:31 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: content inspection in absence of media type, was: [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6.2.5.6.2.20131030060359.0cb29068@elandnews.com>
Date: Thu, 31 Oct 2013 14:31:28 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6CADE9A-2472-44B5-96E4-18B571D48CD6@mnot.net>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de> <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de> <6.2.5.6.2.20131030060359.0cb29068@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1510)
Cc: Julian Reschke <julian.reschke@gmx.de>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, ietf-http-wg@w3.org, apps-discuss@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, 31 Oct 2013 03:31:47 -0000

SM,

Consensus around this text was particularly hard-won; unless there is a =
very good reason to make a change, I'd rather not risk falling into that =
rat-hole again.

Regards,


On 31/10/2013, at 2:49 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Julian,
> At 07:12 29-10-2013, Julian Reschke wrote:
>> I consider that sentence to be useless - if I can't detect the type, =
what else but "treating as arbitrary data" is left as an option anyway?
>=20
> I'll comment below.
>=20
>> I still don't get what the issue is :-)
>=20
> My preference is not to generate material which create more work for =
you.  It's better not to pursue this one. :-)
>=20
>> The subsequent text is:
>>=20
>> "In practice, resource owners do not always properly configure their =
origin server to provide the correct Content-Type for a given =
representation, with the result that some clients will examine a =
payload's content and override the specified type. Clients that do so =
risk drawing incorrect conclusions, which might expose additional =
security risks (e.g., "privilege escalation"). Furthermore, it is =
impossible to determine the sender's intent by examining the data =
format: many data formats match multiple media types that differ only in =
processing semantics. Implementers are encouraged to provide a means of =
disabling such "content sniffing" when it is used."
>>=20
>> Do you think this is insufficient, or that it needs to move to a =
different part of the spec?
>=20
> The subsequent text is, to put it simply, about an operational issue =
and security considerations.  The recommendation in Section 3.1.1.5 is =
to generate a Content-Type header field if the server knows the media =
type.  There are cases when the server does not know the media type.  In =
such cases the server sends the client "application/octet-stream".  =
There is where the user has to determine whether the server is operated =
by good person or a bad person (re. arbitrary data).  The user relies on =
the browser to perform some magic to determine that.  That magic does =
not always work well.
>=20
> If it was my decision (and it is not) I would discuss about this under =
Security Considerations and mention that content sniffing can cause =
security problems.  Please note that there are different alternatives to =
tackle the issue.
>=20
> Regards,
> S. Moonesamy=20
>=20

--
Mark Nottingham   http://www.mnot.net/




From duerst@it.aoyama.ac.jp  Wed Oct 30 21:33:10 2013
Return-Path: <duerst@it.aoyama.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 563A011E830C; Wed, 30 Oct 2013 21:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.947
X-Spam-Level: 
X-Spam-Status: No, score=-103.947 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 9UVBrdxCK4cK; Wed, 30 Oct 2013 21:33:03 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 09B8511E830E; Wed, 30 Oct 2013 21:33:02 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r9V4WQAk032007; Thu, 31 Oct 2013 13:32:27 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 0263_5a55_718ee91e_41e5_11e3_866d_001e6722eec2; Thu, 31 Oct 2013 13:32:25 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 5B5F8BF4BB; Thu, 31 Oct 2013 13:32:25 +0900 (JST)
Message-ID: <5271DD41.2030107@it.aoyama.ac.jp>
Date: Thu, 31 Oct 2013 13:32:01 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [apps-discuss] content inspection in absence of media type, was: APPSDIR review of draft-ietf-httpbis-p2-semantics-24
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com>	<526E8B9E.8030006@gmx.de>	<6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de> <5270C896.6080204@it.aoyama.ac.jp> <5270D5C9.4090004@gmx.de>
In-Reply-To: <5270D5C9.4090004@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, apps-discuss@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Oct 2013 04:33:10 -0000

On 2013/10/30 18:47, Julian Reschke wrote:
> On 2013-10-30 09:51, "Martin J. D=C3=BCrst" wrote:
>> I have to say that I don't consider this sentence to be useless.
>>
>> As far as I remember, there are other specs (mail?) that say that
>> text/plain is the default. So some implementers may be used to this, a=
nd
>> apply it to http, too.
>>
>> Also, while every natural language text has to assume that the reader
>> uses a certain amount of rational thinking, specs are usually written
>> with a somewhat reduced expectation in that respect, not because the
>> average reader is particularly dumb, but because the consequences of
>> interpreting something wrong are different than the consequences of
>> getting something wrong when e.g. reading a novel.
>>
>> So I don't see any reason for not keeping that sentence. Even if it
>> doesn't help, it definitely doesn't hurt.
>
> So what exactly does it mean in *practice* to treat something as
> "arbitrary data". What do you expect a browser to do in that case?

Let's say ask the user. That's what they are doing currently, as far as=20
I'm aware of. I haven't checked every latest version of every browser,=20
but on average, I'd expect a dialog that asks whether (and then where) I=20
want to save the file, or with what application I want to open it.

But of course HTTP cannot say that, because HTTP is about more than=20
browsers. But then, HTTP doesn't say what to do with data that is marked=20
as application/octet-stream, the same way as it doesn't say what to do=20
with data that is marked as text/html or any other media type. And that=20
seems just fine.

Put another way, the sentence is not useless because clients already=20
have to figure out what to do with data marked as application/octet=20
stream. We just tell them to reuse and leverage what they have figured=20
out and apply it to unlabeled content. If a client implementer, e.g. for=20
a debugging tool, has figured out that they want to show=20
application/octet-stream as plain text assuming a 'charset' that shows=20
each byte separately, then it's fine for them to use that for unlabeled=20
data.

That also means that the requirement is testable. Just check whether the=20
same happens for data labeled as application/octet-stream and for=20
unlabeled data. It may be difficult to automate such a test, in=20
particular in a test suite that is supposed to work across clients, but=20
it's nevertheless testable.

Also, the sentence is not useless because it tells implementers to NOT=20
treat as any of the other available content types, and that's what's=20
important.

Regards,   Martin.

From sm@elandsys.com  Wed Oct 30 22:29: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 5925E11E8200; Wed, 30 Oct 2013 22:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.564
X-Spam-Level: 
X-Spam-Status: No, score=-103.564 tagged_above=-999 required=5 tests=[AWL=-0.965, 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 dISD3tkySdt1; Wed, 30 Oct 2013 22:29: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 A0F6D11E81C7; Wed, 30 Oct 2013 22:29:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9V5Sdap011994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Oct 2013 22:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383197334; bh=G3oHs+ULiNXdNnSeILvnkjIh0rte+oNIYoAwiq/gG70=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iL/+RdZtg8+IDaDhuAXV6/Ngy1VvhrO1XXdQrTVk07IbCdMrsuWH6FkcFEPrX0rTD VwsLVUxQQhUn22BY+Q/ogY/JDJC3BMudySWZG3Z3zBTCooOt+TqjivF0+FQPcfrjKe Lys9qVteB0l5gWy27JbGJ6q//fzOCJmWXspVKHiA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383197334; i=@elandsys.com; bh=G3oHs+ULiNXdNnSeILvnkjIh0rte+oNIYoAwiq/gG70=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lOGRbhc8vRuoqaDZPmCEJLs2rsH+5CS+17U6AMxQf4xYXwnfQPPSx18PNcS5+ofGU 0QqKel5aIziVDIHBEkFVLAEuwYNR5+YFuVmQbutLkItp3hO3HOGajXmQb2lcNy8Kaf BDaCXSQm72vrPVDdXl6G0QQoFvPQ4XYV7o8yMCN0=
Message-Id: <6.2.5.6.2.20131030221454.0de19bf8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Oct 2013 22:24:58 -0700
To: Mark Nottingham <mnot@mnot.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: content inspection in absence of media type, was:   [apps-discuss] APPSDIR review of draft-ietf-httpbis-p2-semantics-24
In-Reply-To: <B6CADE9A-2472-44B5-96E4-18B571D48CD6@mnot.net>
References: <6.2.5.6.2.20131027115007.07e32210@elandnews.com> <526E8B9E.8030006@gmx.de> <6.2.5.6.2.20131029050405.0caf8b40@elandnews.com> <526FC24D.7060704@gmx.de> <6.2.5.6.2.20131030060359.0cb29068@elandnews.com> <B6CADE9A-2472-44B5-96E4-18B571D48CD6@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, apps-discuss@ietf.org, Julian Reschke <julian.reschke@gmx.de>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-httpbis-p2-semantics.all@tools.ietf.org, ietf-http-wg@w3.org, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Oct 2013 05:29:27 -0000

Hi Mark,
At 20:31 30-10-2013, Mark Nottingham wrote:
>Consensus around this text was particularly hard-won; unless there 
>is a very good reason to make a change, I'd rather not risk falling 
>into that rat-hole again.

Understood.

I'll copy this message to the Application Area Directors in case they 
have any guidance to provide.

Regards,
S. Moonesamy 


From l.wood@surrey.ac.uk  Wed Oct 30 22:43:02 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 A7DC321E80A8 for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 22:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.206
X-Spam-Level: 
X-Spam-Status: No, score=-3.206 tagged_above=-999 required=5 tests=[AWL=-0.608, 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 OkgRi3lufVDp for <ietf@ietfa.amsl.com>; Wed, 30 Oct 2013 22:42:58 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9EA11E8266 for <ietf@ietf.org>; Wed, 30 Oct 2013 22:42:48 -0700 (PDT)
Received: from [195.245.231.67:25623] by server-13.bemta-5.messagelabs.com id F7/69-31104-5DDE1725; Thu, 31 Oct 2013 05:42:45 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-82.messagelabs.com!1383198165!24490282!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.12; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2449 invoked from network); 31 Oct 2013 05:42:45 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-5.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 31 Oct 2013 05:42:45 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.216]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Thu, 31 Oct 2013 05:42:44 +0000
From: <l.wood@surrey.ac.uk>
To: <joelja@bogus.com>, <scott.brim@gmail.com>
Date: Thu, 31 Oct 2013 05:42:44 +0000
Subject: RE: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Topic: IETF must use only UTC in its announcements (Was: Live Streaming	of the IETF 88 Technical Plenary
Thread-Index: Ac7VkR0HaI++5EAhSV+SynM1KvRDewAajUO4
Message-ID: <290E20B455C66743BE178C5C84F1240847E3E25D9D@EXMB01CMS.surrey.ac.uk>
References: <87879E7D-A55B-4A88-80B8-B503C89E52CB@iab.org> <20131030081355.GA23990@nic.fr> <7F135C08-A550-450F-82B4-1F239E115BC3@tzi.org> <20131030083611.GA27804@nic.fr>	<01P06PWP9XG4004X76@mauve.mrochek.com> <CAPv4CP_X7M0GQr4O4DfSZE=wXGfsuxtCED6JfH+MX34J2j_h=Q@mail.gmail.com>, <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.com>
In-Reply-To: <CB860E86-F3A5-4292-ADA4-E7CBABC5660E@bogus.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: ned+ietf@mauve.mrochek.com, cabo@tzi.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, 31 Oct 2013 05:43:02 -0000

No, Ghana is on GMT, which is equivalent to the time still used British win=
ters. But Ghana has policy control over the offset it chooses...
http://www.timeanddate.com/worldclock/city.html?n=3D4

The nearer the equator you are, the less you need daylight savings.

If you read "Seize the Daylight: The Curious and Contentious Story of Dayli=
ght Saving Time", you'll come to loathe William Willett and all he stood fo=
r.
http://en.wikipedia.org/wiki/William_Willett

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of joel jaegg=
li [joelja@bogus.com]
Sent: 30 October 2013 16:54
To: Scott Brim
Cc: ned+ietf; Carsten Bormann; IETF Discuss
Subject: Re: IETF must use only UTC in its announcements (Was: Live Streami=
ng   of the IETF 88 Technical Plenary

On Oct 30, 2013, at 7:24 AM, Scott Brim <scott.brim@gmail.com> wrote:

> One aspect of the problem is calendar apps.  Some rather popular ones don=
't have a way to enter UTC, only UK time eg. BST, so you need some local ti=
me somewhere to enter the event in your calendar.

And the United Kingdom and Great Britian are not on BST all year. Ghana on =
the other hand is.

From jari.arkko@piuha.net  Thu Oct 31 00:07:17 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 64D0511E80EC for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 00:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=-0.175, 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 reUjJh-9-gMT for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 00:07:05 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE0011E8132 for <ietf@ietf.org>; Thu, 31 Oct 2013 00:07:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 77E692CC6B; Thu, 31 Oct 2013 09:06:48 +0200 (EET)
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 XRRT_TGOJL1R; Thu, 31 Oct 2013 09:06:48 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F064A2CC48; Thu, 31 Oct 2013 09:06:47 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: future of identifiers
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
Date: Thu, 31 Oct 2013 09:06:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA1A0900-81B0-4F03-B78E-547DC734455E@piuha.net>
References: <9F02AA5D-4146-4F8D-B635-DE5B44A9DA9A@piuha.net> <563C58B6-DD66-4CDD-969A-0DAF7DA205D9@frobbit.se>
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1510)
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: Thu, 31 Oct 2013 07:07:17 -0000

Patrik,

> I think it is important to not restart discussions already held =
regarding different requirements on identifiers, requirements that in =
turn lead to various alternatives on how they are allocated, managed and =
resolved.

Understood. Thanks.

> I do not think one can have one identifier that fits all. Instead =
multiple kind of identifiers are needed. Because of requirements on =
uniqueness (absolute, low risk of collisions or not needed at all), =
persistence, human readable/understandable, whether allocation and =
resolution should be designed for read (lookups) or write (allocation), =
what the identifier is to be used for (see id/loc discussions).

Agreed.

Jari


From sm@elandsys.com  Thu Oct 31 00:18:48 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 E658B11E80FC for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 00:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.601
X-Spam-Level: 
X-Spam-Status: No, score=-103.601 tagged_above=-999 required=5 tests=[AWL=-1.002, 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 wgjejudAWTTv for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 00:18: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 41FA711E80D9 for <ietf@ietf.org>; Thu, 31 Oct 2013 00:18:47 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r9V7IZEg007018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Oct 2013 00:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383203926; bh=7IA+rEefblANRpM7Sp7eYKgp1mxaQ/S/16etSRTXuZ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rSEnMEsZsLHXc3eCWWcD8gIgeX6goHoQz3NzeGg/NmTeugyDCxCATPEmr1RWi248Z mqLlMRJdZjaIsrz9GIeqX4kGUQmOqST3O52U+q6AvNub7pw7Zp0S3PQQrNYFp41SEp iQ2YJ/1iXg0jSwP7YPJTEHoh9+hSiA3MxMDyBnyk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1383203926; i=@elandsys.com; bh=7IA+rEefblANRpM7Sp7eYKgp1mxaQ/S/16etSRTXuZ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SzhZvp7syTA2pRoZcgDGDh7QJM7HWo1V3WcDqTo1HjKz/tEOfsUwUch2uqHyO5n4u xF9Lx5Q2yxk+oPQOPLtmaErSoMqFLj9osvjtZdevlqXPAMZ3yWj/4WgNbg7OxtCutV /5EbYnhfuhrt839y7TxN3x+l9lzCtpEdZ1NCBpMc=
Message-Id: <6.2.5.6.2.20131030231652.0ddedc90@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 Oct 2013 00:06:29 -0700
To: Pete Resnick <presnick@qti.qualcomm.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-resnick-on-consensus-05.txt> (On	Consensus and Humming in the IETF) to Informational RFC
In-Reply-To: <526FE354.40106@qti.qualcomm.com>
References: <20131007164829.16131.73595.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131008054041.0d74aa88@resistor.net> <526FE354.40106@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: Thu, 31 Oct 2013 07:18:49 -0000

Hi Pete,
At 09:33 29-10-2013, Pete Resnick wrote:
>See other messages. I think the intention is to make it a consensus 
>Informational document.

Ok.  As the document is Informational I'll read it according to BCP 9.

>I think section 3 is pretty clear that the chair must exercise 
>technical judgment in many cases. Your hypothetical is the extreme 
>case not mentioned in the document. If the group says that the sky 
>is green, *and* nobody questions that assertion, *and* the chair 
>suspects the sky is not green, I believe it is reasonable for the 
>chair to pose the question to the WG: "Are we sure the sky is 
>green?" If the working group simply says "Yes" without explanation, 
>I think the chair is within bounds to say, just as they are if 
>someone else had raised the issue, "I don't think the group has 
>truly considered and weighed this issue such that I can declare 
>(rough) consensus on this point." But this must be done *extremely* 
>carefully. Chairs who insert their technical judgment too often or 
>too heavy-handedly risk losing the confidence of the group as an 
>impartial consensus caller. Better might be for the chair to 
>(perhaps quietly) solicit a review from a sky color expert from 
>another working group, asking for them to comment on this sky being 
>green issue. But having the document go forward with a technical 
>issue that the chair knows about but that the rest of the working 
>group hasn't noticed is, I think, to shirk responsibility as a 
>member of the community.
>
>All that said, I wonder if it's necessary to say this in the 
>document. It's a more general comment about the chair role rather 
>than about consensus per se.

I preferred to use a case which is not related to any IETF 
discussion.  The reason I brought this up is because the Chair may 
not be viewed as impartial (re. above comment).  Thanks for 
explaining the above.

>I think (hope) that if we start thinking about consensus the way the 
>document describes, appeals (at least in the early form, where it's 
>simply discussing the issue with the chair or the AD) would not be 
>nearly so fraught.

Yes.

>I've added a bit to section 5. Send text if you think it is not sufficient.

I'll send text off-list if I notice anything.

Regards,
S. Moonesamy 


From olaf@NLnetLabs.nl  Thu Oct 31 01:45:16 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD9C011E80F1 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 01:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.140, 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 XRGdyG7wp8jH for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 01:45:16 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3F021E80CB for <ietf@ietf.org>; Thu, 31 Oct 2013 01:45:03 -0700 (PDT)
Received: from [IPv6:2001:980:2282:1:9d6e:cb9e:fc6:d8c4] ([IPv6:2001:980:2282:1:9d6e:cb9e:fc6:d8c4]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r9V8issc082432 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 31 Oct 2013 09:44:56 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r9V8issc082432
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1383209098; bh=RtLWwTU8dBT8EWgyNYUreUeh00JF/gHEratg36Vxhm0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=N4KUf4FI5Nq2U5+unT61JksViGKtVsZW6fLwlxi8a3/OAwMzi43/5G6Ra6ZjNNFU9 Lnx6QQ0+qFVY/1UIVpRER/xZL+IaqP5fG0DwASlBLquxb9Pf9JsIwQB0qcGSnPKm44 oWnpDSg8Ljo8L3xAtApRpebbxuXAM/Q7xQ764bY0=
Content-Type: multipart/signed; boundary="Apple-Mail=_6B793330-3601-4B24-A55D-55097690299D"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Review of: Characterization of Proposed Standards
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <CADnDZ8-KtfLSfPupzY2rDCbFpAdQ6es-birt2z3gtdoHG+iRCA@mail.gmail.com>
Date: Thu, 31 Oct 2013 09:44:53 +0100
Message-Id: <5D09DCB7-3359-4F5D-909F-8486844EAFE6@NLnetLabs.nl>
References: <5269209F.3060706@dcrocker.net> <CADnDZ882Rex1GOK6SiGVXrizjNusHtLSbcH4P5AqABb+Y2tXWQ@mail.gmail.com> <F5063677821E3B4F81ACFB7905573F24049EA32C49@MX15A.corp.emc.com> <52696048.1050701@dcrocker.net> <CADnDZ8-KtfLSfPupzY2rDCbFpAdQ6es-birt2z3gtdoHG+iRCA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 31 Oct 2013 09:44:58 +0100 (CET)
Cc: "draft-kolkman-proposed-standards-clarified.all@tools.ietf.org" <draft-kolkman-proposed-standards-clarified.all@tools.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: Thu, 31 Oct 2013 08:45:16 -0000

--Apple-Mail=_6B793330-3601-4B24-A55D-55097690299D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 31 okt. 2013, at 01:49, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi Kathleen
>=20
> As my understanding, this procedure update document under review =
allows comparing SDO work within our IETF work, so as IETF is already =
open to allow all participation of businesses and SDOs into IETF, this =
issue of comparing discussions while our standards draft developing will =
create longer discussions and even disagreements between =
businesses/companies.=20
>=20
> Any cross-organisation standard work issues with external bodies we =
need an agreement policy like our one with ITU. I don't think it is good =
to discuss comparisons in IETF because the IETF is open (other May not =
be), and we should focus on the development of our standards following =
IETF aim. The document does not mention any agreement requirement =
between IETF and other SDOs, if we want to allow such process.
>=20
> IMO the IETF has special aim and different standard vision than other =
SDOs , so IETF standards need to be interoperable, competitive, and not =
dependant. I suggest to add a requirement of existing agreement policy =
when doing work that involve other SDO.
>=20

Dear Abdussalam,

Just to clarify what the draft is about: It is about documenting our =
processes and giving a characterization of Proposed Standards that match =
what amount of review we have performed and what the resulting quality =
is.=20

There has been quite some pushback on the language that compares the =
quality of our output with the quality of other SDOs output. A version =
05 will shortly be available (and I will post a message to the IETF list =
when it is) that is far more neutral (less condescending) than the =
previous versions of the document.

Cooperation with other SDOs, in the form of e.g. liaison relations, is =
not the subject of this document. The document also doesn=92t talk about =
various types of normative relations that IETF standards may have with =
other documents.  I think that this document will not cause =91longer =
discussions=92 by itself.

I hope this clarifies, if not feel free to contact me off-list.

Thanks for engaging and kind regards,

=97Olaf


--Apple-Mail=_6B793330-3601-4B24-A55D-55097690299D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: Signature creating using GPG Tools.

iQIcBAEBAgAGBQJSchiGAAoJEFRqER47aqpko04QALXwYgtuHvXL4wpvtqnve+pw
MHp198V3An8uJ8fAaJpck6mZCmvrQ5BDw0DjDqQ0gPfmUIg6ckDZxZ5I6OPv0vu1
RS+pT0KsKn01xoYkZUx7wpE0xNUtltE5gpp4eVlR1Z4lkds38dEP2mK1W/sw1WWd
iqGJU7Yeq0FShmUbnQZj+CFNJQF5ahMh+NFlTiZi4DDsH58c9jcTsFSVZsW5Hv+I
4ta5cGMetXPJaCOsAyJpmDTukOCr+0ao4lNMqt3ZPQ8bDAY6uRl8M0CNCh3d5r6X
k6a9ugaPfqjFthyFNXucI0l/bY1SEJT444k7Ot94hD1qpoQ4ShkIVJ7t4Bwz3VVg
ndzvPOIHsHGBVWgwYqLTTyl7f/Pkyp8VYjp6gzLBph5BVe/YMzpR6FRqrxTr5JI0
/o8STHNBeQFVoI+PWKAiKcvj5W5wkm6Tmh8oqoetAJB/fJH+1mji7aWwiczxzNMb
07A5g7YPTIM6v3dbCz6x/q0GbxidGlp2g1xmaSSOvdt4n74zfs4VrIJsCkDZbBHb
a4pq7tXnkoUth5tF5SvMzR4jGL44IOFo0yrbT5/hcaquBBr3EB8fwm07fWariklY
j9xKYebfqRCTpXGlv3ui29c0oYbU+z2f3bxY/G+Hhkt9SdtlHmJcJZP4L9UquPUk
+puoD2OecrcgDu7I4hIU
=m420
-----END PGP SIGNATURE-----

--Apple-Mail=_6B793330-3601-4B24-A55D-55097690299D--

From sm@resistor.net  Thu Oct 31 08:48: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 B569011E8167 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 08:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 8Nbgh1dY25sR for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 08:48: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 6C7C511E8229 for <ietf@ietf.org>; Thu, 31 Oct 2013 08:48:31 -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 r9VFmJkF025971; Thu, 31 Oct 2013 08:48:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383234503; bh=VYVAFH0uO01hTjdOMV7RYAqCxtsc3/9/afrtzbMdVYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SHXOr05mkUlYOO06AaPJ9ATUeDILklb80gElIvhOpvKUmtJTK0JE8iZoDx+TudFF3 IsrH5+KY/KMxJpsP6Aitspt1EJi/h/dJn/7wrQeV4G5HVrcF/ZPkISwrYydnAVu8JG U9VdwyG7j+S9vdzQ/k/kE190+BpTIFTw4lydaWK8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1383234503; i=@resistor.net; bh=VYVAFH0uO01hTjdOMV7RYAqCxtsc3/9/afrtzbMdVYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nR7c1pg2wLkwI+e9zABbhNbgrLqqt+0nfKCNnSzyBsuLYFnuXNYWNS2Q5Z4MelvcY uegbxh7Y+P/2J5A+KvGcmIAV0JCBws1TdBxmUB34p4+MxPVubQ3gfsBWnj2SK/6VJO flqmmNZxQcyP/ZFv7JZ9UUtTFlTsPGk34ua1Bu0E=
Message-Id: <6.2.5.6.2.20131031083431.0d161e18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 Oct 2013 08:47:58 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [perpass] [removed] metrics
In-Reply-To: <526FC288.5060203@gmail.com>
References: <13102810494583_8A24@oregon.uoregon.edu> <526EB50D.70008@cs.tcd.ie> <526ECC25.3060106@comcast.net> <526ED0B2.1050006@cs.tcd.ie> <526FC288.5060203@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: rutkowski.tony@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, 31 Oct 2013 15:48:42 -0000

At 07:13 29-10-2013, Tony Rutkowski wrote:
>The metrics below are useful in
>analyzing the dynamics of the group.
>It certainly gets a gold star for diversity.
>
>For those considering ID definitions,
>the one below is available for use.
>
>[removed]: usually, a paranoid
>person stroking their keyboard to send
>message on perpass email list beating
>up on NSA and offering some mitigating
>scheme in an attempt to prevent traffic
>analysis.

The above is part of the message with msg-id: 
526FC288.5060203@gmail.com.  Somebody considered the message was 
offensive.  I did not catch which part might be considered as 
offensive at first.  I read the message again.  In my humble opinion 
the word marked as [removed] in the above is highly unusual for an 
IETF mailing list.

Regards,
-sm 


From ben@nostrum.com  Thu Oct 31 09:13:00 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 0D0C911E812D; Thu, 31 Oct 2013 09:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Level: 
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=0.159, 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 yAqGNodrc-Vy; Thu, 31 Oct 2013 09:12:59 -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 DD22721E80B7; Thu, 31 Oct 2013 09:12:57 -0700 (PDT)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r9VGCoit094836 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 Oct 2013 11:12:51 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Gen-ART LC Review of draft-ietf-ipfix-data-link-layer-monitoring-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <52727FDE.6040108@cisco.com>
Date: Thu, 31 Oct 2013 11:12:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CCBFD9D-71E4-42C4-A10B-B60ABCC5DDE7@nostrum.com>
References: <877E63A6-07D1-45C3-93EA-086871A8ADE7@nostrum.com> <52727FDE.6040108@cisco.com>
To: Paul Aitken <paitken@cisco.com>
X-Mailer: Apple Mail (2.1816)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: "ipfix-ads@tools.ietf.org" <ipfix-ads@tools.ietf.org>, "gen-art@ietf.org Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, draft-ietf-ipfix-data-link-layer-monitoring.all@tools.ietf.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: Thu, 31 Oct 2013 16:13:00 -0000

Thanks for the response. Those changes would address all of my comments.

Thanks!

Ben.

On Oct 31, 2013, at 11:05 AM, Paul Aitken <paitken@cisco.com> wrote:

> Thanks for the review, Ben.
>=20
> As you pointed out, the description in 3.2.18 wrongly specified a =
delta rather than a total; I've fixed it.
>=20
> I also clarified the third paragraph of the Introduction to say that =
the existing models don't yet contain enough elements - which is the =
point of this draft.
>=20
> Regarding section 4 / RFC 5477, the intention is that IANA's IPFIX =
registry is the ultimate reference. We want to avoid new drafts updating =
old RFCs.
> The IPFIX AD is considering how to proceed with that.
>=20
> I'll publish a -07 with the changes.
>=20
> Thanks,
> P.
>=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-ietf-ipfix-data-link-layer-monitoring-06
>> Reviewer: Ben Campbell
>> Review Date: 2013-22-10
>> IETF LC End Date: 2013-23-10
>>=20
>> Summary: Ready for publication as a proposed standard, with  one =
problem that should be easily fixed.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> 3.2.18:
>>=20
>> Title of the data element suggests a total, but the description =
sounds like a delta (i.e change since last report.)
>>=20
>> -- section 4 and subsections
>>=20
>> It looks like this draft updates at least RFC5477. If so, this should =
be indicated in the header and in the abstract.
>>=20
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>> -- section , 3rd paragraph:
>>=20
>> Do you mean to say the existing data models do not contain the =
elements needed, or that the models do not provide the right foundation =
for the needed elements? The wording seems to indicate the latter but I =
think you mean the former.
>>=20
>> -- General:
>> Watch for missing articles.
>=20


From olaf@NLnetLabs.nl  Thu Oct 31 09:36:06 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB5321E8108 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 09:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.117, 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 M59ha7Pb0+pF for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 09:35:31 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD3121F9DBA for <ietf@ietf.org>; Thu, 31 Oct 2013 09:34:31 -0700 (PDT)
Received: from [IPv6:2001:980:2282:1:9d9e:133c:85fa:81bc] ([IPv6:2001:980:2282:1:9d9e:133c:85fa:81bc]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r9VGYHrN019740 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 31 Oct 2013 17:34:20 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r9VGYHrN019740
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1383237261; bh=1e1n4N+HcZ9Oxbs86SjrmCSCmTKMi4xXFUxq+KJXgyQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=FR8CvhIvM4ODSuwEFmxZCeqCTVPqB7yJG4ufsvefqq0Vo/kjX2EVSFptJPwGl6PlJ Z2WvNeTuyZ1NpwAxP6xLryLFBYWFmMnNlI50UsjZk3I9VRGIULQDy+8YyDSQs/msj/ DjuuCSiYlzNE38pIoWJhzsrOMkebKUeYNdN6PpMo=
Content-Type: multipart/signed; boundary="Apple-Mail=_5216943F-006D-4680-A31B-4529277CD7CA"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: Review of:  Characterization of Proposed Standards
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <5269209F.3060706@dcrocker.net>
Date: Thu, 31 Oct 2013 17:34:17 +0100
Message-Id: <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl>
References: <5269209F.3060706@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1816)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 31 Oct 2013 17:34:21 +0100 (CET)
Cc: "<draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>" <draft-kolkman-proposed-standards-clarified.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, 31 Oct 2013 16:36:07 -0000

--Apple-Mail=_5216943F-006D-4680-A31B-4529277CD7CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 24 okt. 2013, at 15:29, Dave Crocker <dhc@dcrocker.net> wrote:

>=20
> Review of:    Characterization of Proposed Standards
> I-D:          draft-kolkman-proposed-standards-clarified-04
>=20
> Reviewed by:  D. Crocker
> Date:         24 October 2013
>=20
>=20
> Summary:
>=20
> This draft offers revised normative text for the criteria used to
> qualify IETF drafts as entry-level Proposed Standards status. The
> draft's background discussion makes a number of assertions of fact
> without substantiation, at least two of which are probably not =
correct.
> The revised normative text includes two criteria that also are likely
> inaccurate.
>=20
>   The draft is not ready for approval.
>=20


Based on these comments and the comments made during the IESG ballot =
I=92ve made changes to the document.
Just posted as:
http://tools.ietf.org/html/draft-kolkman-proposed-standards-clarified-05

See Appendix B.6 for a somewhat detailed in-document log of the changes =
or the excellent diff tool:
=
http://tools.ietf.org/rfcdiff?url2=3Ddraft-kolkman-proposed-standards-clar=
ified-05.txt

There was a suggestion to remove the characterization of Internet =
Standard (for completeness) I think that is a matter of taste and not of =
content.

More a matter of content is Dave=92s (off-list) suggestion to remove =
section 4: That section is result of a discussion on the IETF list =
between Sep 3 and 13 and addresses the worries about setting the bar to =
high for publication.


I believe that with this version all is addressed and we=92ve arrived at =
if not consensus, then only ripply consensus, certainly not rough=85. =
but off course Jari/IESG is the judge of that.

Over (and out?)

=97Olaf

--Apple-Mail=_5216943F-006D-4680-A31B-4529277CD7CA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: Signature creating using GPG Tools.

iQIcBAEBAgAGBQJScoaJAAoJEFRqER47aqpkP/4P/0gqwrSdnQeNgKIcts9Jzfc/
8eEZY9sSnw/TaeYATbw1bteyORrnYJuiRTqWUQJm7tauk9/A34OjNIoZcEBn+f59
br8puLU6C52twNvqYbgEz0Hak5lHahEJaASxlD8H18h86xNRm3MCMsJT2pz0Vx4p
fDDp/dBTmRrnH08t8QsFEEgh+kxX61nDdB83pYfQOQQ8i2Wu8M+QHX+xtPIiRDqn
y7H7WS/GVo+fPFkwVQDX0twshaFvajZt1veQ4FYpluwYZ1ZYr6jemkC8quAG4ts2
3vk5he63B/rI9j7pui1TDXf1x1IFy0QEShwlQBiW/nI9o+9Db1ftFd6Fk/R8aTiE
XYa/yd9jhoyV/VM0E9UWdH0sqQvub8Z0N11Y3WZ17NluFJtB8Dh8HcBXE2b2TI4t
U/roLG5DuA7PBJCY98QlMarGJrc9Em7rPCgHWf/d2gJz51xnozhm7Jwlc31wR9R7
8jvr3H5DHdVyNK+jpYE8cUePyucYYeIJtuaZ1SCycEL98yHwXPYPFWQVZ+ImUSsB
/FnXYhL5zIpw9az8RnaE8v9IqsgaA/AoyvkqJm9QkjaNUWV5Cf0V73fglMjBs2by
rxSTD8tFNGD1ZVNexq1cTbRo1MJ7H+6hLTzydg64lUzwAvBrYgWGApENq8RwK+IF
OV4/WsEKojCwfyzm88Al
=uGyc
-----END PGP SIGNATURE-----

--Apple-Mail=_5216943F-006D-4680-A31B-4529277CD7CA--

From daedulus@btconnect.com  Thu Oct 31 10:38:48 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 A7CD611E81D5 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 10:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.19
X-Spam-Level: 
X-Spam-Status: No, score=-3.19 tagged_above=-999 required=5 tests=[AWL=-0.591,  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 tKvmcZXA+S7F for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 10:38:26 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0184.outbound.messaging.microsoft.com [213.199.154.184]) by ietfa.amsl.com (Postfix) with ESMTP id A646E11E822D for <ietf@ietf.org>; Thu, 31 Oct 2013 10:38:23 -0700 (PDT)
Received: from mail3-db8-R.bigfish.com (10.174.8.234) by DB8EHSOBE032.bigfish.com (10.174.4.95) with Microsoft SMTP Server id 14.1.225.22; Thu, 31 Oct 2013 17:38:21 +0000
Received: from mail3-db8 (localhost [127.0.0.1])	by mail3-db8-R.bigfish.com (Postfix) with ESMTP id 7C29610013C	for <ietf@ietf.org>; Thu, 31 Oct 2013 17:38:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah2222h1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h304l1d11m1155h)
Received: from mail3-db8 (localhost.localdomain [127.0.0.1]) by mail3-db8 (MessageSwitch) id 1383241099173829_19673; Thu, 31 Oct 2013 17:38:19 +0000 (UTC)
Received: from DB8EHSMHS027.bigfish.com (unknown [10.174.8.234])	by mail3-db8.bigfish.com (Postfix) with ESMTP id 26F32480040	for <ietf@ietf.org>; Thu, 31 Oct 2013 17:38:19 +0000 (UTC)
Received: from DB3PRD0710HT005.eurprd07.prod.outlook.com (157.56.253.85) by DB8EHSMHS027.bigfish.com (10.174.4.37) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 31 Oct 2013 17:38:18 +0000
Received: from DB3PRD0210HT005.eurprd02.prod.outlook.com (157.56.253.69) by pod51017.outlook.com (10.255.75.40) with Microsoft SMTP Server (TLS) id 14.16.371.2; Thu, 31 Oct 2013 17:38:18 +0000
Message-ID: <003501ced65f$abf943c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20131031134437.5729.87395.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-leiba-smime-type-registry-01.txt> (Creation of aregistry for smime-type parameter values) to Proposed Standard
Date: Thu, 31 Oct 2013 17:35:51 +0000
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.69]
X-OriginatorOrg: btconnect.com
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: Thu, 31 Oct 2013 17:38:48 -0000

This I-D specifies an IANA entry with
 server-generated-key | [RFC-ietf-pkix-est] Section 4.4.2 |
 with a note to
  replace RFC-ietf-pkix-est in the table above with the RFC number
assigned to draft-ietf-pkix-est.

Should this be RFC7030?

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>; <smime@ietf.org>
Sent: Thursday, October 31, 2013 1:44 PM

>
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Creation of a registry for smime-type parameter values'
>   <draft-leiba-smime-type-registry-01.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-11-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
>
>
>    Secure/Multipurpose Internet Mail Extensions (S/MIME) defined the
>    Content-Type parameter "smime-type".  As the list of defined values
>    for that parameter has increased, it has become clear that a
registry
>    is needed to document those values.  This document creates that
>    registry, registers the current values, and specifies the policies
>    for registration of new values.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-leiba-smime-type-registry/
>
> IESG discussion can be tracked via
>
http://datatracker.ietf.org/doc/draft-leiba-smime-type-registry/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>



From barryleiba.mailing.lists@gmail.com  Thu Oct 31 10:56:32 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 3065D11E8170 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 10:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=0.025, 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 wzLqTheuA78e for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 10:56:31 -0700 (PDT)
Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id B30DB11E813D for <ietf@ietf.org>; Thu, 31 Oct 2013 10:56:31 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id hz11so2189981vcb.38 for <ietf@ietf.org>; Thu, 31 Oct 2013 10:56:31 -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:message-id:subject :from:to:cc:content-type; bh=wrTdRqiW85MGwNnEVvy/dbCfpavGrYzUQQbrn1JQHN4=; b=suRBNj4Ock8G3tB1Fbe3URDP2Sp0XbOG751Og1n0EB4kw2hWSqhFgB7gy0SAFQXK2L X+tl0N2L8wWjjcJmFKBV2904p24loyr4gszp0QdoLDb7Y6oGtF1xZq45rI8R4g2uKy7T IDBekgVJysFSSlMASaE7xccHCfGN6NgL26qLNBAnJCD8s7XxZmxs6jp5R+DcEkkvT1g9 xrByRzpll87x7OqJs14K1IuO8nMMqZn10Dcrh7dCij8BPXKbgJprW3CFlAJJAAFjgQPQ YVIc9toVIwb3Qu4sJGIVwi7O3aRqdL4fgyK+zG3KtsLDS39rj9lmTEF6Il5CwcpgmUgo 07EQ==
MIME-Version: 1.0
X-Received: by 10.52.191.162 with SMTP id gz2mr2432935vdc.26.1383242191087; Thu, 31 Oct 2013 10:56:31 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Thu, 31 Oct 2013 10:56:31 -0700 (PDT)
In-Reply-To: <003501ced65f$abf943c0$4001a8c0@gateway.2wire.net>
References: <20131031134437.5729.87395.idtracker@ietfa.amsl.com> <003501ced65f$abf943c0$4001a8c0@gateway.2wire.net>
Date: Thu, 31 Oct 2013 13:56:31 -0400
X-Google-Sender-Auth: hz-iUAiVOsFzBV6NAGmnQX66ff4
Message-ID: <CAC4RtVAYTUOG7kPE-=C-eFYROfVGLPJf6onbmk6VhM-yJ_4euA@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-smime-type-registry-01.txt> (Creation of aregistry for smime-type parameter values) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: "t.p." <daedulus@btconnect.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: Thu, 31 Oct 2013 17:56:32 -0000

> replace RFC-ietf-pkix-est in the table above with the RFC number
> assigned to draft-ietf-pkix-est.
>
> Should this be RFC7030?

Yes.  The RFC wasn't published yet when I wrote that.  This is changed
in the -02 version that I have waiting.  The -02 version also has
three other smime-type values, from RFCs 2634 and 3854 -- thanks to
Jim Schaad for pointing me to them.

Barry

From dhc@dcrocker.net  Thu Oct 31 11:07:35 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 96C5E11E8281 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 11:07: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 dnPNZVa+mMRP for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 11:06:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BB7C311E817F for <ietf@ietf.org>; Thu, 31 Oct 2013 11:06:41 -0700 (PDT)
Received: from [10.1.10.136] ([63.225.91.78]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r9VI6ZsG013018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 Oct 2013 11:06:39 -0700
Message-ID: <52729C1D.7010400@dcrocker.net>
Date: Thu, 31 Oct 2013 11:06:21 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: Review of:  Characterization of Proposed Standards
References: <5269209F.3060706@dcrocker.net> <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl>
In-Reply-To: <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl>
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.0 (sbh17.songbird.com [72.52.113.66]); Thu, 31 Oct 2013 11:06:40 -0700 (PDT)
Cc: "<draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>" <draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>, 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: Thu, 31 Oct 2013 18:07:36 -0000

Folks,

Thanks to Olaf, et al for putting up with my after-the-deadline 
feedback.  However this document goes to the core of the IETF and it's 
likely to stand for some decades.  So I think we all need to be 
particularly diligent at considering its uses and the opportunities for 
problems with it.  In other words, this is a good document for being 
fussy about fine points.

Note that the motivation for Olaf's draft is the misunderstanding by 
others of the nature and worth of Proposed Standards documents.  We do 
not have complaints about the actual /quality/ of the specifications, 
but of the language describing their formal status.

In effect, such folk are distracted by some of the words in RFC 2026. 
We can't fix their style of reading or limitations in how they integrate 
information and also we cannot ignore such folk.

What we /can/ do is try to have the draft anticipate problems with how 
such folk will read the text.  This requires a very different style of 
draft analysis than we typically expect.  Rather than looking for 
clarity, we need to look for opportunities to misunderstand.  (I call 
that necessary kind of language 'political' speech, since the author 
must worry about active misinterpretation and misrepresentation...)

That's what has motivated much of my feedback, including the additional 
points below...


And by the way...

      1.  For a document that goes to the very heart of the IETF's 
reason for being and especially given how long-lasting its effect is 
likely to be, it has received astonishingly little active, public 
review, based on the public record.

      2.  I also wonder whether we shouldn't circulate the draft more 
broadly, outside of the IETF, to request the comments.  Will it 
accomplish what we want it to accomplish?



Into some details...

On 10/31/2013 9:34 AM, Olaf Kolkman wrote:
 >  There was a suggestion to remove the characterization of Internet
 > Standard (for completeness) I think that is a matter of taste and not
 > of content.

When there is more than one source for something as basic as 
"characterization of Internet Standard" the different copies will, over 
time, diverge and create an opportunity for confusion.  This draft seeks 
to be a normative document.  It needs to stay within its scope.  Its 
scope does not include characterization of Internet Standard.  It 
should, therefore, merely cite the proper text contained elsewhere.

By way of making offering a typical example:  Keep this redundant text 
in the current draft.  Years from now, change the related text in RFC 
2026, in ways that are significantly different from what is in this 
current draft.  There will be no synchronization effort to ensure that 
this draft is fixed to match the new, official text, because there is no 
formal linking of the text.  Anyone reading the RFC version of this 
current draft will therefore be reading an incorrect characterization.


 > More a matter of content is Dave’s (off-list) suggestion to remove
 > section 4: That section is result of a discussion on the IETF list
 > between Sep 3 and 13 and addresses the worries about setting the bar
 > to high for publication.

My concern about section 4 is that it only serves to invite criticism of 
IETF documents.  The statements in Section 4 really apply to all 
technical specifications and all organizations that publish them.  We 
never achieve perfection and we always reserve the right to produce a 
better version.

So including text that says nothing distinctive but has language about 
likely flaws invites criticism; it mostly serves as material for those 
looking for the opportunity.


Again, my apologies for the added round of late-stage effort I've 
triggered and many thanks to Olaf et al for responding so helpfully.

d/



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From barryleiba.mailing.lists@gmail.com  Thu Oct 31 13:53:05 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 DE44711E81B0 for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 13:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.955
X-Spam-Level: 
X-Spam-Status: No, score=-101.955 tagged_above=-999 required=5 tests=[AWL=0.023, 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 P0NL3JYDIPGH for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 13:53:05 -0700 (PDT)
Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0B97311E81AD for <ietf@ietf.org>; Thu, 31 Oct 2013 13:53:04 -0700 (PDT)
Received: by mail-vb0-f46.google.com with SMTP id 10so2269742vbe.5 for <ietf@ietf.org>; Thu, 31 Oct 2013 13:53:04 -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:message-id:subject :from:to:cc:content-type; bh=ZLuZqWl6HNbHjQ6McBqxipgDqr+ica0rX5wbyrybvtk=; b=rVOJrmg8Njq+oF7v7wW5ldGwld5Nel/54VyNT8F9VDRFvoTNSCsO8g/vz65mMCws4y T5RI3N07+r6qZ9Wob7xU4yF2OhHx52OY5bJNuUSdPMJgkSSoTWGnDWe5EmyNq6m/MnTv Rjc0SeI9xQlCSHWCUxJCHBKEHF0j7g8UJN5i4xJxGs/kffj/iG4QXU/BRIYpMLtmUjrW iisaJayO6tlW05s7xJd06NjpM5Y9TLmHl95ZU0iXY1mz81cxeGj6h/jUaBNlFUQcBfPJ iP/9gIJGTAZIDFLFinh393WnF3ASyncyS5g+yIDC3Y+Sh/j0cjMApcPrNhnSp1IIj+nS o5RQ==
MIME-Version: 1.0
X-Received: by 10.221.64.17 with SMTP id xg17mr3248369vcb.5.1383252784445; Thu, 31 Oct 2013 13:53:04 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Thu, 31 Oct 2013 13:53:04 -0700 (PDT)
In-Reply-To: <52729C1D.7010400@dcrocker.net>
References: <5269209F.3060706@dcrocker.net> <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl> <52729C1D.7010400@dcrocker.net>
Date: Thu, 31 Oct 2013 16:53:04 -0400
X-Google-Sender-Auth: Sn-RRzmts9T9BovvZtad17FiWeo
Message-ID: <CAC4RtVCewEKatJKJnBbCqgsuBjHCOHY49WoTx+y-K_zDt+Smxg@mail.gmail.com>
Subject: Re: Review of: Characterization of Proposed Standards
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "<draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>" <draft-kolkman-proposed-standards-clarified.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, 31 Oct 2013 20:53:06 -0000

So far, I've just held the DISCUSS ballot that's been the formal
process to keep this discussion open.  It's time to start paddling the
oar that I've stuck in.

It seems that there are still three points that Dave has:

1. A general point: the document doesn't seem to have had the review
and scrutiny that one would expect for a significant process change.

2. Simple duplication of text from 2026 (in Section 3.2) is not a good
idea, as it invites future divergence.

3. Section 4 should be removed, as it weakens the statements made
elsewhere in the document and invites criticism, and is in effect self
evident anyway.

To point 1, I have a couple of notes in response.  I agree that this
is a formal process change -- some say it's not, but is only
documenting what we already do, and I think that's ignoring the fact
that, notwithstanding that, this document *does* change the formal
definition of what Proposed Standard means.  It doesn't matter that
it's "merely reflecting reality"; it's still a formal change.  That
said, I believe that the light volume of comments is because (1) it
*is* reflecting reality, and that's mostly not controversial and (2) a
lot of this was discussed when RFC 6410 was being developed, and these
changes are really artifacts of that discussion (which did not lack in
participation).  Further, the document has been out here for
discussion; the opportunity has been here, and IETF folks aren't
normally shy if they have things to say.

So, while I understand Dave's concern, I don't share it.  But Dave goes on:

>      2.  I also wonder whether we shouldn't circulate the draft more
> broadly, outside of the IETF, to request the comments.  Will it accomplish
> what we want it to accomplish?

We could post it to the new-work mailing list, or explicitly send it
out through our liaisons.  It's likely, I think, that it would get
little attention that way, though we won't know unless we do it.  On
the other hand, we don't normally send our process documents out that
way -- we didn't do that with the draft that became 6410, for example.
 I have no objection to soliciting external reviews and comments, but
I'm doubtful that it'll be useful.

On point 2, Olaf says this:
>>  There was a suggestion to remove the characterization of Internet
>> Standard (for completeness) I think that is a matter of taste and not
>> of content.

I think that's not really addressing the core of Dave's concern, which
isn't that the repetition is unnecessary (which would be a matter of
taste), but that it's actually harmful, in that future changes could
leave us with two divergent definitions of "Internet Standard".

On this, I'll note that we're already somewhat along that path, as
6410 quoted text from 2026 in its definition of "Internet Standard".
And I'll also note to things along that line:

a. 6410 tweaked the definition of Internet Standard, in order to merge
in aspects of Draft Standard.  That this document quotes 2026 without
also bringing in the changes from 6410 somewhat misstates things (in a
small way, but nonetheless...).

b. 6410 had the opportunity to do the same thing, copying the
definition of Proposed Standard (which it did not change) from 2026,
and it didn't do it.  Instead, it said this:

   The stated requirements for Proposed Standard are not changed; they
   remain exactly as specified in RFC 2026 [1].  No new requirements are
   introduced; no existing published requirements are relaxed.

I suggest that that's a better approach, and would suggest that
Section 3.2 would be better done this way:

   The stated requirements for Internet Standard are not changed; they
   remain exactly as specified in Section 2.2 of [RFC6410], as it updates
   Section 4.1.3 of [RFC2026].

On point 3, I'll note that Section 4 is in this document exactly in
response to my comments.  I was concerned that as this document
tightens the formal criteria for PS, it's likely to cause even more
strictness in IESG approval.  We've always had the option (and have
not infrequently exercised it) to approve a document at PS that *does*
have known limitations.  This is from Section 4.1.1 of RFC 2026:

   A Proposed Standard should have no known technical omissions with
   respect to the requirements placed upon it.  However, the IESG may
   waive this requirement in order to allow a specification to advance
   to the Proposed Standard state when it is considered to be useful and
   necessary (and timely) even with known technical omissions.

Without Section 4, I believe we are removing the option that the
second sentence gives the IESG, and I want to be absolutely sure we
want to do that, before we do.  It's my opinion that we don't want to
remove it, and that's the purpose of Section 4.

> My concern about section 4 is that it only serves to invite criticism of
> IETF documents.  The statements in Section 4 really apply to all technical
> specifications and all organizations that publish them.  We never achieve
> perfection and we always reserve the right to produce a better version.

I believe that Section 4 is saying more than the things that apply to
all technical specifications: it's not just saying that they're not
perfect and that we might find problems later.  It's meant to say that
we might, sometimes, approve specifications at Proposed Standard that
we *know* to have imperfections and limitations, and we're approving
them anyway.  And what it's adding to what 2026 says about that is
that when we do that, we'll explicitly say so in the document.

Perhaps you have a suggestion for different wording, Dave, that will
address your concern while still addressing mine?

Barry

From sm@resistor.net  Thu Oct 31 17:04:20 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 76CF411E810C for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 17:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 Wfn-07EdoOyl for <ietf@ietfa.amsl.com>; Thu, 31 Oct 2013 17:04:19 -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 97EEB11E81C8 for <ietf@ietf.org>; Thu, 31 Oct 2013 17:04:16 -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 rA1046Tg023738; Thu, 31 Oct 2013 17:04:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1383264252; bh=X8YY5KCr2jy4Lrx5YKK60nCKMwpoFQY5WTkzXxeyG1c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O5/iMEqLChGVkztqdOyMJ2sxNMQRcb+nJE6gvDdfJWCZ8g9TGMZ3+vS4mV2yFpyey 4gFWD0xQuz/nOM96tzgsT012BmPQY7llowr+8MNIqtLzH4YpXSvkZWVGE3T10W5zDg VDWlnZfzisCmjdTh+7L9IvQC1sPseoAVofnAkCCs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1383264252; i=@resistor.net; bh=X8YY5KCr2jy4Lrx5YKK60nCKMwpoFQY5WTkzXxeyG1c=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rY+1OGZG/QfJTQccYcyZKteq+zjWw3KU+wWwrOjWbBXI835ZYUpO4khxP3qGPMO9d uFHUUAH/fVycX4Jq0CmIbtjEJlIPERR1Ot1YjOgtL+UlQ9dVMHzWADkmvfyi6ZUBLF m/Rm2axyUsagS6TDYoF/PzQTH3pBjgP7+DeLBZHA=
Message-Id: <6.2.5.6.2.20131031150136.0e281f08@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 Oct 2013 17:00:37 -0700
To: dcrocker@bbiw.net, Olaf Kolkman <olaf@NLnetLabs.nl>
From: SM <sm@resistor.net>
Subject: Re: Review of:  Characterization of Proposed Standards
In-Reply-To: <52729C1D.7010400@dcrocker.net>
References: <5269209F.3060706@dcrocker.net> <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl> <52729C1D.7010400@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-kolkman-proposed-standards-clarified.all@tools.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, 01 Nov 2013 00:04:20 -0000

Hi Dave,
At 11:06 31-10-2013, Dave Crocker wrote:
>Note that the motivation for Olaf's draft is the misunderstanding by 
>others of the nature and worth of Proposed Standards documents.  We 
>do not have complaints about the actual /quality/ of the 
>specifications, but of the language describing their formal status.

Yes.

>In effect, such folk are distracted by some of the words in RFC 
>2026. We can't fix their style of reading or limitations in how they 
>integrate information and also we cannot ignore such folk.

The IAB sent a comment about ICT standardization to a directorate of 
the European Commission in 2009.  My interpretation of the intent is 
that it was so that the IETF is recognized more broadly among 
standardization organizations.  The comment stated that the IETF and 
IAB exert no control over the nature or identity of participants in IETF
activities.  Some parts of the comment was about standards 
making.  Most of the comments are usually about the process instead 
of the quality of the specifications.  If IETF  ignores such folks 
(see above) it can affect where the RFCs can be used.

In Section 2:

   "Hence IETF Proposed Standards are of such quality that they
    are ready for the usual market-based product development and
    deployment efforts into the Internet."

I am not comfortable with having that text in BCP 9.  The argument up 
to now has been running code and that that is the line which has been 
used for test of quality.  A better test of quality might be someone 
who has not followed the working group and who can implement the 
specification.  There is also the IPR test.  That is also one of the 
issues mentioned by the audience which the document targets.

Regards,
-sm 

