
From mmorrow@cisco.com  Tue May  1 00:01:12 2012
Return-Path: <mmorrow@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 2CD8A21F8790 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 00:01:12 -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 MpcqZbXo4jQp for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 00:01:11 -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 6CFC921F877E for <ietf@ietf.org>; Tue,  1 May 2012 00:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mmorrow@cisco.com; l=1245; q=dns/txt; s=iport; t=1335855670; x=1337065270; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=vPVpAMMUTOYbXxM3tOfYcyo6hYglYvheODPhXrYUbcA=; b=YxDMKourqPoL32RQLXudcpy7O01dK5dTvBQS7jWlonuVUqx+uXVWLU0w VUVXzykF44BbevqXWD18QuMUv9oebe/65hArpzbXVzSZcTBCmlawELZI8 tODBXJIJf6f7yQjdRjeixUjumph9XAQ+cYq67Ivw3t78d9WvQrtEEYsHY 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAGGJn0+Q/khL/2dsb2JhbABEr2eDAYEHggkBAQEDARIBKQFBDQEIFQNPNgEBBAESFQEFB4ddAwYFmiqPEYcHDYlTigOHAgSIMDSNGos/gxqBaYMI
X-IronPort-AV: E=Sophos;i="4.75,509,1330905600"; d="scan'208";a="136671871"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 01 May 2012 07:01:09 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q417199S006644; Tue, 1 May 2012 07:01:09 GMT
Received: from xmb-ams-110.cisco.com ([144.254.74.85]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 May 2012 09:01:08 +0200
Received: from 10.61.99.128 ([10.61.99.128]) by XMB-AMS-110.cisco.com ([144.254.74.85]) via Exchange Front-End Server email.cisco.com ([144.254.231.96]) with Microsoft Exchange Server HTTP-DAV ;  Tue,  1 May 2012 07:01:08 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Tue, 01 May 2012 00:01:06 -0700
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Monique Morrow <mmorrow@cisco.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Riccardo Bernardini <framefritti@gmail.com>, IETF discussion list <ietf@ietf.org>
Message-ID: <CBC4D842.CE3C8%mmorrow@cisco.com>
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: Ac0msR/oN8gGn7tgME6s2getERvtyAAK4hPOACLhXl4=
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0A8D@DC-US1MBEX4.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 01 May 2012 07:01:08.0684 (UTC) FILETIME=[2F4670C0:01CD2768]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 07:01:12 -0000

> In the countries with which you are most familiar, what answers do
> girls give you?

 The responses vary from lack of encouragement; lack of role models; lack o=
f
education-inspiring instructors;

 "geek c =E9st chic! "

> What responses do you receive to your motto?

Very positive - my point is geek is not negative and it can be really reall=
y
cool=20

Best -m



On 4/30/12 7:22 AM, "Worley, Dale R (Dale)" <dworley@avaya.com> wrote:

> On 4/30/12 2:03 AM, "Riccardo Bernardini" <framefritti@gmail.com> wrote:
>> In this case the best solution (although not easy to implement) would
>> be to ask directly to young women: "Are you interested in an ICT
>> carrer?, If yes, why?  If no, why not?"
>=20
> From: Monique Morrow [mmorrow@cisco.com]
>> Well I do engage quite actively in these discussion with girls in high
>> school; young women in universities and women in the industry the proble=
m
>> space and opportunity is  multifaceted, cultural depending upon the
>> country
>=20
> In the countries with which you are most familiar, what answers do
> girls give you?
>=20
>> and btw  my motto:
>>=20
>> "geek c =E9st chic! "
>=20
> What responses do you receive to your motto?
>=20
> Dale


From sm@resistor.net  Tue May  1 00:13:03 2012
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 635A421F864A; Tue,  1 May 2012 00:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GmHL2nu+M0jl; Tue,  1 May 2012 00:13:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4C221F8657; Tue,  1 May 2012 00:13:01 -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 q417CgZO001861; Tue, 1 May 2012 00:12:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1335856372; i=@resistor.net; bh=s9CU/SD9U/YQBdSyTK95nyGgOOCt6uC17RO9blwnWJo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Bl6m9xNlkYSL3o5MJrkE7/3OsNMdqC9ns08U44tonC5bZJZCm+bKKE5uhmAt6+9Ci NgbSK8DOL+rt+BUR05MC6/J09ksAuGiHoAmiV44P0CqpOPJJ4546UtsOkapPHLCXIB nh1tnCgQKdB9lO56dtND/eyj8N3stJ/Rt87uK/s4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1335856372; i=@resistor.net; bh=s9CU/SD9U/YQBdSyTK95nyGgOOCt6uC17RO9blwnWJo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=riH8DR4+BDzwvcuSsamLZZnzQ/AWq1vpZXit5qqaACGMG5eqPKkulxcGhrktLQ3Sh U4DWLSaJCyyGke8L9Dl8WwyxvGzH1aZZoxZA4eYxMSq5G7szVMXG7z4Gb/b79aaxHg gk8Gbag13d5yEl8jjdflMB47FYjVaXddXISzdxqU=
Message-Id: <6.2.5.6.2.20120430223624.0c706828@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 30 Apr 2012 23:28:59 -0700
To: Stephan Wenger <stewe@stewe.org>, Ron <ron@debian.org>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-codec-opus-12.txt> (Definition of the Opus Audio Codec) to Proposed Standard
In-Reply-To: <CBC4E0F3.867E4%stewe@stewe.org>
References: <6.2.5.6.2.20120430120153.0947ed48@resistor.net> <CBC4E0F3.867E4%stewe@stewe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: codec@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 07:13:03 -0000

At 15:53 30-04-2012, Stephan Wenger wrote:
>This subject was also raised by our AD on the codec mailing list.  The
>statement is about spec text copyright (with the possible exception of the
>word "use", which is loaded in this context, see BSD license and implicit
>patent grant ambiguity).  Insofar, the patent licensing statement received
>appear to be irrelevant to this discussion.

Ok.

At 18:40 30-04-2012, Ron wrote:
>If this clause becomes a blocker, then we should simply remove it, but in that
>case it would be good to have clear reasons why it became a blocker, since the
>things you say you fear here, I see as already being prohibited anyway.

The text in Section 10 is ambiguous.

Given all the efforts that went into RFC 6569, it's odd to see the 
text being discussed during the Last Call instead of the WGLC.

Regards,
-sm  


From framefritti@gmail.com  Tue May  1 01:19:20 2012
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 C89CC21F8697 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 01:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.227
X-Spam-Level: 
X-Spam-Status: No, score=-3.227 tagged_above=-999 required=5 tests=[AWL=0.372,  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 YfauBxrzTBWM for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 01:19:20 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8531B21F869C for <ietf@ietf.org>; Tue,  1 May 2012 01:19:19 -0700 (PDT)
Received: by werb10 with SMTP id b10so2807416wer.31 for <ietf@ietf.org>; Tue, 01 May 2012 01:19:18 -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=7UEls7P65j8iVJCTredbbvjg0ngdUBizTECPZe2HKuY=; b=AOxRpxTvnHpamFc1cFJ2TUTPjlJtVBSF/edGVDJUoNKk8m0hci7iIdLibhKYhBo/gK XY1eObgn639M2MWj2aB3dMVJhEwLnVJXkYM5El672w4q2Tw12XdJVXt1ZY+D5wvVk7sa Bo0u56ZSz6AHMGMHN+6s6izUQ8rhkl4aZwcCwzZ9BoTJBYDJghobNBSfoh4kfYnfzpT5 qxXgWydAN/74xopLwZ5nrLAkn5S2kB9jPiV2DLuLc52KcvwGUdtvi/SZjbpbd3jLW+TE JGLGCLGqWl6wgs87uFvLknRXwqOhksi3++asVfnH7m0rw9RBRvNvu9Iuu6gvHzzl1FII NRIw==
MIME-Version: 1.0
Received: by 10.216.144.228 with SMTP id n78mr14395013wej.100.1335860358640; Tue, 01 May 2012 01:19:18 -0700 (PDT)
Received: by 10.223.107.2 with HTTP; Tue, 1 May 2012 01:19:18 -0700 (PDT)
In-Reply-To: <4F9EC5FD.7070802@gmail.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CABSMSPV-rON1CetAZFtkQsP2owMPhuTsOkCm=Dgi-2EP-9pAPA@mail.gmail.com> <4F9EC5FD.7070802@gmail.com>
Date: Tue, 1 May 2012 10:19:18 +0200
Message-ID: <CABSMSPVzaeVXt83t=57XbF=DwEfV=r9o47S_VEWSzmsgEaCEYA@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Riccardo Bernardini <framefritti@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 08:19:21 -0000

On Mon, Apr 30, 2012 at 7:03 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 4/30/12 7:33 AM, Riccardo Bernardini wrote:
>>
>> So it seems (by this anecdotal and very limited evidence) that
>
>> [ ... ]
>
> So it seems to me that when in possession of only anecdotal,
> limited evidence that it might be a good idea to acquire more
> evidence before drawing conclusions.

Sorry, I did not want to express any conclusive position about this
issue. I was just expressing my impression, given my personal
experience.  I am sorry if gave another impression, but English is not
my native language, so some misunderstanding can happen.

As I said in another post, I tend to avoid this type of discussions
because of the risk of generating more heat than light.

>
> Melinda
>

From stephen.farrell@cs.tcd.ie  Tue May  1 02:20:06 2012
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 3103B21F871A for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 DhBXsbN3W7Lg for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:20:05 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 093D121F8712 for <ietf@ietf.org>; Tue,  1 May 2012 02:20:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 266131714FA for <ietf@ietf.org>; Tue,  1 May 2012 10:20:04 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-type:in-reply-to:references:subject:mime-version :user-agent:from:date:message-id:received:received: x-virus-scanned; s=cs; t=1335864002; bh=mgJARHU5b1XkkI/fqCnxwNLE cp0pCc+R9jW2NBOHFh4=; b=xdmY97qfx1aiY5st9KNDfp2lTT3FIx0WxmwmPOAX diL5J7/puiW6Xh9TW2s+/NUVE9kZtRrEDtRlyGfwuETEkHPdFSOsAa2fZMIvL26W RdHH0FeBfX+EBTzAZRZ4gReWD4FbIVWo2I31IazWBIpQghoWlu3rmDHp7VV9ByML oWc3BBM91nf3/+eHX0l1k7o3fVv/7No9Gkja6MkPliZqYiMrTCZikr1YE/TjEb6I +4FCkPdsG2CPI0qIOkOaV8QeVDLh3yM3TeY11C80eovzJs3dbD5LUprOoKOJ2VL/ VThlx1Px93hvLiConk8jPqOL3nXb0VpEreiSzFyclVMSag==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id hdHKUwWwIFWt for <ietf@ietf.org>; Tue,  1 May 2012 10:20:02 +0100 (IST)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A67431714F9 for <ietf@ietf.org>; Tue,  1 May 2012 10:20:02 +0100 (IST)
Message-ID: <4F9FAAC2.2050006@cs.tcd.ie>
Date: Tue, 01 May 2012 10:20:02 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120424 Thunderbird/12.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based Authentication of Named Entities (DANE) Protocol for Transport	Layer Security (TLS)) to Proposed Standard
References: <20120412014127.26637.56232.idtracker@ietfa.amsl.com>
In-Reply-To: <20120412014127.26637.56232.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.1
Content-Type: multipart/mixed; boundary="------------060202030202090405020505"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 09:20:06 -0000

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


Hi,

There's been a bunch of mail on this list about this so
here's my summary of the state of play just sent to the
DANE list.

Please feel free to correct me if I've gotten something
wrong.

Cheers,
S.

On 04/12/2012 02:41 AM, The IESG wrote:
> 
> The IESG has received a request from the DNS-based Authentication of
> Named Entities WG (dane) to consider the following document:
> - 'The DNS-Based Authentication of Named Entities (DANE) Protocol for
>    Transport Layer Security (TLS)'
>   <draft-ietf-dane-protocol-19.txt> as a 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 2012-04-25. 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
> 
> 
>    Encrypted communication on the Internet often uses Transport Level
>    Security (TLS), which depends on third parties to certify the keys
>    used.  This document improves on that situation by enabling the
>    administrators of domain names to specify the keys used in that
>    domain's TLS servers.  This requires matching improvements in TLS
>    client software, but no change in TLS server software.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dane-protocol/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dane-protocol/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> dane mailing list
> dane@ietf.org
> https://www.ietf.org/mailman/listinfo/dane
> 

--------------060202030202090405020505
Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message"

X-Mozilla-Keys: 
Return-Path: <dane-bounces@ietf.org>
X-Original-To: stephen.farrell@cs.tcd.ie
Delivered-To: stephen.farrell@cs.tcd.ie
Received: from localhost (localhost [127.0.0.1])
	by hermes.scss.tcd.ie (Postfix) with ESMTP id 5DC991714F9
	for <stephen.farrell@cs.tcd.ie>; Tue,  1 May 2012 10:12:56 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 required=5 tests=[BAYES_00=-2.599,
	DKIM_VALID=1, DKIM_VERIFIED=-0.1, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Authentication-Results: scss.tcd.ie (amavisd-new); dkim=pass
	header.i=@ietf.org
Authentication-Results: scss.tcd.ie (amavisd-new); dkim=softfail (fail,
	message has been altered) header.i=@cs.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1])
	by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10026)
	with ESMTP id DCH5URtv+r25 for <stephen.farrell@cs.tcd.ie>;
	Tue,  1 May 2012 10:12:55 +0100 (IST)
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:123a::1:1e])
	by smtp.scss.tcd.ie (Postfix) with ESMTP id 0643A171471
	for <stephen.farrell@cs.tcd.ie>; Tue,  1 May 2012 10:12:55 +0100 (IST)
Received: from ietfa.amsl.com (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 48BE121F8744;
	Tue,  1 May 2012 02:12:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1335863573; bh=knSoA7MPz4TJN+shl40K1yCm6UCi/SU9eW2QkzoreHE=;
	h=Message-ID:Date:From:MIME-Version:To:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Content-Type:Content-Transfer-Encoding:Sender;
	b=ly2prrfGCMcSE0fGbvQSKW076HlbAozvI3rNtf4UMhVAr9hn2CPLo42/lItbDq+dE
	 RmbmdUZzjcOgIglLu/NA0pnJWpHWdj/23/XU1dbGO63GNg9T06x/eUo070iMmARgQo
	 +mY/RlovZNyLMBdurjapV2NtfgHBNhu74bZdabtY=
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 26A3821F86B4
	for <dane@ietfa.amsl.com>; Tue,  1 May 2012 02:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([12.22.58.30])
	by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LBfnjbNJhfBu for <dane@ietfa.amsl.com>;
	Tue,  1 May 2012 02:12:46 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie
	[IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2])
	by ietfa.amsl.com (Postfix) with ESMTP id 0829921F8693
	for <dane@ietf.org>; Tue,  1 May 2012 02:12:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by hermes.scss.tcd.ie (Postfix) with ESMTP id 7A5541714F9
	for <dane@ietf.org>; Tue,  1 May 2012 10:12:44 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=
	content-transfer-encoding:content-type:subject:mime-version
	:user-agent:from:date:message-id:received:received:
	x-virus-scanned; s=cs; t=1335863563; bh=mLwH6eyb5qyP/aOWijm2JcZd
	/FRGQPrp7Y0BPq7Og4E=; b=Xn9cLLb77NPOXBEdPOL2hK+B8SjxwjWssKqAjK0w
	7Q6+qVUVXNoJYAQE4/KOKoJpb91CpXd2NeF7B8USb+GTS4a7yIFl/VLCwm4EZXTT
	DaSh1uPQZclWTxQC9fpoQ1EQAu5iiYkGeBUL/5SHszeY57TBbsgUTitrZ4iYTOTs
	tdDRbqbOT3wDYvhJTgJYcQ5FEF9kFWaUwJoseY8xqHQpQzJ8zskl0ntCHYz2u0rO
	eE3WrpbTK04ZT2P/9G9U4VlBoXWEkfdXZkG6wTXzrQnMRcVh3TiV+O4MbHDcfzyC
	DngM8OhRayO8btaSfgV8DerD9FnnRY896+16Npca39TA+Q==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1])
	by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027)
	with ESMTP id cbfDKKo59fCH for <dane@ietf.org>;
	Tue,  1 May 2012 10:12:43 +0100 (IST)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown
	[IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c])
	by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C8264171471
	for <dane@ietf.org>; Tue,  1 May 2012 10:12:43 +0100 (IST)
Message-ID: <4F9FA90B.9090607@cs.tcd.ie>
Date: Tue, 01 May 2012 10:12:43 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:12.0) Gecko/20120424 Thunderbird/12.0
MIME-Version: 1.0
To: dane <dane@ietf.org>
X-Enigmail-Version: 1.4.1
Subject: [dane] DANE IETF LC state of play
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>,
	<mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dane>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>,
	<mailto:dane-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dane-bounces@ietf.org
Errors-To: dane-bounces@ietf.org


Hi all,

Well that's been a busy IETF LC. I think that shows that this is an
important spec and the editors and chairs have done a great job
so far on handling IETF LC comments, but I think there is a bit more
work to do to be sure we're done and we may as well get that done
now before the IESG are let loose on it:-)

I went through the DANE WG archive of all the IETF LC comments and
found the following ones where its not crystal clear from the archive
that they're sorted.

Notes: a) they might be just fine, e.g. if just one person comments
and nobody else thought it important, then doing nothing is probably
right. these just weren't clear from the archive so I wanna check;
b) I only had time to scan the WG archive, if there are mails that
were only to ietf@ietf.org or apps-discsuss that resolved these
then I missed them, so just tell me about that, so I'll forward
this to the other lists to check as well.

So here's the list:

1) Jeff Hodges
http://www.ietf.org/mail-archive/web/dane/current/msg04695.html
http://www.ietf.org/mail-archive/web/dane/current/msg04713.html

I mailed Jeff to see if -20 is ok. Silence can be taken to mean
yes I think but since he had a bunch of things its hard to be
sure.

2) PSA
http://www.ietf.org/mail-archive/web/dane/current/msg04702.html
http://www.ietf.org/mail-archive/web/dane/current/msg04790.html

There are a few more small things still open in the last mail
from earlier today.

3) Dave Cridland
http://www.ietf.org/mail-archive/web/dane/current/msg04624.html

I think there are still some occurrences of "certificate type"
in section 8, (e.g. 3rd para, p18) so those weren't all fixed.
I think that's the only remaining thing from Dave's review.

4) John Gilmore,
http://www.ietf.org/mail-archive/web/dane/current/msg04635.html

A.1 only has CA examples, what about non CA uses? I didn't see
any reaction to that and it seems like a fair comment.

5) John Gilmore
http://www.ietf.org/mail-archive/web/dane/current/msg04637.html

John thinks there's a bias in sections 8/8.1, but I didn't see
any reaction to that (other than mine, which just said "please
do the right thing, whatever that is")

6) Mark Andrews
http://www.ietf.org/mail-archive/web/dane/current/msg04657.html

Again, not sure if there was follow-up.

7) PHB
http://www.ietf.org/mail-archive/web/dane/current/msg04709.html

Don't mandate client security policy (hardfail). I didn't see
an obvious conclusion reached to make a change or not make a
change.

8) Various on SRV
http://www.ietf.org/mail-archive/web/dane/current/msg04793.html

I think this might need a tweak to the SRV language in 1.3 (and
just suggested one).

Cheers,
Stephen.

_______________________________________________
dane mailing list
dane@ietf.org
https://www.ietf.org/mailman/listinfo/dane



--------------060202030202090405020505--

From yaakov_s@rad.com  Tue May  1 02:24:08 2012
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBF121F862B for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=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 kkSIaxvhGzJ7 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:24:08 -0700 (PDT)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 85BD321F84CD for <ietf@ietf.org>; Tue,  1 May 2012 02:24:06 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 1 May 2012 12:07:58 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Tue, 1 May 2012 12:24:01 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Fred Baker <fred@cisco.com>, IETF-Discussion list <ietf@ietf.org>
Subject: RE: 'Geek' image scares women away from tech industry ? The Register
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: AQHNJtt3jupmR7EDL0CjH0I4Rav/ipazlYqAgABGBICAABh8gIAAte4Q
Date: Tue, 1 May 2012 09:24:00 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9043C2260@EXRAD5.ad.rad.co.il>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <20120501000305.GL335@mip.aaaaa.org> <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com>
In-Reply-To: <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [207.232.33.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A02020A.4F9FABB2.005F,ss=1,fgs=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, 01 May 2012 09:24:08 -0000

> What if teachers were measured on a survey at the end of a semester or a =
year that asked "does teacher <> make <> interesting to you?".

Feynman recollected that when he returned from school his mother never aske=
d him if he answered the teacher's questions correctly,
rather if he asked any interesting questions.

Y(J)S

From daedulus@btconnect.com  Tue May  1 02:33:39 2012
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 E249421F86D4 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.049
X-Spam-Level: 
X-Spam-Status: No, score=-3.049 tagged_above=-999 required=5 tests=[AWL=-2.050, BAYES_50=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 IYeJSLjam1yj for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 02:33:39 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9E621F86CA for <ietf@ietf.org>; Tue,  1 May 2012 02:33:38 -0700 (PDT)
Received: from mail26-db3-R.bigfish.com (10.3.81.249) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Tue, 1 May 2012 09:33:31 +0000
Received: from mail26-db3 (localhost [127.0.0.1])	by mail26-db3-R.bigfish.com (Postfix) with ESMTP id 0DE7A14013F; Tue,  1 May 2012 09:33:31 +0000 (UTC)
X-SpamScore: -28
X-BigFish: PS-28(zz9371Ic89bh542M1432Nzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24h304l)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT010.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail26-db3 (localhost.localdomain [127.0.0.1]) by mail26-db3 (MessageSwitch) id 1335864809144121_26015; Tue,  1 May 2012 09:33:29 +0000 (UTC)
Received: from DB3EHSMHS010.bigfish.com (unknown [10.3.81.249])	by mail26-db3.bigfish.com (Postfix) with ESMTP id CE0321C0076; Tue,  1 May 2012 09:33:27 +0000 (UTC)
Received: from DB3PRD0702HT010.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS010.bigfish.com (10.3.87.110) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 1 May 2012 09:33:25 +0000
Received: from DB3PRD0402HT001.eurprd04.prod.outlook.com (157.55.9.135) by pod51017.outlook.com (10.3.4.178) with Microsoft SMTP Server (TLS) id 14.15.65.3; Tue, 1 May 2012 09:33:27 +0000
Message-ID: <004b01cd2774$cf7edda0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <huubatwork@gmail.com>, <ietf@ietf.org>
References: <CABSMSPVX8vY8fC02h1xGcJorG8i_mJ0ESqJ82w1qqPJgE+MOkQ@mail.gmail.com>, <CBC3A525.CE290%mmorrow@cisco.com><CD5674C3CD99574EBA7432465FC13C1B22726A0A8D@DC-US1MBEX4.global.avaya.com> <4F9EA735.3040009@gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Date: Tue, 1 May 2012 10:31:23 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.55.9.135]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 09:33:40 -0000

----- Original Message -----
From: "Huub van Helvoort" <huubatwork@gmail.com>
To: <ietf@ietf.org>
Sent: Monday, April 30, 2012 4:52 PM

Hi Dale,

You wondered:

>> and btw  my motto:
>>
>> "geek c =E9st chic!"
>
> What responses do you receive to your motto?

That it is spelled wrong...

<tp>
Sad, isn't it?  All that effort on i18e and we still get the basics wrong=
.  Bit
like all that effort I read about on breaking the glass ceiling.

Tom Petch
</tp>





BR, Huub.



From mary.ietf.barnes@gmail.com  Tue May  1 06:45:58 2012
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 9761021E80C8 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 06:45:58 -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.045, 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 YiLnUJTEZaA3 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 06:45:57 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A571121E809C for <ietf@ietf.org>; Tue,  1 May 2012 06:45:57 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3249765vcb.31 for <ietf@ietf.org>; Tue, 01 May 2012 06:45:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rrBUaeWDgMCTCdRx1CL1+WqQRuLIVisbpRPdKnxlqs4=; b=zPG0CBTylAo9iazn7MdJcHXSuv610KVMKqiQfR59Zb+oBIxHAuqCHiBNG4YbNZgR/C igjBbt5aYSVDX6HXPr7jM48T8F7udBQXoz/WXs75EkitsAx594MrQA56bW7DDCbe+rcz 8xJ5nnU+nwJNa0Rryw41NZmdlvEgKhoQO0tgQ9Uy2Cbk374Z+evaX6d8mqkF/kuhEzWI GGK6vg+aTBO3n+Ebg77hzJdxgym7bn1pxYfdVlYxCVG9/HBhyq5+N5Sxd5NI33MckEhV K7FGXC76d0W9TgKUmvxpLgnPLMPvwH5E6oc84mgUxZZjYlrA0C8LhcZQRzB/OrcUGcFD iW2Q==
MIME-Version: 1.0
Received: by 10.52.69.144 with SMTP id e16mr6697758vdu.65.1335879957121; Tue, 01 May 2012 06:45:57 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Tue, 1 May 2012 06:45:57 -0700 (PDT)
In-Reply-To: <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com>
Date: Tue, 1 May 2012 08:45:57 -0500
Message-ID: <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=20cf3071cdce4e89b604bef9ca10
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, 01 May 2012 13:45:58 -0000

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

The article clearly states that women leave for the two reasons you
mentioned, which are certainly the exact same things males deal with, but
you missed a few others that the article notes, specifically and directly
quoted below:

"...lack of real or perceived opportunities for advancement, and uncivil
work environments where women were treated in condescending or patronizing
manners. Only 25 percent of the women who left engineering did so for
family reasons."

Mary

On Tue, May 1, 2012 at 1:51 AM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Apr 30, 2012, at 10:52 PM, Mary Barnes wrote:
>
> Here is an article that does a far better job of explaining the situation
> than I did:
> http://www.todaysengineer.org/2011/May/women-in-engineering.asp
>
> The largest reason women leave engineering is due to the work environment
> and perceived lack of support from colleagues.
>
>
> Interesting, but I don't really get some of the distinctions they are
> making. Women *are not* leaving engineering to spend time with their
> families, but they *are* leaving engineering because of 60-hour weeks and
> having to work weekends.
>
> I'm also not sure that stereotype is still valid. It's the romantic image
> of a technology start-up trying to get a product out before funding runs
> out, but most engineers won't work in those. Most will work at established
> companies or in corporate IT, and in those places, the 60-hour week is
> either rare or non-existent. There may be other things that scare women
> away from IT/engineering jobs, but there are plenty of those available that
> do not require that type of having no life.
>
> Yoav
>
>

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

The article clearly states that women leave for the two reasons you mention=
ed, which are certainly the exact same things males deal with, but you miss=
ed a few others that the article notes, specifically and directly quoted be=
low:<div>
<br><div><span class=3D"Apple-style-span" style=3D"font-family:georgia;font=
-size:13px;line-height:19px">&quot;...lack of real or perceived opportuniti=
es for advancement, and uncivil work environments where women were treated =
in condescending or patronizing manners. Only 25 percent of the women who l=
eft engineering did so for family reasons.&quot;</span></div>
<div><font class=3D"Apple-style-span" face=3D"georgia"><span class=3D"Apple=
-style-span" style=3D"line-height:19px"><br></span></font></div><div><span =
class=3D"Apple-style-span" style=3D"line-height:19px"><font class=3D"Apple-=
style-span" face=3D"arial, helvetica, sans-serif">Mary</font></span></div>
<div><font class=3D"Apple-style-span" face=3D"georgia"><span class=3D"Apple=
-style-span" style=3D"line-height:19px"><br></span></font><div class=3D"gma=
il_quote">On Tue, May 1, 2012 at 1:51 AM, Yoav Nir <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ynir@checkpoint.com" target=3D"_blank">ynir@checkpoint.com<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div cla=
ss=3D"im"><br><div><div>On Apr 30, 2012, at 10:52 PM, Mary Barnes wrote:</d=
iv><br>
<blockquote type=3D"cite">Here is an article that does a far better job of =
explaining the situation than I did:<div><a href=3D"http://www.todaysengine=
er.org/2011/May/women-in-engineering.asp" target=3D"_blank">http://www.toda=
ysengineer.org/2011/May/women-in-engineering.asp</a></div>

<div><br></div><div>The largest reason women leave engineering is due to th=
e work environment and perceived lack of support from colleagues. =A0=A0</d=
iv></blockquote><br></div></div><div>Interesting, but I don&#39;t really ge=
t some of the distinctions they are making. Women *are not* leaving enginee=
ring to spend time with their families, but they *are* leaving engineering =
because of 60-hour weeks and having to work weekends.</div>
<div><br></div><div>I&#39;m also not sure that stereotype is still valid. I=
t&#39;s the romantic image of a technology start-up trying to get a product=
 out before funding runs out, but most engineers won&#39;t work in those. M=
ost will work at established companies or in corporate IT, and in those pla=
ces, the 60-hour week is either rare or non-existent. There may be other th=
ings that scare women away from IT/engineering jobs, but there are plenty o=
f those available that do not require that type of having no life.</div>
<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Yoav</di=
v><br></font></span></div></blockquote></div><br></div></div>

--20cf3071cdce4e89b604bef9ca10--

From scott.brim@gmail.com  Tue May  1 06:56:11 2012
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 420A821E8281 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 06:56:11 -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 BZVUp08fK3MJ for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 06:56:10 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF5B21E81D6 for <ietf@ietf.org>; Tue,  1 May 2012 06:56:10 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so1692832pbc.31 for <ietf@ietf.org>; Tue, 01 May 2012 06:56: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=czI5pxFWIc8IPO96QC1gclmW45deRAaYdm8L8yS0bDQ=; b=lG2cTjKmT3JappXpKQU3q5c00qyhB5t4kGGEPGpstSYpxigj9VkP/hfAWM7n2OUbFY G0lK7kqLvt3HtjlpiwS5/QrEtP+6iLWbiwxO78+PQQ3UD3KBqreiJgPtn6ISK34xV9Gm 0WhK6FC374jqmbjJtwoaX2RnHCfX0z9XLmer3oEI6TuEBYUbD2+/+WHboapuLpsjMUjb 4fgow8LdSyzFy2LjA6rkQzddBqmIBtohfei8V5hSIQN/Fq5HEKVQXlhsmSjnc4Xl1Rlv FO/7svcxjBOzxQjLZFHWU/gggykrEDndWYiPdrY0xiOAt70heWo6+E2yEqMT6yc9ja73 v6iw==
Received: by 10.68.240.135 with SMTP id wa7mr57542717pbc.7.1335880569991; Tue, 01 May 2012 06:56:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.24.136 with HTTP; Tue, 1 May 2012 06:55:49 -0700 (PDT)
In-Reply-To: <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 1 May 2012 09:55:49 -0400
Message-ID: <CAPv4CP_RZJxb2EpZBo7RUi7Dok=T5G9qOb_zezSeudJB4dr7uA@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 13:56:11 -0000

On Tue, May 1, 2012 at 09:45, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
> The article clearly states that women leave for the two reasons you
> mentioned, which are certainly the exact same things males deal with, but
> you missed a few others that the article notes, specifically and directly
> quoted below:
>
> "...lack of real or perceived opportunities for advancement, and uncivil
> work environments where women were treated in condescending or patronizing
> manners. Only 25 percent of the women who left engineering did so for family
> reasons."
>
> Mary

I conjecture there are few work environments where these are NOT the case.

From mmorrow@cisco.com  Tue May  1 07:00:13 2012
Return-Path: <mmorrow@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 5D19921E82C5 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 07:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.901
X-Spam-Level: 
X-Spam-Status: No, score=-9.901 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 O7vAZZXatN7s for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 07:00:11 -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 0EC7B21E82DC for <ietf@ietf.org>; Tue,  1 May 2012 07:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mmorrow@cisco.com; l=6125; q=dns/txt; s=iport; t=1335880811; x=1337090411; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version; bh=g7usPfGKevFf8EozfP+LTU89RllX306py7UWaloCThw=; b=XOnCtt7AQjJ1t6K+aYuX5b86vdDap4w9LLF9qqooCYKICjVkTj+R0/GH 5jq9Q8xcz14kLpvDquijsfGX6hlRpbH/pzhnXzEaD+EfJOrNnQY1dZBEO ExOwWwtxwG65fOqO2LDfedHGtzc5vYfkXs8EQT0y3Vh6UBkx0EyDMOaxm g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsUFABLsn0+Q/khM/2dsb2JhbABEgkatIYF7gQaBB4IJAQEBAwESASo8BQ0BCBhPNgEBBAENBQkQCYddAwYFC5omlX0NiVOKB4cCBIgwNI0aiz+DGoFpgwg
X-IronPort-AV: E=Sophos;i="4.75,510,1330905600"; d="scan'208,217";a="72162751"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 01 May 2012 14:00:09 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q41E09eP022825; Tue, 1 May 2012 14:00:09 GMT
Received: from xmb-ams-110.cisco.com ([144.254.74.85]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 May 2012 16:00:09 +0200
Received: from 10.155.58.212 ([10.155.58.212]) by XMB-AMS-110.cisco.com ([144.254.74.85]) via Exchange Front-End Server email.cisco.com ([128.107.191.79]) with Microsoft Exchange Server HTTP-DAV ;  Tue,  1 May 2012 14:00:09 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Tue, 01 May 2012 07:00:06 -0700
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Monique Morrow <mmorrow@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Yoav Nir <ynir@checkpoint.com>
Message-ID: <CBC53A76.CE3FA%mmorrow@cisco.com>
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: Ac0norZIvWDPJTU0nU6go0pJp0MKqQ==
In-Reply-To: <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3418700407_41403"
X-OriginalArrivalTime: 01 May 2012 14:00:09.0712 (UTC) FILETIME=[B87EDF00:01CD27A2]
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, 01 May 2012 14:00:13 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3418700407_41403
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

One of the points I discussed in NYC last week was also the role of media
and what is depicted in film, TV and so on wrt girls-women, a topic of the
Miss Representation initiative:

http://www.missrepresentation.org/

Monique


On 5/1/12 6:45 AM, "Mary Barnes" <mary.ietf.barnes@gmail.com> wrote:

> The article clearly states that women leave for the two reasons you menti=
oned,
> which are certainly the exact same things males deal with, but you missed=
 a
> few others that the article notes, specifically and directly quoted below=
:
>=20
> "...lack of real or perceived opportunities for advancement, and uncivil =
work
> environments where women were treated in condescending or patronizing man=
ners.
> Only 25 percent of the women who left engineering did so for family reaso=
ns."
>=20
> Mary
>=20
> On Tue, May 1, 2012 at 1:51 AM, Yoav Nir <ynir@checkpoint.com> wrote:
>>=20
>> On Apr 30, 2012, at 10:52 PM, Mary Barnes wrote:
>>=20
>>> Here is an article that does a far better job of explaining the situati=
on
>>> than I did:
>>> http://www.todaysengineer.org/2011/May/women-in-engineering.asp
>>>=20
>>> The largest reason women leave engineering is due to the work environme=
nt
>>> and perceived lack of support from colleagues. =A0=A0
>>=20
>> Interesting, but I don't really get some of the distinctions they are ma=
king.
>> Women *are not* leaving engineering to spend time with their families, b=
ut
>> they *are* leaving engineering because of 60-hour weeks and having to wo=
rk
>> weekends.
>>=20
>> I'm also not sure that stereotype is still valid. It's the romantic imag=
e of
>> a technology start-up trying to get a product out before funding runs ou=
t,
>> but most engineers won't work in those. Most will work at established
>> companies or in corporate IT, and in those places, the 60-hour week is e=
ither
>> rare or non-existent. There may be other things that scare women away fr=
om
>> IT/engineering jobs, but there are plenty of those available that do not
>> require that type of having no life.
>>=20
>> Yoav
>>=20
>=20
>=20


--B_3418700407_41403
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: 'Geek' image scares women away from tech industry ? The Register=
</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'>One of the points I discussed in NYC last week was also the role of media =
and what is depicted in film, TV and so on wrt girls-women, a topic of the M=
iss Representation initiative:<BR>
<BR>
<a href=3D"http://www.missrepresentation.org/">http://www.missrepresentation.=
org/</a><BR>
<BR>
Monique<BR>
<BR>
<BR>
On 5/1/12 6:45 AM, &quot;Mary Barnes&quot; &lt;<a href=3D"mary.ietf.barnes@gm=
ail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'>The article clearly states that women leave for =
the two reasons you mentioned, which are certainly the exact same things mal=
es deal with, but you missed a few others that the article notes, specifical=
ly and directly quoted below:<BR>
<BR>
</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Georgia, Times New Roman"><SPAN ST=
YLE=3D'font-size:10pt'>&quot;...lack of real or perceived opportunities for ad=
vancement, and uncivil work environments where women were treated in condesc=
ending or patronizing manners. Only 25 percent of the women who left enginee=
ring did so for family reasons.&quot;<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Georgia, Times New Roman"><SPAN STYLE=3D'fon=
t-size:11pt'><BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Arial">Mary<BR>
</FONT><FONT FACE=3D"Georgia, Times New Roman"><BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial">On Tue, May 1, 2012 =
at 1:51 AM, Yoav Nir &lt;<a href=3D"ynir@checkpoint.com">ynir@checkpoint.com</=
a>&gt; wrote:<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Calibri,=
 Verdana, Helvetica, Arial"><BR>
On Apr 30, 2012, at 10:52 PM, Mary Barnes wrote:<BR>
<BR>
</FONT></SPAN><BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Calibri,=
 Verdana, Helvetica, Arial">Here is an article that does a far better job of=
 explaining the situation than I did:<BR>
<a href=3D"http://www.todaysengineer.org/2011/May/women-in-engineering.asp">h=
ttp://www.todaysengineer.org/2011/May/women-in-engineering.asp</a><BR>
<BR>
The largest reason women leave engineering is due to the work environment a=
nd perceived lack of support from colleagues. =A0=A0<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Calibri=
, Verdana, Helvetica, Arial"><BR>
Interesting, but I don't really get some of the distinctions they are makin=
g. Women *are not* leaving engineering to spend time with their families, bu=
t they *are* leaving engineering because of 60-hour weeks and having to work=
 weekends.<BR>
<BR>
I'm also not sure that stereotype is still valid. It's the romantic image o=
f a technology start-up trying to get a product out before funding runs out,=
 but most engineers won't work in those. Most will work at established compa=
nies or in corporate IT, and in those places, the 60-hour week is either rar=
e or non-existent. There may be other things that scare women away from IT/e=
ngineering jobs, but there are plenty of those available that do not require=
 that type of having no life.<BR>
<FONT COLOR=3D"#888888"><BR>
Yoav<BR>
<BR>
</FONT></FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"=
Calibri, Verdana, Helvetica, Arial"><BR>
<BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>


--B_3418700407_41403--


From warren@kumari.net  Tue May  1 07:32:33 2012
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 DC78521E8018; Tue,  1 May 2012 07:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.525
X-Spam-Level: 
X-Spam-Status: No, score=-106.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 H5yd23Q7-ebv; Tue,  1 May 2012 07:32:33 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 4B94921E800F; Tue,  1 May 2012 07:32:32 -0700 (PDT)
Received: from dhcp-172-19-119-246.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 9235E1B402CA; Tue,  1 May 2012 10:32:31 -0400 (EDT)
Subject: Re: [IETF] Re: 'Geek' image scares women away from tech industry ? The Register
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <OF5ABF8912.F0CB0BF0-ON852579F0.00759884-852579F0.007634F8@csc.com>
Date: Tue, 1 May 2012 10:32:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FD0486F-5B3D-463B-9120-B4F6E5FA4B10@kumari.net>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <OF5ABF8912.F0CB0BF0-ON852579F0.00759884-852579F0.007634F8@csc.com>
To: Janet P Gunn <jgunn6@csc.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf-bounces@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 14:32:34 -0000

On Apr 30, 2012, at 5:31 PM, Janet P Gunn wrote:

> My own anecdotes.=20
>=20
> Yes, it starts early.=20
>=20
> When I was 3 I announced that I was going to be a physicist when I =
grew up.  WHY?=20
>=20
> 1 - a physicist has a chair that  is on WHEELS, and spins ROUND and =
ROUND=20
> 2 - a physicist has a blackboard with COLORED CHALK=20
> 3 (and MOST important) a physicist has a CANDY machine in the hall =
outside his office.=20

Hmmm... when I was young I wanted to be a garbage man... then one day I =
realized I didn't own the correct gloves, so I decided I would a doctor =
instead...

Apparently that fact that I would A: be able to buy garbage man gloves =
(or get some provided) and B: doctors also need gloves completely didn't =
occur to me...

:-P

W


>=20
> Well, I didn't become a physicist, but those features certainly put =
technology in a good light from an early age.!!=20
>=20
> Second, while the statistics may say something else, I find MORE =
WOMEN, in MORE RESPECTED positions, at IETF than in my work environment.
>=20
> Janet
>=20
>=20
> ietf-bounces@ietf.org wrote on 04/30/2012 10:13:50 AM:
>=20
> > Mary Barnes <mary.ietf.barnes@gmail.com>=20
> > Sent by: ietf-bounces@ietf.org
> >=20
> > 04/30/2012 10:13 AM=20
> >=20
> > To=20
> >=20
> > Riccardo Bernardini <framefritti@gmail.com>=20
> >=20
> > cc=20
> >=20
> > IETF discussion list <ietf@ietf.org>=20
> >=20
> > Subject=20
> >=20
> > Re: 'Geek' image scares women away from tech industry ? The Register=20=

> >=20
> > Yes, the article is far from complete.  But, your antecdote only=20
> > goes to show your own bias towards women in science and engineering=20=

> > in general.  By the time most females reach high school they have=20
> > already been conditioned that girls aren't as good as boys in math=20=

> > and science. There's a far amount of studies showing this - at least
> > in the US.  As Monique said it is a very complex issue.  Some of it=20=

> > starts at home and it starts extremely early.  It's far more common=20=

> > for girls to be told they are pretty rather than smart.  They have=20=

> > found some physiologic reasons that do influence math abilities -=20
> > those with "math brains" tend to have higher levels of testosterone.=20=

> > That all said, it still doesn't explain why the percentage of women=20=

> > active in the IETF is less than the percentage of women that are in=20=

> > the field. But it might have something to do with IETFers sharing=20
> > your perspective that women just aren't interested. =20
> > Regards,
> > Mary.=20
> >


From ron@debian.org  Mon Apr 30 18:40:43 2012
Return-Path: <ron@debian.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 AF2A521E80F4; Mon, 30 Apr 2012 18:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level: 
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=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 cu2obWOmrXZM; Mon, 30 Apr 2012 18:40:43 -0700 (PDT)
Received: from ipmail06.adl6.internode.on.net (unknown [IPv6:2001:44b8:8060:ff02:300:1:6:6]) by ietfa.amsl.com (Postfix) with ESMTP id B8FEB21E8011; Mon, 30 Apr 2012 18:40:42 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAGQ+n095LXH5/2dsb2JhbABEr2aCf4EIggkBAQU6HCMQCw4KIwsUGA0kiB+6NZAsYwSIYoUvh2wBkEKCeA
Received: from ppp121-45-113-249.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([121.45.113.249]) by ipmail06.adl6.internode.on.net with ESMTP; 01 May 2012 11:10:40 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 68A224F8F3; Tue,  1 May 2012 11:10:38 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rcjKB0XYAb4z; Tue,  1 May 2012 11:10:37 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id C8FD54F8FE; Tue,  1 May 2012 11:10:37 +0930 (CST)
Date: Tue, 1 May 2012 11:10:37 +0930
From: Ron <ron@debian.org>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-ietf-codec-opus-12.txt> (Definition of the Opus Audio Codec) to Proposed Standard
Message-ID: <20120501014037.GA18009@audi.shelbyville.oz>
References: <6.2.5.6.2.20120430120153.0947ed48@resistor.net> <CBC4E0F3.867E4%stewe@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CBC4E0F3.867E4%stewe@stewe.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Tue, 01 May 2012 09:05:48 -0700
Cc: SM <sm@resistor.net>, "codec-chairs@tools.ietf.org" <codec-chairs@tools.ietf.org>, "codec@ietf.org" <codec@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, 01 May 2012 01:40:43 -0000

Hi Stephan,

On Mon, Apr 30, 2012 at 10:53:13PM +0000, Stephan Wenger wrote:
> The question of whether a section in the subject doc is
> the right place for such a grant has not yet been answered.
> My view on the latter: it's not.  One issue of having such a notice is
> that it expressly allows derivative work, possibly WITHOUT removing the
> IETF boilerplate and the TLP copyright notice first.

Except that the additional grant explicitly requires that:

 "redistributed modified works do not contain misleading author, version,
  name of work, or endorsement information."

And my understanding is that the sort of misrepresentations which you suggest
are already well protected against in established law.  So I don't think that
this would weaken the IETF's position in the event of such a thing happening,
and I'm not aware of any such problem occurring with any of the RFCs that are
already published containing such a grant.  Similarly there exist other RFCs
which already have external grants too, and there has been no hint of trouble
or an inability to prevent it if it arose with those either, has there?

If this clause becomes a blocker, then we should simply remove it, but in that
case it would be good to have clear reasons why it became a blocker, since the
things you say you fear here, I see as already being prohibited anyway.


I agree with you that this is an entirely separate issue to the validity or
other implications of any of the IPR claims though.  But on that note, have
you had any clarification from Huawei as to whether they believe their newly
acquired patent actually does read on this technology?  Last I had heard on
that there was some doubt and they were still studying it?  It would be nice
to have them officially clear that up.

Cheers,
Ron



From ron@debian.org  Tue May  1 01:41:13 2012
Return-Path: <ron@debian.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 753D621F86D4; Tue,  1 May 2012 01:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level: 
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=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 UbWFe26rwips; Tue,  1 May 2012 01:41:13 -0700 (PDT)
Received: from ipmail06.adl2.internode.on.net (unknown [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by ietfa.amsl.com (Postfix) with ESMTP id 9083421F86D3; Tue,  1 May 2012 01:41:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAByhn095LXH5/2dsb2JhbABErwJlgwCBCIIJAQEFOhwjEAsYIwsUGA0kJ4d4ui+QImMEiGKFL4dsAZBCgng
Received: from ppp121-45-113-249.lns20.adl6.internode.on.net (HELO audi.shelbyville.oz) ([121.45.113.249]) by ipmail06.adl2.internode.on.net with ESMTP; 01 May 2012 18:11:10 +0930
Received: from localhost (localhost [127.0.0.1]) by audi.shelbyville.oz (Postfix) with ESMTP id 9A8BC4F8F3; Tue,  1 May 2012 18:11:08 +0930 (CST)
X-Virus-Scanned: Debian amavisd-new at audi.shelbyville.oz
Received: from audi.shelbyville.oz ([127.0.0.1]) by localhost (audi.shelbyville.oz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EjQfgvkuUomE; Tue,  1 May 2012 18:11:07 +0930 (CST)
Received: by audi.shelbyville.oz (Postfix, from userid 1000) id 7DA934F8FE; Tue,  1 May 2012 18:11:07 +0930 (CST)
Date: Tue, 1 May 2012 18:11:07 +0930
From: Ron <ron@debian.org>
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-codec-opus-12.txt> (Definition of the Opus Audio Codec) to Proposed Standard
Message-ID: <20120501084107.GB18009@audi.shelbyville.oz>
References: <6.2.5.6.2.20120430120153.0947ed48@resistor.net> <CBC4E0F3.867E4%stewe@stewe.org> <6.2.5.6.2.20120430223624.0c706828@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20120430223624.0c706828@resistor.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Tue, 01 May 2012 09:05:52 -0700
Cc: codec@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, 01 May 2012 08:41:13 -0000

On Mon, Apr 30, 2012 at 11:28:59PM -0700, SM wrote:
> At 18:40 30-04-2012, Ron wrote:
> >If this clause becomes a blocker, then we should simply remove it, but in that
> >case it would be good to have clear reasons why it became a blocker, since the
> >things you say you fear here, I see as already being prohibited anyway.
> 
> The text in Section 10 is ambiguous.
> 
> Given all the efforts that went into RFC 6569, it's odd to see the
> text being discussed during the Last Call instead of the WGLC.

Nobody raised any questions about it to discuss until Robert's AD review.
And since it's essentially the same text as had been included in previously
published RFCs, that didn't seem particularly surprising either.

Whatever resolution we arrive at over this, it doesn't effect the substantive
content of the proposed standard. And the question in question does seem like
something that's out of scope for the CODEC WG to answer in general anyway,
beyond giving the rationale for adding it in this case.

I'm happy to defer to whatever the broader community thinks will work best
on this one.

 Best,
 Ron



From hartmans@mit.edu  Tue May  1 09:11:29 2012
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 7A88521E82B0; Tue,  1 May 2012 09:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.938
X-Spam-Level: 
X-Spam-Status: No, score=-102.938 tagged_above=-999 required=5 tests=[AWL=-0.673, 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 StO+7LWroRep; Tue,  1 May 2012 09:11:28 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6D90B21E8271; Tue,  1 May 2012 09:11:12 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id C7B81201CB; Tue,  1 May 2012 12:07:10 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id D4C5A4769; Tue,  1 May 2012 12:10:58 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ron <ron@debian.org>
Subject: Re: Last Call: <draft-ietf-codec-opus-12.txt> (Definition of the Opus Audio Codec) to Proposed Standard
References: <6.2.5.6.2.20120430120153.0947ed48@resistor.net> <CBC4E0F3.867E4%stewe@stewe.org> <20120501014037.GA18009@audi.shelbyville.oz>
Date: Tue, 01 May 2012 12:10:58 -0400
In-Reply-To: <20120501014037.GA18009@audi.shelbyville.oz> (ron@debian.org's message of "Tue, 1 May 2012 11:10:37 +0930")
Message-ID: <tsllilbvq3x.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: SM <sm@resistor.net>, "codec@ietf.org" <codec@ietf.org>, "codec-chairs@tools.ietf.org" <codec-chairs@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: Tue, 01 May 2012 16:11:29 -0000

For what it's worth, I support authors' (and this is actually one of the
few times I mean that rather than editors) right to make such a grant. I
believe the community is significantly better served by having
additional grants in the RFC, and strongly support us permitting them. I
believe our current policy allows them; if the community consensus is
that is not the case I support changes to the policy up to an
appropriate BCP to permit this.

From ynir@checkpoint.com  Tue May  1 09:13:49 2012
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 4C88621E826F for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level: 
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[AWL=-9.963, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, URIBL_BLACK=20]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19WSbvKWYgyA for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:13:48 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA0F21E8134 for <ietf@ietf.org>; Tue,  1 May 2012 09:13:46 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q41GDhiu014570;  Tue, 1 May 2012 19:13:43 +0300
X-CheckPoint: {4FA019A0-1-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 1 May 2012 19:13:43 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 1 May 2012 19:13:42 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Tue, 1 May 2012 19:12:41 +0300
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: Ac0ntWAQ8T+Sll2hSCWT9sviXGeAKw==
Message-ID: <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
In-Reply-To: <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 113fcd7d1394cec1a09e9a6606cc8b4d1307afe183
Content-Type: multipart/alternative; boundary="_000_C6E91163E7C84813A1B54F2D7155E35Acheckpointcom_"
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
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, 01 May 2012 16:13:49 -0000

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


On May 1, 2012, at 4:45 PM, Mary Barnes wrote:

The article clearly states that women leave for the two reasons you mention=
ed, which are certainly the exact same things males deal with, but you miss=
ed a few others that the article notes, specifically and directly quoted be=
low:

"...lack of real or perceived opportunities for advancement, and uncivil wo=
rk environments where women were treated in condescending or patronizing ma=
nners. Only 25 percent of the women who left engineering did so for family =
reasons."


Well, it says this:
   "The common perception is that women are leaving for taking care of thei=
r families," says Fouad. "But that's clearly not true. They left the profes=
sion for organizational culture reasons."

And then this:
   Among the common factors that women cited as their reasons for leaving t=
he profession were too much travel, working too many hours, lack of real or=
 perceived opportunities for advancement, and uncivil work environments whe=
re women were treated in condescending or patronizing manners. Only 25 perc=
ent of the women who left engineering did so for family reasons.

So on the one hand they claim that women are not leaving to take care of th=
eir families, but on the other the first two correct reasons they mention a=
re too much travel and too many hours. I think these two are pretty much th=
e same, and the primary reason why someone (male or female) would object to=
 travel and long hours is because it takes time away from family. Sure, it'=
s possible they don't want to work long hours so that they can spend more t=
ime playing online games (http://iqu.com/blog/women-dominate-mobile-game-sp=
ending) or gambling online (http://ezinearticles.com/?UK-Online-Gambling-Do=
minated-by-Women-Players&id=3D6934242), but I suspect that few people are q=
uitting their jobs to spend more time on gaming. I could be wrong. IOW I do=
n't see the difference between not wanting to spend too much time at work a=
nd wanting to spend more time with your family.


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; " class=3D""><br class=3D"">=
<div><div class=3D"">On May 1, 2012, at 4:45 PM, Mary Barnes wrote:</div><b=
r class=3D"Apple-interchange-newline"><blockquote type=3D"cite">The article=
 clearly states that women leave for the two reasons you mentioned, which a=
re certainly the exact same things males deal with, but you missed a few ot=
hers that the article notes, specifically and directly quoted below:<div cl=
ass=3D"">
<br class=3D""><div class=3D""><span style=3D"font-family:georgia;font-size=
:13px;line-height:19px" class=3D"Apple-style-span">"...lack of real or perc=
eived opportunities for advancement, and uncivil work environments where wo=
men were treated in condescending or patronizing manners. Only 25 percent o=
f the women who left engineering did so for family reasons."</span></div>
</div></blockquote><br class=3D""></div><div><span style=3D"font-family: ge=
orgia; font-size: 13px; line-height: 19px; " class=3D"Apple-style-span"><br=
></span></div><div><span style=3D"font-family: georgia; font-size: 13px; li=
ne-height: 19px; " class=3D"Apple-style-span">Well, it says this:</span></d=
iv><div><span style=3D"font-family: georgia; font-size: 13px; line-height: =
19px; " class=3D"Apple-style-span">&nbsp; &nbsp;"The common perception is t=
hat women are leaving for taking care of their families," says Fouad. "But =
that's clearly not true. They left the profession for organizational cultur=
e reasons."</span></div><div><span style=3D"font-family: georgia; font-size=
: 13px; line-height: 19px; " class=3D"Apple-style-span"><br></span></div><d=
iv><span style=3D"font-family: georgia; font-size: 13px; line-height: 19px;=
 " class=3D"Apple-style-span">And then this:</span></div><div><span style=
=3D"font-family: georgia; font-size: 13px; line-height: 19px; " class=3D"Ap=
ple-style-span">&nbsp; &nbsp;</span><span class=3D"Apple-style-span" style=
=3D"font-family: georgia; font-size: 13px; line-height: 19px; ">Among the c=
ommon factors that women cited as their reasons for leaving the profession =
were too much travel, working too many hours, lack of real or perceived opp=
ortunities for advancement, and uncivil work environments where women were =
treated in condescending or patronizing manners. Only 25 percent of the wom=
en who left engineering did so for family reasons.</span></div><div><span c=
lass=3D"Apple-style-span" style=3D"font-family: georgia; font-size: 13px; l=
ine-height: 19px; "><br></span></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: georgia; font-size: 13px; line-height: 19px; ">So on =
the one hand they claim that women are not leaving to take care of their fa=
milies, but on the other the first two correct reasons they mention are too=
 much travel and too many hours. I think these two are pretty much the same=
, and the primary reason why someone (male or female) would object to trave=
l and long hours is because it takes time away from family. Sure, it's poss=
ible they don't want to work long hours so that they can spend more time pl=
aying online games (<a href=3D"http://iqu.com/blog/women-dominate-mobile-ga=
me-spending">http://iqu.com/blog/women-dominate-mobile-game-spending</a>) o=
r gambling online (<a href=3D"http://ezinearticles.com/?UK-Online-Gambling-=
Dominated-by-Women-Players&amp;id=3D6934242">http://ezinearticles.com/?UK-O=
nline-Gambling-Dominated-by-Women-Players&amp;id=3D6934242</a>), but I susp=
ect that few people are quitting their jobs to spend more time on gaming. I=
 could be wrong. IOW I don't see the difference between not wanting to spen=
d too much time at work and wanting to spend more time with your family.</s=
pan></div><br class=3D""></body></html>=

--_000_C6E91163E7C84813A1B54F2D7155E35Acheckpointcom_--

From randy_presuhn@mindspring.com  Tue May  1 09:37:13 2012
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 62B5921F8899 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[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 tUI3hQxYhMsF for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:37:12 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id 48C7B21F883D for <ietf@ietf.org>; Tue,  1 May 2012 09:37:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=FQCYbX/2flLzzX2bsW4zOJ6VUlCtadgnKhulGNJPS1vfIUjoXzFJy3nDlKkD71f8; 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 [99.23.161.183] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1SPG4b-0007dq-Vj for ietf@ietf.org; Tue, 01 May 2012 12:37:10 -0400
Message-ID: <002901cd27b8$e4a819a0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF-Discussion list" <ietf@ietf.org>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com><CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com><0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com><CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Date: Tue, 1 May 2012 09:38:51 -0700
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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8882951211ce6890f889503495b5acc9b093c7916ae6cec0d72350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.183
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 16:37:13 -0000

Hi -

> From: "Yoav Nir" <ynir@checkpoint.com>
> To: "Mary Barnes" <mary.ietf.barnes@gmail.com>
> Cc: "IETF-Discussion list" <ietf@ietf.org>
> Sent: Tuesday, May 01, 2012 9:12 AM
> Subject: Re: 'Geek' image scares women away from tech industry ? The Register
...
> IOW I don't see the difference between not wanting to spend too
> much time at work and wanting to spend more time with your family.

I think the notion that one's life is limited to work and family is a
great example of what makes for an unsupportive environment,
regardless of one's gender.  I have no scientific study to back me
up, but my experience has been that men (myself included at times)
tend to be fairly clueless about what makes for an "uncivil work
environment", and in particular, privilege tends to make us oblivious
to "condescending or patronizing" behaviour.

Randy


From melinda.shore@gmail.com  Tue May  1 09:54:15 2012
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 62D4321E8323 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:54:15 -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=0.000,  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 mJEJCt7yHsrg for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 09:54:14 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C307C21E80F7 for <ietf@ietf.org>; Tue,  1 May 2012 09:54:14 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so2354443ghb.31 for <ietf@ietf.org>; Tue, 01 May 2012 09:54:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=I2KBPRGN1+G7rGLMlYzfjwAjMbN8sQ0rzBOcvjpVLos=; b=IHcpuZskWWwp9IRH5iAjVsrEli3MZ9hkbm65DVgwLGrEDO9J+1SGVnf82SjJBoHuCj FTSGoCbEtBwPZfSParDQcOV+VOf2h9ABulzYqEvl76QYsYg08XEhWHgUsE/5b0BzvHjO I1+wffNVXfvwfFhtRUIFX3c7D/JfLBB6cTNVsyk2CcbS9KU8tRt72VjqECVJN4BUmuuP svmdgay/pC0IveUSGTmcyKXMIYQLT3ueLTroK+NZ22nMndtZS4O9D883wPxa6q2ZES6U LF6q0zDoTbR/aadIXWeQSEJIt3aXkcqwqA9acRwtj1+7UhLpTwCLir1qhEyCOiHTUxxV 6Pmg==
Received: by 10.68.220.2 with SMTP id ps2mr59707541pbc.109.1335891254080; Tue, 01 May 2012 09:54:14 -0700 (PDT)
Received: from polypro.local (66-230-101-239-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.239]) by mx.google.com with ESMTPS id wo8sm19603962pbc.0.2012.05.01.09.54.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 09:54:13 -0700 (PDT)
Message-ID: <4FA01532.2040708@gmail.com>
Date: Tue, 01 May 2012 08:54:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
In-Reply-To: <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 16:54:15 -0000

On 5/1/12 8:12 AM, Yoav Nir wrote:
> Well, it says this:
>     "The common perception is that women are leaving for taking care of
> their families," says Fouad. "But that's clearly not true. They left the
> profession for organizational culture reasons."
>
> And then this:
> Among the common factors that women cited as their reasons for leaving
> the profession were too much travel, working too many hours, lack of
> real or perceived opportunities for advancement, and uncivil work
> environments where women were treated in condescending or patronizing
> manners. Only 25 percent of the women who left engineering did so for
> family reasons.

Four reasons were listed, and you're focusing on two of them.  We really
don't know how those reasons were distributed.

It's certainly possible that the men who are being dismissive, here, or
who are saying that the real issue is that women don't *really* want
technology careers or are somehow unworthy are part of the problem.

Melinda

From john-ietf@jck.com  Tue May  1 10:25:01 2012
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 5C0C821E82E7 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxfQRGZyannO for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:25:00 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 659AD21E81CF for <ietf@ietf.org>; Tue,  1 May 2012 10:25:00 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SPGjt-0004w6-EI; Tue, 01 May 2012 13:19:49 -0400
Date: Tue, 01 May 2012 13:24:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Brim <scott.brim@gmail.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Message-ID: <67A16A34D3CEE69C3824DE03@PST.JCK.COM>
In-Reply-To: <CAPv4CP_RZJxb2EpZBo7RUi7Dok=T5G9qOb_zezSeudJB4dr7uA@mail.gmail.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <CAPv4CP_RZJxb2EpZBo7RUi7Dok=T5G9qOb_zezSeudJB4dr7uA@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 17:25:01 -0000

--On Tuesday, May 01, 2012 09:55 -0400 Scott Brim
<scott.brim@gmail.com> wrote:

>> "...lack of real or perceived opportunities for advancement,
>> and uncivil work environments where women were treated in
>> condescending or patronizing manners. Only 25 percent of the
>> women who left engineering did so for family reasons."
>> 
>> Mary
> 
> I conjecture there are few work environments where these are
> NOT the case.

And so?   

I agree with "few", but "few" is not zero.  It is possible to
have work environments where that doesn't happen.  One could
take "few" as "ok, we can give up now", but I don't think that
is a satisfactory inference (and can't imagine, knowing you,
that you do either).

The question for me is what we can and/or should usefully do
about the issue in the IETF.  Partially because I've observed
over the years that it is much easier to change behavior than to
change attitudes but that changing behavior often requires the
ability to apply sanctions, I'm pretty pessimistic about trying
to use the IETF to get ahead of the industrial / work
environment situation.  

I do think we should be more aggressive about leadership
development activities, not just with occasional newcomers
orientations but by making more mentoring opportunities
available to relative newcomers (of both genders).  And I think,
with some reinforcement from some of the articles and
discussions on this list, that it is probably more practical to
focus efforts on retention and advancement rather than
recruitment.  If nothing else, we probably don't have a lot of
control over recruitment given organizational and support
decisions.

best,
    john




From sant9442@gmail.com  Tue May  1 10:32:32 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4234C21F8B8B for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.938
X-Spam-Level: 
X-Spam-Status: No, score=-0.938 tagged_above=-999 required=5 tests=[AWL=2.662,  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 iRc+jv+oeh2o for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:32:31 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1063D21F8B8A for <ietf@ietf.org>; Tue,  1 May 2012 10:32:31 -0700 (PDT)
Received: by yenr9 with SMTP id r9so444837yen.31 for <ietf@ietf.org>; Tue, 01 May 2012 10:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=QdiUawNGg5n0jCEmHIgGlow9rUJU5nXYn4FB8tx+lYs=; b=hPNnfXrO4CE2gZG0OWH+9WJelTaCipyroYIngDUaEjZnMbbfolEB6d4wfnCRmohoN2 OWxur0VR+O3klhEI/5sSEdtsb7NAuPOCBoRwEy2nh9DMgghSHXneTpsdDVdHXtzBVz4j A7aXHMeyiq6uOI9+tq+g4xR1WZw/bPsJbYj5H7OtU7XhOC9L5cl36cjlY7xaQ8cLn0R7 SCIVbnhr76k4ZcwmY/e+m7nIiK2qReIXgrXxOYTDLyqkUlT3AS8yQ8o2BqvgZFXoE8NZ T79TgbyQliUteuCgczYQkaTRG1Rbh+Ccgu8o5XA/SxeW7/1pJfXemoFCC72TQTPl0dDF VkPg==
Received: by 10.236.184.202 with SMTP id s50mr26953583yhm.84.1335893550555; Tue, 01 May 2012 10:32:30 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id i4sm22308467anm.5.2012.05.01.10.32.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 10:32:28 -0700 (PDT)
Message-ID: <4FA01E3E.7090606@gmail.com>
Date: Tue, 01 May 2012 13:32:46 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com>	<CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com>	<20120501000305.GL335@mip.aaaaa.org> <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com>
In-Reply-To: <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.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: Tue, 01 May 2012 17:32:32 -0000

Fred Baker wrote:
> On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:
> 
>> This PBS interview with Harvey Mudd president Maria Klawe, on the
>> subject of why fewer women go into tech & engineering fields, is
>> worth watching:
>>
>> http://www.pbs.org/newshour/extra/video/blog/2012/04/college_president_discusses_wo.html
> 
> This is a discussion that comes up periodically.
> 
> If you want my opinion (nobody asked, but I will presume that someone is wondering), the corollary is "why aren't more students interested in math/science?". I'll observe that there are relatively few teachers that I can say "inspired" me to think their their directions; far-too-many years later, I could probably name them. Two were English teachers, one was a Math teacher, tenth grade geometry, one taught 7th grade Geography, and one taught senior Calculus. And, oh, I liked some of my college profs, but in this context my views were probably formed before I got there.
> 
> What if teachers were measured on a survey at the end of a semester or a year that asked "does teacher <> make <> interesting to you?".

+1.

What about other minorities?  Is the recruitment levels the same?
Public funded, social programs to fill certain needs? Both at the
school and business levels?

A Puerto Rican from the Sough Bronx, I wanted to go to the vocational
school up the block - Alfred E. Smith.  AP/College bounds programs
were presented to me. I didn't know enough to see it or even dream
about it.

A HS counselor helped with showing the availability of AA/Minority
college grant programs which included girls among the selected group
she called to her office.  Otherwise, while a good grades student, I
wasn't thinking about college. I selected Drexel only because a
recruiter came to the HS showing a photo with white, black, spanish
and women all wearing cool Drexel Engineering helmets!  I selected
Chemical Engineering because I saw they made the most salary as a
co-op student among all degrees! I had no idea how brutal the Chemical
Engineering curriculum would be.

But I had even failed a HS class called "Computers" that introduced
this thing called FORTRAN using some punch card thingy.  So I was
presented with even more Pre-college Grant programs to learn about
applied engineering with computers, and it still took an act of GOD
with a lightning strike knocking out a PDP-11, forcing us to do the
engineering problem translation to BASIC on paper by hand, and only
then did I finally get the AH-AH of GIGO!

And even with all that, it still took AA programs it finally get a job
because it was mist of a recession that did not help many get a job
and this dude called Ted Turner speaking in our graduation getting
loud boos recommending that we go into the MILITARY!

IMO, background is very important. Unless there are active social
programs and recruitment efforts A.K.A "Marketing," I don't think
there will a natural tendency of the so called "minority segment" of
(any) society that are not often encouraged or have the family
background already, to explore or even think about the science related
industry as a career.

Take myself. I was deep into computers and the blossoming world of
Telecomputing, micro-at-home era. The wife (Technical Sales Engineer)
and I specifically did not want our two new girls to get into the same
High Tech business as Daddy and Mommy were in.  No Way! Doctors,
Lawyers perhaps! No way ENGINEER!  It was too tough and I also saw how
tough it was for my women peers at Mobil and Westinghouse with an
extreme competition going on, and quite frankly faced tough family
decisions at some point. In fact, during some pending layoffs at big
W, I was told I was going to stay and found out a pregnant software
programmer in the group was going to get laid off. With my existing
"Fire in my Belly" to quit and start my business already, I took the
opportunity and asked the boss to keep her and to lay me off instead
so I can get the benefits, Cobra, etc.  If I had quit, I lose all that.

I had already saw that the salaries were different too. The idea of
working for a corporation lost its appear when I saw a lost of loyalty
with people of 20, 25-30 years who had dedicated their engineering
lives were now forced to get early retirement, laid off or fired.
With no more Federal funding for Advanced Energy programs and the even
Defense in AI, Robots and Star Wars, etc, I did not want my two girls
to go into these life commitment hard sciences. I didn't push the
computers at home on them at all. I didn't teach them about the idea
of "programming" etc. Perhaps only to play games, and perhaps to use
the early on-disc encyclopedias. They were using Apple stuff at school
anyway and that was good enough for us.

Today, both living in NYC, one works for Sony Music productions
department and the oldest is a successful independent artist making
more money that I can ever imagine possible. She was even a contestant
on Bravo's first season "Next Great Artist."  The only thing that
first worried me was whether she would need to cut off an ear before
getting recognized in the art world! :)

We have to consider that the engineering life is not always ideal for
anyone. Its sounds nice, it does give one more respect among their
family peers, helps secure jobs (when available), better pay, etc, but
its takes a very high commitment and it is very competitive to keep up
even if one wishes to stay in one position and not interested to be
move ahead.  That presents employer decisions with competitive
compensation managers need to make. Younger, lower salary recruitement
can do the same job, etc, so generally by 30, aging engineers need to
make life career movements and changes.

For women, well, life is life, it is what it is, they have it harder
to make family oriented decisions and they are in a position to be,
well, let my artist daughter, Jaclyn Santos, show you what woman are
facing with her "Super Mom, Super Executive, Super Ho!"
painting:

        http://www.jaclynsantos.com/images/large/g.jpg

Finally, for the IETF - well, gotta know first what it wants.  What
does recruiting more woman (or other minorities for that matter) mean
to it?  I personally think its just a reflection of whats going on in
the market.  Its not like the IETF is on the radar for anyone to
pursue unless they are presented with it somewhere, somehow, at work
most likely with a position where IETF work is part of the job
production.   I say that is a very very narrow niche job or goal.

PS: These are my views and says nothing about life other than my own.

From melinda.shore@gmail.com  Tue May  1 10:39:52 2012
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 C0F2C21E835F for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:39: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=[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 f1m69bdxCT8h for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:39:52 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2B00321E802D for <ietf@ietf.org>; Tue,  1 May 2012 10:39:52 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so1930614pbc.31 for <ietf@ietf.org>; Tue, 01 May 2012 10:39: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=q0ev2++v67G3fyau0MBe5rKMbEjQg/NSEvBjQZ7g5I4=; b=mAYgEFjwnlX9p5vZjMLn0IJn6lG4QOvOy6ZzMOzeoEyW6kJwfLegJqvd3X3RbzXWd9 J9jXUzVGlndKwqCWlZ480JVQwHLZ108hLQuOi+Ed/MumG0TceHHNPaHXKP0QiPqjFgKS 3ItZUzleHQOckJH9erF1FRB6cDkka4xQaqP5WFVwVjH3SplonOPFRpxHQLlckVwyRHUO YSvjl9qiIUEIdF53vvYjRUgzYqZb+6gHb860Txnvh46658+VjbrSd+JrvyBnzC2P1i2J POd5FyHqXutwtdewuNheRbWG3QBo3Ln1VgCzZNdeMN8BAJsLZ7Pys1ETdSTgyRsGOS65 /JCg==
Received: by 10.68.221.74 with SMTP id qc10mr58816217pbc.80.1335893991959; Tue, 01 May 2012 10:39:51 -0700 (PDT)
Received: from polypro.local (66-230-101-239-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.239]) by mx.google.com with ESMTPS id h10sm19622079pbh.69.2012.05.01.10.39.49 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 10:39:51 -0700 (PDT)
Message-ID: <4FA01FE4.9040005@gmail.com>
Date: Tue, 01 May 2012 09:39:48 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <CAPv4CP_RZJxb2EpZBo7RUi7Dok=T5G9qOb_zezSeudJB4dr7uA@mail.gmail.c om> <67A16A34D3CEE69C3824DE03@PST.JCK.COM>
In-Reply-To: <67A16A34D3CEE69C3824DE03@PST.JCK.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: Tue, 01 May 2012 17:39:52 -0000

On 5/1/12 9:24 AM, John C Klensin wrote:
> I'm pretty pessimistic about trying
> to use the IETF to get ahead of the industrial / work
> environment situation.

Me too, and I'm pretty sure that that's the real issue, anyway.
But still, I do think that if supporting diversity is a cultural
value at the IETF (and do I have a more concrete description of
what that means?  No, I do not) it's something that participants
can take home with them, and that's a positive thing.

> I do think we should be more aggressive about leadership
> development activities, not just with occasional newcomers
> orientations but by making more mentoring opportunities
> available to relative newcomers (of both genders).

Me, too.

Melinda


From sant9442@gmail.com  Tue May  1 10:43:47 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B64E021E83BA for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.47
X-Spam-Level: 
X-Spam-Status: No, score=-1.47 tagged_above=-999 required=5 tests=[AWL=2.129,  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 N-W4rhGSkNZD for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:43:47 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 05F2E21E8252 for <ietf@ietf.org>; Tue,  1 May 2012 10:43:46 -0700 (PDT)
Received: by yhq56 with SMTP id 56so459307yhq.31 for <ietf@ietf.org>; Tue, 01 May 2012 10:43: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=eGbPBgP5PSZ5A06Olt1VBbk1HZWiqmmbTTolHfW2mto=; b=he9XGJAplNylcW0TLVv5NoPzN3iN9ewspCHrufKLeU54IySdjpuGLBdZq9ZVXdwi+i pUKw7UTsM529Q3wZ7L8Of4uYw6L8ycjdspCUcLda5SpYN4nP5dl4XBFK5QA00wxoQA0h 2R2z0yzCdvf3sLo/JtYbzMbzbQDFzHCcGPWiJU0odc2lKtSYw0YBNo0GL8Q3JBU876b9 6FzY4QP/oVjaINyls0D4gnaGjlJT/EaMrx8oaACgiQlT4v2dFdhNXIfzUyn6n4jC4LsL 8W8+hujhidtPIECTdk8HnbHdiXOg7eNflfPWy0Vt/E9ebu5DrsYjoDMI6phTDIY6nYzY vQEQ==
Received: by 10.236.73.99 with SMTP id u63mr27179347yhd.102.1335894226507; Tue, 01 May 2012 10:43:46 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id e1sm93250956yhi.9.2012.05.01.10.43.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 10:43:45 -0700 (PDT)
Message-ID: <4FA020E3.9050000@gmail.com>
Date: Tue, 01 May 2012 13:44:03 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Monique Morrow <mmorrow@cisco.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CBC53A76.CE3FA%mmorrow@cisco.com>
In-Reply-To: <CBC53A76.CE3FA%mmorrow@cisco.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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 17:43:47 -0000

Monique Morrow wrote:
> One of the points I discussed in NYC last week was also the role of media
> and what is depicted in film, TV and so on wrt girls-women, a topic of the
> Miss Representation initiative:
> 
> http://www.missrepresentation.org/
> 
> Monique

My young artist daughter depicted the woman dilemma in her well 
received, career advancing gallery showing painting:

    http://www.jaclynsantos.com/images/large/g.jpg

--
HLS


From jgunn6@csc.com  Tue May  1 10:44:21 2012
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD31B21E83D0; Tue,  1 May 2012 10:44:21 -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, 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 R6Xh2Ru+EI8N; Tue,  1 May 2012 10:44:21 -0700 (PDT)
Received: from mail170.messagelabs.com (mail170.messagelabs.com [216.82.253.227]) by ietfa.amsl.com (Postfix) with ESMTP id 28E9A21E83C7; Tue,  1 May 2012 10:44:21 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-14.tower-170.messagelabs.com!1335894259!14734717!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16742 invoked from network); 1 May 2012 17:44:20 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-14.tower-170.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 May 2012 17:44:20 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q41HiId2012696; Tue, 1 May 2012 13:44:19 -0400
In-Reply-To: <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com>	<CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com>	<CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
MIME-Version: 1.0
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
X-KeepSent: 0C2E8AF0:171B1CFD-852579F1:0060527C; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP3 July 11, 2011
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF0C2E8AF0.171B1CFD-ON852579F1.0060527C-852579F1.006171DB@csc.com>
Date: Tue, 1 May 2012 13:44:20 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 05/01/2012 01:41:02 PM, Serialize complete at 05/01/2012 01:41:02 PM
Content-Type: multipart/alternative; boundary="=_alternative 00616EF6852579F1_="
Cc: ietf-bounces@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 17:44:22 -0000

This is a multipart message in MIME format.
--=_alternative 00616EF6852579F1_=
Content-Type: text/plain; charset="US-ASCII"

This is VERY narrow minded, and, to be honest, somewhat insulting.

You suggest that "time at work" and "family" are the only important things 
to women.

First off, "working too many hours", and "too much travel" are 
considerably MORE onerous when you DON'T have a family to back you up - 
especially if you have a house to be maintained, animals to be fed and 
exercised, and so on. 

If you have a family, they can pick up some of the slack when you have to 
work late  or travel.  If not, you have to struggle to find a pet sitter 
and so forth.

Furthermore, many of us have extensive non-family commitments outside of 
work - serious (time consuming) hobby's and  competitions, volunteer 
organizations for which we are part of the management team, to say nothing 
of exercise and sleep.


No! "too much travel and too many hours" is NOT "pretty much the same" as 
"takes time away from family".

Janet
.



From:   Yoav Nir <ynir@checkpoint.com>





And then this:
   Among the common factors that women cited as their reasons for leaving 
the profession were too much travel, working too many hours, lack of real 
or perceived opportunities for advancement, and uncivil work environments 
where women were treated in condescending or patronizing manners. Only 25 
percent of the women who left engineering did so for family reasons.

So on the one hand they claim that women are not leaving to take care of 
their families, but on the other the first two correct reasons they 
mention are too much travel and too many hours. I think these two are 
pretty much the same, and the primary reason why someone (male or female) 
would object to travel and long hours is because it takes time away from 
family. 



--=_alternative 00616EF6852579F1_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">This is VERY narrow minded, and, to be
honest, somewhat insulting.</font>
<br>
<br><font size=2 face="sans-serif">You suggest that &quot;time at work&quot;
and &quot;family&quot; are the only important things to women.</font>
<br>
<br><font size=2 face="sans-serif">First off, &quot;working too many hours&quot;,
and &quot;too much travel&quot; are considerably MORE onerous when you
DON'T have a family to back you up - especially if you have a house to
be maintained, animals to be fed and exercised, and so on. </font>
<br>
<br><font size=2 face="sans-serif">If you have a family, they can pick
up some of the slack when you have to work late &nbsp;or travel. &nbsp;If
not, you have to struggle to find a pet sitter and so forth.</font>
<br>
<br><font size=2 face="sans-serif">Furthermore, many of us have extensive
non-family commitments outside of work - serious (time consuming) hobby's
and &nbsp;competitions, volunteer organizations for which we are part of
the management team, to say nothing of exercise and sleep.</font>
<br>
<br>
<br><font size=2 face="sans-serif">No! &quot;</font><font size=2 face="Georgia">too
much travel and too many hours</font><font size=2 face="sans-serif">&quot;
is NOT &quot;pretty much the same&quot; as &quot;</font><font size=2 face="Georgia">takes
time away from family</font><font size=2 face="sans-serif">&quot;.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
.</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">Yoav Nir &lt;ynir@checkpoint.com&gt;</font>
<br>
<br>
<hr noshade>
<br>
<br>
<br>
<br><font size=2 face="Georgia">And then this:</font>
<br><font size=2 face="Georgia">&nbsp; &nbsp;Among the common factors that
women cited as their reasons for leaving the profession were too much travel,
working too many hours, lack of real or perceived opportunities for advancement,
and uncivil work environments where women were treated in condescending
or patronizing manners. Only 25 percent of the women who left engineering
did so for family reasons.</font>
<br>
<br><font size=2 face="Georgia">So on the one hand they claim that women
are not leaving to take care of their families, but on the other the first
two correct reasons they mention are too much travel and too many hours.
I think these two are pretty much the same, and the primary reason why
someone (male or female) would object to travel and long hours is because
it takes time away from family. </font>
<br>
<br>
<br>
--=_alternative 00616EF6852579F1_=--

From dworley@avaya.com  Tue May  1 11:18:31 2012
Return-Path: <dworley@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 6D9B521E840E for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 11:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.418
X-Spam-Level: 
X-Spam-Status: No, score=-102.418 tagged_above=-999 required=5 tests=[AWL=-0.678, BAYES_20=-0.74, 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 vLot6JUO82Fb for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 11:18:29 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id B4F8C21E8056 for <ietf@ietf.org>; Tue,  1 May 2012 11:18:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIFAMonoE/GmAcF/2dsb2JhbABEr22DAYEHggkBAQEBAgESBiJEDQEVCCFCJwQTCBIIh2YFmH6EHZxeiwGFJWMEnBaKKoMEgTg
X-IronPort-AV: E=Sophos;i="4.75,512,1330923600"; d="scan'208";a="345195494"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 May 2012 14:17:22 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 May 2012 14:15:32 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 1 May 2012 14:18:24 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF-Discussion list <ietf@ietf.org>
Date: Tue, 1 May 2012 14:18:23 -0400
Subject: Scared away from tech industry?
Thread-Topic: Scared away from tech industry?
Thread-Index: AQHNJ8a+1KdjyPTNtUWorQH3Q9yGkQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0A93@DC-US1MBEX4.global.avaya.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: Tue, 01 May 2012 18:18:31 -0000

Note that I've changed the Subject.  I'm hoping that the readers may
have some information on the question I ask below.

> From: Fred Baker [fred@cisco.com]
>=20
> If you want my opinion (nobody asked, but I will presume that someone
> is wondering), the corollary is "why aren't more students interested
> in math/science?". I'll observe that there are relatively few teachers
> that I can say "inspired" me to think their their directions;

My experience was that my teachers in the early years were not
inspiring at all, but that was not important, in the same way that you
would not say, "My teachers inspired me to want to eat!".  In my
college years, the math and science teachers were somewhat inspiring
in their fields.  But my computing motivations were entirely internal,
my consumption of computing was limited only by the open hours of the
campus computer center.

    I did an interview for BBC Radio for New Year's Day several years ago
    about the early days of developing the Arpanet.  The closing question
    was why, in 1968, we weren't at Woodstock.  I replied, "For us,
    computers were the drug of choice."	-- Steve Crocker

But getting back to the broad question "Why aren't more students
interested in math/science?" ...  I live in Boston, which has a high
concentration of tech industries, and there are occasional items in
the newspaper about encouraging students to choose "STEM" careers
(Science, Technology, Engineering, Math), because there is a shortage
of such people.  The news items never get around to discussing what
the "shortage" is -- If there is a shortage, why do not salaries rise
to the point that more people choose STEM?

To some degree, the answer must be revealed by the fact that the
companies that sponsor the "STEM publicity" programs are all defense
contractors, and so must hire US citizens.  I believe that the pay
scales of STEM fields have been depressed by globalization, and that
the production of STEM people (if not their employment) has been
moving to "developing" countries.  (Can I blame globalization on the
Internet?)

Some years ago, I read a small item that claimed that the pay of
engineers (relative to other people) peaked during World War II and
had been declining ever since.  I've never been able to find any data
to test this claim.

> What if teachers were measured on a survey at the end of a semester or
> a year that asked "does teacher <> make <> interesting to you?".

Since most students don't like school *at all*, it would result in
teachers receiving poor ratings.

Dale

From sant9442@gmail.com  Tue May  1 11:25:28 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECAE21E811B for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 11:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.825
X-Spam-Level: 
X-Spam-Status: No, score=-1.825 tagged_above=-999 required=5 tests=[AWL=1.774,  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 BSbNeGYMJyN0 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 11:25:27 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 910B821E8089 for <ietf@ietf.org>; Tue,  1 May 2012 11:25:27 -0700 (PDT)
Received: by yenq7 with SMTP id q7so49204yen.31 for <ietf@ietf.org>; Tue, 01 May 2012 11:25:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aqmhBJ2jY72651X+pvBc5+I6hYN7/4DWGatUI44wvU4=; b=GDEc9jwq7EWl2pIWRQf14AY3Q6v7NINvHEulk9OkPbFeozwGdcvhTXlUKQMOiaAYhI VnBGUpvOmZx2LHRWeTAEgQSKnmmr7B9UoJRAU8AGNMpyNaLzHu1wt9BC7savwHqSHkLb V47Qtd3qDjzRffHY+n1FVQ/fbqUi5Gd0axeT3jHOWiEW4w1zY/DPrIY0PKjn/9YFF309 /9CXTIEny2b1T9WF1WuZ/5qqUB7E6TmhnJr5kMrf1tvO+pM9Xqutvw3dRFffam2JIPQj kd8cbFgYzrYDVxrfxlb6K75DtHWVgR52SDIQtp2X5yAGdPQuvY0FBS4d/4qnj9BCYG3c Wv9g==
Received: by 10.236.73.169 with SMTP id v29mr7002681yhd.12.1335896727237; Tue, 01 May 2012 11:25:27 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id 49sm93727958yhs.12.2012.05.01.11.25.25 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 11:25:26 -0700 (PDT)
Message-ID: <4FA02AA8.9090009@gmail.com>
Date: Tue, 01 May 2012 14:25:44 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CBC53A76.CE3FA%mmorrow@cisco.com> <4FA020E3.9050000@gmail.com>
In-Reply-To: <4FA020E3.9050000@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 18:25:28 -0000

Hector wrote:
> Monique Morrow wrote:
>> One of the points I discussed in NYC last week was also the role of media
>> and what is depicted in film, TV and so on wrt girls-women, a topic of 
>> the
>> Miss Representation initiative:
>>
>> http://www.missrepresentation.org/
>>
>> Monique
> 
> My young artist daughter depicted the woman dilemma in her well 
> received, career advancing gallery showing painting:
> 
>    http://www.jaclynsantos.com/images/large/g.jpg
> 

Here is Jaclyn's view on this topic:

       http://www.jaclynsantos.com/statement.html

   "I FEEL that contemporary American society places an unattainable
    amount of expectations on women; cinematography in particular
    often creates "superwomen" who are unnaturally beautiful, smart,
    talented, successful, and sexually gifted. However, due to time 
constraints
    as well as genetically determined physical and mental limitations, no
    real woman could ever possibly achieve equality with these
    fictitious idols.

    While women have always been my chosen subject matter, I feel that
    my work simultaneously functions as a more general commentary on the
    dominant isolationist spirit of modern American culture. This is 
why I
    typically paint the figures by themselves. I prefer to place them
    within their own environments to emphasize their isolation."


--
HLS

From narten@us.ibm.com  Tue May  1 12:03:26 2012
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 3CE9321F8A34 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 12:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.414
X-Spam-Level: 
X-Spam-Status: No, score=-110.414 tagged_above=-999 required=5 tests=[AWL=0.185, 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 NZv-kTSZiTc8 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 12:03:21 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id A877021F89A5 for <ietf@ietf.org>; Tue,  1 May 2012 12:03:21 -0700 (PDT)
Received: from /spool/local by e33.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>; Tue, 1 May 2012 13:03:19 -0600
Received: from d01dlp03.pok.ibm.com (9.56.224.17) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 1 May 2012 13:02:50 -0600
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id CA485C9007E for <ietf@ietf.org>; Tue,  1 May 2012 15:02:37 -0400 (EDT)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q41J2d6o099722 for <ietf@ietf.org>; Tue, 1 May 2012 15:02:39 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q41J2Zjs012795 for <ietf@ietf.org>; Tue, 1 May 2012 15:02:35 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-65-233-4.mts.ibm.com [9.65.233.4]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q41J2YWF012704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 1 May 2012 15:02:35 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q41J2QAY008943 for <ietf@ietf.org>; Tue, 1 May 2012 15:02:26 -0400
Message-Id: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.com>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Date: Tue, 01 May 2012 15:02:26 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12050119-2398-0000-0000-0000064455BB
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 19:03:26 -0000

This is a complex topic and one where it's easy to be naive or even
dismissive if one hasn't experienced stuff themselves or worked with
people who have.

If this conversation was about IETF culture, and how it's hard for
non-Americans to participate "IETF style", I bet folk would much more
quickly recognize some of the real issues.

If folk really want to dive, http://www.ncwit.org/ is a good place to
start.

For the IETF, I think that interested folk might want to form an ad
hoc support/networking group and *especially* see about putting
together some sort of mentoring program. I'm sure if there was a way
for potential mentors to volunteer, there would be a good number of
interested volunteers (myself included). Growing a next generation of
leaders is something the entire IETF should do more of.

Thomas


From dworley@avaya.com  Tue May  1 12:15:35 2012
Return-Path: <dworley@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 97FA021E82A0 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 12:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.824
X-Spam-Level: 
X-Spam-Status: No, score=-102.824 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V45ZBlS8ZpOd for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 12:15:35 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id EE45321E821C for <ietf@ietf.org>; Tue,  1 May 2012 12:15:34 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnMFAFM1oE/GmAcF/2dsb2JhbABEr3WDAYEHggkBAQEBAgESKDINBQsCAQgNCCEQIRElAQEEAQ0FCA0Nh10DBgWdHpJ1DYlTigeBAIUfYwSUJodwhSeFA4ME
X-IronPort-AV: E=Sophos;i="4.75,512,1330923600";  d="scan'208";a="7042706"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 01 May 2012 15:15:32 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 May 2012 15:12:33 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 1 May 2012 15:15:25 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Phillip Hallam-Baker <hallam@gmail.com>
Date: Tue, 1 May 2012 15:15:25 -0400
Subject: RE: Is the IETF aging?
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0kh5+WiUKA6OgaQKSIp8U9+1UqsADRPa3P
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.avaya.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>, <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com>
In-Reply-To: <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@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
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, 01 May 2012 19:15:35 -0000

> From: Mary Barnes [mary.ietf.barnes@gmail.com]
>=20
> Personally, I think IETF has far more of an issue when it comes to
> cultural and gender diversity than it does with not having enough
> younger folks.  This is particularly visible in the leadership.

Given that one moves up in the IETF through gaining the respect of
people in the IETF (and particularly, those in leadership postitions),
it would be difficult to get true cultural diversity.  More likely, we
could assemble a panel of people with any required distribution of
demographic characteristics, but all of them would think like
"IETFers".

Gender diversity is similar to aging, IMO, in that it is hindered by
an accumulation of older participants in leadership positions.

One of the strengths of the IETF is that one acquires positions of
power gradually by accumulating respect of one's peers in the IETF --
that ensures that a company with an economic interest in a technical
decision has a hard time "packing" the IETF's decision-making process.
But that structure automatically makes the culture conservative, and
the higher leadership roles accumulate people with much experience.

John Klensin's concept of "leadership development" seems to be a way
to counteract this.  That is, to be aware of the need to keep the
leadership corps continuously refreshed with younger and
less-experienced people.  Which more or less requires a method of
culling the greybeards, given that they don't conveniently die when
they're 50.

Once there's an ongoing upward movement of people into leadership
positions, it's possible to ask whether women are specifically
inhibited from doing so, and if so, why and what can be done about it.

Dale

From ynir@checkpoint.com  Tue May  1 12:26:32 2012
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 87CF621E842A; Tue,  1 May 2012 12:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.334
X-Spam-Level: 
X-Spam-Status: No, score=-10.334 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599, HTML_MESSAGE=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 041R+EUuP1bS; Tue,  1 May 2012 12:26:32 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 58AB021E8432; Tue,  1 May 2012 12:26:30 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q41JQM8x017110;  Tue, 1 May 2012 22:26:22 +0300
X-CheckPoint: {4FA046C5-1-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 1 May 2012 22:26:23 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 1 May 2012 22:26:21 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Janet P Gunn <jgunn6@csc.com>
Date: Tue, 1 May 2012 22:26:19 +0300
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: Ac0n0EnhfIxd7zN6TrG08FFmVd8DXQ==
Message-ID: <BCBC736C-5DD0-46F9-AA29-4C4AD8748726@checkpoint.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <0BE07CF6-DA94-42B7-B96F-C9CCD241B8FC@checkpoint.com> <CAHBDyN5=5ngyxhc=u+ciXsQ=RGEytan6j4X+bKL5X=2-B6Eajw@mail.gmail.com> <C6E91163-E7C8-4813-A1B5-4F2D7155E35A@checkpoint.com> <OF0C2E8AF0.171B1CFD-ON852579F1.0060527C-852579F1.006171DB@csc.com>
In-Reply-To: <OF0C2E8AF0.171B1CFD-ON852579F1.0060527C-852579F1.006171DB@csc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11022c6a7e9c74f82200754b1ff967868061d16ac4
Content-Type: multipart/alternative; boundary="_000_BCBC736C5DD046F9AA294C4AD8748726checkpointcom_"
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "ietf-bounces@ietf.org" <ietf-bounces@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 19:26:32 -0000

--_000_BCBC736C5DD046F9AA294C4AD8748726checkpointcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On May 1, 2012, at 8:44 PM, Janet P Gunn wrote:

This is VERY narrow minded, and, to be honest, somewhat insulting.

You suggest that "time at work" and "family" are the only important things =
to women.

I'm suggesting no such thing. This authors of this survey say that women wh=
o left engineering did not do so to take care of their families, although t=
heir own data says that 25% of them did. They mention long hours and travel=
, but they offer no explanation why these would be different between men an=
d women.

The one issue that would seem to be different between men and women is the =
attitude of co-workers and superiors towards women, and workplace climate i=
ssues, yet only one in three give that as the reason for leaving. So if wom=
en go from 20% when they graduate to 11% at the workplace, only about 3 of =
those percent are explained by workplace climate. I still don't see how tho=
se other things are different for women.

It should also be noted, that this study is not about the kind of engineeri=
ng we do at the IETF. The women interviewed are mechanical, industrial, and=
 chemical engineers. In fact in a couple of places computer programming is =
mentioned as one of those alternative careers women can take when they leav=
e engineering:
"...I got to a certain point in my engineering career when I NO LONGER ADVA=
NCED. I felt I needed additional education to move forward, but no topics i=
nterested me as much as computer programming, so I changed my career to tha=
t. It was a good change. I have been more successful in the computer field =
than I was in the engineering field.=94

I don't know the figures for the IT industry, but I would guess that they'r=
e not as lopsided as those for those so-called real engineering.

Yoav


--_000_BCBC736C5DD046F9AA294C4AD8748726checkpointcom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; "><br><div><div>On May 1, 20=
12, at 8:44 PM, Janet P Gunn wrote:</div><br class=3D"Apple-interchange-new=
line"><blockquote type=3D"cite"><font face=3D"sans-serif">This is VERY narr=
ow minded, and, to be
honest, somewhat insulting.</font>
<br>
<br><font face=3D"sans-serif">You suggest that "time at work"
and "family" are the only important things to women.</font>
<br></blockquote><div><br></div>I'm suggesting no such thing. This authors =
of this survey say that women who left engineering did not do so to take ca=
re of their families, although their own data says that 25% of them did. Th=
ey mention long hours and travel, but they offer no explanation why these w=
ould be different between men and women.</div><div><br></div><div>The one i=
ssue that would seem to be different between men and women is the attitude =
of co-workers and superiors towards women, and workplace climate issues, ye=
t only one in three give that as the reason for leaving. So if women go fro=
m 20% when they graduate to 11% at the workplace, only about 3 of those per=
cent are explained by workplace climate. I still don't see how those other =
things are different for women.&nbsp;</div><div><br></div><div>It should al=
so be noted, that this study is not about the kind of engineering we do at =
the IETF. The women interviewed are mechanical, industrial, and chemical en=
gineers. In fact in a couple of places computer programming is mentioned as=
 one of those alternative careers women can take when they leave engineerin=
g:&nbsp;</div><div>"...I got to a certain point in my engineering career wh=
en&nbsp;I NO LONGER ADVANCED. I felt I needed additional education&nbsp;to =
move forward, but no topics interested me as much as computer programming, =
so I changed my career to that.&nbsp;It was a good change. I have&nbsp;been=
 more successful in the computer field than I was in&nbsp;the engineering f=
ield.=94</div><div><br></div><div>I don't know the figures for the IT indus=
try, but I would guess that they're not as lopsided as those for those so-c=
alled real engineering.</div><div><br></div><div>Yoav</div><div><br></div><=
/body></html>=

--_000_BCBC736C5DD046F9AA294C4AD8748726checkpointcom_--

From john-ietf@jck.com  Tue May  1 13:39:32 2012
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 AF8EA11E8074 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 13:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXp3p4rFsYGh for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 13:39:32 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3077121E8025 for <ietf@ietf.org>; Tue,  1 May 2012 13:39:32 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SPJm7-0005EB-Hl; Tue, 01 May 2012 16:34:19 -0400
Date: Tue, 01 May 2012 16:39:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: Is the IETF aging?
Message-ID: <8DC137508AE27AAD6CC12654@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.avaya.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> , <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.av aya.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 20:39:32 -0000

--On Tuesday, May 01, 2012 15:15 -0400 "Worley, Dale R (Dale)"
<dworley@avaya.com> wrote:

>...
>  That is, to be aware of the need to keep the
> leadership corps continuously refreshed with younger and
> less-experienced people.  Which more or less requires a method
> of culling the greybeards, given that they don't conveniently
> die when they're 50.

Speaking as a greybeard who doesn't particularly like the idea
of being culled, an alternative is to try to move such people on
to mentoring/ advisory roles (and the few tasks we have around
that _really_ need many years of experience) rather than
occupying roles that can be performed by others.  That is
actually easily accomplished because it can be done unilaterally
by the older members of the community.  The harder part
--because it does require community and leadership commitment --
is finding ways to make those mentoring/ advisory roles work.

   john


From jmpolk@cisco.com  Tue May  1 13:40:43 2012
Return-Path: <jmpolk@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 EEB0E21E802B for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 13:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.487
X-Spam-Level: 
X-Spam-Status: No, score=-110.487 tagged_above=-999 required=5 tests=[AWL=0.112, 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 1mGPHkpiRi1m for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 13:40:43 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 73A5E21E8025 for <ietf@ietf.org>; Tue,  1 May 2012 13:40:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=2218; q=dns/txt; s=iport; t=1335904843; x=1337114443; h=message-id:date:to:from:subject:mime-version; bh=wJl2eoLCScXWrphsb2bYsobgKD1qo64aq8cyTx20hf4=; b=aIppRaKARjXlPeNOVuB8nqz7oQcfMlHVtsrEocItdGdBRi8+of8Hcf0I AXduie9E+ucYtWWb8CI9Ny264pSNhD7HY+WQf+8LatjO51ArB9lB0nP4r FYp43JBNcsB2SvqeLD0qShdHfiT6RltsWr8B2QLDTpX8W76TvyVObwMQq Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnEFAERJoE+rRDoH/2dsb2JhbABEr3mDAYEHgiIBJQIyCho6KUQpDIdqmQaBKJ88kCZjBIhkm3OBaYMG
X-IronPort-AV: E=Sophos;i="4.75,512,1330905600"; d="scan'208";a="43021267"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 01 May 2012 20:40:43 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q41Keg7F012654 for <ietf@ietf.org>; Tue, 1 May 2012 20:40:42 GMT
Message-Id: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 01 May 2012 15:40:47 -0500
To: IETF-Discussion list <ietf@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Gender diversity in engineering
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 20:40:44 -0000

There have been some good numbers floated on recent threads, but at 
least for me, they aren't enough to gain a complete (or nearly 
complete) picture of the issue.

Having studied statistics, we need to know a starting point, and look 
for the reductions (or increases) from that point forward. Starting 
in high school is not sufficiently refined enough, as there are a lot 
that take advanced math (personally I'd start with trig - because 
that kicked my ass - but rarely is it its own class, so let's start 
with calculus 1) that don't go into engineering. Thus, high school is 
probably not a good place to measure from. Therefore, it needs to be college.

We need to know

% of class (based on year started) that is female in engineering
    (do we want to start with electrical and CS to
     be more applicable to our situation?)

We'll call that percent 'X'

then

%X of drops from engineering (BS) (or just elec/CS?) over the college 
years before graduation?

then

%X that enter workforce after BS in Engineering (or just elec/CS?) 
into the engineering field?

then

%X that start graduate school (MS) in engineering (or just elec/CS)?

%X that receive MS degree in engineering (or just elec/CS)?

%X that enter workforce after MS in Engineering (or just elec/CS?) 
into the engineering field?

then

%X that start doctoral school (PhD.) in engineering (or just elec/CS)?

%X that achieve PhD. in engineering (or just elec/CS)?

then

%X that enter workforce after PhD in Engineering (or just elec/CS?) 
into the engineering field?

This will likely track those that are entering the engineering 
workforce, and with what level of education. From that point in the 
analysis - we can attempt to track at what point there are further 
drops out of the engineering workforce by women (i.e., after how many 
years). Or is it as simple as problems after childbirth to reenter 
the workforce (for whatever reason).

As an example, if there is a significant difference from those that 
drop out after their BS from those that drop out MS, then maybe 
something should be done to encourage women to stay for the MS.

comments or questions?

James


From sm@resistor.net  Tue May  1 15:34:35 2012
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 3958F21E804D for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 15:34:35 -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 CtdnITvEcGwE for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 15:34:34 -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 90BB521E804A for <ietf@ietf.org>; Tue,  1 May 2012 15:34: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 q41MYRKS010252; Tue, 1 May 2012 15:34:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1335911672; i=@resistor.net; bh=38IELyVxnxlkUp1Vj1AxE5usPOeaRXWfp20s9kw5wh0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZEmu+kILtx9gkS9nzEvp0GXaylYqI/nCrb8MH1n5hucRvFIHsIqD5aTQgvTVOOh5E ANgnYGhUOV4KMcfe1yVYgIfcK8rfguzGX9JckpaBRECopC0rgXIxD6pezpbPXp3y19 A5USptr7xXUmPZ6uE0beD654o3g2yoNMq381tnk0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1335911672; i=@resistor.net; bh=38IELyVxnxlkUp1Vj1AxE5usPOeaRXWfp20s9kw5wh0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1PMczeHMmmNAvlWzQ7jiGW5GZ5LJBEuUi90zb8k/W4bxrBteX0RfnRZISLYdQzzPm kqPjz0W2eyy9jxKVIsMHq231/irDn5bnXmn7f9XDj8hmpCpSe15FmOmi/P8BvVbKTM 8iTp+ZyBS/kd69okR12U+hWyiXkIL9flP/NHzeLY=
Message-Id: <6.2.5.6.2.20120501135823.0a195c98@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 01 May 2012 15:31:47 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: RE: Is the IETF aging?
In-Reply-To: <8DC137508AE27AAD6CC12654@PST.JCK.COM>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.av aya.com> <8DC137508AE27AAD6CC12654@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 01 May 2012 22:34:35 -0000

Hi John,
At 13:39 01-05-2012, John C Klensin wrote:
>Speaking as a greybeard who doesn't particularly like the idea
>of being culled, an alternative is to try to move such people on
>to mentoring/ advisory roles (and the few tasks we have around
>that _really_ need many years of experience) rather than
>occupying roles that can be performed by others.  That is

The problem is that it can always be argued that many of the tasks 
around needs many years of experience.  That may explain why around 
50% of incumbents are returned.  It has been said that "service in 
the IETF's leadership bodies is a short-term contribution to the 
community, not a career".  Here's the incumbent rate at the middle 
level per area (caution advised as the figures are biased):

  APP  50%
  INT  50%
  RAI   0%
  OPS 50%
  RTG  50%
  SEC  50%
  TSV  67%

>actually easily accomplished because it can be done unilaterally
>by the older members of the community.  The harder part
>--because it does require community and leadership commitment --
>is finding ways to make those mentoring/ advisory roles work.

Yes.

Regards,
-sm 


From jgunn6@csc.com  Tue May  1 16:08:19 2012
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E4821E808E; Tue,  1 May 2012 16:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level: 
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5 tests=[AWL=0.186,  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 0-aGf4nAwp1e; Tue,  1 May 2012 16:08:19 -0700 (PDT)
Received: from mail87.messagelabs.com (mail87.messagelabs.com [216.82.250.19]) by ietfa.amsl.com (Postfix) with ESMTP id DAA7821E8024; Tue,  1 May 2012 16:08:18 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-3.tower-87.messagelabs.com!1335913696!9129442!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2577 invoked from network); 1 May 2012 23:08:17 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-3.tower-87.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 May 2012 23:08:17 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q41N8FGx021700; Tue, 1 May 2012 19:08:15 -0400
In-Reply-To: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com>
To: "James M. Polk" <jmpolk@cisco.com>
MIME-Version: 1.0
Subject: Re: Gender diversity in engineering
X-KeepSent: D141039F:C60F52A9-852579F1:007F02F5; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP3 July 11, 2011
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFD141039F.C60F52A9-ON852579F1.007F02F5-852579F1.007F1C46@csc.com>
Date: Tue, 1 May 2012 19:08:22 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 05/01/2012 07:04:58 PM, Serialize complete at 05/01/2012 07:04:58 PM
Content-Type: multipart/alternative; boundary="=_alternative 007F1BD7852579F1_="
Cc: ietf-bounces@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 23:08:19 -0000

This is a multipart message in MIME format.
--=_alternative 007F1BD7852579F1_=
Content-Type: text/plain; charset="US-ASCII"

But that leaves out all of us that started off in a different (technical) 
field (Math and OR in my case) and ended up here..

Janet

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.



From:   "James M. Polk" <jmpolk@cisco.com>
To:     IETF-Discussion list <ietf@ietf.org>
Date:   05/01/2012 04:40 PM
Subject:        Gender diversity in engineering
Sent by:        ietf-bounces@ietf.org



There have been some good numbers floated on recent threads, but at 
least for me, they aren't enough to gain a complete (or nearly 
complete) picture of the issue.

Having studied statistics, we need to know a starting point, and look 
for the reductions (or increases) from that point forward. Starting 
in high school is not sufficiently refined enough, as there are a lot 
that take advanced math (personally I'd start with trig - because 
that kicked my ass - but rarely is it its own class, so let's start 
with calculus 1) that don't go into engineering. Thus, high school is 
probably not a good place to measure from. Therefore, it needs to be 
college.

We need to know

% of class (based on year started) that is female in engineering
    (do we want to start with electrical and CS to
     be more applicable to our situation?)

We'll call that percent 'X'

then

%X of drops from engineering (BS) (or just elec/CS?) over the college 
years before graduation?

then

%X that enter workforce after BS in Engineering (or just elec/CS?) 
into the engineering field?

then

%X that start graduate school (MS) in engineering (or just elec/CS)?

%X that receive MS degree in engineering (or just elec/CS)?

%X that enter workforce after MS in Engineering (or just elec/CS?) 
into the engineering field?

then

%X that start doctoral school (PhD.) in engineering (or just elec/CS)?

%X that achieve PhD. in engineering (or just elec/CS)?

then

%X that enter workforce after PhD in Engineering (or just elec/CS?) 
into the engineering field?

This will likely track those that are entering the engineering 
workforce, and with what level of education. From that point in the 
analysis - we can attempt to track at what point there are further 
drops out of the engineering workforce by women (i.e., after how many 
years). Or is it as simple as problems after childbirth to reenter 
the workforce (for whatever reason).

As an example, if there is a significant difference from those that 
drop out after their BS from those that drop out MS, then maybe 
something should be done to encourage women to stay for the MS.

comments or questions?

James



--=_alternative 007F1BD7852579F1_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">But that leaves out all of us that started
off in a different (technical) field (Math and OR in my case) and ended
up here..</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
<br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">&quot;James M. Polk&quot;
&lt;jmpolk@cisco.com&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">IETF-Discussion list
&lt;ietf@ietf.org&gt;</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date: &nbsp; &nbsp; &nbsp;
&nbsp;</font><font size=1 face="sans-serif">05/01/2012 04:40 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">Gender diversity
in engineering</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by: &nbsp; &nbsp;
&nbsp; &nbsp;</font><font size=1 face="sans-serif">ietf-bounces@ietf.org</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>There have been some good numbers floated on recent
threads, but at <br>
least for me, they aren't enough to gain a complete (or nearly <br>
complete) picture of the issue.<br>
<br>
Having studied statistics, we need to know a starting point, and look <br>
for the reductions (or increases) from that point forward. Starting <br>
in high school is not sufficiently refined enough, as there are a lot <br>
that take advanced math (personally I'd start with trig - because <br>
that kicked my ass - but rarely is it its own class, so let's start <br>
with calculus 1) that don't go into engineering. Thus, high school is <br>
probably not a good place to measure from. Therefore, it needs to be college.<br>
<br>
We need to know<br>
<br>
% of class (based on year started) that is female in engineering<br>
 &nbsp; &nbsp;(do we want to start with electrical and CS to<br>
 &nbsp; &nbsp; be more applicable to our situation?)<br>
<br>
We'll call that percent 'X'<br>
<br>
then<br>
<br>
%X of drops from engineering (BS) (or just elec/CS?) over the college <br>
years before graduation?<br>
<br>
then<br>
<br>
%X that enter workforce after BS in Engineering (or just elec/CS?) <br>
into the engineering field?<br>
<br>
then<br>
<br>
%X that start graduate school (MS) in engineering (or just elec/CS)?<br>
<br>
%X that receive MS degree in engineering (or just elec/CS)?<br>
<br>
%X that enter workforce after MS in Engineering (or just elec/CS?) <br>
into the engineering field?<br>
<br>
then<br>
<br>
%X that start doctoral school (PhD.) in engineering (or just elec/CS)?<br>
<br>
%X that achieve PhD. in engineering (or just elec/CS)?<br>
<br>
then<br>
<br>
%X that enter workforce after PhD in Engineering (or just elec/CS?) <br>
into the engineering field?<br>
<br>
This will likely track those that are entering the engineering <br>
workforce, and with what level of education. From that point in the <br>
analysis - we can attempt to track at what point there are further <br>
drops out of the engineering workforce by women (i.e., after how many <br>
years). Or is it as simple as problems after childbirth to reenter <br>
the workforce (for whatever reason).<br>
<br>
As an example, if there is a significant difference from those that <br>
drop out after their BS from those that drop out MS, then maybe <br>
something should be done to encourage women to stay for the MS.<br>
<br>
comments or questions?<br>
<br>
James<br>
<br>
</font></tt>
<br>
--=_alternative 007F1BD7852579F1_=--

From jgunn6@csc.com  Tue May  1 16:31:57 2012
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E06DA21E8086; Tue,  1 May 2012 16:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.149,  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 88awkWy5kRja; Tue,  1 May 2012 16:31:57 -0700 (PDT)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id BF45C21F88F5; Tue,  1 May 2012 16:31:56 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-85.messagelabs.com!1335915115!23682226!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28015 invoked from network); 1 May 2012 23:31:55 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-2.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 1 May 2012 23:31:55 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q41NVtkh024523; Tue, 1 May 2012 19:31:55 -0400
In-Reply-To: <A103D046-BF44-46AA-B5AC-2FE7263DD162@checkpoint.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <OF5ABF8912.F0CB0BF0-ON852579F0.00759884-852579F0.007634F8@csc.com> <A103D046-BF44-46AA-B5AC-2FE7263DD162@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
MIME-Version: 1.0
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
X-KeepSent: 5CAE0F90:5601353B-852579F1:008126B6; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP3 July 11, 2011
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF5CAE0F90.5601353B-ON852579F1.008126B6-852579F1.00814717@csc.com>
Date: Tue, 1 May 2012 19:32:02 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 05/01/2012 07:28:38 PM, Serialize complete at 05/01/2012 07:28:38 PM
Content-Type: multipart/alternative; boundary="=_alternative 008146EA852579F1_="
Cc: "ietf-bounces@ietf.org" <ietf-bounces@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 23:31:58 -0000

This is a multipart message in MIME format.
--=_alternative 008146EA852579F1_=
Content-Type: text/plain; charset="US-ASCII"

Yoav Nir <ynir@checkpoint.com> wrote on 05/01/2012 02:24:57 AM:

> From: Yoav Nir <ynir@checkpoint.com>
> To: Janet P Gunn/USA/CSC@CSC
> Cc: Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf-
> bounces@ietf.org" <ietf-bounces@ietf.org>, IETF discussion list 
> <ietf@ietf.org>
> Date: 05/01/2012 02:26 AM
> Subject: Re: 'Geek' image scares women away from tech industry ? The 
Register
> 
> On May 1, 2012, at 12:31 AM, Janet P Gunn wrote:
> 
> My own anecdotes. 
> 
> Yes, it starts early. 
> 
> When I was 3 I announced that I was going to be a physicist when I 
> grew up.  WHY? 
> 
> 1 - a physicist has a chair that  is on WHEELS, and spins ROUND and 
ROUND 
> 2 - a physicist has a blackboard with COLORED CHALK 
> 3 (and MOST important) a physicist has a CANDY machine in the hall 
> outside his office. 
> 
> But engineers get to drive trains. Trains > swivel chairs.

If I go back even further, when I was born my father reportedly told a 
colleague "I don't care if she IS a girl.  She is still going to like 
trains!"

Janet
--=_alternative 008146EA852579F1_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Yoav Nir &lt;ynir@checkpoint.com&gt; wrote on 05/01/2012
02:24:57 AM:<br>
<br>
&gt; From: Yoav Nir &lt;ynir@checkpoint.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: Janet P Gunn/USA/CSC@CSC</font></tt>
<br><tt><font size=2>&gt; Cc: Mary Barnes &lt;mary.ietf.barnes@gmail.com&gt;,
&quot;ietf-<br>
&gt; bounces@ietf.org&quot; &lt;ietf-bounces@ietf.org&gt;, IETF discussion
list <br>
&gt; &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 05/01/2012 02:26 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: 'Geek' image scares women away from
tech industry ? The Register</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; On May 1, 2012, at 12:31 AM, Janet P Gunn wrote:</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; My own anecdotes. <br>
&gt; <br>
&gt; Yes, it starts early. <br>
&gt; <br>
&gt; When I was 3 I announced that I was going to be a physicist when I
<br>
&gt; grew up. &nbsp;WHY? <br>
&gt; <br>
&gt; 1 - a physicist has a chair that &nbsp;is on WHEELS, and spins ROUND
and ROUND <br>
&gt; 2 - a physicist has a blackboard with COLORED CHALK <br>
&gt; 3 (and MOST important) a physicist has a CANDY machine in the hall
<br>
&gt; outside his office. </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; But engineers get to drive trains. Trains &gt; swivel chairs.</font></tt>
<br>
<br><tt><font size=2>If I go back even further, when I was born my father
reportedly told a colleague &quot;I don't care if she IS a girl. &nbsp;She
is still going to like trains!&quot;</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
--=_alternative 008146EA852579F1_=--

From cb.list6@gmail.com  Tue May  1 17:49:53 2012
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF1B21E8086; Tue,  1 May 2012 17:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.375
X-Spam-Level: 
X-Spam-Status: No, score=-3.375 tagged_above=-999 required=5 tests=[AWL=0.223,  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 McC6RH9y0V1R; Tue,  1 May 2012 17:49:52 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 76D6321E8020; Tue,  1 May 2012 17:49:52 -0700 (PDT)
Received: by yhq56 with SMTP id 56so116856yhq.31 for <multiple recipients>; Tue, 01 May 2012 17:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=B3Y7ZMNz5ixFRzVifXo08Mnj2nfDGkFc01Kk7NSUoYs=; b=TZgYt6EMLFWYTsLH+zG6wxrOh0X0VtyRFAwsWUDJ7uVBIJzANFVNd7KM6LnDIqCvAT gBKdEBXczx+xV/waIm9jJ9lBI9NZ9oHIMIcDuZgfl6D+FN4TpdIxeTYuB8VVbLLJx7V0 FPrfo3t/HHhashlvUh42JsAJ35aVAEtAqnvaAm4A2iuE9ga5SEbNoA8T9znmJYmzv1mE a8gdErHAWdjxl+LB70Ccc1xXPcsVpZaELR199duoTNnhv7JaVAVyL+lmkm3XDdSAHP1G Cdpu2+s0MvXPAm9sufPPsXE3q0UavYy7HTu0ZbHdpltmUxQVAFC+S7dcoIAc4Cd0Jc3n rRDA==
MIME-Version: 1.0
Received: by 10.68.197.35 with SMTP id ir3mr13986323pbc.79.1335919791696; Tue, 01 May 2012 17:49:51 -0700 (PDT)
Received: by 10.142.102.1 with HTTP; Tue, 1 May 2012 17:49:51 -0700 (PDT)
Received: by 10.142.102.1 with HTTP; Tue, 1 May 2012 17:49:51 -0700 (PDT)
In-Reply-To: <OFD141039F.C60F52A9-ON852579F1.007F02F5-852579F1.007F1C46@csc.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <OFD141039F.C60F52A9-ON852579F1.007F02F5-852579F1.007F1C46@csc.com>
Date: Tue, 1 May 2012 17:49:51 -0700
Message-ID: <CAD6AjGQT9fHDrRH5Z4cCwoMV74vAikT4bnd9jbV920QuR3Eg4g@mail.gmail.com>
Subject: Re: Gender diversity in engineering
From: Cameron Byrne <cb.list6@gmail.com>
To: Janet P Gunn <jgunn6@csc.com>
Content-Type: multipart/alternative; boundary=e89a8ff24e8da1ed5404bf031061
Cc: ietf-bounces@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 00:49:53 -0000

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

On May 1, 2012 4:08 PM, "Janet P Gunn" <jgunn6@csc.com> wrote:
>
> But that leaves out all of us that started off in a different (technical)
field (Math and OR in my case) and ended up here..
>

Furthermore, is rigorous academic STEM  education highly correlated with
whatever it is you are trying to measure ?

CB

> Janet
>
> This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
>
>
>
> From:        "James M. Polk" <jmpolk@cisco.com>
> To:        IETF-Discussion list <ietf@ietf.org>
> Date:        05/01/2012 04:40 PM
> Subject:        Gender diversity in engineering
> Sent by:        ietf-bounces@ietf.org
> ________________________________
>
>
>
> There have been some good numbers floated on recent threads, but at
> least for me, they aren't enough to gain a complete (or nearly
> complete) picture of the issue.
>
> Having studied statistics, we need to know a starting point, and look
> for the reductions (or increases) from that point forward. Starting
> in high school is not sufficiently refined enough, as there are a lot
> that take advanced math (personally I'd start with trig - because
> that kicked my ass - but rarely is it its own class, so let's start
> with calculus 1) that don't go into engineering. Thus, high school is
> probably not a good place to measure from. Therefore, it needs to be
college.
>
> We need to know
>
> % of class (based on year started) that is female in engineering
>    (do we want to start with electrical and CS to
>     be more applicable to our situation?)
>
> We'll call that percent 'X'
>
> then
>
> %X of drops from engineering (BS) (or just elec/CS?) over the college
> years before graduation?
>
> then
>
> %X that enter workforce after BS in Engineering (or just elec/CS?)
> into the engineering field?
>
> then
>
> %X that start graduate school (MS) in engineering (or just elec/CS)?
>
> %X that receive MS degree in engineering (or just elec/CS)?
>
> %X that enter workforce after MS in Engineering (or just elec/CS?)
> into the engineering field?
>
> then
>
> %X that start doctoral school (PhD.) in engineering (or just elec/CS)?
>
> %X that achieve PhD. in engineering (or just elec/CS)?
>
> then
>
> %X that enter workforce after PhD in Engineering (or just elec/CS?)
> into the engineering field?
>
> This will likely track those that are entering the engineering
> workforce, and with what level of education. From that point in the
> analysis - we can attempt to track at what point there are further
> drops out of the engineering workforce by women (i.e., after how many
> years). Or is it as simple as problems after childbirth to reenter
> the workforce (for whatever reason).
>
> As an example, if there is a significant difference from those that
> drop out after their BS from those that drop out MS, then maybe
> something should be done to encourage women to stay for the MS.
>
> comments or questions?
>
> James
>
>

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

<p><br>
On May 1, 2012 4:08 PM, &quot;Janet P Gunn&quot; &lt;<a href=3D"mailto:jgun=
n6@csc.com">jgunn6@csc.com</a>&gt; wrote:<br>
&gt;<br>
&gt; But that leaves out all of us that started off in a different (technic=
al) field (Math and OR in my case) and ended up here.. <br>
&gt;</p>
<p>Furthermore, is rigorous academic STEM=A0 education highly correlated wi=
th whatever it is you are trying to measure ? <br></p>
<p>CB</p>
<p>&gt; Janet<br>
&gt;<br>
&gt; This is a PRIVATE message. If you are not the intended recipient, plea=
se delete without copying and kindly advise us by e-mail of the mistake in =
delivery. NOTE: Regardless of content, this e-mail shall not operate to bin=
d CSC to any order or other contract unless pursuant to explicit written ag=
reement or government initiative expressly permitting the use of e-mail for=
 such purpose. <br>

&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: =A0 =A0 =A0 =A0&quot;James M. Polk&quot; &lt;<a href=3D"mailto:j=
mpolk@cisco.com">jmpolk@cisco.com</a>&gt; <br>
&gt; To: =A0 =A0 =A0 =A0IETF-Discussion list &lt;<a href=3D"mailto:ietf@iet=
f.org">ietf@ietf.org</a>&gt; <br>
&gt; Date: =A0 =A0 =A0 =A005/01/2012 04:40 PM <br>
&gt; Subject: =A0 =A0 =A0 =A0Gender diversity in engineering <br>
&gt; Sent by: =A0 =A0 =A0 =A0<a href=3D"mailto:ietf-bounces@ietf.org">ietf-=
bounces@ietf.org</a> <br>
&gt; ________________________________<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; There have been some good numbers floated on recent threads, but at <b=
r>
&gt; least for me, they aren&#39;t enough to gain a complete (or nearly <br=
>
&gt; complete) picture of the issue.<br>
&gt;<br>
&gt; Having studied statistics, we need to know a starting point, and look =
<br>
&gt; for the reductions (or increases) from that point forward. Starting <b=
r>
&gt; in high school is not sufficiently refined enough, as there are a lot =
<br>
&gt; that take advanced math (personally I&#39;d start with trig - because =
<br>
&gt; that kicked my ass - but rarely is it its own class, so let&#39;s star=
t <br>
&gt; with calculus 1) that don&#39;t go into engineering. Thus, high school=
 is <br>
&gt; probably not a good place to measure from. Therefore, it needs to be c=
ollege.<br>
&gt;<br>
&gt; We need to know<br>
&gt;<br>
&gt; % of class (based on year started) that is female in engineering<br>
&gt; =A0 =A0(do we want to start with electrical and CS to<br>
&gt; =A0 =A0 be more applicable to our situation?)<br>
&gt;<br>
&gt; We&#39;ll call that percent &#39;X&#39;<br>
&gt;<br>
&gt; then<br>
&gt;<br>
&gt; %X of drops from engineering (BS) (or just elec/CS?) over the college =
<br>
&gt; years before graduation?<br>
&gt;<br>
&gt; then<br>
&gt;<br>
&gt; %X that enter workforce after BS in Engineering (or just elec/CS?) <br=
>
&gt; into the engineering field?<br>
&gt;<br>
&gt; then<br>
&gt;<br>
&gt; %X that start graduate school (MS) in engineering (or just elec/CS)?<b=
r>
&gt;<br>
&gt; %X that receive MS degree in engineering (or just elec/CS)?<br>
&gt;<br>
&gt; %X that enter workforce after MS in Engineering (or just elec/CS?) <br=
>
&gt; into the engineering field?<br>
&gt;<br>
&gt; then<br>
&gt;<br>
&gt; %X that start doctoral school (PhD.) in engineering (or just elec/CS)?=
<br>
&gt;<br>
&gt; %X that achieve PhD. in engineering (or just elec/CS)?<br>
&gt;<br>
&gt; then<br>
&gt;<br>
&gt; %X that enter workforce after PhD in Engineering (or just elec/CS?) <b=
r>
&gt; into the engineering field?<br>
&gt;<br>
&gt; This will likely track those that are entering the engineering <br>
&gt; workforce, and with what level of education. From that point in the <b=
r>
&gt; analysis - we can attempt to track at what point there are further <br=
>
&gt; drops out of the engineering workforce by women (i.e., after how many =
<br>
&gt; years). Or is it as simple as problems after childbirth to reenter <br=
>
&gt; the workforce (for whatever reason).<br>
&gt;<br>
&gt; As an example, if there is a significant difference from those that <b=
r>
&gt; drop out after their BS from those that drop out MS, then maybe <br>
&gt; something should be done to encourage women to stay for the MS.<br>
&gt;<br>
&gt; comments or questions?<br>
&gt;<br>
&gt; James<br>
&gt;<br>
&gt;<br>
</p>

--e89a8ff24e8da1ed5404bf031061--

From richard@shockey.us  Tue May  1 18:18:44 2012
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 8A1A221E8098 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 18:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.545
X-Spam-Level: 
X-Spam-Status: No, score=-98.545 tagged_above=-999 required=5 tests=[AWL=-0.650, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 ZIh5yVYirfOi for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 18:18:43 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by ietfa.amsl.com (Postfix) with SMTP id 6CC2421E8019 for <ietf@ietf.org>; Tue,  1 May 2012 18:18:43 -0700 (PDT)
Received: (qmail 18463 invoked by uid 0); 2 May 2012 01:18:41 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by cpoproxy3.bluehost.com with SMTP; 2 May 2012 01:18:41 -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=BUh4/NfZs/SKSCOFTFQObKfjQQ4SIawxrwvNZye920Q=;  b=VrqOLZc4yHQk6tq5F9W03VMjUARhDTKV+QUn1JP0AbUBrqWR5JSZDJexJfiNOIptLTRkGf2FqWn3byGM6Nj7iT86nM+k2Wm9hEH7mwBA+d1KRso9LsDxLaWsrq7xtXmJ;
Received: from pool-108-48-10-220.washdc.fios.verizon.net ([108.48.10.220] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1SPODI-0000AL-J8; Tue, 01 May 2012 19:18:40 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Thomas Narten'" <narten@us.ibm.com>, "'IETF-Discussion list'" <ietf@ietf.org>
References: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.com>
In-Reply-To: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.com>
Subject: RE: 'Geek' image scares women away from tech industry ? The Register
Date: Tue, 1 May 2012 21:18:38 -0400
Message-ID: <005901cd2801$8214c510$863e4f30$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0nzReFr6tyOZPMQdWLl5qYzBBx1wAM5rcQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 108.48.10.220 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, 02 May 2012 01:18:44 -0000

 [RS> ] +1 This is not just something we should do, its something we have to
do. I know the AD's try and keep a strong hand in talent spotting among the
WG chairs on who might succeed them, but one thing I believe WG chairs need
to do is appoint WG Secretaries. I always did. Limit the number of WG's a
single individual can co-chair.  The best way to mentor promising talent of
is to give them a start on the "career ladder"  

I'm sure if there was a way for potential mentors to volunteer, there would
be a good number of interested volunteers (myself included). Growing a next
generation of leaders is something the entire IETF should do more of.

Thomas


From dworley@avaya.com  Tue May  1 18:56:18 2012
Return-Path: <dworley@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 A6F1E21E809F for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 18:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.316
X-Spam-Level: 
X-Spam-Status: No, score=-103.316 tagged_above=-999 required=5 tests=[AWL=0.283, 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 vTNpcJ6myGxf for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 18:56:18 -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 DCECD21E808F for <ietf@ietf.org>; Tue,  1 May 2012 18:56:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FAFWToE/GmAcF/2dsb2JhbABEr3qDAoEHggkBAQEBAxIoTwIBCA0IIRAyJQEBBBMIDA6Ha51EnEyQJWMEnBaKKoME
X-IronPort-AV: E=Sophos;i="4.75,515,1330923600"; d="scan'208";a="304491769"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 May 2012 21:56:14 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 May 2012 21:53:21 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 1 May 2012 21:56:14 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Date: Tue, 1 May 2012 21:55:08 -0400
Subject: RE: Is the IETF aging?
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0n2pBDhEhBfDMoTp6uWSHxN3vu8gALAnIo
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0A9C@DC-US1MBEX4.global.avaya.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> ,  <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.av aya.com>,<8DC137508AE27AAD6CC12654@PST.JCK.COM>
In-Reply-To: <8DC137508AE27AAD6CC12654@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 01:56:18 -0000

________________________________________
From: John C Klensin [john-ietf@jck.com]

The harder part
--because it does require community and leadership commitment --
is finding ways to make those mentoring/ advisory roles work.
________________________________________

What would be good patterns for those roles?

Dale

From melinda.shore@gmail.com  Tue May  1 20:07:32 2012
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 7A40121E8105 for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 20:07:32 -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=0.000,  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 eRKK2WsWM4Ol for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 20:07:32 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 023FE21E8104 for <ietf@ietf.org>; Tue,  1 May 2012 20:07:31 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so375421pbc.31 for <ietf@ietf.org>; Tue, 01 May 2012 20:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zxLacN/5at53O2jvU9cs0RvvkS/4OXmTL30vB2yTBvI=; b=0Vy9+0Dh54cH95XR5Q1mM5Oovdl5C6xj5myVLQ7EeXo7HmWfh9SwX+V731LCljQWUo PBDE0USlHrSPPWTnIm/7whr1EkqmX8OnJB6FIrVBWnvKPcN/Z7h47e7JNU0+x+87iH86 PKdL9MjO7/dG57CON+b2z0hX5o3w3DYUg1szFUNrwf1xlb2Jw+7b+62vFN47brJeWW4J AGVQMRApm3+oaTOKnuafCpqFtXfqnMfLtEvJXZJWTxJqlZvOGHJ2TOLbQnvUfAvpjRzK p9bSO/w3CxF/8qmYRnfap6M0htBw2UEqGNIGYcZy7ZQ2xKxMPCruf26hTAqHZ6660FXu xS5A==
Received: by 10.68.211.197 with SMTP id ne5mr1427233pbc.143.1335928051639; Tue, 01 May 2012 20:07:31 -0700 (PDT)
Received: from polypro.local (66-230-101-239-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.239]) by mx.google.com with ESMTPS id tx9sm632944pbc.10.2012.05.01.20.07.30 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 May 2012 20:07:30 -0700 (PDT)
Message-ID: <4FA0A4F1.1050402@gmail.com>
Date: Tue, 01 May 2012 19:07:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> , <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0A96@DC-US1MBEX4.global.av aya.com>, <8DC137508AE27AAD6CC12654@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0A9C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0A9C@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 03:07:32 -0000

On 5/1/12 5:55 PM, Worley, Dale R (Dale) wrote:
> What would be good patterns for those roles?

I don't know what John has in mind but it strikes me that every
so often we get a wave of new participants (as new topics and/or
work areas are introduced) and it seems to me that it would be
valuable if people who've been through the process a time or
three could help mentor people who are new to the IETF but have
drafts that have been adopted.  Presumably they can help with
process and culture issues, as well.

Melinda


From mary.ietf.barnes@gmail.com  Wed May  2 07:19:01 2012
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 0CCF321F8606 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 07:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.554
X-Spam-Level: 
X-Spam-Status: No, score=-103.554 tagged_above=-999 required=5 tests=[AWL=0.044, 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 qRxKNK9VyEsG for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 07:19:00 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6E021F85FB for <ietf@ietf.org>; Wed,  2 May 2012 07:19:00 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so565248vcb.31 for <ietf@ietf.org>; Wed, 02 May 2012 07:18:59 -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=ykEfZq/KrM//2jR7vntvSaIsJp3LDQgEVDQZddkj+ko=; b=Acvlbk/zuxmHf7GocFhQgLuviJj/8uKJuV0l8E8qOMOww08T1LYI41NYkOpIeNfHe9 eQpf2tMkqwjocBVhmrSPrc2dZf2pqbjPQZpEMhdaKI+osEXSdQ7rAB/1vDEtdwGkqiOV fwGvu0jSlXeRTufBV5pwdKAtyFEaMS+RD8ecJm5u3oao7KYTbgjW8KvFmBO1T+G9X1d/ 5Q3KlnoS9VavBnwLAUNS5RVMqUCHQpq7eW0WXUekZ6v0ly6LB1jaYZACZC2B7tMsrDME 67rRLph0WcfCQ295LiqSsfEjmA2bCbOMz5pI1n9A8AbcZkyGnIfK3Fp8UUZuqPiHGNrs cRAA==
MIME-Version: 1.0
Received: by 10.220.107.6 with SMTP id z6mr29080384vco.37.1335968339749; Wed, 02 May 2012 07:18:59 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Wed, 2 May 2012 07:18:59 -0700 (PDT)
In-Reply-To: <005901cd2801$8214c510$863e4f30$@us>
References: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.com> <005901cd2801$8214c510$863e4f30$@us>
Date: Wed, 2 May 2012 09:18:59 -0500
Message-ID: <CAHBDyN4zePciBgmKO95GHXcO1Grn6_bVZvH7mR4VfFssR-o-AQ@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d0438ed0f526bca04bf0e5eb2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 14:19:01 -0000

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

Here is a very timely article on this topic:
http://news.mentornet.net/content/why-getting-women-stem-matters

Note, this is from an organization that is focused on getting diversity in
engineering and science, so for those interested in more information on
this topic, there are many, many other articles on that website.

I also agree with Thomas and others that IETF would definitely benefit as a
whole by setting up a mentor program.  There is information on how an
organization can get involved with mentor net to setup a mentoring program
here:
http://www.mentornet.net/societies.aspx

Note, that ISOC already has some programs in place that encourage new
leaders in the industry as well as participation from developing developing
countries:
 - Next Generation Leaders Program:
http://www.internetsociety.org/what-we-do/leadership-programmes/next-generation-leaders-ngl-programme
 - the IETF Fellowship Program:
http://www.internetsociety.org/what-we-do/education-and-leadership-programmes

I personally was not at all aware of the NGL program.  As I understand it,
the Fellowship Program is already setup to assign a mentor to each of the 5
individuals.

So, it may be worth discussing whether this ought to be part of the ISOC
programs (or an enhancement to the NGL program) or something that does fall
directly under the IETF similar to the newcomer events.

Regards,
Mary.

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

Here is a very timely article on this topic:<div><a href=3D"http://news.men=
tornet.net/content/why-getting-women-stem-matters">http://news.mentornet.ne=
t/content/why-getting-women-stem-matters</a></div><div><br></div><div>Note,=
 this is from an organization that is focused on getting diversity in engin=
eering and science, so for those interested in more information on this top=
ic, there are many, many other articles on that website.</div>
<div><br></div><div>I also agree with Thomas and others that IETF would def=
initely benefit as a whole by setting up a mentor program. =A0There is info=
rmation on how an organization can get involved with mentor net to setup a =
mentoring program here:</div>
<div><a href=3D"http://www.mentornet.net/societies.aspx">http://www.mentorn=
et.net/societies.aspx</a></div><div><br></div><div>Note, that ISOC already =
has some programs in place that encourage new leaders in the industry as we=
ll as participation from developing developing countries:</div>
<div>=A0- Next Generation Leaders Program:=A0</div><div><a href=3D"http://w=
ww.internetsociety.org/what-we-do/leadership-programmes/next-generation-lea=
ders-ngl-programme">http://www.internetsociety.org/what-we-do/leadership-pr=
ogrammes/next-generation-leaders-ngl-programme</a></div>
<div>=A0- the IETF Fellowship Program:</div><div><a href=3D"http://www.inte=
rnetsociety.org/what-we-do/education-and-leadership-programmes">http://www.=
internetsociety.org/what-we-do/education-and-leadership-programmes</a></div=
>
<div><br></div><div>I personally was not at all aware of the NGL program. =
=A0As I understand it, the Fellowship Program is already setup to assign a =
mentor to each of the 5 individuals.=A0</div><div><br></div><div>So, it may=
 be worth discussing whether this ought to be part of the ISOC programs (or=
 an enhancement to the NGL program) or something that does fall directly un=
der the IETF similar to the newcomer events.=A0</div>
<div><br></div><div>Regards,</div><div>Mary.=A0</div>

--f46d0438ed0f526bca04bf0e5eb2--

From mary.ietf.barnes@gmail.com  Wed May  2 08:08:45 2012
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 1C0F421F85E5 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:08:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level: 
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=0.042, 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 S17Mezl8Xx5v for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:08:44 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8919621F8543 for <ietf@ietf.org>; Wed,  2 May 2012 08:08:44 -0700 (PDT)
Received: by yenq7 with SMTP id q7so940966yen.31 for <ietf@ietf.org>; Wed, 02 May 2012 08:08:44 -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=3CDYZ6u1U9qKUZ5Pr2FyO2BYL1fO37Vo/2luztX+7PQ=; b=W+IkK6mVSkHQP9gO4x7/yvrNXOKneRd534GJAqV46QxpEr2p6bJMht9Mesr+KP23Hj lhwNfQroR3NgKviUPxFIhk2P8xXPGWbh+50NgmrC2o4EBBZ5QWYeYj6vnU4xboLxS29H 8qXjPFlNdUguZqrfImo+BX0Ip97Xlnjj4zEptoyS3ZIKFMUYMmdH9x0DXmdQflRd8Iza qoJLHB5rjZyDEP6YAX+6LSZzmbJoe2DfUKIFfCE1GzPfqUarf8SY2QnQOwuXzhBdrRah 3Ait6Au0xt+0v0xHE+vugYmiwNsMIm0lxCwoeXsQ965nIdWszorRuM1MkoIVwQ+JlMLT KVyw==
MIME-Version: 1.0
Received: by 10.236.78.74 with SMTP id f50mr31157541yhe.26.1335971324110; Wed, 02 May 2012 08:08:44 -0700 (PDT)
Received: by 10.236.176.102 with HTTP; Wed, 2 May 2012 08:08:44 -0700 (PDT)
Date: Wed, 2 May 2012 10:08:44 -0500
Message-ID: <CAHBDyN6JNQ4FhkxfniEk7t9Xcpgea-CCefRp+TzA16g=kLOj2Q@mail.gmail.com>
Subject: Mailing list for IETF women
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf300fad3b34265204bf0f104d
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:08:45 -0000

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

There have been some offline discussions as to how we can improve the
situation and encourage the participation of women in the IETF.   One of
the things was a mailing list.  There actually already is one hosted on
ietf.org (setup by Mirjam and Margaret) -systers@ietf.org:
https://www.ietf.org/mailman/listinfo/systers
In the past, lunches have been organized.  So, I do encourage the women to
join the list if you aren't already a member.

Regards,
Mary.

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

There have been some offline discussions as to how we can improve the situa=
tion and encourage the participation of women in the IETF. =A0 One of the t=
hings was a mailing list. =A0There actually already is one hosted on <a hre=
f=3D"http://ietf.org">ietf.org</a> (setup by Mirjam and Margaret) -<a href=
=3D"mailto:systers@ietf.org">systers@ietf.org</a>: =A0 =A0<a href=3D"https:=
//www.ietf.org/mailman/listinfo/systers">https://www.ietf.org/mailman/listi=
nfo/systers</a><div>
In the past, lunches have been organized. =A0So, I do encourage the women t=
o join the list if you aren&#39;t already a member. =A0</div><div><div><br>=
</div><div>Regards,</div><div>Mary.=A0</div></div>

--20cf300fad3b34265204bf0f104d--

From scott.brim@gmail.com  Wed May  2 08:11:41 2012
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 555D821F860E for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:11: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 cBkDyqDWC1+b for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:11:40 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B19AC21F85D8 for <ietf@ietf.org>; Wed,  2 May 2012 08:11:40 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so628600vcb.31 for <ietf@ietf.org>; Wed, 02 May 2012 08:11: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:from:date:message-id:subject:to :cc:content-type; bh=G7eQt+liuczXodYVPvXULm6Z+rDlPQmHnGykP9htB4s=; b=xGBHpvjshQozMsZwPv6bgJoGxaITEk4fRTxZUwJZC+lp4fRtdeeix8bJez05idM3Ed mfpohizvzxdL+jQWFExZ7o2sSehywJ0RQMlHPVBA/cu4tR8HXCJg76HlW/4iIhtk47Oe OarJ8JNhQoyec10huPcq0EsS6/QrutdX/TYZzfvmTDWTTBYDxnNy3+3d+UWwZN9iuXh5 vpZ7NeA/kDS/ok+S3r1CieWnIGNVSV+GaauNneQJpBril5hUCWXx/s9/xwhPQabYPCmS 3yvK1nmXnw8cha2JLBKoGMkMXlzbfT7+9BExB7OlFfiOyNlZlHvmvsGtNVGmLBuQMY9d kYpA==
Received: by 10.52.180.232 with SMTP id dr8mr24704763vdc.111.1335971499780; Wed, 02 May 2012 08:11:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.203.132 with HTTP; Wed, 2 May 2012 08:11:19 -0700 (PDT)
In-Reply-To: <4FA0A4F1.1050402@gmail.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <8DC137508AE27AAD6CC12654@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0A9C@DC-US1MBEX4.global.avaya.com> <4FA0A4F1.1050402@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 2 May 2012 11:11:19 -0400
Message-ID: <CAPv4CP_mSx1VaG+dLASHjP0A4Y_J=d-=qGLfWCTKn=qvk4KLJg@mail.gmail.com>
Subject: Re: Is the IETF aging?
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 15:11:41 -0000

On Tue, May 1, 2012 at 11:07 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> I don't know what John has in mind but it strikes me that every
> so often we get a wave of new participants (as new topics and/or
> work areas are introduced) and it seems to me that it would be
> valuable if people who've been through the process a time or
> three could help mentor people who are new to the IETF but have
> drafts that have been adopted.

That happens pretty regularly.

> Presumably they can help with
> process and culture issues, as well.

Here I'm not so sure.  While retaining the basic mission statement,
IETF culture _should_ change, to fit the times and to be relevant.
I'm geezer category and I'm hoping the newer folks come up with a lot
more revolution than they have so far.  I look forward to it.

Scott

From dhc@dcrocker.net  Wed May  2 08:36:32 2012
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 4884721E8019 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.958
X-Spam-Level: 
X-Spam-Status: No, score=-5.958 tagged_above=-999 required=5 tests=[AWL=0.641,  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 ClfBIvjxBJmc for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 08:36:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 74A9C21E8034 for <ietf@ietf.org>; Wed,  2 May 2012 08:36:30 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q42FaQfL032551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 May 2012 08:36:27 -0700
Message-ID: <4FA15477.8040808@dcrocker.net>
Date: Wed, 02 May 2012 08:36:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <CAHBDyN7RUFcKVy=Uhj1GAoM3WQM62eBmM-fVhps9kccc_AULiQ@mail.gmail.com> <8DC137508AE27AAD6CC12654@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0A9C@DC-US1MBEX4.global.avaya.com> <4FA0A4F1.1050402@gmail.com> <CAPv4CP_mSx1VaG+dLASHjP0A4Y_J=d-=qGLfWCTKn=qvk4KLJg@mail.gmail.com>
In-Reply-To: <CAPv4CP_mSx1VaG+dLASHjP0A4Y_J=d-=qGLfWCTKn=qvk4KLJg@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.17]); Wed, 02 May 2012 08:36:27 -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: Wed, 02 May 2012 15:36:32 -0000

On 5/2/2012 8:11 AM, Scott Brim wrote:
> Here I'm not so sure.  While retaining the basic mission statement,
> IETF culture_should_  change, to fit the times and to be relevant.


While true, it should be a balancing act, between adapting methods to 
the times, while preserving core values.

Original core values of IETF technical work were relative simplicity of 
design and immediacy of utility.  We pressed to get something useful 
working as quickly as we could and then to evolve it.

That still happens.  Sometimes.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From lars@netapp.com  Wed May  2 10:53:01 2012
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 9B3D121F84A6 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 10:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.633
X-Spam-Level: 
X-Spam-Status: No, score=-10.633 tagged_above=-999 required=5 tests=[AWL=-0.034, 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 n6COZf97H5mk for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 10:53:00 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 97B0521F8463 for <ietf@ietf.org>; Wed,  2 May 2012 10:53:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.75,518,1330934400";  d="p7s'?scan'208";a="644806599"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 02 May 2012 10:53:00 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q42Hr0NW010016; Wed, 2 May 2012 10:53:00 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.117]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0247.003; Wed, 2 May 2012 10:53:00 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Mailing list for IETF women
Thread-Topic: Mailing list for IETF women
Thread-Index: AQHNKHV4HgIl/9SOoECHxMR6w+Xb2Za3PUEA
Date: Wed, 2 May 2012 17:52:59 +0000
Message-ID: <1D558AB9-E4A6-4667-9EDC-712320CFE1A9@netapp.com>
References: <CAHBDyN6JNQ4FhkxfniEk7t9Xcpgea-CCefRp+TzA16g=kLOj2Q@mail.gmail.com>
In-Reply-To: <CAHBDyN6JNQ4FhkxfniEk7t9Xcpgea-CCefRp+TzA16g=kLOj2Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_56380610-F603-4756-BB3C-C52A38DE2F1D"; protocol="application/pkcs7-signature"; micalg=sha1
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: Wed, 02 May 2012 17:53:01 -0000

--Apple-Mail=_56380610-F603-4756-BB3C-C52A38DE2F1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Also related: =
http://cms.comsoc.org/eprise/main/SiteGen/n2women/Content/Home.html

There is a meeting at least once a year at SIGCOMM.

Lars

On May 2, 2012, at 12:08, Mary Barnes wrote:

> There have been some offline discussions as to how we can improve the
> situation and encourage the participation of women in the IETF.   One =
of
> the things was a mailing list.  There actually already is one hosted =
on
> ietf.org (setup by Mirjam and Margaret) -systers@ietf.org:
> https://www.ietf.org/mailman/listinfo/systers
> In the past, lunches have been organized.  So, I do encourage the =
women to
> join the list if you aren't already a member.
>=20
> Regards,
> Mary.


--Apple-Mail=_56380610-F603-4756-BB3C-C52A38DE2F1D
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDUwMjE3NTMwMFowIwYJKoZIhvcNAQkEMRYEFBU6
5UaSeBv8cv6BFrczQdrS/PC7MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAGdFPlCw
IS88iq2itqkbGp0cYhOOJa8IJLvH33qIHVNrmvlqvue5v6iDBOkQag/PcW/+em7hugk4u8yQYpOg
1a74FiMC3pt4aajmeuJbPw31HWPSj+35tuPEPaIHWj+qYSe9uoZVm/pe16yjCHrPPWdEL+idpuqy
k5ITNonog6vg1PPmpOBgJQw1dSnDQtR6FhFlWvMC2Fgpw/6Yc2jTnvDuyzYZChiWsJFiPzG4O9+U
piIg/7iXSp11xFdWXRUlFm3kcuv/bppqYOkwmXMIgMX0yzooUyu/5fTsQuEBkOr7Z0C+raOCMaIn
YnLadklzL6+EbBssa2fKlqYPx4b8nEwAAAAAAAA=

--Apple-Mail=_56380610-F603-4756-BB3C-C52A38DE2F1D--

From ted.ietf@gmail.com  Wed May  2 11:16:51 2012
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 6C4C121F84FB for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 11:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.429
X-Spam-Level: 
X-Spam-Status: No, score=-3.429 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q0=0.303]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQ50HAEz8A66 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 11:16:51 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id DC00411E8081 for <ietf@ietf.org>; Wed,  2 May 2012 11:16:50 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so822262vcb.31 for <ietf@ietf.org>; Wed, 02 May 2012 11:16:50 -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=sIwLWMj7YMWbpi0nBsANj9QLYZAtMMuejFgG/Qz71WY=; b=KhThV8LoMSASVfuOgM+pctjUF5Vk1mmZf+8Neu2FxYRVhiV9sox/UYuxlrB1mD9mS4 gVh/bSh+35Tu/AuXy0B3e4LTbOLc7Kp/BDg0bYxyMXfAc6c52lnHzXw3CQ6Ur7FuFw4V 4tmmG9yt3OcIYmfVhZbyRNoHz18gNPiMg8SF7j+c1atfb1BdknmGWWCrJpNviKLY9G93 t4uhyJXAyhxtaq732rb6Eoy5YjYjFlVa1hDqJcnNDLBxV/2jdwz587yLuZoYONXnp0Ab KdEoX64DwmTlU83xyYgygKIYf4xFjVK8eqpSjeezurf8xQ+0UB01N2WgYSNYafKmYI8U zMeA==
MIME-Version: 1.0
Received: by 10.52.89.106 with SMTP id bn10mr25211960vdb.116.1335982610472; Wed, 02 May 2012 11:16:50 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Wed, 2 May 2012 11:16:50 -0700 (PDT)
Date: Wed, 2 May 2012 11:16:50 -0700
Message-ID: <CA+9kkMDQNDBdyeJV_-395JMFcK_t31mRgOFPLnMsNs4q1t0_1Q@mail.gmail.com>
Subject: Mailing list for LGBTQ participants in the IETF
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 18:16:51 -0000

For those not aware of it, there is a long-standing mailing list for
LGBTQ participants in
the IETF: ietf-motss@lists.pensieve.org (with subscription at
ietf-motss-request@lists.pensive.org).


About the IETF-MOTSS List:
 ----- --- ---------- -----

 This list is for use by members of the IETF-MOTSS (Members of the Same
 Sex, an out of date term for lesbian, gay, bi, transgendered, etc.)
 community.

 Topics of discussion include social events held during IETF meetings
 (traditionally called "anti-socials" if they occur at the same time,
 but separate from, the main social or "sub-socials" if they occur
 within the main social), and anything else of interest to the
 community.

regards,

Ted

From hsantos@santronics.com  Tue May  1 10:20:08 2012
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D4A21E83AA for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:20:08 -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_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 wByM+QOBIine for <ietf@ietfa.amsl.com>; Tue,  1 May 2012 10:20:07 -0700 (PDT)
Received: from pop3.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6B621E8015 for <ietf@ietf.org>; Tue,  1 May 2012 10:20:05 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6767; t=1335892799; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=p1N+unO EIRzAtDvsBQ6cBb+L+SI=; b=KBK7E1NEmsjpHWmsiKK55GyrxJMtEE8QJxkkM3W x1b1NBaWxOy5uLiDvcthna1L1i8H0vZ8Hx4rZXYlsKJCGQ2g2s9qU79Ee88ynwZ1 ksl82+XEAFzOwE+5hUB1N9iYBZ+MYqQ0chHZGkcis/F5YMtQVhTE/FSi3AvHucuf Si64=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 01 May 2012 13:19:59 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 504641010.42666.5976; Tue, 01 May 2012 13:19:58 -0400
Message-ID: <4FA01B50.1010100@santronics.com>
Date: Tue, 01 May 2012 13:20:16 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com>	<CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com>	<20120501000305.GL335@mip.aaaaa.org> <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com>
In-Reply-To: <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700
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, 01 May 2012 17:20:08 -0000

Fred Baker wrote:
> On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:
> 
>> This PBS interview with Harvey Mudd president Maria Klawe, on the
>> subject of why fewer women go into tech & engineering fields, is
>> worth watching:
>>
>> http://www.pbs.org/newshour/extra/video/blog/2012/04/college_president_discusses_wo.html
> 
> This is a discussion that comes up periodically.
> 
> If you want my opinion (nobody asked, but I will presume that someone is wondering), the corollary is "why aren't more students interested in math/science?". I'll observe that there are relatively few teachers that I can say "inspired" me to think their their directions; far-too-many years later, I could probably name them. Two were English teachers, one was a Math teacher, tenth grade geometry, one taught 7th grade Geography, and one taught senior Calculus. And, oh, I liked some of my college profs, but in this context my views were probably formed before I got there.
> 
> What if teachers were measured on a survey at the end of a semester or a year that asked "does teacher <> make <> interesting to you?".

+1.

What about other minorities?  Is the recruitment levels the same? 
Public funded, social programs to fill certain needs? Both at the 
school and business levels?

A Puerto Rican from the Sough Bronx, I wanted to go to the vocational 
school up the block - Alfred E. Smith.  AP/College bounds programs 
were presented to me. I didn't know enough to see it or even dream 
about it.

A HS counselor helped with showing the availability of AA/Minority 
college grant programs which included girls among the selected group 
she called to her office.  Otherwise, while a good grades student, I 
wasn't thinking about college. I selected Drexel only because a 
recruiter came to the HS showing a photo with white, black, spanish 
and women all wearing cool Drexel Engineering helmets!  I selected 
Chemical Engineering because I saw they made the most salary as a 
co-op student among all degrees! I had no idea how brutal the Chemical 
Engineering curriculum would be.

But I had even failed a HS class called "Computers" that introduced 
this thing called FORTRAN using some punch card thingy.  So I was 
presented with even more Pre-college Grant programs to learn about 
applied engineering with computers, and it still took an act of GOD 
with a lightning strike knocking out a PDP-11, forcing us to do the 
engineering problem translation to BASIC on paper by hand, and only 
then did I finally get the AH-AH of GIGO!

And even with all that, it still took AA programs it finally get a job 
because it was mist of a recession that did not help many get a job 
and this dude called Ted Turner speaking in our graduation getting 
loud boos recommending that we go into the MILITARY!

IMO, background is very important. Unless there are active social 
programs and recruitment efforts A.K.A "Marketing," I don't think 
there will a natural tendency of the so called "minority segment" of 
(any) society that are not often encouraged or have the family 
background already, to explore or even think about the science related 
industry as a career.

Take myself. I was deep into computers and the blossoming world of 
Telecomputing, micro-at-home era. The wife (Technical Sales Engineer) 
and I specifically did not want our two new girls to get into the same 
High Tech business as Daddy and Mommy were in.  No Way! Doctors, 
Lawyers perhaps! No way ENGINEER!  It was too tough and I also saw how 
tough it was for my women peers at Mobil and Westinghouse with an 
extreme competition going on, and quite frankly faced tough family 
decisions at some point. In fact, during some pending layoffs at big 
W, I was told I was going to stay and found out a pregnant software 
programmer in the group was going to get laid off. With my existing 
"Fire in my Belly" to quit and start my business already, I took the 
opportunity and asked the boss to keep her and to lay me off instead 
so I can get the benefits, Cobra, etc.  If I had quit, I lose all that.

I had already saw that the salaries were different too. The idea of 
working for a corporation lost its appear when I saw a lost of loyalty 
with people of 20, 25-30 years who had dedicated their engineering 
lives were now forced to get early retirement, laid off or fired. 
With no more Federal funding for Advanced Energy programs and the even 
Defense in AI, Robots and Star Wars, etc, I did not want my two girls 
to go into these life commitment hard sciences. I didn't push the 
computers at home on them at all. I didn't teach them about the idea 
of "programming" etc. Perhaps only to play games, and perhaps to use 
the early on-disc encyclopedias. They were using Apple stuff at school 
anyway and that was good enough for us.

Today, both living in NYC, one works for Sony Music productions 
department and the oldest is a successful independent artist making 
more money that I can ever imagine possible. She was even a contestant 
on Bravo's first season "Next Great Artist."  The only thing that 
first worried me was whether she would need to cut off an ear before 
getting recognized in the art world! :)

We have to consider that the engineering life is not always ideal for 
anyone. Its sounds nice, it does give one more respect among their 
family peers, helps secure jobs (when available), better pay, etc, but 
its takes a very high commitment and it is very competitive to keep up 
even if one wishes to stay in one position and not interested to be 
move ahead.  That presents employer decisions with competitive 
compensation managers need to make. Younger, lower salary recruitement 
can do the same job, etc, so generally by 30, aging engineers need to 
make life career movements and changes.

For women, well, life is life, it is what it is, they have it harder 
to make family oriented decisions and they are in a position to be, 
well, let my artist daughter, Jaclyn Santos, show you what woman are 
facing with her "Super Mom, Super Executive, Super Ho!"
painting:

        http://www.jaclynsantos.com/images/large/g.jpg

Finally, for the IETF - well, gotta know first what it wants.  What 
does recruiting more woman (or other minorities for that matter) mean 
to it?  I personally think its just a reflection of whats going on in 
the market.  Its not like the IETF is on the radar for anyone to 
pursue unless they are presented with it somewhere, somehow, at work 
most likely with a position where IETF work is part of the job 
production.   I say that is a very very narrow niche job or goal.

PS: These are my views and says nothing about life other than my own.

-- 
Sincerely

Hector Santos
http://www.santronics.com
jabber: hector@jabber.isdg.net


From hannes.tschofenig@gmx.net  Wed May  2 12:14:23 2012
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 0649621E8099 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 BmtSh+9J9g5s for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:14:22 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id D69DA21E8095 for <ietf@ietf.org>; Wed,  2 May 2012 12:14:21 -0700 (PDT)
Received: (qmail invoked by alias); 02 May 2012 19:14:20 -0000
Received: from unknown (EHLO [10.2.4.113]) [64.9.249.121] by mail.gmx.net (mp035) with SMTP; 02 May 2012 21:14:20 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18f+7wV280fw5OYpmymcR4S4cnaeCQXBPeosDJ3kA qE9Pu1EEolUsSE
Subject: Re: Is the IETF aging?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>
Date: Wed, 2 May 2012 22:14:16 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 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: Wed, 02 May 2012 19:14:23 -0000

Hi PHB,=20

the IETF is not like an enterprise where you can decide (as part of the =
hiring process) what characteristics your employees should have.=20

In a volunteer organization the offered topics drive the participation. =
Ask yourself: what you as someone who just finished a university =
education want to hang around in the IETF to standardize yet another =
IPv4/IPv6 transition mechanism or to participate in the MPLS-TP =
discussions?

When people suggest new work to the IETF they often see a strange =
reaction. I remember when Mozilla came to the IETF and proposed to work =
on the privacy topic "Do Not Track". I couldn't find support for doing =
the work in the IETF. I don't exactly know why people didn't like it but =
the W3C immediately picked it up and had seen lots of new companies =
(mostly from the advertising industry) joining the W3C.=20

Ciao
Hannes

On Apr 27, 2012, at 5:06 PM, Phillip Hallam-Baker wrote:

> A question arose on the RFC-interest list, I observed that 20 years
> ago I was one of the youngest IETF participants and 20 years later
> that still seems to be the case.
>=20
> I see some grad students and some postdocs in their 20s but not as
> many as I think there should be. By now at least a third of the
> organization should be younger than me, preferably half. That is
> certainly not what I see when I attend IETFs. And yes, the lack of
> women is also highly noticeable.
>=20
> If this is the case it should worry us greatly. But first I think we
> need to determine if it is the case or not. I suggest an optional
> demographic survey of participants in the next IETF meeting to be
> repeated at regular intervals (no more than 5 years apart).
>=20
> People can argue about process, RFC formats and governance but it
> should be beyond argument that any institution that cannot recruit
> younger members is going to die.
>=20
> --=20
> Website: http://hallambaker.com/


From kpfleming@digium.com  Wed May  2 12:24:59 2012
Return-Path: <kpfleming@digium.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A090121E80B0 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.423
X-Spam-Level: 
X-Spam-Status: No, score=-106.423 tagged_above=-999 required=5 tests=[AWL=0.176, 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 4xZg8TSYpYkL for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:24:58 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id B7ECA21E80AD for <ietf@ietf.org>; Wed,  2 May 2012 12:24:58 -0700 (PDT)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1SPfAY-0007fx-BA for ietf@ietf.org; Wed, 02 May 2012 14:24:58 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 4777CD8004 for <ietf@ietf.org>; Wed,  2 May 2012 14:24:58 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lq5ylH4uuUio for <ietf@ietf.org>; Wed,  2 May 2012 14:24:57 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id CB4C2D8002 for <ietf@ietf.org>; Wed,  2 May 2012 14:24:57 -0500 (CDT)
Message-ID: <4FA189FB.6040909@digium.com>
Date: Wed, 02 May 2012 14:24:43 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
In-Reply-To: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
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, 02 May 2012 19:24:59 -0000

On 05/02/2012 02:14 PM, Hannes Tschofenig wrote:
> When people suggest new work to the IETF they often see a strange reaction. I remember when Mozilla came to the IETF and proposed to work on the privacy topic "Do Not Track". I couldn't find support for doing the work in the IETF. I don't exactly know why people didn't like it but the W3C immediately picked it up and had seen lots of new companies (mostly from the advertising industry) joining the W3C.

As a counter-point (which supports your position <G>) the creation of 
the CODEC WG has actually brought a number of people/companies into 
active IETF involvement that were likely never involved before.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

From dhc@dcrocker.net  Wed May  2 12:58:14 2012
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 0F7A221E80DF for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:58:14 -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 oL8Yq4rQGFnK for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 12:58:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id DE48C21E80BE for <ietf@ietf.org>; Wed,  2 May 2012 12:58:09 -0700 (PDT)
Received: from [10.2.4.28] ([64.9.249.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q42Jw91X004561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 2 May 2012 12:58:09 -0700
Message-ID: <4FA191CD.5010301@dcrocker.net>
Date: Wed, 02 May 2012 12:58:05 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
In-Reply-To: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.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.17]); Wed, 02 May 2012 12:58:09 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 19:58:14 -0000

Howevermuch the answer to the Subject question was not true when the 
thread started, it's true now...

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mary.ietf.barnes@gmail.com  Wed May  2 13:06:48 2012
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 DE9C621E80E8 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 13:06:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.725
X-Spam-Level: 
X-Spam-Status: No, score=-102.725 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N0jC9bqxQL1v for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 13:06:47 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 13C5021E80BB for <ietf@ietf.org>; Wed,  2 May 2012 13:06:46 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so919844vbb.31 for <ietf@ietf.org>; Wed, 02 May 2012 13:06:46 -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=a8zBWFRsoUnJB8x/OAOLnK08f/y/xs2wkooFysOZIio=; b=l26mMmcm/f1OlWaOqD6ln4XpI7G3j1j8txyXRxzoFXQntOpBpEbbSMXJa8d9QMObMy 8FezIPOJKOe2UfweE6ssAbpzoTpPs2ZPqW3RlsBYZXVGTiAbPsSH6+kr8qQWYxquGWgf 4DG7d1g25A01pmmlEQeTE62lqd6la/1TDw2mdNFFFD2rSg1JbZOncULppIiSCIAs//oh rGn+dlAiYuBAd/OlL9qwtZ7+VbxABZCtRkbX+o7nN+Cq1J03ioXnf/EaIFrwyDWmIfuM xe7uJNsxhV2MZEWh7qTMf15MAove+4vSail54kpStBbRJxuhmp0Vtr6Jui0vrP+lmuhw L9Cg==
MIME-Version: 1.0
Received: by 10.52.92.204 with SMTP id co12mr19128786vdb.105.1335989206400; Wed, 02 May 2012 13:06:46 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Wed, 2 May 2012 13:06:46 -0700 (PDT)
In-Reply-To: <4FA01B50.1010100@santronics.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <20120501000305.GL335@mip.aaaaa.org> <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com> <4FA01B50.1010100@santronics.com>
Date: Wed, 2 May 2012 15:06:46 -0500
Message-ID: <CAHBDyN56_xa1-oXTnodZ7QAeZMVWMqBYe8MFAJH65ivd9LsBHg@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Hector Santos <hsantos@santronics.com>
Content-Type: multipart/alternative; boundary=bcaec50162f3123e1104bf133a39
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 20:06:49 -0000

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

Note that mentor net that I mentioned in another email is also focused on
increasing minorities in engineering: http://www.mentornet.net/
They are always looking for new mentors:
http://www.mentornet.net/mentor.aspx

If your child doesn't seem to have the aptitude for engineering, then
certainly you shouldn't push them in that direction.  But, I do have to
wonder if you wouldn't have treated a son differently.  As you likely
figured out, you really do need to allow your child to find their own
interests and make their own career decisions,while making sure they  have
exposure to a broad range of areas.   Unfortunately, a lot of public
schools don't give kids that exposure these days - they often cut the
arts/music and there is almost always an extremely high demand for science
and math teachers.

As far as my kids, my oldest son is a Freshman studying mechanical
engineering (entirely his decision, but he did get awards for the top math
and science student, so it does seem a sensible choice). My younger son is
the artsy one although he does quite well in math and science.  I can't see
either or them ever getting involved in IETF - they've gone with me to
meetings (and have more t-shirts than many regular attendees) and they were
turned off by the overall geekiness (so it's not just women ;)  and told me
that I actually seem normal relative to everyone else ;)

Mary.

On Tue, May 1, 2012 at 12:20 PM, Hector Santos <hsantos@santronics.com>wrote:

> Fred Baker wrote:
>
>> On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:
>>
>>  This PBS interview with Harvey Mudd president Maria Klawe, on the
>>> subject of why fewer women go into tech & engineering fields, is
>>> worth watching:
>>>
>>> http://www.pbs.org/newshour/**extra/video/blog/2012/04/**
>>> college_president_discusses_**wo.html<http://www.pbs.org/newshour/extra/video/blog/2012/04/college_president_discusses_wo.html>
>>>
>>
>> This is a discussion that comes up periodically.
>>
>> If you want my opinion (nobody asked, but I will presume that someone is
>> wondering), the corollary is "why aren't more students interested in
>> math/science?". I'll observe that there are relatively few teachers that I
>> can say "inspired" me to think their their directions; far-too-many years
>> later, I could probably name them. Two were English teachers, one was a
>> Math teacher, tenth grade geometry, one taught 7th grade Geography, and one
>> taught senior Calculus. And, oh, I liked some of my college profs, but in
>> this context my views were probably formed before I got there.
>>
>> What if teachers were measured on a survey at the end of a semester or a
>> year that asked "does teacher <> make <> interesting to you?".
>>
>
> +1.
>
> What about other minorities?  Is the recruitment levels the same? Public
> funded, social programs to fill certain needs? Both at the school and
> business levels?
>
> A Puerto Rican from the Sough Bronx, I wanted to go to the vocational
> school up the block - Alfred E. Smith.  AP/College bounds programs were
> presented to me. I didn't know enough to see it or even dream about it.
>
> A HS counselor helped with showing the availability of AA/Minority college
> grant programs which included girls among the selected group she called to
> her office.  Otherwise, while a good grades student, I wasn't thinking
> about college. I selected Drexel only because a recruiter came to the HS
> showing a photo with white, black, spanish and women all wearing cool
> Drexel Engineering helmets!  I selected Chemical Engineering because I saw
> they made the most salary as a co-op student among all degrees! I had no
> idea how brutal the Chemical Engineering curriculum would be.
>
> But I had even failed a HS class called "Computers" that introduced this
> thing called FORTRAN using some punch card thingy.  So I was presented with
> even more Pre-college Grant programs to learn about applied engineering
> with computers, and it still took an act of GOD with a lightning strike
> knocking out a PDP-11, forcing us to do the engineering problem translation
> to BASIC on paper by hand, and only then did I finally get the AH-AH of
> GIGO!
>
> And even with all that, it still took AA programs it finally get a job
> because it was mist of a recession that did not help many get a job and
> this dude called Ted Turner speaking in our graduation getting loud boos
> recommending that we go into the MILITARY!
>
> IMO, background is very important. Unless there are active social programs
> and recruitment efforts A.K.A "Marketing," I don't think there will a
> natural tendency of the so called "minority segment" of (any) society that
> are not often encouraged or have the family background already, to explore
> or even think about the science related industry as a career.
>
> Take myself. I was deep into computers and the blossoming world of
> Telecomputing, micro-at-home era. The wife (Technical Sales Engineer) and I
> specifically did not want our two new girls to get into the same High Tech
> business as Daddy and Mommy were in.  No Way! Doctors, Lawyers perhaps! No
> way ENGINEER!  It was too tough and I also saw how tough it was for my
> women peers at Mobil and Westinghouse with an extreme competition going on,
> and quite frankly faced tough family decisions at some point. In fact,
> during some pending layoffs at big W, I was told I was going to stay and
> found out a pregnant software programmer in the group was going to get laid
> off. With my existing "Fire in my Belly" to quit and start my business
> already, I took the opportunity and asked the boss to keep her and to lay
> me off instead so I can get the benefits, Cobra, etc.  If I had quit, I
> lose all that.
>
> I had already saw that the salaries were different too. The idea of
> working for a corporation lost its appear when I saw a lost of loyalty with
> people of 20, 25-30 years who had dedicated their engineering lives were
> now forced to get early retirement, laid off or fired. With no more Federal
> funding for Advanced Energy programs and the even Defense in AI, Robots and
> Star Wars, etc, I did not want my two girls to go into these life
> commitment hard sciences. I didn't push the computers at home on them at
> all. I didn't teach them about the idea of "programming" etc. Perhaps only
> to play games, and perhaps to use the early on-disc encyclopedias. They
> were using Apple stuff at school anyway and that was good enough for us.
>
> Today, both living in NYC, one works for Sony Music productions department
> and the oldest is a successful independent artist making more money that I
> can ever imagine possible. She was even a contestant on Bravo's first
> season "Next Great Artist."  The only thing that first worried me was
> whether she would need to cut off an ear before getting recognized in the
> art world! :)
>
> We have to consider that the engineering life is not always ideal for
> anyone. Its sounds nice, it does give one more respect among their family
> peers, helps secure jobs (when available), better pay, etc, but its takes a
> very high commitment and it is very competitive to keep up even if one
> wishes to stay in one position and not interested to be move ahead.  That
> presents employer decisions with competitive compensation managers need to
> make. Younger, lower salary recruitement can do the same job, etc, so
> generally by 30, aging engineers need to make life career movements and
> changes.
>
>
> For women, well, life is life, it is what it is, they have it harder to
> make family oriented decisions and they are in a position to be, well, let
> my artist daughter, Jaclyn Santos, show you what woman are facing with her
> "Super Mom, Super Executive, Super Ho!"
> painting:
>
>       http://www.jaclynsantos.com/**images/large/g.jpg<http://www.jaclynsantos.com/images/large/g.jpg>
>
> Finally, for the IETF - well, gotta know first what it wants.  What does
> recruiting more woman (or other minorities for that matter) mean to it?  I
> personally think its just a reflection of whats going on in the market.
>  Its not like the IETF is on the radar for anyone to pursue unless they are
> presented with it somewhere, somehow, at work most likely with a position
> where IETF work is part of the job production.   I say that is a very very
> narrow niche job or goal.
>
> PS: These are my views and says nothing about life other than my own.
>
> --
> Sincerely
>
> Hector Santos
> http://www.santronics.com
> jabber: hector@jabber.isdg.net
>
>

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

Note that mentor net that I mentioned in another email is also focused on i=
ncreasing minorities in engineering:=A0<a href=3D"http://www.mentornet.net/=
">http://www.mentornet.net/</a><div>They are always looking for new mentors=
:</div>
<div><div><a href=3D"http://www.mentornet.net/mentor.aspx">http://www.mento=
rnet.net/mentor.aspx</a></div><div><br><div>If your child doesn&#39;t seem =
to have the aptitude for engineering, then certainly you shouldn&#39;t push=
 them in that direction. =A0But, I do have to wonder if you wouldn&#39;t ha=
ve treated a son differently. =A0As you likely figured out, you really do n=
eed to allow your child to find their own interests and make their own care=
er decisions,while making sure they =A0have exposure to a broad range of ar=
eas. =A0 Unfortunately, a lot of public schools don&#39;t give kids that ex=
posure these days - they often cut the arts/music and there is almost alway=
s an extremely high demand for science and math teachers.=A0</div>
<div><br></div><div>As far as my kids, my oldest son is a Freshman studying=
 mechanical engineering (entirely his decision, but he did get awards for t=
he top math and science student, so it does seem a sensible choice). My you=
nger son is the artsy one although he does quite well in math and science. =
=A0I can&#39;t see either or them ever getting involved in IETF - they&#39;=
ve gone with me to meetings (and have more t-shirts than many regular atten=
dees) and they were turned off by the overall geekiness (so it&#39;s not ju=
st women ;) =A0and told me that I actually seem normal relative to everyone=
 else ;) =A0=A0</div>
<div><br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Tue, May =
1, 2012 at 12:20 PM, Hector Santos <span dir=3D"ltr">&lt;<a href=3D"mailto:=
hsantos@santronics.com" target=3D"_blank">hsantos@santronics.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">Fred=
 Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This PBS interview with Harvey Mudd president Maria Klawe, on the<br>
subject of why fewer women go into tech &amp; engineering fields, is<br>
worth watching:<br>
<br>
<a href=3D"http://www.pbs.org/newshour/extra/video/blog/2012/04/college_pre=
sident_discusses_wo.html" target=3D"_blank">http://www.pbs.org/newshour/<u>=
</u>extra/video/blog/2012/04/<u></u>college_president_discusses_<u></u>wo.h=
tml</a><br>

</blockquote>
<br>
This is a discussion that comes up periodically.<br>
<br>
If you want my opinion (nobody asked, but I will presume that someone is wo=
ndering), the corollary is &quot;why aren&#39;t more students interested in=
 math/science?&quot;. I&#39;ll observe that there are relatively few teache=
rs that I can say &quot;inspired&quot; me to think their their directions; =
far-too-many years later, I could probably name them. Two were English teac=
hers, one was a Math teacher, tenth grade geometry, one taught 7th grade Ge=
ography, and one taught senior Calculus. And, oh, I liked some of my colleg=
e profs, but in this context my views were probably formed before I got the=
re.<br>

<br>
What if teachers were measured on a survey at the end of a semester or a ye=
ar that asked &quot;does teacher &lt;&gt; make &lt;&gt; interesting to you?=
&quot;.<br>
</blockquote>
<br></div></div><div class=3D"im">
+1.<br>
<br>
What about other minorities? =A0Is the recruitment levels the same? Public =
funded, social programs to fill certain needs? Both at the school and busin=
ess levels?<br>
<br>
A Puerto Rican from the Sough Bronx, I wanted to go to the vocational schoo=
l up the block - Alfred E. Smith. =A0AP/College bounds programs were presen=
ted to me. I didn&#39;t know enough to see it or even dream about it.<br>

<br>
A HS counselor helped with showing the availability of AA/Minority college =
grant programs which included girls among the selected group she called to =
her office. =A0Otherwise, while a good grades student, I wasn&#39;t thinkin=
g about college. I selected Drexel only because a recruiter came to the HS =
showing a photo with white, black, spanish and women all wearing cool Drexe=
l Engineering helmets! =A0I selected Chemical Engineering because I saw the=
y made the most salary as a co-op student among all degrees! I had no idea =
how brutal the Chemical Engineering curriculum would be.<br>

<br>
But I had even failed a HS class called &quot;Computers&quot; that introduc=
ed this thing called FORTRAN using some punch card thingy. =A0So I was pres=
ented with even more Pre-college Grant programs to learn about applied engi=
neering with computers, and it still took an act of GOD with a lightning st=
rike knocking out a PDP-11, forcing us to do the engineering problem transl=
ation to BASIC on paper by hand, and only then did I finally get the AH-AH =
of GIGO!<br>

<br>
And even with all that, it still took AA programs it finally get a job beca=
use it was mist of a recession that did not help many get a job and this du=
de called Ted Turner speaking in our graduation getting loud boos recommend=
ing that we go into the MILITARY!<br>

<br>
IMO, background is very important. Unless there are active social programs =
and recruitment efforts A.K.A &quot;Marketing,&quot; I don&#39;t think ther=
e will a natural tendency of the so called &quot;minority segment&quot; of =
(any) society that are not often encouraged or have the family background a=
lready, to explore or even think about the science related industry as a ca=
reer.<br>

<br>
Take myself. I was deep into computers and the blossoming world of Telecomp=
uting, micro-at-home era. The wife (Technical Sales Engineer) and I specifi=
cally did not want our two new girls to get into the same High Tech busines=
s as Daddy and Mommy were in. =A0No Way! Doctors, Lawyers perhaps! No way E=
NGINEER! =A0It was too tough and I also saw how tough it was for my women p=
eers at Mobil and Westinghouse with an extreme competition going on, and qu=
ite frankly faced tough family decisions at some point. In fact, during som=
e pending layoffs at big W, I was told I was going to stay and found out a =
pregnant software programmer in the group was going to get laid off. With m=
y existing &quot;Fire in my Belly&quot; to quit and start my business alrea=
dy, I took the opportunity and asked the boss to keep her and to lay me off=
 instead so I can get the benefits, Cobra, etc. =A0If I had quit, I lose al=
l that.<br>

<br>
I had already saw that the salaries were different too. The idea of working=
 for a corporation lost its appear when I saw a lost of loyalty with people=
 of 20, 25-30 years who had dedicated their engineering lives were now forc=
ed to get early retirement, laid off or fired. With no more Federal funding=
 for Advanced Energy programs and the even Defense in AI, Robots and Star W=
ars, etc, I did not want my two girls to go into these life commitment hard=
 sciences. I didn&#39;t push the computers at home on them at all. I didn&#=
39;t teach them about the idea of &quot;programming&quot; etc. Perhaps only=
 to play games, and perhaps to use the early on-disc encyclopedias. They we=
re using Apple stuff at school anyway and that was good enough for us.<br>

<br>
Today, both living in NYC, one works for Sony Music productions department =
and the oldest is a successful independent artist making more money that I =
can ever imagine possible. She was even a contestant on Bravo&#39;s first s=
eason &quot;Next Great Artist.&quot; =A0The only thing that first worried m=
e was whether she would need to cut off an ear before getting recognized in=
 the art world! :)<br>

<br></div>
We have to consider that the engineering life is not always ideal for anyon=
e. Its sounds nice, it does give one more respect among their family peers,=
 helps secure jobs (when available), better pay, etc, but its takes a very =
high commitment and it is very competitive to keep up even if one wishes to=
 stay in one position and not interested to be move ahead. =A0That presents=
 employer decisions with competitive compensation managers need to make. Yo=
unger, lower salary recruitement can do the same job, etc, so generally by =
30, aging engineers need to make life career movements and changes.<div cla=
ss=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
For women, well, life is life, it is what it is, they have it harder to mak=
e family oriented decisions and they are in a position to be, well, let my =
artist daughter, Jaclyn Santos, show you what woman are facing with her &qu=
ot;Super Mom, Super Executive, Super Ho!&quot;<br>

painting:<br>
<br>
 =A0 =A0 =A0 <a href=3D"http://www.jaclynsantos.com/images/large/g.jpg" tar=
get=3D"_blank">http://www.jaclynsantos.com/<u></u>images/large/g.jpg</a><br=
>
<br>
Finally, for the IETF - well, gotta know first what it wants. =A0What does =
recruiting more woman (or other minorities for that matter) mean to it? =A0=
I personally think its just a reflection of whats going on in the market. =
=A0Its not like the IETF is on the radar for anyone to pursue unless they a=
re presented with it somewhere, somehow, at work most likely with a positio=
n where IETF work is part of the job production. =A0 I say that is a very v=
ery narrow niche job or goal.<br>

<br>
PS: These are my views and says nothing about life other than my own.<br>
<br></div></div><span class=3D"HOEnZb"><font color=3D"#888888">
-- <br>
Sincerely<br>
<br>
Hector Santos<br>
<a href=3D"http://www.santronics.com" target=3D"_blank">http://www.santroni=
cs.com</a><br>
jabber: <a href=3D"mailto:hector@jabber.isdg.net" target=3D"_blank">hector@=
jabber.isdg.net</a><br>
<br>
</font></span></blockquote></div><br></div></div></div>

--bcaec50162f3123e1104bf133a39--

From mrex@sap.com  Wed May  2 13:07:12 2012
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 56C7721E80F4 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 13:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.121
X-Spam-Level: 
X-Spam-Status: No, score=-10.121 tagged_above=-999 required=5 tests=[AWL=0.128, 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 hbhE5XE7BU03 for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 13:07:11 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 21E4B21E80F0 for <ietf@ietf.org>; Wed,  2 May 2012 13:07:10 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q42K772R021824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 May 2012 22:07:08 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205022007.q42K77mv009497@fs4113.wdf.sap.corp>
Subject: Re: Is the IETF aging?
To: hannes.tschofenig@gmx.net (Hannes Tschofenig)
Date: Wed, 2 May 2012 22:07:07 +0200 (MEST)
In-Reply-To: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net> from "Hannes Tschofenig" at May 2, 12 10:14:16 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: hallam@gmail.com, 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: Wed, 02 May 2012 20:07:12 -0000

Hannes Tschofenig wrote:
> 
> When people suggest new work to the IETF they often see a strange
> reaction. I remember when Mozilla came to the IETF and proposed to
> work on the privacy topic "Do Not Track". I couldn't find support
> for doing the work in the IETF. I don't exactly know why people
> didn't like it but the W3C immediately picked it up and had seen
> lots of new companies (mostly from the advertising industry)
> joining the W3C. 

What exactly to you mean by "came to the IETF and proposed to work
on the privacy topic"?

What is the I-D that you submitted and how many volunteers were there
to do the work?  And who opposed that you do the work within the
IETF?

What usually does not work in the IETF is that you "drop off" an idea
and "pick up" a standard some time later...

-Martin

From avri@psg.com  Wed May  2 14:50:56 2012
Return-Path: <avri@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 386C811E80BD for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 14:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.288
X-Spam-Level: 
X-Spam-Status: No, score=-106.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, 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 7iXhXz9poJzg for <ietf@ietfa.amsl.com>; Wed,  2 May 2012 14:50:55 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 7C84011E809B for <ietf@ietf.org>; Wed,  2 May 2012 14:50:55 -0700 (PDT)
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <avri@psg.com>) id 1SPhRm-000G7x-Mu for ietf@ietf.org; Wed, 02 May 2012 21:50:54 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: Is the IETF aging?
From: Avri Doria <avri@psg.com>
In-Reply-To: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
Date: Wed, 2 May 2012 17:50:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3494DB29-775B-491A-B1E2-C87AD85E1A4F@psg.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 21:50:56 -0000

Hi,

It may not be line a hiring manager, but all those who have budget can =
make it a point to make sure some of the younger engineers get to some =
of the meetings, at least the ones that are relatively local to them.  I =
assume that many of the older participants, have the means to influence =
the travel lists.  For years there have been people working on the =
gender balance perhaps some focus on the age balance may become =
appropriate.

It was good, though to see that the distribution was not too skewed =
toward the older participants.

As for bringing new work in, doesn't that take a plan for introducing =
the subject and showing why it is relevant to the IETF community. =
Although, knowing you, you probably had such a plan.  I think that the =
technical privacy issues, for example, while belonging in the IETF, =
might still feel strange to some of the traditional engineering =
participants.  So in this case, you may need to promote a slight =
cultural change that accepts privacy as a requirement as well as the =
technical challenge of the issue.

avri



On 2 May 2012, at 15:14, Hannes Tschofenig wrote:

> Hi PHB,=20
>=20
> the IETF is not like an enterprise where you can decide (as part of =
the hiring process) what characteristics your employees should have.=20
>=20
> In a volunteer organization the offered topics drive the =
participation. Ask yourself: what you as someone who just finished a =
university education want to hang around in the IETF to standardize yet =
another IPv4/IPv6 transition mechanism or to participate in the MPLS-TP =
discussions?
>=20
> When people suggest new work to the IETF they often see a strange =
reaction. I remember when Mozilla came to the IETF and proposed to work =
on the privacy topic "Do Not Track". I couldn't find support for doing =
the work in the IETF. I don't exactly know why people didn't like it but =
the W3C immediately picked it up and had seen lots of new companies =
(mostly from the advertising industry) joining the W3C.=20
>=20
> Ciao
> Hannes
>=20
>=20


From rumbiles@gmail.com  Thu May  3 00:15:30 2012
Return-Path: <rumbiles@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20C2421F860B for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 00:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfgZmGUUk4rt for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 00:15:28 -0700 (PDT)
Received: from mail-pz0-f52.google.com (mail-pz0-f52.google.com [209.85.210.52]) by ietfa.amsl.com (Postfix) with ESMTP id 5213C21F8603 for <ietf@ietf.org>; Thu,  3 May 2012 00:15:28 -0700 (PDT)
Received: by dadz9 with SMTP id z9so1451079dad.39 for <ietf@ietf.org>; Thu, 03 May 2012 00:15: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=Jt1WrTYhaz1lobU9bmzuOxbGcPi8yhXv9p3woQh5EHA=; b=um70CqeYkiprvFQqGm7n3i3jeQCT5Fd+39t85ljdrOf8YNSIGQ5BCD0Yt+jEygZRRb CLhS6MZWxlAizhZvS9Etjmg6ScOQ9J6J/QFN7Xt0RSfpzcY+gAwpanPgBTqZBc7Xvf4u o1zDvlVE7aliuG0gOekOc/i1ZSdn4TuT0gwgTAkEbpzuKJ258o+l9T5bsaQl6PEJOdqD AQ1i6f5pA/mtia6E5VZxolwep8I+jpi7N2UYHPBHpSA9qguf0TOk9za6xJjn7W2nrFvU Fe4htvlZObsLcuYQQN7tndzhSLFLK63qVX6hYQMx2XaYfwHsxP9TzpYwAn36dgVIPhe3 b4Qw==
MIME-Version: 1.0
Received: by 10.68.224.167 with SMTP id rd7mr4562932pbc.129.1336029327841; Thu, 03 May 2012 00:15:27 -0700 (PDT)
Received: by 10.68.38.164 with HTTP; Thu, 3 May 2012 00:15:27 -0700 (PDT)
In-Reply-To: <CAHBDyN56_xa1-oXTnodZ7QAeZMVWMqBYe8MFAJH65ivd9LsBHg@mail.gmail.com>
References: <CAHBDyN7SNAyW_Y5bPSq+hNOhw2vzRCSX07idtefE50SWYN1_2A@mail.gmail.com> <CAHBDyN4eYD7yAEzUaAbDR4J61JKEW44XVM-QVZAXF7zPBpPFDw@mail.gmail.com> <20120501000305.GL335@mip.aaaaa.org> <F58F1B71-2697-4540-B779-FB74EF396B94@cisco.com> <4FA01B50.1010100@santronics.com> <CAHBDyN56_xa1-oXTnodZ7QAeZMVWMqBYe8MFAJH65ivd9LsBHg@mail.gmail.com>
Date: Thu, 3 May 2012 09:15:27 +0200
Message-ID: <CAOnoajwHpoJm2embuUNsQycUjjg+nv35McaBGXLsG50RDsCfjg@mail.gmail.com>
Subject: Re: 'Geek' image scares women away from tech industry ? The Register
From: Rumbidzayi Gadhula <rumbiles@gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8ff24b3d7edb8804bf1c916b
Cc: Hector Santos <hsantos@santronics.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, 03 May 2012 07:15:30 -0000

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

Culture plays a vital role in determining what one's options are, incuding
career options. When I was in high schoool I was good at maths and science.
After  completing my O'levels, there was a general assumptions that I wold
take up Commercial/business subjects and when I opted for the science
subjects the genral notion was that i wouldn't do well. Now 8 after my
undergrad. I find that the workplace can really be hostile and uncivil to
women in the technical field, that is,  if you are lucky to get an
opportunity. I have found that at times male colleagues look at you as an
intruder and you are expected to behave like a wife in the boardroom, very
subservient and always looking up and aying the man.

Getting ahead is very difficult and the best way to do so is to move jobs.
I have three kids and two of them are girls. If they want to enter the
technical field, I will definitely sit down and have an honest ho holds
barred talk with them to prepare them for the disappointments they may
face. However if it was my decision, I would discourage them even tough I
am in the technical field, enjoy my job and wouldn't want to change careers.

The workplace is supposed to have evolved, to include women, but the
workplace really isn't inclusive.

What I have outllined is my perception of things and could very well be
true for other professions, which I find to be very similar to that of
other women techies. The reason for the perception above are varied and
addressing each of them is essential for women to have an interest in
engineering. There really won't be a need to push unless being geeky can be
pereived as being attractive. What makes geek attractive? That should be
the question we need to answer. How do we make geek attractive?



On 2 May 2012 22:06, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:

> Note that mentor net that I mentioned in another email is also focused on
> increasing minorities in engineering: http://www.mentornet.net/
> They are always looking for new mentors:
> http://www.mentornet.net/mentor.aspx
>
> If your child doesn't seem to have the aptitude for engineering, then
> certainly you shouldn't push them in that direction.  But, I do have to
> wonder if you wouldn't have treated a son differently.  As you likely
> figured out, you really do need to allow your child to find their own
> interests and make their own career decisions,while making sure they  have
> exposure to a broad range of areas.   Unfortunately, a lot of public
> schools don't give kids that exposure these days - they often cut the
> arts/music and there is almost always an extremely high demand for science
> and math teachers.
>
> As far as my kids, my oldest son is a Freshman studying mechanical
> engineering (entirely his decision, but he did get awards for the top math
> and science student, so it does seem a sensible choice). My younger son is
> the artsy one although he does quite well in math and science.  I can't see
> either or them ever getting involved in IETF - they've gone with me to
> meetings (and have more t-shirts than many regular attendees) and they were
> turned off by the overall geekiness (so it's not just women ;)  and told me
> that I actually seem normal relative to everyone else ;)
>
> Mary.
>
>
> On Tue, May 1, 2012 at 12:20 PM, Hector Santos <hsantos@santronics.com>wrote:
>
>> Fred Baker wrote:
>>
>>> On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:
>>>
>>>  This PBS interview with Harvey Mudd president Maria Klawe, on the
>>>> subject of why fewer women go into tech & engineering fields, is
>>>> worth watching:
>>>>
>>>> http://www.pbs.org/newshour/**extra/video/blog/2012/04/**
>>>> college_president_discusses_**wo.html<http://www.pbs.org/newshour/extra/video/blog/2012/04/college_president_discusses_wo.html>
>>>>
>>>
>>> This is a discussion that comes up periodically.
>>>
>>> If you want my opinion (nobody asked, but I will presume that someone is
>>> wondering), the corollary is "why aren't more students interested in
>>> math/science?". I'll observe that there are relatively few teachers that I
>>> can say "inspired" me to think their their directions; far-too-many years
>>> later, I could probably name them. Two were English teachers, one was a
>>> Math teacher, tenth grade geometry, one taught 7th grade Geography, and one
>>> taught senior Calculus. And, oh, I liked some of my college profs, but in
>>> this context my views were probably formed before I got there.
>>>
>>> What if teachers were measured on a survey at the end of a semester or a
>>> year that asked "does teacher <> make <> interesting to you?".
>>>
>>
>> +1.
>>
>> What about other minorities?  Is the recruitment levels the same? Public
>> funded, social programs to fill certain needs? Both at the school and
>> business levels?
>>
>> A Puerto Rican from the Sough Bronx, I wanted to go to the vocational
>> school up the block - Alfred E. Smith.  AP/College bounds programs were
>> presented to me. I didn't know enough to see it or even dream about it.
>>
>> A HS counselor helped with showing the availability of AA/Minority
>> college grant programs which included girls among the selected group she
>> called to her office.  Otherwise, while a good grades student, I wasn't
>> thinking about college. I selected Drexel only because a recruiter came to
>> the HS showing a photo with white, black, spanish and women all wearing
>> cool Drexel Engineering helmets!  I selected Chemical Engineering because I
>> saw they made the most salary as a co-op student among all degrees! I had
>> no idea how brutal the Chemical Engineering curriculum would be.
>>
>> But I had even failed a HS class called "Computers" that introduced this
>> thing called FORTRAN using some punch card thingy.  So I was presented with
>> even more Pre-college Grant programs to learn about applied engineering
>> with computers, and it still took an act of GOD with a lightning strike
>> knocking out a PDP-11, forcing us to do the engineering problem translation
>> to BASIC on paper by hand, and only then did I finally get the AH-AH of
>> GIGO!
>>
>> And even with all that, it still took AA programs it finally get a job
>> because it was mist of a recession that did not help many get a job and
>> this dude called Ted Turner speaking in our graduation getting loud boos
>> recommending that we go into the MILITARY!
>>
>> IMO, background is very important. Unless there are active social
>> programs and recruitment efforts A.K.A "Marketing," I don't think there
>> will a natural tendency of the so called "minority segment" of (any)
>> society that are not often encouraged or have the family background
>> already, to explore or even think about the science related industry as a
>> career.
>>
>> Take myself. I was deep into computers and the blossoming world of
>> Telecomputing, micro-at-home era. The wife (Technical Sales Engineer) and I
>> specifically did not want our two new girls to get into the same High Tech
>> business as Daddy and Mommy were in.  No Way! Doctors, Lawyers perhaps! No
>> way ENGINEER!  It was too tough and I also saw how tough it was for my
>> women peers at Mobil and Westinghouse with an extreme competition going on,
>> and quite frankly faced tough family decisions at some point. In fact,
>> during some pending layoffs at big W, I was told I was going to stay and
>> found out a pregnant software programmer in the group was going to get laid
>> off. With my existing "Fire in my Belly" to quit and start my business
>> already, I took the opportunity and asked the boss to keep her and to lay
>> me off instead so I can get the benefits, Cobra, etc.  If I had quit, I
>> lose all that.
>>
>> I had already saw that the salaries were different too. The idea of
>> working for a corporation lost its appear when I saw a lost of loyalty with
>> people of 20, 25-30 years who had dedicated their engineering lives were
>> now forced to get early retirement, laid off or fired. With no more Federal
>> funding for Advanced Energy programs and the even Defense in AI, Robots and
>> Star Wars, etc, I did not want my two girls to go into these life
>> commitment hard sciences. I didn't push the computers at home on them at
>> all. I didn't teach them about the idea of "programming" etc. Perhaps only
>> to play games, and perhaps to use the early on-disc encyclopedias. They
>> were using Apple stuff at school anyway and that was good enough for us.
>>
>> Today, both living in NYC, one works for Sony Music productions
>> department and the oldest is a successful independent artist making more
>> money that I can ever imagine possible. She was even a contestant on
>> Bravo's first season "Next Great Artist."  The only thing that first
>> worried me was whether she would need to cut off an ear before getting
>> recognized in the art world! :)
>>
>> We have to consider that the engineering life is not always ideal for
>> anyone. Its sounds nice, it does give one more respect among their family
>> peers, helps secure jobs (when available), better pay, etc, but its takes a
>> very high commitment and it is very competitive to keep up even if one
>> wishes to stay in one position and not interested to be move ahead.  That
>> presents employer decisions with competitive compensation managers need to
>> make. Younger, lower salary recruitement can do the same job, etc, so
>> generally by 30, aging engineers need to make life career movements and
>> changes.
>>
>>
>> For women, well, life is life, it is what it is, they have it harder to
>> make family oriented decisions and they are in a position to be, well, let
>> my artist daughter, Jaclyn Santos, show you what woman are facing with her
>> "Super Mom, Super Executive, Super Ho!"
>> painting:
>>
>>       http://www.jaclynsantos.com/**images/large/g.jpg<http://www.jaclynsantos.com/images/large/g.jpg>
>>
>> Finally, for the IETF - well, gotta know first what it wants.  What does
>> recruiting more woman (or other minorities for that matter) mean to it?  I
>> personally think its just a reflection of whats going on in the market.
>>  Its not like the IETF is on the radar for anyone to pursue unless they are
>> presented with it somewhere, somehow, at work most likely with a position
>> where IETF work is part of the job production.   I say that is a very very
>> narrow niche job or goal.
>>
>> PS: These are my views and says nothing about life other than my own.
>>
>> --
>> Sincerely
>>
>> Hector Santos
>> http://www.santronics.com
>> jabber: hector@jabber.isdg.net
>>
>>
>


-- 
*Senior Systems Administrator
UZCHS- NECTAR
Ward C10, Parirenyatwa Hospital
Mazoe St, Avondale
Harare
Tel: +263772 148 889/890 x 320
Cell:0772588210*

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

Culture plays a vital role in determining what one&#39;s options are, incud=
ing career options. When I was in high schoool I was good at maths and scie=
nce. After=A0 completing my O&#39;levels, there was a general assumptions t=
hat I wold take up Commercial/business subjects and when I opted for the sc=
ience subjects the genral notion was that i wouldn&#39;t do well. Now 8 aft=
er my undergrad. I find that the workplace can really be hostile and uncivi=
l to women in the technical field, that is,=A0 if you are lucky to get an o=
pportunity. I have found that at times male colleagues look at you as an in=
truder and you are expected to behave like a wife in the boardroom, very su=
bservient and always looking up and aying the man.<br>
<br>Getting ahead is very difficult and the best way to do so is to move jo=
bs. I have three kids and two of them are girls. If they want to enter the =
technical field, I will definitely sit down and have an honest ho holds bar=
red talk with them to prepare them for the disappointments they may face. H=
owever if it was my decision, I would discourage them even tough I am in th=
e technical field, enjoy my job and wouldn&#39;t want to change careers.<br=
>
<br>The workplace is supposed to have evolved, to include women, but the wo=
rkplace really isn&#39;t inclusive. <br><br>What I have outllined is my per=
ception of things and could very well be true for other professions, which =
I find to be very similar to that of other women techies. The reason for th=
e perception above are varied and addressing each of them is essential for =
women to have an interest in engineering. There really won&#39;t be a need =
to push unless being geeky can be pereived as being attractive. What makes =
geek attractive? That should be the question we need to answer. How do we m=
ake geek attractive?<br>
<br><br><br><div class=3D"gmail_quote">On 2 May 2012 22:06, Mary Barnes <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:mary.ietf.barnes@gmail.com" target=3D"=
_blank">mary.ietf.barnes@gmail.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
Note that mentor net that I mentioned in another email is also focused on i=
ncreasing minorities in engineering:=A0<a href=3D"http://www.mentornet.net/=
" target=3D"_blank">http://www.mentornet.net/</a><div>They are always looki=
ng for new mentors:</div>

<div><div><a href=3D"http://www.mentornet.net/mentor.aspx" target=3D"_blank=
">http://www.mentornet.net/mentor.aspx</a></div><div><br><div>If your child=
 doesn&#39;t seem to have the aptitude for engineering, then certainly you =
shouldn&#39;t push them in that direction. =A0But, I do have to wonder if y=
ou wouldn&#39;t have treated a son differently. =A0As you likely figured ou=
t, you really do need to allow your child to find their own interests and m=
ake their own career decisions,while making sure they =A0have exposure to a=
 broad range of areas. =A0 Unfortunately, a lot of public schools don&#39;t=
 give kids that exposure these days - they often cut the arts/music and the=
re is almost always an extremely high demand for science and math teachers.=
=A0</div>

<div><br></div><div>As far as my kids, my oldest son is a Freshman studying=
 mechanical engineering (entirely his decision, but he did get awards for t=
he top math and science student, so it does seem a sensible choice). My you=
nger son is the artsy one although he does quite well in math and science. =
=A0I can&#39;t see either or them ever getting involved in IETF - they&#39;=
ve gone with me to meetings (and have more t-shirts than many regular atten=
dees) and they were turned off by the overall geekiness (so it&#39;s not ju=
st women ;) =A0and told me that I actually seem normal relative to everyone=
 else ;) =A0=A0</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div></font></span><div><span class=3D"HOEnZb"><font color=3D"#88=
8888">Mary.=A0</font></span><div><div class=3D"h5"><br><br><div class=3D"gm=
ail_quote">On Tue, May 1, 2012 at 12:20 PM, Hector Santos <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:hsantos@santronics.com" target=3D"_blank">hsantos@sa=
ntronics.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><div>Fred Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Apr 30, 2012, at 5:03 PM, Ofer Inbar wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This PBS interview with Harvey Mudd president Maria Klawe, on the<br>
subject of why fewer women go into tech &amp; engineering fields, is<br>
worth watching:<br>
<br>
<a href=3D"http://www.pbs.org/newshour/extra/video/blog/2012/04/college_pre=
sident_discusses_wo.html" target=3D"_blank">http://www.pbs.org/newshour/<u>=
</u>extra/video/blog/2012/04/<u></u>college_president_discusses_<u></u>wo.h=
tml</a><br>


</blockquote>
<br>
This is a discussion that comes up periodically.<br>
<br>
If you want my opinion (nobody asked, but I will presume that someone is wo=
ndering), the corollary is &quot;why aren&#39;t more students interested in=
 math/science?&quot;. I&#39;ll observe that there are relatively few teache=
rs that I can say &quot;inspired&quot; me to think their their directions; =
far-too-many years later, I could probably name them. Two were English teac=
hers, one was a Math teacher, tenth grade geometry, one taught 7th grade Ge=
ography, and one taught senior Calculus. And, oh, I liked some of my colleg=
e profs, but in this context my views were probably formed before I got the=
re.<br>


<br>
What if teachers were measured on a survey at the end of a semester or a ye=
ar that asked &quot;does teacher &lt;&gt; make &lt;&gt; interesting to you?=
&quot;.<br>
</blockquote>
<br></div></div><div>
+1.<br>
<br>
What about other minorities? =A0Is the recruitment levels the same? Public =
funded, social programs to fill certain needs? Both at the school and busin=
ess levels?<br>
<br>
A Puerto Rican from the Sough Bronx, I wanted to go to the vocational schoo=
l up the block - Alfred E. Smith. =A0AP/College bounds programs were presen=
ted to me. I didn&#39;t know enough to see it or even dream about it.<br>


<br>
A HS counselor helped with showing the availability of AA/Minority college =
grant programs which included girls among the selected group she called to =
her office. =A0Otherwise, while a good grades student, I wasn&#39;t thinkin=
g about college. I selected Drexel only because a recruiter came to the HS =
showing a photo with white, black, spanish and women all wearing cool Drexe=
l Engineering helmets! =A0I selected Chemical Engineering because I saw the=
y made the most salary as a co-op student among all degrees! I had no idea =
how brutal the Chemical Engineering curriculum would be.<br>


<br>
But I had even failed a HS class called &quot;Computers&quot; that introduc=
ed this thing called FORTRAN using some punch card thingy. =A0So I was pres=
ented with even more Pre-college Grant programs to learn about applied engi=
neering with computers, and it still took an act of GOD with a lightning st=
rike knocking out a PDP-11, forcing us to do the engineering problem transl=
ation to BASIC on paper by hand, and only then did I finally get the AH-AH =
of GIGO!<br>


<br>
And even with all that, it still took AA programs it finally get a job beca=
use it was mist of a recession that did not help many get a job and this du=
de called Ted Turner speaking in our graduation getting loud boos recommend=
ing that we go into the MILITARY!<br>


<br>
IMO, background is very important. Unless there are active social programs =
and recruitment efforts A.K.A &quot;Marketing,&quot; I don&#39;t think ther=
e will a natural tendency of the so called &quot;minority segment&quot; of =
(any) society that are not often encouraged or have the family background a=
lready, to explore or even think about the science related industry as a ca=
reer.<br>


<br>
Take myself. I was deep into computers and the blossoming world of Telecomp=
uting, micro-at-home era. The wife (Technical Sales Engineer) and I specifi=
cally did not want our two new girls to get into the same High Tech busines=
s as Daddy and Mommy were in. =A0No Way! Doctors, Lawyers perhaps! No way E=
NGINEER! =A0It was too tough and I also saw how tough it was for my women p=
eers at Mobil and Westinghouse with an extreme competition going on, and qu=
ite frankly faced tough family decisions at some point. In fact, during som=
e pending layoffs at big W, I was told I was going to stay and found out a =
pregnant software programmer in the group was going to get laid off. With m=
y existing &quot;Fire in my Belly&quot; to quit and start my business alrea=
dy, I took the opportunity and asked the boss to keep her and to lay me off=
 instead so I can get the benefits, Cobra, etc. =A0If I had quit, I lose al=
l that.<br>


<br>
I had already saw that the salaries were different too. The idea of working=
 for a corporation lost its appear when I saw a lost of loyalty with people=
 of 20, 25-30 years who had dedicated their engineering lives were now forc=
ed to get early retirement, laid off or fired. With no more Federal funding=
 for Advanced Energy programs and the even Defense in AI, Robots and Star W=
ars, etc, I did not want my two girls to go into these life commitment hard=
 sciences. I didn&#39;t push the computers at home on them at all. I didn&#=
39;t teach them about the idea of &quot;programming&quot; etc. Perhaps only=
 to play games, and perhaps to use the early on-disc encyclopedias. They we=
re using Apple stuff at school anyway and that was good enough for us.<br>


<br>
Today, both living in NYC, one works for Sony Music productions department =
and the oldest is a successful independent artist making more money that I =
can ever imagine possible. She was even a contestant on Bravo&#39;s first s=
eason &quot;Next Great Artist.&quot; =A0The only thing that first worried m=
e was whether she would need to cut off an ear before getting recognized in=
 the art world! :)<br>


<br></div>
We have to consider that the engineering life is not always ideal for anyon=
e. Its sounds nice, it does give one more respect among their family peers,=
 helps secure jobs (when available), better pay, etc, but its takes a very =
high commitment and it is very competitive to keep up even if one wishes to=
 stay in one position and not interested to be move ahead. =A0That presents=
 employer decisions with competitive compensation managers need to make. Yo=
unger, lower salary recruitement can do the same job, etc, so generally by =
30, aging engineers need to make life career movements and changes.<div>

<div><br>
<br>
For women, well, life is life, it is what it is, they have it harder to mak=
e family oriented decisions and they are in a position to be, well, let my =
artist daughter, Jaclyn Santos, show you what woman are facing with her &qu=
ot;Super Mom, Super Executive, Super Ho!&quot;<br>


painting:<br>
<br>
 =A0 =A0 =A0 <a href=3D"http://www.jaclynsantos.com/images/large/g.jpg" tar=
get=3D"_blank">http://www.jaclynsantos.com/<u></u>images/large/g.jpg</a><br=
>
<br>
Finally, for the IETF - well, gotta know first what it wants. =A0What does =
recruiting more woman (or other minorities for that matter) mean to it? =A0=
I personally think its just a reflection of whats going on in the market. =
=A0Its not like the IETF is on the radar for anyone to pursue unless they a=
re presented with it somewhere, somehow, at work most likely with a positio=
n where IETF work is part of the job production. =A0 I say that is a very v=
ery narrow niche job or goal.<br>


<br>
PS: These are my views and says nothing about life other than my own.<br>
<br></div></div><span><font color=3D"#888888">
-- <br>
Sincerely<br>
<br>
Hector Santos<br>
<a href=3D"http://www.santronics.com" target=3D"_blank">http://www.santroni=
cs.com</a><br>
jabber: <a href=3D"mailto:hector@jabber.isdg.net" target=3D"_blank">hector@=
jabber.isdg.net</a><br>
<br>
</font></span></blockquote></div><br></div></div></div></div></div>
</blockquote></div><br><br clear=3D"all"><br>-- <br><i>Senior Systems Admin=
istrator<br>UZCHS- NECTAR<br>Ward C10, Parirenyatwa Hospital<br>Mazoe St, A=
vondale<br>Harare<br>Tel: +263<span style=3D"font-family:Arial" lang=3D"en-=
US">772 148 889/890 x 320<br>
Cell:0772588210</span></i><span lang=3D"en-ZW"></span>


<br>

--e89a8ff24b3d7edb8804bf1c916b--

From sm@resistor.net  Thu May  3 03:48:55 2012
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 0499D21F8495; Thu,  3 May 2012 03:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpM0cSdWVhAm; Thu,  3 May 2012 03:48: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 1698B21F8464; Thu,  3 May 2012 03:48:51 -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 q43Amjsw017828; Thu, 3 May 2012 03:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336042130; i=@resistor.net; bh=6n6W8vQ4ro5GTsV3FkuqH7X6RTRBD3mw9kprFoLVv4w=; h=Date:To:From:Subject:Cc; b=lkLyatsxY8/8ACWxADizM5YOuat2XZbBZy8Cffd1DrQ2/ipG87VYOzpx36N2iwkeE BpCCU+kE8q8+WDdF1AMMi31gdy9fORLG97W/js65SLsk5AzZk9SHn/eCHvp5SrEexE vYKg9Y8CKgLy5P3/qr2gR/KSEpAWAcak6nG0obA4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336042130; i=@resistor.net; bh=6n6W8vQ4ro5GTsV3FkuqH7X6RTRBD3mw9kprFoLVv4w=; h=Date:To:From:Subject:Cc; b=nLDpbP9cVTiuJQKRh6mnQb7uQm3pMsftpDqZDsahhcFOIKRwNVH3gSx1LRLVakinM gcFUYrHKqKfyHZkBCySChohthJMnbOvoKtvy8/n4OU9v1ia6M/zgYd8Bsy46wDoISQ w7dfxJnLGDIu+Ge/kFxV4yn2jibcP8HgGoIx4E7w=
Message-Id: <6.2.5.6.2.20120503032341.0b11fe78@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 03 May 2012 03:48:35 -0700
To: trustees@ietf.org
From: SM <sm@resistor.net>
Subject: IETF Trust Minutes since August 2011
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, 03 May 2012 10:48:55 -0000

Dear IETF Trust,

The IETF Trust reported during the IETF83 meeting that the "Minutes 
are complete except for the meeting held this morning".  I don't see 
any minutes published since August 2011.    Could these minutes be 
published in a timely manner?

It was also mentioned the subpoenas would be published as they come 
in.  Where can I find them?

Does the amount of US$600 cover the storage cost of the "blue 
sheets"?  Can the IETF Trust review the second paragraph of the 
message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73049.html and 
provide feedback to the IETF Community?

Regards,
-sm


From dworley@avaya.com  Thu May  3 11:18:21 2012
Return-Path: <dworley@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 7728721F8625 for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 11:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.811
X-Spam-Level: 
X-Spam-Status: No, score=-102.811 tagged_above=-999 required=5 tests=[AWL=-0.212, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTz+KFdUgRHv for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 11:18:20 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8D6C721F861D for <ietf@ietf.org>; Thu,  3 May 2012 11:18:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAJ/Lok/GmAcF/2dsb2JhbABEsnyBB4IJAQEBAQIBEihECwIBCA0IIRAyJQEBBAESCA0Nh2YFnVWdJpAlYwScFooqgwQ
X-IronPort-AV: E=Sophos;i="4.75,526,1330923600";  d="scan'208";a="7446171"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 03 May 2012 14:18:03 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 May 2012 14:15:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 3 May 2012 14:18:04 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Thomas Narten <narten@us.ibm.com>, IETF-Discussion list <ietf@ietf.org>
Date: Thu, 3 May 2012 14:16:40 -0400
Subject: RE: 'Geek' image scares women away from tech industry ? The Register
Thread-Topic: 'Geek' image scares women away from tech industry ? The Register
Thread-Index: Ac0nzRwhkYlm1eZtQB2v179SISFj2QBi8d28
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0AA5@DC-US1MBEX4.global.avaya.com>
References: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.com>
In-Reply-To: <201205011902.q41J2QAY008943@cichlid.raleigh.ibm.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: Thu, 03 May 2012 18:18:21 -0000

> From: Thomas Narten [narten@us.ibm.com]
>=20
> If this conversation was about IETF culture, and how it's hard for
> non-Americans to participate "IETF style", I bet folk would much more
> quickly recognize some of the real issues.

Has there been any organized attempt to reduce the difficulty for
non-Americans to participate "IETF style"?

Dale

From msk@cloudmark.com  Thu May  3 14:51:39 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC7621F86DA for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 14:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrkgCZtTn7Gx for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 14:51:36 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id C453721F86D1 for <ietf@ietf.org>; Thu,  3 May 2012 14:51:34 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id 5Zrp1j0010ZaKgw01ZrpPw; Thu, 03 May 2012 14:51:49 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=Xth4yC59 c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=LvckAehuu68A:10 a=1Iosk0GGxfIA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=XANSSh8q98T2yvBriOsA:9 a=-b6x93Z0736LMppDEowA:7 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Thu, 3 May 2012 14:51:23 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
Thread-Topic: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
Thread-Index: AQHNKXK9tNZFYCfQGk6/JYv2d4ePlZa4mmWA
Date: Thu, 3 May 2012 21:51:22 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com>
References: <20120503212126.3638.47131.idtracker@ietfa.amsl.com>
In-Reply-To: <20120503212126.3638.47131.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336081909; bh=qU8pr7UPBASzX9iI4jd7hOEAcjmkMiU+NcpcpJNIpBA=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=TO/S1+3Gxk+cUlz2K4gO3NA+yqvbqZ6gcvb5qPAY5cOpegM917N0aSIRvjl8c2n/K PzXNJbz+st7At2izJ4lXT4PZxk4KA2SUWwzCTXHKiuGsWZcIT0ObYesQ0ltUUzUA9Y bWnnVFpabdjfug1pie/PfDUzB2lNZrDP8fYmm9ZU=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 21:51:39 -0000

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg] On Behalf Of The IESG
> Sent: Thursday, May 03, 2012 2:21 PM
> To: IETF-Announce
> Subject: Last Call: <draft-levine-application-gzip-02.txt> (The applicati=
on/zlib and application/gzip media types) to Informational RFC
>=20
> The IESG has received a request from an individual submitter to
> consider the following document:
> - 'The application/zlib and application/gzip media types'
>   <draft-levine-application-gzip-02.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 2012-05-31. 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.

Only two things:

1) Shouldn't this be Standards Track?

2) Should it mention the "xdash" draft, since it talks about "application/x=
-*" types?

-MSK

From ned+ietf@mauve.mrochek.com  Thu May  3 15:07:20 2012
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 9D10121F8691 for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 15:07: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 C+ScVFru3YgX for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 15:07:20 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C126421F8620 for <ietf@ietf.org>; Thu,  3 May 2012 15:07:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF1TOUHF5S00128Y@mauve.mrochek.com> for ietf@ietf.org; Thu, 3 May 2012 15:07:00 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OENEYWYFI80006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 3 May 2012 15:06:58 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OF1TOTG2700006TF@mauve.mrochek.com>
Date: Thu, 03 May 2012 14:54:21 -0700 (PDT)
Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
In-reply-to: "Your message dated Thu, 03 May 2012 21:51:22 +0000" <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120503212126.3638.47131.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.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: Thu, 03 May 2012 22:07:20 -0000

> > -----Original Message-----
> > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
> > Sent: Thursday, May 03, 2012 2:21 PM
> > To: IETF-Announce
> > Subject: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to Informational RFC
> >
> > The IESG has received a request from an individual submitter to
> > consider the following document:
> > - 'The application/zlib and application/gzip media types'
> >   <draft-levine-application-gzip-02.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 2012-05-31. 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.

> Only two things:

> 1) Shouldn't this be Standards Track?

Based on past practices, the answer to that seems to be "no". See, for example,
RFC 6208, RFC 6207, RFC 6129, RFC 5967, and so on.

The rule seems to that if the specification defines the format as well as
registering one or more media types, then it needs to be on the standards
track. But if the specification simply registers a bunch of types, then
it's informational.

And I think this makes sense. After all, how would one assess interoperability
or pretty much anything else of a registration? 

I suppose you could argue that in cases where the registration points at an
external specification (which is not the case here) that it could be a sort of
"hook" to allow such assessment, but I think we have enough problems performing
evaluations of our own work that we don't need to added fun of evaluating
externally defined formats.

> 2) Should it mention the "xdash" draft, since it talks about "application/x-*" types?

That specification is really focused on not using x- in newly defined
registries, not on how it's used in existing registries. And since x-gzip and
friends are only mentioned to say they shouldn't be used, I'd say that while
such a reference would not bother me, I don't think it's especially helpful.

				Ned

From msk@cloudmark.com  Thu May  3 15:15:02 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 629F021F86EA for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 15:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-ZalbYeB4sZ for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 15:15:00 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id A9E3C21F86D8 for <ietf@ietf.org>; Thu,  3 May 2012 15:15:00 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id 5aEG1j0010as01C01aEG9j; Thu, 03 May 2012 15:14:16 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=bcDpoZzB c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=LvckAehuu68A:10 a=1Iosk0GGxfIA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=9aueKP-jAAAA:8 a=48vgC7mUAAAA:8 a=TCQNA5ogF0hvqhS2S24A:9 a=CjuIK1q_8ugA:10 a=jwvSBeqQ3e8A:10 a=lZB815dzVvQA:10 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Thu, 3 May 2012 15:14:16 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
Thread-Topic: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
Thread-Index: AQHNKXK9tNZFYCfQGk6/JYv2d4ePlZa4mmWAgAAFIimAAAGZsA==
Date: Thu, 3 May 2012 22:14:15 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392810BFA5@exch-mbx901.corp.cloudmark.com>
References: <20120503212126.3638.47131.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com> <01OF1TOTG2700006TF@mauve.mrochek.com>
In-Reply-To: <01OF1TOTG2700006TF@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336083256; bh=CZPlGFbSMRwHgzVJt71cnJNqLNA73eo/GFT7Duqvz6M=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=dbPFErtwicbMeDD1eytxZ1cV5Am7hXYdtP0duAccChzFaCWkmw0reP32IHByl/l/L 8TXoOdIhuEN+4YYK6hXiwUIKgBm2QiIDBpRatdxaepTEVAu3lwc1rOYCr91LAG8mn8 uDE38WsZBe8RM6++Vhgx1/q/bIjhJuzokGydfxzg=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 22:15:02 -0000

> -----Original Message-----
> From: Ned Freed [mailto:ned.freed@mrochek.com]
> Sent: Thursday, May 03, 2012 2:54 PM
> To: Murray S. Kucherawy
> Cc: ietf@ietf.org
> Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The appli=
cation/zlib and application/gzip media types) to Informational RFC
>=20
> > 1) Shouldn't this be Standards Track?
>=20
> Based on past practices, the answer to that seems to be "no". See, for
> example, RFC 6208, RFC 6207, RFC 6129, RFC 5967, and so on.
>=20
> [...]
>=20
> > 2) Should it mention the "xdash" draft, since it talks about
> "application/x-*" types?
>=20
> That specification is really focused on not using x- in newly defined
> registries, not on how it's used in existing registries. And since x-
> gzip and friends are only mentioned to say they shouldn't be used, I'd
> say that while such a reference would not bother me, I don't think it's
> especially helpful.

Good enough, just thought I'd ask.

I support publication as-is.

-MSK

From ned+ietf@mauve.mrochek.com  Thu May  3 17:11:36 2012
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 DA4A311E8081 for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 17:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YI4tK-AAKikZ for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 17:11:36 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73B21F86B3 for <ietf@ietf.org>; Thu,  3 May 2012 17:11:36 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF1Y28NHBK000LGW@mauve.mrochek.com> for ietf@ietf.org; Thu, 3 May 2012 17:11:33 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OENEYWYFI80006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 3 May 2012 17:11:31 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OF1Y27CWNY0006TF@mauve.mrochek.com>
Date: Thu, 03 May 2012 17:11:21 -0700 (PDT)
Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to	Informational RFC
In-reply-to: "Your message dated Thu, 03 May 2012 22:14:15 +0000" <9452079D1A51524AA5749AD23E00392810BFA5@exch-mbx901.corp.cloudmark.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120503212126.3638.47131.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com> <01OF1TOTG2700006TF@mauve.mrochek.com> <9452079D1A51524AA5749AD23E00392810BFA5@exch-mbx901.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.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 May 2012 00:11:37 -0000

> > -----Original Message-----
> > From: Ned Freed [mailto:ned.freed@mrochek.com]
> > Sent: Thursday, May 03, 2012 2:54 PM
> > To: Murray S. Kucherawy
> > Cc: ietf@ietf.org
> > Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The application/zlib and application/gzip media types) to Informational RFC
> >
> > > 1) Shouldn't this be Standards Track?
> >
> > Based on past practices, the answer to that seems to be "no". See, for
> > example, RFC 6208, RFC 6207, RFC 6129, RFC 5967, and so on.
> >
> > [...]
> >
> > > 2) Should it mention the "xdash" draft, since it talks about
> > "application/x-*" types?
> >
> > That specification is really focused on not using x- in newly defined
> > registries, not on how it's used in existing registries. And since x-
> > gzip and friends are only mentioned to say they shouldn't be used, I'd
> > say that while such a reference would not bother me, I don't think it's
> > especially helpful.

> Good enough, just thought I'd ask.

> I support publication as-is.

As do I.

				Ned

From narten@us.ibm.com  Thu May  3 21:53:45 2012
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 DB1A721F86FF for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 21:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.175
X-Spam-Level: 
X-Spam-Status: No, score=-109.175 tagged_above=-999 required=5 tests=[AWL=-1.176, BAYES_50=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 FcEjAOw8R8F3 for <ietf@ietfa.amsl.com>; Thu,  3 May 2012 21:53:44 -0700 (PDT)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by ietfa.amsl.com (Postfix) with ESMTP id 647AD21F86F7 for <ietf@ietf.org>; Thu,  3 May 2012 21:53:42 -0700 (PDT)
Received: from /spool/local by e35.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 3 May 2012 22:53:40 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 3 May 2012 22:53:05 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 8B20419D8048 for <ietf@ietf.org>; Thu,  3 May 2012 22:52:53 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q444r4GM183800 for <ietf@ietf.org>; Thu, 3 May 2012 22:53:04 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q444r3oo003350 for <ietf@ietf.org>; Thu, 3 May 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q444r3XK003300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 3 May 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q444r2kW018847 for <ietf@ietf.org>; Fri, 4 May 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q444r2AQ018809 for ietf@ietf.org; Fri, 4 May 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201205040453.q444r2AQ018809@rotala.raleigh.ibm.com>
Date: Fri, 04 May 2012 00:53:01 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12050404-6148-0000-0000-0000058CE156
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 04:53:46 -0000

Total of 125 messages in the last 7 days.
 
script run at: Fri May  4 00:53:01 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.40% |    8 |  9.28% |    93921 | mary.ietf.barnes@gmail.com
  6.40% |    8 |  5.17% |    52339 | dworley@avaya.com
  5.60% |    7 |  4.37% |    44283 | melinda.shore@gmail.com
  4.80% |    6 |  5.10% |    51614 | ynir@checkpoint.com
  4.80% |    6 |  4.02% |    40699 | sm@resistor.net
  3.20% |    4 |  4.06% |    41134 | jgunn6@csc.com
  4.00% |    5 |  3.05% |    30885 | john-ietf@jck.com
  3.20% |    4 |  3.54% |    35851 | msk@cloudmark.com
  3.20% |    4 |  3.34% |    33782 | mmorrow@cisco.com
  0.80% |    1 |  4.59% |    46476 | nurit.sprecher@nsn.com
  2.40% |    3 |  2.46% |    24903 | sant9442@gmail.com
  2.40% |    3 |  2.33% |    23568 | narten@us.ibm.com
  2.40% |    3 |  2.19% |    22127 | hallam@gmail.com
  2.40% |    3 |  2.11% |    21375 | framefritti@gmail.com
  2.40% |    3 |  1.88% |    19051 | ned+ietf@mauve.mrochek.com
  2.40% |    3 |  1.84% |    18652 | rbarnes@bbn.com
  0.80% |    1 |  2.89% |    29234 | rumbiles@gmail.com
  1.60% |    2 |  1.94% |    19672 | stewe@stewe.org
  1.60% |    2 |  1.34% |    13565 | ron@debian.org
  1.60% |    2 |  1.32% |    13334 | fred@cisco.com
  1.60% |    2 |  1.22% |    12351 | bortzmeyer@nic.fr
  1.60% |    2 |  1.21% |    12246 | scott.brim@gmail.com
  1.60% |    2 |  1.07% |    10838 | dhc@dcrocker.net
  0.80% |    1 |  1.53% |    15493 | stephen.farrell@cs.tcd.ie
  0.80% |    1 |  1.44% |    14590 | linda.dunbar@huawei.com
  0.80% |    1 |  1.33% |    13427 | alan.kavanagh@ericsson.com
  0.80% |    1 |  1.28% |    12969 | cb.list6@gmail.com
  0.80% |    1 |  1.20% |    12143 | lars@netapp.com
  0.80% |    1 |  1.19% |    12029 | hsantos@santronics.com
  0.80% |    1 |  0.96% |     9742 | marc.blanchet@viagenie.ca
  0.80% |    1 |  0.83% |     8416 | dave@cridland.net
  0.80% |    1 |  0.74% |     7532 | stbryant@cisco.com
  0.80% |    1 |  0.74% |     7489 | glenzorn@gmail.com
  0.80% |    1 |  0.72% |     7257 | mcr@sandelman.ca
  0.80% |    1 |  0.71% |     7236 | jmpolk@cisco.com
  0.80% |    1 |  0.71% |     7201 | warren@kumari.net
  0.80% |    1 |  0.71% |     7158 | hgs@cs.columbia.edu
  0.80% |    1 |  0.69% |     6949 | akatlas@gmail.com
  0.80% |    1 |  0.66% |     6709 | hannes.tschofenig@gmx.net
  0.80% |    1 |  0.66% |     6680 | avri@psg.com
  0.80% |    1 |  0.64% |     6477 | daedulus@btconnect.com
  0.80% |    1 |  0.63% |     6401 | jdrake@juniper.net
  0.80% |    1 |  0.63% |     6397 | uyeshiro@ifa.hawaii.edu
  0.80% |    1 |  0.62% |     6288 | mrw@lilacglade.org
  0.80% |    1 |  0.62% |     6278 | randy_presuhn@mindspring.com
  0.80% |    1 |  0.61% |     6177 | cabo@tzi.org
  0.80% |    1 |  0.61% |     6165 | richard@shockey.us
  0.80% |    1 |  0.61% |     6128 | kpfleming@digium.com
  0.80% |    1 |  0.58% |     5859 | huubatwork@gmail.com
  0.80% |    1 |  0.58% |     5858 | ben@nostrum.com
  0.80% |    1 |  0.56% |     5683 | joelja@bogus.com
  0.80% |    1 |  0.56% |     5671 | paul.hoffman@vpnc.org
  0.80% |    1 |  0.56% |     5668 | ted.ietf@gmail.com
  0.80% |    1 |  0.56% |     5622 | brian.e.carpenter@gmail.com
  0.80% |    1 |  0.55% |     5614 | yaakov_s@rad.com
  0.80% |    1 |  0.55% |     5611 | derhoermi@gmx.net
  0.80% |    1 |  0.54% |     5487 | harald@alvestrand.no
  0.80% |    1 |  0.54% |     5454 | hartmans-ietf@mit.edu
  0.80% |    1 |  0.53% |     5343 | mrex@sap.com
  0.80% |    1 |  0.53% |     5316 | acooper@cdt.org
  0.80% |    1 |  0.52% |     5277 | john@jck.com
  0.80% |    1 |  0.50% |     5025 | randy@psg.com
  0.80% |    1 |  0.50% |     5017 | robert@raszuk.net
  0.80% |    1 |  0.47% |     4802 | cos@aaaaa.org
--------+------+--------+----------+------------------------
100.00% |  125 |100.00% |  1012538 | Total


From eburger-l@standardstrack.com  Fri May  4 02:20:51 2012
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9C021F8745 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 02:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, 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 oj3KBah2jaQ7 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 02:20:50 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id CB1B421F8744 for <ietf@ietf.org>; Fri,  4 May 2012 02:20:50 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:58842 helo=[192.168.15.135]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SQEgz-0003Eb-17; Fri, 04 May 2012 02:20:49 -0700
Subject: Re: Gender diversity in engineering
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com>
Date: Fri, 4 May 2012 05:20:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com>
To: James M. Polk <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
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, 04 May 2012 09:20:51 -0000

NSF has a ton of information on this for the U.S. population.  I'm too =
lazy right now to dig it up, but it is there.

On May 1, 2012, at 4:40 PM, James M. Polk wrote:

> There have been some good numbers floated on recent threads, but at =
least for me, they aren't enough to gain a complete (or nearly complete) =
picture of the issue.
>=20
> Having studied statistics, we need to know a starting point, and look =
for the reductions (or increases) from that point forward. Starting in =
high school is not sufficiently refined enough, as there are a lot that =
take advanced math (personally I'd start with trig - because that kicked =
my ass - but rarely is it its own class, so let's start with calculus 1) =
that don't go into engineering. Thus, high school is probably not a good =
place to measure from. Therefore, it needs to be college.
>=20
> We need to know
>=20
> % of class (based on year started) that is female in engineering
>   (do we want to start with electrical and CS to
>    be more applicable to our situation?)
>=20
> We'll call that percent 'X'
>=20
> then
>=20
> %X of drops from engineering (BS) (or just elec/CS?) over the college =
years before graduation?
>=20
> then
>=20
> %X that enter workforce after BS in Engineering (or just elec/CS?) =
into the engineering field?
>=20
> then
>=20
> %X that start graduate school (MS) in engineering (or just elec/CS)?
>=20
> %X that receive MS degree in engineering (or just elec/CS)?
>=20
> %X that enter workforce after MS in Engineering (or just elec/CS?) =
into the engineering field?
>=20
> then
>=20
> %X that start doctoral school (PhD.) in engineering (or just elec/CS)?
>=20
> %X that achieve PhD. in engineering (or just elec/CS)?
>=20
> then
>=20
> %X that enter workforce after PhD in Engineering (or just elec/CS?) =
into the engineering field?
>=20
> This will likely track those that are entering the engineering =
workforce, and with what level of education. =46rom that point in the =
analysis - we can attempt to track at what point there are further drops =
out of the engineering workforce by women (i.e., after how many years). =
Or is it as simple as problems after childbirth to reenter the workforce =
(for whatever reason).
>=20
> As an example, if there is a significant difference from those that =
drop out after their BS from those that drop out MS, then maybe =
something should be done to encourage women to stay for the MS.
>=20
> comments or questions?
>=20
> James
>=20


From allison.mankin@gmail.com  Fri May  4 08:22:22 2012
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 8502821F86C2 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 08:22:20 -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 j4o6q7eSJHdj for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 08:22:19 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 901CC21F8700 for <ietf@ietf.org>; Fri,  4 May 2012 08:22:02 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2421464lbb.31 for <ietf@ietf.org>; Fri, 04 May 2012 08:22:01 -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=vsMcqRmwwsuASnD0yaLLhDn6Z3myoY3jp2W+i6HEL0I=; b=sIydOMD57luo8GBxrT1A2nhJUnZKU6Mlm+Fvc+c8jCbq9159OQy3Wfh9kG0oT96msH AHvuUcedRumQcA7+XS04RsNT9jtw5fom2k/dtKGi/SGfsRoWP0j12x4A9BXx3BQTnMem 5GlSjC/bP/QBGCud8MPVNL+Wfhgej7p7v9bnURi0voJNVP9j6BzSGWar+2oQIU5zVKVh 56UQ6jLTup7XxTG4E+7Lb4o+twDU2QKF4eevwhCQPjZPRsWg+B0XYQaG/6BXCEoN/Qnk JitgAwoIbw2bJfi9ZfDc2mEDZvq5YOlPZWvkNiy89XQHg02BiDiiZFJh2YFZf7rmu3IX YZaQ==
MIME-Version: 1.0
Received: by 10.112.29.166 with SMTP id l6mr3056486lbh.78.1336144921516; Fri, 04 May 2012 08:22:01 -0700 (PDT)
Received: by 10.112.41.162 with HTTP; Fri, 4 May 2012 08:22:01 -0700 (PDT)
In-Reply-To: <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>
Date: Fri, 4 May 2012 11:22:01 -0400
Message-ID: <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@mail.gmail.com>
Subject: Re: Gender diversity in engineering
From: Allison Mankin <allison.mankin@gmail.com>
To: Eric Burger <eburger-l@standardstrack.com>, "James M. Polk" <jmpolk@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 04 May 2012 15:22:24 -0000

A good URL for the NSF statistics:

http://www.nsf.gov/statistics/wmpd/

Also, there's extensive information and analysis about the
educational pipeline in the US (for all groups, and including K12) in
the 2010 American Association of University Women report "Why So Few?"

www.aauw.org/learn/research/upload/whysofew.pdf

I'd be interested to learn of studies of the CS workforce outside the
US.  Are there recruitment and attrition problems everywhere?

Allison



On Fri, May 4, 2012 at 5:20 AM, Eric Burger
<eburger-l@standardstrack.com> wrote:
>
> NSF has a ton of information on this for the U.S. population. =A0I'm too =
lazy right now to dig it up, but it is there.
>
> On May 1, 2012, at 4:40 PM, James M. Polk wrote:
>
> > There have been some good numbers floated on recent threads, but at lea=
st for me, they aren't enough to gain a complete (or nearly complete) pictu=
re of the issue.
> >
> > Having studied statistics, we need to know a starting point, and look f=
or the reductions (or increases) from that point forward. Starting in high =
school is not sufficiently refined enough, as there are a lot that take adv=
anced math (personally I'd start with trig - because that kicked my ass - b=
ut rarely is it its own class, so let's start with calculus 1) that don't g=
o into engineering. Thus, high school is probably not a good place to measu=
re from. Therefore, it needs to be college.
> >
> > We need to know
> >
> > % of class (based on year started) that is female in engineering
> > =A0 (do we want to start with electrical and CS to
> > =A0 =A0be more applicable to our situation?)
> >
> > We'll call that percent 'X'
> >
> > then
> >
> > %X of drops from engineering (BS) (or just elec/CS?) over the college y=
ears before graduation?
> >
> > then
> >
> > %X that enter workforce after BS in Engineering (or just elec/CS?) into=
 the engineering field?
> >
> > then
> >
> > %X that start graduate school (MS) in engineering (or just elec/CS)?
> >
> > %X that receive MS degree in engineering (or just elec/CS)?
> >
> > %X that enter workforce after MS in Engineering (or just elec/CS?) into=
 the engineering field?
> >
> > then
> >
> > %X that start doctoral school (PhD.) in engineering (or just elec/CS)?
> >
> > %X that achieve PhD. in engineering (or just elec/CS)?
> >
> > then
> >
> > %X that enter workforce after PhD in Engineering (or just elec/CS?) int=
o the engineering field?
> >
> > This will likely track those that are entering the engineering workforc=
e, and with what level of education. From that point in the analysis - we c=
an attempt to track at what point there are further drops out of the engine=
ering workforce by women (i.e., after how many years). Or is it as simple a=
s problems after childbirth to reenter the workforce (for whatever reason).
> >
> > As an example, if there is a significant difference from those that dro=
p out after their BS from those that drop out MS, then maybe something shou=
ld be done to encourage women to stay for the MS.
> >
> > comments or questions?
> >
> > James
> >
>

From dworley@avaya.com  Fri May  4 08:32:50 2012
Return-Path: <dworley@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 5F05221F877E for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 08:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.281
X-Spam-Level: 
X-Spam-Status: No, score=-103.281 tagged_above=-999 required=5 tests=[AWL=0.318, 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 n2kMbHkTDCXS for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 08:32:49 -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 95F6A21F877D for <ietf@ietf.org>; Fri,  4 May 2012 08:32:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJ31o0/GmAcF/2dsb2JhbABFsmWBB4IJAQEBAQIBEig/BQsCAQgNCCEQIRElAQEEDgUIGoddAwYFnXGTQA2JU4oLhh9jBJQmh3CFJ4UDgwQ
X-IronPort-AV: E=Sophos;i="4.75,531,1330923600"; d="scan'208";a="304938578"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 May 2012 11:32:10 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 May 2012 11:29:42 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 4 May 2012 11:32:44 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Allison Mankin <allison.mankin@gmail.com>
Date: Fri, 4 May 2012 11:30:09 -0400
Subject: RE: Gender diversity in engineering
Thread-Topic: Gender diversity in engineering
Thread-Index: Ac0qCb0MWGqg/BofQSGt0TwY/6Lx1QAAQyBO
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0AA8@DC-US1MBEX4.global.avaya.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>, <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@mail.gmail.com>
In-Reply-To: <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@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
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, 04 May 2012 15:32:50 -0000

> From: Allison Mankin [allison.mankin@gmail.com]
>=20
> I'd be interested to learn of studies of the CS workforce outside the
> US.  Are there recruitment and attrition problems everywhere?

I've seen reports in the popular press that the fraction of women
entering software is higher in many Asian countries than in the US, so
presumably there is solid information to that extent.

I've heard anecdotes that the fraction of women in software in Israel
is much higher than in the US.

Dale

From ondrej.sury@nic.cz  Thu May  3 08:54:18 2012
Return-Path: <ondrej.sury@nic.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E8421F865C; Thu,  3 May 2012 08:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level: 
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[AWL=-0.692, BAYES_05=-1.11, J_CHICKENPOX_23=0.6, 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 NQARRNz8dmHO; Thu,  3 May 2012 08:54:17 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0E021F865B; Thu,  3 May 2012 08:54:17 -0700 (PDT)
Received: from kimac-wifi.office.nic.cz (fw.nic.cz [217.31.207.1]) by mail.nic.cz (Postfix) with ESMTPSA id 793ED13F9E9; Thu,  3 May 2012 17:54:16 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1336060456; bh=wHXyacjAkR15b7HbfDQaN0ZpwkSWVFdO8vM3UickTZA=; h=Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=nmUF0VjLgbAcInhM4jYV+sYxJ9dyRin0YrV/5D7lAhx+pathX5AflpQTfzrUjrE4Y f286AL1Pmq1auHEX7WglTT/fs1WH1sofR1NtBJDwk6pXUF9VQtKeuQgD4Ru0me1OhB Q9SwONC1bNoHH5GR/fyfDTcir+HSfqQvllDd2oD0=
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=utf-8
From: =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= <ondrej.sury@nic.cz>
In-Reply-To: <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com>
Date: Thu, 3 May 2012 17:54:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz>
References: <01OE8FJG30ZM00ZUIL@mauve.mrochek.com> <ned+ietf@mauve.mrochek.com@Apr> <201204130359.q3D3xlG0007556@fs4113.wdf.sap.corp> <01OE9150IMNI00ZUIL@mauve.mrochek.com> <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1257)
X-Virus-Scanned: clamav-milter 0.96.5 at mail
X-Virus-Status: Clean
X-Mailman-Approved-At: Fri, 04 May 2012 10:29:00 -0700
Cc: ietf@ietf.org, dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:54:18 -0000

Phillip,

I haven't seen any consensus for the change of the document, thus
chairs think the document is fine as it is.

Ondrej

On 25. 4. 2012, at 15:52, Phillip Hallam-Baker wrote:

> I have raised these comments in the WG numerous times, I am raising
> them here as I do not believe that anyone is going to implement the
> specification as currently described.
>=20
> As currently written, the specification attempts to mandate client
> behavior when DANE records are encountered in ways that are outside
> the scope of interoperability. While the objective of the authors is
> to mandate certain behavior they consider necessary for security
> reasons, what they end up doing is attempting to substitute their own
> judgement for that of the security experts who advise the client
> providers.
>=20
>=20
> Client providers already ignore significant parts of the PKIX
> specification because they do not meet their performance criteria. In
> particular virtually all browsers treat inability to obtain OCSP
> certificate status as being equivalent to 'good'. This is a terrible
> security design, one that every CA would like to see change. But it is
> also a fact that we have been trying to get this changed for ten years
> without success.
>=20
> The browser providers do not hard fail on OCSP because doing so would
> require them to wait for the OCSP response within the TLS handshake
> and this is considered an unacceptable performance degradation. I do
> not like this situation, but I can either play Canute and tell the
> tide to turn or I can consider it to be a fact and try to work round
> it.
>=20
>=20
> DANE attempts to fix PKI with another mandate that is certain to be
> ignored. In this case the mandate is to establish a critical
> dependency on the DNSSEC trust chain despite the easily observed fact
> that less than 97% of DNS resolvers will pass anything other than
> A/AAAA and CNAME records.
>=20
> Section 4 of the draft mandates a client hardfail if the DNSSEC trust
> chain cannot be obtained. This is essential if the client is going to
> use DNSSEC to establish certificate constraints just as certificate
> revocation is an essential part of the PKIX model. But no browser
> provider can expect to succeed with a product that simply stops
> working when the user tries to surf the Web from a coffee shop.
>=20
> Since the coffee shop problem is not intentional we might imagine that
> it will eventually go away. But this puts DANE in a deployment
> deadlock bind. Nobody is going to fix their coffee shop routers until
> there is a need to and that need won't exist until the coffee shop
> routers are fixed.
>=20
> It is not just coffee shops that are the problem either. It might seem
> really easy to put an SSL cert on a server and keep it up to date but
> IETF participants represent the 1% of network admins. We all know from
> experience how successful protocols that require two sets of records
> to be kept in sync are. A protocol that requires a network admin to
> remember to update their DNS with each cert change or suffer a
> hardfail is going to have a very high administrative error rate.
>=20
>=20
> Rather than mandating hardfail or any particular client behavior, the
> specification should simply state that the client MUST conclude that
> the DANE status of the certificate is invalid and then leave the
> client to decide on what course of action to take. This will depend on
> the circumstances of the particular user and the client provider's
> assessment of the reliability of the DANE data and might range from do
> nothing to send a security policy violation notification somewhere to
> hardfail.
>=20
>=20
> Contrary to the assumptions of the specification authors, hard fail is
> not the best option. It is not even the best option in the case that
> the users are dissidents.
>=20
> To understand the logic of the dissident case it is important to have
> a change of perspective. The objective of the authorities is not to
> intimidate a single protester, it is to intimidate a whole country.
> Being a protester carries inevitable risks. No security protocol is
> going to eliminate those risks for the individual. What is important
> is to minimize the risk for the population as a whole.
>=20
> The Google cert pinning code did not provide much direct protection to
> the Iranian dissidents because it only covered one site. But it proved
> critical in exposing the Diginotar situation because it provided the
> first evidence of the breach. Had the client been designed slightly
> differently the breach might have become evident earlier.
>=20
>=20
> The coffee shop issue is unintended but there are also parties that
> are going to intentionally sabotage any infrastructure that looks like
> DANE. We are not in the 1990s any longer, people in authority no
> longer expect OSI to replace the Internet. The result is that it is
> much harder to get away with no infrastructure. At present there is no
> point in blocking DNSSEC records. But you can be sure that Iran,
> Russia and China will be doing so the minute any client started to
> make use of DANE. These countries can (and will) make use of a client
> hard fail to ensure that people don't use browsers that might be used
> for 'information terrorism' or freedom of speech as the rest of us
> call it.
>=20
> And don't think that out own governments necessarily mean what they
> say. In public Thatcher was a stalwart champion of freedom. In private
> she was begging Gorbachev to send in the tanks to stop the fall of the
> Berlin wall. Her own foundation has materials that report this
> exchange:
>=20
> http://www.margaretthatcher.org/document/112006
>=20
> The last thing I want to do is to hand the authorities another tool
> that can be used to selectively shut down the network at the critical
> moment in a crisis. Completely shutting off the Internet is one thing,
> it probably worked in our favor in Egypt as the 101st keyboarders lost
> their Internet connection and were forced to find out what was going
> on in the streets. It was a visceral sign of panic on the part of the
> regime.
>=20
>=20
> DANE is really a form of security policy information and so far there
> is no case where we have succeeded in applying raw security policy
> information at the client end. DKIM policies are a success because
> they are filtered and interpreted by the anti-spam services. There is
> a huge infrastructure in place that is working to apply the data from
> the DKIM records intelligently and equally importantly provides
> feedback to publishers of inconsistent records.
>=20
> DANE is proposed on the basis of a mistaken interpretation of how DKIM
> security policies work in practice and the result is a protocol that
> is deeply flawed and likely to fail.
>=20
> It would be a pity if the lack of success of a group that has
> steadfastly worked to ignore and discourage outside advice became a
> precedent to avoid future security policy efforts. Security policy is
> a very powerful tool, one that we can and must use if we are going to
> make the insecure Internet secure. But the DANE approach is too
> dogmatic to succeed.
> _______________________________________________
> dane mailing list
> dane@ietf.org
> https://www.ietf.org/mailman/listinfo/dane

--
 Ond=C5=99ej Sur=C3=BD -- Chief Science Officer
 -------------------------------------------
 CZ.NIC, z.s.p.o.    --    Laborato=C5=99e CZ.NIC
 Americka 23, 120 00 Praha 2, Czech Republic
 mailto:ondrej.sury@nic.cz    http://nic.cz/
 tel:+420.222745110       fax:+420.222745112
 -------------------------------------------


From john-ietf@jck.com  Fri May  4 10:44:00 2012
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 CA2F921F8637 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 10:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0ipaq7y7RVH for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 10:44:00 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C0FE521F8600 for <ietf@ietf.org>; Fri,  4 May 2012 10:43:59 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SQMSp-000Ay7-4d; Fri, 04 May 2012 13:38:43 -0400
Date: Fri, 04 May 2012 13:43:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Is the IETF aging?
Message-ID: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 17:44:00 -0000

--On Tuesday, May 01, 2012 19:07 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 5/1/12 5:55 PM, Worley, Dale R (Dale) wrote:
>> What would be good patterns for those roles?
> 
> I don't know what John has in mind but it strikes me that every
> so often we get a wave of new participants (as new topics
> and/or
> work areas are introduced) and it seems to me that it would be
> valuable if people who've been through the process a time or
> three could help mentor people who are new to the IETF but have
> drafts that have been adopted.  Presumably they can help with
> process and culture issues, as well.

That is pretty much what I had in mind ... mostly one on one. I
also think that there is a similar role for/with, e.g.,
newly-minted WG Chairs and document editors with the "advisor"
concentrating at least as much on helping on teaching/ showing
someone the ropes as on providing technical advice or oversight
to the WG itself.  

This has some dangers, or at least issues, that I think we need
to keep in mind.  

First, Paul Hoffman is exactly right.  To elaborate on the way I
understood his comment, the IETF community has a tendency to
turn good informal ideas into detailed structures and
requirements.  For example, we have evolved "BOF" from
"AD-approved informal discussion of potential work items" into a
highly-structured near-requirement for WG formation with
specific roles, combined IESG and IAB reviews, guidelines for
success in RFCs, and so on.  We almost certainly do not need to
have WGs with two Co-chairs, a Secretary, a few Editors, a
Responsible AD, a Technical Advisor, and designated Watchers/
Mentors for each person in the first three of those categories.
Too much formalism, too top-heavy, and possibly another barrier
to WG creation (of which, IMO, we already have too many).

I'd rather see this kept a little more informal or maybe a lot
more informal.  An AD should definitely be able to move someone
into a Chair or Co-chair position with designated support, but
it is at least as important that people who have been around for
a while be able to spot potential new talent and offer advice
and coaching in an informal environment.

I do have two major concerns with the way in which the
discussion has evolved.  First, vocabulary affects how we think
or at least how others assume we think.  "Greybeard" is a nasty
example of that because, no matter how much experience women
have in the IETF, few of them will sport beards or any color
and, at the risk of a silly example, expecting them to don such
garb on a regular basis is unreasonable.  So, unless we want to
send the message that all of the senior members of the community
are necessarily male (and inclined to grow beards), we need to
find another term.  

At the same time, while I'm all in favor of members of
particular communities drawing together to share experiences and
ways of coping with "the system", moves toward talking about the
IETF context in terms of "gender diversity" (or any other type
of "diversity") strike me as risky for the community.  If the
IETF were doing more user interface work, there would be a
really strong argument for making sure the IETF, or at least the
relevant WGs, were diverse enough to reflect the broader
community.   But I don't think that anyone has made a convincing
case that there is anything inherently "male" (or "northern", or
"white", or...) about TCP, IP, or much of anything else in the
IETF's sub-UI work.  Until and unless that case is made, I think
we need to be absolutely sure that capable and promising women
have at least as much opportunity to make useful contributions
in the IETF --including taking on leadership roles-- as capable
and promising men.  But, even a step or two in the direction of
promoting or preferring less-able women in order to make IETF
bodies more diverse would be likely to result in shooting
ourselves in our collective feet.

Let me also make a suggestion that I hope is constructive: the
newcomers meet-and-greet may be really helpful in giving the new
people a chance to meet some of those they should be working
with.   It would work better if a larger fraction of the
leadership sought out newcomers to talk with rather than
treating it as a pre-welcome-reception opportunity to talk with
each other, but I don't know how it fix that.   However those
newcomer sessions don't --I suggest can't-- work for forming
mentoring relationships for two reasons.  First, the people who
should be most available for mentoring are those with
significant IETF experience who do not have present WG Chair,
IESG, or IAB responsibilities.  But those people are excluded
from the newcomers meet and greet sessions.  Second, it is just
too early, especially since we, as a community, have little
control over who will be back the second and third time and the
second and third year.  So I suggest we think about how to put
together 2nd-comer or 3rd-comer opportunities with potential
(and committed) mentors available and other attendance limited
to self-selected relatively new people (but normally not
first-timers) who are interested in that kind of experience and
support.

    john



 




From john-ietf@jck.com  Fri May  4 11:02:18 2012
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 C0B2C21F8609 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DAOpQzxv2W8f for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:02:18 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 359B321F8607 for <ietf@ietf.org>; Fri,  4 May 2012 11:02:18 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SQMkX-000Azn-1m; Fri, 04 May 2012 13:57:01 -0400
Date: Fri, 04 May 2012 14:02:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, ietf@ietf.org
Subject: RE: Last Call: <draft-levine-application-gzip-02.txt> (The	application/zlib and application/gzip media types) to	Informational RFC
Message-ID: <2B5D4A5F530D7C2C1E81518A@PST.JCK.COM>
In-Reply-To: <9452079D1A51524AA5749AD23E00392810BFA5@exch-mbx901.corp.cloudmark.com>
References: <20120503212126.3638.47131.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392810BF15@exch-mbx901.corp.cloudmark.com> <01OF1TOTG2700006TF@mauve.mrochek.com> <9452079D1A51524AA5749AD23E00392810BFA5@exch-mbx901.corp.cloudmark.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: Fri, 04 May 2012 18:02:18 -0000

+1 

I'm still a little concerned about the boundary between media
(content) -type and content-transfer-encoding, but I've become
convinced that we should not put the burden of that issue onto
this document.  

I do believe that, someday, someone should try to write up an
up-to-date description of the difference that recognizes the
fact that compressed files are in use as media types with
application/zip (in assorted spellings) and application/gzip
(from this spec and in assorted spellings) as examples.  But I
now believe it is a separate task that should not block this
document or registration.

    john


--On Thursday, May 03, 2012 22:14 +0000 "Murray S. Kucherawy"
<msk@cloudmark.com> wrote:

>> -----Original Message-----
>> From: Ned Freed [mailto:ned.freed@mrochek.com]
>> Sent: Thursday, May 03, 2012 2:54 PM
>> To: Murray S. Kucherawy
>> Cc: ietf@ietf.org
>> Subject: RE: Last Call:
>> <draft-levine-application-gzip-02.txt> (The application/zlib
>> and application/gzip media types) to Informational RFC
>> 
>> > 1) Shouldn't this be Standards Track?
>> 
>> Based on past practices, the answer to that seems to be "no".
>> See, for example, RFC 6208, RFC 6207, RFC 6129, RFC 5967, and
>> so on.
>> 
>> [...]
>> 
>> > 2) Should it mention the "xdash" draft, since it talks about
>> "application/x-*" types?
>> 
>> That specification is really focused on not using x- in newly
>> defined registries, not on how it's used in existing
>> registries. And since x- gzip and friends are only mentioned
>> to say they shouldn't be used, I'd say that while such a
>> reference would not bother me, I don't think it's especially
>> helpful.
> 
> Good enough, just thought I'd ask.
> 
> I support publication as-is.
> 
> -MSK





From ted.ietf@gmail.com  Fri May  4 11:25:55 2012
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 2026C21F860B for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.592
X-Spam-Level: 
X-Spam-Status: No, score=-3.592 tagged_above=-999 required=5 tests=[AWL=0.007,  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 0fH41ukjnggi for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:25:54 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7949F21F8607 for <ietf@ietf.org>; Fri,  4 May 2012 11:25:54 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2676624vbb.31 for <ietf@ietf.org>; Fri, 04 May 2012 11:25: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=DHCuTYVaBZmuuajAeqq+zaywxitKBf5/iil5e8Dog3w=; b=bk30gkxeix84Kf6w9gIqqTh6Lx3Toj8SoEmfbTWvOPNtb1b5men/JwPeaq9sqgwl2H 8ZQ2xQPujyCUuHPWjYKdrOkur3NZXBhibYcEG9VgqvTtcJ9qkxEntkz8IuYYrs6LmgNr Fwz1DMaiz5EzdHo/lpWccfAyQvxnBos5UMf649AYs/LceyKtbNeoIqHhuoX2Nhoy/C0C 4XNlpSLp86uXSjgNs/gzF5BLRC+FjdjCpMxQwtROzgrO5PCAwtxhr85+bVKwyIQra29v phADDhOuvMj8qb0UZe9rWG5bc5+FBRP10QZ+UDXwpiL7jgc/XrlME4ccK1/2aNAr8jf/ nEYw==
MIME-Version: 1.0
Received: by 10.52.36.65 with SMTP id o1mr3457940vdj.59.1336154496988; Fri, 04 May 2012 11:01:36 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Fri, 4 May 2012 11:01:36 -0700 (PDT)
In-Reply-To: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com>
References: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com>
Date: Fri, 4 May 2012 11:01:36 -0700
Message-ID: <CA+9kkMDf=3rL6CE9-XRW2O2gDsTGROQVcWcMFsyjiKWHZUCvug@mail.gmail.com>
Subject: Re: Is the IETF aging?
From: Ted Hardie <ted.ietf@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 18:25:55 -0000

On Fri, May 4, 2012 at 10:43 AM, John C Klensin <john-ietf@jck.com> wrote:

"But, even a step or two in the direction of promoting or preferring
less-able women in order to make IETF  bodies more diverse would be
likely to result in shooting ourselves in our collective feet."

I think the analysis here is subtly wrong.  If you have two candidates
who can clearly do the job, it seems to imply that you should always
still stack rank them and pick the higher ranked.  But that's a very
local optimization.

Efforts to increase to diversity are a very different optimization--by
making more visible that opportunities are present for all, these
initiatives attempt to increase the pool of talent over time.  If
people who would previously have left a field stay or folks who had
not thought of entering a field do so, that field wins.  The scale of
that win can be the field of  "Science, Technology, Engineering, Math"
or it can be "working group leadership" or "the IETF".  But a bigger
pool of talent to draw from is a big win for almost any sized field.

regards,

Ted Hardie

From john-ietf@jck.com  Fri May  4 11:29:39 2012
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 10AC121F858E for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0ls4HlbGIdx for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 11:29:38 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFB821F8585 for <ietf@ietf.org>; Fri,  4 May 2012 11:29:38 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SQNB0-000B1R-1u; Fri, 04 May 2012 14:24:22 -0400
Date: Fri, 04 May 2012 14:29:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Is the IETF aging?
Message-ID: <84DF474E61E0F554266A72EE@PST.JCK.COM>
In-Reply-To: <CA+9kkMDf=3rL6CE9-XRW2O2gDsTGROQVcWcMFsyjiKWHZUCvug@mail.gmail.com>
References: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com> <CA+9kkMDf=3rL6CE9-XRW2O2gDsTGROQVcWcMFsyjiKWHZUCvug@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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 18:29:39 -0000

--On Friday, May 04, 2012 11:01 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:

> On Fri, May 4, 2012 at 10:43 AM, John C Klensin
> <john-ietf@jck.com> wrote:
> 
> "But, even a step or two in the direction of promoting or
> preferring less-able women in order to make IETF  bodies more
> diverse would be likely to result in shooting ourselves in our
> collective feet."
 
> I think the analysis here is subtly wrong.  If you have two
> candidates who can clearly do the job, it seems to imply that
> you should always still stack rank them and pick the higher
> ranked.  But that's a very local optimization.
> 
> Efforts to increase to diversity are a very different
> optimization--by making more visible that opportunities are
> present for all, these initiatives attempt to increase the
> pool of talent over time.  If people who would previously have
> left a field stay or folks who had not thought of entering a
> field do so, that field wins.  The scale of that win can be
> the field of  "Science, Technology, Engineering, Math" or it
> can be "working group leadership" or "the IETF".  But a bigger
> pool of talent to draw from is a big win for almost any sized
> field.

Ted,

I completely agree with that way of looking at things.  I was
reacting to something else --not a choice between "two
candidates who can clearly do the job" but to models that easily
can (and in some demonstrable cases in communities close to
ours, clearly have) shifted past that and into scoring systems
in which so much weight is given to diversity (by some measure)
that significantly less-qualified people --people who would be
unlikely to do as good a job or even an adequate one-- are
chosen in preference to more qualified ones who do not satisfy
the diversity criteria.  

I don't think the IETF wants to go there.  I'm reluctant to get
into name-calling by identifying examples of organizations
on-list that interact with the IETF that have gone down that
path, but will do so in private if needed.

   john






From johnl@iecc.com  Fri May  4 12:11:30 2012
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 8DEC821F85B8 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 12:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.242
X-Spam-Level: 
X-Spam-Status: No, score=-110.242 tagged_above=-999 required=5 tests=[AWL=0.957, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7XuJiopt4ynY for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 12:11:29 -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 410C521F85B4 for <ietf@ietf.org>; Fri,  4 May 2012 12:11:28 -0700 (PDT)
Received: (qmail 19349 invoked from network); 4 May 2012 19:11:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 May 2012 19:11: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:vbr-info; s=4fa429de.xn--btvx9d.k1205; i=johnl@user.iecc.com; bh=SvWejmjWGQ0vL2hLvq4KObTcTnaHoA3ZxDyUmX2jASE=; b=CAknZLLCmT6MClpD4i4Ht5gdY6ukbLMRvFTuPRiRQHYPpZDiKms415iTA6RkKxqPualganVQpGVkqNIzfRsTte3Dz1PjFXxzLn81/KFiN0mprWq9Nn3YjPYq1gMdnZqxnW/B0/seMo4VKrWFL18t/GOOs0cZgcoM5N0u9/OAj7o=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 May 2012 19:11:04 -0000
Message-ID: <20120504191104.24520.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-levine-application-gzip-02.txt> (The	application/zlib and application/gzip media types) to	Informational RFC
In-Reply-To: <2B5D4A5F530D7C2C1E81518A@PST.JCK.COM>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
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, 04 May 2012 19:11:30 -0000

>I do believe that, someday, someone should try to write up an
>up-to-date description of the difference that recognizes the
>fact that compressed files are in use as media types with
>application/zip (in assorted spellings) and application/gzip
>(from this spec and in assorted spellings) as examples.  But I
>now believe it is a separate task that should not block this
>document or registration.

I'll be happy to do that if I can ever find enough spare time to write
it.

You're right, it would be nice if there were some way to distinguish
containers from content in MIME types.  But given the existing
historical mess, and that some kinds of compression are just a
different way to encode a bunch of bits (zlib) whereas others are more
like a small filesystem (zip and tgz), even if we could start with a
clean sheet it's not obvious to me what would be the best thing to do.

R's,
John

From sm@resistor.net  Fri May  4 13:22:51 2012
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 F064F21F859A for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 13:22:51 -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=1.035, 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 jgSfHm4mAYLv for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 13:22:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EED21F856C for <ietf@ietf.org>; Fri,  4 May 2012 13:22:49 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q44KMfw5007015; Fri, 4 May 2012 13:22:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336162967; i=@resistor.net; bh=BB9eIRm9hv4i58doiR5Zlhokwng4xBDe4kgeuP9FTqM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cD0Q3yxQ8nLUyPEcEazw/bTk0ZO17xXzPuLsPDIWBrwkPJg3/YDbNNbClnPeKc8iG fG4qjUVHjqOE1YOFJ6VuyS4Wz2SiJ8kqgdLat3z6QPIZ8Iet+9KXQzlSvauR/g0UyO 4WRKWQu66nwj41pt/RGH5AjHAMdC4DT+jOPOVBS4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336162967; i=@resistor.net; bh=BB9eIRm9hv4i58doiR5Zlhokwng4xBDe4kgeuP9FTqM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XPuHls5j9Cd6cGlPBDgnRYcn9NIb3KfRQsUPuX+wp6fMBPP64k1yZ4OrVD2Nls6Ox uz5W0PhmEI0CO5mrBogRA8H8t0CkfcJ7u5OVyqAok+crbyx1R2I600c40lO90GWXq9 N9WpLIskTFAN8bZpDVTjz8EeHz+D0RlYe+srNESw=
Message-Id: <6.2.5.6.2.20120504110005.0ac44140@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 04 May 2012 13:08:28 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Is the IETF aging?
In-Reply-To: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com>
References: <FCBBE378343C667A71ECA2A1@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 20:22:52 -0000

Hi John,
At 10:43 04-05-2012, John C Klensin wrote:
>garb on a regular basis is unreasonable.  So, unless we want to
>send the message that all of the senior members of the community
>are necessarily male (and inclined to grow beards), we need to
>find another term.

The term SIR was proposed instead of male and knighted.

>IETF's sub-UI work.  Until and unless that case is made, I think
>we need to be absolutely sure that capable and promising women
>have at least as much opportunity to make useful contributions
>in the IETF --including taking on leadership roles-- as capable
>and promising men.  But, even a step or two in the direction of

There hasn't been any response to the gender note sent to another 
IETF mailing list a few days ago.  It's one thing to provide 
opportunities for women; making it happen is another story.  If you 
or anyone else know anyone who is interested, I'll contribute.

>Let me also make a suggestion that I hope is constructive: the
>newcomers meet-and-greet may be really helpful in giving the new
>people a chance to meet some of those they should be working
>with.   It would work better if a larger fraction of the
>leadership sought out newcomers to talk with rather than
>treating it as a pre-welcome-reception opportunity to talk with
>each other, but I don't know how it fix that.   However those

It has an air of formality.  It's a constructive step though.

Currently, there's a two hour session for newcomers with around 65 
slides.  It's a lot of content, a lot of acronyms and a lot of rules 
and sub-rules.  There's also a two hour session about how to create 
I-D at the same time.  The newcomer has to choose between learning 
about the IETF or learning how to create I-Ds.  They then go into a 
room full of strange people where it is a miss and hit affair like 
Internet dating.

>newcomer sessions don't --I suggest can't-- work for forming
>mentoring relationships for two reasons.  First, the people who
>should be most available for mentoring are those with
>significant IETF experience who do not have present WG Chair,
>IESG, or IAB responsibilities.  But those people are excluded
>from the newcomers meet and greet sessions.  Second, it is just
>too early, especially since we, as a community, have little
>control over who will be back the second and third time and the
>second and third year.  So I suggest we think about how to put
>together 2nd-comer or 3rd-comer opportunities with potential
>(and committed) mentors available and other attendance limited
>to self-selected relatively new people (but normally not
>first-timers) who are interested in that kind of experience and
>support.

The 2nd-comer and 2rd-comer idea is interesting.  There is free time 
and free rooms on tutorial day.  How about getting a room, get people 
who are interested in there and send an informal invitation to the 
attendees?  You could even have affinity groups to avoid the old-boys 
club atmosphere.

Regards,
-sm 


From ynir@checkpoint.com  Fri May  4 14:20:45 2012
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 3B61C21F855B for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 14:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.362
X-Spam-Level: 
X-Spam-Status: No, score=-10.362 tagged_above=-999 required=5 tests=[AWL=0.237, 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 VPiiANeqh00j for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 14:20:44 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7011121F847C for <ietf@ietf.org>; Fri,  4 May 2012 14:20:43 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q44LKcsh031521;  Sat, 5 May 2012 00:20:38 +0300
X-CheckPoint: {4FA455E1-2-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 5 May 2012 00:20:37 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Date: Sat, 5 May 2012 00:20:39 +0300
Subject: Re: Gender diversity in engineering
Thread-Topic: Gender diversity in engineering
Thread-Index: Ac0qO79JEODICgIxS/eMPPS6HST8sg==
Message-ID: <8638E241-928A-421F-A7A2-DDB404ADBAC3@checkpoint.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>, <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA8@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0AA8@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1141aa25e462fe5c64397e0892d586f881bea18144
Content-Type: text/plain; charset="us-ascii"
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: Fri, 04 May 2012 21:20:45 -0000

On May 4, 2012, at 6:30 PM, Worley, Dale R (Dale) wrote:

>> From: Allison Mankin [allison.mankin@gmail.com]
>>=20
>> I'd be interested to learn of studies of the CS workforce outside the
>> US.  Are there recruitment and attrition problems everywhere?
>=20
> I've seen reports in the popular press that the fraction of women
> entering software is higher in many Asian countries than in the US, so
> presumably there is solid information to that extent.
>=20
> I've heard anecdotes that the fraction of women in software in Israel
> is much higher than in the US.

Around 30%-40%. I don't have hard numbers, but I have a feeling that it has=
 gone down a bit in the last 10 years. One of my tasks is to give a monthly=
 "VPN basics" talk to new recruits, and women seem to be about 1 in 4. This=
 could be specific to my company, though.

Yoav=

From hallam@gmail.com  Fri May  4 18:50:22 2012
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 59FEC21E8029 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 18:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.571
X-Spam-Level: 
X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028,  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 TZd2Agnvn6Wd for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 18:50:21 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC4121E8018 for <ietf@ietf.org>; Fri,  4 May 2012 18:50:21 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so5619514obb.31 for <ietf@ietf.org>; Fri, 04 May 2012 18:50: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:content-transfer-encoding; bh=Z6eblm/GVK2Dqa6HI9mNZQ9LJZQ2NnVmSk1NyE/kiJM=; b=0hf3xR9JR7RXrGSqhn3ZZqblhxsQFq/zS+uvjDQB1o6TDMUe5bnHYNm/cyhzHa2aMj vHxUQKzjsdn8BtEY+3uMD5JTz8A+O4YBQ+lLhyuvCyFsXKHNpwIaijjNh73O2xRIrGCI KmfhclVChk7y/FRP3wstEFYzmsBqjrrOyN636Sc+/V1igBxWqlE1vMOj0k24d6QU6ine fqa8598SLLzaDVSjfiwdQfkvaRLpysdTIFWJOKD/OodO2gFSkpPj/YWDlIHhXRbzBHoy dKpqS2zV7iS2N2EGcIHnDyoVmkfEzE4wC87bWtWssZDC+TxWUMLj6OfgathM8/+owgDA OMHw==
MIME-Version: 1.0
Received: by 10.60.26.231 with SMTP id o7mr11328579oeg.31.1336182621059; Fri, 04 May 2012 18:50:21 -0700 (PDT)
Received: by 10.182.41.165 with HTTP; Fri, 4 May 2012 18:50:20 -0700 (PDT)
In-Reply-To: <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>
Date: Fri, 4 May 2012 21:50:20 -0400
Message-ID: <CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com>
Subject: Re: Is the IETF aging?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 05 May 2012 01:50:22 -0000

On Wed, May 2, 2012 at 3:14 PM, Hannes Tschofenig
<hannes.tschofenig@gmx.net> wrote:
> Hi PHB,
>
> the IETF is not like an enterprise where you can decide (as part of the h=
iring process) what characteristics your employees should have.

True, but that does not mean that you should decide that there is
nothing the IETF can do to change those characteristics or is in fact
doing albeit unintentionally.


> In a volunteer organization the offered topics drive the participation. A=
sk yourself: what you as someone who just finished a university education w=
ant to hang around in the IETF to standardize yet another IPv4/IPv6 transit=
ion mechanism or to participate in the MPLS-TP discussions?

That is one aspect that might influence the decision. But there is a
huge amount of Internet development going on right now and the mean
age of the developers writing protocols is likely in the 20s.

The IETF has a security area and an Apps area, its not just routing.


> When people suggest new work to the IETF they often see a strange reactio=
n. I remember when Mozilla came to the IETF and proposed to work on the pri=
vacy topic "Do Not Track". I couldn't find support for doing the work in th=
e IETF. I don't exactly know why people didn't like it but the W3C immediat=
ely picked it up and had seen lots of new companies (mostly from the advert=
ising industry) joining the W3C.


And often the people who show them the door are people who contribute
absolutely nothing to the process other than their opinion. They don't
have any pull with the parties that are needed to act to deploy, they
don't have any real technical chops, they don't even have official
positions often.

But when proposals are raised in IETF it only takes five or six people
in a WG who bring nothing to the table to kill an idea.

Now that might be justified if the argument was that the idea was
likely to cause actual damage. But when the argument is 'I am not
convinced of the need for this' well whats the point?


I have just finished a couple of drafts that I have strong backing for
in my industry. The decision to deploy or not will be taken by my
industry, not the IETF.

The reason I raised this is that I can see a generation gap in my
industry. The IETF has ceased to be the leading force in PKI standards
development because the younger engineers don't want to have to engage
here.



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

From marshall.eubanks@gmail.com  Fri May  4 18:58:05 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3E1521E801B for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 18:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.651
X-Spam-Level: 
X-Spam-Status: No, score=-103.651 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 om5qigBJrFxv for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 18:58:04 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id EA00521E8018 for <ietf@ietf.org>; Fri,  4 May 2012 18:58:03 -0700 (PDT)
Received: by lagj5 with SMTP id j5so2772815lag.31 for <ietf@ietf.org>; Fri, 04 May 2012 18:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=XEOBEd/qoLi7xsd8btj4evmBkGymGtL/ZGtarVNUNNw=; b=GSnpvOdp7rPEaG/f1plhggmXT1UGik6Q5TuMVVTFwZQvEnmar81pFKfX1MA8OONmLm BoV81f2FCPdbgR+s86cgWLpvEOM2kPLx//sK/gEuSxYE75+I/a5kLYbtQzxMBldW0c10 NviBruApnlcakRMBWT7kf28EV/biZMp6DsGOCbH1FJjqCt3nNuuyatqLkJsEzr+HHpXy Jsbi2ds8a603iBMe8JPoyKxssj6Cmq0Zc2A8d2NkZDxkm2V3hbwyuIAtv6ZISaBV5/2P Rtu7C+shYPWyrJE/yHM40Q1NJYoSNrQFa3jmOEszPhu4l2fx+FfCiNZuwcv3TbJEyi6N F0RQ==
MIME-Version: 1.0
Received: by 10.112.104.99 with SMTP id gd3mr4131167lbb.70.1336183082853; Fri, 04 May 2012 18:58:02 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Fri, 4 May 2012 18:58:02 -0700 (PDT)
In-Reply-To: <CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net> <CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com>
Date: Fri, 4 May 2012 21:58:02 -0400
Message-ID: <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
Subject: Re: Is the IETF aging?
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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, 05 May 2012 01:58:05 -0000

On Fri, May 4, 2012 at 9:50 PM, Phillip Hallam-Baker <hallam@gmail.com> wro=
te:
> On Wed, May 2, 2012 at 3:14 PM, Hannes Tschofenig
> <hannes.tschofenig@gmx.net> wrote:
>> Hi PHB,
>>
>> the IETF is not like an enterprise where you can decide (as part of the =
hiring process) what characteristics your employees should have.
>
> True, but that does not mean that you should decide that there is
> nothing the IETF can do to change those characteristics or is in fact
> doing albeit unintentionally.

So, what would you do to adjust things ?

Regards
Marshall

>
>
>> In a volunteer organization the offered topics drive the participation. =
Ask yourself: what you as someone who just finished a university education =
want to hang around in the IETF to standardize yet another IPv4/IPv6 transi=
tion mechanism or to participate in the MPLS-TP discussions?
>
> That is one aspect that might influence the decision. But there is a
> huge amount of Internet development going on right now and the mean
> age of the developers writing protocols is likely in the 20s.
>
> The IETF has a security area and an Apps area, its not just routing.
>
>
>> When people suggest new work to the IETF they often see a strange reacti=
on. I remember when Mozilla came to the IETF and proposed to work on the pr=
ivacy topic "Do Not Track". I couldn't find support for doing the work in t=
he IETF. I don't exactly know why people didn't like it but the W3C immedia=
tely picked it up and had seen lots of new companies (mostly from the adver=
tising industry) joining the W3C.
>
>
> And often the people who show them the door are people who contribute
> absolutely nothing to the process other than their opinion. They don't
> have any pull with the parties that are needed to act to deploy, they
> don't have any real technical chops, they don't even have official
> positions often.
>
> But when proposals are raised in IETF it only takes five or six people
> in a WG who bring nothing to the table to kill an idea.
>
> Now that might be justified if the argument was that the idea was
> likely to cause actual damage. But when the argument is 'I am not
> convinced of the need for this' well whats the point?
>
>
> I have just finished a couple of drafts that I have strong backing for
> in my industry. The decision to deploy or not will be taken by my
> industry, not the IETF.
>
> The reason I raised this is that I can see a generation gap in my
> industry. The IETF has ceased to be the leading force in PKI standards
> development because the younger engineers don't want to have to engage
> here.
>
>
>
> --
> Website: http://hallambaker.com/

From ned+ietf@mauve.mrochek.com  Fri May  4 19:29:18 2012
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 C984921F84A6 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 19:29: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRqZKGSVTaEi for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 19:29:18 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDBB21F84A0 for <ietf@ietf.org>; Fri,  4 May 2012 19:29:18 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF3H57CULC00142Q@mauve.mrochek.com> for ietf@ietf.org; Fri, 4 May 2012 19:29:11 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OENEYWYFI80006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 4 May 2012 19:29:06 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OF3H54UZIS0006TF@mauve.mrochek.com>
Date: Fri, 04 May 2012 19:26:55 -0700 (PDT)
Subject: Re: Last Call: <draft-levine-application-gzip-02.txt>	(The application/zlib and application/gzip media types)	to	Informational RFC
In-reply-to: "Your message dated Fri, 04 May 2012 19:11:04 +0000" <20120504191104.24520.qmail@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <2B5D4A5F530D7C2C1E81518A@PST.JCK.COM> <20120504191104.24520.qmail@joyce.lan>
To: John Levine <johnl@iecc.com>
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: Sat, 05 May 2012 02:29:18 -0000

> >I do believe that, someday, someone should try to write up an
> >up-to-date description of the difference that recognizes the
> >fact that compressed files are in use as media types with
> >application/zip (in assorted spellings) and application/gzip
> >(from this spec and in assorted spellings) as examples.  But I
> >now believe it is a separate task that should not block this
> >document or registration.

That pretty much sums up my view as well.

> I'll be happy to do that if I can ever find enough spare time to write
> it.

> You're right, it would be nice if there were some way to distinguish
> containers from content in MIME types.  But given the existing
> historical mess, and that some kinds of compression are just a
> different way to encode a bunch of bits (zlib) whereas others are more
> like a small filesystem (zip and tgz), even if we could start with a
> clean sheet it's not obvious to me what would be the best thing to do.

This is further complicated by the fact that there are now a number of types
defined that are actually zip with specific semantics attached to the content.
There are also types defined for use only within such containers.

				Ned

From john-ietf@jck.com  Fri May  4 20:15:49 2012
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 F07D921E8029 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 20:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjP2s2LAsKle for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 20:15:49 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBCA21F8495 for <ietf@ietf.org>; Fri,  4 May 2012 20:15:49 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SQVO8-000Bfi-48; Fri, 04 May 2012 23:10:28 -0400
Date: Fri, 04 May 2012 23:15:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>, John Levine <johnl@iecc.com>
Subject: Re: Last Call: <draft-levine-application-gzip-02.txt>	(The	application/zlib and application/gzip media types)	to	Informational RFC
Message-ID: <25F56945DB03E8A51FC14EB2@PST.JCK.COM>
In-Reply-To: <01OF3H54UZIS0006TF@mauve.mrochek.com>
References: <2B5D4A5F530D7C2C1E81518A@PST.JCK.COM> <20120504191104.24520.qmail@joyce.lan> <01OF3H54UZIS0006TF@mauve.mrochek.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: Sat, 05 May 2012 03:15:50 -0000

--On Friday, May 04, 2012 19:26 -0700 Ned Freed
<ned.freed@mrochek.com> wrote:

>> You're right, it would be nice if there were some way to
>> distinguish containers from content in MIME types.  But given
>> the existing historical mess, and that some kinds of
>> compression are just a different way to encode a bunch of
>> bits (zlib) whereas others are more like a small filesystem
>> (zip and tgz), even if we could start with a clean sheet it's
>> not obvious to me what would be the best thing to do.
> 
> This is further complicated by the fact that there are now a
> number of types defined that are actually zip with specific
> semantics attached to the content. There are also types
> defined for use only within such containers.

With the wonderful advantage of hindsight, it might have been
better to define compound Content-Types/Media Types or a
universal encoding parameter rather than trying to separate
C-T-E out.   The first might have given us, e.g.,
application/foo+base64 and 'application/bar+xml+gzip' or
'application/bar+xml+gzip+base64'; the second something like
application/foo; encoding="base64" and 'application/bar+xml;
encoding=gzip+base64'.  Obviously a little late now :-(

And, again, not a blocking issue for this document, one way or
the other.

   john




From ynir@checkpoint.com  Fri May  4 20:48:54 2012
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 4B86611E8081 for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 20:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.366
X-Spam-Level: 
X-Spam-Status: No, score=-10.366 tagged_above=-999 required=5 tests=[AWL=0.233, 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 DhGDMrA-S5We for <ietf@ietfa.amsl.com>; Fri,  4 May 2012 20:48:53 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6763B11E8072 for <ietf@ietf.org>; Fri,  4 May 2012 20:48:52 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q453mnrY003812;  Sat, 5 May 2012 06:48:49 +0300
X-CheckPoint: {4FA4B0D9-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 5 May 2012 06:48:47 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Date: Sat, 5 May 2012 06:48:53 +0300
Subject: Re: Is the IETF aging?
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0qcfltNLNJ4Dv+QbinDjYMcsthDg==
Message-ID: <E23229AB-6B85-4D17-87C1-6C5D8CF721CE@checkpoint.com>
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net> <CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com> <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
In-Reply-To: <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 119099044b2b9a351a6169646392a844257c1a4a4e
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 May 2012 03:48:54 -0000

On May 5, 2012, at 4:58 AM, Marshall Eubanks wrote:

> On Fri, May 4, 2012 at 9:50 PM, Phillip Hallam-Baker <hallam@gmail.com> w=
rote:
>> On Wed, May 2, 2012 at 3:14 PM, Hannes Tschofenig
>> <hannes.tschofenig@gmx.net> wrote:
>>> Hi PHB,
>>>=20
>>> the IETF is not like an enterprise where you can decide (as part of the=
 hiring process) what characteristics your employees should have.
>>=20
>> True, but that does not mean that you should decide that there is
>> nothing the IETF can do to change those characteristics or is in fact
>> doing albeit unintentionally.
>=20
> So, what would you do to adjust things ?

I'm not PHB, but an obvious idea would be to change the requirements for a =
new work item from "rough consensus" to "a bunch of people willing to do th=
e work and at least one willing to implement".  Some working groups already=
 work like this, but it's not universal.=

From sant9442@gmail.com  Sat May  5 15:39:38 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4752821F8585 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 15:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.078
X-Spam-Level: 
X-Spam-Status: No, score=-2.078 tagged_above=-999 required=5 tests=[AWL=1.521,  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 SBl0jOKY4pD8 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 15:39:37 -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 6C1FA21F8582 for <ietf@ietf.org>; Sat,  5 May 2012 15:39:37 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so792109ggm.31 for <ietf@ietf.org>; Sat, 05 May 2012 15:39: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 :content-type:content-transfer-encoding; bh=1XTXK8DZeBR/SJKueMAnXUi6HVz5LpCPNLthtbEpJ1Q=; b=ftN7FkZ4viSjPWEEyZcpb+kgtYMd+ivhtxKPts1dKQ2SvUyZUUGZBwxencFcNm8YZZ 8MGSmU8bCojYDwAt4nc8Mf3IOj+ER70XEOr+w9YBNJa5AuA+fYXB/co9A0qZkVCimiS8 twL29/CjNHI2TpPna2w3u/6AAOEZWtL1HKZEQuvsS5naqvI0AfuoBAK1pObBvB+WpPFE g+T8a9QMPGRqXC8cDGf5X/kV8WKEsZXu2Q531V1JAr1IFVeL6gsH/H/irMzfSX469g2F FomlPmqhhdpi8eo4PGbqIQ3Vt3DETf+zmqNcPI1GVZA7ut+9O3o1Hn5SC/zeVQFkaVrD i3WA==
Received: by 10.236.190.234 with SMTP id e70mr13560906yhn.62.1336257576859; Sat, 05 May 2012 15:39:36 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id d11sm59326345yhi.21.2012.05.05.15.39.34 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 May 2012 15:39:35 -0700 (PDT)
Message-ID: <4FA5AC1F.4010005@gmail.com>
Date: Sat, 05 May 2012 18:39:27 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: IETF posting delays
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 May 2012 22:39:38 -0000

For IETF mailing lists like this, I would prefer to use my real 
"professional" email address hsantos@santronics.com. However, since it 
often takes over 24 hours or longer, and in cases over the year "lost" 
(never posted), I regularly now use my junk gmail.com alias account 
which is posted on the IETF list "immediately" with a copy sent my 
santronics.com account hosting server and picked up within minutes of 
my next mail reader pop3 poll.

Have others experience similar delays with their accounts? and had to 
use other domains, like gmail.com?

When I first begin to take notice a while back and last year I decided 
to ask the list admin.  He replied shortly and indicated there was no 
moderation. I also asked a few IETF veterans, a WG chair and AD, and 
they all repeated there was no moderation going on.

But I believe I read an IETF person in the list explained delays was 
mostly due to moderation. If so, while I don't see any reason for it, 
I was never given any notice my email would be moderated and I would 
like to ask why my email is being moderated?

Of course, it doesn't make sense because if there was moderation it 
would be on the address and not the "person" since I can post via 
gmail.com.

If not the case, trying to provide the benefit of doubt and seeking a 
logical reason for it, I figured the IETF list/MTA software is using 
some custom outbound queuing/scheduling logic with a higher preference 
for email domain volume, i.e. gmail.com at the top and individual 
domain accounts last in its scheduling logic.  Since gmail.com is a 
popular account used by many in this list, maybe that would explain 
why the MTA sending this out faster than others. I offered this 
logical out reason to the list admin and he wasn't sure of the legacy 
software queuing logic.

Anyway, just trying to figure out why the delays since I can stick 
with my real account and not the gmail.com junk account.

Thanks

--
HLS

From randy@psg.com  Sat May  5 19:40:11 2012
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 C70B421F84EC for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 19:40: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 z8M9yZ1kwTmK for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 19:40:11 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5C14621F84E6 for <ietf@ietf.org>; Sat,  5 May 2012 19:40:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SQrOM-0006zU-96; Sun, 06 May 2012 02:40:10 +0000
Date: Sat, 05 May 2012 16:40:09 -1000
Message-ID: <m2vckac9rq.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Hector <sant9442@gmail.com>
Subject: Re: IETF posting delays
In-Reply-To: <4FA5AC1F.4010005@gmail.com>
References: <4FA5AC1F.4010005@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 02:40:11 -0000

> When I first begin to take notice a while back and last year I decided 
> to ask the list admin.  He replied shortly and indicated there was no 
> moderation. I also asked a few IETF veterans, a WG chair and AD, and 
> they all repeated there was no moderation going on.
> 
> But I believe I read an IETF person in the list explained delays was 
> mostly due to moderation. If so, while I don't see any reason for it, 
> I was never given any notice my email would be moderated and I would 
> like to ask why my email is being moderated?

i know of no moderated lists.  but, instead of conjecturbation, let's
debug the problem.  please show the Received: and other header lines of
a message posted from your work address.  or just post one now and we
can see it for ourselves.  thanks.

randy

From hannes.tschofenig@nsn.com  Sat May  5 20:53:13 2012
Return-Path: <hannes.tschofenig@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 6C5E321F84FF for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.027
X-Spam-Level: 
X-Spam-Status: No, score=-106.027 tagged_above=-999 required=5 tests=[AWL=0.572, 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 7WABNV4v5Gnr for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:53:12 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD7E21F84EC for <ietf@ietf.org>; Sat,  5 May 2012 20:53:11 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q463r3bB014657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 6 May 2012 05:53:03 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q463r05Q023942; Sun, 6 May 2012 05:53:03 +0200
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 6 May 2012 05:53:00 +0200
Received: from 10.144.240.63 ([10.144.240.63]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Sun,  6 May 2012 03:52:59 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Sun, 06 May 2012 06:51:34 +0300
Subject: Re: Is the IETF aging?
From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
To: Avri Doria <avri@psg.com>, IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <CBCBCFF6.32D8%hannes.tschofenig@nsn.com>
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0rO4eAMCTQ/EwRhU2eE8S1d6A8LA==
In-Reply-To: <3494DB29-775B-491A-B1E2-C87AD85E1A4F@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 May 2012 03:53:00.0737 (UTC) FILETIME=[BB332B10:01CD2B3B]
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: 1434
X-purgate-ID: 151667::1336276385-00001F01-25093217/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: Sun, 06 May 2012 03:53:13 -0000

Hi Avri, 

> It may not be line a hiring manager, but all those who have budget can make it
> a point to make sure some of the younger engineers get to some of the
> meetings, at least the ones that are relatively local to them.  I assume that
> many of the older participants, have the means to influence the travel lists.
> For years there have been people working on the gender balance perhaps some
> focus on the age balance may become appropriate.

My experience in selecting people who go to standards organizations is a bit
different. Managers typically don't pick people based on discussion skills,
social kills, communication + language skills, writing skills, hair color,
etc. Instead, those who suggest topics and raise their hand at the right
time go to meetings and work on selected topics. There are not that many
people available who are interested in this type of work.

Then, there is an incredible stickiness for staying within the same
organization. If you have started attending 3GPP meetings then you typically
go there forever. You may switch groups and topics (within an organization)
but you rarely see people switching organizations.

In the telecommunication industry you have also seen a lot of layoffs over
the last 10 years and so there are rarely young people around in these
companies anymore (because they either got fired or left the company
voluntarily). 
 
Ciao
Hannes


From hannes.tschofenig@nsn.com  Sat May  5 20:53:28 2012
Return-Path: <hannes.tschofenig@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 378CD21F84F0 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.091
X-Spam-Level: 
X-Spam-Status: No, score=-106.091 tagged_above=-999 required=5 tests=[AWL=0.508, 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 sRWPtD2JDfMW for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:53:27 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6479A21F84FF for <ietf@ietf.org>; Sat,  5 May 2012 20:53:27 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q463rO79014795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 6 May 2012 05:53:24 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q463rORl015841; Sun, 6 May 2012 05:53:24 +0200
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 6 May 2012 05:53:24 +0200
Received: from 10.144.240.63 ([10.144.240.63]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Sun,  6 May 2012 03:53:22 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Sun, 06 May 2012 06:52:17 +0300
Subject: Re: Is the IETF aging?
From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
To: <mrex@sap.com>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Message-ID: <CBCBD021.32DD%hannes.tschofenig@nsn.com>
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0rO6EhdG/8sEv/bE2fyoYk/N5GfA==
In-Reply-To: <201205022007.q42K77mv009497@fs4113.wdf.sap.corp>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 May 2012 03:53:24.0299 (UTC) FILETIME=[C93E71B0:01CD2B3B]
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: 1413
X-purgate-ID: 151667::1336276404-00001F01-717233B9/0-0/0-0
Cc: Phillip Hallam-Baker <hallam@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: Sun, 06 May 2012 03:53:28 -0000

Hi Martin, 

The DNT privacy work was just an example of something that did not work out.
At this point in time the details don't matter anymore since the work
already happens at the W3C.

My point is that you will not find interest from young engineers to work on
10 year old topics. You can try it yourself: give a talk at a university and
see the reaction from the students. Pick a lower-layer topic and a topic
from the application layer (some Web stuff).

Ciao
Hannes
 
On 5/2/12 11:07 PM, "ext Martin Rex" <mrex@sap.com> wrote:

> Hannes Tschofenig wrote:
>> 
>> When people suggest new work to the IETF they often see a strange
>> reaction. I remember when Mozilla came to the IETF and proposed to
>> work on the privacy topic "Do Not Track". I couldn't find support
>> for doing the work in the IETF. I don't exactly know why people
>> didn't like it but the W3C immediately picked it up and had seen
>> lots of new companies (mostly from the advertising industry)
>> joining the W3C.
> 
> What exactly to you mean by "came to the IETF and proposed to work
> on the privacy topic"?
> 
> What is the I-D that you submitted and how many volunteers were there
> to do the work?  And who opposed that you do the work within the
> IETF?
> 
> What usually does not work in the IETF is that you "drop off" an idea
> and "pick up" a standard some time later...
> 
> -Martin


From marshall.eubanks@gmail.com  Sat May  5 20:54:27 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BB821F850C for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.649
X-Spam-Level: 
X-Spam-Status: No, score=-103.649 tagged_above=-999 required=5 tests=[AWL=-0.050, 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 FgLtsJQaeWew for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 20:54:26 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2277521F84F0 for <ietf@ietf.org>; Sat,  5 May 2012 20:54:25 -0700 (PDT)
Received: by lagj5 with SMTP id j5so3211302lag.31 for <ietf@ietf.org>; Sat, 05 May 2012 20:54: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:content-transfer-encoding; bh=Kxik/V1/IrKCADTKZoqKgQMuEMVOAxZRbVH/vU7nmas=; b=E9NaffSIPii2DqrxHfTEUfrlvjXrLmnmZ6fef6CIpjXBp5lWq+Qab4pfE8eQvUphvD Sy1EjRrBgnBDBDPRABIotY6EsmRKO1if4UQmjegnVb0N+gryYg2FBIQTpSi5bXizFppr F9yZYYJVZccjOcS52dankIERxeGRuN1AT8fhaQ+zUpS297v72veQsMV6V4kH13G/PBZh uDXtUar5OPO6A9Nph9+7HYQH38qkJgG9dj0cGnt1c5hXqIWYx2aETgg79xBB34Hf6GyR tKfbFmCB3OF5Bwu1i9mCwZxEpOHZOrITumyUMCtp+NA039e+ackYlmqq6rb2KFM2siAD sMKA==
MIME-Version: 1.0
Received: by 10.112.104.99 with SMTP id gd3mr5593681lbb.70.1336276464775; Sat, 05 May 2012 20:54:24 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Sat, 5 May 2012 20:54:24 -0700 (PDT)
In-Reply-To: <4FA5AC1F.4010005@gmail.com>
References: <4FA5AC1F.4010005@gmail.com>
Date: Sat, 5 May 2012 23:54:24 -0400
Message-ID: <CAJNg7VKZqdTbiQSAQDNh3-fLr+6sUk+kB5HBDFgczJA2ENMx8A@mail.gmail.com>
Subject: Re: IETF posting delays
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Hector <sant9442@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 03:54:27 -0000

On Sat, May 5, 2012 at 6:39 PM, Hector <sant9442@gmail.com> wrote:
> For IETF mailing lists like this, I would prefer to use my real
> "professional" email address hsantos@santronics.com. However, since it of=
ten
> takes over 24 hours or longer, and in cases over the year "lost" (never
> posted), I regularly now use my junk gmail.com alias account which is pos=
ted
> on the IETF list "immediately" with a copy sent my santronics.com account
> hosting server and picked up within minutes of my next mail reader pop3
> poll.

You should post an email that had this problem _with full headers_ to
action@ietf.org, which will open a trouble ticket.

It is possible you have been caught up in the anti-spam system, or you
may have uncovered some other problem.

Regards
Marshall


>
> Have others experience similar delays with their accounts? and had to use
> other domains, like gmail.com?
>
> When I first begin to take notice a while back and last year I decided to
> ask the list admin. =A0He replied shortly and indicated there was no
> moderation. I also asked a few IETF veterans, a WG chair and AD, and they
> all repeated there was no moderation going on.
>
> But I believe I read an IETF person in the list explained delays was most=
ly
> due to moderation. If so, while I don't see any reason for it, I was neve=
r
> given any notice my email would be moderated and I would like to ask why =
my
> email is being moderated?
>
> Of course, it doesn't make sense because if there was moderation it would=
 be
> on the address and not the "person" since I can post via gmail.com.
>
> If not the case, trying to provide the benefit of doubt and seeking a
> logical reason for it, I figured the IETF list/MTA software is using some
> custom outbound queuing/scheduling logic with a higher preference for ema=
il
> domain volume, i.e. gmail.com at the top and individual domain accounts l=
ast
> in its scheduling logic. =A0Since gmail.com is a popular account used by =
many
> in this list, maybe that would explain why the MTA sending this out faste=
r
> than others. I offered this logical out reason to the list admin and he
> wasn't sure of the legacy software queuing logic.
>
> Anyway, just trying to figure out why the delays since I can stick with m=
y
> real account and not the gmail.com junk account.
>
> Thanks
>
> --
> HLS

From hannes.tschofenig@nsn.com  Sat May  5 21:12:30 2012
Return-Path: <hannes.tschofenig@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 F2BFC21F84D1 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 21:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.142
X-Spam-Level: 
X-Spam-Status: No, score=-106.142 tagged_above=-999 required=5 tests=[AWL=0.457, 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 MZW0guaQSjd0 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 21:12:30 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE0821F84FB for <ietf@ietf.org>; Sat,  5 May 2012 21:12:29 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q463rMtt014786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 6 May 2012 05:53:23 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q463rM8p024179; Sun, 6 May 2012 05:53:22 +0200
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 6 May 2012 05:53:22 +0200
Received: from 10.144.240.63 ([10.144.240.63]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Sun,  6 May 2012 03:53:21 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Sun, 06 May 2012 06:51:45 +0300
Subject: Re: Is the IETF aging?
From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
To: "ext Kevin P. Fleming" <kpfleming@digium.com>, <ietf@ietf.org>
Message-ID: <CBCBD001.32D8%hannes.tschofenig@nsn.com>
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0rO44OCRrd2ALIh0CIhHDxMv+mOg==
In-Reply-To: <4FA189FB.6040909@digium.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 06 May 2012 03:53:22.0676 (UTC) FILETIME=[C846CB40:01CD2B3B]
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: 339
X-purgate-ID: 151667::1336276403-00001F01-3BD6A381/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: Sun, 06 May 2012 04:12:31 -0000

> As a counter-point (which supports your position <G>) the creation of
> the CODEC WG has actually brought a number of people/companies into
> active IETF involvement that were likely never involved before.

Right. 

Whether that working group also attracted the type of people PHB or others
want is something I cannot judge.



From sant9442@gmail.com  Sat May  5 22:15:34 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3728021F84D6 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 22:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, MANGLED_LOOK=2.3, 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 dJLAEVO3aTEk for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 22:15:31 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8487421F84D5 for <ietf@ietf.org>; Sat,  5 May 2012 22:15:31 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4346851yhq.31 for <ietf@ietf.org>; Sat, 05 May 2012 22:15: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=Emjr97fZWtvDxn0UcwwtaWI4IKw5ChEvbnrzZ2nxVmY=; b=yfWt4zKOEwBRjIPlnSO+q/Q8ygkBOxfh08AKXFYEduPOZ5dYwfbG6K+wlsUxn4lt4K WpXDsyV7pQ1P6gBzYs0QbH4Locq+26/7Cnx+pw5O1VUPHleiLDhz62hvdwPzSsjof4Yk 9xQF0/8uSv/OuaQ15ZTI3kC49xUkZTZdJxxiJI0gk9J4XgYizIIgMLX0vT1qqtClOgI4 eu80KyWUs88Euu9KiTOesfEOy/uUHJ5n54/9/0zN1gpDMUvOO51OZlHn0sm+xe9BXtOZ pglOcFeVug49ZF2SRyhpg7w4nSjUklJrl+9bXhr+UIBe2fBuWzybH2wTS2t3q9wJA/QY OPtw==
Received: by 10.236.75.234 with SMTP id z70mr14789899yhd.5.1336281330922; Sat, 05 May 2012 22:15:30 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id f40sm21439205ani.16.2012.05.05.22.15.22 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 May 2012 22:15:29 -0700 (PDT)
Message-ID: <4FA60919.9000403@gmail.com>
Date: Sun, 06 May 2012 01:16:09 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: IETF posting delays
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com>
In-Reply-To: <m2vckac9rq.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 05:15:34 -0000

Randy Bush wrote:
>> When I first begin to take notice a while back and last year I decided 
>> to ask the list admin.  He replied shortly and indicated there was no 
>> moderation. I also asked a few IETF veterans, a WG chair and AD, and 
>> they all repeated there was no moderation going on.
>>
>> But I believe I read an IETF person in the list explained delays was 
>> mostly due to moderation. If so, while I don't see any reason for it, 
>> I was never given any notice my email would be moderated and I would 
>> like to ask why my email is being moderated?
> 
> i know of no moderated lists.  but, instead of conjecturbation, let's
> debug the problem.  please show the Received: and other header lines of
> a message posted from your work address.  or just post one now and we
> can see it for ourselves.  thanks.
> 

Thanks Randy, I asked because I had replied to the last J. Klensin and 
M. Banks  exchange (Re: Is the IETF aging?) with my 
hsantos@santronics.com account and it has yet to be posted.

These are the MUA creation sent headers and payload as shown my my MUA 
and below this is my MSA/MTA server SMTP session trace showing the 
transport to the list:

           ------------ CUT HERE ----------
Message-ID: <4FA58B0C.1010803@santronics.com>
Date: Sat, 05 May 2012 16:18:20 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Is the IETF aging?
References: 
<CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>	<0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net> 
<CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com> 
<CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
In-Reply-To: 
<CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Marshall Eubanks wrote:

>> True, but that does not mean that you should decide that there is
>> nothing the IETF can do to change those characteristics or is in fact
>> doing albeit unintentionally.
> 
> So, what would you do to adjust things ?
> 
> Regards
> Marshall

Some suggestions:

   - Increase IETF brand awareness
     - Leverage the IETF Brand
     - FaceBook page
     - Twitter account
     - Better On-line Access/Participation
     - Forums based communications
        - Offer personalization profiling
           - Photos, etc, "face behind name"
     - IETF "Radio"

   - Encourage elders, veterans Mentoring
       - ID, RFC development
          - Discourage "Use Usual Editors" mindset
       - Consider "PWG "Preliminary Working Groups" to sense full WG
          - Often decision left to the certain few (high barrier)

      on an indirect but I believe part of the improving IETF
      brand and image:

      - Serious review of "Rough Consensus" process
         - Technical Advisors need to get involved earlier

   - Leverage Assets
       - RFC format as a Tech Writing model for Engineering Students
       - Professional Trade member/certification "badge"
       - IETF membership subscriptions
          - Discounts

   - Seek more academia, industry, govt joint ventures
       - Summer "IETF" Internship
       - Start up, grants
       - Resource site

   - Assistance, Awareness with Legal, IP issues (international, etc)

   - Personally, increase the quality of work, minimize the "Fix it
     later" mindset - major turn off for young people IMV.

And perhaps, hire a PR, technical sales consultant who knows the
subtleties of what comes first; Marketing or Technology.

-- 
Sincerely

Hector Santos
http://www.santronics.com
jabber: hector@jabber.isdg.net
           ------------ CUT HERE ----------

And the following is my host MTA output smtp session trace to the 
list. You can see the MUA to MSA and router MTA send off time diff 
only by 12-13 secs. The message has not been list processed yet as of 
this post (or I have not received it yet by my host).

               ------- CUT HERE ---------
**************************************************************************
Wildcat! ESMTP Server v6.4.454.1
SMTP log started at Sat, 05 May 2012  16:18:31
Connection Time: 20120505 16:18:31  cid: 00000000 tid: 1540
SSL Enabled: YES
Message Queue: d:\spool\santronics\smtp\22516W
Destination: ietf@ietf.org
Mail Host IP: 12.22.58.30:25 (mail.ietf.org)
Attempt #1 LastAttempt: n/a
16:18:31.058 (1540.0075260) ** Opening Connection to host: 
mail.ietf.org ip: 12.22.58.30:25
16:18:31.916 (1540.0075260) S: 220 ietfa.amsl.com ESMTP Postfix
16:18:31.916 (1540.0075260) C: EHLO dkim.winserver.com
16:18:32.010 (1540.0075260) S: 250-ietfa.amsl.com
16:18:32.010 (1540.0075260) S: 250-PIPELINING
16:18:32.010 (1540.0075260) S: 250-SIZE 67108864
16:18:32.010 (1540.0075260) S: 250-ETRN
16:18:32.010 (1540.0075260) S: 250-AUTH LOGIN PLAIN
16:18:32.010 (1540.0075260) S: 250-AUTH=LOGIN PLAIN
16:18:32.010 (1540.0075260) S: 250-ENHANCEDSTATUSCODES
16:18:32.010 (1540.0075260) S: 250-8BITMIME
16:18:32.010 (1540.0075260) S: 250 DSN
16:18:32.010 (1540.0075260) C: MAIL FROM:<hsantos@santronics.com>
16:18:32.088 (1540.0075260) S: 250 2.1.0 Ok
16:18:32.088 (1540.0075260) C: RCPT TO:<ietf@ietf.org>
16:18:33.180 (1540.0075260) S: 250 2.1.5 Ok
16:18:33.180 (1540.0075260) C: DATA
16:18:33.258 (1540.0075260) S: 354 End data with <CR><LF>.<CR><LF>
16:18:33.461 (1540.0075260) S: 250 2.0.0 Ok: queued as 20B0821F85FF
16:18:33.461 (1540.0075260) C: QUIT
16:18:33.555 (1540.0075260) S: 221 2.0.0 Bye
16:18:33.555 (1540.0075260) ** Completed. Elapsed Time: 2543 msecs
               ------- CUT HERE ---------


Thanks for your interest


--
HLS

From brian.e.carpenter@gmail.com  Sun May  6 00:07:56 2012
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 CE42821F849D for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 00:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.561
X-Spam-Level: 
X-Spam-Status: No, score=-101.561 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 WddbgQwLJKsU for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 00:07:56 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id BF2F621F849A for <ietf@ietf.org>; Sun,  6 May 2012 00:07:55 -0700 (PDT)
Received: by wibhm4 with SMTP id hm4so1921424wib.1 for <ietf@ietf.org>; Sun, 06 May 2012 00:07: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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7f3nAqM2Oa7z/aPkJMj/pGMGNzg0xCO1K1sRe+TdyhM=; b=mRD0SdbHnOf78C0dednyT8sNO/bWEhTJbkefBqGYdKf7o7jZcIFu8LSxwJlrtqBf78 cohz+h8AXeQaBQ2t61V+8mIeYPs2x8v3QHQGPoGq5g2/IOmOlObXRWnQKVO3kkifj289 mv/PcFiCp4N2tgqkHbA6pvh8U6m8N2HjAaE5xzd3hPQ+ylf3cpZJld5IhES271mah1a0 BDc7N0yZi3e1VCCW7OQwA3ECv+JVSuVIVLKQUis0vEo+syzBdZQsxM0KNDPHpuUlWLlt ESRRadEVP5OqeFhW/Mnq6+en8+x7xScKuhVHFJLxjL7CgnqhJK+u9dClu2Y37mIF5dkO IkUg==
Received: by 10.180.24.66 with SMTP id s2mr16094038wif.7.1336288074974; Sun, 06 May 2012 00:07:54 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-144.as13285.net. [2.102.217.144]) by mx.google.com with ESMTPS id ex2sm18324918wib.8.2012.05.06.00.07.52 (version=SSLv3 cipher=OTHER); Sun, 06 May 2012 00:07:53 -0700 (PDT)
Message-ID: <4FA6232C.6020800@gmail.com>
Date: Sun, 06 May 2012 08:07:24 +0100
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 Mailing List <ietf@ietf.org>
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>	<0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>	<CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com>	<CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com> <E23229AB-6B85-4D17-87C1-6C5D8CF721CE@checkpoint.com>
In-Reply-To: <E23229AB-6B85-4D17-87C1-6C5D8CF721CE@checkpoint.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 07:07:56 -0000

On 2012-05-05 04:48, Yoav Nir wrote:
...
> an obvious idea would be to change the requirements for a new work item from "rough consensus" to "a bunch of people willing to do the work and at least one willing to implement".  Some working groups already work like this, but it's not universal.

There's nothing to stop a group of people developing a specification
as an I-D and prototyping it. They don't need a WG or a BOF or a
sponsoring AD.

The barrier for spending collective resources (WG time, AD time, RFC
Editor time, IANA time) on it should be real, IMHO.

On 2012-05-06 04:52, Hannes Tschofenig wrote:
...
> My point is that you will not find interest from young engineers to work on
> 10 year old topics. You can try it yourself: give a talk at a university and
> see the reaction from the students. Pick a lower-layer topic and a topic
> from the application layer (some Web stuff).

It's true. But the fact is that as in any major technical system, neglect
of the infrastructure is a very bad idea. Just consider what happens to
a city if it ignores the sewers and water pipes. Sorry to say that the
IETF (and the operators who read RFCs) are in the same position as
municipal utilities. It's hard to get students interested in sanitary
engineering.

   Brian

From chair@ietf.org  Sun May  6 09:46:20 2012
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 3733621F8454 for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 09:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkJo7t46hhzC for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 09:46:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id D8A2521F844E for <ietf@ietf.org>; Sun,  6 May 2012 09:46:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D757E12C7AE for <ietf@ietf.org>; Sun,  6 May 2012 09:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjGWijLZTvIY for <ietf@ietf.org>; Sun,  6 May 2012 09:46:19 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) by c8a.amsl.com (Postfix) with ESMTPSA id 940C912C7A9 for <ietf@ietf.org>; Sun,  6 May 2012 09:46:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Future Handling of Blue Sheets
From: IETF Chair <chair@ietf.org>
In-Reply-To: <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu>
Date: Sun, 6 May 2012 12:46:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 16:46:20 -0000

We have heard from many community participants, and consensus is quite =
rough on this topic.  The IESG discussed this thread and reached two =
conclusions:

(1) Rough consensus: an open and transparent standards process is more =
important to the IETF than privacy of blue sheet information.

(2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.


Based on these conclusions, the plan is to handle blue sheets as =
follows:

  - Continue to collect email addresses on blue sheets;

  - Scan the blue sheet and include the image in the proceedings for the =
WG session;

  - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and

  - Discard paper blue sheets after scanning.


On behalf of the IESG,
  Russ


From dougb@dougbarton.us  Sun May  6 15:07:26 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC4C621F855F for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 15:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.788
X-Spam-Level: 
X-Spam-Status: No, score=-1.788 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_40=-0.185, 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 VkdQQTqzRTPZ for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 15:07:26 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D6B2C21F854D for <ietf@ietf.org>; Sun,  6 May 2012 15:07:25 -0700 (PDT)
Received: (qmail 14109 invoked by uid 399); 6 May 2012 22:07:17 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 6 May 2012 22:07:17 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4FA6F614.3040601@dougbarton.us>
Date: Sun, 06 May 2012 15:07:16 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
In-Reply-To: <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
X-Enigmail-Version: 1.5pre
OpenPGP: id=1A1ABC84
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: Sun, 06 May 2012 22:07:27 -0000

On 05/06/2012 09:46, IETF Chair wrote:
>   - Discard paper blue sheets after scanning.

Everything else seems fine, but I'm concerned about this one. Have you
run this idea past some sort of legal counsel who is knowledgeable about
intellectual property litigation? If so, no worries.

Doug

-- 
    If you're never wrong, you're not trying hard enough

From housley@vigilsec.com  Sun May  6 15:54:05 2012
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 3295221F854F for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 15:54: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 oe1dNQV1AxZa for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 15:54:04 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B019021F854E for <ietf@ietf.org>; Sun,  6 May 2012 15:54:04 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 5689A9A471B; Sun,  6 May 2012 18:54:17 -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 R8sEEQFfbJ+N; Sun,  6 May 2012 18:54:03 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B84E59A470F; Sun,  6 May 2012 18:54:16 -0400 (EDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FA6F614.3040601@dougbarton.us>
Date: Sun, 6 May 2012 18:54:03 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <D0C6D69F-930A-4B66-B1DB-B264860D961B@vigilsec.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <4FA6F614.3040601@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
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: Sun, 06 May 2012 22:54:05 -0000

Doug:

>>  - Discard paper blue sheets after scanning.
> 
> Everything else seems fine, but I'm concerned about this one. Have you
> run this idea past some sort of legal counsel who is knowledgeable about
> intellectual property litigation? If so, no worries.

The IETF Counsel has been consulted, and he sees no trouble in this regard.

Russ

From dwm@xpasc.com  Sun May  6 16:03:51 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EC821F8512; Sun,  6 May 2012 16:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[AWL=-1.600, 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 q6VDMvcUDq91; Sun,  6 May 2012 16:03:50 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id B2FD921F8467; Sun,  6 May 2012 16:03:50 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 4D4913FA24; Sun,  6 May 2012 23:03:50 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q46N3nDE011979; Sun, 6 May 2012 16:03:49 -0700
Date: Sun, 6 May 2012 16:03:49 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
Message-ID: <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD7Hu1vr-461603o
X-CLX-Spam: false
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: Sun, 06 May 2012 23:03:51 -0000

>From my following of the topic, that concensus was really rough, in 
particular the part about publishing the scans on-line. That represents
a significant difference in ease access which I think required more than
the very very rough concensus you seem to think you found.

On Sun, 6 May 2012, IETF Chair wrote:

> We have heard from many community participants, and consensus is quite rough on this topic.  The IESG discussed this thread and reached two conclusions:
> 
> (1) Rough consensus: an open and transparent standards process is more important to the IETF than privacy of blue sheet information.
> 
> (2) Rough consensus: inclusion of email addresses is a good way to distinguish participants with the same or similar names.
> 
> 
> Based on these conclusions, the plan is to handle blue sheets as follows:
> 
>   - Continue to collect email addresses on blue sheets;
> 
>   - Scan the blue sheet and include the image in the proceedings for the WG session;
> 
>   - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
> 
>   - Discard paper blue sheets after scanning.
> 
> 
> On behalf of the IESG,
>   Russ
> 
> 

From hsantos@isdg.net  Sun May  6 17:09:36 2012
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 18A7621F856A for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 17:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level: 
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=0.339,  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 Lv9yflcHyadK for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 17:09:35 -0700 (PDT)
Received: from news.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 89DC821F854C for <ietf@ietf.org>; Sun,  6 May 2012 17:09:33 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3957; t=1336349363; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=P08CwULplyzg60xoVj865PxIpAs=; b=DePXxn+bviptBje2j+f8 yQ5gSQL0kGUXjP8/0VahiJj/doru63OhaLpZj63qRQS5LWc48+Q5NH499r/1Kc/H cYSRmMC+A6kt9+JqCToc16+LR9e2dtFEh9odLqtJafbwrB1U+38vw9hYxmmE6mSs LA0LNk8GBcE0Jy3YZAAoYqM=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 06 May 2012 20:09:23 -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 v6.4.454.1) with ESMTP id 961200431.49781.6080; Sun, 06 May 2012 20:09:22 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3957; t=1336349000; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=hdEgXcg TZ8FXbwwxG1YCYcf411eS/VHFXeqPFC8HnUI=; b=18o6E4QQ3tvHyaz7UGPzxrE 0fpQffUOYFbfqrLZqf977XtG5eC7dIy97FwUWk1jnSfl0Uf2nNjknSrixeW7YQtI rbiFr5N83tcRDDZhiBHLTfdJ5+PlCLrp0Sewb+O5JR+iT7+iaV6+wsNG/+3ujKDP FWHq7OddrYyME78uMxzE=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 06 May 2012 20:03:20 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1560088425.5448.4700; Sun, 06 May 2012 20:03:19 -0400
Message-ID: <4FA7129D.4010006@isdg.net>
Date: Sun, 06 May 2012 20:09:01 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF posting delays
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com>
In-Reply-To: <4FA60919.9000403@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 00:09:36 -0000

Please pardon this submission processing test using a different account.

--
Hector Santos, CTO
http://www.santronics.com
http://hector.wildcatblog.com

Hector wrote:
> Randy Bush wrote:
>>> When I first begin to take notice a while back and last year I 
>>> decided to ask the list admin.  He replied shortly and indicated 
>>> there was no moderation. I also asked a few IETF veterans, a WG chair 
>>> and AD, and they all repeated there was no moderation going on.
>>>
>>> But I believe I read an IETF person in the list explained delays was 
>>> mostly due to moderation. If so, while I don't see any reason for it, 
>>> I was never given any notice my email would be moderated and I would 
>>> like to ask why my email is being moderated?
>>
>> i know of no moderated lists.  but, instead of conjecturbation, let's
>> debug the problem.  please show the Received: and other header lines of
>> a message posted from your work address.  or just post one now and we
>> can see it for ourselves.  thanks.
>>
> 
> Thanks Randy, I asked because I had replied to the last J. Klensin and 
> M. Banks  exchange (Re: Is the IETF aging?) with my 
> hsantos@santronics.com account and it has yet to be posted.
> 
> These are the MUA creation sent headers and payload as shown my my MUA 
> and below this is my MSA/MTA server SMTP session trace showing the 
> transport to the list:
> 
>           ------------ CUT HERE ----------
> Message-ID: <4FA58B0C.1010803@santronics.com>
> Date: Sat, 05 May 2012 16:18:20 -0400
> From: Hector Santos <hsantos@santronics.com>
> Organization: Santronics Software, Inc.
> User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
> MIME-Version: 1.0
> To: Marshall Eubanks <marshall.eubanks@gmail.com>
> CC: IETF Discussion Mailing List <ietf@ietf.org>
> Subject: Re: Is the IETF aging?
> References: 
> <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>    
> <0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net> 
> <CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com> 
> <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
> In-Reply-To: 
> <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> Marshall Eubanks wrote:
> 
>>> True, but that does not mean that you should decide that there is
>>> nothing the IETF can do to change those characteristics or is in fact
>>> doing albeit unintentionally.
>>
>> So, what would you do to adjust things ?
>>
>> Regards
>> Marshall
> 
> Some suggestions:
> 
>   - Increase IETF brand awareness
>     - Leverage the IETF Brand
>     - FaceBook page
>     - Twitter account
>     - Better On-line Access/Participation
>     - Forums based communications
>        - Offer personalization profiling
>           - Photos, etc, "face behind name"
>     - IETF "Radio"
> 
>   - Encourage elders, veterans Mentoring
>       - ID, RFC development
>          - Discourage "Use Usual Editors" mindset
>       - Consider "PWG "Preliminary Working Groups" to sense full WG
>          - Often decision left to the certain few (high barrier)
> 
>      on an indirect but I believe part of the improving IETF
>      brand and image:
> 
>      - Serious review of "Rough Consensus" process
>         - Technical Advisors need to get involved earlier
> 
>   - Leverage Assets
>       - RFC format as a Tech Writing model for Engineering Students
>       - Professional Trade member/certification "badge"
>       - IETF membership subscriptions
>          - Discounts
> 
>   - Seek more academia, industry, govt joint ventures
>       - Summer "IETF" Internship
>       - Start up, grants
>       - Resource site
> 
>   - Assistance, Awareness with Legal, IP issues (international, etc)
> 
>   - Personally, increase the quality of work, minimize the "Fix it
>     later" mindset - major turn off for young people IMV.
> 
> And perhaps, hire a PR, technical sales consultant who knows the
> subtleties of what comes first; Marketing or Technology.
> 





From chair@ietf.org  Sun May  6 18:26:08 2012
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 C316121F841B for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 18:26: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=[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 KsIOi-9R13zI for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 18:26:08 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 36FEA21F8419 for <ietf@ietf.org>; Sun,  6 May 2012 18:26:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7768212C7CE; Sun,  6 May 2012 18:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdruGRYBLRLa; Sun,  6 May 2012 18:26:01 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) by c8a.amsl.com (Postfix) with ESMTPSA id F3DBC12C7CB; Sun,  6 May 2012 18:26:00 -0700 (PDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com>
Date: Sun, 6 May 2012 21:26:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
X-Mailer: Apple Mail (2.1084)
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 May 2012 01:26:09 -0000

David:

The list of participants and their addresses are already part of the =
proceedings.  The incremental difference shows which participants signed =
in at each session.

Russ



On May 6, 2012, at 7:03 PM, David Morris wrote:

>=20
> =46rom my following of the topic, that concensus was really rough, in=20=

> particular the part about publishing the scans on-line. That =
represents
> a significant difference in ease access which I think required more =
than
> the very very rough concensus you seem to think you found.
>=20
> On Sun, 6 May 2012, IETF Chair wrote:
>=20
>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>=20
>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>=20
>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>=20
>>=20
>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>=20
>>  - Continue to collect email addresses on blue sheets;
>>=20
>>  - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>=20
>>  - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>=20
>>  - Discard paper blue sheets after scanning.
>>=20
>>=20
>> On behalf of the IESG,
>>  Russ
>>=20
>>=20
>=20


From randy@psg.com  Sun May  6 18:41:48 2012
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 DE80321F84E2 for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 18:41: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 iasA7mP-SPO9 for <ietf@ietfa.amsl.com>; Sun,  6 May 2012 18:41:48 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD7921F84DF for <ietf@ietf.org>; Sun,  6 May 2012 18:41:48 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SRCxN-0009tq-2p; Mon, 07 May 2012 01:41:45 +0000
Date: Sun, 06 May 2012 15:41:44 -1000
Message-ID: <m2y5p4aht3.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Hector Santos <hsantos@santronics.com>
Subject: Re: IETF posting delays
In-Reply-To: <4FA716D6.2050402@santronics.com>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.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.6 - "Maruoka")
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: Mon, 07 May 2012 01:41:49 -0000

indeed, the following line in your header was the clue.

X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700

this means you posted from an address not subscribed and it required
manual intervention.

randy

From dwm@xpasc.com  Sun May  6 19:04:04 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB0C21F8554; Sun,  6 May 2012 19:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-1.333, 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 mMjJ6AYWi3Tx; Sun,  6 May 2012 19:04:04 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 1735621F854E; Sun,  6 May 2012 19:04:04 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id D3C0440416; Mon,  7 May 2012 02:04:03 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q47242SX013132; Sun, 6 May 2012 19:04:03 -0700
Date: Sun, 6 May 2012 19:04:02 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org>
Message-ID: <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD7Hu1vr-4619043
X-CLX-Spam: false
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 May 2012 02:04:04 -0000

I consider that there is a significant difference between the information 
provided in the registered attendee list and the individual blue sheets:

a) to the extent that the information on the blue sheet is valid, it 
provides an hour by hour log of location, the overall list of attendees at 
most indicates an individual was present to pick up their badge at some
point during the meeting.
b) the validity of the list of registered attendees has a higher degree
of probable validity because of the requirement for a significant payment
and the processes required to process that payment.
c) Individual blue sheets can suffer from any number of unintentional and
intentional issues which limit their factual validity but not the mischief
which can be caused by their easy online access.
d) Scanning and publication imports a validity to the data which is not
widely accepted by the community.

David Morris

On Sun, 6 May 2012, IETF Chair wrote:

> David:
> 
> The list of participants and their addresses are already part of the proceedings.  The incremental difference shows which participants signed in at each session.
> 
> Russ
> 
> 
> 
> On May 6, 2012, at 7:03 PM, David Morris wrote:
> 
> > 
> > From my following of the topic, that concensus was really rough, in 
> > particular the part about publishing the scans on-line. That represents
> > a significant difference in ease access which I think required more than
> > the very very rough concensus you seem to think you found.
> > 
> > On Sun, 6 May 2012, IETF Chair wrote:
> > 
> >> We have heard from many community participants, and consensus is quite rough on this topic.  The IESG discussed this thread and reached two conclusions:
> >> 
> >> (1) Rough consensus: an open and transparent standards process is more important to the IETF than privacy of blue sheet information.
> >> 
> >> (2) Rough consensus: inclusion of email addresses is a good way to distinguish participants with the same or similar names.
> >> 
> >> 
> >> Based on these conclusions, the plan is to handle blue sheets as follows:
> >> 
> >>  - Continue to collect email addresses on blue sheets;
> >> 
> >>  - Scan the blue sheet and include the image in the proceedings for the WG session;
> >> 
> >>  - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
> >> 
> >>  - Discard paper blue sheets after scanning.
> >> 
> >> 
> >> On behalf of the IESG,
> >>  Russ
> >> 
> >> 
> > 
> 
> 

From jaap@NLnetLabs.nl  Mon May  7 01:25:09 2012
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 1AC3E21F84EF for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 01:25: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 pASe0IirlX4b for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 01:25:08 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by ietfa.amsl.com (Postfix) with ESMTP id 380CF21F84AA for <ietf@ietf.org>; Mon,  7 May 2012 01:25:07 -0700 (PDT)
Received: from NLnetLabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id q478P38h050921; Mon, 7 May 2012 10:25:04 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 bartok.nlnetlabs.nl q478P38h050921
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=sleutel; t=1336379105; bh=cQ5k6WuYHHc1aMMPr2w6AzbJmzL2cXeKytnWKr2KAW4=; h=To:cc:Subject:In-reply-to:References:Date:From; b=mlXVniCvvSIWMRCQxpXMFAX/C8sa16YS+WCaJXs2YkNYF5clfLkfjixMxeRtfeAJS RUtmpt7ARghnaJkxEPBfjB0F0Yypq8jP9OqJhPCH0cr3fF8EXIHb16MqcZOez8C84V 1hZ010ipsqMFKPSVqh01SI4uzvFMLVTxawNX5g78=
Message-Id: <201205070825.q478P38h050921@bartok.nlnetlabs.nl>
To: Randy Bush <randy@psg.com>
Subject: Re: IETF posting delays
In-reply-to: <m2y5p4aht3.wl%randy@psg.com>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com>
Comments: In-reply-to Randy Bush <randy@psg.com> message dated "Sun, 06 May 2012 15:41:44 -1000."
Date: Mon, 07 May 2012 10:25:03 +0200
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bartok.nlnetlabs.nl [127.0.0.1]); Mon, 07 May 2012 10:25:04 +0200 (CEST)
Cc: Hector Santos <hsantos@santronics.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: Mon, 07 May 2012 08:25:09 -0000

    indeed, the following line in your header was the clue.
    X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700

That is interesting, I didn't had this line in the header. Strange.

	jaap



From randy@psg.com  Mon May  7 01:51:41 2012
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 E316C21F8567 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 01:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 2wFYU+Emg+p7 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 01:51:41 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E72F521F8494 for <ietf@ietf.org>; Mon,  7 May 2012 01:51:40 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SRJfP-000AcF-5J; Mon, 07 May 2012 08:51:39 +0000
Date: Sun, 06 May 2012 22:51:38 -1000
Message-ID: <m2txzs8jc5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Subject: Re: IETF posting delays
In-Reply-To: <201205070825.q478P38h050921@bartok.nlnetlabs.nl>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com> <201205070825.q478P38h050921@bartok.nlnetlabs.nl>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
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: Mon, 07 May 2012 08:51:42 -0000

>     indeed, the following line in your header was the clue.
>     X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700
> That is interesting, I didn't had this line in the header. Strange.

that is because you posted from the address which was subscribed so
needed no manual intervention.

From hsantos@isdg.net  Mon May  7 05:48:37 2012
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 AF4F521F85DD for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 05:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.714
X-Spam-Level: 
X-Spam-Status: No, score=-1.714 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 OX4KdqOuiKxv for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 05:48:36 -0700 (PDT)
Received: from winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9E77A21F84C5 for <ietf@ietf.org>; Mon,  7 May 2012 05:48:36 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3148; t=1336394915; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=PeZC5o9/pPDbZTV11Xo8mipiRBA=; b=qzxhkJZvARN+oAza6+Yq x9zKhGUowNMm4c0NJSZo2ywnCxobCdA6IVp0PeNZvfsFgQjvcmugarJPT0I1EkgP iwtiuTZfgn76rYLO8uJw8Th2LfxOdfuBXJEcODrvA0Dq9mim7qY7g6bHSELWHpfu OVkKrifzlla88jYlGk7FMzs=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 07 May 2012 08:48:35 -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 v6.4.454.1) with ESMTP id 1006751039.51127.1620; Mon, 07 May 2012 08:48:33 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3148; t=1336394908; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=xckGEEv PuOiGyu0907EJF2uX5ho3cVoFX9ASXSQnSXk=; b=m4ClcmVjvmACYy97xUgTsdl l1WLnWk5j1mMaQambxxvinZ8eQXyCbHYdfRVBxekNpHV+4Lktdisr0a1e5OsMZgl 7+fIenr+MO90E7h0jRjWDu9kLLSw1chZ0yQa0hi7160aHmh/8hB2BzAqgtDcwGsg 12y++l6SRwJJNQEl3SLo=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 07 May 2012 08:48:28 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1605641112.5547.5724; Mon, 07 May 2012 08:48:27 -0400
Message-ID: <4FA7C483.1060204@isdg.net>
Date: Mon, 07 May 2012 08:48:03 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF Disgust <ietf@ietf.org>
Subject: Re: IETF posting delays
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com>	<4FA60919.9000403@gmail.com>	<F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com>	<4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com>	<201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com>
In-Reply-To: <m2txzs8jc5.wl%randy@psg.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: Mon, 07 May 2012 12:48:37 -0000

Randy Bush wrote:
>>     indeed, the following line in your header was the clue.
>>     X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700
>> That is interesting, I didn't had this line in the header. Strange.
> 
> that is because you posted from the address which was subscribed so
> needed no manual intervention.

Question, did the IETF list setup disable the "non-member" email 
notifications?

I use to get these emails offering options to wait for moderator 
approval or click a URL to cancel the submission.  I have not seen 
these again for this IETF list.  The grief with the unknown delays and 
mistake postings would of been avoided.

I wonder if it was disabled since for this special IETF DISCUSS list 
there are times when I see an RFC editor or IESG reviewers want 
responses to include/keep the target addresses. If it includes 
non-member list addresses, then you begin to get the annoying 
non-member notifications.  So you either punt and don't provide input 
or you are presented with the undesired need to subscribe to the 
list(s) perhaps only temporarily to avoid the notifications and also 
avoid delays waiting for moderator approval and that may not even 
happen! Not pleasant to put time and energy in IETF participation and 
having to wonder what is going with postings delays.  Do you repost? 
Do you use another address? How long do you wait?  Should you bother 
people about this?

Anyway thought about this problem and created a possible Temporary Non 
Member White listing idea:

bool CheckMemberShip(
     char *pszList, // list name
     char *pszFrom, // poster address
     char *pszSubj  // message 5322.Subject
)

/*
    return true if pszFrom address is a member of pszList
    or is a returning non-member submission with the same list
    and same pszSubj (topic) allowing for an automated means
    to reduce delays, reduce hold mail queues and reduce
    the moderator work load without requiring the user to
    subscribe to a list he prefers not to join for a limited
    posting need.
*/

{
    // If the user is a list member, then return true
    // and continue with the list submission.

    if (IsListMember(pszList, pszFrom))
       return true;

    // Check for a returning non-member same topic post.
    // If missing, create conocalized hash for the list+from+topic
    // allowing temp authorization to post to the list under the
    // same topic in future submissions. return true if
    // the returning user is allowed to post without delay.

    if (CheckTempMemberHash(pszList,pszFrom,pszSubj))
       return true;

    // first time submission or different topic.
    // Create the non-member notification. When a poster
    // changes the subject line, will trigger a reset.

    CreateNonMemberNotification(pszList,pszFrom,pszSubj);

    // return false to move the submission to a hold
    // queue waiting for moderator approval

    return false;
}

Of course, other control factors are not shown, like a limited time 
window for expiring the temp member status.  I might just add this to 
our list server. :)

-- 
Hector Santos
http://www.santronics.com
http://hector.wildcatblog.com
jabber: hector@jabber.isdg.net



From hallam@gmail.com  Mon May  7 05:52:22 2012
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 8A97621F8567; Mon,  7 May 2012 05:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.122
X-Spam-Level: 
X-Spam-Status: No, score=-3.122 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3, 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 Fnpym6T7f4gb; Mon,  7 May 2012 05:52:20 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDD021F84FD; Mon,  7 May 2012 05:52:19 -0700 (PDT)
Received: by yenq13 with SMTP id q13so382280yen.31 for <multiple recipients>; Mon, 07 May 2012 05:52: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:content-transfer-encoding; bh=h/POpsZdxhIPWhmrROjywBhd64y2YyR/oG/A3ofh5ZE=; b=jBoqT71dN6WKZo03CaqvQX3JCP6VqKV/u1h5te6lQOWGreHdoOfrGfAMGwYdbFREE0 /QypZg8cOre/GWUm7U/LUvzNQ1SSDzeJFjedQZx9Oobz1H93hEs7XLxEAOaL0hpvE06E 7PHpyuJ+XmLQ9z9Pr6Iewp1gMTxmZN9ZM6NKtC5LpRkeFuxeZhveFaI/nA0Gkrdygztm MIc64VkrEq3a0yw38JfqwDJPM+UGZk5aVF83T9abLiAU0roXiCKGO6Ass4V4XVqlcgE1 Jr6zXrazLwnNnXPIQXQB5p0tm8REdzoPBlNXtP7MD5JE1G6jvs15t9jolB8wak3JaP/w TGtw==
MIME-Version: 1.0
Received: by 10.60.32.204 with SMTP id l12mr15424776oei.47.1336395138962; Mon, 07 May 2012 05:52:18 -0700 (PDT)
Received: by 10.182.41.165 with HTTP; Mon, 7 May 2012 05:52:18 -0700 (PDT)
In-Reply-To: <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz>
References: <01OE8FJG30ZM00ZUIL@mauve.mrochek.com> <201204130359.q3D3xlG0007556@fs4113.wdf.sap.corp> <01OE9150IMNI00ZUIL@mauve.mrochek.com> <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com> <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz>
Date: Mon, 7 May 2012 08:52:18 -0400
Message-ID: <CAMm+Lwg4J-XDMdC1CMycm2FA4-Of-0Ee-u2VW3hqtUDY3+VZ5g@mail.gmail.com>
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based
From: Phillip Hallam-Baker <hallam@gmail.com>
To: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej.sury@nic.cz>
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 12:52:22 -0000

So far I don't see any interest in production deployment other than
our own plans so I don't think your working group consensus has
relevance.

The point I am making applies to all forms of security policy, not
just DANE. If the party enforcing a security policy is not the same as
the party asserting it, the party enforcing that policy can and will
treat it as advice.

The big problem with all security policy mechanisms is that the policy
records have to be maintained separately from the system being
administered. That will inevitably lead to incompatibilities between
the policy and the practice. Attempting to rely on raw, uncurated
security policy records is a certain recipe for failure.


You can try to order the policy enforcement point around in the
Request For Comments, but here the comment is going to be 'we don't
want to do that'.


On Thu, May 3, 2012 at 11:54 AM, Ond=F8ej Sur=FD <ondrej.sury@nic.cz> wrote=
:
> Phillip,
>
> I haven't seen any consensus for the change of the document, thus
> chairs think the document is fine as it is.
>
> Ondrej
>
> On 25. 4. 2012, at 15:52, Phillip Hallam-Baker wrote:
>
>> I have raised these comments in the WG numerous times, I am raising
>> them here as I do not believe that anyone is going to implement the
>> specification as currently described.
>>
>> As currently written, the specification attempts to mandate client
>> behavior when DANE records are encountered in ways that are outside
>> the scope of interoperability. While the objective of the authors is
>> to mandate certain behavior they consider necessary for security
>> reasons, what they end up doing is attempting to substitute their own
>> judgement for that of the security experts who advise the client
>> providers.
>>
>>
>> Client providers already ignore significant parts of the PKIX
>> specification because they do not meet their performance criteria. In
>> particular virtually all browsers treat inability to obtain OCSP
>> certificate status as being equivalent to 'good'. This is a terrible
>> security design, one that every CA would like to see change. But it is
>> also a fact that we have been trying to get this changed for ten years
>> without success.
>>
>> The browser providers do not hard fail on OCSP because doing so would
>> require them to wait for the OCSP response within the TLS handshake
>> and this is considered an unacceptable performance degradation. I do
>> not like this situation, but I can either play Canute and tell the
>> tide to turn or I can consider it to be a fact and try to work round
>> it.
>>
>>
>> DANE attempts to fix PKI with another mandate that is certain to be
>> ignored. In this case the mandate is to establish a critical
>> dependency on the DNSSEC trust chain despite the easily observed fact
>> that less than 97% of DNS resolvers will pass anything other than
>> A/AAAA and CNAME records.
>>
>> Section 4 of the draft mandates a client hardfail if the DNSSEC trust
>> chain cannot be obtained. This is essential if the client is going to
>> use DNSSEC to establish certificate constraints just as certificate
>> revocation is an essential part of the PKIX model. But no browser
>> provider can expect to succeed with a product that simply stops
>> working when the user tries to surf the Web from a coffee shop.
>>
>> Since the coffee shop problem is not intentional we might imagine that
>> it will eventually go away. But this puts DANE in a deployment
>> deadlock bind. Nobody is going to fix their coffee shop routers until
>> there is a need to and that need won't exist until the coffee shop
>> routers are fixed.
>>
>> It is not just coffee shops that are the problem either. It might seem
>> really easy to put an SSL cert on a server and keep it up to date but
>> IETF participants represent the 1% of network admins. We all know from
>> experience how successful protocols that require two sets of records
>> to be kept in sync are. A protocol that requires a network admin to
>> remember to update their DNS with each cert change or suffer a
>> hardfail is going to have a very high administrative error rate.
>>
>>
>> Rather than mandating hardfail or any particular client behavior, the
>> specification should simply state that the client MUST conclude that
>> the DANE status of the certificate is invalid and then leave the
>> client to decide on what course of action to take. This will depend on
>> the circumstances of the particular user and the client provider's
>> assessment of the reliability of the DANE data and might range from do
>> nothing to send a security policy violation notification somewhere to
>> hardfail.
>>
>>
>> Contrary to the assumptions of the specification authors, hard fail is
>> not the best option. It is not even the best option in the case that
>> the users are dissidents.
>>
>> To understand the logic of the dissident case it is important to have
>> a change of perspective. The objective of the authorities is not to
>> intimidate a single protester, it is to intimidate a whole country.
>> Being a protester carries inevitable risks. No security protocol is
>> going to eliminate those risks for the individual. What is important
>> is to minimize the risk for the population as a whole.
>>
>> The Google cert pinning code did not provide much direct protection to
>> the Iranian dissidents because it only covered one site. But it proved
>> critical in exposing the Diginotar situation because it provided the
>> first evidence of the breach. Had the client been designed slightly
>> differently the breach might have become evident earlier.
>>
>>
>> The coffee shop issue is unintended but there are also parties that
>> are going to intentionally sabotage any infrastructure that looks like
>> DANE. We are not in the 1990s any longer, people in authority no
>> longer expect OSI to replace the Internet. The result is that it is
>> much harder to get away with no infrastructure. At present there is no
>> point in blocking DNSSEC records. But you can be sure that Iran,
>> Russia and China will be doing so the minute any client started to
>> make use of DANE. These countries can (and will) make use of a client
>> hard fail to ensure that people don't use browsers that might be used
>> for 'information terrorism' or freedom of speech as the rest of us
>> call it.
>>
>> And don't think that out own governments necessarily mean what they
>> say. In public Thatcher was a stalwart champion of freedom. In private
>> she was begging Gorbachev to send in the tanks to stop the fall of the
>> Berlin wall. Her own foundation has materials that report this
>> exchange:
>>
>> http://www.margaretthatcher.org/document/112006
>>
>> The last thing I want to do is to hand the authorities another tool
>> that can be used to selectively shut down the network at the critical
>> moment in a crisis. Completely shutting off the Internet is one thing,
>> it probably worked in our favor in Egypt as the 101st keyboarders lost
>> their Internet connection and were forced to find out what was going
>> on in the streets. It was a visceral sign of panic on the part of the
>> regime.
>>
>>
>> DANE is really a form of security policy information and so far there
>> is no case where we have succeeded in applying raw security policy
>> information at the client end. DKIM policies are a success because
>> they are filtered and interpreted by the anti-spam services. There is
>> a huge infrastructure in place that is working to apply the data from
>> the DKIM records intelligently and equally importantly provides
>> feedback to publishers of inconsistent records.
>>
>> DANE is proposed on the basis of a mistaken interpretation of how DKIM
>> security policies work in practice and the result is a protocol that
>> is deeply flawed and likely to fail.
>>
>> It would be a pity if the lack of success of a group that has
>> steadfastly worked to ignore and discourage outside advice became a
>> precedent to avoid future security policy efforts. Security policy is
>> a very powerful tool, one that we can and must use if we are going to
>> make the insecure Internet secure. But the DANE approach is too
>> dogmatic to succeed.
>> _______________________________________________
>> dane mailing list
>> dane@ietf.org
>> https://www.ietf.org/mailman/listinfo/dane
>
> --
> =A0Ond=F8ej Sur=FD -- Chief Science Officer
> =A0-------------------------------------------
> =A0CZ.NIC, z.s.p.o. =A0 =A0-- =A0 =A0Laborato=F8e CZ.NIC
> =A0Americka 23, 120 00 Praha 2, Czech Republic
> =A0mailto:ondrej.sury@nic.cz =A0 =A0http://nic.cz/
> =A0tel:+420.222745110 =A0 =A0 =A0 fax:+420.222745112
> =A0-------------------------------------------
>



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

From fred@cisco.com  Mon May  7 06:30:39 2012
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 0E28621F8618 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.602
X-Spam-Level: 
X-Spam-Status: No, score=-110.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 AvhbZymMCXKy for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:30:38 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 7785321F8615 for <ietf@ietf.org>; Mon,  7 May 2012 06:30:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=568; q=dns/txt; s=iport; t=1336397438; x=1337607038; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=EQSaoS5vf0tK0Xko4myxsNShJSn9n9eE/gPnDmo5M44=; b=ccX4Vb0AcAyCy5OUymommLXxaflr6LJ1hHGDKW+cTXwUa0grfldEydAO lYTHgUO6v9agcOnOwhsd0kuI4EiuWZpfY+qTUu3KipHUQywTxcPHYpw/K AMjgeX0M79L5LsSlu4IeFO4k0A1Q/iQUu6d+8AeRrxj/x5M0zI96PYJJz Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAHOp0+rRDoJ/2dsb2JhbABEr02DS4EHggwBAQEDARIBJzQLBQsLDgouVwY1h2cEmyKfRop/hT1jBIhkjRqFdohjgWmDB4FA
X-IronPort-AV: E=Sophos;i="4.75,543,1330905600"; d="scan'208";a="40678308"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 07 May 2012 13:30:38 +0000
Received: from Freds-Computer.local ([10.21.86.194]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q47DTnBk019948; Mon, 7 May 2012 13:30:37 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 07 May 2012 08:30:37 -0500
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 07 May 2012 08:30:37 -0500
Subject: Re: IETF posting delays
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4FA7C483.1060204@isdg.net>
Date: Mon, 7 May 2012 08:30:36 -0500
Message-Id: <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com>	<4FA60919.9000403@gmail.com>	<F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com>	<4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com>	<201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com> <4FA7C483.1060204@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 13:30:39 -0000

On May 7, 2012, at 7:48 AM, Hector Santos wrote:

> Randy Bush wrote:
>>>    indeed, the following line in your header was the clue.
>>>    X-Mailman-Approved-At: Wed, 02 May 2012 12:10:17 -0700
>>> That is interesting, I didn't had this line in the header. Strange.
>> that is because you posted from the address which was subscribed so
>> needed no manual intervention.
>=20
> Question, did the IETF list setup disable the "non-member" email =
notifications?

Spam reduction. We apply the rule to all of our mailing lists, and it is =
very helpful.=

From dhc@dcrocker.net  Mon May  7 06:42:55 2012
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 5DE2321F8649 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:42: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 UVfJLzzfkGgH for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:42:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EB24B21F863E for <ietf@ietf.org>; Mon,  7 May 2012 06:42:53 -0700 (PDT)
Received: from [172.16.35.88] ([38.100.136.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q47Dgpvf031834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 7 May 2012 06:42:52 -0700
Message-ID: <4FA7D153.1000702@dcrocker.net>
Date: Mon, 07 May 2012 09:42:43 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF Disgust <ietf@ietf.org>
Subject: Re: IETF posting delays
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com>	<4FA60919.9000403@gmail.com>	<F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com>	<4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com>	<201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com> <4FA7C483.1060204@isdg.net> <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com>
In-Reply-To: <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.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.17]); Mon, 07 May 2012 06:42: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, 07 May 2012 13:42:55 -0000

On 5/7/2012 9:30 AM, Fred Baker wrote:
>> Question, did the IETF list setup disable the "non-member" email notifications?
>
> Spam reduction. We apply the rule to all of our mailing lists, and it is very helpful.


Indeed, this is a common practice, especially for highly public and 
active mailing lists.

It saves traffic and it saves administrative effort.

Talking about it in an extended thread defeats both of these benefits...

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From cos@mip.polyamory.org  Mon May  7 06:45:23 2012
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B813121F8592 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.800,  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 GIGGjgEYIk8p for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:45:22 -0700 (PDT)
Received: from mip.polyamory.org (mip.polyamory.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 79F1621F8569 for <ietf@ietf.org>; Mon,  7 May 2012 06:45:22 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id BEE2110760; Mon,  7 May 2012 09:45:13 -0400 (EDT)
Date: Mon, 7 May 2012 09:45:13 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Fred Baker <fred@cisco.com>
Subject: Re: IETF posting delays
Message-ID: <20120507134513.GJ335@mip.aaaaa.org>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com> <201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com> <4FA7C483.1060204@isdg.net> <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 13:45:23 -0000

Fred Baker <fred@cisco.com> wrote:
> > Question, did the IETF list setup disable the "non-member" email notifications?
> 
> Spam reduction. We apply the rule to all of our mailing lists, and it is very helpful.

I don't think that's what Hector asked.

The question isn't "do we block email from non-members";
the question seems to be "we used to reply to the sender with a
notification that their message was blocked due to not being a
list member, with options to wait or cancel; did we disable those
notifications?"

At least that's how I read it.
  -- Cos

From dhc@dcrocker.net  Mon May  7 06:55:55 2012
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 05A9821F8655 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:55:54 -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 8apsxTMNbpdW for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:55:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E585D21F8658 for <ietf@ietf.org>; Mon,  7 May 2012 06:55:52 -0700 (PDT)
Received: from [172.16.35.88] ([38.100.136.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q47DtfAH032104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 7 May 2012 06:55:44 -0700
Message-ID: <4FA7D456.1090302@dcrocker.net>
Date: Mon, 07 May 2012 09:55:34 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ofer Inbar <cos@aaaaa.org>
Subject: Re: IETF posting delays
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com> <201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com> <4FA7C483.1060204@isdg.net> <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com> <20120507134513.GJ335@mip.aaaaa.org>
In-Reply-To: <20120507134513.GJ335@mip.aaaaa.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.17]); Mon, 07 May 2012 06:55:45 -0700 (PDT)
Cc: IETF Disgust <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 May 2012 13:55:55 -0000

On 5/7/2012 9:45 AM, Ofer Inbar wrote:
> Fred Baker<fred@cisco.com>  wrote:
>>> Question, did the IETF list setup disable the "non-member" email notifications?
>>
>> Spam reduction. We apply the rule to all of our mailing lists, and it is very helpful.
>
> I don't think that's what Hector asked.
>
> The question isn't "do we block email from non-members";
> the question seems to be "we used to reply to the sender with a
> notification that their message was blocked due to not being a
> list member, with options to wait or cancel; did we disable those
> notifications?"


And I took Fred's response as answering it.

Spam efforts exploit return address vectors.  This can make it 
problematic to send back failure notices.

It has become common for automated response mechanisms NOT to send a 
response, such as for a failed posting.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From johnl@iecc.com  Mon May  7 07:18:29 2012
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 4F23021F85E4 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 07:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.302
X-Spam-Level: 
X-Spam-Status: No, score=-110.302 tagged_above=-999 required=5 tests=[AWL=0.897, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ty6Q33VbV6-1 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 07:18: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 A78F621F85D4 for <ietf@ietf.org>; Mon,  7 May 2012 07:18:28 -0700 (PDT)
Received: (qmail 336 invoked from network); 7 May 2012 14:18:27 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 May 2012 14:18:27 -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:vbr-info; s=4fa7d9b2.xn--30v786c.k1205; i=johnl@user.iecc.com; bh=Zm4SMqmPFfASwPH70+nvAIwwFPuLPgVSnjGsiiLE0Kw=; b=NGLLHyBau3RPex6IQxQg4//d23n9HOMr3UwYer7vGIXhMtCH59zBHw/jEnbNdYybWuTQzXBY5w/5nrmZfMv6DnhuNeSXKcnNCQ67E915YPYr4XR33f+qS4ZnBflYyiOngLQ3Eq3hEhWInPXKjGUyxWPYBIC4+hj9SSD/uuJlKYM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 7 May 2012 14:18:04 -0000
Message-ID: <20120507141804.80865.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: IETF posting delays
In-Reply-To: <4FA7D456.1090302@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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, 07 May 2012 14:18:29 -0000

>> the question seems to be "we used to reply to the sender with a
>> notification that their message was blocked due to not being a
>> list member, with options to wait or cancel; did we disable those
>> notifications?"

I sure hope so.  These days about 99.9% of spam from unknown senders
is spam with forged addresses, so responses are just more spam aka
blowback.

There are networks that send me far more blowback than all the other
mail they send combined.

R's,
John

PS: Postini, we're talking to you.


From hsantos@santronics.com  Sat May  5 13:18:34 2012
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5043F21F8603 for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 13:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.039
X-Spam-Level: 
X-Spam-Status: No, score=-1.039 tagged_above=-999 required=5 tests=[AWL=-1.040, 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 YWo5kg0nKReY for <ietf@ietfa.amsl.com>; Sat,  5 May 2012 13:18:33 -0700 (PDT)
Received: from dkim.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 20B0821F85FF for <ietf@ietf.org>; Sat,  5 May 2012 13:18:32 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1700; t=1336249102; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=vNrl/IL BSdLWFnPqBsxzInQoKC0=; b=wcwzTlQ/84iiW0O8hCa1/hGn1u+E0JsNA85KA8D ZUAhLQqdki+sAFLD5XhpL+w1CMEo5er6Cer66KTaH8qg42dd6CUg9jARD+GVN1zG SVLabo0jrqWBHy3KMBpXBNWtKvCY5BqDt6yZh4ViMAvSxv5zKpCTpzqELdar05tH J5yk=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sat, 05 May 2012 16:18:22 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 860941069.48439.972; Sat, 05 May 2012 16:18:22 -0400
Message-ID: <4FA58B0C.1010803@santronics.com>
Date: Sat, 05 May 2012 16:18:20 -0400
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: Is the IETF aging?
References: <CAMm+Lwg23nd92CchxHh8br5ZM8JdiaUpKi4aj8asdSLz+i9dGA@mail.gmail.com>	<0CE35C09-274A-46B2-BFC6-28AEE45D2867@gmx.net>	<CAMm+Lwi8iOEnXxrj3-AaYVresops03LmasBs16FHk_1kaSX=Kg@mail.gmail.com> <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
In-Reply-To: <CAJNg7VK95in2XCPf2dG1f1-fNeUjzvnNqFY-FdJL4mDsU4+wxQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 07 May 2012 07:23:33 -0700
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, 05 May 2012 20:18:34 -0000

Marshall Eubanks wrote:

>> True, but that does not mean that you should decide that there is
>> nothing the IETF can do to change those characteristics or is in fact
>> doing albeit unintentionally.
> 
> So, what would you do to adjust things ?
> 
> Regards
> Marshall

Some suggestions:

  - Increase IETF brand awareness
    - Leverage the IETF Brand
    - FaceBook page
    - Twitter account
    - Better On-line Access/Participation
    - Forums based communications
       - Offer personalization profiling
          - Photos, etc, "face behind name"
    - IETF "Radio"

  - Encourage elders, veterans Mentoring
      - ID, RFC development
         - Discourage "Use Usual Editors" mindset
      - Consider "PWG "Preliminary Working Groups" to sense full WG
         - Often decision left to the certain few (high barrier)

     on an indirect but I believe part of the improving IETF
     brand and image:

     - Serious review of "Rough Consensus" process
        - Technical Advisors need to get involved earlier

  - Leverage Assets
      - RFC format as a Tech Writing model for Engineering Students
      - Professional Trade member/certification "badge"
      - IETF membership subscriptions
         - Discounts

  - Seek more academia, industry, govt joint ventures
      - Summer "IETF" Internship
      - Start up, grants
      - Resource site

  - Assistance, Awareness with Legal, IP issues (international, etc)

  - Personally, increase the quality of work, minimize the "Fix it
    later" mindset - major turn off for young people IMV.

And perhaps, hire a PR, technical sales consultant who knows the 
subtleties of what comes first; Marketing or Technology.

-- 
Sincerely

Hector Santos
http://www.santronics.com
jabber: hector@jabber.isdg.net


From Markku.Savela@vtt.fi  Mon May  7 06:14:14 2012
Return-Path: <Markku.Savela@vtt.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40A321F85FF for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:14:14 -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 BCrilNc+0tB8 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 06:14:14 -0700 (PDT)
Received: from sally.edelkey.net (sally.edelkey.net [213.138.147.136]) by ietfa.amsl.com (Postfix) with ESMTP id BD9D021F85F6 for <ietf@ietf.org>; Mon,  7 May 2012 06:14:12 -0700 (PDT)
Received: from vttcashub1.ad.vtt.fi (213214159140.edelkey.net [213.214.159.140]) by sally.edelkey.net (8.14.2/8.14.2) with ESMTP id q47DEBld002177 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 7 May 2012 16:14:11 +0300
Received: from [130.188.198.79] (130.188.198.79) by vttcashub1.ad.vtt.fi (130.188.126.26) with Microsoft SMTP Server (TLS) id 8.2.213.0; Mon, 7 May 2012 16:14:10 +0300
Message-ID: <4FA7CAA2.8030003@vtt.fi>
Date: Mon, 7 May 2012 16:14:10 +0300
From: Markku Savela <Markku.Savela@vtt.fi>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based
References: <01OE8FJG30ZM00ZUIL@mauve.mrochek.com> <201204130359.q3D3xlG0007556@fs4113.wdf.sap.corp> <01OE9150IMNI00ZUIL@mauve.mrochek.com> <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com> <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz> <CAMm+Lwg4J-XDMdC1CMycm2FA4-Of-0Ee-u2VW3hqtUDY3+VZ5g@mail.gmail.com>
In-Reply-To: <CAMm+Lwg4J-XDMdC1CMycm2FA4-Of-0Ee-u2VW3hqtUDY3+VZ5g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-2"; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 07 May 2012 07:23:32 -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 May 2012 13:15:10 -0000

On 05/07/2012 03:52 PM, Phillip Hallam-Baker wrote:
> So far I don't see any interest in production deployment other than
> our own plans so I don't think your working group consensus has
> relevance.

The draft is for TLS, but it occurs to me to ponder.. would
similar approach work for IPsec IKEv2 as an alternative to
verify endpoints?



From dworley@avaya.com  Mon May  7 07:57:39 2012
Return-Path: <dworley@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 586E821F8600 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 07:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.779
X-Spam-Level: 
X-Spam-Status: No, score=-102.779 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pe+DH3KDI7ot for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 07:57:38 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id C893B21F85FF for <ietf@ietf.org>; Mon,  7 May 2012 07:57:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKDhp0+HCzI1/2dsb2JhbABEsxmBB4IMAQEBAQIBEihECwIBCA0IIRAyJQEBBBMIGodnBZ4hnFaQPGMEnBaKKoMF
X-IronPort-AV: E=Sophos;i="4.75,544,1330923600";  d="scan'208";a="7931651"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 07 May 2012 10:57:36 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 May 2012 10:40:25 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 7 May 2012 10:57:37 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Date: Mon, 7 May 2012 10:57:36 -0400
Subject: RE: Is the IETF aging?
Thread-Topic: Is the IETF aging?
Thread-Index: Ac0rO4eAMCTQ/EwRhU2eE8S1d6A8LABJX6cZ
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0AB1@DC-US1MBEX4.global.avaya.com>
References: <3494DB29-775B-491A-B1E2-C87AD85E1A4F@psg.com>, <CBCBCFF6.32D8%hannes.tschofenig@nsn.com>
In-Reply-To: <CBCBCFF6.32D8%hannes.tschofenig@nsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 14:57:39 -0000

> From: Hannes Tschofenig [hannes.tschofenig@nsn.com]
>=20
> In the telecommunication industry you have also seen a lot of layoffs ove=
r
> the last 10 years and so there are rarely young people around in these
> companies anymore (because they either got fired or left the company
> voluntarily).

... or weren't hired in the first place.

If a company has no higher head-count now than 10 years ago, the only
young people who have been hired were hired because they were cheaper
than the older people who have been laid off.  People like that often
either leave for better opportunities, or aren't up to standards work.

For that matter, is the network industry growing?  Almost all IETF
work is at layers 3 to 6; what has been the consumption of new people
in those parts of the industry?

Dale

From chair@ietf.org  Mon May  7 08:02:07 2012
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 6A1B921F85C4 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kRYoZSPlwux for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:02:06 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C44E321F861D for <ietf@ietf.org>; Mon,  7 May 2012 08:02:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 11B1A12C7DE; Mon,  7 May 2012 08:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fupR1z2LvkDg; Mon,  7 May 2012 08:01:59 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) by c8a.amsl.com (Postfix) with ESMTPSA id 8D80912C7D0; Mon,  7 May 2012 08:01:59 -0700 (PDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com>
Date: Mon, 7 May 2012 11:02:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
X-Mailer: Apple Mail (2.1084)
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 May 2012 15:02:07 -0000

During the IESG discussion of this thread, we recognized the quality of =
the information on the blue sheets.  This point was made very clearly at =
the open mic discussion at the plenary and on the mail list.

Some people voiced agreement with your position, and others supported =
the posting of this information.  As I said in my earlier message, the =
consensus is quite rough.  By my review of the thread, which was made =
more difficult by the many off-topic postings, there is rough consensus =
for the inclusion of blue sheet information in the proceedings.

Russ


On May 6, 2012, at 10:04 PM, David Morris wrote:

>=20
> I consider that there is a significant difference between the =
information=20
> provided in the registered attendee list and the individual blue =
sheets:
>=20
> a) to the extent that the information on the blue sheet is valid, it=20=

> provides an hour by hour log of location, the overall list of =
attendees at=20
> most indicates an individual was present to pick up their badge at =
some
> point during the meeting.
> b) the validity of the list of registered attendees has a higher =
degree
> of probable validity because of the requirement for a significant =
payment
> and the processes required to process that payment.
> c) Individual blue sheets can suffer from any number of unintentional =
and
> intentional issues which limit their factual validity but not the =
mischief
> which can be caused by their easy online access.
> d) Scanning and publication imports a validity to the data which is =
not
> widely accepted by the community.
>=20
> David Morris
>=20
> On Sun, 6 May 2012, IETF Chair wrote:
>=20
>> David:
>>=20
>> The list of participants and their addresses are already part of the =
proceedings.  The incremental difference shows which participants signed =
in at each session.
>>=20
>> Russ
>>=20
>>=20
>>=20
>> On May 6, 2012, at 7:03 PM, David Morris wrote:
>>=20
>>>=20
>>> =46rom my following of the topic, that concensus was really rough, =
in=20
>>> particular the part about publishing the scans on-line. That =
represents
>>> a significant difference in ease access which I think required more =
than
>>> the very very rough concensus you seem to think you found.
>>>=20
>>> On Sun, 6 May 2012, IETF Chair wrote:
>>>=20
>>>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>>>=20
>>>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>>>=20
>>>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>>>=20
>>>>=20
>>>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>>>=20
>>>> - Continue to collect email addresses on blue sheets;
>>>>=20
>>>> - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>>>=20
>>>> - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>>>=20
>>>> - Discard paper blue sheets after scanning.
>>>>=20
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>>=20
>>>=20
>>=20
>>=20
>=20


From john-ietf@jck.com  Mon May  7 08:03:36 2012
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 A683221F85CD for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GImDxwdEEY+a for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:03:36 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CCBFE21F85C4 for <ietf@ietf.org>; Mon,  7 May 2012 08:03:35 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SRPO9-000GOs-8f; Mon, 07 May 2012 10:58:13 -0400
Date: Mon, 07 May 2012 11:03:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@iecc.com>, ietf@ietf.org
Subject: Re: IETF posting delays
Message-ID: <23CFBE2A92AF704229AD806D@PST.JCK.COM>
In-Reply-To: <20120507141804.80865.qmail@joyce.lan>
References: <20120507141804.80865.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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, 07 May 2012 15:03:36 -0000

--On Monday, May 07, 2012 14:18 +0000 John Levine
<johnl@iecc.com> wrote:

>>> the question seems to be "we used to reply to the sender
>>> with a notification that their message was blocked due to
>>> not being a list member, with options to wait or cancel; did
>>> we disable those notifications?"
> 
> I sure hope so.  These days about 99.9% of spam from unknown
> senders is spam with forged addresses, so responses are just
> more spam aka blowback.

At the same time, the IETF has considerable obligations about
openness.  From that point of view, silently discarding messages
from someone who thought they had properly subscribed could be
rather bad news.  Fortunately, if I correctly understand the
thread, we aren't doing that, we are moderating instead.  

If that is correct, it seems to me that it might be appropriate
to send a message to the submitter of a moderated message
explaining that moderation leads to both delays and extra work
so that, if they intend to submit further messages from the
address, they should subscribe properly.  That approach would
seem to serve both efficiency (fewer messages to moderate
because people would be warned to subscribe) and anti-blowback
efforts (the only messages that would generate responses to a
supposed submission addresses are those that had already been
found sufficiently valid/relevant to post to the list).

It also seems to me that our subscription and archive pages
might well be modified to be explicit about what our procedures
actually are.  Doing so would improve openness, help some
contributors, and not help any spammers who are indifferent to
whether their messages go (anyone wanting to specifically spam
IETF lists can figure out how to subscribe, even with our
verification process).

If an active contributor like Hector is posting one message
after another, seeing delays, and not noticing that he is not
properly subscribed at that address, it seems to me that we
could, and should, be doing better rather than blaming the
victim.

    john



From stephen.farrell@cs.tcd.ie  Mon May  7 08:53:24 2012
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 8769021F85D1 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvXTJlJGgPjd for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 08:53:23 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 8214721F85D5 for <ietf@ietf.org>; Mon,  7 May 2012 08:53:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id E6777157D25; Mon,  7 May 2012 16:53:22 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1336406002; bh=vi6YjDgVw8O/gH xn8Wfhlm/+7j7CZyOnbjqIIe1t+dU=; b=MkvQr3ZPWc5dLQ+43Ez9AKhj38yfNl B6vSkAtEGMPjR0FDmIYuNR4rZtX7PI4A8QgfY3GJiICX6ie4S58pZfFGDz3sscAT liCzQf7psH0p2mBYY3LhKU6kfOBss4ifIQUJaSla6Unl+sqbKwNrfz8tCQa7Bdom 7h1fkj+cTP7miiq1VeHW6eEecXcMiWaayffMZYAqv0+1XLU3NuTdNITQlA9xV3Qo /dkP0NMrTSW/5cfP58UMZWGz30SJk2jwuks6lrks2jUdht5lyRauNm/VMupsOITX gFZ7T3Sc5VlDVBqVcTCRXTlKnjbVlaAL2WYVxxzzg/6hBGwpJs6l6r5A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id qNRMo9zBEPyE; Mon,  7 May 2012 16:53:22 +0100 (IST)
Received: from [10.87.48.9] (unknown [86.46.17.170]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5FA1E157D22; Mon,  7 May 2012 16:53:21 +0100 (IST)
Message-ID: <4FA7EFF1.9080803@cs.tcd.ie>
Date: Mon, 07 May 2012 16:53:21 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Markku Savela <Markku.Savela@vtt.fi>
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based
References: <01OE8FJG30ZM00ZUIL@mauve.mrochek.com> <201204130359.q3D3xlG0007556@fs4113.wdf.sap.corp> <01OE9150IMNI00ZUIL@mauve.mrochek.com> <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com> <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz> <CAMm+Lwg4J-XDMdC1CMycm2FA4-Of-0Ee-u2VW3hqtUDY3+VZ5g@mail.gmail.com> <4FA7CAA2.8030003@vtt.fi>
In-Reply-To: <4FA7CAA2.8030003@vtt.fi>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 15:53:24 -0000

On 05/07/2012 02:14 PM, Markku Savela wrote:
> On 05/07/2012 03:52 PM, Phillip Hallam-Baker wrote:
>> So far I don't see any interest in production deployment other than
>> our own plans so I don't think your working group consensus has
>> relevance.
> 
> The draft is for TLS, but it occurs to me to ponder.. would
> similar approach work for IPsec IKEv2 as an alternative to
> verify endpoints?

IPsec is in the WG charter, [1] but there's been zero energy
for that so far. I believe the chairs plan to poll the WG
about that kind of thing once the current spec is out the
door. So, if you're interested in that, sign up to the WG
list.

S

[1] http://tools.ietf.org/wg/dane/charters

> 
> 
> 

From ted.ietf@gmail.com  Mon May  7 08:56:43 2012
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 D65E921F8625; Mon,  7 May 2012 08:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Level: 
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[AWL=0.007,  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 S+yV8Hk3DACw; Mon,  7 May 2012 08:56:43 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1E27421F8623; Mon,  7 May 2012 08:56:43 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so217701vbb.31 for <multiple recipients>; Mon, 07 May 2012 08:56: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:content-transfer-encoding; bh=Msuoy/8u1QcY9w1A53gMuOIBEp08Vsvo6zAQo+2cr14=; b=TbBk+SKHsHEtOquBBMf2xtK091SnEH2DGnMuN25/Nbs/UqxkZkpFTqvvGnYHRzLU2+ YNCv430hdAegzGwMvW2cVdo4zrinpp5riWX56614s6yx6DXnwT72fDcx6Vu0rsnboMSL j2jsbZbWVv32nsy1PEm2AQn4GKGa0RLutwgo8LSzPlwP/fWe8vVk7HEgh6/oRHA5IGfv wRhrE5zx09b226RJYi2mHw8bc0tQIn1Izq8MIKU9pIFTH/SgZKkklvBXpwgzxMDAEKtY x7GHoK7cuD/DPAZDMBVDi3hYI+ad8pn/PPGTFhrDxQ625E+clkQKEblxQZ8P7y5M3ezC oUUA==
MIME-Version: 1.0
Received: by 10.220.239.81 with SMTP id kv17mr6129109vcb.2.1336405856021; Mon, 07 May 2012 08:50:56 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Mon, 7 May 2012 08:50:55 -0700 (PDT)
In-Reply-To: <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org>
Date: Mon, 7 May 2012 08:50:55 -0700
Message-ID: <CA+9kkMD0xToJuQrgSmaA7P8p0r_TX-Ne=+DPbwiLkrY-pEsbng@mail.gmail.com>
Subject: Re: Future Handling of Blue Sheets
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 07 May 2012 15:56:44 -0000

As a clarifying question, did the IESG discuss whether the image of
the blue sheets might be made available online under other terms of
use, rather than within the proceedings?  For example, making these
available to anyone with a tools login, so that anyone willing to
register as a user has access, but they are not broadcast?

regards,

Ted Hardie

On Sun, May 6, 2012 at 9:46 AM, IETF Chair <chair@ietf.org> wrote:
> We have heard from many community participants, and consensus is quite ro=
ugh on this topic. =A0The IESG discussed this thread and reached two conclu=
sions:
>
> (1) Rough consensus: an open and transparent standards process is more im=
portant to the IETF than privacy of blue sheet information.
>
> (2) Rough consensus: inclusion of email addresses is a good way to distin=
guish participants with the same or similar names.
>
>
> Based on these conclusions, the plan is to handle blue sheets as follows:
>
> =A0- Continue to collect email addresses on blue sheets;
>
> =A0- Scan the blue sheet and include the image in the proceedings for the=
 WG session;
>
> =A0- Add indication to top of the blue sheet so people know it will be pa=
rt of the proceedings; and
>
> =A0- Discard paper blue sheets after scanning.
>
>
> On behalf of the IESG,
> =A0Russ
>

From chair@ietf.org  Mon May  7 09:02:34 2012
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 BF80A21F85CC for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:02:34 -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 tO4zdywTcnSh for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:02:34 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id ED1FB21F851B for <ietf@ietf.org>; Mon,  7 May 2012 09:02:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E796312C7EB; Mon,  7 May 2012 09:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8GgaONevteg; Mon,  7 May 2012 09:02:33 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-140-3.washdc.fios.verizon.net [96.255.140.3]) by c8a.amsl.com (Postfix) with ESMTPSA id 6DC0712C7E9; Mon,  7 May 2012 09:02:33 -0700 (PDT)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <CA+9kkMD0xToJuQrgSmaA7P8p0r_TX-Ne=+DPbwiLkrY-pEsbng@mail.gmail.com>
Date: Mon, 7 May 2012 12:02:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9151A484-2EFF-47DA-9531-E96C7279D9AD@ietf.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <CA+9kkMD0xToJuQrgSmaA7P8p0r_TX-Ne=+DPbwiLkrY-pEsbng@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1084)
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 May 2012 16:02:34 -0000

Ted:

I will raise this with the IESG.  Of the many variants that were =
discussed, this was not one of them.

Russ


On May 7, 2012, at 11:50 AM, Ted Hardie wrote:

> As a clarifying question, did the IESG discuss whether the image of
> the blue sheets might be made available online under other terms of
> use, rather than within the proceedings?  For example, making these
> available to anyone with a tools login, so that anyone willing to
> register as a user has access, but they are not broadcast?
>=20
> regards,
>=20
> Ted Hardie
>=20
> On Sun, May 6, 2012 at 9:46 AM, IETF Chair <chair@ietf.org> wrote:
>> We have heard from many community participants, and consensus is =
quite rough on this topic.  The IESG discussed this thread and reached =
two conclusions:
>>=20
>> (1) Rough consensus: an open and transparent standards process is =
more important to the IETF than privacy of blue sheet information.
>>=20
>> (2) Rough consensus: inclusion of email addresses is a good way to =
distinguish participants with the same or similar names.
>>=20
>>=20
>> Based on these conclusions, the plan is to handle blue sheets as =
follows:
>>=20
>>  - Continue to collect email addresses on blue sheets;
>>=20
>>  - Scan the blue sheet and include the image in the proceedings for =
the WG session;
>>=20
>>  - Add indication to top of the blue sheet so people know it will be =
part of the proceedings; and
>>=20
>>  - Discard paper blue sheets after scanning.
>>=20
>>=20
>> On behalf of the IESG,
>>  Russ
>>=20
>=20


From mary.ietf.barnes@gmail.com  Mon May  7 09:28:52 2012
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 7A88221F8645 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.049, 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 DW3aCQRLmz3s for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:28:51 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 834C721F8644 for <ietf@ietf.org>; Mon,  7 May 2012 09:28:51 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so246163vbb.31 for <ietf@ietf.org>; Mon, 07 May 2012 09:28: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=vuyU88GryMC6LWkJCUHtnFFse9CHVt/tkkbmVkIayi8=; b=kXHYNY3N2UDUs0/XyNglmzJCoKrqr+WAqmprZoVcy1Q89y7+TQFDdfCMPNbICqsu4b OgXDf+4s1EKc1/dfmDIwzxVHTc0scd7O2OA4FJmhFTqGZ16Q761EfUx8C5XMHMHr+TLj fiD3ThAZ1RlA4UBcRgr9BfQZGQTsyH7cr3BVzDC0f76jDTOdJAWOS8xDPcoGIUYa9wa4 lkiD5MWLPcZLRIR1S2v+33teVFU3TwWIs7CXZDp9aESCzNUO4ix2corb/4YPIjZvRRvi 8GcbcKytv31ezq8MOKJ30OYaYL8QvuF6yKWkMjpYp4kfNfzZomckhKMSGa4L09/Gz/4k g5Fg==
MIME-Version: 1.0
Received: by 10.220.150.12 with SMTP id w12mr5629569vcv.39.1336406772056; Mon, 07 May 2012 09:06:12 -0700 (PDT)
Received: by 10.52.68.145 with HTTP; Mon, 7 May 2012 09:06:12 -0700 (PDT)
In-Reply-To: <23CFBE2A92AF704229AD806D@PST.JCK.COM>
References: <20120507141804.80865.qmail@joyce.lan> <23CFBE2A92AF704229AD806D@PST.JCK.COM>
Date: Mon, 7 May 2012 11:06:12 -0500
Message-ID: <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com>
Subject: Re: IETF posting delays
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=f46d04389097ec836a04bf7472f7
Cc: John Levine <johnl@iecc.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: Mon, 07 May 2012 16:28:52 -0000

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

I agree with you John.  I know that I have had messages discarded on
several occasions.  As a moderator, I look at the legitimacy of the posting
and if it is a member of the community (it's generally very easy to tell),
then I add them as being able to post even though they aren't subscribed.
This can be very helpful as many of us use multiple addresses.

Mary.

On Mon, May 7, 2012 at 10:03 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Monday, May 07, 2012 14:18 +0000 John Levine
> <johnl@iecc.com> wrote:
>
> >>> the question seems to be "we used to reply to the sender
> >>> with a notification that their message was blocked due to
> >>> not being a list member, with options to wait or cancel; did
> >>> we disable those notifications?"
> >
> > I sure hope so.  These days about 99.9% of spam from unknown
> > senders is spam with forged addresses, so responses are just
> > more spam aka blowback.
>
> At the same time, the IETF has considerable obligations about
> openness.  From that point of view, silently discarding messages
> from someone who thought they had properly subscribed could be
> rather bad news.  Fortunately, if I correctly understand the
> thread, we aren't doing that, we are moderating instead.
>
> If that is correct, it seems to me that it might be appropriate
> to send a message to the submitter of a moderated message
> explaining that moderation leads to both delays and extra work
> so that, if they intend to submit further messages from the
> address, they should subscribe properly.  That approach would
> seem to serve both efficiency (fewer messages to moderate
> because people would be warned to subscribe) and anti-blowback
> efforts (the only messages that would generate responses to a
> supposed submission addresses are those that had already been
> found sufficiently valid/relevant to post to the list).
>
> It also seems to me that our subscription and archive pages
> might well be modified to be explicit about what our procedures
> actually are.  Doing so would improve openness, help some
> contributors, and not help any spammers who are indifferent to
> whether their messages go (anyone wanting to specifically spam
> IETF lists can figure out how to subscribe, even with our
> verification process).
>
> If an active contributor like Hector is posting one message
> after another, seeing delays, and not noticing that he is not
> properly subscribed at that address, it seems to me that we
> could, and should, be doing better rather than blaming the
> victim.
>
>    john
>
>
>

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

I agree with you John. =A0I know that I have had messages discarded on seve=
ral occasions. =A0As a moderator, I look at the legitimacy of the posting a=
nd if it is a member of the community (it&#39;s generally very easy to tell=
), then I add them as being able to post even though they aren&#39;t subscr=
ibed. This can be very helpful as many of us use multiple addresses.=A0<div=
>
<br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Mon, May 7, 20=
12 at 10:03 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_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<br>
<br>
--On Monday, May 07, 2012 14:18 +0000 John Levine<br>
&lt;<a href=3D"mailto:johnl@iecc.com">johnl@iecc.com</a>&gt; wrote:<br>
<br>
&gt;&gt;&gt; the question seems to be &quot;we used to reply to the sender<=
br>
&gt;&gt;&gt; with a notification that their message was blocked due to<br>
&gt;&gt;&gt; not being a list member, with options to wait or cancel; did<b=
r>
&gt;&gt;&gt; we disable those notifications?&quot;<br>
&gt;<br>
&gt; I sure hope so. =A0These days about 99.9% of spam from unknown<br>
&gt; senders is spam with forged addresses, so responses are just<br>
&gt; more spam aka blowback.<br>
<br>
At the same time, the IETF has considerable obligations about<br>
openness. =A0From that point of view, silently discarding messages<br>
from someone who thought they had properly subscribed could be<br>
rather bad news. =A0Fortunately, if I correctly understand the<br>
thread, we aren&#39;t doing that, we are moderating instead.<br>
<br>
If that is correct, it seems to me that it might be appropriate<br>
to send a message to the submitter of a moderated message<br>
explaining that moderation leads to both delays and extra work<br>
so that, if they intend to submit further messages from the<br>
address, they should subscribe properly. =A0That approach would<br>
seem to serve both efficiency (fewer messages to moderate<br>
because people would be warned to subscribe) and anti-blowback<br>
efforts (the only messages that would generate responses to a<br>
supposed submission addresses are those that had already been<br>
found sufficiently valid/relevant to post to the list).<br>
<br>
It also seems to me that our subscription and archive pages<br>
might well be modified to be explicit about what our procedures<br>
actually are. =A0Doing so would improve openness, help some<br>
contributors, and not help any spammers who are indifferent to<br>
whether their messages go (anyone wanting to specifically spam<br>
IETF lists can figure out how to subscribe, even with our<br>
verification process).<br>
<br>
If an active contributor like Hector is posting one message<br>
after another, seeing delays, and not noticing that he is not<br>
properly subscribed at that address, it seems to me that we<br>
could, and should, be doing better rather than blaming the<br>
victim.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
 =A0 =A0john<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--f46d04389097ec836a04bf7472f7--

From john-ietf@jck.com  Mon May  7 09:30:20 2012
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 483FC21F85F2 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.229
X-Spam-Level: 
X-Spam-Status: No, score=-102.229 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, J_CHICKENPOX_37=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 I2T2lHTbl509 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 09:30:19 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5A921F860B for <ietf@ietf.org>; Mon,  7 May 2012 09:30:16 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SRQk1-000GUx-PE; Mon, 07 May 2012 12:24:53 -0400
Date: Mon, 07 May 2012 12:30:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF posting delays
Message-ID: <58E92CB4F308E89E3A9718CE@PST.JCK.COM>
In-Reply-To: <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com>
References: <20120507141804.80865.qmail@joyce.lan> <23CFBE2A92AF704229AD806D@PST.JCK.COM> <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@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: John Levine <johnl@iecc.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: Mon, 07 May 2012 16:30:20 -0000

--On Monday, May 07, 2012 11:06 -0500 Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:

> I agree with you John.  I know that I have had messages
> discarded on several occasions.  As a moderator, I look at the
> legitimacy of the posting and if it is a member of the
> community (it's generally very easy to tell), then I add them
> as being able to post even though they aren't subscribed. This
> can be very helpful as many of us use multiple addresses.

Yes.  As a user of multiple addresses, one of the cases I was
worried about was precisely the one of someone posting from an
address that is not normally used with a particular list.

I just had a very helpful off-list discussion with Paul Hoffman
who pointed out that my suggestion was stated badly and easily
misunderstood.  So, to clarify, assume that a message from a
previously-unknown address shows up on the list.  Unless other
heuristics discard it as, e.g., malware, the message goes into a
moderator queue.  There are then, I think, three possible cases:

(1) Moderator decides message is trash and discards it.  As you
say, it is usually pretty easy to tell.

(2) Moderator decides the message is legitimate, allows it to be
posted, and authorizes that address to post to the list in the
future (as you suggest).

(3) Moderator decides the message is legitimate, allows it to be
posted, but does not authorize future unmoderated postings from
that address.  This could happen for any of several reasons,
ranging from accidentally not getting the box checked to the
moderator's not being sure the message is really from an active
community member who is already subscribed to the list even
though the message content is fine.

For that third case, I was trying to suggest that it would be
good to automatically generate a message to the posting address
indicating that, while the posting had been approved by the
moderator, subscribing would be a really good idea if the person
intended to use the address in the future.  

Paul pointed out that automatically generating such a message
would almost certainly require modifications to Mailman code and
that such modifications are a non=starter.   That doesn't make
the idea a bad one, only one that is unimplementable with an
acceptable level of resource investment and possibly one that
should be passed on to the Mailman powers-that-be as a
suggestion.

I was not suggesting any change at all for the first case other
than we review our subscription and archive pages to be sure
they are adequately clear that postings from non-subscribers are
not guaranteed to appear on the relevant list.

best,
    john





From dougb@dougbarton.us  Mon May  7 10:33:41 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D787421F8691 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 10:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.845
X-Spam-Level: 
X-Spam-Status: No, score=-2.845 tagged_above=-999 required=5 tests=[AWL=0.755,  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 Rn-vrBNpNcGE for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 10:33:39 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id EFDA121F8686 for <ietf@ietf.org>; Mon,  7 May 2012 10:33:38 -0700 (PDT)
Received: (qmail 2597 invoked by uid 399); 7 May 2012 17:33:36 -0000
Received: from unknown (HELO ?172.17.194.139?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 7 May 2012 17:33:36 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4FA80770.7050803@dougbarton.us>
Date: Mon, 07 May 2012 10:33:36 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <4FA6F614.3040601@dougbarton.us> <D0C6D69F-930A-4B66-B1DB-B264860D961B@vigilsec.com>
In-Reply-To: <D0C6D69F-930A-4B66-B1DB-B264860D961B@vigilsec.com>
X-Enigmail-Version: 1.4
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: Mon, 07 May 2012 17:33:43 -0000

On 05/06/2012 03:54 PM, Russ Housley wrote:
> Doug:
> 
>>>  - Discard paper blue sheets after scanning.
>>
>> Everything else seems fine, but I'm concerned about this one. Have you
>> run this idea past some sort of legal counsel who is knowledgeable about
>> intellectual property litigation? If so, no worries.
> 
> The IETF Counsel has been consulted, and he sees no trouble in this regard.

Excellent! Thanks for clarifying.

Doug

From sm@resistor.net  Mon May  7 10:35:05 2012
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 E5B8D21F845E for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 10:35:04 -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 d9agcbz5Ndru for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 10:35: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 F100121F845D for <ietf@ietf.org>; Mon,  7 May 2012 10:35:01 -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 q47HYkf2001427; Mon, 7 May 2012 10:34:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336412091; i=@resistor.net; bh=d0FEzyvh3Xnp7kczO2fZXagLzNMQ1P0T3hEpApe7HQ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LeZsfsu1K/F6u3MPTuEgmp4d0GrTVYyotHkScRe7d7J4pUBZiN7zR/BJrR/aC6xIA leT5uL/BTSIiAGpsDNBZHiZamtkhrFjNG87qo9euZHfRnomBq1gptuNuNlWHtZce0u Nx6RY1MOyyF5VJq/18AB2kJEx7NVKNfsduo/WRbw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336412091; i=@resistor.net; bh=d0FEzyvh3Xnp7kczO2fZXagLzNMQ1P0T3hEpApe7HQ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EWHN79c2nmyr2M21DqzoViePnAzoct9QODQxXVo7NpIcjK3H3Udnf5e5NkB+DlWEh rNMpTYo1E+5iT5Rpso4QT8bMjJfQvA/GmFSLR+JRj+hJ9iSHS8xAwYQ2ipnJNiocpl gSKz8e1kYBDlNA+1TSveIm2qao434y4Yhc9TPYio=
Message-Id: <6.2.5.6.2.20120507093459.0a67a6f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 07 May 2012 10:26:39 -0700
To: Ofer Inbar <cos@aaaaa.org>
From: SM <sm@resistor.net>
Subject: Re: IETF posting delays
In-Reply-To: <20120507134513.GJ335@mip.aaaaa.org>
References: <4FA5AC1F.4010005@gmail.com> <m2vckac9rq.wl%randy@psg.com> <4FA60919.9000403@gmail.com> <F9304BA3-C842-42B3-97BF-F3B2B725AD9C@cisco.com> <4FA716D6.2050402@santronics.com> <m2y5p4aht3.wl%randy@psg.com> <201205070825.q478P38h050921@bartok.nlnetlabs.nl> <m2txzs8jc5.wl%randy@psg.com> <4FA7C483.1060204@isdg.net> <5E4DCB9F-57B7-41A5-8D9C-EDEBAB62859D@cisco.com> <20120507134513.GJ335@mip.aaaaa.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2012 17:35:05 -0000

Hi Ofer,
At 06:45 07-05-2012, Ofer Inbar wrote:
>The question isn't "do we block email from non-members";
>the question seems to be "we used to reply to the sender with a
>notification that their message was blocked due to not being a
>list member, with options to wait or cancel; did we disable those
>notifications?"

Some IETF mailing lists send a notification to the sender if a 
message is held for moderation and the ability to cancel the 
posting.  Speaking about the IETF mailing lists I am aware of, email 
from non-subscribers go to a moderation queue.  The options used for 
these queues have always been reject (send a bounce) or allow the 
message through.  The "discard" option is not used on those lists.

The response time is usually under twenty-four hours.  There was only 
one case of incorrect rejection as it was not possible for the 
moderator to read the contents of that message easily.  There were 
only two cases of posting delays:

  (i)  Misunderstanding relating to prior discussions about postings

  (ii) Forty-eight hour delay which could be attributed to laziness

The IETF celebrates Mailman day on the first day of each 
month.  Every subscriber is sent a notification about the IETF 
mailing lists he or she is subscribed to.  There are a few cases of 
subscribers being automatically unsubscribed from an IETF mailing 
list due to excessive bounces.  This happened for an IETF mailing 
list which makes ietf@ look like a low volume.

The IESG in its wisdom and kindness has provided the following statements:

http://www.ietf.org/iesg/statement/moderated-lists.html
http://www.ietf.org/iesg/statement/spam-control.html

IETF mailing lists do not use the List-Owner: header.  If you need a 
point of contact, you can find the email address of the mailing list 
moderator by accessing the first URI in the List-Subscribe: header.

The message with msg-id 4FA58B0C.1010803@santronics.com was delayed 
due to moderation.  The delay may be influenced by the current 
definition of GMT (UTC - 0700) within the IETF.

Regards,
-sm 


From dcrocker@bbiw.net  Mon May  7 12:21:25 2012
Return-Path: <dcrocker@bbiw.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 95BD021F8700 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 12:21: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 mcIqGaJMOFDJ for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 12:21:24 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AE51921F86F5 for <ietf@ietf.org>; Mon,  7 May 2012 12:21:12 -0700 (PDT)
Received: from [142.131.211.169] ([142.131.211.169]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q47JL9Uc006091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 7 May 2012 12:21:10 -0700
Message-ID: <4FA820A5.5010804@bbiw.net>
Date: Mon, 07 May 2012 15:21:09 -0400
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF posting delays
References: <20120507141804.80865.qmail@joyce.lan> <23CFBE2A92AF704229AD806D@PST.JCK.COM> <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com>
In-Reply-To: <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@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.17]); Mon, 07 May 2012 12:21:10 -0700 (PDT)
Cc: 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: Mon, 07 May 2012 19:21:25 -0000

offlist.



On 5/7/2012 12:06 PM, Mary Barnes wrote:
>   I know that I have had messages discarded on several occasions.  As a
> moderator, I look at the legitimacy of the posting and if it is a member
> of the community (it's generally very easy to tell), then I add them as
> being able to post even though they aren't subscribed. This can be very
> helpful as many of us use multiple addresses.


Mary,

The issue is a matter of scaling and resources.  For small lists with 
low traffic, setting to moderate mis-postings works well.  For larger 
and more visible lists, with more activity, it doesn't.  The 
signal-to-noise ratio is horrible.  (That's a first-hand opinion, not an 
abstraction.)

On the other hand, if you are volunteering to moderate mis-posted 
messages for the IETF list, perhaps the list administrator will let you...


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From paul@cypherpunks.ca  Mon May  7 14:08:50 2012
Return-Path: <paul@cypherpunks.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D081121F8667 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 14:08: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 61xX-HDBFNkk for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 14:08:50 -0700 (PDT)
Received: from letoams.cypherpunks.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 49D4421F867A for <ietf@ietf.org>; Mon,  7 May 2012 14:08:49 -0700 (PDT)
Received: by letoams.cypherpunks.ca (Postfix, from userid 500) id A7E5C85428; Mon,  7 May 2012 17:08:32 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by letoams.cypherpunks.ca (Postfix) with ESMTP id 9A4388033B; Mon,  7 May 2012 17:08:32 -0400 (EDT)
Date: Mon, 7 May 2012 17:08:32 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [dane] Last Call: <draft-ietf-dane-protocol-19.txt> (The DNS-Based
In-Reply-To: <4FA7EFF1.9080803@cs.tcd.ie>
Message-ID: <alpine.LFD.2.02.1205071704580.21578@bofh.nohats.ca>
References: <01OE8FJG30ZM00ZUIL@mauve.mrochek.com> <201204130359.q3D3xlG0007556@fs4113.wdf.sap.corp> <01OE9150IMNI00ZUIL@mauve.mrochek.com> <CAMm+LwgP7FTA=B2Q6=mke6Vu_hVRN=p06_BL98SdW04j31UOqQ@mail.gmail.com> <27A5BF91-C082-4FB4-8D6E-B68F725440EC@nic.cz> <CAMm+Lwg4J-XDMdC1CMycm2FA4-Of-0Ee-u2VW3hqtUDY3+VZ5g@mail.gmail.com> <4FA7CAA2.8030003@vtt.fi> <4FA7EFF1.9080803@cs.tcd.ie>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: Markku Savela <Markku.Savela@vtt.fi>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 21:08:50 -0000

On Mon, 7 May 2012, Stephen Farrell wrote:

>> The draft is for TLS, but it occurs to me to ponder.. would
>> similar approach work for IPsec IKEv2 as an alternative to
>> verify endpoints?
>
> IPsec is in the WG charter, [1] but there's been zero energy
> for that so far. I believe the chairs plan to poll the WG
> about that kind of thing once the current spec is out the
> door. So, if you're interested in that, sign up to the WG
> list.

Related to these are RFC-4025 and draft-kivinen-ipsecme-oob-pubkey,
and I do think there is a need to update the RFC to allow for the
new raw pubkets in IPsec using SPKI and wrap it up in a dane like
specification document, and would be willing to help.

Paul

From hsantos@isdg.net  Mon May  7 15:19:26 2012
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 5C93F21F8534 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 15:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level: 
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=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 cWrmrrdGO8k1 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 15:19:24 -0700 (PDT)
Received: from mail.catinthebox.net (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 75AFD21F842B for <ietf@ietf.org>; Mon,  7 May 2012 15:19:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3593; t=1336429160; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=0dbHRyjZd3FzOMxE3O2H9Cd5Sfk=; b=GDR8xkVYpDVSLe/9ybhe MOdmkHqNUAKdHGgPCBktOLl+c1nkKaX1REGuaAv2J4cPZ52hCwkN3nzFUCF2W1Hg 4nYNy/iw8UzJjnMKPMYMtMr8boPwOR4myN/+CbOwMuDOY4D86kV5W9gcQe9Bx0S0 n2dCVGXdgKlPoiH/9vDvJUE=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 07 May 2012 18:19:20 -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 v6.4.454.1) with ESMTP id 1040996721.51127.2704; Mon, 07 May 2012 18:19:19 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3593; t=1336429152; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=+5a0EQY rzckVW835ADcFbvLAFYIutpfmJiEIGJkvSj8=; b=HCzeVXA0VdMEk3+iyzEpobN HP6heDCs2IbDqw/c4dOJhBi7+7csaf4+j+4J80FqTqAorXnhP+LUm+hVI/jg2TEM a0A9jz0ENphiT3b0J/huhbbsUABa+4dV4pBQ2LVmusT8lqhoDVjifnItteas4Ntw NXDjNXBZvJY+YFE57f/0=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 07 May 2012 18:19:12 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1639884831.5606.7352; Mon, 07 May 2012 18:19:11 -0400
Message-ID: <4FA84A46.2020407@isdg.net>
Date: Mon, 07 May 2012 18:18:46 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF posting delays
References: <20120507141804.80865.qmail@joyce.lan>	<23CFBE2A92AF704229AD806D@PST.JCK.COM> <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com>
In-Reply-To: <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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: Mon, 07 May 2012 22:19:26 -0000

Hi,

I think what has been lost here is that the delays were not just with 
my non-member submission, but also my member address as well.  The 
fact that it is intermittent makes it all very odd.  I still have yet 
to receive a May 6 8:49PM reply post using my member address and its 
been nearly 22 hours.  The odd thing is that someone indicated offlist 
they received a copy of it.  But its not on the IETF list archive and 
my servers show no evidence of any attempt.

My MTA machine use SPF with hard fail policies (no softfail or neutral 
results) and all my mail is signed, that doesn't seem to have any 
weight.  Whats odd is if this is indeed of case of specific 
individuals moderation, its filtered on domains only and not the 
"person" because I have no problem with gmail.com postings.

Thanks

-- 
Hector Santos
http://www.santronics.com
http://hector.wildcatblog.com
jabber: hector@jabber.isdg.net

Mary Barnes wrote:
> I agree with you John.  I know that I have had messages discarded on
> several occasions.  As a moderator, I look at the legitimacy of the posting
> and if it is a member of the community (it's generally very easy to tell),
> then I add them as being able to post even though they aren't subscribed.
> This can be very helpful as many of us use multiple addresses.
> 
> Mary.
> 
> On Mon, May 7, 2012 at 10:03 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
>>
>> --On Monday, May 07, 2012 14:18 +0000 John Levine
>> <johnl@iecc.com> wrote:
>>
>>>>> the question seems to be "we used to reply to the sender
>>>>> with a notification that their message was blocked due to
>>>>> not being a list member, with options to wait or cancel; did
>>>>> we disable those notifications?"
>>> I sure hope so.  These days about 99.9% of spam from unknown
>>> senders is spam with forged addresses, so responses are just
>>> more spam aka blowback.
>> At the same time, the IETF has considerable obligations about
>> openness.  From that point of view, silently discarding messages
>> from someone who thought they had properly subscribed could be
>> rather bad news.  Fortunately, if I correctly understand the
>> thread, we aren't doing that, we are moderating instead.
>>
>> If that is correct, it seems to me that it might be appropriate
>> to send a message to the submitter of a moderated message
>> explaining that moderation leads to both delays and extra work
>> so that, if they intend to submit further messages from the
>> address, they should subscribe properly.  That approach would
>> seem to serve both efficiency (fewer messages to moderate
>> because people would be warned to subscribe) and anti-blowback
>> efforts (the only messages that would generate responses to a
>> supposed submission addresses are those that had already been
>> found sufficiently valid/relevant to post to the list).
>>
>> It also seems to me that our subscription and archive pages
>> might well be modified to be explicit about what our procedures
>> actually are.  Doing so would improve openness, help some
>> contributors, and not help any spammers who are indifferent to
>> whether their messages go (anyone wanting to specifically spam
>> IETF lists can figure out how to subscribe, even with our
>> verification process).
>>
>> If an active contributor like Hector is posting one message
>> after another, seeing delays, and not noticing that he is not
>> properly subscribed at that address, it seems to me that we
>> could, and should, be doing better rather than blaming the
>> victim.
>>
>>    john
>>
>>
>>
> 



From scott@kitterman.com  Mon May  7 15:35:19 2012
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 13E8B21F86C4 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 15:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KrzrEb1ErwUI for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 15:35:18 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1371321F86B6 for <ietf@ietf.org>; Mon,  7 May 2012 15:35:18 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 16EAF20E40D0; Mon,  7 May 2012 18:35:17 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1336430117; bh=X6/Sh4u3oO16cpKz9dti+XBBDZxK4HgOEtC2stZ68Os=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=dPHj7sUKF1YQjLgD++0Hkk8AljP7mGL4cDptWW73KKIjZtDlECb95YZiAzJgBw5ys vOPe+KkcV9MOmZss8g4k/Y00ROrolOrsMMMGfdDiuK4kkRGy6GH++1Unsi+z9zo9R5 hJ/cLomIlyuBPJ+wPW+4alOhGM6m4lNjmVl1Afh0=
Received: from scott-latitude-e6320.localnet (unknown [12.50.158.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id C73FB20E4095;  Mon,  7 May 2012 18:35:15 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Date: Mon, 07 May 2012 18:35:11 -0400
Message-ID: <1755826.2gyQD9Uvee@scott-latitude-e6320>
User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic-pae; KDE/4.8.2; i686; ; )
In-Reply-To: <20120507195025.19948.3410.idtracker@ietfa.amsl.com>
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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: Mon, 07 May 2012 22:35:19 -0000

On Monday, May 07, 2012 12:50:25 PM The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Source Ports in ARF Reports'
>   <draft-kucherawy-marf-source-ports-03.txt> as Proposed Standard
...

I think adding the source port field has value, particularly for abuse 
reporting, but I think making it RECOMMENDED for authentication failure 
reporting is not appropriate.

The last two paragraphs of section three read (trivial typo - there's an extra 
new line in the first paragraph that I removed here):

   When any report is generated that includes the "Source-IP" reporting
   field (see Section 3.2 of [ARF]), this field SHOULD also be present,
   unless the port number is unavailable.

   Use of this field is RECOMMENED for reports generated per
   [AUTHFAILURE-REPORT] (see Section 3.1 of that document).

The first corresponds to use in abuse reporting.  As described in this draft 
and the references, I think the addition of source ports for abuse reports is 
well justified.  OTOH, if you look at Section 3.1 of RFC 6591  [AUTHFAILURE-
REPORT], it gives the purpose of the most of the various data elements it 
RECOMMENDS as "to aid in diagnosing the authentication failure."

I'm not aware of any authentication methods supported by RFC 6591  
[AUTHFAILURE-REPORT] where source port makes a difference in authentication 
results.  If RFC 6591 is extended in the future to include one that does, that 
would be the time to make source port RECOMMENDED for authentication failure 
reports.  In the mean time it's just additional overhead and message size.

My suggestion would be to change the last part of section three to read:

   When any authentication failure report [AUTHFAILURE-REPORT] is generated
   that includes the "Source-IP" reporting field (see Section 3.1 of
   [AUTHFAILURE-REPORT]]), this field MAY also be included.

Other than that, I think it's ready to go.

Scott K

From warren@kumari.net  Mon May  7 16:01:17 2012
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 4796A21F8664 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 16:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.555
X-Spam-Level: 
X-Spam-Status: No, score=-96.555 tagged_above=-999 required=5 tests=[AWL=-9.956, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hts+KqJOPE0 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 16:01:16 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3C021F865F for <ietf@ietf.org>; Mon,  7 May 2012 16:01:16 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 3AFD31B401ED; Mon,  7 May 2012 19:01:15 -0400 (EDT)
Subject: Re: [IETF] Re: IETF posting delays
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4FA84A46.2020407@isdg.net>
Date: Mon, 7 May 2012 19:01:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC2F4F72-0F69-452D-993C-9266041DD5A2@kumari.net>
References: <20120507141804.80865.qmail@joyce.lan>	<23CFBE2A92AF704229AD806D@PST.JCK.COM> <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com> <4FA84A46.2020407@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1257)
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: Mon, 07 May 2012 23:01:17 -0000

On May 7, 2012, at 6:18 PM, Hector Santos wrote:

> Hi,
>=20
> I think what has been lost here is that the delays were not just with =
my non-member submission, but also my member address as well.  The fact =
that it is intermittent makes it all very odd.  I still have yet to =
receive a May 6 8:49PM reply post using my member address and its been =
nearly 22 hours.  The odd thing is that someone indicated offlist they =
received a copy of it.  But its not on the IETF list archive and my =
servers show no evidence of any attempt.

Maybe you have "not metoo" (Receive your own posts to the list?) set on =
your mailman entry?=20
Actually, if you login to mailman for the discuss list does it show =
anything interesting about your address?

W

>=20
> My MTA machine use SPF with hard fail policies (no softfail or neutral =
results) and all my mail is signed, that doesn't seem to have any =
weight.  Whats odd is if this is indeed of case of specific individuals =
moderation, its filtered on domains only and not the "person" because I =
have no problem with gmail.com postings.
>=20
> Thanks
>=20
> --=20
> Hector Santos
> http://www.santronics.com
> http://hector.wildcatblog.com
> jabber: hector@jabber.isdg.net
>=20
> Mary Barnes wrote:
>> I agree with you John.  I know that I have had messages discarded on
>> several occasions.  As a moderator, I look at the legitimacy of the =
posting
>> and if it is a member of the community (it's generally very easy to =
tell),
>> then I add them as being able to post even though they aren't =
subscribed.
>> This can be very helpful as many of us use multiple addresses.
>> Mary.
>> On Mon, May 7, 2012 at 10:03 AM, John C Klensin <john-ietf@jck.com> =
wrote:
>>>=20
>>> --On Monday, May 07, 2012 14:18 +0000 John Levine
>>> <johnl@iecc.com> wrote:
>>>=20
>>>>>> the question seems to be "we used to reply to the sender
>>>>>> with a notification that their message was blocked due to
>>>>>> not being a list member, with options to wait or cancel; did
>>>>>> we disable those notifications?"
>>>> I sure hope so.  These days about 99.9% of spam from unknown
>>>> senders is spam with forged addresses, so responses are just
>>>> more spam aka blowback.
>>> At the same time, the IETF has considerable obligations about
>>> openness.  =46rom that point of view, silently discarding messages
>>> from someone who thought they had properly subscribed could be
>>> rather bad news.  Fortunately, if I correctly understand the
>>> thread, we aren't doing that, we are moderating instead.
>>>=20
>>> If that is correct, it seems to me that it might be appropriate
>>> to send a message to the submitter of a moderated message
>>> explaining that moderation leads to both delays and extra work
>>> so that, if they intend to submit further messages from the
>>> address, they should subscribe properly.  That approach would
>>> seem to serve both efficiency (fewer messages to moderate
>>> because people would be warned to subscribe) and anti-blowback
>>> efforts (the only messages that would generate responses to a
>>> supposed submission addresses are those that had already been
>>> found sufficiently valid/relevant to post to the list).
>>>=20
>>> It also seems to me that our subscription and archive pages
>>> might well be modified to be explicit about what our procedures
>>> actually are.  Doing so would improve openness, help some
>>> contributors, and not help any spammers who are indifferent to
>>> whether their messages go (anyone wanting to specifically spam
>>> IETF lists can figure out how to subscribe, even with our
>>> verification process).
>>>=20
>>> If an active contributor like Hector is posting one message
>>> after another, seeing delays, and not noticing that he is not
>>> properly subscribed at that address, it seems to me that we
>>> could, and should, be doing better rather than blaming the
>>> victim.
>>>=20
>>>   john
>>>=20
>>>=20
>>>=20
>=20
>=20


From sm@resistor.net  Mon May  7 16:41:20 2012
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 E893F21F85A5 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 16:41:19 -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 CRF-ONmvOQl7 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 16:41:18 -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 4C2AF21F84D5 for <ietf@ietf.org>; Mon,  7 May 2012 16:41:17 -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 q47NfBvR018301; Mon, 7 May 2012 16:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336434077; i=@resistor.net; bh=52EFAItuWULMskG0QcaWmq9AxUjzlSG72+0dWla1Zu0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k/lwraZOh6a7dQJKT7iX8W2XMqdsKlSSFJCZZtmDK0+OQ5K+UYpo7X6pfQ+irs9fO qk/gJPEehTocEl6K5TTAjpB+0Iidtw+5YXKy+DGnNnNBYLB/ZfKGt/Q9v4H9s9Z+32 7epetO4iTgqr/wC8aHk5ScQ/2+E4/Cn+n+GikNMM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336434077; i=@resistor.net; bh=52EFAItuWULMskG0QcaWmq9AxUjzlSG72+0dWla1Zu0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BCMmDKH9Dlr1UhptiZV3+NMoIPVvSpzxX0x2nKaj2eh0NLBO1bI1v/QIbGHAaqL1j p98Nq14T4FSWsZd/mTqTw+1h3ACctjqyBYzSu8aHqa+xjUYJiCjro94ViinL5rQxmg A+SYfe3/+6RMAs8ITGVfTsxFqSMU6piAgpswI8WM=
Message-Id: <6.2.5.6.2.20120507160625.09da1248@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 07 May 2012 16:40:59 -0700
To: Hector Santos <hsantos@isdg.net>
From: SM <sm@resistor.net>
Subject: Re: IETF posting delays
In-Reply-To: <4FA84A46.2020407@isdg.net>
References: <20120507141804.80865.qmail@joyce.lan> <23CFBE2A92AF704229AD806D@PST.JCK.COM> <CAHBDyN6DSqg19V_SuV4fX+aA+7i7zwevxmixFNubBkRcy=Lxhw@mail.gmail.com> <4FA84A46.2020407@isdg.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: Mon, 07 May 2012 23:41:20 -0000

Hi Hector,
At 15:18 07-05-2012, Hector Santos wrote:
>I think what has been lost here is that the delays were not just 
>with my non-member submission, but also my member address as 
>well.  The fact that it is intermittent makes

How do you know that the email address is currently subscribed to 
this mailing list?

>  it all very odd.  I still have yet to receive a May 6 8:49PM reply 
> post using my member address and its been nearly 22 hours.  The odd 
> thing is that someone indicated offlist they received a copy of 
> it.  But its not on the IETF list archive and my servers show no 
> evidence of any attempt.

The "May 6 8:49 PM" in the above is ambiguous.  The problem which you 
described is odd.  It was mentioned in a message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73207.html that:

   "I figured the IETF list/MTA software is using some custom outbound
    queuing/scheduling logic with a higher preference for email domain
    volume, i.e. gmail.com at the top and individual domain accounts
    last in its scheduling logic."

The round-trip for a message posted earlier was 20 seconds.  What 
response did you receive from ietf-action@ietf.org when you reported 
the posting problem?

Regards,
-sm 


From dotis@mail-abuse.org  Mon May  7 17:59:50 2012
Return-Path: <dotis@mail-abuse.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 C80D921F8604 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 17:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tEVm3w-0ICC for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 17:59:50 -0700 (PDT)
Received: from mailserv.mail-abuse.org (mailserv.mail-abuse.org [150.70.98.118]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE2821F8483 for <ietf@ietf.org>; Mon,  7 May 2012 17:59:50 -0700 (PDT)
Received: from US-DOUGO-MAC.local (unknown [10.31.37.8]) by mailserv.mail-abuse.org (Postfix) with ESMTPSA id C6789174027A for <ietf@ietf.org>; Tue,  8 May 2012 00:59:49 +0000 (UTC)
Message-ID: <4FA87005.80704@mail-abuse.org>
Date: Mon, 07 May 2012 17:59:49 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <1755826.2gyQD9Uvee@scott-latitude-e6320>
In-Reply-To: <1755826.2gyQD9Uvee@scott-latitude-e6320>
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, 08 May 2012 00:59:50 -0000

On 5/7/12 3:35 PM, Scott Kitterman wrote:
>  On Monday, May 07, 2012 12:50:25 PM The IESG wrote:
> > The IESG has received a request from an individual submitter to
> > consider the following document: - 'Source Ports in ARF Reports'
> > <draft-kucherawy-marf-source-ports-03.txt> as Proposed Standard
>  ...
>
>  I think adding the source port field has value, particularly for
>  abuse reporting, but I think making it RECOMMENDED for authentication
>  failure reporting is not appropriate.
>
>  The last two paragraphs of section three read (trivial typo - there's
>  an extra new line in the first paragraph that I removed here):
>
>  When any report is generated that includes the "Source-IP" reporting
>  field (see Section 3.2 of [ARF]), this field SHOULD also be present,
>  unless the port number is unavailable.
>
>  Use of this field is RECOMMENED for reports generated per
>  [AUTHFAILURE-REPORT] (see Section 3.1 of that document).
>
>  The first corresponds to use in abuse reporting. As described in
>  this draft and the references, I think the addition of source ports
>  for abuse reports is well justified. OTOH, if you look at Section
>  3.1 of RFC 6591 [AUTHFAILURE- REPORT], it gives the purpose of the
>  most of the various data elements it RECOMMENDS as "to aid in
>  diagnosing the authentication failure."
>
>  I'm not aware of any authentication methods supported by RFC 6591
>  [AUTHFAILURE-REPORT] where source port makes a difference in
>  authentication results. If RFC 6591 is extended in the future to
>  include one that does, that would be the time to make source port
>  RECOMMENDED for authentication failure reports. In the mean time
>  it's just additional overhead and message size.
>
>  My suggestion would be to change the last part of section three to
>  read:
>
>  When any authentication failure report [AUTHFAILURE-REPORT] is
>  generated that includes the "Source-IP" reporting field (see Section
>  3.1 of [AUTHFAILURE-REPORT]]), this field MAY also be included.
>
>  Other than that, I think it's ready to go.
Dear Scott,

Agreed.  Logging ports translated by LSNs is not recommended.  The only 
tangible data represents the source IP address made available by LSN 
services.  Both of which touch upon the changes you recommend.   At some 
point, authentication reporting also needs to be updated as well.

Regards,
Douglas Otis


From msk@cloudmark.com  Mon May  7 21:20:13 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA5B21F8557 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 21:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.624
X-Spam-Level: 
X-Spam-Status: No, score=-102.624 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 PJeuNldNMDzM for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 21:20:12 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4400521F84A6 for <ietf@ietf.org>; Mon,  7 May 2012 21:20:12 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id 7GLU1j0030as01C01GLUKH; Mon, 07 May 2012 21:20:28 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=Xth4yC59 c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=ldJM1g7oyCcA:10 a=YfYFAX1pRpwA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=OlMI6XHdcPpTm43xq40A:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=O3L55zdx2w7MxNjT:21 a=qJ8e67autuJQ_2r0:21 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Mon, 7 May 2012 21:20:00 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Scott Kitterman <scott@kitterman.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Topic: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Index: AQHNLKHAkXDvdhJ2jUSCN0WTYs7sLZa/SMQA
Date: Tue, 8 May 2012 04:20:00 +0000
Message-ID: <9452079D1A51524AA5749AD23E003928118C04@exch-mbx901.corp.cloudmark.com>
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <1755826.2gyQD9Uvee@scott-latitude-e6320>
In-Reply-To: <1755826.2gyQD9Uvee@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336450828; bh=vc7tIQ1tgbguaAO6ssqAbFI7qeWMRUV8yE2HtEpdGb4=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=AqAGewSqounayLoeoHyJJ6mQcFfQ1Uma3BH2gyMpNPsTJMwiloCe6PIiVd1Wr85Ap JZhTl//FzrDvOrSEzL3P4akxKJaou8BG3HgfvWZF2gYxF9tBoR7+SYYtESY/J//sP5 EHoBCGgYH/rFEE9xPQUVqGcKD+y9cShGEaR2E/30=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 04:20:13 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Monday, May 07, 2012 3:35 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Sourc=
e Ports in ARF Reports) to Proposed Standard
>=20
> My suggestion would be to change the last part of section three to
> read:
>=20
>    When any authentication failure report [AUTHFAILURE-REPORT] is generat=
ed
>    that includes the "Source-IP" reporting field (see Section 3.1 of
>    [AUTHFAILURE-REPORT]]), this field MAY also be included.
>=20
> Other than that, I think it's ready to go.

If all one is doing is figuring out why something like a DKIM signature fai=
led on an otherwise legitimate message, then I agree the source port isn't =
a useful input to that work.  In fact, as far as DKIM goes, the source IP a=
ddress is probably not useful either.

If, however, one is trying to track down the transmission of fraudulent ema=
il such as phishing attacks, source ports can be used to identify the perpe=
trator more precisely when compared to logs.  Support for this latter use c=
ase is why I believe RECOMMENDED is appropriate.

-MSK

From scott@kitterman.com  Mon May  7 22:49:11 2012
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 0F73A21F854E for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 22:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_ENC_UTF8x2=0.246]
Received: 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+ffbPq2jxfT for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 22:49:10 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDA121F8543 for <ietf@ietf.org>; Mon,  7 May 2012 22:49:10 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 72148D0408B; Tue,  8 May 2012 00:49:09 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1336456149; bh=NDYpvGP0Wa+UpCZAKG47zHquR3NaJxDi4u1fBrSfhcQ=; h=References:In-Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Subject:From:Date:To:Message-ID; b=DegkS2poVLvD7eV7McXZzu9wN/e3FI+2HD9aIMO+HJx5Q/a7HwvC59nDOo/eklUPB 2hykVs6H9AQdMNHdOE+pYUi7mqy6bj/DKaAzU/nxvBp54Qcrp7Qij3KJkE/v5xOBcp nqbMMcOdewSutKbgV67x4oqdIiX8tgyzRgMkPo0w=
Received: from 223.sub-97-210-212.myvzw.com (223.sub-97-210-212.myvzw.com [97.210.212.223]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id CECD0D04087;  Tue,  8 May 2012 00:49:08 -0500 (CDT)
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <1755826.2gyQD9Uvee@scott-latitude-e6320> <9452079D1A51524AA5749AD23E003928118C04@exch-mbx901.corp.cloudmark.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <9452079D1A51524AA5749AD23E003928118C04@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: =?UTF-8?Q?RE=3A_Last_Call=3A_=3Cdraft-kucherawy-marf-source-ports-03=2Et?= =?UTF-8?Q?xt=3E_=28Source=09Ports_in_ARF_Reports=29_to_Proposed_Standard?=
From: Scott Kitterman <scott@kitterman.com>
Date: Tue, 08 May 2012 00:49:09 -0500
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <a80ed582-27a1-4669-acf5-782b4f342b04@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: Tue, 08 May 2012 05:49:11 -0000

"Murray S. Kucherawy" <msk@cloudmark.com> wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>Of Scott Kitterman
>> Sent: Monday, May 07, 2012 3:35 PM
>> To: ietf@ietf.org
>> Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt>
>(Source Ports in ARF Reports) to Proposed Standard
>> 
>> My suggestion would be to change the last part of section three to
>> read:
>> 
>>    When any authentication failure report [AUTHFAILURE-REPORT] is
>generated
>>    that includes the "Source-IP" reporting field (see Section 3.1 of
>>    [AUTHFAILURE-REPORT]]), this field MAY also be included.
>> 
>> Other than that, I think it's ready to go.
>
>If all one is doing is figuring out why something like a DKIM signature
>failed on an otherwise legitimate message, then I agree the source port
>isn't a useful input to that work.  In fact, as far as DKIM goes, the
>source IP address is probably not useful either.
>
>If, however, one is trying to track down the transmission of fraudulent
>email such as phishing attacks, source ports can be used to identify
>the perpetrator more precisely when compared to logs.  Support for this
>latter use case is why I believe RECOMMENDED is appropriate.

Which is exactly the case (abuse report) the second to last paragraph takes care of.  I agree RECOMMENDED is appropriate there and you have it there.

For auth failure analysis I read you as agreeing it's not needed.  There are some authorization methods that use IP address, so I don't think that for auth failure reports inclusion of IP address and source port are comparable.

Based on your response, I don't understand your objection to dropping the RECOMMENDS for auth failure reports and keeping it  for abuse reports? 


From msk@cloudmark.com  Mon May  7 23:23:48 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4B121F84BF for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 23:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.624
X-Spam-Level: 
X-Spam-Status: No, score=-102.624 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 esPHS-xajdI1 for <ietf@ietfa.amsl.com>; Mon,  7 May 2012 23:23:48 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6D921F84B9 for <ietf@ietf.org>; Mon,  7 May 2012 23:23:47 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.25]) by mail.cloudmark.com with bizsmtp id 7JQF1j0010ZaKgw01JQFwZ; Mon, 07 May 2012 23:24:15 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=Xth4yC59 c=1 sm=1 a=LdFkGDrDWH2mcjCZERnC4w==:17 a=ldJM1g7oyCcA:10 a=YfYFAX1pRpwA:10 a=zutiEJmiVI4A:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=OlMI6XHdcPpTm43xq40A:9 a=WRl78pWfFLQDaxsteXUA:7 a=QEXdDO2ut3YA:10 a=lZB815dzVvQA:10 a=yTKvJPHZ5YSD8RtJ:21 a=KU3NlbQ4F-xZLdqj:21 a=LdFkGDrDWH2mcjCZERnC4w==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas901.corp.cloudmark.com ([fe80::2524:76b6:a865:539c%10]) with mapi id 14.01.0355.002; Mon, 7 May 2012 23:23:47 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Scott Kitterman <scott@kitterman.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Topic: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Index: AQHNLKHAkXDvdhJ2jUSCN0WTYs7sLZa/SMQAgACP5ID//5MiMA==
Date: Tue, 8 May 2012 06:23:46 +0000
Message-ID: <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.com>
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <1755826.2gyQD9Uvee@scott-latitude-e6320> <9452079D1A51524AA5749AD23E003928118C04@exch-mbx901.corp.cloudmark.com> <a80ed582-27a1-4669-acf5-782b4f342b04@email.android.com>
In-Reply-To: <a80ed582-27a1-4669-acf5-782b4f342b04@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336458255; bh=1r0RSVbPVrw4hVsEg0amcONWTmBTZZc88ML8KWPjGhc=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=uulDjtsa72105GsJmY+Igt85ZqYvQprEW9VOJgA+6AAkFB/u+8+6xGHj2nQEOnmg0 sJCyot1H0mAoZWZ1UTgWMgYTRG5lFoTvmzsJj3tAdv6XqsS36jpLamjaxzI7sOhAlA 5gqO+ezcrugDOIl1xZv2eptLrpi2Y0NxTAgz+mPU=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 06:23:49 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBTY290dCBLaXR0
ZXJtYW4NCj4gU2VudDogTW9uZGF5LCBNYXkgMDcsIDIwMTIgMTA6NDkgUE0NCj4gVG86IGlldGZA
aWV0Zi5vcmcNCj4gU3ViamVjdDogUkU6IExhc3QgQ2FsbDogPGRyYWZ0LWt1Y2hlcmF3eS1tYXJm
LXNvdXJjZS1wb3J0cy0wMy50eHQ+IChTb3VyY2UgUG9ydHMgaW4gQVJGIFJlcG9ydHMpIHRvIFBy
b3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiA+SWYgYWxsIG9uZSBpcyBkb2luZyBpcyBmaWd1cmluZyBv
dXQgd2h5IHNvbWV0aGluZyBsaWtlIGEgREtJTSBzaWduYXR1cmUNCj4gPmZhaWxlZCBvbiBhbiBv
dGhlcndpc2UgbGVnaXRpbWF0ZSBtZXNzYWdlLCB0aGVuIEkgYWdyZWUgdGhlIHNvdXJjZSBwb3J0
DQo+ID5pc24ndCBhIHVzZWZ1bCBpbnB1dCB0byB0aGF0IHdvcmsuICBJbiBmYWN0LCBhcyBmYXIg
YXMgREtJTSBnb2VzLCB0aGUNCj4gPnNvdXJjZSBJUCBhZGRyZXNzIGlzIHByb2JhYmx5IG5vdCB1
c2VmdWwgZWl0aGVyLg0KPiA+DQo+ID5JZiwgaG93ZXZlciwgb25lIGlzIHRyeWluZyB0byB0cmFj
ayBkb3duIHRoZSB0cmFuc21pc3Npb24gb2YgZnJhdWR1bGVudA0KPiA+ZW1haWwgc3VjaCBhcyBw
aGlzaGluZyBhdHRhY2tzLCBzb3VyY2UgcG9ydHMgY2FuIGJlIHVzZWQgdG8gaWRlbnRpZnkNCj4g
PnRoZSBwZXJwZXRyYXRvciBtb3JlIHByZWNpc2VseSB3aGVuIGNvbXBhcmVkIHRvIGxvZ3MuICBT
dXBwb3J0IGZvciB0aGlzDQo+ID5sYXR0ZXIgdXNlIGNhc2UgaXMgd2h5IEkgYmVsaWV2ZSBSRUNP
TU1FTkRFRCBpcyBhcHByb3ByaWF0ZS4NCj4gDQo+IFdoaWNoIGlzIGV4YWN0bHkgdGhlIGNhc2Ug
KGFidXNlIHJlcG9ydCkgdGhlIHNlY29uZCB0byBsYXN0IHBhcmFncmFwaA0KPiB0YWtlcyBjYXJl
IG9mLiAgSSBhZ3JlZSBSRUNPTU1FTkRFRCBpcyBhcHByb3ByaWF0ZSB0aGVyZSBhbmQgeW91IGhh
dmUNCj4gaXQgdGhlcmUuDQo+IA0KPiBGb3IgYXV0aCBmYWlsdXJlIGFuYWx5c2lzIEkgcmVhZCB5
b3UgYXMgYWdyZWVpbmcgaXQncyBub3QgbmVlZGVkLg0KPiBUaGVyZSBhcmUgc29tZSBhdXRob3Jp
emF0aW9uIG1ldGhvZHMgdGhhdCB1c2UgSVAgYWRkcmVzcywgc28gSSBkb24ndA0KPiB0aGluayB0
aGF0IGZvciBhdXRoIGZhaWx1cmUgcmVwb3J0cyBpbmNsdXNpb24gb2YgSVAgYWRkcmVzcyBhbmQg
c291cmNlDQo+IHBvcnQgYXJlIGNvbXBhcmFibGUuDQo+IA0KPiBCYXNlZCBvbiB5b3VyIHJlc3Bv
bnNlLCBJIGRvbid0IHVuZGVyc3RhbmQgeW91ciBvYmplY3Rpb24gdG8gZHJvcHBpbmcNCj4gdGhl
IFJFQ09NTUVORFMgZm9yIGF1dGggZmFpbHVyZSByZXBvcnRzIGFuZCBrZWVwaW5nIGl0ICBmb3Ig
YWJ1c2UNCj4gcmVwb3J0cz8NCg0KSSBkb24ndCB0aGluayBpdCdzIHBvc3NpYmxlIGZvciBzb2Z0
d2FyZSB0byBpZGVudGlmeSBjb3JyZWN0bHkgYSBjYXNlIG9mIGFuIGFjY2lkZW50YWwgYXV0aGVu
dGljYXRpb24gZmFpbHVyZSB2ZXJzdXMgZGV0ZWN0ZWQgZnJhdWQuICBJZiBpdCB3ZXJlLCB0aGVu
IEknZCBhZ3JlZSB0aGF0IGZvciB0aGUgc2ltcGxlIGF1dGhlbnRpY2F0aW9uIGZhaWx1cmUgY2Fz
ZSB0aGUgc291cmNlIHBvcnQgaXNuJ3QgdXNlZnVsLg0KDQpJbiB0aGUgYWJzZW5jZSBvZiB0aGF0
IGNhcGFiaWxpdHksIGlzbid0IGl0IGJldHRlciB0byBnaXZlIHRoZSBpbnZlc3RpZ2F0aW5nIHVz
ZXIgYXMgbXVjaCBpbmZvcm1hdGlvbiBhcyBwb3NzaWJsZSB0byB1c2UgaW4gY29ycmVsYXRpb24g
b2YgbG9ncyBhbmQgc3VjaD8NCg0KLU1TSw0K

From yaakov_s@rad.com  Tue May  8 03:12:48 2012
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB1921F8550 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 03:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.244
X-Spam-Level: 
X-Spam-Status: No, score=-101.244 tagged_above=-999 required=5 tests=[AWL=-1.246, BAYES_50=0.001, UNPARSEABLE_RELAY=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 bG+h1NZrR7LE for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 03:12:47 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 80F2521F8496 for <ietf@ietf.org>; Tue,  8 May 2012 03:12:44 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 8 May 2012 12:54:05 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Tue, 8 May 2012 13:12:40 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: RE: Gender diversity in engineering
Thread-Topic: Gender diversity in engineering
Thread-Index: AQHNKdc7gcUmzr72jki88vroRrN4G5a5jVWAgAACRYCAAGHugIAFvOeg
Date: Tue, 8 May 2012 10:12:40 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9043C6483@EXRAD5.ad.rad.co.il>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>, <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA8@DC-US1MBEX4.global.avaya.com> <8638E241-928A-421F-A7A2-DDB404ADBAC3@checkpoint.com>
In-Reply-To: <8638E241-928A-421F-A7A2-DDB404ADBAC3@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090203.4FA8F199.006E,ss=1,fgs=0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 10:12:48 -0000

> Around 30%-40%. I don't have hard numbers,=20
> but I have a feeling that it has gone down a bit in the last 10 years.=20

Yoav,=20

Your feelings are quite accurate as to the range,
but less so regarding the trend.
According to a recent study, 35.6% of high-tech employees in Israel are wom=
en,
and this percentage has been relatively stable for the past 10 years.

Women make up 47.5% of all employees with academic credentials (as of 2010)=
 in all sectors,
so high-tech is actually comparatively under-represented.
On the other hand, only 32.9% of managerial positions (in all sectors)
are occupied by women.

Y(J)S



From sant9442@gmail.com  Tue May  8 04:35:55 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D270F21F8495 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 04:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.419
X-Spam-Level: 
X-Spam-Status: No, score=-2.419 tagged_above=-999 required=5 tests=[AWL=1.180,  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 wch-zo9owRS4 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 04:35:55 -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 1142921F849A for <ietf@ietf.org>; Tue,  8 May 2012 04:35:54 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so1717293ggm.31 for <ietf@ietf.org>; Tue, 08 May 2012 04:35:54 -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 :content-type:content-transfer-encoding; bh=TrhHLGWHNYDeXcqn8MQBotu2W8/EV1xalbOtDrUMG20=; b=rVlzKmclD4xNRAcZwYP0745S6woi+zZcx/heh3M9HSzMR2Dx4vV+/mJkTHVroMlmEv jfYEVMUVobyRODJbMw2dp80lelRhlo6HH4g1ZPznyVeNNoz+r9kZBNBreG2++0uEE4Cj sshpTkv+MAUjLOce273Mvir8fI9cDnlksrxCijPUMTzlDbHgNi37JIyryXdUt2G/EXrC zfn6OO5arf16dky05rYlz3SorRwGrfzZs3cQ1vULpNir2JGQxteY946G0teZXlpVtudS d68grGaHMHPlrCdtOzPBiFFxY8p9fYlKx4vXsxhD2NO0m4171chLwSWwS5Dp8S9jXVAr iAKQ==
Received: by 10.236.103.106 with SMTP id e70mr8402142yhg.121.1336476954658; Tue, 08 May 2012 04:35:54 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id r5sm32306571ani.19.2012.05.08.04.35.53 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 May 2012 04:35:53 -0700 (PDT)
Message-ID: <4FA90503.2070109@gmail.com>
Date: Tue, 08 May 2012 07:35:31 -0400
From: Hector Santos <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF Discuss <ietf@ietf.org>
Subject: [Fwd: IETF posting delays]
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: Tue, 08 May 2012 11:35:56 -0000

-------- Original Message --------
Subject: [Fwd: Re: [IETF] Re: IETF posting delays]
Date: Tue, 08 May 2012 07:31:13 -0400
From: Hector Santos <sant9442@gmail.com>
To: Warren Kumari <warren@kumari.net>
CC: SM <sm@resistor.net>, John C Klensin <john-ietf@jck.com>, 
ietf-action@ietf.org

I'm giving up. Now using gmail account.

As you can see with the response below to Warren and cc: Mary, John,
and the IETF list, was sent last night at May 7, 23:01.  My MTA
transport logs show it was sent to all four, so I am presuming the
direct mail was received and perhaps you can confirm you received it.
Yet, not posted on the list, not on the IETF archive, my copy never sent.

Thats now two submissions by a subscribed member that are in la la
land.  So its not working.

The IETF wants to improve its image with the minority engineering
community?  Wants to reduce the noise? Wants to increase IETF meeting
attendance?

IMO, this policy in place for subscribed member mail holding and
filtering when the mail is never posted,  needs to be seriously
reviewed.   The perception amounts to nothing else but deliberate
censorship, especially when the mail appears to be discarded.

I have current plans and budgeting to attend the next two IETF
Meetings. I have second thoughts now, dropping my I-D work and just
stay out of the IETF scene. Who needs the stress!

-- 
Hector Santos
http://www.santronics.com
http://hector.wildcatblog.com
jabber: hector@jabber.isdg.net

From ynir@checkpoint.com  Tue May  8 06:01:54 2012
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 3839821F8540 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 06:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.201, 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 BEtEqgEJi3-E for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 06:01:53 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C537C21F84B6 for <ietf@ietf.org>; Tue,  8 May 2012 06:01:52 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q48D1o0Z003593;  Tue, 8 May 2012 16:01:50 +0300
X-CheckPoint: {4FA926C6-3-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 8 May 2012 16:01:49 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Yaakov Stein <yaakov_s@rad.com>
Date: Tue, 8 May 2012 16:01:33 +0300
Subject: Re: Gender diversity in engineering
Thread-Topic: Gender diversity in engineering
Thread-Index: Ac0tGroWj4+tMZnSQ3K4jAzvN0rOcA==
Message-ID: <973D9CC4-83E8-4831-81AE-94B6D10887A9@checkpoint.com>
References: <201205012040.q41Keg7F012654@mtv-core-2.cisco.com> <FD424DD0-F514-497D-B3D1-7A18A484FD1F@standardstrack.com>, <CAP8yD=t6zcAtbfufaJWbt=oRONaQhnVOn4aL52nYTL+-hecqCQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA8@DC-US1MBEX4.global.avaya.com> <8638E241-928A-421F-A7A2-DDB404ADBAC3@checkpoint.com> <07F7D7DED63154409F13298786A2ADC9043C6483@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9043C6483@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 13:01:54 -0000

On May 8, 2012, at 1:12 PM, Yaakov Stein wrote:

>> Around 30%-40%. I don't have hard numbers,=20
>> but I have a feeling that it has gone down a bit in the last 10 years.=20
>=20
> Yoav,=20
>=20
> Your feelings are quite accurate as to the range,
> but less so regarding the trend.
> According to a recent study, 35.6% of high-tech employees in Israel are w=
omen,
> and this percentage has been relatively stable for the past 10 years.
>=20
> Women make up 47.5% of all employees with academic credentials (as of 201=
0) in all sectors,
> so high-tech is actually comparatively under-represented.
> On the other hand, only 32.9% of managerial positions (in all sectors)
> are occupied by women.

I can believe that. It could be specific to Check Point. OTOH there are tho=
se companies with departments where only women work. That could be keeping =
the balance.

Yoav=

From ajs@anvilwalrusden.com  Tue May  8 06:52:13 2012
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 9C81821F85A4 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 06:52:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.626
X-Spam-Level: 
X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=-0.027, 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 gRknb30Bk8+A for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 06:52:11 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id DC4FE21F847F for <ietf@ietf.org>; Tue,  8 May 2012 06:52:10 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id C8DD51ECB41D for <ietf@ietf.org>; Tue,  8 May 2012 13:52:09 +0000 (UTC)
Date: Tue, 8 May 2012 09:52:00 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [Fwd: IETF posting delays]
Message-ID: <20120508135200.GA10226@mail.yitter.info>
References: <4FA90503.2070109@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FA90503.2070109@gmail.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, 08 May 2012 13:52:14 -0000

On Tue, May 08, 2012 at 07:35:31AM -0400, Hector Santos wrote:
> Thats now two submissions by a subscribed member that are in la la
> land.  So its not working.

I just looked at the subscriber's list available to list members at
https://www.ietf.org/mailman/roster/ietf, and I don't find the string
"santronics" on that page.  There are, however, 30 people whose list
membership is undisclosed, so I might have missed something.  Are you
sure you actually subscribed, though?  Don't forget that there's a
confirmation step.

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dotis@mail-abuse.org  Tue May  8 08:08:27 2012
Return-Path: <dotis@mail-abuse.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 5FCCE11E809B for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 08:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Level: 
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cmTaO4rqoij for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 08:08:26 -0700 (PDT)
Received: from mailserv.mail-abuse.org (mailserv.mail-abuse.org [150.70.98.118]) by ietfa.amsl.com (Postfix) with ESMTP id 88AFF11E8091 for <ietf@ietf.org>; Tue,  8 May 2012 08:08:26 -0700 (PDT)
Received: from US-DOUGO-MAC.local (unknown [10.31.37.9]) by mailserv.mail-abuse.org (Postfix) with ESMTPSA id 0BA711740216 for <ietf@ietf.org>; Tue,  8 May 2012 15:08:26 +0000 (UTC)
Message-ID: <4FA936E9.2050705@mail-abuse.org>
Date: Tue, 08 May 2012 08:08:25 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <1755826.2gyQD9Uvee@scott-latitude-e6320> <9452079D1A51524AA5749AD23E003928118C04@exch-mbx901.corp.cloudmark.com> <a80ed582-27a1-4669-acf5-782b4f342b04@email.android.com> <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.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: Tue, 08 May 2012 15:08:27 -0000

On 5/7/12 11:23 PM, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Scott Kitterman
>> Sent: Monday, May 07, 2012 10:49 PM
>> To: ietf@ietf.org
>> Subject: RE: Last Call:<draft-kucherawy-marf-source-ports-03.txt>  (Source Ports in ARF Reports) to Proposed Standard
>>
>>> If all one is doing is figuring out why something like a DKIM signature
>>> failed on an otherwise legitimate message, then I agree the source port
>>> isn't a useful input to that work.  In fact, as far as DKIM goes, the
>>> source IP address is probably not useful either.
>>>
>>> If, however, one is trying to track down the transmission of fraudulent
>>> email such as phishing attacks, source ports can be used to identify
>>> the perpetrator more precisely when compared to logs.  Support for this
>>> latter use case is why I believe RECOMMENDED is appropriate.
>> Which is exactly the case (abuse report) the second to last paragraph
>> takes care of.  I agree RECOMMENDED is appropriate there and you have
>> it there.
>>
>> For auth failure analysis I read you as agreeing it's not needed.
>> There are some authorization methods that use IP address, so I don't
>> think that for auth failure reports inclusion of IP address and source
>> port are comparable.
>>
>> Based on your response, I don't understand your objection to dropping
>> the RECOMMENDS for auth failure reports and keeping it  for abuse
>> reports?
> I don't think it's possible for software to identify correctly a case of an accidental authentication failure versus detected fraud.  If it were, then I'd agree that for the simple authentication failure case the source port isn't useful.
>
> In the absence of that capability, isn't it better to give the investigating user as much information as possible to use in correlation of logs and such?
Dear Murray,

This is not about individual submissions or retaining privacy.  This is 
about retaining the only (weakly) authenticated piece of information 
within public SMTP exchanges.  All other SMTP elements are easily 
spoofed and worthless at positively identifying compromised systems for 
the purpose of subsequent isolation.   Attempts to track ports in the 
presence of LSN overlooks the highly transitory translations.  However, 
the LSN scheme provides a means to determine the source IP address.

Regards,
Douglas Otis




From sm@resistor.net  Tue May  8 08:15:27 2012
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 2930D21F84D8; Tue,  8 May 2012 08:15:27 -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 lXExYe-eb5hm; Tue,  8 May 2012 08:15: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 8A35C21F84D6; Tue,  8 May 2012 08:15: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 q48FFBpa022958; Tue, 8 May 2012 08:15:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336490117; i=@resistor.net; bh=acwb3SGzH9RTgDI8YdglGzC/qUIcLBdMwQrKMh+Keks=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RscUnf6nCG8yuY5lqxUIiI/rW4S1OL4OkFKigZJ37LfgJmME7HE0N3/UDKMujzf53 9yOhb84lBGk1ByVKkI26iB9AoNY98mBFzC6y+4MFwlQKHtzcuG8BYT+mkU/qFnY/Ek d2XVOoPNShFuE1b9wO1We8Vbb4gQD4efEeIh4gEg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336490117; i=@resistor.net; bh=acwb3SGzH9RTgDI8YdglGzC/qUIcLBdMwQrKMh+Keks=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CSvPdfkyKOY4P9M7CA3GYiXHPu+0bDqFtf1SjSCCx+6gIK8t2KpjZt4AzIxuwl7A2 XOvO+SKV0/R72DyO4zb6rA08425LlZm7M4EAaMnpduaCpE1TXyHSd6pYq03B/cQIzb 9bPBd/3nJIv0bTPe/kzaeJr+AcVpYmgYSWvuzv6Y=
Message-Id: <6.2.5.6.2.20120508072511.0aa7eef0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 May 2012 08:12:25 -0700
To: Hector Santos <sant9442@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: [Fwd: IETF posting delays]
In-Reply-To: <4FA90503.2070109@gmail.com>
References: <4FA90503.2070109@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: list-manager@ietf.org, IETF Discuss <ietf@ietf.org>, ietf-owner@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:15:27 -0000

Hi Hector,

[Cc to ietf-owner@ietf.org and list-manager@ietf.org.  I note that 
the "visible" email address and the email address in the mailto: are different]

At 04:35 08-05-2012, Hector Santos wrote:
>Thats now two submissions by a subscribed member that are in la la
>land.  So its not working.

[snip]

>IMO, this policy in place for subscribed member mail holding and
>filtering when the mail is never posted,  needs to be seriously
>reviewed.   The perception amounts to nothing else but deliberate
>censorship, especially when the mail appears to be discarded.

I see hsantos@isdg.net as subscribed to ietf@ietf.org.  There hasn't 
been an announcement, which is required, mentioning that the 
hsantos@isdg.net email address is moderated.  The message posted 
around 7 May 2012 23:01:38 -0400 by hsantos@isdg.net does not show up 
in the mailing list archive of ietf@ietf.org.

The message (4FA84A46.2020407@isdg.net) posted by hsantos@isdg.net 
around 7 May 2012 18:18:46 -0400 was handed over to mail.ietf.org 
around 7 May 2012 18:19:23 -0400 and distributed to the mailing list 
around 7 May 2012 18:19:47 -0400 without moderation.

It is understandable that there is a perception that the mail from 
the above email address appears to be discarded or moderated.  If the 
escalation path is not working to your satisfaction, I suggest 
contacting the General Area Director ( gen-ads@tools.ietf.org ).

Regards,
-sm 


From marshall.eubanks@gmail.com  Tue May  8 08:30:59 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67DC811E807F; Tue,  8 May 2012 08:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.648
X-Spam-Level: 
X-Spam-Status: No, score=-103.648 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 A+IDMTaq1NFz; Tue,  8 May 2012 08:30:58 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 074D721F85BB; Tue,  8 May 2012 08:30:57 -0700 (PDT)
Received: by lagj5 with SMTP id j5so4939524lag.31 for <multiple recipients>; Tue, 08 May 2012 08:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2giYF/7+aVellBbuYYq78oUgSpZjSwBRMw1E5Bbxg/E=; b=u0pjN4haw7i+gLmeNAXDVs420CfdwgrLeqNIoPeTY5UcvJ6NmUNC5cvj8NrMEHhyZr /0Xj5UirMNyLOUV9DEpTD1qe4jKk521IOsArNEhiQXMXMIWm9UuO0Er2cucNvcY/Vfht Nqnp+z4o2DvrBZr71tQCECR6Pdv8gAokQ6UM2ZggJSGwBsL6/KHYSBgGD52FEniJuw1U /2TpvKMgRFzaRbkcODab0Jw7WH/P2E3MmMphMpPrGwakq7m5WckbnsSuFjqeAEFiRGOo tchaGIzaSaLKMgYNDEUHgG3MrosqgdodoAh50Rh+hHwPC8EZPkvUiWFag2rh3gHAgIv+ tvMA==
MIME-Version: 1.0
Received: by 10.112.37.164 with SMTP id z4mr7112375lbj.100.1336491056907; Tue, 08 May 2012 08:30:56 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Tue, 8 May 2012 08:30:56 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120508072511.0aa7eef0@resistor.net>
References: <4FA90503.2070109@gmail.com> <6.2.5.6.2.20120508072511.0aa7eef0@resistor.net>
Date: Tue, 8 May 2012 11:30:56 -0400
Message-ID: <CAJNg7VLhiK3PQ6WAKt_D0H4SxkYtLr9J0d0XnQ6m6dXVROGucQ@mail.gmail.com>
Subject: Re: [Fwd: IETF posting delays]
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: list-manager@ietf.org, IETF Discuss <ietf@ietf.org>, ietf-owner@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:30:59 -0000

On Tue, May 8, 2012 at 11:12 AM, SM <sm@resistor.net> wrote:
> Hi Hector,
>
> [Cc to ietf-owner@ietf.org and list-manager@ietf.org. =A0I note that the
> "visible" email address and the email address in the mailto: are differen=
t]
>
>
> At 04:35 08-05-2012, Hector Santos wrote:
>>
>> Thats now two submissions by a subscribed member that are in la la
>> land. =A0So its not working.
>
>
> [snip]
>
>
>> IMO, this policy in place for subscribed member mail holding and
>> filtering when the mail is never posted, =A0needs to be seriously
>> reviewed. =A0 The perception amounts to nothing else but deliberate
>> censorship, especially when the mail appears to be discarded.
>
>
> I see hsantos@isdg.net as subscribed to ietf@ietf.org. =A0There hasn't be=
en an
> announcement, which is required, mentioning that the hsantos@isdg.net ema=
il
> address is moderated. =A0The message posted around 7 May 2012 23:01:38 -0=
400
> by hsantos@isdg.net does not show up in the mailing list archive of
> ietf@ietf.org.
>
> The message (4FA84A46.2020407@isdg.net) posted by hsantos@isdg.net around=
 7
> May 2012 18:18:46 -0400 was handed over to mail.ietf.org around 7 May 201=
2
> 18:19:23 -0400 and distributed to the mailing list around 7 May 2012
> 18:19:47 -0400 without moderation.
>
> It is understandable that there is a perception that the mail from the ab=
ove
> email address appears to be discarded or moderated. =A0If the escalation =
path
> is not working to your satisfaction, I suggest contacting the General Are=
a
> Director ( gen-ads@tools.ietf.org ).
>
> Regards,
> -sm

As I mentioned on May 5th, the IETF has a trouble reporting mechanism,
action@ietf.org (or  ietf-action@ietf.org , they both alias to the
same people).

Has this been reported there ? Bringing in Russ is not appropriate if
the basic reporting process
has not been followed.

Regards
Marshall

From msk@cloudmark.com  Tue May  8 09:37:49 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8553221F8567 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 09:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFeX7rbiMENl for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 09:37:48 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id D7F5221F8564 for <ietf@ietf.org>; Tue,  8 May 2012 09:37:48 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id 7UeG1j0010as01C01UeGH8; Tue, 08 May 2012 09:38:16 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=Xth4yC59 c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=LvckAehuu68A:10 a=oUkRCPef0LAA:10 a=zutiEJmiVI4A:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=pGLkceISAAAA:8 a=8EpMBZrOAAAA:8 a=SClJIqFMAAAA:8 a=9NGZVl_YAAAA:8 a=48vgC7mUAAAA:8 a=3zmTlSqYKXTgQThR2fwA:9 a=YBuBk023CSrA3giPuDQA:7 a=QEXdDO2ut3YA:10 a=MSl-tDqOz04A:10 a=ByZQ1NMAAcIA:10 a=HH8gw8bN0psA:10 a=I9DA3x22SqsA:10 a=lZB815dzVvQA:10 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Tue, 8 May 2012 09:37:48 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discuss <ietf@ietf.org>
Subject: RE: [Fwd: IETF posting delays]
Thread-Topic: [Fwd: IETF posting delays]
Thread-Index: AQHNLQ7GCJgRKVCXVk2CJQq2BzuKJ5bAFq7A
Date: Tue, 8 May 2012 16:37:47 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392811955D@exch-mbx901.corp.cloudmark.com>
References: <4FA90503.2070109@gmail.com>
In-Reply-To: <4FA90503.2070109@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336495096; bh=hzohw0Bkf5XfVrMsBBm4pF+8vWEUJu7D4PQd6MV3mXY=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=uoVH6mCiqsb6dKr2ofAi3/mXTdsX85QAbe7Ar4fOyLE9seaiZEpq7BaeADuyGcstH sX0TPqD5kPw9WiBSqRwI+CX02+ukTGV1xz/NIzt4dqoqtGwaaHRZ9mlSHl55PpcLkx qNCz+/mjo/3iPGZ74ydOptGJ9LfzkRVPmOI42DCY=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 16:37:49 -0000

PiAtLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQo+IFN1YmplY3Q6IFtGd2Q6IFJl
OiBbSUVURl0gUmU6IElFVEYgcG9zdGluZyBkZWxheXNdDQo+IERhdGU6IFR1ZSwgMDggTWF5IDIw
MTIgMDc6MzE6MTMgLTA0MDANCj4gRnJvbTogSGVjdG9yIFNhbnRvcyA8c2FudDk0NDJAZ21haWwu
Y29tPg0KPiBUbzogV2FycmVuIEt1bWFyaSA8d2FycmVuQGt1bWFyaS5uZXQ+DQo+IENDOiBTTSA8
c21AcmVzaXN0b3IubmV0PiwgSm9obiBDIEtsZW5zaW4gPGpvaG4taWV0ZkBqY2suY29tPiwgaWV0
Zi0NCj4gYWN0aW9uQGlldGYub3JnDQo+IA0KPiBJJ20gZ2l2aW5nIHVwLiBOb3cgdXNpbmcgZ21h
aWwgYWNjb3VudC4NCj4gDQo+IEFzIHlvdSBjYW4gc2VlIHdpdGggdGhlIHJlc3BvbnNlIGJlbG93
IHRvIFdhcnJlbiBhbmQgY2M6IE1hcnksIEpvaG4sDQo+IGFuZCB0aGUgSUVURiBsaXN0LCB3YXMg
c2VudCBsYXN0IG5pZ2h0IGF0IE1heSA3LCAyMzowMS4gIE15IE1UQQ0KPiB0cmFuc3BvcnQgbG9n
cyBzaG93IGl0IHdhcyBzZW50IHRvIGFsbCBmb3VyLCBzbyBJIGFtIHByZXN1bWluZyB0aGUNCj4g
ZGlyZWN0IG1haWwgd2FzIHJlY2VpdmVkIGFuZCBwZXJoYXBzIHlvdSBjYW4gY29uZmlybSB5b3Ug
cmVjZWl2ZWQgaXQuDQo+IFlldCwgbm90IHBvc3RlZCBvbiB0aGUgbGlzdCwgbm90IG9uIHRoZSBJ
RVRGIGFyY2hpdmUsIG15IGNvcHkgbmV2ZXINCj4gc2VudC4NCj4gDQo+IFRoYXRzIG5vdyB0d28g
c3VibWlzc2lvbnMgYnkgYSBzdWJzY3JpYmVkIG1lbWJlciB0aGF0IGFyZSBpbiBsYSBsYQ0KPiBs
YW5kLiAgU28gaXRzIG5vdCB3b3JraW5nLg0KPiANCj4gVGhlIElFVEYgd2FudHMgdG8gaW1wcm92
ZSBpdHMgaW1hZ2Ugd2l0aCB0aGUgbWlub3JpdHkgZW5naW5lZXJpbmcNCj4gY29tbXVuaXR5PyAg
V2FudHMgdG8gcmVkdWNlIHRoZSBub2lzZT8gV2FudHMgdG8gaW5jcmVhc2UgSUVURiBtZWV0aW5n
DQo+IGF0dGVuZGFuY2U/DQo+IA0KPiBJTU8sIHRoaXMgcG9saWN5IGluIHBsYWNlIGZvciBzdWJz
Y3JpYmVkIG1lbWJlciBtYWlsIGhvbGRpbmcgYW5kDQo+IGZpbHRlcmluZyB3aGVuIHRoZSBtYWls
IGlzIG5ldmVyIHBvc3RlZCwgIG5lZWRzIHRvIGJlIHNlcmlvdXNseQ0KPiByZXZpZXdlZC4gICBU
aGUgcGVyY2VwdGlvbiBhbW91bnRzIHRvIG5vdGhpbmcgZWxzZSBidXQgZGVsaWJlcmF0ZQ0KPiBj
ZW5zb3JzaGlwLCBlc3BlY2lhbGx5IHdoZW4gdGhlIG1haWwgYXBwZWFycyB0byBiZSBkaXNjYXJk
ZWQuDQo+IA0KPiBJIGhhdmUgY3VycmVudCBwbGFucyBhbmQgYnVkZ2V0aW5nIHRvIGF0dGVuZCB0
aGUgbmV4dCB0d28gSUVURg0KPiBNZWV0aW5ncy4gSSBoYXZlIHNlY29uZCB0aG91Z2h0cyBub3cs
IGRyb3BwaW5nIG15IEktRCB3b3JrIGFuZCBqdXN0DQo+IHN0YXkgb3V0IG9mIHRoZSBJRVRGIHNj
ZW5lLiBXaG8gbmVlZHMgdGhlIHN0cmVzcyENCg0KQ291bGQgd2UgcGVyaGFwcyB0cnkgYmVpbmcg
YSBsaXR0bGUgYml0IHBhdGllbnQgYW5kIGRlYnVnZ2luZyB0aGUgcHJvYmxlbSBpbiBhIGNvLW9w
ZXJhdGl2ZSBtYW5uZXIgYmVmb3JlIGxvYmJpbmcgcmhldG9yaWNhbCBncmVuYWRlcyBhdCB0aGUg
cGVvcGxlIHdobyBjYW4gc29sdmUgdGhlIHByb2JsZW0geW91J3JlIGhhdmluZz8NCg0KQmVjYXVz
ZSB0aGF0IHdvdWxkIGJlIGF3ZXNvbWUuDQoNCi1NU0sNCg==

From randy@psg.com  Tue May  8 09:49:20 2012
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 CA7F821F855B for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 09:49: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 8aE01GeWNqNJ for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 09:49:20 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 382AA21F852A for <ietf@ietf.org>; Tue,  8 May 2012 09:49:20 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SRnbC-000F05-Ky for ietf@ietf.org; Tue, 08 May 2012 16:49:18 +0000
Date: Tue, 08 May 2012 09:49:18 -0700
Message-ID: <m2obpy4nzl.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Discuss <ietf@ietf.org>
Subject: Re: [Fwd: IETF posting delays]
In-Reply-To: <9452079D1A51524AA5749AD23E00392811955D@exch-mbx901.corp.cloudmark.com>
References: <4FA90503.2070109@gmail.com> <9452079D1A51524AA5749AD23E00392811955D@exch-mbx901.corp.cloudmark.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 16:49:21 -0000

i have already plonked the troller who wasted my time.  could we drop
this thread?

randy

From glen@amsl.com  Tue May  8 11:13:24 2012
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93F8A21F8526 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 11:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.087
X-Spam-Level: 
X-Spam-Status: No, score=-101.087 tagged_above=-999 required=5 tests=[AWL=-1.099, BAYES_00=-2.599, FAKE_REPLY_C=2.012, J_CHICKENPOX_23=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 uDv1wI-31HNh for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 11:13:24 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE9621F84FF for <ietf@ietf.org>; Tue,  8 May 2012 11:13:24 -0700 (PDT)
Received: by c8a.amsl.com (Postfix, from userid 1000) id 061CB12C84B; Tue,  8 May 2012 11:13:22 -0700 (PDT)
Date: Tue, 8 May 2012 11:13:22 -0700
From: Glen <glen@amsl.com>
To: ietf@ietf.org
Subject: Re: IETF posting delays
Message-ID: <20120508181322.GA11635@amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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, 08 May 2012 18:13:24 -0000

On Tue May 08 04:31:41 2012, sant9442@gmail.com wrote:
> I'm giving up. Now using gmail account.
> As you can see with the response below to Warren and cc: Mary, John, 
> and the IETF list, was sent last night at May 7, 23:01.  My MTA 
> transport logs show it was sent to all four, so I am presuming the 
> direct mail was received and perhaps you can confirm you received it. 
> Yet, not posted on the list, not on the IETF archive, my copy never sent.

As the above ticket was cc'ed to the IETF community list, I am cc'ing our
resolution report to the list as well.

Dear Mr. Santos:

This is the first report we've received at IETF-ACTION on this problem.

The problem with these two messages was easy to identify.  Your two email
messages were triggering the spamassassin scoring system used by the IETF,
and causing your mail to be discarded as spam.

Although I do not have a detail log of the report for your mail, I would
think that the phrase "GO NY RANGERS" in your message contributed to the
elevated spam score.  Such things are generally interpreted as spam phrases
by spam filters, especially in environments like the IETF's where such
phrases are neither relevant nor expected.

This is an easy problem to solve.  I have whitelisted your address(es) so
that you will not have this problem again.

And, I can only stress that, in the future, when you have problems of this
type, you will get much faster resolution if you file a report with
IETF-ACTION, as directed on the IETF website, rather than going to the IETF
discussion list.  Had you done so in this case, and in the other cases I now
see you've discussed on the IETF discussion list, these problems could have
been resolved and/or answered before turning into what I now see has become
a major thread.  Please see the IETF website at
http://www.ietf.org/contact-the-ietf.html and
http://www.ietf.org/secretariat.html for further information about the
correct ways to report problems encountered with IETF systems.

I trust this information is helpful.  If you have further questions or
problems, please direct a new message to:
          ietf-action@ietf.org
and a member of the secretariat staff will assist you.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)

From touch@isi.edu  Tue May  8 16:19:33 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B941F21F8491 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.503
X-Spam-Level: 
X-Spam-Status: No, score=-103.503 tagged_above=-999 required=5 tests=[AWL=-0.904, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wtuLUeFrQxT for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:19:33 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3819C21F848F for <ietf@ietf.org>; Tue,  8 May 2012 16:19:33 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q48NJR5s023967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 May 2012 16:19:27 -0700 (PDT)
Message-ID: <4FA9A9FE.7050307@isi.edu>
Date: Tue, 08 May 2012 16:19:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: a favor from the list about Jon Postel
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2012 23:19:33 -0000

Hi, all,

My apologies for contacting this list with a non-IETF issue, but since 
this community knew Jon well, I'm asking for its help (among others).

---

There is a Facebook page that falsely implies being owned by Jon Postel:

https://www.facebook.com/jon.postel

Facebook has declined requests from Jon's family to have this page removed.

To everyone on this list:

PLEASE do not "LIKE" or interact with this page. Jon passed in 1998, as 
you know, 5 years before Facebook ever existed. He never had a page on 
this or any other social networking site, and whomever is running this 
should stop misrepresenting themselves.

If anyone here can help, please let me know.

Joe
touch@isi.edu

From fred@cisco.com  Tue May  8 16:36:19 2012
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 A30189E8001 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.602
X-Spam-Level: 
X-Spam-Status: No, score=-110.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 TDKOnOGd0ccu for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:36:18 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id DE74321F853B for <ietf@ietf.org>; Tue,  8 May 2012 16:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=900; q=dns/txt; s=iport; t=1336520178; x=1337729778; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=qLIb4U3x5kuzsKWJQBrYF6Tbie0ksBvS1Xnixf0ZGxM=; b=a1haPHHlz4o2UHyCHKD1y/UKO+Rb3VLxAWfe/Y4BlNPqVYfvN7FXHUXW 9sSpWGYKpYgQ3Hyk4PQYnbmWTMWa00rA+YYeOg+79Gitz45Ug+DsszUV7 dE8SkdGHYfT7Vys5cLka6y4meZLBWotTD1fLb0rBdPfQZNDlfKt+Z8Pww 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALOsqU+rRDoG/2dsb2JhbABEDrMrgQeCDAEBAQMBEgEnPwULC0ZXBhMUDodnBAyaeqATBIsDhS9jBIhkhziFYoV2iGOBaYIwVw
X-IronPort-AV: E=Sophos;i="4.75,553,1330905600"; d="scan'208";a="40929374"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 08 May 2012 23:36:18 +0000
Received: from dhcp-10-59-1-30.cisco.com (sjc-vpn7-1468.cisco.com [10.21.149.188]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q48NaH3d031896; Tue, 8 May 2012 23:36:17 GMT
Received: from [127.0.0.1] by dhcp-10-59-1-30.cisco.com (PGP Universal service); Tue, 08 May 2012 18:36:18 -0500
X-PGP-Universal: processed; by dhcp-10-59-1-30.cisco.com on Tue, 08 May 2012 18:36:18 -0500
Subject: Re: a favor from the list about Jon Postel
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4FA9A9FE.7050307@isi.edu>
Date: Tue, 8 May 2012 18:35:55 -0500
Message-Id: <CB433728-3715-4B1A-9827-A64B760F18F8@cisco.com>
References: <4FA9A9FE.7050307@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
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, 08 May 2012 23:36:19 -0000

question:

would it be helpful to report or block the page?

On May 8, 2012, at 6:19 PM, Joe Touch wrote:

> Hi, all,
>=20
> My apologies for contacting this list with a non-IETF issue, but since =
this community knew Jon well, I'm asking for its help (among others).
>=20
> ---
>=20
> There is a Facebook page that falsely implies being owned by Jon =
Postel:
>=20
> https://www.facebook.com/jon.postel
>=20
> Facebook has declined requests from Jon's family to have this page =
removed.
>=20
> To everyone on this list:
>=20
> PLEASE do not "LIKE" or interact with this page. Jon passed in 1998, =
as you know, 5 years before Facebook ever existed. He never had a page =
on this or any other social networking site, and whomever is running =
this should stop misrepresenting themselves.
>=20
> If anyone here can help, please let me know.
>=20
> Joe
> touch@isi.edu


From touch@isi.edu  Tue May  8 16:38:34 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B180C9E800E for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.485
X-Spam-Level: 
X-Spam-Status: No, score=-103.485 tagged_above=-999 required=5 tests=[AWL=-0.886, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTGIxQz8Edqr for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:38:34 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA5A21F8542 for <ietf@ietf.org>; Tue,  8 May 2012 16:38:34 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q48NcRNh026857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 May 2012 16:38:27 -0700 (PDT)
Message-ID: <4FA9AE72.8030904@isi.edu>
Date: Tue, 08 May 2012 16:38:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: a favor from the list about Jon Postel
References: <4FA9A9FE.7050307@isi.edu> <CB433728-3715-4B1A-9827-A64B760F18F8@cisco.com>
In-Reply-To: <CB433728-3715-4B1A-9827-A64B760F18F8@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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, 08 May 2012 23:38:34 -0000

On 5/8/2012 4:35 PM, Fred Baker wrote:
> question:
>
> would it be helpful to report or block the page?

I and Jon's family have tried, to no avail thus far.

Joe

>
> On May 8, 2012, at 6:19 PM, Joe Touch wrote:
>
>> Hi, all,
>>
>> My apologies for contacting this list with a non-IETF issue, but since this community knew Jon well, I'm asking for its help (among others).
>>
>> ---
>>
>> There is a Facebook page that falsely implies being owned by Jon Postel:
>>
>> https://www.facebook.com/jon.postel
>>
>> Facebook has declined requests from Jon's family to have this page removed.
>>
>> To everyone on this list:
>>
>> PLEASE do not "LIKE" or interact with this page. Jon passed in 1998, as you know, 5 years before Facebook ever existed. He never had a page on this or any other social networking site, and whomever is running this should stop misrepresenting themselves.
>>
>> If anyone here can help, please let me know.
>>
>> Joe
>> touch@isi.edu
>

From sm@resistor.net  Tue May  8 16:51:58 2012
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 D51529E800F for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:51:58 -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 lH4q1u-9U+Qu for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 16:51:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD4069E800E for <ietf@ietf.org>; Tue,  8 May 2012 16:51:56 -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 q48NpnXM022601; Tue, 8 May 2012 16:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336521115; i=@resistor.net; bh=gcqBgH2E4T3l/pS4njpk/peZh90QEAWAiciz9aSsq3A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZEanEujIoWUY9a99xvzNgh0OWe0Iv0Xr/JWVRkGeSWnsOLtf3LYcI/oouze8Y7Oox 7TxDXOUlJ3aJPBFosN72a1TZixewudP3+LFX0GkyERfFAw6H2coeCFOILf77YzSeh5 0XRANgMDt43UuUGWQPneqvKv5hrZKauX4NAbD7vc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336521115; i=@resistor.net; bh=gcqBgH2E4T3l/pS4njpk/peZh90QEAWAiciz9aSsq3A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=D7N8qIg0PZiMU09sd/F9Gy2Ik0IM5M6IwJ5desSngQmpiwmaUQslqBgEqnVSAGuYh we5sH2aq92mpTCa5YcDsAqu7rZBwWp4GLgz5WYaKcD31QXkH/f8d3tBfX5ralRnby4 4vI/OSGy8APNYoCGHNAK6wXpeKch4pBnX2U3/b3g=
Message-Id: <6.2.5.6.2.20120508163721.0a3d7190@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 May 2012 16:51:11 -0700
To: Joe Touch <touch@isi.edu>
From: SM <sm@resistor.net>
Subject: Re: a favor from the list about Jon Postel
In-Reply-To: <4FA9A9FE.7050307@isi.edu>
References: <4FA9A9FE.7050307@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 08 May 2012 23:51:59 -0000

Hi Joe,
At 16:19 08-05-2012, Joe Touch wrote:
>There is a Facebook page that falsely implies being owned by Jon Postel:

See 
http://www.scribd.com/gawker/d/81877124-Abuse-Standards-6-2-Operation-Manual

There are a few ISOC people in the photos ...

Regards,
-sm  


From dwm@xpasc.com  Tue May  8 18:08:35 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5193F11E8085 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.096
X-Spam-Level: 
X-Spam-Status: No, score=-3.096 tagged_above=-999 required=5 tests=[AWL=-1.789, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jau-a-byoNIX for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:08:34 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id E2AAE11E8080 for <ietf@ietf.org>; Tue,  8 May 2012 18:08:33 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id F342540282 for <ietf@ietf.org>; Wed,  9 May 2012 01:08:32 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q490NlIf009335 for <ietf@ietf.org>; Tue, 8 May 2012 17:23:47 -0700
Date: Tue, 8 May 2012 17:23:47 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: a favor from the list about Jon Postel
In-Reply-To: <4FA9A9FE.7050307@isi.edu>
Message-ID: <alpine.LRH.2.01.1205081719210.6210@egate.xpasc.com>
References: <4FA9A9FE.7050307@isi.edu>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD7Hu1vr-481808X
X-CLX-Spam: false
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: Wed, 09 May 2012 01:08:35 -0000

I don't think it helps the case against this page to have "Likes" by
W3C, Tim Berners-Lee, Vint Cerf, ARIN and ICANN ... of course,
there is no reason for me to know that those aren't frauds as well.

On Tue, 8 May 2012, Joe Touch wrote:

> Hi, all,
> 
> My apologies for contacting this list with a non-IETF issue, but since this
> community knew Jon well, I'm asking for its help (among others).
> 
> ---
> 
> There is a Facebook page that falsely implies being owned by Jon Postel:
> 
> https://www.facebook.com/jon.postel
> 
> Facebook has declined requests from Jon's family to have this page removed.
> 
> To everyone on this list:
> 
> PLEASE do not "LIKE" or interact with this page. Jon passed in 1998, as you
> know, 5 years before Facebook ever existed. He never had a page on this or any
> other social networking site, and whomever is running this should stop
> misrepresenting themselves.
> 
> If anyone here can help, please let me know.
> 
> Joe
> touch@isi.edu
> 

From bob.hinden@gmail.com  Tue May  8 18:42:52 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B64311E8095 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:42:52 -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 t05NFAfFsdEG for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:42:52 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 047EB11E8094 for <ietf@ietf.org>; Tue,  8 May 2012 18:42:51 -0700 (PDT)
Received: by yenq13 with SMTP id q13so2683175yen.31 for <ietf@ietf.org>; Tue, 08 May 2012 18:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=0ToXuLbm/UaaN3miLnR072d4Jy5uogWqMge6ClStP88=; b=fobJdX+E7VtXQoKrEbHuoaWLSykzJjcfvuj+mVRQJmaGWq8FZdeeWG/L/1MyVVy2MG dDUb/M1VXS+HIIwFA9O83BLTAGmT4zWU3kmeHnFvW9FqvWUwy5TYSMIU5e+fKks/Lv70 zazDlfZR9jptc6s2OyQVpcSw/TnvGYsvTKq6FtqxV8dKvu87FPReHhUWxhooGUEvGV+a AkKDLsk908M8YKR4usmki14Ef8Idft9pgojtR0YmoBrlH/2h+auojnsfTufLZ24Dc474 w3pSiKWYkR6/JmnKudDlkS4TaJ3C9+v6nL5jnNhraY/GryVZCNy/1TQcPMP63agUdmDY O+Zg==
Received: by 10.50.106.162 with SMTP id gv2mr8827737igb.40.1336527771302; Tue, 08 May 2012 18:42:51 -0700 (PDT)
Received: from [142.131.211.148] ([142.131.211.148]) by mx.google.com with ESMTPS id de2sm9842684igc.4.2012.05.08.18.42.50 (version=SSLv3 cipher=OTHER); Tue, 08 May 2012 18:42:50 -0700 (PDT)
Subject: Re: a favor from the list about Jon Postel
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4FA9A9FE.7050307@isi.edu>
Date: Tue, 8 May 2012 21:42:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com>
References: <4FA9A9FE.7050307@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.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: Wed, 09 May 2012 01:42:52 -0000

Joe,

On May 8, 2012, at 7:19 PM, Joe Touch wrote:

> Hi, all,
>=20
> My apologies for contacting this list with a non-IETF issue, but since =
this community knew Jon well, I'm asking for its help (among others).
>=20
> ---
>=20
> There is a Facebook page that falsely implies being owned by Jon =
Postel:
>=20
> https://www.facebook.com/jon.postel

I just tried going to this page and it says it doesn't exist.  Has the =
problem been fixed?

Bob

>=20
> Facebook has declined requests from Jon's family to have this page =
removed.
>=20
> To everyone on this list:
>=20
> PLEASE do not "LIKE" or interact with this page. Jon passed in 1998, =
as you know, 5 years before Facebook ever existed. He never had a page =
on this or any other social networking site, and whomever is running =
this should stop misrepresenting themselves.
>=20
> If anyone here can help, please let me know.
>=20
> Joe
> touch@isi.edu


From michel@arneill-py.sacramento.ca.us  Tue May  8 18:46:53 2012
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 64A8A11E808C for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=0.093,  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 IhRxNx8H9LX7 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 18:46: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 E431111E8087 for <ietf@ietf.org>; Tue,  8 May 2012 18:46:52 -0700 (PDT)
Content-class: urn:content-classes:message
Subject: RE: a favor from the list about Jon Postel
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 8 May 2012 18:46:52 -0700
Message-ID: <392CB277BC2EAE4FB83C1206954BA6CEFAF6@newserver.arneill-py.local>
In-Reply-To: <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com>
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: a favor from the list about Jon Postel
Thread-Index: Ac0thRPFNsBY3k5VSvqSSn8Ia5IzLwAABkew
References: <4FA9A9FE.7050307@isi.edu> <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com>
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Bob Hinden" <bob.hinden@gmail.com>, "Joe Touch" <touch@isi.edu>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 01:46:53 -0000

> Bob Hinden wrote:
> I just tried going to this page and it says it
> doesn't exist.  Has the problem been fixed?

It appears so; I went to it earlier in the day and it was up; I saw the
post by Julia Postel asking whoever was putting the page up to contact
the family. I kept the processing of this for later (now) and I get the
page cannot be found too.

Michel.


From scott@kitterman.com  Tue May  8 19:04:46 2012
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 DA08311E8080 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 19:04: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8f2-xK+g0LPa for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 19:04:46 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 9941911E8074 for <ietf@ietf.org>; Tue,  8 May 2012 19:04:45 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 1FC5420E40D0; Tue,  8 May 2012 22:04:44 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1336529084; bh=i5hAHIyomzTHpy4rVvmypcPY3df2Q4p4BTVsJaEkE04=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=Znx149ZqjWyALjN83yKVVuFdFhAPDK0vOW46Fcob8g0A9VnkzbT9wFGzz9VgUenKV b41TA0sWdcuVr4iDbP3l2StNXaHyv+pMm40ZASAD2htcqNd0hE5mbk/J9rgGnOBtqK SBQi208OPDYPXGD+bauprqGVLe9sERYFMPVJar1k=
Received: from scott-latitude-e6320.localnet (unknown [12.50.158.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3199320E40B9;  Tue,  8 May 2012 22:04:42 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Date: Tue, 08 May 2012 22:04:30 -0400
Message-ID: <7750789.HxqQGoXypG@scott-latitude-e6320>
User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic-pae; KDE/4.8.2; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.com>
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <a80ed582-27a1-4669-acf5-782b4f342b04@email.android.com> <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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: Wed, 09 May 2012 02:04:47 -0000

On Tuesday, May 08, 2012 06:23:46 AM Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Scott Kitterman
 Sent: Monday, May 07, 2012 10:49 PM
> > To: ietf@ietf.org
> > Subject: RE: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source
> > Ports in ARF Reports) to Proposed Standard
 
> > 
> > >If all one is doing is figuring out why something like a DKIM signature
> > >failed on an otherwise legitimate message, then I agree the source port
> > >isn't a useful input to that work.  In fact, as far as DKIM goes, the
> > >source IP address is probably not useful either.
> > >
> > >If, however, one is trying to track down the transmission of fraudulent
> > >email such as phishing attacks, source ports can be used to identify
> > >the perpetrator more precisely when compared to logs.  Support for this
> > >latter use case is why I believe RECOMMENDED is appropriate.
> > 
> > 
> > Which is exactly the case (abuse report) the second to last paragraph
> > takes care of.  I agree RECOMMENDED is appropriate there and you have
> > it there.
> > 
> > For auth failure analysis I read you as agreeing it's not needed.
> > There are some authorization methods that use IP address, so I don't
> > think that for auth failure reports inclusion of IP address and source
> > port are comparable.
> > 
> > Based on your response, I don't understand your objection to dropping
> > the RECOMMENDS for auth failure reports and keeping it  for abuse
> > reports?
> 
> 
> I don't think it's possible for software to identify correctly a case of an
> accidental authentication failure versus detected fraud.  If it were, then
> I'd agree that for the simple authentication failure case the source port
> isn't useful.
 
Then why did we bother with a separate type or report for authentication 
failure?  Presumably we believe systems can have criteria for "I'm sending 
this because the message is abusive" versus "I'm sending this because it 
failed $authentication_type".

> In the absence of that capability, isn't it better to give the investigating
> user as much information as possible to use in correlation of logs and
> such?

Personally, in the forensic work I've done I've found things like mail queue 
IDs a lot more important than source port.  There is lots of information that 
would be useful for an investigation.  On this basis, I could see MAY include 
source port on auth failure reports, but I think making it RECOMMENDED on the 
basis of it may be useful is justified.

Scott K

From paul@cypherpunks.ca  Tue May  8 19:19:25 2012
Return-Path: <paul@cypherpunks.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF4C21F8483 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 19:19: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gl2kiP9M2aWX for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 19:19:24 -0700 (PDT)
Received: from letoams.cypherpunks.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id B59A321F8476 for <ietf@ietf.org>; Tue,  8 May 2012 19:19:24 -0700 (PDT)
Received: by letoams.cypherpunks.ca (Postfix, from userid 500) id 34D8A853FC; Tue,  8 May 2012 22:09:50 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by letoams.cypherpunks.ca (Postfix) with ESMTP id 28C9D853FB; Tue,  8 May 2012 22:09:50 -0400 (EDT)
Date: Tue, 8 May 2012 22:09:50 -0400 (EDT)
From: Paul Wouters <paul@cypherpunks.ca>
X-X-Sender: paul@bofh.nohats.ca
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: a favor from the list about Jon Postel
In-Reply-To: <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com>
Message-ID: <alpine.LFD.2.02.1205082144320.18036@bofh.nohats.ca>
References: <4FA9A9FE.7050307@isi.edu> <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com>
User-Agent: Alpine 2.02 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 02:19:25 -0000

On Tue, 8 May 2012, Bob Hinden wrote:

>> https://www.facebook.com/jon.postel
>
> I just tried going to this page and it says it doesn't exist.  Has the problem been fixed?

Looks like it. An hour ago i could still report the page, which I did
(and prob many more?)

Paul

From msk@cloudmark.com  Tue May  8 20:14:21 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8766B11E8079 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 20:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.623
X-Spam-Level: 
X-Spam-Status: No, score=-102.623 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 8-TRMJQCvBv5 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 20:14:20 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id E230C11E8074 for <ietf@ietf.org>; Tue,  8 May 2012 20:14:20 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id 7fE91j0010as01C01fE9VW; Tue, 08 May 2012 20:14:09 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=R/iB6KtX c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=ldJM1g7oyCcA:10 a=YfYFAX1pRpwA:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=48vgC7mUAAAA:8 a=OlMI6XHdcPpTm43xq40A:9 a=yG1VNaFF4NKdj6terSsA:7 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Tue, 8 May 2012 20:14:09 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Scott Kitterman <scott@kitterman.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Topic: Last Call: <draft-kucherawy-marf-source-ports-03.txt> (Source Ports in ARF Reports) to Proposed Standard
Thread-Index: AQHNLKHAkXDvdhJ2jUSCN0WTYs7sLZa/SMQAgACP5ID//5MiMIABwG4A//+c6MA=
Date: Wed, 9 May 2012 03:14:08 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392811A51A@exch-mbx901.corp.cloudmark.com>
References: <20120507195025.19948.3410.idtracker@ietfa.amsl.com> <a80ed582-27a1-4669-acf5-782b4f342b04@email.android.com> <9452079D1A51524AA5749AD23E003928118D24@exch-mbx901.corp.cloudmark.com> <7750789.HxqQGoXypG@scott-latitude-e6320>
In-Reply-To: <7750789.HxqQGoXypG@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1336533249; bh=G90L6b/yfqzEQbOTwYoZPbxvvm+Mf8LQ/ASrP8v0Ws0=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=wDsC4ZhVa0n5g3fygTvAzW5T+SpfUiU16ExPOVXMDxQQ0JVWCmKMfopkPWEXzK+72 UOvvz9g52H9H/W/LiGEaDEOv/V5WNwE8J7XWaDVsQ3bkfq6AN+EZSZKJyRFyl8NG0P Nl3EVeU2Iqfzssozes91evUve1fkPDzLY7lmZTdY=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 03:14:21 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Tuesday, May 08, 2012 7:05 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-kucherawy-marf-source-ports-03.txt>
> (Source Ports in ARF Reports) to Proposed Standard
>=20
> > In the absence of that capability, isn't it better to give the
> > investigating user as much information as possible to use in
> > correlation of logs and such?
>=20
> Personally, in the forensic work I've done I've found things like mail
> queue IDs a lot more important than source port.  There is lots of
> information that would be useful for an investigation.  On this basis,
> I could see MAY include source port on auth failure reports, but I
> think making it RECOMMENDED on the basis of it may be useful is
> justified.

If a spam bot connects to your MTA and sends a message in, the only queue I=
D you have is the one your own MTA generated.  How will that be useful trac=
ing the spam back to the very machine that generated it?

RFC6302 talks about why this is important a lot more than this document doe=
s.

-MSK

From mail@sabahattin-gucukoglu.com  Tue May  8 20:34:37 2012
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 517A411E8089 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 20:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.942
X-Spam-Level: 
X-Spam-Status: No, score=0.942 tagged_above=-999 required=5 tests=[AWL=-1.630,  BAYES_50=0.001, GAPPY_SUBJECT=1.02, HOST_MISMATCH_COM=0.311, 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 UNIPbB+s82rd for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 20:34:36 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (mintaka.sabahattin-gucukoglu.com [IPv6:2001:470:babd::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7141311E8074 for <ietf@ietf.org>; Tue,  8 May 2012 20:34:36 -0700 (PDT)
Received: by Mintaka.sabahattin-gucukoglu.com (Postfix, from userid 1000) id EDE2710403B; Wed,  9 May 2012 04:34:35 +0100 (BST)
Received: from [192.168.1.28] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) (using SMTP over TLS) by mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Wed, 09 May 2012 04:34:34 +0100
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Finally, It's The Year Of Linux^H^H^H^H^HIPv6
Date: Wed, 9 May 2012 04:34:32 +0100
Message-Id: <2F5949CF-7769-4E15-9FF9-C12EB168947D@sabahattin-gucukoglu.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1339126475.eebd54@sabahattin-gucukoglu.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 May 2012 03:34:37 -0000
X-List-Received-Date: Wed, 09 May 2012 03:34:37 -0000

I really shouldn't, so soon after his last inflammatory rant, but here:
http://www.theregister.co.uk/2012/05/08/ipv6_coming_next_month/

<Quote>
One month from now, World IPv6 Launch Day with be upon us. Numerous =
online services will be enabling IPv6 and leaving it on. AAAA records =
will be published, and those of us with IPv6 enabled systems will start =
to use IPv6 preferentially to IPv4. But what does this all mean? For the =
short term at least, the truth is "not much". =85
</quote>

Ignoring the obvious error with the preceding quote, on this occasion, =
he does at least appear to have one thing right: most people really =
aren't all that motivated, in the short term.  The apathy continues a =
pace, and most of the industry is obliged to help in turn by doing =
almost nothing.  Whether it will after June 6 is an open question, but I =
don't imagine he'll be far off there, either.  What's important here, I =
think, is simply that the desire to have IPv6 deployed and running is =
outpaced by people's ongoing desire to ignore it.  "Networking nerds" =
are happy because IPv6 at long last has a sporting chance.  Everyone =
else just wants less of the hype. *Grumble*

Cheers,
Sabahattin

From brian.e.carpenter@gmail.com  Tue May  8 23:52:07 2012
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 5E1D621F8628 for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 23:52:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.575
X-Spam-Level: 
X-Spam-Status: No, score=-101.575 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 PSAMxYITAXqN for <ietf@ietfa.amsl.com>; Tue,  8 May 2012 23:52:06 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7136E21F8627 for <ietf@ietf.org>; Tue,  8 May 2012 23:52:06 -0700 (PDT)
Received: by eabd1 with SMTP id d1so1648152eab.31 for <ietf@ietf.org>; Tue, 08 May 2012 23:52:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/y0YLsItMWhcFSZ6hftn/zdeleIhsWg2IilB/92bI6M=; b=dY/YmYRif41G41BPxpoCoUCy75xCRlrDMDMha4moVUcWkNViEM9FDEDBy/mNvZ2QkK kCL55lLIl2zIv7KSbSxDMPp7lARpMpjVKWgfPTOIOnYH4bYijBNk2cbfXSPGxTvpCJsW 5h+gM5F2yL1APjwrC4YRlSwuWDuT4s3tY1TiTxSRmUDNeRSycCh0Sf5RCmd6ntNsglVO whsBkjaA7rH3XNeX/Y+3rYSKn2M4Lj+IGPj7ySINDtxKXYvB/Gbs5M6ICvFcOST9vRcF lDBSC3/C/aMF6fRvqlrD3bXj9X4ZD841gcYW4NKUz9XR6aDOj9TcrljZFuyoFMJsqDcR gRnA==
Received: by 10.213.157.2 with SMTP id z2mr309864ebw.149.1336546325542; Tue, 08 May 2012 23:52:05 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-118.as13285.net. [2.102.216.118]) by mx.google.com with ESMTPS id e56sm7922697eea.11.2012.05.08.23.52.03 (version=SSLv3 cipher=OTHER); Tue, 08 May 2012 23:52:04 -0700 (PDT)
Message-ID: <4FAA140B.4010703@gmail.com>
Date: Wed, 09 May 2012 07:51:55 +0100
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: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>
In-Reply-To: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 06:52:07 -0000

I'd like to be reassured that this has been carefully reviewed
by the IETF counsel and the IETF Trust. In particular I would
be interested in its possible interaction with the IETF's
liability insurance.

>    Any IETF participant can call for sanctions to be applied to anyone
>    they believe has violated the IETF's IPR policy. This can be done by
>    sending email to the appropriate IETF mailing list.  

That seems reasonable, but publishing such a belief without having the
wording checked by a libel lawyer might be risky. I think the draft
should state that a call for sanctions should be based on factual
evidence and not on "belief". How about

   Any IETF participant can call for sanctions to be applied to anyone
   shown to have violated the IETF's IPR policy.  This can be done by
   sending email to the appropriate IETF mailing list, including a
   a short summary of the relevant facts and events.

Regards
   Brian Carpenter

On 2012-05-07 22:56, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
>   <draft-farrresnickel-ipr-sanctions-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 2012-06-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 developed and documented policies that govern the
>    behavior of all IETF participants with respect to Intellectual
>    Property Rights (IPR) about which they might reasonably be aware.
> 
>    The IETF takes conformance to these IPR policies very seriously.
>    However, there has been some ambiguity as to what the appropriate
>    sanctions are for the violation of these policies, and how and by
>    whom those sanctions are to be applied.
> 
>    This document discusses these issues and provides a suite of
>    potential actions that may be taken within the IETF community.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 

From ynir@checkpoint.com  Wed May  9 00:07:58 2012
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 ACA7B21F85B1 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.405
X-Spam-Level: 
X-Spam-Status: No, score=-10.405 tagged_above=-999 required=5 tests=[AWL=0.194, 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 Y35K1NlZRJFc for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:07:57 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7958521F85A8 for <ietf@ietf.org>; Wed,  9 May 2012 00:07:57 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4977rJt023561;  Wed, 9 May 2012 10:07:53 +0300
X-CheckPoint: {4FAA2546-6-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 9 May 2012 10:07:28 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 9 May 2012 10:07:27 +0300
Subject: RE: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions	Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Topic: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions	Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Index: Ac0tsFAgJcRig/VAQeyKHBFnCeXWwQAAdOLQ
Message-ID: <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com>
In-Reply-To: <4FAA140B.4010703@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
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 May 2012 07:07:58 -0000

I think that regardless of how it's worded, the real question is whether li=
ability falls to the person who sent the email (to a public mailing list) o=
r the IETF. The difference between "believe" and "shown" seems minor in com=
parison.=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Bri=
an E Carpenter
Sent: 09 May 2012 09:52
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctio=
ns Available for Application to Violators of IETF IPR Policy) to Informatio=
nal RFC

I'd like to be reassured that this has been carefully reviewed by the IETF =
counsel and the IETF Trust. In particular I would be interested in its poss=
ible interaction with the IETF's liability insurance.

>    Any IETF participant can call for sanctions to be applied to anyone
>    they believe has violated the IETF's IPR policy. This can be done by
>    sending email to the appropriate IETF mailing list. =20

That seems reasonable, but publishing such a belief without having the word=
ing checked by a libel lawyer might be risky. I think the draft should stat=
e that a call for sanctions should be based on factual evidence and not on =
"belief". How about

   Any IETF participant can call for sanctions to be applied to anyone
   shown to have violated the IETF's IPR policy.  This can be done by
   sending email to the appropriate IETF mailing list, including a
   a short summary of the relevant facts and events.

Regards
   Brian Carpenter

On 2012-05-07 22:56, The IESG wrote:
> The IESG has received a request from an individual submitter to=20
> consider the following document:
> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
>   <draft-farrresnickel-ipr-sanctions-05.txt> as Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2012-06-04. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    The IETF has developed and documented policies that govern the
>    behavior of all IETF participants with respect to Intellectual
>    Property Rights (IPR) about which they might reasonably be aware.
>=20
>    The IETF takes conformance to these IPR policies very seriously.
>    However, there has been some ambiguity as to what the appropriate
>    sanctions are for the violation of these policies, and how and by
>    whom those sanctions are to be applied.
>=20
>    This document discusses these issues and provides a suite of
>    potential actions that may be taken within the IETF community.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball
> ot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20

Scanned by Check Point Total Security Gateway.

From brian.e.carpenter@gmail.com  Wed May  9 00:19:15 2012
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 0F1ED21F847C for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:19:15 -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=0.114, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 Wwr8WLDgx1NJ for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:19:14 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id CE1B621F847A for <ietf@ietf.org>; Wed,  9 May 2012 00:19:13 -0700 (PDT)
Received: by werf13 with SMTP id f13so4117857wer.31 for <ietf@ietf.org>; Wed, 09 May 2012 00:19: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=gWsjtWDnrY39GruijPuskN3lHazfrlNX20kaeh3fWlY=; b=zN19/5wOxt4/KDR1i4cjZ92dHn2/WR3z4mK/m0O0agEry9QXI1ylrdByT/2envwx31 cq2pVtpYM8ktoKkk3jTd+BwQ1SX2uznZmjOrXGGl25JsPP6wELniXQkVv0y4SU1b0JXN 0bAsRquXDxCSI/nBj1N5Qw8rCdqHPTgKQ5zJN7JGy9n7N08ANSsdCyOZb1akuUaqD/nP +z74w5iLzV5YvQ2NQzqSVNnGMP2ImKC4XJJi28fYm7kdBVLAfKhwy9JrWFmYvrbIWJ3E lsYQBmqRBtGkONCO+iPG7nrlnCQ1fw5SGgzaq4JT0OOTLskKdcWWMgiE1o2+8COh8RPy y6wQ==
Received: by 10.180.104.168 with SMTP id gf8mr4102430wib.12.1336547952960; Wed, 09 May 2012 00:19:12 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-118.as13285.net. [2.102.216.118]) by mx.google.com with ESMTPS id h8sm6847261wix.4.2012.05.09.00.19.10 (version=SSLv3 cipher=OTHER); Wed, 09 May 2012 00:19:12 -0700 (PDT)
Message-ID: <4FAA1A6A.5070500@gmail.com>
Date: Wed, 09 May 2012 08:19:06 +0100
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: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com>
In-Reply-To: <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com>
Content-Type: text/plain; charset=UTF-8
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, 09 May 2012 07:19:15 -0000

Yoav,

IANAL, but as far as I know libel suits are normally against individuals
(or media outlets such as newspapers). The defence against a libel
suit in the British courts, the most popular jurisdiction for
international libel suits, is factual accuracy. Therefore, I think
the draft should state the need for factual evidence.

And to be clear, there are plenty of precedents for libels originating
outside the UK leading to successful suits in the UK courts, if they
have been received in the UK via the Internet.

Regards
   Brian Carpenter




On 2012-05-09 08:07, Yoav Nir wrote:
> I think that regardless of how it's worded, the real question is whether liability falls to the person who sent the email (to a public mailing list) or the IETF. The difference between "believe" and "shown" seems minor in comparison. 
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: 09 May 2012 09:52
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
> 
> I'd like to be reassured that this has been carefully reviewed by the IETF counsel and the IETF Trust. In particular I would be interested in its possible interaction with the IETF's liability insurance.
> 
>>    Any IETF participant can call for sanctions to be applied to anyone
>>    they believe has violated the IETF's IPR policy. This can be done by
>>    sending email to the appropriate IETF mailing list.  
> 
> That seems reasonable, but publishing such a belief without having the wording checked by a libel lawyer might be risky. I think the draft should state that a call for sanctions should be based on factual evidence and not on "belief". How about
> 
>    Any IETF participant can call for sanctions to be applied to anyone
>    shown to have violated the IETF's IPR policy.  This can be done by
>    sending email to the appropriate IETF mailing list, including a
>    a short summary of the relevant facts and events.
> 
> Regards
>    Brian Carpenter
> 
> On 2012-05-07 22:56, The IESG wrote:
>> The IESG has received a request from an individual submitter to 
>> consider the following document:
>> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
>>   <draft-farrresnickel-ipr-sanctions-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 2012-06-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 developed and documented policies that govern the
>>    behavior of all IETF participants with respect to Intellectual
>>    Property Rights (IPR) about which they might reasonably be aware.
>>
>>    The IETF takes conformance to these IPR policies very seriously.
>>    However, there has been some ambiguity as to what the appropriate
>>    sanctions are for the violation of these policies, and how and by
>>    whom those sanctions are to be applied.
>>
>>    This document discusses these issues and provides a suite of
>>    potential actions that may be taken within the IETF community.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball
>> ot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
> 
> Scanned by Check Point Total Security Gateway.
> 

From ynir@checkpoint.com  Wed May  9 00:45:05 2012
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 0C19D21F85B5 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.408
X-Spam-Level: 
X-Spam-Status: No, score=-10.408 tagged_above=-999 required=5 tests=[AWL=0.191, 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 Ym0vz3on4uyy for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 00:45:03 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8629121F859E for <ietf@ietf.org>; Wed,  9 May 2012 00:44:50 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q497ifYM031985;  Wed, 9 May 2012 10:44:41 +0300
X-CheckPoint: {4FAA2DE6-2-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 9 May 2012 10:44:40 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 9 May 2012 10:44:42 +0300
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Topic: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Index: Ac0tt5Z/rJewtmUURm6iFnZ4sUan0A==
Message-ID: <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com> <4FAA1A6A.5070500@gmail.com>
In-Reply-To: <4FAA1A6A.5070500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 07:45:05 -0000

I am not a lawyer either, but I think it depends on jurisdiction whether a =
mailing list will be considered as a media outlet or merely a "conduit".=20

What the IETF writes in its policy amounts to a plea to users to pretty ple=
ase send only factual information. I don't know that it makes a difference =
as to who is liable if the information turns out to be non-factual.

On May 9, 2012, at 10:19 AM, Brian E Carpenter wrote:

> Yoav,
>=20
> IANAL, but as far as I know libel suits are normally against individuals
> (or media outlets such as newspapers). The defence against a libel
> suit in the British courts, the most popular jurisdiction for
> international libel suits, is factual accuracy. Therefore, I think
> the draft should state the need for factual evidence.
>=20
> And to be clear, there are plenty of precedents for libels originating
> outside the UK leading to successful suits in the UK courts, if they
> have been received in the UK via the Internet.
>=20
> Regards
>   Brian Carpenter
>=20
>=20
>=20
>=20
> On 2012-05-09 08:07, Yoav Nir wrote:
>> I think that regardless of how it's worded, the real question is whether=
 liability falls to the person who sent the email (to a public mailing list=
) or the IETF. The difference between "believe" and "shown" seems minor in =
comparison.=20
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Brian E Carpenter
>> Sent: 09 May 2012 09:52
>> To: ietf@ietf.org
>> Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanc=
tions Available for Application to Violators of IETF IPR Policy) to Informa=
tional RFC
>>=20
>> I'd like to be reassured that this has been carefully reviewed by the IE=
TF counsel and the IETF Trust. In particular I would be interested in its p=
ossible interaction with the IETF's liability insurance.
>>=20
>>>   Any IETF participant can call for sanctions to be applied to anyone
>>>   they believe has violated the IETF's IPR policy. This can be done by
>>>   sending email to the appropriate IETF mailing list. =20
>>=20
>> That seems reasonable, but publishing such a belief without having the w=
ording checked by a libel lawyer might be risky. I think the draft should s=
tate that a call for sanctions should be based on factual evidence and not =
on "belief". How about
>>=20
>>   Any IETF participant can call for sanctions to be applied to anyone
>>   shown to have violated the IETF's IPR policy.  This can be done by
>>   sending email to the appropriate IETF mailing list, including a
>>   a short summary of the relevant facts and events.
>>=20
>> Regards
>>   Brian Carpenter
>>=20
>> On 2012-05-07 22:56, The IESG wrote:
>>> The IESG has received a request from an individual submitter to=20
>>> consider the following document:
>>> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
>>>  <draft-farrresnickel-ipr-sanctions-05.txt> as Informational RFC
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and solicits=20
>>> final comments on this action. Please send substantive comments to the=
=20
>>> ietf@ietf.org mailing lists by 2012-06-04. Exceptionally, comments may=
=20
>>> be sent to iesg@ietf.org instead. In either case, please retain the=20
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>>   The IETF has developed and documented policies that govern the
>>>   behavior of all IETF participants with respect to Intellectual
>>>   Property Rights (IPR) about which they might reasonably be aware.
>>>=20
>>>   The IETF takes conformance to these IPR policies very seriously.
>>>   However, there has been some ambiguity as to what the appropriate
>>>   sanctions are for the violation of these policies, and how and by
>>>   whom those sanctions are to be applied.
>>>=20
>>>   This document discusses these issues and provides a suite of
>>>   potential actions that may be taken within the IETF community.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
>>>=20
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball
>>> ot/
>>>=20
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>>=20
>>>=20
>>>=20
>>=20
>> Scanned by Check Point Total Security Gateway.
>>=20
>=20
> Scanned by Check Point Total Security Gateway.


From sm@resistor.net  Wed May  9 02:41:57 2012
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 AB06621F85B8 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 02:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuyEzfabHoWe for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 02:41:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA5621F85B5 for <ietf@ietf.org>; Wed,  9 May 2012 02:41:57 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q499fPHF027497; Wed, 9 May 2012 02:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336556504; i=@resistor.net; bh=08/Brvy+r69VNP5Jd723lTZPVKwKBwu5GKig5R3Qf0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HZihEX5ZtmcrD/tisvJufAO/8h19HEMYb2ZZk+oRfPnO/pe5K7AZ3qHDVYsl/XxgL 86rs5ay4VyViggNUjxyZZQPCSyt02pAxmNLLDJ0YQs38PzeBIpNDyr+JuSykLfMnwY fFcBRfS/nq0MV/rjuUBNVXXfESuwxn0a+DwWwznM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336556504; i=@resistor.net; bh=08/Brvy+r69VNP5Jd723lTZPVKwKBwu5GKig5R3Qf0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vtbePUOBFSGr1ROBzwHgSR5V8SodF4X4P8v7fCnnida+XgjaJrXYWyNn3QRGfqXX6 O0FAHNGzlt2UvVfzN4Op8iJkPD3ME7DQQY2Q0MlebHwqPZBD6sabh88gtcVFC7VrE+ ByRmjpc6r39CE5aR6QYetn7dgQTdKTlqCEDlRffU=
Message-Id: <6.2.5.6.2.20120509013727.0a999478@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 02:28:32 -0700
To: Yoav Nir <ynir@checkpoint.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
In-Reply-To: <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com> <4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 09:41:57 -0000

Hi Yoav,
At 00:44 09-05-2012, Yoav Nir wrote:
>What the IETF writes in its policy amounts to a plea to users to 
>pretty please send only factual information. I don't know that it 
>makes a difference as to who is liable if the information turns out 
>to be non-factual.

Section 3 text mentions several paths for the issue, i.e. 
responsibility lies with the working group chair with escalation to 
area directors.  Paragraph 2 and 3 discusses about that.  The issue 
which predates this draft is mentioned in the message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg71484.html

Do you know any IETF participant who is dumb enough to send a public 
request for sanctions? :-)  That can affect the individual's carrier 
path in the IETF and in the corporate world.  Some IETF participants 
might even ask lawyers to take action.  Watching "Behind enemy lines" 
(disambiguation required) might be instructive in this context.

At the end of the day, this draft is simply a matter of having an RFC 
for those who might find the information helpful.  Sometimes all one 
can do is to say "pretty please".

I'll +1 this draft as it stands.

Regards,
-sm


From ynir@checkpoint.com  Wed May  9 03:38:20 2012
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 3076221F8567 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 03:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.411
X-Spam-Level: 
X-Spam-Status: No, score=-10.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 fhUpVgzv68AD for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 03:38:18 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD8621F855D for <ietf@ietf.org>; Wed,  9 May 2012 03:38:17 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q49AbAX7002398;  Wed, 9 May 2012 13:37:45 +0300
X-CheckPoint: {4FAA5651-5-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 9 May 2012 13:37:12 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Date: Wed, 9 May 2012 13:37:15 +0300
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Topic: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Index: Ac0tz7EVxLJy+DceRT+REpZnuHXpfQ==
Message-ID: <F7C15739-CBD0-41AF-9FEB-6000971D8A79@checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com> <4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com> <6.2.5.6.2.20120509013727.0a999478@resistor.net>
In-Reply-To: <6.2.5.6.2.20120509013727.0a999478@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 10:38:20 -0000

On May 9, 2012, at 12:28 PM, SM wrote:

> Hi Yoav,
> At 00:44 09-05-2012, Yoav Nir wrote:
>> What the IETF writes in its policy amounts to a plea to users to=20
>> pretty please send only factual information. I don't know that it=20
>> makes a difference as to who is liable if the information turns out=20
>> to be non-factual.
>=20
> Section 3 text mentions several paths for the issue, i.e.=20
> responsibility lies with the working group chair with escalation to=20
> area directors.  Paragraph 2 and 3 discusses about that.  The issue=20
> which predates this draft is mentioned in the message at=20
> http://www.ietf.org/mail-archive/web/ietf/current/msg71484.html
>=20
> Do you know any IETF participant who is dumb enough to send a public=20
> request for sanctions? :-) =20

Dean Anderson often linked to his website: http://www.av8.net/IETF-watch/Pe=
ople/ (also loads of fun without the "People" path). IANAL but this does so=
und like libel.

More recently, but not related to IPR issues, during the last IETF quite a =
few of our prominent members were calling for sanctions (removal of posting=
 privileges) after some of the IETF.Fact.Check posts.

> That can affect the individual's carrier=20
> path in the IETF and in the corporate world.  Some IETF participants=20
> might even ask lawyers to take action.  Watching "Behind enemy lines"=20
> (disambiguation required) might be instructive in this context.
>=20
> At the end of the day, this draft is simply a matter of having an RFC=20
> for those who might find the information helpful.  Sometimes all one=20
> can do is to say "pretty please".
>=20
> I'll +1 this draft as it stands.

I'm fine with it as it is. I just hope the IETF is not held responsible for=
 postings by individuals.


From adrian@olddog.co.uk  Wed May  9 03:58:10 2012
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 B23FE21F84D5 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 03:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  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 RY4d2w5qVfNb for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 03:58:09 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB8421F846F for <ietf@ietf.org>; Wed,  9 May 2012 03:58:09 -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 q49AvxG1012809;  Wed, 9 May 2012 11:57:59 +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 q49AvtoH012751 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 May 2012 11:57:57 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Yoav Nir'" <ynir@checkpoint.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com>	<4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
In-Reply-To: <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com>
Subject: RE: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>	(Sanctions Available for Application to Violators of IETF IPR Policy)	to Informational RFC
Date: Wed, 9 May 2012 11:57:53 +0100
Message-ID: <021301cd2dd2$96c18760$c4449620$@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: AQGQEkUpByYTCLejnCgd2FgvYaJqvQHQdm1yAO2O2oYCFkhzfAKp9XxClv+NclA=
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: Wed, 09 May 2012 10:58:10 -0000

Hi,

I don't even own a television on which to watch people pretending to be
lawyers...

Both Brian and Yoav are making a worthwhile point, but I don't see how this I-D
changes what happens on IETF mailing lists as normal business. It is perfectly
possible for the IETF lists to be used to libel someone with or without this
I-D.

Brian makes a good point that the text should make it clear what level of
back-up we expect for such a claim. In writing the original text I had assumed
that everyone behaves like a reasonable adult when participating in the IETF -
gosh, am I naif?

Will fold in text close to Brian's suggestion.

Thanks,
Adrian

> I am not a lawyer either, but I think it depends on jurisdiction whether a
mailing
> list will be considered as a media outlet or merely a "conduit".
> 
> What the IETF writes in its policy amounts to a plea to users to pretty please
send
> only factual information. I don't know that it makes a difference as to who is
liable
> if the information turns out to be non-factual.
> 
> On May 9, 2012, at 10:19 AM, Brian E Carpenter wrote:
> 
> > Yoav,
> >
> > IANAL, but as far as I know libel suits are normally against individuals
> > (or media outlets such as newspapers). The defence against a libel
> > suit in the British courts, the most popular jurisdiction for
> > international libel suits, is factual accuracy. Therefore, I think
> > the draft should state the need for factual evidence.
> >
> > And to be clear, there are plenty of precedents for libels originating
> > outside the UK leading to successful suits in the UK courts, if they
> > have been received in the UK via the Internet.
> >
> > Regards
> >   Brian Carpenter
> >
> >
> >
> >
> > On 2012-05-09 08:07, Yoav Nir wrote:
> >> I think that regardless of how it's worded, the real question is whether
liability
> falls to the person who sent the email (to a public mailing list) or the IETF.
The
> difference between "believe" and "shown" seems minor in comparison.
> >>
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> >> Sent: 09 May 2012 09:52
> >> To: ietf@ietf.org
> >> Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>
(Sanctions
> Available for Application to Violators of IETF IPR Policy) to Informational
RFC
> >>
> >> I'd like to be reassured that this has been carefully reviewed by the IETF
> counsel and the IETF Trust. In particular I would be interested in its
possible
> interaction with the IETF's liability insurance.
> >>
> >>>   Any IETF participant can call for sanctions to be applied to anyone
> >>>   they believe has violated the IETF's IPR policy. This can be done by
> >>>   sending email to the appropriate IETF mailing list.
> >>
> >> That seems reasonable, but publishing such a belief without having the
> wording checked by a libel lawyer might be risky. I think the draft should
state
> that a call for sanctions should be based on factual evidence and not on
"belief".
> How about
> >>
> >>   Any IETF participant can call for sanctions to be applied to anyone
> >>   shown to have violated the IETF's IPR policy.  This can be done by
> >>   sending email to the appropriate IETF mailing list, including a
> >>   a short summary of the relevant facts and events.
> >>
> >> Regards
> >>   Brian Carpenter
> >>
> >> On 2012-05-07 22:56, The IESG wrote:
> >>> The IESG has received a request from an individual submitter to
> >>> consider the following document:
> >>> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
> >>>  <draft-farrresnickel-ipr-sanctions-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 2012-06-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 developed and documented policies that govern the
> >>>   behavior of all IETF participants with respect to Intellectual
> >>>   Property Rights (IPR) about which they might reasonably be aware.
> >>>
> >>>   The IETF takes conformance to these IPR policies very seriously.
> >>>   However, there has been some ambiguity as to what the appropriate
> >>>   sanctions are for the violation of these policies, and how and by
> >>>   whom those sanctions are to be applied.
> >>>
> >>>   This document discusses these issues and provides a suite of
> >>>   potential actions that may be taken within the IETF community.
> >>>
> >>>
> >>>
> >>>
> >>> The file can be obtained via
> >>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
> >>>
> >>> IESG discussion can be tracked via
> >>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball
> >>> ot/
> >>>
> >>>
> >>> No IPR declarations have been submitted directly on this I-D.
> >>>
> >>>
> >>>
> >>
> >> Scanned by Check Point Total Security Gateway.
> >>
> >
> > Scanned by Check Point Total Security Gateway.


From brian.e.carpenter@gmail.com  Wed May  9 04:03:19 2012
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 703C821F854E for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 04:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.579
X-Spam-Level: 
X-Spam-Status: No, score=-101.579 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 X6pi1mGwrFq8 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 04:03:18 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6658021F854B for <ietf@ietf.org>; Wed,  9 May 2012 04:03:18 -0700 (PDT)
Received: by eekd4 with SMTP id d4so66595eek.31 for <ietf@ietf.org>; Wed, 09 May 2012 04:03:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HBu0xYJmbtOt4/k/enHy8wwP+wEq0iinkhEgyjFiBn0=; b=nwocEmUvnJ3BMh331N/Ep/j+fpcYjRlQXgEGOMFeaiJHK7YVHzmeBagWLhHbu3BaUz NE12FauKFNU6WkHhWdcTrZMSET976J2PuS9N05ex7uMD2kWfJRGZVGLlvDSqK1RkVLoV HrQBRzopGMQDn6qGil4mkX7SC4jx7m7aalAjDxjVM07rZQwdRolLwdAKdhcbQ5PX8I+V 0uIyU2+2gOK+e8uHBzmUguZJm1MtdA9yTddIYiME66wunFiUZXb7R+LzauZ75nkEzNE9 AhRwmwXDBzzTf746tXjgNLZKcMbbgb1MJMEeNZ4Au7bGrYPvAIOAshh5K6N7+/Q+S19G 9vOA==
Received: by 10.14.127.204 with SMTP id d52mr4130912eei.18.1336561397558; Wed, 09 May 2012 04:03:17 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-118.as13285.net. [2.102.216.118]) by mx.google.com with ESMTPS id u10sm11074526eem.1.2012.05.09.04.03.15 (version=SSLv3 cipher=OTHER); Wed, 09 May 2012 04:03:16 -0700 (PDT)
Message-ID: <4FAA4EF0.3030802@gmail.com>
Date: Wed, 09 May 2012 12:03:12 +0100
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: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com>	<4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com> <021301cd2dd2$96c18760$c4449620$@olddog.co.uk>
In-Reply-To: <021301cd2dd2$96c18760$c4449620$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 11:03:19 -0000

Hi Adrian,

On 2012-05-09 11:57, Adrian Farrel wrote:
> Hi,
> 
> I don't even own a television on which to watch people pretending to be
> lawyers...
> 
> Both Brian and Yoav are making a worthwhile point, but I don't see how this I-D
> changes what happens on IETF mailing lists as normal business. It is perfectly
> possible for the IETF lists to be used to libel someone with or without this
> I-D.

Absolutely.

> Brian makes a good point that the text should make it clear what level of
> back-up we expect for such a claim. In writing the original text I had assumed
> that everyone behaves like a reasonable adult when participating in the IETF -
> gosh, am I naif?

Any reply I gave to that would most likely be libellous ;-)

> Will fold in text close to Brian's suggestion.

Thanks.

   Brian
> 
> Thanks,
> Adrian
> 
>> I am not a lawyer either, but I think it depends on jurisdiction whether a
> mailing
>> list will be considered as a media outlet or merely a "conduit".
>>
>> What the IETF writes in its policy amounts to a plea to users to pretty please
> send
>> only factual information. I don't know that it makes a difference as to who is
> liable
>> if the information turns out to be non-factual.
>>
>> On May 9, 2012, at 10:19 AM, Brian E Carpenter wrote:
>>
>>> Yoav,
>>>
>>> IANAL, but as far as I know libel suits are normally against individuals
>>> (or media outlets such as newspapers). The defence against a libel
>>> suit in the British courts, the most popular jurisdiction for
>>> international libel suits, is factual accuracy. Therefore, I think
>>> the draft should state the need for factual evidence.
>>>
>>> And to be clear, there are plenty of precedents for libels originating
>>> outside the UK leading to successful suits in the UK courts, if they
>>> have been received in the UK via the Internet.
>>>
>>> Regards
>>>   Brian Carpenter
>>>
>>>
>>>
>>>
>>> On 2012-05-09 08:07, Yoav Nir wrote:
>>>> I think that regardless of how it's worded, the real question is whether
> liability
>> falls to the person who sent the email (to a public mailing list) or the IETF.
> The
>> difference between "believe" and "shown" seems minor in comparison.
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Brian E Carpenter
>>>> Sent: 09 May 2012 09:52
>>>> To: ietf@ietf.org
>>>> Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>
> (Sanctions
>> Available for Application to Violators of IETF IPR Policy) to Informational
> RFC
>>>> I'd like to be reassured that this has been carefully reviewed by the IETF
>> counsel and the IETF Trust. In particular I would be interested in its
> possible
>> interaction with the IETF's liability insurance.
>>>>>   Any IETF participant can call for sanctions to be applied to anyone
>>>>>   they believe has violated the IETF's IPR policy. This can be done by
>>>>>   sending email to the appropriate IETF mailing list.
>>>> That seems reasonable, but publishing such a belief without having the
>> wording checked by a libel lawyer might be risky. I think the draft should
> state
>> that a call for sanctions should be based on factual evidence and not on
> "belief".
>> How about
>>>>   Any IETF participant can call for sanctions to be applied to anyone
>>>>   shown to have violated the IETF's IPR policy.  This can be done by
>>>>   sending email to the appropriate IETF mailing list, including a
>>>>   a short summary of the relevant facts and events.
>>>>
>>>> Regards
>>>>   Brian Carpenter
>>>>
>>>> On 2012-05-07 22:56, The IESG wrote:
>>>>> The IESG has received a request from an individual submitter to
>>>>> consider the following document:
>>>>> - 'Sanctions Available for Application to Violators of IETF IPR Policy'
>>>>>  <draft-farrresnickel-ipr-sanctions-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 2012-06-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 developed and documented policies that govern the
>>>>>   behavior of all IETF participants with respect to Intellectual
>>>>>   Property Rights (IPR) about which they might reasonably be aware.
>>>>>
>>>>>   The IETF takes conformance to these IPR policies very seriously.
>>>>>   However, there has been some ambiguity as to what the appropriate
>>>>>   sanctions are for the violation of these policies, and how and by
>>>>>   whom those sanctions are to be applied.
>>>>>
>>>>>   This document discusses these issues and provides a suite of
>>>>>   potential actions that may be taken within the IETF community.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> The file can be obtained via
>>>>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/
>>>>>
>>>>> IESG discussion can be tracked via
>>>>> http://datatracker.ietf.org/doc/draft-farrresnickel-ipr-sanctions/ball
>>>>> ot/
>>>>>
>>>>>
>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>
>>>>>
>>>>>
>>>> Scanned by Check Point Total Security Gateway.
>>>>
>>> Scanned by Check Point Total Security Gateway.
> 
> 

From touch@isi.edu  Wed May  9 07:10:24 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED1611E8073 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 07:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.332
X-Spam-Level: 
X-Spam-Status: No, score=-105.332 tagged_above=-999 required=5 tests=[AWL=1.268, 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 yX2A7a5Dc-L7 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 07:10:23 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id ADB1E11E8072 for <ietf@ietf.org>; Wed,  9 May 2012 07:10:23 -0700 (PDT)
Received: from [192.168.1.95] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q49E8xGt003802 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 May 2012 07:09:09 -0700 (PDT)
Subject: Re: a favor from the list about Jon Postel
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <alpine.LFD.2.02.1205082144320.18036@bofh.nohats.ca>
Date: Wed, 9 May 2012 07:09:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <15D1BBDB-581F-4C3B-90B1-769AF449D691@isi.edu>
References: <4FA9A9FE.7050307@isi.edu> <0AD02572-A3E8-402A-903E-244D4F342A40@gmail.com> <alpine.LFD.2.02.1205082144320.18036@bofh.nohats.ca>
To: Paul Wouters <paul@cypherpunks.ca>
X-Mailer: Apple Mail (2.1257)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Bob Hinden <bob.hinden@gmail.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: Wed, 09 May 2012 14:10:24 -0000

On May 8, 2012, at 7:09 PM, Paul Wouters wrote:

> On Tue, 8 May 2012, Bob Hinden wrote:
>=20
>>> https://www.facebook.com/jon.postel
>>=20
>> I just tried going to this page and it says it doesn't exist.  Has =
the problem been fixed?

Yes it has.=20

Many thanks to those on this list - and other lists - who responded =
rapidly and helped resolve this quickly.

Joe=

From sm@resistor.net  Wed May  9 10:12:02 2012
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 9457811E8079 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 10:12: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 69ykzxtlAMmz for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 10:12:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E07C11E807F for <ietf@ietf.org>; Wed,  9 May 2012 10:12:01 -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 q49HBgmg028223; Wed, 9 May 2012 10:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336583511; i=@resistor.net; bh=C/vbnyp2Z0kSl5dVAV+6EydK8N8PQssw1S0AgOWGwhU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PP0JiBbT3iSMVZ+1Em8mQhvaTFHPvTxw/gDaYhW8RJErO6N1K6AFViXLkVGRL0SEP VBCLRPrvXwsyvQgSppnjIvYCWZJzcK7UFP+8mGnQJH5zcfv7sUZjDl1WjhJ2ESzpLb wVnrBAR+pKCYVUQoBONue+k4dodis8Q8Eo3cByTA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336583511; i=@resistor.net; bh=C/vbnyp2Z0kSl5dVAV+6EydK8N8PQssw1S0AgOWGwhU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=umcn2Sem8S8DVKRXLVWKXylDeM1tA5a+WTQflK5ZzVDaNmAZNSWaVLnrbsgEAPd0v 7ZFpM2hFMazTodFwT8kqnAARVA39WOOahIiu/4pOPqk2t9jPIqB1Jof1ZsZwYWe6Kt 6Mw1mKB8TgDGhI3rYxcEK709KMjQxHM2Lf2gqx8s=
Message-Id: <6.2.5.6.2.20120509065722.0a70aef0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 10:00:00 -0700
To: Yoav Nir <ynir@checkpoint.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy)  to Informational RFC
In-Reply-To: <F7C15739-CBD0-41AF-9FEB-6000971D8A79@checkpoint.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <006FEB08D9C6444AB014105C9AEB133F017A7C056C4B@il-ex01.ad.checkpoint.com> <4FAA1A6A.5070500@gmail.com> <6585DDB2-11FB-4B49-B63E-4F75D540E920@checkpoint.com> <6.2.5.6.2.20120509013727.0a999478@resistor.net> <F7C15739-CBD0-41AF-9FEB-6000971D8A79@checkpoint.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 17:12:02 -0000

Hi Yoav,
At 03:37 09-05-2012, Yoav Nir wrote:
>loads of fun without the "People" path). IANAL but this does sound like libel.

http://www.ietf.org/mail-archive/web/ietf-announce/current/msg01967.html

>More recently, but not related to IPR issues, during the last IETF 
>quite a few of our prominent members were calling for sanctions 
>(removal of posting privileges) after some of the IETF.Fact.Check posts.

Some identifiers are well-known in some communities.  There is a 
zero-based risk to identify such identifiers.  People tend to go 
after low-hanging fruits.  Why would the "prominent members" be any different?

Regards,
-sm 


From presnick@qualcomm.com  Wed May  9 13:19:30 2012
Return-Path: <presnick@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 F237C21F85AA for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 13:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.559
X-Spam-Level: 
X-Spam-Status: No, score=-106.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGuTKlZ6xiHf for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 13:19:30 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD0A21F85A7 for <ietf@ietf.org>; Wed,  9 May 2012 13:19:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1336594770; x=1368130770; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=dLvstSsnPY7/huCek7XWN+I/WDPKWGf7FgpSfAWOLIk=; b=iXoAeaKUU/4f737vS0BgSHXaaZfIbRs5/kciVjLbt9pRyHZry2J2G0Im 2T+tS0SKcVvurkRKYOpLzifhJ/I9hDEbyfHU8ml2g55SVM7Q6MBpkbEkK E/wfDey9Ig48pmJNHSpw17gBIAnCe65ReDsAZFvoRFi1wEQ9t7Qa/V6Nq Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6706"; a="186969482"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 09 May 2012 13:19:29 -0700
X-IronPort-AV: E=Sophos;i="4.75,557,1330934400"; d="scan'208";a="216312548"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 May 2012 13:19:29 -0700
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 9 May 2012 13:19:29 -0700
Message-ID: <4FAAD14F.40009@qualcomm.com>
Date: Wed, 9 May 2012 15:19:27 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to	Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com>
In-Reply-To: <4FAA140B.4010703@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 20:19:31 -0000

On 5/9/12 1:51 AM, Brian E Carpenter wrote:
>>     Any IETF participant can call for sanctions to be applied to anyone
>>      they believe has violated the IETF's IPR policy. This can be done by
>>      sending email to the appropriate IETF mailing list.
>>      
> That seems reasonable, but publishing such a belief without having the
> wording checked by a libel lawyer might be risky. I think the draft
> should state that a call for sanctions should be based on factual
> evidence and not on "belief". How about
>
>     Any IETF participant can call for sanctions to be applied to anyone
>     shown to have violated the IETF's IPR policy.  This can be done by
>     sending email to the appropriate IETF mailing list, including a
>     a short summary of the relevant facts and events.
>    

Shown how and by whom? I think you're conflating two things here. Any 
participant can *call* for sanctions to be applied to anyone they 
believe has violated the policy. No libel in saying that I believe you 
have violated the policy. The sanctions ought not be applied until the 
chair/AD/whoever reasonably determines that the policy has in fact been 
violated. But that's not what the sentence above is talking about. I 
don't want participants to think that they can't bring up the issue of 
violation without some sort of "burden of proof". Can we figure out some 
words that express both things?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From sm@resistor.net  Wed May  9 16:02:57 2012
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 EBC8A11E8086 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 16:02:57 -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 b3kwoykeB3TZ for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 16:02: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 9915311E80CF for <ietf@ietf.org>; Wed,  9 May 2012 16:02:54 -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 q49N2l8K006149; Wed, 9 May 2012 16:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336604572; i=@resistor.net; bh=KC0+1HJrlLofhb7vTIt5oeeMH3RATfFYBM4YrEN6i/4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ku1yaNpCziFxx8ldW8k/Pb/XbvYhsT4sG8nQRYWQ23HHS8jnkn7ThS39S70V4As8y EevIyRb14Dt6Rwlje14pQD+3HzCUA/FmGuq9X4EMDHGns3wscQ4D53dudpVLm0eyE6 p5X9Dda3V0VpYnQtns2CKbhRH0P+ms1MYDPjA2b4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336604572; i=@resistor.net; bh=KC0+1HJrlLofhb7vTIt5oeeMH3RATfFYBM4YrEN6i/4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tPphKPbfnMwsEFd3hEJjp98OUWPB2R4MDuynbaCBXvwWhpZeL2I97jzYrJjDMPJGH WrEeL2UTx47MZ8pl1S1KYaDbj4gIfFMwUBS0JEH2A8zeL0FgnPlj8YJhZcH9aUxKC8 Px7iJo4smxT9qDzsaCJvrNqAvC3RfA5HCEtXkULo=
Message-Id: <6.2.5.6.2.20120509150640.090d7098@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 15:58:47 -0700
To: Pete Resnick <presnick@qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to	Informational RFC
In-Reply-To: <4FAAD14F.40009@qualcomm.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@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: Wed, 09 May 2012 23:02:58 -0000

At 13:19 09-05-2012, Pete Resnick wrote:
>Shown how and by whom? I think you're conflating two things here. 
>Any participant can *call* for sanctions to be applied to anyone 
>they believe has violated the policy. No libel in saying that I 
>believe you have violated the policy. The sanctions ought not be 
>applied until the chair/AD/whoever reasonably determines that the 
>policy has in fact been violated. But that's not what the sentence 
>above is talking about. I don't want participants to think that they 
>can't bring up the issue of violation without some sort of "burden 
>of proof". Can we figure out some words that express both things?

Here's some text for the entire paragraph:

    Any IETF participant can call for sanctions to be applied to anyone they
    believe has violated the IETF's IPR policy.  This can be done by
    sending email to the appropriate IETF mailing list.  The area director or
    working group chair will discuss the matter with the IETF participant and
    determine whether the policy has in fact been violated.  Thus, when
    sanctions are called for, working group chairs will be the first actors
    when there is an active working group involved in the technical work, and
    area directors will be the first actors in other cases.

I avoided the "including a short summary of the relevant facts and 
events" as it comes out as "burden of proof".

Regards,
-sm 


From fred@cisco.com  Wed May  9 16:41:34 2012
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 9839911E80AD for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 16:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.602
X-Spam-Level: 
X-Spam-Status: No, score=-110.602 tagged_above=-999 required=5 tests=[AWL=-0.003, 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 DepyZV3V+ZPH for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 16:41:34 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0A10511E80AA for <ietf@ietf.org>; Wed,  9 May 2012 16:41:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=803; q=dns/txt; s=iport; t=1336606894; x=1337816494; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=tTteHNQRDq0er5dgr8v/Ae7T9pqBCtzWnuRIUM1s3f0=; b=inrygq3w4IR47e+yz3VR7QSs3MpGqLwdFaRWvTo4Owpdwchr/s7xkNaE W4TqThCLlXOi28MKZZlcBMgtc9eq9UzBE01OYT7Fie+OPVDz8+RaDOsN0 hq1wwP5dIrtC/YgdCbhGD/r8hQioJ7LcLcCCjP5kP9vrAdHNTLAVmD32u 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAK//qk+rRDoH/2dsb2JhbABEsRoBAYIcgQeCDAEBAQMBEgEnPwULCw4tC1cGNYdnBJszoA+QUmMEiGSNGYV2iGKBaYMH
X-IronPort-AV: E=Sophos;i="4.75,559,1330905600"; d="scan'208";a="41621402"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 09 May 2012 23:41:33 +0000
Received: from Freds-Computer.local ([10.21.75.243]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q49NfWFF032705; Wed, 9 May 2012 23:41:33 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 09 May 2012 18:41:33 -0500
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 09 May 2012 18:41:33 -0500
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to	Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <6.2.5.6.2.20120509150640.090d7098@resistor.net>
Date: Wed, 9 May 2012 18:40:32 -0500
Message-Id: <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 23:41:34 -0000

> I don't want participants to think that they can't bring up the issue =
of violation without some sort of "burden of proof".

Hmm.

I'm concerned about people bringing baseless accusations, as yet another =
way to DOS a WG with IPR. If a person believes that there is a violation =
that is worthy of the name, they should probably see to it that it gets =
discussed, but I don't see how they make that determination without =
having at least some data or report that can be verified. If someone in =
my working group brings such an accusation to me, trust me, the first =
question I am going to ask is "why do you believe that". If the answer =
is "can't you see they have shifty eyes", it will end there. I'm looking =
for at minimum that a named party has evidence to support it.=

From randy@psg.com  Wed May  9 18:33:34 2012
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 C03E111E80E1 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 18:33: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 qO6KyfP1LLRz for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 18:33:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC6811E80AA for <ietf@ietf.org>; Wed,  9 May 2012 18:33:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SSIG5-000Jqv-DN; Thu, 10 May 2012 01:33:33 +0000
Date: Wed, 09 May 2012 15:33:32 -1000
Message-ID: <m2ipg4zuoj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>	(Sanctions Available for Application to Violators of IETF IPR Policy)	to	Informational RFC
In-Reply-To: <6.2.5.6.2.20120509150640.090d7098@resistor.net>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 01:33:34 -0000

> Any IETF participant can call for sanctions to be applied to anyone they
> believe has violated the IETF's IPR policy.

oh goodie!  let's have witch trials.  why bother with accusations, let's
just burn everyone below layer nine at the stake!

plonk.  that's two political crap stirrers in a week.  sad.

randy

From presnick@qualcomm.com  Wed May  9 19:18:36 2012
Return-Path: <presnick@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 778F111E80AA for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 19:18:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 wpBObXWQOHwY for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 19:18:35 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id D16F611E80AF for <ietf@ietf.org>; Wed,  9 May 2012 19:18:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1336616315; x=1368152315; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=F3C3C6SMyu5QrTw5x2FZaskIyfUGiZAq+0jDKZBl6lE=; b=WoaYxzojXWv1qsgCFO8pciv/C33I6png3F4UIfqIa+I906qD4TWGwCwB 8SzqdZSllRRqk5EAIrOJd1YJzVeIHXUo/+FL7+0vXRmgezuJra5xBjCyd 7WnYegBA+dfdYf2kJAQYNMm0cB+wwqdpaezA3ODfnbv9qqrslzF+tezLF o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6706"; a="187086523"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 09 May 2012 19:18:20 -0700
X-IronPort-AV: E=Sophos;i="4.75,557,1330934400"; d="scan'208";a="216667760"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 May 2012 19:18:20 -0700
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 9 May 2012 19:18:19 -0700
Message-ID: <4FAB2563.3090309@qualcomm.com>
Date: Wed, 9 May 2012 21:18:11 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to	Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>
In-Reply-To: <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.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, 10 May 2012 02:18:36 -0000

On 5/9/12 6:40 PM, Fred Baker wrote:

>> I don't want participants to think that they can't bring up the issue of violation without some sort of "burden of proof".
>>      
> Hmm.
>
> I'm concerned about people bringing baseless accusations, as yet another way to DOS a WG with IPR. If a person believes that there is a violation that is worthy of the name, they should probably see to it that it gets discussed, but I don't see how they make that determination without having at least some data or report that can be verified. If someone in my working group brings such an accusation to me, trust me, the first question I am going to ask is "why do you believe that". If the answer is "can't you see they have shifty eyes", it will end there. I'm looking for at minimum that a named party has evidence to support it.

I completely agree. That's why I asked that we figure out some text that 
does both things: Indicate that it's OK to say that you believe someone 
crossed the line and explain your reasons for that belief, but not 
require that it be a proven fact before you can even broach the subject. 
I can see how the current text might be too lax, but I thought Brian's 
text was too stringent. Looking for a happy medium.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From marka@isc.org  Wed May  9 19:26:54 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D827011E80B0 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 19:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.032
X-Spam-Level: 
X-Spam-Status: No, score=-2.032 tagged_above=-999 required=5 tests=[AWL=0.567,  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 rjvNFzOSZIFU for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 19:26:54 -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 2369B11E80AA for <ietf@ietf.org>; Wed,  9 May 2012 19:26:54 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 01ECBC96BC; Thu, 10 May 2012 02:26:40 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9d32:49e9:1eb7:9a6f]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id B27CC216C33; Thu, 10 May 2012 02:26:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 813D220891FA; Thu, 10 May 2012 12:26:33 +1000 (EST)
To: Pete Resnick <presnick@qualcomm.com>
From: Mark Andrews <marka@isc.org>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com> <4FAB2563.3090309@qualcomm.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
In-reply-to: Your message of "Wed, 09 May 2012 21:18:11 EST." <4FAB2563.3090309@qualcomm.com>
Date: Thu, 10 May 2012 12:26:33 +1000
Message-Id: <20120510022633.813D220891FA@drugs.dv.isc.org>
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, 10 May 2012 02:26:55 -0000

	In good faith that you believe, or potentially believe, that
	....
	
In message <4FAB2563.3090309@qualcomm.com>, Pete Resnick writes:
> On 5/9/12 6:40 PM, Fred Baker wrote:
> 
> >> I don't want participants to think that they can't bring up the issue of v
> iolation without some sort of "burden of proof".
> >>      
> > Hmm.
> >
> > I'm concerned about people bringing baseless accusations, as yet another wa
> y to DOS a WG with IPR. If a person believes that there is a violation that i
> s worthy of the name, they should probably see to it that it gets discussed, 
> but I don't see how they make that determination without having at least some
>  data or report that can be verified. If someone in my working group brings s
> uch an accusation to me, trust me, the first question I am going to ask is "w
> hy do you believe that". If the answer is "can't you see they have shifty eye
> s", it will end there. I'm looking for at minimum that a named party has evid
> ence to support it.
> 
> I completely agree. That's why I asked that we figure out some text that 
> does both things: Indicate that it's OK to say that you believe someone 
> crossed the line and explain your reasons for that belief, but not 
> require that it be a proven fact before you can even broach the subject. 
> I can see how the current text might be too lax, but I thought Brian's 
> text was too stringent. Looking for a happy medium.
> 
> pr
> 
> -- 
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From randy@psg.com  Wed May  9 20:09:56 2012
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 E92DD11E80B0 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 20:09: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 zt1kRnF9lxOY for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 20:09:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 577DB11E80AF for <ietf@ietf.org>; Wed,  9 May 2012 20:09:56 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SSJlF-000K1F-M9; Thu, 10 May 2012 03:09:49 +0000
Date: Wed, 09 May 2012 17:09:48 -1000
Message-ID: <m24nrozq83.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>	(Sanctions Available for Application to Violators of IETF IPR	Policy)	to	Informational RFC
In-Reply-To: <4FAB2A79.3090402@qualcomm.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <m2ipg4zuoj.wl%randy@psg.com> <4FAB2A79.3090402@qualcomm.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 03:09:57 -0000

ok, ok, i put my foot in, so now have to pay

   Not conforming to the IETF's IPR policy undermines the work of the
   IETF, and sanctions should be applied against offenders.

s/should/may/

3.  Who May Call For and Apply Sanctions

   Any IETF participant can call for sanctions to be applied to anyone
   they believe has violated the IETF's IPR policy.

participants should not call for sanctions.  they should point out to wg
chairs, or ADs FACTS about questinable activity, non-disclosure, ...

and so forth.  i hope that this is not a witch hunt.  that it is not
creating courts and guillotines.  we should assume people want to act in
a responsible fashion and provide simple gentle paths to be taken when
that assumption fails.

randy

From stpeter@stpeter.im  Wed May  9 20:29:58 2012
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 1AA7D11E80EB for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 20:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 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 KHbuJA4zvfV5 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 20:29:57 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 561C611E80AF for <ietf@ietf.org>; Wed,  9 May 2012 20:29:57 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.175.160]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1F22040058; Wed,  9 May 2012 21:45:19 -0600 (MDT)
Message-ID: <4FAB362E.8050503@stpeter.im>
Date: Wed, 09 May 2012 21:29:50 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>	(Sanctions Available for Application to Violators of IETF IPR	Policy)	to	Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <m2ipg4zuoj.wl%randy@psg.com> <4FAB2A79.3090402@qualcomm.com> <m24nrozq83.wl%randy@psg.com>
In-Reply-To: <m24nrozq83.wl%randy@psg.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@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: Thu, 10 May 2012 03:29:58 -0000

On 5/9/12 9:09 PM, Randy Bush wrote:

> i hope that this is not a witch hunt.  that it is not
> creating courts and guillotines.  we should assume people want to act in
> a responsible fashion and provide simple gentle paths to be taken when
> that assumption fails.

Well, draft-farrresnickel-ipr-sanctions is the stick here, whereas
draft-polk-ipr-disclosure is the carrot that we hope will make it more
likely that folks will indeed act in a responsible fashion.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From tobias.gondrom@gondrom.org  Wed May  9 23:23:30 2012
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 353EB21F85B8 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 23:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.778
X-Spam-Level: 
X-Spam-Status: No, score=-96.778 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7U8SaXquDd5 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 23:23:29 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id F180E21F851C for <ietf@ietf.org>; Wed,  9 May 2012 23:23:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=q559Md5fWRQuP3UMV4Ef9vkFhRxM1iGC8DAiHbN2yf7yf87vR6ilsL6EIjcKrOWvnGxtcd/KTl38WIzn4Ru+gsqps9dsJgsyaWSnQJtRIkyIj21uc+xHk3hU7IQzOFcj; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 1401 invoked from network); 10 May 2012 08:23:25 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 08:23:25 +0200
Message-ID: <4FAB5ED8.7070004@gondrom.org>
Date: Thu, 10 May 2012 14:23:20 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org>
In-Reply-To: <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.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: Thu, 10 May 2012 06:23:30 -0000

Dear Russ,

please forgive me for adding one more comment on that after you judged 
on rough consensus.

As you said this rough consensus is quite rough (if we may call it 
"rough consensus").
I would like to point out two things:
1. the statement "(1) Rough consensus: an open and transparent standards 
process is more important to the IETF than privacy of blue sheet 
information." puts transparent process in competition with privacy. This 
is misleading, because there is no contradiction between an open and 
transparent process and privacy of personal information on this one. For 
example the availability of blue sheet information on request by an 
authenticated person does allow full transparency without broadcasting 
the personal location information. (e.g. see also Ted's proposal from 
yesterday)
(Furthermore, if I would be devil's advocate, I would question this 
comparison even further, because it could be misread as stating that the 
current standards process as it is today (with blue sheets on request) 
is not open or transparent...)

2. if consensus is so rough, we should also consider that the subject of 
the email discussion was maybe not clear enough about its impact to 
inform the audience of the consequences of the discussion and the 
consensus to be measured. We could equally have used a subject like 
this: "IETF wants to publish your specific locations / whereabouts 
(within 10m) on an 2-hourly basis during the day for each meeting and 
keep this information available published on the website indefinitely." 
It might have resulted in a different rough consensus.

Just my 5cents.

Best regards, Tobias




On 07/05/12 23:02, IETF Chair wrote:
> During the IESG discussion of this thread, we recognized the quality of the information on the blue sheets.  This point was made very clearly at the open mic discussion at the plenary and on the mail list.
>
> Some people voiced agreement with your position, and others supported the posting of this information.  As I said in my earlier message, the consensus is quite rough.  By my review of the thread, which was made more difficult by the many off-topic postings, there is rough consensus for the inclusion of blue sheet information in the proceedings.
>
> Russ
>
>
> On May 6, 2012, at 10:04 PM, David Morris wrote:
>
>> I consider that there is a significant difference between the information
>> provided in the registered attendee list and the individual blue sheets:
>>
>> a) to the extent that the information on the blue sheet is valid, it
>> provides an hour by hour log of location, the overall list of attendees at
>> most indicates an individual was present to pick up their badge at some
>> point during the meeting.
>> b) the validity of the list of registered attendees has a higher degree
>> of probable validity because of the requirement for a significant payment
>> and the processes required to process that payment.
>> c) Individual blue sheets can suffer from any number of unintentional and
>> intentional issues which limit their factual validity but not the mischief
>> which can be caused by their easy online access.
>> d) Scanning and publication imports a validity to the data which is not
>> widely accepted by the community.
>>
>> David Morris
>>
>> On Sun, 6 May 2012, IETF Chair wrote:
>>
>>> David:
>>>
>>> The list of participants and their addresses are already part of the proceedings.  The incremental difference shows which participants signed in at each session.
>>>
>>> Russ
>>>
>>>
>>>
>>> On May 6, 2012, at 7:03 PM, David Morris wrote:
>>>
>>>>  From my following of the topic, that concensus was really rough, in
>>>> particular the part about publishing the scans on-line. That represents
>>>> a significant difference in ease access which I think required more than
>>>> the very very rough concensus you seem to think you found.
>>>>
>>>> On Sun, 6 May 2012, IETF Chair wrote:
>>>>
>>>>> We have heard from many community participants, and consensus is quite rough on this topic.  The IESG discussed this thread and reached two conclusions:
>>>>>
>>>>> (1) Rough consensus: an open and transparent standards process is more important to the IETF than privacy of blue sheet information.
>>>>>
>>>>> (2) Rough consensus: inclusion of email addresses is a good way to distinguish participants with the same or similar names.
>>>>>
>>>>>
>>>>> Based on these conclusions, the plan is to handle blue sheets as follows:
>>>>>
>>>>> - Continue to collect email addresses on blue sheets;
>>>>>
>>>>> - Scan the blue sheet and include the image in the proceedings for the WG session;
>>>>>
>>>>> - Add indication to top of the blue sheet so people know it will be part of the proceedings; and
>>>>>
>>>>> - Discard paper blue sheets after scanning.
>>>>>
>>>>>
>>>>> On behalf of the IESG,
>>>>> Russ
>>>>>
>>>>>
>>>


From brian.e.carpenter@gmail.com  Wed May  9 23:46:28 2012
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 99D9E21F85D3 for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 23:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.582
X-Spam-Level: 
X-Spam-Status: No, score=-101.582 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 9ErLPdh-FyIK for <ietf@ietfa.amsl.com>; Wed,  9 May 2012 23:46:28 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id BD77621F8570 for <ietf@ietf.org>; Wed,  9 May 2012 23:46:27 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so749408wgb.13 for <ietf@ietf.org>; Wed, 09 May 2012 23:46:26 -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=lOo8EJw7/TItMw8/9eLE9EuEvb0PB8sY/TvPKW8L82U=; b=OmskEd8Qvm+wyXt35xjm4TMrtaYaya7fG9FrVV2s9Iwz1QCWP+nWJjb3VZoVlWT68k T+pAOYCscQG3WNuXy0GJfprqrgmsWp/uCEMh7i17O/MfLagyqJj0pwPh6VNZpr1I9VtH JFFfQLBJGIA8I6o7NJEh58LUoQuBKCk/m8I7GdwfT3mlsDRmDy4BSnz9fjoOdZ2cNUnw 8b42DQEmsCDrxoWhwwVf34zHPA0zfrdI3e+ixifjZ+YiyoiAIXuWUqFZlvFsfCBebn84 P25PkIg3BfqdVCEn5cQQmgZuYN3S6Xdy6K5u9VARKkUXTLFrwNStifPTkAFOuZ0zY8Ox 2rlw==
Received: by 10.180.97.4 with SMTP id dw4mr13205905wib.18.1336632386707; Wed, 09 May 2012 23:46:26 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-118.as13285.net. [2.102.216.118]) by mx.google.com with ESMTPS id l5sm1266732wia.11.2012.05.09.23.46.24 (version=SSLv3 cipher=OTHER); Wed, 09 May 2012 23:46:25 -0700 (PDT)
Message-ID: <4FAB643C.108@gmail.com>
Date: Thu, 10 May 2012 07:46:20 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy)	to	Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com>	<6.2.5.6.2.20120509150640.090d7098@resistor.net>	<AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com> <4FAB2563.3090309@qualcomm.com>
In-Reply-To: <4FAB2563.3090309@qualcomm.com>
Content-Type: text/plain; charset=UTF-8
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: Thu, 10 May 2012 06:46:28 -0000

On 2012-05-10 03:18, Pete Resnick wrote:
> On 5/9/12 6:40 PM, Fred Baker wrote:
> 
>>> I don't want participants to think that they can't bring up the issue
>>> of violation without some sort of "burden of proof".
>>>      
>> Hmm.
>>
>> I'm concerned about people bringing baseless accusations, as yet
>> another way to DOS a WG with IPR. If a person believes that there is a
>> violation that is worthy of the name, they should probably see to it
>> that it gets discussed, but I don't see how they make that
>> determination without having at least some data or report that can be
>> verified. If someone in my working group brings such an accusation to
>> me, trust me, the first question I am going to ask is "why do you
>> believe that". If the answer is "can't you see they have shifty eyes",
>> it will end there. I'm looking for at minimum that a named party has
>> evidence to support it.
> 
> I completely agree. That's why I asked that we figure out some text that
> does both things: Indicate that it's OK to say that you believe someone
> crossed the line and explain your reasons for that belief, but not
> require that it be a proven fact before you can even broach the subject.
> I can see how the current text might be too lax, but I thought Brian's
> text was too stringent. Looking for a happy medium.

Fair enough. I can't agree with SM though - as for appeals under RFC 2026,
the person bringing up an issue really has to provide a factual summary,
exactly to avoid witch hunts. It can be very short:

   Hi, I noticed that US Patent 12345 was filed in March 2010, and
   draft-blo-foobar was posted that June, and Jo Blo was an author
   of both. It looks as if they describe the same method, so why
   wasn't there an IPR disclosure in 2010? Would the WG Chairs consider
   sanctions against Jo Blo appropriate?

Possible text:

   Any IETF participant can draw attention to an apparent violation
   of the IETF's IPR policy.  This can be done by sending email to
   the appropriate IETF mailing list, including a short summary of
   the known facts and, optionally, a call for sanctions to be
   applied.

       Brian

From tobias.gondrom@gondrom.org  Thu May 10 00:59:43 2012
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 3033321F85D4 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.778
X-Spam-Level: 
X-Spam-Status: No, score=-96.778 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zK5voOqV3KK6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:59:42 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id 25BED21F85C3 for <ietf@ietf.org>; Thu, 10 May 2012 00:59:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=qjbd9ydhMTn2aIPOgOTr11UAHK2l0pL65nEz2qeGSyeEOvXOcy4PGV2XY/DNpwPhXVgDB6KUaPXLyaYlwUvDPhrD7MM9l0xzO2BMGjEPks3wfF/KAcQNumuLN/0KtKGc; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 1951 invoked from network); 10 May 2012 09:59:39 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 09:59:39 +0200
Message-ID: <4FAB7567.7070402@gondrom.org>
Date: Thu, 10 May 2012 15:59:35 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: john@jck.com
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com>
In-Reply-To: <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.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: Thu, 10 May 2012 07:59:43 -0000

John,

sorry, maybe I did not articulate myself precisely enough. I did not 
intend to say it would be published in real-time. What I wanted to 
communicate is that we would collect that data only during daytime and 
only with 2hours-granularity as it's only meeting attendance in which 
room you are (and publish it at any point in time later). However, we 
would keep it public indefinitely (in the proceedings).

Like you, I am very cautious about broadcasting my travel plans. Plus, I 
am not only concerned about in advance and real-time, but also about 
broadcasting to the public places I've been in the past (or for that 
matter any personal information).

Best regards, Tobias



On 10/05/12 15:09, John C Klensin wrote:
> (top post)
> Tobias,
>
> Constructing and then attacking strawmen is not helpful.
>
> As far as I know, no one has proposed making blue sheet
> information --and hence precise location information for
> identified individuals-- available to the public in real time
> during the meetings.   As one of, I assume, many members of this
> community who will not broadcast my travel plans to social
> networks, etc., until after I return home, I would strenuously
> object to any such thing but, again, as far as I know, no one
> proposed it.
>
>       john
>
>
> --On Thursday, May 10, 2012 14:23 +0800 Tobias Gondrom
> <tobias.gondrom@gondrom.org>  wrote:
>
>> Dear Russ,
>>
>> please forgive me for adding one more comment on that after
>> you judged on rough consensus.
>>
>> As you said this rough consensus is quite rough (if we may
>> call it "rough consensus").
>> I would like to point out two things:
>> 1. the statement "(1) Rough consensus: an open and transparent
>> standards process is more important to the IETF than privacy
>> of blue sheet information." puts transparent process in
>> competition with privacy. This is misleading, because there is
>> no contradiction between an open and transparent process and
>> privacy of personal information on this one. For example the
>> availability of blue sheet information on request by an
>> authenticated person does allow full transparency without
>> broadcasting the personal location information. (e.g. see also
>> Ted's proposal from yesterday)
>> (Furthermore, if I would be devil's advocate, I would question
>> this comparison even further, because it could be misread as
>> stating that the current standards process as it is today
>> (with blue sheets on request) is not open or transparent...)
>>
>> 2. if consensus is so rough, we should also consider that the
>> subject of the email discussion was maybe not clear enough
>> about its impact to inform the audience of the consequences of
>> the discussion and the consensus to be measured. We could
>> equally have used a subject like this: "IETF wants to publish
>> your specific locations / whereabouts (within 10m) on an
>> 2-hourly basis during the day for each meeting and keep this
>> information available published on the website indefinitely."
>> It might have resulted in a different rough consensus.
>
>
>


From sm@resistor.net  Thu May 10 01:18:58 2012
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 D96B221F85E7 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.583
X-Spam-Level: 
X-Spam-Status: No, score=-103.583 tagged_above=-999 required=5 tests=[AWL=1.016, 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 6X14FRA4W74t for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:18: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 810CF21F84FC for <ietf@ietf.org>; Thu, 10 May 2012 01:18:54 -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 q4A8Im1s004715 for <ietf@ietf.org>; Thu, 10 May 2012 01:18:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1336637933; i=@resistor.net; bh=0CpkFdn9TaxMBh+bzM0rmhF7bqLWs4beC8r901Xmllo=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=gbD29JrLALbZbuGfXF6DrBqF3T8a6X9UYD2Khrx5x9v+faAlJyrQ2GzyLlbmQ4WaL 5ceHFe/Da5B8OyI+fZx7p8ypkFfNn6pwGC6C60oqJFCahMgNCiMKkvHqXdYFAdVylz luRPqMyUKfRtz2v7UbU7D3ItYlPcgiGTcY3Mw2Mo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1336637933; i=@resistor.net; bh=0CpkFdn9TaxMBh+bzM0rmhF7bqLWs4beC8r901Xmllo=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=2mo/HjBIM9unXsHjBGr80jVqEHUeSusweuG0sdRj7oqWM148lLzRiPGNwZrz2AF9s uiY461SQ/zpC3J3JawY9r6Siwdl9R+3JAgRJdXn/ZiTATZqkOafCaXJo5LeQZp3qtl /SsbUfV0PBGZWksfswqr36lxVDF31ZPDECRPpyDU=
Message-Id: <6.2.5.6.2.20120509210747.0a901d38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 09 May 2012 23:30:17 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt>	(Sanctions Available for Application to Violators of IETF IPR	Policy)	to	Informational RFC
In-Reply-To: <m24nrozq83.wl%randy@psg.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <m2ipg4zuoj.wl%randy@psg.com> <4FAB2A79.3090402@qualcomm.com> <m24nrozq83.wl%randy@psg.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: Thu, 10 May 2012 08:18:59 -0000

At 20:09 09-05-2012, Randy Bush wrote:
>participants should not call for sanctions.  they should point out to wg
>chairs, or ADs FACTS about questinable activity, non-disclosure, ...

Yes.

>and so forth.  i hope that this is not a witch hunt.  that it is not
>creating courts and guillotines.  we should assume people want to act in
>a responsible fashion and provide simple gentle paths to be taken when
>that assumption fails.

There are times when it is difficult to keep assuming that people are 
acting in a responsible fashion given the high levels of 
unpleasantness.  The situation can be such that simple gentle paths 
are ignored.

Fred Baker commented  [1]:

   "I'm concerned about people bringing baseless accusations, as
    yet another way to DOS a WG with IPR."

It only takes an IPR disclosure to make the WG work difficult.  It 
seems that an employer was not keen about the WG creation.

There are currently three IPR related issues affecting different 
working groups.  draft-farrresnickel-ipr-sanctions-05 does not affect 
any of these issues.  In one of these cases, the IPR disclosure 
happened after the document went through a Last Call.  A company gave 
up fighting a claim related to that IPR after spending US$1 million 
on lawyers.  If you write open source software, you stay away from 
IPR if you don't like the users of your software to receive ransom letters.

If someone wants to ask for sanctions, the person might have to file 
a third-party IPR disclosure first.  It is unlikely that there will 
be any action under draft-farrresnickel-ipr-sanctions-05 unless one 
of the WG participants is listed as an inventor.

At 23:46 09-05-2012, Brian E Carpenter wrote:
>Fair enough. I can't agree with SM though - as for appeals under RFC 2026,
>the person bringing up an issue really has to provide a factual summary,
>exactly to avoid witch hunts. It can be very short:

Agreed.

>    Hi, I noticed that US Patent 12345 was filed in March 2010, and
>    draft-blo-foobar was posted that June, and Jo Blo was an author
>    of both. It looks as if they describe the same method, so why
>    wasn't there an IPR disclosure in 2010? Would the WG Chairs consider
>    sanctions against Jo Blo appropriate?

That could be added as an example.

>Possible text:
>
>    Any IETF participant can draw attention to an apparent violation
>    of the IETF's IPR policy.  This can be done by sending email to
>    the appropriate IETF mailing list, including a short summary of
>    the known facts and, optionally, a call for sanctions to be
>    applied.

I suggested an adaptation of existing text from the draft based on 
Pete's comments.  I don't have a strong opinion about which text goes in.

 From the "island of stone money":

   "their island yields no metals, they had recourse to stone; stone,
    on which labour in fetching and fashioning has been expended, is
    as truly a representation of labour as the mined and minted coins
    of civilization."

    The German Government wanted the paths or highways, which were in
    bad condition to be repaired.  The commands to the chiefs of the
    districts remained unheeded.  It was decided to impose a fine by
    sending a man to mark a certain number of the stones with a cross
    in black paint.  "This instantly worked like a charm"; the people
    repaired the highways.

History will tell whether there is a parallel between the above and this draft.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg73287.html   


From john-ietf@jck.com  Thu May 10 01:35:20 2012
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 338D121F85F0 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:35:20 -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 bL1AbDQFVfCd for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:35:19 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A954621F85EE for <ietf@ietf.org>; Thu, 10 May 2012 01:35:19 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SSOkz-000MTx-I5; Thu, 10 May 2012 04:29:53 -0400
Date: Thu, 10 May 2012 04:35:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Subject: Re: Future Handling of Blue Sheets
Message-ID: <12F34D6725B91B95351EB144@JcK-HP8200.jck.com>
In-Reply-To: <4FAB7567.7070402@gondrom.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.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, 10 May 2012 08:35:20 -0000

--On Thursday, May 10, 2012 15:59 +0800 Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:

> John,
> 
> sorry, maybe I did not articulate myself precisely enough. I
> did not intend to say it would be published in real-time. What
> I wanted to communicate is that we would collect that data
> only during daytime and only with 2hours-granularity as it's
> only meeting attendance in which room you are (and publish it
> at any point in time later). However, we would keep it public
> indefinitely (in the proceedings).

Good.  My apologies for misunderstanding your intent.

> Like you, I am very cautious about broadcasting my travel
> plans. Plus, I am not only concerned about in advance and
> real-time, but also about broadcasting to the public places
> I've been in the past (or for that matter any personal
> information).

But it seems to me that takes us back to Russ's summary in that
it is normal, and arguably necessary, for a standards body to
record --and make available to those who are interested-- the
identities of those participating in meetings.

best regards,
   john


From tobias.gondrom@gondrom.org  Thu May 10 01:49:04 2012
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 1FA2321F85F6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:49:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.778
X-Spam-Level: 
X-Spam-Status: No, score=-96.778 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKGt5nfSFe64 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 01:49:03 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id CAB8521F85ED for <ietf@ietf.org>; Thu, 10 May 2012 01:49:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=Zr0hM1kcrVK53iB6IWFmP2pnlidqEaFeLc3p7Ds9uIC7PIel8kotWT2JwO+44mz/0OtMBYsDk4hH5w9wN4HgN6MtYZIzsE95QkfkodEvlQ5fxsMbUUE64M2pr05wTtED; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 3235 invoked from network); 10 May 2012 10:49:01 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 10:49:01 +0200
Message-ID: <4FAB80F9.40207@gondrom.org>
Date: Thu, 10 May 2012 16:48:57 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: john-ietf@jck.com
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com>
In-Reply-To: <12F34D6725B91B95351EB144@JcK-HP8200.jck.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: Thu, 10 May 2012 08:49:04 -0000

On 10/05/12 16:35, John C Klensin wrote:
>
> --On Thursday, May 10, 2012 15:59 +0800 Tobias Gondrom
> <tobias.gondrom@gondrom.org>  wrote:
>
>> John,
>>
>> sorry, maybe I did not articulate myself precisely enough. I
>> did not intend to say it would be published in real-time. What
>> I wanted to communicate is that we would collect that data
>> only during daytime and only with 2hours-granularity as it's
>> only meeting attendance in which room you are (and publish it
>> at any point in time later). However, we would keep it public
>> indefinitely (in the proceedings).
> Good.  My apologies for misunderstanding your intent.
>
>> Like you, I am very cautious about broadcasting my travel
>> plans. Plus, I am not only concerned about in advance and
>> real-time, but also about broadcasting to the public places
>> I've been in the past (or for that matter any personal
>> information).
> But it seems to me that takes us back to Russ's summary in that
> it is normal, and arguably necessary, for a standards body to
> record --and make available to those who are interested-- the
> identities of those participating in meetings.

I do not dispute that.
What I dispute is that "make available to those who are interested" 
necessarily leads to the need to broadcast the data (i.e. publish in the 
proceedings).
As we did in the past, we can equally achieve this openness by requiring 
that an interested person requests this data (including then providing 
his own identify) as we do at the moment.

Best regards, Tobias

> best regards,
>     john
>


From dougb@dougbarton.us  Thu May 10 02:10:03 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FED921F85F9 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.928
X-Spam-Level: 
X-Spam-Status: No, score=-2.928 tagged_above=-999 required=5 tests=[AWL=0.671,  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 0YNP9V0CWf5t for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:10:02 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB0C21F85F8 for <ietf@ietf.org>; Thu, 10 May 2012 02:10:01 -0700 (PDT)
Received: (qmail 24395 invoked by uid 399); 10 May 2012 09:09:59 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 10 May 2012 09:09:59 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4FAB85EA.7080608@dougbarton.us>
Date: Thu, 10 May 2012 02:10:02 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org>
In-Reply-To: <4FAB80F9.40207@gondrom.org>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Thu, 10 May 2012 09:10:03 -0000

On 5/10/2012 1:48 AM, Tobias Gondrom wrote:
> What I dispute is that "make available to those who are interested"
> necessarily leads to the need to broadcast the data (i.e. publish in the
> proceedings).

What is the harm you are trying to guard against by requiring the request?

Or, to take a completely different tack, given that there are a non-zero
number of people who think the data should be published, how do you
intend to deal with someone who makes the request, and then puts it up
on their own website?

I don't hesitate to criticize when I think that the IESG gets it wrong,
but in this case I think they threaded the needle about as well as it
could be threaded.

Doug

-- 
    If you're never wrong, you're not trying hard enough

From dwm@xpasc.com  Thu May 10 02:17:17 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B547C21F84FD for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Level: 
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5 tests=[AWL=-0.919, 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 rGJBV-WXg5Xn for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:17:17 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4FB21F843A for <ietf@ietf.org>; Thu, 10 May 2012 02:17:17 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 363BD3FBE7 for <ietf@ietf.org>; Thu, 10 May 2012 09:17:15 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q4A9HErr023369 for <ietf@ietf.org>; Thu, 10 May 2012 02:17:14 -0700
Date: Thu, 10 May 2012 02:17:14 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <4FAB80F9.40207@gondrom.org>
Message-ID: <alpine.LRH.2.01.1205100210140.23269@egate.xpasc.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a120AD3GD7Hu1vr-4A0217G
X-CLX-Spam: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 09:17:17 -0000

On Thu, 10 May 2012, Tobias Gondrom wrote:

> On 10/05/12 16:35, John C Klensin wrote:
> > But it seems to me that takes us back to Russ's summary in that
> > it is normal, and arguably necessary, for a standards body to
> > record --and make available to those who are interested-- the
> > identities of those participating in meetings.
> 
> I do not dispute that.
> What I dispute is that "make available to those who are interested"
> necessarily leads to the need to broadcast the data (i.e. publish in the
> proceedings).
> As we did in the past, we can equally achieve this openness by requiring that
> an interested person requests this data (including then providing his own
> identify) as we do at the moment.

I object to the quantum change in ease of access and persistence of the
information. I see way too much aggregation of personal information and
don't think open-ness is justification for increasing that potential.

One of the ways we deal with SPAM and DOS attacks is to intentionally slow
the process. Ted's proposal would be vastly improved with the provision
that access, once authenticated, was delayed approximately the same
amount of time as the current manual process. Propably with some
form of the failed login approach ... maximum requests per week or
other similar unit of time.

David Morris

From ynir@checkpoint.com  Thu May 10 02:35:53 2012
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 6B79421F8656 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.414
X-Spam-Level: 
X-Spam-Status: No, score=-10.414 tagged_above=-999 required=5 tests=[AWL=0.185, 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 8QlBGrPud-nc for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:35:52 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 79BC421F8655 for <ietf@ietf.org>; Thu, 10 May 2012 02:35:52 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4A9ZbpS027283;  Thu, 10 May 2012 12:35:39 +0300
X-CheckPoint: {4FAB9956-3-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 10 May 2012 12:35:37 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 10 May 2012 12:35:30 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Doug Barton <dougb@dougbarton.us>
Date: Thu, 10 May 2012 12:35:01 +0300
Subject: Re: Future Handling of Blue Sheets
Thread-Topic: Future Handling of Blue Sheets
Thread-Index: Ac0ukD2fgxl+vBq7SmyCzDGGC9byjQ==
Message-ID: <CE1FAD6B-C8D6-4BBC-9938-1E3A34B51782@checkpoint.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org>	<5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org>	<12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org> <4FAB85EA.7080608@dougbarton.us>
In-Reply-To: <4FAB85EA.7080608@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean
Cc: "john-ietf@jck.com" <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: Thu, 10 May 2012 09:35:53 -0000

On May 10, 2012, at 12:10 PM, Doug Barton wrote:

> On 5/10/2012 1:48 AM, Tobias Gondrom wrote:
>> What I dispute is that "make available to those who are interested"
>> necessarily leads to the need to broadcast the data (i.e. publish in the
>> proceedings).
>=20
> What is the harm you are trying to guard against by requiring the request=
?

Well, there's the obvious issue of spam, although this post that I'm making=
 right now provides my email address to the spammers in a much more conveni=
ent form. It's also convenient for headhunters. It also allows my employer =
to check whether I really went to sessions instead of just touring Paris. I=
s it the business of the IETF to help in these activities?

I still don't get why you would want this published. My name on a blue shee=
t could mean that I was presenting for half the session, or that I was at t=
he mike telling people they were wrong, or just sitting quietly in the back=
 minding my own business and reading email. Blue sheets (unlike minutes and=
 jabber logs) don't make such a distinction.

> Or, to take a completely different tack, given that there are a non-zero
> number of people who think the data should be published, how do you
> intend to deal with someone who makes the request, and then puts it up
> on their own website?

I think this would be a copyright violation, unless the IETF specifically a=
uthorized them to do so (which it shouldn't). I don't think the IETF should=
 prosecute, but it's still a violation.

> I don't hesitate to criticize when I think that the IESG gets it wrong,
> but in this case I think they threaded the needle about as well as it
> could be threaded.

I think that needle should not be threaded at all. A list of participants s=
hould maybe be kept (scanned or not) but never published without subpoena, =
just as it is now. I don't see any reason why publishing it (as opposed to =
recording actual participation) is a requirement for an open process.

Yoav


From tobias.gondrom@gondrom.org  Thu May 10 02:42:50 2012
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 A4F4D21F85E4 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.478
X-Spam-Level: 
X-Spam-Status: No, score=-96.478 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_82=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 4r24zrN6U3YI for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:42:50 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id 96BB821F84FB for <ietf@ietf.org>; Thu, 10 May 2012 02:42:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=pmTHvogS8WLIBKYSKKdIS7xdr88EjU8zyweOS7E2/ftj4YyBOIbRx/CH0uzGNIk2qSXPQX4KLzX5442yCDFF5SvA6v++LYYXhTRr9tPAOz58hBocSRyrJcy+GT4bYREa; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 3487 invoked from network); 10 May 2012 11:42:46 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 11:42:46 +0200
Message-ID: <4FAB8D91.5060201@gondrom.org>
Date: Thu, 10 May 2012 17:42:41 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: dougb@dougbarton.us
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org> <4FAB85EA.7080608@dougbarton.us>
In-Reply-To: <4FAB85EA.7080608@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 10 May 2012 09:42:50 -0000

Doug,

you are right in the end I can not prevent someone else from publishing 
this. Even today a party that subpoena'ed them might publish the data. 
(Or a person might just take a photo of the blue sheet in the room and 
publish that...)

Of course we can not control other people's actions, however the 
question remains whether we (as the IETF) do publish that data and how 
easy/fast we make it for others to publish that data.

Just to be clear, I agree basically with most of the proposal from the 
IESG.*
But when it comes to privacy I think we must be extremely careful and 
conservative with information, only releasing information where it 
really adds benefit to transparency. Because once released, it's 
impossible to get it back.
Thinking about how to thread the needle (as you put it), I don't agree 
that the current proposal is optimal, and I would reiterate my proposal 
to not publish the bluesheets in the proceedings but to make them 
available to an individual upon email request to the IETF secretariat, 
providing name and email of the requesting person (and with a disclaimer 
in the IETF answer that this information is not meant to be re-published 
to the public (note I intentionally say "public", i.e. sharing among 
groups would still be ok.)).
If we are worried about high volumes of requests, I would like to ask 
for more information on current volumes of subpoenas and why we get high 
volumes in the future. And if it's really too cumbersome for a person to 
answer the requests, we could then still discuss to use an email account 
based request system (IETF tools login) as proposed by Ted yesterday.

Best regards, Tobias


Ps.: *just as a disclaimer regarding the scanning part of the IESG 
proposal: I like it, but IMHO I would be slightly more cautious than the 
IETF counsel with the admissibility of scanned documents in court 
compared to paper originals. I've experienced quite some cases and legal 
discussions around value of proof of scanned documents.... - what I 
basically learned there was: scanning is ok in most IP jurisdictions, 
but handling the scanned data must use well documented procedures and 
access controls to keep the same level of non-repudiation of integrity 
and authenticity later in court.


On 10/05/12 17:10, Doug Barton wrote:
> On 5/10/2012 1:48 AM, Tobias Gondrom wrote:
>> What I dispute is that "make available to those who are interested"
>> necessarily leads to the need to broadcast the data (i.e. publish in the
>> proceedings).
> What is the harm you are trying to guard against by requiring the request?
>
> Or, to take a completely different tack, given that there are a non-zero
> number of people who think the data should be published, how do you
> intend to deal with someone who makes the request, and then puts it up
> on their own website?
>
> I don't hesitate to criticize when I think that the IESG gets it wrong,
> but in this case I think they threaded the needle about as well as it
> could be threaded.
>
> Doug
>


From tobias.gondrom@gondrom.org  Thu May 10 02:43:13 2012
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 E4F2A21F866E for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.735
X-Spam-Level: 
X-Spam-Status: No, score=-96.735 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2NXyzonGOj1 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 02:43:13 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (www.gondrom.org [83.169.7.107]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAAF21F866C for <ietf@ietf.org>; Thu, 10 May 2012 02:43:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=rd8HUd+t9O8a4g9PiPPwxP91UsinWDVHtA1KidXiCTow0dFs8XaqyoUNKbMim4xPa9aFPhnxyUG5FzOn8kpETfiJGknyxF/wUMkKwG51NCHENprFQwpL2jY3krS9xc30; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 3515 invoked from network); 10 May 2012 11:43:11 +0200
Received: from n2028211917.imsbiz.com (HELO ?10.65.1.159?) (202.82.119.17) by www.gondrom.org with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 May 2012 11:43:10 +0200
Message-ID: <4FAB8DA9.6060104@gondrom.org>
Date: Thu, 10 May 2012 17:43:05 +0800
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ynir@checkpoint.com
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org>	<5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org>	<12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org> <4FAB85EA.7080608@dougbarton.us> <CE1FAD6B-C8D6-4BBC-9938-1E3A34B51782@checkpoint.com>
In-Reply-To: <CE1FAD6B-C8D6-4BBC-9938-1E3A34B51782@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 10 May 2012 09:43:14 -0000

+1
Agree with Yoav.
BR, Tobias

On 10/05/12 17:35, Yoav Nir wrote:
> On May 10, 2012, at 12:10 PM, Doug Barton wrote:
>
>> On 5/10/2012 1:48 AM, Tobias Gondrom wrote:
>>> What I dispute is that "make available to those who are interested"
>>> necessarily leads to the need to broadcast the data (i.e. publish in the
>>> proceedings).
>> What is the harm you are trying to guard against by requiring the request?
> Well, there's the obvious issue of spam, although this post that I'm making right now provides my email address to the spammers in a much more convenient form. It's also convenient for headhunters. It also allows my employer to check whether I really went to sessions instead of just touring Paris. Is it the business of the IETF to help in these activities?
>
> I still don't get why you would want this published. My name on a blue sheet could mean that I was presenting for half the session, or that I was at the mike telling people they were wrong, or just sitting quietly in the back minding my own business and reading email. Blue sheets (unlike minutes and jabber logs) don't make such a distinction.
>
>> Or, to take a completely different tack, given that there are a non-zero
>> number of people who think the data should be published, how do you
>> intend to deal with someone who makes the request, and then puts it up
>> on their own website?
> I think this would be a copyright violation, unless the IETF specifically authorized them to do so (which it shouldn't). I don't think the IETF should prosecute, but it's still a violation.
>
>> I don't hesitate to criticize when I think that the IESG gets it wrong,
>> but in this case I think they threaded the needle about as well as it
>> could be threaded.
> I think that needle should not be threaded at all. A list of participants should maybe be kept (scanned or not) but never published without subpoena, just as it is now. I don't see any reason why publishing it (as opposed to recording actual participation) is a requirement for an open process.
>
> Yoav
>


From hsantos@isdg.net  Thu May 10 03:05:02 2012
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 56B8121F86A4 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level: 
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=0.549,  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 96AZzRf78Ltl for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:05:01 -0700 (PDT)
Received: from dkim.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D10DC21F86A1 for <ietf@ietf.org>; Thu, 10 May 2012 03:05:00 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2972; t=1336644291; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=P0xVWCW82TsfhhHFMFMpEuANsPI=; b=BJvf3vujz/km74cYu0f9 AmHmcy5nXanl89h0vHglFgLBoyKs1LcxuPi5Wbvc7mBfic7UJgDwBoJC3i9huAOb PILmajpS7RBd7T5YCqitmJHsmY/qHmASp8haLjASQBLIYyrLAFKvCNG4V0xJ8JSv ZGnSJ6zl3X0FD0b2ojK7Khk=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:04:51 -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 v6.4.454.1) with ESMTP id 1256125033.53896.4744; Thu, 10 May 2012 06:04:50 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2972; t=1336644278; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ZOls+Im mpN22yw/jwNBJ7QTwH/Ud8JvadkMT7blnisA=; b=TO8bokMUlNUanrnl8zCZnb5 ZJYX+Z2lgwnqCyXjuhaTzvZnw1z1mOnLlM+AiYp//8SxIYi9WiW23h5OpY+ttenC 7vTEu0V576bQ0wcBC1NLNRY+vg8OVvb1zXZ1REovgZCxknA4AHwZbP3NAO9tssFx 6dzkGo9dIveW1qn0qTmM=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:04:38 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1855010800.5934.7964; Thu, 10 May 2012 06:04:37 -0400
Message-ID: <4FAB92BF.8090408@isdg.net>
Date: Thu, 10 May 2012 06:04:47 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR	Policy)	to	Informational RFC
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<4FAAD14F.40009@qualcomm.com>	<6.2.5.6.2.20120509150640.090d7098@resistor.net>	<AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>	<4FAB2563.3090309@qualcomm.com> <4FAB643C.108@gmail.com>
In-Reply-To: <4FAB643C.108@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@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 May 2012 10:05:02 -0000

Brian E Carpenter wrote:
> 
> Fair enough. I can't agree with SM though - as for appeals under RFC 2026,
> the person bringing up an issue really has to provide a factual summary,
> exactly to avoid witch hunts. It can be very short:
> 
>    Hi, I noticed that US Patent 12345 was filed in March 2010, and
>    draft-blo-foobar was posted that June, and Jo Blo was an author
>    of both. It looks as if they describe the same method, so why
>    wasn't there an IPR disclosure in 2010? Would the WG Chairs consider
>    sanctions against Jo Blo appropriate?
> 
> Possible text:
> 
>    Any IETF participant can draw attention to an apparent violation
>    of the IETF's IPR policy.  This can be done by sending email to
>    the appropriate IETF mailing list, including a short summary of
>    the known facts and, optionally, a call for sanctions to be
>    applied.

+1.

I think the major part of the issue is the growing potential and ease 
to violate BCP79 section 6.2.1 in regards to belated patent filings 
after contributions are made as your above "Jo Blo" scenario reflects.

With the relaxation of patentability guidelines, software/business 
methods and availability of low cost Provisional Patents, it is far 
easier to fall trap to violation BCP79 6.2.1

Provisional Patents is the cheapest way to begin the patent process 
allowing up to one year to complete the full patent. This is an ideal 
way to first test the market which also legally allows the usage of 
"Patent Pending" in marketing material.  If the I-D gets no interest, 
then there is little cost (less than $200) lost to forget about the 
work.  In one year, the provisional patent expires.  There is 
strategic value not to disclose IP related information in the I-D 
perhaps to maximize interest and perhaps this is a IETF new dilemma 
the draft should also focus on and address.

For example, in the draft 2.1, the 3rd paragraph talks about 
"Timeliness" and specifically states:

    The timeliness of disclosure is very important within [BCP79].  No
    precise definition of "timeliness" is given in [BCP79] and it is not
    the purpose of this document to do so.

However, where provisional patent filings are in play, there is at 
least 1 year allowance and incentive to not disclose and that could be 
a problem depending on the speed and interest of the I-D development. 
The draft intro can highlight belated IPR disclosures and section 2.1 
first paragraph, for example, can add:

    According to [BCP79], individual IETF participants have a
    personal responsibility to disclose or ensure the timely disclosure
    of IPR of which they are aware or plan to create .....

So overall, more text emphasizing specifically BC979 section 6.2.1 to 
help highlight the awareness for document authors with a goal to lower 
the concerns of implementators who are watchful of protocols having 
current IPR disclosures and now belated IPR disclosure issues which 
much easier to occur today.

-- 
HLS




From peter.sylvester@edelweb.fr  Thu May 10 03:51:09 2012
Return-Path: <peter.sylvester@edelweb.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 7E2E321F863D for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:51: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8Hmpp9BczgP for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:51:09 -0700 (PDT)
Received: from mx1.on-x.com (mx1.on-x.com [92.103.215.13]) by ietfa.amsl.com (Postfix) with ESMTP id D9B2921F8643 for <ietf@ietf.org>; Thu, 10 May 2012 03:51:08 -0700 (PDT)
Received: from varuna.puteaux.on-x (varuna.puteaux.on-x [192.168.10.6]) by mx1.on-x.com (Postfix) with ESMTP id A7B927DB3 for <ietf@ietf.org>; Thu, 10 May 2012 12:51:07 +0200 (CEST)
Received: from smtps.on-x.com (mintaka.puteaux.on-x [192.168.14.11]) by varuna.puteaux.on-x (Postfix) with ESMTP id 9F3A45C4648 for <ietf@ietf.org>; Thu, 10 May 2012 12:43:17 +0200 (CEST)
Received: from [192.168.0.27] (gut75-3-82-227-163-182.fbx.proxad.net [82.227.163.182]) by smtps.on-x.com (Postfix) with ESMTPSA id A091D236373 for <ietf@ietf.org>; Thu, 10 May 2012 06:44:38 -0400 (EDT)
Message-ID: <4FAB9D9B.9020402@edelweb.fr>
Date: Thu, 10 May 2012 12:51:07 +0200
From: Peter Sylvester <peter.sylvester@edelweb.fr>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org> <alpine.LRH.2.01.1205100210140.23269@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1205100210140.23269@egate.xpasc.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: Thu, 10 May 2012 10:51:09 -0000

On 05/10/2012 11:17 AM, David Morris wrote:
> I object to the quantum change in ease of access and persistence of the
> information. I see way too much aggregation of personal information and
> don't think open-ness is justification for increasing that potential.
>
+1


From hsantos@isdg.net  Thu May 10 03:55:57 2012
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 2A25C21F8669 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.056
X-Spam-Level: 
X-Spam-Status: No, score=-2.056 tagged_above=-999 required=5 tests=[AWL=0.543,  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 Xg8QIxb1Wv0C for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 03:55:56 -0700 (PDT)
Received: from dkim.winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B32EE21F8510 for <ietf@ietf.org>; Thu, 10 May 2012 03:55:55 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4809; t=1336647352; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=y23Oap79D0pJ5xi9QQ/AuluTEeE=; b=CJdWirUbBB84NTUSfGHE QFrYuQxlC3OZlXrr5tm1+XoH1kqDT3jAYuGOQ9YoGgSQqDNPn4RBur8GZs6aid2s RL5ys6a0eLkiyTv7XJ3zMa28W8lLGQqD3TSmSdX1zOK4+acVjdXRb2wGtkPSLh90 +TKkhhQ9aahWIuoJl88JGMM=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:55:52 -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 v6.4.454.1) with ESMTP id 1259185476.53896.5336; Thu, 10 May 2012 06:55:51 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4809; t=1336647339; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=XdvWO1g BlkGlmBByC6Y/mfJsaQGjK01jFreQi1FnDKw=; b=fr0NUZeXU29n+Qpb/lMh4UX CPtTrh6D2dVEVMUa1g9D6kwFkvWttgB0F0X6CawQEPrA55Fj/5BjIF2Kdl/LMro8 TVKHcS7iNklGEOFhtZAQfYGO6rhZWUBGnNgzAKyuS3iCO20R+EoEKszdCYS7OrFW sfLGsgRLT2HgE68/tY0o=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Thu, 10 May 2012 06:55:39 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 1858071644.5939.364; Thu, 10 May 2012 06:55:38 -0400
Message-ID: <4FAB9EB4.8020704@isdg.net>
Date: Thu, 10 May 2012 06:55:48 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
Subject: Leverage Patent Search API to reduce BCP79 related issues [was: Re: Last Call: draft-farrresnickel-ipr-sanctions-05.txt]
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<4FAAD14F.40009@qualcomm.com>	<6.2.5.6.2.20120509150640.090d7098@resistor.net>	<AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>	<4FAB2563.3090309@qualcomm.com>	<4FAB643C.108@gmail.com> <4FAB92BF.8090408@isdg.net>
In-Reply-To: <4FAB92BF.8090408@isdg.net>
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
Cc: Pete Resnick <presnick@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 May 2012 10:55:57 -0000

Always looking for automated solutions, perhaps the IETF I-D 
submissions process should include a patent database query check using 
document authors, document titles, abstract, keywords etc to find 
possible exact or near filings made, and if any are found, it can 
report immediately at the web site and/or send as part of the I-D 
submission confirmation message, something like so:

    NOTE: IPR INFORMATION FOUND, PLEASE VERIFY IF ANY OF THE FOLLOWING 
APPLIES:

    o US PATENT 12345 [title/abstract]
    o US PATENT 22202 [title/abstract]
    o including non-US patents found

The IETF I-D submission code can use a backend HTTP REST query using 
the Google Patent Search API.

Oh gosh, testing how this made work with my current I-D work:

     http://tools.ietf.org/html/draft-santos-smtpgrey-02

If the IETF I-D submission process did include a HTTP REST query with 
I-D extracted keywords such as: SMTP Extension Greylisting:

 
http://www.google.com/search?tbo=p&tbm=pts&hl=en&q=SMTP+Extension+Greylisting&num=10

then I-D submission confirmation message would of said:

    NOTE: IPR INFORMATION FOUND, PLEASE VERIFY IF ANY OF THE FOLLOWING 
APPLIES:

    o US PATENT 7849142
      Managing connections, messages, and directory harvest attacks at 
a server

And now I need to see if this needs applies or needs to be referenced 
in my I-D.

Either way, I think the IETF should consider using backend patent API 
searches with the services available.  I can see how can probably 
reduce a big part of the BCP79 related concerns.  Sometimes these IP 
things are not always obvious for I-D contributors.

-- 
Hector Santos
http://www.santronics.com
http://hector.wildcatblog.com
jabber: hector@jabber.isdg.net

Hector Santos wrote:
> Brian E Carpenter wrote:
>>
>> Fair enough. I can't agree with SM though - as for appeals under RFC 
>> 2026,
>> the person bringing up an issue really has to provide a factual summary,
>> exactly to avoid witch hunts. It can be very short:
>>
>>    Hi, I noticed that US Patent 12345 was filed in March 2010, and
>>    draft-blo-foobar was posted that June, and Jo Blo was an author
>>    of both. It looks as if they describe the same method, so why
>>    wasn't there an IPR disclosure in 2010? Would the WG Chairs consider
>>    sanctions against Jo Blo appropriate?
>>
>> Possible text:
>>
>>    Any IETF participant can draw attention to an apparent violation
>>    of the IETF's IPR policy.  This can be done by sending email to
>>    the appropriate IETF mailing list, including a short summary of
>>    the known facts and, optionally, a call for sanctions to be
>>    applied.
> 
> +1.
> 
> I think the major part of the issue is the growing potential and ease to 
> violate BCP79 section 6.2.1 in regards to belated patent filings after 
> contributions are made as your above "Jo Blo" scenario reflects.
> 
> With the relaxation of patentability guidelines, software/business 
> methods and availability of low cost Provisional Patents, it is far 
> easier to fall trap to violation BCP79 6.2.1
> 
> Provisional Patents is the cheapest way to begin the patent process 
> allowing up to one year to complete the full patent. This is an ideal 
> way to first test the market which also legally allows the usage of 
> "Patent Pending" in marketing material.  If the I-D gets no interest, 
> then there is little cost (less than $200) lost to forget about the 
> work.  In one year, the provisional patent expires.  There is strategic 
> value not to disclose IP related information in the I-D perhaps to 
> maximize interest and perhaps this is a IETF new dilemma the draft 
> should also focus on and address.
> 
> For example, in the draft 2.1, the 3rd paragraph talks about 
> "Timeliness" and specifically states:
> 
>    The timeliness of disclosure is very important within [BCP79].  No
>    precise definition of "timeliness" is given in [BCP79] and it is not
>    the purpose of this document to do so.
> 
> However, where provisional patent filings are in play, there is at least 
> 1 year allowance and incentive to not disclose and that could be a 
> problem depending on the speed and interest of the I-D development. The 
> draft intro can highlight belated IPR disclosures and section 2.1 first 
> paragraph, for example, can add:
> 
>    According to [BCP79], individual IETF participants have a
>    personal responsibility to disclose or ensure the timely disclosure
>    of IPR of which they are aware or plan to create .....
> 
> So overall, more text emphasizing specifically BC979 section 6.2.1 to 
> help highlight the awareness for document authors with a goal to lower 
> the concerns of implementators who are watchful of protocols having 
> current IPR disclosures and now belated IPR disclosure issues which much 
> easier to occur today.
> 




From jason_livingood@cable.comcast.com  Thu May 10 05:13:38 2012
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 0860521F8644 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 05:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.756
X-Spam-Level: 
X-Spam-Status: No, score=-100.756 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, 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 yjfcOBTLlKmp for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 05:13:37 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 764D621F8618 for <ietf@ietf.org>; Thu, 10 May 2012 05:13:37 -0700 (PDT)
Received: from ([24.40.56.115]) by pacdcavaout01.cable.comcast.com with ESMTP  id 97wm3m1.12010694; Thu, 10 May 2012 08:05:41 -0400
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0283.003; Thu, 10 May 2012 08:13:32 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Topic: Last Call: <draft-farrresnickel-ipr-sanctions-05.txt> (Sanctions Available for Application to Violators of IETF IPR Policy) to Informational RFC
Thread-Index: AQHNLqZQRIuTvI8Sc0OaypDUerDuTg==
Date: Thu, 10 May 2012 12:13:31 +0000
Message-ID: <CBD12356.5E2FD%jason_livingood@cable.comcast.com>
In-Reply-To: <6.2.5.6.2.20120509210747.0a901d38@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.55.70]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9376F9BD0047004FB389E0EF98796AAB@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 12:13:38 -0000

On 5/10/12 2:30 AM, "SM" <sm@resistor.net> wrote:

>There are times when it is difficult to keep assuming that people are
>acting in a responsible fashion given the high levels of
>unpleasantness.  The situation can be such that simple gentle paths
>are ignored.

This is IMO perhaps more a reflection of the bizarre state of patent laws
for software, processes, and methods around the world than the collective
maliciousness of IETF participants.

We may surely have some people with bad intentions but I think by and
large it's more 'we're engineers and it's hard to figure out all this
patent stuff' -- especially when the law keeps changing. Were it easy, the
discussion/update a few years ago if IETF IPR policy would have taken only
a week or two.=20

I see the risks here including that this is the start of masses of lawyers
showing up at every IETF, etc. That'd kinda be a bummer (no offense to
lawyers).=20

Jason


From nick@inex.ie  Thu May 10 05:47:34 2012
Return-Path: <nick@inex.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 3E44A21F8527 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 05:47: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 a1gouJSDuCsz for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 05:47:33 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id E7E5121F8483 for <ietf@ietf.org>; Thu, 10 May 2012 05:47:32 -0700 (PDT)
X-Envelope-To: <ietf@ietf.org>
Received: from cupcake.local ([IPv6:2001:1bb8:2004:100:c94:487f:4ca3:7417]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4ACkwSe075388 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 10 May 2012 13:46:58 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FABB8E1.6040604@inex.ie>
Date: Thu, 10 May 2012 13:47:29 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was: Re: Last Call: draft-farrresnickel-ipr-sanctions-05.txt]
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<4FAAD14F.40009@qualcomm.com>	<6.2.5.6.2.20120509150640.090d7098@resistor.net>	<AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>	<4FAB2563.3090309@qualcomm.com>	<4FAB643C.108@gmail.com> <4FAB92BF.8090408@isdg.net> <4FAB9EB4.8020704@isdg.net>
In-Reply-To: <4FAB9EB4.8020704@isdg.net>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
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, 10 May 2012 12:47:34 -0000

On 10/05/2012 11:55, Hector Santos wrote:
> Always looking for automated solutions, perhaps the IETF I-D submissions
> process should include a patent database query check using document
> authors, document titles, abstract, keywords etc to find possible exact or
> near filings made, and if any are found, it can report immediately at the
> web site and/or send as part of the I-D submission confirmation message,
> something like so:

The world is a large place.  If this process is implemented, it might also
be wise to search other large patent offices.  In order of population size:

- China Patent and Trademark Office
- The Patent Office of India
- European Patent Office
- USPTO
- Japan Patent Office

A more complete list can be found here:

http://www.wipo.int/directory/en/urls.jsp

The european and chinese patent offices would seem to be of at least equal
significance to the USPTO, on the basis that they are the relevant
intellectual property agencies for the #1 and #3 global economic powers.
Japan comes in at #4.

This will create Interesting Problems in terms of getting appropriate clue
to search chinese and japanese patent databases.

Nick

From mrex@sap.com  Thu May 10 06:04:25 2012
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 93EE221F8648 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 06:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.077
X-Spam-Level: 
X-Spam-Status: No, score=-10.077 tagged_above=-999 required=5 tests=[AWL=0.172, 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 3yTHI5zljdIR for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 06:04:24 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 600BA21F863D for <ietf@ietf.org>; Thu, 10 May 2012 06:04:24 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q4AD4MW0017064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 15:04:22 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101304.q4AD4LCv013256@fs4113.wdf.sap.corp>
Subject: Re: Future Handling of Blue Sheets
To: peter.sylvester@edelweb.fr (Peter Sylvester)
Date: Thu, 10 May 2012 15:04:21 +0200 (MEST)
In-Reply-To: <4FAB9D9B.9020402@edelweb.fr> from "Peter Sylvester" at May 10, 12 12:51:07 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 10 May 2012 13:04:25 -0000

Peter Sylvester wrote:
> 
> On 05/10/2012 11:17 AM, David Morris wrote:
> > I object to the quantum change in ease of access and persistence of the
> > information. I see way too much aggregation of personal information and
> > don't think open-ness is justification for increasing that potential.
> >
> +1
 
+1


From housley@vigilsec.com  Thu May 10 08:56:54 2012
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 2E46421F86D1 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 08:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.499
X-Spam-Level: 
X-Spam-Status: No, score=-92.499 tagged_above=-999 required=5 tests=[AWL=-9.900, BAYES_00=-2.599, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71TryfDf2mgQ for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 08:56:49 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id AECA621F8672 for <ietf@ietf.org>; Thu, 10 May 2012 08:56:49 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 47AF89A471B; Thu, 10 May 2012 11:57:09 -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 elyCsTZp9Q35; Thu, 10 May 2012 11:56:27 -0400 (EDT)
Received: from [10.0.1.181] (82.ffbccf.client.atlantech.net [207.188.255.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4D6259A470F; Thu, 10 May 2012 11:57:04 -0400 (EDT)
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was: Re: Last Call: draft-farrresnickel-ipr-sanctions-05.txt]
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FAB9EB4.8020704@isdg.net>
Date: Thu, 10 May 2012 11:56:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com>	<4FAA140B.4010703@gmail.com>	<4FAAD14F.40009@qualcomm.com>	<6.2.5.6.2.20120509150640.090d7098@resistor.net>	<AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com>	<4FAB2563.3090309@qualcomm.com>	<4FAB643C.108@gmail.com> <4FAB92BF.8090408@isdg.net> <4FAB9EB4.8020704@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1084)
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, 10 May 2012 15:56:54 -0000

BCP 79 says:

      "Reasonably and personally known": means something an individual
      knows personally or, because of the job the individual holds,
      would reasonably be expected to know.  This wording is used to
      indicate that an organization cannot purposely keep an individual
      in the dark about patents or patent applications just to avoid the
      disclosure requirement.  But this requirement should not be
      interpreted as requiring the IETF Contributor or participant (or
      his or her represented organization, if any) to perform a patent
      search to find applicable IPR.

Your suggestion seems to be in direct conflict with BCP 79.

Russ


On May 10, 2012, at 6:55 AM, Hector Santos wrote:

> Always looking for automated solutions, perhaps the IETF I-D =
submissions process should include a patent database query check using =
document authors, document titles, abstract, keywords etc to find =
possible exact or near filings made, and if any are found, it can report =
immediately at the web site and/or send as part of the I-D submission =
confirmation message, something like so:
>=20
>   NOTE: IPR INFORMATION FOUND, PLEASE VERIFY IF ANY OF THE FOLLOWING =
APPLIES:
>=20
>   o US PATENT 12345 [title/abstract]
>   o US PATENT 22202 [title/abstract]
>   o including non-US patents found
>=20
> The IETF I-D submission code can use a backend HTTP REST query using =
the Google Patent Search API.
>=20
> Oh gosh, testing how this made work with my current I-D work:
>=20
>    http://tools.ietf.org/html/draft-santos-smtpgrey-02
>=20
> If the IETF I-D submission process did include a HTTP REST query with =
I-D extracted keywords such as: SMTP Extension Greylisting:
>=20
> =
http://www.google.com/search?tbo=3Dp&tbm=3Dpts&hl=3Den&q=3DSMTP+Extension+=
Greylisting&num=3D10
>=20
> then I-D submission confirmation message would of said:
>=20
>   NOTE: IPR INFORMATION FOUND, PLEASE VERIFY IF ANY OF THE FOLLOWING =
APPLIES:
>=20
>   o US PATENT 7849142
>     Managing connections, messages, and directory harvest attacks at a =
server
>=20
> And now I need to see if this needs applies or needs to be referenced =
in my I-D.
>=20
> Either way, I think the IETF should consider using backend patent API =
searches with the services available.  I can see how can probably reduce =
a big part of the BCP79 related concerns.  Sometimes these IP things are =
not always obvious for I-D contributors.
>=20
> --=20
> Hector Santos
> http://www.santronics.com
> http://hector.wildcatblog.com
> jabber: hector@jabber.isdg.net
>=20
> Hector Santos wrote:
>> Brian E Carpenter wrote:
>>>=20
>>> Fair enough. I can't agree with SM though - as for appeals under RFC =
2026,
>>> the person bringing up an issue really has to provide a factual =
summary,
>>> exactly to avoid witch hunts. It can be very short:
>>>=20
>>>   Hi, I noticed that US Patent 12345 was filed in March 2010, and
>>>   draft-blo-foobar was posted that June, and Jo Blo was an author
>>>   of both. It looks as if they describe the same method, so why
>>>   wasn't there an IPR disclosure in 2010? Would the WG Chairs =
consider
>>>   sanctions against Jo Blo appropriate?
>>>=20
>>> Possible text:
>>>=20
>>>   Any IETF participant can draw attention to an apparent violation
>>>   of the IETF's IPR policy.  This can be done by sending email to
>>>   the appropriate IETF mailing list, including a short summary of
>>>   the known facts and, optionally, a call for sanctions to be
>>>   applied.
>> +1.
>> I think the major part of the issue is the growing potential and ease =
to violate BCP79 section 6.2.1 in regards to belated patent filings =
after contributions are made as your above "Jo Blo" scenario reflects.
>> With the relaxation of patentability guidelines, software/business =
methods and availability of low cost Provisional Patents, it is far =
easier to fall trap to violation BCP79 6.2.1
>> Provisional Patents is the cheapest way to begin the patent process =
allowing up to one year to complete the full patent. This is an ideal =
way to first test the market which also legally allows the usage of =
"Patent Pending" in marketing material.  If the I-D gets no interest, =
then there is little cost (less than $200) lost to forget about the =
work.  In one year, the provisional patent expires.  There is strategic =
value not to disclose IP related information in the I-D perhaps to =
maximize interest and perhaps this is a IETF new dilemma the draft =
should also focus on and address.
>> For example, in the draft 2.1, the 3rd paragraph talks about =
"Timeliness" and specifically states:
>>   The timeliness of disclosure is very important within [BCP79].  No
>>   precise definition of "timeliness" is given in [BCP79] and it is =
not
>>   the purpose of this document to do so.
>> However, where provisional patent filings are in play, there is at =
least 1 year allowance and incentive to not disclose and that could be a =
problem depending on the speed and interest of the I-D development. The =
draft intro can highlight belated IPR disclosures and section 2.1 first =
paragraph, for example, can add:
>>   According to [BCP79], individual IETF participants have a
>>   personal responsibility to disclose or ensure the timely disclosure
>>   of IPR of which they are aware or plan to create .....
>> So overall, more text emphasizing specifically BC979 section 6.2.1 to =
help highlight the awareness for document authors with a goal to lower =
the concerns of implementators who are watchful of protocols having =
current IPR disclosures and now belated IPR disclosure issues which much =
easier to occur today.
>=20
>=20
>=20


From mrex@sap.com  Thu May 10 09:31:51 2012
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 C29B821F870A for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.079
X-Spam-Level: 
X-Spam-Status: No, score=-10.079 tagged_above=-999 required=5 tests=[AWL=0.170, 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 gtxb+W3L7Tpn for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:31:48 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8000721F8705 for <ietf@ietf.org>; Thu, 10 May 2012 09:31:48 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q4AGVjws010110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 18:31:45 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was:
To: housley@vigilsec.com (Russ Housley)
Date: Thu, 10 May 2012 18:31:44 +0200 (MEST)
In-Reply-To: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com> from "Russ Housley" at May 10, 12 11:56:42 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 10 May 2012 16:31:51 -0000

Russ Housley wrote:
> 
> BCP 79 says:
> 
>       "Reasonably and personally known": means something an individual
>       knows personally or, because of the job the individual holds,
>       would reasonably be expected to know.  This wording is used to
>       indicate that an organization cannot purposely keep an individual
>       in the dark about patents or patent applications just to avoid the
>       disclosure requirement.  But this requirement should not be
>       interpreted as requiring the IETF Contributor or participant (or
>       his or her represented organization, if any) to perform a patent
>       search to find applicable IPR.
> 
> Your suggestion seems to be in direct conflict with BCP 79.


IMHO your quote from BCP79 (page 4, bullet l.) is a very important
point in BCP79.  I can not speak for others, but the Internet Proxy
of our company blocks urls to all "well known" online patent search
and patent publication sites (and these are the only blocked sites
I've ever encountered) for the simple reason of the insane US patent
laws with this 3-fold "punitive damages" for "willful infringement"
of a patent, i.e. a patent that was known to exist when shipping.
As engineers, we MUST NOT read any patents because of this.
All of the patent reasarch stuff is done by patent lawyers exclusively.

btw. I personally know only about one patent where I refused to be
listed as inventor because I considered my contribution to it to be
"obvious to someone skilled in the technology".  When I read the
description after it had been processed by patent lawyers, I had
serious difficulties understanding what that text meant...


-Martin

From john@jck.com  Thu May 10 00:09:20 2012
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 7BA2F21F85C6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ji+VxKak+2rm for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 00:09:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DC0C721F85AF for <ietf@ietf.org>; Thu, 10 May 2012 00:09:19 -0700 (PDT)
Received: from localhost ([::1] helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1SSNPh-000MA1-Nj; Thu, 10 May 2012 03:03:49 -0400
Date: Thu, 10 May 2012 03:09:15 -0400
From: John C Klensin <john@jck.com>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>, ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
Message-ID: <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com>
In-Reply-To: <4FAB5ED8.7070004@gondrom.org>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.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
X-Mailman-Approved-At: Thu, 10 May 2012 09:34:55 -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, 10 May 2012 07:09:20 -0000

(top post) 
Tobias,

Constructing and then attacking strawmen is not helpful.

As far as I know, no one has proposed making blue sheet
information --and hence precise location information for
identified individuals-- available to the public in real time
during the meetings.   As one of, I assume, many members of this
community who will not broadcast my travel plans to social
networks, etc., until after I return home, I would strenuously
object to any such thing but, again, as far as I know, no one
proposed it.

     john


--On Thursday, May 10, 2012 14:23 +0800 Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:

> Dear Russ,
> 
> please forgive me for adding one more comment on that after
> you judged on rough consensus.
> 
> As you said this rough consensus is quite rough (if we may
> call it "rough consensus").
> I would like to point out two things:
> 1. the statement "(1) Rough consensus: an open and transparent
> standards process is more important to the IETF than privacy
> of blue sheet information." puts transparent process in
> competition with privacy. This is misleading, because there is
> no contradiction between an open and transparent process and
> privacy of personal information on this one. For example the
> availability of blue sheet information on request by an
> authenticated person does allow full transparency without
> broadcasting the personal location information. (e.g. see also
> Ted's proposal from yesterday)
> (Furthermore, if I would be devil's advocate, I would question
> this comparison even further, because it could be misread as
> stating that the current standards process as it is today
> (with blue sheets on request) is not open or transparent...)
> 
> 2. if consensus is so rough, we should also consider that the
> subject of the email discussion was maybe not clear enough
> about its impact to inform the audience of the consequences of
> the discussion and the consensus to be measured. We could
> equally have used a subject like this: "IETF wants to publish
> your specific locations / whereabouts (within 10m) on an
> 2-hourly basis during the day for each meeting and keep this
> information available published on the website indefinitely."
> It might have resulted in a different rough consensus.





From melinda.shore@gmail.com  Thu May 10 09:52:22 2012
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 1F55D21F84CD for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:52:22 -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 2t9F5lgg9nb5 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 09:52:20 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 987EE21F850F for <ietf@ietf.org>; Thu, 10 May 2012 09:52:20 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so2245091pbc.31 for <ietf@ietf.org>; Thu, 10 May 2012 09:52:20 -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=15EeObd5RAeiePtgVaMXbqsF2eaveFe8GFVkaQUhAG0=; b=03I3L7dAqaL88bTAH5CCc1PTykR5kWHAV+nwNyYVj6GAA4CAVu69BRyB97I/f/BI0+ 4R8jcyRYcQb7WDxl1QFDRdZeDgI110AJ2tIQFEjhYG7q/FzCjx0fBaS/3wHfLc/V40c9 MyZz56+XSQXmjupcQzUdnJqqTuXFfn2Nh4BFX+p6ZntkdMFII71Anx3YFNw8BNKtg+FS mpEx6lHF4WBIvU9V6/pxCuU/Q4wCUsZPpB9rhb0s/+b6i8e9qj04e6LNgy5GA6Me0FUP 6OSf3pGHDd0hf6E68J9xL7F/Odx+yZ54KlBZIGTK7G3CukEFIKk9+JhCpbdkuELGoyEW 5Oiw==
Received: by 10.68.129.194 with SMTP id ny2mr21892907pbb.56.1336668740408; Thu, 10 May 2012 09:52:20 -0700 (PDT)
Received: from polypro.local (66-230-101-239-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.239]) by mx.google.com with ESMTPS id q1sm9982108pbp.62.2012.05.10.09.52.18 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 10 May 2012 09:52:19 -0700 (PDT)
Message-ID: <4FABF241.3040801@gmail.com>
Date: Thu, 10 May 2012 08:52:17 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Future Handling of Blue Sheets
References: <201205101304.q4AD4LCv013256@fs4113.wdf.sap.corp>
In-Reply-To: <201205101304.q4AD4LCv013256@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 16:52:22 -0000

On 5/10/12 5:04 AM, Martin Rex wrote:
> Peter Sylvester wrote:
>> On 05/10/2012 11:17 AM, David Morris wrote:
>>> I object to the quantum change in ease of access and persistence of the
>>> information. I see way too much aggregation of personal information and
>>> don't think open-ness is justification for increasing that potential.
>> +1
> +1

I disagree rather strongly.  This is an open standards body with an open
process, and I think if we're going to change that it needs to be as a
result of a more general discussion rather than simply chipping away
around the edges.

Melinda

From ted.ietf@gmail.com  Thu May 10 10:00:12 2012
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 A110321F861C for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  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 N4SvdqGnd39j for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:00:10 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 37B6A21F860B for <ietf@ietf.org>; Thu, 10 May 2012 10:00:10 -0700 (PDT)
Received: by qabj40 with SMTP id j40so737444qab.15 for <ietf@ietf.org>; Thu, 10 May 2012 10:00: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 :content-type; bh=k6gwJb9i+rYWkZD7fzHbKixMQYUnC6E5yLsr5LOdVxw=; b=WwrD3QHNv724jVotgmJAaImCu2B3+UW3GlnAkTqytBAXdf4a88JwH5X1wiVuZUF8M7 Rpt2BiATH6nZtWkjcQQlFDo6jFUaFgcpluRA3oeOsM6xRQTLCcWYLIQEtqlEJEL0xUtr M8Moq/JASO2PPz2ukETVAEWTYHcREAZnEgq96xUsVgJEpYNEUx3kYTWxNaEC8d1zfj7s tfVqFPPZJr16PopGRTQp2FhlnZkfbEhq8FFnhWOSAHiDtyGrOSzRnywZl6Z5fILoIisk WDjIbM65pMmdAf3JtC1wr7ebMHlSKja8yG8gDCDLC5wbu0i2aCHa1Ht0gcNRi6tbP+c0 ZYRw==
MIME-Version: 1.0
Received: by 10.220.107.198 with SMTP id c6mr3122649vcp.54.1336669209627; Thu, 10 May 2012 10:00:09 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Thu, 10 May 2012 10:00:09 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.01.1205100210140.23269@egate.xpasc.com>
References: <97BB17A56A65B20E9FB38128@JcK-HP8200.jck.com> <360B33DF-0603-4B86-B488-DDDBEDF2B10B@bbn.com> <64D096E2-78E1-4B4F-B227-42AB7B658FF6@cs.columbia.edu> <BE62B481-1FBD-4F82-92BA-EAC0D0519639@ietf.org> <alpine.LRH.2.01.1205061559060.10886@egate.xpasc.com> <92DE3992-7212-4DE4-A4FA-57AED9DFE827@ietf.org> <alpine.LRH.2.01.1205061851340.12673@egate.xpasc.com> <2A1B808B-217C-4B09-B2A7-E179B3CA8FC8@ietf.org> <4FAB5ED8.7070004@gondrom.org> <5D365E621E09E8B8DE2F4006@JcK-HP8200.jck.com> <4FAB7567.7070402@gondrom.org> <12F34D6725B91B95351EB144@JcK-HP8200.jck.com> <4FAB80F9.40207@gondrom.org> <alpine.LRH.2.01.1205100210140.23269@egate.xpasc.com>
Date: Thu, 10 May 2012 10:00:09 -0700
Message-ID: <CA+9kkMAY9A_KdaG6MJ+CbNLUZ3pWy06qE4A6N3-XV7Otd0jkPQ@mail.gmail.com>
Subject: Re: Future Handling of Blue Sheets
From: Ted Hardie <ted.ietf@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 17:00:12 -0000

On Thu, May 10, 2012 at 2:17 AM, David Morris <dwm@xpasc.com> wrote:
> One of the ways we deal with SPAM and DOS attacks is to intentionally slow
> the process. Ted's proposal would be vastly improved with the provision
> that access, once authenticated, was delayed approximately the same
> amount of time as the current manual process. Propably with some
> form of the failed login approach ... maximum requests per week or
> other similar unit of time.
>

Just as a point of clarification, I did not actually make a proposal;
I asked whether the IESG had considered using making them available
outside the proceedings and other a different set of terms of use.  I
would be happy to make an actual proposal if the IESG decides it is
willing to consider that approach, but I'm not going to bother
drafting such a thing if they are firmly convinced that the
proceedings are the right way to go.

regards,

Ted

From sm@resistor.net  Thu May 10 10:00:22 2012
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 4F6E821F86F6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.597
X-Spam-Level: 
X-Spam-Status: No, score=-92.597 tagged_above=-999 required=5 tests=[AWL=-9.998, BAYES_00=-2.599, URIBL_BLACK=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fux6-1j8+M-v for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:00:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38FCF21F86E3 for <ietf@ietf.org>; Thu, 10 May 2012 10:00: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 q4AH0Dpp005477; Thu, 10 May 2012 10:00:16 -0700 (PDT)
Message-Id: <6.2.5.6.2.20120510092502.0a6408f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 May 2012 09:53:20 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: URI listing (was: Leverage Patent Search API to reduce BCP79 related issues)
In-Reply-To: <4FAB9EB4.8020704@isdg.net>
References: <20120507215610.10679.15815.idtracker@ietfa.amsl.com> <4FAA140B.4010703@gmail.com> <4FAAD14F.40009@qualcomm.com> <6.2.5.6.2.20120509150640.090d7098@resistor.net> <AEFA3A3E-F672-4522-BCF9-5D75DC82D112@cisco.com> <4FAB2563.3090309@qualcomm.com> <4FAB643C.108@gmail.com> <4FAB92BF.8090408@isdg.net> <4FAB9EB4.8020704@isdg.net>
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 May 2012 17:00:22 -0000

At 03:55 10-05-2012, Hector Santos wrote:
>http://hector.wildcatblog.com

The above URI is listed by uribl.com.  Changes to mail.ietf.org will 
not fix the problem as it doesn't change the behavior of message 
filters on the recipient's side.

In case it is not clear, no action is requested from ietf.org. 
Messages from the sender with such content will still be distributed 
to IETF mailing lists and will still appear in the IETF mailing list archives.

Regards,
-sm 


From mrex@sap.com  Thu May 10 10:32:44 2012
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 E1A5A21F8526 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.08
X-Spam-Level: 
X-Spam-Status: No, score=-10.08 tagged_above=-999 required=5 tests=[AWL=0.169,  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 s+wkby9Yc6pB for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:32:43 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 38B3321F84DD for <ietf@ietf.org>; Thu, 10 May 2012 10:32:34 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q4AHWRN4027298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 19:32:32 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp>
Subject: Re: Future Handling of Blue Sheets
To: melinda.shore@gmail.com (Melinda Shore)
Date: Thu, 10 May 2012 19:32:26 +0200 (MEST)
In-Reply-To: <4FABF241.3040801@gmail.com> from "Melinda Shore" at May 10, 12 08:52:17 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 10 May 2012 17:32:45 -0000

Melinda Shore wrote:
> 
> On 5/10/12 5:04 AM, Martin Rex wrote:
> > Peter Sylvester wrote:
> >> On 05/10/2012 11:17 AM, David Morris wrote:
> >>> I object to the quantum change in ease of access and persistence of the
> >>> information. I see way too much aggregation of personal information and
> >>> don't think open-ness is justification for increasing that potential.
> >> +1
> > +1
> 
> I disagree rather strongly.  This is an open standards body with an open
> process, and I think if we're going to change that it needs to be as a
> result of a more general discussion rather than simply chipping away
> around the edges.


There has never been a need to actively broadcast these massive amounts
of personally identifiable information (PII), and I haven't seen any
convincing rationale for doing it now.

Whenever dealing with PII the most responsible action is to distribute
it only when a real need has been demonstrated.  When publishing information
on the internet, it is not possible to undo it, so it is better to err
on the safe side for PII.

-Martin

From melinda.shore@gmail.com  Thu May 10 10:42:46 2012
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 9165E21F8693 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:42:46 -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 6IpAJJvj3SHB for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 10:42:46 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 044A621F8674 for <ietf@ietf.org>; Thu, 10 May 2012 10:42:45 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so2299319pbc.31 for <ietf@ietf.org>; Thu, 10 May 2012 10:42:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=gEfbCvXZ0uHDVZCl5df4lxL8Jg7bsVRLu/s8AIA2n4s=; b=fQCtEXlnlwO6SgB3bhw89y2bx2ZZ+JgQfGmPXXWunqDv/BY0pU5LEuPmuPpD8x7e7V gjzGln3FXJki1gu5QjVcvq6SqDCU0bdvSFGzjqss0zIOE/s2BnzGNBVaB+ZXAfZjFcLG wZpnGKaNlVjEd0hs6yRTCEdZsyB+2v8kOYvVay46msuDJnjx6qNbWFrhq0s4AleD1btE UOcZVt9ebrxhYRBeF7dL+KevxgKQ+47D3B1m3WnoBrtwoxlq83m5eTFmlQctQ3GSTE7m PkAqpE/nfgjZHob7WCktu9ygnJjJgQ+Pe5M6Rtn4QnihG45bI3kG5bj5qKlm/d78lhP8 bYHw==
Received: by 10.68.204.227 with SMTP id lb3mr22689881pbc.92.1336671765834; Thu, 10 May 2012 10:42:45 -0700 (PDT)
Received: from polypro.local (66-230-101-239-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.101.239]) by mx.google.com with ESMTPS id gl2sm1945768pbc.2.2012.05.10.10.42.44 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 10 May 2012 10:42:45 -0700 (PDT)
Message-ID: <4FABFE13.3020800@gmail.com>
Date: Thu, 10 May 2012 09:42:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Future Handling of Blue Sheets
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp>
In-Reply-To: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp>
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: Thu, 10 May 2012 17:42:46 -0000

On 5/10/12 9:32 AM, Martin Rex wrote:
> There has never been a need to actively broadcast these massive amounts
> of personally identifiable information (PII), and I haven't seen any
> convincing rationale for doing it now.

To be honest, "I don't want to receive more spam" and "My boss might
find out I skipped a session" are not reasons not to be open about
who's participating in sessions, particularly as we drift towards a
meetings/voting model.  I understand sensitivity about broadcasting
travel plans but in general some of the arguments being offered for
being a less open organization with a less open process are drifting
into "The FBI implanted a radio transmitter in my teeth" territory,
and it seems to me that making blue sheets available after meetings
does not reveal much PII beyond what's already available on the mailing
lists.

There's a serious question here about tradeoffs between privacy and
openness.  Openness is not just a core institutional value (although
it is one - do not forget that), but it's also a defense against
charges of collusion, which, unfortunately, we've been seeing.

Melinda

From ned+ietf@mauve.mrochek.com  Thu May 10 11:15:53 2012
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 C6CBB21F86F0 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:15: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=[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 U2nE0EDk3sFZ for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:15:53 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6EB21F86EB for <ietf@ietf.org>; Thu, 10 May 2012 11:15:53 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFBDNMNIW0001H9G@mauve.mrochek.com> for ietf@ietf.org; Thu, 10 May 2012 11:15:50 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 10 May 2012 11:15:45 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFBDNJS9F80006TF@mauve.mrochek.com>
Date: Thu, 10 May 2012 11:14:05 -0700 (PDT)
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was:
In-reply-to: "Your message dated Thu, 10 May 2012 18:31:44 +0200 (MEST)" <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com> <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp>
To: Martin Rex <mrex@sap.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 18:15:53 -0000

> Russ Housley wrote:
> >
> > BCP 79 says:
> >
> >       "Reasonably and personally known": means something an individual
> >       knows personally or, because of the job the individual holds,
> >       would reasonably be expected to know.  This wording is used to
> >       indicate that an organization cannot purposely keep an individual
> >       in the dark about patents or patent applications just to avoid the
> >       disclosure requirement.  But this requirement should not be
> >       interpreted as requiring the IETF Contributor or participant (or
> >       his or her represented organization, if any) to perform a patent
> >       search to find applicable IPR.
> >
> > Your suggestion seems to be in direct conflict with BCP 79.


> IMHO your quote from BCP79 (page 4, bullet l.) is a very important
> point in BCP79.  I can not speak for others, but the Internet Proxy
> of our company blocks urls to all "well known" online patent search
> and patent publication sites (and these are the only blocked sites
> I've ever encountered) for the simple reason of the insane US patent
> laws with this 3-fold "punitive damages" for "willful infringement"
> of a patent, i.e. a patent that was known to exist when shipping.
> As engineers, we MUST NOT read any patents because of this.
> All of the patent reasarch stuff is done by patent lawyers exclusively.

I don't know if a similar block exists, but the policy is the same for us.
Such a policy, if implemented, could easily lead to various people being
unable to participate in the process.

> btw. I personally know only about one patent where I refused to be
> listed as inventor because I considered my contribution to it to be
> "obvious to someone skilled in the technology".  When I read the
> description after it had been processed by patent lawyers, I had
> serious difficulties understanding what that text meant...

A pretty common occurance, unfortunately.

				Ned

From ynir@checkpoint.com  Thu May 10 11:25:22 2012
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 7D01211E80D6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.417
X-Spam-Level: 
X-Spam-Status: No, score=-10.417 tagged_above=-999 required=5 tests=[AWL=0.182, 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 7E23h0KT8XIl for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:25:22 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8F21011E80C8 for <ietf@ietf.org>; Thu, 10 May 2012 11:25:20 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4AIPH7G004856;  Thu, 10 May 2012 21:25:17 +0300
X-CheckPoint: {4FAC1575-6-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 10 May 2012 21:25:17 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 10 May 2012 21:25:15 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Melinda Shore <melinda.shore@gmail.com>
Date: Thu, 10 May 2012 21:25:14 +0300
Subject: Re: Future Handling of Blue Sheets
Thread-Topic: Future Handling of Blue Sheets
Thread-Index: Ac0u2j5TQNfB2By/RhCk8vNqIskh/g==
Message-ID: <660BE5FB-E81E-4094-990C-7840966F0E38@checkpoint.com>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com>
In-Reply-To: <4FABFE13.3020800@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean
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 May 2012 18:25:22 -0000

On May 10, 2012, at 8:42 PM, Melinda Shore wrote:

> On 5/10/12 9:32 AM, Martin Rex wrote:
>> There has never been a need to actively broadcast these massive amounts
>> of personally identifiable information (PII), and I haven't seen any
>> convincing rationale for doing it now.
>=20
> To be honest, "I don't want to receive more spam" and "My boss might
> find out I skipped a session" are not reasons not to be open about
> who's participating in sessions, particularly as we drift towards a
> meetings/voting model.

Participating is one thing. Presence is another. Reporting that I spoke up =
against the hard-fail requirement at Websec is part of the openness. Report=
ing that I was at SCIM, where I never once approached the microphone is not=
.

>  I understand sensitivity about broadcasting
> travel plans but in general some of the arguments being offered for
> being a less open organization with a less open process are drifting
> into "The FBI implanted a radio transmitter in my teeth" territory,
> and it seems to me that making blue sheets available after meetings
> does not reveal much PII beyond what's already available on the mailing
> lists.

The FBI needn't bother. They can just read the blue sheets :-)

> There's a serious question here about tradeoffs between privacy and
> openness.  Openness is not just a core institutional value (although
> it is one - do not forget that), but it's also a defense against
> charges of collusion, which, unfortunately, we've been seeing.

And how does the existence of such a lame attempt to list attendees help in=
 this?

Yoav


From john-ietf@jck.com  Thu May 10 11:31:15 2012
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 43C6721F8598 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jd9DL9YoNx7x for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:31:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E894B21F8595 for <ietf@ietf.org>; Thu, 10 May 2012 11:31:12 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SSY3b-000NJ8-Kx; Thu, 10 May 2012 14:25:43 -0400
Date: Thu, 10 May 2012 14:31:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, mrex@sap.com
Subject: Re: Future Handling of Blue Sheets
Message-ID: <367E45C5495F9BDB6E24C211@PST.JCK.COM>
In-Reply-To: <4FABFE13.3020800@gmail.com>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 18:31:15 -0000

--On Thursday, May 10, 2012 09:42 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 5/10/12 9:32 AM, Martin Rex wrote:
>> There has never been a need to actively broadcast these
>> massive amounts of personally identifiable information (PII),
>> and I haven't seen any convincing rationale for doing it now.
> 
> To be honest, "I don't want to receive more spam" and "My boss
> might
> find out I skipped a session" are not reasons not to be open
> about
> who's participating in sessions, particularly as we drift
> towards a
> meetings/voting model.  I understand sensitivity about
> broadcasting
> travel plans but in general some of the arguments being
> offered for
> being a less open organization with a less open process are
> drifting
> into "The FBI implanted a radio transmitter in my teeth"
> territory,
> and it seems to me that making blue sheets available after
> meetings
> does not reveal much PII beyond what's already available on
> the mailing
> lists.
> 
> There's a serious question here about tradeoffs between
> privacy and
> openness.  Openness is not just a core institutional value
> (although
> it is one - do not forget that), but it's also a defense
> against
> charges of collusion, which, unfortunately, we've been seeing.

+1

Also, please note that there is an interaction between this and
draft-farrresnickel-ipr-sanctions (now in Last Call).
Regardless of the other issues with that particular proposal,
the only real way to escape the IETF's IPR disclosure
requirements about something of which one is aware is to not
participate in any way in an affected WG.  I hate the idea of
the community getting embroiled in accusations and
counter-accusations but one advantage to a working IPR policy
(as well as general openness) of publishing the blue sheets is
the ability to notice and send reminder notes of the form of
"hey, I think I say you in WG FooBar and you've mentioned that
your company is doing work in the area, did you accidentally
forget to sign the blue sheet".   Of course, that means there is
one missing part of the current IESG picture and that is the
ability of people to add their names (perhaps as errata) to the
published blue sheets if an omission was unintentional.

    john


From mrex@sap.com  Thu May 10 11:53:17 2012
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 8792211E807F for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.082
X-Spam-Level: 
X-Spam-Status: No, score=-10.082 tagged_above=-999 required=5 tests=[AWL=0.167, 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 d-UanxPd7bFH for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 11:53:17 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id B07E111E8072 for <ietf@ietf.org>; Thu, 10 May 2012 11:53:16 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q4AIrC6H007933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 20:53:13 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101853.q4AIrBis003938@fs4113.wdf.sap.corp>
Subject: Re: Future Handling of Blue Sheets
To: john-ietf@jck.com (John C Klensin)
Date: Thu, 10 May 2012 20:53:11 +0200 (MEST)
In-Reply-To: <367E45C5495F9BDB6E24C211@PST.JCK.COM> from "John C Klensin" at May 10, 12 02:31:04 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 10 May 2012 18:53:17 -0000

John C Klensin wrote:
> 
> I hate the idea of the community getting embroiled in accusations and
> counter-accusations but one advantage to a working IPR policy
> (as well as general openness) of publishing the blue sheets is
> the ability to notice and send reminder notes of the form of
> "hey, I think I say you in WG FooBar and you've mentioned that
> your company is doing work in the area, did you accidentally
> forget to sign the blue sheet".   Of course, that means there is
> one missing part of the current IESG picture and that is the
> ability of people to add their names (perhaps as errata) to the
> published blue sheets if an omission was unintentional.


I think this blowing the issue out of proportion.

Do you want to require anyone listening to the audio stream
from the IETF Meeting (realtime or from the archive) to sign
up with name first and append it to the blue sheet?

I attended a few IETF meetings in person during 1995-1998 plus
one in 2000 and since then I've only been remotely participating
if at all.  While I did go to the meetings of WGs I actively
participated & signed the blue sheets there, I attended several
other WG meetings.  In case I attended primarily out of curiosity,
I sometimes came late, sometimes left early, and rarely signed
blue sheets.  The idea behind this is "cross-pollination",
something that the ADs of the security area had been actively
advocating for.

If the IESG decides it wants to publish the blue sheets, that may
result in attendees to deliberately not sign it or sign with fake
data, which may impair the usefulness of the blue sheets.


-Martin

From dhc@dcrocker.net  Thu May 10 12:16:51 2012
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 B867D11E8111 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.982
X-Spam-Level: 
X-Spam-Status: No, score=-5.982 tagged_above=-999 required=5 tests=[AWL=0.617,  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 txMJOv-IhZPB for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:16:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E16E111E810F for <ietf@ietf.org>; Thu, 10 May 2012 12:16:50 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4AJGoKi011654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 10 May 2012 12:16:50 -0700
Message-ID: <4FAC141D.30400@dcrocker.net>
Date: Thu, 10 May 2012 12:16:45 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Leverage Patent Search API to reduce BCP79 related issues [was:
References: <34D509ED-2D64-4383-A49E-F249D4263EF9@vigilsec.com> <201205101631.q4AGViCG025328@fs4113.wdf.sap.corp> <01OFBDNJS9F80006TF@mauve.mrochek.com>
In-Reply-To: <01OFBDNJS9F80006TF@mauve.mrochek.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.17]); Thu, 10 May 2012 12:16:50 -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 May 2012 19:16:51 -0000

On 5/10/2012 11:14 AM, ned+ietf@mauve.mrochek.com wrote:
> I don't know if a similar block exists, but the policy is the same for us.
> Such a policy, if implemented, could easily lead to various people being
> unable to participate in the process.


indeed.

more generally:  patents and the responsible handling of patent-related 
information are social issues.  we cannot solve or mitigate social 
issues with technical mechanisms.  let's not try.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From warren@kumari.net  Thu May 10 12:32:08 2012
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 4AD9B11E80E3 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.945
X-Spam-Level: 
X-Spam-Status: No, score=-105.945 tagged_above=-999 required=5 tests=[AWL=0.654, 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 EowyOxCGDyp6 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:32:07 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 72E0111E80D0 for <ietf@ietf.org>; Thu, 10 May 2012 12:32:07 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 7AF871B40541; Thu, 10 May 2012 15:32:06 -0400 (EDT)
Subject: Re: [IETF] Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4FABFE13.3020800@gmail.com>
Date: Thu, 10 May 2012 15:32:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86946C66-F656-4709-B5D5-A139337DCE0E@kumari.net>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1257)
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 May 2012 19:32:08 -0000

On May 10, 2012, at 1:42 PM, Melinda Shore wrote:

> On 5/10/12 9:32 AM, Martin Rex wrote:
>> There has never been a need to actively broadcast these massive =
amounts
>> of personally identifiable information (PII), and I haven't seen any
>> convincing rationale for doing it now.
>=20
> To be honest, "I don't want to receive more spam" and "My boss might
> find out I skipped a session" are not reasons not to be open about
> who's participating in sessions, particularly as we drift towards a
> meetings/voting model.  I understand sensitivity about broadcasting
> travel plans but in general some of the arguments being offered for
> being a less open organization with a less open process are drifting
> into "The FBI implanted a radio transmitter in my teeth" territory,
> and it seems to me that making blue sheets available after meetings
> does not reveal much PII beyond what's already available on the =
mailing
> lists.

Oh dear, oh dear oh dear=85.

I've been trying hard to stay out of this discussion, but finally cannot =
anymore=85

I fully agree with Melinda here -- if you are active in the IETF (or =
even if you aren't), you email address is already known to the spammers. =
Our lists, and list archives are all public -- if you think that you are =
important enough that spammers would download and OCR blue sheets to get =
your address, you are A: out of touch with the current spam model and / =
or b: believe that you are much more important than you really are...

If you are concerned that your bossman might figure out that you skipped =
a session -- well, here's an idea, actually two:
1: work somewhere where you manager trusts you enough to do what's in =
the best interests of the organization (and then do so) and / or
2: attend the friggin' sessions. Presumably you flew half way round the =
world to participate, not to drink espressos in some new and exotic =
city.

For the record:
1: My email addresses are warren@kumari.net, wkumari@google.com, =
wkumari@gmail.com, warren@snozzages.com and ...
2: I was sitting in seat 3A in room 243 at 15:25 on TUESDAY, March 27, =
2012.  I cannot remember what I was wearing, but it probably involved a =
t-shirt, sandals and some kind of hat. When you invent a time machines =
and travel back, you should be able to find me there..
3: I didn't attend a single session on Afternoon Session I, WEDNESDAY, =
March 28, 2012

(I feel that I have gotten much much rantier than intended, but, oh =
well=85)

W


[0]: and mailman's super secure s/warren@kumari.net/warren at =
kumari.net/ was figured out a long time ago!

>=20
> There's a serious question here about tradeoffs between privacy and
> openness.  Openness is not just a core institutional value (although
> it is one - do not forget that), but it's also a defense against
> charges of collusion, which, unfortunately, we've been seeing.
>=20
> Melinda
>=20


From mrex@sap.com  Thu May 10 12:49:42 2012
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 A436821F8648 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.084
X-Spam-Level: 
X-Spam-Status: No, score=-10.084 tagged_above=-999 required=5 tests=[AWL=0.165, 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 KSZr0yHjF5Dp for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 12:49:41 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 634B121F8644 for <ietf@ietf.org>; Thu, 10 May 2012 12:49:41 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q4AJnYYm004043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 10 May 2012 21:49:39 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201205101949.q4AJnX4A007180@fs4113.wdf.sap.corp>
Subject: Re: [IETF] Re: Future Handling of Blue Sheets
To: warren@kumari.net (Warren Kumari)
Date: Thu, 10 May 2012 21:49:33 +0200 (MEST)
In-Reply-To: <86946C66-F656-4709-B5D5-A139337DCE0E@kumari.net> from "Warren Kumari" at May 10, 12 03:32:04 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: 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: Thu, 10 May 2012 19:49:42 -0000

Warren Kumari wrote:
> 
> -- if you are active in the IETF (or even if you aren't), you email
> address is already known to the spammers. Our lists, and list archives
> are all public


If the blue sheets would _only_ contain PII that is _already_available_
in other places, then we should stop creating them in the first place.

The arguments of the folks that want to see it published is that
these sheet contain PII that is _not_yet_published_.

Which means we're talking past each other.

-Martin

From chair@ietf.org  Thu May 10 15:15:21 2012
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 968C921F851C; Thu, 10 May 2012 15:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uj1UxauFAGYu; Thu, 10 May 2012 15:15:21 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2E52F21F8516; Thu, 10 May 2012 15:15:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C57EA12C5F4; Thu, 10 May 2012 15:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id De3Q4U8s3RzP; Thu, 10 May 2012 15:15:21 -0700 (PDT)
Received: from [10.71.1.176] (static-70-108-241-115.res.east.verizon.net [70.108.241.115]) by c8a.amsl.com (Postfix) with ESMTPSA id 2635112C5A3; Thu, 10 May 2012 15:15:20 -0700 (PDT)
Subject: Re: Query to the community -- An additional IETF Meeting event?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <87471C16-AD53-4716-8DC4-BEB9B17B6A00@ietf.org>
Date: Thu, 10 May 2012 18:15:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <057FF15D-8026-4355-B774-C6DEA85D1640@ietf.org>
References: <87471C16-AD53-4716-8DC4-BEB9B17B6A00@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
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, 10 May 2012 22:15:21 -0000

We have identified space in Vancouver to hold the "Bits and Bites" =
event, and we are now seeking sponsors for tables at the event.  If your =
organization is interested in face-to-face time with hundreds of IETF =
participants, please contact Drew Dvorshak <dvorshak@isoc.org> to =
sponsor a table.  Please act promptly as we need to make some =
commitments in the first few days of June.

The expectation is that exhibitors will showcase products and services.  =
That is, exhibitor tables will be staffed by product vendors (hardware =
and software) and service providers (registries, registrars, ISPs, ESPs, =
etc.) and others interested in face-to-face time with IETF participants. =
 While attendance is optional, many IETF participants are likely to show =
up to consume the free beer, wine, soft drinks, and hors d'oeuvres that =
will be served in the same room.

Each exhibitor table will include a single power strip and access to the =
IETF wireless network.  Additional power or wired network connections =
may require an additional fee from the table sponsor.

Thanks,
Russ


On Apr 16, 2012, at 11:40 AM, IETF Chair wrote:

> We sent a query to the community on March 16, 2012.  There was a =
discussion on the IETF mailing list.  We also presented the topic in the =
IETF chair and IAOC chair presentations at administrative plenary at =
IETF 83, and there was an active discussion at the open mic that =
followed.
>=20
> Our conclusion is there is a consensus to test the event for the next =
two IETF meetings (Vancouver and Atlanta).  We believe this can be done =
in a manner that will not turn the meeting into a trade show, and we =
believe that it will create an opportunity for IETFers to network with =
each other, as well as talking to vendors and service providers.
>=20
> On behalf of the IESG and the IAOC,
> Russ Housley
> Bob Hinden


From sm@resistor.net  Thu May 10 15:20:54 2012
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 2578621F8598 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 15:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rT-ZzF5EfCmy for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 15:20: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 8077E21F844E for <ietf@ietf.org>; Thu, 10 May 2012 15:20:53 -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 q4AMKmNJ027736; Thu, 10 May 2012 15:20:51 -0700 (PDT)
Message-Id: <6.2.5.6.2.20120510123935.094139d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 May 2012 15:11:25 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Future Handling of Blue Sheets
In-Reply-To: <367E45C5495F9BDB6E24C211@PST.JCK.COM>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com> <367E45C5495F9BDB6E24C211@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 22:20:54 -0000

Hi John,
At 11:31 10-05-2012, John C Klensin wrote:
>participate in any way in an affected WG.  I hate the idea of
>the community getting embroiled in accusations and
>counter-accusations but one advantage to a working IPR policy
>(as well as general openness) of publishing the blue sheets is

I am fine either way with the handling of the blue sheets.  I am also 
fine with whatever the IESG decides (on this topic only :-)).  This 
topic has been sold as a matter of openness.  The question can be 
traced back to newspaperization.  In those days, propagation of 
information was localized.  Nowadays, it can be globalized.  That can 
be good; it can also be bad.

The scrawls from the blue sheets will be accessible after around a 
month.  Should the world be able to find out that:

   (i)  you were in Paris

   (ii) you attended the EAI session

Now let's assume that the work is covered by one of your 
inventions.  Although you were in that session according to the blue 
sheets, you did not participate in the discussion according to the 
minutes (the analogy is that you are subscribed to the mailing list 
but you have not posted any messages).  Do you have to file an IPR disclosure?

Coming back to being open and transparent, the IETF tends to have a 
variable stance on that.  Exposing information allows other people to 
evaluate fairness, whether there is conflict of interest, etc.  It 
does not always work out well; some people may be unhappy, offended 
or uncomfortable.  If you look at the list of WGs being tracked, you 
will notice that some people provided the information, some 
didn't.  I didn't ask why.  As a quick thought, I guess that people 
are uneasy with the idea of the information being publicized to the 
world or they used the default, this information is not relevant to 
any random person.

Let's ignore the IPR argument.  What question(s) should one ask in 
setting the boundaries for open and transparent?

Regards,
-sm 


From narten@us.ibm.com  Thu May 10 21:53:16 2012
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 5277821F8517 for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.007
X-Spam-Level: 
X-Spam-Status: No, score=-109.007 tagged_above=-999 required=5 tests=[AWL=-1.008, BAYES_50=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 m8W8+5pSSTCM for <ietf@ietfa.amsl.com>; Thu, 10 May 2012 21:53:14 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 8B15521F8512 for <ietf@ietf.org>; Thu, 10 May 2012 21:53:13 -0700 (PDT)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 10 May 2012 22:53:12 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 10 May 2012 22:53:06 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 9B4B31FF001A for <ietf@ietf.org>; Thu, 10 May 2012 22:53:03 -0600 (MDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q4B4r5UT254082 for <ietf@ietf.org>; Thu, 10 May 2012 22:53:05 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q4B4r5sk017303 for <ietf@ietf.org>; Thu, 10 May 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q4B4r4Qg017279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 10 May 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q4B4r4Gr005833 for <ietf@ietf.org>; Fri, 11 May 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q4B4r3VA005819 for ietf@ietf.org; Fri, 11 May 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201205110453.q4B4r3VA005819@rotala.raleigh.ibm.com>
Date: Fri, 11 May 2012 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12051104-2398-0000-0000-0000068C3BAC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 04:53:16 -0000

Total of 137 messages in the last 7 days.
 
script run at: Fri May 11 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.03% |   11 |  7.81% |    75340 | sm@resistor.net
  5.84% |    8 |  6.11% |    58911 | ynir@checkpoint.com
  5.84% |    8 |  5.74% |    55379 | john-ietf@jck.com
  3.65% |    5 |  5.12% |    49405 | hsantos@isdg.net
  3.65% |    5 |  4.54% |    43771 | brian.e.carpenter@gmail.com
  3.65% |    5 |  4.40% |    42406 | tobias.gondrom@gondrom.org
  4.38% |    6 |  3.12% |    30131 | randy@psg.com
  3.65% |    5 |  3.57% |    34387 | chair@ietf.org
  3.65% |    5 |  2.87% |    27711 | mrex@sap.com
  2.92% |    4 |  3.10% |    29856 | msk@cloudmark.com
  2.92% |    4 |  2.65% |    25521 | dwm@xpasc.com
  2.19% |    3 |  2.60% |    25080 | sant9442@gmail.com
  2.19% |    3 |  2.39% |    23047 | marshall.eubanks@gmail.com
  2.19% |    3 |  2.35% |    22671 | scott@kitterman.com
  2.19% |    3 |  2.06% |    19886 | hannes.tschofenig@nsn.com
  2.19% |    3 |  2.04% |    19640 | fred@cisco.com
  2.19% |    3 |  2.01% |    19427 | ted.ietf@gmail.com
  2.19% |    3 |  1.78% |    17163 | dhc@dcrocker.net
  2.19% |    3 |  1.73% |    16638 | dougb@dougbarton.us
  2.19% |    3 |  1.69% |    16255 | touch@isi.edu
  1.46% |    2 |  2.28% |    21993 | hallam@gmail.com
  1.46% |    2 |  1.71% |    16487 | housley@vigilsec.com
  1.46% |    2 |  1.67% |    16111 | warren@kumari.net
  1.46% |    2 |  1.49% |    14405 | presnick@qualcomm.com
  1.46% |    2 |  1.49% |    14367 | dotis@mail-abuse.org
  1.46% |    2 |  1.30% |    12556 | melinda.shore@gmail.com
  1.46% |    2 |  1.30% |    12541 | ned+ietf@mauve.mrochek.com
  1.46% |    2 |  1.27% |    12273 | dworley@avaya.com
  1.46% |    2 |  1.18% |    11333 | johnl@iecc.com
  1.46% |    2 |  1.09% |    10517 | paul@cypherpunks.ca
  0.73% |    1 |  1.34% |    12937 | ondrej.sury@nic.cz
  0.73% |    1 |  1.16% |    11194 | mary.ietf.barnes@gmail.com
  0.73% |    1 |  1.08% |    10431 | adrian@olddog.co.uk
  0.73% |    1 |  1.02% |     9790 | narten@us.ibm.com
  0.73% |    1 |  0.88% |     8467 | allison.mankin@gmail.com
  0.73% |    1 |  0.78% |     7499 | eburger-l@standardstrack.com
  0.73% |    1 |  0.75% |     7190 | john@jck.com
  0.73% |    1 |  0.73% |     7062 | hsantos@santronics.com
  0.73% |    1 |  0.72% |     6960 | marka@isc.org
  0.73% |    1 |  0.68% |     6593 | stephen.farrell@cs.tcd.ie
  0.73% |    1 |  0.68% |     6523 | nick@inex.ie
  0.73% |    1 |  0.67% |     6457 | glen@amsl.com
  0.73% |    1 |  0.67% |     6413 | bob.hinden@gmail.com
  0.73% |    1 |  0.64% |     6200 | jason_livingood@cable.comcast.com
  0.73% |    1 |  0.63% |     6049 | mail@sabahattin-gucukoglu.com
  0.73% |    1 |  0.61% |     5914 | yaakov_s@rad.com
  0.73% |    1 |  0.60% |     5830 | dcrocker@bbiw.net
  0.73% |    1 |  0.60% |     5780 | peter.sylvester@edelweb.fr
  0.73% |    1 |  0.57% |     5470 | markku.savela@vtt.fi
  0.73% |    1 |  0.57% |     5460 | stpeter@stpeter.im
  0.73% |    1 |  0.56% |     5404 | jaap@nlnetlabs.nl
  0.73% |    1 |  0.55% |     5293 | cos@aaaaa.org
  0.73% |    1 |  0.53% |     5083 | michel@arneill-py.sacramento.ca.us
  0.73% |    1 |  0.52% |     5037 | ajs@anvilwalrusden.com
--------+------+--------+----------+------------------------
100.00% |  137 |100.00% |   964244 | Total


From vesely@tana.it  Fri May 11 00:08:55 2012
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 F3CFE21F864C for <ietf@ietfa.amsl.com>; Fri, 11 May 2012 00:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.607
X-Spam-Level: 
X-Spam-Status: No, score=-4.607 tagged_above=-999 required=5 tests=[AWL=0.112,  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 BQb+XXtym28p for <ietf@ietfa.amsl.com>; Fri, 11 May 2012 00:08:54 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id DC3EB21F8628 for <ietf@ietf.org>; Fri, 11 May 2012 00:08:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1336720130; bh=DafsihJVcePahiTpIkBz5yKAi7rO/WYmmEMu08GYbkk=; l=355; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=E2+9EWLAgq1qJTy8z7aHFAzqSZcgrnL8Akjz0jxMsuseJeDgr7ZQ749A819T17mfy 4aAfW1eu81aM9/K2sktIxHTUXQvF4aAXaSIzgXA/fHhXSOuE4E8oZrp9quLuZ20uda ni5Kh6khxH+Y8qX3IDIGnCaqb4cklefk2bk3vmX0=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 11 May 2012 09:08:50 +0200 id 00000000005DC042.000000004FACBB02.000068D9
Message-ID: <4FACBB02.2040908@tana.it>
Date: Fri, 11 May 2012 09:08:50 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Query to the community -- An additional IETF Meeting event?
References: <87471C16-AD53-4716-8DC4-BEB9B17B6A00@ietf.org> <057FF15D-8026-4355-B774-C6DEA85D1640@ietf.org>
In-Reply-To: <057FF15D-8026-4355-B774-C6DEA85D1640@ietf.org>
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: Fri, 11 May 2012 07:08:55 -0000

On Fri 11/May/2012 08:56:14 +0200 IETF Chair wrote:
> 
> We have identified space in Vancouver to hold the "Bits and Bites" event,

Would it be possible to design a _unified_ event board that mentions
_all_ the events at the location, including this one, WGs, BoFs, not
only IETF, but also IRTF, ISOC, social, official and informal alike?

Thanks

From peter.sylvester@edelweb.fr  Sat May 12 07:32:04 2012
Return-Path: <peter.sylvester@edelweb.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 171A621F8608 for <ietf@ietfa.amsl.com>; Sat, 12 May 2012 07:32: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=[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 EBp1bVTbOd-Y for <ietf@ietfa.amsl.com>; Sat, 12 May 2012 07:32:03 -0700 (PDT)
Received: from mx1.on-x.com (mx1.on-x.com [92.103.215.13]) by ietfa.amsl.com (Postfix) with ESMTP id 759CA21F8606 for <ietf@ietf.org>; Sat, 12 May 2012 07:32:03 -0700 (PDT)
Received: from varuna.puteaux.on-x (varuna.puteaux.on-x [192.168.10.6]) by mx1.on-x.com (Postfix) with ESMTP id 020C47DAC for <ietf@ietf.org>; Sat, 12 May 2012 16:32:02 +0200 (CEST)
Received: from smtps.on-x.com (mintaka.puteaux.on-x [192.168.14.11]) by varuna.puteaux.on-x (Postfix) with ESMTP id 371187D9664 for <ietf@ietf.org>; Sat, 12 May 2012 16:23:43 +0200 (CEST)
Received: from [192.168.0.28] (gut75-3-82-227-163-182.fbx.proxad.net [82.227.163.182]) by smtps.on-x.com (Postfix) with ESMTPSA id 7ED37236373 for <ietf@ietf.org>; Sat, 12 May 2012 10:25:22 -0400 (EDT)
Message-ID: <4FAE745F.10104@edelweb.fr>
Date: Sat, 12 May 2012 16:31:59 +0200
From: Peter Sylvester <peter.sylvester@edelweb.fr>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Future Handling of Blue Sheets
References: <201205101949.q4AJnX4A007180@fs4113.wdf.sap.corp>
In-Reply-To: <201205101949.q4AJnX4A007180@fs4113.wdf.sap.corp>
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, 12 May 2012 14:32:04 -0000

On 05/10/2012 09:49 PM, Martin Rex wrote:
> Warren Kumari wrote:
>> -- if you are active in the IETF (or even if you aren't), you email
>> address is already known to the spammers. Our lists, and list archives
>> are all public
>
> If the blue sheets would _only_ contain PII that is _already_available_
> in other places, then we should stop creating them in the first place.
>
> The arguments of the folks that want to see it published is that
> these sheet contain PII that is _not_yet_published_.
>
> Which means we're talking past each other.
>
> -Martin
Not even that: the information which is on a blue sheet
is not the same as the information that the former is on the blue sheet.

<flame>The arguments to publish them, even to keep them secret as today,
begin to sound close to (or stink like) those used to justify to store travel
information, mobile phone tracking, etc etc.
</flame>

The number of participants in a meeting can be counted to get an
idea for meeting planning, and then the blue sheets should be distroyed.
Or, no blue sheets at all, the chairman makes a rough count
and this number, announces it at the end, and it is put into the minutes.

<fun>could the persons who are in favor of publishing confirm that
they don't work for spam companies, secret services ...  :-)</fun>

Anyway, adding an X and an unreadable address on a blue sheet
remains always an option. It serves the purpose of meeting preparation.

I did not had the impression that there was  "rough consensus" for
any change.

it's weekend :-)




From ynir@checkpoint.com  Sat May 12 23:46:38 2012
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 A7FE121F85D3; Sat, 12 May 2012 23:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.411
X-Spam-Level: 
X-Spam-Status: No, score=-10.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 6-bJIF8pQeO0; Sat, 12 May 2012 23:46:38 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C96C521F85A5; Sat, 12 May 2012 23:46:37 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4D6kYM3005131;  Sun, 13 May 2012 09:46:34 +0300
X-CheckPoint: {4FAF660F-1-1B221DC2-2FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sun, 13 May 2012 09:46:34 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Sun, 13 May 2012 09:46:32 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "ietf@ietf.org list" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>,  "draft-ietf-ccamp-assoc-info@tools.ietf.org" <draft-ietf-ccamp-assoc-info@tools.ietf.org>
Date: Sun, 13 May 2012 09:46:39 +0300
Subject: SecDir review of draft-ietf-ccamp-assoc-info-03
Thread-Topic: SecDir review of draft-ietf-ccamp-assoc-info-03
Thread-Index: Ac0w1CH59UUTwht/T5yyQqZVlWAu/w==
Message-ID: <329567CB-2EC4-4D9A-8E52-5D9D22C24417@checkpoint.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-KSE-AntiSpam-Interceptor-Info: protection disabled
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 06:46:38 -0000

Hi,

I have reviewed this document as part of the security directorate's ongoing=
 effort to review all IETF documents being processed by the IESG.  These co=
mments were written primarily for the benefit of the security area director=
s. Document editors and WG chairs should treat these comments just like any=
 other last call comments.

The document does not define any new procedures or mechanisms, and mentions=
 this fact three times throughout the document. It formalizes an email by A=
drian Farrel clarifying the procedures for processing an ASSOCIATION object=
 on a path message.=20

The security considerations section repeats that the document does not defi=
ne new procedures, and concludes that no security considerations are added.=
 This is not a valid deduction, as clarification often involves prohibiting=
 non-functional or insecure interpretation of the original document text. H=
owever, in this case the clarification is not about such insecure configura=
tions, so the document is fine.

One textual comment, though: section 2.2 near the bottom of page #5 lists 3=
 possible values for association ID. The second option is "The LSP ID of th=
e LSP protecting an LSP". This is not clear. I suggest rewording as "The LS=
P ID of the protecting LSP" without an indefinite "an LSP".

Yoav=

From adrian@olddog.co.uk  Sun May 13 14:08:49 2012
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 66EF121F84DE; Sun, 13 May 2012 14:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 Dj4bDR+C7eno; Sun, 13 May 2012 14:08:49 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id A475421F84A5; Sun, 13 May 2012 14:08:48 -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 q4DL8Z46000494;  Sun, 13 May 2012 22:08:39 +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 q4DL8YiW000480 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 13 May 2012 22:08:34 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Yoav Nir'" <ynir@checkpoint.com>, <ietf@ietf.org>, <secdir@ietf.org>, <draft-ietf-ccamp-assoc-info@tools.ietf.org>
References: <329567CB-2EC4-4D9A-8E52-5D9D22C24417@checkpoint.com>
In-Reply-To: <329567CB-2EC4-4D9A-8E52-5D9D22C24417@checkpoint.com>
Subject: RE: SecDir review of draft-ietf-ccamp-assoc-info-03
Date: Sun, 13 May 2012 22:08:34 +0100
Message-ID: <007d01cd314c$8f990c60$aecb2520$@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: AQFQj/2ZSa0yZlPsIw/HdQ+ygAHEMZfBePeQ
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: Sun, 13 May 2012 21:08:49 -0000

Thanks Yoav,

RFC Editor note entered for your observation.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Yoav
> Nir
> Sent: 13 May 2012 07:47
> To: ietf@ietf.org list; secdir@ietf.org;
draft-ietf-ccamp-assoc-info@tools.ietf.org
> Subject: SecDir review of draft-ietf-ccamp-assoc-info-03
> 
> Hi,
> 
> I have reviewed this document as part of the security directorate's ongoing
effort
> to review all IETF documents being processed by the IESG.  These comments
> were written primarily for the benefit of the security area directors.
Document
> editors and WG chairs should treat these comments just like any other last
call
> comments.
> 
> The document does not define any new procedures or mechanisms, and
> mentions this fact three times throughout the document. It formalizes an email
> by Adrian Farrel clarifying the procedures for processing an ASSOCIATION
object
> on a path message.
> 
> The security considerations section repeats that the document does not define
> new procedures, and concludes that no security considerations are added. This
is
> not a valid deduction, as clarification often involves prohibiting
non-functional or
> insecure interpretation of the original document text. However, in this case
the
> clarification is not about such insecure configurations, so the document is
fine.
> 
> One textual comment, though: section 2.2 near the bottom of page #5 lists 3
> possible values for association ID. The second option is "The LSP ID of the
LSP
> protecting an LSP". This is not clear. I suggest rewording as "The LSP ID of
the
> protecting LSP" without an indefinite "an LSP".
> 
> Yoav=


From hartmans@mit.edu  Mon May 14 10:56:24 2012
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 5940911E8095; Mon, 14 May 2012 10:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.747
X-Spam-Level: 
X-Spam-Status: No, score=-102.747 tagged_above=-999 required=5 tests=[AWL=-0.482, 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 08fZtSKAFBaU; Mon, 14 May 2012 10:56:23 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id DB38C11E8096; Mon, 14 May 2012 10:56:22 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 5FBFD203C0; Mon, 14 May 2012 13:52:06 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 16B4B44B6; Mon, 14 May 2012 13:56:02 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Joe Salowey <jsalowey@cisco.com>
Subject: Re: [secdir] secdir review of draft-ietf-emu-chbind-14
References: <AC6674AB7BC78549BB231821ABF7A9AEB82E64DB6F@EMBX01-WF.jnpr.net> <FCD56997-4431-4BD2-9352-AABAB5DBD999@cisco.com>
Date: Mon, 14 May 2012 13:56:02 -0400
In-Reply-To: <FCD56997-4431-4BD2-9352-AABAB5DBD999@cisco.com> (Joe Salowey's message of "Mon, 23 Apr 2012 14:06:38 -0700")
Message-ID: <tslvcjy4pfx.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Sam Hartman <hartmans-ietf@mit.edu>, draft-ietf-emu-chbind@tools.ietf.org, IETF-Discussion list <ietf@ietf.org>, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2012 17:56:24 -0000

>>>>> "Joe" == Joe Salowey <jsalowey@cisco.com> writes:

Hi.
I'm responding where  I'm not able to just take Steve's changes.
    Joe> Hi Steve, Thanks for taking time to perform a detailed review
    >> In the Introduction, the second paragraph says that the problem
    >> "results when the same credentials are used to access multiple
    >> services that differ in some interesting property". Do you mean
    >> client or server credentials?  I think you mean EAP server
    >> credentials. Please be more explicit to make this clearer, since
    >> many people will assume that you mean client (EAP peer)
    >> credentials. If I'm correct and you do mean EAP server
    >> credentials, I suggest that you say so in the first sentence of
    >> this paragraph and also in the last sentence.
    >> 

[Joe]   The case here is both client and server credentials.  If different credentials are required for each type of service then the authenticator will not be able to lie about the type of service it is representing to the client because the client credentials are bound to the service. 

There are a couple of things going on.
first, not all EAP methods distinguish server and client credentials.
Generally, you can fix the problem either way: use different server
credentials or have access to disjoint service sets from  different
client credentials.
Lots of factors affect whether that's an adequate defense. For example
using different server credentials for accessing different services
provides no defense for peers who do not validate server credentials.
I've added a sentence indicating that generally either type of
credential can be used as a defense but I have not gone into the full
details.
That's not appropriate for the introduction and may not be appropriate
for this document.

    >> In the first paragraph of the Problem Statement, the second
    >> sentence says "However, when operating in pass-through mode, the
    >> EAP server can be far removed from the authenticator."  While
    >> this is true, I think the more relevant statement here is that
    >> the EAP server can be far removed from the EAP peer.  This
    >> paragraph is all about problems that can arise when parties
    >> between the EAP peer and the EAP server (including the
    >> authenticator) are malicious or compromised. So the important
    >> thing to point out at the start of the paragraph is the large
    >> number of parties that may come between the EAP server and the
    >> EAP peer.
    >> 

[Joe]  I think I see your point, but I'm not sure.  Traditionally, we have often thought of the path between EAP peer and EAP authenticator as being vulnerable to having multiple parties able to insert themselves into the conversation.  However it may be the case that the authenticator the peer is talking to isn't the one it thinks it is and the "real" authenticator may be somewhere in the path as well.  The conversation between the EAP peer and EAP server will not be compromised, however the result of the conversation may not have its intended effect.  

I think Steve's clarification makes the text worse.
Conceptually/trust wise, the peer and EAP server are very close. There's
a protected path between them.
I've added 
both in terms of network distance and number of entities who need to be
trusted in order to establish trusted communication

I'm also happy with the original text.

    >> In the second bullet of section 3 (on page 7), the EAP GSS-API
    >> mechanism is a good example. However, I wonder if this attack
    >> might take a slightly different form. Could the IM server pretend
    >> to be the mail server? I think so. That's just one specific
    >> example of a relatively untrusted service pretending to be a
    >> relatively trusted service. I suggest that you add an example
    >> like that since the current language is quite abstract.
    >> 

[Joe] I agree having a more concrete example would be helpful.  
The reason I didn't do that is that trust is relative.
Apparently in Steve's environments mail servers are more trusted than IM
servers. In my environments I think the opposite may be true, although
both are relatively untrusted.

I added "For example, the instant messaging service could impersonate
the mail server."

I think there is a WG consensus to keep that text, and would push back
against a change at this point.
I'm fairly sure this issue was discussed in the WG  and keeping that
text was part of a compromise to move forward with a specific approach.
Like Joe, if there are clarity issues surrounding what's normative I'd
like to make sure those are fixed.

    >> In the first paragraph of section 5.1, you say that "the EAP
    >> server needs to be able to access information from the AAA server
    >> that is utilized during the EAP session and a local
    >> database". Which information? A parenthetical example (an e.g.)
    >> would help with understanding what you mean.
    >> 

[Joe] OK

I added (i2 below) to the sentence.
There's a fair bit of detail around this information in the following
text.

    >> the EAP lower layer in use. But you say in the first sentence of
    >> that section that this attribute is defined to "carry the EAP
    >> lower layer". That sounds like all the lower layer traffic will
    >> be encapsulated in this attribute and carried in it. I think you
    >> should change the word "carry" in that text to "identify".
    >> Unless I misunderstood you.
    >> 

[Joe] OK

Thanks for this catch!

    >> As I read section 8, I wonder whether include the User-Name
    >> attribute in i2 could open the system up to attacks where an
    >> authenticator or intermediate proxy could remove the anonymity of
    >> a user who's using a pseudonym for the username by changing the
    >> value of the User-Name attribute to the username of the user
    >> suspected of being responsible for this authentication. If the
    >> channel bindings checks fail, the authenticator will know they
    >> were wrong but if the channel bindings checks succeed, the
    >> authenticator will have confirmation of the user's identity.
    >> 

[Joe] Perhaps, on the one hand I would think the system would not behave this way, the server would be expecting a pseudonym or token and fail if it got something else.  On the other hand, I don' think the text for the user-name check or the test itself are that useful.  We could either warn against the possible identity disclosure or remove the user-name check.  

    >> I didn't understand that sending i2 from the server to the peer
    >> is optional until I got to section 9.1. In section 5.3, you said
    >> that "For success, the server returns the attributes that were
    >> considered by the server in making the determination that channel
    >> bindings are successfully validated". Which of these is right?
    >> 

[Joe]  The server is required to return the channel-binding attributes it verified because the client may require certain attributes to be checked.   This list of verified attributes is not equivalent to i2.  i2 is what attributes are sent in the AAA protocol and I don't think it should be referenced here.  Instead it should probably say:

    Joe> "sending the result from server to peer over
    Joe> integrity-protected channel"

Good tactch; made a similar change.


    >> At the top of page 23, you say that "In many EAP deployments
    >> today attacks where one NAS can impersonate another are out of
    >> scope." Do you mean that these attacks are generally not
    >> considered but they are a potential problem? Or that they are not
    >> a problem? I think they are always a possible problem. Even when
    >> all the NASes are owned and managed by the same organization that
    >> runs the AAA server and no proxies are used, there's still the
    >> potential for a NAS to become compromised. So I think you should
    >> say these attacks are "not considered although a real concern"
    >> not that they are "out of scope".

    Joe> [Joe] As EAP is deployed in most cases today the authenticator
    Joe> is not identified, it is merely authorized as being part of the
    Joe> network.  The peer does not expect differentiated service based
    Joe> on the NAS it is connected to.  Since the service is the same
    Joe> it does not matter to the peer if one authenticator
    Joe> impersonates another.  When we start discussing use case such
    Joe> as ABFAB where different services are being provided did the
    Joe> identity of the authenticator really become an issue.

    Joe> Perhaps the following text is better

    Joe> "In many EAP deployments today attacks where one authenticator
    Joe> can impersonate another not a real concern since different
    Joe> authenticators provide the same service.  In these situations
    Joe> an authenticator does not gain significant advantage in
    Joe> impersonating another authenticator. "


    >> And then the following sentence says that "Channel bindings
    >> brings these attacks into scope". Again, I think those attacks
    >> are always a potential issue. Channel bindings provide a good way
    >> to address them, whereas there were few ways to do so
    >> before. Maybe it would be better to say that.
    >> 

[Joe] I see your point here, how about:

    Joe> "The use of EAP in situations where different authenticators
    Joe> provide different services makes the ability to authorize
    Joe> different authenticators more important.  The system as a whole
    Joe> needs to be analyzed to evaluate cases where one authenticator
    Joe> may impersonate another and to evaluate the impact of this
    Joe> impersonation.  Channel bindings provides a way to address
    Joe> these issues. "



    >> In the next paragraph, you say that when cryptographic binding is
    >> used in a tunnel method, the MSK is disclosed to the NAS.  I
    >> don't think that's right. The MSK that's disclosed to the NAS is
    >> the one generated by the outer method. The MSK that's used in
    >> cryptographic binding is the one that's generated by the inner
    >> method. I don't think there's a problem there.
    >> 

[Joe]  OK, this test is referring to where there is separate between the terminating server of the inner and outer methods.  Maybe it would be clearer if the text said the following:

    Joe> "Even when cryptographic binding does attempt to confirm that
    Joe> the inner and outer server are the same, the Master Session Key
    Joe> (MSK) from the inner method is typically used to protect the
    Joe> binding.  However, if the outer method tunnel terminates on the
    Joe> authenticator the inner MSK is disclosed to the authenticator,
    Joe> which can attack cryptographic binding."


    >> Later in that paragraph, you say that an attack where the NAS
    >> terminates an EAP tunnel method is not in scope for existing
    >> models for cryptographic binding. I think that's wrong also.  EAP
    >> tunnel methods protect against just this sort of attack.  The
    >> first step in these methods is for the EAP peer and the EAP
    >> server to build a TLS tunnel. This requires the EAP peer to
    >> authenticate the EAP server and decide whether it's trusted.  If
    >> the NAS has credentials that will cause the EAP peer to trust it
    >> as an EAP server, a MITM attack is possible. Of course, that's
    >> true for any secure communications and it's a very bad
    >> situation. That's why the EAP peer must be very careful about who
    >> it trusts and how it authenticates them and the EAP server (and
    >> any CAs or other TTPs) must also be similarly careful.  I don't
    >> see that any of this has much to do with channel bindings.  Am I
    >> missing something here? If so, please explain it. And maybe you
    >> can clarify the text so that other folks get it also.
    >> 

[Joe]  The issue is when you have different services the client may not have enough information to determine what an authenticator is authorized for based on its identity alone.  In this case it would like help from the server that terminates the inner method.  However current crypto binding is based on the MSK so the authenticator can generate whatever channel binding quantities it wants because the authenticator has all the necessary key material.  In order for channel bindings to determine if the authenticator is authorized or not,   the method needs protect the channel bindings with a key generated from the inner method EMSK that the authenticator does not possess.   Here is some text that may help:

    Joe> "If the authenticator controls the cryptographic binding then
    Joe> it also controls the channel binding parameters and results.
    Joe> If the channel binding process is used to differentiate one
    Joe> authenticator from another then the authenticator can claim to
    Joe> support services that it was not authorized to.  This attack
    Joe> was not in scope for existing threat models for cryptographic
    Joe> binding because differentiated authenticators was not a
    Joe> consideration.  Thus, existing cryptographic binding does not
    Joe> typically provide mutual authentication of the inner method
    Joe> server required for channel binding."



    >> In section 9.2, this paragraph appears:
    >> 
    >> Dishonest peers can only manipulate the first message i1 of the
    >> channel binding protocol.  In this scenario, a peer sends i1' to
    >> the server.  If i1' is invalid, the channel binding validation
    >> will fail.  On the other hand if i1' passes the validation,
    >> either the original i1 was wrong and i1' corrected the problem or
    >> both i1 and i1' constitute valid information.  A peer could
    >> potentially gain an advantage in auditing or charging if both are
    >> valid and information from i1 is used for auditing or charging.
    >> Such peers can be detected by including the information in i2 and
    >> checking i1 against i2.
    >> 
    >> In the penultimate sentence, I think you mean "information from
    >> i1' is used for auditing or charging." There's no problem if
    >> information from i1 is used for auditing. If that happens, the
    >> bad peer's information is being ignored.
    >> 

[Joe]  I think you are correct.

    >> That paragraph does make me wonder about another attack that
    >> could be enabled by channel bindings. What if a malicious peer
    >> gets perfectly good i1 from a NAS but then sends bad i1' to the
    >> EAP server with a goal of damaging the reputation of the NAS? The
    >> EAP peer could be working for a competitor of the organization
    >> that runs the NAS or just be malicious. Is that a valid concern?
    >> If so, maybe you should cite it and suggest a countermeasure.
    >> 

[Joe] I think this is a valid concern for some environments.  I think we should add a section for that.  


    >> In section 9.4, you refer to "the optional result message".  I
    >> didn't know before this that the result message was optional.
    >> Could you make that clear earlier?
    >> 

[Joe] The result message is not intended to be optional.  This text needs to be fixed. 


    >> In the IANA Considerations, you talk about creating a new "EAP
    >> Channel Binding Parameters" top level registry. That's fine. But
    >> then you talk about a "Channel Binding Codes" registry. Didn't
    >> you mean a "sub registry"? If you want the Channel Binding Codes
    >> registry to be in the EAP Channel Binding Paramters registry, I
    >> think the first one is really a sub registry.

    Joe> [Joe] Yes

    >> Also, you say that "Early allocation is allowed" for that
    >> registry. What does that mean? I don't see any description of
    >> "early allocation" in RFC 5226.  I expect that IANA will want to
    >> know what they need to do to provide "early allocation". How
    >> early? Etc.
    >> 

[Joe] OK, I need to check if there is any convention here. 

    >> In the definition of the "Channel Binding Namespaces" registry,
    >> did you want to include a reference column as you did in the
    >> "Channel Binding Codes" registry?  If so, maybe you should say
    >> so.
    >> 

[Joe] OK

    >> At the end of section 11.1, a sentence says that "Values skipped
    >> in the above table are available for assignment." I don't think
    >> any values were skipped so I don't think you need that sentence.
    >> 

[Joe] Yup, left over from previous version. 

    >> Appendix A is pretty similar to section 1. Might you be able to
    >> merge them somehow?
    >> 

[Joe] I think the authors attempted to do this and then decided it was better to keep them separate. 

    >> In section A.3, you describe downgrading attacks and how channel
    >> bindings can prevent them. However, I think this will only work
    >> if the EAP peer rejects all methods that don't include channel
    >> bindings. Otherwise, the NAS can just offer an unauthorized EAP
    >> method that permits it to obtain the user's credentials and off
    >> to the bank.
    >> 

[Joe] I believe you are correct. 

From elwynd@folly.org.uk  Mon May 14 08:06:23 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0865C21F880C for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 08:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.575
X-Spam-Level: ***
X-Spam-Status: No, score=3.575 tagged_above=-999 required=5 tests=[AWL=2.282,  BAYES_50=0.001, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kvZ86IGxBKBE for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 08:06:18 -0700 (PDT)
Received: from auth.b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 67DA621F880B for <ietf@ietf.org>; Mon, 14 May 2012 08:06:17 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1STwql-0003Wa-6v for ietf@ietf.org; Mon, 14 May 2012 16:06:15 +0100
Subject: Gen-art last call review of  draft-ietf-codec-opus-12.txt (completed)
From: Elwyn Davies <elwynd@folly.org.uk>
Cc: IETF discussion <ietf@ietf.org>
Content-Type: text/plain
Organization: Folly Consulting
Date: Mon, 14 May 2012 16:06:13 +0100
Message-Id: <1337007973.23527.1614.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 14 May 2012 11:05:21 -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, 14 May 2012 15:06:23 -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-codec-opus-12.txt
Reviewer:  Elwyn Davies
Review Date:  14 May 2012 (completed)
IETF LC End Date: 10 May 2012
IESG Telechat date: (if known) -

Summary: 
Before offering some views on the document, let me say that this piece
of work seems to be a tour de force on behalf of its developers.  It is
certainly one of the (if not the) most technically complex pieces of
work that has been presented to the IETF, and is far more mathematically
complex and rigorous than our usual run of standards.  It is also
perhaps a vindication of the rough concensus and running code
philosophy. So congratulations to the authors and the companies that
have supported this work.  But back to the review....

I came to this review with a very outdated view of what goes on inside
codecs, so it was rather a shock to the system.  Taking that into
account, I think that some additional high level, up front description
of the two parts (SILK and CELT) and the range encoding system would
make it easier for future (naive) readers and potential implementers to
understand what is going on.  For example, after struggling with the
description of CELT in the decoder (s4.3) I found that going off and
reading the slides on CELT presented at IETF 79 helped considerably.
Such additions might also help future dissemination of the technique by
giving potential users a quick overview.  It would also make it easier
to justify the decision to postpone the high level (and highly
mathematical/technical) view to section 5 after the detailed description
of the decoder.

I also found that the descriptions of the SILK and CELT decoders
appeared to be written with a different perspective (see detailed
comments) doubtless by different authors.  This is not ideal and,
despite the expected further increase in page count, some additional
text in s4.3 seems desirable.

By far the most difficult to parse section is 4.3.3 talking about bit
allocation in CELT.  Despite considerable study, I didn't feel I had
really got to grips with how this worked.  An example might help.

Finally, the most contentious aspect of this document is the requirement
to treat the code as normative.  There are just over 30,000 physical
lines of code and I haven't checked them hardly at all.  Slocount
reckons this represents 7.14 man years of effort.  As with the document,
there is a discrepancy between CELT and SILK with the latter code being
more heavily commented, especially as regards routine parameters.  A
proper validation of the claim that the code implements the description
would take several weeks of time: I guess that we have to take the
document shepherd's assurances on this.  One issue is that both code and
document are pretty much saturated with what we used to call 'magic
numbers'.  Although these are explained in the document, it does not
appear that this is always the case in the code.  I would also be
happier if the code contained Doxygen (or similar) dcoumentation
statements for all routines (rather than just the API).

So overall, the work is something that ought to be standardized but the
document needs further work - not quite ready for the IESG. 

Major issues: 
Can we accept the code as normative?  If not how do we proceed?

Minor issues:
Contrast between decoder descriptions of LP part and CELT part:  The
SILK descriptions go into gory detail on the values used in lots of
tables, etc., whereas the CELT part has a very limited treatment of the
numeric values used (assuming reliance on finding the values in the
reference implementation, either explictly or implicitly).  There are
things to be said for both techniques.  I was wondering (while reading
the SILK description) if the authors have any means of automatically
generating the tables from the code in the SILK part (or vice versa) to
avoid double maintenance. On the other hand, there are pieces of the
CELT decoder description (especially in s4.3.3 where knowing numbers of
bands, etc.) where some actual numbers would help comprehension.

s2 (and more generally):  The splitting of the signal in the frequency
domain into signal (components?) below and above 8kHz in the hybrid case
presumably requires that the output of the CELT encoder is windowed so
that only one of encoders gnerates output below 8kHZ.  I think something
is needed in s2 to explain how this is managed (presumably to do with
energy bands?).  I didn't find anything in s5 about what has to be done
for the encoder when running in hybrid mode which surprised me somewhat.

s4.1: Despite having found a copy of the range coding paper and tried to
read it, I found the description of range coding opaque (there are some
more words later in s5 but this is a bit late for understanding the
decoder).  Given that this is (I think) fairly novel, some additional
less opaque description could be very helpful to people trying to
understand what is going on. In particular knowledge of how entropy
coding works is pretty much a prerequisite. 

s4.2.5, para 3:
>    When switching from 20 ms to 10 ms, the 10 ms
>    20 ms Opus frame, potentially leaving a hole that needs to be
>    concealed from even a single packet loss.
How?

s4.2.5, para 4: 
> In order to properly produce LBRR frames under all conditions, an
>    encoder might need to buffer up to 60 ms of audio and re-encode it
>    during these transitions.  However, the reference implementation opts
>    to disable LBRR frames at the transition point for simplicity.
> 
Should this be phrased in RFC 2119 requiremenmts language?  The first
part sounds like a SHOULD with the second part being the get out , but
its not entirely clear what the consequences are other then simplicity.


======================================================================
            MINOR ISSUES ABOVE submitted as part 1 of review
======================================================================
general/s11.2:  Several references [Hadamard], [Viterbi}, etc., are to
Wikipaedia pages.  Whilst these are convenient (and only illustrative)
they are not guaranteed to be very stable.  Better (i.e., more stable)
references are desirable.

s1, para 2:
>    The decoder contains a great deal of integer and fixed-point
>    arithmetic which must be performed exactly, including all rounding
>    considerations,...
Is this a MUST?  There are instances in the text which might contradict
this (e.g., para 1 of s4.2.7.5 which has (capitalized) SHOULDs).

s4.3:
As a complete newcomer to CELT, I would have appreciated a more high
level understanding of what CELT is doing at this point.  I  tried
reading s4.3 without any additional input and found it very hard going.
Eventually I gave up and went looking for some additional input.  This
presentation seems to have a useful view 
http://www.ietf.org/proceedings/79/slides/codec-2.pdf

I think that it would be extremely helpful to have a description similar
to this at this point in the document, even though there is some
material in section 5.3 which could also be forward referenced.  Still
the material in s5.3 does not start from the basic principles that CELT
is using, and since these are essentially novel, it would be very good
to give prospective implementers/users an understanding of what is going
on.  Incidentally, I found the above IETF presentation more useful than
http://www.celt-codec.org/presentations/misc/lca-celt.pdf
Note that the SILK part seems rather less opaque.  It would also be
useful to indicate numerically how many bands are involved and what the
number of MDCT bins are in the various bands. 

s4.3, last para: Can the 'out of range error' occur in the LP decoder? (if not why not?)

======================================================================

Nits/editorial comments: 

global: bytes -> octets
global: The form/terminology Q<n> (e.g., Q13, Q15, Q16) ought to be
explained.

s1: Expand CELP

s1.1.6: Need to define floor().

s2: ? Expand SILK

s2: Reference for Vorbis.

s2.1.8: Expand AAC (and MP3).

s3: References for Ogg, Matroska, maybe RTP.

s3: Fig 1, Table 2 and intervening text:  Presumably SILK only (Table 2)
etc correspond to MODES 1-3 in Figure 1. This needs to be consistent.

s3.2.1: Make it clear which of the octets is len[0]/len[1].  To be
precise it might be better to say len0/len1 are the values of the two
length octets (in whichever order you intend). The form len[0] could be
misinterpreted as a function 'length of 0'.

s3.2.5: better s/figure below/Figure 5/

s3.2.5:
> In the CBR case, the compressed length of each frame in bytes is
>    equal to the number of remaining bytes in the packet after
>    subtracting the (optional) padding, (N-2-P), divided by M. This
>    number MUST be a non-negative integer multiple of M.
'This number' is not the  compressed length of each frame that is the
subject of the first sentence, but the number of remaining octets - this
needs rewording.

s3.2.5:
> The number of header bytes (TOC byte, frame
>    count byte, padding length bytes, and frame length bytes), plus the
>    length of the first M-1 frames themselves, plus the length of the
>    padding MUST be no larger than N, the total size of the packet.
Surely this is a non sequitur? This might be better phrased as 'The
total size of a well formed packet MUST be at least...' 

s3.3: The example diagrams ought to have figure numbers.

s3.4: I am not keen on duplicating normative requirements in this way
(double maintenance issue).  It would be better to put explicit numbered
requirements in the sections above an reference the resulting numbers
here. 

s4.1:
> The decoder initializes rng to 128 and initializes val to
>    127 minus the top 7 bits of the first input octet. 
How are the 'top seven bits' to be interpreted here? e.g. as the bottom
seven bits of a 8 bit integer field? an 8 bit integer with the lowest
bit zeroed out?


s4.1.1:  This is really a global point.  This section refers to
entdec.c.  Presumably (since we haven't reached the code yet) and it is
still compressed, there is some file structure.  I don't think this has
been said above.  It would be good to provide a list of the file
components (i.e., sectional structure of the code) at the start, maybe
even  giving line number positions within the decompressed code.


s4.1.1.1:
> Then it reads the next octet of the
>    payload and combines it with the left-over bit buffered from the
>    previous octet to form the 8-bit value sym.  It takes the left-over
>    bit as the high bit (bit 7) of sym, and the top 7 bits of the octet
>    it just read as the other 7 bits of sym.
This is not well phrased.  Better
     Then it reads the next octet of the payload [packet? payload hasn't
really been used before] and combines the left  over bit from the
previous octet (see Section 4.1 for starting this process) as the high
bit (bit 7)| of 'sym' and the top 7 bits of the octet as the other 7
bits of sym, leaving the remaining bit for the next iteration.  

s4.1.5.2:
Should r_Q15 = rng >> (l-16) be r_Q15 = rng >> (lg-16)?  There doesn't
seem to be an 'l' defined.

s4.2.1: Expand LTP earlier. It would also be useful to expand LPC again.
 
s4.2.2: acronym VAD is not expanded until the beginning of s4.2.3.

s4.2.7: acronym LSF needs to be expanded on first use.

s4.2.7.1: Explain briefly why Table 7 has values for indices 0 to 15
when wi0/1 are in range 0 to 14.

s4.2.7.4, para below Table 12:
> These 6 bits are combined to form a gain index between 0 and 63.

s/gain index/gain_index/ as this variable is used subsequently.

s4.2.7.4: The use of log_gain seems slightly confusing when combined
with gain_index.  One at least is presumably log scaled.  Maybe a bit
more explanation is needed.

======================================================================
            COMMENTS ABOVE submitted as part 1 of review
======================================================================
General: Define L1 and L2 (as in L1-norm, etc).

s4.2.7.2, last para:
> In that case, if this
>    flag is zero (indicating that there should be a side channel), then
>    Packet Loss Concealment (PLC, see Section 4.4) SHOULD be invoked to
>    recover a side channel signal.
What are the consequences (or what actions need to be taken) if it is
not invoked?

s4.2.7.5, para 1:
> These represent the interleaved zeros on the
>    unit circle between 0 and pi (hence "normalized") in the standard
>    decomposition of the LPC filter into a symmetric part and an anti-
>    symmetric part (P and Q in Section 4.2.7.5.6).
'on the unit circle between 0 and pi' might be clearer as 'on the upper
half of the unit circle' or 'on the half of the unit circle in the
positive imaginary area of the complex plane'.
'standard decomposition'?  Needs a reference.

s4.2.7.5, para 1: A reference for the use of LSF in LPC would be useful.

s4.2.7.5.x: There is inconsistent use of stage 1/stage 2 vs
stage-1/stage-2.  Please be consistent.

s4.2.7.5, para 1:
>    Because of non-linear
>    effects in the decoding process, an implementation SHOULD match the
>    fixed-point arithmetic described in this section exactly.  An encoder
>    SHOULD also use the same process.
- Does this contradict the 'must' in s1, para 2?
- What are the consequences of ignoring the SHOULD?  How bad would they
get?  Might it become unstable and how would one know?

s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
   selects the PDFs for the second stage of the VQ/This indexes an 
   element in a coarse codebook that selects the PDFs for the second stage 
   of the VQ/

s4.2.7.5.3, last para: 
> However, nothing in
>    either the reconstruction process or the quantization process in the
>    encoder thus far guarantees that the coefficients are monotonically
>    increasing and separated well enough to ensure a stable filter.
A reference that indicates why this requirement is needed would be desirable.
(and also for s4.2.5.7.8).

s4.2.7.5.4 and Table 25: Are the values in Table 25 NDeltaMin or NDelatMin_Q15?
The equations after Table 25 use both NDeltaMin and NDeltaMin_Q15.  Is this correct?
In particular the first two equations deliver _Q15 values but use raw NDeltaMin.

s4.1.1/s4.2.7.1 and other places:  The term 'exact integer division' is
used in various places.  My understanding was that this phrase implied
that it was known that the dividend was an exact multiple of the divisor
by some out-of-band means.  This doesn't seem to be the case generally
in Opus (e.g,, where both n/5 and n%5  are needed - clearly this doesn't
anticipate n%5 == 0 every time!)  So what does 'exact integer division'
imply?  A definition may be needed. 

s4.3, last para: s/described in the figure above./described in Table 55 above./

s4.3.1: 
> The "transient" flag encoded in the bitstream has a probability of 1/8. 
This statement appears out of the blue apparently.  Some more
explanation of what the transient flag actually implies and why we
should be so sure about its PDF would help.

s4.3.2.1: Arguably a reference is needed for the z-transform.

s4.3.2.1: Avoid the equation picture splitting across page boundaries.
in the current version it is unclear what the denominator is. (use
needLines processing direcrive in xml2rfc).  Same applies to the
equation below Table 57 in s4.3.4.3.

4.3.2.1, after the equations:
> The
>    prediction is clamped internally so that fixed point implementations
>    with limited dynamic range do not suffer desynchronization.
As a person with limited skills in the srt, I have no idea what
desynchronization implies here. 

4.3.2.1, ibid:
> We
>    approximate the ideal probability distribution of the prediction
>    error using a Laplace distribution with separate parameters for each
>    frame size in intra- and inter-frame modes.
I suspect this sentence belongs before the equation described the z-transform.
Where are the values of the parameters for the inter-frame mode defined
(the intra-frame ones are in the text)?

s4.3.2.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.2.3, para above table 56: s/iff/if and only if/

s4.3.2.3: LOG2_FRAC_TABLE is missing.

s4.3.3: It would be helpful to explain either here, or at the outset of
s4.3 overall, how the concept of energy bands and MDCT bins applies to
the CELT part of the codec, and just how many bands and bins are used.
Some of this is contained in s5.3.2, but the magic number 17 appears
later in 4.3.3 which is presumably something to do with the point in the
frequency domain that CELT takes over from LP in the hybrid mode.  It
would make the very complex section 4.3.3 rather easier to understand
with this extra information - I have to say I struggled!  On reflection,
I think an example of what bits are allocated to a band and how thay rae
subsequently used would be quite helpful - Without going to delve into
the code I am really not clear that I understand just what bits are
allocated and what they then encode and I have read the text quite a few
times now.

s4.3.3: Be consistent between 'tone to noise' and 'tone-to-noise'.

s4.3.3:
>    The band-energy normalized structure of Opus MDCT mode ensures that a
>    constant bit allocation for the shape content of a band will result
>    in a roughly constant tone to noise ratio, which provides for fairly
>    consistent perceptual performance.  The effectiveness of this
>    approach is the result of two factors: that the band energy, which is
>    understood to be perceptually important on its own, is always
>    preserved regardless of the shape precision, and because the constant
>    tone-to-noise ratio implies a constant intra-band noise to masking
>    ratio.  Intra-band masking is the strongest of the perceptual masking
>    effects.  This structure means that the ideal allocation is more
>    consistent from frame to frame than it is for other codecs without an
>    equivalent structure.
This paragraph contains a number of interesting assertions:  Is there a
reference where one could see them justified (it may be that this is the
result of original research in the Opus team).
 
s4.3.3, paragraphs after the bullet points:  The concepts of 'shape' and
'shape encoding' is introcuced here without explicit definition.  Are we
talking about the shape windowing used in FFT/MDCT here? This should be
made clear.

s4.3.3, 5th para after bullet points: s/In the reference the maximums/In
the reference implementation the maximums/

s4.3.3, 6th para after the bullet points:  A table of bands per mode and
number of MDCT bins  covered would be helpful here in order to  get a
feeling for the scale of the problem.  Also the cache_caps50 table in
the code contains the magic number 168.  Where does this come from?

s4.3.3, 6th para after the bullet points:
> set LM to the shift value for the frame size (e.g. 0 for 120, 1 for
>    240, 3 for 480),  
Where do these frame sizes get specified? And what is the total set of
frame sizes? The text says 'e.g.' (which incidentally should be 'e.g.,')
implying that this is not the complete set.

s4.3.3, 6th para after the bullet points: Need to define 'truncating
integer division' to go with 'exact integer division'.

s4.3.3, 7th para after the bullet points: 
> The band boosts are represented by a series of binary symbols which
>    are coded with very low probability.
How many, at least, and what values?  Are these range encoded? I don't
see them in the table above or with a PDF specified.

s4.3.3, 7th para after the bullet points:
>    and every time
>    a band is boosted the initial cost is reduced (down to a minimum of
>    two).
Would that be a value of two or two bits? 
  
s4.3.3: Paragraph on decoding band boosts:  Might be improved by using
equations rather than the wordy descriptions used at present.

(global)s4.3.3, para above table 56: s/iff/if and only if/

s4.3.3, 2nd para after Table 56: 
> For stereo frames, bits are reserved for intensity stereo and for
>    dual stereo.  Intensity stereo requires ilog2(end-start) bits.
The terms 'intenmsity stereo' and 'dual stereo' don't appear to have
been defined.

s4.3.3: LOG2_FRAC_TABLE is missing.

4.3.4.3, last para:
>    If the decoded vector represents more than one time block, then the
>    following process is applied separately on each time block. 
Should this sentence come before the previous paragraph?  There  isn't
really a 'following process' in this section and I don't think it menas
the process in s4.3.4.4?


s4.3.4.3, last sentence: 
> This extra rotation is applied in an interleaved manner with a stride
>    equal to round(sqrt(N/nb_blocks))
I think this needs some more explanation for the uninitiated.

s4.3.4.4:
> Multiple levels of splitting may be
>    applied up to a frame size dependent limit. 
What this limit is does not appear to be defined.

s4.3.5: The 'collapse' phenomenon is not fully defined, and it would be
useful to mention why it happens.  Also s/min/minimum/.

s4.3.6: s/Just like/Just as/

s4.3.7, last para: I think 'power complementarity' requires further
explanation or a reference.

s4.5, para 3: s/To avoid or reduces glitches during these/To avoid or
reduce glitches during these/

s4.5.1.1, para 1: s/For for SILK-only/For SILK-only/

s4.5.1.4, para 2: s/redundant frame is as-is,/redundant frame as-is,/

s5, figure 16: The Optional High-pass Filter box has two spurious '+'
symbols on the vertical sides. 

s5, last para:  A reference for the Auto Regressive Moving Average
(ARMA) filter would be useful.

s5.2.3.4.2.1, title: s/Burgs method/Burg's Method/

s5.2.3.5, para 2: Expand 'R/D performance' (or probably specify it as
abbreviation for rate-distortion in para 1).

s5.3.5, para 1 below equation: Is E an abbreviation for 'extra'?

s5.3.6: The abbreviation RD for rate-distortion is defined here (see
comment on s5.2.3.5).

s6.1: This section is perhaps a little 'triumphalist' for the reference
implementation (this may of course be justified!.  The quality metric is
a 'relative quality metric' and presumably if someone does a *really*
good job of coding, it is entirely possible that the new algorithms
might get better than 100 on the quality score (i.e., provide a better
answer than the reference implementation).

s6.2: Just wondering, but is non-standard frame size the only option
offered by Opus Custom?  If not, probably more text is needed here.  Are
there any major changes to the algorithms implied by the use of Opus
Custom?

s7.  Referencing SECGUIDE (RFC 3552) seems inappropriate since it occurs
in such a security considerations section. Just omit it.

s11.2: A number of references are to Wikipaedia pages.  While these were
useful to me in refreshing or initializing my knowledge, they are not
usually considered adequately stable for use in RFCs.  I fear you may
have to provide more stable references.

Appendix A: I checked that the code extracted as inicated and was able
to be compiled under Ubuntu 10.04 LTS.









  




From ben@nostrum.com  Mon May 14 12:11:56 2012
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 CC3D421F88D0; Mon, 14 May 2012 12:11:56 -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 KkKuTJch2xw7; Mon, 14 May 2012 12:11:56 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7721F88C9; Mon, 14 May 2012 12:11:55 -0700 (PDT)
Received: from dn3-123.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4EJBs4E074214 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 May 2012 14:11:55 -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-ccamp-assoc-info-03
Date: Mon, 14 May 2012 14:12:10 -0500
Message-Id: <6D18CD1E-FBB8-43F7-8D82-46667AA2075B@nostrum.com>
To: draft-ietf-ccamp-assoc-info.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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, 14 May 2012 19:11:57 -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-ccamp-assoc-info-03
Reviewer: Ben Campbell
Review Date: 2012-06-14
IETF LC End Date: 2012-06-14

Summary: This draft is ready for publication as an informational RFC.

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- 2.1, 1st paragraph:

Please expand RSVP-TE on first mention.

-- 2.1, 2nd paragraph: "...can take place independent from..."

s/independent/independently

-- 2.2, paragraph 5: "... definition of the Association ID, which is =
(quoting [RFC4872]):"

The quoted text this refers to is more of a description of use than a =
definition.=

From sm@resistor.net  Mon May 14 12:24:07 2012
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 F099D21F8899 for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 12:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 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 iIqdqNGqWOdN for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 12:24: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 6BA0B21F887D for <ietf@ietf.org>; Mon, 14 May 2012 12:24:01 -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 q4EJNrNE010641; Mon, 14 May 2012 12:23:56 -0700 (PDT)
Message-Id: <6.2.5.6.2.20120514114036.0952ae18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 May 2012 12:13:20 -0700
To: Elwyn Davies <elwynd@folly.org.uk>
From: SM <sm@resistor.net>
Subject: Re: Gen-art last call review of  draft-ietf-codec-opus-12.txt (completed)
In-Reply-To: <1337007973.23527.1614.camel@mightyatom.folly.org.uk>
References: <1337007973.23527.1614.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 14 May 2012 19:24:07 -0000

Hi Elwyn,
At 08:06 14-05-2012, Elwyn Davies wrote:
>I am the assigned Gen-ART reviewer for this draft. For background on

[snip]

>Summary:
>Before offering some views on the document, let me say that this piece
>of work seems to be a tour de force on behalf of its developers.  It is
>certainly one of the (if not the) most technically complex pieces of
>work that has been presented to the IETF, and is far more mathematically
>complex and rigorous than our usual run of standards.  It is also

Let me say that this is one of the best Gen-ART reviews I have 
read.  It is not easy to review draft-ietf-codec-opus-12.  I agree 
that it is the most technically complex piece of work within all IETF 
areas.  The normative choice made by the WG is highly unusual.  The 
alternative would be much more work; it might even be an unworkable option.

Regards,
-sm 


From fluffy@iii.ca  Mon May 14 16:08:48 2012
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 7E2FC21F890C for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 16:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  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 kAgENy-vI3Gp for <ietf@ietfa.amsl.com>; Mon, 14 May 2012 16:08:48 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id EA34121F84A5 for <ietf@ietf.org>; Mon, 14 May 2012 16:08:47 -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 3247D22DD6D; Mon, 14 May 2012 19:08:40 -0400 (EDT)
Subject: Re: Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <1337007973.23527.1614.camel@mightyatom.folly.org.uk>
Date: Mon, 14 May 2012 17:08:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <C44FF905-1CB4-4041-8DD3-F3718C00B402@iii.ca>
References: <1337007973.23527.1614.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@folly.org.uk>
X-Mailer: Apple Mail (2.1084)
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, 14 May 2012 23:08:48 -0000

Thank you kindly for the detailed review. More inline ...

On May 14, 2012, at 9:06 AM, Elwyn Davies wrote:

> Summary:=20
> Before offering some views on the document, let me say that this piece
> of work seems to be a tour de force on behalf of its developers.  It =
is
> certainly one of the (if not the) most technically complex pieces of
> work that has been presented to the IETF,

And I would like to say thank you for the detailed review - having read =
the whole draft several times, I know that ones eyes can start to glaze =
over on what seems like something almost as long as the NFS spec ... so =
thanks for the review.=20

I did want to comment on the one major issues=20

>=20
>=20
> Major issues:=20
> Can we accept the code as normative?  If not how do we proceed?

RFC 6569 says that the code needs to be the normative specification so I =
think this issues is pretty much resolved by that RFC.=20

As a bit of irrelevant history - this topic was discussed at various =
stages. If was discussed in the chartering process - =
draft-valin-codec-guidelines referred to by the charter said code would =
be normative. I don't mean by this that the charter said the code had to =
be normative but just that this conversation goes back to before the WG =
was formed. It was later discussed in the WG and resulted in WG =
consensus to having the code as normative. Just as background on a few =
of the reasons that this was decided this way, many people felt that the =
spec would be much longer, and much harder to implement or review if the =
text was normative. Code is a very compact representation of what =
happens on boundary edge conditions and eliminates many types of =
misinterpretations. I do understand normative code introduces other =
types of issues but it is a fairly common practice in specifying codecs =
to use normative code.

Cullen <Codec Co-Chair>








From elwynd@folly.org.uk  Tue May 15 03:30:21 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B031A21F8638 for <ietf@ietfa.amsl.com>; Tue, 15 May 2012 03:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.939
X-Spam-Level: 
X-Spam-Status: No, score=0.939 tagged_above=-999 required=5 tests=[AWL=3.538,  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 pDi3TB-RYv9d for <ietf@ietfa.amsl.com>; Tue, 15 May 2012 03:30:21 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 0402121F8636 for <ietf@ietf.org>; Tue, 15 May 2012 03:30:21 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SUF1E-0005HB-CA; Tue, 15 May 2012 11:30:16 +0100
Subject: Re: Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
From: Elwyn Davies <elwynd@folly.org.uk>
To: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <C44FF905-1CB4-4041-8DD3-F3718C00B402@iii.ca>
References: <1337007973.23527.1614.camel@mightyatom.folly.org.uk> <C44FF905-1CB4-4041-8DD3-F3718C00B402@iii.ca>
Content-Type: text/plain
Organization: Folly Consulting
Date: Tue, 15 May 2012 11:30:12 +0100
Message-Id: <1337077812.23527.2492.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 15 May 2012 08:35:03 -0700
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, 15 May 2012 10:30:21 -0000

On Mon, 2012-05-14 at 17:08 -0600, Cullen Jennings wrote:
> Thank you kindly for the detailed review. More inline ...
> 
> On May 14, 2012, at 9:06 AM, Elwyn Davies wrote:
> 
> > Summary: 
> > Before offering some views on the document, let me say that this piece
> > of work seems to be a tour de force on behalf of its developers.  It is
> > certainly one of the (if not the) most technically complex pieces of
> > work that has been presented to the IETF,
> 
> And I would like to say thank you for the detailed review - having read the whole draft several times, I know that ones eyes can start to glaze over on what seems like something almost as long as the NFS spec ... so thanks for the review. 
> 
Not sure I would say 'it was my pleasure' but it certainly taught me a
thing or two!

> I did want to comment on the one major issues 
> 
> > 
> > 
> > Major issues: 
> > Can we accept the code as normative?  If not how do we proceed?
> 
> RFC 6569 says that the code needs to be the normative specification so
> I think this issues is pretty much resolved by that RFC. 
> 
> As a bit of irrelevant history - this topic was discussed at various
> stages. If was discussed in the chartering process -
> draft-valin-codec-guidelines referred to by the charter said code
> would be normative. I don't mean by this that the charter said the
> code had to be normative but just that this conversation goes back to
> before the WG was formed. It was later discussed in the WG and
> resulted in WG consensus to having the code as normative. Just as
> background on a few of the reasons that this was decided this way,
> many people felt that the spec would be much longer, and much harder
> to implement or review if the text was normative. Code is a very
> compact representation of what happens on boundary edge conditions and
> eliminates many types of misinterpretations. I do understand normative
> code introduces other types of issues but it is a fairly common
> practice in specifying codecs to use normative code.
> 
> Cullen <Codec Co-Chair>

I don't have a problem with this in principle: however as a reviewer I
get this nagging feeling that on a few days acquaintance, its impossible
to demonstrate that the text accurately, albeit non-normatively
describes the code.  And that makes me feel I have done a half job.
However, I also know that starting from scratch it would take me several
months to get anywhere near an accurate view (I know from considerable
experience with the DTN2 reference implementation and years ago the
source code of yacc - now that ages me!) 

If the wg, doc shepherd and the IESG are happy that the mapping is near
enough, so be it.  And, sorry, I didn't look at RFC 6569 during my
review.. probably shoyuld have done.

Regards,
Elwyn
> 
> 
> 
> 
> 
> 
> 


From barryleiba@computer.org  Wed May 16 06:59:26 2012
Return-Path: <barryleiba@computer.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 AB8D621F864A for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 06:59: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 pe8gTnjyRzDn for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 06:59:18 -0700 (PDT)
Received: from server1.netnutz.com (server1.netnutz.com [72.233.90.3]) by ietfa.amsl.com (Postfix) with ESMTP id 37D0821F85F7 for <ietf@ietf.org>; Wed, 16 May 2012 06:59:18 -0700 (PDT)
Received: from ool-4a599c7c.dyn.optonline.net ([74.89.156.124]:64275 helo=[192.168.0.2]) by server1.netnutz.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <barryleiba@computer.org>) id 1SUel2-00030S-Lv for ietf@ietf.org; Wed, 16 May 2012 09:59:17 -0400
Date: Wed, 16 May 2012 09:59:08 -0400
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Subject: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <562A61B995B24BD854A4D154@[192.168.0.2]>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server1.netnutz.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 13:59:26 -0000

Some snippets from another discussion thread, in a galaxy far, far =
away:

Murray:
>>> Sections 1, 3-7: The "may" in a document citing RFC2119 ought to be
>>> "can" or such.

Ned:
>> This seems pretty silly to me. The entire point of capitalizing =
these
>> terms is so they aren't confused with conventional usage, freeing up
>> the regular forms for conventional use.

Murray:
> As Dave would have pointed out had I not beaten him to it, RFC2119
> doesn't actually say "MAY" is different from "may". =C2=A0And I've =
been
> asked to deal with this in enough of my own drafts that now I bring
> it up when I see it.
>
> Barry has suggested, and I believe the IESG has allowed, that the
> RFC2119 boilerplate included in the document also say that the =
RFC2119
> meaning for each only applies when the word is in all-uppercase.=20
=C2=A0That
> allows the stuff you're talking about.
>
> We could further suggest that someone who feels so inclined propose a
> BCP draft to actually update RFC2119 accordingly.


In fact, RFC 2119 says that the normative keywords are "often=20
capitalized", but doesn't require that they be.

As Murray says, my habit is to use this for 2119 boilerplate:

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when they
   appear in ALL CAPS.  These words may also appear in this document in
   lower case as plain English words, absent their normative meanings.

This passes all nit checks, including those involving the eyes of the=20
IESG, and I think it makes the situation absolutely clear.  We could,=20
certainly, as Murray notes, update 2119 to require all caps in order to =

use the words as 2119 terms.

Alternatively, Tony and Dave had submitted this draft, now expired:
   http://tools.ietf.org/html/draft-hansen-nonkeywords-non2119
It suggests words such as "can" and "ought to" as substitutes, which is =

what Murray's original review was also suggesting.

The trouble with the first approach (using all caps as 2119 terms, and=20
using the same words in lower case as normal English) isn't so much=20
that someone might be confused later, but that during development and=20
review we're not sure whether you meant to put the word in all caps,=20
and just forgot.  No amount of documentation can avoid that question,=20
and using "can" or "ought to" gets us away from the issue.

The trouble with the "non-normative synonyms" is that it makes document =

text awkward, by requiring us to artificially substitute less apt=20
words, when "may" and "should", as English words, are exactly what we=20
mean.

It's probably worth having a discussion of all of that, and seeing=20
whether there's some possibility of developing a rough community=20
consensus on what we might-could-maybe-oughta-should do.

Barry



From dhc@dcrocker.net  Wed May 16 07:17:15 2012
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 C6C8E21F8622 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07: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 p3XbfZ31tJqI for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:17:15 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2F021F8613 for <ietf@ietf.org>; Wed, 16 May 2012 07:17:15 -0700 (PDT)
Received: from [192.168.9.2] (mb62736d0.tmodns.net [208.54.39.182]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GEH8gn017921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 May 2012 07:17:10 -0700
Message-ID: <4FB3B6E0.2070506@dcrocker.net>
Date: Wed, 16 May 2012 07:17:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
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.17]); Wed, 16 May 2012 07:17:10 -0700 (PDT)
Cc: Barry Leiba <barryleiba@computer.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, 16 May 2012 14:17:15 -0000

On 5/16/2012 6:59 AM, Barry Leiba wrote:
> This passes all nit checks, including those involving the eyes of the
> IESG,

Computer Science has a long history of being quaint about the role of 
upper/lower case and then ignoring the problems caused by the 
distinctive interpretation it imposes.  It has never recovered from a 
couple of decades of having no upper case, and continues to treat the 
capability as worthy for semantic distinction, in contrast with natural 
usage.

it is ALso interesting to hear that the IETF's actual standards are not 
what is written in our documents but what is in our SUBMISSION testing 
code and the whims of personal interpretation (by the IESG).  There are 
faint echos of Through the Looking Glass, here.  Things mean whatever 
the IESG chooses to declare them to mean, not what the plain language in 
formally adopted documents say they mean.

This is not the sort of topic that should be artificial nor nuanced, nor 
should it encourage misunderstanding.  Case does not define meaning in 
normal language, why should it here?

It is not exactly an onerous task to use different vocabulary, to make 
sure there is no potential ambiguity for readers.  Relying solely on 
case to distinguish between normative vs. non-normative is, forgive me, 
really silly.


> Alternatively, Tony and Dave had submitted this draft, now expired:
> http://tools.ietf.org/html/draft-hansen-nonkeywords-non2119
> It suggests words such as "can" and "ought to" as substitutes, which is
> what Murray's original review was also suggesting.
>
> The trouble with the first approach (using all caps as 2119 terms, and
> using the same words in lower case as normal English) isn't so much that
> someone might be confused later,

It is certainly one of the troubles with it.


> but that during development and review
> we're not sure whether you meant to put the word in all caps, and just
> forgot. No amount of documentation can avoid that question, and using
> "can" or "ought to" gets us away from the issue.

And yes, this is certainly another trouble with it.


> The trouble with the "non-normative synonyms" is that it makes document
> text awkward, by requiring us to artificially substitute less apt words,
> when "may" and "should", as English words, are exactly what we mean.

Because, after all, technical specification language is already such 
elegant prose, maintaining that elegance is more important than robustly 
encoding the semantic of being normative in a way that avoids ambiguity?

I guess the underlying issue here is whether the rather essential burden 
of working to carefully discerning normativity is placed on the small 
range of authors of a specification or on the variable ocean of 
potential readers?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From randy@psg.com  Wed May 16 07:28:27 2012
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 49B5521F8504 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:28:27 -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 gxbto+u2l6R6 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:28:27 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id EDEDE21F8503 for <ietf@ietf.org>; Wed, 16 May 2012 07:28:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SUfDE-000HLr-OS; Wed, 16 May 2012 14:28:25 +0000
Date: Wed, 16 May 2012 04:28:23 -1000
Message-ID: <m2boloci9k.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 14:28:27 -0000

can != may

one is ability, the other permission

randy

From dhc@dcrocker.net  Wed May 16 07:32:03 2012
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 4E09121F8504 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:32:03 -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 E0m4vFd3kyEF for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:32:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC5BB21F8503 for <ietf@ietf.org>; Wed, 16 May 2012 07:32:02 -0700 (PDT)
Received: from [192.168.9.2] (md02736d0.tmodns.net [208.54.39.208]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GEVv4g018329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 May 2012 07:31:59 -0700
Message-ID: <4FB3BA59.2010801@dcrocker.net>
Date: Wed, 16 May 2012 07:31:53 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m2boloci9k.wl%randy@psg.com>
In-Reply-To: <m2boloci9k.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.17]); Wed, 16 May 2012 07:32: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: Wed, 16 May 2012 14:32:03 -0000

On 5/16/2012 7:28 AM, Randy Bush wrote:
> can != may
>
> one is ability, the other permission


When we were first taught English grammar, yes.  Today, not so much.

Actually pretty much never.  In modern usage, the distinction has been lost.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From scott@kitterman.com  Wed May 16 07:34:23 2012
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 650C221F8504 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXs6YIIuakZc for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:34:22 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id A021921F8503 for <ietf@ietf.org>; Wed, 16 May 2012 07:34:22 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id C1E1D20E40A6; Wed, 16 May 2012 10:34:21 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1337178861; bh=eftsjf4zHjT+2xBNYAqqI+vrkjO9LS81CBeuYW1t8gU=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=BvY51vrG3h/1ACfg3BO65Jwwm7D7/voyTkPeFytxC6GA4SuOznJEEI80NHv9douRV odyDWmRb/3BNJV6Kbyf8thS921B74EkKIlP5G55X2e0HFFMInL3K3ecRd3B3h//+R/ lcPT76bST71ZF6xlFbwWielrbV1Cj4YLKHFA2PIw=
Received: from scott-latitude-e6320.localnet (65-122-15-169.dia.static.qwest.net [65.122.15.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 8898320E4093;  Wed, 16 May 2012 10:34:21 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Date: Wed, 16 May 2012 10:34:19 -0400
Message-ID: <1465291.UuhlZNcsd8@scott-latitude-e6320>
User-Agent: KMail/4.8.2 (Linux/3.2.0-24-generic-pae; KDE/4.8.2; i686; ; )
In-Reply-To: <4FB3BA59.2010801@dcrocker.net>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m2boloci9k.wl%randy@psg.com> <4FB3BA59.2010801@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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: Wed, 16 May 2012 14:34:23 -0000

On Wednesday, May 16, 2012 07:31:53 AM Dave Crocker wrote:
> On 5/16/2012 7:28 AM, Randy Bush wrote:
> > can != may
> > 
> > one is ability, the other permission
> 
> When we were first taught English grammar, yes.  Today, not so much.
> 
> Actually pretty much never.  In modern usage, the distinction has been lost.

I must be ancient then as I still use this distinction (and similarly 
would/could).

Scott K

From Ed.Lewis@neustar.biz  Wed May 16 07:36:51 2012
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A02C21F8504 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.778
X-Spam-Level: 
X-Spam-Status: No, score=-105.778 tagged_above=-999 required=5 tests=[AWL=0.821, 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 Y1viIvfsDWoG for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:36:50 -0700 (PDT)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id 053B121F8503 for <ietf@ietf.org>; Wed, 16 May 2012 07:36:49 -0700 (PDT)
Received: from work-laptop-2 (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id q4GEamUK015637; Wed, 16 May 2012 10:36:48 -0400 (EDT) (envelope-from Ed.Lewis@neustar.biz)
Received: from [10.31.201.99] by work-laptop-2 (PGP Universal service); Wed, 16 May 2012 10:36:48 -0400
X-PGP-Universal: processed; by work-laptop-2 on Wed, 16 May 2012 10:36:48 -0400
Mime-Version: 1.0
Message-Id: <a06240804cbd9698a8fa4@[10.31.201.99]>
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
Date: Wed, 16 May 2012 10:36:44 -0400
To: <ietf@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.72 on 10.20.30.4
Cc: ed.lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 14:36:51 -0000

At 9:59 -0400 5/16/12, Barry Leiba wrote:

>It's probably worth having a discussion of all of that, and seeing
>whether there's some possibility of developing a rough community consensus
>on what we might-could-maybe-oughta-should do.

What I've run into, a couple of times, in the past few years are 
customer documents, such as RFP (request for proposals) that ask 
about compliance with RFC documents.  In that role it doesn't really 
matter whether the RFC 2119 words are written one way or another, the 
pain is that RFCs generally do not define what it means to be 
compliant.

Granted the RFC series is not intended to be (all) requirements 
documents nor standards documents against which compliance can be 
judged.  I am not saying the RFC series is deficient in the role it 
is intended to play.  But if there is a discussion on the topic of 
the RFC 2119 words, I'd encourage giving thought to appeasing those 
that want documents against which compliance can be judged.

Perhaps a sub-series of RFC documents can be tagged for compliance 
applicability, written in way that testing of requirements is 
possible, and so on.  In such a sub-series, special-meaning words 
would matter.  In all other documents, all words would "revert" to 
their natural meanings.  E.g., SHOULD would be the same as "ought 
to", MUST would be the same as "it has to be" and so on.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

2012...time to reuse those 1984 calendars!

From dhc@dcrocker.net  Wed May 16 07:38:23 2012
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 452FB21F857F for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:38:23 -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 5K+W7oGKO1yL for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:38:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A4E9721F8543 for <ietf@ietf.org>; Wed, 16 May 2012 07:38:22 -0700 (PDT)
Received: from [192.168.9.2] (md02736d0.tmodns.net [208.54.39.208]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GEcJBA018532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 May 2012 07:38:21 -0700
Message-ID: <4FB3BBD2.9050704@dcrocker.net>
Date: Wed, 16 May 2012 07:38:10 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@192.168.0.2> <m2boloci9k.wl%randy@psg.com> <4FB3BA59.2010801@dcrocker.net> <1465291.UuhlZNcsd8@scott-latitude-e6320>
In-Reply-To: <1465291.UuhlZNcsd8@scott-latitude-e6320>
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.17]); Wed, 16 May 2012 07:38:22 -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: Wed, 16 May 2012 14:38:23 -0000

On 5/16/2012 7:34 AM, Scott Kitterman wrote:
> On Wednesday, May 16, 2012 07:31:53 AM Dave Crocker wrote:
>> On 5/16/2012 7:28 AM, Randy Bush wrote:
>>> can != may
>>>
>>> one is ability, the other permission
>>
>> When we were first taught English grammar, yes.  Today, not so much.
>>
>> Actually pretty much never.  In modern usage, the distinction has been lost.
>
> I must be ancient then as I still use this distinction (and similarly
> would/could).


I try to too.  The issue isn't with those of us who generate the 
distinction but the masses that don't hear it and seem not to know of it.

This sort of change in language, across a few decades, seems to be 
extremely common.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From randy@psg.com  Wed May 16 07:38:58 2012
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 5D25A21F85A1 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:38: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=[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 7E5kcXTHllbZ for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:38:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id ADB7321F8543 for <ietf@ietf.org>; Wed, 16 May 2012 07:38:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SUfNR-000HNo-A6; Wed, 16 May 2012 14:38:57 +0000
Date: Wed, 16 May 2012 04:38:56 -1000
Message-ID: <m27gwcchrz.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <1465291.UuhlZNcsd8@scott-latitude-e6320>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m2boloci9k.wl%randy@psg.com> <4FB3BA59.2010801@dcrocker.net> <1465291.UuhlZNcsd8@scott-latitude-e6320>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 14:38:58 -0000

>>> can != may
>>> one is ability, the other permission
>> When we were first taught English grammar, yes.  Today, not so much.
>> Actually pretty much never.  In modern usage, the distinction has been lost.
> I must be ancient then as I still use this distinction (and similarly 
> would/could).

yep.  let's stick to hacking our own documents, not the english
language.

further, quoting barry:

> The trouble with the first approach (using all caps as 2119 terms, and 
> using the same words in lower case as normal English) isn't so much 
> that someone might be confused later, but that during development and 
> review we're not sure whether you meant to put the word in all caps, 
> and just forgot.

and when i say a field is 42 bits long, you don't know if i really meant
41.

just address the document, do not try to guess intent.  life is already
sufficiently complex.

randy

From randy@psg.com  Wed May 16 07:39:25 2012
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 F2F0E21F8631 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:39: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 0W-eXKMs+ZjC for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:39:24 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 734A521F857F for <ietf@ietf.org>; Wed, 16 May 2012 07:39:24 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SUfNr-000HO3-T4; Wed, 16 May 2012 14:39:24 +0000
Date: Wed, 16 May 2012 04:39:22 -1000
Message-ID: <m262bwchr9.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Barry Leiba <barryleiba@computer.org>
Sent-via: Barry Leiba <barryleiba@computer.org>
Sent-via: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 14:39:25 -0000

>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in [RFC2119] when they
>    appear in ALL CAPS.  These words may also appear in this document in
>    lower case as plain English words, absent their normative meanings.

i like this a lot

randy

From adrian@olddog.co.uk  Wed May 16 07:44:33 2012
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 3E66221F85EF for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2g+a9u7xnm-5 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:44:32 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 20E5021F85A5 for <ietf@ietf.org>; Wed, 16 May 2012 07:44:31 -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 q4GEiU80008606 for <ietf@ietf.org>; Wed, 16 May 2012 15:44:30 +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 q4GEiTES008600 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 16 May 2012 15:44:30 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com>
In-Reply-To: <m262bwchr9.wl%randy@psg.com>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Date: Wed, 16 May 2012 15:44:27 +0100
Message-ID: <08ab01cd3372$65934110$30b9c330$@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: AQHGz4alFcB3TxKmEduea4L+EpGxoAJtdb6SlsXZQoA=
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: Wed, 16 May 2012 14:44:33 -0000

How about...

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
    document are to be interpreted as described in [RFC2119] when they
    appear in ALL CAPS.  These words may also appear in this document in
    lower case as plain English words, absent their normative meanings. Other
    words found in this document MAY also have their expected meanings. The
    term TROLL-BAIT is to be interpreted as described in [1].


[1] http://www.urbandictionary.com/define.php?term=TROLL%20BAIT



From dhc@dcrocker.net  Wed May 16 07:54:20 2012
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 18FF121F862F for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:54: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 VXBRzbxkL+1k for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:54:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 79C2621F862B for <ietf@ietf.org>; Wed, 16 May 2012 07:54:19 -0700 (PDT)
Received: from [192.168.1.132] (cpe-76-93-137-195.san.res.rr.com [76.93.137.195]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GEsH2Q018816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 May 2012 07:54:17 -0700
Message-ID: <4FB3BF95.30803@dcrocker.net>
Date: Wed, 16 May 2012 07:54:13 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com>
In-Reply-To: <m262bwchr9.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.17]); Wed, 16 May 2012 07:54:18 -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, 16 May 2012 14:54:20 -0000

On 5/16/2012 7:39 AM, Randy Bush wrote:
>>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>>     document are to be interpreted as described in [RFC2119] when they
>>     appear in ALL CAPS.  These words may also appear in this document in
>>     lower case as plain English words, absent their normative meanings.
>
> i like this a lot


So do I.  Rather than attend to likely misinterpretation by average 
readers, it relieves us from responsibilities for misunderstandings due 
to our choosing not to conform to normal language usage.

Making an artificial, formal distinction is far more productive than 
worrying about characteristics of typical readers.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ajs@anvilwalrusden.com  Wed May 16 07:57:05 2012
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 7069521F862F for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.323
X-Spam-Level: 
X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[AWL=-0.324, BAYES_50=0.001, 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 hJeKEKK5ghOx for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 07:57:05 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id EF12021F8628 for <ietf@ietf.org>; Wed, 16 May 2012 07:56:57 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 214F71ECB41C for <ietf@ietf.org>; Wed, 16 May 2012 14:56:57 +0000 (UTC)
Date: Wed, 16 May 2012 10:56:55 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <20120516145655.GH26714@mail.yitter.info>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4FB3B6E0.2070506@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: Wed, 16 May 2012 14:57:05 -0000

On Wed, May 16, 2012 at 07:17:04AM -0700, Dave Crocker wrote:
> Case does not define meaning in normal language, why should it here?

That is false.  Consider these two passages:

    The King asked the Queen,
    and the Queen asked the dairy-maid â€¦

vs

    The king asked the queen,
    and the queen asked the dairy-maidâ€¦

The King is not the kind and the Queen is not the queen, and you can
tell just by virtue of the initial capital letter (and though you
can't tell which king or queen, you can tell for sure which King and
which Queen.  The King has no current referent, rather like Russell's
present King of France, bald or otherwise).  What's more, you can tell
which dairy-maid in the first passage (by virtue of relation to the
Queen) but not in the second.

But your claim is actually a symptom of the disease you've diagnosed:
computers obliterated distinctions that are important in the writing
of natural languages, mostly because case transformation for ASCII was
a trivial task and treating these differences as meaningless saved
some work.  Many have stopped treating case as meaningful.

Since the task of written specification is to be as clear as possible,
I have to agree with your conclusion, despite disagreeing with the
premise: the lower case form of a protocol word will confuse people
too, and therefore we mustn't rely on case alone to carry the freight.
Use other words.

> Because, after all, technical specification language is already such
> elegant prose, maintaining that elegance is more important than
> robustly encoding the semantic of being normative in a way that
> avoids ambiguity?

One dreams of a period in which precision and elegance were not
mutually exclusive properties.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From simon.perreault@viagenie.ca  Wed May 16 08:06:22 2012
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 93F9121F863E for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8R+QHJbC4e9 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:06:22 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 301A721F8584 for <ietf@ietf.org>; Wed, 16 May 2012 08:06:22 -0700 (PDT)
Received: from [IPv6:2607:fa48:94:201:7dcb:4d7f:6ab0:60f0] (unknown [IPv6:2607:fa48:94:201:7dcb:4d7f:6ab0:60f0]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 861554003E for <ietf@ietf.org>; Wed, 16 May 2012 11:06:20 -0400 (EDT)
Message-ID: <4FB3C271.6040902@viagenie.ca>
Date: Wed, 16 May 2012 11:06:25 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info>
In-Reply-To: <20120516145655.GH26714@mail.yitter.info>
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: Wed, 16 May 2012 15:06:22 -0000

On 2012-05-16 10:56, Andrew Sullivan wrote:
>> Because, after all, technical specification language is already such
>> elegant prose, maintaining that elegance is more important than
>> robustly encoding the semantic of being normative in a way that
>> avoids ambiguity?
>
> One dreams of a period in which precision and elegance were not
> mutually exclusive properties.

You mean when French was the dominant language?

Simon

From dhc@dcrocker.net  Wed May 16 08:08:33 2012
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 4A97921F86AB for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:08: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 C6UmhvUKChlU for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:08:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAB021F86A8 for <ietf@ietf.org>; Wed, 16 May 2012 08:08:32 -0700 (PDT)
Received: from [192.168.1.132] (cpe-76-93-137-195.san.res.rr.com [76.93.137.195]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GF8KiM019169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 May 2012 08:08:30 -0700
Message-ID: <4FB3C2E0.9030505@dcrocker.net>
Date: Wed, 16 May 2012 08:08:16 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info>
In-Reply-To: <20120516145655.GH26714@mail.yitter.info>
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.17]); Wed, 16 May 2012 08:08:31 -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: Wed, 16 May 2012 15:08:33 -0000

On 5/16/2012 7:56 AM, Andrew Sullivan wrote:
> But your claim is actually a symptom of the disease you've diagnosed:
> computers obliterated distinctions that are important in the writing
> of natural languages, mostly because case transformation for ASCII was
> a trivial task and treating these differences as meaningless saved
> some work.  Many have stopped treating case as meaningful.


ahh.  it's computerization THAT HAS COMPLETELY CHANged MeaNing.

gOOd to NO.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From hartmans@mit.edu  Wed May 16 08:58:50 2012
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 1944821F8631 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.651
X-Spam-Level: 
X-Spam-Status: No, score=-102.651 tagged_above=-999 required=5 tests=[AWL=-0.386, 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 2B8JGLo59JXC for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 08:58:49 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDAD21F862B for <ietf@ietf.org>; Wed, 16 May 2012 08:58:49 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 871C82014F; Wed, 16 May 2012 11:54:30 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 28BF544B1; Wed, 16 May 2012 11:58:28 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: adrian@olddog.co.uk
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk>
Date: Wed, 16 May 2012 11:58:28 -0400
In-Reply-To: <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> (Adrian Farrel's message of "Wed, 16 May 2012 15:44:27 +0100")
Message-ID: <tslaa18w21n.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:58:50 -0000

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

    Adrian> How about...  The key words "MUST", "MUST NOT", "REQUIRED",
    Adrian> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
    Adrian> "MAY", and "OPTIONAL" in this document are to be interpreted
    Adrian> as described in [RFC2119] when they appear in ALL CAPS.
    Adrian> These words may also appear in this document in lower case
    Adrian> as plain English words, absent their normative
    Adrian> meanings. Other words found in this document MAY also have
    Adrian> their expected meanings. The term TROLL-BAIT is to be
    Adrian> interpreted as described in [1].


I like this a lot with no sarcasm intended.
I'll note that  in my normal reading mode I  do not distinguish case,
but even so I find the ability to use may and should in RFC text without
the 2119 implications valuable.

Yes, you need to be careful. Yes, you should consider how your reader
might or might not notice the difference.  Consider though if you're
saying something like "an octet may contain a value between 0 and 255."
It's not really normative; it's a statement of fact. However, the world
will not really be made worse if someone checks the range of their octet
values.

From hsantos@isdg.net  Wed May 16 10:48:24 2012
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 47AD821F8628 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 10:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.567
X-Spam-Level: 
X-Spam-Status: No, score=-0.567 tagged_above=-999 required=5 tests=[AWL=-0.749, BAYES_20=-0.74, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=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 gwtO9MdCqXPl for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 10:48:23 -0700 (PDT)
Received: from mail.catinthebox.net (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6C40E21F8617 for <ietf@ietf.org>; Wed, 16 May 2012 10:48:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=111; t=1337190501; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=l/K2JPEnuBSlPCWJ0RW53IITdjQ=; b=HxCYRJgPQMYPPFyLRenS mH80tPq2m9EQrShbYxjwVTljHbAslGvkUZqOFokh5BXXUj62T7jF9HImk3pY6pQG BsWw3Lr7ANnVPal9JlrjkqEtkDTkwtKaqheRPrvQb7C+M0vufmsjQS3UavzYxG6Z ny1b4cEl5kXBvDHETSm4yVc=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 13:48:21 -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 v6.4.454.1) with ESMTP id 1802328354.90.2180; Wed, 16 May 2012 13:48:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=111; t=1337190478; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=CqWZ5LZ HsVcnhfXobq3xqn2jNKMinas3j4tEjVjtydM=; b=DYPeYEcYX8sp+XbmusVmxIf azcVWBP3/Gu/aDPzd656bBUsHND7JFtamx9IfI+wUbCPcTMNNoBirbp7ZsGzbNHG n9ZLWVq0P+hU4rWUgdPVxv9o4O3Uw2xp39crIy6hJdR/iCOSf/rvsZZ6nLQTJWth zwYxN5sEmLsLkYFkamnk=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 13:47:58 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2401210987.7614.5320; Wed, 16 May 2012 13:47:57 -0400
Message-ID: <4FB3E85A.7050804@isdg.net>
Date: Wed, 16 May 2012 13:48:10 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m2boloci9k.wl%randy@psg.com>
In-Reply-To: <m2boloci9k.wl%randy@psg.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: Wed, 16 May 2012 17:48:24 -0000

+1

Randy Bush wrote:
> can != may
> 
> one is ability, the other permission
> 
> randy
> 
> 

-- 
HLS



From stpeter@stpeter.im  Wed May 16 10:53:37 2012
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 1D74121F8592 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 10:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4+Ov8Vh1cMBP for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 10:53:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 49AFB21F866A for <ietf@ietf.org>; Wed, 16 May 2012 10:53:35 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0055240067; Wed, 16 May 2012 12:09:18 -0600 (MDT)
Message-ID: <4FB3E99D.1040606@stpeter.im>
Date: Wed, 16 May 2012 11:53:33 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu>
In-Reply-To: <tslaa18w21n.fsf@mit.edu>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Wed, 16 May 2012 17:53:37 -0000

On 5/16/12 9:58 AM, Sam Hartman wrote:
>>>>>> "Adrian" == Adrian Farrel <adrian@olddog.co.uk> writes:
> 
>     Adrian> How about...  The key words "MUST", "MUST NOT", "REQUIRED",
>     Adrian> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
>     Adrian> "MAY", and "OPTIONAL" in this document are to be interpreted
>     Adrian> as described in [RFC2119] when they appear in ALL CAPS.
>     Adrian> These words may also appear in this document in lower case
>     Adrian> as plain English words, absent their normative
>     Adrian> meanings. Other words found in this document MAY also have
>     Adrian> their expected meanings. The term TROLL-BAIT is to be
>     Adrian> interpreted as described in [1].
> 
> 
> I like this a lot with no sarcasm intended.
> I'll note that  in my normal reading mode I  do not distinguish case,
> but even so I find the ability to use may and should in RFC text without
> the 2119 implications valuable.

Your mileage may (or is that MAY?) vary, but to forestall confusion I've
settled on the practice of using "can" and "might" instead of lowercase
"may", "ought to" and "is suggested to" instead of lowercase "should",
and "needs to" or "has to" instead of lowercase "must" (etc.). I'm not
saying that anyone else SHOULD or MUST use that convention, but you
might consider it in your own spec-writing.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From mary.ietf.barnes@gmail.com  Wed May 16 11:02:22 2012
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 0D8E721F846E for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.633
X-Spam-Level: 
X-Spam-Status: No, score=-103.633 tagged_above=-999 required=5 tests=[AWL=-0.035, 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 PVkO6KbXTi3l for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:02:18 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7D021F86FA for <ietf@ietf.org>; Wed, 16 May 2012 11:02:18 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1147208vbb.31 for <ietf@ietf.org>; Wed, 16 May 2012 11:02: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=3jLO4okH3Di5RXBaMPUE4EIxT8L5So4cYpFA8iiHZX8=; b=MVrEcqohI6gYtgwDhHdq5KQGZ6O7ardyi23cXUz9sSvhhnTp/EAKOFXatWPhrN/yDN 9mN405vnc1Cz92oc4PMQQKuei5XzTx5WaP2Dy1pjTfBiEW2mawlpRrWQbnJZSvhhDtsq Y/Jq7C0sV5iIiENJzLHVe0HDTQ/DFslq7dIYoamp8Q/Bs57uEq+O0cQNkVlBaYA5AHTg 8jaOZs6Fpb6TeSHMtw0UYvibciDSocz+whLrU7bsiuX3ujrs0ugCFXOOfLVSc0sw6Fix +mabejyrvMwpyF6I/9Rp8h2LmH3ZxkbilnjSWKG7sK+oOjB7hQ4NDWMG8DnFTuL1OBws m71A==
MIME-Version: 1.0
Received: by 10.52.28.71 with SMTP id z7mr2522148vdg.105.1337191337752; Wed, 16 May 2012 11:02:17 -0700 (PDT)
Received: by 10.52.166.100 with HTTP; Wed, 16 May 2012 11:02:17 -0700 (PDT)
In-Reply-To: <4FB3E99D.1040606@stpeter.im>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im>
Date: Wed, 16 May 2012 13:02:17 -0500
Message-ID: <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=20cf3078119eaef82904c02b1e47
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 18:02:22 -0000

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

Peter,

I also try to follow the same practice after I got the suggestion for one
of my documents. The issue I see with the suggestion that "may" is not
normative whereas MAY is, is that it is not at all uncommon for folks to
typo and forget to make the "may" uppercase - that puts the burden on the
RFC editor to find those if others don't during IETF LC.  I also believe
that many times that "may" is used, it actually is better stated as "can"
and the same with "ought" for "should".

Mary.

On Wed, May 16, 2012 at 12:53 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> On 5/16/12 9:58 AM, Sam Hartman wrote:
> >>>>>> "Adrian" == Adrian Farrel <adrian@olddog.co.uk> writes:
> >
> >     Adrian> How about...  The key words "MUST", "MUST NOT", "REQUIRED",
> >     Adrian> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
> >     Adrian> "MAY", and "OPTIONAL" in this document are to be interpreted
> >     Adrian> as described in [RFC2119] when they appear in ALL CAPS.
> >     Adrian> These words may also appear in this document in lower case
> >     Adrian> as plain English words, absent their normative
> >     Adrian> meanings. Other words found in this document MAY also have
> >     Adrian> their expected meanings. The term TROLL-BAIT is to be
> >     Adrian> interpreted as described in [1].
> >
> >
> > I like this a lot with no sarcasm intended.
> > I'll note that  in my normal reading mode I  do not distinguish case,
> > but even so I find the ability to use may and should in RFC text without
> > the 2119 implications valuable.
>
> Your mileage may (or is that MAY?) vary, but to forestall confusion I've
> settled on the practice of using "can" and "might" instead of lowercase
> "may", "ought to" and "is suggested to" instead of lowercase "should",
> and "needs to" or "has to" instead of lowercase "must" (etc.). I'm not
> saying that anyone else SHOULD or MUST use that convention, but you
> might consider it in your own spec-writing.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>

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

<div>Peter,</div><div><br></div>I also try to follow the same practice afte=
r I got the suggestion for one of my documents. The issue I see with the su=
ggestion that &quot;may&quot; is not normative whereas MAY is, is that it i=
s not at all uncommon for folks to typo and forget to make the &quot;may&qu=
ot; uppercase - that puts the burden on the RFC editor to find those if oth=
ers don&#39;t during IETF LC. =A0I also believe that many times that &quot;=
may&quot; is used, it actually is better stated as &quot;can&quot; and the =
same with &quot;ought&quot; for &quot;should&quot;. =A0<div>
<br></div><div>Mary. =A0<br><br><div class=3D"gmail_quote">On Wed, May 16, =
2012 at 12:53 PM, Peter Saint-Andre <span dir=3D"ltr">&lt;<a href=3D"mailto=
:stpeter@stpeter.im" target=3D"_blank">stpeter@stpeter.im</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 5/16/12 9:58 AM, Sam Hartman wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt; &quot;Adrian&quot; =3D=3D Adrian Farrel &lt;<a hre=
f=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; writes:<br>
&gt;<br>
&gt; =A0 =A0 Adrian&gt; How about... =A0The key words &quot;MUST&quot;, &qu=
ot;MUST NOT&quot;, &quot;REQUIRED&quot;,<br>
&gt; =A0 =A0 Adrian&gt; &quot;SHALL&quot;, &quot;SHALL NOT&quot;, &quot;SHO=
ULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,<br>
&gt; =A0 =A0 Adrian&gt; &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this d=
ocument are to be interpreted<br>
&gt; =A0 =A0 Adrian&gt; as described in [RFC2119] when they appear in ALL C=
APS.<br>
&gt; =A0 =A0 Adrian&gt; These words may also appear in this document in low=
er case<br>
&gt; =A0 =A0 Adrian&gt; as plain English words, absent their normative<br>
&gt; =A0 =A0 Adrian&gt; meanings. Other words found in this document MAY al=
so have<br>
&gt; =A0 =A0 Adrian&gt; their expected meanings. The term TROLL-BAIT is to =
be<br>
&gt; =A0 =A0 Adrian&gt; interpreted as described in [1].<br>
&gt;<br>
&gt;<br>
&gt; I like this a lot with no sarcasm intended.<br>
&gt; I&#39;ll note that =A0in my normal reading mode I =A0do not distinguis=
h case,<br>
&gt; but even so I find the ability to use may and should in RFC text witho=
ut<br>
&gt; the 2119 implications valuable.<br>
<br>
Your mileage may (or is that MAY?) vary, but to forestall confusion I&#39;v=
e<br>
settled on the practice of using &quot;can&quot; and &quot;might&quot; inst=
ead of lowercase<br>
&quot;may&quot;, &quot;ought to&quot; and &quot;is suggested to&quot; inste=
ad of lowercase &quot;should&quot;,<br>
and &quot;needs to&quot; or &quot;has to&quot; instead of lowercase &quot;m=
ust&quot; (etc.). I&#39;m not<br>
saying that anyone else SHOULD or MUST use that convention, but you<br>
might consider it in your own spec-writing.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
<br>
--<br>
Peter Saint-Andre<br>
<a href=3D"https://stpeter.im/" target=3D"_blank">https://stpeter.im/</a><b=
r>
<br>
<br>
</font></span></blockquote></div><br></div>

--20cf3078119eaef82904c02b1e47--

From brian.e.carpenter@gmail.com  Wed May 16 11:11:21 2012
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 2128021F86B7 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.587
X-Spam-Level: 
X-Spam-Status: No, score=-101.587 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 Ur4jJd1+-oKr for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:11:15 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9AF21F8625 for <ietf@ietf.org>; Wed, 16 May 2012 11:11:15 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so696060wgb.13 for <ietf@ietf.org>; Wed, 16 May 2012 11:11: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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Frt7h1A22h5WlSwg08b/3I/3yBzAQO84qGCFLJO71VA=; b=mlg5smgWiGLizcKLrngaUdzU/H2X3s0+uYX5LGOnyzZhkJ/w/MkNqOdE8Qm2sCWleL 9vqeV++9vTrE91dC6PWaN+9rvs+ajZwJZerjNEdCsYwTeZkDQ08sYK2ve0HIhp3ZLXDR iFRaxZSwP97kWOuYLf7Rm+cNjV/D2XMgHOJqhnMvh6RilgkKmbNlHUByxB6cLI2AC7iR aAnMXwaFbNCvsOgo9OiJXUcK61Rt3oB3fwgfakPOCzZHpy6jylkSugbNkuii4G3FTLj0 na7M1kpxGiWDcrZr9HEkKLBGLAMISd9UE2EnIE1+COx4irpO7RXrq+2nmrR/zIFWriBm QgYg==
Received: by 10.180.102.101 with SMTP id fn5mr10372637wib.6.1337191874476; Wed, 16 May 2012 11:11:14 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-67.as13285.net. [2.102.216.67]) by mx.google.com with ESMTPS id ga8sm11374372wib.5.2012.05.16.11.11.11 (version=SSLv3 cipher=OTHER); Wed, 16 May 2012 11:11:13 -0700 (PDT)
Message-ID: <4FB3EDB8.60809@gmail.com>
Date: Wed, 16 May 2012 19:11:04 +0100
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: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk>	<tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im>
In-Reply-To: <4FB3E99D.1040606@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 18:11:21 -0000

On 2012-05-16 18:53, Peter Saint-Andre wrote:
> On 5/16/12 9:58 AM, Sam Hartman wrote:

...
>> I'll note that  in my normal reading mode I  do not distinguish case,
>> but even so I find the ability to use may and should in RFC text without
>> the 2119 implications valuable.

Agreed. But as a gen-art reviewer, I have several times had to ask
authors whether a particular lower case "may" was intended to be normative
or normal English. Authors must be fastidious about this.

> Your mileage may (or is that MAY?) vary, but to forestall confusion I've
> settled on the practice of using "can" and "might" instead of lowercase
> "may", "ought to" and "is suggested to" instead of lowercase "should",
> and "needs to" or "has to" instead of lowercase "must" (etc.). I'm not
> saying that anyone else SHOULD or MUST use that convention, but you
> might consider it in your own spec-writing.

It is indeed very important not to use "may" when it's ambiguous.
"It may rain today" is fine; "you may leave now" is not (I can think
of three different meanings). In RFC2119-talk, "you MAY leave now"
only has one meaning.

   Brian

From ole@cisco.com  Wed May 16 11:26:06 2012
Return-Path: <ole@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 DDEFE21F866C for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.69
X-Spam-Level: 
X-Spam-Status: No, score=-110.69 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 csmZez1jKV6J for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:26:06 -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 69A0121F84DE for <ietf@ietf.org>; Wed, 16 May 2012 11:26:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=427; q=dns/txt; s=iport; t=1337192766; x=1338402366; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=Nrnbu6OVLvGdmPM5uDX8MfGrC0dGwVf/XZDGvljPRhw=; b=ECG/BZ8J1KYsMyLm9Vvdm+OukJf2NM3dax0rFOP4JNtuzKuwWB1W7hn0 2VKatU+9/CreFwyL+mGv+wOlPeqS9A/mjkiDJZLfLJ6TftWDiGMwTsJcA bDOCC363RabqUth0FGfkBJLmvTsEUSnXR4ZyJg596mw6SkLvXgyedbDTZ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIvTs0+tJV2d/2dsb2JhbABBA7QLgQeCFgEBBBIBAiU/EAtGVwYTIodsmyODRRCcMIssghSDKAOIY5hXgxeBAmeDCYE/
X-IronPort-AV: E=Sophos;i="4.75,604,1330905600"; d="scan'208";a="83647306"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 16 May 2012 18:26:06 +0000
Received: from bxb-vpn3-744.cisco.com (bxb-vpn3-744.cisco.com [10.86.250.232]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q4GIQ3c8021443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 18:26:04 GMT
Date: Wed, 16 May 2012 11:26:02 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@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: Wed, 16 May 2012 18:26:07 -0000

And of course if we had a slightly richer publication format we could 
use, oh, say, underline, bold, italics and maybe even a special font 
for normative terms, but I guess I am dreaming decades ahead...

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From stpeter@stpeter.im  Wed May 16 11:43:30 2012
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 0809221F866C for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OO5eqFz2N31r for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:43:29 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4B96E21F865A for <ietf@ietf.org>; Wed, 16 May 2012 11:43:29 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9951D40067; Wed, 16 May 2012 12:59:12 -0600 (MDT)
Message-ID: <4FB3F54F.2030705@stpeter.im>
Date: Wed, 16 May 2012 12:43:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 18:43:30 -0000

On 5/16/12 12:26 PM, Ole Jacobsen wrote:
> 
> And of course if we had a slightly richer publication format we could 
> use, oh, say, underline, bold, italics and maybe even a special font 
> for normative terms, but I guess I am dreaming decades ahead...

Although I too dream the impossible dream, I would prefer not to trust
in formatting to enforce the semantic distinction in this instance.

Peter

From adrian@olddog.co.uk  Wed May 16 11:45:37 2012
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 0EA5721F8655 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 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 84Afs+j4wf5H for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:45:36 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6021F861C for <ietf@ietf.org>; Wed, 16 May 2012 11:45:35 -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 q4GIjV22018119;  Wed, 16 May 2012 19:45:31 +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 q4GIjUgR018108 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 May 2012 19:45:31 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Peter Saint-Andre'" <stpeter@stpeter.im>, "'Ole Jacobsen'" <ole@cisco.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im>
In-Reply-To: <4FB3F54F.2030705@stpeter.im>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Date: Wed, 16 May 2012 19:45:28 +0100
Message-ID: <097701cd3394$113cb520$33b61f60$@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: AQFpat9TDb/FjKlnnRfytPU9brudgAJtdb6SAUcBXMACpPelUwJZ29rfAeBZyNoBw7xEwgH5kHzhlyHKdWA=
Content-Language: en-gb
Cc: 'Sam Hartman' <hartmans-ietf@mit.edu>, 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, 16 May 2012 18:45:37 -0000

Remind me:
Is bold must more or less compelling that underlined must. And where =
does uppercase MUST fit in?

I fear the slightly richer publication format will give rise to a =
slightly more complex revision of RFC 2119.

Adrian

> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter@stpeter.im]
> Sent: 16 May 2012 19:43
> To: Ole Jacobsen
> Cc: Mary Barnes; adrian@olddog.co.uk; Sam Hartman; ietf@ietf.org
> Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
>=20
> On 5/16/12 12:26 PM, Ole Jacobsen wrote:
> >
> > And of course if we had a slightly richer publication format we =
could
> > use, oh, say, underline, bold, italics and maybe even a special font
> > for normative terms, but I guess I am dreaming decades ahead...
>=20
> Although I too dream the impossible dream, I would prefer not to trust
> in formatting to enforce the semantic distinction in this instance.
>=20
> Peter


From ole@cisco.com  Wed May 16 11:46:29 2012
Return-Path: <ole@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 4CFDF21F866C for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.682
X-Spam-Level: 
X-Spam-Status: No, score=-110.682 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 yytLfFD3dkrn for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 11:46:28 -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 BE32721F865A for <ietf@ietf.org>; Wed, 16 May 2012 11:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=926; q=dns/txt; s=iport; t=1337193988; x=1338403588; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=herdpmaQUqv+BiNCbvchNVoGnqQeo1wDDdZheV0Mdhk=; b=O65OAOnsuTOz6+wMEdHPI0AlG3YDK07CeP5rvygoli7R+yvYN3zG1scF FEq/rQyqaa08AHcNF1a9yAto7naiARaauhPV9ZCt9w5B4J52kklUbiY46 kEFhEDlW+Z1Afv9+eBu1l0cHUoJmeQ5GYhUUxyERLtv04juEIr0XB9dKZ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIvTs0+tJV2d/2dsb2JhbABBA7QLgQeCFQEBAQMBEgECJT8FCwsYLlcGEyKHZwWbI4NFEJwwixMZghSDKAOIY5hXgxeBAmeDCYE/
X-IronPort-AV: E=Sophos;i="4.75,604,1330905600"; d="scan'208";a="83653715"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 16 May 2012 18:46:28 +0000
Received: from bxb-vpn3-744.cisco.com (bxb-vpn3-744.cisco.com [10.86.250.232]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q4GIkPp6010058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 May 2012 18:46:27 GMT
Date: Wed, 16 May 2012 11:46:24 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <4FB3F54F.2030705@stpeter.im>
Message-ID: <alpine.OSX.2.01.1205161144580.47757@bxb-vpn3-744.cisco.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@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: Wed, 16 May 2012 18:46:29 -0000

Yeah, that's probably a safer approach. One could of course
imagine some kind of hybrid and parsing in the form of *very*
or /very/ explicit terms. Maybe this is orthogonal to the
other discussion we are having...

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Wed, 16 May 2012, Peter Saint-Andre wrote:

> On 5/16/12 12:26 PM, Ole Jacobsen wrote:
> > 
> > And of course if we had a slightly richer publication format we could 
> > use, oh, say, underline, bold, italics and maybe even a special font 
> > for normative terms, but I guess I am dreaming decades ahead...
> 
> Although I too dream the impossible dream, I would prefer not to trust
> in formatting to enforce the semantic distinction in this instance.
> 
> Peter
> 

From jmvalin@jmvalin.ca  Tue May 15 17:33:30 2012
Return-Path: <jmvalin@jmvalin.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 7D18321F85F2; Tue, 15 May 2012 17:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 EQNhI0S0FQaq; Tue, 15 May 2012 17:33:26 -0700 (PDT)
Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by ietfa.amsl.com (Postfix) with ESMTP id 07FB921F85F1; Tue, 15 May 2012 17:33:26 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)"
Received: from [192.168.1.14] ([96.21.20.94]) by VL-VM-MR006.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0M4300KGTAVO2L70@VL-VM-MR006.ip.videotron.ca>; Tue, 15 May 2012 20:33:25 -0400 (EDT)
Message-id: <4FB2F5D0.7070701@jmvalin.ca>
Date: Tue, 15 May 2012 20:33:20 -0400
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
To: Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: Gen-art last call review of  draft-ietf-codec-opus-12.txt (completed)
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk>
In-reply-to: <1337001184.23527.1544.camel@mightyatom.folly.org.uk>
X-Enigmail-Version: 1.4.1
X-Mailman-Approved-At: Wed, 16 May 2012 12:32:14 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.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, 16 May 2012 00:33:30 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Elwyn,

Thanks for the very thorough review. We've addressed your issues and
submitted draft version -13. See our response to each of the issues you
raised (aggregated from all the authors) in the attached document.

Cheers,

	Jean-Marc

On 12-05-14 09:13 AM, Elwyn Davies 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-codec-opus-12.txt
> Reviewer:  Elwyn Davies
> Review Date:  14 May 2012 (completed)
> IETF LC End Date: 10 May 2012
> IESG Telechat date: (if known) -
> 

--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)
Content-type: text/plain; CHARSET=US-ASCII; name=Gen-art.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=Gen-art.txt

Elwyn Davies wrote:
> Major issues: 
> Can we accept the code as normative?  If not how do we proceed?

The issue with code being normative was specifically addressed in 
the guidelines document for this WG (RFC 6569).

> Minor issues:
> Contrast between decoder descriptions of LP part and CELT part:  The
> SILK descriptions go into gory detail on the values used in lots of
> tables, etc., whereas the CELT part has a very limited treatment of the
> numeric values used (assuming reliance on finding the values in the
> reference implementation, either explictly or implicitly).  There are
> things to be said for both techniques.  I was wondering (while reading
> the SILK description) if the authors have any means of automatically
> generating the tables from the code in the SILK part (or vice versa) to
> avoid double maintenance. On the other hand, there are pieces of the
> CELT decoder description (especially in s4.3.3 where knowing numbers of
> bands, etc.) where some actual numbers would help comprehension.
> 

We have made many changes to section 4.3 (and 4.3.3 specifically) to address
the specific issues below. As for the tables, they are not generated
automatically.


> s2 (and more generally):  The splitting of the signal in the frequency
> domain into signal (components?) below and above 8kHz presumably
> requires that the signal is subjected to a Discrete Fourier Transform to
> allow the signal to be split.  I think sometging is needed in s2 to
> explain how this is managed (or if I don't understand, to explain why it
> isn't necessary).

No DFT is used. The lower band is obtained through resampling (which is already described) and the higher band is obtained by not coding the lower band with CELT (the text says that CELT starts at band 17 in hybrid mode). The explanation was reworded to make this as clear as possible at this point in the text.

> s4.1: Despite having found a copy of the range coding paper and tried to
> read it, I found the whole business of range coding opaque.  Given that
> this is (I think) fairly novel, some additional less opaque description
> could be very helpful to people trying to understand what is going on.
> In particular knowledge of how entropy coding works is pretty much a
> prerequisite.

Added a link to the Wikipedia article on range coding.

> s4.2.5, para 3:
>>     When switching from 20 ms to 10 ms, the 10 ms
>>     20 ms Opus frame, potentially leaving a hole that needs to be
>>     concealed from even a single packet loss.
> How?

As explained in the LBRR text, a 10 ms frame will only contain 10 ms LBRR data even if the previous frame was 20 ms, so there's 10 ms "missing".

> s4.2.5, para 4:
>> In order to properly produce LBRR frames under all conditions, an
>>     encoder might need to buffer up to 60 ms of audio and re-encode it
>>     during these transitions.  However, the reference implementation opts
>>     to disable LBRR frames at the transition point for simplicity.
>>
> Should this be phrased in RFC 2119 requiremenmts language?  The first
> part sounds like a SHOULD with the second part being the get out , but
> its not entirely clear what the consequences are other then simplicity.

There really is no SHOULD there. We're just describing possible strategies for encoding. In general, we have avoided 2119 language as much as possible for the encoder. However, the sentence, "Since transitions are relatively infrequent in normal usage, this does not have a significant impact on packet loss robustness," was added to alleviate any concerns about the consequences of this decision.

> ======================================================================
>              MINOR ISSUES ABOVE submitted as part 1 of review
> ======================================================================
> general/s11.2:  Several references [Hadamard], [Viterbi}, etc., are to
> Wikipaedia pages.  Whilst these are convenient (and only illustrative)
> they are not guaranteed to be very stable.  Better (i.e., more stable)
> references are desirable.

We believe that the links themselves should be quite stable. We could 
also link specific revisions in Wikipedia, but the quality of the content
is more likely to get better than worse. Considering
that these references are informational, we believe that Wikipedia is a
good source.

> s1, para 2:
>>     The decoder contains a great deal of integer and fixed-point
>>     arithmetic which must be performed exactly, including all rounding
>>     considerations,...
> Is this a MUST?  There are instances in the text which might contradict
> this (e.g., para 1 of s4.2.7.5 which has (capitalized) SHOULDs).

This sentence did not mean to imply that _all_ such arithmetic must be performed exactly, only that there exists a good deal of arithmetic for which this is true (for example, to achieve the final range check MUST from Section 6). Since it isn't clear at this point exactly which arithmetic is being referred to, we can't use RFC 2119 strength here. Replaced "must be" with "needs to be" to avoid the impression of an RFC 2119 requirement.

> s4.3:
> As a complete newcomer to CELT, I would have appreciated a more high
> level understanding of what CELT is doing at this point.  I  tried
> reading s4.3 without any additional input and found it very hard going.
> Eventually I gave up and went looking for some additional input.  This
> presentation seems to have a useful view 
> http://www.ietf.org/proceedings/79/slides/codec-2.pdf
> I think that it would be extremely helpful to have a description similar
> to this at this point in the document, even though there is some
> material in section 5.3 which could also be forward referenced.  Still
> the material in s5.3 does not start from the basic principles that CELT
> is using, and since these are essentially novel, it would be very good
> to give prospective implementers/users an understanding of what is going
> on.  Incidentally, I found the above IETF presentation more useful than
> http://www.celt-codec.org/presentations/misc/lca-celt.pdf
> Note that the SILK part seems rather less opaque.  It would also be
> useful to indicate numerically how many bands are involved and what the
> number of MDCT bins are in the various bands. 

The intro of section 4.3 has been expanded with general information about CELT
similar to what the codec-2.pdf slides from 79 included. 

> s4.3, last para: Can the 'out of range error' occur in the LP decoder? (if not why not?)

Added the following text:
"Such out of range errors cannot occur in the SILK layer."


> ======================================================================
> 
> Nits/editorial comments:
> 
> global: bytes ->  octets

We believe that in the field of audio codecs, the mention of "byte" without
further context is well understood to mean 8 bits.

> global: The form/terminology Q<n>  (e.g., Q13, Q15, Q16) ought to be
> explained.

This was already defined in the section on notation:
   The notation "Q<n>", where n
   is an integer, denotes the number of binary digits to the right of
   the decimal point in a fixed-point number. 

> s1: Expand CELP

Done.
 
> s1.1.6: Need to define floor().

Done. Also defined abs(), ceil(), and round().

> s2: ? Expand SILK

SILK is not an acronym.

> s2: Reference for Vorbis.

Linked to http://xiph.org/vorbis/

> s2.1.8: Expand AAC (and MP3).

Expanded
MP3: MPEG 1, Layer 3
AAC: Advanced Audio Coding

> s3: References for Ogg, Matroska, maybe RTP.

Done.

> s3: Fig 1, Table 2 and intervening text:  Presumably SILK only (Table 2)
> etc correspond to MODES 1-3 in Figure 1. This needs to be consistent.

Changed LP to SILK and MDCT to CELT.

> s3.2.1: Make it clear which of the octets is len[0]/len[1].  To be
> precise it might be better to say len0/len1 are the values of the two
> length octets (in whichever order you intend). The form len[0] could be
> misinterpreted as a function 'length of 0'.

Replaced len[0] and len[1] with first_byte and second_byte, respectively.

> s3.2.5: better s/figure below/Figure 5/

Fixed for all cases of "figure below".

> s3.2.5:
>> In the CBR case, the compressed length of each frame in bytes is
>>     equal to the number of remaining bytes in the packet after
>>     subtracting the (optional) padding, (N-2-P), divided by M. This
>>     number MUST be a non-negative integer multiple of M.
> 'This number' is not the  compressed length of each frame that is the
> subject of the first sentence, but the number of remaining octets - this
> needs rewording.

Fixed by defining R=N-2-P, e.g.,
   In the CBR case, let R=N-2-P be the number of bytes remaining in the
   packet after subtracting the (optional) padding.  Then the compressed
   length of each frame in bytes is equal to R/M. The value R MUST be a
   non-negative integer multiple of M. The compressed data for all M
   frames follows, each of size R/M bytes, as illustrated in Figure 6.
 
> s3.2.5:
>> The number of header bytes (TOC byte, frame
>>     count byte, padding length bytes, and frame length bytes), plus the
>>     length of the first M-1 frames themselves, plus the length of the
>>     padding MUST be no larger than N, the total size of the packet.
> Surely this is a non sequitur? This might be better phrased as 'The
> total size of a well formed packet MUST be at least...'

Note that the text mentions the "length of the first M-1 frames", so the calculation does not include the size of the last frame. That being said, we also clarified by using "signaled length" instead of "length".

> s3.3: The example diagrams ought to have figure numbers.

Fixed.

> s3.4: I am not keen on duplicating normative requirements in this way
> (double maintenance issue).  It would be better to put explicit numbered
> requirements in the sections above an reference the resulting numbers
> here.

A checklist style summary is quite useful for implementors, and worth the maintenance burden for a document that is (hopefully) going to be published once and read many times. The list intentionally does not include any RFC 2119 keywords, to avoid any conflict should there (accidentally) be room to interpret the re-statement any differently from the original statement. Numbering the requirements and referencing the numbers is still a good idea, but it should be possible to read the list without flipping back and forth to the previous sections.

> s4.1:
>> The decoder initializes rng to 128 and initializes val to
>>     127 minus the top 7 bits of the first input octet.
> How are the 'top seven bits' to be interpreted here? e.g. as the bottom
> seven bits of a 8 bit integer field? an 8 bit integer with the lowest
> bit zeroed out?

Tried for something more explicit:
   Let b0 be the first input octet (or zero if there are no octets in
   this Opus frame).  The decoder initializes rng to 128 and initializes
   val to (127 - (b0>>1)), where (b0>>1) is the top 7 bits of the first
   input octet.  It saves the remaining bit, (b0&1), for use in the
   renormalization procedure described in ...

> s4.1.1:  This is really a global point.  This section refers to
> entdec.c.  Presumably (since we haven't reached the code yet) and it is
> still compressed, there is some file structure.  I don't think this has
> been said above.  It would be good to provide a list of the file
> components (i.e., sectional structure of the code) at the start, maybe
> even  giving line number positions within the decompressed code.

In cases where it was deemed necessary (e.g. large functions), there are
indeed line numbers in references to the code. As for a list of files
we did not think it was useful because one already needs to decompress
the code to see the references.

> s4.1.1.1:
>> Then it reads the next octet of the
>>     payload and combines it with the left-over bit buffered from the
>>     previous octet to form the 8-bit value sym.  It takes the left-over
>>     bit as the high bit (bit 7) of sym, and the top 7 bits of the octet
>>     it just read as the other 7 bits of sym.
> This is not well phrased.  Better
>       Then it reads the next octet of the payload [packet? payload hasn't
> really been used before] and combines the left  over bit from the

"Packet" is inaccurate, as the next byte in the packet may come from a different Opus frame. Replaced with "Opus frame" instead.

> previous octet (see Section 4.1 for starting this process) as the high
> bit (bit 7)| of 'sym' and the top 7 bits of the octet as the other 7
> bits of sym, leaving the remaining bit for the next iteration.

This may be trying to do too much in a single sentence. Perhaps:
  Then it reads the next octet of the Opus frame and forms an 8-bit
  value sym, using the left-over bit buffered from the previous octet
  as the high bit and the top 7 bits of the octet just read as the
  other 7 bits of sym.  The remaining bit in the octet just read is
  buffered for use in the next iteration.  If no more input octets
  remain, it uses zero bits instead.  See
  <xref target="range-decoder-init"/> for the initialization used to
  process the first octet.

Also broke out range-decoder-init into its own section to make it easier to reference.

> s4.1.5.2:
> Should r_Q15 = rng>>  (l-16) be r_Q15 = rng>>  (lg-16)?  There doesn't
> seem to be an 'l' defined.

Fixed. Sorry; this is a leftover from changing "l" to "lg" in response to one of the AD's review comments.

> s4.2.1: Expand LTP earlier. It would also be useful to expand LPC again.

Done (both).

> s4.2.2: acronym VAD is not expanded until the beginning of s4.2.3.

Fixed.

> s4.2.7: acronym LSF needs to be expanded on first use.

Fixed.

> s4.2.7.1: Explain briefly why Table 7 has values for indices 0 to 15
> when wi0/1 are in range 0 to 14.

Added:
   Although wi0 and wi1 only have 15 possible values, Table 7 contains
   16 entries to allow interpolation between entry wi0 and (wi0 + 1)
   (and likewise for wi1).

> s4.2.7.4, para below Table 12:
>> These 6 bits are combined to form a gain index between 0 and 63.
> s/gain index/gain_index/ as this variable is used subsequently.

Used:
  These 6 bits are combined to form a value, gain_index, between 0 and
  63.
Also updated the "delta gain index" for subframes without an independent gain, below.

> s4.2.7.4: The use of log_gain seems slightly confusing when combined
> with gain_index.  One at least is presumably log scaled.  Maybe a bit
> more explanation is needed.

The gain_index happens to map directly to log_gain for subframes with an independent gain (with the exception of the clamping), but this is not true for subframes where the gain is coded relative to the previous subframe. We are open to suggestions that would make the need for this distinction clearer.

Also replaced "previous gain index" with "previous_log_gain", as it is the latter that actually matters.

> ======================================================================
>              COMMENTS ABOVE submitted as part 1 of review
> ======================================================================
> s4.2.7.2, last para:
>> In that case, if this
>>     flag is zero (indicating that there should be a side channel), then
>>     Packet Loss Concealment (PLC, see Section 4.4) SHOULD be invoked to
>>     recover a side channel signal.
> What are the consequences (or what actions need to be taken) if it is
> not invoked?

Added:
  Otherwise, the stereo image will collapse.

> s4.2.7.5, para 1:
>> These represent the interleaved zeros on the
>>     unit circle between 0 and pi (hence "normalized") in the standard
>>     decomposition of the LPC filter into a symmetric part and an anti-
>>     symmetric part (P and Q in Section 4.2.7.5.6).
> 'on the unit circle between 0 and pi' might be clearer as 'on the upper
> half of the unit circle' or 'on the half of the unit circle in the
> positive imaginary area of the complex plane'.
> 'standard decomposition'?  Needs a reference.

Reworded as:
   These represent the interleaved zeros on the upper half of the unit
   circle (between 0 and pi, hence "normalized") in the standard
   decomposition [line-spectral-pairs] of the LPC filter into a
   symmetric part and an anti-symmetric part (P and Q in Section
   4.2.7.5.6).

Added the reference [line-spectral-pairs] pointing to http://en.wikipedia.org/wiki/Line_spectral_pairs

> s4.2.7.5, para 1: A reference for the use of LSF in LPC would be useful.

The above reference serves this function as well.

> s4.2.7.5.x: There is inconsistent use of stage 1/stage 2 vs
> stage-1/stage-2.  Please be consusistent

"Stage 1" is correct when referring to the noun by itself, or as an object of a verb ("stage 1 decoding"). "Stage-1" is correct when modifying another noun ("stage-1 index"). However, we changed the titles of some of the tables around to allow them to use the modifier form more consistently.

> s4.2.7.5, para 1:
>>     Because of non-linear
>>     effects in the decoding process, an implementation SHOULD match the
>>     fixed-point arithmetic described in this section exactly.  An encoder
>>     SHOULD also use the same process.
> - Does this contradict the 'must' in s1, para 2?

No, for the reasons described above.

> - What are the consequences of ignoring the SHOULD?  How bad would they
> get?  Might it become unstable and how would one know?

They would not become unstable. However, changing the exact arithmetic may
lead to a decoder output that is not close enough to that of the 
reference decoder to pass the conformance test.

> s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
>     selects the PDFs for the second stage of the VQ/This indexes an
>     element in a coarse codebook that selects the PDFs for the second stage
>     of the VQ/

The text as written is correct. The index I1 is what selects the PDFs for the second stage, not the vector from the coarse codebook in Tables 23 and 24. I.e., it's saying, "This does A, B, and C."

> s4.2.7.5.3, last para: 
>> However, nothing in
>>    either the reconstruction process or the quantization process in the
>>    encoder thus far guarantees that the coefficients are monotonically
>>    increasing and separated well enough to ensure a stable filter.
> A reference that indicates why this requirement is needed would be desirable.
> (and also for s4.2.5.7.8).

Added a reference to:
P. Kabal and R. P. Ramachandran, "The Computation of Line Spectral Frequencies 
Using Chebyshev Polynomials", IEEE Trans. Acoustics, Speech, Signal Processing,
vol. 34, no. 6, pp. 1419-1426, Dec. 1986.

> s4.2.7.5.4 and Table 25: Are the values in Table 25 NDeltaMin or NDelatMin_Q15?
> The equations after Table 25 use both NDeltaMin and NDeltaMin_Q15.  Is this correct?
> In particular the first two equations deliver _Q15 values but use raw NDeltaMin.

Good catch. All uses of NDeltaMin should have been NDeltaMin_Q15.

> s4.1.1/s4.2.7.1 and other places:  The term 'exact integer division' is
> used in various places.  My understanding was that this phrase implied
> that it was known that the dividend was an exact multiple of the divisor
> by some out-of-band means.  This doesn't seem to be the case generally
> in Opus (e.g,, where both n/5 and n%5  are needed - clearly this doesn't
> anticipate n%5 == 0 every time!)  So what does 'exact integer division'
> imply?  A definition may be needed. 

The "exact" here was merely 
meant in contrast to inexact floating-point division. Removed "exact", leaving only 
"integer division" (which, like all other operators, uses C conventions, as stated in 
Notation and Conventions). Hopefully this should avoid people trying to read too much into 
the phrase.

> s4.3, last para: s/described in the figure above./described in Table 55 above./

Fixed.

> s4.3.1: 
>> The "transient" flag encoded in the bitstream has a probability of 1/8. 
> This statement appears out of the blue apparently.  Some more
> explanation of what the transient flag actually implies and why we
> should be so sure about its PDF would help.

Added a bit of context and moved the probability 1/8 to later in the text.

> s4.3.2.1: Arguably a reference is needed for the z-transform.

Reference added.

> s4.3.2.1: Avoid the equation picture splitting across page boundaries.
> in the current version it is unclear what the denominator is. (use
> needLines processing direcrive in xml2rfc).  Same applies to the
> equation below Table 57 in s4.3.4.3.

It's not quite clear how to use needLines without undesirable side-effects.
Hopefully this is something the RFC editor should be able to handle.

> 4.3.2.1, after the equations:
>> The
>>    prediction is clamped internally so that fixed point implementations
>>    with limited dynamic range do not suffer desynchronization.
> As a person with limited skills in the srt, I have no idea what
> desynchronization implies here. 

Clarified to "always remain in the same state as floating point implementations".

> 4.3.2.1, ibid:
>> We
>>    approximate the ideal probability distribution of the prediction
>>    error using a Laplace distribution with separate parameters for each
>>    frame size in intra- and inter-frame modes.
> I suspect this sentence belongs before the equation described the z-transform.
> Where are the values of the parameters for the inter-frame mode defined
> (the intra-frame ones are in the text)?

The probability model is for the difference between the energy and its
prediction. Added a reference to the table where the pdf parameters are
located in the code.

> s4.3.2.3: Paragraph on decoding band boosts:  Might be improved by using
> equations rather than the wordy descriptions used at present.
> 
> (global)s4.3.2.3, para above table 56: s/iff/if and only if/

Fixed.

> s4.3.2.3: LOG2_FRAC_TABLE is missing.

Text now says that the table is in rate.c

> s4.3.3: It would be helpful to explain either here, or at the outset of
> s4.3 overall, how the concept of energy bands and MDCT bins applies to
> the CELT part of the codec, and just how many bands and bins are used.
> Some of this is contained in s5.3.2, but the magic number 17 appears
> later in 4.3.3 which is presumably something to do with the point in the
> frequency domain that CELT takes over from LP in the hybrid mode.  It
> would make the very complex section 4.3.3 rather easier to understand
> with this extra information - I have to say I struggled!  On reflection,
> I think an example of what bits are allocated to a band and how thay rae
> subsequently used would be quite helpful - Without going to delve into
> the code I am really not clear that I understand just what bits are
> allocated and what they then encode and I have read the text quite a few
> times now.

Added an explanation of band 17 at the beginning of 4.3. There is also
some text about the number of bins per band.

> s4.3.3: Be consistent between 'tone to noise' and 'tone-to-noise'.

The text was rephrased in terms of signal-to-noise.

> s4.3.3:
>>    The band-energy normalized structure of Opus MDCT mode ensures that a
>>    constant bit allocation for the shape content of a band will result
>>    in a roughly constant tone to noise ratio, which provides for fairly
>>    consistent perceptual performance.  The effectiveness of this
>>    approach is the result of two factors: that the band energy, which is
>>    understood to be perceptually important on its own, is always
>>    preserved regardless of the shape precision, and because the constant
>>    tone-to-noise ratio implies a constant intra-band noise to masking
>>    ratio.  Intra-band masking is the strongest of the perceptual masking
>>    effects.  This structure means that the ideal allocation is more
>>    consistent from frame to frame than it is for other codecs without an
>>    equivalent structure.
> This paragraph contains a number of interesting assertions:  Is there a
> reference where one could see them justified (it may be that this is the
> result of original research in the Opus team).

The particular importance of energy preservation was substantively a discovery
of the Vorbis team during the later tuning of that codec. Vorbis encoders 
include a separate step called 'noise normalization' which attempts to restore
lost energy. In CELT this energy preservation was made implicit in the design of the
codec. 

The text here is intended to explain the motivation behind the particular
band-energy normalized structure of this part of the codec in the hopes
that a higher-level understanding would help make the component steps make
a little more sense. This is "original research", but there is now a link
to an older paper describing this research:
   [Valin2010]
              Valin, JM., Terriberry, T., Montgomery, C., and G.
              Maxwell, "A High-Quality Speech and Audio Codec With Less
              Than 10 ms delay", IEEE Trans. on Audio, Speech and
              Language Processing, Vol. 18, No. 1, pp. 58-67 2010.


> s4.3.3, paragraphs after the bullet points:  The concepts of 'shape' and
> 'shape encoding' is introcuced here without explicit definition.  Are we
> talking about the shape windowing used in FFT/MDCT here? This should be
> made clear.

The concept of shape is now discussed at the beginning of s4.3.

> s4.3.3, 5th para after bullet points: s/In the reference the maximums/In
> the reference implementation the maximums/

Fixed.

> s4.3.3, 6th para after the bullet points:  A table of bands per mode and
> number of MDCT bins  covered would be helpful here in order to  get a
> feeling for the scale of the problem.  Also the cache_caps50 table in
> the code contains the magic number 168.  Where does this come from?

The layout of the band is now included at the beginning of 4.3. Also, section
4.3.3 now includes an explanation for the size of cache_caps50 
(21 bands, 4 values of LM, mono+stereo). 

> s4.3.3, 6th para after the bullet points:
>> set LM to the shift value for the frame size (e.g. 0 for 120, 1 for
>>    240, 3 for 480),  
> Where do these frame sizes get specified? And what is the total set of
> frame sizes? The text says 'e.g.' (which incidentally should be 'e.g.,')
> implying that this is not the complete set.

The calculation of LM is now given earlier in section 4.3.3


> s4.3.3, 6th para after the bullet points: Need to define 'truncating
> integer division' to go with 'exact integer division'.

Replaced with "integer division"

> s4.3.3, 7th para after the bullet points: 
>> The band boosts are represented by a series of binary symbols which
>>    are coded with very low probability.
> How many, at least, and what values?  Are these range encoded? I don't
> see them in the table above or with a PDF specified.

The text has been clarified to say that this is entropy coded. Also, the
probabilities that correspond to 6 bit and 2 bits (1/64 and 1/4, respectively)
are given to emphasize the fact that the number of bits is directly related to
the probabilities.

> s4.3.3, 7th para after the bullet points:
>>    and every time
>>    a band is boosted the initial cost is reduced (down to a minimum of
>>    two).
> Would that be a value of two or two bits? 

Two bits (fixed in the draft).

> s4.3.3: Paragraph on decoding band boosts:  Might be improved by using
> equations rather than the wordy descriptions used at present.
> 
> (global)s4.3.3, para above table 56: s/iff/if and only if/

Fixed.

> s4.3.3, 2nd para after Table 56: 
>> For stereo frames, bits are reserved for intensity stereo and for
>>    dual stereo.  Intensity stereo requires ilog2(end-start) bits.
> The terms 'intenmsity stereo' and 'dual stereo' don't appear to have
> been defined.

Added a definition of intensity, dual, and mid-side stereo to the beginning
of section 4.3. 

> s4.3.3: LOG2_FRAC_TABLE is missing.

Text now says that the table is in rate.c

> 4.3.4.3, last para:
>>    If the decoded vector represents more than one time block, then the
>>    following process is applied separately on each time block. 
> Should this sentence come before the previous paragraph?  There  isn't
> really a 'following process' in this section and I don't think it menas
> the process in s4.3.4.4?


Indeed. Replaced "the following process" with "this spreading process".

> s4.3.4.3, last sentence: 
>> This extra rotation is applied in an interleaved manner with a stride
>>    equal to round(sqrt(N/nb_blocks))
> I think this needs some more explanation for the uninitiated.

Although "stride" is a relatively common term, we added this to the sentence:
"i.e. it is applied independently for each set of sample S_k = {stride*n + k},
n=0..N/stride-1."

> s4.3.4.4:
>> Multiple levels of splitting may be
>>    applied up to a frame size dependent limit. 
> What this limit is does not appear to be defined.

Added the limit of LM+1 splits.

> s4.3.5: The 'collapse' phenomenon is not fully defined, and it would be
> useful to mention why it happens.  Also s/min/minimum/.

Added a short description of the anti-collapse feature and fixed the
s/min/minimum/

> s4.3.6: s/Just like/Just as/

Fixed.

> s4.3.7, last para: I think 'power complementarity' requires further
> explanation or a reference.

Added reference to:
John P. Princen and Alan B. Bradley, "Analysis/synthesis filter bank design based on time domain aliasing cancellation," IEEE Trans. Acoust. Speech Sig. Proc. ASSP-34 (5), 1153-1161 (1986)

> s4.5, para 3: s/To avoid or reduces glitches during these/To avoid or
> reduce glitches during these/

Fixed.

> s4.5.1.1, para 1: s/For for SILK-only/For SILK-only/

Fixed.

> s4.5.1.4, para 2: s/redundant frame is as-is,/redundant frame as-is,/

Fixed.

> s5, figure 16: The Optional High-pass Filter box has two spurious '+'
> symbols on the vertical sides. 

Fixed.

> s5, last para:  A reference for the Auto Regressive Moving Average
> (ARMA) filter would be useful.

This is a simple issue and a reference to the entire theory would have made 
the issue more complicated. The parenthesis now states "i.e. with poles and 
zeros" to clarify this.

> s5.2.3.4.2.1, title: s/Burgs method/Burg's Method/

Fixed.

> s5.2.3.5, para 2: Expand 'R/D performance' (or probably specify it as
> abbreviation for rate-distortion in para 1).

Done.

> s5.3.5, para 1 below equation: Is E an abbreviation for 'extra'?

Oops. s/extra/E/ in the text below.

> s5.3.6: The abbreviation RD for rate-distortion is defined here (see
> comment on s5.2.3.5).

Fixed.

> s6.1: This section is perhaps a little 'triumphalist' for the reference
> implementation (this may of course be justified!.  The quality metric is
> a 'relative quality metric' and presumably if someone does a *really*
> good job of coding, it is entirely possible that the new algorithms
> might get better than 100 on the quality score (i.e., provide a better
> answer than the reference implementation).

Conformance with the specification is defined by a faithful reproduction of
the specified decoder behavior (see RFC 6569 s4.3). By specifying the
decoder, future encoders have the freedom to have improved quality with the
confidence that they know what output a conforming decoder will produce.

The tests in s6.1 are measuring the quality of the decoded signal against the 
reference decoded signal, not against the original audio, so greater than 100%
wouldn't be possible or meaningful. The test signals have been specially
prepared to thoroughly test a decoder implementation, and they sacrifice encoded
quality in order to rapidly exercise the corner cases.

> s6.2: Just wondering, but is non-standard frame size the only option
> offered by Opus Custom?  If not, probably more text is needed here.  Are
> there any major changes to the algorithms implied by the use of Opus
> Custom?

Opus-custom permits more flexibility for frame-sizes at a cost of limiting
the mode switching, requiring more dynamic memory, etc. The algorithm itself
remains exactly the same, though some things like the band count/layout change
to accommodate the different frame sizes while still approximating the same Bark
structure.

> s7.  Referencing SECGUIDE (RFC 3552) seems inappropriate since it occurs
> in such a security considerations section. Just omit it.

Done.

> s11.2: A number of references are to Wikipaedia pages.  While these were
> useful to me in refreshing or initializing my knowledge, they are not
> usually considered adequately stable for use in RFCs.  I fear you may
> have to provide more stable references.

In the cases where we use Wikipedia citations, they are intended as informative 
general references for introductory subject matter, and we are not relying on any
specific details or wording that would be affected by further revisions. While 
the alternatives are often dense academic papers that may not be well suited
to  a general codec implementing audience.


--Boundary_(ID_+C3bRGW2uyqqCN0LMd/yZQ)--

From john-ietf@jck.com  Wed May 16 13:03:25 2012
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 00B1921F861C for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:03:25 -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 sBSkPteevKB8 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:03:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 77ECB21F8610 for <ietf@ietf.org>; Wed, 16 May 2012 13:03:24 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SUkLp-000AaX-Sb; Wed, 16 May 2012 15:57:37 -0400
Date: Wed, 16 May 2012 16:03:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'Peter Saint-Andre' <stpeter@stpeter.im>, 'Ole Jacobsen' <ole@cisco.com>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <867B9B680EBE3644D4CCD518@PST.JCK.COM>
In-Reply-To: <097701cd3394$113cb520$33b61f60$@olddog.co.uk>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im> <097701cd3394$113cb520$33b61f60$@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: 'Sam Hartman' <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 20:03:25 -0000

--On Wednesday, May 16, 2012 19:45 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> Remind me:
> Is bold must more or less compelling that underlined must. And
> where does uppercase MUST fit in?
> 
> I fear the slightly richer publication format will give rise
> to a slightly more complex revision of RFC 2119.

Let's try to remember that many of the comments/ requests for
alternate publication formats have been to make "display" more a
function of the devices being used.  Depending on type style
variations (style, size, font variations, underlining, etc.)
would pretty much defeat that particular claimed requirement.
As I take Sam's note to sort of point out, even the use of
uppercase to imply specific semantics can be problematic; we
should at least strive to not make things worse, IMO.

    john


From randy@psg.com  Wed May 16 13:10:04 2012
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 9861E21F865B for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOiP4L3NokiD for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:10:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0E321F8655 for <ietf@ietf.org>; Wed, 16 May 2012 13:10:04 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SUkXr-000I9K-83; Wed, 16 May 2012 20:10:03 +0000
Date: Wed, 16 May 2012 10:10:02 -1000
Message-ID: <m2mx57c2g5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <4FB3EDB8.60809@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@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.6 - "Maruoka")
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, 16 May 2012 20:10:04 -0000

> Authors must be fastidious about this.

s/this/documents/

> "It may rain today" is fine

iff you are talaya

randy

From dworley@avaya.com  Wed May 16 13:12:05 2012
Return-Path: <dworley@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 205CB21F8655 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.81
X-Spam-Level: 
X-Spam-Status: No, score=-102.81 tagged_above=-999 required=5 tests=[AWL=-0.211, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sm5W6rWwiZgd for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:12:04 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 37D4421F8616 for <ietf@ietf.org>; Wed, 16 May 2012 13:12:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADQJtE/GmAcF/2dsb2JhbABEtA6BB4IVAQEBAQIBEihECwIBCA0IIRAyJQEBBBMIGodnBZ5KnQ+QBmIDnBGKKYMF
X-IronPort-AV: E=Sophos;i="4.75,605,1330923600";  d="scan'208";a="9639095"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 16 May 2012 16:12:01 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 May 2012 16:10:23 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 16 May 2012 16:12:02 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 16 May 2012 16:10:24 -0400
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Thread-Topic: RFC 2119 terms, ALL CAPS vs lower case
Thread-Index: Ac0znvmgtEX0EYejSIWrtRJ02RoOnAAAPOzA
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im> <097701cd3394$113cb520$33b61f60$@olddog.co.uk>, <867B9B680EBE3644D4CCD518@PST.JCK.COM>
In-Reply-To: <867B9B680EBE3644D4CCD518@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 20:12:05 -0000

> From: John C Klensin [john-ietf@jck.com]
>=20
> > Remind me:
> > Is bold must more or less compelling that underlined must. And
> > where does uppercase MUST fit in?
> >
> > I fear the slightly richer publication format will give rise
> > to a slightly more complex revision of RFC 2119.
>=20
> Let's try to remember that many of the comments/ requests for
> alternate publication formats have been to make "display" more a
> function of the devices being used.  Depending on type style
> variations (style, size, font variations, underlining, etc.)
> would pretty much defeat that particular claimed requirement.
> As I take Sam's note to sort of point out, even the use of
> uppercase to imply specific semantics can be problematic; we
> should at least strive to not make things worse, IMO.

I'm looking forward to the normative use of <BLINK>...</BLINK>.

Dale

From dave@cridland.net  Wed May 16 13:29:51 2012
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 6855021F8702 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sg8UGuG5ul5M for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 13:29:50 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 933B021F86FA for <ietf@ietf.org>; Wed, 16 May 2012 13:29:50 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 0947E116808F; Wed, 16 May 2012 21:29:44 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDrq8nlZClB1; Wed, 16 May 2012 21:29:40 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 868B4116808D; Wed, 16 May 2012 21:29:40 +0100 (BST)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com> <m2mx57c2g5.wl%randy@psg.com>
In-Reply-To: <m2mx57c2g5.wl%randy@psg.com>
MIME-Version: 1.0
Message-Id: <22965.1337200180.525898@puncture>
Date: Wed, 16 May 2012 21:29:40 +0100
From: Dave Cridland <dave@cridland.net>
To: Randy Bush <randy@psg.com>, IETF-Discussion <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; delsp="yes"; 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: Wed, 16 May 2012 20:29:51 -0000

On Wed May 16 21:10:02 2012, Randy Bush wrote:
> > Authors must be fastidious about this.
> 
> s/this/documents/

RFC 2119 §6 says:

   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.

I note two things:

1) RFC 2119 also uses lower-case "must" and "may" throughout.

2) RFC 2119 also clearly states that using the terms too much will  
harm interoperability.

The second is the one I feel we have violated much more, and caused  
much more damage, than any possible problem with the first.

Consider:

"An octet may contain 0-255".

This is most certainly not going to be helped if we say:

"An octet MAY contain 0-255".

We could either rephrase:

"An octet contains 0-255".

Or use a different awkward word - although up with this I will not  
put:

"An octet might contain 0-255" - or it might not?

But many requirements can be re-cast as statements of fact about  
valid protocol:

"The Foo octet MUST lie between 0 and 127 inclusive; that is, the  
highest bit MUST NOT be set."

As Pete Resnick, I think, once said, these terms are not just a stick  
to beat people with.

"A valid Foo octet lies between 0 and 127 inclusive; that is, the  
highest bit is never set."

That's just as clear, to me, and allows me to concentrate the MUST  
stick where I actually do want to stress a real problem, perhaps:

"Receivers of an invalid Foo octet - that is, one with the highest  
bit set - MUST emit the 'Invalid Foo' error, and therefore terminate  
the session immediately."

Overuse of RFC 2119 language reduces its utility.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From warren@kumari.net  Wed May 16 14:22:53 2012
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 9DCDA21F8722 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.137
X-Spam-Level: 
X-Spam-Status: No, score=-106.137 tagged_above=-999 required=5 tests=[AWL=0.462, 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 EBXJxpznKSdV for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:22:53 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 0290121F8720 for <ietf@ietf.org>; Wed, 16 May 2012 14:22:52 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 5BD301B40300; Wed, 16 May 2012 17:22:52 -0400 (EDT)
Subject: Re: [IETF] RE: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
Date: Wed, 16 May 2012 17:22:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF1213D-76DC-4666-8D09-CE38F42BC174@kumari.net>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im> <097701cd3394$113cb520$33b61f60$@olddog.co.uk>, <867B9B680EBE3644D4CCD518@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1257)
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, 16 May 2012 21:22:53 -0000

On May 16, 2012, at 4:10 PM, Worley, Dale R (Dale) wrote:

>> From: John C Klensin [john-ietf@jck.com]
>>=20
>>> Remind me:
>>> Is bold must more or less compelling that underlined must. And
>>> where does uppercase MUST fit in?
>>>=20
>>> I fear the slightly richer publication format will give rise
>>> to a slightly more complex revision of RFC 2119.
>>=20
>> Let's try to remember that many of the comments/ requests for
>> alternate publication formats have been to make "display" more a
>> function of the devices being used.  Depending on type style
>> variations (style, size, font variations, underlining, etc.)
>> would pretty much defeat that particular claimed requirement.
>> As I take Sam's note to sort of point out, even the use of
>> uppercase to imply specific semantics can be problematic; we
>> should at least strive to not make things worse, IMO.
>=20
> I'm looking forward to the normative use of <BLINK>...</BLINK>.

Errr=85 would that be more or less strong then the non-<BLINK> version =
of a word?

Initially I'd think more, but on reflection it only visible for half the =
time, so I guess it is half as strong?!  ;-)

W

>=20
> Dale
>=20


From ned+ietf@mauve.mrochek.com  Wed May 16 14:23:20 2012
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 C61CC21F8753 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 nJoDObSRLQD5 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:23:19 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 06A7521F875E for <ietf@ietf.org>; Wed, 16 May 2012 14:23:19 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFJXY26ZF4001SY3@mauve.mrochek.com> for ietf@ietf.org; Wed, 16 May 2012 14:23:15 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 16 May 2012 14:23:10 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFJXXZJB2I0006TF@mauve.mrochek.com>
Date: Wed, 16 May 2012 14:22:47 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: "Your message dated Wed, 16 May 2012 04:39:22 -1000" <m262bwchr9.wl%randy@psg.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
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, 16 May 2012 21:23:20 -0000

> >    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >    document are to be interpreted as described in [RFC2119] when they
> >    appear in ALL CAPS.  These words may also appear in this document in
> >    lower case as plain English words, absent their normative meanings.

> i like this a lot

I agree. In fact I just incorporated it into the media types registration
update.

				Ned

From rdroms.ietf@gmail.com  Wed May 16 14:26:45 2012
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 DF7A521F879E for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 PkOLx+aKE4JU for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:26:45 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE0E21F879D for <ietf@ietf.org>; Wed, 16 May 2012 14:26:45 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so1001859qcs.31 for <ietf@ietf.org>; Wed, 16 May 2012 14:26:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=fj29V1TH7Kj6qCvNdVn5JAhCGcr9/5ZwCTMb4eY8qEk=; b=nJEObE4XRxgCrdizootCNDNDQD7ZWSouNke4EHmBHZOVIw4vAMyt5N4miXY5jhHRUB G+Pg7SC1WgBSmWe2bzFB27lGlrXFpUXCOzg1bNVGEUEKp4GJyfnoABFRFddifYzeT8fK 4CPMuUmOYj5cucQVZUpYdm+eZdOdaIiqPtJJCy1W/2Ew1KAbDDNiLpprNUY6Vopz6n0N HNLOqg1WftoBt0yMMak4RRWjtA+tS4QGsxHNKndAljIlKYbGvD7bFwzfFT3VVewoESIP 3f3Lo5d7+kG4i10j1EfeZFNXE26H3PPA9R1S3AoXdGn/Y/0XE37/TW0FNFQL1zQToOTx biEQ==
Received: by 10.229.136.75 with SMTP id q11mr2231450qct.97.1337203604575; Wed, 16 May 2012 14:26:44 -0700 (PDT)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id df8sm10961493qab.6.2012.05.16.14.26.42 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 May 2012 14:26:43 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <01OFJXXZJB2I0006TF@mauve.mrochek.com>
Date: Wed, 16 May 2012 17:26:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com>
To: IETF list discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: ned+ietf@mauve.mrochek.com, Leiba Barry <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: Wed, 16 May 2012 21:26:46 -0000

On May 16, 2012, at 5:22 PM 5/16/12, ned+ietf@mauve.mrochek.com wrote:

>>>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",
>>>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this
>>>   document are to be interpreted as described in [RFC2119] when they
>>>   appear in ALL CAPS.  These words may also appear in this document =
in
>>>   lower case as plain English words, absent their normative =
meanings.
>=20
>> i like this a lot
>=20
> I agree. In fact I just incorporated it into the media types =
registration
> update.

To be sure of meaning and help confusion avoidance, I would prefer that =
the key words not appear in the document in lower case and that authors =
use the suggested replacement words (or break out the thesaurus?).

- Ralph

>=20
> 				Ned


From dhc@dcrocker.net  Wed May 16 14:54:45 2012
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 C4D179E8021 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:54:45 -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 AWLaVcUZ-lGg for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:54:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 256D221F8627 for <ietf@ietf.org>; Wed, 16 May 2012 14:54:43 -0700 (PDT)
Received: from [21.253.71.205] (mea2736d0.tmodns.net [208.54.39.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4GLscMJ028080 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 16 May 2012 14:54:40 -0700
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im>
User-Agent: K-9 Mail for Android
In-Reply-To: <4FB3F54F.2030705@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Dave Crocker <dhc@dcrocker.net>
Date: Wed, 16 May 2012 14:54:36 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>, Ole Jacobsen <ole@cisco.com>
Message-ID: <40f08a1c-7ea0-43db-99d8-9865fa1cfd4c@email.android.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 16 May 2012 14:54:41 -0700 (PDT)
Cc: adrian@olddog.co.uk, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 21:54:46 -0000

+1

and for the current thread, case is format...

Peter Saint-Andre <stpeter@stpeter.im> wrote:

>On 5/16/12 12:26 PM, Ole Jacobsen wrote:
>> 
>> And of course if we had a slightly richer publication format we could
>
>> use, oh, say, underline, bold, italics and maybe even a special font 
>> for normative terms, but I guess I am dreaming decades ahead...
>
>Although I too dream the impossible dream, I would prefer not to trust
>in formatting to enforce the semantic distinction in this instance.
>
>Peter


/d
--
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

 via mobile

From jaap@NLnetLabs.nl  Wed May 16 15:03:09 2012
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 9142621F85B1 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 15:03: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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4wwgzW6pkY3 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 15:03:09 -0700 (PDT)
Received: from bartok.nlnetlabs.nl (bartok.nlnetlabs.nl [IPv6:2001:7b8:206:1:216:76ff:feb8:3c02]) by ietfa.amsl.com (Postfix) with ESMTP id ADF0321F85A5 for <ietf@ietf.org>; Wed, 16 May 2012 15:03:08 -0700 (PDT)
Received: from NLnetLabs.nl (localhost [127.0.0.1]) by bartok.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id q4GM1kdv071395; Thu, 17 May 2012 00:01:46 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 bartok.nlnetlabs.nl q4GM1kdv071395
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=sleutel; t=1337205707; bh=irTn0jbvwQgrpkOcn9A9+l+gEpocxQBFCCe3lnXk3PI=; h=To:cc:Subject:In-reply-to:References:Date:From; b=NA+0A8OBv9OUzJovOVT1lshjscNQ06YbeJ0h3NekpVIhBDe0qE83ktAMQWI5t3NMp B1t10CxzFgGPXvKhVMEEcQgJWXPisFwKq7asHe5SyHviC6EEoxKrdcEOhat2qQBZC4 q5QoEanC2BlFreiVZDNC7JUK1jOTAD7h5t9nOtZw=
Message-Id: <201205162201.q4GM1kdv071395@bartok.nlnetlabs.nl>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im> <097701cd3394$113cb520$33b61f60$@olddog.co.uk>, <867B9B680EBE3644D4CCD518@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
Comments: In-reply-to "Worley, Dale R (Dale)" <dworley@avaya.com> message dated "Wed, 16 May 2012 16:10:24 -0400."
Date: Thu, 17 May 2012 00:01:46 +0200
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bartok.nlnetlabs.nl [127.0.0.1]); Thu, 17 May 2012 00:01:47 +0200 (CEST)
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, 16 May 2012 22:03:09 -0000

    
    I'm looking forward to the normative use of <BLINK>...</BLINK>.

Proper use should be <NORMATIVE>....</NORMATIVE>, how that is revealed to
the user is decided by the display system.

	jaap

From hsantos@isdg.net  Wed May 16 16:00:03 2012
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 E9F2011E8086 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 16:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level: 
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[AWL=0.649,  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 Q1SS1HvLfVQ5 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 16:00:03 -0700 (PDT)
Received: from mail.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB8111E8085 for <ietf@ietf.org>; Wed, 16 May 2012 16:00:02 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2052; t=1337209201; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=/V1HM82Q20EGGwb+gZRPJzPqOtI=; b=WNeLjtYda+eYnD3U5a1y ujvBV+iLRzukS3AEMiq9AR+nZXs4xCAI0ZgW3cvU0w5ja51l9h0dZkXty8SyQX9F YmXLDss3jx7GJEEj/FXycIZXRSzsAqIss0PNuWbuymzBxbQt8r8kmi2w1MQY6c15 jxmbZQ/ro0YXe7ZtGbYbXxI=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 19:00:01 -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 v6.4.454.1) with ESMTP id 1821028677.90.5388; Wed, 16 May 2012 19:00:00 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2052; t=1337209179; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Qdfnu0w GuwZg7FuojuCXh1D7e63od7Pv2ouHwIcMQkc=; b=iik4qeygPR5RL9TfdTxgs8w rDv0hESj7Rsd1XaVuQQjh7hA5TLaSC3TVmgV7+YoZaEzeSxDiqkoGFGTb3jiypw3 453qAiR91Bl8iRV4sV19j8DmCTm6GjIbcwMTvcBhzRNkEy2QQIWkItVJMw4E3Klf HbAxeA+RAjB9aTJ628g0=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 16 May 2012 18:59:39 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2419911847.7642.2832; Wed, 16 May 2012 18:59:38 -0400
Message-ID: <4FB4317C.3000900@isdg.net>
Date: Wed, 16 May 2012 19:00:12 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk>	<tslaa18w21n.fsf@mit.edu>	<4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com>
In-Reply-To: <4FB3EDB8.60809@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 23:00:04 -0000

+1

My view that this is more about the specific issues of documents and 
not just RFC2119 itself.  Sometimes it falls through the cracks. 
Sometimes a justification or argument is found to show the contrary of 
what is stated, especially when its uses lower cases or even terms 
like "choose."  Sometimes its just new conflicts of integrated 
documents where perhaps an augmented RFC attempts to reinforce what 
the base RFC may have lacked.

In my view, it will help if future I-D and RFC authors begin to have 
one new section called in chapter 1.0

   1.x - Minimum Compliancy Requirement Summary

Far too often documents have mixed functional and technical 
specifications, mixed normative and non-normative compliance semantics 
too spread out and peppered throughout the document making it harder 
to catch compliance level issues.

-- 
HLS


Brian E Carpenter wrote:
> On 2012-05-16 18:53, Peter Saint-Andre wrote:
>> On 5/16/12 9:58 AM, Sam Hartman wrote:
> 
> ...
>>> I'll note that  in my normal reading mode I  do not distinguish case,
>>> but even so I find the ability to use may and should in RFC text without
>>> the 2119 implications valuable.
> 
> Agreed. But as a gen-art reviewer, I have several times had to ask
> authors whether a particular lower case "may" was intended to be normative
> or normal English. Authors must be fastidious about this.
> 
>> Your mileage may (or is that MAY?) vary, but to forestall confusion I've
>> settled on the practice of using "can" and "might" instead of lowercase
>> "may", "ought to" and "is suggested to" instead of lowercase "should",
>> and "needs to" or "has to" instead of lowercase "must" (etc.). I'm not
>> saying that anyone else SHOULD or MUST use that convention, but you
>> might consider it in your own spec-writing.
> 
> It is indeed very important not to use "may" when it's ambiguous.
> "It may rain today" is fine; "you may leave now" is not (I can think
> of three different meanings). In RFC2119-talk, "you MAY leave now"
> only has one meaning.




From ned+ietf@mauve.mrochek.com  Wed May 16 19:24:04 2012
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 CB89E21F85F6 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 19:24: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=[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 7AixJnH4c8SF for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 19:24:04 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B17A221F85F4 for <ietf@ietf.org>; Wed, 16 May 2012 19:24:03 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFK8GRC5Y8000OIW@mauve.mrochek.com> for ietf@ietf.org; Wed, 16 May 2012 19:23:52 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 16 May 2012 19:23:46 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFK8GNXASC0006TF@mauve.mrochek.com>
Date: Wed, 16 May 2012 19:22:42 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: "Your message dated Wed, 16 May 2012 17:26:40 -0400" <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Cc: ned+ietf@mauve.mrochek.com, Leiba Barry <barryleiba@computer.org>, IETF list 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 May 2012 02:24:04 -0000

> On May 16, 2012, at 5:22 PM 5/16/12, ned+ietf@mauve.mrochek.com wrote:

> >>>   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >>>   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >>>   document are to be interpreted as described in [RFC2119] when they
> >>>   appear in ALL CAPS.  These words may also appear in this document in
> >>>   lower case as plain English words, absent their normative meanings.
> >
> >> i like this a lot
> >
> > I agree. In fact I just incorporated it into the media types registration
> > update.

> To be sure of meaning and help confusion avoidance, I would prefer that the
> key words not appear in the document in lower case and that authors use the
> suggested replacement words (or break out the thesaurus?).

Preferring it is one thing; I'm OK with that. Making it some sort of
hard-and-fast rule is another matter entirely. We have too many of those
as it is.

				Ned

From stpeter@stpeter.im  Wed May 16 20:25:33 2012
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 787EC11E809F; Wed, 16 May 2012 20:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yi41x+TK7DaX; Wed, 16 May 2012 20:25:31 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2837111E809C; Wed, 16 May 2012 20:25:31 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.175.160]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C63A24005A; Wed, 16 May 2012 21:41:15 -0600 (MDT)
Message-ID: <4FB46FA6.6060005@stpeter.im>
Date: Wed, 16 May 2012 21:25:26 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [mile] Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining	Extensions to IODEF) to Informational RFC
References: <20120516215321.9671.39664.idtracker@ietfa.amsl.com>
In-Reply-To: <20120516215321.9671.39664.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: mile@ietf.org, The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 03:25:33 -0000

On 5/16/12 3:53 PM, The IESG wrote:
> 
> The IESG has received a request from the Managed Incident Lightweight
> Exchange WG (mile) to consider the following document:
> - 'Guidelines for Defining Extensions to IODEF'
>   <draft-ietf-mile-template-04.txt> as Informational RFC

Although this document does no harm, I have my doubts that the topic
warrants publication of an RFC (and I say that as someone who is
defining some IODEF extensions for use on the XMPP network [1]). Why
would a simple wiki page [2] not suffice?

If we decide than an RFC is needed, I have some more actionable feedback...

1. The document could be construed as assuming that IODEF extensions
will all be defined in Internet-Drafts, that extension namespaces will
be registered with IANA, and even that namespaces will be of the form
'urn:ietf:params:xml:schema:iodef-*'. It might be helpful to clarify the
intended applicability of this document, i.e., merely as helpful
suggestions for authors of Internet-Drafts, not truly as universally
applicable guidelines for defining IODEF extensions.

2. Why is RFC 6545 a normative reference?

3. Given the many comments provided by Martin DÃ¼rst, mentioning his
AppsDir review in the Acknowledgements seems appropriate.

4. Some of the text in the appendix seems needlessly detailed (e.g.,
saying that each extension needs to be specified in a subsection, or the
recommendation to include a UML diagram).

5. Why is the list of datatypes in appendix A.4.1 copied from RFC 5070?
A simple reference would do. (I almost said the same about the list in
Section 3, but that one is marginally useful.)

6. Some of the information in this document repeats information from the
RFC style guide and other sources; why?

Peter

[1] http://xmpp.org/extensions/xep-0268.html

[2] http://trac.tools.ietf.org/wg/mile/trac/wiki


From dougb@dougbarton.us  Wed May 16 23:18:38 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D644A11E8081 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 23:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.995
X-Spam-Level: 
X-Spam-Status: No, score=-2.995 tagged_above=-999 required=5 tests=[AWL=0.604,  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 pHNqJOFxXCjV for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 23:18:38 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2280111E8076 for <ietf@ietf.org>; Wed, 16 May 2012 23:18:37 -0700 (PDT)
Received: (qmail 25594 invoked by uid 399); 17 May 2012 06:18:34 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 17 May 2012 06:18:34 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4FB49838.6050300@dougbarton.us>
Date: Wed, 16 May 2012 23:18:32 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
X-Enigmail-Version: 1.5pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
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, 17 May 2012 06:18:39 -0000

On 05/16/2012 06:59, Barry Leiba wrote:
> In fact, RFC 2119 says that the normative keywords are "often
> capitalized", but doesn't require that they be.

Standards should be written in such a way as to remove as much ambiguity
as possible, not show how clever we are. That allowance in 2119 was a
mistake, and the fact that people remain confused 15 years later is
clear evidence of that.

Normative use of the 2119 key words should always be capitalized.

And yes, "can" is about ability, "may" is about permission. Choosing to
add to the confusion about the simple English meaning of those words
doesn't make us look any more clever.

Doug

-- 
    If you're never wrong, you're not trying hard enough

From sm@resistor.net  Thu May 17 00:35:53 2012
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 8799B21F85E1 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 00:35:53 -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 mOnbDBq4wD2V for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 00:35: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 5F35121F85DD for <ietf@ietf.org>; Thu, 17 May 2012 00:35: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 q4H7Zj9s027522 for <ietf@ietf.org>; Thu, 17 May 2012 00:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1337240150; i=@resistor.net; bh=hRcCkwouDpFsoe73J3v5S9S2JBRpHlm3YQ+C1slo4jY=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=w6NklT4FLe2JP8Bpp3AMpbw2UHKM7vK/+NsHJUKprqcYykyeF8oQyVp/VdxakgTx4 1Udnf9rYm6QQeGwZuJUm5MgJK2q4DGHPNky/FfeTqwHHDpMfdkoahpQa6YUU/Tb31b rp1z7uPAgnUB56LO/YnnmTBGfn2z82eoIk8LL2JE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1337240150; i=@resistor.net; bh=hRcCkwouDpFsoe73J3v5S9S2JBRpHlm3YQ+C1slo4jY=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Wi+VgMmAh2cknbievAnk/SoQZ01T0utQ0LLvGsGdUEj5V9oIevTiP9qc/IS9wWHzn A3LLxr/b1P3KV/jgFsKsYxhnC4ks0yr9n8n1KwK+zZ0sDP3B43PjraT/b2grglku8y yDNVj4r8j/87LpSgDAqkRvIbuEoULGvVTp+fHp+M=
Message-Id: <6.2.5.6.2.20120516232523.0a7d9a60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 May 2012 23:50:23 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining Extensions to IODEF) to Informational RFC
In-Reply-To: <20120516215321.9671.39664.idtracker@ietfa.amsl.com>
References: <20120516215321.9671.39664.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: Thu, 17 May 2012 07:35:53 -0000

At 14:53 16-05-2012, The IESG wrote:
>The IESG has received a request from the Managed Incident Lightweight
>Exchange WG (mile) to consider the following document:
>- 'Guidelines for Defining Extensions to IODEF'
>   <draft-ietf-mile-template-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 2012-05-30. Exceptionally, comments may be

The Abstract mentions that this draft contains a template for 
[writing] Internet-Drafts describing [extensions to IODEF].  Why is a 
RFC needed for a template to write I-Ds?  It seems like the WG is 
encouraging future authors to copy and paste the text and generate new RFCs.

Regards,
-sm 


From daedulus@btconnect.com  Thu May 17 01:14:06 2012
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 DED4C21F85DF for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 01:14:05 -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 KVjS8AEtus8Z for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 01:14:04 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe004.messaging.microsoft.com [213.199.154.142]) by ietfa.amsl.com (Postfix) with ESMTP id D0AF821F85E1 for <ietf@ietf.org>; Thu, 17 May 2012 01:14:02 -0700 (PDT)
Received: from mail54-db3-R.bigfish.com (10.3.81.237) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Thu, 17 May 2012 08:13:53 +0000
Received: from mail54-db3 (localhost [127.0.0.1])	by mail54-db3-R.bigfish.com (Postfix) with ESMTP id D61B616065E; Thu, 17 May 2012 08:13:53 +0000 (UTC)
X-SpamScore: -32
X-BigFish: PS-32(zzbb2dI9371I542M1432N98dKzz1202hzz1033IL8275dhz2dh2a8h5a9h668h839hd24h304l)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT010.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail54-db3 (localhost.localdomain [127.0.0.1]) by mail54-db3 (MessageSwitch) id 1337242431941085_16281; Thu, 17 May 2012 08:13:51 +0000 (UTC)
Received: from DB3EHSMHS019.bigfish.com (unknown [10.3.81.228])	by mail54-db3.bigfish.com (Postfix) with ESMTP id DFAA41E035E; Thu, 17 May 2012 08:13:51 +0000 (UTC)
Received: from DB3PRD0702HT010.eurprd07.prod.outlook.com (157.55.224.141) by DB3EHSMHS019.bigfish.com (10.3.87.119) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 17 May 2012 08:13:51 +0000
Received: from BL2PRD0410HT005.namprd04.prod.outlook.com (157.56.240.85) by pod51017.outlook.com (10.3.4.178) with Microsoft SMTP Server (TLS) id 14.15.74.2; Thu, 17 May 2012 08:13:56 +0000
Message-ID: <004401cd3404$a2c2c780$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Doug Barton <dougb@dougbarton.us>, <ietf@ietf.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB49838.6050300@dougbarton.us>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Date: Thu, 17 May 2012 09:11:09 +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.240.85]
X-OriginatorOrg: btconnect.com
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, 17 May 2012 08:14:06 -0000

----- Original Message -----
From: "Doug Barton" <dougb@dougbarton.us>
To: <ietf@ietf.org>
Cc: "Barry Leiba" <barryleiba@computer.org>
Sent: Thursday, May 17, 2012 7:18 AM
> On 05/16/2012 06:59, Barry Leiba wrote:
> > In fact, RFC 2119 says that the normative keywords are "often
> > capitalized", but doesn't require that they be.
>
> Standards should be written in such a way as to remove as much
ambiguity
> as possible, not show how clever we are. That allowance in 2119 was a
> mistake, and the fact that people remain confused 15 years later is
> clear evidence of that.
>
> Normative use of the 2119 key words should always be capitalized.
>
> And yes, "can" is about ability, "may" is about permission. Choosing
to
> add to the confusion about the simple English meaning of those words
> doesn't make us look any more clever.

Yes, normative use should be capitalised and non-normative use should be
avoided, but there is also a distinction to be drawn between MAY and the
others.  Frequently, at or around WG Last Call, the question arises as
to the meaning of MAY, the conclusion often being that it is
meaningless; this MAY or MAY NOT be the case, so who cares, why bother?

MUST and SHOULD are quite different, they do have a force to them and
they are distinct.  SO while I would not comment on the use of 'may', I
would comment on the use of 'should' or 'must'; the latter confuse, the
former, who cares?

Tom Petch

>
> Doug
>
> --
>     If you're never wrong, you're not trying hard enough
>



From fanf2@hermes.cam.ac.uk  Thu May 17 03:54:09 2012
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 475A821F85E1 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.229
X-Spam-Level: 
X-Spam-Status: No, score=-5.229 tagged_above=-999 required=5 tests=[AWL=-1.230, 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 YL1bSbMSTon5 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:54:08 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB2921F85D9 for <ietf@ietf.org>; Thu, 17 May 2012 03:54:07 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:36584) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1SUyLO-000700-r2 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:54:06 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1SUyLO-0002VF-Cu (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:54:06 +0100
Date: Thu, 17 May 2012 11:54:06 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <20120516145655.GH26714@mail.yitter.info>
Message-ID: <alpine.LSU.2.00.1205171142220.32614@hermes-2.csi.cam.ac.uk>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1870870024-1741023179-1337252046=:32614"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
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 May 2012 10:54:09 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870870024-1741023179-1337252046=:32614
Content-Type: TEXT/PLAIN; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> On Wed, May 16, 2012 at 07:17:04AM -0700, Dave Crocker wrote:
> > Case does not define meaning in normal language, why should it here?
>
> That is false.  Consider these two passages:
>
>     The King asked the Queen,
>     and the Queen asked the dairy-maid =E2=80=A6
>
> vs
>
>     The king asked the queen,
>     and the queen asked the dairy-maid=E2=80=A6

I really can't tell any difference between the two. The capitalization
here is just a conventional mark of respect (cf. God). Better examples:

Polish / polish
"I helped my uncle Jack off a horse"
Catholic / catholic
Conservative / conservative

In the latter two cases you often get disambiguating circumlocutions (such
as "conservative with a small c" in British political discussion) so even
if you can use case to make a distinction in meaning, it's usually too
subtle to rely on if you want to avoid "amusing" misinterpretations.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Humber, Thames: South or southwest 3 or 4, backing east 4 or 5 later. Sligh=
t
or moderate. Mainly fair. Mainly good.
--1870870024-1741023179-1337252046=:32614--

From fanf2@hermes.cam.ac.uk  Thu May 17 03:56:34 2012
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 10FDA21F8609 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.491
X-Spam-Level: 
X-Spam-Status: No, score=-6.491 tagged_above=-999 required=5 tests=[AWL=0.108,  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 SS9fg6CPaW4i for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:56:33 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 82AAC21F85F7 for <ietf@ietf.org>; Thu, 17 May 2012 03:56:33 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:56426) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1SUyNj-0008IV-rI (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:56:31 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1SUyNj-0002yS-FS (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:56:31 +0100
Date: Thu, 17 May 2012 11:56:31 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Randy Bush <randy@psg.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <m2boloci9k.wl%randy@psg.com>
Message-ID: <alpine.LSU.2.00.1205171155200.32614@hermes-2.csi.cam.ac.uk>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m2boloci9k.wl%randy@psg.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: 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: Thu, 17 May 2012 10:56:34 -0000

Randy Bush <randy@psg.com> wrote:

> can != may
>
> one is ability, the other permission

Right, and if you are giving some entity permission to do something in a
protocol spec, surely that ought to be written in normative terms.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
FitzRoy: Cyclonic at times in far north, otherwise mainly westerly or
northwesterly 5 to 7, occasionally gale 8 in southeast at first, decreasing 4
or 5 later. Moderate or rough. Showers. Good.

From julian.reschke@gmx.de  Thu May 17 07:00:59 2012
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 6BD1221F86BB for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 07:00:59 -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 PYOed6sB9txM for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 07:00:59 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7AF1D21F86B3 for <ietf@ietf.org>; Thu, 17 May 2012 07:00:58 -0700 (PDT)
Received: (qmail invoked by alias); 17 May 2012 14:00:57 -0000
Received: from p54BB26EE.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.38.238] by mail.gmx.net (mp040) with SMTP; 17 May 2012 16:00:57 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18VxPJsDMQVsDL/0cnHZqCXvwGyGvhRSq7Y0VLnVa RYKICJkK1Ap3dF
Message-ID: <4FB50486.2@gmx.de>
Date: Thu, 17 May 2012 16:00:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com> <m2mx57c2g5.wl%randy@psg.com> <22965.1337200180.525898@puncture>
In-Reply-To: <22965.1337200180.525898@puncture>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 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: Thu, 17 May 2012 14:00:59 -0000

On 2012-05-16 22:29, Dave Cridland wrote:
> On Wed May 16 21:10:02 2012, Randy Bush wrote:
>> > Authors must be fastidious about this.
>>
>> s/this/documents/
>
> RFC 2119 §6 says:
>
> 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.
>
> I note two things:
>
> 1) RFC 2119 also uses lower-case "must" and "may" throughout.
>
> 2) RFC 2119 also clearly states that using the terms too much will harm
> interoperability.
>
> The second is the one I feel we have violated much more, and caused much
> more damage, than any possible problem with the first.
> ...

+100

From fluffy@cisco.com  Thu May 17 09:07:48 2012
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 333A821F857D; Thu, 17 May 2012 09:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.046
X-Spam-Level: 
X-Spam-Status: No, score=-110.046 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 TK+FQYnzJvDI; Thu, 17 May 2012 09:07:44 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id E483F21F856F; Thu, 17 May 2012 09:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=15303; q=dns/txt; s=iport; t=1337270864; x=1338480464; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=+7VXU0/Uqjw0HmjEr8WbvfXDskmVmkLnY7AOJGlYICQ=; b=Oxjq+HzUXKRghpaaHKf6pMU2GMqGcCDzeBjICW6Cftmmv94oOQz6vra2 KrM9i77fw0hGHk8hs7aaDdsXMSR1es9GyBJbho5IznU4hUrWJpFQWLmRH lHeCmWejIn5BqqkZFRK5BvmTWClNjhuCkIAEiC6V7J+rODeHwNqdxSU9t E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjcFANohtU+rRDoJ/2dsb2JhbABEgx2wIIEHghUBAQECAQESARQTOgUFCwsYLlcGHAsHB4dnBAybZ6AGixMTAYRhYgOIY40XgRGEZIhigWmDCIE3AQ
X-IronPort-AV: E=Sophos;i="4.75,610,1330905600"; d="scan'208";a="45193506"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 17 May 2012 16:07:37 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q4HG7a6o025259; Thu, 17 May 2012 16:07:36 GMT
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
Date: Thu, 17 May 2012 10:07:36 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D6B36EF-C4B4-4C65-AA07-6C6A59725291@cisco.com>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca> <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
To: Elwyn Davies <elwynd@folly.org.uk>
X-Mailer: Apple Mail (2.1084)
Cc: codec@ietf.org, Jean-Marc Valin <jmvalin@jmvalin.ca>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.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, 17 May 2012 16:07:48 -0000

I think the authors just about have a -14 draft ready but I wanted to =
comment on one topic inline ....


On May 16, 2012, at 3:26 PM, Elwyn Davies wrote:

> Hi, Jean-Marc.
>=20
> ... and thanks for the super-quick response!  You have been quite =
busy.
>=20
> I have had a look through the new draft and I think the additions help
> considerably with comprehension for the naive (and to give new
> implementers a way in.)
>=20
> I'll leave you to negotiate with the RFC Editor over the Wikipaedia
> references.  To quote the RFC Style guide
> http://www.rfc-editor.org/rfc-style-guide/rfc-style
> Section 4.8, item (x) References, last section:
>> URLs and DNS names in RFCs
>>=20
>>      The use of URLs in RFCs is discouraged, because many URLs are =
not
>>      stable references.  Exceptions may be made for normative
>>      references in those cases where the URL is demonstrably the most
>>      stable reference available.  References to long-lived files on
>>      ietf.org and rfc-editor.org are generally acceptable.
> They are certainly convenient *as long as they remain in place and
> aren't corrupted*.
>=20
> I found a couple of trivial editorial nits in the changes:
> s4.3.3 (in the added text):
>> The CELT layer, however, can adapt over a very wide range of rates,
>> and thus has a large number of codebooks sizes
> s/codebooks/codebook/
>=20
> s4.3.3, para after Table 57: s?the maximums in bit/sample are
> precomputed?the maximums in bits/sample are precomputed?
>=20
> Also suggest:
> s4.3: Add reference for Bark scale: Zwicker, E. (1961), "Subdivision =
of
> the audible frequency range into critical bands," The Journal of the
> Acoustical Society of America, 33, Feb., 1961.
>=20
> A few responses in line below (agreed pieces elided):=20
>=20
> Regards,
> Elwyn  Davies
> =
=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> On Tue, 2012-05-15 at 20:33 -0400, Jean-Marc Valin wrote:
>> Hi Elwyn,
>>=20
>> Thanks for the very thorough review. We've addressed your issues and
>> submitted draft version -13. See our response to each of the issues =
you
>> raised (aggregated from all the authors) in the attached document.
>=20
> Thanks very much to all the authors.
>>=20
>> Cheers,
>>=20
>> 	Jean-Marc
>>=20
>=20
>=20
>> Elwyn Davies wrote:
>>> Major issues:=20
>>> Can we accept the code as normative?  If not how do we proceed?
>>=20
>> The issue with code being normative was specifically addressed in=20
>> the guidelines document for this WG (RFC 6569).
>>=20
> Yes.  I failed to read this although Robert Sparks did point out to me
> that the code was normative - but he didn't think he said this was
> agreed in advance (or maybe I didn't understand what he was saying).
>=20
> To be honest I would like to have had the time to tie the text to the
> code but realistically that is several weeks or even months work to do
> it properly - without that I feel that I have only done half a job. I
> may decide that it interests me enough to have a superficial go next
> week but no promises!
>=20
>>=20
>>> Minor issues:
>>> Contrast between decoder descriptions of LP part and CELT part:  The
>>> SILK descriptions go into gory detail on the values used in lots of
>>> tables, etc., whereas the CELT part has a very limited treatment of
>> the
>>> numeric values used (assuming reliance on finding the values in the
>>> reference implementation, either explictly or implicitly).  There
>> are
>>> things to be said for both techniques.  I was wondering (while
>> reading
>>> the SILK description) if the authors have any means of automatically
>>> generating the tables from the code in the SILK part (or vice versa)
>> to
>>> avoid double maintenance. On the other hand, there are pieces of the
>>> CELT decoder description (especially in s4.3.3 where knowing numbers
>> of
>>> bands, etc.) where some actual numbers would help comprehension.
>>>=20
>>=20
>> We have made many changes to section 4.3 (and 4.3.3 specifically) to
>> address
>> the specific issues below. As for the tables, they are not generated
>> automatically.
>=20
> I think this is addressed satisfactorily now.  There is still some
> difference but it is much reduced and not so glaring now. The addition
> of the band tables really helps.
>=20
>>=20
>>=20
>>> s2 (and more generally):  The splitting of the signal in the
>> frequency
>>> domain into signal (components?) below and above 8kHz presumably
>>> requires that the signal is subjected to a Discrete Fourier
>> Transform to
>>> allow the signal to be split.  I think sometging is needed in s2 to
>>> explain how this is managed (or if I don't understand, to explain
>> why it
>>> isn't necessary).
>>=20
>> No DFT is used. The lower band is obtained through resampling (which
>> is already described) and the higher band is obtained by not coding
>> the lower band with CELT (the text says that CELT starts at band 17 =
in
>> hybrid mode). The explanation was reworded to make this as clear as
>> possible at this point in the text.
>=20
> [I thought I had reworded this comment in the 2nd version to talk =
about
> MDCT but no matter].=20
> Yes, para 5 of s2 does say that the bands are discarded.  I think it
> would useful to have a concrete statement in the new text added to =
s4.3
> that bands 0 to 16 are discarded in hybrid mode (thereby making the 17
> in the band boost section more obvious) [There is a comment below that
> you have added some text about band 17 in section 4.3 but I can't see
> it].
>=20
>=20
>>=20
>>> s4.2.5, para 3:
>>>>    When switching from 20 ms to 10 ms, the 10 ms
>>>>    20 ms Opus frame, potentially leaving a hole that needs to be
>>>>    concealed from even a single packet loss.
>>> How?
>>=20
>> As explained in the LBRR text, a 10 ms frame will only contain 10 ms
>> LBRR data even if the previous frame was 20 ms, so there's 10 ms
>> "missing".
> Indeed - that there would be a hole was clear.  The 'How' referred to
> how would it be concealed.  Having read further by now this may be =
down
> to Packet Loss Concealment - so maybe all it needs is a foward ref to
> s4.4.=20
>>=20
>>> s4.3:
>>> As a complete newcomer to CELT, I would have appreciated a more high
>>> level understanding of what CELT is doing at this point.  I  tried
>>> reading s4.3 without any additional input and found it very hard
>> going.
>>> Eventually I gave up and went looking for some additional input.
>> This
>>> presentation seems to have a useful view=20
>>> http://www.ietf.org/proceedings/79/slides/codec-2.pdf
>>> I think that it would be extremely helpful to have a description
>> similar
>>> to this at this point in the document, even though there is some
>>> material in section 5.3 which could also be forward referenced.
>> Still
>>> the material in s5.3 does not start from the basic principles that
>> CELT
>>> is using, and since these are essentially novel, it would be very
>> good
>>> to give prospective implementers/users an understanding of what is
>> going
>>> on.  Incidentally, I found the above IETF presentation more useful
>> than
>>> http://www.celt-codec.org/presentations/misc/lca-celt.pdf
>>> Note that the SILK part seems rather less opaque.  It would also be
>>> useful to indicate numerically how many bands are involved and what
>> the
>>> number of MDCT bins are in the various bands.=20
>>=20
>> The intro of section 4.3 has been expanded with general information
>> about CELT
>> similar to what the codec-2.pdf slides from 79 included.=20
>>=20
> I think this is an excellent improvement.
>>=20
>>> Nits/editorial comments:
>>>=20
>>> global: bytes ->  octets
>>=20
>> We believe that in the field of audio codecs, the mention of "byte"
>> without
>> further context is well understood to mean 8 bits.
>=20
> True. But this is a matter of IETF style.  The style is to use octets
> where we mean 8 bit bytes. I think you now have a mixture!


This topic has generated more phone calls and discussion for me than all =
the rest of your review comments put together :-)=20

The use of the term "byte" does not seem to have caused any confusion or =
issues in either the spec writing or in the implementations and it is =
the term generally used by the community to refer to a group of 8 bits - =
so folks would like to stay with that. If the IESG wants to put  a =
discuss on this, preferable with a pointer to the relevant section of =
the discuss criteria document, we can deal with that then. If using =
octet is the IESG's desire, the document can easily be moved to use =
octet and my belief is that implementors, thought finding that sort of =
weird , will not have implementation or interoperability problems from =
that change.=20

Thanks, Cullen <CODEC WG Co-Chair>


>=20
>>=20
>>> global: The form/terminology Q<n>  (e.g., Q13, Q15, Q16) ought to be
>>> explained.
>>=20
>> This was already defined in the section on notation:
>>   The notation "Q<n>", where n
>>   is an integer, denotes the number of binary digits to the right of
>>   the decimal point in a fixed-point number.
> Sorry - I missed that.
>>=20
>>> s3.4: I am not keen on duplicating normative requirements in this
>> way
>>> (double maintenance issue).  It would be better to put explicit
>> numbered
>>> requirements in the sections above an reference the resulting
>> numbers
>>> here.
>>=20
>> A checklist style summary is quite useful for implementors, and worth
>> the maintenance burden for a document that is (hopefully) going to be
>> published once and read many times. The list intentionally does not
>> include any RFC 2119 keywords, to avoid any conflict should there
>> (accidentally) be room to interpret the re-statement any differently
>> from the original statement. Numbering the requirements and
>> referencing the numbers is still a good idea, but it should be
>> possible to read the list without flipping back and forth to the
>> previous sections.
>=20
> Good solution!
>=20
>>=20
>>> s4.1.1:  This is really a global point.  This section refers to
>>> entdec.c.  Presumably (since we haven't reached the code yet) and it
>> is
>>> still compressed, there is some file structure.  I don't think this
>> has
>>> been said above.  It would be good to provide a list of the file
>>> components (i.e., sectional structure of the code) at the start,
>> maybe
>>> even  giving line number positions within the decompressed code.
>>=20
>> In cases where it was deemed necessary (e.g. large functions), there
>> are
>> indeed line numbers in references to the code. As for a list of files
>> we did not think it was useful because one already needs to =
decompress
>> the code to see the references.
>=20
> OK. We'll have to live with this situation.
>=20
> Having looked at the code, I think it is a considerable pity that it
> isn't Doxygen commented (or some such) throughout so that the whole
> system can be viewed as a Doxygen tree. I can smell roasted programmer
> from here... :-)
>>=20
>>> s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
>>>    selects the PDFs for the second stage of the VQ/This indexes an
>>>    element in a coarse codebook that selects the PDFs for the
>> second stage
>>>    of the VQ/
>>=20
>> The text as written is correct. The index I1 is what selects the PDFs
>> for the second stage, not the vector from the coarse codebook in
>> Tables 23 and 24. I.e., it's saying, "This does A, B, and C."
>=20
> OK.  I think it might be clearer if the three things were separated =
out
> as a list.  Now you point it out I can read it correctly but it
> triggered minor confusion - worth turning the three things into bullet
> points.
>=20
> NEW:  s4.3: Add reference for Bark scale: Zwicker, E. (1961),
> "Subdivision of the audible frequency range into critical bands," The
> Journal of the Acoustical Society of America, 33, Feb., 1961.
>=20
> Generally the new intro to s4.3 helps *a lot*.
>>> s4.3.2.1: Avoid the equation picture splitting across page
>> boundaries.
>>> in the current version it is unclear what the denominator is. (use
>>> needLines processing direcrive in xml2rfc).  Same applies to the
>>> equation below Table 57 in s4.3.4.3.
>>=20
>> It's not quite clear how to use needLines without undesirable
>> side-effects.
>> Hopefully this is something the RFC editor should be able to handle.
> Indeed.. but I don't know what undesirable side effects there are?
> AFAIK (and in my own usage) it just ensures there are n lines =
available
> on the current page at some point in the text and forces a page throw =
if
> not.
>>=20
>>=20
>>> s4.3.3: (was specified as s 4.3.2.3 whcj was wrong) Paragraph on
>> decoding band boosts:  Might be improved by using
>>> equations rather than the wordy descriptions used at present.
>=20
> Any thoughts on this one
>>>=20
>>> (global)s4.3.2.3, para above table 56: s/iff/if and only if/
>>=20
>> Fixed.
>>=20
>>=20
>>> s4.3.3: <<snip>>.
>>=20
>> Added an explanation of band 17=20
>=20
> I don't think this happened.
>=20
>>=20
>>=20
>>> s6.1: This section is perhaps a little 'triumphalist' for the
>> reference
>>> implementation (this may of course be justified!.  The quality
>> metric is
>>> a 'relative quality metric' and presumably if someone does a
>> *really*
>>> good job of coding, it is entirely possible that the new algorithms
>>> might get better than 100 on the quality score (i.e., provide a
>> better
>>> answer than the reference implementation).
>>=20
>> Conformance with the specification is defined by a faithful
>> reproduction of
>> the specified decoder behavior (see RFC 6569 s4.3). By specifying the
>> decoder, future encoders have the freedom to have improved quality
>> with the
>> confidence that they know what output a conforming decoder will
>> produce.
>>=20
>> The tests in s6.1 are measuring the quality of the decoded signal
>> against the=20
>> reference decoded signal, not against the original audio, so greater
>> than 100%
>> wouldn't be possible or meaningful. The test signals have been
>> specially
>> prepared to thoroughly test a decoder implementation, and they
>> sacrifice encoded
>> quality in order to rapidly exercise the corner cases.
>>=20
> You might want to add this comment to the text.
>=20
> As regards the 100 limit, I was sort of assuming that the quality =
figure
> was derived from improving on the 48dB SNR figure.  Probably a
> misreading.  AS a matter of interest, would one be able to tell from =
the
> tests that a putative new implementation really was 'better' in some
> sense? Or is this now almost a subjective matter that can only be
> determined by extensive listening tests?  I got the impression we may =
be
> converging on the diminishing returns point.
>=20
> /Elwyn
>=20
>>=20
>=20
>=20


From lee@asgard.org  Thu May 17 10:19:09 2012
Return-Path: <lee@asgard.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 A79DF21F8623 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 10:19:09 -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 oWiwyjmQZfQF for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 10:19:09 -0700 (PDT)
Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by ietfa.amsl.com (Postfix) with ESMTP id 0100D21F861D for <ietf@ietf.org>; Thu, 17 May 2012 10:19:08 -0700 (PDT)
Received: from cm-omr8 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q4HHJ7dT002868 for <ietf@ietf.org>; Thu, 17 May 2012 13:19:08 -0400
Authentication-Results: cm-omr8 smtp.user=lee@asgard.org; auth=pass (LOGIN)
X-Authenticated-UID: lee@asgard.org
Received: from [204.235.115.167] ([204.235.115.167:34177] helo=HDC00042402) by cm-omr8 (envelope-from <lee@asgard.org>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id D2/BF-01735-B0335BF4; Thu, 17 May 2012 13:19:07 -0400
From: "Lee Howard" <lee@asgard.org>
To: "'Dave Cridland'" <dave@cridland.net>, "'IETF-Discussion'" <ietf@ietf.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk>	<tslaa18w21n.fsf@mit.edu>	<4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com>	<m2mx57c2g5.wl%randy@psg.com> <22965.1337200180.525898@puncture>
In-Reply-To: <22965.1337200180.525898@puncture>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Date: Thu, 17 May 2012 13:19:07 -0400
Message-ID: <006601cd3451$2aaa94b0$7fffbe10$@asgard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHGz4alFcB3TxKmEduea4L+EpGxoAJtdb6SAUcBXMACpPelUwJZ29rfAuOqtVUCYxzVwwHMpEuallzMA2A=
Content-Language: en-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: Thu, 17 May 2012 17:19:09 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Dave Cridland
> Consider:
> 
> "An octet may contain 0-255".
> "An octet contains 0-255".
> "An octet might contain 0-255" - or it might not?
> "The Foo octet MUST lie between 0 and 127 inclusive; that is, the highest
bit MUST NOT
> be set."
> "A valid Foo octet lies between 0 and 127 inclusive; that is, the highest
bit is never set."

We do not improve clarity by making sentences harder to read.
We should avoid rfc2119 language where possible, to be clear, but not at the
expense of
clarity.

* Could be read as normative: "Always do this, unless you can explain why
you can't."

Lee


From elwynd@folly.org.uk  Wed May 16 14:26:50 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149B821F87CD; Wed, 16 May 2012 14:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.873
X-Spam-Level: 
X-Spam-Status: No, score=0.873 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_EQ_IP_ADDR=1.119, J_CHICKENPOX_13=0.6,  RDNS_DYNAMIC=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 2W0cFGKDAa6V; Wed, 16 May 2012 14:26:45 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id D109721F8799; Wed, 16 May 2012 14:26:44 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SUlk2-0005BY-54; Wed, 16 May 2012 22:26:42 +0100
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
From: Elwyn Davies <elwynd@folly.org.uk>
To: Jean-Marc Valin <jmvalin@jmvalin.ca>
In-Reply-To: <4FB2F5D0.7070701@jmvalin.ca>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca>
Content-Type: text/plain
Organization: Folly Consulting
Date: Wed, 16 May 2012 22:26:40 +0100
Message-Id: <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 17 May 2012 11:49:23 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.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, 16 May 2012 21:26:50 -0000

Hi, Jean-Marc.

... and thanks for the super-quick response!  You have been quite busy.

I have had a look through the new draft and I think the additions help
considerably with comprehension for the naive (and to give new
implementers a way in.)

I'll leave you to negotiate with the RFC Editor over the Wikipaedia
references.  To quote the RFC Style guide
http://www.rfc-editor.org/rfc-style-guide/rfc-style
Section 4.8, item (x) References, last section:
> URLs and DNS names in RFCs
> 
>       The use of URLs in RFCs is discouraged, because many URLs are not
>       stable references.  Exceptions may be made for normative
>       references in those cases where the URL is demonstrably the most
>       stable reference available.  References to long-lived files on
>       ietf.org and rfc-editor.org are generally acceptable.
They are certainly convenient *as long as they remain in place and
aren't corrupted*.

I found a couple of trivial editorial nits in the changes:
s4.3.3 (in the added text):
> The CELT layer, however, can adapt over a very wide range of rates,
> and thus has a large number of codebooks sizes
s/codebooks/codebook/

s4.3.3, para after Table 57: s?the maximums in bit/sample are
precomputed?the maximums in bits/sample are precomputed?

Also suggest:
s4.3: Add reference for Bark scale: Zwicker, E. (1961), "Subdivision of
the audible frequency range into critical bands," The Journal of the
Acoustical Society of America, 33, Feb., 1961.

A few responses in line below (agreed pieces elided): 

Regards,
Elwyn  Davies
====================================================================================

On Tue, 2012-05-15 at 20:33 -0400, Jean-Marc Valin wrote:
> Hi Elwyn,
> 
> Thanks for the very thorough review. We've addressed your issues and
> submitted draft version -13. See our response to each of the issues you
> raised (aggregated from all the authors) in the attached document.

Thanks very much to all the authors.
> 
> Cheers,
> 
> 	Jean-Marc
> 


> Elwyn Davies wrote:
> > Major issues: 
> > Can we accept the code as normative?  If not how do we proceed?
> 
> The issue with code being normative was specifically addressed in 
> the guidelines document for this WG (RFC 6569).
> 
Yes.  I failed to read this although Robert Sparks did point out to me
that the code was normative - but he didn't think he said this was
agreed in advance (or maybe I didn't understand what he was saying).

To be honest I would like to have had the time to tie the text to the
code but realistically that is several weeks or even months work to do
it properly - without that I feel that I have only done half a job. I
may decide that it interests me enough to have a superficial go next
week but no promises!

> 
> > Minor issues:
> > Contrast between decoder descriptions of LP part and CELT part:  The
> > SILK descriptions go into gory detail on the values used in lots of
> > tables, etc., whereas the CELT part has a very limited treatment of
> the
> > numeric values used (assuming reliance on finding the values in the
> > reference implementation, either explictly or implicitly).  There
> are
> > things to be said for both techniques.  I was wondering (while
> reading
> > the SILK description) if the authors have any means of automatically
> > generating the tables from the code in the SILK part (or vice versa)
> to
> > avoid double maintenance. On the other hand, there are pieces of the
> > CELT decoder description (especially in s4.3.3 where knowing numbers
> of
> > bands, etc.) where some actual numbers would help comprehension.
> > 
> 
> We have made many changes to section 4.3 (and 4.3.3 specifically) to
> address
> the specific issues below. As for the tables, they are not generated
> automatically.

I think this is addressed satisfactorily now.  There is still some
difference but it is much reduced and not so glaring now. The addition
of the band tables really helps.

> 
> 
> > s2 (and more generally):  The splitting of the signal in the
> frequency
> > domain into signal (components?) below and above 8kHz presumably
> > requires that the signal is subjected to a Discrete Fourier
> Transform to
> > allow the signal to be split.  I think sometging is needed in s2 to
> > explain how this is managed (or if I don't understand, to explain
> why it
> > isn't necessary).
> 
> No DFT is used. The lower band is obtained through resampling (which
> is already described) and the higher band is obtained by not coding
> the lower band with CELT (the text says that CELT starts at band 17 in
> hybrid mode). The explanation was reworded to make this as clear as
> possible at this point in the text.

[I thought I had reworded this comment in the 2nd version to talk about
MDCT but no matter]. 
Yes, para 5 of s2 does say that the bands are discarded.  I think it
would useful to have a concrete statement in the new text added to s4.3
that bands 0 to 16 are discarded in hybrid mode (thereby making the 17
in the band boost section more obvious) [There is a comment below that
you have added some text about band 17 in section 4.3 but I can't see
it].


> 
> > s4.2.5, para 3:
> >>     When switching from 20 ms to 10 ms, the 10 ms
> >>     20 ms Opus frame, potentially leaving a hole that needs to be
> >>     concealed from even a single packet loss.
> > How?
> 
> As explained in the LBRR text, a 10 ms frame will only contain 10 ms
> LBRR data even if the previous frame was 20 ms, so there's 10 ms
> "missing".
Indeed - that there would be a hole was clear.  The 'How' referred to
how would it be concealed.  Having read further by now this may be down
to Packet Loss Concealment - so maybe all it needs is a foward ref to
s4.4. 
> 
> > s4.3:
> > As a complete newcomer to CELT, I would have appreciated a more high
> > level understanding of what CELT is doing at this point.  I  tried
> > reading s4.3 without any additional input and found it very hard
> going.
> > Eventually I gave up and went looking for some additional input.
> This
> > presentation seems to have a useful view 
> > http://www.ietf.org/proceedings/79/slides/codec-2.pdf
> > I think that it would be extremely helpful to have a description
> similar
> > to this at this point in the document, even though there is some
> > material in section 5.3 which could also be forward referenced.
> Still
> > the material in s5.3 does not start from the basic principles that
> CELT
> > is using, and since these are essentially novel, it would be very
> good
> > to give prospective implementers/users an understanding of what is
> going
> > on.  Incidentally, I found the above IETF presentation more useful
> than
> > http://www.celt-codec.org/presentations/misc/lca-celt.pdf
> > Note that the SILK part seems rather less opaque.  It would also be
> > useful to indicate numerically how many bands are involved and what
> the
> > number of MDCT bins are in the various bands. 
> 
> The intro of section 4.3 has been expanded with general information
> about CELT
> similar to what the codec-2.pdf slides from 79 included. 
> 
I think this is an excellent improvement.
> 
> > Nits/editorial comments:
> > 
> > global: bytes ->  octets
> 
> We believe that in the field of audio codecs, the mention of "byte"
> without
> further context is well understood to mean 8 bits.

True. But this is a matter of IETF style.  The style is to use octets
where we mean 8 bit bytes. I think you now have a mixture!

> 
> > global: The form/terminology Q<n>  (e.g., Q13, Q15, Q16) ought to be
> > explained.
> 
> This was already defined in the section on notation:
>    The notation "Q<n>", where n
>    is an integer, denotes the number of binary digits to the right of
>    the decimal point in a fixed-point number.
Sorry - I missed that.
> 
> > s3.4: I am not keen on duplicating normative requirements in this
> way
> > (double maintenance issue).  It would be better to put explicit
> numbered
> > requirements in the sections above an reference the resulting
> numbers
> > here.
> 
> A checklist style summary is quite useful for implementors, and worth
> the maintenance burden for a document that is (hopefully) going to be
> published once and read many times. The list intentionally does not
> include any RFC 2119 keywords, to avoid any conflict should there
> (accidentally) be room to interpret the re-statement any differently
> from the original statement. Numbering the requirements and
> referencing the numbers is still a good idea, but it should be
> possible to read the list without flipping back and forth to the
> previous sections.

Good solution!

> 
> > s4.1.1:  This is really a global point.  This section refers to
> > entdec.c.  Presumably (since we haven't reached the code yet) and it
> is
> > still compressed, there is some file structure.  I don't think this
> has
> > been said above.  It would be good to provide a list of the file
> > components (i.e., sectional structure of the code) at the start,
> maybe
> > even  giving line number positions within the decompressed code.
> 
> In cases where it was deemed necessary (e.g. large functions), there
> are
> indeed line numbers in references to the code. As for a list of files
> we did not think it was useful because one already needs to decompress
> the code to see the references.

OK. We'll have to live with this situation.

Having looked at the code, I think it is a considerable pity that it
isn't Doxygen commented (or some such) throughout so that the whole
system can be viewed as a Doxygen tree. I can smell roasted programmer
from here... :-)
> 
> > s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
> >     selects the PDFs for the second stage of the VQ/This indexes an
> >     element in a coarse codebook that selects the PDFs for the
> second stage
> >     of the VQ/
> 
> The text as written is correct. The index I1 is what selects the PDFs
> for the second stage, not the vector from the coarse codebook in
> Tables 23 and 24. I.e., it's saying, "This does A, B, and C."

OK.  I think it might be clearer if the three things were separated out
as a list.  Now you point it out I can read it correctly but it
triggered minor confusion - worth turning the three things into bullet
points.

NEW:  s4.3: Add reference for Bark scale: Zwicker, E. (1961),
"Subdivision of the audible frequency range into critical bands," The
Journal of the Acoustical Society of America, 33, Feb., 1961.

Generally the new intro to s4.3 helps *a lot*.
> > s4.3.2.1: Avoid the equation picture splitting across page
> boundaries.
> > in the current version it is unclear what the denominator is. (use
> > needLines processing direcrive in xml2rfc).  Same applies to the
> > equation below Table 57 in s4.3.4.3.
> 
> It's not quite clear how to use needLines without undesirable
> side-effects.
> Hopefully this is something the RFC editor should be able to handle.
Indeed.. but I don't know what undesirable side effects there are?
AFAIK (and in my own usage) it just ensures there are n lines available
on the current page at some point in the text and forces a page throw if
not.
> 
> 
> > s4.3.3: (was specified as s 4.3.2.3 whcj was wrong) Paragraph on
> decoding band boosts:  Might be improved by using
> > equations rather than the wordy descriptions used at present.

Any thoughts on this one
> > 
> > (global)s4.3.2.3, para above table 56: s/iff/if and only if/
> 
> Fixed.
> 
> 
> > s4.3.3: <<snip>>.
> 
> Added an explanation of band 17 

I don't think this happened.

> 
> 
> > s6.1: This section is perhaps a little 'triumphalist' for the
> reference
> > implementation (this may of course be justified!.  The quality
> metric is
> > a 'relative quality metric' and presumably if someone does a
> *really*
> > good job of coding, it is entirely possible that the new algorithms
> > might get better than 100 on the quality score (i.e., provide a
> better
> > answer than the reference implementation).
> 
> Conformance with the specification is defined by a faithful
> reproduction of
> the specified decoder behavior (see RFC 6569 s4.3). By specifying the
> decoder, future encoders have the freedom to have improved quality
> with the
> confidence that they know what output a conforming decoder will
> produce.
> 
> The tests in s6.1 are measuring the quality of the decoded signal
> against the 
> reference decoded signal, not against the original audio, so greater
> than 100%
> wouldn't be possible or meaningful. The test signals have been
> specially
> prepared to thoroughly test a decoder implementation, and they
> sacrifice encoded
> quality in order to rapidly exercise the corner cases.
> 
You might want to add this comment to the text.

As regards the 100 limit, I was sort of assuming that the quality figure
was derived from improving on the 48dB SNR figure.  Probably a
misreading.  AS a matter of interest, would one be able to tell from the
tests that a putative new implementation really was 'better' in some
sense? Or is this now almost a subjective matter that can only be
determined by extensive listening tests?  I got the impression we may be
converging on the diminishing returns point.

/Elwyn

> 



From jmvalin@jmvalin.ca  Thu May 17 09:49:14 2012
Return-Path: <jmvalin@jmvalin.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 0C31921F86A6; Thu, 17 May 2012 09:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uM1zOyNLW1da; Thu, 17 May 2012 09:49:13 -0700 (PDT)
Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by ietfa.amsl.com (Postfix) with ESMTP id 3181621F866B; Thu, 17 May 2012 09:49:13 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)"
Received: from [192.168.1.14] ([96.21.20.94]) by VL-VM-MR003.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0M4600ALWEQ0NZA0@VL-VM-MR003.ip.videotron.ca>; Thu, 17 May 2012 12:49:12 -0400 (EDT)
Message-id: <4FB52BFE.4070606@jmvalin.ca>
Date: Thu, 17 May 2012 12:49:02 -0400
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
To: Elwyn Davies <elwynd@folly.org.uk>
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca> <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
In-reply-to: <1337203600.31554.2213.camel@mightyatom.folly.org.uk>
X-Enigmail-Version: 1.4.1
X-Mailman-Approved-At: Thu, 17 May 2012 11:49:18 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.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, 17 May 2012 16:49:14 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Hi Elwyn,

We're submitted a -14 draft to address your comments. Again, see the
response to each of these issues in the attached document.

Thanks again,

	Jean-Marc


On 12-05-16 05:26 PM, Elwyn Davies wrote:
> Hi, Jean-Marc.
> 
> ... and thanks for the super-quick response!  You have been quite busy.
> 
> I have had a look through the new draft and I think the additions help
> considerably with comprehension for the naive (and to give new
> implementers a way in.)


--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)
Content-type: text/plain; CHARSET=US-ASCII; name=genart2.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=genart2.txt

On 12-05-16 05:26 PM, Elwyn Davies wrote:
>> The CELT layer, however, can adapt over a very wide range of rates,
>> and thus has a large number of codebooks sizes
> s/codebooks/codebook/

Fixed.

> s4.3.3, para after Table 57: s?the maximums in bit/sample are
> precomputed?the maximums in bits/sample are precomputed?

Fixed.

> Also suggest:
> s4.3: Add reference for Bark scale: Zwicker, E. (1961), "Subdivision of
> the audible frequency range into critical bands," The Journal of the
> Acoustical Society of America, 33, Feb., 1961.

Done.

>> No DFT is used. The lower band is obtained through resampling (which
>> is already described) and the higher band is obtained by not coding
>> the lower band with CELT (the text says that CELT starts at band 17 in
>> hybrid mode). The explanation was reworded to make this as clear as
>> possible at this point in the text.
> 
> [I thought I had reworded this comment in the 2nd version to talk about
> MDCT but no matter]. 
> Yes, para 5 of s2 does say that the bands are discarded.  I think it
> would useful to have a concrete statement in the new text added to s4.3
> that bands 0 to 16 are discarded in hybrid mode (thereby making the 17
> in the band boost section more obvious) [There is a comment below that
> you have added some text about band 17 in section 4.3 but I can't see
> it].

Sorry, we started working on the revision as soon as you sent the first part
of the review, and then we just copied the new parts (didn't notice some of
the review changed).

Also, the reason you didn't see the new explanations about band 17 in s4.3 is that we moved them to s2 para 5, to help make the explanation of the signal splitting clearer, but forgot to update the response to indicate that (sorry about that). However, it probably does make sense to explain it in both places, so the sentence,
  "In hybrid mode, the first 17 bands (up to 8 kHz) are not coded."
has been added to s4.3 as well.

>> As explained in the LBRR text, a 10 ms frame will only contain 10 ms
>> LBRR data even if the previous frame was 20 ms, so there's 10 ms
>> "missing".
> Indeed - that there would be a hole was clear.  The 'How' referred to
> how would it be concealed.  Having read further by now this may be down
> to Packet Loss Concealment - so maybe all it needs is a foward ref to
> s4.4. 

Reference added.

>> We believe that in the field of audio codecs, the mention of "byte"
>> without
>> further context is well understood to mean 8 bits.
> 
> True. But this is a matter of IETF style.  The style is to use octets
> where we mean 8 bit bytes. I think you now have a mixture!
> 
>>

Indeed, there's a bit of inconsistency here. Considering Cullen's email,
the document now uses "byte" consistently.

>>> s4.2.7.5.1, para 1: s/This indexes an element in a coarse codebook,
>>>     selects the PDFs for the second stage of the VQ/This indexes an
>>>     element in a coarse codebook that selects the PDFs for the
>> second stage
>>>     of the VQ/
>>
>> The text as written is correct. The index I1 is what selects the PDFs
>> for the second stage, not the vector from the coarse codebook in
>> Tables 23 and 24. I.e., it's saying, "This does A, B, and C."
> 
> OK.  I think it might be clearer if the three things were separated out
> as a list.  Now you point it out I can read it correctly but it
> triggered minor confusion - worth turning the three things into bullet
> points.

This is not a bad idea. I agree it helps make things clearer. Done.

> NEW:  s4.3: Add reference for Bark scale: Zwicker, E. (1961),
> "Subdivision of the audible frequency range into critical bands," The
> Journal of the Acoustical Society of America, 33, Feb., 1961.

Done (as stated above).

>>> s4.3.3: (was specified as s 4.3.2.3 whcj was wrong) Paragraph on
>> decoding band boosts:  Might be improved by using
>>> equations rather than the wordy descriptions used at present.
> 
> Any thoughts on this one

Oops, that one slipped through. While most of the text is actually
describing an algorithm rather than an equation, it was possible to simplify
the part about the quanta with an equation. The text now reads:
"For each band from the coding start (0 normally, but 17 in Hybrid mode)
to the coding end (which changes depending on the signaled bandwidth), the boost quanta
in units of 1/8 bit is calculated as: quanta = min(8*N, max(48, N))."

>>> s4.3.3: <<snip>>.
>>
>> Added an explanation of band 17 
> 
> I don't think this happened.

See above -- operator error. It's fixed now.

>> The tests in s6.1 are measuring the quality of the decoded signal
>> against the 
>> reference decoded signal, not against the original audio, so greater
>> than 100%
>> wouldn't be possible or meaningful. The test signals have been
>> specially
>> prepared to thoroughly test a decoder implementation, and they
>> sacrifice encoded
>> quality in order to rapidly exercise the corner cases.
>>
> You might want to add this comment to the text.

Added the comment about 100 being the max. As for the other part, the test
vector section already states that:
"These test vectors were created specifically to exercise all aspects of the
decoder and therefore the audio quality of the decoded output is
significantly lower than what Opus can achieve in normal operation."

> As regards the 100 limit, I was sort of assuming that the quality figure
> was derived from improving on the 48dB SNR figure.  Probably a
> misreading.  AS a matter of interest, would one be able to tell from the
> tests that a putative new implementation really was 'better' in some
> sense? Or is this now almost a subjective matter that can only be
> determined by extensive listening tests?  I got the impression we may be
> converging on the diminishing returns point.

You can't have a "better" decoder because the reference implementation is
*by definition* the best decoder possible. From there, the encoder can
be improved to optimize the quality of a bitstream to be decoded by that
reference decoder. The encoder included with the reference is mature enough
that improvements usually need to be validated with human listening tests;
objective quality measurements aren't quite reliable enough alone to distinguish
'different' from 'better', unless the change is very significant.



--Boundary_(ID_9fGhe3E5xtAslVrakW0puQ)--

From narten@us.ibm.com  Thu May 17 21:54:05 2012
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 1FA8221F8716 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 21:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.181
X-Spam-Level: 
X-Spam-Status: No, score=-110.181 tagged_above=-999 required=5 tests=[AWL=0.418, 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 OkGz90v4Ga1D for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 21:54:03 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE7F21F869E for <ietf@ietf.org>; Thu, 17 May 2012 21:54:02 -0700 (PDT)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 17 May 2012 22:54:00 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 17 May 2012 22:53:07 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 73FDF19D804A for <ietf@ietf.org>; Thu, 17 May 2012 22:52:54 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q4I4r6A2261148 for <ietf@ietf.org>; Thu, 17 May 2012 22:53:06 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q4I4r5CM021896 for <ietf@ietf.org>; Thu, 17 May 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q4I4r53c021867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 17 May 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q4I4r4I5015951 for <ietf@ietf.org>; Fri, 18 May 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q4I4r3V2015928 for ietf@ietf.org; Fri, 18 May 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201205180453.q4I4r3V2015928@rotala.raleigh.ibm.com>
Date: Fri, 18 May 2012 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12051804-7408-0000-0000-000005228E82
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 04:54:05 -0000

Total of 57 messages in the last 7 days.
 
script run at: Fri May 18 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.53% |    6 |  7.75% |    35365 | dhc@dcrocker.net
  5.26% |    3 | 11.69% |    53304 | elwynd@folly.org.uk
  3.51% |    2 | 11.14% |    50783 | jmvalin@jmvalin.ca
  7.02% |    4 |  4.31% |    19674 | randy@psg.com
  3.51% |    2 |  6.19% |    28233 | hartmans-ietf@mit.edu
  5.26% |    3 |  4.02% |    18321 | adrian@olddog.co.uk
  5.26% |    3 |  3.92% |    17857 | stpeter@stpeter.im
  3.51% |    2 |  3.11% |    14177 | hsantos@isdg.net
  3.51% |    2 |  2.80% |    12792 | ole@cisco.com
  1.75% |    1 |  4.43% |    20226 | fluffy@cisco.com
  3.51% |    2 |  2.60% |    11865 | dot@dotat.at
  3.51% |    2 |  2.53% |    11557 | sm@resistor.net
  3.51% |    2 |  2.40% |    10960 | ned+ietf@mauve.mrochek.com
  1.75% |    1 |  2.35% |    10703 | mary.ietf.barnes@gmail.com
  1.75% |    1 |  2.04% |     9307 | narten@us.ibm.com
  1.75% |    1 |  1.69% |     7686 | barryleiba@computer.org
  1.75% |    1 |  1.61% |     7348 | daedulus@btconnect.com
  1.75% |    1 |  1.61% |     7347 | dave@cridland.net
  1.75% |    1 |  1.49% |     6775 | brian.e.carpenter@gmail.com
  1.75% |    1 |  1.44% |     6553 | dworley@avaya.com
  1.75% |    1 |  1.43% |     6527 | fluffy@iii.ca
  1.75% |    1 |  1.42% |     6464 | ynir@checkpoint.com
  1.75% |    1 |  1.42% |     6459 | rdroms.ietf@gmail.com
  1.75% |    1 |  1.40% |     6394 | peter.sylvester@edelweb.fr
  1.75% |    1 |  1.40% |     6374 | ajs@anvilwalrusden.com
  1.75% |    1 |  1.38% |     6297 | warren@kumari.net
  1.75% |    1 |  1.37% |     6252 | ed.lewis@neustar.biz
  1.75% |    1 |  1.29% |     5906 | lee@asgard.org
  1.75% |    1 |  1.28% |     5855 | julian.reschke@gmx.de
  1.75% |    1 |  1.27% |     5772 | john-ietf@jck.com
  1.75% |    1 |  1.27% |     5770 | jaap@nlnetlabs.nl
  1.75% |    1 |  1.25% |     5709 | scott@kitterman.com
  1.75% |    1 |  1.22% |     5571 | ben@nostrum.com
  1.75% |    1 |  1.19% |     5439 | dougb@dougbarton.us
  1.75% |    1 |  1.19% |     5420 | vesely@tana.it
  1.75% |    1 |  1.10% |     5020 | simon.perreault@viagenie.ca
--------+------+--------+----------+------------------------
100.00% |   57 |100.00% |   456062 | Total


From hsantos@isdg.net  Thu May 17 22:07:02 2012
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 4ABEB21F86FA for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 22:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.495
X-Spam-Level: 
X-Spam-Status: No, score=-1.495 tagged_above=-999 required=5 tests=[AWL=0.182,  BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=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 Lpwg1em+im-y for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 22:07:00 -0700 (PDT)
Received: from ftp.catinthebox.net (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A41A321F86F5 for <ietf@ietf.org>; Thu, 17 May 2012 22:07:00 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=806; t=1337317614; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Lc5kNJUTZT+J21dOkfN3m0jldO4=; b=g6gSzKlLmRuE25NsxP35 WdHD4Uya+teV11BdkCn8AxkbPw1mV0F1mQP/WtNY0Dcflr2RDo+7oAI7QUceVExD IKEpuMaZRlHGAnCgLZygnQn9Tpex1de4y43IKlLSiCr8UTFPMw6GMXWUf9o+70tq sp87U1h86OggniaiDVzA4ZQ=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 18 May 2012 01:06:54 -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 v6.4.454.1) with ESMTP id 1929440449.90.4012; Fri, 18 May 2012 01:06:53 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=806; t=1337317588; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Psz3A9S 7g8ovzsvsAdiJuvhCpUOHXMb55yyoxHst1XA=; b=qeObEkavNqf8ShctHjXwFNu tgYY2LCMgzqkHz5UXJd8r0H89KaGVSmdSj54/CQq40Lhl5IA1nIgDI7u9i+ne9wU Nvy2+5VWr63uFqETW0f7Pz+q8NhyeDm2zZwy+ybyMgh9q9vgSPNPkOT3zoe1y1DD q4Vzf8eDH4Y77C4JqG6o=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Fri, 18 May 2012 01:06:28 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2528320847.8002.3232; Fri, 18 May 2012 01:06:27 -0400
Message-ID: <4FB5D8E0.8060306@isdg.net>
Date: Fri, 18 May 2012 01:06:40 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Lee Howard <lee@asgard.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<08ab01cd3372$65934110$30b9c330$@olddog.co.uk>	<tslaa18w21n.fsf@mit.edu>	<4FB3E99D.1040606@stpeter.im>	<4FB3EDB8.60809@gmail.com>	<m2mx57c2g5.wl%randy@psg.com>	<22965.1337200180.525898@puncture> <006601cd3451$2aaa94b0$7fffbe10$@asgard.org>
In-Reply-To: <006601cd3451$2aaa94b0$7fffbe10$@asgard.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: Fri, 18 May 2012 05:07:02 -0000

Lee Howard wrote:
> 
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Dave Cridland
>> Consider:
>>
>> "An octet may contain 0-255".
>> "An octet contains 0-255".
>> "An octet might contain 0-255" - or it might not?
>> "The Foo octet MUST lie between 0 and 127 inclusive; that is, the highest
> bit MUST NOT
>> be set."
>> "A valid Foo octet lies between 0 and 127 inclusive; that is, the highest
> bit is never set."
> 
> We do not improve clarity by making sentences harder to read.

Or colorizing it.

> We should avoid rfc2119 language where possible, to be clear, but not at the
> expense of clarity.

+1, I think this is more specific to documents and not RFC2119. I 
don't think we can generalize RFC2119.


-- 
HLS



From trammell@tik.ee.ethz.ch  Fri May 18 05:13:27 2012
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 5A74B21F858D; Fri, 18 May 2012 05:13:27 -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 E2nkSDvtvlXN; Fri, 18 May 2012 05:13:26 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 9009521F857F; Fri, 18 May 2012 05:13:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id F37D7D930A; Fri, 18 May 2012 14:13:25 +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 0p+YUr-N73VR; Fri, 18 May 2012 14:13:25 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (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 BE77ED9304; Fri, 18 May 2012 14:13:25 +0200 (MEST)
Subject: Re: [mile] Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining	Extensions to IODEF) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4FB46FA6.6060005@stpeter.im>
Date: Fri, 18 May 2012 14:13:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B06DB832-2813-4431-94B9-1F7B3492A595@tik.ee.ethz.ch>
References: <20120516215321.9671.39664.idtracker@ietfa.amsl.com> <4FB46FA6.6060005@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1278)
Cc: mile@ietf.org, The IESG <iesg-secretary@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 May 2012 12:13:27 -0000

Hi, Peter, all,

Many thanks for the comments; replies inline...

On May 17, 2012, at 5:25 AM, Peter Saint-Andre wrote:

> On 5/16/12 3:53 PM, The IESG wrote:
>>=20
>> The IESG has received a request from the Managed Incident Lightweight
>> Exchange WG (mile) to consider the following document:
>> - 'Guidelines for Defining Extensions to IODEF'
>>  <draft-ietf-mile-template-04.txt> as Informational RFC
>=20
> Although this document does no harm, I have my doubts that the topic
> warrants publication of an RFC (and I say that as someone who is
> defining some IODEF extensions for use on the XMPP network [1]). Why
> would a simple wiki page [2] not suffice?

Indeed, it may; the WG decided we wanted something semi-permanent to =
give guidance to extension authors, especially given that we anticipated =
(and have had) significant participation from people with little or no =
previous involvement in the IETF. Whether that's an RFC or not is, but =
an RFC seemed the natural thing to do, as it is how things are published =
out of IETF WGs.

The previous version of this document _did_ need to be an RFC as it =
specified a change to the IANA XML registry requiring a Standards =
Action; this has been split out into draft-ietf-mile-iodef-xmlreg per AD =
guidance.

> If we decide than an RFC is needed, I have some more actionable =
feedback...
>=20
> 1. The document could be construed as assuming that IODEF extensions
> will all be defined in Internet-Drafts, that extension namespaces will
> be registered with IANA, and even that namespaces will be of the form
> 'urn:ietf:params:xml:schema:iodef-*'. It might be helpful to clarify =
the
> intended applicability of this document, i.e., merely as helpful
> suggestions for authors of Internet-Drafts, not truly as universally
> applicable guidelines for defining IODEF extensions.

Hm. The document does indeed assume that extensions to IODEF are defined =
in Internet-Drafts, that extension namespaces will be registered with =
IANA, and that those namespaces be of the described form; it makes these =
assumptions because that is the intent of the document. Whether that's =
"universal" or not could be an open question, perhaps, but the intent is =
to specify a more restrictive method of extension than that in 5070 in =
the interests of consistency. So, yes, it's an informational document, =
they're just helpful suggestions, but we would hope they'd be followed, =
and the document is written assuming that they will...

> 2. Why is RFC 6545 a normative reference?

Oversight, should be informative (I checked this briefly; it is =
referenced from a section entitled "Terminology", but this is =
terminology in the Appendix; oops.)

> 3. Given the many comments provided by Martin D=FCrst, mentioning his
> AppsDir review in the Acknowledgements seems appropriate.

Indeed, also oversight; thanks.

> 4. Some of the text in the appendix seems needlessly detailed (e.g.,
> saying that each extension needs to be specified in a subsection, or =
the
> recommendation to include a UML diagram).

These guidelines are intended to help the set of drafts defining IODEF =
extensions to be consistent with RFC 5070 and with each other.

> 5. Why is the list of datatypes in appendix A.4.1 copied from RFC =
5070?
> A simple reference would do. (I almost said the same about the list in
> Section 3, but that one is marginally useful.)

The A.4.1. list was copied over because doing so was consistent with the =
list in Section 3, more or less; it's intended to give an inline =
definition of the allowable TYPE values as in the UML diagram in Figure =
1, section A.4. (Copying this was also consistent with the inclusion of =
the list in Section 3.)

> 6. Some of the information in this document repeats information from =
the
> RFC style guide and other sources; why?

Here we have a duelling-commenters situation; this is per early-AD =
commentary in =
http://www.ietf.org/mail-archive/web/mile/current/msg00657.html and the =
subsequent thread.

Best regards,

Brian (as author, draft-ietf-mile-template)


From marshall.eubanks@gmail.com  Fri May 18 06:28:37 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C71B21F8658 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 06:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.653
X-Spam-Level: 
X-Spam-Status: No, score=-103.653 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 oHLUpKL4K+jE for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 06:28:36 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7EAF121F8633 for <ietf@ietf.org>; Fri, 18 May 2012 06:28:36 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2391520lbb.31 for <ietf@ietf.org>; Fri, 18 May 2012 06:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3n+IvTr0bpQ5oO0gllTVCreWSYvoxnHTEzDzP/QWWOM=; b=0rY0/35u1Urs+EfGHOaWsgx0Lv4t1Xwk/GZ0q+CKt+HzExFdfswFqvyzE8LxztWIKD J2qGXmxcV/D1ynxoLV5r4ymjLiG6BdqzlGFOQEs7TcA64ooGlxuekZjsgp2emUo325Jj MPFk+ziE5h/Dk0UD/Pg2Q/UDG3QX7ZAGptSO7yFaR0OPpLEvLrpDdrhUBvm1yR4jS1r2 RJueFzqpZKCQ0pStHJ3ElZurSBFf/nlAfkGEVb/D1BeHsCPgzGmOzdRy/SlKqgV3DpFo TvPBFjvME+XnMXNgsF8MlLJrp5RmK34YrIKb8mnzq69Cz5dv99gMMEB5DsWlgwEH6KST jc4A==
MIME-Version: 1.0
Received: by 10.112.28.10 with SMTP id x10mr4854680lbg.41.1337347715423; Fri, 18 May 2012 06:28:35 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Fri, 18 May 2012 06:28:35 -0700 (PDT)
In-Reply-To: <4FB5D8E0.8060306@isdg.net>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com> <m2mx57c2g5.wl%randy@psg.com> <22965.1337200180.525898@puncture> <006601cd3451$2aaa94b0$7fffbe10$@asgard.org> <4FB5D8E0.8060306@isdg.net>
Date: Fri, 18 May 2012 09:28:35 -0400
Message-ID: <CAJNg7V+M0a1kzgjVH7QJ1_9UUzh5_5CUbQmoVRLkJ8PxYrEBhQ@mail.gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 13:28:37 -0000

On Fri, May 18, 2012 at 1:06 AM, Hector Santos <hsantos@isdg.net> wrote:
> Lee Howard wrote:
>>
>>
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>
>> Dave Cridland
>>>
>>> Consider:
>>>
>>> "An octet may contain 0-255".
>>> "An octet contains 0-255".
>>> "An octet might contain 0-255" - or it might not?
>>> "The Foo octet MUST lie between 0 and 127 inclusive; that is, the highest
>>
>> bit MUST NOT
>>>
>>> be set."
>>> "A valid Foo octet lies between 0 and 127 inclusive; that is, the highest
>>
>> bit is never set."
>>
>> We do not improve clarity by making sentences harder to read.
>
>
> Or colorizing it.

I find this morning a message on the URN WG list
by Alfred Hines on RFC 6329, which has a new (AFAIK) convention on
normative language

3.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   The lowercase forms with an initial capital "Must", "Must Not",
   "Shall", "Shall Not", "Should", "Should Not", "May", and "Optional"
   in this document are to be interpreted in the sense defined in
   [RFC2119], but are used where the normative behavior is defined in
   documents published by SDOs other than the IETF.


I am not sure this is in the direction of greater clarity. Should
there be a need to
overlay different degrees of normativeness onto a text, XML would
probably be better bet.
Whether the previous sentence is normative or not is left as an
exercise for the reader.

Regards
Marshall


>
>
>> We should avoid rfc2119 language where possible, to be clear, but not at
>> the
>> expense of clarity.
>
>
> +1, I think this is more specific to documents and not RFC2119. I don't
> think we can generalize RFC2119.
>
>
> --
> HLS
>
>

From ned+ietf@mauve.mrochek.com  Fri May 18 08:22:22 2012
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 7F6DC21F85AA for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 08:22: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=[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 sfOWKJyuK1wc for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 08:22:22 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0129521F8594 for <ietf@ietf.org>; Fri, 18 May 2012 08:22:21 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFMDXA9EWG00081Q@mauve.mrochek.com> for ietf@ietf.org; Fri, 18 May 2012 08:22:19 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 18 May 2012 08:22:17 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFMDX95S0W0006TF@mauve.mrochek.com>
Date: Fri, 18 May 2012 08:14:34 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: "Your message dated Fri, 18 May 2012 09:28:35 -0400" <CAJNg7V+M0a1kzgjVH7QJ1_9UUzh5_5CUbQmoVRLkJ8PxYrEBhQ@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <4FB3EDB8.60809@gmail.com> <m2mx57c2g5.wl%randy@psg.com> <22965.1337200180.525898@puncture> <006601cd3451$2aaa94b0$7fffbe10$@asgard.org> <4FB5D8E0.8060306@isdg.net> <CAJNg7V+M0a1kzgjVH7QJ1_9UUzh5_5CUbQmoVRLkJ8PxYrEBhQ@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
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 May 2012 15:22:22 -0000

> I find this morning a message on the URN WG list
> by Alfred Hines on RFC 6329, which has a new (AFAIK) convention on
> normative language

> 3.  Conventions Used in This Document

>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in [RFC2119].

>    The lowercase forms with an initial capital "Must", "Must Not",
>    "Shall", "Shall Not", "Should", "Should Not", "May", and "Optional"
>    in this document are to be interpreted in the sense defined in
>    [RFC2119], but are used where the normative behavior is defined in
>    documents published by SDOs other than the IETF.


> I am not sure this is in the direction of greater clarity. Should
> there be a need to
> overlay different degrees of normativeness onto a text, XML would
> probably be better bet.
> Whether the previous sentence is normative or not is left as an
> exercise for the reader.

By my count, there are also two lower case "must"s and six lower case "should"s
in there. In a document with compliance language this complex, those SHOULD
have been eliminated.

Be that as it may, this is asking more of the convention that it realistically
can be expected to deliver. I don't know the circumstances behind this
document - maybe there was no alternative - but the right thing IMO is to
try and avoid having to do anything like this.

				Ned

From rdroms.ietf@gmail.com  Fri May 18 09:41:18 2012
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 5631C21F867A for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 09:41:18 -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 Yt3eh6WA+cJw for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 09:41:17 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6E93A21F8627 for <ietf@ietf.org>; Fri, 18 May 2012 09:41:16 -0700 (PDT)
Received: by qabj40 with SMTP id j40so394716qab.15 for <ietf@ietf.org>; Fri, 18 May 2012 09:41:16 -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:x-mailer; bh=hfGAlZZtABxRgFVVWJfZw5k1iC6SbdQgCXQplZyO7qo=; b=oJHwzkRh0ZWsx6cGp44IBvmmaltLNrdglF5jWUTA+cdoGHrKJM5nLAdIwBWoZZ0Wrh 6MzZPhdvQxrOmgiE/lybyrYmD88nKuEeLX9bypjm497G+gRZyFEZpGQJJNZy1aVRAZrc znVxcDw/oPWGcx4wgCkiur7PLJT0xWLkyn33do2LbuQViJk3dMbzRMmGLGRgmpqpFY+1 EW78qnm9nU3vaMpl6rCVHNsQ9WI3eiZiyYqHqtg60QmDv9TqDP+SC71sB4O0U67aFpAh Mr2JyE3mJybx+Fdf3YTuTNnfoh9AdSnm1cRf6CL82O0tsFjcwWQfSxhgf2+qYEkuYGBk TZbw==
Received: by 10.224.212.5 with SMTP id gq5mr24434562qab.1.1337359275952; Fri, 18 May 2012 09:41:15 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id x10sm21868449qan.1.2012.05.18.09.41.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 May 2012 09:41:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <01OFK8GNXASC0006TF@mauve.mrochek.com>
Date: Fri, 18 May 2012 12:41:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com>
To: IETF list discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 16:41:18 -0000

On May 16, 2012, at 10:22 PM 5/16/12, Ned Freed wrote:

>=20
>> On May 16, 2012, at 5:22 PM 5/16/12, ned+ietf@mauve.mrochek.com =
wrote:
>=20
>>>>>  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",
>>>>>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this
>>>>>  document are to be interpreted as described in [RFC2119] when =
they
>>>>>  appear in ALL CAPS.  These words may also appear in this document =
in
>>>>>  lower case as plain English words, absent their normative =
meanings.
>>>=20
>>>> i like this a lot
>>>=20
>>> I agree. In fact I just incorporated it into the media types =
registration
>>> update.
>=20
>> To be sure of meaning and help confusion avoidance, I would prefer =
that the
>> key words not appear in the document in lower case and that authors =
use the
>> suggested replacement words (or break out the thesaurus?).
>=20
> Preferring it is one thing; I'm OK with that. Making it some sort of
> hard-and-fast rule is another matter entirely. We have too many of =
those
> as it is.

Well, here's another example of imprecision in the written word.  What I =
meant is that my preference would be a requirement that RFC 2119 key =
words not appear in lower case at all.

Seems to me that precision of meaning overrides graceful use of the =
language.  Making the requirement something like "RFC 2119 key words =
SHOULD NOT appear in lower case unless the lower case usage is clearly =
non-normative" means we have to think a lot harder about some details =
and (AD hat and reading glasses firmly in place) we have enough details =
to think about already.  So, I recommend an errata to RFC 2119: "These =
words MUST NOT appear in a document in lower case."

- Ralph

>=20
> 				Ned


From marshall.eubanks@gmail.com  Fri May 18 10:04:13 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE1A21F857A for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 10:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.653
X-Spam-Level: 
X-Spam-Status: No, score=-103.653 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 W1S4W7hh-JN2 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 10:04:12 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 627F121F853F for <ietf@ietf.org>; Fri, 18 May 2012 10:04:12 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2576979lbb.31 for <ietf@ietf.org>; Fri, 18 May 2012 10:04: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:content-transfer-encoding; bh=tb8u3ghla3SefuPLKhF0VE58lgZiXp5+1zf36avWiEY=; b=D3ugTbKlz3k/0VOkWOPcjgrXtPuJfgECgKElrGWWw51R0qUrCcvIjIgqMxGJRp926C GdKgMep55tthVol74FRRGscJXxuRAniqtNWeWw4BjZkR5D6OTMamaJeXK9ea4Z//VtMY KyD5QLBrwl57U1qzVxkjP2MPpGOVHpqo4XOtK32bKHtx9I5if5znFj8eDfmCrj4YxBDq 3qN6rp5tfLM/QDDpR9oMc1qKEDU3EYqNyJ82sFirx/h19cHD7xQeCPBInvaABg6yBIcv RVX2tMWy7eKIh+YYqtk+liIXPfNzNxqCoMDEk8k8B7JpaoOvnY3ETWs+HMge4tw+3qDi GyiQ==
MIME-Version: 1.0
Received: by 10.112.98.225 with SMTP id el1mr1786783lbb.30.1337360651247; Fri, 18 May 2012 10:04:11 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Fri, 18 May 2012 10:04:11 -0700 (PDT)
In-Reply-To: <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>
Date: Fri, 18 May 2012 13:04:11 -0400
Message-ID: <CAJNg7VLPALpjN4MGDfPj1i41aPw8St0Pg6OyCcgV-t6d_2teHg@mail.gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF list 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 May 2012 17:04:13 -0000

On Fri, May 18, 2012 at 12:41 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote=
:
>
> On May 16, 2012, at 10:22 PM 5/16/12, Ned Freed wrote:
>
>>
>>> On May 16, 2012, at 5:22 PM 5/16/12, ned+ietf@mauve.mrochek.com wrote:
>>
>>>>>> =A0The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT=
",
>>>>>> =A0"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in t=
his
>>>>>> =A0document are to be interpreted as described in [RFC2119] when the=
y
>>>>>> =A0appear in ALL CAPS. =A0These words may also appear in this docume=
nt in
>>>>>> =A0lower case as plain English words, absent their normative meaning=
s.
>>>>
>>>>> i like this a lot
>>>>
>>>> I agree. In fact I just incorporated it into the media types registrat=
ion
>>>> update.
>>
>>> To be sure of meaning and help confusion avoidance, I would prefer that=
 the
>>> key words not appear in the document in lower case and that authors use=
 the
>>> suggested replacement words (or break out the thesaurus?).
>>
>> Preferring it is one thing; I'm OK with that. Making it some sort of
>> hard-and-fast rule is another matter entirely. We have too many of those
>> as it is.
>
> Well, here's another example of imprecision in the written word. =A0What =
I meant is that my preference would be a requirement that RFC 2119 key word=
s not appear in lower case at all.
>
> Seems to me that precision of meaning overrides graceful use of the langu=
age. =A0Making the requirement something like "RFC 2119 key words SHOULD NO=
T appear in lower case unless the lower case usage is clearly non-normative=
" means we have to think a lot harder about some details and (AD hat and re=
ading glasses firmly in place) we have enough details to think about alread=
y. =A0So, I recommend an errata to RFC 2119: "These words MUST NOT appear i=
n a document in lower case."

...except in a direct quote of another document.

Regards
Marshall

>
> - Ralph
>
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned
>

From elwynd@folly.org.uk  Thu May 17 11:56:16 2012
Return-Path: <elwynd@folly.org.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E05D21F8749; Thu, 17 May 2012 11:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.423
X-Spam-Level: 
X-Spam-Status: No, score=0.423 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888,  HELO_EQ_IP_ADDR=1.119, RDNS_DYNAMIC=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 SZOnUTjBiws8; Thu, 17 May 2012 11:56:15 -0700 (PDT)
Received: from b.c.painless.aa.net.uk (c.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e35]) by ietfa.amsl.com (Postfix) with ESMTP id 984BD21F86A6; Thu, 17 May 2012 11:56:15 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[81.187.254.250]) by c.painless.aaisp.net.uk with esmtp (Exim 4.72) (envelope-from <elwynd@folly.org.uk>) id 1SV5rz-0004j9-L1; Thu, 17 May 2012 19:56:15 +0100
Subject: Re: [Gen-art] Gen-art last call review of draft-ietf-codec-opus-12.txt (completed)
From: Elwyn Davies <elwynd@folly.org.uk>
To: Jean-Marc Valin <jmvalin@jmvalin.ca>
In-Reply-To: <4FB52BFE.4070606@jmvalin.ca>
References: <1337001184.23527.1544.camel@mightyatom.folly.org.uk> <4FB2F5D0.7070701@jmvalin.ca> <1337203600.31554.2213.camel@mightyatom.folly.org.uk> <4FB52BFE.4070606@jmvalin.ca>
Content-Type: text/plain
Organization: Folly Consulting
Date: Thu, 17 May 2012 19:56:13 +0100
Message-Id: <1337280973.31554.4834.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 18 May 2012 10:49:57 -0700
Cc: General Area Review Team <gen-art@ietf.org>, "codec@ietf.org" <codec@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-codec-opus.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, 17 May 2012 18:56:16 -0000

Hi, Jean-Marc and co-authors

On Thu, 2012-05-17 at 12:49 -0400, Jean-Marc Valin wrote:
> Hi Elwyn,
> 
> We're submitted a -14 draft to address your comments. Again, see the
> response to each of these issues in the attached document.

I think we are done.  Thanks once again for the rapid response.

Regards,
Elwyn

PS
I still prefer octets.

/E
> 
> Thanks again,
> 
> 	Jean-Marc
> 
> 
> On 12-05-16 05:26 PM, Elwyn Davies wrote:
> > Hi, Jean-Marc.
> > 
> > ... and thanks for the super-quick response!  You have been quite busy.
> > 
> > I have had a look through the new draft and I think the additions help
> > considerably with comprehension for the naive (and to give new
> > implementers a way in.)
> 


From erosen@cisco.com  Fri May 18 11:23:44 2012
Return-Path: <erosen@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 E8F2D21F8692 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:23:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G3LCLyFYuho6 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:23:44 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0C821F852A for <ietf@ietf.org>; Fri, 18 May 2012 11:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=erosen@cisco.com; l=1416; q=dns/txt; s=iport; t=1337365424; x=1338575024; h=to:cc:subject:in-reply-to:reply-to:date:message-id:from; bh=bHx36wjMynRKYrKHb8+oIrLzubyywWqRnVAf+R71Cfk=; b=ifMM86dWluzjx5JHMabWQ2gqmsJC2HeLX1zVOch2hl5koBb4lAPiGzY8 Q9Rbh9oFFUIk0h3f1hmpNw0cf6etb5ngqMr43kZA3UtM9GdmDSAviqvdc r2q5WW0yBd23KUB2fjEueYvpo/zgfwZu4b97abDfu4phRW4+aPx5n3S0i 4=;
X-IronPort-AV: E=Sophos;i="4.75,618,1330905600"; d="scan'208";a="42246321"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 18 May 2012 18:23:43 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q4IINhcQ021603; Fri, 18 May 2012 18:23:43 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id q4IINgSt017848;  Fri, 18 May 2012 14:23:42 -0400
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: Your message of Fri, 18 May 2012 12:41:11 -0400. <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>
Date: Fri, 18 May 2012 14:23:42 -0400
Message-ID: <17847.1337365422@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: IETF list discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: erosen@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 18:23:45 -0000

> So, I recommend an errata to RFC 2119: "These words MUST NOT appear in a
> document in lower case."

I'm glad you said "I recommend" instead of "I have recommended", as the
latter would violate the recommended (oh dear) rule.

This RECOMMENDED rule would also imply that documents can no longer be
published during the month of May, as otherwise the date line would put the
document out of compliance with this erratum.

Also, it would no longer be possible for the references to list any document
that was published in the month of May.  I suppose we could make it a rule
that the month of May be referred to as "the month between April and June".

Of course, you didn't say that the reserved words muSt nOt appear in mixed
case, so mAybe that will become a workaround.

> Seems to me that precision of meaning overrides graceful use of the
> language.

Many IETF specs lack the desirable degree of precision, but the use of the
"reserved words" in capitalized or uncapitalized form just is not that big a
contributor to the imprecision.  Failure to properly specify all the actions
in all the possible state/event combinations is a much bigger source of
confusion than failure to capitalize "must" (I mean failure to capitalize
"MUST").  I don't know why so much attention is being given to something
that is NOT going to improve the quality of the specs by any appreciable
amount.







From randy@psg.com  Fri May 18 11:27:19 2012
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 E126721F878E for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:27:19 -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 XbQFMZ-i8BPs for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:27:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8E53B21F877F for <ietf@ietf.org>; Fri, 18 May 2012 11:27:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SVRtV-0004Ok-VR; Fri, 18 May 2012 18:27:18 +0000
Date: Sat, 19 May 2012 03:27:17 +0900
Message-ID: <m2396x73az.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF list 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 May 2012 18:27:20 -0000

> I recommend an errata to RFC 2119: "These words MUST NOT appear in a
> document in lower case."

first, that is not an erratum, it is a non-trivial semantic change.

second, do we not already have enough problems being clear and concise
without removing common words from our language?

randy

From ned+ietf@mauve.mrochek.com  Fri May 18 11:33:44 2012
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 AEC1821F87F3 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:33:44 -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 raGvyYInDwwa for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:33:44 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id CCA3621F87EE for <ietf@ietf.org>; Fri, 18 May 2012 11:33:43 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OFMKMIPI28001OLU@mauve.mrochek.com> for ietf@ietf.org; Fri, 18 May 2012 11:33:41 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OF7HODY84G0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 18 May 2012 11:33:38 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OFMKMH65440006TF@mauve.mrochek.com>
Date: Fri, 18 May 2012 11:32:56 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-reply-to: "Your message dated Sat, 19 May 2012 03:27:17 +0900" <m2396x73az.wl%randy@psg.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Cc: IETF list 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 May 2012 18:33:44 -0000

> > I recommend an errata to RFC 2119: "These words MUST NOT appear in a
> > document in lower case."

> first, that is not an erratum, it is a non-trivial semantic change.

And therefore explicitly disallowed by the erratum process.

> second, do we not already have enough problems being clear and concise
> without removing common words from our language?

A very emphatic +1.

				Ned

From rdroms.ietf@gmail.com  Fri May 18 11:35:52 2012
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 E2ED721F8811 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.6
X-Spam-Level: 
X-Spam-Status: No, score=-100.6 tagged_above=-999 required=5 tests=[AWL=0.399,  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 NZHDkgU3-H3t for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:35:52 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 48E7A21F8751 for <ietf@ietf.org>; Fri, 18 May 2012 11:35:52 -0700 (PDT)
Received: by qadz3 with SMTP id z3so384681qad.10 for <ietf@ietf.org>; Fri, 18 May 2012 11:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=14zM1GWxPJFBEfJls7TyFiVyuZkuWZAGHPIncagtb2k=; b=QF0/7mrvw5eNmh88EcTApttX3wcgzGAMHY/nOJFWDE7GmXgVUIyPOMl/6fMAvrfKuP LdsFEDuO4ZC//jb0iRMf1kfhCpblCGmADw89gK3Heolx2/GwrAO0DLukzFjOP2kzwxfN 8nFvUrTOMOuESo27oEkDCtr3QPlYV6kwOY5nn8G4IHcX/FCwoFcEJqbBdRMc5hGjZCpK 6OsG0k023NUdvPXdDTr5pTpAKugflHYBOepzE+3kaEVQGZiTBXOcvow64nKmjYpFVIYg wKMEfK6WC+u6vZO9zlL67c6TugqDo1O5kLb+bHcc6bmb9gmd7Teq/+Qh3xnqHsj5c3Ui kOkw==
Received: by 10.224.110.70 with SMTP id m6mr24863894qap.69.1337366151853; Fri, 18 May 2012 11:35:51 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id r19sm22386987qae.14.2012.05.18.11.35.50 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 May 2012 11:35:50 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <m2396x73az.wl%randy@psg.com>
Date: Fri, 18 May 2012 14:35:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9880F32-9540-417F-B340-5C3AC7B374B5@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF list 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 May 2012 18:35:53 -0000

On May 18, 2012, at 2:27 PM 5/18/12, Randy Bush wrote:

>> I recommend an errata to RFC 2119: "These words MUST NOT appear in a
>> document in lower case."
>=20
> first, that is not an erratum, it is a non-trivial semantic change.

You are correct and point taken. =20

>=20
> second, do we not already have enough problems being clear and concise
> without removing common words from our language?

Dave Crocker's suggestion would minimize the number of words taken out =
of our vocabulary:

> I'd be inclined to change 2119 to reserve only Must, Should and May, =
independent of case and for no other use, and release the other terms.


In addition to "clear and concise" we need precision and avoidance of =
ambiguity.

- Ralph


>=20
> randy


From randy@psg.com  Fri May 18 11:40:15 2012
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 D9E4221F86B3 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:40:15 -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 7DTWW-F+xVgp for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 11:40:15 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 90A7321F86A4 for <ietf@ietf.org>; Fri, 18 May 2012 11:40:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SVS62-0004QI-R7; Fri, 18 May 2012 18:40:15 +0000
Date: Sat, 19 May 2012 03:40:13 +0900
Message-ID: <m2zk955o4y.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <B9880F32-9540-417F-B340-5C3AC7B374B5@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <B9880F32-9540-417F-B340-5C3AC7B374B5@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF list 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 May 2012 18:40:16 -0000

> Dave Crocker's suggestion would minimize the number of words taken out
> of our vocabulary:

for a language other than english.

> In addition to "clear and concise" we need precision and avoidance of
> ambiguity.

wonderful rofl.  thanks.  mind if i put that in my public quotes file?

randy

From rdroms.ietf@gmail.com  Fri May 18 12:59:25 2012
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 9553221F8638 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 12:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.033
X-Spam-Level: 
X-Spam-Status: No, score=-102.033 tagged_above=-999 required=5 tests=[AWL=1.566, 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 cbN3Scr30BqS for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 12:59:25 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id EBE1E21F853E for <ietf@ietf.org>; Fri, 18 May 2012 12:59:24 -0700 (PDT)
Received: by qabj40 with SMTP id j40so549528qab.15 for <ietf@ietf.org>; Fri, 18 May 2012 12:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=2XvKw24+gOsTzJ7AKzgR114RfLezqGPZ9eJLdr0R8qY=; b=BNkhCk44X3VcpCkziomGXhcIAZK8EwrGEzJetq2c/GswQ+ADUZ8VhpQJ6VIRgUNFqw Ef2vXfmEOFkYkZwl2Yj1Hv9uL2mXxhXblOwMbfuR1EAiYyQNGAGQKeXc31LOA2LCHigq 5oNf77cJ4BuzEohD/yFfJbaSpuBuTHYmzrNfjtqrBX792TpeqxuvMq4fQhZvH84BSNpr 19I5Gb3d+QLLug3DWGGsik8c18BICAFd0PgU+GQcX6IG4frzqe4UwLD6W2uLvaccIUwA ZHGkSumOhQJXZfugPDredyISyaFnqJLRsQWkwD19W1JQKxRwiO4hcCV8rNDbdtIjE4ve /6kg==
Received: by 10.224.97.132 with SMTP id l4mr24991166qan.15.1337371164430; Fri, 18 May 2012 12:59:24 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id i7sm22784250qae.20.2012.05.18.12.59.22 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 May 2012 12:59:23 -0700 (PDT)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <m2zk955o4y.wl%randy@psg.com>
Date: Fri, 18 May 2012 15:59:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <5938DB68-DE55-40C5-988F-F16BB5847515@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <B9880F32-9540-417F-B340-5C3AC7B374B5@gmail.com> <m2zk955o4y.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF list 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 May 2012 19:59:25 -0000

On May 18, 2012, at 2:40 PM 5/18/12, Randy Bush wrote:

>> Dave Crocker's suggestion would minimize the number of words taken out
>> of our vocabulary:
> 
> for a language other than english.
> 
>> In addition to "clear and concise" we need precision and avoidance of
>> ambiguity.
> 
> wonderful rofl.  thanks.  mind if i put that in my public quotes file?

Always happy to entertain, even if unintentionally...

- Ralph

> 
> randy


From shanna@juniper.net  Fri May 18 15:10:49 2012
Return-Path: <shanna@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 CE2AB21F85F1; Fri, 18 May 2012 15:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.11
X-Spam-Level: 
X-Spam-Status: No, score=-105.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 oH4uhsP9CzOK; Fri, 18 May 2012 15:10:49 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 816F321F85ED; Fri, 18 May 2012 15:10:48 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT7bI5/jbxGJGM/l/+O0I/EVnjsyuF7+l@postini.com; Fri, 18 May 2012 15:10:49 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 18 May 2012 15:10:21 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 18 May 2012 18:10:20 -0400
From: Stephen Hanna <shanna@juniper.net>
To: Sam Hartman <hartmans-ietf@mit.edu>, "emu@ietf.org" <emu@ietf.org>
Date: Fri, 18 May 2012 18:10:19 -0400
Subject: Updated secdir review of draft-ietf-emu-chbind-15.txt
Thread-Topic: Updated secdir review of draft-ietf-emu-chbind-15.txt
Thread-Index: Ac0yBUYMaadU2/1USxesme5e9bVqqQDOFijw
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net>
References: <20120514190642.11168.14882.idtracker@ietfa.amsl.com> <tslvcjy37fi.fsf@mit.edu>
In-Reply-To: <tslvcjy37fi.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2012 22:10:49 -0000

The changes in draft-ietf-emu-chbind-15.txt satisfactorily address
almost all of the comments in my April 13, 2012 secdir review. I do
have one remaining substantive comment on this latest draft and two
non-substantive ones.

Substantive Comment
-------------------

The last paragraph of section 9.1 points out a security problem
with implementing channel bindings using EAP tunnel methods. If
the EAP tunnel method terminates on the authenticator, the channel
bindings can easily be defeated by the authenticator. While that's
true, nobody terminates the EAP tunnel method on the authenticator
today. In the EAP model, the authenticator is not trusted so
terminating the EAP tunnel method on the authenticator is a bad
idea for many reasons. For example, the authenticator would then
have the ability to bypass protected result indications and to
bypass all the cryptographic protections provided by the tunnel.
Sometimes there is value in having the inner and outer methods
terminate on different servers but both servers must be trusted.
The authenticator is not. So there is no big security hole here,
unless you have already opened an enormous security hole. It's
ironic that this document which attempts to close vulnerabilities
caused by malicious authenticators ends up subtly suggesting that
people open a much larger vulnerability!

I would recommend deleting the end of this paragraph, starting
with the sentence that starts "Even when cryptographic binding".
If you choose to keep this strange text, I suggest that you at
least note that terminating an EAP tunnel method on the
authenticator is unusual. For example, you could add a
parenthetical comment like "(rare)" after the clause "if the
outer method tunnel terminates on the authenticator".

Non-Substantive Comments
------------------------

In the first paragraph of section 3, an extraneous numeral 3 was
somehow added to the end of the second sentence.

T. Charles Clancy's address in the Authors' Addresses section
now reads:

   T. Charles Clancy
   Virginia Tech
   Virginia Tech
   Arlington, VA  22203
   USA

The duplication of Virginia Tech should be removed from
this address.

I appreciate the hard work of the document editors to address
my many earlier comments. I hope that these new comments will
also be useful.

Thanks,

Steve


From randy@psg.com  Fri May 18 15:54:57 2012
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 EF25321F8501 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 15:54:57 -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 Bt-XfGzefGYd for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 15:54:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A713F21F8463 for <ietf@ietf.org>; Fri, 18 May 2012 15:54:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SVW4W-0004pv-J0; Fri, 18 May 2012 22:54:56 +0000
Date: Sat, 19 May 2012 07:54:55 +0900
Message-ID: <m2sjex5ccg.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <5938DB68-DE55-40C5-988F-F16BB5847515@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <B9880F32-9540-417F-B340-5C3AC7B374B5@gmail.com> <m2zk955o4y.wl%randy@psg.com> <5938DB68-DE55-40C5-988F-F16BB5847515@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF list 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 May 2012 22:54:58 -0000

my wife says the purpose of tourists (we in japan) is to amuse the
natives

randy

From brian.e.carpenter@gmail.com  Fri May 18 23:48:55 2012
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 B8A3721F8661 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 n3SOPPe4ypxR for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:48:55 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 138FA21F8670 for <ietf@ietf.org>; Fri, 18 May 2012 23:48:54 -0700 (PDT)
Received: by werb13 with SMTP id b13so1090078wer.31 for <ietf@ietf.org>; Fri, 18 May 2012 23:48: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=vQt3OCwEv2CC6fDj0iag2PwaMYG3TMRJ57iycCb2Cpo=; b=QJ/T8RvpWKjCIbGx2XeAzrb+EnOtMsDEwhBNYt6n2O4uip0txhVnQOy5GXScts/Tu6 L7rLiIQqa3xf/nYi6/F0QBBJTKop3Y6Z79T8XGvNuD05x9vgb1cmTufCoZomx6KdgdS/ j0BS6PAyKp7tKgNOKHR0+WfbGLShd0WFCFC+XNgTi5sGaGVYqnrvpDKe2rYs0Ugqm91c TeCOhaJnRdTiffjcIIXOzZh3i6fVLgMDlbRbdA3zAkHHmvxdGFQ/7+RVYVP1Px5TkCmM YVKpXKP35a8WU30TfMIobFK8vUQ1utnar/YGiMQ5JhcjZGhUyGnKf4i3CKrFo06vfnoj Fppw==
Received: by 10.180.100.2 with SMTP id eu2mr8112175wib.1.1337410134233; Fri, 18 May 2012 23:48:54 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-67.as13285.net. [2.102.216.67]) by mx.google.com with ESMTPS id fm1sm6749344wib.10.2012.05.18.23.48.52 (version=SSLv3 cipher=OTHER); Fri, 18 May 2012 23:48:53 -0700 (PDT)
Message-ID: <4FB7424C.8070508@gmail.com>
Date: Sat, 19 May 2012 07:48:44 +0100
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: Randy Bush <randy@psg.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<01OFJXXZJB2I0006TF@mauve.mrochek.com>	<3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>	<01OFK8GNXASC0006TF@mauve.mrochek.com>	<384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com>
In-Reply-To: <m2396x73az.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF list 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, 19 May 2012 06:48:55 -0000

On 2012-05-18 19:27, Randy Bush wrote:
>> I recommend an errata to RFC 2119: "These words MUST NOT appear in a
>> document in lower case."
> 
> first, that is not an erratum, it is a non-trivial semantic change.
> 
> second, do we not already have enough problems being clear and concise
> without removing common words from our language?

May I say "+1"?

Very seriously - after all that has been said on this thread, I see
no reason to change anything. Authors and the RFC Editor can create
unambiguous language with a bit of thought. There is an erratum
in 2119 ("NOT RECOMMENDED" is not mentioned in the recommended
boilerplate) but we know how to deal with that.

A strong argument against updating RFC 2119 is the fact that it's
one of the most cited RFCs *outside* the RFC series. Several other
SDOs commonly cite RFC 2119 and use its terminology. If it was
a protocol, we'd be proud of its success, but that makes changing
it a source of unintended consequences.

   Brian

From randy@psg.com  Fri May 18 23:54:30 2012
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 0F76E21F86A4 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:54:30 -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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Md5LttrBHyX0 for <ietf@ietfa.amsl.com>; Fri, 18 May 2012 23:54:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A871321F869A for <ietf@ietf.org>; Fri, 18 May 2012 23:54:29 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SVdYa-0007Xs-85; Sat, 19 May 2012 06:54:28 +0000
Date: Sat, 19 May 2012 15:54:26 +0900
Message-ID: <m2fwawek4d.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <4FB7424C.8070508@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF list 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, 19 May 2012 06:54:30 -0000

> Very seriously - after all that has been said on this thread, I see
> no reason to change anything.

the discussion has incited me to change the boiler plate which i will
use henceforth

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English words, without any normative meaning.

randy

From cabo@tzi.org  Sat May 19 00:28:25 2012
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 56E7621F8699 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 00:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACmGCdpesx6I for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 00:28:24 -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 7DF3921F8694 for <ietf@ietf.org>; Sat, 19 May 2012 00:28:24 -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.3/8.14.3) with ESMTP id q4J7SDmV026786; Sat, 19 May 2012 09:28:13 +0200 (CEST)
Received: from [127.0.0.1] (fido.informatik.uni-bremen.de [134.102.218.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5B04B4E6; Sat, 19 May 2012 09:28:13 +0200 (CEST)
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4FB7424C.8070508@gmail.com>
Date: Sat, 19 May 2012 09:28:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0491704F-FA53-4E98-8208-C420C825024D@tzi.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<01OFJXXZJB2I0006TF@mauve.mrochek.com>	<3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>	<01OFK8GNXASC0006TF@mauve.mrochek.com>	<384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF list 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, 19 May 2012 07:28:25 -0000

On May 19, 2012, at 08:48, Brian E Carpenter wrote:

> Very seriously - after all that has been said on this thread, I see
> no reason to change anything.=20

+1

This is one of those issues that is best addressed by *awareness*, not =
by new rules.

Gr=FC=DFe, Carsten


From cos@mip.polyamory.org  Sat May 19 12:39:14 2012
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381B721F8631 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 12:39: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 IMi+FfePcSq2 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 12:39:13 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id A2CFB21F8630 for <ietf@ietf.org>; Sat, 19 May 2012 12:39:13 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id DC78C10760; Sat, 19 May 2012 15:39:04 -0400 (EDT)
Date: Sat, 19 May 2012 15:39:04 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <20120519193904.GD335@mip.aaaaa.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FB7424C.8070508@gmail.com>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Cc: IETF list 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, 19 May 2012 19:39:14 -0000

As a reader of RFCs, I've come to expect that 2119 words are always
capitalized, and that when the same words appear in lowercase or mixed
case they're not being used in the 2119 sense.  This seems to be a de
facto standard, even though 2119 doesn't require it.  I'm in favor of
continuing with this standard since I think most readers of RFCs have
grown to expect it, but there doesn't seem to be a need to make any
change.

Two things I like:

 - Randy's new suggested boilerplate

 - Avoiding using 2119-like words in lowercase when other wording
 would work equally well, at the author's discretion.  That seems
 like a reasonable practice, but trying to define and enforce it
 would be far too much trouble and have silly unintended consequences.

So perhaps if Randy's new suggested boilerplate could be added as an
erratum to 2119, clearly labeled an optional suggestion, I think that
might be useful.  But don't change the rules.  2119 works well as is IMO.
  -- Cos

From lear@cisco.com  Sat May 19 13:19:40 2012
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 7FB4611E8088 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 13:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.599
X-Spam-Level: 
X-Spam-Status: No, score=-111.599 tagged_above=-999 required=5 tests=[AWL=-1.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 w2ZIxnrLDFOQ for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 13:19:40 -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 EE73B11E8080 for <ietf@ietf.org>; Sat, 19 May 2012 13:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=147; q=dns/txt; s=iport; t=1337458780; x=1338668380; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=Hb9UlMPWW6a2ZpN9HmNVNAn3YBBiOmYqgn20l5XUTG0=; b=IDBjvP2nB+8cQyWw1YAPrQ3DwCmDejCwgY2KmmcD7+Gf3TY1495x4ZZ+ b4U5j6aTNGT2gnAdzyNeoDM0e8OgsL7+IjqVtsg+JSLZMe3TCBTj7QB3K HdMyvgwLF1cItHWh1eRte92qZi/vGmgPVPzgz2jgNfPezGdrHm8xRhI8Y s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjgFAAMAuE+tJXG9/2dsb2JhbABFhS2GAqhcgQeCFQEBAQQSARBVEQsYAgIFFgsCAgkDAgECAUUTCAEBHodsnFSNFJIHgSaMDoIKgRQDlRuODIFkgms
X-IronPort-AV: E=Sophos;i="4.75,622,1330905600"; d="scan'208";a="84780111"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 19 May 2012 20:19:39 +0000
Received: from rtp-vpn5-1022.cisco.com (rtp-vpn5-1022.cisco.com [10.82.236.2]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q4JKJbMX005124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sat, 19 May 2012 20:19:38 GMT
Message-ID: <4FB80058.2080906@cisco.com>
Date: Sat, 19 May 2012 22:19:36 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>
In-Reply-To: <562A61B995B24BD854A4D154@[192.168.0.2]>
X-Enigmail-Version: 1.4.1
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 May 2012 20:19:40 -0000

On 5/16/12 3:59 PM, Barry Leiba wrote:
>
> It's probably worth having a discussion of all of that

Did you envision THIS much discussion?

From randy@psg.com  Sat May 19 14:45:30 2012
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 B699F11E8073 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 14:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 b8PgWgwZxZ74 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 14:45:30 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 66F3921F853E for <ietf@ietf.org>; Sat, 19 May 2012 14:45:30 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SVrSr-000E9A-Is; Sat, 19 May 2012 21:45:29 +0000
Date: Sun, 20 May 2012 06:45:28 +0900
Message-ID: <m2396vetfr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ofer Inbar <cos@aaaaa.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <20120519193904.GD335@mip.aaaaa.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com> <20120519193904.GD335@mip.aaaaa.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF list 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, 19 May 2012 21:45:30 -0000

> So perhaps if Randy's new suggested boilerplate could be added as
> an erratum to 2119

yikes!  i did not intend that.  and i think folk need to look up
'erratum', think trivial bug fix.  this would be a change.  and i do
not have the hubris to change sob's immortal words :)

i think the practical problem my text may hit is id-nits and id nit
pickers.  two friends have warned me that i may have fun getting a
draft through the iesg with it, and that i can look forward to
silliness.  my read of the iesg is that they have been taking a
higher road these years.  but we'll see.

randy

From yaakov_s@rad.com  Sat May 19 23:26:01 2012
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A689521F85D8 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 23:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.998
X-Spam-Level: 
X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, UNPARSEABLE_RELAY=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 YXlV113GuH+g for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 23:26:01 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id 73FF921F85B6 for <ietf@ietf.org>; Sat, 19 May 2012 23:25:57 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 20 May 2012 09:04:22 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sun, 20 May 2012 09:25:53 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Ole Jacobsen <ole@cisco.com>
Subject: RE: RFC 2119 terms, ALL CAPS vs lower case
Thread-Topic: RFC 2119 terms, ALL CAPS vs lower case
Thread-Index: AQHNM2wjjUWCYSP1L0KRqAIgPef6jpbMSjoAgAABbICAAEcgbv//7bWAgAACcYCAAAajAIAFrxsg
Date: Sun, 20 May 2012 06:25:52 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9043CDE8A@EXRAD5.ad.rad.co.il>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com>
In-Reply-To: <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090204.4FB88E72.00C8,ss=1,fgs=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: Sun, 20 May 2012 06:26:01 -0000

> And of course if we had a slightly richer publication format we could=20
> use, oh, say, underline, bold, italics and maybe even a special font=20
> for normative terms, but I guess I am dreaming decades ahead...

I was waiting to see if someone was going to bring this up.

In Roman law, the way you capitalized something in a document could have si=
gnificant consequences,
for example, incorrect use of Capitis Diminutio could change you from a fre=
e person into a slave!

OTOH, the Uniform Commercial Code requires certain terms be rendered "consp=
icuous",
which may be accomplished though capitalization, or using bold face, or a l=
arger font, or contrasting color, etc.

The intervening 2000 years enabled the UCC to exploit more modern typesetti=
ng technologies.

But the IETF is still living in Roman times.

Y(J)S


From ron.even.tlv@gmail.com  Sat May 19 23:50:33 2012
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 5037D21F85A0; Sat, 19 May 2012 23:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=-0.628, BAYES_20=-0.74, 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 AGoQSIC09+Ve; Sat, 19 May 2012 23:50:32 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5B421F8599; Sat, 19 May 2012 23:50:26 -0700 (PDT)
Received: by wibhj8 with SMTP id hj8so1109658wib.13 for <multiple recipients>; Sat, 19 May 2012 23:50:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=Kr/BjTgAlXXRfz34R3lHws69uWnBSH+D1pf2vJev9SA=; b=rLU2A6zlMO/uZFd56bV4+oFGAKLn3Yt786sw0pj1Fb5TBULLo+VsZhIJmRA0h3OWgp FCPPQ+3OOkjtnc4mKJ4hhcjSl4xag2pE//l7sFhf6Twx+Fl/47ur59jgqNTcMQuqzzng /1xe1ty5cKU9OgZjSRxk0Qvjpt9aqWd/SZbee+QUq5EbqWKjguebiqsmfKEAIX4Wl9C1 T2oQlIUK1fkVgRcp1PtLPJLrt3cTK77I0ytJQq2YkOxUR6T9peR0BrP5sA/9Xkms34xE DykiMFbK5VBx1S/7rqiW0PB6p8Nrxg6V1Otxd14T1zjG+7uu+33MoOXxF3ahcALVdjnh VZrA==
Received: by 10.180.79.166 with SMTP id k6mr14743884wix.8.1337496626274; Sat, 19 May 2012 23:50:26 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id j3sm24030073wiw.1.2012.05.19.23.50.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 19 May 2012 23:50:25 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-melnikov-smtp-priority.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-melnikov-smtp-priority-13
Date: Sun, 20 May 2012 09:47:52 +0300
Message-ID: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CD366D.A19A94D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac02VHodmFEqqIDRT6GfHoZ8rqHIpg==
Content-Language: en-us
Cc: 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, 20 May 2012 06:50:33 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0028_01CD366D.A19A94D0
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-melnikov-smtp-priority-13

Reviewer: Roni Even

Review Date:2012-5-20

IETF LC End Date: 2012-5-28

IESG Telechat date:

 

Summary: This draft is ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

 

 

 

Nits/editorial comments:

 

1.       MUA is used but not expanded.

 

 

 


------=_NextPart_000_0028_01CD366D.A19A94D0
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 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: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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</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"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-melni=
kov-smtp-priority-13<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;5&#8211;20<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: 2012&#8211;5&#8211;28<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 a standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=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"'>Nits/editor=
ial comments:<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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>MUA is =
used but not expanded.<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><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0028_01CD366D.A19A94D0--


From brian.e.carpenter@gmail.com  Sat May 19 23:54:07 2012
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 8DDBA21F8619 for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 23:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 0v3HZKTkTsXP for <ietf@ietfa.amsl.com>; Sat, 19 May 2012 23:54:07 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id D597321F8618 for <ietf@ietf.org>; Sat, 19 May 2012 23:54:06 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so1125675wib.13 for <ietf@ietf.org>; Sat, 19 May 2012 23:54:06 -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=JFE7JPZihwOC2oC2t8L54mvYfbQV4RjjNvNIO8kz4js=; b=MUqblX2wwewKpb96y+v7nU+PEfMFHmKMmu6N4LmC4pzqKUywMIDUHKa6a363YWVSdD 04iTiIh6VBcWrsHyxIl478BT9UiNtZV+ivdUodCHdCv06H+dkkUBEGzgQLt5PwmVSJiY pU+b0yLrxqECybUzgXBQtSGAttVarcVKvdZhruU+JWFgF5OJHNmSvSLjh9f0p3wIqtfm L9dF/TWXHTa87hqYfa5npb99d8VRFHQDmdv3cnN3WSe1Q+i1j2i2Ric1VVioKRDM86lW F2RtSqt2HoTj9WJbSbBUEr/NIGXfsvUAXyYW0Sbxu9tOiWIk1BbbOG5biLFQtO/cV9UI 74Ag==
Received: by 10.180.109.197 with SMTP id hu5mr14782996wib.8.1337496845998; Sat, 19 May 2012 23:54:05 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-62.as13285.net. [2.102.217.62]) by mx.google.com with ESMTPS id ei4sm15841716wid.5.2012.05.19.23.54.04 (version=SSLv3 cipher=OTHER); Sat, 19 May 2012 23:54:05 -0700 (PDT)
Message-ID: <4FB89502.3090702@gmail.com>
Date: Sun, 20 May 2012 07:53:54 +0100
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: Ofer Inbar <cos@aaaaa.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com> <20120519193904.GD335@mip.aaaaa.org>
In-Reply-To: <20120519193904.GD335@mip.aaaaa.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF list 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 May 2012 06:54:07 -0000

On 2012-05-19 20:39, Ofer Inbar wrote:
...

>  But don't change the rules.  2119 works well as is IMO.

Just to be clear about the current rules, 2119 makes it clear that
upper case keywords are optional ("These words are often capitalized").
Indeed, numerous standards track documents don't use them.

    Brian

From McQuilWP@pobox.com  Sun May 20 00:39:51 2012
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1631221F8593 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 00:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeRyW4C97nDQ for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 00:39:50 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED4F21F856F for <ietf@ietf.org>; Sun, 20 May 2012 00:39:50 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 58407710D; Sun, 20 May 2012 03:39:49 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=z8kXUy2kyzpy vsv/aFHd4k19DYE=; b=oARFK6uPXf3Is5aZ2bvXiBosxNAwrwCxXs29rPb1ymwo 1MOvzax2fk7uRYYTDhSLJjVABQhlkN58h9PGH94hSwyIatvRYHQuxIPevytUGFjj +2jnOZaI78N/sbjgCWT4jRzEwPp0h8yOjVNUm5fsC8tKtqVjHDP42QFxGJkqFEg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=cPQDt2 /5MV89B+W8fvw1ct3T3AZzYOWMz1yi9yMdM086a2r6lKO2wmnEY99ey0oVNdDtNx WamEefE8PKAjl9bnvwu2MxMWDT5J/WOukiVZcqKiFQDzt4YI4e5w648stKU9A/AT CPio3ZjDJ8oky76pX9qt/uP6VNMYppJPk/VtE=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 4F156710C; Sun, 20 May 2012 03:39:49 -0400 (EDT)
Received: from [192.168.0.3] (unknown [68.107.110.211]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 856AC7108; Sun, 20 May 2012 03:39:48 -0400 (EDT)
Date: Sun, 20 May 2012 00:39:46 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <978859982.20120520003946@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <4FB89502.3090702@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com> <20120519193904.GD335@mip.aaaaa.org> <4FB89502.3090702@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: FA6BDE14-A24E-11E1-B74D-FC762E706CDE-02871704!b-pb-sasl-quonix.pobox.com
Cc: Ofer Inbar <cos@aaaaa.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 07:39:51 -0000

On Sat, 2012-05-19, Brian E Carpenter wrote:
> On 2012-05-19 20:39, Ofer Inbar wrote:
> ...

>>  But don't change the rules.  2119 works well as is IMO.

> Just to be clear about the current rules, 2119 makes it clear that
> upper case keywords are optional ("These words are often capitalized").
> Indeed, numerous standards track documents don't use them.

I do not agree that 2119 is "clear" on this topic. I read the
beginning of the first paragraph of the Abstract as:

Some background motivation:

  In many standards track documents several words are used to
  signify the requirements in the specification. These words are
  often capitalized.

A new proposal:

  This document defines these words as they should be interpreted
  in IETF documents.

Thus, it is defining a new, unified convention for documenting 
requirements language.

And then the boilerplate shows all of the requirement words in 
uppercase, obviously convincing a lot of people that the new 
standard is to use them in uppercase when their meaning is 
normative.

As one example, in section 6 the text reads:

   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.

There is one instance of "MUST" and two of "must" in this 
paragraph. I would observe that the "MUST" is used to define a 
requirement upon RFC texts, but the two "must"s are used to 
try to affect the motivation of the humans writing the RFC texts.

There are examples elsewhere in 2119 of the use of these words in
lowercase that seem NOT be used in a normative way.

If anything I would evaluate the evidence to indicate that the 
distinction of case *was intended* to be meaningful.

-- 
Bill McQuillan <McQuilWP@pobox.com>


From stephen.farrell@cs.tcd.ie  Sun May 20 03:29:17 2012
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 C902621F8512 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 03:29:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cb9BBEbhfytU for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 03:29:17 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 1CFE121F84E6 for <ietf@ietf.org>; Sun, 20 May 2012 03:29:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 3812217153E; Sun, 20 May 2012 11:29:13 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1337509752; bh=OdrTBhSyDBNqWM prbjRewcaNuoUnCDhtYvJ9j+HIkQ8=; b=6lQ1kVfmgkGf4D+/NR0LYI8Uckhk3e yVMoIyEOxv1SAUpKk2onhddFRaOvHAk7zLxvdJm2pyuFxDqesppoRp3RAxIMgqny XjsvplJ/3KJ9D0u6emuLPLL09aAYT0YUEM2XpsqL+/h8JftsFHUAVX9PnqoRl6h1 kiQwkxA+clTrnPvII0NqBh5xwY6Kf0MaLX7W/nWDf7jtgf/PlmEOkq7llBO7cs8I vuQQKcTVvuBy0njO3djVNPyNDgBDAvLbHKnb6/hQg+nltyFXeWqSCluM8DeCl+eO X8GJLbucopZvlvn509q0HykSsloLni12NtO1M4QsxEnoPgO739Okflrw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id YXfY1SVCZ-aP; Sun, 20 May 2012 11:29:12 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.42.20.120]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 2768917153D; Sun, 20 May 2012 11:29:09 +0100 (IST)
Message-ID: <4FB8C775.4000305@cs.tcd.ie>
Date: Sun, 20 May 2012 11:29:09 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <07F7D7DED63154409F13298786A2ADC9043CDE8A@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9043CDE8A@EXRAD5.ad.rad.co.il>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ole Jacobsen <ole@cisco.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 May 2012 10:29:17 -0000

On 05/20/2012 07:25 AM, Yaakov Stein wrote:
> But the IETF is still living in Roman times.

If you want a discussion as to whether we should live
in Times Roman, that'd be best on the rfc editor list.
(Sorry, couldn't resist;-)

S.


From hsantos@isdg.net  Sun May 20 07:40:06 2012
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 8B17B21F849A for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 07:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.246
X-Spam-Level: 
X-Spam-Status: No, score=-100.246 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 r2KG6hBH+wmU for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 07:40:06 -0700 (PDT)
Received: from groups.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B0D5D21F8467 for <ietf@ietf.org>; Sun, 20 May 2012 07:40:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1345; t=1337524794; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Nz0uTTzDIavUNkNk6ONm0aKTi3Q=; b=Skj8tYKtbHu1hfbfBiXP rswSvY3CNz4zyb3/QfJU92LWw36Tt1ZK3EqgWbjXrgNyvI/gaFaWZ3yiCnQYFDy0 7cLF1XmHfzQBpzRtXlIW5JJTQnDz9INxIFPB141oDc1BIsrP5bSsCfq9MctYA6Ve mcNRQwsod8EtiC1DWk/7VSU=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 20 May 2012 10:39:54 -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 v6.4.454.1) with ESMTP id 2136617389.90.3244; Sun, 20 May 2012 10:39:53 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1345; t=1337524765; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=u1Oj4Yi jjtDgIDHWlyTqHscRLsI5c15tbjW1qRAsK9c=; b=Bjvjc49FYswahb2LdagH7Fw 6ybH3kgOq1Ev2XnLbJlAI0ZgcWBMAumw2cLzEm9qynn0HIbPMtvLzdxUpo3TvlB5 8SvM4RI48jeHff3qG0I80Uhi6/Mw1KLeelscYAkrlIPicGfYzrjH0FDL5uMVwogw 43xPNcB2v6vWr8xcK2Tg=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Sun, 20 May 2012 10:39:25 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 2735497581.8505.4176; Sun, 20 May 2012 10:39:24 -0400
Message-ID: <4FB9024F.6060605@isdg.net>
Date: Sun, 20 May 2012 10:40:15 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF list discussion <ietf@ietf.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]>	<m262bwchr9.wl%randy@psg.com>	<01OFJXXZJB2I0006TF@mauve.mrochek.com>	<3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com>	<01OFK8GNXASC0006TF@mauve.mrochek.com>	<384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com>	<m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com>	<20120519193904.GD335@mip.aaaaa.org> <4FB89502.3090702@gmail.com>
In-Reply-To: <4FB89502.3090702@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2012 14:40:06 -0000

Brian E Carpenter wrote:
> On 2012-05-19 20:39, Ofer Inbar wrote:
> ...
> 
>>  But don't change the rules.  2119 works well as is IMO.
> 
> Just to be clear about the current rules, 2119 makes it clear that
> upper case keywords are optional ("These words are often capitalized").
> Indeed, numerous standards track documents don't use them.

Curious, does any "fixes" of 2119, will fix a document or set of 
documents?  automatically, unchanged?

It just seems that the docs themselves need the fixing and desires to 
change meanings in 2119 is to correct past mistakes or perhaps 
intentional relaxations wanting to be stronger today.

Here is one example where a conflict is often raised that "Local 
Policy" Rules.

    The Checking Software can choose between A or B.
    It is RECOMMENDED that C is used.

A is not defined, B has 2119 language.  However, although it is not 
written, C is only possible if A is used.  B preempts, short-circuits C.

A possible correction would based on Implementation vs Deployment, two 
different readers getting the same understanding:

    The Implementation MUST offer A and B and C.
    The Deployment CAN choose between A or B.
    The Deployment SHOULD use C when the Deployment uses A.

I would use a MUST in the last one, but that will change the original 
RECOMMENDED spec item.

-- 
HLS



From john-ietf@jck.com  Sun May 20 09:29:35 2012
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 5419721F8604 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 09:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnuYU1gmhA0N for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 09:29:34 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C925021F85D3 for <ietf@ietf.org>; Sun, 20 May 2012 09:29:34 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SW8v7-000KRl-MA; Sun, 20 May 2012 12:23:49 -0400
Date: Sun, 20 May 2012 12:29:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ofer Inbar <cos@aaaaa.org>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <C434362C680B405F6D53A6AB@PST.JCK.COM>
In-Reply-To: <4FB89502.3090702@gmail.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com>	<20120519193904.GD335@mip.aaaaa.org> <4FB89502.3090702@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 list 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 May 2012 16:29:35 -0000

--On Sunday, May 20, 2012 07:53 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 2012-05-19 20:39, Ofer Inbar wrote:
> ...
> 
>>  But don't change the rules.  2119 works well as is IMO.
> 
> Just to be clear about the current rules, 2119 makes it clear
> that upper case keywords are optional ("These words are often
> capitalized"). Indeed, numerous standards track documents
> don't use them.

Brian,

I've been trying really hard to avoid this discussion, but I
think the above is misleading.

In recent years, various IESG members have insisted that any
IETF Track document that contains anything approximating
conformance language include the 2119 reference and whatever the
strict interpretation of the week is about caps, etc.  As Randy
suggests, there have been signs of more nuance in the last IESG
or two, but...

The same problem applies to the other issue with 2119, which is
that we have history for at least two different interpretations
of those words, the ones in 2119 that are interpreted as
"necessary for interoperability" and the ones in, e.g.,
1122/1123 (Section 1.3.2 in the latter) which are "requirements
of the specification" without binding those requirements to a
particular reason.  From my point of view, the other difficulty
with treating 2119 like Received Wisdom and a set of absolute
requirements is that the interoperability criterion often makes
no sense for what are perfectly reasonable requirements.  As an
example drawn from 1123, a specification might reasonably say
"this option MUST be configurable" because it is necessary to
make things work in a plausible way even if that statement
cannot be explicitly linked to "won't interoperate unless it
does".   But again, in recent years, some IESG members (and
others) have insisted that only the 2119 definitions are
permitted.

The combination of the two is known in some quarters as writing
technically poor or deficient specs in the interest of clear
conformance to procedures.  At least historically, that was a
trap the IETF tried to avoid.

    john


    




From brian.e.carpenter@gmail.com  Sun May 20 11:00:20 2012
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 9BCAF21F85E5 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 11:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.67
X-Spam-Level: 
X-Spam-Status: No, score=-101.67 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 FqkLpXJXE+yo for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 11:00:20 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D111F21F856C for <ietf@ietf.org>; Sun, 20 May 2012 11:00:19 -0700 (PDT)
Received: by werb13 with SMTP id b13so1794515wer.31 for <ietf@ietf.org>; Sun, 20 May 2012 11:00:19 -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=eC0dvuxeoqbuaDtbNVACDLz95fabMjBm+jQ6+Py9uao=; b=n09jw/ARzrhKoJBQc1SA++U/HLiloZv6j4OOpHQFH4rQlYMzBHapsQTkSf4VwNxM8q 17d0WfqxDStPBB0y5A74B5xVTNST7Nr0hkwl7pcEc3R0yT5ZTbsAuaq+5wvu5JmLlB8/ N307BO47nkQvO8Igf6q3+N559wJfPm3LniHX5Y+g+aio5VbT+uQfIZnIiXhhKymjAwIg 6k4QIg/XubF98tqvmkuBZpCHheVbWDmK2wx0A6rtyEIGH1dgIKket0zPx+OLL2NxHPyi KRm9vkV+k/lENNv4Sh/dEDUidBnd8LfQXRa4pvUQ9mB+QKJwGGTeesI43DaUNSQ/RjEm Byxg==
Received: by 10.180.83.168 with SMTP id r8mr18199478wiy.22.1337536818907; Sun, 20 May 2012 11:00:18 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-62.as13285.net. [2.102.217.62]) by mx.google.com with ESMTPS id eb8sm19770927wib.11.2012.05.20.11.00.16 (version=SSLv3 cipher=OTHER); Sun, 20 May 2012 11:00:17 -0700 (PDT)
Message-ID: <4FB9312D.7020105@gmail.com>
Date: Sun, 20 May 2012 19:00:13 +0100
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: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <m262bwchr9.wl%randy@psg.com> <01OFJXXZJB2I0006TF@mauve.mrochek.com> <3AAB0DB9-5E51-4117-B2BB-851700FD9CDC@gmail.com> <01OFK8GNXASC0006TF@mauve.mrochek.com> <384732C7-C0D6-4D00-B1A8-2B9B86587264@gmail.com> <m2396x73az.wl%randy@psg.com> <4FB7424C.8070508@gmail.com>	<20120519193904.GD335@mip.aaaaa.org> <4FB89502.3090702@gmail.com> <C434362C680B405F6D53A6AB@PST.JCK.COM>
In-Reply-To: <C434362C680B405F6D53A6AB@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ofer Inbar <cos@aaaaa.org>, IETF list 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 May 2012 18:00:20 -0000

On 2012-05-20 17:29, John C Klensin wrote:
> 
> --On Sunday, May 20, 2012 07:53 +0100 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2012-05-19 20:39, Ofer Inbar wrote:
>> ...
>>
>>>  But don't change the rules.  2119 works well as is IMO.
>> Just to be clear about the current rules, 2119 makes it clear
>> that upper case keywords are optional ("These words are often
>> capitalized"). Indeed, numerous standards track documents
>> don't use them.
> 
> Brian,
> 
> I've been trying really hard to avoid this discussion, but I
> think the above is misleading.

My personal preference is to use RFC 2119, but if the IESG made
that into a rule without community consensus, I think it would
be wrong.

> 
> In recent years, various IESG members have insisted that any
> IETF Track document that contains anything approximating
> conformance language include the 2119 reference and whatever the
> strict interpretation of the week is about caps, etc.  As Randy
> suggests, there have been signs of more nuance in the last IESG
> or two, but...
> 
> The same problem applies to the other issue with 2119, which is
> that we have history for at least two different interpretations
> of those words, the ones in 2119 that are interpreted as
> "necessary for interoperability" and the ones in, e.g.,
> 1122/1123 (Section 1.3.2 in the latter) which are "requirements
> of the specification" without binding those requirements to a
> particular reason.  From my point of view, the other difficulty
> with treating 2119 like Received Wisdom and a set of absolute
> requirements is that the interoperability criterion often makes
> no sense for what are perfectly reasonable requirements.  As an
> example drawn from 1123, a specification might reasonably say
> "this option MUST be configurable" because it is necessary to
> make things work in a plausible way even if that statement
> cannot be explicitly linked to "won't interoperate unless it
> does".   But again, in recent years, some IESG members (and
> others) have insisted that only the 2119 definitions are
> permitted.
> 
> The combination of the two is known in some quarters as writing
> technically poor or deficient specs in the interest of clear
> conformance to procedures.  At least historically, that was a
> trap the IETF tried to avoid.

Yes, it would be sad if the IETF were no longer to allow itself to
apply common sense rather than rules.

   Brian

> 
>     john
> 
> 
>     
> 
> 
> 
> 

From bortzmeyer@nic.fr  Sun May 20 12:43:10 2012
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 E065F21F85FC for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 12:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.111
X-Spam-Level: 
X-Spam-Status: No, score=-101.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 MoB7ARxMeVFC for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 12:43:10 -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 46A9621F85FB for <ietf@ietf.org>; Sun, 20 May 2012 12:43:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 84A083B3AF; Sun, 20 May 2012 19:43:08 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 3F1D3190876; Sun, 20 May 2012 21:41:40 +0200 (CEST)
Date: Sun, 20 May 2012 21:41:40 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Message-ID: <20120520194140.GA20228@sources.org>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info> <5040_1337541981_4FB9455B_5040_14884_1_4FB3C271.6040902@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5040_1337541981_4FB9455B_5040_14884_1_4FB3C271.6040902@viagenie.ca>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
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 May 2012 19:43:11 -0000

On Wed, May 16, 2012 at 11:06:25AM -0400,
 Simon Perreault <simon.perreault@viagenie.ca> wrote 
 a message of 12 lines which said:

> >One dreams of a period in which precision and elegance were not
> >mutually exclusive properties.
> 
> You mean when French was the dominant language?

Nice troll. Let me amend it: we now have languages which were
conceived for writing precisely what you mean (not too much ambiguity,
not too little). Lojban <http://en.wikipedia.org/wiki/Lojban> is the
best known. I do not expect IETF to adopt it for RFCs (despite the
imperfections of English) but I regret it. This would give me the push
I need to really learn Lojban.


From petithug@acm.org  Sun May 20 13:37:03 2012
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 D84DE21F8575 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 13:37:03 -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 FSXW2cqLtmOc for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 13:37:03 -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 5599D21F8573 for <ietf@ietf.org>; Sun, 20 May 2012 13:37:02 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "petithug", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id E33D32151B; Sun, 20 May 2012 20:36:59 +0000 (UTC)
Message-ID: <4FB955EA.7090306@acm.org>
Date: Sun, 20 May 2012 13:36:58 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info> <5040_1337541981_4FB9455B_5040_14884_1_4FB3C271.6040902@viagenie.ca> <20120520194140.GA20228@sources.org>
In-Reply-To: <20120520194140.GA20228@sources.org>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2012 20:37:04 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/20/2012 12:41 PM, Stephane Bortzmeyer wrote:
> On Wed, May 16, 2012 at 11:06:25AM -0400, Simon Perreault
> <simon.perreault@viagenie.ca> wrote a message of 12 lines which said:
> 
>>> One dreams of a period in which precision and elegance were not 
>>> mutually exclusive properties.
>> 
>> You mean when French was the dominant language?
> 
> Nice troll. Let me amend it: we now have languages which were conceived for
> writing precisely what you mean (not too much ambiguity, not too little).
> Lojban <http://en.wikipedia.org/wiki/Lojban> is the best known. I do not
> expect IETF to adopt it for RFCs (despite the imperfections of English) but
> I regret it. This would give me the push I need to really learn Lojban.
> 

Su'i pa

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPuVXnAAoJECnERZXWan7E4tEP/RmoX1ga8rxp9PdWgBKImiwu
HYrypdCvVndRLwrdnNiEBU0hx83gdOdFn6MhOImmVmY7LMwuL0sofkCI9Y4ZnN4G
X6yBHqji1aTbGHbliQK5p44pebqX7NKxtQa4msFCl+8BNQ6bezHmwK9CKyN7QMSc
zXaA8Y7wo0mlmgbPfCF93/cR3yXUEdKLOi3wZDwEP/jFX632cUS6n2am9mL/HZA9
qm8td0F0xRb/+oV0MMfzEb+MDDi2TptKDNDSXIqyCMsZ1qMyVUwVOCTUnJ7waxoX
dmHTZ5HhPFlOTY+aPYwSDzmqDfZa4jd1z6vUR5hZ2uLxLX6LD4/Bjc4W2E1yPWG+
BAZxGbwNchWwXlb1xzuCch4CVIXtuN7nGe3EPvNDLiWM50vSuFyOROsIaV1MgW0W
EVA0Vk68CvDu9O+OjCg83eDkFHi/OHloTqz0tx71xD5vtnPxrZWvR4hdIe/ffs4e
i/PKY2c0PItN9vA4hskDkoJoXQ1Drg91t9eoh4qJBulm4+YZ+Xv6SrmmnYJtzTzk
ezHeCzatkGB9FvXoyBkNnbZPLFDqgHuPDIdcV067x+r2Yqdywb04ECy/30Dy6HfH
BI//qYZEO3fbgbLYz7s8NpvuucP43OpsDIkUpp4p7CKss1LTVodiWd7aj5HdN8W2
QcmRb7nsKeR1jGigGIjR
=tiWK
-----END PGP SIGNATURE-----

From ynir@checkpoint.com  Sun May 20 15:44:46 2012
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 55D3921F853D for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 15:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_21=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 B7n04l3lVKp0 for <ietf@ietfa.amsl.com>; Sun, 20 May 2012 15:44:45 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3749721F853C for <ietf@ietf.org>; Sun, 20 May 2012 15:44:37 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (dlpgw.checkpoint.com [194.29.34.27]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4KMiW2d009134; Mon, 21 May 2012 01:44:32 +0300
X-CheckPoint: {4FB980AA-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 21 May 2012 01:44:30 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Date: Mon, 21 May 2012 01:44:25 +0300
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
Thread-Topic: RFC 2119 terms, ALL CAPS vs lower case
Thread-Index: Ac022h5pTrkZsUlVRt63yYIuig27ag==
Message-ID: <AD15F455-43B4-40F1-B492-E792A1720AE3@checkpoint.com>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net>	<20120516145655.GH26714@mail.yitter.info> <5040_1337541981_4FB9455B_5040_14884_1_4FB3C271.6040902@viagenie.ca> <20120520194140.GA20228@sources.org> <4FB955EA.7090306@acm.org>
In-Reply-To: <4FB955EA.7090306@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2012 22:44:46 -0000

On May 20, 2012, at 11:36 PM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> On 05/20/2012 12:41 PM, Stephane Bortzmeyer wrote:
>> On Wed, May 16, 2012 at 11:06:25AM -0400, Simon Perreault
>> <simon.perreault@viagenie.ca> wrote a message of 12 lines which said:
>>=20
>>>> One dreams of a period in which precision and elegance were not=20
>>>> mutually exclusive properties.
>>>=20
>>> You mean when French was the dominant language?
>>=20
>> Nice troll. Let me amend it: we now have languages which were conceived =
for
>> writing precisely what you mean (not too much ambiguity, not too little)=
.
>> Lojban <http://en.wikipedia.org/wiki/Lojban> is the best known. I do not
>> expect IETF to adopt it for RFCs (despite the imperfections of English) =
but
>> I regret it. This would give me the push I need to really learn Lojban.
>>=20
>=20
> Su'i pa

la lojban satci .ije la lojban na'e nolmle=

From marka@isc.org  Sun May 20 16:00:25 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D6621F85AF; Sun, 20 May 2012 16:00:25 -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 uJiqViHhWn7n; Sun, 20 May 2012 16:00:25 -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 E8A4221F8597; Sun, 20 May 2012 16:00:24 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id C7453C95AA; Sun, 20 May 2012 23:00:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f9c1:59cf:bb40:d253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 67889216C36; Sun, 20 May 2012 23:00:12 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 1E51A20C6C42; Mon, 21 May 2012 09:00:08 +1000 (EST)
To: ietf@ietf.org
From: Mark Andrews <marka@isc.org>
References: <20120517210122.19283.4263.idtracker@ietfa.amsl.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-bis-updates-18.txt> (Clarifications and Implementation Notes for DNSSECbis) to Proposed Standard
In-reply-to: Your message of "Thu, 17 May 2012 14:01:22 MST." <20120517210122.19283.4263.idtracker@ietfa.amsl.com>
Date: Mon, 21 May 2012 09:00:07 +1000
Message-Id: <20120520230008.1E51A20C6C42@drugs.dv.isc.org>
Cc: dnsext@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: Sun, 20 May 2012 23:00:25 -0000

I am repeating what I have said earlier during WGLS that Section
5.9., Always set the CD bit on Queries, contains bad advice on how
to set the CD bit.

The setting of CD make little difference if all the machines involved
are being correctly managed.  In that case all responses will
successfully validate.   However if there is a off path attacker
or one or more of the authorititive sources is returning stale
records the setting of CD is critical to ensuring that the ultimate
client can get the necessary records to ensure that the responses
it gets validate.

When there is a non-validating stub resolver all queries from that
client come in with CD=0 and a validating recursive server try
multiple authoritative servers until it gets a answer which validates
as secure or insecure, in other words it rejects answers from
attackers or from authoritative servers that return stale data.

Now take a validating validating stub resolver, if all queries from
that client come in the CD=1, them the recursive server returns the
answer from upstream immediately without filtering out bad responses.
If there is a off path attacker or if there is a stale authoritative
server then there is no way to ensure that the stub client will
ever get a answer that will validate.  It can continue to re-query
forever but there is no requirement for the recursive server to try
a different authoritative source or to wait for a valid response
from a authoritive source.

A similar problem arises when a recursive server is talking through
a second recursive server.  The server is no longer talking to the
authoritative servers directly and can't recover from getting answers
that do not validate.

Now sending CD=0 has its own set of problems caused by stale trust
anchors and clocks being out of sync so I am not suggesting that
we always send CD=0 queries either when incoming queries are sent
with CD=0.

Stub resolvers and recursive servers talking through other recursive
servers need to be prepared to ask queries with both CD=0 and CD=1.
CD=1 when talking to authoritative servers,  CD=0 when talking to
recursive servers falling back to CD=1 on SERVFAIL to handle stale
trust anchors and out of sync clocks unless the incoming query was
received with CD=1 in which case you MUST make CD=1 upstream queries.

Now if the recursive server is not validating, validating down
stream clients are vulnerable to all the failure modes caused by
sending CD=1 queries.  Fixing this will require protocol extensions
to pass trust anchors, and maybe current time, along with the query
and having on demand validation performed using those values in the
recursive server for this client.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From stpeter@stpeter.im  Mon May 21 08:16:44 2012
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 1C02121F867A; Mon, 21 May 2012 08:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5h6B9Xn9RDok; Mon, 21 May 2012 08:16:43 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1A23F21F8679; Mon, 21 May 2012 08:16:43 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F1FD540067; Mon, 21 May 2012 09:32:41 -0600 (MDT)
Message-ID: <4FBA5C59.4030102@stpeter.im>
Date: Mon, 21 May 2012 09:16:41 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Subject: Re: [mile] Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining	Extensions to IODEF) to Informational RFC
References: <20120516215321.9671.39664.idtracker@ietfa.amsl.com> <4FB46FA6.6060005@stpeter.im> <B06DB832-2813-4431-94B9-1F7B3492A595@tik.ee.ethz.ch>
In-Reply-To: <B06DB832-2813-4431-94B9-1F7B3492A595@tik.ee.ethz.ch>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: mile@ietf.org, The IESG <iesg-secretary@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, 21 May 2012 15:16:44 -0000

On 5/18/12 6:13 AM, Brian Trammell wrote:
> Hi, Peter, all,
> 
> Many thanks for the comments; 

And to you for following up.

> replies inline...

Likewise.

> On May 17, 2012, at 5:25 AM, Peter Saint-Andre wrote:
> 
>> On 5/16/12 3:53 PM, The IESG wrote:
>>> 
>>> The IESG has received a request from the Managed Incident
>>> Lightweight Exchange WG (mile) to consider the following
>>> document: - 'Guidelines for Defining Extensions to IODEF' 
>>> <draft-ietf-mile-template-04.txt> as Informational RFC
>> 
>> Although this document does no harm, I have my doubts that the
>> topic warrants publication of an RFC (and I say that as someone who
>> is defining some IODEF extensions for use on the XMPP network [1]).
>> Why would a simple wiki page [2] not suffice?
> 
> Indeed, it may; the WG decided we wanted something semi-permanent to
> give guidance to extension authors, especially given that we
> anticipated (and have had) significant participation from people with
> little or no previous involvement in the IETF. Whether that's an RFC
> or not is, but an RFC seemed the natural thing to do, as it is how
> things are published out of IETF WGs.
> 
> The previous version of this document _did_ need to be an RFC as it
> specified a change to the IANA XML registry requiring a Standards
> Action; this has been split out into draft-ietf-mile-iodef-xmlreg per
> AD guidance.

Thanks for the clarifications. I chatted about this I-D offlist with
Sean Turner and he explained that a bunch of folks who are not familiar
with the IETF might be coming here to define IODEF extensions, so I now
think that an Informational RFC could be useful.

>> If we decide than an RFC is needed, I have some more actionable
>> feedback...
>> 
>> 1. The document could be construed as assuming that IODEF
>> extensions will all be defined in Internet-Drafts, that extension
>> namespaces will be registered with IANA, and even that namespaces
>> will be of the form 'urn:ietf:params:xml:schema:iodef-*'. It might
>> be helpful to clarify the intended applicability of this document,
>> i.e., merely as helpful suggestions for authors of Internet-Drafts,
>> not truly as universally applicable guidelines for defining IODEF
>> extensions.
> 
> Hm. The document does indeed assume that extensions to IODEF are
> defined in Internet-Drafts, that extension namespaces will be
> registered with IANA, and that those namespaces be of the described
> form; it makes these assumptions because that is the intent of the
> document. Whether that's "universal" or not could be an open
> question, perhaps, but the intent is to specify a more restrictive
> method of extension than that in 5070 in the interests of
> consistency. So, yes, it's an informational document, they're just
> helpful suggestions, but we would hope they'd be followed, and the
> document is written assuming that they will...

As mentioned, I happen to be working on some IODEF extensions that are
specific to the XMPP community. Is it expected that I work on the
relevant spec in the MILE WG, in the XMPP WG, or (as I'm doing right
now) at the XMPP Standards Foundation? IMHO, doing this work at the XSF
makes the most sense because that's where most of the XMPP developers
and operators are active. Seeking a sanity check on this work from the
MILE WG does seem reasonable, though (once it's ready for review).

>> 2. Why is RFC 6545 a normative reference?
> 
> Oversight, should be informative (I checked this briefly; it is
> referenced from a section entitled "Terminology", but this is
> terminology in the Appendix; oops.)
> 
>> 3. Given the many comments provided by Martin DÃ¼rst, mentioning
>> his AppsDir review in the Acknowledgements seems appropriate.
> 
> Indeed, also oversight; thanks.
> 
>> 4. Some of the text in the appendix seems needlessly detailed
>> (e.g., saying that each extension needs to be specified in a
>> subsection, or the recommendation to include a UML diagram).
> 
> These guidelines are intended to help the set of drafts defining
> IODEF extensions to be consistent with RFC 5070 and with each other.
> 
>> 5. Why is the list of datatypes in appendix A.4.1 copied from RFC
>> 5070? A simple reference would do. (I almost said the same about
>> the list in Section 3, but that one is marginally useful.)
> 
> The A.4.1. list was copied over because doing so was consistent with
> the list in Section 3, more or less; it's intended to give an inline
> definition of the allowable TYPE values as in the UML diagram in
> Figure 1, section A.4. (Copying this was also consistent with the
> inclusion of the list in Section 3.)
> 
>> 6. Some of the information in this document repeats information
>> from the RFC style guide and other sources; why?
> 
> Here we have a duelling-commenters situation; this is per early-AD
> commentary in
> http://www.ietf.org/mail-archive/web/mile/current/msg00657.html and
> the subsequent thread.

IMHO, it seems fine to repeat some of that information, as long as you
say that the styleguide rules on general matters of RFC authorship. But
your AD might know better. ;-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hartmans@mit.edu  Mon May 21 14:51:13 2012
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 178B621F84D9; Mon, 21 May 2012 14:51:13 -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 X5NvhxAskfQy; Mon, 21 May 2012 14:51:12 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7954721F8493; Mon, 21 May 2012 14:51:12 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (unknown [217.28.191.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 2982420463; Mon, 21 May 2012 17:51:04 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E1BC44151; Mon, 21 May 2012 17:50:57 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Hanna <shanna@juniper.net>
Subject: Re: Updated secdir review of draft-ietf-emu-chbind-15.txt
References: <20120514190642.11168.14882.idtracker@ietfa.amsl.com> <tslvcjy37fi.fsf@mit.edu> <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net>
Date: Mon, 21 May 2012 17:50:57 -0400
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net> (Stephen Hanna's message of "Fri, 18 May 2012 18:10:19 -0400")
Message-ID: <tslr4udmce6.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 May 2012 21:51:13 -0000

>>>>> "Stephen" == Stephen Hanna <shanna@juniper.net> writes:

    Stephen> The changes in draft-ietf-emu-chbind-15.txt satisfactorily
    Stephen> address almost all of the comments in my April 13, 2012
    Stephen> secdir review. I do have one remaining substantive comment
    Stephen> on this latest draft and two non-substantive ones.

    Stephen> Substantive Comment -------------------

    Stephen> The last paragraph of section 9.1 points out a security
    Stephen> problem with implementing channel bindings using EAP tunnel
    Stephen> methods. If the EAP tunnel method terminates on the
    Stephen> authenticator, the channel bindings can easily be defeated
    Stephen> by the authenticator. While that's true, nobody terminates
    Stephen> the EAP tunnel method on the authenticator today. In the
    Stephen> EAP model, the authenticator is not trusted so terminating
    Stephen> the EAP tunnel method on the authenticator is a bad idea
    Stephen> for many reasons. For example, the authenticator would then
    Stephen> have the ability to bypass protected result indications and
    Stephen> to bypass all the cryptographic protections provided by the
    Stephen> tunnel.  Sometimes there is value in having the inner and
    Stephen> outer methods terminate on different servers but both
    Stephen> servers must be trusted.  The authenticator is not. So
    Stephen> there is no big security hole here, unless you have already
    Stephen> opened an enormous security hole. It's ironic that this
    Stephen> document which attempts to close vulnerabilities caused by
    Stephen> malicious authenticators ends up subtly suggesting that
    Stephen> people open a much larger vulnerability!

    Stephen> I would recommend deleting the end of this paragraph,
    Stephen> starting with the sentence that starts "Even when
    Stephen> cryptographic binding".>

I disagree very strongly with this proposed change.  It's possible that
the text is not clear and I'd be happy to work for a round or two to see
if we can clarify the text, but ending the paragraph as you propose
would defeate the point of text we added after a WG consensus call.

I agree with you that authenticators are not trusted.
The issue is that you cannot trust attackers to act within a
specification.
If an attacker can gain benefit from doing something, they may do so.

So, if an attacker can create a tunnel terminating at an authenticator
and gain advantage from doing so, then they will do so.

Remember that we're talking about crypto binding. If crypto binding is
relevant for confirming there are no extra servers, then we're in a
threat model space where we're trusting the inner method to authenticate
the server, not the outer method.  You can't say "you should only
establish trusted tunnels," because we're hoping that crypto binding
will give us that trust.  So, the issue here is that once you add
channel bindings and the associated changes to the threat model to EAP,
an authenticator can gain advantage through convincing a client to trust
a tunnel that terminates at an authenticator.  That is, an authenticator
can mount an attack.  Yes, the authenticator needs to convince the peer
to trust the extra tunnel. However, as I discuss in
draft-hartman-emu-mutual-crypto-binding and in my presentation at last
IETF, that's often fairly easy.

So, how can we make the text more clear?

From shanna@juniper.net  Tue May 22 13:03:55 2012
Return-Path: <shanna@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 B589421F869E; Tue, 22 May 2012 13:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.252
X-Spam-Level: 
X-Spam-Status: No, score=-105.252 tagged_above=-999 required=5 tests=[AWL=1.347, 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 AkDmDKxL08d2; Tue, 22 May 2012 13:03:55 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 44F0D21F86A3; Tue, 22 May 2012 13:03:52 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKT7vxJ+TDYVW/wC+63FzmvM056h/Z6qAp@postini.com; Tue, 22 May 2012 13:03:53 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 22 May 2012 13:00:21 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Tue, 22 May 2012 16:00:20 -0400
From: Stephen Hanna <shanna@juniper.net>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Tue, 22 May 2012 16:00:19 -0400
Subject: RE: Updated secdir review of draft-ietf-emu-chbind-15.txt
Thread-Topic: Updated secdir review of draft-ietf-emu-chbind-15.txt
Thread-Index: Ac03m9Vz0ExW5KUcShO4ogGhcZvyUgAAFxvw
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB82FBA10E8@EMBX01-WF.jnpr.net>
References: <20120514190642.11168.14882.idtracker@ietfa.amsl.com> <tslvcjy37fi.fsf@mit.edu> <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net> <tslr4udmce6.fsf@mit.edu>
In-Reply-To: <tslr4udmce6.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 20:03:56 -0000

Sam,

I see now that you are concerned not with circumstances where
the NAS terminates the tunnel by design but rather with times
when the NAS is maliciously terminating the tunnel. I'm glad
that we both agree that having the NAS terminate the tunnel
is highly undesirable. That did not come through in the draft.
I'm much relieved to learn that nobody is suggesting this
as a desirable outcome. I agree that it's an attack scenario
that must be considered and carefully addressed.

Maybe we can resolve this issue by clarifying the text to
say more clearly that we're dealing with an attack scenario
here. For example, we could add a sentence before the words
"Tunnel methods sometimes use" saying something like "However,
this is not secure if the NAS can terminate the tunnel (a
highly undesirable situation)." Then you can mention several
countermeasures against such an attack: mutual cryptographic
bindings (still just a -00 individual draft), carefully
checking the EAP server's identity, etc. We might also take
this opportunity to split this long paragraph into two:
one that includes the first three sentences (describing how
EAP tunnel methods can support channel binding) and another
describing the attack scenario and countermeasures.

Thanks,

Steve

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Monday, May 21, 2012 5:51 PM
> To: Stephen Hanna
> Cc: Sam Hartman; emu@ietf.org; secdir@ietf.org; ietf@ietf.org
> Subject: Re: Updated secdir review of draft-ietf-emu-chbind-15.txt
> Importance: High
>=20
> >>>>> "Stephen" =3D=3D Stephen Hanna <shanna@juniper.net> writes:
>=20
>     Stephen> The changes in draft-ietf-emu-chbind-15.txt satisfactorily
>     Stephen> address almost all of the comments in my April 13, 2012
>     Stephen> secdir review. I do have one remaining substantive comment
>     Stephen> on this latest draft and two non-substantive ones.
>=20
>     Stephen> Substantive Comment -------------------
>=20
>     Stephen> The last paragraph of section 9.1 points out a security
>     Stephen> problem with implementing channel bindings using EAP
> tunnel
>     Stephen> methods. If the EAP tunnel method terminates on the
>     Stephen> authenticator, the channel bindings can easily be defeated
>     Stephen> by the authenticator. While that's true, nobody terminates
>     Stephen> the EAP tunnel method on the authenticator today. In the
>     Stephen> EAP model, the authenticator is not trusted so terminating
>     Stephen> the EAP tunnel method on the authenticator is a bad idea
>     Stephen> for many reasons. For example, the authenticator would
> then
>     Stephen> have the ability to bypass protected result indications
> and
>     Stephen> to bypass all the cryptographic protections provided by
> the
>     Stephen> tunnel.  Sometimes there is value in having the inner and
>     Stephen> outer methods terminate on different servers but both
>     Stephen> servers must be trusted.  The authenticator is not. So
>     Stephen> there is no big security hole here, unless you have
> already
>     Stephen> opened an enormous security hole. It's ironic that this
>     Stephen> document which attempts to close vulnerabilities caused by
>     Stephen> malicious authenticators ends up subtly suggesting that
>     Stephen> people open a much larger vulnerability!
>=20
>     Stephen> I would recommend deleting the end of this paragraph,
>     Stephen> starting with the sentence that starts "Even when
>     Stephen> cryptographic binding".>
>=20
> I disagree very strongly with this proposed change.  It's possible that
> the text is not clear and I'd be happy to work for a round or two to
> see
> if we can clarify the text, but ending the paragraph as you propose
> would defeate the point of text we added after a WG consensus call.
>=20
> I agree with you that authenticators are not trusted.
> The issue is that you cannot trust attackers to act within a
> specification.
> If an attacker can gain benefit from doing something, they may do so.
>=20
> So, if an attacker can create a tunnel terminating at an authenticator
> and gain advantage from doing so, then they will do so.
>=20
> Remember that we're talking about crypto binding. If crypto binding is
> relevant for confirming there are no extra servers, then we're in a
> threat model space where we're trusting the inner method to
> authenticate
> the server, not the outer method.  You can't say "you should only
> establish trusted tunnels," because we're hoping that crypto binding
> will give us that trust.  So, the issue here is that once you add
> channel bindings and the associated changes to the threat model to EAP,
> an authenticator can gain advantage through convincing a client to
> trust
> a tunnel that terminates at an authenticator.  That is, an
> authenticator
> can mount an attack.  Yes, the authenticator needs to convince the peer
> to trust the extra tunnel. However, as I discuss in
> draft-hartman-emu-mutual-crypto-binding and in my presentation at last
> IETF, that's often fairly easy.
>=20
> So, how can we make the text more clear?

From stpeter@stpeter.im  Tue May 22 15:20:48 2012
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 ADCCE21F8631 for <ietf@ietfa.amsl.com>; Tue, 22 May 2012 15:20:48 -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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ieBcWXfgV8J for <ietf@ietfa.amsl.com>; Tue, 22 May 2012 15:20:47 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1744F21F864D for <ietf@ietf.org>; Tue, 22 May 2012 15:20:47 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 71EF840067; Tue, 22 May 2012 16:36:49 -0600 (MDT)
Message-ID: <4FBC113C.3050707@stpeter.im>
Date: Tue, 22 May 2012 16:20:44 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <CBC48C89.8671C%stewe@stewe.org>
In-Reply-To: <CBC48C89.8671C%stewe@stewe.org>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
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: Tue, 22 May 2012 22:20:49 -0000

Hi Stephan, thanks for the feedback and sorry about the slow reply.

On 4/30/12 11:19 AM, Stephan Wenger wrote:
> Hi,
> Here are a few comments to this draft.
> Stephan
> 
> (1) Section 3.1, final paragraph.  An IETF disclosure has to be made
> against a Contribution.  In the case described in this paragraph, the
> Contribution may not have been made at the time of the Disclosure request,
> and, therefore, it would be impossible to make a Disclosure.  For example,
> if someone wants to discuss a technology verbally, you cannot make an IPR
> disclosure before the words have been uttered.  I would remove this
> paragraph.  Alternatively, limit it to "materials you plan to make
> available at the meeting" in the sprit it of section 4.1.

I see your point: one can't realistically be expected to file a
disclosure before making a Contribution. Tim and I will discuss together
how we'd like to make this clearer. One possibility is to use a less
formal method, e.g., providing information about known IPR in the
materials to be presented or posting to the relevant discussion list
ahead of time (rather than filing a formal disclosure).

> (2) Section 3.2, "silence may be interpreted as a weak "No".".  This
> statement is IMO not supported by the IETF patent policy, and should
> therefore be removed.  Generally speaking, any additional burden to
> non-Contributors beyond making them aware of the voluntary disclosure
> opportunity IMP constitutes a policy change and must be avoided.

I think you're right that absence of evidence can't be interpreted as
evidence of absence. If Tim agrees, we'll stike that sentence.

> (3) Section 3.3.  I would replace "author" with "authors and other
> Contributors".  Or "known Contributors", "prominent Contributors", or
> something like this.  It is entirely possible, and in fact not uncommon,
> that non-author Contributors influence the technology choices of I-Ds.
> One possible metric for identifying some of these Contributors would be a
> review of the Acknowledgement section many I-Ds include.  I see this
> mentioned in section 3.4; I would shift (or duplicate?) the burden of
> double-checking with Contributors to the WG chairs as WGLC.

Your suggestion of "authors and other Contributors" seems right.

> (4) Section 4.2.  Suggest to include Contributors in the spirit of comment
> (3) above.

Agreed.

> (5) Section A.1.  The email has a logical structure, but sometimes a
> logical structure may not have the best effect.  As written, people will
> probably not read it in its entirety, but will give up once its clear that
> it includes legalese.  Suggest to move the final paragraph "As FOO WG
> chairs" to the top, and put the formal justification stuff at the end.
> 
> (6) Section A.2: I would substitute "Dear FOO WG" with "Dear FOO WG and
> especially authors and Contributors:"
> 
> (7) Section A.2, third paragraph, sentence "We will not be able to advance
> this document to the next stage until we have received a reply from each
> author and listed contributor."  If this sentence starts appearing with
> some consistency in IETF WGs, then we have a de-facto policy change
> (requiring affirmative negative declarations).  Suggest to soften the
> language: "we may not be able to advance" or "it does not appear to be
> sensible to us to advance"
> 
> (8) Section A.2, fourth paragraph: I would express this along the
> following: "you are reminded of your opportunity for a voluntary IPR
> disclosure under BCP79 section xxx.  Unless you want to make such a
> voluntary disclosure, please do not reply."
> 
> (9) Section A.3, see previous comments (7) and (8).
>  
> (10) Section A.4, see previous comment (7)
> 
> (11) Section A.5, see previous comment (7)

Thanks for those suggestions. We'll look at those sample messages again,
but on a first look I think all your points are spot-on.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From bclaise@cisco.com  Tue May 22 16:44:12 2012
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 1BA5221F86B0; Tue, 22 May 2012 16:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level: 
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HTML_MESSAGE=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 dBix-febMl-A; Tue, 22 May 2012 16:44:09 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5D221F86AD; Tue, 22 May 2012 16:44:09 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4MNUfbX020073; Wed, 23 May 2012 01:30:41 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4MNUbKH000323; Wed, 23 May 2012 01:30:37 +0200 (CEST)
Message-ID: <4FBC219D.8070000@cisco.com>
Date: Wed, 23 May 2012 01:30:37 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com>
In-Reply-To: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com>
Content-Type: multipart/alternative; boundary="------------080106040303000401020104"
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2012 23:44:12 -0000

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

Hi Roni,

Thanks for your review.
See in-line.
>
> 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-claise-export-application-info-in-ipfix-05
>
> Reviewer: Roni Even
>
> Review Date:2012--4--7
>
> IETF LC End Date: 2012--4--17
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as an 
> Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> 1.In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information 
> in Cisco web page. I could not locate and information that is 
> referenced. The link is to the main Cisco web page. For example in 
> section 6.5 it lists the selectorID as 10000, where is this value located?
>
The exact URsL are 
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html
and 
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment.
>
> 2.For the definition of Classification engine IDs in section 4.1 for 
> the non standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is 
> there a requirement that the selector IDs will be publically available?
>
Yes. Also, they would be exported with an IPFIX Options Template Record.
An example of PANA-L3 was the IPFIX port, 4739, which was pre-reserved 
by IANA, 3 years before RFC5101 was published.

> 3.In section 4.2 "However, an IANA L3 protocol encoding may encoded 
> with 3 bytes." When is it encoded in 3 bytes, also figure 2 is not 
> reflecting this example, I expected to see a 32 bit value according to 
> the text and not a general figure. (small nit in the above sentence 
> "may be" instead of "may".
>
Will be corrected.
>
> 4.In section 7 I noticed that "p2pTechnology, tunnelTechnology, and 
> encryptedTechnology" are already assigned in the IANA IPFIX 
> Information elements so why assign them again as new?
>
from RFC5102:

    The value of these identifiers is in the range of 1-32767.  Within
    this range, Information Element identifier values in the sub-range of
    1-127 are compatible with field types used by NetFlow version 9
    [RFC3954  <http://tools.ietf.org/html/rfc3954>].


So basically, if Cisco has assigned those numbers already, they can 
reused in IANA.
>
> 5.In section 7 I noticed that you request that the  
> applicationDescription, applicationId, applicationName, 
> classificationEngineId will receive elementid values from the range 
> 0-127. My reading from section 4.2 is this is not required, maybe add 
> text that will explain this request.
>
See my previous remark.
>
> 6.In the security section arethere additional considerations when the 
> applicationid information is coming from a proprietary classification 
> engine about authentication of the information source?
>
Not as far as I know.
Maybe I'm missing something. Can you please elaborate.
>
> Nits/editorial comments:
>
> 1.In section 4.1 last sentence what is the meaning of "by theses 
> specifications" , I did not understand the context.
>
> 2.In section 6.6 "to determine whether or the default HTTP port" 
> delete the "or"
>
> 3.In section 6.6 "The Classification Engine ID is 2" should be "3".
>

will be corrected.

Thanks again.

Regards, Benoit.
>


--------------080106040303000401020104
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">
    Hi Roni,<br>
    <br>
    Thanks for your review.<br>
    See in-line.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="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: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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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">I am the assigned Gen-ART reviewer for this
          draft. For background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Please resolve these comments along with
          any other Last Call comments you may receive.<o:p></o:p></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
          </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">draft-claise-export-application-info-in-ipfix-05<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
            Roni Even<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
            Date:2012&#8211;4&#8211;7<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
            LC End Date: 2012&#8211;4&#8211;17<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
            Telechat date:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
            This draft is almost ready for publication as an
            Informational </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">RFC</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">In sections 2,
            4.1 (PANA-L7), 5, 6.5 the draft points to information in
            Cisco web page. I could not locate and information that is
            referenced. The link is to the main Cisco web page. For
            example in section 6.5 it lists the selectorID as 10000,
            where is this value located?</span></p>
      </div>
    </blockquote>
    The exact URsL are
    <a class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br>
    and
    <a class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html</a><br>
    As you can see from the URLs, there is a chance that those might
    change.<br>
    Stephen Farrell had the same comment. <br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">For
            the definition of Classification engine IDs in section 4.1
            for the non standard values like PANA-L3, PANA-L4, PANA-L7,
            PANA-L2, is there a requirement that the selector IDs will
            be publically available?</span></p>
      </div>
    </blockquote>
    Yes. Also, they would be exported with an IPFIX Options Template
    Record.<br>
    An example of PANA-L3 was the IPFIX port, 4739, which was
    pre-reserved by IANA, 3 years before RFC5101 was published.<br>
    <br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 4.2 &#8220;However, an IANA L3 protocol encoding may
            encoded with 3 bytes.&#8221; When is it encoded in 3 bytes, also
            figure 2 is not reflecting this example, I expected to see a
            32 bit value according to the text and not a general figure.
            (small nit in the above sentence &#8220;may be&#8221; instead of &#8220;may&#8221;.</span></p>
      </div>
    </blockquote>
    Will be corrected.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">4.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 7 I noticed that &#8221;p2pTechnology, tunnelTechnology,
            and encryptedTechnology&#8221; are already assigned in the IANA
            IPFIX Information elements so why assign them again as new?</span></p>
      </div>
    </blockquote>
    from RFC5102:<br>
    <pre class="newpage">   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [<a href="http://tools.ietf.org/html/rfc3954" title="&quot;Cisco Systems NetFlow Services Export Version 9&quot;">RFC3954</a>].

</pre>
    So basically, if Cisco has assigned those numbers already, they can
    reused in IANA.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">5.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 7 I noticed that you request that the&nbsp;
            applicationDescription, applicationId, applicationName,
            classificationEngineId will receive elementid values from
            the range 0-127. My reading from section 4.2 is this is not
            required, maybe add text that will explain this request.</span></p>
      </div>
    </blockquote>
    See my previous remark.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">6.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            the security section are</span><span style="font-size: 11pt;
            font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">
            there additional considerations when the applicationid
            information is coming from a proprietary classification
            engine about authentication of the information source?</span></p>
      </div>
    </blockquote>
    Not as far as I know.<br>
    Maybe I'm missing something. Can you please elaborate.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
            comments:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 4.1 last sentence what is the meaning of &#8220;by theses
            specifications&#8221; , I did not understand the context.<o:p></o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
            section 6.6 &#8220;</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">to
            determine whether or the default HTTP port&#8221; delete the &#8220;or&#8221;<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">In section 6.6
            &#8220;The Classification Engine ID is 2&#8221; should be &#8220;3&#8221;.</span></p>
      </div>
    </blockquote>
    <br>
    will be corrected.<br>
    <br>
    Thanks again.<br>
    <br>
    Regards, Benoit.<br>
    <blockquote cite="mid:4f800f2f.634cb40a.13a1.ffff8003@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------080106040303000401020104--

From ron.even.tlv@gmail.com  Wed May 23 00:14:08 2012
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 1F61C21F8587; Wed, 23 May 2012 00:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.293
X-Spam-Level: 
X-Spam-Status: No, score=-3.293 tagged_above=-999 required=5 tests=[AWL=0.305,  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 Vl8N91RWfaUn; Wed, 23 May 2012 00:14:05 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id C29B121F8596; Wed, 23 May 2012 00:14:04 -0700 (PDT)
Received: by werb13 with SMTP id b13so3849212wer.31 for <multiple recipients>; Wed, 23 May 2012 00:14:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=i0uIYONZ23Pp3We4GBrw/scoeu3XMXvXaS1hp9fbhcE=; b=kcgTJf35t25E4XeWZUU9/yGmCzAK1EEpUwHaKDP6j3lcSNnGJsMEeJewbmgkJ56xGH RAmlm3V3gYGzfMRAQT7iEayub1nRN+kzxUhlXLEhqhV3/ONLLchsIa17vNRJVgHsapG4 5uTH0Q6+4xXMdcKMJ1Ecu/VBFfKuaku55c/ZlmMLYibRaKtRRxtrvE128i6jdjiOgPQe BXJiHBeTmFtFvYZPr6oExKD2xKnm1JW/2BbPPw2bPm7nYIAQtp+Aiv/6Ai1RvekyaqDW kCE4zu8ZYmQRIVD/on2Tx2BTaTL5+sZ6ooFQtzyaF/dY/wZNIK0dbDIyGm3MxQwZd3U6 pNig==
Received: by 10.180.98.201 with SMTP id ek9mr43318051wib.7.1337757243756; Wed, 23 May 2012 00:14:03 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id gb9sm38468117wib.8.2012.05.23.00.14.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 May 2012 00:14:03 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com>
In-Reply-To: <4FBC219D.8070000@cisco.com>
Subject: RE: Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
Date: Wed, 23 May 2012 10:11:50 +0300
Message-ID: <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002E_01CD38CC.7A29B550"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac04cuj+nPaJQ4f7Ra6W4Tdvse+fBgAPFb+g
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.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, 23 May 2012 07:14:08 -0000

This is a multi-part message in MIME format.

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

Hi Benoit,

Thanks, see in-line

Roni

 

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-claise-export-application-info-in-ipfix-05

Reviewer: Roni Even

Review Date:2012-4-7

IETF LC End Date: 2012-4-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as an Informational RFC.

 

Major issues:

 

Minor issues:

 

In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in
Cisco web page. I could not locate and information that is referenced. The
link is to the main Cisco web page. For example in section 6.5 it lists the
selectorID as 10000, where is this value located?

The exact URsL are
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/pre
sentation_c96-629396.html
and
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/pro
duct_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment. 

 

RE: My concern was that going to Cisco web page I tried to search for the
information using the search window and could not find it so I think that
this link is not helpful for finding the information.





For the definition of Classification engine IDs in section 4.1 for the non
standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is there a
requirement that the selector IDs will be publically available?

Yes. Also, they would be exported with an IPFIX Options Template Record.
An example of PANA-L3 was the IPFIX port, 4739, which was pre-reserved by
IANA, 3 years before RFC5101 was published.

 

RE: OK






In section 4.2 "However, an IANA L3 protocol encoding may encoded with 3
bytes." When is it encoded in 3 bytes, also figure 2 is not reflecting this
example, I expected to see a 32 bit value according to the text and not a
general figure. (small nit in the above sentence "may be" instead of "may".

Will be corrected.

 

RE:OK





In section 7 I noticed that "p2pTechnology, tunnelTechnology, and
encryptedTechnology" are already assigned in the IANA IPFIX Information
elements so why assign them again as new?

from RFC5102:

   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [RFC3954 <http://tools.ietf.org/html/rfc3954> ].
 

So basically, if Cisco has assigned those numbers already, they can reused
in IANA.

 

RE: The question is if you want the existing assignment to be used without
change than why have this information in the IANA consideration in the first
place. 

 





In section 7 I noticed that you request that the  applicationDescription,
applicationId, applicationName, classificationEngineId will receive
elementid values from the range 0-127. My reading from section 4.2 is this
is not required, maybe add text that will explain this request.

See my previous remark. 

 

RE:  OK, even though it should be clear that this applies to these specific
selectors since you want them to be compatible with NetFlow version 9 and it
is not a general request for using specific sub range for all selectors.





In the security section are there additional considerations when the
applicationid information is coming from a proprietary classification engine
about authentication of the information source?

Not as far as I know.
Maybe I'm missing something. Can you please elaborate.

RE: No, this is OK for me.





 

Nits/editorial comments:

 

1.  In section 4.1 last sentence what is the meaning of "by theses
specifications" , I did not understand the context.

2.  In section 6.6 "to determine whether or the default HTTP port" delete
the "or"

In section 6.6 "The Classification Engine ID is 2" should be "3".


will be corrected.

Thanks again.

Regards, Benoit.



 

 


------=_NextPart_000_002E_01CD38CC.7A29B550
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 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: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";
	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;}
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;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Hi =
Benoit,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks, see in-line<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal>I am the assigned Gen-ART reviewer for this =
draft. For background on Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<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"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;4&#8211;7</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as an Informational =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In =
sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in =
Cisco web page. I could not locate and information that is referenced. =
The link is to the main Cisco web page. For example in section 6.5 it =
lists the selectorID as 10000, where is this value =
located?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>The =
exact URsL are <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555=
/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/col=
lateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br=
>and <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558=
/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod=
/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.htm=
l</a><br>As you can see from the URLs, there is a chance that those =
might change.<br>Stephen Farrell had the same comment. </span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: My concern was that going to Cisco web =
page I tried to search for the information using the search window and =
could not find it so I think that this link is not helpful for finding =
the information.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For the =
definition of Classification engine IDs in section 4.1 for the non =
standard values like PANA-L3, PANA-L4, PANA-L7, PANA-L2, is there a =
requirement that the selector IDs will be publically =
available?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Yes. =
Also, they would be exported with an IPFIX Options Template =
Record.<br>An example of PANA-L3 was the IPFIX port, 4739, which was =
pre-reserved by IANA, 3 years before RFC5101 was published.</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: OK<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><br><o:p></o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4.2 &#8220;However, an IANA L3 protocol encoding may encoded with 3 =
bytes.&#8221; When is it encoded in 3 bytes, also figure 2 is not =
reflecting this example, I expected to see a 32 bit value according to =
the text and not a general figure. (small nit in the above sentence =
&#8220;may be&#8221; instead of =
&#8220;may&#8221;.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Will =
be corrected.</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif";color:#1F497D'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE:OK<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that &#8221;p2pTechnology, tunnelTechnology, and =
encryptedTechnology&#8221; are already assigned in the IANA IPFIX =
Information elements so why assign them again as =
new?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>from =
RFC5102:<o:p></o:p></span></p><pre>&nbsp;&nbsp; The value of these =
identifiers is in the range of 1-32767.&nbsp; =
Within<o:p></o:p></pre><pre>&nbsp;&nbsp; this range, Information Element =
identifier values in the sub-range of<o:p></o:p></pre><pre>&nbsp;&nbsp; =
1-127 are compatible with field types used by NetFlow version =
9<o:p></o:p></pre><pre>&nbsp;&nbsp; [<a =
href=3D"http://tools.ietf.org/html/rfc3954" title=3D"&quot;Cisco Systems =
NetFlow Services Export Version =
9&quot;">RFC3954</a>].<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>So =
basically, if Cisco has assigned those numbers already, they can reused =
in IANA.</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: The question is if you want the existing =
assignment to be used without change than why have this information in =
the IANA consideration in the first place. <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that you request that the&nbsp; applicationDescription, =
applicationId, applicationName, classificationEngineId will receive =
elementid values from the range 0-127. My reading from section 4.2 is =
this is not required, maybe add text that will explain this =
request.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>See =
my previous remark.</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'> <o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: &nbsp;OK, even though it should be clear =
that this applies to these specific selectors since you want them to be =
compatible with NetFlow version 9 and it is not a general request for =
using specific sub range for all selectors.<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the =
security section are there additional considerations when the =
applicationid information is coming from a proprietary classification =
engine about authentication of the information =
source?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>Not =
as far as I know.<br>Maybe I'm missing something. Can you please =
elaborate.</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: No, this is OK for =
me.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br><br><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4.1 last sentence what is the meaning of &#8220;by theses =
specifications&#8221; , I did not understand the =
context.</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo4'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;to determine whether or the default HTTP port&#8221; delete =
the &#8220;or&#8221;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;The Classification Engine ID is 2&#8221; should be =
&#8220;3&#8221;.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><br>will be corrected.<br><br>Thanks =
again.<br><br>Regards, Benoit.<br><br><o:p></o:p></span></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_002E_01CD38CC.7A29B550--


From sm@resistor.net  Wed May 23 01:17:55 2012
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 7BB9521F86C6 for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 01:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZR97h9iULz5I for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 01:17: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 EA42521F850C for <ietf@ietf.org>; Wed, 23 May 2012 01:17:49 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q4N8HhqL010497; Wed, 23 May 2012 01:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1337761069; i=@resistor.net; bh=5l0Sgy4GGK9cxEhv90wSNjIKx/FSa1+Yeehs7MmT/60=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eD1pzHifWJGrsX6Ruz8YJFm3kOAJ7ml2pdmCpbFCfbnuoOnNn8Y5P0j6c7rkLgqVu 4I5RZG3rWmrZununxUgZb61H/9ozgnpAwm9MDnbGaNqjb19BR+ZLYduAPDsSJItp9D duioYYREwfSo0dRnU+cfMIguNV7lBgJyAICGlUa4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1337761069; i=@resistor.net; bh=5l0Sgy4GGK9cxEhv90wSNjIKx/FSa1+Yeehs7MmT/60=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Kels/Dttv3otGN+rQVgqw0Sa0daP3x33fkv5KxmUcSQvkGVfjQTk7ZAQBOavGTpKx BzHGQai1dwaUUTBIbBJ61xeh76Sfdfy10ZIn7oPBozP3IhBWQE90JTJ6t+53dHPGSh wcRqvie2PvGLI5f5ri0qELcSyzS1/VMqGBOLU1s8=
Message-Id: <6.2.5.6.2.20120522233611.08d14c78@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 23 May 2012 01:16:45 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
In-Reply-To: <4FBC113C.3050707@stpeter.im>
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im>
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, 23 May 2012 08:17:55 -0000

Hi Peter,

I understand why the intended status is not BCP.  I suggest taking 
into account the wider audience feedback to determine whether the it 
should not be made clearer.

A question which is not covered by the draft is when a draft is 
"adopted" through a charter.  I assume that the AD will contact the 
authors in such cases.

In Section 2:

There is a typo, "secretatires".

in Section 3.1:

   "If necessary disclosures have not been submitted, the chairs have a
    choice: insist on an informal disclosure in the presentation, or deny
    the agenda slot unless the IPR disclosure is submitted.  One factor
    in this decision could be the number of revisions that have occurred:
    the chairs might wish to permit presentation of a -00 draft with a
    verbal disclosure, but not after a draft has gone through multiple
    cycles."

The boilerplate explicitly states that this draft as any other draft 
is submitted in full conformance with the provisions of the usual 
BCPs.  If disclosures are necessary they should be submitted 
especially if the goal of this draft is to promote 
compliance.  Informal disclosures causes uncomfortable situations as 
there are usually valid reasons.  There is also the presumption of 
good faith which makes it a difficult decision.  I don't know how 
often verbal disclosures go on record.  The information may not be 
available to the working group (decisions are taken through the 
mailing list) unless the participants go through the audio.

In A.1:

   "In order to comply with IETF processes while avoiding unnecessary
    delays, document authors and contributors to our discussions in
    the FOO WG are asked to take these messages seriously, and to
    reply in a timely fashion."

Is there any message from WG chairs which should not be taken 
seriously? :-)  I'll suggest:

    In order to comply with IETF processes and avoid unnecessary delays,
    document authors and contributors to our discussions in the FOO WG
    are asked to take pay careful attention to these messages and to
    reply in a timely fashion.

In A.2:

   "We will weigh this information when we judge the consensus on
   the call for adoption."

The wording is not that clear.  It is up to the participants to see 
whether they are ok to work the specification given the IPR 
claims.  Sam Hartman posted some possible responses in such cases ( 
http://www.ietf.org/mail-archive/web/oauth/current/msg08992.html 
).  What we were are looking for here is whether there are any 
claims.  The easy path is to remove the sentence and keep the IPR 
question for the follow-up question.

In A.3:

   "The authors of draft-ietf-foo-wiffle have asked for a Working Group
    Last Call.  Before issuing the Last Call, we would like to check"

I suggest "before issuing the Working Group Last Call" as Last Call 
is generally considered as what's in the subject line of this message.

I'll +1 the draft.  Please feel free to ignore the comments to keep 
matters simple.

Regards,
-sm


From trammell@tik.ee.ethz.ch  Wed May 23 05:08:33 2012
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 05D4521F86AA; Wed, 23 May 2012 05:08: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 UIf1BONb80fm; Wed, 23 May 2012 05:08:32 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 5B94121F86A4; Wed, 23 May 2012 05:08:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 8C38ED930A; Wed, 23 May 2012 14:08:30 +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 0jO0Funr0bzk; Wed, 23 May 2012 14:08:30 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (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 5D494D9307; Wed, 23 May 2012 14:08:30 +0200 (MEST)
Subject: Re: [mile] Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining	Extensions to IODEF) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4FBA5C59.4030102@stpeter.im>
Date: Wed, 23 May 2012 14:08:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAAC19A0-9FF8-4DF4-B7CD-9A843743D2E5@tik.ee.ethz.ch>
References: <20120516215321.9671.39664.idtracker@ietfa.amsl.com> <4FB46FA6.6060005@stpeter.im> <B06DB832-2813-4431-94B9-1F7B3492A595@tik.ee.ethz.ch> <4FBA5C59.4030102@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1278)
Cc: "<mile@ietf.org>" <mile@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 May 2012 12:08:33 -0000

Hi, Peter,

One minor point, inline...

On May 21, 2012, at 5:16 PM, Peter Saint-Andre wrote:

>> Hm. The document does indeed assume that extensions to IODEF are
>> defined in Internet-Drafts, that extension namespaces will be
>> registered with IANA, and that those namespaces be of the described
>> form; it makes these assumptions because that is the intent of the
>> document. Whether that's "universal" or not could be an open
>> question, perhaps, but the intent is to specify a more restrictive
>> method of extension than that in 5070 in the interests of
>> consistency. So, yes, it's an informational document, they're just
>> helpful suggestions, but we would hope they'd be followed, and the
>> document is written assuming that they will...
>=20
> As mentioned, I happen to be working on some IODEF extensions that are
> specific to the XMPP community. Is it expected that I work on the
> relevant spec in the MILE WG, in the XMPP WG, or (as I'm doing right
> now) at the XMPP Standards Foundation? IMHO, doing this work at the =
XSF
> makes the most sense because that's where most of the XMPP developers
> and operators are active. Seeking a sanity check on this work from the
> MILE WG does seem reasonable, though (once it's ready for review).

This is IMO the right way to go. During the creation of this document, =
we envisioned in most cases that work to extend IODEF would not have any =
other "natural" home, and as such would be done within the IETF in the =
MILE WG; this assumption is probably apparent in the document.

In cases where the work _does_ have a natural home (the application of =
IODEF to XMPP-specific events is a perfect example), it definitely makes =
sense to do work there in possible consultation with the MILE WG.

Indeed, for such cases, the IODEF expert review on IODEF extension =
schemas specified by draft-ietf-mile-iodef-xmlreg would be a final =
backstop to ensure that specified extensions are consistent with IODEF.

Best regards,

Brian (as author, draft-ietf-mile-template)=

From abdussalambaryun@gmail.com  Wed May 23 03:49:30 2012
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 E958F21F861B for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 03:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.424
X-Spam-Level: 
X-Spam-Status: No, score=-3.424 tagged_above=-999 required=5 tests=[AWL=0.175,  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 b51m42KttFpe for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 03:49:29 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 36E7D21F849B for <ietf@ietf.org>; Wed, 23 May 2012 03:49:29 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so4822856wgb.13 for <ietf@ietf.org>; Wed, 23 May 2012 03:49:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=scABkWfVov+Xk4C4zLGHPdx7DeEA7v6yqd6MlcreC3Y=; b=G2p7hRf5LathQcfa+Jj06ODz7dkm8aJ4JuZ0h5If+9M2pPRkD83bViGJzGqSX7dmfT wgGNEuLRG3N+VaUQK0QuhMQuX7mX76b7poZKVFLjfgLFzwjZIRrHJiBDLemGDN++pHW7 aupWiF2DjinYq+b7byp3jHruH4ry7XvIeDZRl/qj1TviRciNjUQa2ANCq2ZRztS3l6VN QL2O3/IsrGhgaryqQeEA3/xjW/ODOKx0YxZ6L5DRN8mgi/CK2wDylS0yCs2VXo5KyZbP o37K3aX2+xbU3n/96LWzj4vBvhyJH+wqH/W6UB1xLdKhMhKJh93+sATFxMCXWrmYGHDA mUSA==
MIME-Version: 1.0
Received: by 10.180.94.163 with SMTP id dd3mr12823586wib.22.1337770168367; Wed, 23 May 2012 03:49:28 -0700 (PDT)
Received: by 10.180.100.10 with HTTP; Wed, 23 May 2012 03:49:28 -0700 (PDT)
Date: Wed, 23 May 2012 12:49:28 +0200
Message-ID: <CADnDZ8-bT9BgmKEBD_NcvSew3mMf-KUhwK2cGOG+Q9ynSEzWcg@mail.gmail.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ofer Inbar <cos@aaaaa.org>, John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 23 May 2012 09:04:01 -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: Wed, 23 May 2012 10:49:31 -0000

Hi

It is preferable to update RFC2119 to be more suitable for IETF RFCs
in the future, IMO importance of using CAPS is understood, but when to
use lower case (e.g. must, should, etc.) is not clear. Some use their
sensibility to determine when to use lower case. In the end we can
leave it for the editors to feedback on that when submitting, or use
different sentences. In summary, from some discussions, RFC2119 seems
not to be the best practice so far.

Abdussalam

+++++++++++++++++++++++++++++++++++++++++++++
--On Sunday, May 20, 2012 07:53 +0100 Brian E Carpenter
<brian.e.carpenter at gmail.com> wrote:

> On 2012-05-19 20:39, Ofer Inbar wrote:
> ...
>
>>  But don't change the rules.  2119 works well as is IMO.
>
> Just to be clear about the current rules, 2119 makes it clear
> that upper case keywords are optional ("These words are often
> capitalized"). Indeed, numerous standards track documents
> don't use them.

Brian,

I've been trying really hard to avoid this discussion, but I
think the above is misleading.

In recent years, various IESG members have insisted that any
IETF Track document that contains anything approximating
conformance language include the 2119 reference and whatever the
strict interpretation of the week is about caps, etc.  As Randy
suggests, there have been signs of more nuance in the last IESG
or two, but...

The same problem applies to the other issue with 2119, which is
that we have history for at least two different interpretations
of those words, the ones in 2119 that are interpreted as
"necessary for interoperability" and the ones in, e.g.,
1122/1123 (Section 1.3.2 in the latter) which are "requirements
of the specification" without binding those requirements to a
particular reason.  From my point of view, the other difficulty
with treating 2119 like Received Wisdom and a set of absolute
requirements is that the interoperability criterion often makes
no sense for what are perfectly reasonable requirements.  As an
example drawn from 1123, a specification might reasonably say
"this option MUST be configurable" because it is necessary to
make things work in a plausible way even if that statement
cannot be explicitly linked to "won't interoperate unless it
does".   But again, in recent years, some IESG members (and
others) have insisted that only the 2119 definitions are
permitted.

The combination of the two is known in some quarters as writing
technically poor or deficient specs in the interest of clear
conformance to procedures.  At least historically, that was a
trap the IETF tried to avoid.

    john

From dhc@dcrocker.net  Wed May 23 09:56:54 2012
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 910CF21F8692 for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 09:56:54 -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 kR5mwywotjPV for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 09:56:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 01EE721F8452 for <ietf@ietf.org>; Wed, 23 May 2012 09:56:53 -0700 (PDT)
Received: from [192.168.1.132] (rrcs-76-79-112-91.west.biz.rr.com [76.79.112.91]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4NGupv8015773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 23 May 2012 09:56:53 -0700
Message-ID: <4FBD16D1.9070808@dcrocker.net>
Date: Wed, 23 May 2012 09:56:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: abnf discussion list?
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.17]); Wed, 23 May 2012 09:56: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: Wed, 23 May 2012 16:56:54 -0000

Folks,

g'day.

There are periodic questions about ABNF that go beyond the specifics of 
a specification attempting to use it.

While these are not hot topics, they do occur periodically.  Also, there 
is support material (software, documentation) for ABNF that has no 
single, natural home.

I'd like to suggest an abnf-discuss@ietf.org mailing list and an 
abnf.ietf.org web page.

Thoughts?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From julian.reschke@gmx.de  Wed May 23 23:34:18 2012
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 DC6A921F8531 for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 23:34: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2TUDS0YyqiX for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 23:34:18 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 01D9321F852D for <ietf@ietf.org>; Wed, 23 May 2012 23:34:17 -0700 (PDT)
Received: (qmail invoked by alias); 24 May 2012 06:34:15 -0000
Received: from p5DD97F30.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.127.48] by mail.gmx.net (mp032) with SMTP; 24 May 2012 08:34:15 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/7gRtdsmL7ochTNWzAQsoOFAWbwSAlGhEewfIq7z Tesw12z4KzCs0Y
Message-ID: <4FBDD661.6030907@gmx.de>
Date: Thu, 24 May 2012 08:34:09 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: abnf discussion list?
References: <4FBD16D1.9070808@dcrocker.net>
In-Reply-To: <4FBD16D1.9070808@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 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: Thu, 24 May 2012 06:34:19 -0000

On 2012-05-23 18:56, Dave Crocker wrote:
> Folks,
>
> g'day.
>
> There are periodic questions about ABNF that go beyond the specifics of
> a specification attempting to use it.
>
> While these are not hot topics, they do occur periodically. Also, there
> is support material (software, documentation) for ABNF that has no
> single, natural home.
>
> I'd like to suggest an abnf-discuss@ietf.org mailing list and an
> abnf.ietf.org web page.
>
> Thoughts?
>
> d/

Sounds good to me.

Best regards, Julian

From alexey.melnikov@isode.com  Thu May 24 01:33:32 2012
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 C445821F8603; Thu, 24 May 2012 01:33: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.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 iYxz4q+yffKr; Thu, 24 May 2012 01:33:31 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5F621F85FD; Thu, 24 May 2012 01:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1337848410; d=isode.com; s=selector; i=@isode.com; bh=1+fS+vrIYw5fHFLlvwVeRV5Y0fi4KKv0f/QjpxlRHRs=; 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=lJN0BmbZEzgw+63q0CMBoaiMpDiW6XssutUOenxaj3Bkq0r2bIhSXwSRyzyiSAfYhaBAnN Ha2rW5+ntLTk5yD1Vlh4J2WSlAcV9fzyQeVLSy/CmEm/T9RFHZKXKTM9ifmaqXMSpkSb8I UsRGUOv8sD/VlH4VZE0L6CFgSAuilAY=;
Received: from [192.168.1.144] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T73yWgAE4yDB@rufus.isode.com>; Thu, 24 May 2012 09:33:30 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
Message-ID: <4FBDF270.10606@isode.com>
Date: Thu, 24 May 2012 09:33:52 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-melnikov-smtp-priority-13
References: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
In-Reply-To: <4fb89431.634cb40a.0fe6.ffffbced@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------050109010604060202050908"
Cc: gen-art@ietf.org, draft-melnikov-smtp-priority.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, 24 May 2012 08:33:32 -0000

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

Hi Roni,

On 20/05/2012 07:47, 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-melnikov-smtp-priority-13
>
> Reviewer: Roni Even
>
> Review Date:2012--5--20
>
> IETF LC End Date: 2012--5--28
>
> IESG Telechat date:
>
> Summary: This draft is ready for publication as a standard track RFC.
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
> 1.MUA is used but not expanded.
>

Expanded the first reference in my copy, thanks.


--------------050109010604060202050908
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">
    Hi Roni,<br>
    <br>
    On 20/05/2012 07:47, Roni Even wrote:
    <blockquote cite="mid:4fb89431.634cb40a.0fe6.ffffbced@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="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: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;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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">I am the assigned Gen-ART reviewer for this
          draft. For background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Please resolve these comments along with
          any other Last Call comments you may receive.<o:p></o:p></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
          </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">draft-melnikov-smtp-priority-13<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
            Roni Even<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
            Date:2012&#8211;5&#8211;20<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
            LC End Date: 2012&#8211;5&#8211;28<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
            Telechat date:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
            This draft is ready for publication as a standard track </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">RFC</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
            comments:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">MUA is used but
            not expanded.</span></p>
      </div>
    </blockquote>
    <br>
    Expanded the first reference in my copy, thanks.<br>
    <br>
  </body>
</html>

--------------050109010604060202050908--

From shanna@juniper.net  Thu May 24 06:10:03 2012
Return-Path: <shanna@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 CC28121F852A; Thu, 24 May 2012 06:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.701
X-Spam-Level: 
X-Spam-Status: No, score=-105.701 tagged_above=-999 required=5 tests=[AWL=0.898, 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 toA1ntr12YBi; Thu, 24 May 2012 06:10:03 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF3B21F8523; Thu, 24 May 2012 06:10:01 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT74zKPRnXvty282Gmexf/Q9g1Y89DavE@postini.com; Thu, 24 May 2012 06:10:02 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 24 May 2012 06:07:35 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 24 May 2012 09:07:35 -0400
From: Stephen Hanna <shanna@juniper.net>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 24 May 2012 09:07:33 -0400
Subject: Updated secdir review of draft-ietf-emu-chbind-16.txt
Thread-Topic: Updated secdir review of draft-ietf-emu-chbind-16.txt
Thread-Index: Ac03m9Vz0ExW5KUcShO4ogGhcZvyUgAAFxvwAIQuNxA=
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB82FC94472@EMBX01-WF.jnpr.net>
References: <20120514190642.11168.14882.idtracker@ietfa.amsl.com> <tslvcjy37fi.fsf@mit.edu> <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net> <tslr4udmce6.fsf@mit.edu> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 13:10:04 -0000

Sam,

Thanks for addressing my comments in draft-ietf-emu-chbind-16.txt.
I'm happy with this version. All my substantive concerns are addressed.

I do see two non-substantive issues. These can be addressed in some
future version or not at all.

1) The word "subvert" is misspelled as "subvirt" in the new text.

2) Editing Charles Clancy's address in the Authors' Addresses section
   has apparently caused the list of authors in the top right corner of
   the first page to revert to this suboptimal form:

EMU Working Group                                        S. Hartman, Ed.
Internet-Draft                                         Painless Security
Intended status: Standards Track                               T. Clancy
Expires: November 25, 2012                      Department of Electrical
                                        Engineering and Computer Science
                                                               K. Hoeper
                                                Motorola Solutions, Inc.

   As you can see, Dr. Clancy's affiliation has now changed back to
   "Department of Electrical Engineering and Computer Science". I guess
   that whatever tool you're using to create the draft must insist on
   placing the second line of each author's address on the first page.
   If that's the case, you might want to change Dr. Clancy's address to

   T. Charles Clancy
   Virginia Tech
   Department of Electrical Engineering and Computer Science
   Arlington, VA  22203
   USA

   Or perhaps you'll just have to surrender to the flawed tool and
   leave the credit for Dr. Clancy on the first page as nonsensical.

Thanks for your patience in addressing the issues that I raised.
I think the document is much better for this attention.

Take care,

Steve

> -----Original Message-----
> From: Stephen Hanna
> Sent: Tuesday, May 22, 2012 4:00 PM
> To: 'Sam Hartman'
> Cc: emu@ietf.org; secdir@ietf.org; ietf@ietf.org
> Subject: RE: Updated secdir review of draft-ietf-emu-chbind-15.txt
>=20
> Sam,
>=20
> I see now that you are concerned not with circumstances where
> the NAS terminates the tunnel by design but rather with times
> when the NAS is maliciously terminating the tunnel. I'm glad
> that we both agree that having the NAS terminate the tunnel
> is highly undesirable. That did not come through in the draft.
> I'm much relieved to learn that nobody is suggesting this
> as a desirable outcome. I agree that it's an attack scenario
> that must be considered and carefully addressed.
>=20
> Maybe we can resolve this issue by clarifying the text to
> say more clearly that we're dealing with an attack scenario
> here. For example, we could add a sentence before the words
> "Tunnel methods sometimes use" saying something like "However,
> this is not secure if the NAS can terminate the tunnel (a
> highly undesirable situation)." Then you can mention several
> countermeasures against such an attack: mutual cryptographic
> bindings (still just a -00 individual draft), carefully
> checking the EAP server's identity, etc. We might also take
> this opportunity to split this long paragraph into two:
> one that includes the first three sentences (describing how
> EAP tunnel methods can support channel binding) and another
> describing the attack scenario and countermeasures.
>=20
> Thanks,
>=20
> Steve
>=20
> > -----Original Message-----
> > From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> > Sent: Monday, May 21, 2012 5:51 PM
> > To: Stephen Hanna
> > Cc: Sam Hartman; emu@ietf.org; secdir@ietf.org; ietf@ietf.org
> > Subject: Re: Updated secdir review of draft-ietf-emu-chbind-15.txt
> > Importance: High
> >
> > >>>>> "Stephen" =3D=3D Stephen Hanna <shanna@juniper.net> writes:
> >
> >     Stephen> The changes in draft-ietf-emu-chbind-15.txt
> satisfactorily
> >     Stephen> address almost all of the comments in my April 13, 2012
> >     Stephen> secdir review. I do have one remaining substantive
> comment
> >     Stephen> on this latest draft and two non-substantive ones.
> >
> >     Stephen> Substantive Comment -------------------
> >
> >     Stephen> The last paragraph of section 9.1 points out a security
> >     Stephen> problem with implementing channel bindings using EAP
> > tunnel
> >     Stephen> methods. If the EAP tunnel method terminates on the
> >     Stephen> authenticator, the channel bindings can easily be
> defeated
> >     Stephen> by the authenticator. While that's true, nobody
> terminates
> >     Stephen> the EAP tunnel method on the authenticator today. In the
> >     Stephen> EAP model, the authenticator is not trusted so
> terminating
> >     Stephen> the EAP tunnel method on the authenticator is a bad idea
> >     Stephen> for many reasons. For example, the authenticator would
> > then
> >     Stephen> have the ability to bypass protected result indications
> > and
> >     Stephen> to bypass all the cryptographic protections provided by
> > the
> >     Stephen> tunnel.  Sometimes there is value in having the inner
> and
> >     Stephen> outer methods terminate on different servers but both
> >     Stephen> servers must be trusted.  The authenticator is not. So
> >     Stephen> there is no big security hole here, unless you have
> > already
> >     Stephen> opened an enormous security hole. It's ironic that this
> >     Stephen> document which attempts to close vulnerabilities caused
> by
> >     Stephen> malicious authenticators ends up subtly suggesting that
> >     Stephen> people open a much larger vulnerability!
> >
> >     Stephen> I would recommend deleting the end of this paragraph,
> >     Stephen> starting with the sentence that starts "Even when
> >     Stephen> cryptographic binding".>
> >
> > I disagree very strongly with this proposed change.  It's possible
> that
> > the text is not clear and I'd be happy to work for a round or two to
> > see
> > if we can clarify the text, but ending the paragraph as you propose
> > would defeate the point of text we added after a WG consensus call.
> >
> > I agree with you that authenticators are not trusted.
> > The issue is that you cannot trust attackers to act within a
> > specification.
> > If an attacker can gain benefit from doing something, they may do so.
> >
> > So, if an attacker can create a tunnel terminating at an
> authenticator
> > and gain advantage from doing so, then they will do so.
> >
> > Remember that we're talking about crypto binding. If crypto binding
> is
> > relevant for confirming there are no extra servers, then we're in a
> > threat model space where we're trusting the inner method to
> > authenticate
> > the server, not the outer method.  You can't say "you should only
> > establish trusted tunnels," because we're hoping that crypto binding
> > will give us that trust.  So, the issue here is that once you add
> > channel bindings and the associated changes to the threat model to
> EAP,
> > an authenticator can gain advantage through convincing a client to
> > trust
> > a tunnel that terminates at an authenticator.  That is, an
> > authenticator
> > can mount an attack.  Yes, the authenticator needs to convince the
> peer
> > to trust the extra tunnel. However, as I discuss in
> > draft-hartman-emu-mutual-crypto-binding and in my presentation at
> last
> > IETF, that's often fairly easy.
> >
> > So, how can we make the text more clear?

From marshall.eubanks@gmail.com  Thu May 24 07:12:12 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F0F21F85E3 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 07:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.557
X-Spam-Level: 
X-Spam-Status: No, score=-103.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 F2HPIdMhk78I for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 07:12:11 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3223321F8577 for <ietf@ietf.org>; Thu, 24 May 2012 07:12:11 -0700 (PDT)
Received: by lagv3 with SMTP id v3so6888607lag.31 for <ietf@ietf.org>; Thu, 24 May 2012 07:12: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:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6V84GXDz6XgopQ1XzYLHsw3VzkXxpjKOi6MU7eOcrhQ=; b=USq8aG/kvdwSn7B88211CiJJbY00rPfwW+0IZDsT4mliUk5CRxTt20tbaEnJrBzY6v HBYA1i2+L/kYQ2wVNtq1s+/EHz0ezeGiI5vjONNk+7FCKdgCRr3gaUeW9YsUiTq8ab0z kfew1Fjc/TAxgU/gv0A2oLgfvn1TGGgJjAD2Tibz2odBHExEYKpik/vEgZoZOkWhf+NA hG7+C82vLqZU1lzyPvzIxfxlZ3RXwwiFDmSLH8ghEhd9AHz87j/z9nYzXrITKJosNpEi K1C2xmAT27mU0PbQOVLdxUbhQYqeO5KoY5GosHIqhE/DRaFrWIvMMHh66ExAxPAtix6a 94Mg==
MIME-Version: 1.0
Received: by 10.112.36.195 with SMTP id s3mr13618834lbj.42.1337868730062; Thu, 24 May 2012 07:12:10 -0700 (PDT)
Received: by 10.112.132.65 with HTTP; Thu, 24 May 2012 07:12:09 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120510123935.094139d0@resistor.net>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com> <367E45C5495F9BDB6E24C211@PST.JCK.COM> <6.2.5.6.2.20120510123935.094139d0@resistor.net>
Date: Thu, 24 May 2012 10:12:09 -0400
Message-ID: <CAJNg7V+9+_mab9SJQeM9jnwpObcwjVq=351WNwt2NeMstvQwBA@mail.gmail.com>
Subject: Re: Future Handling of Blue Sheets
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Thu, 24 May 2012 14:12:12 -0000

For what it is worth, here is my opinion on this subject (which I was
asked to post here).

I see  possible privacy law problems with posting the blue sheets, so
I would not.

I see a good reason to scan and have images of new blue sheets, make
it easier to respond to subpoenas.

I do see a historical benefit to keeping the blue sheets (as blue
sheets, not just scans), and the expense
of doing so is minimal, so I would urge that their archiving be continued.

Regards
Marshall

On Thu, May 10, 2012 at 6:11 PM, SM <sm@resistor.net> wrote:
> Hi John,
>
> At 11:31 10-05-2012, John C Klensin wrote:
>>
>> participate in any way in an affected WG. =A0I hate the idea of
>> the community getting embroiled in accusations and
>> counter-accusations but one advantage to a working IPR policy
>> (as well as general openness) of publishing the blue sheets is
>
>
> I am fine either way with the handling of the blue sheets. =A0I am also f=
ine
> with whatever the IESG decides (on this topic only :-)). =A0This topic ha=
s
> been sold as a matter of openness. =A0The question can be traced back to
> newspaperization. =A0In those days, propagation of information was locali=
zed.
> =A0Nowadays, it can be globalized. =A0That can be good; it can also be ba=
d.
>
> The scrawls from the blue sheets will be accessible after around a month.
> =A0Should the world be able to find out that:
>
> =A0(i) =A0you were in Paris
>
> =A0(ii) you attended the EAI session
>
> Now let's assume that the work is covered by one of your inventions.
> =A0Although you were in that session according to the blue sheets, you di=
d not
> participate in the discussion according to the minutes (the analogy is th=
at
> you are subscribed to the mailing list but you have not posted any
> messages). =A0Do you have to file an IPR disclosure?
>
> Coming back to being open and transparent, the IETF tends to have a varia=
ble
> stance on that. =A0Exposing information allows other people to evaluate
> fairness, whether there is conflict of interest, etc. =A0It does not alwa=
ys
> work out well; some people may be unhappy, offended or uncomfortable. =A0=
If
> you look at the list of WGs being tracked, you will notice that some peop=
le
> provided the information, some didn't. =A0I didn't ask why. =A0As a quick
> thought, I guess that people are uneasy with the idea of the information
> being publicized to the world or they used the default, this information =
is
> not relevant to any random person.
>
> Let's ignore the IPR argument. =A0What question(s) should one ask in sett=
ing
> the boundaries for open and transparent?
>
> Regards,
> -sm

From weiler+secdir@watson.org  Wed May 23 16:12:20 2012
Return-Path: <weiler+secdir@watson.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 3F69411E8072; Wed, 23 May 2012 16:12: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 ouNN4g+fyEJk; Wed, 23 May 2012 16:12:19 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 897D121F8603; Wed, 23 May 2012 16:12:19 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id q4NNCItk072501; Wed, 23 May 2012 19:12:18 -0400 (EDT) (envelope-from weiler+secdir@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id q4NNCHjx072494; Wed, 23 May 2012 19:12:17 -0400 (EDT) (envelope-from weiler+secdir@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Wed, 23 May 2012 19:12:17 -0400 (EDT)
From: Samuel Weiler <weiler+secdir@watson.org>
X-X-Sender: weiler@fledge.watson.org
To: secdir@ietf.org, ietf@ietf.org, draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org
Subject: secdir review of draft-sakane-dhc-dhcpv6-kdc-option
Message-ID: <alpine.BSF.2.00.1205231837020.9762@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Wed, 23 May 2012 19:12:18 -0400 (EDT)
X-Mailman-Approved-At: Thu, 24 May 2012 08:16:08 -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, 23 May 2012 23:12:20 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This doc specifies several DHCPv6 options for carrying Kerberos config 
info.  There are obvious risks to doing this, but they're discussed 
reasonably well in this and similar cited docs (e.g. RFC3634, which 
specifies a much more limited option for DHCPv4).  The doc explains by 
DNS service discovery isn't ideal for some environments.

With that said, there are some things that need clarification, and the 
doc sorely needs an editorial pass.  As-is, the doc is not ready for 
publication.  I will be happy to review the doc again once it's been 
thoroughly edited.


Things that need clarification or consideration:

For the transport type field, would it be better to use a bitmask? 
Then one could use a single DHCPv6 option to specify a KDC that's 
reachable over both TCP and UDP, rather than needing two DHCPv6 
options.

Section 7 uses the term "TGT" without expansion.  In the Kerberos 
world I can't imagine someone not knowing what this is, but it's not 
clear to the layman.  It probably needs to be expanded.

The algorithm in section 4.1 needs work.  The obvious thing is to read 
it linearly.  Doing that, one would prefer DHCP over DNS SVR info (per 
step 2), which is not what step 6 and the graphic say.

Saying "no answer from the DNS server" is probably not the desired 
semantic.

In 3.4, the option-len field is ambiguous.  It says "24-octet + the 
length of the realm-name field in octets."  But it looks to me like 
this option is 27 octets + length of realm name.  Perhaps it would be 
better to just count the length of the realm name?


And here are some examples of wording that needs work.  There are many 
more -- I quit copying them into this review after the first few:

3.2 "This option informs a DHCPv6 server of which realm the client 
want to access, ..."

7 "... a rogue KDC that does not know the client access."  What is 
"the client access"?

"The incorrect KDC is not be able to proceed any further state of the 
client."

"The considerable situation is that the support of an unconfigured 
workstation used by multiple users, which obtains its KDC information 
and default realm via DHCP."

From pradeepar@gmail.com  Wed May 23 16:31:15 2012
Return-Path: <pradeepar@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD0421F8699 for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 16:31:15 -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 pVyzsTdiemwV for <ietf@ietfa.amsl.com>; Wed, 23 May 2012 16:31:14 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 51A7821F8697 for <ietf@ietf.org>; Wed, 23 May 2012 16:31:02 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so10782390pbc.31 for <ietf@ietf.org>; Wed, 23 May 2012 16:31:02 -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=g7coAu9k2riz9FddFkydAz2EqptiMdlzewcy8qD90Rg=; b=CTOqiI+hPyLdRTsXzc6NUfdaEguUurPYB1QqO1Spg0FxPzP1OVSMaBGVjblLPA13sv zIkneQiNXmMlyN0MTmVvoPbMjnUCV/XhDvmcNgNJySlZsEiHHk4TGpsMcROPWURNEm+l w3BOOM4GG1TFOxkIYDEd67tI5/UEUClcsejJcaihzckJFMj7S23z05PwAoTdwjPeCHzM iLzqdkcGXIAwDCjQ0i7PBpRfEqZ0OgCgQOCMuQpJCNHuKeKMS8VvZpOPHm9PwQELVD3X EBgyEJMJn/4f5KmYx1F4H6dDTtZt0+1FSMxSNCsia2Nr2QambVioolmw0TgbHY/vDnDs znlQ==
MIME-Version: 1.0
Received: by 10.68.125.138 with SMTP id mq10mr15528196pbb.25.1337815862049; Wed, 23 May 2012 16:31:02 -0700 (PDT)
Received: by 10.68.25.37 with HTTP; Wed, 23 May 2012 16:31:02 -0700 (PDT)
Date: Thu, 24 May 2012 05:01:02 +0530
Message-ID: <CAGoJNch4YVXF92TmY7HLWeUzBZH9K9sQv69HWswk9OLuo0CPOQ@mail.gmail.com>
Subject: Question on DHCPv6 / RFC3315
From: pradeep ramachandran <pradeepar@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=047d7b2e4d6e3b7adc04c0bc87cc
X-Mailman-Approved-At: Thu, 24 May 2012 08:16:08 -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, 23 May 2012 23:33:53 -0000

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

Hello All

Had a question on RFC 3315, Section 18.1.2 Creation and Transmission of
Confirm messages

When a client changes its configuration from dhcpv6 enabled to static ipv6,
is this considered as moving to a new link and is the client required to
send out a Confirm message ?

Thanks
pradeep

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

<div>Hello All<br>=A0<br>Had a question on RFC 3315, Section 18.1.2 Creatio=
n and Transmission of Confirm messages<br>=A0<br>When a client=A0changes it=
s configuration from dhcpv6 enabled to static ipv6, is this considered as m=
oving to a new link and is the client required to send out a Confirm messag=
e ? <br>
=A0<br>Thanks</div>
<div>pradeep</div>

--047d7b2e4d6e3b7adc04c0bc87cc--

From cabo@tzi.org  Thu May 24 08:37:28 2012
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 CE2E421F860E for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 08:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.149
X-Spam-Level: 
X-Spam-Status: No, score=-106.149 tagged_above=-999 required=5 tests=[AWL=0.100, 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 JjqVlt0jkB5o for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 08:37:28 -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 19C7521F85FF for <ietf@ietf.org>; Thu, 24 May 2012 08:37:27 -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.3/8.14.3) with ESMTP id q4OFbKt6023949; Thu, 24 May 2012 17:37:20 +0200 (CEST)
Received: from eduroam-pool6-0073.wlan.uni-bremen.de (eduroam-pool6-0073.wlan.uni-bremen.de [134.102.24.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5617DFC3; Thu, 24 May 2012 17:37:20 +0200 (CEST)
Subject: Re: Future Handling of Blue Sheets
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAJNg7V+9+_mab9SJQeM9jnwpObcwjVq=351WNwt2NeMstvQwBA@mail.gmail.com>
Date: Thu, 24 May 2012 17:37:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6ECB0955-72FE-4866-97AD-7D0D92581CFD@tzi.org>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com> <367E45C5495F9BDB6E24C211@PST.JCK.COM> <6.2.5.6.2.20120510123935.094139d0@resistor.net> <CAJNg7V+9+_mab9SJQeM9jnwpObcwjVq=351WNwt2NeMstvQwBA@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF list 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, 24 May 2012 15:37:28 -0000

On May 24, 2012, at 16:12, Marshall Eubanks wrote:

> For what it is worth, here is my opinion on this subject (which I was
> asked to post here).
>=20
> I see  possible privacy law problems with posting the blue sheets, so
> I would not.
>=20
> I see a good reason to scan and have images of new blue sheets, make
> it easier to respond to subpoenas.
>=20
> I do see a historical benefit to keeping the blue sheets (as blue
> sheets, not just scans), and the expense
> of doing so is minimal, so I would urge that their archiving be =
continued.

To me this seems to be the compelling, non-surprising result of this =
discussion.
We don't need another 100 messages to finally arrive at the same result.
So it would help if the responsible I* would make a decision, please.

Gr=FC=DFe, Carsten


From jhutz@cmu.edu  Thu May 24 10:50:41 2012
Return-Path: <jhutz@cmu.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 3AA7621F8595; Thu, 24 May 2012 10:50:41 -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 2IiD-2Ivl0cG; Thu, 24 May 2012 10:50:40 -0700 (PDT)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9FC21F847D; Thu, 24 May 2012 10:50:40 -0700 (PDT)
Received: from [128.2.210.96] (destiny.pc.cs.cmu.edu [128.2.210.96]) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q4OHoc3l014311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 May 2012 13:50:38 -0400 (EDT)
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Samuel Weiler <weiler+secdir@watson.org>
In-Reply-To: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org>
References: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 24 May 2012 13:50:37 -0400
Message-ID: <1337881837.3279.45.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, secdir@ietf.org, ietf@ietf.org, jhutz@cmu.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, 24 May 2012 17:50:41 -0000

On Wed, 2012-05-23 at 19:12 -0400, Samuel Weiler wrote:

> With that said, there are some things that need clarification, and the 
> doc sorely needs an editorial pass.  As-is, the doc is not ready for 
> publication.  I will be happy to review the doc again once it's been 
> thoroughly edited.

It does need copy-editing.  As far as I know, the IETF does not have a
team of volunteer copy-editors, and multiple attempts to get help from
within the working group have met with only limited success (most
notably in the form of help from Stephen, who did quite a bit of work on
this before starting on his AD review).  If anyone wants to volunteer to
spend some time on helping to clean up this document, let me know.

Otherwise, I think our only options are either to ask the paid editors
at the RFC production center to take a stab, or block an otherwise
completed document on cycles that may never appear.


> Section 7 uses the term "TGT" without expansion.  In the Kerberos 
> world I can't imagine someone not knowing what this is, but it's not 
> clear to the layman.  It probably needs to be expanded.

It does; I somehow missed that in my review.


> The algorithm in section 4.1 needs work.  The obvious thing is to read 
> it linearly.  Doing that, one would prefer DHCP over DNS SVR info (per 
> step 2), which is not what step 6 and the graphic say.

The algorithm is fine, but the description requires careful reading.
Step 2 kicks in only if you get a DHCP response containing Kerberos
configuration but no nameservers.  


> Saying "no answer from the DNS server" is probably not the desired 
> semantic.

There are only two branches here.  Either you get a response containing
one or more relevant SRV RRs, or you don't.  The latter is phrased as
"no answer from the DNS server", but is meant to also include errors and
empty responses.  A suggestion for how to word this better would be
welcome.


> In 3.4, the option-len field is ambiguous.  It says "24-octet + the 
> length of the realm-name field in octets."  But it looks to me like 
> this option is 27 octets + length of realm name.  Perhaps it would be 
> better to just count the length of the realm name?

Yes, the description is wrong; the correct length is _23_ plus the
length of the realm.  The 16-bit option code and length are part of the
DHCPv6 protocol; unless I'm misremembering, the length is the length of
the option payload (that is, excluding the two header fields).


Thanks for taking the time to review this.

-- Jeff


From vinayakh@gmail.com  Thu May 24 10:58:14 2012
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 D7BE121F85F9 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 10:58:14 -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 vkbpUQdY2BEh for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 10:58:14 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D081A21F85F7 for <ietf@ietf.org>; Thu, 24 May 2012 10:58:13 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so47075vbb.31 for <ietf@ietf.org>; Thu, 24 May 2012 10:58:13 -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=dRuBxyYN6ZLs09JKu9g3H43gv7rey3ikWhKcAs/x3Lk=; b=wyaTQ9JBzvMn8JDChQCyxy2hrjExnrrTQjdYT4551v7ZmcNCxEAusrpr79lRNPZp0f XGBjMvriyAmDigwPmOvkjuBOkJlGxaGk15Bosn1dMo4BLPRS1IYV1GDudjYE2BKm42Dz UO1Hm/ScHpyyc/WfeHJvxA3sLpV5tPbnUpenQVSu68qSqNiFMZgvJRp0HikmiMmSrfQB x3hRDJOBcwSoPZ8FeW2FRIAx869jy78Zx6hIp2WIdZy4FzpNQgpUWM4k/KRDzC6tG1HN VvYj68vEC/Ld9wHPb994BuFwfnyOIV0zv8IjiLsJXvdmNNyA4z5kWsIbIUCv7rFysljW NqDw==
MIME-Version: 1.0
Received: by 10.220.151.71 with SMTP id b7mr267151vcw.62.1337882293295; Thu, 24 May 2012 10:58:13 -0700 (PDT)
Received: by 10.52.29.1 with HTTP; Thu, 24 May 2012 10:58:13 -0700 (PDT)
Date: Thu, 24 May 2012 23:28:13 +0530
Message-ID: <CAKe6YvMpvZnLTvuJd79woRz=-72WKG6=WmmAk=bExqZjReR46w@mail.gmail.com>
Subject: Inconsistent behavior of IETF meeting registration page
From: Vinayak Hegde <vinayakh@gmail.com>
To: IETF Discussion Mailing 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, 24 May 2012 17:58:15 -0000

Hi,

I was trying to register for IETF 84 and tried the link
http://www.ietf.org/meeting/register.html from the main site.
Sometimes it takes me to the IETF 80 page (registration over) and
sometimes it takes me to the right note well page.

Trying to replicate the issue, I am seeing that it works well on IE
and Safari on Windows but not on Firefox on Linux/Windows. Further
attempts to replicate this problem on Firefox on Windows did not work.

Posting this here as I am not sure what is the right place to post
such issues. Please point me there. Also hoping that I would get more
datapoints of this problem from other people on this list (which
probably will help pinpoint the problem). Looks like a cache-expiry or
an improper redirection issue.

Either ways the workaround is to change the number of the IETF meeting
in the link as this
(https://www.ietf.org/registration/ietf84/ietfreg.py) works.

-- Vinayak

From bob.hinden@gmail.com  Thu May 24 11:32:24 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0ED611E80A4 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:32:24 -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=0.000, 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 NS3oGZBqLDW0 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:32:24 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 37A3511E8076 for <ietf@ietf.org>; Thu, 24 May 2012 11:32:24 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so85839qcs.31 for <ietf@ietf.org>; Thu, 24 May 2012 11:32:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JQpPfSqi8MIBB4gJs7oq2nB0PYochguJ0yQuO91Q1NY=; b=AS5j4Bn9UwZqBJ+Dn4fkgvaRuV1X9F+xNhqKlCH6PClUs+QRA8UqMzNTFa29I7L1fO 4Su1GmAS73ChLQ4pOzL5ZDe+x10xAan0X9dyCZ5x7zzBHCQQZmjUkjxO2wxqo5KgwD+N oA9GwuX90I9jAqSJ14k/eVzpPj2wmFIDEeQu3lAri11IDbxgG81IMXZRu/wZ8Jg16T3x stReEi5EB/eDuMJIKMcYGG1c4bw6rVujco4lSoY/X6+ynUo+6yZsjWLAUtrQ1rqDvRqt l4vvTnDgEAp3T4cJP0reg0sTB5BAIK8FG6NMhMeGpFR6sPKEOoC43Yc646SgNM6a8cMO tICg==
Received: by 10.50.193.132 with SMTP id ho4mr17464766igc.17.1337884343517; Thu, 24 May 2012 11:32:23 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id k6sm8286891igz.9.2012.05.24.11.32.21 (version=SSLv3 cipher=OTHER); Thu, 24 May 2012 11:32:22 -0700 (PDT)
Subject: Re: Inconsistent behavior of IETF meeting registration page
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAKe6YvMpvZnLTvuJd79woRz=-72WKG6=WmmAk=bExqZjReR46w@mail.gmail.com>
Date: Thu, 24 May 2012 11:32:20 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <A2F13C62-547F-442B-B3B2-7768EA188DC7@gmail.com>
References: <CAKe6YvMpvZnLTvuJd79woRz=-72WKG6=WmmAk=bExqZjReR46w@mail.gmail.com>
To: Vinayak Hegde <vinayakh@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 18:32:25 -0000

Please sent it to <ietf-action@ietf.org>.

Bob

On May 24, 2012, at 10:58 AM, Vinayak Hegde wrote:

> Hi,
> 
> I was trying to register for IETF 84 and tried the link
> http://www.ietf.org/meeting/register.html from the main site.
> Sometimes it takes me to the IETF 80 page (registration over) and
> sometimes it takes me to the right note well page.
> 
> Trying to replicate the issue, I am seeing that it works well on IE
> and Safari on Windows but not on Firefox on Linux/Windows. Further
> attempts to replicate this problem on Firefox on Windows did not work.
> 
> Posting this here as I am not sure what is the right place to post
> such issues. Please point me there. Also hoping that I would get more
> datapoints of this problem from other people on this list (which
> probably will help pinpoint the problem). Looks like a cache-expiry or
> an improper redirection issue.
> 
> Either ways the workaround is to change the number of the IETF meeting
> in the link as this
> (https://www.ietf.org/registration/ietf84/ietfreg.py) works.
> 
> -- Vinayak


From housley@vigilsec.com  Thu May 24 11:42:47 2012
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 8C5CD21F84EA for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:42:47 -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 WG6lWhU2+1va for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 11:42:47 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 19E6321F84A1 for <ietf@ietf.org>; Thu, 24 May 2012 11:42:47 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B640E9A4727 for <ietf@ietf.org>; Thu, 24 May 2012 14:43: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 TjCxEe8CIRJT for <ietf@ietf.org>; Thu, 24 May 2012 14:42:38 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-42-75.washdc.fios.verizon.net [96.255.42.75]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 072539A4725 for <ietf@ietf.org>; Thu, 24 May 2012 14:43:04 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Future Handling of Blue Sheets
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CAJNg7V+9+_mab9SJQeM9jnwpObcwjVq=351WNwt2NeMstvQwBA@mail.gmail.com>
Date: Thu, 24 May 2012 14:42:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD67670C-4A2B-4F50-B25F-77EC38DB6E24@vigilsec.com>
References: <201205101732.q4AHWQnP028852@fs4113.wdf.sap.corp> <4FABFE13.3020800@gmail.com> <367E45C5495F9BDB6E24C211@PST.JCK.COM> <6.2.5.6.2.20120510123935.094139d0@resistor.net> <CAJNg7V+9+_mab9SJQeM9jnwpObcwjVq=351WNwt2NeMstvQwBA@mail.gmail.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 18:42:47 -0000

> For what it is worth, here is my opinion on this subject (which I was
> asked to post here).
>=20
> I see  possible privacy law problems with posting the blue sheets, so
> I would not.
>=20
> I see a good reason to scan and have images of new blue sheets, make
> it easier to respond to subpoenas.
>=20
> I do see a historical benefit to keeping the blue sheets (as blue
> sheets, not just scans), and the expense
> of doing so is minimal, so I would urge that their archiving be =
continued.

During the IESG off-site meeting, this topic received quite a bit of =
discussion.  The IESG recognized that blue sheet information is valuable =
for peer pressure to abide by the IPR rules.  In contrast, I understand =
the concerns that have been raised on this thread.  As a result, I am =
looking into a mechanism where a datatracker password is needed to get =
the blue sheet images.  This would be the same password that an IETF =
community participant will to use with the soon-to-be-released =
Internet-Draft Tracking features (see RFC 6293).  These accounts are =
available to anyone; however, the need for an account to access blue =
sheet images raises the bar for access.  Additionally, the need for an =
account will keep the blue sheet images hidden from web crawlers.

Thanks to Ted hardie for the question that lead to this potential =
solution.

Russ=

From chair@ietf.org  Thu May 24 12:38:41 2012
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 D5D0211E8086; Thu, 24 May 2012 12:38: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 zPxzeBFRCcbC; Thu, 24 May 2012 12:38:41 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0C211E8081; Thu, 24 May 2012 12:38:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 582BF12C773; Thu, 24 May 2012 12:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kw8LS8Uu+jmk; Thu, 24 May 2012 12:38:38 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-42-75.washdc.fios.verizon.net [96.255.42.75]) by c8a.amsl.com (Postfix) with ESMTPSA id DE1F512C769; Thu, 24 May 2012 12:38:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Vancouver IETF Codesprint
Mime-Version: 1.0 (Apple Message framework v1084)
From: IETF Chair <chair@ietf.org>
Date: Thu, 24 May 2012 15:38:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D9B1776-6DFD-4B80-97C6-FA8774DB7BA9@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: 84all@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 19:38:42 -0000

Vancouver IETF Codesprint

When:  Saturday, 28 July 2012, starting at 9:30 AM

Where: IETF Hotel

What:  A bunch of hackers get together to work on code for the
    IETF.  All code will become part of the open source IETF tools.

Who:   Hopefully you can help

Many of the results of previous codesprint activities are being used =
every day by the IETF community.  Shortly before the Paris meeting, we =
transitioned to a new database schema.  It makes many tasks much easier. =
 Of course, the transition left some 'shim code' that should be cleaned =
up.  Please come to the codesprint and work to polish or improve =
existing tools, fix bugs, or make altogether new tools.  All efforts are =
appreciated and most welcome.

Steve Conte will be helping with advance planning.  Henrik Levkowetz =
will be coordinating the event in Vancouver.  You can find more =
information here:

   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF84Sprint

If you are able to participate, please sign up on the wiki at:

   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF84SprintSignUp

Please support the tools development effort,
  Russ


From stpeter@stpeter.im  Thu May 24 15:01:51 2012
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 C8DAD11E808A for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 15:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uR44zd70SsiA for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 15:01:50 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 21E7511E8081 for <ietf@ietf.org>; Thu, 24 May 2012 15:01:50 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D818D4005A; Thu, 24 May 2012 16:17:58 -0600 (MDT)
Message-ID: <4FBEAFC8.40703@stpeter.im>
Date: Thu, 24 May 2012 16:01:44 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net>
In-Reply-To: <6.2.5.6.2.20120522233611.08d14c78@resistor.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2012 22:01:51 -0000

On 5/23/12 2:16 AM, SM wrote:
> Hi Peter,
> 
> I understand why the intended status is not BCP.  I suggest taking into
> account the wider audience feedback to determine whether the it should
> not be made clearer.

OK, Tim and I will look into perhaps adding a sentence or two about this.

> A question which is not covered by the draft is when a draft is
> "adopted" through a charter.  I assume that the AD will contact the
> authors in such cases.

Even if a document is mentioned in a charter as a likely starting point,
the chairs still need to make an explicit call for adoption of that
document as a WG item.

> In Section 2:
> 
> There is a typo, "secretatires".
> 
> in Section 3.1:
> 
>   "If necessary disclosures have not been submitted, the chairs have a
>    choice: insist on an informal disclosure in the presentation, or deny
>    the agenda slot unless the IPR disclosure is submitted.  One factor
>    in this decision could be the number of revisions that have occurred:
>    the chairs might wish to permit presentation of a -00 draft with a
>    verbal disclosure, but not after a draft has gone through multiple
>    cycles."
> 
> The boilerplate explicitly states that this draft as any other draft is
> submitted in full conformance with the provisions of the usual BCPs.  If
> disclosures are necessary they should be submitted especially if the
> goal of this draft is to promote compliance.  Informal disclosures
> causes uncomfortable situations as there are usually valid reasons. 
> There is also the presumption of good faith which makes it a difficult
> decision.  I don't know how often verbal disclosures go on record. 

The slides and audio are part of the record.

> The
> information may not be available to the working group (decisions are
> taken through the mailing list) unless the participants go through the
> audio.

Naturally it would be best if the disclosure were explicitly called out
in the minutes, as well. However, I agree with you that a formal
disclosure is always best. Let me chat about this with Tim.

> In A.1:
> 
>   "In order to comply with IETF processes while avoiding unnecessary
>    delays, document authors and contributors to our discussions in
>    the FOO WG are asked to take these messages seriously, and to
>    reply in a timely fashion."
> 
> Is there any message from WG chairs which should not be taken seriously?
> :-)  I'll suggest:
> 
>    In order to comply with IETF processes and avoid unnecessary delays,
>    document authors and contributors to our discussions in the FOO WG
>    are asked to take pay careful attention to these messages and to
>    reply in a timely fashion.

WFM.

> In A.2:
> 
>   "We will weigh this information when we judge the consensus on
>   the call for adoption."
> 
> The wording is not that clear.  It is up to the participants to see
> whether they are ok to work the specification given the IPR claims.  Sam
> Hartman posted some possible responses in such cases (
> http://www.ietf.org/mail-archive/web/oauth/current/msg08992.html ). 

Yes, I saw that message, and I thought it was helpful.

> What we were are looking for here is whether there are any claims.  The
> easy path is to remove the sentence and keep the IPR question for the
> follow-up question.

Now your wording is not clear to me. What do you mean by "the follow-up
question"?

> In A.3:
> 
>   "The authors of draft-ietf-foo-wiffle have asked for a Working Group
>    Last Call.  Before issuing the Last Call, we would like to check"
> 
> I suggest "before issuing the Working Group Last Call" as Last Call is
> generally considered as what's in the subject line of this message.

Good point.

Thanks for the feedback!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From sm@resistor.net  Thu May 24 16:12:26 2012
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 7101011E80A3 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 16:12: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 KkxGsxTVUJb5 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 16:12: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 27E5D11E8081 for <ietf@ietf.org>; Thu, 24 May 2012 16:12:23 -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 q4ONCBUt020935; Thu, 24 May 2012 16:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1337901137; i=@resistor.net; bh=1wlIsamDvVu/MIoKvvJn7lY+ZFTLG45x39iW1NEam88=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=a8emTV5AJtirGgVXTfoo3NMgI0iWEQWLH1UFfkbYkj+l1zXRTirnspVgJLOQLrv/v /FT1XgeTfxtn9JwnXVHGIJJj6qdfm1mmCv7VmhZ9vQ+apFJfjcHLIvz3BHH2AqCMrW lh0TDRx53BeANKYHaCkVFJLWkSVywG+AHGumxgCE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1337901137; i=@resistor.net; bh=1wlIsamDvVu/MIoKvvJn7lY+ZFTLG45x39iW1NEam88=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0sOE+muICLzpoUHP8mKLiEp+O6xpdTkklSkT1r5+FpuxIbZeng2lc+pV0Tz063JTT o07sPgehoNCMG7oIwvcUFtVtwzni1x86/YBqFUeQvxPBOwqhcFmcYoGTagY/9OM0nO vPKBhS55UnlrtbAeYyuRPaAf4dJH2X3L1L+mquto=
Message-Id: <6.2.5.6.2.20120524154050.09714b10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 24 May 2012 16:10:18 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
In-Reply-To: <4FBEAFC8.40703@stpeter.im>
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net> <4FBEAFC8.40703@stpeter.im>
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, 24 May 2012 23:12:26 -0000

Hi Peter,
At 15:01 24-05-2012, Peter Saint-Andre wrote:
>Even if a document is mentioned in a charter as a likely starting point,
>the chairs still need to make an explicit call for adoption of that
>document as a WG item.

Ok.

>The slides and audio are part of the record.

The audio seemed like a grey area to me.  I'll keep that discussion 
for another day.

>Naturally it would be best if the disclosure were explicitly called out
>in the minutes, as well. However, I agree with you that a formal
>disclosure is always best. Let me chat about this with Tim.

Ok.

> > What we were are looking for here is whether there are any claims.  The
> > easy path is to remove the sentence and keep the IPR question for the
> > follow-up question.
>
>Now your wording is not clear to me. What do you mean by "the follow-up
>question"?

The possible steps are:

   1. Reminder checks whether there are claims of IPR that needs
      to be disclosed

   2. Someone mentions a claim

   3. Ask the WG whether they are ok given the new information

   4. consensus call on the technical work

Step 3 is the follow-up question.  I consider it as separate as what 
is being asked of the WG participant is not clear.  Some guidance is 
needed so participants know what they are being asked to do or what 
they can say (see past OAUTH thread as an example).

Regards,
-sm 


From stpeter@stpeter.im  Thu May 24 17:25:18 2012
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 8523F11E808D for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 17:25: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xs4TP3o1-aNg for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 17:25:18 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1443111E8081 for <ietf@ietf.org>; Thu, 24 May 2012 17:25:18 -0700 (PDT)
Received: from [192.168.0.9] (unknown [216.17.175.135]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id EDC144005A; Thu, 24 May 2012 18:41:27 -0600 (MDT)
Message-ID: <4FBED16C.3080008@stpeter.im>
Date: Thu, 24 May 2012 18:25:16 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net> <4FBEAFC8.40703@stpeter.im> <6.2.5.6.2.20120524154050.09714b10@resistor.net>
In-Reply-To: <6.2.5.6.2.20120524154050.09714b10@resistor.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 00:25:18 -0000

On 5/24/12 5:10 PM, SM wrote:
> Hi Peter,
> At 15:01 24-05-2012, Peter Saint-Andre wrote:
>> Even if a document is mentioned in a charter as a likely starting point,
>> the chairs still need to make an explicit call for adoption of that
>> document as a WG item.
> 
> Ok.
> 
>> The slides and audio are part of the record.
> 
> The audio seemed like a grey area to me.  I'll keep that discussion for
> another day.
> 
>> Naturally it would be best if the disclosure were explicitly called out
>> in the minutes, as well. However, I agree with you that a formal
>> disclosure is always best. Let me chat about this with Tim.
> 
> Ok.
> 
>> > What we were are looking for here is whether there are any claims.  The
>> > easy path is to remove the sentence and keep the IPR question for the
>> > follow-up question.
>>
>> Now your wording is not clear to me. What do you mean by "the follow-up
>> question"?
> 
> The possible steps are:
> 
>   1. Reminder checks whether there are claims of IPR that needs
>      to be disclosed
> 
>   2. Someone mentions a claim
> 
>   3. Ask the WG whether they are ok given the new information
> 
>   4. consensus call on the technical work
> 
> Step 3 is the follow-up question.  I consider it as separate as what is
> being asked of the WG participant is not clear.  Some guidance is needed
> so participants know what they are being asked to do or what they can
> say (see past OAUTH thread as an example).

Got it. Thanks!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From narten@us.ibm.com  Thu May 24 21:54:01 2012
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 C0AFD21F8518 for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 21:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.299
X-Spam-Level: 
X-Spam-Status: No, score=-108.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-W5CUk+oBtr for <ietf@ietfa.amsl.com>; Thu, 24 May 2012 21:54:01 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id E00C621F8512 for <ietf@ietf.org>; Thu, 24 May 2012 21:53:56 -0700 (PDT)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 24 May 2012 22:53:55 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 24 May 2012 22:53:54 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 78DF13E40048 for <ietf@ietf.org>; Thu, 24 May 2012 22:53:52 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q4P4rKsG139752 for <ietf@ietf.org>; Thu, 24 May 2012 22:53:36 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q4P4rpZV024364 for <ietf@ietf.org>; Thu, 24 May 2012 22:53:51 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q4P4roM5024346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 May 2012 22:53:50 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q4P4r3pt030289 for <ietf@ietf.org>; Fri, 25 May 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q4P4r3RZ030256 for ietf@ietf.org; Fri, 25 May 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201205250453.q4P4r3RZ030256@rotala.raleigh.ibm.com>
Date: Fri, 25 May 2012 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12052504-1780-0000-0000-000005DF07ED
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000277; HX=3.00000188; KW=3.00000007; PH=3.00000001; SC=3.00000002; SDB=6.00142149; UDB=6.00032790; UTC=2012-05-25 04:53:55
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 04:54:01 -0000

Total of 59 messages in the last 7 days.
 
script run at: Fri May 25 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.47% |    5 |  5.54% |    25712 | randy@psg.com
  6.78% |    4 |  7.16% |    33268 | stpeter@stpeter.im
  3.39% |    2 |  9.13% |    42391 | ron.even.tlv@gmail.com
  5.08% |    3 |  6.59% |    30626 | shanna@juniper.net
  5.08% |    3 |  4.94% |    22928 | marshall.eubanks@gmail.com
  5.08% |    3 |  4.57% |    21219 | brian.e.carpenter@gmail.com
  5.08% |    3 |  4.30% |    19950 | rdroms.ietf@gmail.com
  1.69% |    1 |  6.05% |    28097 | bclaise@cisco.com
  3.39% |    2 |  3.54% |    16456 | trammell@tik.ee.ethz.ch
  3.39% |    2 |  3.27% |    15189 | sm@resistor.net
  3.39% |    2 |  3.15% |    14620 | hsantos@isdg.net
  3.39% |    2 |  2.53% |    11729 | cabo@tzi.org
  3.39% |    2 |  2.52% |    11728 | ned+ietf@mauve.mrochek.com
  1.69% |    1 |  2.94% |    13672 | alexey.melnikov@isode.com
  1.69% |    1 |  1.80% |     8383 | hartmans-ietf@mit.edu
  1.69% |    1 |  1.77% |     8218 | narten@us.ibm.com
  1.69% |    1 |  1.72% |     7972 | mcquilwp@pobox.com
  1.69% |    1 |  1.69% |     7844 | marka@isc.org
  1.69% |    1 |  1.65% |     7684 | abdussalambaryun@gmail.com
  1.69% |    1 |  1.57% |     7270 | weiler+secdir@watson.org
  1.69% |    1 |  1.56% |     7263 | jhutz@cmu.edu
  1.69% |    1 |  1.50% |     6980 | john-ietf@jck.com
  1.69% |    1 |  1.44% |     6703 | petithug@acm.org
  1.69% |    1 |  1.44% |     6687 | housley@vigilsec.com
  1.69% |    1 |  1.42% |     6591 | bob.hinden@gmail.com
  1.69% |    1 |  1.39% |     6464 | erosen@cisco.com
  1.69% |    1 |  1.34% |     6215 | stephen.farrell@cs.tcd.ie
  1.69% |    1 |  1.33% |     6161 | ynir@checkpoint.com
  1.69% |    1 |  1.32% |     6136 | yaakov_s@rad.com
  1.69% |    1 |  1.27% |     5907 | chair@ietf.org
  1.69% |    1 |  1.27% |     5894 | pradeepar@gmail.com
  1.69% |    1 |  1.26% |     5850 | vinayakh@gmail.com
  1.69% |    1 |  1.22% |     5646 | elwynd@folly.org.uk
  1.69% |    1 |  1.21% |     5627 | cos@aaaaa.org
  1.69% |    1 |  1.21% |     5618 | lear@cisco.com
  1.69% |    1 |  1.18% |     5462 | bortzmeyer@nic.fr
  1.69% |    1 |  1.11% |     5178 | julian.reschke@gmx.de
  1.69% |    1 |  1.11% |     5138 | dhc@dcrocker.net
--------+------+--------+----------+------------------------
100.00% |   59 |100.00% |   464476 | Total


From turners@ieca.com  Fri May 25 05:57:43 2012
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 8B7CD21F8686 for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 05:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.219
X-Spam-Level: 
X-Spam-Status: No, score=-102.219 tagged_above=-999 required=5 tests=[AWL=0.047, 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 oilCE5YsLjbE for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 05:57:42 -0700 (PDT)
Received: from gateway06.websitewelcome.com (gateway06.websitewelcome.com [67.18.21.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF9F21F868A for <ietf@ietf.org>; Fri, 25 May 2012 05:57:42 -0700 (PDT)
Received: by gateway06.websitewelcome.com (Postfix, from userid 5007) id C5CFF7016FC57; Fri, 25 May 2012 07:57:41 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway06.websitewelcome.com (Postfix) with ESMTP id BA7167016FC1E for <ietf@ietf.org>; Fri, 25 May 2012 07:57:41 -0500 (CDT)
Received: from [96.231.123.235] (port=35380 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <turners@ieca.com>) id 1SXu5M-0005cW-TS; Fri, 25 May 2012 07:57:41 -0500
Message-ID: <4FBF81C4.7050503@ieca.com>
Date: Fri, 25 May 2012 08:57:40 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Stephen Hanna <shanna@juniper.net>
Subject: Re: [Emu] Updated secdir review of draft-ietf-emu-chbind-16.txt
References: <20120514190642.11168.14882.idtracker@ietfa.amsl.com> <tslvcjy37fi.fsf@mit.edu> <AC6674AB7BC78549BB231821ABF7A9AEB82F8758EF@EMBX01-WF.jnpr.net> <tslr4udmce6.fsf@mit.edu> <AC6674AB7BC78549BB231821ABF7A9AEB82FC94472@EMBX01-WF.jnpr.net>
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AEB82FC94472@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [96.231.123.235]:35380
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: "secdir@ietf.org" <secdir@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "emu@ietf.org" <emu@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 12:57:43 -0000

Steve/Sam,

I've gone ahead and entered fixes for these two as RFC editor notes to 
ensure we won't forget them.

Thanks for working through this!

spt

On 5/24/12 9:07 AM, Stephen Hanna wrote:
> Sam,
>
> Thanks for addressing my comments in draft-ietf-emu-chbind-16.txt.
> I'm happy with this version. All my substantive concerns are addressed.
>
> I do see two non-substantive issues. These can be addressed in some
> future version or not at all.
>
> 1) The word "subvert" is misspelled as "subvirt" in the new text.
>
> 2) Editing Charles Clancy's address in the Authors' Addresses section
>     has apparently caused the list of authors in the top right corner of
>     the first page to revert to this suboptimal form:
>
> EMU Working Group                                        S. Hartman, Ed.
> Internet-Draft                                         Painless Security
> Intended status: Standards Track                               T. Clancy
> Expires: November 25, 2012                      Department of Electrical
>                                          Engineering and Computer Science
>                                                                 K. Hoeper
>                                                  Motorola Solutions, Inc.
>
>     As you can see, Dr. Clancy's affiliation has now changed back to
>     "Department of Electrical Engineering and Computer Science". I guess
>     that whatever tool you're using to create the draft must insist on
>     placing the second line of each author's address on the first page.
>     If that's the case, you might want to change Dr. Clancy's address to
>
>     T. Charles Clancy
>     Virginia Tech
>     Department of Electrical Engineering and Computer Science
>     Arlington, VA  22203
>     USA
>
>     Or perhaps you'll just have to surrender to the flawed tool and
>     leave the credit for Dr. Clancy on the first page as nonsensical.
>
> Thanks for your patience in addressing the issues that I raised.
> I think the document is much better for this attention.
>
> Take care,
>
> Steve
>
>> -----Original Message-----
>> From: Stephen Hanna
>> Sent: Tuesday, May 22, 2012 4:00 PM
>> To: 'Sam Hartman'
>> Cc: emu@ietf.org; secdir@ietf.org; ietf@ietf.org
>> Subject: RE: Updated secdir review of draft-ietf-emu-chbind-15.txt
>>
>> Sam,
>>
>> I see now that you are concerned not with circumstances where
>> the NAS terminates the tunnel by design but rather with times
>> when the NAS is maliciously terminating the tunnel. I'm glad
>> that we both agree that having the NAS terminate the tunnel
>> is highly undesirable. That did not come through in the draft.
>> I'm much relieved to learn that nobody is suggesting this
>> as a desirable outcome. I agree that it's an attack scenario
>> that must be considered and carefully addressed.
>>
>> Maybe we can resolve this issue by clarifying the text to
>> say more clearly that we're dealing with an attack scenario
>> here. For example, we could add a sentence before the words
>> "Tunnel methods sometimes use" saying something like "However,
>> this is not secure if the NAS can terminate the tunnel (a
>> highly undesirable situation)." Then you can mention several
>> countermeasures against such an attack: mutual cryptographic
>> bindings (still just a -00 individual draft), carefully
>> checking the EAP server's identity, etc. We might also take
>> this opportunity to split this long paragraph into two:
>> one that includes the first three sentences (describing how
>> EAP tunnel methods can support channel binding) and another
>> describing the attack scenario and countermeasures.
>>
>> Thanks,
>>
>> Steve
>>
>>> -----Original Message-----
>>> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
>>> Sent: Monday, May 21, 2012 5:51 PM
>>> To: Stephen Hanna
>>> Cc: Sam Hartman; emu@ietf.org; secdir@ietf.org; ietf@ietf.org
>>> Subject: Re: Updated secdir review of draft-ietf-emu-chbind-15.txt
>>> Importance: High
>>>
>>>>>>>> "Stephen" == Stephen Hanna<shanna@juniper.net>  writes:
>>>
>>>      Stephen>  The changes in draft-ietf-emu-chbind-15.txt
>> satisfactorily
>>>      Stephen>  address almost all of the comments in my April 13, 2012
>>>      Stephen>  secdir review. I do have one remaining substantive
>> comment
>>>      Stephen>  on this latest draft and two non-substantive ones.
>>>
>>>      Stephen>  Substantive Comment -------------------
>>>
>>>      Stephen>  The last paragraph of section 9.1 points out a security
>>>      Stephen>  problem with implementing channel bindings using EAP
>>> tunnel
>>>      Stephen>  methods. If the EAP tunnel method terminates on the
>>>      Stephen>  authenticator, the channel bindings can easily be
>> defeated
>>>      Stephen>  by the authenticator. While that's true, nobody
>> terminates
>>>      Stephen>  the EAP tunnel method on the authenticator today. In the
>>>      Stephen>  EAP model, the authenticator is not trusted so
>> terminating
>>>      Stephen>  the EAP tunnel method on the authenticator is a bad idea
>>>      Stephen>  for many reasons. For example, the authenticator would
>>> then
>>>      Stephen>  have the ability to bypass protected result indications
>>> and
>>>      Stephen>  to bypass all the cryptographic protections provided by
>>> the
>>>      Stephen>  tunnel.  Sometimes there is value in having the inner
>> and
>>>      Stephen>  outer methods terminate on different servers but both
>>>      Stephen>  servers must be trusted.  The authenticator is not. So
>>>      Stephen>  there is no big security hole here, unless you have
>>> already
>>>      Stephen>  opened an enormous security hole. It's ironic that this
>>>      Stephen>  document which attempts to close vulnerabilities caused
>> by
>>>      Stephen>  malicious authenticators ends up subtly suggesting that
>>>      Stephen>  people open a much larger vulnerability!
>>>
>>>      Stephen>  I would recommend deleting the end of this paragraph,
>>>      Stephen>  starting with the sentence that starts "Even when
>>>      Stephen>  cryptographic binding".>
>>>
>>> I disagree very strongly with this proposed change.  It's possible
>> that
>>> the text is not clear and I'd be happy to work for a round or two to
>>> see
>>> if we can clarify the text, but ending the paragraph as you propose
>>> would defeate the point of text we added after a WG consensus call.
>>>
>>> I agree with you that authenticators are not trusted.
>>> The issue is that you cannot trust attackers to act within a
>>> specification.
>>> If an attacker can gain benefit from doing something, they may do so.
>>>
>>> So, if an attacker can create a tunnel terminating at an
>> authenticator
>>> and gain advantage from doing so, then they will do so.
>>>
>>> Remember that we're talking about crypto binding. If crypto binding
>> is
>>> relevant for confirming there are no extra servers, then we're in a
>>> threat model space where we're trusting the inner method to
>>> authenticate
>>> the server, not the outer method.  You can't say "you should only
>>> establish trusted tunnels," because we're hoping that crypto binding
>>> will give us that trust.  So, the issue here is that once you add
>>> channel bindings and the associated changes to the threat model to
>> EAP,
>>> an authenticator can gain advantage through convincing a client to
>>> trust
>>> a tunnel that terminates at an authenticator.  That is, an
>>> authenticator
>>> can mount an attack.  Yes, the authenticator needs to convince the
>> peer
>>> to trust the extra tunnel. However, as I discuss in
>>> draft-hartman-emu-mutual-crypto-binding and in my presentation at
>> last
>>> IETF, that's often fairly easy.
>>>
>>> So, how can we make the text more clear?
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>

From rbarnes@bbn.com  Fri May 25 14:02:32 2012
Return-Path: <rbarnes@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 0058F21F87F7; Fri, 25 May 2012 14:02:31 -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 KX6I3a8nQbuy; Fri, 25 May 2012 14:02:31 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 48BFC21F87F1; Fri, 25 May 2012 14:02:31 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:55969) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SY1e1-00054m-T0; Fri, 25 May 2012 17:01:57 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
Date: Fri, 25 May 2012 17:02:28 -0400
Message-Id: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com>
To: IESG <iesg@ietf.org>, ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 21:02:32 -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-dnsext-dnssec-bis-updates-18
Reviewer: Richard Barnes
Review Date: May-25-2012
IETF LC End Date: Not known
IESG Telechat date: Jan-05-2012

Summary: Almost ready, couple of questions

MAJOR:

4.1.
It's not clear what the threat model is that this section is designed to =
address.  If the zone operator is malicious, then it can simulate the =
necessary zone cut and still prove the non-existence of records in the =
child zone. =20

5.10.
I find the recommendation of the "Accept Any Success" policy troubling.  =
It deals very poorly with compromise (and other roll-over scenarios): =
Suppose there are two trust anchors, one for example.com and one for =
child.example.com.  If the private key corresponding to the TA for =
child.example.com is compromised, but the validator continues to trust =
it, this negates the benefit provided by the parent (example.com) =
facilitating a rollover.  Suggest an alternative policy, "Highest =
Signer": Out of the set of keys configured as TAs, the validator only =
uses a key as a TA (for purposes of validation) if there does not exist =
a DNSSEC path from it to any other TA.  This policy seems like more work =
to enforce (because you have to do more backward chaining), but ISTM =
that the validator should have the necessary DNSSEC records anyway, so =
it's just a matter a couple of quick checks.




From iad@ietf.org  Fri May 25 15:00:17 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF84421F859B; Fri, 25 May 2012 15:00: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 0sBZUJBT2ec2; Fri, 25 May 2012 15:00:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD4521F8512; Fri, 25 May 2012 15:00:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: RFP for IETF Meeting Agenda Scheduling Tool
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120525220016.11236.83513.idtracker@ietfa.amsl.com>
Date: Fri, 25 May 2012 15:00:16 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 22:00:17 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF, =
announces this Request for Proposals for an IETF Meeting Agenda Scheduling =
Tool.  The successful bidder will enter into a contract with the Internet S=
ociety.

The agenda tool will manage all meeting scheduling and space allocation ass=
ociated with interim meetings, Large Interim Meetings and regular IETF meet=
ings. This includes working group sessions, leadership meetings, EDU sessio=
ns, BoFs, office hours, registration, breaks, and more.

The Secretariat will construct the agenda template in the tool by entering =
venue, date and time information. The community will input the agenda conte=
nt by submitting session requests. The tool shall include an interface for =
an automatic schedule creation capability, which may optionally be included=
 in the initial delivery or procured in the future. The schedule creation c=
apability will generate a proposed agenda by finding the most appropriate m=
atch of venue (room capacity and availability) and the session request prof=
iles, which includes conflicts to be avoided. The tool will also be flexibl=
e enough to allow for ongoing updates and schedule regeneration as the meet=
ing content evolves.

Bidders may propose customization of an existing product(s), and/or develop=
ment of the solution.

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html =


Proposals must be received via email at agenda-tool@ietf-bids.org no later =
than July 9, 2012 5:00 P.M.  All questions/inquiries must be submitted in w=
riting and must be received no later than midnight, June 18, 2012.  Respons=
es to questions and inquiries shall be posted online at:  http://iaoc.ietf.=
org/rfpsrfis.html by June 22, 2012. =


The point of contact regarding this RFP is the IETF Administrative Director=
, Ray Pelletier, iad@ietf.org.

Ray Pelletier



From fluffy@iii.ca  Fri May 25 15:30:57 2012
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 EE9A021F882D; Fri, 25 May 2012 15:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvZrM6qL2Hvx; Fri, 25 May 2012 15:30:56 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id DF77521F882E; Fri, 25 May 2012 15:30:55 -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 5FE2022E259; Fri, 25 May 2012 18:30:49 -0400 (EDT)
Subject: Re: WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <20120515175324.14098.64192.idtracker@ietfa.amsl.com>
Date: Fri, 25 May 2012 16:30:47 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA14C988-FE03-4FBA-B452-FF2A00A74024@iii.ca>
References: <20120515175324.14098.64192.idtracker@ietfa.amsl.com>
To: The IESG <iesg@ietf.org>, IETF discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
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: Fri, 25 May 2012 22:30:57 -0000

WIll the IPFIX and MIB  work also be usable by v4 to v4 NATs?


On May 15, 2012, at 11:53 AM, IESG Secretary wrote:

> A modified charter has been submitted for the Behavior Engineering for =
Hindrance Avoidance (behave) working group in the Transport Area of the =
IETF.  The IESG has not made any determination as yet.  The modified =
charter is provided below for informational purposes only.  Please send =
your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, May =
22, 2012.
>=20
> Behavior Engineering for Hindrance Avoidance (behave)
> -----------------------------------------------------
> Current Status: Active
> Last updated: 2012-05-10
>=20
> Chairs:
>     Dan Wing <dwing@cisco.com>
>     Dave Thaler <dthaler@microsoft.com>
>=20
> Transport Area Directors:
>     Wesley Eddy <wes@mti-systems.com>
>     Martin Stiemerling <martin.stiemerling@neclab.eu>
>=20
> Transport Area Advisor:
>     Wesley Eddy <wes@mti-systems.com>
>=20
> Mailing Lists:
>     General Discussion: behave@ietf.org
>     To Subscribe:       https://www.ietf.org/mailman/listinfo/behave
>     Archive:            http://www.ietf.org/mail-archive/web/behave
>=20
> Description of Working Group
>=20
> The working group creates documents to enable IPv4/IPv4 and IPv6/IPv4
> NATs to function in as deterministic a fashion as possible.
>=20
> To support deployments where communicating hosts require using
> different address families (IPv4 or IPv6), address family translation =
is
> needed to establish communication. In BEHAVE's specification work on
> this topic it will coordinate with the V6ops WG on requirements and
> operational considerations.
>=20
> "An IPv4 network" or "an IPv6 network" in the descriptions below refer
> to a network with a clearly identifiable administrative domain (e.g., =
an
> enterprise campus network, a mobile operator's cellular network, a
> residential subscriber network, etc.). It will also be that network =
that
> deploys the necessary equipment for translation.
>=20
> BEHAVE will finish four scenarios: (1) An IPv6 network to IPv4
> Internet, (2) an IPv6 Internet to an IPv4 network, (3) an IPv6 network
> to an IPv4 network, and (4) an IPv4 network to an IPv6 network.
>=20
> Specifically, BEHAVE will update the NAT MIB (RFC 4008) to be
> consistent with the management aspects of its IPv6/IPv4 NAT solutions,
> and specify IPFIX information elements to meet logging requirements,
> reusing existing elements, if possible.=20
>=20
> In addition, when a NAT (such as a NAT64 in the "An IPv6 network to
> IPv4 Internet" scenario) serves multiple subscribers, inter-subscriber
> fairness issues arise.  As such, BEHAVE will complete its work on
> Carrier Grade NAT requirements for such scenarios, and update the NAT
> MIB as needed to meet such requirements.  BEHAVE will not, however,
> standardize IPv4-specific behavioral mechanisms.
>=20
> The following scenarios remain in scope for discussion, but will not =
be
> solved by BEHAVE:
>=20
> * An IPv4 network to IPv6 Internet, i.e. perform translation between
> IPv4 and IPv6 for packets in uni- or bi-directional flows that are
> initiated from an IPv4 host towards an IPv6 host. The translator
> function is intended to service a specific IPv4 network using either
> public or private IPv4 address space.
>=20
> * IPv4 Internet to an IPv6 network, i.e. perform translation between
> IPv4 and IPv6 for packets in uni- or bi-directional flows that are
> initiated from an IPv4 host towards an IPv6 host. The translator
> function is intended to service a specific IPv6 network where selected
> IPv6 hosts and services are to be reachable.
>=20
> This group will also provide reviews of any work by the MBoneD WG on
> multicast translation, including control traffic (IGMP and MLD),  =
Single
> Source Multicast (SSM) and Any Source Multicast (ASM).
>=20
> If the WG deems it necessary, BEHAVE will revise RFCs previously
> published by BEHAVE.
>=20
> Goals and Milestones
>=20
> Done	Submit BCP that defines unicast UDP behavioral requirements for=20=

>        NATs to IESG=20
> Done	Submit a BCP that defines TCP behavioral requirements for NATs=20=

>        to IESG=20
> Done	Submit a BCP that defines ICMP behavioral requirements for NATs=20=

>        to IESG=20
> Done	Submit informational that discusses current NAT traversal=20
>        techniques used by applications=20
> Done	Submit BCP that defines multicast UDP=20
> Done	Submit revision of RFC 3489 to IESG behavioral requirements for=20=

>        NATs to IESG=20
> Done	Submit informational document for rfc3489bis test vectors=20
> Done	Submit experimental document that describes how an application=20=

>        can determine the type of NAT it is behind=20
> Done	Submit BCP document for DCCP NAT behavior=20
> Done	Determine relative prioritization of the four translation cases.=20=

>        Documented in IETF74 minutes.=20
> Done	Determine what solutions(s) and components are needed to solve=20=

>        each of the four cases. Create new milestones for the=20
>        solution(s) and the components. Documented in IETF74 minutes.=20=

> Done	Submit to IESG: relaying of a TCP bytestream (std)=20
> Done	Submit to IESG: relay protocol (std)=20
> Done	Submit to IESG: TURN-URI document (std)=20
> Done	Submit to IESG: IPv6 relay protocol (std)=20
> Done	Submit to IESG: framework for IPv6/IPv4 translation (info)=20
> Done	Submit to IESG: stateless IPv6/IPv4 translation (std)=20
> Done	Submit to IESG: stateful IPv6/IPv4 translation (std)=20
> Done	Submit to IESG: DNS rewriting for IPv6/IPv4 translation (std)=20
> Done	Submit to IESG: IPv6 prefix for IPv6/IPv4 translator (std)=20
> Done	Determine need and scope of multicast 6/4 translation=20
> Done	Submit to IESG: FTP ALG for IPv6/IPv4 translation (std)=20
> Jul 2012  Submit to IESG: large scale NAT requirements (BCP)=20
> Done	Submit to IESG: Analysis of NAT-PT considerations with IPv6/IPv4=20=

>        translation (info)
> Jul 2012  Submit to IESG: avoiding NAT64 with dual-stack host for=20
>          local networks (std)=20
> Done    Submit to IESG: host-based NAT46 translation for IPv4-only=20
>        applications to access IPv6-only servers (std)=20
> Nov 2012  Submit to IESG: updates to NAT MIB for NAT64 (std)
> Nov 2012  Submit to IESG: updates to NAT MIB for CGNs (std)
> Nov 2012  Submit to IESG: IPFIX information elements (std)


From malcolm.betts@zte.com.cn  Fri May 25 19:01:25 2012
Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0650211E8089 for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 19:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.591
X-Spam-Level: 
X-Spam-Status: No, score=-101.591 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uLJeExe44tK for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 19:01:24 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0844611E807F for <ietf@ietf.org>; Fri, 25 May 2012 19:01:23 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 2862011182326; Sat, 26 May 2012 09:15:42 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 73517.11182326; Sat, 26 May 2012 10:01:02 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q4Q21GIH030270 for <ietf@ietf.org>; Sat, 26 May 2012 10:01:16 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
Subject: MalcolmBETTS90013533 is out of the office.
Auto-Submitted: auto-generated
From: Malcolm.BETTS@zte.com.cn
To: ietf@ietf.org
Message-ID: <OFE6181777.500E3E62-ON48257A0A.000B14EF-48257A0A.000B14EF@zte.com.cn>
Date: Sat, 26 May 2012 10:01:02 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-05-26 10:01:17
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-MAIL: mse02.zte.com.cn q4Q21GIH030270
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 02:01:25 -0000

I will be out of the office starting  25/05/2012 and will not return until
04/06/2012.

I will not have access to email, I will respond to your message when I
return.



From hartmans@mit.edu  Sat May 26 16:23:43 2012
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 D2C2921F84D9 for <ietf@ietfa.amsl.com>; Sat, 26 May 2012 16:23:43 -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 NJcB7q0S09Er for <ietf@ietfa.amsl.com>; Sat, 26 May 2012 16:23:43 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7200421F84BF for <ietf@ietf.org>; Sat, 26 May 2012 16:23:42 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id E058C20177; Sat, 26 May 2012 19:23:34 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id AE6964151; Sat, 26 May 2012 19:23:35 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net> <4FBEAFC8.40703@stpeter.im> <6.2.5.6.2.20120524154050.09714b10@resistor.net> <4FBED16C.3080008@stpeter.im>
Date: Sat, 26 May 2012 19:23:35 -0400
In-Reply-To: <4FBED16C.3080008@stpeter.im> (Peter Saint-Andre's message of "Thu, 24 May 2012 18:25:16 -0600")
Message-ID: <tsl1um6h6h4.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: SM <sm@resistor.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: Sat, 26 May 2012 23:23:43 -0000

I'd like to challenge the assumption that an explicit call for adoption
is required if work is mentioned in a charter.  Sometimes, if work is
mentioned as a possible starting point, that's true.  However for
working groups like the original XMPP, DKIM, ABFAB and BEEP, where work
was mentioned as a basis/as *the* starting point, the question of
whether to adopt the work happens as part of the chartering process.
I'm not sure that impacts how IPR is handled; in that case I'd expect
the IPR to be confirmed/discussed as part of the chartering process.

From housley@vigilsec.com  Sun May 27 09:22:25 2012
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 17D7F21F853C for <ietf@ietfa.amsl.com>; Sun, 27 May 2012 09:22:25 -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 axWnMnNLRI4k for <ietf@ietfa.amsl.com>; Sun, 27 May 2012 09:22:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB2A21F8469 for <ietf@ietf.org>; Sun, 27 May 2012 09:22:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D5C42F24025; Sun, 27 May 2012 12:22:20 -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 UNh-hjlNMVQZ; Sun, 27 May 2012 12:22:17 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-161.washdc.fios.verizon.net [96.255.37.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 31C62F24014; Sun, 27 May 2012 12:22:20 -0400 (EDT)
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <tsl1um6h6h4.fsf@mit.edu>
Date: Sun, 27 May 2012 12:22:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F86376BB-2E7A-46BE-8ABD-E5005C01F1B9@vigilsec.com>
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net> <4FBEAFC8.40703@stpeter.im> <6.2.5.6.2.20120524154050.09714b10@resistor.net> <4FBED16C.3080008@stpeter.im> <tsl1um6h6h4.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1084)
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: Sun, 27 May 2012 16:22:25 -0000

Sam:

I'm seeking clarity.  Are you suggesting that the pre-WG mail list ask =
this question while drafting the charter, or are you suggesting that the =
IESG include this question in the call for external review of the =
charter, or both?

Russ


On May 26, 2012, at 7:23 PM, Sam Hartman wrote:

> I'd like to challenge the assumption that an explicit call for =
adoption
> is required if work is mentioned in a charter.  Sometimes, if work is
> mentioned as a possible starting point, that's true.  However for
> working groups like the original XMPP, DKIM, ABFAB and BEEP, where =
work
> was mentioned as a basis/as *the* starting point, the question of
> whether to adopt the work happens as part of the chartering process.
> I'm not sure that impacts how IPR is handled; in that case I'd expect
> the IPR to be confirmed/discussed as part of the chartering process.


From hartmans@mit.edu  Sun May 27 11:51:27 2012
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 A66A021F849B for <ietf@ietfa.amsl.com>; Sun, 27 May 2012 11:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=-1.084, 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 Jsbasev1wSqg for <ietf@ietfa.amsl.com>; Sun, 27 May 2012 11:51:27 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 446CB21F846C for <ietf@ietf.org>; Sun, 27 May 2012 11:51:19 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 79720203BA; Sun, 27 May 2012 14:51:11 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 9C9784151; Sun, 27 May 2012 14:51:10 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-polk-ipr-disclosure-03.txt> (Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules) to Informational RFC
References: <CBC48C89.8671C%stewe@stewe.org> <4FBC113C.3050707@stpeter.im> <6.2.5.6.2.20120522233611.08d14c78@resistor.net> <4FBEAFC8.40703@stpeter.im> <6.2.5.6.2.20120524154050.09714b10@resistor.net> <4FBED16C.3080008@stpeter.im> <tsl1um6h6h4.fsf@mit.edu> <F86376BB-2E7A-46BE-8ABD-E5005C01F1B9@vigilsec.com>
Date: Sun, 27 May 2012 14:51:10 -0400
In-Reply-To: <F86376BB-2E7A-46BE-8ABD-E5005C01F1B9@vigilsec.com> (Russ Housley's message of "Sun, 27 May 2012 12:22:16 -0400")
Message-ID: <tslwr3xe9up.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Sam Hartman <hartmans-ietf@mit.edu>, 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 May 2012 18:51:27 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:

    Russ> Sam: I'm seeking clarity.  Are you suggesting that the pre-WG
    Russ> mail list ask this question while drafting the charter, or are
    Russ> you suggesting that the IESG include this question in the call
    Russ> for external review of the charter, or both?

I don't know; I haven't thought in that much detail.  I'm stating as
fact that there are cases where we adopt documents as part of chartering
work; I've been involved in that as a BOF proponent and as an AD.

I believe that it's important to consider the IPR implications then as
with any other adoption.  In the cases I've been aware of there has been
no IPR.  I suspect that if there were IPR that a WG would be much more
likely to consider something as a potential starting point ((not adopted
in the charter process) than as a basis (adopted in the charter
process.)

My personal opinion is that if we're diligent about making sure
disclosures are filed prior to the review of the charter, the rest will
take care of itself.  I don't mind if people want more process than
that, but I don't have strong opinions on what it should be.  I agree
with you that asking on the bof list or asking in external review would
be reasonable ways to approach that.

From simon.perreault@viagenie.ca  Mon May 28 06:35:20 2012
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 5548B21F8494; Mon, 28 May 2012 06:35: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 bFybxoFbHtnp; Mon, 28 May 2012 06:35:19 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id CD5CB21F8493; Mon, 28 May 2012 06:35:19 -0700 (PDT)
Received: from [192.168.0.100] (modemcable010.192-131-66.mc.videotron.ca [66.131.192.10]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 6E81440031; Mon, 28 May 2012 09:35:18 -0400 (EDT)
Message-ID: <4FC37F16.6070904@viagenie.ca>
Date: Mon, 28 May 2012 09:35:18 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Cullen Jennings <fluffy@iii.ca>
Subject: Re: [BEHAVE] WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave)
References: <20120515175324.14098.64192.idtracker@ietfa.amsl.com> <BA14C988-FE03-4FBA-B452-FF2A00A74024@iii.ca>
In-Reply-To: <BA14C988-FE03-4FBA-B452-FF2A00A74024@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: behave@ietf.org, The IESG <iesg@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: Mon, 28 May 2012 13:35:20 -0000

On 2012-05-25 18:30, Cullen Jennings wrote:
> WIll the IPFIX and MIB  work also be usable by v4 to v4 NATs?

Speaking as an author of draft-ietf-behave-nat-mib, our intent is to 
support all kinds of NAT, but it isn't clear yet whether it will be done 
in multiple drafts or a single one. There is stuff that is common to all 
NAT no matter the IP version, and there stuff that is IP version specific.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From bortzmeyer@nic.fr  Mon May 28 08:38:12 2012
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 1AABE21F8613 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 08:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.111
X-Spam-Level: 
X-Spam-Status: No, score=-101.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 vQtzpTDz-zxf for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 08:38:11 -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 3140B21F854B for <ietf@ietf.org>; Mon, 28 May 2012 08:38:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 422FB3B3BB; Mon, 28 May 2012 15:38:08 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 807ED190976; Mon, 28 May 2012 17:34:33 +0200 (CEST)
Date: Mon, 28 May 2012 17:34:33 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Long discussion about IETF on the Internet Governance Caucus mailing list
Message-ID: <20120528153433.GA3026@sources.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 May 2012 15:38:12 -0000

I believe it is relevant here since IETF is currently being discussed
in depth on the Internet Governance Caucus mailing list (one of the
biggest forums of the "civil society" about Internet governance).

The thread is long and, for those who are not subscribed, can be found
here on the Web:

http://lists.igcaucus.org/arc/governance/2012-05/msg00380.html

There are two things being discussed about the IETF:

1) Does it do a good job of creating and promoting technical
standards?

2) If yes, can it be used as a "model" for Internet governance of
other, more political, functions?


From tbray@textuality.com  Mon May 28 08:51:48 2012
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 1A3D621F8628 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 08:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvqqRlquMMup for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 08:51:47 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5680021F8625 for <ietf@ietf.org>; Mon, 28 May 2012 08:51:47 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so6871175obb.31 for <ietf@ietf.org>; Mon, 28 May 2012 08:51:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=2dKVdbX01SMYeL5WiLH4swXGfKBdeXzz+snw2A3tYFA=; b=JWRvL39dVHmTYzMOrAhMBsCw9TPbJbD74YcEdkZP0fCu+24RBoM4gCi5gGrcI7pP8z UA+IP6Yu+WbuVJ/op7T5x62w27JbDc3s3wDFHf9vmruzJD2q51NcxDBLxOFbv8F2UNEo 5piYEaMZ0bETec1x27FZkWJwJ0vHyV/9An6VwU0JMlJ67dNnDJz04t17Dov5t+V8tEy+ ydfNbewtxiUvC412wsIrQ2WsEgHhMbAA/kRBNopXR212ewCrc9s+6lVOItMJ5JqFEGei RqkL7mpqgjqHm/jyppg8W8MpZ0M0maplr4giDsTEsQkiJn2l4vKH9E3h0kQ6UliG0luQ Ae9Q==
MIME-Version: 1.0
Received: by 10.182.115.74 with SMTP id jm10mr8360212obb.71.1338220306866; Mon, 28 May 2012 08:51:46 -0700 (PDT)
Received: by 10.182.220.97 with HTTP; Mon, 28 May 2012 08:51:46 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <20120528153433.GA3026@sources.org>
References: <20120528153433.GA3026@sources.org>
Date: Mon, 28 May 2012 08:51:46 -0700
Message-ID: <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
From: Tim Bray <tbray@textuality.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkG0sjZxl5VlpgLxntRhjS61Hlyjoz/Ipv40qiCiyUjkjO09gDmhIT/jCQZ75OYt2khMZ5I
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, 28 May 2012 15:51:48 -0000

Who are these people? -T

On Mon, May 28, 2012 at 8:34 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> I believe it is relevant here since IETF is currently being discussed
> in depth on the Internet Governance Caucus mailing list (one of the
> biggest forums of the "civil society" about Internet governance).
>
> The thread is long and, for those who are not subscribed, can be found
> here on the Web:
>
> http://lists.igcaucus.org/arc/governance/2012-05/msg00380.html
>
> There are two things being discussed about the IETF:
>
> 1) Does it do a good job of creating and promoting technical
> standards?
>
> 2) If yes, can it be used as a "model" for Internet governance of
> other, more political, functions?
>

From bortzmeyer@nic.fr  Mon May 28 09:18:11 2012
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 BC0BC21F860F for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.856
X-Spam-Level: 
X-Spam-Status: No, score=-101.856 tagged_above=-999 required=5 tests=[AWL=0.745, 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 Ap9lWKpxZZqS for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:18:11 -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 E3D9021F84A0 for <ietf@ietf.org>; Mon, 28 May 2012 09:18:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id E11063B3BE; Mon, 28 May 2012 16:18:09 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 7938B190976; Mon, 28 May 2012 18:15:45 +0200 (CEST)
Date: Mon, 28 May 2012 18:15:45 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tim Bray <tbray@textuality.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
Message-ID: <20120528161545.GA7789@sources.org>
References: <20120528153433.GA3026@sources.org> <25604_1338221401_4FC3A357_25604_1127_1_CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25604_1338221401_4FC3A357_25604_1127_1_CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 28 May 2012 16:18:11 -0000

On Mon, May 28, 2012 at 08:51:46AM -0700,
 Tim Bray <tbray@textuality.com> wrote 
 a message of 20 lines which said:

> Who are these people? -T

They may ask the same thing about you :-)

From johnl@iecc.com  Mon May 28 09:19:52 2012
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 B122121F8454 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9y7lIYixDbR for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:19:52 -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 7D3F721F8433 for <ietf@ietf.org>; Mon, 28 May 2012 09:19:51 -0700 (PDT)
Received: (qmail 48386 invoked from network); 28 May 2012 16:19:50 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 May 2012 16:19:50 -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:vbr-info; s=4fc3a5a6.xn--hew.k1205; i=johnl@user.iecc.com; bh=VNwm78xaMjD1CQ0CFr+ipsqEZpNG/pAdBldkr/GQkCI=; b=Pay2JXt841QPHS7Qjj7H8yD5TWhwJXCvWLwuLrCjPeprfzjqMA9NHw0P4RV6T6u/p/UQiXBSgsfW6Ufll48gobEgYlI+fXRPgN6SIvTxyf3PkCYFb4ZjMOmd0ZCXp1deKKrFOoEg+ipIeEfICu3/PyP59S+TulL4X5YFHdu/5/g=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 28 May 2012 16:19:28 -0000
Message-ID: <20120528161928.23662.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
In-Reply-To: <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: tbray@textuality.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, 28 May 2012 16:19:52 -0000

In article <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> you write:
>Who are these people? -T

Based on what I've seem on the IGF list, people with an extraordinary
amount of free time.

R's,
John

From brian.e.carpenter@gmail.com  Mon May 28 09:20:18 2012
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 D0C0B21F85CC for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.677
X-Spam-Level: 
X-Spam-Status: No, score=-101.677 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 ramFnns3JHLN for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:20:18 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id B76B421F85BE for <ietf@ietf.org>; Mon, 28 May 2012 09:20:17 -0700 (PDT)
Received: by eekd4 with SMTP id d4so857856eek.31 for <ietf@ietf.org>; Mon, 28 May 2012 09:20:16 -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=LwFwrKN/cEUUqvnzzZO8QnX7P8BTtpaO2167N5I0ad4=; b=jrjZAWE9gOs/jwGgWimKOKNcukox6SzCjAgKBs68MppI/xw1NDcTbIjIoEuFe72ee9 Ku3ckGtbbTwWpMsusbyt06++g9Bq74e5YsJbmKEp69U1qmzp+cx2XPMxuJeXhDew6ERN JbkfK2Udp6bdt3I7rAlXM5uuaTQIq41v9elP+vIp7UiQdEqObNtUZItM5A2efFQ8XKpp AlnOiusKvNH+bir9MH/gn1Ms/1AaMYeau7xdZLAgALeUcKW4YbbwxJN1ejIcg5AoKUpK TEpMWu4mCINnGmFm5R58w3tCV1t8ZTMB2Q4xi0acqSLVTZh7BaOtM+Tfnn/oCkRKB3gu /vwA==
Received: by 10.14.48.73 with SMTP id u49mr2474914eeb.10.1338222016697; Mon, 28 May 2012 09:20:16 -0700 (PDT)
Received: from [192.168.1.67] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id o16sm38898365eeb.13.2012.05.28.09.20.15 (version=SSLv3 cipher=OTHER); Mon, 28 May 2012 09:20:16 -0700 (PDT)
Message-ID: <4FC3A5BA.9020202@gmail.com>
Date: Mon, 28 May 2012 17:20:10 +0100
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: Tim Bray <tbray@textuality.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
References: <20120528153433.GA3026@sources.org> <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
In-Reply-To: <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2012 16:20:18 -0000

On 2012-05-28 16:51, Tim Bray wrote:
> Who are these people? -T

<politicallyIncorrect>
So far, fortunately, the Internet Governance Forum and its associated
talking shops add up to a no-op. The danger is always there that they
will persuade government reps in the ITU or other UN bodies to take
action that will damage the Internet.
</politicallyIncorrect>

   Brian

> 
> On Mon, May 28, 2012 at 8:34 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>> I believe it is relevant here since IETF is currently being discussed
>> in depth on the Internet Governance Caucus mailing list (one of the
>> biggest forums of the "civil society" about Internet governance).
>>
>> The thread is long and, for those who are not subscribed, can be found
>> here on the Web:
>>
>> http://lists.igcaucus.org/arc/governance/2012-05/msg00380.html
>>
>> There are two things being discussed about the IETF:
>>
>> 1) Does it do a good job of creating and promoting technical
>> standards?
>>
>> 2) If yes, can it be used as a "model" for Internet governance of
>> other, more political, functions?
>>
> 

From bortzmeyer@nic.fr  Mon May 28 09:38:11 2012
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 CD20C21F862A for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.104
X-Spam-Level: 
X-Spam-Status: No, score=-102.104 tagged_above=-999 required=5 tests=[AWL=0.496, 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 bvpnkz6of0An for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:38:11 -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 553C621F8629 for <ietf@ietf.org>; Mon, 28 May 2012 09:38:11 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 99A693B3BE; Mon, 28 May 2012 16:38:10 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id CA1A5190976; Mon, 28 May 2012 18:34:09 +0200 (CEST)
Date: Mon, 28 May 2012 18:34:09 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: John Levine <johnl@iecc.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
Message-ID: <20120528163409.GA10172@sources.org>
References: <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> <25604_1338222652_4FC3A83C_25604_1209_1_20120528161928.23662.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25604_1338222652_4FC3A83C_25604_1209_1_20120528161928.23662.qmail@joyce.lan>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: tbray@textuality.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, 28 May 2012 16:38:11 -0000

On Mon, May 28, 2012 at 04:19:28PM -0000,
 John Levine <johnl@iecc.com> wrote 
 a message of 8 lines which said:

> Based on what I've seem on the IGF list, people with an
> extraordinary amount of free time.

In some cases ("RFC 2119 terms, ALL CAPS vs lower case"), IETFers have
some free time, too...

From bortzmeyer@nic.fr  Mon May 28 09:43:10 2012
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 8035D21F866B for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.228
X-Spam-Level: 
X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=0.372, 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 MkAwnNZothVQ for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:43:09 -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 AF7CF21F866A for <ietf@ietf.org>; Mon, 28 May 2012 09:43:09 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 063703B3BC; Mon, 28 May 2012 16:43:08 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 6D4A0190976; Mon, 28 May 2012 18:38:47 +0200 (CEST)
Date: Mon, 28 May 2012 18:38:47 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
Message-ID: <20120528163847.GB10172@sources.org>
References: <20120528153433.GA3026@sources.org> <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> <25604_1338222641_4FC3A831_25604_1208_1_4FC3A5BA.9020202@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <25604_1338222641_4FC3A831_25604_1208_1_4FC3A5BA.9020202@gmail.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 28 May 2012 16:43:10 -0000

On Mon, May 28, 2012 at 05:20:10PM +0100,
 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote 
 a message of 32 lines which said:

> So far, fortunately, the Internet Governance Forum 

Hold on, the Internet Governance Caucus I was talking about (a civil
society loosely connected group) is not the Internet Governance Forum
(an intergovernmental body). 

> The danger is always there that they will persuade government reps
> in the ITU or other UN bodies to take action that will damage the
> Internet.

The main danger to the Internet comes from existing governments (and
not only the repressive regimes), not from the UN or the ITU or an
hypothetical UN-inspired organization
<http://www.internetgovernance.org/2012/05/24/threat-analysis-of-itus-wcit-part-1-historical-context/>.

From gtw@gtwassociates.com  Mon May 28 09:44:27 2012
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 D330621F8679 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTjbyWXwxaId for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:44:26 -0700 (PDT)
Received: from mail1.primary.net (mail1.primary.net [216.87.38.221]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCBA21F866B for <ietf@ietf.org>; Mon, 28 May 2012 09:44:25 -0700 (PDT)
Received: from pool-108-28-107-35.washdc.fios.verizon.net ([108.28.107.35]:1963 helo=gtwassociates) by mail1.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1SZ33O-0003mt-1g for ietf@ietf.org; Mon, 28 May 2012 11:44:24 -0500
Message-ID: <167D4FF3D1E049B89350EAA79CC6C367@gtwassociates>
From: "George Willingmyre" <gtw@gtwassociates.com>
To: <ietf@ietf.org>
References: <20120528161928.23662.qmail@joyce.lan>
Subject: Re: Long discussion about IETF on the Internet Governance Caucusmailing list
Date: Mon, 28 May 2012 12:44:15 -0400
Organization: GTW Associates
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B0_01CD3CCF.96F33330"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: George Willingmyre <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: Mon, 28 May 2012 16:44:28 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01B0_01CD3CCF.96F33330
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Congressional Hearing  this week =
http://thehill.com/blogs/hillicon-valley/technology/229653-house-to-exami=
ne-plan-to-let-un-regulate-internet  about ITU meeting in Dubai in =
December

clip
House to examine plan for United Nations to regulate the Internet
House lawmakers will consider an international proposal next week to =
give the United Nations more control over the Internet.

The proposal is backed by China, Russia, Brazil, India and other UN =
members, and would give the UN=E2=80=99s International Telecommunication =
Union (ITU) more control over the governance of the Internet.


It=E2=80=99s an unpopular idea with lawmakers on both sides of the aisle =
in Congress, and officials with the Obama administration have also =
criticized it.=20

=E2=80=9CWe're quite concerned,=E2=80=9D Larry Strickling, the head of =
the Commerce Department's National Telecommunications and Information =
Administration, said in an interview with The Hill earlier this year.

He said the measure would expose the Internet to =E2=80=9Ctop-down =
regulation where it's really the governments that are at the table, but =
the rest of the stakeholders aren't.=E2=80=9D

At a hearing earlier this month, Sen. Marco Rubio (R-Fla.) also =
criticized the proposal. He said China and Russia are "not exactly =
bastions of Internet freedom."

"Any place that bans certain terms from search should not be a leader in =
international Internet regulatory frameworks," he said, adding that he =
will keep a close eye on the process.

Yet the proposal could come up for a vote at a UN conference in Dubai in =
December.



end clip

George T. Willingmyre, P.E.
President, GTW Associates
Spencerville, MD USA 20868
301.421.4138
www.gtwassociates.com
----- Original Message -----=20
From: "John Levine" <johnl@iecc.com>
To: <ietf@ietf.org>
Cc: <tbray@textuality.com>
Sent: Monday, May 28, 2012 12:19 PM
Subject: Re: Long discussion about IETF on the Internet Governance =
Caucusmailing list


> In article =
<CAHBU6iui0_n_=3D3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> =
you write:
>>Who are these people? -T
>=20
> Based on what I've seem on the IGF list, people with an extraordinary
> amount of free time.
>=20
> R's,
> John
>
------=_NextPart_000_01B0_01CD3CCF.96F33330
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19222">
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT size=3D2 face=3DArial>Congressional Hearing&nbsp; this week =
</FONT><A=20
href=3D"http://thehill.com/blogs/hillicon-valley/technology/229653-house-=
to-examine-plan-to-let-un-regulate-internet"><FONT=20
size=3D2=20
face=3DArial>http://thehill.com/blogs/hillicon-valley/technology/229653-h=
ouse-to-examine-plan-to-let-un-regulate-internet</FONT></A><FONT=20
size=3D2 face=3DArial>&nbsp; about ITU meeting in Dubai in =
December</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>clip</FONT></DIV>
<DIV>
<DIV class=3Dtitle>
<H1 class=3Dtitle><FONT size=3D2 face=3DArial>House to examine plan for =
United Nations=20
to regulate the Internet</FONT></H1></DIV></DIV>
<DIV>
<P><FONT size=3D2 face=3DArial>House lawmakers will consider an =
international=20
proposal next week to give the United Nations more control over the=20
Internet.</FONT></P>
<P><FONT size=3D2 face=3DArial>The proposal is backed by China, Russia, =
Brazil,=20
India and other UN members, and would give the UN=E2=80=99s =
International=20
Telecommunication Union (ITU) more control over the governance of the=20
Internet.</FONT></P></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>It=E2=80=99s an unpopular idea with =
lawmakers on both sides=20
of the aisle in Congress, and officials with the Obama administration =
have also=20
criticized it. </FONT></DIV>
<P><FONT size=3D2 face=3DArial></FONT></P>
<P><FONT size=3D2 face=3DArial>=E2=80=9CWe're quite concerned,=E2=80=9D =
Larry Strickling, the head=20
of the Commerce Department's National Telecommunications and Information =

Administration, said in an interview with The Hill earlier this =
year.</FONT></P>
<P><FONT size=3D2 face=3DArial>He said the measure would expose the =
Internet to=20
=E2=80=9Ctop-down regulation where it's really the governments that are =
at the table,=20
but the rest of the stakeholders aren't.=E2=80=9D</FONT></P>
<P><FONT size=3D2 face=3DArial>At a hearing earlier this month, Sen. =
Marco Rubio=20
(R-Fla.) also criticized the proposal. He said China and Russia are "not =
exactly=20
bastions of Internet freedom."</FONT></P>
<P><FONT size=3D2 face=3DArial>"Any place that bans certain terms from =
search should=20
not be a leader in international Internet regulatory frameworks," he =
said,=20
adding that he will keep a close eye on the process.</FONT></P>
<P><FONT size=3D2 face=3DArial>Yet the proposal could come up for a vote =
at a UN=20
conference in Dubai in December.</FONT></P>
<P><FONT size=3D2 face=3DArial></FONT>&nbsp;</P>
<P><FONT size=3D2 face=3DArial>end clip</FONT></P>
<DIV><FONT size=3D2 face=3DArial>George T. Willingmyre, =
P.E.<BR>President, GTW=20
Associates<BR>Spencerville, MD USA 20868<BR>301.421.4138<BR></FONT><A=20
href=3D"http://www.gtwassociates.com"><FONT size=3D2=20
face=3DArial>www.gtwassociates.com</FONT></A></DIV>
<DIV><FONT size=3D2 face=3DArial>----- Original Message ----- </FONT>
<DIV><FONT size=3D2 face=3DArial>From: "John Levine" &lt;</FONT><A=20
href=3D"mailto:johnl@iecc.com"><FONT size=3D2=20
face=3DArial>johnl@iecc.com</FONT></A><FONT size=3D2 =
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>To: &lt;</FONT><A =
href=3D"mailto:ietf@ietf.org"><FONT=20
size=3D2 face=3DArial>ietf@ietf.org</FONT></A><FONT size=3D2=20
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Cc: &lt;</FONT><A=20
href=3D"mailto:tbray@textuality.com"><FONT size=3D2=20
face=3DArial>tbray@textuality.com</FONT></A><FONT size=3D2=20
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Sent: Monday, May 28, 2012 12:19 =
PM</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Subject: Re: Long discussion about IETF =
on the=20
Internet Governance Caucusmailing list</FONT></DIV></DIV>
<DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT =
size=3D2=20
face=3DArial>&gt; In article &lt;</FONT><A=20
href=3D"mailto:CAHBU6iui0_n_=3D3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail=
.gmail.com"><FONT=20
size=3D2=20
face=3DArial>CAHBU6iui0_n_=3D3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.g=
mail.com</FONT></A><FONT=20
size=3D2 face=3DArial>&gt; you write:<BR>&gt;&gt;Who are these people? =
-T<BR>&gt;=20
<BR>&gt; Based on what I've seem on the IGF list, people with an=20
extraordinary<BR>&gt; amount of free time.<BR>&gt; <BR>&gt; R's,<BR>&gt; =

John<BR>&gt;</FONT></BODY></HTML>

------=_NextPart_000_01B0_01CD3CCF.96F33330--


From brian.e.carpenter@gmail.com  Mon May 28 09:52:10 2012
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 C743321F85CC for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.678
X-Spam-Level: 
X-Spam-Status: No, score=-101.678 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 xaqIJ2MGFGzH for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 09:52:10 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE8BA21F859E for <ietf@ietf.org>; Mon, 28 May 2012 09:52:09 -0700 (PDT)
Received: by eekd4 with SMTP id d4so867850eek.31 for <ietf@ietf.org>; Mon, 28 May 2012 09:52:09 -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=nl3K62UCkkD/H7FwXAZPlqGJJdbZgmu9yffU+qtXIIE=; b=bnwJaGNoMynQnkHeTqWzjZEQjYQK5GbBd2avJkx9ScxzcqcTosvLf4APUSx0UK5yQA Pn5U5Z4+1kl6e587FZeiV1i3mML9/Oj+LaeBL43L9Sj+n8ekDU38uWVfEtVVfoqtwIs5 bQNRvebDh7rEgVJAw0GzHKNMF9RtquWFIwVkxFUKkv3kMeCWLfelCz8NRoOxUD+4R76o vle0JN/isR80vVSU7B42HMr5xiQb/U67pp2RB7MJS3qeWx3NRtExz+f8oz//j02HOIJO cd+QQwCiy/9dA2RyF2URmPmgyijSiKRb5WosZY5+LZkp+NHbp07P+NFedlOo81+A1yB3 At8w==
Received: by 10.14.188.130 with SMTP id a2mr2368970een.86.1338223928946; Mon, 28 May 2012 09:52:08 -0700 (PDT)
Received: from [192.168.1.67] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id e45sm11447267eeb.6.2012.05.28.09.52.07 (version=SSLv3 cipher=OTHER); Mon, 28 May 2012 09:52:08 -0700 (PDT)
Message-ID: <4FC3AD32.4030108@gmail.com>
Date: Mon, 28 May 2012 17:52:02 +0100
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: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
References: <20120528153433.GA3026@sources.org> <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> <25604_1338222641_4FC3A831_25604_1208_1_4FC3A5BA.9020202@gmail.com> <20120528163847.GB10172@sources.org>
In-Reply-To: <20120528163847.GB10172@sources.org>
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: Mon, 28 May 2012 16:52:10 -0000

On 2012-05-28 17:38, Stephane Bortzmeyer wrote:
> On Mon, May 28, 2012 at 05:20:10PM +0100,
>  Brian E Carpenter <brian.e.carpenter@gmail.com> wrote 
>  a message of 32 lines which said:
> 
>> So far, fortunately, the Internet Governance Forum 
> 
> Hold on, the Internet Governance Caucus I was talking about (a civil
> society loosely connected group) is not the Internet Governance Forum
> (an intergovernmental body). 

I fully realise that, but when you look at the names of those active
in the "caucus", it's clear that it exists to lobby the IGF.

As I understand it the IGF is a multi-stakeholder body, which is not
the same thing as an intergovernmental body, fortunately.

    Brian
> 
>> The danger is always there that they will persuade government reps
>> in the ITU or other UN bodies to take action that will damage the
>> Internet.
> 
> The main danger to the Internet comes from existing governments (and
> not only the repressive regimes), not from the UN or the ITU or an
> hypothetical UN-inspired organization
> <http://www.internetgovernance.org/2012/05/24/threat-analysis-of-itus-wcit-part-1-historical-context/>.
> .
> 

From john-ietf@jck.com  Mon May 28 10:03:13 2012
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 72DA721F8672 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 10:03: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 HlFy0gRjpvJP for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 10:03:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C1E5C21F8671 for <ietf@ietf.org>; Mon, 28 May 2012 10:03:12 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SZ3Fp-000AJ3-HT; Mon, 28 May 2012 12:57:13 -0400
X-Vipre-Scanned: 046D7CCA002C31046D7E17-TDI
Date: Mon, 28 May 2012 13:03:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus	mailing list
Message-ID: <E73DCCB36CF919BD8A61D8FD@[192.168.1.128]>
In-Reply-To: <20120528163847.GB10172@sources.org>
References: <20120528153433.GA3026@sources.org> <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> <25604_1338222641_4FC3A831_25604_1208_1_4FC3A5BA.9020202@gmail.com> <20120528163847.GB10172@sources.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: Mon, 28 May 2012 17:03:13 -0000

--On Monday, May 28, 2012 18:38 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

>> So far, fortunately, the Internet Governance Forum 
> 
> Hold on, the Internet Governance Caucus I was talking about (a
> civil society loosely connected group) is not the Internet
> Governance Forum (an intergovernmental body). 

But that makes Tim's original question about who these people
are far more relevant.   You've answered part of that question
above, but it may be relevant to note that many of the
participants are self-selected (perhaps no worse than the IETF),
self-defined, "experts" on Internet technology and the
"governance" models that might rationally be used with it.  A
subset of the group is rather self-interested in that they
believe that the Internet is best trusted to themselves rather
than to other groups or bodies.  A different way to put that is
that they are no more interested in a true collaborative and
balanced multistakeholder model than the worst of the
"governments, preferably my government, should be in charge"
folks -- they just have a different opinion about which
particular group of stakeholders should be in control of things.
Another subset consists of academics and "governance"
theoreticians who are interested in using the Internet as a
field for their particular sociopolitical experiments.  Since
most of that group doesn't believe their ideas could possibly
fail, they don't have to worry about the consequences of such
failures, whether there is an escape or backout path, etc.

And that is probably even more politically incorrect than
Brian's comment.

    john




From bortzmeyer@nic.fr  Tue May 29 01:49:33 2012
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 521FC21F8741 for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 01:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level: 
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=0.122, 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 O6PHUDejS3mk for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 01:49:30 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 463A421F8775 for <ietf@ietf.org>; Tue, 29 May 2012 01:49:30 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id DA7E4280529 for <ietf@ietf.org>; Tue, 29 May 2012 10:49:05 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 2EBA6280591; Tue, 29 May 2012 10:49:04 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [IPv6:2001:67c:2218:9::4:162]) by mx4.nic.fr (Postfix) with ESMTP id 28815280529 for <ietf@ietf.org>; Tue, 29 May 2012 10:49:04 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay1.nic.fr (Postfix) with ESMTP id 217654C002C for <ietf@ietf.org>; Tue, 29 May 2012 10:49:04 +0200 (CEST)
Date: Tue, 29 May 2012 10:49:04 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: AFNIC's Technology Backdrop Survey (2nd edition): your input highly appreciated
Message-ID: <20120529084903.GA11883@nic.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM"
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-2-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Bogosity: No, tests=bogofilter, spamicity=0.000017, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2012.5.29.84219
X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, __ANY_URI 0, __CD 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __PHISH_SUBJ_PHRASE5 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_MAILTO 0, __URI_NS , __USER_AGENT 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, 29 May 2012 08:49:33 -0000

--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[It is not *directly* related to IETF work but I assume that the goal
is shared by many people here: try to find about the future of the
Internet. Do note that most questions about what you *wish* will
happen but about what you *think* will happen.]

To that end, with the help of its Scientific Council and INIT company,
AFNIC is carrying out the 2nd edition[1] of its "Technology Backdrop"
survey among Internet users and professionals, in the medium-to-long
term.

We kindly invite you to participate to this survey which is open
until 4 June 2012, at the following URL. It is a bit long but, we
believe, worth it:

http://www.init-web.com/cgi-cluster/Cluster/SF?P=3D7z254z6z-1z-1zF44165B408

Some complements on methodology and objectives:
-----------------------------------------------

Based on forecasts made by respondents to the survey, the backdrop
consists of two types of assertions concerning trends. First, the
basis of the backdrop consists of items on which there is
consensus. Then, forecasts on which sub-populations of respondents
disagree are used to integrate alternative scenarios into the
backdrop.

We believe that the backdrop resulting from this survey may be also of
interest to you.

Three themes have been chosen in this survey for two profiles, "User"
and "Professional":

1. "The Purpose Of The Internet", for both profiles
2. "Global Architecture Of The Internet", for the "Professional" profile on=
ly
3. "The Internet Domain Name System (DNS)", for the "Professional" profile =
only

Thank you in advance for your your time and input and please feel free
to forward this e-mail to people you would like to invite to provide
their input as well.

[1] The results of the 1st edition of this survey is available here:
http://www.slideshare.net/AFNIC/findings-techbackdropafnic-6789205=20



--cWoXeonUoKmBZSoM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iD8DBQFPxI1/QTZHl5fW0kYRAgywAJ0dtzLJLRNRP4TrlRfeJ/AMBtu8VACguiDb
6L8SabC4sg4j207Gm1C+fWY=
=MLYF
-----END PGP SIGNATURE-----

--cWoXeonUoKmBZSoM--

From ietfdbh@comcast.net  Fri May 25 22:00:38 2012
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 ED95E21F858D for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 22:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.253
X-Spam-Level: 
X-Spam-Status: No, score=-101.253 tagged_above=-999 required=5 tests=[AWL=0.746, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+BWZP3Wwmg1 for <ietf@ietfa.amsl.com>; Fri, 25 May 2012 22:00:36 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 2669D21F8594 for <ietf@ietf.org>; Fri, 25 May 2012 22:00:35 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by QMTA11.westchester.pa.mail.comcast.net with comcast id EUzs1j0021ap0As5BV0aM0; Sat, 26 May 2012 05:00:34 +0000
Received: from [192.168.1.34] ([71.233.85.150]) by omta22.westchester.pa.mail.comcast.net with comcast id EV0W1j00k3Ecudz3iV0XpH; Sat, 26 May 2012 05:00:34 +0000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Sat, 26 May 2012 01:00:29 -0400
Subject: Re: [BEHAVE] WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave)
From: David Harrington <ietfdbh@comcast.net>
To: Cullen Jennings <fluffy@iii.ca>, The IESG <iesg@ietf.org>, IETF discussion <ietf@ietf.org>
Message-ID: <CBE5DABE.2286E%ietfdbh@comcast.net>
Thread-Topic: [BEHAVE] WG Review: Recharter of Behavior Engineering for Hindrance Avoidance (behave)
In-Reply-To: <BA14C988-FE03-4FBA-B452-FF2A00A74024@iii.ca>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Tue, 29 May 2012 07:17:27 -0700
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: Sat, 26 May 2012 05:00:38 -0000

Hi Cullen,

I would assume the MIB module would be written in a way to be IP version
agnostic.
But I'm not sure the NAT technologies are version agnostic.
And I'm not sure that the current NAT-MIB can support the version-agnostic
addressing textual conventions (I haven't looked yet).

I have similar expectations regarding ipfix IEs.

--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 5/25/12 6:30 PM, "Cullen Jennings" <fluffy@iii.ca> wrote:

>
>WIll the IPFIX and MIB  work also be usable by v4 to v4 NATs?
>
>
>On May 15, 2012, at 11:53 AM, IESG Secretary wrote:
>
>> A modified charter has been submitted for the Behavior Engineering for
>>Hindrance Avoidance (behave) working group in the Transport Area of the
>>IETF.  The IESG has not made any determination as yet.  The modified
>>charter is provided below for informational purposes only.  Please send
>>your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, May
>>22, 2012.
>> 
>> Behavior Engineering for Hindrance Avoidance (behave)
>> -----------------------------------------------------
>> Current Status: Active
>> Last updated: 2012-05-10
>> 
>> Chairs:
>>     Dan Wing <dwing@cisco.com>
>>     Dave Thaler <dthaler@microsoft.com>
>> 
>> Transport Area Directors:
>>     Wesley Eddy <wes@mti-systems.com>
>>     Martin Stiemerling <martin.stiemerling@neclab.eu>
>> 
>> Transport Area Advisor:
>>     Wesley Eddy <wes@mti-systems.com>
>> 
>> Mailing Lists:
>>     General Discussion: behave@ietf.org
>>     To Subscribe:       https://www.ietf.org/mailman/listinfo/behave
>>     Archive:            http://www.ietf.org/mail-archive/web/behave
>> 
>> Description of Working Group
>> 
>> The working group creates documents to enable IPv4/IPv4 and IPv6/IPv4
>> NATs to function in as deterministic a fashion as possible.
>> 
>> To support deployments where communicating hosts require using
>> different address families (IPv4 or IPv6), address family translation is
>> needed to establish communication. In BEHAVE's specification work on
>> this topic it will coordinate with the V6ops WG on requirements and
>> operational considerations.
>> 
>> "An IPv4 network" or "an IPv6 network" in the descriptions below refer
>> to a network with a clearly identifiable administrative domain (e.g., an
>> enterprise campus network, a mobile operator's cellular network, a
>> residential subscriber network, etc.). It will also be that network that
>> deploys the necessary equipment for translation.
>> 
>> BEHAVE will finish four scenarios: (1) An IPv6 network to IPv4
>> Internet, (2) an IPv6 Internet to an IPv4 network, (3) an IPv6 network
>> to an IPv4 network, and (4) an IPv4 network to an IPv6 network.
>> 
>> Specifically, BEHAVE will update the NAT MIB (RFC 4008) to be
>> consistent with the management aspects of its IPv6/IPv4 NAT solutions,
>> and specify IPFIX information elements to meet logging requirements,
>> reusing existing elements, if possible.
>> 
>> In addition, when a NAT (such as a NAT64 in the "An IPv6 network to
>> IPv4 Internet" scenario) serves multiple subscribers, inter-subscriber
>> fairness issues arise.  As such, BEHAVE will complete its work on
>> Carrier Grade NAT requirements for such scenarios, and update the NAT
>> MIB as needed to meet such requirements.  BEHAVE will not, however,
>> standardize IPv4-specific behavioral mechanisms.
>> 
>> The following scenarios remain in scope for discussion, but will not be
>> solved by BEHAVE:
>> 
>> * An IPv4 network to IPv6 Internet, i.e. perform translation between
>> IPv4 and IPv6 for packets in uni- or bi-directional flows that are
>> initiated from an IPv4 host towards an IPv6 host. The translator
>> function is intended to service a specific IPv4 network using either
>> public or private IPv4 address space.
>> 
>> * IPv4 Internet to an IPv6 network, i.e. perform translation between
>> IPv4 and IPv6 for packets in uni- or bi-directional flows that are
>> initiated from an IPv4 host towards an IPv6 host. The translator
>> function is intended to service a specific IPv6 network where selected
>> IPv6 hosts and services are to be reachable.
>> 
>> This group will also provide reviews of any work by the MBoneD WG on
>> multicast translation, including control traffic (IGMP and MLD),  Single
>> Source Multicast (SSM) and Any Source Multicast (ASM).
>> 
>> If the WG deems it necessary, BEHAVE will revise RFCs previously
>> published by BEHAVE.
>> 
>> Goals and Milestones
>> 
>> Done	Submit BCP that defines unicast UDP behavioral requirements for
>>        NATs to IESG
>> Done	Submit a BCP that defines TCP behavioral requirements for NATs
>>        to IESG 
>> Done	Submit a BCP that defines ICMP behavioral requirements for NATs
>>        to IESG 
>> Done	Submit informational that discusses current NAT traversal
>>        techniques used by applications
>> Done	Submit BCP that defines multicast UDP
>> Done	Submit revision of RFC 3489 to IESG behavioral requirements for
>>        NATs to IESG
>> Done	Submit informational document for rfc3489bis test vectors
>> Done	Submit experimental document that describes how an application
>>        can determine the type of NAT it is behind
>> Done	Submit BCP document for DCCP NAT behavior
>> Done	Determine relative prioritization of the four translation cases.
>>        Documented in IETF74 minutes.
>> Done	Determine what solutions(s) and components are needed to solve
>>        each of the four cases. Create new milestones for the
>>        solution(s) and the components. Documented in IETF74 minutes.
>> Done	Submit to IESG: relaying of a TCP bytestream (std)
>> Done	Submit to IESG: relay protocol (std)
>> Done	Submit to IESG: TURN-URI document (std)
>> Done	Submit to IESG: IPv6 relay protocol (std)
>> Done	Submit to IESG: framework for IPv6/IPv4 translation (info)
>> Done	Submit to IESG: stateless IPv6/IPv4 translation (std)
>> Done	Submit to IESG: stateful IPv6/IPv4 translation (std)
>> Done	Submit to IESG: DNS rewriting for IPv6/IPv4 translation (std)
>> Done	Submit to IESG: IPv6 prefix for IPv6/IPv4 translator (std)
>> Done	Determine need and scope of multicast 6/4 translation
>> Done	Submit to IESG: FTP ALG for IPv6/IPv4 translation (std)
>> Jul 2012  Submit to IESG: large scale NAT requirements (BCP)
>> Done	Submit to IESG: Analysis of NAT-PT considerations with IPv6/IPv4
>>        translation (info)
>> Jul 2012  Submit to IESG: avoiding NAT64 with dual-stack host for
>>          local networks (std)
>> Done    Submit to IESG: host-based NAT46 translation for IPv4-only
>>        applications to access IPv6-only servers (std)
>> Nov 2012  Submit to IESG: updates to NAT MIB for NAT64 (std)
>> Nov 2012  Submit to IESG: updates to NAT MIB for CGNs (std)
>> Nov 2012  Submit to IESG: IPFIX information elements (std)
>
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave



From peter@akayla.com  Sat May 26 23:59:52 2012
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 122AD21F8507 for <ietf@ietfa.amsl.com>; Sat, 26 May 2012 23:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwdvpuuJTzxq for <ietf@ietfa.amsl.com>; Sat, 26 May 2012 23:59:50 -0700 (PDT)
Received: from smtpauth23.prod.mesa1.secureserver.net (smtpauth23.prod.mesa1.secureserver.net [64.202.165.47]) by ietfa.amsl.com (Postfix) with SMTP id 3EF0621F8468 for <ietf@ietf.org>; Sat, 26 May 2012 23:59:50 -0700 (PDT)
Received: (qmail 17455 invoked from network); 27 May 2012 06:59:49 -0000
Received: from unknown (70.77.224.29) by smtpauth23.prod.mesa1.secureserver.net (64.202.165.47) with ESMTP; 27 May 2012 06:59:47 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-mile-template.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-mile-template-04
Date: Sat, 26 May 2012 23:59:46 -0700
Message-ID: <01df01cd3bd6$4e62a460$eb27ed20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac07f1lxlPP7F3TrS72lPztocaSCDg==
Content-Language: en-us
X-Mailman-Approved-At: Tue, 29 May 2012 07:17:27 -0700
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 May 2012 06:59:52 -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-mile-template-04
Reviewer: Peter Yee
Review Date: 26-May-2012
IETF LC End Date: 28-May-2012
IESG Telechat date: 07-June-2012

Summary: This draft gives guidance on creating extensions to IODEF (RFC 5070).
The document is ready for publication as an informational RFC. 

Major Issues: None

Minor Issues: None

Nits/editorial comments:
	1) There are two occurrences of the statement "Note that this list is
present as of publication time".  It might be clearer to use the word "current"
in place of "present".
	2) Section A.3, insert "section" after "This" in the third sentence.
	3) Section A.8, drop "section" in the second sentence.
	4) Regarding the example in Appendix B, RFC 6116 uses the e164.arpa
domain, not e164.int.  You'll probably want to switch to the former.



From Basavaraj.Patil@nokia.com  Mon May 28 05:00:11 2012
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 474A121F8453 for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 05:00:11 -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 DIIYKehP6IKf for <ietf@ietfa.amsl.com>; Mon, 28 May 2012 05:00:10 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 73C0221F8447 for <ietf@ietf.org>; Mon, 28 May 2012 05:00:09 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (in-mx.nokia.com [10.160.244.30]) by mgw-sa02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q4SC05hw009745; Mon, 28 May 2012 15:00:06 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.24]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 May 2012 15:00:05 +0300
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.16]) by 008-AM1MMR1-008.mgdnok.nokia.com ([65.54.30.24]) with mapi id 14.02.0283.004; Mon, 28 May 2012 14:00:04 +0200
From: <Basavaraj.Patil@nokia.com>
To: <ietf@ietf.org>, <Markus.Isomaki@nokia.com>, <jouni.nospam@gmail.com>
Subject: Re: Vl: Last Call: <draft-ietf-mif-dns-server-selection-09.txt> (Improved Recursive DNS Server Selection for Multi-Interfaced Nodes) to Proposed Standard
Thread-Topic: Vl: Last Call: <draft-ietf-mif-dns-server-selection-09.txt> (Improved Recursive DNS Server Selection for Multi-Interfaced Nodes) to Proposed Standard
Thread-Index: AQHNPMlqsi6s/Ew1M0yMXeXpP5oQjg==
Date: Mon, 28 May 2012 12:00:03 +0000
Message-ID: <CBE8D2CE.1F528%basavaraj.patil@nokia.com>
In-Reply-To: <3XM9XQ7V74Ms@rFB0kgDC>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [173.64.197.222]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B2FB370BA03C2D428F977DC5C75CAD76@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 May 2012 12:00:05.0568 (UTC) FILETIME=[6BA4FC00:01CD3CC9]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Tue, 29 May 2012 07:17:27 -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, 28 May 2012 12:00:11 -0000

Finally :)

Lets hope the I-D has only fair weather going forward..

On 5/26/12 12:21 AM, "Savolainen Teemu (Nokia-NRC/Tampere)"
<teemu.savolainen@nokia.com> wrote:

>Here we go... Let's see what happens. This has just been 3.5 years in the
>process...
>
>Teemu
>
>---- alkuper=E4inen viesti ----
>L=E4hett.: ext The IESG
>L=E4het.:  26.05.2012, 01:35
>V.ottaja: IETF-Announce
>Kopio: mif@ietf.org
>Aihe: Last Call: <draft-ietf-mif-dns-server-selection-09.txt> (Improved
>Recursive DNS Server Selection for Multi-Interfaced Nodes) to   Proposed
>Standard
>
>
>The IESG has received a request from the Multiple Interfaces WG (mif) to
>consider the following document:
>- 'Improved Recursive DNS Server Selection for Multi-Interfaced Nodes'
>  <draft-ietf-mif-dns-server-selection-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 2012-06-08. 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
>
>
>   A multi-interfaced node is connected to multiple networks, some of
>   which may be utilizing private DNS namespaces.  A node commonly
>   receives recursive DNS server configuration information from all
>   connected networks.  Some of the recursive DNS servers may have
>   information about namespaces other servers do not have.  When a
>   multi-interfaced node needs to utilize DNS, the node has to choose
>   which of the recursive DNS servers to contact to.  This document
>   describes DHCPv4 and DHCPv6 options that can be used to configure
>   nodes with information required to perform informed recursive DNS
>   server selection decisions.
>
>
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-mif-dns-server-selection/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-mif-dns-server-selection/ballot
>/
>
>
>No IPR declarations have been submitted directly on this I-D.  The
>following IPR declaration may be related to this I-D:
>
>https://datatracker.ietf.org/ipr/1103/
>
>


From msk@cloudmark.com  Tue May 29 12:04:25 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B2C11E80D0 for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 12:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHyo2zFKuTjn for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 12:04:25 -0700 (PDT)
Received: from mail.cloudmark.com (cmgw1.cloudmark.com [208.83.136.25]) by ietfa.amsl.com (Postfix) with ESMTP id E855311E80F7 for <ietf@ietf.org>; Tue, 29 May 2012 12:04:24 -0700 (PDT)
Received: from ht1-outbound.cloudmark.com ([72.5.239.26]) by mail.cloudmark.com with bizsmtp id Fv4P1j0010as01C01v4PPc; Tue, 29 May 2012 12:04:23 -0700
X-CMAE-Match: 0
X-CMAE-Score: 0.00
X-CMAE-Analysis: v=2.0 cv=dpJZ+ic4 c=1 sm=1 a=QMZKka45TBd+hNGtXG2bIg==:17 a=LvckAehuu68A:10 a=Nd0-PibDfu8A:10 a=zutiEJmiVI4A:10 a=kj9zAlcOel0A:10 a=xqWC_Br6kY4A:10 a=b6nfwRhkAAAA:8 a=48vgC7mUAAAA:8 a=GDThVHyN_hZ64527sycA:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=QMZKka45TBd+hNGtXG2bIg==:117
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::54de:dc60:5f3e:334%10]) with mapi id 14.01.0355.002; Tue, 29 May 2012 12:04:23 -0700
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "spfbis@ietf.org" <spfbis@ietf.org>, IETF Discuss <ietf@ietf.org>
Subject: RE: [spfbis] Last Call: <draft-ietf-spfbis-experiment-09.txt> (Resolution of The	SPF and Sender ID Experiments) to	Informational RFC
Thread-Topic: [spfbis] Last Call: <draft-ietf-spfbis-experiment-09.txt> (Resolution of The	SPF and Sender ID Experiments) to	Informational RFC
Thread-Index: AQHNOz1INsCQPVSMfUCCwx/dWdUXtZbhI4RA
Date: Tue, 29 May 2012 19:04:22 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392813826C@exch-mbx901.corp.cloudmark.com>
References: <20120526124417.28073.97552.idtracker@ietfa.amsl.com>
In-Reply-To: <20120526124417.28073.97552.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudmark.com; s=default; t=1338318263; bh=lJxMbq64HAARGGVhcr5jpNpHAi04yj9jfFotQ4pgl8c=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=un6Kp4Up/me6fZRMgrmqthml9Ahzj79fi6g/Q16DODxeWDGxvj643UgDm4MBe7ULQ ETP0TcQhVViZv7yrOcdJPz90dPiI7mD4vTXJt/eBs3r0EnuY0OVqkfyQ6dF1vuHr4p GASlGVtaTmTbqVJbqhJ+Z21/OmeN39J3PMm1WLZE=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 19:04:25 -0000

> -----Original Message-----
> From: spfbis-bounces@ietf.org [mailto:spfbis-bounces@ietf.org] On Behalf =
Of The IESG
> Sent: Saturday, May 26, 2012 5:44 AM
> To: IETF-Announce
> Cc: spfbis@ietf.org
> Subject: [spfbis] Last Call: <draft-ietf-spfbis-experiment-09.txt> (Resol=
ution of The SPF and Sender ID Experiments) to Informational RFC
>=20
> The IESG has received a request from the SPF Update WG (spfbis) to
> consider the following document:
> - 'Resolution of The SPF and Sender ID Experiments'
>   <draft-ietf-spfbis-experiment-09.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 2012-06-09. 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.

In my quest to ensure I'm never done with a document I'm editing, I reviewe=
d this myself and found a couple of things I plan to change after Last Call=
 completes.  They are either grammar corrections or removal of redundant te=
xt, and aren't substantive, so I don't expect they're controversial.  So ju=
st to head off other reviewers' comments:

1) The Introduction's first and second paragraph contain substantially iden=
tical text.  This will be trimmed.

2) In the Analysis section, I believe conclusions 4 and 6 are redundant.  I=
 propose to remove 6.

3) There are a few places where I should've used "that" instead of "which".

-MSK



From faber@isi.edu  Tue May 29 14:14:17 2012
Return-Path: <faber@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 7802A11E8074 for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 14:14:17 -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=[BAYES_50=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 WtlXjtqB6HUe for <ietf@ietfa.amsl.com>; Tue, 29 May 2012 14:14:16 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id A10D421F867F for <ietf@ietf.org>; Tue, 29 May 2012 14:14:16 -0700 (PDT)
Received: from vim.isi.edu (vim.isi.edu [128.9.168.184]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q4TLDu5w025376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 May 2012 14:13:57 -0700 (PDT)
Date: Tue, 29 May 2012 14:13:56 -0700
From: Ted Faber <faber@isi.edu>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: Long discussion about IETF on the Internet Governance Caucus mailing list
Message-ID: <20120529211355.GG34428@vim.isi.edu>
References: <CAHBU6iui0_n_=3p85msgdcswC3jOhL5F0HcByCMip04FvUon7Q@mail.gmail.com> <25604_1338222652_4FC3A83C_25604_1209_1_20120528161928.23662.qmail@joyce.lan> <20120528163409.GA10172@sources.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xs+9IvWevLaxKUtW"
Content-Disposition: inline
In-Reply-To: <20120528163409.GA10172@sources.org>
X-url: http://www.isi.edu/~faber
User-Agent: Mutt/1.5.21 (2010-09-15)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: faber@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: Tue, 29 May 2012 21:14:17 -0000

--xs+9IvWevLaxKUtW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 28, 2012 at 06:34:09PM +0200, Stephane Bortzmeyer wrote:
> On Mon, May 28, 2012 at 04:19:28PM -0000,
>  John Levine <johnl@iecc.com> wrote=20
>  a message of 8 lines which said:
>=20
> > Based on what I've seem on the IGF list, people with an
> > extraordinary amount of free time.
>=20
> In some cases ("RFC 2119 terms, ALL CAPS vs lower case"), IETFers have
> some free time, too...

That's a service the IETF list provides.  I hadn't noticed that it was
springtime until the seasonal discussion broke out.

--=20
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.=
asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#=
SIG

--xs+9IvWevLaxKUtW
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAk/FPBMACgkQaUz3f+Zf+Xu2QQCgzwMVO+ugRUNtcOLOvd/oKfy6
208An0eRLwo4fx6PgdHBQflAoLp4GSZX
=5ASv
-----END PGP SIGNATURE-----

--xs+9IvWevLaxKUtW--

From bclaise@cisco.com  Tue May 29 16:14:28 2012
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 3593B11E817B; Tue, 29 May 2012 16:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.499
X-Spam-Level: 
X-Spam-Status: No, score=-10.499 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, HTML_MESSAGE=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 CbDCCuNcQM6V; Tue, 29 May 2012 16:14:25 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 8D65911E8173; Tue, 29 May 2012 16:14:24 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4TNAkXF001703; Wed, 30 May 2012 01:10:46 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4TNAhH7023219; Wed, 30 May 2012 01:10:43 +0200 (CEST)
Message-ID: <4FC55773.3000803@cisco.com>
Date: Wed, 30 May 2012 01:10:43 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com> <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
In-Reply-To: <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com>
Content-Type: multipart/alternative; boundary="------------060607070404000601010907"
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2012 23:14:28 -0000

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

Hi Roni,

[keeping only the open discussions]
>
> Hi Benoit,
>
> Thanks, see in-line
>
> Roni
>
> 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-claise-export-application-info-in-ipfix-05
>
> Reviewer: Roni Even
>
> Review Date:2012--4--7
>
> IETF LC End Date: 2012--4--17
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as an 
> Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information 
> in Cisco web page. I could not locate and information that is 
> referenced. The link is to the main Cisco web page. For example in 
> section 6.5 it lists the selectorID as 10000, where is this value located?
>
> The exact URsL are 
> http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html
> and 
> http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html
> As you can see from the URLs, there is a chance that those might change.
> Stephen Farrell had the same comment.
>
> RE: My concern was that going to Cisco web page I tried to search for 
> the information using the search window and could not find it so I 
> think that this link is not helpful for finding the information.
>
Understood. We propose
1. to remove all references to [CISCO] in the draft, except in the appendix
2. to add the following text

             Appendix X (non normative)

       A reference to the Cisco Systems assigned numbers for the Application Id and
       the different attribute assignments can be found at [CISCO  <http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07#ref-CISCO>].

       [CISCO-APPLICATION-REGISTRY] http://www.cisco.com/go/application-registry
  

3. However, it will take a couple of days to set up this new URL. So we 
propose to add

             RFC-EDITOR NOTE: at the time of publication, if the 
[CISCO-APPLICATION-REGISTRY] is not available,
             this appendix must be removed

Does it work for you?

>
>
> In section 7 I noticed that "p2pTechnology, tunnelTechnology, and 
> encryptedTechnology" are already assigned in the IANA IPFIX 
> Information elements so why assign them again as new?
>
> from RFC5102:
>
>     The value of these identifiers is in the range of 1-32767.  Within
>     this range, Information Element identifier values in the sub-range of
>     1-127 are compatible with field types used by NetFlow version 9
>     [RFC3954  <http://tools.ietf.org/html/rfc3954>].
>   
>
> So basically, if Cisco has assigned those numbers already, they can 
> reused in IANA.
>
> RE: The question is if you want the existing assignment to be used 
> without change than why have this information in the IANA 
> consideration in the first place.
>
Because the IANA registry currently contain "reserved for the 
corresponding IEs
See "100-127 Reserved" at http://www.iana.org/assignments/ipfix/ipfix.xml
>
>
>
> In section 7 I noticed that you request that the  
> applicationDescription, applicationId, applicationName, 
> classificationEngineId will receive elementid values from the range 
> 0-127. My reading from section 4.2 is this is not required, maybe add 
> text that will explain this request.
>
> See my previous remark.
>
> RE:  OK, even though it should be clear that this applies to these 
> specific selectors since you want them to be compatible with NetFlow 
> version 9 and it is not a general request for using specific sub range 
> for all selectors.
>
>
>
> Nits/editorial comments:
>
> 1.In section 4.1 last sentence what is the meaning of "by theses 
> specifications" , I did not understand the context.
>
> 2.In section 6.6 "to determine whether or the default HTTP port" 
> delete the "or"
>
> In section 6.6 "The Classification Engine ID is 2" should be "3".
>
All corrected in to-be-posted-version.

Regards, Benoit.
>
>
> will be corrected.
>
> Thanks again.
>
> Regards, Benoit.
>


--------------060607070404000601010907
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">
    Hi Roni,<br>
    <br>
    [keeping only the open discussions]<br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="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: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";
	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;}
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;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1347488741;
	mso-list-type:hybrid;
	mso-list-template-ids:-636856504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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="color:#1F497D">Hi Benoit,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Thanks, see
            in-line<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Roni<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal">I am the assigned Gen-ART reviewer for
            this draft. For background on Gen-ART, please see the FAQ at
            &lt;<a moz-do-not-send="true"
              href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
              target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal">Please resolve these comments along with
            any other Last Call comments you may receive.<o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:
              draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:
              Roni Even</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review
              Date:2012&#8211;4&#8211;7</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF
              LC End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG
              Telechat date:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:
              This draft is almost ready for publication as an
              Informational RFC.</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major
              issues:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor
              issues:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to
              information in Cisco web page. I could not locate and
              information that is referenced. The link is to the main
              Cisco web page. For example in section 6.5 it lists the
              selectorID as 10000, where is this value located?</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">The exact URsL are <a
                moz-do-not-send="true"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br>
              and <a moz-do-not-send="true"
href="http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.html</a><br>
              As you can see from the URLs, there is a chance that those
              might change.<br>
              Stephen Farrell had the same comment. </span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-bottom: 0.0001pt;
            line-height: normal;"><span style="color: rgb(31, 73, 125);">RE:
              My concern was that going to Cisco web page I tried to
              search for the information using the search window and
              could not find it so I think that this link is not helpful
              for finding the information.</span></p>
        </div>
      </div>
    </blockquote>
    Understood. We propose <br>
    1. to remove all references to [CISCO] in the draft, except in the
    appendix<br>
    2. to add the following text<br>
    &nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Appendix X (non normative)<br>
    <br>
    <pre class="newpage">      A reference to the Cisco Systems assigned numbers for the Application Id and
      the different attribute assignments can be found at [<a href="http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07#ref-CISCO">CISCO</a>].

      [CISCO-APPLICATION-REGISTRY] <a class="moz-txt-link-freetext" href="http://www.cisco.com/go/application-registry">http://www.cisco.com/go/application-registry</a>
&nbsp;</pre>
    3. However, it will take a couple of days to set up this new URL. So
    we propose to add<br>
    <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; RFC-EDITOR NOTE: at the time of publication, if the
    [CISCO-APPLICATION-REGISTRY] is not available, <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this appendix must be removed<br>
    <br>
    Does it work for you?<br>
    <br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 7 I noticed that &#8221;p2pTechnology, tunnelTechnology,
              and encryptedTechnology&#8221; are already assigned in the IANA
              IPFIX Information elements so why assign them again as
              new?</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">from RFC5102:<o:p></o:p></span></p>
          <pre>&nbsp;&nbsp; The value of these identifiers is in the range of 1-32767.&nbsp; Within<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; this range, Information Element identifier values in the sub-range of<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; 1-127 are compatible with field types used by NetFlow version 9<o:p></o:p></pre>
          <pre>&nbsp;&nbsp; [<a moz-do-not-send="true" href="http://tools.ietf.org/html/rfc3954" title="&quot;Cisco Systems NetFlow Services Export Version 9&quot;">RFC3954</a>].<o:p></o:p></pre>
          <pre><o:p>&nbsp;</o:p></pre>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">So basically, if Cisco has
              assigned those numbers already, they can reused in IANA.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-bottom: 0.0001pt;
            line-height: normal;"><span style="color: rgb(31, 73, 125);">RE:
              The question is if you want the existing assignment to be
              used without change than why have this information in the
              IANA consideration in the first place. </span></p>
        </div>
      </div>
    </blockquote>
    Because the IANA registry currently contain "reserved for the
    corresponding IEs<br>
    See "100-127 Reserved" at
    <a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/ipfix/ipfix.xml">http://www.iana.org/assignments/ipfix/ipfix.xml</a>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D">&nbsp;<o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 7 I noticed that you request that the&nbsp;
              applicationDescription, applicationId, applicationName,
              classificationEngineId will receive elementid values from
              the range 0-127. My reading from section 4.2 is this is
              not required, maybe add text that will explain this
              request.</span><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;">See my previous remark.</span><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;;color:#1F497D"> <o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="color:#1F497D">RE: &nbsp;OK, even though it should be
              clear that this applies to these specific selectors since
              you want them to be compatible with NetFlow version 9 and
              it is not a general request for using specific sub range
              for all selectors.<o:p></o:p></span></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <o:p></o:p></span></p>
          <span style="color:#1F497D"><o:p></o:p></span>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial
              comments:</span><o:p></o:p></p>
          <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">&nbsp;</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in;mso-list:l0
            level1 lfo4"><!--[if !supportLists]--><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp; </span></span><!--[endif]--><span
              dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 4.1 last sentence what is the meaning of &#8220;by
              theses specifications&#8221; , I did not understand the context.</span><o:p></o:p></p>
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in;mso-list:l0
            level1 lfo4"><!--[if !supportLists]--><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp; </span></span><!--[endif]--><span
              dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 6.6 &#8220;to determine whether or the default HTTP
              port&#8221; delete the &#8220;or&#8221;</span><o:p></o:p></p>
          <p class="MsoPlainText" style="margin-left: 0.5in;
            text-indent: -0.25in;"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In
              section 6.6 &#8220;The Classification Engine ID is 2&#8221; should be
              &#8220;3&#8221;.</span></p>
        </div>
      </div>
    </blockquote>
    All corrected in to-be-posted-version.<br>
    <br>
    Regards, Benoit.<br>
    <blockquote cite="mid:4fbc8e3b.2968b40a.5c9a.4414@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoPlainText"
            style="margin-left:.5in;text-indent:-.25in"><o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              will be corrected.<br>
              <br>
              Thanks again.<br>
              <br>
              Regards, Benoit.<br>
              <br>
              <o:p></o:p></span></p>
          <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          <p class="MsoNormal"
            style="margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060607070404000601010907--

From ron.even.tlv@gmail.com  Tue May 29 21:36:55 2012
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 0FECB21F8673; Tue, 29 May 2012 21:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.444
X-Spam-Level: 
X-Spam-Status: No, score=-3.444 tagged_above=-999 required=5 tests=[AWL=0.154,  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 aZQfe3VFadkg; Tue, 29 May 2012 21:36:46 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id E968C11E80C7; Tue, 29 May 2012 21:36:44 -0700 (PDT)
Received: by wibhn6 with SMTP id hn6so2737826wib.13 for <multiple recipients>; Tue, 29 May 2012 21:36:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:x-mailer:thread-index:content-language; bh=5br74H5zE59Y29A6PxRb5bPP8qXRxrPaG/ImXFvabfo=; b=akrhoAgJPq+XMzr+t15JUDuJdo5eI4WPecwqzzM/CRziR7ALORu6Idxs98d71KIB2z L93NpugzHaDzHLeyTaWAwwuEPaASHgNO7JvXGPdMrYZ2pc2f2QK5ev6XgqlYDmvNNYzX EfwgGHLX6IzlT8nVlLzVsVSyINGMbU4oBoyd3t7yrOtyBviPaZWu9u5G0p6T4PHqu6CX gvWIn+K+RuvrWM/Go4xChoD8YUClB6EeYTGIkYVLshDcUSLyc7iqvcjbrsH+dPcvRERV BJYVA7icCq5z1y5OjfTwmeDEvZklYEVAFUNA/9uH3Wd3LnxgpLFUhL2w+DTOcbWnOPuY sVTw==
Received: by 10.216.143.148 with SMTP id l20mr9909939wej.115.1338352603969; Tue, 29 May 2012 21:36:43 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id f19sm52415571wiw.11.2012.05.29.21.36.40 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 May 2012 21:36:41 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <4f800f2f.634cb40a.13a1.ffff8003@mx.google.com> <4FBC219D.8070000@cisco.com> <4fbc8e3b.2968b40a.5c9a.4414@mx.google.com> <4FC55773.3000803@cisco.com>
In-Reply-To: <4FC55773.3000803@cisco.com>
Subject: RE: Gen-ART LC review of draft-claise-export-application-info-in-ipfix-05
Date: Wed, 30 May 2012 07:34:27 +0300
Message-ID: <4fc5a3d9.f34bb40a.71e1.4c87@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0034_01CD3E36.A698F2D0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac098EkDfcSzloutTp2WdvYu0WEgvAALR5bw
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF' <ietf@ietf.org>, draft-claise-export-application-info-in-ipfix.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 May 2012 04:36:55 -0000

This is a multi-part message in MIME format.

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

Hi Benoit,

Your proposals are OK with me

Roni

 

From: Benoit Claise [mailto:bclaise@cisco.com] 
Sent: Wednesday, May 30, 2012 2:11 AM
To: Roni Even
Cc: draft-claise-export-application-info-in-ipfix.all@tools.ietf.org;
gen-art@ietf.org; 'IETF'; me
Subject: Re: Gen-ART LC review of
draft-claise-export-application-info-in-ipfix-05

 

Hi Roni,

[keeping only the open discussions]



Hi Benoit,

Thanks, see in-line

Roni

 

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-claise-export-application-info-in-ipfix-05

Reviewer: Roni Even

Review Date:2012-4-7

IETF LC End Date: 2012-4-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as an Informational RFC.

 

Major issues:

 

Minor issues:

 

In sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in
Cisco web page. I could not locate and information that is referenced. The
link is to the main Cisco web page. For example in section 6.5 it lists the
selectorID as 10000, where is this value located?

The exact URsL are
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/pre
sentation_c96-629396.html
and
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558/ps6616/pro
duct_bulletin_c25-627831.html
As you can see from the URLs, there is a chance that those might change.
Stephen Farrell had the same comment. 

 

RE: My concern was that going to Cisco web page I tried to search for the
information using the search window and could not find it so I think that
this link is not helpful for finding the information.

Understood. We propose 
1. to remove all references to [CISCO] in the draft, except in the appendix
2. to add the following text
    
            Appendix X (non normative)

      A reference to the Cisco Systems assigned numbers for the Application
Id and
      the different attribute assignments can be found at [CISCO
<http://tools.ietf.org/html/draft-claise-export-application-info-in-ipfix-07
#ref-CISCO> ].
 
      [CISCO-APPLICATION-REGISTRY]
http://www.cisco.com/go/application-registry
 

3. However, it will take a couple of days to set up this new URL. So we
propose to add

            RFC-EDITOR NOTE: at the time of publication, if the
[CISCO-APPLICATION-REGISTRY] is not available, 
            this appendix must be removed

Does it work for you?









In section 7 I noticed that "p2pTechnology, tunnelTechnology, and
encryptedTechnology" are already assigned in the IANA IPFIX Information
elements so why assign them again as new?

from RFC5102:

   The value of these identifiers is in the range of 1-32767.  Within
   this range, Information Element identifier values in the sub-range of
   1-127 are compatible with field types used by NetFlow version 9
   [RFC3954 <http://tools.ietf.org/html/rfc3954> ].
 

So basically, if Cisco has assigned those numbers already, they can reused
in IANA.

 

RE: The question is if you want the existing assignment to be used without
change than why have this information in the IANA consideration in the first
place. 

Because the IANA registry currently contain "reserved for the corresponding
IEs
See "100-127 Reserved" at http://www.iana.org/assignments/ipfix/ipfix.xml 

 






In section 7 I noticed that you request that the  applicationDescription,
applicationId, applicationName, classificationEngineId will receive
elementid values from the range 0-127. My reading from section 4.2 is this
is not required, maybe add text that will explain this request.

See my previous remark. 

 

RE:  OK, even though it should be clear that this applies to these specific
selectors since you want them to be compatible with NetFlow version 9 and it
is not a general request for using specific sub range for all selectors.






 

Nits/editorial comments:

 

1.  In section 4.1 last sentence what is the meaning of "by theses
specifications" , I did not understand the context.

2.  In section 6.6 "to determine whether or the default HTTP port" delete
the "or"

In section 6.6 "The Classification Engine ID is 2" should be "3".

All corrected in to-be-posted-version.

Regards, Benoit.




will be corrected.

Thanks again.

Regards, Benoit.




 

 

 


------=_NextPart_000_0034_01CD3E36.A698F2D0
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 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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Times New Roman \, serif";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* 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";
	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;}
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;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1032532832;
	mso-list-type:hybrid;
	mso-list-template-ids:-209704826 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Hi =
Benoit,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Your proposals are OK with =
me<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> Benoit Claise [mailto:bclaise@cisco.com] <br><b>Sent:</b> =
Wednesday, May 30, 2012 2:11 AM<br><b>To:</b> Roni Even<br><b>Cc:</b> =
draft-claise-export-application-info-in-ipfix.all@tools.ietf.org; =
gen-art@ietf.org; 'IETF'; me<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-claise-export-application-info-in-ipfix-05<o:p></o:p></span></p></d=
iv></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hi Roni,<br><br>[keeping only the open =
discussions]<br><br><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Benoit,</span><o:p></o:p></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks, see =
in-line</span><o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt;border-color:-moz-use-text-color -moz-use-text-color =
-moz-use-text-color&#13;&#10;          blue;-moz-border-top-colors: =
none;-moz-border-right-colors:
          none;-moz-border-bottom-colors: none;-moz-border-left-colors: =
none;-moz-border-image: none'><p class=3DMsoNormal>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;<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"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
draft-claise-export-application-info-in-ipfix-05</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;4&#8211;7</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;4&#8211;17</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as an Informational =
RFC.</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In =
sections 2, 4.1 (PANA-L7), 5, 6.5 the draft points to information in =
Cisco web page. I could not locate and information that is referenced. =
The link is to the main Cisco web page. For example in section 6.5 it =
lists the selectorID as 10000, where is this value =
located?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>The exact URsL are <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555=
/ps6601/presentation_c96-629396.html">http://www.cisco.com/en/US/prod/col=
lateral/iosswrel/ps6537/ps6555/ps6601/presentation_c96-629396.html</a><br=
>and <a =
href=3D"http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6558=
/ps6616/product_bulletin_c25-627831.html">http://www.cisco.com/en/US/prod=
/collateral/iosswrel/ps6537/ps6558/ps6616/product_bulletin_c25-627831.htm=
l</a><br>As you can see from the URLs, there is a chance that those =
might change.<br>Stephen Farrell had the same comment. =
</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: My concern was that going to Cisco web =
page I tried to search for the information using the search window and =
could not find it so I think that this link is not helpful for finding =
the information.</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt;line-height:normal'><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Understood. We propose <br>1. to remove all references =
to [CISCO] in the draft, except in the appendix<br>2. to add the =
following text<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Appendix X (non =
normative)<o:p></o:p></span></p><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A =
reference to the Cisco Systems assigned numbers for the Application Id =
and<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the different =
attribute assignments can be found at [<a =
href=3D"http://tools.ietf.org/html/draft-claise-export-application-info-i=
n-ipfix-07#ref-CISCO">CISCO</a>].<o:p></o:p></pre><pre><o:p>&nbsp;</o:p><=
/pre><pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [CISCO-APPLICATION-REGISTRY] <a =
href=3D"http://www.cisco.com/go/application-registry">http://www.cisco.co=
m/go/application-registry</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre=
><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>3. =
However, it will take a couple of days to set up this new URL. So we =
propose to add<br><br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp; RFC-EDITOR NOTE: at the time of publication, if the =
[CISCO-APPLICATION-REGISTRY] is not available, =
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
this appendix must be removed<br><br>Does it work for =
you?<br><br><br><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that &#8221;p2pTechnology, tunnelTechnology, and =
encryptedTechnology&#8221; are already assigned in the IANA IPFIX =
Information elements so why assign them again as =
new?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>from RFC5102:</span><o:p></o:p></p><pre>&nbsp;&nbsp; The =
value of these identifiers is in the range of 1-32767.&nbsp; =
Within<o:p></o:p></pre><pre>&nbsp;&nbsp; this range, Information Element =
identifier values in the sub-range of<o:p></o:p></pre><pre>&nbsp;&nbsp; =
1-127 are compatible with field types used by NetFlow version =
9<o:p></o:p></pre><pre>&nbsp;&nbsp; [<a =
href=3D"http://tools.ietf.org/html/rfc3954" title=3D"&quot;Cisco Systems =
NetFlow Services Export Version =
9&quot;">RFC3954</a>].<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>So basically, if Cisco has assigned those numbers =
already, they can reused in IANA.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: The question is if you want the existing =
assignment to be used without change than why have this information in =
the IANA consideration in the first place. =
</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'>Because the IANA registry currently contain =
&quot;reserved for the corresponding IEs<br>See &quot;100-127 =
Reserved&quot; at <a =
href=3D"http://www.iana.org/assignments/ipfix/ipfix.xml">http://www.iana.=
org/assignments/ipfix/ipfix.xml</a> <o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid windowtext 1.5pt;padding:0in 0in =
0in 4.0pt;border-color:-moz-use-text-color -moz-use-text-color =
-moz-use-text-color&#13;&#10;          blue;-moz-border-top-colors: =
none;-moz-border-right-colors:
          none;-moz-border-bottom-colors: none;-moz-border-left-colors: =
none;-moz-border-image: none'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 I noticed that you request that the&nbsp; applicationDescription, =
applicationId, applicationName, classificationEngineId will receive =
elementid values from the range 0-127. My reading from section 4.2 is =
this is not required, maybe add text that will explain this =
request.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>See my previous remark.</span><span =
style=3D'font-size:12.0pt'> </span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>RE: &nbsp;OK, even though it should be clear =
that this applies to these specific selectors since you want them to be =
compatible with NetFlow version 9 and it is not a general request for =
using specific sub range for all selectors.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br><br><br></span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:</span><o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</spa=
n><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
4.1 last sentence what is the meaning of &#8220;by theses =
specifications&#8221; , I did not understand the =
context.</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;to determine whether or the default HTTP port&#8221; delete =
the &#8220;or&#8221;</span><o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
6.6 &#8220;The Classification Engine ID is 2&#8221; should be =
&#8220;3&#8221;.</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>All =
corrected in to-be-posted-version.<br><br>Regards, =
Benoit.<br><br><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'><br>will be corrected.<br><br>Thanks =
again.<br><br>Regards, Benoit.<br><br><br></span><o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New Roman , =
serif","serif"'>&nbsp;</span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0034_01CD3E36.A698F2D0--


From dromasca@avaya.com  Wed May 30 05:17:06 2012
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 8582221F861C; Wed, 30 May 2012 05:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.468
X-Spam-Level: 
X-Spam-Status: No, score=-103.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 e3UNwY+R0dvr; Wed, 30 May 2012 05:17:06 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id D1DFE21F8625; Wed, 30 May 2012 05:17:05 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAB4Pxk/GmAcF/2dsb2JhbABEtA2BB4IXAQEBAQMSHgo0CwwEAgEIDQQEAQELBgwHBAEGAUUJCAEBBBMIGodpC5wTnSGLBYIsgjZgA5YnhGKKAoJi
X-IronPort-AV: E=Sophos;i="4.75,685,1330923600"; d="scan'208";a="350038127"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 30 May 2012 08:15:05 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 May 2012 08:14:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for DefiningExtensions to IODEF) to Informational RFC
Date: Wed, 30 May 2012 14:16:52 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407A503C2@307622ANEX5.global.avaya.com>
In-Reply-To: <20120516215321.9671.39664.idtracker@ietfa.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for DefiningExtensions to IODEF) to Informational RFC
Thread-Index: Ac0zrndzehc1YPfHShOUxclriX6j+AKrpZyg
References: <20120516215321.9671.39664.idtracker@ietfa.amsl.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ietf@ietf.org>
Cc: mile@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 12:17:06 -0000

Hi,=20

The inclusion of the template as an Appendix in the document is
confusing - right now A.1 through A.7 define sections in the future
I-Ds, while A.8 and A.9 describe appendices in the future I-D. This
document has two sections each titled Appendix A and Appendix B.
Moreover, this inclusion has the disadvantage that if changes or updates
need to be brought up for reasons whatsoever, a new RFC needs to be
written. Did the author and the WG considered adopting the approach
taken by RFC 5249 which located the templates under the IETF tools web
pages and only referred them from the RFC?=20

Regards,

Dan




> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Thursday, May 17, 2012 12:53 AM
> To: IETF-Announce
> Cc: mile@ietf.org
> Subject: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for
> DefiningExtensions to IODEF) to Informational RFC
>=20
>=20
> The IESG has received a request from the Managed Incident Lightweight
> Exchange WG (mile) to consider the following document:
> - 'Guidelines for Defining Extensions to IODEF'
>   <draft-ietf-mile-template-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 2012-05-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.
>=20
> Abstract
>=20
>=20
>    This document provides guidelines for extensions to IODEF [RFC5070]
>    for exchange of incident management data, and contains a template
> for
>    Internet-Drafts describing those extensions, in order to ease the
>    work and improve the quality of extension descriptions.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mile-template/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mile-template/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20


From dhc2@dcrocker.net  Wed May 30 09:15:59 2012
Return-Path: <dhc2@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 E21CD11E80F9 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 09:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0YwcQxu-Q1O for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 09:15:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2D911E80F8 for <ietf@ietf.org>; Wed, 30 May 2012 09:15:59 -0700 (PDT)
Received: from [192.168.2.101] (f052240238.adsl.alicedsl.de [78.52.240.238]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4UGFsdt011378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 May 2012 09:15:55 -0700
Message-ID: <4FC647B5.8070708@dcrocker.net>
Date: Wed, 30 May 2012 18:15:49 +0200
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: new mailing list for discussing ABNF issues
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.17]); Wed, 30 May 2012 09:15:57 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2012 16:16:00 -0000

Folks,

Periodically someone wants to ask a question about ABNF, suggest an 
enhancement or otherwise exchange views about ABNF.  There has not been 
an obvious forum for this.  This sometimes means that Paul Overell and I 
get queried, as authors of the relevant RFC.  For quick items, that's 
fine, but sometimes the issues are more substantive.

So we've set up:

    abnf-discuss@ietf.org

For public discussion of the meta-language.

Subscribe at:

    https://www.ietf.org/mailman/listinfo/abnf-discuss
There will also be a web page to hold listings of tools and other 
relevant materials.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mehmet.ersue@nsn.com  Wed May 30 11:24:16 2012
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 D9EB111E80E8; Wed, 30 May 2012 11:24:16 -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 Rw0S39S8VKWi; Wed, 30 May 2012 11:24:16 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id CB1C211E80E5; Wed, 30 May 2012 11:24:15 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q4UIOA7u000371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 May 2012 20:24:10 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q4UIO81J025488; Wed, 30 May 2012 20:24:10 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 May 2012 20:24:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New Maillist for the discussion on the Management of Constrained Networks and Devices
Date: Wed, 30 May 2012 20:24:00 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403D56943@DEMUEXC006.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: New Maillist for the discussion on the Management of Constrained Networks and Devices
Thread-Index: Ac0+kWJuHevLc3OQQiun3QRVzjfThQ==
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: <coma@ietf.org>
X-OriginalArrivalTime: 30 May 2012 18:24:08.0463 (UTC) FILETIME=[671B39F0:01CD3E91]
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: 3587
X-purgate-ID: 151667::1338402250-00001F01-9841B028/0-0/0-0
Cc: ops-dir@ietf.org, core-chairs@tools.ietf.org, ietf@ietf.org, smartobject-interest@ietf.org, core@ietf.org, opsawg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 18:24:17 -0000

Hi All,

as noted in the maillist announcement of IETF secretary "coma" maillist
is for the discussion on the management of constrained networks and
devices. The mailing list will discuss and identify the issues and
requirements and objectives for the management of devices in such an
environment with a special focus on and differentiation of device
classes.=20

The idea and trigger for the maillist creation came from a discussion in
the OPS directorate during IETF #82. As
draft-ietf-opsawg-management-stds-07 states IETF so far has not
developed specific technologies for the management of constrained
networks. OPS directorate members stated in IETF #82 that there is a
need to understand the requirements and the necessary solutions for the
management of such a constrained network and its devices. The assumption
people had was that we need a comprehensive management approach to be
able to address the diverse needs of different device classes.

Although the OPS area was doing already standardization work for network
management, the Core WG is one of the essential WGs at IETF interested
in the management of constrained devices.=20

Following are some of the questions which have been raised in the OPS
directorate meeting, which are for sure subject to extend from Core WG
pov.:

*	Do we need a new development for IoT management (i.e.
constrained devices) at all?=20
-	If yes, what is really needed as standard and what is an
overkill?
*	What type of devices can we support?
*	How are the classes 0-2 for constrained devices defined in
detail?
*	Is some simple configuration management already sufficient?
-	Or do we need also a simple fault management and monitoring?
*	What type of data model modules do we need to standardize?=20
-	Just a few core models like ip-cfg, interface?
-	or also other specific models for monitoring?
*	Can we use available management standards and data models as a
starting point and simplify them?
*	Concerning the encoding (JSON, XML, or binary) we seem to be
flexible with tools.
-	Concerning a normative data modeling language, we need to choose
a suitable language capable to prepare structured models.=20
-	Is JSON sufficient for this purpose, or should YANG or any other
modeling language be used?=20
*	What is appropriate as message transport?
-	CoAP over UDP with soft-transactions?
-	Netconf-Light over TCP?

Obviously the list of the questions above is not exhaustive.

Carsten kindfully provided already in the Prague meeting the definition
of device classes 0-2
(http://www.ietf.org/proceedings/80/slides/core-0.pdf). I think it would
be useful to start a discussion first on the detailed definition of
these device classes 0-2 in constrained networks and based on their
capabilities which functionality they will be able to support. This can
be then used as a guideline for further discussion on the requirements
or objectives for management of such devices.=20

As noted in the announcement the result of the coma discussion can lead
to a taxonomy document and a problem statement highlighting the need for
new work.

Please send your opinions/comments to the coma maillist (coma@ietf.org).
To subscribe pls go to: https://www.ietf.org/mailman/listinfo/coma=20

Cheers,=20
Mehmet=20


BTW: Coma has been chosen as the maillist name following the definition
below:

Coma \Co"ma\, n. [L., hair, fr. Gr. ko`mh.]
   1. (Astron.) The envelope of a comet; a nebulous covering,
      which surrounds the nucleus or body of a comet.
      [1913 Webster]


From hartmans@mit.edu  Wed May 30 11:29:50 2012
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 7BF2221F8505 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 11:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.194
X-Spam-Level: 
X-Spam-Status: No, score=-103.194 tagged_above=-999 required=5 tests=[AWL=-0.929, 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 nyMQUR6VPlqt for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 11:29:50 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0842321F84FC for <ietf@ietf.org>; Wed, 30 May 2012 11:29:49 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 7446E20424; Wed, 30 May 2012 14:29:47 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 7CF274151; Wed, 30 May 2012 14:29:48 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simo Sorce <simo@redhat.com>
Subject: Re: [Ietf-krb-wg] Add. comments on Kdc model, WAS[Re:  I-D Action: draft-ietf-krb-wg-kdc-model-12.txt]
References: <20120529110632.12414.30105.idtracker@ietfa.amsl.com> <tsly5o97gfc.fsf@mit.edu> <1338397999.8230.7.camel@willson.li.ssimo.org> <1338399915.8230.37.camel@willson.li.ssimo.org>
Date: Wed, 30 May 2012 14:29:48 -0400
In-Reply-To: <1338399915.8230.37.camel@willson.li.ssimo.org> (Simo Sorce's message of "Wed, 30 May 2012 13:45:15 -0400")
Message-ID: <tslvcjd5xpf.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf-krb-wg@anl.gov, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 18:29:50 -0000

[I'm going to forward Simo's original comments to the IETF list because
this doc is in IETF last call.
Here are my responses as chair.
]
>>>>> "Simo" == Simo Sorce <simo@redhat.com> writes:

    Simo> 4.1.1.5.  principalNumberOfFailedAuthenticationAttempts

    Simo>    This single-valued integer attribute contains a count of
    Simo> the number of times an authentication attempt was unsuccessful
    Simo> for this Principal.  Implementations SHOULD NOT allow this
    Simo> counter to be reset.

[. . .]

    Simo> They force a mechanism where you have a specific counter. It
    Simo> seems to prevent instead an implementation that may have a
    Simo> multi-valued attribute where all failed attempts are recorded
    Simo> in order to have an audit trail, and the number of failed
    Simo> attempts is computed by counting these values.

I think you'd also need to record last successful authentication.
However, given last successful authentication and  a set of failed
authentications I think it's  quite easy to give an algorithm for
producing count of failed authentications and  last failed
authentication.
It does mean that to increment the count of failed authentications you
need to decide on a time for the list of failed authentications.
I think  that's consistent with the information model though.


    Simo> However assuming that this scheme is really preferred, then I
    Simo> do not understand how it can be implemented if 4.1.1.5 says
    Simo> that the counter should not be reset. I think implementations
    Simo> need to reset it when a successful authentication happens. I
    Simo> think that should be explicitly said, rather than a blanket
    Simo> 'SHOULD NOT reset'.

There was WG discussion on this.
The text really means the count should be non-decreasing.
This  makes it impossible to implement a policy like 2 failed auths
since the last successful auth.

With my chair hat on, my reading of the discussion is that we really do
mean what the text says. However, I don't think the point about being
unable to track number of failed auths since last successful auth has
been brought up before and that point is sufficient to reopen the
discussion.

From hartmans@mit.edu  Wed May 30 11:30:35 2012
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 27E9521F8534 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 11:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.228
X-Spam-Level: 
X-Spam-Status: No, score=-103.228 tagged_above=-999 required=5 tests=[AWL=-0.963, 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 bY7wj3M7Ym+V for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 11:30:34 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0252B21F8505 for <ietf@ietf.org>; Wed, 30 May 2012 11:30:33 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 76F75204BA; Wed, 30 May 2012 14:30:30 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A8E514151; Wed, 30 May 2012 14:30:31 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org,ietf-krb-wg@anl.gov
Subject: last call comments on draft-ietf-krb-wg-kdc-model
Date: Wed, 30 May 2012 14:30:31 -0400
Message-ID: <tslr4u15xo8.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/digest; boundary="=-=-="
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 18:30:35 -0000

--=-=-=

Subject: Topics
MIME-Version: 1.0

Topics:
   [Ietf-krb-wg] Add. comments on Kdc model,  WAS[Re:  I-D Action: draft-ietf-krb-wg-kdc-model-12.txt]
   Re: [Ietf-krb-wg] I-D Action: draft-ietf-krb-wg-kdc-model-12.txt

--=-=-=

Date: Wed, 30 May 2012 13:45:15 -0400
From: Simo Sorce <simo@redhat.com>
To: ietf-krb-wg@anl.gov
Subject: [Ietf-krb-wg] Add. comments on Kdc model,  WAS[Re:  I-D Action: draft-ietf-krb-wg-kdc-model-12.txt]
Message-ID: <1338399915.8230.37.camel@willson.li.ssimo.org>
References: <20120529110632.12414.30105.idtracker@ietfa.amsl.com>
	<tsly5o97gfc.fsf@mit.edu>
	<1338397999.8230.7.camel@willson.li.ssimo.org>
MIME-Version: 1.0

I have additional comments.


These following 3 attribute definitions bind the implementer to a very
special way to address counting failed authentication attempts.

4.1.1.5.  principalNumberOfFailedAuthenticationAttempts

   This single-valued integer attribute contains a count of the number
   of times an authentication attempt was unsuccessful for this
   Principal.  Implementations SHOULD NOT allow this counter to be
   reset.

4.1.1.6.  principalLastFailedAuthentication

   This single-valued attribute contains the time and date for the last
   failed authentication attempt for this Principal.  The syntax of the
   attribute MUST be Internet Date/Time Format from [RFC3339].

4.1.1.7.  principalLastSuccessfulAuthentication

   This single-valued attribute contains the time and date for the last
   successful authentication attempt for this principal.  The syntax of
   the attribute MUST be Internet Date/Time Format from [RFC3339].\


They force a mechanism where you have a specific counter. It seems to
prevent instead an implementation that may have a multi-valued attribute
where all failed attempts are recorded in order to have an audit trail,
and the number of failed attempts is computed by counting these values.

However assuming that this scheme is really preferred, then I do not
understand how it can be implemented if 4.1.1.5 says that the counter
should not be reset. I think implementations need to reset it when a
successful authentication happens. I think that should be explicitly
said, rather than a blanket 'SHOULD NOT reset'.


I would like to make 4.1.1.8, 4.1.1.9 a SHOULD, not a MUST

The way 4.1.1.10 is worded makes it impossible to reuse the
modifyTimestamp attribute normally present in LDAP directories, as
Kerberos implementations cannot force the directory not to update the
timestamp on credential changes, so please drop the exclusion, I do not
see what's the point anyways.

In 4.2, it is unclear what 'MUST facilitate, to the extent possible, an
   administrator's ability to place more restrictive access
controls ...' will end up being interpreted.
How do you measure if an implementation complies with this mandate ?

I am not sure I understand 4.3.

4.3.1.5 and 4.3.1.6 are not consistent with the rest of the document
about how the date format is mandated. (Will need to be fixed to
whatever we decide after discussion about date format I opened in a
separate thread)

Also keyNotUsedBefore keyNotUsedAfter keyIsDisabled are not something
normally associated to key attributes today generally they are
associated to keysets, is there a MUST implied in these having to be
available per key, and not per keyset ?


I find the part on policy a bit hand-wavy, what is the point of
identifying specific, yet undefined, policies with OIDs if they are
opaque in the end ?

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York

_______________________________________________
ietf-krb-wg mailing list
ietf-krb-wg@lists.anl.gov
https://lists.anl.gov/mailman/listinfo/ietf-krb-wg



--=-=-=

Date: Wed, 30 May 2012 13:13:19 -0400
From: Simo Sorce <simo@redhat.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: ietf-krb-wg@anl.gov
Subject: Re: [Ietf-krb-wg] I-D Action: draft-ietf-krb-wg-kdc-model-12.txt
Message-ID: <1338397999.8230.7.camel@willson.li.ssimo.org>
References: <20120529110632.12414.30105.idtracker@ietfa.amsl.com>
	 <tsly5o97gfc.fsf@mit.edu>
MIME-Version: 1.0

On Wed, 2012-05-30 at 13:00 -0400, Sam Hartman wrote:
> I'd like to call the working group's attention to the new text
> surrounding RFc 2119 language.  In particular in this draft, MUST
> features in the information model MUST be representable in schema *and*
> MUST be supported by all implementations of the information model.  That
> last was intended by Leif but was new to me.

Thanks for bringing this up Sam.


I am reading the doc now and I have a question as to why we have a MUST
on the syntax of attributes like principalNotUsedBefore.

It says it MUST use "Internet Date/Time Format from [RFC3339]"

This is problematic as LDAP uses generalizedTime defined in RFC4517.
It is a representation of ISO8061 just like RFC3339, but a *different*
representation.

Trying to force all implementations to use the RFC3339 definition seem
wrong.
What implementation, today, uses RFC3339 ?

I would rather suggest that the document does not mandate the specific
representation discussed in RFC3339 but allow any ISO8601 based
representation.

If it is felt that one representation really needs to be chosen then I'd
ask to use the generalizedTime representation as defined by RFC4517
instead of the one in RFC3339.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York




--=-=-=--

From stpeter@stpeter.im  Wed May 30 18:49:42 2012
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 BA5CA11E80D5 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 18:49: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=[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 vTBwjWrEpifC for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 18:49:41 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 61F9E11E80D2 for <ietf@ietf.org>; Wed, 30 May 2012 18:49:41 -0700 (PDT)
Received: from [192.168.0.7] (unknown [216.17.179.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1A5064005A; Wed, 30 May 2012 20:06:10 -0600 (MDT)
Message-ID: <4FC6CE2F.70903@stpeter.im>
Date: Wed, 30 May 2012 19:49:35 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
In-Reply-To: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 01:49:42 -0000

Overall I continue to think that this is a helpful document, as were its
predecessors.

That said, I would assume that many potential readers of this document
are not native English speakers. Thus I suggest that the more colloquial
words and phrases might best be changed to more standard English.
Naturally one can quibble about particulars, but here are some examples
as I see them:

"get into the swing of things"
"give them a warm, fuzzy feeling"
"happenings"
"unsung heroes"
"home base"
"pet project"
"pet peeve"
"leaps and bounds"
"get technical"
"discussions of cosmic significance"
"gatherings of the tribes"
"kicks in"
"breath of fresh air"
"big-name"
"take the pluge"

I realize that such words and phrases lend a friendly tone to the
document, but IMHO that friendliness will be lost on non-native speakers.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

From lear@cisco.com  Wed May 30 23:22:05 2012
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 D98AF11E80B7 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEAtlEa2b9Ex for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:22:04 -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 F3B0C11E8093 for <ietf@ietf.org>; Wed, 30 May 2012 23:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=7261; q=dns/txt; s=iport; t=1338445324; x=1339654924; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=F+Q7rCtgPI3AxRd9/ZnNWHgGLJLvS+sikZc9BtwWtBQ=; b=lslrvfNHMmjNldtjklZm/ZfL7elf28BvwWCXeJ9IEcbdstomdUbKVzOd LNvkAwg+u4/Uv9nLaRR7j/dMYbeKixxPYXtJAU6osovRCtsHgRNZ0xaaW lUPiTpn0tL1niJR/wTkAuYHz2+wBp/7uq2pIKlLC5NjU5r5Q04s7zzmlw U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAEQNx0+Q/khL/2dsb2JhbABEhU2FXqhpgQeCFwEBAQQSARBLGwsYCRoHAgIPAjUREwYCAQEeh2kLmSONH5JUjzyBEgOVGIEPjH6BZoJigV0
X-IronPort-AV: E=Sophos;i="4.75,689,1330905600"; d="scan'208,217";a="73844008"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 31 May 2012 06:22:02 +0000
Received: from dhcp-10-61-99-222.cisco.com (dhcp-10-61-99-222.cisco.com [10.61.99.222]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q4V6M1ZB015458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 31 May 2012 06:22:02 GMT
Message-ID: <4FC70E09.30002@cisco.com>
Date: Thu, 31 May 2012 08:22:01 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
In-Reply-To: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.1
Content-Type: multipart/alternative; boundary="------------020509040505070302020600"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 06:22:06 -0000

This is a multi-part message in MIME format.
--------------020509040505070302020600
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi,

I agree with much of what Peter Saint-Andre wrote.  In addition I
suggest the following changes:

  * I've been told by some that the Mission of the IETF is in some way
    out of date.  I don't know whether this is true, but if it is, the
    reference should be removed.
  * It's probably worth adding a word or two about the fact that the
    ISOC Board is the final appellate avenue in the standardization
    process.  In this way it may also make sense to move Section 3.2.1
    further back behind the IAB.
  * I don't know about anyone else, but my experience has changed with
    regard to there being a "fair amount of time for socializing".  I
    would say there is a modest amount of time for socializing.
  * The Tao mentions that we meet once a year in each region.  I don't
    think that's true for Asia at this point.  The text might call out
    that we meet where there are participants, or words that the IAOC
    might provide.
  * The last paragraph in Section 4 is outdated.  Everyone uses wireless
    these daysâ€“ everywhere at nearly every meeting.
  * 4.12 really should be a top level section (moved further back).
  * Section 5 (Working Groups) really should be moved forward (after
    Section 3 but before what is now Section 4).
  * Move acknowledgments to the back.  As it stands that text forms a
    disconnect between the Intro and later sections.

Finally I have been told that the Tao is meant to be a living document,
e.g., a wiki.  Is that now not to be the case?

Eliot


On 5/31/12 12:56 AM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'The Tao of IETF: A Novice's Guide to the Internet Engineering Task
>    Force'
>   <draft-hoffman-tao4677bis-15.txt> as Informational RFC
>
> The Tao of the IETF has grown a bit stale.  For example, many of the
> tasks that were requested by email are now done with online tools,
> completely avoiding manual intervention by the Secretariat.  This is
> an effort to refresh the document.
>
> 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 2012-06-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.
>
> Abstract
>
>    This document describes the inner workings of IETF meetings and
>    Working Groups, discusses organizations related to the IETF, and
>    introduces the standards process.  It is not a formal IETF process
>    document but instead an informational overview.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/ballot/
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>

--------------020509040505070302020600
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    I agree with much of what Peter Saint-Andre wrote.Â  In addition I
    suggest the following changes:<br>
    <ul>
      <li>I've been told by some that the Mission of the IETF is in some
        way out of date.Â  I don't know whether this is true, but if it
        is, the reference should be removed.</li>
      <li>It's probably worth adding a word or two about the fact that
        the ISOC Board is the final appellate avenue in the
        standardization process.Â  In this way it may also make sense to
        move Section 3.2.1 further back behind the IAB.</li>
      <li>I don't know about anyone else, but my experience has changed
        with regard to there being a "fair amount of time for
        socializing".Â  I would say there is a modest amount of time for
        socializing.</li>
      <li>The Tao mentions that we meet once a year in each region.Â  I
        don't think that's true for Asia at this point.Â  The text might
        call out that we meet where there are participants, or words
        that the IAOC might provide.<br>
      </li>
      <li>The last paragraph in Section 4 is outdated.Â  Everyone uses
        wireless these daysâ€“ everywhere at nearly every meeting.</li>
      <li>4.12 really should be a top level section (moved further
        back).</li>
      <li>Section 5 (Working Groups) really should be moved forward
        (after Section 3 but before what is now Section 4).</li>
      <li>Move acknowledgments to the back.Â  As it stands that text
        forms a disconnect between the Intro and later sections.</li>
    </ul>
    <p>Finally I have been told that the Tao is meant to be a living
      document, e.g., a wiki.Â  Is that now not to be the case?<br>
    </p>
    <p>Eliot<br>
    </p>
    <br>
    On 5/31/12 12:56 AM, The IESG wrote:
    <blockquote
      cite="mid:20120530225655.19475.74871.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
The IESG has received a request from an individual submitter to consider
the following document:
- 'The Tao of IETF: A Novice's Guide to the Internet Engineering Task
   Force'
  &lt;draft-hoffman-tao4677bis-15.txt&gt; as Informational RFC

The Tao of the IETF has grown a bit stale.  For example, many of the
tasks that were requested by email are now done with online tools,
completely avoiding manual intervention by the Secretariat.  This is
an effort to refresh the document.

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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2012-06-27. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract

   This document describes the inner workings of IETF meetings and
   Working Groups, discusses organizations related to the IETF, and
   introduces the standards process.  It is not a formal IETF process
   document but instead an informational overview.

The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/">http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/ballot/">http://datatracker.ietf.org/doc/draft-hoffman-tao4677bis/ballot/</a>

No IPR declarations have been submitted directly on this I-D.




</pre>
    </blockquote>
  </body>
</html>

--------------020509040505070302020600--

From brian.e.carpenter@gmail.com  Wed May 30 23:31:44 2012
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 2B9EB11E80EF for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.681
X-Spam-Level: 
X-Spam-Status: No, score=-101.681 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 PCpD8O2WqCb3 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:31:43 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6017C11E80F2 for <ietf@ietf.org>; Wed, 30 May 2012 23:31:43 -0700 (PDT)
Received: by eekd4 with SMTP id d4so179635eek.31 for <ietf@ietf.org>; Wed, 30 May 2012 23:31: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=mWSfUS60kwqhajnA9FxfPL5zGA1BnYWeDCjV1MeiHg8=; b=Ny60nF4VHb0H465ypAEVThWXtT/uaIzJEV+PF3nGoypmcnspnRinqgoOopXQensfQZ 0xOxSkThxptU03TfaRuXCzFP3rfhw85mG84Dzb+Eeb9S2a2w6G/m5JVGnvfyCNXGtToy Rbp4t/ahsyCXVIBn3hGu+GQgzzzC3ShRBaXVTXbAtXn7rMDGmFWknlfPxCYPD17clzvb Hwjw0a+3uTUf06eJF5LIIhFmp/vX9/lUfDLHXvbRY11kUvzIu7jejqn54ccTBmESWMDC KqTflrbiuM+cpqqmwrP3Agcr8KdhaRVMNnWHP9GmOBb/BH1ngQqQ72mAx9AZOKa45Hon O68Q==
Received: by 10.14.119.140 with SMTP id n12mr7656747eeh.30.1338445902476; Wed, 30 May 2012 23:31:42 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id h53sm3304155eea.1.2012.05.30.23.31.40 (version=SSLv3 cipher=OTHER); Wed, 30 May 2012 23:31:41 -0700 (PDT)
Message-ID: <4FC71041.3040609@gmail.com>
Date: Thu, 31 May 2012 07:31:29 +0100
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: Eliot Lear <lear@cisco.com>
Subject: Mission statement [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com>
In-Reply-To: <4FC70E09.30002@cisco.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: Thu, 31 May 2012 06:31:44 -0000

On 2012-05-31 07:22, Eliot Lear wrote:

...
>   * I've been told by some that the Mission of the IETF is in some way
>     out of date.  I don't know whether this is true, 

That sound like somebody's personal opinion, but it is still a BCP
and therefore still represents IETF consensus.

>     but if it is, the
>     reference should be removed.

I don't think so.

   Brian

From brian.e.carpenter@gmail.com  Wed May 30 23:36:52 2012
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 1AF4511E80AF for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.682
X-Spam-Level: 
X-Spam-Status: No, score=-101.682 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 YCNjekruUJpW for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:36:51 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6795311E8093 for <ietf@ietf.org>; Wed, 30 May 2012 23:36:51 -0700 (PDT)
Received: by eekd4 with SMTP id d4so180947eek.31 for <ietf@ietf.org>; Wed, 30 May 2012 23:36:49 -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=d3aQ7XohdMDSLyzztv1xJS4mGdJsZMayBG66cor1oac=; b=hIam5MZI57P9uknHqhwxgncf6U+eQpjTSekN7q8Mb0+QZuJz3QW4ibUad3mfViO0gG 6x+0myxadyt/ffVA9tZxpaHWtoUOfEXwDIdnswIMf4okyPBE8zYqmqZdmscOZ/CWPmO/ lvkquAvqz5fkuMnca/8ZKK6MxErnuw/CJ3RdESy9srToDlenJXWUXYtCttAm51vnrfsD iU+PVfsW9+QD34dCEMmxZ5G1hx1P8vp/4oqpv0w84AQgF1JDk8ZU11pSbDjiAT0DrYaK bNo4z0roQu5djUKcaw5HevOiKXWoGosVbIe9T0KvNpDQmu1k8Dw5W52JuwQu5FzozpgD j4/A==
Received: by 10.14.127.16 with SMTP id c16mr8300162eei.182.1338446209197; Wed, 30 May 2012 23:36:49 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id o16sm6669256eeb.13.2012.05.30.23.36.47 (version=SSLv3 cipher=OTHER); Wed, 30 May 2012 23:36:48 -0700 (PDT)
Message-ID: <4FC71178.2050401@gmail.com>
Date: Thu, 31 May 2012 07:36:40 +0100
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: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im>
In-Reply-To: <4FC6CE2F.70903@stpeter.im>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 06:36:52 -0000

On 2012-05-31 02:49, Peter Saint-Andre wrote:
> Overall I continue to think that this is a helpful document, as were its
> predecessors.
> 
> That said, I would assume that many potential readers of this document
> are not native English speakers. Thus I suggest that the more colloquial
> words and phrases might best be changed to more standard English.

Have we any evidence that this is a problem for the community? The informal
style is one of the virtues of the Tao. I'd be sorry to lose it.

Maybe we can ask some of the people concerned, such as recent presenters
of the Newcomers tutorial in languages other than English.

    Brian

From dhc@dcrocker.net  Wed May 30 23:59:10 2012
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 C21D711E80E5 for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u5IRzGIrY29b for <ietf@ietfa.amsl.com>; Wed, 30 May 2012 23:59:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 267B111E8093 for <ietf@ietf.org>; Wed, 30 May 2012 23:59:10 -0700 (PDT)
Received: from [192.168.2.101] (f052240238.adsl.alicedsl.de [78.52.240.238]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4V6x5Ii025053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 May 2012 23:59:06 -0700
Message-ID: <4FC716B8.2090208@dcrocker.net>
Date: Thu, 31 May 2012 08:59:04 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com>
In-Reply-To: <4FC71178.2050401@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.17]); Wed, 30 May 2012 23:59:08 -0700 (PDT)
Cc: ietf@ietf.org, Paul Hoffman <paul.hoffman@vpnc.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 May 2012 06:59:10 -0000

On 5/31/2012 8:36 AM, Brian E Carpenter wrote:
> Have we any evidence that this is a problem for the community? The informal
> style is one of the virtues of the Tao. I'd be sorry to lose it.


Let's separate use of colloquial language from overall writing style. 
It is possible to write in an informal style without using 
colloquialisms.  I could, for example, insert some side comment here 
that would be informal and lack colloquialisms.  By some measures, the 
preceding sentence is an example of exactly that...

Colloquialisms are well known to impede understanding by non-native 
English speakers.

So, do you have any evidence that this is /not/ a problem for that part 
of our community?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From brian.e.carpenter@gmail.com  Thu May 31 00:23:14 2012
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 D995F11E809A for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.682
X-Spam-Level: 
X-Spam-Status: No, score=-101.682 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 QznWjDHQmUHQ for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:23:13 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC5211E8074 for <ietf@ietf.org>; Thu, 31 May 2012 00:23:13 -0700 (PDT)
Received: by eekd4 with SMTP id d4so197198eek.31 for <ietf@ietf.org>; Thu, 31 May 2012 00:23:12 -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=GLRb94gKRnUe9JKl3lwzMRenzk0e1NI3wl2MIWogArg=; b=Qx1Zvc0fuIOK6ugfaH1TIKk1UBkFDk8RfX83A3eL8YAVQy2g98Kd7aLyFrl3hZbLbV IsjSJ2c3yVSIefaqyoEl3Om0S2RsxuUo8n112wdsukbL3Y9AB1oTiQLeLaKTpCiO48ed xYID1dUd6U7BnmhT9z41ab1LpW1OZ8p6JtO7/oKUECnBsfOIGzJZ5suCHHwj7JXJYkcv IuQAwpAlP3P1v/9Q2TXvJY59TmBl6TaL0QaXoEPPfhO0lCUZsDVtfurINTiyRWrayPUW NjScijEaWGidJyEPRYrXjj/xBGrfIQ8fTrBLBdXGdmFIMViJpKS1JOooGiXhj9fumRh0 SwMw==
Received: by 10.14.127.136 with SMTP id d8mr7765453eei.159.1338448992550; Thu, 31 May 2012 00:23:12 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id z5sm7139806eem.3.2012.05.31.00.23.10 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 00:23:11 -0700 (PDT)
Message-ID: <4FC71C58.2030106@gmail.com>
Date: Thu, 31 May 2012 08:23:04 +0100
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: ICANN relationship [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
In-Reply-To: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 07:23:15 -0000

> 3.2.4.  IANA (Internet Assigned Numbers Authority)
> 
>    The core registrar for the IETF's activities is the IANA (see
>    http://www.iana.org).  Many Internet protocols require that someone
>    keep track of protocol items that were added after the protocol came
>    out.  Typical examples of the kinds of registries needed are for TCP
>    port numbers and MIME types.  The IAB has designated the IANA
>    organization to perform these tasks, and the IANA's activities are
>    financially supported by ICANN, the Internet Corporation for Assigned
>    Names and Numbers.  The IAB selected ICANN, and the IANA activities
>    are provided for free as specified in [RFC2860].

The phrase "The IAB selected ICANN" is, as the saying goes, economical with
the truth. The fact is that we had no choice at the time. Suggestion
for the last sentence:

  The IAB and the IETF established a Memorandum of Understanding with
  ICANN [RFC2860], under which the IANA services are provided for free
  to the IETF.

Nit:

> Editor is a separate job. Today, these jobs are preformed by

s/preformed/performed/



Regards
   Brian Carpenter

From brian.e.carpenter@gmail.com  Thu May 31 00:25:06 2012
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 BD69421F8656 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.683
X-Spam-Level: 
X-Spam-Status: No, score=-101.683 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 HnFd2ptbQ7MS for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:25:06 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id F047321F8655 for <ietf@ietf.org>; Thu, 31 May 2012 00:25:05 -0700 (PDT)
Received: by eaaq13 with SMTP id q13so191820eaa.31 for <ietf@ietf.org>; Thu, 31 May 2012 00:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=eHPiVLefSQe+cCPko7142q7XbRmtrGMCfPc8udQAUaU=; b=VAybxQC7Nu4+NIyMEW4ZlD4kBP6bP7G0De8HF0LXYUlpnrdg501gKk7U4eDilFHgZa Si2wIeU6jkhF+HACeQWYgq0Cv1m9KWJrr8OD68cElCzNtvjrwxSv1r4eINm4iVgLAIgG CfhZCFRfEZ+a/7Kfgxn3ZTvyUDFJz6m2dVfvJI+/yGL8LGss/hu62pTJKtPaffXzxriH T4C3cgOQ0/nhs2W6T4pQ8vvFoDU6XV5bNSt+iKGJPg33tO3L+8wLnrAp+b4eR5h5s0YR KeiBtaSm0miuydYCYoP/qOB0lJM2aUQ5LmhBdSon0ylxxASBszfBPChjD22zKDNR/BjI KxhQ==
Received: by 10.14.119.12 with SMTP id m12mr6830628eeh.17.1338449105078; Thu, 31 May 2012 00:25:05 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id s47sm7149905eef.4.2012.05.31.00.25.03 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 00:25:04 -0700 (PDT)
Message-ID: <4FC71CC9.2000604@gmail.com>
Date: Thu, 31 May 2012 08:24:57 +0100
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: dcrocker@bbiw.net
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <4FC716B8.2090208@dcrocker.net>
In-Reply-To: <4FC716B8.2090208@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 07:25:06 -0000

On 2012-05-31 07:59, Dave Crocker wrote:
> 
> On 5/31/2012 8:36 AM, Brian E Carpenter wrote:
>> Have we any evidence that this is a problem for the community? The
>> informal
>> style is one of the virtues of the Tao. I'd be sorry to lose it.
> 
> 
> Let's separate use of colloquial language from overall writing style. It
> is possible to write in an informal style without using colloquialisms. 
> I could, for example, insert some side comment here that would be
> informal and lack colloquialisms.  By some measures, the preceding
> sentence is an example of exactly that...
> 
> Colloquialisms are well known to impede understanding by non-native
> English speakers.
> 
> So, do you have any evidence that this is /not/ a problem for that part
> of our community?

I actually have no evidence either way; that's why I suggested asking
some of them ;-)

   Brian

From dcrocker@bbiw.net  Thu May 31 00:47:37 2012
Return-Path: <dcrocker@bbiw.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 2AF3221F8633 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:47: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 1Milf9JKfLDx for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 00:47:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 695C021F8630 for <ietf@ietf.org>; Thu, 31 May 2012 00:47:35 -0700 (PDT)
Received: from [192.168.2.101] (f052240238.adsl.alicedsl.de [78.52.240.238]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4V7lWEW025789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2012 00:47:34 -0700
Message-ID: <4FC72213.8060800@bbiw.net>
Date: Thu, 31 May 2012 09:47:31 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com>
In-Reply-To: <4FC71CC9.2000604@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.17]); Thu, 31 May 2012 00:47:34 -0700 (PDT)
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 May 2012 07:47:37 -0000

On 5/31/2012 9:24 AM, Brian E Carpenter wrote:
> I actually have no evidence either way; that's why I suggested asking
> some of them;-)

1.  Reliance on self-reporting for such things is methodologically 
problematic.  It presumes a degree of self-awareness that is often 
missing.  For example a native speaker of a language that uses noun 
doubling -- saying the noun twice -- to indicate plurals was quite 
insistent with me that that wasn't the rule.

2.  To claim a lack of evidence presumes some previous effort to acquire 
it.  However a quick search discloses:

 
http://journals.cambridge.org/action/displayAbstract;jsessionid=054711CCAB4AFB348F7E70C9079E7305.journals?fromPage=online&aid=2546012

 
http://dc.library.okstate.edu/cdm/singleitem/collection/theses/id/1031/rec/9

 
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CF0QFjAC&url=http%3A%2F%2Fscholarcommons.usf.edu%2Fcgi%2Fviewcontent.cgi%3Farticle%3D1255%26context%3Detd&ei=iyDHT4eBB874sgaa-rGQDw&usg=AFQjCNFnYm2MzlDnknB6AzfB0Oi4tUVyVg

among others.

The mere existence of these ought to make clear that there is a 
significant issue in the use of colloquialisms with non-native listeners.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ole@cisco.com  Thu May 31 01:14:06 2012
Return-Path: <ole@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 9638E21F866C for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:14:05 -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 T5m2HGmySM1Q for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:14:03 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1161A21F8667 for <ietf@ietf.org>; Thu, 31 May 2012 01:14:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1577; q=dns/txt; s=iport; t=1338452043; x=1339661643; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=v7LoFafYEAECgl95KTPcKvRiQQh8G6heZeHfrHoL/XU=; b=RC+5LBFwSiNW/JPRYwSBodG7ffS7WpvkFQcP0qAactBk+3GDk9mi5yMu J5+x0k1GfxGgJTOFWcx1rzfg5rk6xyV05bLFuLCK6S6RB4CzX3Pbmrb8t FLohgjCr1hWuqcayhruaf8vSa2MzXv/On9moHg59y8ztO8WpxKuE1d10t Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAE4nx0+rRDoI/2dsb2JhbABBA7QUgQeCFwEBAQMBEgECJT8FCwsYIwtXBhMUAQ2HZASZF4NHEJwgiBiCcBqCEYMbA4hAl1ODEoEEYoMAgT8
X-IronPort-AV: E=Sophos;i="4.75,690,1330905600"; d="scan'208";a="44511749"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 31 May 2012 08:14:02 +0000
Received: from sjc-vpn7-992.cisco.com (sjc-vpn7-992.cisco.com [10.21.147.224]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q4V8E2tB017696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Thu, 31 May 2012 08:14:02 GMT
Date: Thu, 31 May 2012 01:16:52 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <4FC71178.2050401@gmail.com>
Message-ID: <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@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: Thu, 31 May 2012 08:14:06 -0000

On Thu, 31 May 2012, Brian E Carpenter wrote:

> On 2012-05-31 02:49, Peter Saint-Andre wrote:
> > 
> > That said, I would assume that many potential readers of this document
> > are not native English speakers. Thus I suggest that the more colloquial
> > words and phrases might best be changed to more standard English.
> 
> Have we any evidence that this is a problem for the community? The informal
> style is one of the virtues of the Tao. I'd be sorry to lose it.

"Informal style" does not equal heavy use of (localized) 
colloquialisms. My copy editor always reminds me that I have an 
international readership and thus should avoid such phrases as the 
ones listed by Peter.

> 
> Maybe we can ask some of the people concerned, such as recent presenters
> of the Newcomers tutorial in languages other than English.

Sounds like a difficult thing to do with any kind of predictable or 
measurable outcome, although it might be fun to ask the Brits if they
understand everything the Americans are saying and vice versa :-)

"Having evindence" that someone did not understand a particular phrase
gets into the weeds of cultural differences which go way beyond a 
group of engineers who don't understand the meaning of "approximately".
I suggest we NOT conduct that particular line of questioning, really.

> 
>     Brian
> 


Ole J. Jacobsen 
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From ynir@checkpoint.com  Thu May 31 01:25:02 2012
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 A9B4021F855B for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 x8pKWyH-3zd4 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:25:01 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 563EA21F8559 for <ietf@ietf.org>; Thu, 31 May 2012 01:25:00 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (dlpgw.checkpoint.com [194.29.34.27]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4V8OswO011634; Thu, 31 May 2012 11:24:54 +0300
X-CheckPoint: {4FC7371D-9-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 31 May 2012 11:24:51 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 31 May 2012 11:24:50 +0300
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Topic: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Thread-Index: Ac0/BtjYIKyIUgttSlCp9VbZsGpK0Q==
Message-ID: <F0FDD3C5-3AC4-42AC-9356-02CE5F8C8DAE@checkpoint.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im>
In-Reply-To: <4FC6CE2F.70903@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 112246da057a5bf88dc0ba08be455e930b23b69158
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 08:25:02 -0000

Hi Peter

I tend to disagree. I am not a native English speaker, although I will admi=
t to watching way too much American TV in my teens.=20

I believe most of these should be recognizable to anyone who has learned en=
ough English to participate meaningfully in IETF mailing lists and discussi=
ons. What you haven't seen before, you can usually either deduce ("cosmic s=
ignificance" would obviously mean a lot of significance), or else easily se=
archable on the net or in idiom books, although I did get some incorrect re=
sults searching google for "warm fuzzy feeling".

Yes, we should keep both messages and documents straight-forward, and avoid=
 cultural references and memes (like "home base" or "I do have a Dalek but =
I do not yet have a Tardis", or any reference to taking arrows to the knee)=
, but I don't think it's necessary to go back and prune all idioms out of a=
 document.

Yoav

On May 31, 2012, at 4:49 AM, Peter Saint-Andre wrote:

> Overall I continue to think that this is a helpful document, as were its
> predecessors.
>=20
> That said, I would assume that many potential readers of this document
> are not native English speakers. Thus I suggest that the more colloquial
> words and phrases might best be changed to more standard English.
> Naturally one can quibble about particulars, but here are some examples
> as I see them:
>=20
> "get into the swing of things"
> "give them a warm, fuzzy feeling"
> "happenings"
> "unsung heroes"
> "home base"
> "pet project"
> "pet peeve"
> "leaps and bounds"
> "get technical"
> "discussions of cosmic significance"
> "gatherings of the tribes"
> "kicks in"
> "breath of fresh air"
> "big-name"
> "take the pluge"
>=20
> I realize that such words and phrases lend a friendly tone to the
> document, but IMHO that friendliness will be lost on non-native speakers.


From dhc@dcrocker.net  Thu May 31 01:32:54 2012
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 4CF6221F8697 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.995
X-Spam-Level: 
X-Spam-Status: No, score=-5.995 tagged_above=-999 required=5 tests=[AWL=0.603,  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 76Nz2ncQRqry for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:32:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D02B121F866C for <ietf@ietf.org>; Thu, 31 May 2012 01:32:50 -0700 (PDT)
Received: from [192.168.2.101] (f052240238.adsl.alicedsl.de [78.52.240.238]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q4V8WkwO026387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2012 01:32:48 -0700
Message-ID: <4FC72CAD.1030604@dcrocker.net>
Date: Thu, 31 May 2012 10:32:45 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com>
In-Reply-To: <4FC70E09.30002@cisco.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.17]); Thu, 31 May 2012 01:32:49 -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, 31 May 2012 08:32:54 -0000

On 5/31/2012 8:22 AM, Eliot Lear wrote:
> The Tao mentions that we meet once a year in each region.  I don't think
> that's true for Asia at this point.  The text might call out that we
> meet where there are participants, or words that the IAOC might provide.


The relatively recent change in policy is to average one meeting in each 
region every year.  The current departure from that policy is due to 
logistics and cost issues, not a change in policy.

Hence, possible language could be:

    The IETF policy is to meeting in each region once a year, as possible.

Or the like.

d/

ps.  this note is a personal offering, not an IAOC one.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Thu May 31 01:43:27 2012
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 9166421F86B3 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.299
X-Spam-Level: 
X-Spam-Status: No, score=-101.299 tagged_above=-999 required=5 tests=[AWL=-1.300, 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 w9c8ZwJZVM5L for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:43: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 50C4221F869D for <ietf@ietf.org>; Thu, 31 May 2012 01:43:26 -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 q4V8hK7s003720 for <ietf@ietf.org>; Thu, 31 May 2012 01:43:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338453805; i=@resistor.net; bh=YpjoJKDTNv09LV+NU4iW1C4BwnkElu0mokRhTnzT1Rg=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=2TeIOTkcMGaxQqueszXC8TsXhHSKD2HNOY/jG+kIOpP0VxUq2NPYaIA2DBJg+JqGp cFUTLEEd6PtVJpw5w0ukx2TLvs7WDUIBKi3KxN3yez6E9lNGvBKTc/6Vfh3NwiPjV2 0g0eegboee21LXRbb9ea8rgegTj6AzqE41d9jXhI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338453805; i=@resistor.net; bh=YpjoJKDTNv09LV+NU4iW1C4BwnkElu0mokRhTnzT1Rg=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=1Ovd14DF+LOavIxLZfwr/Efxw3gCNmwTixhsrweTdpUEBzP8Mss1CMbR4w4zfoyur ir2QjYp3TEjU/W+hE0lbOJtJ6xlo4iXhwvFFg1Gzvx6oEBgImDght6/xnX6qxyczMN oPbsB23Mfu0LhSYacNN4jn4VnWDT6C+ltD64Cpvc=
Message-Id: <6.2.5.6.2.20120530214914.094ac8d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 May 2012 01:24:40 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
In-Reply-To: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
References: <20120530225655.19475.74871.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: Thu, 31 May 2012 08:43:27 -0000

At 15:56 30-05-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'The Tao of IETF: A Novice's Guide to the Internet Engineering Task
>    Force'
>   <draft-hoffman-tao4677bis-15.txt> as Informational RFC

In the Introduction Section:

   "This will give them a warm, fuzzy feeling and enable them to
    make the meeting and the Working Group discussions more
    productive for everyone."

Reading 51 pages may give people who are a bit stale a warm, fuzzy 
feeling.  I don't think that is what newcomers seek.  Reading this 
draft does not make the meeting or Working Group discussions more 
productive except for people who have been around before November, 2008.

Section 3.2.1 mentions "ISOC (Internet Society)".  Didn't ISOC 
rebrand itself to "Internet Society"?

   "The ISOC is one of the major unsung heroes of the Internet."

This sounds like a line from the marketing department.

According to www.ietf.org, the "Internet Engineering Task Force 
(IETF) is an organized activity of the Internet Society 
(ISOC)".   This draft places ISOC at the top of the hierarchy.  Does 
that mean that ISOC runs the IETF?

In Section 3.2.2:

   "It administers the process according to the rules and procedures
    that have been ratified by the ISOC Board of Trustees."

Isn't the process (and rules) documented through BCPs?  Are the BCPs 
ratified by the ISOC Board of Trustees?

   "Because of this, one of the main reasons that the IESG might block
    something that was produced in a WG is that the result did not really
    gain consensus in the IETF as a whole, that is, among all of the
    Working Groups in all Areas."

The above does not seem correct to me.  All working groups do not 
participate through this mailing list.  This list is more of a venue 
for the IETF as a whole, i.e. its participants and not its Working 
Groups, to provide substantive comments about a draft during a Last 
Call.  These substantive comments tends to include "+1" as it is 
viewed as a way for some participants to make their vote heard.  The 
origins of the "+1" can be traced back to another community, which is 
unrelated to the IETF, where contributors actually vote.

In Section 3.2.3:

   "Approves the appointment of the IANA"

Isn't IANA more of a U.S. Government decision?

In Section 3.2.5:


   "Once an RFC is published, it is never revised."

That can be debatable [1].

In Section 3.2.7:

   "Few IETF participants come into contact with the IETF Trust,
    which is a good sign that they are quietly doing their job."

This sounds more like marketing.

In Section 3.3:

   'People who would like to "get technical" may also join the IETF
    general discussion list'

People who would like to get a vague idea of IETF politics may also 
join the IETF general discussion lists.  Some of the topics discussed 
on that mailing list are:

  - What is a "MUST"

  - Future Handling of the Blue Sheets

  - IETF aging

  - Proposed IESG Statements (not even mentioned in the draft)

  - Is IPv6 bad news

  - Why is DNS broken

  - A proxy war between the IETF and the ITU

  - Shared IPv4 address space

I wouldn't describe the above-mentioned topics as being of cosmic significance.

In Section 4:

  "primary goal is to reinvigorate the WGs to get their tasks done"

After watching two people taking shots at low flying ducks, my guess 
is that such action does have an invigorating effect.  Those ducks 
must have read the current version of the Tao to learn the inner 
workings.  There were a couple of unfortunate accidents [1].

   "although IASA kicks in additional funds for things such as the audio
    broadcast of some Working Group sessions.

This is an unnecessary detail.  How important is it to know that some 
body within the IETF called IASA is paying for that?

   "There is no exposition hall"

Isn't there a plan to have an exposition during meetings?

In Section 4.5:

   "These are used for long-term archival purpose to show how many
    people came to a particular meeting and, in rare cases, exactly
    who showed up."

What's the consensus on "Blue Sheets" these days?

In Section 5.2:

   "Any decision made at a face-to-face meeting must also gain
   consensus on the WG mailing list."

Are decisions taken during meetings or only on the mailing list?

   "There are numerous examples of important decisions made in
    WG meetings that are later overturned on the mailing list,
    often because someone who couldn't attend the meeting pointed
    out a serious flaw in the logic used to come to the decision."

The above does not seem correct.

In Section 7.3:

  '[RFC2223], "Instructions to RFC Authors", describes the submission format.'

Isn't RFC 2223 considered as Historic?  I doubt that the RFC editor 
uses that RFC.

In Section 7.4:

   "To become an Internet Standard, an RFC must have multiple
    interoperable implementations and the unused features in the
    Proposed Standard must be removed; there are additional
    requirements listed in [BCP9]."

Is this correct?  Unused features (the MAY) are not removed in practice.

In B.1:

   "P4.  Participation in the IETF or of its WGs is not fee-based or
         organizationally defined, but is based upon self-identification
         and active participation by individuals."

What is the meaning of self-identification?

In B.2:

   "P7.   Dissent, complaint, and appeal are a consequence of the IETF's
          nature and should be regarded as normal events, but ultimately
          it is a fact of life that certain decisions cannot be
          effectively appealed."

Is this a roundabout way of saying that a person can appeal but it 
won't change anything?

   "P10.  A community process is used to select the leadership."

It's not a community process in my opinion (see NomCom selection process).

   "P11.  Leaders are empowered to make the judgment that rough consensus
          has been demonstrated.  Without formal membership, there are no
          formal rules for consensus."

This is like using the draft as a backdoor to say something.  It 
looks like accountability is being glossed over.  I suggest renaming 
B.2 as Animal Farm [1].

In B.3:

   "P14.  Parts of the process that have proved impractical should be
          removed or made optional."

Why is the above in this draft?

In B.5:

   "P30.  Standards Track and Best Current Practice documents must be
          subject to IETF wide rough consensus (Last Call process)."

Is it "rough consensus" or "consensus"?

Some parts of this draft are well-written.  Other parts comes out as 
nostalgia instead of providing a view of the inner workings of the 
IETF.  Overall this draft could be more effective in helping 
newcomers if it was reorganized and if it used a language which is 
more accessible to non-English speakers [2].  There is truth in 
advertising and what the IETF would like people to believe.  If the 
objective is the later, it has been met.  There is a long coverage of 
the meeting details.  That can be traced back to a RFC written in 
1993.  In the old days meetings could have been considered as "the 
IETF".  I would describe meetings more as a landmark nowadays than 
being "the IETF".

I don't think I know what "the IETF" is.  Some of the people on this 
mailing list have been active in the IETF for the last 19 years and 
they may have a better idea of what the IETF universe must be.  If 
this is their idea of a better idea, I'll say "ok".  There is a world 
out there.  That world has a different view of the IETF.  After 
reading this draft that world will still have a disconnected view of 
the IETF.  It could be said that "that world" is not important, that 
newcomers are not important, that those who have built the Internet 
know better.

I am going to file the minority report on this draft before the one 
[1] that sometimes does that.  BTW, I don't see the "please be 
patient with the old folks" advice in this draft.  Is it politically 
incorrect to say that?

Regards,
-sm

1. Insert smiley
2. http://www.youtube.com/watch?v=FL7iS4aZHas 


From stephen.farrell@cs.tcd.ie  Thu May 31 01:59:07 2012
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 9A53521F8671 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.011
X-Spam-Level: 
X-Spam-Status: No, score=-103.011 tagged_above=-999 required=5 tests=[AWL=-0.412, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1YuUzFXl16y for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 01:59:06 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 18D2321F866D for <ietf@ietf.org>; Thu, 31 May 2012 01:59:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id E268C1535F7; Thu, 31 May 2012 09:59:01 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1338454741; bh=Nn8WCRrojrD00T 8e30PP9t+9HI63hsilcLZm9VIGIfc=; b=isoD7fITW1oeId48QkxviwEVb2b/OB WwzDM5fektdN67diynFzNAHnl2tMmSVMtCbSAj/m/Y8iMvQ3+5m5AemGoqFIh+6z j2bP8VQGdjL9o62yTBxAg/R8Qm/2yWQIWmWvbkwWtD2PQeMKjDyuobJqrVsPaWBE /mEtV3xLKhIkyZKW2rQos8zYjSAyJaOTw2seEgP+wnenwphbBzbLKblRCs/QPl1i W62xSR8HoN35vy3BaAzTN1HWM75Uj45Z1+Yb1eRTHbJV1qcxQ1M93pI3sYQVt36i vcVbqKwRIqVhm4360ptgVdURN128pmdsbXAAztRoQK1NKIeDRrs5tk/A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id AL-9gIfK5iU0; Thu, 31 May 2012 09:59:01 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.42.25.154]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 68274153577; Thu, 31 May 2012 09:58:59 +0100 (IST)
Message-ID: <4FC732D3.7090904@cs.tcd.ie>
Date: Thu, 31 May 2012 09:58:59 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com> <4FC72213.8060800@bbiw.net>
In-Reply-To: <4FC72213.8060800@bbiw.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 08:59:07 -0000

I'm with Brian and Yoav on this. I don't see a need
to change here. And I do think we might lose something
if we become too PC. If a bunch of non-native speakers
did say "yes, I found that made the document less
useful" then I'd be more convinced that all these
changes were worth it.

On 05/31/2012 08:47 AM, Dave Crocker wrote:
> 
> On 5/31/2012 9:24 AM, Brian E Carpenter wrote:
>> I actually have no evidence either way; that's why I suggested asking
>> some of them;-)
> 
> 1.  Reliance on self-reporting for such things is methodologically
> problematic.  It presumes a degree of self-awareness that is often
> missing.  For example a native speaker of a language that uses noun
> doubling -- saying the noun twice -- to indicate plurals was quite
> insistent with me that that wasn't the rule.
> 
> 2.  To claim a lack of evidence presumes some previous effort to acquire
> it.  However a quick search discloses:
> 
> 
> http://journals.cambridge.org/action/displayAbstract;jsessionid=054711CCAB4AFB348F7E70C9079E7305.journals?fromPage=online&aid=2546012

Paywalled. Abstract says "comprehen-sibility of the non-native's
interlanguage" so is a worse sinner IMO:-)

> http://dc.library.okstate.edu/cdm/singleitem/collection/theses/id/1031/rec/9

Drives NoScript bonkers and needs some kind of FF plug in.

> http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CF0QFjAC&url=http%3A%2F%2Fscholarcommons.usf.edu%2Fcgi%2Fviewcontent.cgi%3Farticle%3D1255%26context%3Detd&ei=iyDHT4eBB874sgaa-rGQDw&usg=AFQjCNFnYm2MzlDnknB6AzfB0Oi4tUVyVg

289 pages, so only read abstract.

That's about adolescents. My experience at IETF meetings is
that more native English speakers seem to behave like
adolescents, but maybe that's just me:-)

It does make the point that there's a (presumably positive)
correlation between understanding of idiom and academic
achievement,

I guess the argument could also be made that the Tao should
be about as difficult to read as a typical IETF mailing list.

S.

> 
> among others.
> 
> The mere existence of these ought to make clear that there is a
> significant issue in the use of colloquialisms with non-native listeners.
> 
> d/

From klaas@cisco.com  Thu May 31 02:05:38 2012
Return-Path: <klaas@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 E31B921F8671 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 02:05:37 -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 AqabkiZIU+bR for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 02:05:36 -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 D441421F866D for <ietf@ietf.org>; Thu, 31 May 2012 02:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=klaas@cisco.com; l=2696; q=dns/txt; s=iport; t=1338455136; x=1339664736; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=QieCfeIohsw4JC+PDesSkdEtByzQiNud/WZuy1QxxOU=; b=Lr8tVA4HVvATWgnTcsIOdn1Wq9E0asuFYw5HxvOpjh+FYEaoQ/PAGYsY Qijg36tHaaiZ+k1FwGtZstmWRhDUxBw6TAZyfjX7zx9iezlR82lzhcbtR 63nWtILPnDcgPoKK6o7zE9UhJuEwSs4FsNZRq1eyLSWR6+CuC2aMAyKp5 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAN8zx0+Q/khR/2dsb2JhbABEtBWBB4IXAQEBAwESASU2GwsYCRoLDwJGEwgBAR6HZAULmQCfeogYgnCCMIMWA5UYgQ+MfoFmgmI
X-IronPort-AV: E=Sophos;i="4.75,690,1330905600"; d="scan'208";a="138873624"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 31 May 2012 09:05:34 +0000
Received: from dhcp-ams5-vlan252-wdata-144-254-205-139.cisco.com (dhcp-ams5-vlan252-wdata-144-254-205-139.cisco.com [144.254.205.139]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q4V95Yxa031164 for <ietf@ietf.org>; Thu, 31 May 2012 09:05:34 GMT
Message-ID: <4FC7345E.807@cisco.com>
Date: Thu, 31 May 2012 11:05:34 +0200
From: Klaas Wierenga <klaas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Colloquial language [Re: Last Call:	<draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com>	<4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com>	<4FC72213.8060800@bbiw.net> <4FC732D3.7090904@cs.tcd.ie>
In-Reply-To: <4FC732D3.7090904@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 09:05:38 -0000

On 5/31/12 10:58 AM, Stephen Farrell wrote:
>
> I'm with Brian and Yoav on this. I don't see a need
> to change here. And I do think we might lose something
> if we become too PC. If a bunch of non-native speakers
> did say "yes, I found that made the document less
> useful" then I'd be more convinced that all these
> changes were worth it.

As a non-native speaker I agree. I think colloquial is fine. The one 
thing causes me some trouble is all the references that Americans make 
to sports that nobody in the civilized world cares about ;-) ("left 
field", "Hail Mary passes" etc.) But I think the Tao pretty much avoids 
those (perhaps "Home base" is the exception).

Klaas


>
> On 05/31/2012 08:47 AM, Dave Crocker wrote:
>>
>> On 5/31/2012 9:24 AM, Brian E Carpenter wrote:
>>> I actually have no evidence either way; that's why I suggested asking
>>> some of them;-)
>>
>> 1.  Reliance on self-reporting for such things is methodologically
>> problematic.  It presumes a degree of self-awareness that is often
>> missing.  For example a native speaker of a language that uses noun
>> doubling -- saying the noun twice -- to indicate plurals was quite
>> insistent with me that that wasn't the rule.
>>
>> 2.  To claim a lack of evidence presumes some previous effort to acquire
>> it.  However a quick search discloses:
>>
>>
>> http://journals.cambridge.org/action/displayAbstract;jsessionid=054711CCAB4AFB348F7E70C9079E7305.journals?fromPage=online&aid=2546012
>
> Paywalled. Abstract says "comprehen-sibility of the non-native's
> interlanguage" so is a worse sinner IMO:-)
>
>> http://dc.library.okstate.edu/cdm/singleitem/collection/theses/id/1031/rec/9
>
> Drives NoScript bonkers and needs some kind of FF plug in.
>
>> http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CF0QFjAC&url=http%3A%2F%2Fscholarcommons.usf.edu%2Fcgi%2Fviewcontent.cgi%3Farticle%3D1255%26context%3Detd&ei=iyDHT4eBB874sgaa-rGQDw&usg=AFQjCNFnYm2MzlDnknB6AzfB0Oi4tUVyVg
>
> 289 pages, so only read abstract.
>
> That's about adolescents. My experience at IETF meetings is
> that more native English speakers seem to behave like
> adolescents, but maybe that's just me:-)
>
> It does make the point that there's a (presumably positive)
> correlation between understanding of idiom and academic
> achievement,
>
> I guess the argument could also be made that the Tao should
> be about as difficult to read as a typical IETF mailing list.
>
> S.
>
>>
>> among others.
>>
>> The mere existence of these ought to make clear that there is a
>> significant issue in the use of colloquialisms with non-native listeners.
>>
>> d/


From simon.perreault@viagenie.ca  Thu May 31 05:33:30 2012
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 CD05921F868A for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 05:33:30 -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 eXkn7Khu2i4S for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 05:33:30 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id EA10F21F8672 for <ietf@ietf.org>; Thu, 31 May 2012 05:33:29 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:515a:b1c9:5e03:79b7]) by jazz.viagenie.ca (Postfix) with ESMTPSA id F34FC41306 for <ietf@ietf.org>; Thu, 31 May 2012 08:33:28 -0400 (EDT)
Message-ID: <4FC76518.3060508@viagenie.ca>
Date: Thu, 31 May 2012 08:33:28 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com> <4FC72213.8060800@bbiw.net> <4FC732D3.7090904@cs.tcd.ie>
In-Reply-To: <4FC732D3.7090904@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 12:33:31 -0000

On 2012-05-31 04:58, Stephen Farrell wrote:
> I'm with Brian and Yoav on this. I don't see a need
> to change here. And I do think we might lose something
> if we become too PC. If a bunch of non-native speakers
> did say "yes, I found that made the document less
> useful" then I'd be more convinced that all these
> changes were worth it.

Another non-native English speaker here. Didn't have any problem 
understanding the Tao. Its level of language made me more interested in 
the IETF. Although my level of English is better than other non-native 
speakers'. Non-native != bad at English.

I think colloquialisms may often be as hard to understand as excellent 
but seldom-used vocabulary. Should we also "dumb down" our level of 
language? Such as this:
http://simple.wikipedia.org/wiki/Simple_English_Wikipedia

I don't think so.

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From jnc@mercury.lcs.mit.edu  Thu May 31 06:46:19 2012
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 5909221F864B for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 06:46:19 -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 bfOHMBAzIBEg for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 06:46: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 CB63321F8644 for <ietf@ietf.org>; Thu, 31 May 2012 06:46:18 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CD2B018C0C7; Thu, 31 May 2012 09:46:17 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
Message-Id: <20120531134617.CD2B018C0C7@mercury.lcs.mit.edu>
Date: Thu, 31 May 2012 09:46:17 -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, 31 May 2012 13:46:19 -0000

    > From: Simon Perreault <simon.perreault@viagenie.ca>

    > I think colloquialisms may often be as hard to understand as excellent
    > but seldom-used vocabulary.

Indeed - and now that we have this really cool Internet thingy (it's odd to
think that young people have no memory of what the world was like before a
large fraction of its information was instantly at one's fingertips - and in
80 years or so, _nobody_ will remember that age personally), one can very
easily look up either a recondite word, or an obscure colloquialism, in
moments...

	Noel

From john-ietf@jck.com  Thu May 31 07:54:07 2012
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 D15C821F86DA for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 07:54:06 -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 20qQwAfrUxRa for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 07:54:05 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5D87921F8723 for <ietf@ietf.org>; Thu, 31 May 2012 07:54:00 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sa6fM-000I6Y-Ni; Thu, 31 May 2012 10:47:56 -0400
Date: Thu, 31 May 2012 10:53:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Eliot Lear <lear@cisco.com>
Subject: Re: Mission statement [Re: Last Call: <draft-hoffman-tao4677bis-15.txt>	(The Tao of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
Message-ID: <C5ABD549485AE1AF8F831363@PST.JCK.COM>
In-Reply-To: <4FC71041.3040609@gmail.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <4FC71041.3040609@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 14:54:07 -0000

--On Thursday, May 31, 2012 07:31 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 2012-05-31 07:22, Eliot Lear wrote:
> 
> ...
>>   * I've been told by some that the Mission of the IETF is in
>>   some way out of date.  I don't know whether this is true, 
> 
> That sound like somebody's personal opinion, but it is still a
> BCP and therefore still represents IETF consensus.

Brian,

Regardless of how I feel about this particular case, I don't
understand how to put your comment in context.  In particular,
would you 

* Assert that the IETF is so diligent about its process BCPs
that any that have become out of date, overtaken by events, or
otherwise irrelevant have been immediately and formally declared
obsolete or historic?  I have better ways to spend my time at
the moment, but I imagine that many members of the community
could come up with lists of counterexamples rather quickly
(perhaps starting from how long it took us to get "automatic
review" out of RFC 2026).

* When a document is revised ("updated" or "obsoleted") omitting
a reference that appeared in the earlier version requires a
special consensus call rather than treating consensus on the new
document, once achieved, as atomic?   Granted, the relatively
new provisions requiring identification and explanation of what
was obsoleted or updated are a step toward making sure that
those participating in the consensus process are aware of what
happened but (i) those provisions have, no far, not been
extended to require a discussion of every changed reference and
(ii) are not themselves in a BCP or other document that has been
documented as achieving community consensus on the details.
Independent of that BCP problem, would you advocate making each
new document list all of the references to BCP or Standards
Track documents that were not carried forward and identifying
the reasons?

     john


From scott.brim@gmail.com  Thu May 31 08:02:22 2012
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 CE77321F8710 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:02:22 -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 90WtbaQy7QPa for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:02:22 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 15E2B21F875D for <ietf@ietf.org>; Thu, 31 May 2012 08:02:22 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1406565dac.31 for <ietf@ietf.org>; Thu, 31 May 2012 08:02: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:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=sJRtqdE+0je79EpAfQTjG0R1ChGmJ8ESiSBSE51IJ7Q=; b=MkKRkwc+ypHMCL9NX2tI2WENEVtBZa3XX1AL5//FiSXBopJc7Qbs4UwEJbk0eYzFjT TTKF1fQkslIdgShLQ9kkbMgJWgGhkz+cOcw4kufeupPR/xRPbzkPrHDqaM6T49ovoLA9 QhFdf9zz4EekN5Ludh0FphYqZzFKFuUp6vPzuGJIxTnJVPkvakzYQiHn19G3apWKNO/S PV6gfygPiE0swpTY291SVKRtKae2C41Vs2ZaTRvNnqp4D+xhhg2vxyjTmzeUCzRnnYIw ZD6RMGqPNCusVbLqtaI1lLzQ71to3PuaTm2w2UgS+FMzQm5Ltnwaaf2w70tvS7COl3H5 iJkA==
Received: by 10.68.234.97 with SMTP id ud1mr381522pbc.152.1338476541839; Thu, 31 May 2012 08:02:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.220.132 with HTTP; Thu, 31 May 2012 08:02:01 -0700 (PDT)
In-Reply-To: <4FC71041.3040609@gmail.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <4FC71041.3040609@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 May 2012 11:02:01 -0400
Message-ID: <CAPv4CP_Yw4vc0VQ2PAMwN8o7S6fFWrgA7UWYtni63s4uCgYN8A@mail.gmail.com>
Subject: Re: Mission statement [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 31 May 2012 15:02:23 -0000

On Thu, May 31, 2012 at 2:31 AM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 2012-05-31 07:22, Eliot Lear wrote:
>
> ...
>> =A0 * I've been told by some that the Mission of the IETF is in some way
>> =A0 =A0 out of date. =A0I don't know whether this is true,
>
> That sound like somebody's personal opinion, but it is still a BCP
> and therefore still represents IETF consensus.
>
>> =A0 =A0 but if it is, the
>> =A0 =A0 reference should be removed.
>
> I don't think so.

I just want to support the sense of this message.  The mission
statement is one of the few things that anchors and orients the work
of the IETF -- and personally I like it.  If people think it's out of
date, let them say explicitly why (they can still do so anonymously)
so we can have a real discussion.  I don't want to have doubt cast on
the mission statement, and have our leadership feel a need to
reconsider it, because someone somewhere might have said something
general about not liking it.  And in any case as long as we have a
mission statement the Tao should refer to it.

Scott

From john-ietf@jck.com  Thu May 31 08:19:53 2012
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 ED8AE11E8080 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:19:52 -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.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBNLmFQ-wHRx for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:19:52 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BB80621F874A for <ietf@ietf.org>; Thu, 31 May 2012 08:19:51 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Sa74P-000I9W-Cv for ietf@ietf.org; Thu, 31 May 2012 11:13:49 -0400
Date: Thu, 31 May 2012 11:19:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A	Novice's Guide to the Internet Engineering Task Force) to	Informational RFC
Message-ID: <CE474406564976FC0A885D95@PST.JCK.COM>
In-Reply-To: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>
References: <20120530225655.19475.74871.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 15:19:53 -0000

--On Wednesday, May 30, 2012 15:56 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> The IESG has received a request from an individual submitter
> to consider the following document:
> - 'The Tao of IETF: A Novice's Guide to the Internet
> Engineering Task    Force'
>   <draft-hoffman-tao4677bis-15.txt> as Informational RFC
> 
> The Tao of the IETF has grown a bit stale.  For example, many
> of the tasks that were requested by email are now done with
> online tools, completely avoiding manual intervention by the
> Secretariat.  This is an effort to refresh the document.

I'd like to move this discussion up a level from discussions
about the present state of the text.  

The community has concluded several times that certain types of
documents are better handled as web pages (wiki or otherwise),
by published "statements", or even as permanent I-Ds, rather
than as archival RFCs.  Examples include the "Internet Official
Protocol Standards" sequence, the "Requests for Comments
Summary", the "Instructions to RFC Authors", procedures of the
IAOC and other bodies, and a series of IESG statements.  

I've argued that we use RFCs for anything of normative
significance, even when the only marginal value the RFC provides
is a good time-stamped snapshot (and sometimes lost those
arguments).  But this is an Informational document merely
provides advice, general guidance about procedures, and pointers
to the real specifications.

I suggest that, if anything is stale, it is RFC 4677, not the
rolling I-D updates that Paul has been maintaining from time to
time.  I haven't pointed a newcomer to the IETF to the RFC,
rather than the current I-D, for years.  I assume that others
have done similarly.

Assuming Paul isn't planning to get this published as an RFC and
then immediately retire from the IETF and that we don't have a
delusion that this document will not need to be maintained and
updated as things change, I propose the following:

(1) Establish the Tao as a modified Wiki, complete with live
HTML links to relevant documents and other relevant
discussions.. Provide some mechanism for comments to the editor
or even discussion that works better than the RFC Errata
process.  Turn maintenance of that page over to a volunteer or
two (ideally someone young enough to learn a lot from the
process) or the Secretariat.   Before someone says "cost",
please calculate the costs to the community of an extended Last
Call in which people debate details of wording.

(2) Appoint Paul as chair of an editorial committee with zero or
more additional members to be appointed at his discretion
subject to advice and consent of the IESG.  That committee gets
to consider whether to make changes.  If they get it wrong, they
are subject to the community's normal forms of abuse and, in
principle, appeals.  That could add a bit of work for the IESG
but I suggest only a bit and less than running a Last Call.

(3) Replace/ obsolete RFC 4677 by a document modeled on RFC
5000.  I.e., it should explain why we are maintaining the Tao as
one or more web pages and should provide a durable pointer to
how the web page can be found.

just my opinion,
   john


From stpeter@stpeter.im  Thu May 31 08:35:32 2012
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 A594B11E80EE for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:35:32 -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 4obZ55Grv8FT for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:35:31 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D1C7F11E80D9 for <ietf@ietf.org>; Thu, 31 May 2012 08:35:31 -0700 (PDT)
Received: from [64.101.72.115] (unknown [64.101.72.115]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3CE0240075; Thu, 31 May 2012 09:52:02 -0600 (MDT)
Message-ID: <4FC78FC2.9030800@stpeter.im>
Date: Thu, 31 May 2012 09:35:30 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Colloquial language
References: <20120531134617.CD2B018C0C7@mercury.lcs.mit.edu>
In-Reply-To: <20120531134617.CD2B018C0C7@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 15:35:32 -0000

On 5/31/12 7:46 AM, Noel Chiappa wrote:
>     > From: Simon Perreault <simon.perreault@viagenie.ca>
> 
>     > I think colloquialisms may often be as hard to understand as excellent
>     > but seldom-used vocabulary.
> 
> Indeed - and now that we have this really cool Internet thingy (it's odd to
> think that young people have no memory of what the world was like before a
> large fraction of its information was instantly at one's fingertips - and in
> 80 years or so, _nobody_ will remember that age personally), one can very
> easily look up either a recondite word, or an obscure colloquialism, in
> moments...

So the way we introduce some people to the IETF is to expect that they
will look up fifty unfamiliar words and phrases? Having taught English
as a second language, I can attest that some of the idioms and
colloquialisms included in this document would have caused puzzlement in
my students.

It's bad enough that many IETFers speak in a highly colloquial fashion
at our meetings. I think it would be a shame if we do not avoid such
confusion in our written (and supposedly user-friendly) introduction to
the IETF.

Showing up at your first IETF meeting is quite enough of "taking the
plunge" [1] for most people. Why make it even more difficult?

Peter

[1] http://idioms.thefreedictionary.com/take+the+plunge

From jnc@mercury.lcs.mit.edu  Thu May 31 08:54:49 2012
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 CFADD21F867F for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:54: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 hMoPv2DrpLmd for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:54:48 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id A7C4C21F8417 for <ietf@ietf.org>; Thu, 31 May 2012 08:54:47 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id EA34618C0D0; Thu, 31 May 2012 11:54:46 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Colloquial language
Message-Id: <20120531155446.EA34618C0D0@mercury.lcs.mit.edu>
Date: Thu, 31 May 2012 11:54:46 -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, 31 May 2012 15:54:49 -0000

    > From: Peter Saint-Andre <stpeter@stpeter.im>

    > It's bad enough that many IETFers speak in a highly colloquial fashion
    > at our meetings. ... Showing up at your first IETF meeting is quite
    > enough of "taking the plunge" [1] for most people.

If it's meeting attendees one is worried about, I'd have thought that having
common colloquialisms in the document would be a feature, not a bug - people
would meet them while facing a computer upon which they could look them up at
their leisure, not in a live (and likely fast-moving) conversation.

Having said that, I think both sides have decent points, and personally don't
have any strong preference.

	Noel

From ole@cisco.com  Thu May 31 08:59:26 2012
Return-Path: <ole@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 E4C4B11E8149 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.932
X-Spam-Level: 
X-Spam-Status: No, score=-110.932 tagged_above=-999 required=5 tests=[AWL=-0.333, 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 EUZ+OXyoSW+z for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 08:59:26 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 647FA11E8147 for <ietf@ietf.org>; Thu, 31 May 2012 08:59:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1943; q=dns/txt; s=iport; t=1338479966; x=1339689566; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=f6CDe4zjFeQ47sD3GSxIdNlpUnccc9ZbtAYS9z0iKzM=; b=YhycXF3AjMBaJyiVFNSPaPNLTVSwlHQlOaGfHGoVrzKj8TJ7g1UyOQjG Z2vO53REuk4oGF18H4IIJcI+eFywEKubHJcJnzK/AXmG1Y57vkNZ0cs7w 3+aQ2YjSTb/tOFftfykloxANvZWlB4lwENrfzORkSPTUnNktfIvzD6RKq 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAH6Ux0+rRDoJ/2dsb2JhbABBA7QMgQeCGAEBAQMBEgECJT8FCwsVAy5XBhMih2QEDJkxg0cQnAKIH4JyGoIRgxsDiECNZ4lsgxKBBGKDAIE/
X-IronPort-AV: E=Sophos;i="4.75,693,1330905600"; d="scan'208";a="44016945"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 31 May 2012 15:59:26 +0000
Received: from sjc-vpn7-992.cisco.com (sjc-vpn7-992.cisco.com [10.21.147.224]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q4VFxPFs022212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Thu, 31 May 2012 15:59:25 GMT
Date: Thu, 31 May 2012 09:02:15 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Colloquial language
In-Reply-To: <4FC78FC2.9030800@stpeter.im>
Message-ID: <alpine.OSX.2.01.1205310900340.85201@sjc-vpn7-992.cisco.com>
References: <20120531134617.CD2B018C0C7@mercury.lcs.mit.edu> <4FC78FC2.9030800@stpeter.im>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@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: Thu, 31 May 2012 15:59:27 -0000

I fully agree. One could (perhaps) argue that this document would be a 
suitable place to INTRODUCE non-native speakers to such language, but
then the document really needs to do that rather than have the reader
infer meaning based on context.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Thu, 31 May 2012, Peter Saint-Andre wrote:

> On 5/31/12 7:46 AM, Noel Chiappa wrote:
> >     > From: Simon Perreault <simon.perreault@viagenie.ca>
> > 
> >     > I think colloquialisms may often be as hard to understand as excellent
> >     > but seldom-used vocabulary.
> > 
> > Indeed - and now that we have this really cool Internet thingy (it's odd to
> > think that young people have no memory of what the world was like before a
> > large fraction of its information was instantly at one's fingertips - and in
> > 80 years or so, _nobody_ will remember that age personally), one can very
> > easily look up either a recondite word, or an obscure colloquialism, in
> > moments...
> 
> So the way we introduce some people to the IETF is to expect that they
> will look up fifty unfamiliar words and phrases? Having taught English
> as a second language, I can attest that some of the idioms and
> colloquialisms included in this document would have caused puzzlement in
> my students.
> 
> It's bad enough that many IETFers speak in a highly colloquial fashion
> at our meetings. I think it would be a shame if we do not avoid such
> confusion in our written (and supposedly user-friendly) introduction to
> the IETF.
> 
> Showing up at your first IETF meeting is quite enough of "taking the
> plunge" [1] for most people. Why make it even more difficult?
> 
> Peter
> 
> [1] http://idioms.thefreedictionary.com/take+the+plunge
> 

From brian.e.carpenter@gmail.com  Thu May 31 09:36:27 2012
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 F081C21F86CF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.683
X-Spam-Level: 
X-Spam-Status: No, score=-101.683 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 vIF-z-ysGL8M for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:36:26 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id BBD6121F86D6 for <ietf@ietf.org>; Thu, 31 May 2012 09:36:25 -0700 (PDT)
Received: by eekd4 with SMTP id d4so560178eek.31 for <ietf@ietf.org>; Thu, 31 May 2012 09:36: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=DCyzpkBvOaGbW4VwjFH6QLNxw1okMxR9SkE1fA5/4eM=; b=kmhqhwloM2u+x0uwWp8nWbKatWc7vS1eUEsECkw54rI+YaEJJEkobg+qKcyFBEAxnu B0S88Wke0mGrmkBAGglZSsmi9tLhgFbPHuBNGup5fRUXxBD2y48332SQ1HY26XRcspy9 7fp7pv3qaUya70OL8zdWap8sgR2LOtGSSP1ulxYi4qohAdLG4UF4r7GLfAz4qenJ4fii T4uYwy/zzKnis7lfnI7gDNspNFgLB/yp4cHlFbFF6l7KoQ8yqNw9KGc3ry0m3jFpfz7O qljWWeqXfitBgrKG6/8EDoGv7LF8UFBlauIRgMtMMPrPTFyam/H3u9Ky7fiv5j0NAwB3 fNDQ==
Received: by 10.14.39.70 with SMTP id c46mr9440201eeb.118.1338482184520; Thu, 31 May 2012 09:36:24 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id a16sm12335456eeg.0.2012.05.31.09.36.22 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 09:36:23 -0700 (PDT)
Message-ID: <4FC79E00.7030600@gmail.com>
Date: Thu, 31 May 2012 17:36:16 +0100
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: Mission statement [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC70E09.30002@cisco.com> <4FC71041.3040609@gmail.com> <C5ABD549485AE1AF8F831363@PST.JCK.COM>
In-Reply-To: <C5ABD549485AE1AF8F831363@PST.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: Thu, 31 May 2012 16:36:27 -0000

John,

On 2012-05-31 15:53, John C Klensin wrote:
> 
> --On Thursday, May 31, 2012 07:31 +0100 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2012-05-31 07:22, Eliot Lear wrote:
>>
>> ...
>>>   * I've been told by some that the Mission of the IETF is in
>>>   some way out of date.  I don't know whether this is true, 
>> That sound like somebody's personal opinion, but it is still a
>> BCP and therefore still represents IETF consensus.
> 
> Brian,
> 
> Regardless of how I feel about this particular case, I don't
> understand how to put your comment in context.  In particular,
> would you 
> 
> * Assert that the IETF is so diligent about its process BCPs
> that any that have become out of date, overtaken by events, or
> otherwise irrelevant have been immediately and formally declared
> obsolete or historic?  I have better ways to spend my time at
> the moment, but I imagine that many members of the community
> could come up with lists of counterexamples rather quickly
> (perhaps starting from how long it took us to get "automatic
> review" out of RFC 2026).

True, but adding to what Scott Brim said, where is the evidence that the
mission statement is OBE? The comment I was responding to seemed
quite gratuitous.

> 
> * When a document is revised ("updated" or "obsoleted") omitting
> a reference that appeared in the earlier version requires a
> special consensus call rather than treating consensus on the new
> document, once achieved, as atomic?   Granted, the relatively
> new provisions requiring identification and explanation of what
> was obsoleted or updated are a step toward making sure that
> those participating in the consensus process are aware of what
> happened but (i) those provisions have, no far, not been
> extended to require a discussion of every changed reference and
> (ii) are not themselves in a BCP or other document that has been
> documented as achieving community consensus on the details.
> Independent of that BCP problem, would you advocate making each
> new document list all of the references to BCP or Standards
> Track documents that were not carried forward and identifying
> the reasons?

Certainly not, although there might be cases where it was
useful. ("Since carrier pigeons have gone extinct, the mapping
to Avian Carriers has been removed from this specification.")

   Brian

From brian.e.carpenter@gmail.com  Thu May 31 09:42:38 2012
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 7079C11E80B3 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.684
X-Spam-Level: 
X-Spam-Status: No, score=-101.684 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 ka3JWW5HDYzx for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:42:38 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE0EF11E80B1 for <ietf@ietf.org>; Thu, 31 May 2012 09:42:34 -0700 (PDT)
Received: by eekd4 with SMTP id d4so565185eek.31 for <ietf@ietf.org>; Thu, 31 May 2012 09:42:34 -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=Yri8Y8TmHhl6e5AV3z9B9HVO5+wks+dCRRDjs85Ft2o=; b=qVnVjg4DfxfNEKp6cBUfwN0qsjZv7xERscMhXy2wEviJw2jHyLrSQ0h7zF7wznxEkP a9BJUFUfapkhFVc5C9wjlq1uWLsNbsCkaBflsTvtA8khN7OBfvGlkdeYQJx6BmkH61A4 +W/Iwz2RlvpvsAej1/q/Y1C4T0OitUkfG2PqceYA/mrzio0v+aOazMsp4uDs3VuxhH20 AZo5Q7ITKI3p2m26W05sw7p9UTP3yYG+2qn6EUEy5apxh8ArUpOkXrZ0xXgQohzRfVK/ pU+SGgRrYn4Q1UOU3sr/213IaBu/6bVD752q2e38HFw7AHP1Q0Db/IgToS07U85u8/zW /MCQ==
Received: by 10.14.127.134 with SMTP id d6mr9733840eei.45.1338482553765; Thu, 31 May 2012 09:42:33 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id z5sm12367801eem.3.2012.05.31.09.42.31 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 09:42:32 -0700 (PDT)
Message-ID: <4FC79F71.6060000@gmail.com>
Date: Thu, 31 May 2012 17:42:25 +0100
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: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM>
In-Reply-To: <CE474406564976FC0A885D95@PST.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: Thu, 31 May 2012 16:42:38 -0000

John,

On 2012-05-31 16:19, John C Klensin wrote:
...
> Assuming Paul isn't planning to get this published as an RFC and
> then immediately retire from the IETF and that we don't have a
> delusion that this document will not need to be maintained and
> updated as things change, I propose the following:
> 
> (1) Establish the Tao as a modified Wiki, complete with live
> HTML links to relevant documents and other relevant
> discussions.. Provide some mechanism for comments to the editor
> or even discussion that works better than the RFC Errata
> process.  Turn maintenance of that page over to a volunteer or
> two (ideally someone young enough to learn a lot from the
> process) or the Secretariat.   Before someone says "cost",
> please calculate the costs to the community of an extended Last
> Call in which people debate details of wording.

+- some trivia such as avoiding the fuzziness of a wiki, isn't that
what http://www.ietf.org/tao.html already achieves?

I tend to agree with your suggestions below.

    Brian

> 
> (2) Appoint Paul as chair of an editorial committee with zero or
> more additional members to be appointed at his discretion
> subject to advice and consent of the IESG.  That committee gets
> to consider whether to make changes.  If they get it wrong, they
> are subject to the community's normal forms of abuse and, in
> principle, appeals.  That could add a bit of work for the IESG
> but I suggest only a bit and less than running a Last Call.
> 
> (3) Replace/ obsolete RFC 4677 by a document modeled on RFC
> 5000.  I.e., it should explain why we are maintaining the Tao as
> one or more web pages and should provide a durable pointer to
> how the web page can be found.
> 
> just my opinion,
>    john
> 
> 

From brian.e.carpenter@gmail.com  Thu May 31 09:44:42 2012
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 138F411E80CF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.684
X-Spam-Level: 
X-Spam-Status: No, score=-101.684 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, 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 SHIZELUCibqW for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:44:41 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0AB11E80CD for <ietf@ietf.org>; Thu, 31 May 2012 09:44:41 -0700 (PDT)
Received: by eekd4 with SMTP id d4so566941eek.31 for <ietf@ietf.org>; Thu, 31 May 2012 09:44:40 -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=EX1qIqRCeGbCw5zhWg6qU1tkup+7hlrF6mLuqcpAwyQ=; b=M0Z7TrkoIhZzN28S59ry8wAyHCX6b0sfcp261oAtQ386UuhktBpgTzjuTbULgDxRlW MhtMiwg+r1rNMv3rx/MLy4jwlgBG9vDK+0cDaT/ujG9j9bZ71QJXIrc4eRGuygZmHZMs j4oqlQB2G4P+6MTd1niWeJ7wk/OTYFzJ2TLl/1q/OWNFqNYheCfHjDCaTklcEwvUKHPY xJ/nyhOTUZSnPFR7c/jabmmL/+NynSQtNuvuBZtXbySkkh2ri1HmcX+q8eaPafvuSele kYqkXBvMnCzszgFiu1TYCr/uYJVq5eh/SlD7O6zvwQa4ozbLoz6KJ+fJ1kuRB1d1CU4f a4GQ==
Received: by 10.14.97.16 with SMTP id s16mr8111247eef.117.1338482680502; Thu, 31 May 2012 09:44:40 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-25.as13285.net. [2.102.217.25]) by mx.google.com with ESMTPS id s8sm12274968ees.16.2012.05.31.09.44.38 (version=SSLv3 cipher=OTHER); Thu, 31 May 2012 09:44:39 -0700 (PDT)
Message-ID: <4FC79FF0.9010001@gmail.com>
Date: Thu, 31 May 2012 17:44:32 +0100
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: SM <sm@resistor.net>
Subject: IANA [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to	Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120530214914.094ac8d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120530214914.094ac8d0@resistor.net>
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, 31 May 2012 16:44:42 -0000

On 2012-05-31 09:24, SM wrote:

...
> In Section 3.2.3:
> 
>   "Approves the appointment of the IANA"
> 
> Isn't IANA more of a U.S. Government decision? 

The IAB decides who acts as the IETF's IANA. RFC 2860 again.

  Brian

From melinda.shore@gmail.com  Thu May 31 09:55:51 2012
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 7CD8021F86F7 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:55:51 -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 edZB4dq29RYk for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 09:55:50 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA4621F86F6 for <ietf@ietf.org>; Thu, 31 May 2012 09:55:50 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1540713dac.31 for <ietf@ietf.org>; Thu, 31 May 2012 09: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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+bqv4Fs3atphw2KgorgSXPqWN9XAS7XbbTWY8Y2+XrY=; b=qA7HEJ91j/+oJ+5ybE85zOuSjbpiipT4MNW5IN3HF18rf9ux1ao4MdYywLh1grKvcl sPlj9Qb2nzXyJUs7KMBnncdtsefqdIGjDYXTHSW1BJAtFKUQFjL6HVZtEMSHR70GPDGo gPJkZql6Zfid/PaXIa/VtVoVOTFXeRfVS4BXcTQs3kSejBdwzBT+3yZTJzWZoU53eyja uQi4whYWsFJhlb3E2fGZckg0LBF3+LeD4Ey0HG3IkVpYiXlkswmIeyA8PUcvwVm9q2OU Bv9tcPaRw15kMRGVXX+7SlujlhpdP8oLKgvcQ/9Ge+iRAqx0WY1xTuXi5hK5KowtBLd5 uh0A==
Received: by 10.68.237.166 with SMTP id vd6mr1129254pbc.139.1338483350164; Thu, 31 May 2012 09:55:50 -0700 (PDT)
Received: from Melindas-iMac.local (66-230-85-178-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.178]) by mx.google.com with ESMTPS id rs3sm4710609pbc.47.2012.05.31.09.55.48 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 May 2012 09:55:49 -0700 (PDT)
Message-ID: <4FC7A293.20502@gmail.com>
Date: Thu, 31 May 2012 08:55:47 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task	Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com>	<4FC716B8.2090208@dcrocker.net> <4FC71CC9.2000604@gmail.com>	<4FC72213.8060800@bbiw.net> <4FC732D3.7090904@cs.tcd.ie> <4FC7345E.807@cisco.com>
In-Reply-To: <4FC7345E.807@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2012 16:55:51 -0000

On 5/31/12 1:05 AM, Klaas Wierenga wrote:
> As a non-native speaker I agree. I think colloquial is fine. The one
> thing causes me some trouble is all the references that Americans make
> to sports that nobody in the civilized world cares about ;-) ("left
> field", "Hail Mary passes" etc.) But I think the Tao pretty much avoids
> those (perhaps "Home base" is the exception).

A previous employer's HR team put together training material
for those of us who were helping with university recruiting and
it was one extended American football metaphor.  Since nearly
all the engineers who were volunteering were Indian or Chinese
it turned out to be more confusing than effective (and not
necessarily understandable by North American nerds, either).

I tend to use a lot of idiomatic language when I write but I
do understand the issues around use of regional idioms, and I
note that so far of the non-native speakers who've commented,
all are either European or Israeli.  I'm wondering if regional
idioms are as clear to people from east, southeast, and south
Asian countries.  Also, for whatever it's worth, the English
idioms under discussion all seem to be American.

Melinda

From mrex@sap.com  Thu May 31 12:39:56 2012
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 08F5B21F86E2 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 12:39:56 -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=[AWL=0.000, 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 TPgwIPd3VYxa for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 12:39:55 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3216E21F86D7 for <ietf@ietf.org>; Thu, 31 May 2012 12:39:55 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q4VJdilG023485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 31 May 2012 21:39:45 +0200 (MEST)
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <4FC732D3.7090904@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Thu, 31 May 2012 21:39:44 +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: <20120531193944.BF2321A094@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Dave Crocker <dcrocker@bbiw.net>, 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: Thu, 31 May 2012 19:39:56 -0000

Stephen Farrell wrote:
> 
> I'm with Brian and Yoav on this. I don't see a need
> to change here. And I do think we might lose something
> if we become too PC. If a bunch of non-native speakers
> did say "yes, I found that made the document less
> useful" then I'd be more convinced that all these
> changes were worth it.

+1

I do not believe that *over*simplyfying the language is beneficial for
a clearly non-technical document.  Using a language that is similar
to discussion on mailing lists should be perfectly OK, as long as
the colloquial expressions can still be googled easily, for those
not familiar with them.  I have to google Dilberts and xkcd every once
in a while, an those sometimes contain very "local" expressions that
are really difficult to find -- and still I'm OK with this.

-Martin

From ynir@checkpoint.com  Thu May 31 13:22:36 2012
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 1971221F86CE for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 13:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.561
X-Spam-Level: 
X-Spam-Status: No, score=-10.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 E7RgCRveSxTg for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 13:22:35 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E813121F86D0 for <ietf@ietf.org>; Thu, 31 May 2012 13:22:34 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (dlpgw.checkpoint.com [194.29.34.27]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q4VKMHeA025650; Thu, 31 May 2012 23:22:17 +0300
X-CheckPoint: {4FC7DF39-1-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 31 May 2012 23:22:16 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "mrex@sap.com" <mrex@sap.com>
Date: Thu, 31 May 2012 23:22:12 +0300
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide	to the Internet Engineering Task Force) to Informational RFC]
Thread-Topic: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide	to the Internet Engineering Task Force) to Informational RFC]
Thread-Index: Ac0/axHdOpmb9P4wSyGHf89cSsgPkQ==
Message-ID: <16CF07A8-31C4-421D-A84A-DFB19516AFAB@checkpoint.com>
References: <20120531193944.BF2321A094@ld9781.wdf.sap.corp>
In-Reply-To: <20120531193944.BF2321A094@ld9781.wdf.sap.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11e8ca8945042f3b877518198816425a8bc232a810
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <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: Thu, 31 May 2012 20:22:36 -0000

On May 31, 2012, at 10:39 PM, Martin Rex wrote:

> Stephen Farrell wrote:
>>=20
>> I'm with Brian and Yoav on this. I don't see a need
>> to change here. And I do think we might lose something
>> if we become too PC. If a bunch of non-native speakers
>> did say "yes, I found that made the document less
>> useful" then I'd be more convinced that all these
>> changes were worth it.
>=20
> +1
>=20
> I do not believe that *over*simplyfying the language is beneficial for
> a clearly non-technical document.  Using a language that is similar
> to discussion on mailing lists should be perfectly OK, as long as
> the colloquial expressions can still be googled easily, for those
> not familiar with them.  I have to google Dilberts and xkcd every once
> in a while, an those sometimes contain very "local" expressions that
> are really difficult to find -- and still I'm OK with this.
>=20
> -Martin

I had to look up some things when I ready The Adventures of ACTION ITEM for=
 the first time[1], but the TAO draft is nowhere near that level. Besides, =
it's essential vocabulary for anyone seeking a career in project management=
.

Yoav

[1] http://professionalsuperhero.com/


From ben@nostrum.com  Thu May 31 15:08:17 2012
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 717CE21F866B; Thu, 31 May 2012 15:08:17 -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 1tq+XpNl1WUY; Thu, 31 May 2012 15:08:16 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9B21F8665; Thu, 31 May 2012 15:08:16 -0700 (PDT)
Received: from [10.0.1.33] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q4VM8FgH004192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 May 2012 17:08:15 -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/Telechat review of draft-ietf-trill-rbridge-extension-04
Date: Thu, 31 May 2012 17:08:14 -0500
Message-Id: <8A72CDEF-BC47-4385-A6E3-B5F4474FC70F@nostrum.com>
To: draft-ietf-trill-rbridge-extension.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The 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 May 2012 22:08:17 -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-trill-rbridge-extension-04
Reviewer: Ben Campbell
Review Date: 2012-05-31
IETF LC End Date: 2012-06-07
IESG Telechat date: 2012-06-07

Note: Since this draft is on the agenda of the IESG Telechat on the same =
day that the IETF last call expires, this review is intended for both =
purposes.

Summary:=20

This draft is almost ready for publication as a proposed standard, but I =
have some clarification questions and comments that should be considered =
prior to publication.

Major issues:

None

Minor issues:

-- section 2, general:

Do the authors assume that all TRILL extensions will follow this spec? =
Since RFC6325 already specifies an extension mechanism, what stops an =
extension from ignoring this spec and doing something different? Does it =
hurt if they do?

-- section 2, 3rd paragraph from end: "Non-critical extensions can be =
safely ignored."

Is that intended to be normative? (Seems like it should be, since =
behavior for critical extensions is normative).

-- section 2.1, 1st paragraph, last sentence:

Redundant with normative language in previous section.


-- section 2.3, first paragraph:=20

Is the first sentence intended as normative?

-- section 6, last paragraph:

No security implications of this are mentioned. Is it really a security =
consideration?

Also, is this more likely to be set incorrectly than all the other =
things that some implementation might screw up, so that it warrants =
special treatment?


Nits/editorial comments:

-- section 1:=20

Please expand TRILL on first mention in the body of the document (i.e. =
not just in the Abstract.)

-- section 2:

Please expand RBridge and IS-IS on first mention.

-- section 2, bullet list, 2nd bullet: " ... which would only =
necessarily affect the RBridge(s) where a TRILL frame is decapsulated"

Does that mean it always affects the decapsulating RBridge but might =
effect transit RBridges as well?=20

-- section 2, first paragraph after bullet list: "critical hop-by-hop =
extension"

I assume this means an extension with the critical flag set? If so, it =
would be more precise to say that.

-- sectio 2.1, 1st paragraph:

I'm a little confused by a citation for "future documents". Do you mean =
the cited document as an example of something that might do this (in =
which case a "for example" would help), or do you mean to say that =
document will do this?

-- section 2.2, 1st paragraph:

Please expand PDU on first mention.

-- section 2.3, first paragraph:=20

s/modifictions/modifications

-- section 5:

Since section 3 is entirely composed of the referenced table, and seems =
to exist mostly if not entirely for the purpose of this reference, why =
not just move the table to the IANA considerations section.



From ben@niven-jenkins.co.uk  Thu May 31 15:36:11 2012
Return-Path: <ben@niven-jenkins.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 6CA7D21F863D for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 15: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 hmxxpnJnc71v for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 15:36:10 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id A20BC21F8638 for <ietf@ietf.org>; Thu, 31 May 2012 15:36:10 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1SaDyT-00017v-FR; Thu, 31 May 2012 23:36:09 +0100
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com>
Date: Thu, 31 May 2012 23:36:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: "ietf@ietf.org 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, 31 May 2012 22:36:11 -0000

On 31 May 2012, at 09:16, Ole Jacobsen wrote:
> Sounds like a difficult thing to do with any kind of predictable or=20
> measurable outcome, although it might be fun to ask the Brits if they
> understand everything the Americans are saying and vice versa :-)

I don't really have any issues understanding American English but I'm =
regularly gobsmacked by how many North Americans struggle to understand =
some things that I say :-)

Ben


From joelja@bogus.com  Thu May 31 15:44:20 2012
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 2080D21F8611 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 15:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApceqEPAuv45 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 15:44:19 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 92F7A21F85AF for <ietf@ietf.org>; Thu, 31 May 2012 15:44:19 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q4VMiHFl008067 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 31 May 2012 22:44:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FC7F43C.6010609@bogus.com>
Date: Thu, 31 May 2012 15:44:12 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <4FC6CE2F.70903@stpeter.im> <4FC71178.2050401@gmail.com> <alpine.OSX.2.01.1205310108380.82586@sjc-vpn7-992.cisco.com> <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
In-Reply-To: <47983FE3-D3C5-4AC6-BAC3-F8DC96CAF854@niven-jenkins.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 31 May 2012 22:44:17 +0000 (UTC)
Cc: Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org 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, 31 May 2012 22:44:20 -0000

On 5/31/12 15:36 , Ben Niven-Jenkins wrote:
> 
> On 31 May 2012, at 09:16, Ole Jacobsen wrote:
>> Sounds like a difficult thing to do with any kind of predictable or
>>  measurable outcome, although it might be fun to ask the Brits if
>> they understand everything the Americans are saying and vice versa
>> :-)
> 
> I don't really have any issues understanding American English but I'm
> regularly gobsmacked by how many North Americans struggle to
> understand some things that I say :-)

Do we spell Standardization with and s or a z?

> Ben
> 
> 


From paul.hoffman@vpnc.org  Thu May 31 16:04:32 2012
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 28EC321F8636 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.019
X-Spam-Level: 
X-Spam-Status: No, score=-102.019 tagged_above=-999 required=5 tests=[AWL=0.580, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyX5ux2AXIdV for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:04:31 -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 8B70321F8630 for <ietf@ietf.org>; Thu, 31 May 2012 16:04:31 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4VN4UDt057855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 31 May 2012 16:04:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Making the Tao a web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CE474406564976FC0A885D95@PST.JCK.COM>
Date: Thu, 31 May 2012 16:04:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.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 May 2012 23:04:32 -0000

On May 31, 2012, at 8:19 AM, John C Klensin wrote:

> (1) Establish the Tao as a modified Wiki, complete with live
> HTML links to relevant documents and other relevant
> discussions.. Provide some mechanism for comments to the editor
> or even discussion that works better than the RFC Errata
> process.  Turn maintenance of that page over to a volunteer or
> two (ideally someone young enough to learn a lot from the
> process) or the Secretariat.   Before someone says "cost",
> please calculate the costs to the community of an extended Last
> Call in which people debate details of wording.
>=20
> (2) Appoint Paul as chair of an editorial committee with zero or
> more additional members to be appointed at his discretion
> subject to advice and consent of the IESG.  That committee gets
> to consider whether to make changes.  If they get it wrong, they
> are subject to the community's normal forms of abuse and, in
> principle, appeals.  That could add a bit of work for the IESG
> but I suggest only a bit and less than running a Last Call.
>=20
> (3) Replace/ obsolete RFC 4677 by a document modeled on RFC
> 5000.  I.e., it should explain why we are maintaining the Tao as
> one or more web pages and should provide a durable pointer to
> how the web page can be found.


Works for me, other than it should not be a "wiki". It should have one =
editor who takes proposed changes from the community the same way we do =
it now. Not all suggestions from this community, even from individuals =
in the leadership, are ones that should appear in such a document.

Simpler than the above: make it a web page (as Brian points out, we =
already have a good URL), have one editor, have one leadership person =
who approves non-trivial changes (I think "IETF Chair" fits here well), =
have a "last modified" date on it, and update it as needed. If there is =
consensus in the community to do this, I'm happy to take on the =
HTMLizing and skip the RFCizing for this round.

--Paul Hoffman


From nick@inex.ie  Thu May 31 16:30:27 2012
Return-Path: <nick@inex.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 ACFC221F8559 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:30:27 -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 CdZ72bY0zfX5 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:30:27 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 016FB21F8557 for <ietf@ietf.org>; Thu, 31 May 2012 16:30:26 -0700 (PDT)
X-Envelope-To: <ietf@ietf.org>
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:d086:dc37:f3ff:ac3e]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q4VNU7CC059619 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 1 Jun 2012 00:30:12 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4FC7FF09.4020701@inex.ie>
Date: Fri, 01 Jun 2012 00:30:17 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
In-Reply-To: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
X-Enigmail-Version: 1.4.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
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, 31 May 2012 23:30:27 -0000

On 01/06/2012 00:04, Paul Hoffman wrote:
> Works for me, other than it should not be a "wiki". It should have one
> editor who takes proposed changes from the community the same way we do
> it now. Not all suggestions from this community, even from individuals
> in the leadership, are ones that should appear in such a document.

In practice, if this is to be a living document then it should be open for
inspection and poking rather than preserved in formaldehyde and put in a
display case, only to be opened occasionally when the curator decides the
glass needs some dusting.  That way leads to sclerosis.

Please put it on a wiki and put all changes through a lightweight review
system.  If someone makes a change which doesn't work, then it can be
reverted quickly and easily.  This approach is much more in line with the
ietf approach of informality / asking for forgiveness rather than
permission / rough consensus + running code / etc.

Nick

From paul.hoffman@vpnc.org  Thu May 31 16:50:14 2012
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 3D27911E8098 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.185
X-Spam-Level: 
X-Spam-Status: No, score=-102.185 tagged_above=-999 required=5 tests=[AWL=0.414, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOc9C6fU+5oG for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 16:50:13 -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 9BC9611E8080 for <ietf@ietf.org>; Thu, 31 May 2012 16:50:13 -0700 (PDT)
Received: from [10.20.30.102] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q4VNoAD8059217 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 May 2012 16:50:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Making the Tao a web page
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FC7FF09.4020701@inex.ie>
Date: Thu, 31 May 2012 16:50:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <98BC45C2-3C58-4DC6-89FA-766B426778BF@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <4FC7FF09.4020701@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1278)
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 May 2012 23:50:14 -0000

On May 31, 2012, at 4:30 PM, Nick Hilliard wrote:

> On 01/06/2012 00:04, Paul Hoffman wrote:
>> Works for me, other than it should not be a "wiki". It should have =
one
>> editor who takes proposed changes from the community the same way we =
do
>> it now. Not all suggestions from this community, even from =
individuals
>> in the leadership, are ones that should appear in such a document.
>=20
> In practice, if this is to be a living document then it should be open =
for
> inspection and poking rather than preserved in formaldehyde and put in =
a
> display case, only to be opened occasionally when the curator decides =
the
> glass needs some dusting.  That way leads to sclerosis.

Thank you for that most colorful analogy. :-) What I proposed is exactly =
what we are doing now, except that the changes would appear on the web =
page instead of an Internet-Draft and, five years later, an RFC. Are you =
saying that the current system (which you have not commented on until =
now) is sclerotic (a word that I have wanted to use since I learned it =
in high school)?

> Please put it on a wiki and put all changes through a lightweight =
review
> system.  If someone makes a change which doesn't work, then it can be
> reverted quickly and easily.  This approach is much more in line with =
the
> ietf approach of informality / asking for forgiveness rather than
> permission / rough consensus + running code / etc.


In the IETF approach, only the authors of an Internet-Draft can change =
the contents of that draft. I hope you are not proposing a change to =
that as well.

--Paul Hoffman


From fred@cisco.com  Thu May 31 17:01:44 2012
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 C1F2A11E8098 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.47
X-Spam-Level: 
X-Spam-Status: No, score=-110.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 affXhN3alTLC for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:01:44 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 14B2F11E8080 for <ietf@ietf.org>; Thu, 31 May 2012 17:01:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=474; q=dns/txt; s=iport; t=1338508904; x=1339718504; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=p1IN62oMU6c2AKCmcVP6x4e690yJ+9dkPqummow+EIU=; b=UyrL4a+bZ8MiQdl/Ug/4CqqNZ3arEqr/OTh5zXeROcIhqj4ilMkWt2F/ L1JixdsLAcw/IesC5/jvF2hjlvrVM7Ob+RwgRU+ZTFpsMWcL3NlBbiqBy UkMxBX7o/oYd6gpBv3dPSDGqBPqpdUlWfp8Q3r5ZeMCRWlLODVflu7jrw M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGMFyE+rRDoH/2dsb2JhbABEtCeBB4IYAQEBAwESASc/BQsLRlcGJw6HZASZCp9TixGFFWADiECMWYVPiD+BZoMA
X-IronPort-AV: E=Sophos;i="4.75,695,1330905600"; d="scan'208";a="47118668"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 01 Jun 2012 00:01:43 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q510103r020945; Fri, 1 Jun 2012 00:01:43 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 31 May 2012 17:01:43 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 31 May 2012 17:01:43 -0700
Subject: Re: Making the Tao a web page
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
Date: Thu, 31 May 2012 16:59:41 -0700
Message-Id: <8A6D2A4F-AE0A-4770-B8BB-75FF0F43660D@cisco.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
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, 01 Jun 2012 00:01:44 -0000

On May 31, 2012, at 4:04 PM, Paul Hoffman wrote:

> Simpler than the above: make it a web page (as Brian points out, we =
already have a good URL), have one editor, have one leadership person =
who approves non-trivial changes (I think "IETF Chair" fits here well), =
have a "last modified" date on it, and update it as needed. If there is =
consensus in the community to do this, I'm happy to take on the =
HTMLizing and skip the RFCizing for this round.

wfm=

From stpeter@stpeter.im  Thu May 31 17:04:15 2012
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 B82E211E80AB for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:04: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 BDykq+rVz6dD for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:04:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0D83A11E8080 for <ietf@ietf.org>; Thu, 31 May 2012 17:04:15 -0700 (PDT)
Received: from [192.168.0.7] (unknown [216.17.179.239]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1FB244005A; Thu, 31 May 2012 18:20:46 -0600 (MDT)
Message-ID: <4FC806FD.7050902@stpeter.im>
Date: Thu, 31 May 2012 18:04:13 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Making the Tao a web page
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <8A6D2A4F-AE0A-4770-B8BB-75FF0F43660D@cisco.com>
In-Reply-To: <8A6D2A4F-AE0A-4770-B8BB-75FF0F43660D@cisco.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.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, 01 Jun 2012 00:04:15 -0000

On 5/31/12 5:59 PM, Fred Baker wrote:
> 
> On May 31, 2012, at 4:04 PM, Paul Hoffman wrote:
> 
>> Simpler than the above: make it a web page (as Brian points out, we already have a good URL), have one editor, have one leadership person who approves non-trivial changes (I think "IETF Chair" fits here well), have a "last modified" date on it, and update it as needed. If there is consensus in the community to do this, I'm happy to take on the HTMLizing and skip the RFCizing for this round.
> 
> wfm

Me, too. And I'd volunteer to help maintain it. :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From fadi20052002@gmail.com  Thu May 31 17:28:52 2012
Return-Path: <fadi20052002@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A655C11E80BF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:28:52 -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 KSIu9C86-wmE for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:28:51 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABA611E80BB for <ietf@ietf.org>; Thu, 31 May 2012 17:28:51 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1377459lbb.31 for <ietf@ietf.org>; Thu, 31 May 2012 17:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xHVppBJmW4aeQd3mj1DjDGojHBqHNevFYDYqs0O+O84=; b=cRlyj2+9jbaNIu47Thh9W5wm2BpRnvDRfF9WQIMGym6oAhv+oWJ+ANbzkxRTcGn3gO RylmsceAQuSDEWzc5w3XyW6XesCYpFDlQqroLdR9ZWc2ujdaaSvlRPqpHoycSDx2+XY7 lo6RY4Mf9dkJbmDEY5hyafoKDLib7krtpPb362acgtvLM8BevzLQ1k3rLrI2gv6IdxNe nvOxAKo5YTldq4lVvezhUdOnyrc5cSwU3j28mr/Ua11yozRSwKk0RD/majQSPqHPav0W pcF3QMhkNhliODVyunkimCVETsAvSw/opK4W5MbWSDdFPEND6M6Ra0nbQ4yH9u3h8C05 MDig==
MIME-Version: 1.0
Received: by 10.112.43.37 with SMTP id t5mr916877lbl.89.1338510530345; Thu, 31 May 2012 17:28:50 -0700 (PDT)
Received: by 10.112.45.194 with HTTP; Thu, 31 May 2012 17:28:50 -0700 (PDT)
In-Reply-To: <4FC806FD.7050902@stpeter.im>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <8A6D2A4F-AE0A-4770-B8BB-75FF0F43660D@cisco.com> <4FC806FD.7050902@stpeter.im>
Date: Thu, 31 May 2012 20:28:50 -0400
Message-ID: <CAAHTV9PADReKBVei+mA9OCRqz4rRZ_0zUV6opbgmYhKWp0_52A@mail.gmail.com>
Subject: Re: Making the Tao a web page
From: Fadi Mohsen <fadi20052002@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=e0cb4efe344cb07c8704c15e44bf
Cc: IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2012 00:28:52 -0000

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

Awesome idea, I will be more than happy to be part of it.

On Thu, May 31, 2012 at 8:04 PM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> On 5/31/12 5:59 PM, Fred Baker wrote:
> >
> > On May 31, 2012, at 4:04 PM, Paul Hoffman wrote:
> >
> >> Simpler than the above: make it a web page (as Brian points out, we
> already have a good URL), have one editor, have one leadership person who
> approves non-trivial changes (I think "IETF Chair" fits here well), have a
> "last modified" date on it, and update it as needed. If there is consensus
> in the community to do this, I'm happy to take on the HTMLizing and skip
> the RFCizing for this round.
> >
> > wfm
>
> Me, too. And I'd volunteer to help maintain it. :)
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
>


-- 
Fadi.Mohsen

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

Awesome idea, I will be more than happy to be part of it.<div><br><div clas=
s=3D"gmail_quote">On Thu, May 31, 2012 at 8:04 PM, Peter Saint-Andre <span =
dir=3D"ltr">&lt;<a href=3D"mailto:stpeter@stpeter.im" target=3D"_blank">stp=
eter@stpeter.im</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On 5=
/31/12 5:59 PM, Fred Baker wrote:<br>
&gt;<br>
&gt; On May 31, 2012, at 4:04 PM, Paul Hoffman wrote:<br>
&gt;<br>
&gt;&gt; Simpler than the above: make it a web page (as Brian points out, w=
e already have a good URL), have one editor, have one leadership person who=
 approves non-trivial changes (I think &quot;IETF Chair&quot; fits here wel=
l), have a &quot;last modified&quot; date on it, and update it as needed. I=
f there is consensus in the community to do this, I&#39;m happy to take on =
the HTMLizing and skip the RFCizing for this round.<br>

&gt;<br>
&gt; wfm<br>
<br>
</div></div>Me, too. And I&#39;d volunteer to help maintain it. :)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
<br>
--<br>
Peter Saint-Andre<br>
<a href=3D"https://stpeter.im/" target=3D"_blank">https://stpeter.im/</a><b=
r>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Fadi.Mohsen<br>
</div>

--e0cb4efe344cb07c8704c15e44bf--

From john-ietf@jck.com  Thu May 31 17:32:18 2012
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 5C70B11E80BF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uktgkAV7fVwP for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:32:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 54E0A11E8080 for <ietf@ietf.org>; Thu, 31 May 2012 17:32:15 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SaFgx-000In9-64; Thu, 31 May 2012 20:26:11 -0400
Date: Thu, 31 May 2012 20:32:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: Making the Tao a web page
Message-ID: <DE525620890A9E2CF79769CF@PST.JCK.COM>
In-Reply-To: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2012 00:32:18 -0000

--On Thursday, May 31, 2012 16:04 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> On May 31, 2012, at 8:19 AM, John C Klensin wrote:
> 
>> (1) Establish the Tao as a modified Wiki, complete with live
>> HTML links to relevant documents and other relevant
>> discussions.. Provide some mechanism for comments to the
>> editor or even discussion that works better than the RFC
>> Errata process.  Turn maintenance of that page over to a
>> volunteer or two (ideally someone young enough to learn a lot
>> from the process) or the Secretariat.   Before someone says
>> "cost", please calculate the costs to the community of an
>> extended Last Call in which people debate details of wording.
>> 
>> (2) Appoint Paul as chair of an editorial committee with zero
>> or more additional members to be appointed at his discretion
>> subject to advice and consent of the IESG.  That committee
>> gets to consider whether to make changes.  If they get it
>> wrong, they are subject to the community's normal forms of
>> abuse and, in principle, appeals.  That could add a bit of
>> work for the IESG but I suggest only a bit and less than
>> running a Last Call.
>> 
>> (3) Replace/ obsolete RFC 4677 by a document modeled on RFC
>> 5000.  I.e., it should explain why we are maintaining the Tao
>> as one or more web pages and should provide a durable pointer
>> to how the web page can be found.

> Works for me, other than it should not be a "wiki". It should
> have one editor who takes proposed changes from the community
> the same way we do it now. Not all suggestions from this
> community, even from individuals in the leadership, are ones
> that should appear in such a document.

Paul, that is precisely what I meant by "modified Wiki" and the
editorial committee comment.  Note that I was not only proposing
appointing you (in recognition both of doing a good job and of
the status quo) but giving you discretion over whether you
wanted a committee.   If that wasn't clear, I apologize.  If it
is clear now (whether it was before or not), kumbayah.
 
> Simpler than the above: make it a web page (as Brian points
> out, we already have a good URL), have one editor, have one
> leadership person who approves non-trivial changes (I think
> "IETF Chair" fits here well), have a "last modified" date on
> it, and update it as needed. If there is consensus in the
> community to do this, I'm happy to take on the HTMLizing and
> skip the RFCizing for this round.

Wfm.  And also, I think, completely consistent with what I was
trying to suggest.  Make that "IETF Chair or designee" and you
are back to my editorial committee, modulo my desire to make you
the final authority unless extraordinary measures are taken
rather than adding to the required task list of the IETF Chair
or even the IESG more generally.

best,
   john


From sm@resistor.net  Thu May 31 17:48:02 2012
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 6F06811E80BD for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rohoivui95nj for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:48:00 -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 6DBE611E8080 for <ietf@ietf.org>; Thu, 31 May 2012 17:48: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 q510lq48019561; Thu, 31 May 2012 17:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1338511676; i=@resistor.net; bh=WOCFQY1GiZq8igFfITjEqHbnii/VtUuvxVn2ODOmDzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=smvWNkzN8+fpwGboJGEjVye8t/Hio3BMpj7yNUscbyUQQGN1WaFjIgKZp37Y5rC0/ KxXA9MDwjRM0Kh+Fj7wnYOAJw53YpLlmOHRYTNv95R86bOYOPbEXiggLOlkHBcsAg5 GcTfAjjJAfiEKgupb4J4TFzJVCxWdi+OFLqijycY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1338511676; i=@resistor.net; bh=WOCFQY1GiZq8igFfITjEqHbnii/VtUuvxVn2ODOmDzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vJm05LcO7B8TGNQY7+304cP0qau0gAJRBw1sB4MOdQRuL+9bThPD7cNsLuW3Pycsk 6QL5UBQ1U54cyry/ZtJlvBQPqAdH9Mza9Hrae+Qh4/Nzlsw/3OMsZMyWm5uWUWS1FT FJT1E1G6ysNNIQfy3HN7R2r/7wqRtD1ekVht5pxY=
Message-Id: <6.2.5.6.2.20120531173911.0b362e70@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 May 2012 17:46:25 -0700
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
Subject: Re: Making the Tao a web page
In-Reply-To: <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com> <CE474406564976FC0A885D95@PST.JCK.COM> <DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 01 Jun 2012 00:48:02 -0000

Hi Paul,
At 16:04 31-05-2012, Paul Hoffman wrote:
>needed. If there is consensus in the community to do this, I'm happy 
>to take on the HTMLizing and skip the RFCizing for this round.

I'll volunteer to help.

Regards,
-sm

P.S. To see what the Web 3.0 folks are up to, see 
http://trac.tools.ietf.org/wg/httpbis/trac/wiki  


From medel@globetel.com.ph  Thu May 31 17:58:25 2012
Return-Path: <medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD95111E80BF for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.605
X-Spam-Level: 
X-Spam-Status: No, score=-1.605 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QB8SCes4cabJ for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 17:58:25 -0700 (PDT)
Received: from smtp01.globetel.com.ph (smtp01.globetel.com.ph [203.177.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 2009411E8080 for <ietf@ietf.org>; Thu, 31 May 2012 17:58:24 -0700 (PDT)
Received: from exgtbh01.globetel.com ([10.225.208.17]) by smtp01.globetel.com.ph (8.14.4/8.14.4) with ESMTP id q510wMP3007126;  Fri, 1 Jun 2012 08:58:22 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.146]) by exgtbh01.globetel.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 1 Jun 2012 08:58:19 +0800
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Making the Tao a web page
Date: Fri, 1 Jun 2012 08:58:18 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE18A0C372@EXVSGT02.globetel.com>
In-Reply-To: <6.2.5.6.2.20120531173911.0b362e70@resistor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Making the Tao a web page
Thread-Index: Ac0/kD+TA+GlGWJ+QvCSq5581z8bggAAUdXg
X-Priority: 1
Priority: Urgent
Importance: high
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com><CE474406564976FC0A885D95@PST.JCK.COM><DAEDF66E-8FB3-4A00-846A-FECE181E2EC3@vpnc.org> <6.2.5.6.2.20120531173911.0b362e70@resistor.net>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
X-OriginalArrivalTime: 01 Jun 2012 00:58:19.0849 (UTC) FILETIME=[A2D81390:01CD3F91]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7580, 1.0.260, 0.0.0000 definitions=2012-05-31_07:2012-05-21, 2012-05-31, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1205310306
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, 01 Jun 2012 00:58:25 -0000

Wish come true...

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
SM
Sent: Friday, June 01, 2012 8:46 AM
To: Paul Hoffman
Cc: IETF discussion list
Subject: Re: Making the Tao a web page

Hi Paul,
At 16:04 31-05-2012, Paul Hoffman wrote:
>needed. If there is consensus in the community to do this, I'm happy=20
>to take on the HTMLizing and skip the RFCizing for this round.

I'll volunteer to help.

Regards,
-sm

P.S. To see what the Web 3.0 folks are up to, see=20
http://trac.tools.ietf.org/wg/httpbis/trac/wiki=20=20

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

From johnl@iecc.com  Thu May 31 18:37:06 2012
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 4693811E80D0 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 18:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.734
X-Spam-Level: 
X-Spam-Status: No, score=-110.734 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJ3PXojo3YX5 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 18:37:04 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2CA11E8074 for <ietf@ietf.org>; Thu, 31 May 2012 18:37:03 -0700 (PDT)
Received: (qmail 51753 invoked from network); 1 Jun 2012 01:37:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 1 Jun 2012 01:37:02 -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:vbr-info; s=4fc81cbe.xn--3zv.k1205; i=johnl@user.iecc.com; bh=q6REeqhc/orfsSvcXstQDjOsnElEgs0DpPPaYs3QHpU=; b=HPX8pT97QRDZmECylu+NsHtkPl4HDaHjtVt/k4ymOaCC8GXBDeTvbFcxPY21O59C7pQy9oDF/0ZY+k6MyMhkPsCZAfTIsG4glAaOQBi9oJo4cKEWQrr1efiC7z6gtpS8M/pyZO41suVd80NnOlNrDepMcWW0x1xFwCCmNn2mkmQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 1 Jun 2012 01:36:40 -0000
Message-ID: <20120601013640.36907.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Colloquial language [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of IETF: A Novice's Guide to the Internet Engineering Task Force) to Informational RFC]
In-Reply-To: <4FC7F43C.6010609@bogus.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
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, 01 Jun 2012 01:37:06 -0000

>Do we spell Standardization with and s or a z?

Yez.

R's,
John

From thierry.moreau@connotech.com  Thu May 31 19:51:36 2012
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 F407721F84B2 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 19:51: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 YwFC4YYNycou for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 19:51:35 -0700 (PDT)
Received: from mail.connotech.com (unknown [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7295411E80E4 for <ietf@ietf.org>; Thu, 31 May 2012 19:51:35 -0700 (PDT)
Received: from [192.168.1.200] (unknown [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id BA2B7308FB; Fri,  1 Jun 2012 03:30:39 -0400 (EDT)
Message-ID: <4FC82EA2.4000406@connotech.com>
Date: Thu, 31 May 2012 22:53:22 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20090608)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IANA [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of	IETF: A Novice's Guide to the Internet Engineering Task Force)	to	Informational RFC]
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120530214914.094ac8d0@resistor.net> <4FC79FF0.9010001@gmail.com>
In-Reply-To: <4FC79FF0.9010001@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.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: Fri, 01 Jun 2012 02:51:36 -0000

Brian E Carpenter wrote:
> On 2012-05-31 09:24, SM wrote:
> 
> ...
>> In Section 3.2.3:
>>
>>   "Approves the appointment of the IANA"
>>
>> Isn't IANA more of a U.S. Government decision? 
> 
> The IAB decides who acts as the IETF's IANA. RFC 2860 again.
> 
>   Brian
> 

See e.g.

http://ntia.doc.gov/page/iana-functions-purchase-order

-- 
- Thierry Moreau


From heard@pobox.com  Thu May 31 20:08:58 2012
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90C9F11E80EE for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 20:08: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 UsN3DAQuAk5d for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 20:08:57 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62E211E8072 for <ietf@ietf.org>; Thu, 31 May 2012 20:08:57 -0700 (PDT)
Received: (qmail 3320 invoked from network); 31 May 2012 20:08:57 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 31 May 2012 20:08:57 -0700
Date: Thu, 31 May 2012 20:08:57 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
In-Reply-To: <20120531143816.30508.66250.idtracker@ietfa.amsl.com>
Message-ID: <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2012 03:08:58 -0000

On Thu, 31 May 2012, The IESG wrote:

> The IESG has received a request from the Internet Area Working Group WG
> (intarea) to consider the following document:
> - 'Updated Specification of the IPv4 ID Field'
>   <draft-ietf-intarea-ipv4-id-update-05.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 2012-06-14. 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.

I commented on the previous version of this draft during WG last 
call (as a WG non-member) and supported its publication then.  I 
have looked over the changes in the present version and continue to 
support its publication.  I believe that it addresses an operational 
deficiency in current IPv4 specifications and largely codifies 
existing pactice.

My one reservation is that I do not think it is strictly necessary 
to ban re-use of the IPv4 ID value in retransmitted non-atomic IPv4 
datagrams.  On the other hand, the evidence available to me suggests 
that existing implementations overwhelmingly comply with this ban 
anyway, so it does not seem to do any harm.

Regards,

C. M. Heard

From fred@cisco.com  Thu May 31 21:39:51 2012
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 2758721F8460 for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 21:39:51 -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 q+Gr7FWgHV8o for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 21:39:49 -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 7DBF021F845F for <ietf@ietf.org>; Thu, 31 May 2012 21:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=556; q=dns/txt; s=iport; t=1338525589; x=1339735189; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=XcFyuIBbC9kLHa4p/TJliVfRi2vd/wf9gNvW1pWfDuA=; b=FLadhmP5f2ZwtF0oDNQVpn1MUN/PD+/qU/LMUbiQe00rKnpI9fwF3JaW HcWn/VY4rD4WoEjGqgOdrxZ9R2hTqNNTiNuoYfONmKUFfL9GwX/tb1v+y j4IttrcsDMC8yMxLad3TFJELC2GwW1QAfZ/+/rwQlgolApbk2D+BLmU8X k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAApHyE+tJV2a/2dsb2JhbABEtC+BB4IYAQEBAwESASc/BQsLGCMLVwY1h2QFC5hvn1qLEYUVYAOIQIxZgQ+EQIg/gWaDAA
X-IronPort-AV: E=Sophos;i="4.75,695,1330905600"; d="scan'208";a="88523959"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 01 Jun 2012 04:39:49 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q514des6008428;  Fri, 1 Jun 2012 04:39:48 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 31 May 2012 21:39:48 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 31 May 2012 21:39:48 -0700
Subject: Re: IANA [Re: Last Call: <draft-hoffman-tao4677bis-15.txt> (The Tao of	IETF: A Novice's Guide to the Internet Engineering Task Force)	to	Informational RFC]
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4FC82EA2.4000406@connotech.com>
Date: Thu, 31 May 2012 21:38:42 -0700
Message-Id: <E583EE89-5772-4E85-AFDF-49E2C3ADEAC2@cisco.com>
References: <20120530225655.19475.74871.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120530214914.094ac8d0@resistor.net> <4FC79FF0.9010001@gmail.com> <4FC82EA2.4000406@connotech.com>
To: Thierry Moreau <thierry.moreau@connotech.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.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: Fri, 01 Jun 2012 04:39:51 -0000

On May 31, 2012, at 7:53 PM, Thierry Moreau wrote:

> Brian E Carpenter wrote:
>> On 2012-05-31 09:24, SM wrote:
>> ...
>>> In Section 3.2.3:
>>>=20
>>>  "Approves the appointment of the IANA"
>>>=20
>>> Isn't IANA more of a U.S. Government decision?=20
>> The IAB decides who acts as the IETF's IANA. RFC 2860 again.
>>  Brian
>=20
> See e.g.
>=20
> http://ntia.doc.gov/page/iana-functions-purchase-order

You're correct that NTIA wants to pay someone to do the "protocol =
parameter" job. The IAB can decide to not use that office.=

From narten@us.ibm.com  Thu May 31 21:54:21 2012
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 A7F5021F851B for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 21:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.449
X-Spam-Level: 
X-Spam-Status: No, score=-109.449 tagged_above=-999 required=5 tests=[AWL=1.150, 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 NsvwJ9BOjYXJ for <ietf@ietfa.amsl.com>; Thu, 31 May 2012 21:54:20 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 7061A21F851A for <ietf@ietf.org>; Thu, 31 May 2012 21:54:19 -0700 (PDT)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 31 May 2012 22:54:19 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 31 May 2012 22:53:51 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 6AD2E3E4004C for <ietf@ietf.org>; Fri,  1 Jun 2012 04:53:50 +0000 (WET)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q514rJu6048846 for <ietf@ietf.org>; Thu, 31 May 2012 22:53:34 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q514r4Op021537 for <ietf@ietf.org>; Thu, 31 May 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q514r3Lk021526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 31 May 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q514r3SH032220 for <ietf@ietf.org>; Fri, 1 Jun 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q514r24V032173 for ietf@ietf.org; Fri, 1 Jun 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201206010453.q514r24V032173@rotala.raleigh.ibm.com>
Date: Fri, 01 Jun 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12060104-2398-0000-0000-0000071BA4F6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2012 04:54:21 -0000

Total of 76 messages in the last 7 days.
 
script run at: Fri Jun  1 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.84% |    9 | 10.55% |    60521 | brian.e.carpenter@gmail.com
  6.58% |    5 |  4.99% |    28656 | bortzmeyer@nic.fr
  5.26% |    4 |  5.11% |    29344 | hartmans-ietf@mit.edu
  5.26% |    4 |  4.92% |    28206 | john-ietf@jck.com
  3.95% |    3 |  2.93% |    16803 | stpeter@stpeter.im
  1.32% |    1 |  5.43% |    31182 | bclaise@cisco.com
  1.32% |    1 |  5.13% |    29420 | ron.even.tlv@gmail.com
  2.63% |    2 |  3.35% |    19220 | sm@resistor.net
  2.63% |    2 |  2.54% |    14594 | ole@cisco.com
  2.63% |    2 |  2.39% |    13720 | ynir@checkpoint.com
  2.63% |    2 |  2.29% |    13169 | paul.hoffman@vpnc.org
  2.63% |    2 |  2.01% |    11525 | dhc@dcrocker.net
  2.63% |    2 |  1.94% |    11147 | simon.perreault@viagenie.ca
  2.63% |    2 |  1.81% |    10366 | johnl@iecc.com
  2.63% |    2 |  1.66% |     9540 | jnc@mercury.lcs.mit.edu
  1.32% |    1 |  2.40% |    13754 | turners@ieca.com
  1.32% |    1 |  2.21% |    12707 | lear@cisco.com
  1.32% |    1 |  2.09% |    12016 | gtw@gtwassociates.com
  1.32% |    1 |  2.08% |    11949 | ietfdbh@comcast.net
  1.32% |    1 |  1.91% |    10932 | fluffy@iii.ca
  1.32% |    1 |  1.59% |     9123 | mehmet.ersue@nsn.com
  1.32% |    1 |  1.46% |     8382 | klaas@cisco.com
  1.32% |    1 |  1.46% |     8360 | narten@us.ibm.com
  1.32% |    1 |  1.40% |     8049 | stephen.farrell@cs.tcd.ie
  1.32% |    1 |  1.36% |     7801 | fadi20052002@gmail.com
  1.32% |    1 |  1.36% |     7797 | basavaraj.patil@nokia.com
  1.32% |    1 |  1.35% |     7738 | ben@nostrum.com
  1.32% |    1 |  1.31% |     7531 | msk@cloudmark.com
  1.32% |    1 |  1.31% |     7489 | dromasca@avaya.com
  1.32% |    1 |  1.21% |     6922 | melinda.shore@gmail.com
  1.32% |    1 |  1.17% |     6697 | medel@globetel.com.ph
  1.32% |    1 |  1.15% |     6583 | scott.brim@gmail.com
  1.32% |    1 |  1.10% |     6334 | dcrocker@bbiw.net
  1.32% |    1 |  1.10% |     6288 | fred@cisco.com
  1.32% |    1 |  1.09% |     6240 | housley@vigilsec.com
  1.32% |    1 |  1.07% |     6112 | iad@ietf.org
  1.32% |    1 |  1.06% |     6094 | rbarnes@bbn.com
  1.32% |    1 |  1.06% |     6066 | nick@inex.ie
  1.32% |    1 |  1.06% |     6064 | tbray@textuality.com
  1.32% |    1 |  1.04% |     5976 | faber@isi.edu
  1.32% |    1 |  1.02% |     5826 | heard@pobox.com
  1.32% |    1 |  1.00% |     5767 | joelja@bogus.com
  1.32% |    1 |  0.97% |     5567 | peter@akayla.com
  1.32% |    1 |  0.96% |     5490 | mrex@sap.com
  1.32% |    1 |  0.95% |     5468 | ben@niven-jenkins.co.uk
  1.32% |    1 |  0.93% |     5338 | dhc2@dcrocker.net
  1.32% |    1 |  0.89% |     5080 | thierry.moreau@connotech.com
  1.32% |    1 |  0.85% |     4883 | malcolm.betts@zte.com.cn
--------+------+--------+----------+------------------------
100.00% |   76 |100.00% |   573836 | Total

