
From mbeaulieu@amsl.com  Thu Aug  1 02:39:30 2013
Return-Path: <mbeaulieu@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DEB11E8106; Thu,  1 Aug 2013 02:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.705
X-Spam-Level: 
X-Spam-Status: No, score=-1.705 tagged_above=-999 required=5 tests=[AWL=-0.595, BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVw8L2-o2m7z; Thu,  1 Aug 2013 02:39:23 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 23B4121F9FDE; Thu,  1 Aug 2013 02:39:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id CBE36A609C; Thu,  1 Aug 2013 02:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rEavSE0S9wa; Thu,  1 Aug 2013 02:39:06 -0700 (PDT)
Received: from dhcp-10ce.meeting.ietf.org (dhcp-10ce.meeting.ietf.org [130.129.16.206]) by c9a.amsl.com (Postfix) with ESMTPA id 3A4F89FB96; Thu,  1 Aug 2013 02:39:05 -0700 (PDT)
From: Marcia Beaulieu <mbeaulieu@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF 87 - 2nd Floor Meeting Rooms
Date: Thu, 1 Aug 2013 11:39:15 +0200
Message-Id: <14EC4368-93B5-4543-A771-58E3E91801CC@amsl.com>
To: wgchairs@ietf.org, IESG IESG <iesg@ietf.org>, iab@iab.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: Allison Mankin <amankin@verisign.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:39:30 -0000

Rooms: Rook, Chess, Bishop

Please note that to close the doors to these rooms (if the door is being =
held open by the magnetic mechanism), please release the door by pushing =
the red button located near the door.

Thank you.
Marcia


From jhaas@slice.pfrc.org  Thu Aug  1 02:50:25 2013
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBD321F99E9 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 02:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.038, 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 BDZXbv7T0OzW for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 02:50:20 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF5B21F9F95 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 02:50:16 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 1B660C28E; Thu,  1 Aug 2013 05:50:16 -0400 (EDT)
Date: Thu, 1 Aug 2013 05:50:16 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "\"Martin J. D??rst\"" <duerst@it.aoyama.ac.jp>
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
Message-ID: <20130801095016.GB12720@pfrc>
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com> <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com> <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82@CVA-MB002.centreville.ads.sparta.com> <20130731092605.GA29173@pfrc> <20130731102503.GS23086@x28.adm.denic.de> <51F8EC91.50209@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F8EC91.50209@it.aoyama.ac.jp>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:50:25 -0000

On Wed, Jul 31, 2013 at 07:53:05PM +0900, "Martin J. D??rst" wrote:
> >so, do resist accepting offers from active participants (known in advance)
> >unless you consider this a feature, or, what has worked for my/our wg, look
> >for two scribes who can backup each other.
> 
> Or allow the jabber scribe to channel somebody, and then also give
> his own comment, without having to stand in line (twice). That way,
> we might get more Jabber scribes.

^ That

A significant number of scribes end up being "the usual ietf volunteers".
This is consistent with how most volunteer-run organizations operate.

-- Jeff

From presnick@qti.qualcomm.com  Thu Aug  1 04:28:46 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E2821F9F44 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.379
X-Spam-Level: 
X-Spam-Status: No, score=-102.379 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWVpDQ1CPZuD for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:28:42 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id D9C8821F9AB3 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1375356521; x=1406892521; h=message-id:date:from:mime-version:to:cc:subject: content-transfer-encoding; bh=PHJYt+wCM286IJtWFkNT/4MSQzXmHzdONQDeub0euc0=; b=PBfBfv30mtOlTk9DAbZZLM1KSKyBERzNVOuW6d30VmcSBfxwDFup6Yqy NYgIGzZA0I4BynqAV/l3DwtihS+HPXfiqeVmGglmtX2jM6v77P1F9qcya etmkfFwYXe8+pvT5EHqV2Ej1DW3SYNXsbuvt+YzuKYpSOj7mmWsS2Kvx5 M=;
X-IronPort-AV: E=Sophos;i="4.89,793,1367996400"; d="scan'208";a="48614082"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth01.qualcomm.com with ESMTP; 01 Aug 2013 04:28:36 -0700
X-IronPort-AV: E=Sophos;i="4.89,793,1367996400"; d="scan'208";a="577350019"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Aug 2013 04:28:36 -0700
Received: from dhcp-2530.meeting.ietf.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 1 Aug 2013 04:28:36 -0700
Message-ID: <51FA4662.4050404@qti.qualcomm.com>
Date: Thu, 1 Aug 2013 13:28:34 +0200
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Successful BOF Sessions (RFC 5434) - Missing piece?
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Thomas Narten <narten@us.ibm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:28:46 -0000

I considered posting to the IETF main list, but I thought I'd start a 
bit smaller.

Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434 
that surprised me:

    ...the goal of the BOF is to demonstrate that the community has
    agreement that:

       - there is a problem that needs solving, and the IETF is the right
         group to attempt solving it.

       - there is a critical mass of participants willing to work on the
         problem (e.g., write drafts, review drafts, etc.).

       - the scope of the problem is well defined and understood, that
         is, people generally understand what the WG will work on (and
         what it won't) and what its actual deliverables will be.

       - there is agreement that the specific deliverables (i.e.,
         proposed documents) are the right set.

       - it is believed that the WG has a reasonable probability of
         having success (i.e., in completing the deliverables in its
         charter in a timely fashion).

It seemed to me that there was a serious omission from this list:

    - it is believed that there a critical mass of implementers who will
      use the output of the working group.

In fact, I couldn't find the word "implement" anywhere in the document. 
Do we just assume implementers but don't mention them, or (and I hope 
this is not the case) do we really think that it is an irrelevant 
question to consider regarding a successful BOF?

pr

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


From presnick@qti.qualcomm.com  Thu Aug  1 04:41:52 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE68E21F9E44 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fw1wCEg4xqbD for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:41:48 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 08AB021F9CC8 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:41:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1375357308; x=1406893308; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=8wg42mgDV0wVT9VWAjBW0jEUwNAk4T6KIYI6CYjng+4=; b=yfEP/vMmhjDhBttXBLwOCgsTQIxGCo6Sq1Hqugs2Y69i27rVF1bYWbzy /bhGiOL4eThB4/mRUVat4k66zaYz4rqQ28rhXMt0NRixSUNa7ZUsig3T4 2cI7fcOw0k+aEJgY8BljtEt6Qjbe/R5UR3QCczpr9aLc5drntGOeO81ER M=;
X-IronPort-AV: E=Sophos;i="4.89,793,1367996400"; d="scan'208";a="48720971"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 01 Aug 2013 04:41:46 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Aug 2013 04:41:46 -0700
Received: from dhcp-2530.meeting.ietf.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 1 Aug 2013 04:41:46 -0700
Message-ID: <51FA4978.2020502@qti.qualcomm.com>
Date: Thu, 1 Aug 2013 13:41:44 +0200
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
References: <51FA4662.4050404@qti.qualcomm.com>
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Thomas Narten <narten@us.ibm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:41:52 -0000

On 8/1/13 1:28 PM, Pete Resnick wrote:
> ...a critical mass of implementers...

And of course I was reminded offline that I forgot about "operators", 
who are also the consumers of our output. I'm such an apps guy. :-[

pr

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


From ted.ietf@gmail.com  Thu Aug  1 04:42:21 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C9D21E809A for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TgnJoPrPimrn for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:42:21 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 8A08321F8EC2 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:42:14 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id eh20so3685588obb.29 for <wgchairs@ietf.org>; Thu, 01 Aug 2013 04:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WoQDiTIwP3jY7P9G2mj7cN2sz/1JukEa6OwnKQg9bLs=; b=Z3bGAzbOsmkg55yQu0ve5Tx5/y1TwIYLMxRbpJIeWKfD7iOHal2Rrg+DkrfxKleGPG CCge4aVfS+ow9oLHTw1PASWNdAIywxUTgMZEUAm6oDLdokOFuF2HQ3ILAuL7C51FSnDR mkWalMu7r88CNT5UI+/rOkZEgHw/+SxvP05i4X8HT+nzVaqFx1aB7y4barG64CKmm2ps flMWH8rbsxqv2+f9rCtQxGCFBLbBURGM6S3a+kZUxpiGP7Fa2ZjCjVjRFzAJ68jwJWIf w2xCmmGocco0urgVDJL8cQsIfnL/QXbxGX0RlilEAQn+dNrfjYJTHYnyBWo4dagzeAN/ p28w==
MIME-Version: 1.0
X-Received: by 10.50.164.167 with SMTP id yr7mr140567igb.22.1375357328147; Thu, 01 Aug 2013 04:42:08 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Thu, 1 Aug 2013 04:42:08 -0700 (PDT)
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
References: <51FA4662.4050404@qti.qualcomm.com>
Date: Thu, 1 Aug 2013 13:42:08 +0200
Message-ID: <CA+9kkMDx+daex2ia2C=i7LCdMQtxHUsZ1KSmgqEci1YBbTKesQ@mail.gmail.com>
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
From: Ted Hardie <ted.ietf@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e0122a7fcfc191c04e2e15494
Cc: Thomas Narten <narten@us.ibm.com>, WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:42:21 -0000

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

Sorry for top posting, but I believe you are missing the idea that BoFs can
be on topics related to operational practice.  You are looking for "is
there a community that will *use* the results of the work", of which
implementors are a potential class.

regards,

Ted

On Thu, Aug 1, 2013 at 1:28 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> I considered posting to the IETF main list, but I thought I'd start a bit
> smaller.
>
> Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434
> that surprised me:
>
>    ...the goal of the BOF is to demonstrate that the community has
>    agreement that:
>
>       - there is a problem that needs solving, and the IETF is the right
>         group to attempt solving it.
>
>       - there is a critical mass of participants willing to work on the
>         problem (e.g., write drafts, review drafts, etc.).
>
>       - the scope of the problem is well defined and understood, that
>         is, people generally understand what the WG will work on (and
>         what it won't) and what its actual deliverables will be.
>
>       - there is agreement that the specific deliverables (i.e.,
>         proposed documents) are the right set.
>
>       - it is believed that the WG has a reasonable probability of
>         having success (i.e., in completing the deliverables in its
>         charter in a timely fashion).
>
> It seemed to me that there was a serious omission from this list:
>
>    - it is believed that there a critical mass of implementers who will
>      use the output of the working group.
>
> In fact, I couldn't find the word "implement" anywhere in the document. Do
> we just assume implementers but don't mention them, or (and I hope this is
> not the case) do we really think that it is an irrelevant question to
> consider regarding a successful BOF?
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.**com/~presnick/<http://www.qualcomm.com/~presnick/>
> >
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

Sorry for top posting, but I believe you are missing the idea that BoFs can=
 be on topics related to operational practice.=A0 You are looking for &quot=
;is there a community that will *use* the results of the work&quot;, of whi=
ch implementors are a potential class.<br>
<br>regards,<br><br>Ted<br><br><div class=3D"gmail_quote">On Thu, Aug 1, 20=
13 at 1:28 PM, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnic=
k@qti.qualcomm.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I considered posting to the IETF main list, =
but I thought I&#39;d start a bit smaller.<br>
<br>
Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434 th=
at surprised me:<br>
<br>
=A0 =A0...the goal of the BOF is to demonstrate that the community has<br>
=A0 =A0agreement that:<br>
<br>
=A0 =A0 =A0 - there is a problem that needs solving, and the IETF is the ri=
ght<br>
=A0 =A0 =A0 =A0 group to attempt solving it.<br>
<br>
=A0 =A0 =A0 - there is a critical mass of participants willing to work on t=
he<br>
=A0 =A0 =A0 =A0 problem (e.g., write drafts, review drafts, etc.).<br>
<br>
=A0 =A0 =A0 - the scope of the problem is well defined and understood, that=
<br>
=A0 =A0 =A0 =A0 is, people generally understand what the WG will work on (a=
nd<br>
=A0 =A0 =A0 =A0 what it won&#39;t) and what its actual deliverables will be=
.<br>
<br>
=A0 =A0 =A0 - there is agreement that the specific deliverables (i.e.,<br>
=A0 =A0 =A0 =A0 proposed documents) are the right set.<br>
<br>
=A0 =A0 =A0 - it is believed that the WG has a reasonable probability of<br=
>
=A0 =A0 =A0 =A0 having success (i.e., in completing the deliverables in its=
<br>
=A0 =A0 =A0 =A0 charter in a timely fashion).<br>
<br>
It seemed to me that there was a serious omission from this list:<br>
<br>
=A0 =A0- it is believed that there a critical mass of implementers who will=
<br>
=A0 =A0 =A0use the output of the working group.<br>
<br>
In fact, I couldn&#39;t find the word &quot;implement&quot; anywhere in the=
 document. Do we just assume implementers but don&#39;t mention them, or (a=
nd I hope this is not the case) do we really think that it is an irrelevant=
 question to consider regarding a successful BOF?<span class=3D"HOEnZb"><fo=
nt color=3D"#888888"><br>

<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</font></span></blockquote></div><br>

--089e0122a7fcfc191c04e2e15494--

From dromasca@avaya.com  Thu Aug  1 04:45:00 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF16311E8113 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.443
X-Spam-Level: 
X-Spam-Status: No, score=-103.443 tagged_above=-999 required=5 tests=[AWL=0.156, 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 fF8LgxVv-XcI for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:44:55 -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 095A711E8112 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:44:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0HAGNJ+lGHCzI1/2dsb2JhbABYAxaCTyE1UKpBlAaBHxZ0giQBAQEBAxIoPwwEAgEIDQEDBAEBCxQJBzIUCQgCBAENBQgMDoduAQudKpt8F49WIRAHBguDCHMDniaLB4MUgio
X-IronPort-AV: E=Sophos;i="4.89,793,1367985600"; d="scan'208";a="21909496"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 01 Aug 2013 07:44:53 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 01 Aug 2013 07:38:19 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0146.000; Thu, 1 Aug 2013 13:44:52 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, WG Chairs <wgchairs@ietf.org>
Subject: RE: Successful BOF Sessions (RFC 5434) - Missing piece?
Thread-Topic: Successful BOF Sessions (RFC 5434) - Missing piece?
Thread-Index: AQHOjqpkikaamfkZKEWiy7X94DLEs5mAOnbA
Date: Thu, 1 Aug 2013 11:44:51 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA12894518@AZ-FFEXMB04.global.avaya.com>
References: <51FA4662.4050404@qti.qualcomm.com>
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:45:00 -0000

+1 and + more, because I am missing at least another two words beyond 'impl=
ement' in this text, and these are 'deploy' and 'use'.=20

I guess that in the intention of the authors of RFC 5434 these words are hi=
dden behind the etc. in (e.g., write drafts, review drafts, etc.)

I believe that these should be made explicit.=20

Dan




> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Pete Resnick
> Sent: Thursday, August 01, 2013 2:29 PM
> To: WG Chairs
> Cc: Thomas Narten
> Subject: Successful BOF Sessions (RFC 5434) - Missing piece?
>=20
> I considered posting to the IETF main list, but I thought I'd start a
> bit smaller.
>=20
> Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434
> that surprised me:
>=20
>     ...the goal of the BOF is to demonstrate that the community has
>     agreement that:
>=20
>        - there is a problem that needs solving, and the IETF is the
> right
>          group to attempt solving it.
>=20
>        - there is a critical mass of participants willing to work on the
>          problem (e.g., write drafts, review drafts, etc.).
>=20
>        - the scope of the problem is well defined and understood, that
>          is, people generally understand what the WG will work on (and
>          what it won't) and what its actual deliverables will be.
>=20
>        - there is agreement that the specific deliverables (i.e.,
>          proposed documents) are the right set.
>=20
>        - it is believed that the WG has a reasonable probability of
>          having success (i.e., in completing the deliverables in its
>          charter in a timely fashion).
>=20
> It seemed to me that there was a serious omission from this list:
>=20
>     - it is believed that there a critical mass of implementers who will
>       use the output of the working group.
>=20
> In fact, I couldn't find the word "implement" anywhere in the document.
> Do we just assume implementers but don't mention them, or (and I hope
> this is not the case) do we really think that it is an irrelevant
> question to consider regarding a successful BOF?
>=20
> pr
>=20
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478


From ietfdbh@comcast.net  Thu Aug  1 04:49:48 2013
Return-Path: <ietfdbh@comcast.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8AD21F9A38 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.3
X-Spam-Level: 
X-Spam-Status: No, score=-100.3 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5r9MvnvT6bkw for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:49:42 -0700 (PDT)
Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:64]) by ietfa.amsl.com (Postfix) with ESMTP id B7A2B21F9967 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:49:42 -0700 (PDT)
Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta07.emeryville.ca.mail.comcast.net with comcast id 7Pnj1m0030vp7WLA7Pphwu; Thu, 01 Aug 2013 11:49:41 +0000
Received: from [130.129.70.183] ([130.129.70.183]) by omta05.emeryville.ca.mail.comcast.net with comcast id 7PpQ1m0053xFRL28RPpTgF; Thu, 01 Aug 2013 11:49:39 +0000
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Thu, 01 Aug 2013 13:49:22 +0200
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
From: David Harrington <ietfdbh@comcast.net>
To: Pete Resnick <presnick@qti.qualcomm.com>, WG Chairs <wgchairs@ietf.org>
Message-ID: <CE2015D5.2F37D%ietfdbh@comcast.net>
Thread-Topic: Successful BOF Sessions (RFC 5434) - Missing piece?
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1375357781; bh=l2BeQfIPHV/fHWTAMQfyGzEeqEQgMsB2+toKAGCdxyQ=; h=Received:Received:Date:Subject:From:To:Message-ID:Mime-version: Content-type; b=X6u9zT5kOVWAM0wvE/fkB8dt5W5ZQKfVuO3vnqWVDyXzrA/AjWgcrquNZ2qgVDxu2 vKZ/g47C60Nc9UW2ZSTbIdU50HL7z/PXrSyWMlrd2HxQN7Sv1CSbqypLUF3+ce4jNi cuEMxfK7j00ictVjloBSFUelQOep6XwZakovKnxMsXKDV6NcmVmrQOXV3TvITiSNr6 /pt8Wo9Ygtik+bA6cEocFtpfBD2dtdjzbl/Him/AtS6GPPQuJPMcVk5EP4SQ4e9rYx dRLy+fgNc+BxH9Zn2HTrU4+W3kheATnUDSF6+I/AoV1XPoQifIcH0w+fCU/ll2PbFb O4rbZrfGUqtDg==
Cc: Thomas Narten <narten@us.ibm.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:49:48 -0000

How do we measure critical mass?
I think that critical mass typically means commercial products include
implementations and are shipped to customers (I.e., there is running code).
I'm not sure that WG participants necessarily have the authority to
promise implementations.
I think that "the right set" item might imply that implementations would
follow. 
--
David Harrington
Ietfdbh@comcast.net
+1-603-828-1401





On 8/1/13 1:28 PM, "Pete Resnick" <presnick@qti.qualcomm.com> wrote:

>I considered posting to the IETF main list, but I thought I'd start a
>bit smaller.
>
>Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434
>that surprised me:
>
>    ...the goal of the BOF is to demonstrate that the community has
>    agreement that:
>
>       - there is a problem that needs solving, and the IETF is the right
>         group to attempt solving it.
>
>       - there is a critical mass of participants willing to work on the
>         problem (e.g., write drafts, review drafts, etc.).
>
>       - the scope of the problem is well defined and understood, that
>         is, people generally understand what the WG will work on (and
>         what it won't) and what its actual deliverables will be.
>
>       - there is agreement that the specific deliverables (i.e.,
>         proposed documents) are the right set.
>
>       - it is believed that the WG has a reasonable probability of
>         having success (i.e., in completing the deliverables in its
>         charter in a timely fashion).
>
>It seemed to me that there was a serious omission from this list:
>
>    - it is believed that there a critical mass of implementers who will
>      use the output of the working group.
>
>In fact, I couldn't find the word "implement" anywhere in the document.
>Do we just assume implementers but don't mention them, or (and I hope
>this is not the case) do we really think that it is an irrelevant
>question to consider regarding a successful BOF?
>
>pr
>
>-- 
>Pete Resnick<http://www.qualcomm.com/~presnick/>
>Qualcomm Technologies, Inc. - +1 (858)651-4478
>



From presnick@qti.qualcomm.com  Thu Aug  1 04:58:00 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B236421F9C01 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 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 5N7fSWAyauQ9 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 04:57:47 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6311E21F9DE9 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 04:57:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1375358265; x=1406894265; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WwdUmxTW3w/iLVfndFWosMv8bn30nMatOAzePA3wceY=; b=hUalaYNlU6TWxnVaSWel2q8v2ZpPKJV76BM8XmJjOp4R/2UU1+k6FBbS mnTD0j9Rw31dZBIx1M8S5qhUzvliiQGPUwm1eHInk5lUllsj96t/HhADA tW8q9fq+DT5jyiOqQQvBGjaf3W81Qo9AzLDX7ldN14zEY8d8RFyP2A6Kb g=;
X-IronPort-AV: E=Sophos;i="4.89,793,1367996400"; d="scan'208";a="48615189"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 01 Aug 2013 04:57:44 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Aug 2013 04:57:44 -0700
Received: from dhcp-2530.meeting.ietf.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 1 Aug 2013 04:57:43 -0700
Message-ID: <51FA4D35.5050501@qti.qualcomm.com>
Date: Thu, 1 Aug 2013 13:57:41 +0200
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
References: <CE2015D5.2F37D%ietfdbh@comcast.net>
In-Reply-To: <CE2015D5.2F37D%ietfdbh@comcast.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Thomas Narten <narten@us.ibm.com>, WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:58:00 -0000

On 8/1/13 1:49 PM, David Harrington wrote:
> How do we measure critical mass?
> I think that critical mass typically means commercial products include
> implementations and are shipped to customers (I.e., there is running code).
> I'm not sure that WG participants necessarily have the authority to
> promise implementations.
>    

It depends on the technology. For some (again, I'm such an apps guy), 
the implementers had better be in the room themselves. With others it 
might be an educated guess on potential for consumers of the technology, 
be it "the people writing code back at my office" or "the operators who 
I'm pretty sure will use this knob if I give it to them". But my gut was 
that it should be explicitly thought about during the BOF.

> I think that "the right set" item might imply that implementations would
> follow.
>    

It wasn't clear to me that it was. That's why I asked.

pr

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


From tjc@ecs.soton.ac.uk  Thu Aug  1 06:50:25 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1590C21E8110 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 06:50: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 e23DwRyge8zy for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 06:50:17 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA5021E813F for <wgchairs@ietf.org>; Thu,  1 Aug 2013 06:49:57 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r71DnhQN022968; Thu, 1 Aug 2013 14:49:43 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r71DnhQN022968
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1375364983; bh=FaPzCZn8bexse9gPdy+N1R9aFrw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=saJG87T6rvhZEeoYArB2B7MRQZDWSJz+G/4UnYjFXFXO1cKVQUk0AxIMB60Nup8CO LXc+ooMTY/HR4ARwGOg3J2T9Q6ymQFmvmDlLUQ53plfRNlCWyW7CoPMxTC0kEopsE0 VkD4Noz/8zvy7P3GpHYevP2qac8ysq3iu0OH77l8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p70Eng0544503237ok ret-id none; Thu, 01 Aug 2013 14:49:43 +0100
Received: from [IPv6:2001:df8::16:600e:43bf:a14f:8ff9] ([IPv6:2001:df8:0:16:600e:43bf:a14f:8ff9]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r71DncSc020717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Aug 2013 14:49:39 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
Date: Thu, 1 Aug 2013 14:49:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|616670d51e61afb192928ef7848da851p70Eng03tjc|ecs.soton.ac.uk|2C7ED32B-DC69-449B-8A19-B5EB74BF57CB@ecs.soton.ac.uk>
References: <51FA4662.4050404@qti.qualcomm.com> <2C7ED32B-DC69-449B-8A19-B5EB74BF57CB@ecs.soton.ac.uk>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p70Eng054450323700; tid=p70Eng0544503237ok; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r71DnhQN022968
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Thomas Narten <narten@us.ibm.com>, WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 13:50:25 -0000

On 1 Aug 2013, at 12:28, Pete Resnick <presnick@qti.qualcomm.com> wrote:

> I considered posting to the IETF main list, but I thought I'd start a =
bit smaller.
>=20
> Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC =
5434 that surprised me:
>=20
>   ...the goal of the BOF is to demonstrate that the community has
>   agreement that:
>=20
>      - there is a problem that needs solving, and the IETF is the =
right
>        group to attempt solving it.
>=20
>      - there is a critical mass of participants willing to work on the
>        problem (e.g., write drafts, review drafts, etc.).
=85.
>=20
> It seemed to me that there was a serious omission from this list:
>=20
>   - it is believed that there a critical mass of implementers who will
>     use the output of the working group.
>=20
> In fact, I couldn't find the word "implement" anywhere in the =
document. Do we just assume implementers but don't mention them, or (and =
I hope this is not the case) do we really think that it is an irrelevant =
question to consider regarding a successful BOF?

This is a fair question.  I think it's implicit in "there is a problem =
that needs solving" and "there is a critical mass of participats willing =
to work on the problem" but perhaps it could be made more explicit.

In the case of dnssdext we are aware of a number of early vendor =
implementations that are attempting to address the problem documented in =
the charter, hence a desire to work towards a standards-based way of =
doing it.

I've only been to a small number of BoFs this IETF, but not all have =
taken the 5434 approach.

Tim


From stpeter@stpeter.im  Thu Aug  1 07:39:38 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584A221E81BA for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 07:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 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 PUVhklPc5E97 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 07:39:32 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C9F9821E823A for <wgchairs@ietf.org>; Thu,  1 Aug 2013 07:39:11 -0700 (PDT)
Received: from ergon.local (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 714EB40344; Thu,  1 Aug 2013 08:41:27 -0600 (MDT)
Message-ID: <51FA730A.3070800@stpeter.im>
Date: Thu, 01 Aug 2013 16:39:06 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: mic lines
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 14:39:38 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At a session I participated in yesterday, several people were at the
mic. One of the chairs said "the mic line is cut", by which he meant
"those at the mic line need to sit down". I don't think that's how
it's supposed to work.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR+nMKAAoJEOoGpJErxa2pGxkP/3G9zR6ZIuF3kjFovExrO4bx
WnYfgCJvz4wHwPT4RmmgTQedPonCzu+v9mRqYtlOhyEL2gCDRXjQZxU59PnEisqb
RJrBDLRgOyWeTSsMlLLQAVxerXZvTZ+MGGowwbHe1IgMQ91IEvh8EuzP/FHAgUJc
IvIKEX/lYpcSYfdTLiBc53HeFCfVKgLhlqr+jLPChPNd86ZPyLBGM34knDemvh8J
LPi2AOIQkpjvx61ErhUM6YF1BCtZiPsSDdbSQH18tH0p9KNZ8fB6j2eeN8F2Qk91
YvSWQhaoRV+J46U6JwZtbTlN/TwHHoCY3KzhdhKFLp+XLrtJn1gyQAfcPIX9BWu/
nlJXtaWel7ri8xNHAE3r6reWjvvdT/l3CBgkQIIWYvuRReHw0g6TS4uGtbNh7Z2o
RlgGA/RfLrJ0MX8XdgqWmBs7bdHaUgW4Lm5tFCKuCRDFsAebF0sWCf3Ji0Tka1hd
lfCzFomNOyy1rKoIQOVreMEfOtlkZiln+pGjjqK9xhlD4FrqEeXAQRaJ8s3wNxyZ
fnhutcwFqHNaD08ZIW+cDNoeBIGlw5pp+Q1DXRNo7DVJVjwp+yoLfiEuf3TsApth
5c+D6OVZcQxlpDCZJM0DltgFlQfAOzD434HeYAbb9P9TKok77/lkdxAVAo0Opdqj
OpdxHnRlcaHL876rnpdN
=Lp4d
-----END PGP SIGNATURE-----

From yaronf.ietf@gmail.com  Thu Aug  1 07:57:09 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB5621E80EB for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 07:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[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 tTYPeMFhz0hV for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 07:57:08 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id E047821E80FF for <wgchairs@ietf.org>; Thu,  1 Aug 2013 07:57:05 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so2166824pbc.8 for <wgchairs@ietf.org>; Thu, 01 Aug 2013 07:57:04 -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=9H5pA1RM+hnjbrWrKr7eryUtp6As1ZQqX149zMYPwg8=; b=rgrLXrIY8swN6d3uDQRWzjCg5MlvxCCoXQtNNz1SB677qX6K1Zu35i8qUuQvCBNjCL 3iFnt93opurDlIRQZdh1vh/vqpZGvUo2JXSidS3NT2UbplyqCAmPTsgFqfpc7dplZaNg o0bvgc6EOc0XG4LEwgDGwXm1s3OQ4V9x8cKxvTMfeZkPed4YP9KbfyrobLvqp91ddTCx 53LBIMy9TeTIo/h0lGlO24zxFI8O/XVYGN1g+VppbxFasDS5dXDXWI6TulixlFFASu7V OaR//XH0seKcVhz9wfFRfjEf5+x/vAAhUfLnO2K3XSnvxfXGj59YMQ7iTRcZEodFERfO AMsA==
X-Received: by 10.66.219.38 with SMTP id pl6mr4786844pac.59.1375369024554; Thu, 01 Aug 2013 07:57:04 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:16:c091:d3ed:5b64:514e? ([2001:df8:0:16:c091:d3ed:5b64:514e]) by mx.google.com with ESMTPSA id bg3sm3653073pbb.44.2013.08.01.07.57.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 07:57:03 -0700 (PDT)
Message-ID: <51FA773A.9040506@gmail.com>
Date: Thu, 01 Aug 2013 16:56:58 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
References: <51FA4662.4050404@qti.qualcomm.com>
In-Reply-To: <51FA4662.4050404@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 14:57:09 -0000

Hi Pete,

I think this question is just too speculative to take seriously. Not 
your question here, the question you'd want asked at the BOF.

Even when we ask people at a BOF, "who would be willing to edit/review", 
we know the responses are way too optimistic. So asking about 
implementations this early in the process is IMHO not useful, in that we 
cannot expect reliable information.

Thanks,
	Yaron

On 2013-08-01 13:28, Pete Resnick wrote:
> I considered posting to the IETF main list, but I thought I'd start a
> bit smaller.
>
> Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC 5434
> that surprised me:
>
>     ...the goal of the BOF is to demonstrate that the community has
>     agreement that:
>
>        - there is a problem that needs solving, and the IETF is the right
>          group to attempt solving it.
>
>        - there is a critical mass of participants willing to work on the
>          problem (e.g., write drafts, review drafts, etc.).
>
>        - the scope of the problem is well defined and understood, that
>          is, people generally understand what the WG will work on (and
>          what it won't) and what its actual deliverables will be.
>
>        - there is agreement that the specific deliverables (i.e.,
>          proposed documents) are the right set.
>
>        - it is believed that the WG has a reasonable probability of
>          having success (i.e., in completing the deliverables in its
>          charter in a timely fashion).
>
> It seemed to me that there was a serious omission from this list:
>
>     - it is believed that there a critical mass of implementers who will
>       use the output of the working group.
>
> In fact, I couldn't find the word "implement" anywhere in the document.
> Do we just assume implementers but don't mention them, or (and I hope
> this is not the case) do we really think that it is an irrelevant
> question to consider regarding a successful BOF?
>
> pr
>

From d3e3e3@gmail.com  Thu Aug  1 18:40:14 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5ED11E8167 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 18:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2R2T-DAQlsn for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 18:40:06 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id DE5C611E8314 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 17:51:55 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id ef5so92577obb.9 for <wgchairs@ietf.org>; Thu, 01 Aug 2013 17:51:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mAr88B+7JIPpYQb7LaR7SAw6dsudBxNjJXfYo2YYp8U=; b=OJtu1TyMBpE7wKKwoviq4gpBoqzflJbYdzA7iYGb0ShZujaYgaaEaCcAMNP0ybHwIU aIzQs9/B4YTZEkqX0sXgXi5q9LHDn+LNoGfX+C+nhsnnhSzhlVXl/fh15T14KXKsgJQc 1kjPmDM6pbZ65h8d2g3s+zMdqKvrC4aAVMjrjBxw64d5PYxO9f+ufO3snri6IQJv8VVU tfRdMntmclRYv4cTsT27AMq7vbjz2kmns1eV9cpa6wQgFVpXUQCd29Smqg4+Kuy5VD5Q EAuor6iDGNJFwnDthsjIyeRDLFS3kGwv30cfdpwAQeO5sWjEHAbJnXXtwUYzWabjLtpI 9XGw==
X-Received: by 10.60.173.235 with SMTP id bn11mr3361942oec.43.1375404715423; Thu, 01 Aug 2013 17:51:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.131.7 with HTTP; Thu, 1 Aug 2013 17:51:35 -0700 (PDT)
In-Reply-To: <51FA730A.3070800@stpeter.im>
References: <51FA730A.3070800@stpeter.im>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 1 Aug 2013 20:51:35 -0400
Message-ID: <CAF4+nEGVY45Vn3xSG=e_F2-Dcj4wJLSfFgz4TX5PvJ2a3X=9Eg@mail.gmail.com>
Subject: Re: mic lines
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=089e0116112e7c3e0104e2ec5d24
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 01:40:14 -0000

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

It seems more polite to let those in line speak and stop people form
joining the line and I try to do that but you can't make hard and fast
rules for this sort of this. It all depends. Certainly if you have previous
said the line was closed and no new people should join but people do
anyway, you can tell them to leave the line. Was something relatively
insignificant being discussed and was it cut off to avoid impinging on time
reserved for a more important technical controversy? Had a fair amount of
discussion already occurred and you were getting to the stage where the
same points were being repeated again and again? Where those in line people
who had had a chance to speak before?

Those who don't get a chance to say everything they wanted at a meeting can
always post to the mailing list.

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


On Thu, Aug 1, 2013 at 10:39 AM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> At a session I participated in yesterday, several people were at the
> mic. One of the chairs said "the mic line is cut", by which he meant
> "those at the mic line need to sit down". I don't think that's how
> it's supposed to work.
>
> Peter
>
> - --
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJR+nMKAAoJEOoGpJErxa2pGxkP/3G9zR6ZIuF3kjFovExrO4bx
> WnYfgCJvz4wHwPT4RmmgTQedPonCzu+v9mRqYtlOhyEL2gCDRXjQZxU59PnEisqb
> RJrBDLRgOyWeTSsMlLLQAVxerXZvTZ+MGGowwbHe1IgMQ91IEvh8EuzP/FHAgUJc
> IvIKEX/lYpcSYfdTLiBc53HeFCfVKgLhlqr+jLPChPNd86ZPyLBGM34knDemvh8J
> LPi2AOIQkpjvx61ErhUM6YF1BCtZiPsSDdbSQH18tH0p9KNZ8fB6j2eeN8F2Qk91
> YvSWQhaoRV+J46U6JwZtbTlN/TwHHoCY3KzhdhKFLp+XLrtJn1gyQAfcPIX9BWu/
> nlJXtaWel7ri8xNHAE3r6reWjvvdT/l3CBgkQIIWYvuRReHw0g6TS4uGtbNh7Z2o
> RlgGA/RfLrJ0MX8XdgqWmBs7bdHaUgW4Lm5tFCKuCRDFsAebF0sWCf3Ji0Tka1hd
> lfCzFomNOyy1rKoIQOVreMEfOtlkZiln+pGjjqK9xhlD4FrqEeXAQRaJ8s3wNxyZ
> fnhutcwFqHNaD08ZIW+cDNoeBIGlw5pp+Q1DXRNo7DVJVjwp+yoLfiEuf3TsApth
> 5c+D6OVZcQxlpDCZJM0DltgFlQfAOzD434HeYAbb9P9TKok77/lkdxAVAo0Opdqj
> OpdxHnRlcaHL876rnpdN
> =Lp4d
> -----END PGP SIGNATURE-----
>

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

It seems more polite to let those in line speak and stop people form joinin=
g the line and I try to do that but you can&#39;t make hard and fast rules =
for this sort of this. It all depends. Certainly if you have previous said =
the line was closed and no new people should join but people do anyway, you=
 can tell them to leave the line. Was something relatively insignificant be=
ing discussed and was it cut off to avoid impinging on time reserved for a =
more important technical controversy? Had a fair amount of discussion alrea=
dy occurred and you were getting to the stage where the same points were be=
ing repeated again and again? Where those in line people who had had a chan=
ce to speak before?<div>

<br></div><div>Those who don&#39;t get a chance to say everything they want=
ed at a meeting can always post to the mailing list.<div><br clear=3D"all">=
<div>Thanks,<br>Donald<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=A0Donald E. Eastlake 3rd=A0=A0 =
+1-508-333-2270 (cell)<br>

=A0155 Beaver Street,=A0Milford, MA 01757 USA<br>=A0<a href=3D"mailto:d3e3e=
3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a></div>
<br><br><div class=3D"gmail_quote">On Thu, Aug 1, 2013 at 10:39 AM, Peter S=
aint-Andre <span dir=3D"ltr">&lt;<a href=3D"mailto:stpeter@stpeter.im" targ=
et=3D"_blank">stpeter@stpeter.im</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
At a session I participated in yesterday, several people were at the<br>
mic. One of the chairs said &quot;the mic line is cut&quot;, by which he me=
ant<br>
&quot;those at the mic line need to sit down&quot;. I don&#39;t think that&=
#39;s how<br>
it&#39;s supposed to work.<br>
<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>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)<br>
Comment: GPGTools - <a href=3D"http://gpgtools.org" target=3D"_blank">http:=
//gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href=3D"http://www.enigmail.net/=
" target=3D"_blank">http://www.enigmail.net/</a><br>
<br>
iQIcBAEBAgAGBQJR+nMKAAoJEOoGpJErxa2pGxkP/3G9zR6ZIuF3kjFovExrO4bx<br>
WnYfgCJvz4wHwPT4RmmgTQedPonCzu+v9mRqYtlOhyEL2gCDRXjQZxU59PnEisqb<br>
RJrBDLRgOyWeTSsMlLLQAVxerXZvTZ+MGGowwbHe1IgMQ91IEvh8EuzP/FHAgUJc<br>
IvIKEX/lYpcSYfdTLiBc53HeFCfVKgLhlqr+jLPChPNd86ZPyLBGM34knDemvh8J<br>
LPi2AOIQkpjvx61ErhUM6YF1BCtZiPsSDdbSQH18tH0p9KNZ8fB6j2eeN8F2Qk91<br>
YvSWQhaoRV+J46U6JwZtbTlN/TwHHoCY3KzhdhKFLp+XLrtJn1gyQAfcPIX9BWu/<br>
nlJXtaWel7ri8xNHAE3r6reWjvvdT/l3CBgkQIIWYvuRReHw0g6TS4uGtbNh7Z2o<br>
RlgGA/RfLrJ0MX8XdgqWmBs7bdHaUgW4Lm5tFCKuCRDFsAebF0sWCf3Ji0Tka1hd<br>
lfCzFomNOyy1rKoIQOVreMEfOtlkZiln+pGjjqK9xhlD4FrqEeXAQRaJ8s3wNxyZ<br>
fnhutcwFqHNaD08ZIW+cDNoeBIGlw5pp+Q1DXRNo7DVJVjwp+yoLfiEuf3TsApth<br>
5c+D6OVZcQxlpDCZJM0DltgFlQfAOzD434HeYAbb9P9TKok77/lkdxAVAo0Opdqj<br>
OpdxHnRlcaHL876rnpdN<br>
=3DLp4d<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div></div>

--089e0116112e7c3e0104e2ec5d24--

From peter@denic.de  Thu Aug  1 22:48:55 2013
Return-Path: <peter@denic.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0277311E8224 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 22:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Dw1j65VDn6L for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 22:48:54 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9C20C21E8265 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 22:48:23 -0700 (PDT)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1V58Du-0006iw-Ex; Fri, 02 Aug 2013 07:48:22 +0200
Received: from localhost by x27.adm.denic.de with local  id 1V58Du-0006kw-BS; Fri, 02 Aug 2013 07:48:22 +0200
Date: Fri, 2 Aug 2013 07:48:22 +0200
From: Peter Koch <pk@ISOC.DE>
To: WG Chairs <wgchairs@ietf.org>
Subject: Re: mic lines
Message-ID: <20130802054822.GE23086@x28.adm.denic.de>
Mail-Followup-To: WG Chairs <wgchairs@ietf.org>
References: <51FA730A.3070800@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51FA730A.3070800@stpeter.im>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 05:48:55 -0000

On Thu, Aug 01, 2013 at 04:39:06PM +0200, Peter Saint-Andre wrote:

> mic. One of the chairs said "the mic line is cut", by which he meant
> "those at the mic line need to sit down". I don't think that's how
> it's supposed to work.

agree, but it would help if people in the line pre-embargo would
be brief.  Queue length is only a rough estimate of airtime to be
consumed.

-Peter

From dcrocker@bbiw.net  Thu Aug  1 22:56:44 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F8A11E8224 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 22:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id arLQ6uGpVxKl for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 22:56:39 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3897311E8249 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 22:56:25 -0700 (PDT)
Received: from [192.168.1.203] (g231112078.adsl.alicedsl.de [92.231.112.78]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r725uEvK032168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Aug 2013 22:56:21 -0700
Message-ID: <51FB49F8.6000103@bbiw.net>
Date: Fri, 02 Aug 2013 07:56:08 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im>
In-Reply-To: <51FA730A.3070800@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Thu, 01 Aug 2013 22:56:24 -0700 (PDT)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 05:56:44 -0000

On 8/1/2013 4:39 PM, Peter Saint-Andre wrote:
> At a session I participated in yesterday, several people were at the
> mic. One of the chairs said "the mic line is cut", by which he meant
> "those at the mic line need to sit down". I don't think that's how
> it's supposed to work.


At the IETF, I've only seen that happen once.  And by coincidence I was 
the only person at the mic -- I've no evidence this was personal 
treatment...  Happily, before I could say anything or move, the audience 
"corrected" the chair, to switch to normal IETF etiquette.

Probably forever, that etiquette is is handled by having access to the 
mics terminated with "cut at the end of the current line(s)".

As with any long-standing organization, we have a mass of details that 
guide our group etiquette.  Especially for an organization with so much 
"churn" -- that is, so many new administrators (chairs, scribes, ADs, 
authors, ...) we need to write shit down, if we expect these folk to 
know about the etiquette.

Seems like the wgchairs wiki is the home for this?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From spencerdawkins.ietf@gmail.com  Thu Aug  1 23:14:17 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7FE11E81B0 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 23:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOqjKCu9smfc for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 23:14:16 -0700 (PDT)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 81EBB11E8221 for <wgchairs@ietf.org>; Thu,  1 Aug 2013 23:14:16 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e52so106276eek.30 for <wgchairs@ietf.org>; Thu, 01 Aug 2013 23:14:15 -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=8OC4REd1kEvTIXjGNBaUCEfaOtsFZJDmFrVDv2uMV2g=; b=mbrVxk5FrpKahwsOLnxAMrRETRanypji+8NkLV8IEvqR9J/ly5Opiberqu81b1N6TC NwP4vRbIE14bmvEeQo0Rsaz0eUctfFi0GQJCoSLV7/FaRm5msGqfFmc0nX9LyL2UpM7m fJ37l8l5lXnEom3MuF3o7mvjQVYXj/tmFsEmEEdpujuuS35DU/lCzk4YZFTsjKEmHDlR 7Z+uGD1ln51IGQNfHyGGDy4+P6XRTTd4SHuM1/EzLSC+QFpcY6eFD7SgnTd9d1R3WZ1D g2w3CZ9NY3/hwzZ/EDzWpXYTiTLsZauJCg5ZqT/ZiCGMP4WK4ceMnPpNA8k1XtOB1bp8 R3CQ==
MIME-Version: 1.0
X-Received: by 10.14.221.198 with SMTP id r46mr4454758eep.18.1375424055634; Thu, 01 Aug 2013 23:14:15 -0700 (PDT)
Received: by 10.223.84.130 with HTTP; Thu, 1 Aug 2013 23:14:15 -0700 (PDT)
In-Reply-To: <51FB49F8.6000103@bbiw.net>
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net>
Date: Fri, 2 Aug 2013 01:14:15 -0500
Message-ID: <CAKKJt-dvvoStLEwi09yGRFHzVKUus_sycS-F_6b2=fdVse471A@mail.gmail.com>
Subject: Re: mic lines
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b66f68140916f04e2f0de7f
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 06:14:17 -0000

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

On Friday, August 2, 2013, Dave Crocker wrote:
>
>
> As with any long-standing organization, we have a mass of details that
> guide our group etiquette.  Especially for an organization with so much
> "churn" -- that is, so many new administrators (chairs, scribes, ADs,
> authors, ...) we need to write shit down, if we expect these folk to know
> about the etiquette.
>
> Seems like the wgchairs wiki is the home for this?
>

Perhaps also worth mentioning at whatever classes are targeting new/all
working group chairs?

Spencer

P.s. I apologize for not being current on Sunday afternoon training; I've
been in IAB meetings on Sunday afternoons for the past three years, and I
was meeting with my working group chairs this time. Next time, I'll be able
to focus on education ...

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

<br><br>On Friday, August 2, 2013, Dave Crocker  wrote:<blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<br>
As with any long-standing organization, we have a mass of details that guid=
e our group etiquette. =A0Especially for an organization with so much &quot=
;churn&quot; -- that is, so many new administrators (chairs, scribes, ADs, =
authors, ...) we need to write shit down, if we expect these folk to know a=
bout the etiquette.<br>

<br>
Seems like the wgchairs wiki is the home for this?<br>
</blockquote><div><br></div><div>Perhaps also worth mentioning at whatever =
classes are targeting new/all working group chairs?</div><div><br></div><di=
v>Spencer</div><div><br></div><div>P.s. I apologize for not being current o=
n Sunday afternoon training; I&#39;ve been in IAB meetings on Sunday aftern=
oons for the past three years, and I was meeting with my working group chai=
rs this time. Next time, I&#39;ll be able to focus on education ...<span></=
span>=A0</div>

--047d7b66f68140916f04e2f0de7f--

From adrian@olddog.co.uk  Thu Aug  1 23:46:06 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B8F11E825A for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 23:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-VvRimRNj08 for <wgchairs@ietfa.amsl.com>; Thu,  1 Aug 2013 23:46:01 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id D889A11E825F for <wgchairs@ietf.org>; Thu,  1 Aug 2013 23:45:53 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r726jihl013934;  Fri, 2 Aug 2013 07:45:44 +0100
Received: from 950129200 (dhcp-13f0.meeting.ietf.org [130.129.19.240]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r726jfUA013903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Aug 2013 07:45:41 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Dave Crocker'" <dcrocker@bbiw.net>, "'Peter Saint-Andre'" <stpeter@stpeter.im>
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net>
In-Reply-To: <51FB49F8.6000103@bbiw.net>
Subject: RE: mic lines
Date: Fri, 2 Aug 2013 07:45:39 +0100
Message-ID: <011a01ce8f4b$e8689410$b939bc30$@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: AQGj4UreW1gPq+3tTSvHOOUefxR43AF4FNvZmcsSBQA=
Content-Language: en-gb
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 06:46:06 -0000

Chairing I have cut lines with people on their feet.

I have done this mainly by the clock saying, in advance, "The lines are long, we
will cut the lines after another 11 minutes" and also provided frequent
reminders to "keep it quick."

I once did it with "This conversation is not productive. I know lots of you want
to participate, but it needs to be on the list and not in this meeting."

I also once did it to a WG while I was AD on the grounds of non-productivity and
hi-jack :-(   It became necessary to stop the line which was multiple people
standing around multiple mics, not yielding and arguing. That has to be pretty
rare and I did not offer "sit down and move on," I offered "move on or close the
meeting".

Adrian

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
> Of Dave Crocker
> Sent: 02 August 2013 06:56
> To: Peter Saint-Andre
> Cc: WG Chairs
> Subject: Re: mic lines
> 
> On 8/1/2013 4:39 PM, Peter Saint-Andre wrote:
> > At a session I participated in yesterday, several people were at the
> > mic. One of the chairs said "the mic line is cut", by which he meant
> > "those at the mic line need to sit down". I don't think that's how
> > it's supposed to work.
> 
> 
> At the IETF, I've only seen that happen once.  And by coincidence I was
> the only person at the mic -- I've no evidence this was personal
> treatment...  Happily, before I could say anything or move, the audience
> "corrected" the chair, to switch to normal IETF etiquette.
> 
> Probably forever, that etiquette is is handled by having access to the
> mics terminated with "cut at the end of the current line(s)".
> 
> As with any long-standing organization, we have a mass of details that
> guide our group etiquette.  Especially for an organization with so much
> "churn" -- that is, so many new administrators (chairs, scribes, ADs,
> authors, ...) we need to write shit down, if we expect these folk to
> know about the etiquette.
> 
> Seems like the wgchairs wiki is the home for this?
> 
> d/
> 
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From dcrocker@bbiw.net  Fri Aug  2 00:11:45 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBA0911E827B for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:11: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 d+xr8ffFlmYc for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:11:40 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id DC98D11E8270 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:11:40 -0700 (PDT)
Received: from [192.168.1.203] (g231112078.adsl.alicedsl.de [92.231.112.78]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r727BV06000660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 00:11:37 -0700
Message-ID: <51FB5B9D.8090202@bbiw.net>
Date: Fri, 02 Aug 2013 09:11:25 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net> <011a01ce8f4b$e8689410$b939bc30$@olddog.co.uk>
In-Reply-To: <011a01ce8f4b$e8689410$b939bc30$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Fri, 02 Aug 2013 00:11:40 -0700 (PDT)
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:11:46 -0000

On 8/2/2013 8:45 AM, Adrian Farrel wrote:
> Chairing I have cut lines with people on their feet.
>
> I have done this mainly by the clock saying, in advance, "The lines are long, we
> will cut the lines after another 11 minutes" and also provided frequent
> reminders to "keep it quick."
>
> I once did it with "This conversation is not productive. I know lots of you want
> to participate, but it needs to be on the list and not in this meeting."
>
> I also once did it to a WG while I was AD on the grounds of non-productivity and
> hi-jack :-(   It became necessary to stop the line which was multiple people
> standing around multiple mics, not yielding and arguing. That has to be pretty
> rare and I did not offer "sit down and move on," I offered "move on or close the
> meeting".


The critical aspect of what you've described is predictability.  You 
announced some limits for the future, giving the room time to conform or 
object.  I'd see that as quite different from a spontaneous termination 
of the mike.  (The one exception would, of course, be a spontaneous 
blow-up of a topic that requires immediate fire suppression...)

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ajs@anvilwalrusden.com  Fri Aug  2 00:18:23 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EF211E828C for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level: 
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51fnCDsVh6EO for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:18:18 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 760A311E8274 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:18:17 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-650a.meeting.ietf.org [130.129.101.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9A6D58A031 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 07:18:16 +0000 (UTC)
Date: Fri, 2 Aug 2013 03:17:42 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: mic lines
Message-ID: <20130802071742.GA58539@mx1.yitter.info>
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net> <011a01ce8f4b$e8689410$b939bc30$@olddog.co.uk> <51FB5B9D.8090202@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51FB5B9D.8090202@bbiw.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:18:24 -0000

On Fri, Aug 02, 2013 at 09:11:25AM +0200, Dave Crocker wrote:

> spontaneous termination of the mike.  (The one exception would, of
> course, be a spontaneous blow-up of a topic that requires immediate
> fire suppression...)

Or one of those mic disagreements that takes up all the time left.  As
usual, general principles along with judgement is what we want, rather
than laws (particularly those generated by hard cases).

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From prvs=1926ad17cd=sandra.murphy@parsons.com  Fri Aug  2 00:22:31 2013
Return-Path: <prvs=1926ad17cd=sandra.murphy@parsons.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4734C21E8249 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pQB1uzqPLQ8 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:22:25 -0700 (PDT)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id C4E4521E809A for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:22:22 -0700 (PDT)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id r727LjuT009975;  Fri, 2 Aug 2013 02:22:13 -0500
Received: from uther.sparta.com (uther.sparta.com [157.185.0.2]) by txdal11mx03.parsons.com with ESMTP id 1e05pegfpj-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 02 Aug 2013 02:22:13 -0500
Received: from durin.laguna.sparta.com ([10.62.216.7]) by Uther.sparta.com (8.13.8/8.13.8) with ESMTP id r727M1Zj005852; Fri, 2 Aug 2013 00:22:01 -0700
Received: from CVA-HUB001.centreville.ads.sparta.com ([10.62.108.11]) by durin.laguna.sparta.com (8.13.8/8.13.8) with ESMTP id r727M1hv012455; Fri, 2 Aug 2013 00:22:01 -0700
Received: from CVA-MB002.centreville.ads.sparta.com ([fe80::6046:a82a:c500:c9ad]) by CVA-HUB001.centreville.ads.sparta.com ([fe80::8ca8:7aea:3db9:1972%11]) with mapi id 14.02.0342.003; Fri, 2 Aug 2013 03:21:54 -0400
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Dave Crocker <dcrocker@bbiw.net>
Subject: RE: mic lines
Thread-Topic: mic lines
Thread-Index: AQHOjw98qYCLQVelvE20xvJC7rcg5ZmBruYAgAAFD4D//8zplA==
Date: Fri, 2 Aug 2013 07:21:52 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F6749C98AA@CVA-MB002.centreville.ads.sparta.com>
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net>, <CAKKJt-dvvoStLEwi09yGRFHzVKUus_sycS-F_6b2=fdVse471A@mail.gmail.com>
In-Reply-To: <CAKKJt-dvvoStLEwi09yGRFHzVKUus_sycS-F_6b2=fdVse471A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.62.8.137]
Content-Type: multipart/alternative; boundary="_000_24B20D14B2CD29478C8D5D6E9CBB29F6749C98AACVAMB002centrev_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-08-02_03:2013-08-01, 2013-08-02, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=1.56430424169685e-13 kscore.compositescore=0 circleOfTrustscore=13.0103365532123 compositescore=0.000437136136528448 urlsuspect_oldscore=0.00437136136528448 suspectscore=0 recipient_domain_to_sender_totalscore=1 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=715918 rbsscore=0.000437136136528448 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.3 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1308020002
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:22:31 -0000

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

The edu team has held a lunchtime seminar for wgchairs on Wed for the past,=
 oh, well, lots of meetings.

It's a new topic each time, so always a benefit to wgchairs in general.   T=
his time was about the wgchairs part of the datatracker, very valuable.

That's different from basic training into wg process, which is another edu =
team tutorial sometimes offered during the Sun tutorial time.  (sometimes =
=3D=3D ietf 86, 85, 81...)  There's always a newcomer's meeting but the wg =
leadership meeting seems to trade off with ietf process and bringing new wo=
rk, etc.

--Sandy

________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of Sp=
encer Dawkins at IETF [spencerdawkins.ietf@gmail.com]
Sent: Friday, August 02, 2013 2:14 AM
To: Dave Crocker
Cc: WG Chairs
Subject: Re: mic lines



On Friday, August 2, 2013, Dave Crocker wrote:

As with any long-standing organization, we have a mass of details that guid=
e our group etiquette.  Especially for an organization with so much "churn"=
 -- that is, so many new administrators (chairs, scribes, ADs, authors, ...=
) we need to write shit down, if we expect these folk to know about the eti=
quette.

Seems like the wgchairs wiki is the home for this?

Perhaps also worth mentioning at whatever classes are targeting new/all wor=
king group chairs?

Spencer

P.s. I apologize for not being current on Sunday afternoon training; I've b=
een in IAB meetings on Sunday afternoons for the past three years, and I wa=
s meeting with my working group chairs this time. Next time, I'll be able t=
o focus on education ...

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

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" id=3D"owaParaStyle"></style>
</head>
<body fpstyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Arial;color: #000000;font-size: 1=
0pt;">The edu team has held a lunchtime seminar for wgchairs on Wed for the=
 past, oh, well, lots of meetings.
<div><br>
</div>
<div>It's a new topic each time, so always a benefit to wgchairs in general=
. &nbsp; This time was about the wgchairs part of the datatracker, very val=
uable.</div>
<div><br>
</div>
<div>That's different from basic training into wg process, which is another=
 edu team tutorial sometimes offered during the Sun tutorial time. &nbsp;(s=
ometimes =3D=3D ietf 86, 85, 81...) &nbsp;There's always a newcomer's meeti=
ng but the wg leadership meeting seems to trade
 off with ietf process and bringing new work, etc.</div>
<div><br>
</div>
<div>--Sandy</div>
<div><br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div id=3D"divRpF920005" style=3D"direction: ltr; "><font face=3D"Tahoma" s=
ize=3D"2" color=3D"#000000"><b>From:</b> wgchairs-bounces@ietf.org [wgchair=
s-bounces@ietf.org] on behalf of Spencer Dawkins at IETF [spencerdawkins.ie=
tf@gmail.com]<br>
<b>Sent:</b> Friday, August 02, 2013 2:14 AM<br>
<b>To:</b> Dave Crocker<br>
<b>Cc:</b> WG Chairs<br>
<b>Subject:</b> Re: mic lines<br>
</font><br>
</div>
<div></div>
<div><br>
<br>
On Friday, August 2, 2013, Dave Crocker wrote:
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<br>
As with any long-standing organization, we have a mass of details that guid=
e our group etiquette. &nbsp;Especially for an organization with so much &q=
uot;churn&quot; -- that is, so many new administrators (chairs, scribes, AD=
s, authors, ...) we need to write shit down, if
 we expect these folk to know about the etiquette.<br>
<br>
Seems like the wgchairs wiki is the home for this?<br>
</blockquote>
<div><br>
</div>
<div>Perhaps also worth mentioning at whatever classes are targeting new/al=
l working group chairs?</div>
<div><br>
</div>
<div>Spencer</div>
<div><br>
</div>
<div>P.s. I apologize for not being current on Sunday afternoon training; I=
've been in IAB meetings on Sunday afternoons for the past three years, and=
 I was meeting with my working group chairs this time. Next time, I'll be a=
ble to focus on education ...<span></span>&nbsp;</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_24B20D14B2CD29478C8D5D6E9CBB29F6749C98AACVAMB002centrev_--

From adrian@olddog.co.uk  Fri Aug  2 00:29:26 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D921C21E809A for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VeF0MS2mstLD for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:29:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 71CFF11E8279 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:29:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r727TJOt003883 for <wgchairs@ietf.org>; Fri, 2 Aug 2013 08:29:19 +0100
Received: from 950129200 (dhcp-13f0.meeting.ietf.org [130.129.19.240]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r727THVY003858 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Fri, 2 Aug 2013 08:29:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'WG Chairs'" <wgchairs@ietf.org>
References: <51FA730A.3070800@stpeter.im> <51FB49F8.6000103@bbiw.net> <011a01ce8f4b$e8689410$b939bc30$@olddog.co.uk> <51FB5B9D.8090202@bbiw.net>
In-Reply-To: <51FB5B9D.8090202@bbiw.net>
Subject: RE: mic lines
Date: Fri, 2 Aug 2013 08:29:16 +0100
Message-ID: <013201ce8f51$ffb5cab0$ff216010$@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: AQGj4UreW1gPq+3tTSvHOOUefxR43AF4FNvZAnVe4l4BgqyYZZmrYAWA
Content-Language: en-gb
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:29:27 -0000

Just witnessed a (visiting) AD bounced by the chairs because he went to the mic
(as a regular contributor) after the lines had been cut.

Very nice chairing, and appreciated by the meeting with wry grins.

A

> -----Original Message-----
> From: Dave Crocker [mailto:dcrocker@bbiw.net]
> Sent: 02 August 2013 08:11
> To: adrian@olddog.co.uk
> Cc: 'Peter Saint-Andre'; 'WG Chairs'
> Subject: Re: mic lines
> 
> On 8/2/2013 8:45 AM, Adrian Farrel wrote:
> > Chairing I have cut lines with people on their feet.
> >
> > I have done this mainly by the clock saying, in advance, "The lines are
long, we
> > will cut the lines after another 11 minutes" and also provided frequent
> > reminders to "keep it quick."
> >
> > I once did it with "This conversation is not productive. I know lots of you
want
> > to participate, but it needs to be on the list and not in this meeting."
> >
> > I also once did it to a WG while I was AD on the grounds of non-productivity
and
> > hi-jack :-(   It became necessary to stop the line which was multiple people
> > standing around multiple mics, not yielding and arguing. That has to be
pretty
> > rare and I did not offer "sit down and move on," I offered "move on or close
> the
> > meeting".
> 
> 
> The critical aspect of what you've described is predictability.  You
> announced some limits for the future, giving the room time to conform or
> object.  I'd see that as quite different from a spontaneous termination
> of the mike.  (The one exception would, of course, be a spontaneous
> blow-up of a topic that requires immediate fire suppression...)
> 
> d/
> 
> 
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From warren@kumari.net  Fri Aug  2 00:34:48 2013
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88F721E825D for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.387
X-Spam-Level: 
X-Spam-Status: No, score=-102.387 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 EvEs5NfED9kt for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:34:35 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7998C21E826D for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:33:00 -0700 (PDT)
Received: from [130.129.0.225] (unknown [130.129.0.225]) by vimes.kumari.net (Postfix) with ESMTPSA id 547501B40C61; Fri,  2 Aug 2013 03:32:59 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: mic lines
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <51FA730A.3070800@stpeter.im>
Date: Fri, 2 Aug 2013 09:32:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A894B74-5B80-4846-A957-ED9A126795F2@kumari.net>
References: <51FA730A.3070800@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1508)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:34:56 -0000

On Aug 1, 2013, at 4:39 PM, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:

> Signed PGP part
> At a session I participated in yesterday, several people were at the
> mic. One of the chairs said "the mic line is cut", by which he meant
> "those at the mic line need to sit down". I don't think that's how
> it's supposed to work.
>=20

Probably not how it is *supposed* to work, but I think that without more =
details (I read the rest of the thread) it is hard to tell=85

If the chair knew that the rest of the conversation / folk in the line =
were simply going to spiral this into fist-fights and name calling and =
beard pulling then they may have done it to prevent an explosion. Or if =
it was clear that consensus was already figured out and everyone else =
just a: in the rough or b: simply wanting to chime and feel important=85

I guess the answer is "It all depends=85"

W


> Peter
>=20
> - --=20
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
>=20

---
Schizophrenia beats being alone.



From keith.drage@alcatel-lucent.com  Fri Aug  2 00:43:38 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6CB11E828F for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.637
X-Spam-Level: 
X-Spam-Status: No, score=-110.637 tagged_above=-999 required=5 tests=[AWL=-0.038, 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 M0bxsQQoxse9 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 00:43:32 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9AED811E8283 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 00:43:31 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r727hS1Q018161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 2 Aug 2013 02:43:29 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r727hR60028628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Aug 2013 09:43:27 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 2 Aug 2013 09:43:27 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Peter Koch <pk@ISOC.DE>, WG Chairs <wgchairs@ietf.org>
Subject: RE: mic lines
Thread-Topic: mic lines
Thread-Index: AQHOjxJIIUiAi2qd00O6+3xIDWLAbZmBSB8AgAAz0WA=
Date: Fri, 2 Aug 2013 07:43:26 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de>
In-Reply-To: <20130802054822.GE23086@x28.adm.denic.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:43:38 -0000

Experience tells me that asking speakers at the microphone to be brief has =
no effect whatsoever.

Suspect it is lack of training. Most people could say what they needed to s=
ay in something like a quarter of the time if they though about what they w=
anted to say before opening their mouths. As an occasional note taker, I ca=
n claim that many speakers cannot even manage to put their point across in =
complete sentences, and manage to get lost in so many levels of subthoughts=
 as to make what they say unintelligible. (and I am not claiming any perfec=
tion in this myself)

If as WG chair you have a key decision to make at the end of your meeting t=
ime (or at the end of a specific agenda item), sometimes all you can do is =
terminate the speaker, otherwise the decision effectively gets talked out o=
f the meeting.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Peter Koch
> Sent: 02 August 2013 06:48
> To: WG Chairs
> Subject: Re: mic lines
>=20
> On Thu, Aug 01, 2013 at 04:39:06PM +0200, Peter Saint-Andre wrote:
>=20
> > mic. One of the chairs said "the mic line is cut", by which he meant
> > "those at the mic line need to sit down". I don't think that's how
> > it's supposed to work.
>=20
> agree, but it would help if people in the line pre-embargo would
> be brief.  Queue length is only a rough estimate of airtime to be
> consumed.
>=20
> -Peter

From ajs@anvilwalrusden.com  Fri Aug  2 01:17:09 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22E2D21E82C7 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level: 
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1i9DbdflixlB for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:16:52 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6821711E82A2 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:16:36 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-650a.meeting.ietf.org [130.129.101.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3BB538A031 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 08:16:34 +0000 (UTC)
Date: Fri, 2 Aug 2013 04:16:31 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: mic lines
Message-ID: <20130802081630.GE58539@mx1.yitter.info>
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:17:09 -0000

On Fri, Aug 02, 2013 at 07:43:26AM +0000, DRAGE, Keith (Keith) wrote:
> Experience tells me that asking speakers at the microphone to be brief has no effect whatsoever.

But telling people "you each have 1.5 minutes" does, if you enforce it.

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dcrocker@bbiw.net  Fri Aug  2 01:37:26 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88FE211E82E2 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sp0dd8nm7slG for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:37:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0656B11E82B3 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:32:57 -0700 (PDT)
Received: from [192.168.1.203] (g231112078.adsl.alicedsl.de [92.231.112.78]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r728WRnp002377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 01:32:33 -0700
Message-ID: <51FB6E95.6030506@bbiw.net>
Date: Fri, 02 Aug 2013 10:32:21 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.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.67]); Fri, 02 Aug 2013 01:32:34 -0700 (PDT)
Cc: WG Chairs <wgchairs@ietf.org>, Peter Koch <pk@ISOC.DE>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:37:29 -0000

On 8/2/2013 9:43 AM, DRAGE, Keith (Keith) wrote:
> Experience tells me that asking speakers at the microphone to be brief has no effect whatsoever.


More generally, giving people goals that are subjective, relative and 
even conceptual (what is "brief"?) typically isn't helpful.

In this case, a comparison would be against such a concrete directive as 
"no more than 1 minute", with prods along the way.  This is objective 
and measurable.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Adam.Montville@cisecurity.org  Fri Aug  2 01:43:32 2013
Return-Path: <Adam.Montville@cisecurity.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D071311E8320 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.271
X-Spam-Level: 
X-Spam-Status: No, score=-3.271 tagged_above=-999 required=5 tests=[AWL=0.327,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RCuoBkfcVahe for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:43:26 -0700 (PDT)
Received: from mail1.bemta7.messagelabs.com (mail1.bemta7.messagelabs.com [216.82.254.108]) by ietfa.amsl.com (Postfix) with ESMTP id 55E1E11E82BB for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:40:51 -0700 (PDT)
Received: from [216.82.253.243:36640] by server-12.bemta-7.messagelabs.com id 84/70-18680-F807BF15; Fri, 02 Aug 2013 08:40:47 +0000
X-Env-Sender: Adam.Montville@cisecurity.org
X-Msg-Ref: server-12.tower-171.messagelabs.com!1375432845!2033872!2
X-Originating-IP: [69.195.43.86]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=cisecurity.org,-,-
X-VirusChecked: Checked
Received: (qmail 5164 invoked from network); 2 Aug 2013 08:40:46 -0000
Received: from mail.msisac.org (HELO mail.msisac.org) (69.195.43.86) by server-12.tower-171.messagelabs.com with AES128-SHA encrypted SMTP; 2 Aug 2013 08:40:46 -0000
Received: from CISEXCHANGE1.msisac.org.local ([fe80::4f0:b68d:e779:38c3]) by CISEXCHANGE2.msisac.org.local ([fe80::9d91:1cd4:d9fb:616c%14]) with mapi id 14.02.0342.003; Fri, 2 Aug 2013 04:40:43 -0400
From: Adam Montville <Adam.Montville@cisecurity.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: mic lines
Thread-Topic: mic lines
Thread-Index: AQHOjw95uCJuCBgvrEOGxVFzazgdNpmBrLoAgAAgJgCAAAk/gP//w10w
Date: Fri, 2 Aug 2013 08:40:42 +0000
Message-ID: <05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local>
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20130802081630.GE58539@mx1.yitter.info>
In-Reply-To: <20130802081630.GE58539@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.252.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:43:33 -0000

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Andrew Sullivan
> Sent: Friday, August 02, 2013 1:17 AM
> To: wgchairs@ietf.org
> Subject: Re: mic lines
>=20
> On Fri, Aug 02, 2013 at 07:43:26AM +0000, DRAGE, Keith (Keith) wrote:
> > Experience tells me that asking speakers at the microphone to be brief=
 has
> no effect whatsoever.
>=20
> But telling people "you each have 1.5 minutes" does, if you enforce it.
>=20

Has anyone tried reminding everyone in line that the more time they take u=
p, the less time they're leaving for others in the room (to handle most ca=
ses)?  Maybe that's naive.

> A
>=20
>=20
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>=20
> ...

. . .

From Ted.Lemon@nominum.com  Fri Aug  2 01:46:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB9211E82BB for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 UErlVv99VQRE for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 01:46:41 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id CB59111E82A5 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:46:40 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUftx8I3Md7pqiw1PO2MJbk/ndYSnYpi1@postini.com; Fri, 02 Aug 2013 01:46:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7D3EC1B8257 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:46:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 754A8190065; Fri,  2 Aug 2013 01:46:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 01:46:40 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: mic lines
Thread-Topic: mic lines
Thread-Index: AQHOjw99YbUyVxAhqU2XZIQGkXXAe5mB3wUAgAAgJgCAABGvAA==
Date: Fri, 2 Aug 2013 08:46:39 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077523EF82@mbx-01.win.nominum.com>
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2C97DBF29BEB5049AF3169AB0A1710E3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Peter Koch <pk@ISOC.DE>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:46:48 -0000

On Aug 2, 2013, at 9:43 AM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-luc=
ent.com> wrote:
> As an occasional note taker, I can claim that many speakers cannot even m=
anage to put their point across in complete sentences, and manage to get lo=
st in so many levels of subthoughts as to make what they say unintelligible=
. (and I am not claiming any perfection in this myself)

I have no idea what you are talking about, and resent the implication.   ;)

(I had a moment of that in MIF yesterday=97I claim that it was lack of slee=
p, but maybe I'm just not very coherent... :)


From dcrocker@bbiw.net  Fri Aug  2 02:04:42 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AA711E832F for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:04: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 q+1PMHitlbNo for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:03:53 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6114B21F8BE6 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 01:58:11 -0700 (PDT)
Received: from [192.168.1.203] (g231112078.adsl.alicedsl.de [92.231.112.78]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r728vRVF002854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 01:57:35 -0700
Message-ID: <51FB7470.5070109@bbiw.net>
Date: Fri, 02 Aug 2013 10:57:20 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Adam Montville <Adam.Montville@cisecurity.org>
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20130802081630.GE58539@mx1.yitter.info> <05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local>
In-Reply-To: <05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local>
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.67]); Fri, 02 Aug 2013 01:57:38 -0700 (PDT)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 09:04:43 -0000

On 8/2/2013 10:40 AM, Adam Montville wrote:
> Has anyone tried reminding everyone in line that the more time they take up, the less time they're leaving for others in the room (to handle most cases)?  Maybe that's naive.


That's very conceptual.  As a preface to the assertion of some concrete 
rules, it's reasonable, because it provides justification. As a behavior 
goal, it's essentially meaningless.  Everyone is speaking only as much 
as they deem necessary...

Write better code.

Do a better network configuration.

These have no associated metrics, so there's no way to know what to do.

Make the fast path take half the execution time.

Reduce line costs by half.

These have clear metrics, if perhaps unreasonable managers asserting them...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ajs@anvilwalrusden.com  Fri Aug  2 02:08:29 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57D511E8373 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level: 
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b9umaDdu6dyl for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:08:23 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 5D9B711E82F9 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 02:02:58 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-650a.meeting.ietf.org [130.129.101.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 74A9E8A031 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 09:02:57 +0000 (UTC)
Date: Fri, 2 Aug 2013 05:02:54 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: mic lines
Message-ID: <20130802090254.GH58539@mx1.yitter.info>
References: <51FA730A.3070800@stpeter.im> <20130802054822.GE23086@x28.adm.denic.de> <949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com> <20130802081630.GE58539@mx1.yitter.info> <05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 09:08:29 -0000

On Fri, Aug 02, 2013 at 08:40:42AM +0000, Adam Montville wrote:

> 
> Has anyone tried reminding everyone in line that the more time they take up, the less time they're leaving for others in the room (to handle most cases)?  Maybe that's naive.
> 

Oddly, this is an example of something ICANN does well.  There's a
shot-clock and a 30 second warning and a big buzzer.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From duerst@it.aoyama.ac.jp  Fri Aug  2 02:48:56 2013
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BA321E82AE for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.573
X-Spam-Level: 
X-Spam-Status: No, score=-101.573 tagged_above=-999 required=5 tests=[AWL=-1.783, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UDZ7-nYsYgY for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 02:48:50 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 56C8221E809B for <wgchairs@ietf.org>; Fri,  2 Aug 2013 02:48:44 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r729kg6F014022; Fri, 2 Aug 2013 18:46:42 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 35bf_8e6a_6f9b93ba_fb58_11e2_9ee9_001e6722eec2; Fri, 02 Aug 2013 18:46:41 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 6D3B7BF4E3; Fri,  2 Aug 2013 18:44:35 +0900 (JST)
Message-ID: <51FB7FEE.3010605@it.aoyama.ac.jp>
Date: Fri, 02 Aug 2013 18:46:22 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im>	<20130802054822.GE23086@x28.adm.denic.de>	<949EF20990823C4C85C18D59AA11AD8B07A93C@FR712WXCHMBA11.zeu.alcatel-lucent.com>	<20130802081630.GE58539@mx1.yitter.info>	<05BCCEB107AF88469B9F99783D47C1D673BAF1@CISEXCHANGE1.msisac.org.local> <20130802090254.GH58539@mx1.yitter.info>
In-Reply-To: <20130802090254.GH58539@mx1.yitter.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 09:48:57 -0000

On 2013/08/02 18:02, Andrew Sullivan wrote:

> Oddly, this is an example of something ICANN does well.  There's a
> shot-clock and a 30 second warning and a big buzzer.

Perhaps not so oddly. There are many more people at ICANN than at IETF 
who's main talent is talking, who like to make sure they have given all 
the right framing, haven't been impolite to anybody, and so on :-). So 
the need is bigger, and the implementation more worked out.

Regards,   Martin.

From adrian@olddog.co.uk  Fri Aug  2 03:24:08 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630ED21E8367 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 03:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhi5vML1btQ7 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 03:24:02 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 9283E21F8618 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 03:23:58 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r72ANsaW006582;  Fri, 2 Aug 2013 11:23:54 +0100
Received: from 950129200 (dhcp-13f0.meeting.ietf.org [130.129.19.240]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r72ANmlb006466 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Aug 2013 11:23:49 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Yaron Sheffer'" <yaronf.ietf@gmail.com>, "'Pete Resnick'" <presnick@qti.qualcomm.com>
References: <51FA4662.4050404@qti.qualcomm.com> <51FA773A.9040506@gmail.com>
In-Reply-To: <51FA773A.9040506@gmail.com>
Subject: RE: Successful BOF Sessions (RFC 5434) - Missing piece?
Date: Fri, 2 Aug 2013 11:23:46 +0100
Message-ID: <004701ce8f6a$6303ecb0$290bc610$@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: AQFwnSa9JQPtEq3pWW9/+/LSQ5A2HwJpDD3WmipRHzA=
Content-Language: en-gb
Cc: 'WG Chairs' <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 10:24:08 -0000

+1

I sometimes feel the question is "Who would be willing to put their hand =
up if I asked a question?"

A

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On =
Behalf
> Of Yaron Sheffer
> Sent: 01 August 2013 15:57
> To: Pete Resnick
> Cc: Thomas Narten; WG Chairs
> Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
>=20
> Hi Pete,
>=20
> I think this question is just too speculative to take seriously. Not
> your question here, the question you'd want asked at the BOF.
>=20
> Even when we ask people at a BOF, "who would be willing to =
edit/review",
> we know the responses are way too optimistic. So asking about
> implementations this early in the process is IMHO not useful, in that =
we
> cannot expect reliable information.
>=20
> Thanks,
> 	Yaron
>=20
> On 2013-08-01 13:28, Pete Resnick wrote:
> > I considered posting to the IETF main list, but I thought I'd start =
a
> > bit smaller.
> >
> > Ralph put up a slide in the DNSSDEXT BOF, which quoted a bit of RFC =
5434
> > that surprised me:
> >
> >     ...the goal of the BOF is to demonstrate that the community has
> >     agreement that:
> >
> >        - there is a problem that needs solving, and the IETF is the =
right
> >          group to attempt solving it.
> >
> >        - there is a critical mass of participants willing to work on =
the
> >          problem (e.g., write drafts, review drafts, etc.).
> >
> >        - the scope of the problem is well defined and understood, =
that
> >          is, people generally understand what the WG will work on =
(and
> >          what it won't) and what its actual deliverables will be.
> >
> >        - there is agreement that the specific deliverables (i.e.,
> >          proposed documents) are the right set.
> >
> >        - it is believed that the WG has a reasonable probability of
> >          having success (i.e., in completing the deliverables in its
> >          charter in a timely fashion).
> >
> > It seemed to me that there was a serious omission from this list:
> >
> >     - it is believed that there a critical mass of implementers who =
will
> >       use the output of the working group.
> >
> > In fact, I couldn't find the word "implement" anywhere in the =
document.
> > Do we just assume implementers but don't mention them, or (and I =
hope
> > this is not the case) do we really think that it is an irrelevant
> > question to consider regarding a successful BOF?
> >
> > pr
> >


From adam@nostrum.com  Fri Aug  2 05:46:07 2013
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E637211E8119 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 05:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4+kSZNy5caqV for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 05:46:07 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 71B8121E80D3 for <wgchairs@ietf.org>; Fri,  2 Aug 2013 05:46:01 -0700 (PDT)
Received: from dhcp-55a4.meeting.ietf.org (dhcp-55a4.meeting.ietf.org [130.129.85.164]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r72CjxXW020213 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Fri, 2 Aug 2013 07:46:00 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <51FBAA06.3090108@nostrum.com>
Date: Fri, 02 Aug 2013 14:45:58 +0200
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: IETF WG Chairs <wgchairs@ietf.org>
Subject: Please Note: IETF Tools Feedback
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 130.129.85.164 is authenticated by a trusted mechanism)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:46:08 -0000

During Wednesday's chair training session, it became clear that the 
means of providing feedback to the tools team have not been sufficiently 
publicized. I would implore everyone here to take note of the following 
information.

For clear bugs, please submit a new bug using the form here:

http://trac.tools.ietf.org/tools/ietfdb/newticket

If you have something you would like to discuss or ask, the proper place 
would be the tools-discuss mailing list:

https://www.ietf.org/mailman/listinfo/tools-discuss

Thanks!

/a

From pkyzivat@alum.mit.edu  Fri Aug  2 10:01:43 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1400821E8102 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 10:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.182
X-Spam-Level: 
X-Spam-Status: No, score=0.182 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RCVD_IN_SORBS_WEB=0.619, 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 t5rjNUXwR2F7 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 10:01:38 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id A7DDC21E80FF for <wgchairs@ietf.org>; Fri,  2 Aug 2013 10:01:36 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta01.westchester.pa.mail.comcast.net with comcast id 7oF11m0061swQuc51t1cJZ; Fri, 02 Aug 2013 17:01:36 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([89.246.150.136]) by omta15.westchester.pa.mail.comcast.net with comcast id 7szE1m00S2wpE7M3bszKam; Fri, 02 Aug 2013 16:59:31 +0000
Message-ID: <51FBE561.7080906@alum.mit.edu>
Date: Fri, 02 Aug 2013 18:59:13 +0200
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Please Note: IETF Tools Feedback
References: <51FBAA06.3090108@nostrum.com>
In-Reply-To: <51FBAA06.3090108@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1375462896; bh=/k1uHwvhNk01Z/CN+bnhm49xad9BK962bLqFPRFwSg8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=a5qCqMPC45UmgWXMAPfILUbV/cm3NCjBE5HimxQ9aXk9l0DesL5tmIKiO9m7dTz3V PfUYezfke+QluQ/dMJc4ZBlSEyio2Y5VXuvtY1dec0b//dqFG1ioImNshyL0mulT02 MngFmXRk1h2Rv0SRK/myVYPf55rlODAkai4Oa+2s04I6SlBvcujfMwbGs1CQBupAWH vOs8pti2lXmhm4+j1rssbn4I9FeZ65t4mgu+2lrU3F1umsrwzIq4Au/Sv5A+imOI3C 5DrF1B6xnjdDwIFms1R5G3Knk3fqBBq4m58sAkAjyES/0X+yp7QL5hWyGiNCMpqN6K oynUk5tto9aFA==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 17:01:43 -0000

On 8/2/13 2:45 PM, Adam Roach wrote:
> During Wednesday's chair training session, it became clear that the
> means of providing feedback to the tools team have not been sufficiently
> publicized. I would implore everyone here to take note of the following
> information.
>
> For clear bugs, please submit a new bug using the form here:
>
> http://trac.tools.ietf.org/tools/ietfdb/newticket
>
> If you have something you would like to discuss or ask, the proper place
> would be the tools-discuss mailing list:
>
> https://www.ietf.org/mailman/listinfo/tools-discuss

This is helpful. But it would be more helpful if all the tools pages had 
links for these.

	Thanks,
	Paul


From dcrocker@bbiw.net  Fri Aug  2 21:00:19 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7039A11E80E0 for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 21:00: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 6GRVQvE1hYBa for <wgchairs@ietfa.amsl.com>; Fri,  2 Aug 2013 21:00:14 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8700611E80DC for <wgchairs@ietf.org>; Fri,  2 Aug 2013 21:00:14 -0700 (PDT)
Received: from [10.140.221.9] ([88.128.80.12]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r73407bP024722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 21:00:12 -0700
Message-ID: <51FC8040.3060302@bbiw.net>
Date: Sat, 03 Aug 2013 06:00:00 +0200
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: Please Note: IETF Tools Feedback
References: <51FBAA06.3090108@nostrum.com> <51FBE561.7080906@alum.mit.edu>
In-Reply-To: <51FBE561.7080906@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Fri, 02 Aug 2013 21:00:13 -0700 (PDT)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 04:00:19 -0000

On 8/2/2013 6:59 PM, Paul Kyzivat wrote:
>
> This is helpful. But it would be more helpful if all the tools pages had
> links for these.


+1.  Easy and useful.

Wouldn't want that for a mass-market web page, but for our group, I'm 
sure everyone will be diligent and restrained...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From fred@cisco.com  Sat Aug  3 18:41:57 2013
Return-Path: <fred@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A2121F9ABB for <wgchairs@ietfa.amsl.com>; Sat,  3 Aug 2013 18:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdjYXgIbn0wz for <wgchairs@ietfa.amsl.com>; Sat,  3 Aug 2013 18:41:52 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id F2EE921E808F for <wgchairs@ietf.org>; Sat,  3 Aug 2013 18:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=439; q=dns/txt; s=iport; t=1375580511; x=1376790111; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=05jIA3tdG060ALg0vjdwPTyBkvvfgDOb70bAtV4mdFg=; b=EfflOWv8fU/HpY7t10mz3uH2+UEUIUXE+188hKEdcd3g74vE31EZZZwX iWTj38+A1bM5BiS/KKwVyOCX45JWRYo7p/gNvDXgRyhPber14HCm0My8p uZoTgpu4LsnNGU5XTIrsUNwO5g95JdsM/Zwwxk8xUPwvi0Dh9f1+dxkXx Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFABSw/VGtJXHA/2dsb2JhbABagwaBBYJJvEmBGxZ0giQBAQEBAgF5BQsCAQgiJDIlAgQOBQiIAga2MY9mAjEHgxl0A4hyoD2DF4Iq
X-IronPort-AV: E=Sophos;i="4.89,810,1367971200"; d="scan'208";a="243172725"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 04 Aug 2013 01:41:50 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r741foRJ032251 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 4 Aug 2013 01:41:50 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.235]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 20:41:49 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: mic lines
Thread-Topic: mic lines
Thread-Index: AQHOjw99Bjs8yfwfakmZxMJYam416JmEnTmA
Date: Sun, 4 Aug 2013 01:41:49 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B96D07A@xmb-rcd-x09.cisco.com>
References: <51FA730A.3070800@stpeter.im>
In-Reply-To: <51FA730A.3070800@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.214.111]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3ABD3282D6919847886D4A80A7779ADC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 01:41:57 -0000

On Aug 1, 2013, at 7:39 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

> At a session I participated in yesterday, several people were at the
> mic. One of the chairs said "the mic line is cut", by which he meant
> "those at the mic line need to sit down". I don't think that's how
> it's supposed to work.

I use the word "capped" rather than "cut", and by it I mean that new people=
 are not permitted to enter the line.=

From stpeter@stpeter.im  Sat Aug  3 21:22:59 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3BC11E80D2 for <wgchairs@ietfa.amsl.com>; Sat,  3 Aug 2013 21:22:59 -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 jcgZbetT9nVi for <wgchairs@ietfa.amsl.com>; Sat,  3 Aug 2013 21:22:54 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 49AEA21F9D9B for <wgchairs@ietf.org>; Sat,  3 Aug 2013 21:22:54 -0700 (PDT)
Received: from ergon.local (unknown [93.219.101.21]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 36441403AE; Sat,  3 Aug 2013 22:25:17 -0600 (MDT)
Message-ID: <51FDD71A.9060501@stpeter.im>
Date: Sun, 04 Aug 2013 06:22:50 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: mic lines
References: <51FA730A.3070800@stpeter.im> <0A894B74-5B80-4846-A957-ED9A126795F2@kumari.net>
In-Reply-To: <0A894B74-5B80-4846-A957-ED9A126795F2@kumari.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 04:22:59 -0000

On 8/2/13 9:32 AM, Warren Kumari wrote:
> 
> On Aug 1, 2013, at 4:39 PM, Peter Saint-Andre <stpeter@stpeter.im>
> wrote:
> 
>> Signed PGP part At a session I participated in yesterday, several
>> people were at the mic. One of the chairs said "the mic line is
>> cut", by which he meant "those at the mic line need to sit down". I
>> don't think that's how it's supposed to work.
>> 
> 
> Probably not how it is *supposed* to work, but I think that without
> more details (I read the rest of the thread) it is hard to tell…
> 
> If the chair knew that the rest of the conversation / folk in the
> line were simply going to spiral this into fist-fights and name
> calling and beard pulling then they may have done it to prevent an
> explosion. Or if it was clear that consensus was already figured out
> and everyone else just a: in the rough or b: simply wanting to chime
> and feel important…

I didn't see anything special going on in the session: no fights, no
time pressures, etc. That chair just decided he didn't want to hear from
anyone else on the point being discussed.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From acooper@cdt.org  Tue Aug  6 09:30:15 2013
Return-Path: <acooper@cdt.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045F421F99B8; Tue,  6 Aug 2013 09:30:15 -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 4K+Gna2yMPSn; Tue,  6 Aug 2013 09:30:10 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 6318D21F9A2E; Tue,  6 Aug 2013 09:30:09 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 6 Aug 2013 12:30:05 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Trial of privacy tutorial at IETF 87
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
Date: Tue, 6 Aug 2013 12:30:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1FE5759-2AB1-40D3-9E95-CEEAC3364035@cdt.org>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF EDU Team <edu-team@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 16:30:15 -0000

Hi all,

Thanks to everyone who came and provided feedback on the privacy =
tutorial last week. The video is available here: =
<http://recordings.conf.meetecho.com/Recordings/watch.jsp?recording=3DIETF=
87_PRIVACY_TUTORIAL&chapter=3Dpart_1>. If folks have further feedback, =
please send it to privacy-program@iab.org.

Thanks,
Alissa

On Jul 11, 2013, at 2:14 PM, Alissa Cooper <acooper@cdt.org> wrote:

> Hi all,
>=20
> The IAB privacy program has put together a privacy tutorial for IETF =
participants. We'd like to trial it with a small group of folks =
interested in providing feedback before we expand to presenting the =
tutorial to a larger group. We have a trial run of the tutorial =
scheduled for Sunday, July 28 from 9:15 to 10:30 at the meeting venue in =
Berlin.=20
>=20
> If you're interested in attending and providing feedback, please reply =
to me and I'll follow up with you. We're looking for about a dozen folks =
with different areas of expertise, most of whom would not consider =
themselves privacy experts.
>=20
> Thanks,
> Alissa
>=20



From narten@us.ibm.com  Mon Aug 12 10:04:47 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2573D21F9BA4 for <wgchairs@ietfa.amsl.com>; Mon, 12 Aug 2013 10:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.469
X-Spam-Level: 
X-Spam-Status: No, score=-110.469 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_BEASTUD=0.26, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8nntk2HLG7H for <wgchairs@ietfa.amsl.com>; Mon, 12 Aug 2013 10:04:40 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id D730921F85C9 for <wgchairs@ietf.org>; Mon, 12 Aug 2013 09:45:05 -0700 (PDT)
Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <wgchairs@ietf.org> from <narten@us.ibm.com>; Mon, 12 Aug 2013 10:45:05 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 12 Aug 2013 10:44:53 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 5124A19D804C for <wgchairs@ietf.org>; Mon, 12 Aug 2013 10:44:40 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7CGiqOq208726 for <wgchairs@ietf.org>; Mon, 12 Aug 2013 10:44:52 -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 r7CGld97006862 for <wgchairs@ietf.org>; Mon, 12 Aug 2013 10:47:39 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-146-100.mts.ibm.com [9.49.146.100]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7CGlbPL006776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Aug 2013 10:47:39 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r7CGinLX014047; Mon, 12 Aug 2013 12:44:50 -0400
Message-Id: <201308121644.r7CGinLX014047@cichlid.raleigh.ibm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Successful BOF Sessions (RFC 5434) - Missing piece?
In-reply-to: <51FA4662.4050404@qti.qualcomm.com>
References: <51FA4662.4050404@qti.qualcomm.com>
Comments: In-reply-to Pete Resnick <presnick@qti.qualcomm.com> message dated "Thu, 01 Aug 2013 13:28:34 +0200."
Date: Mon, 12 Aug 2013 12:44:49 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13081216-5518-0000-0000-000011226947
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:04:47 -0000

> In fact, I couldn't find the word "implement" anywhere in the document. 
> Do we just assume implementers but don't mention them, or (and I hope 
> this is not the case) do we really think that it is an irrelevant 
> question to consider regarding a successful BOF?

FWIW, some more words would probably be helpful. But it would require
nuance...

I could be flippant and note that in today's internet, one can pretty
much always find an implementation of just about everything. I.e.,
could be a student project in linux. Thus, even asking about
"implementations" needs to be more nuanced, with a key aspect
presumably being an implementation that is "real" and would be the
basis for "real" deployment/usage.

Up-leveling, an important theme is "understand the real/actual end
customer" of the work and what their real commitment to using the
output will be. If no such "real" end customer actually exists (or if
they are not in the room helping forumlate the requirements), be
skeptical of forming a WG.

Thomas


From iad@ietf.org  Mon Aug 12 14:54:37 2013
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D48A21F9F44; Mon, 12 Aug 2013 14:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-FRk2fXGBff; Mon, 12 Aug 2013 14:54:36 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9DD21F9F2B; Mon, 12 Aug 2013 14:54:35 -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: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Mon, 12 Aug 2013 14:54:35 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 21:54:39 -0000

The RFC Series Editor (RSE) is proposing changes to the Statements of Work =
(SOW) for the RFC =

Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive c=
ommunity input prior to =

negotiating the proposed changes with the contractor.  Community input will=
 be discussed with the RSE =

prior to negotiations and reviewed by the IAOC.

In forwarding the proposed Statements of Work the RSE said:  "The changes s=
eek to make the SoWs =

more current [implementing RFC 6635] and specific, correcting the issues of=
 "multiple masters" =

directing the RPC and Publisher, as well as preparing the way for a more si=
gnificant revision to the SoWs
when the RFC Format changes are operationalized.  The SoWs have also been r=
eviewed and supported =

by the RSOC [RFC Series Oversight Committee].  We consider the changes with=
in the SoWs critical to the =

clear function of the RPC and Publisher, but suggest that the changes do no=
t imply a significant change =

in responsibility for the RPC or Publisher."

The proposed SOWs, the current SOWs and a diff file for each can be found h=
ere under Community =

Review: <http://iaoc.ietf.org/rfps.html>

We appreciate the community's input and look forward to hearing from you.  =


Thanks

Ray Pelletier
IAD

From framefritti@gmail.com  Tue Aug 13 00:36:16 2013
Return-Path: <framefritti@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67FEC21E80B9; Tue, 13 Aug 2013 00:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.001,  NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SERZDn8X7wLP; Tue, 13 Aug 2013 00:36:16 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB7321F99B8; Tue, 13 Aug 2013 00:36:13 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so7608978pbb.20 for <multiple recipients>; Tue, 13 Aug 2013 00:36:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0C9gdWz36drHvd10IpsuZ9sSGryjmplDrEMb7oK5fmg=; b=JFYy+PSZdUyhHrzdLgSDo13NNjxNy0jg6KobffwQ/cJudCgYzCHuYJeQm18Hxf4Soy yQnSLIqPqcgpFdy+PKaqYXM0be6rOLBoHXRWuFxy+2ud5XWcsT4NVltj+Aja3/0LLf7C +M35IVabkc4c4drVU6A4HdVPFM5OF7VKm0bVQVGIqy2aJSVJGdcJw92F0iF96xySftPu 5QvuM7oZjvwJTezuW6MXhq2fohh5ssNNQQMlEtzxhB3meAJ8p8gKMbIRc+yvTus8n7CT RFV8eWVP50mUuWFYCC5jIOnofngo4PCXo0QCKta+lbiuFOC3FzWcBY9XB+nbVBsNco3f ZzJQ==
MIME-Version: 1.0
X-Received: by 10.68.242.105 with SMTP id wp9mr3113037pbc.153.1376379372824; Tue, 13 Aug 2013 00:36:12 -0700 (PDT)
Received: by 10.70.27.97 with HTTP; Tue, 13 Aug 2013 00:36:12 -0700 (PDT)
In-Reply-To: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Tue, 13 Aug 2013 09:36:12 +0200
Message-ID: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Tue, 13 Aug 2013 07:15:47 -0700
Cc: wgchairs@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>, iab@iab.org, iaoc@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 07:36:16 -0000

Is this the document with the proposed SOW?

   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc

I know that I should not this, but... I am a bit surprised
(disappointed) in seeing a proprietary format used here.  I am not
saying that you should not use the Office suite to write it, but you
could convert it to PDF (better, PDF/A) before publishing it.

Anyway, I use Linux, so I guess I will not be able to give my input about it.

Best regards,

Riccardo


On Mon, Aug 12, 2013 at 11:54 PM, IETF Administrative Director
<iad@ietf.org> wrote:
> The RFC Series Editor (RSE) is proposing changes to the Statements of Work (SOW) for the RFC
> Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive community input prior to
> negotiating the proposed changes with the contractor.  Community input will be discussed with the RSE
> prior to negotiations and reviewed by the IAOC.
>
> In forwarding the proposed Statements of Work the RSE said:  "The changes seek to make the SoWs
> more current [implementing RFC 6635] and specific, correcting the issues of "multiple masters"
> directing the RPC and Publisher, as well as preparing the way for a more significant revision to the SoWs
> when the RFC Format changes are operationalized.  The SoWs have also been reviewed and supported
> by the RSOC [RFC Series Oversight Committee].  We consider the changes within the SoWs critical to the
> clear function of the RPC and Publisher, but suggest that the changes do not imply a significant change
> in responsibility for the RPC or Publisher."
>
> The proposed SOWs, the current SOWs and a diff file for each can be found here under Community
> Review: <http://iaoc.ietf.org/rfps.html>
>
> We appreciate the community's input and look forward to hearing from you.
>
> Thanks
>
> Ray Pelletier
> IAD

From keith.drage@alcatel-lucent.com  Tue Aug 13 08:04:47 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 889AE21E816D for <wgchairs@ietfa.amsl.com>; Tue, 13 Aug 2013 08:04:47 -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 UXOO+vExEeKA for <wgchairs@ietfa.amsl.com>; Tue, 13 Aug 2013 08:04:42 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 02A0121E80FA for <wgchairs@ietf.org>; Tue, 13 Aug 2013 08:04:41 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r7DF4cj7012629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 13 Aug 2013 10:04:40 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r7DF4bQk008932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 13 Aug 2013 17:04:37 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 13 Aug 2013 17:04:37 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Riccardo Bernardini <framefritti@gmail.com>
Subject: RE: Community Input Sought on SOWs for RFC Production Center and RFC	Publisher
Thread-Topic: Community Input Sought on SOWs for RFC Production Center and RFC	Publisher
Thread-Index: AQHOmC+g6asimUrBF06wI+r9mAHakpmTO9Ow
Date: Tue, 13 Aug 2013 15:04:36 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B081BFB@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
In-Reply-To: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 15:04:47 -0000

Not objecting you your comments, but

The document opens perfectly well in OpenOffice (revision marks and all), w=
hich I believe is supported on Linux.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Riccardo Bernardini
> Sent: 13 August 2013 08:36
> To: IETF Discussion
> Cc: wgchairs@ietf.org; RFC Interest; iab@iab.org; iaoc@ietf.org
> Subject: Re: Community Input Sought on SOWs for RFC Production Center and
> RFC Publisher
>=20
> Is this the document with the proposed SOW?
>=20
>    http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc
>=20
> I know that I should not this, but... I am a bit surprised
> (disappointed) in seeing a proprietary format used here.  I am not
> saying that you should not use the Office suite to write it, but you
> could convert it to PDF (better, PDF/A) before publishing it.
>=20
> Anyway, I use Linux, so I guess I will not be able to give my input about
> it.
>=20
> Best regards,
>=20
> Riccardo
>=20
>=20
> On Mon, Aug 12, 2013 at 11:54 PM, IETF Administrative Director
> <iad@ietf.org> wrote:
> > The RFC Series Editor (RSE) is proposing changes to the Statements of
> Work (SOW) for the RFC
> > Production Center (RPC) and the RFC Publisher.  The IAOC wants to
> receive community input prior to
> > negotiating the proposed changes with the contractor.  Community input
> will be discussed with the RSE
> > prior to negotiations and reviewed by the IAOC.
> >
> > In forwarding the proposed Statements of Work the RSE said:  "The
> changes seek to make the SoWs
> > more current [implementing RFC 6635] and specific, correcting the issue=
s
> of "multiple masters"
> > directing the RPC and Publisher, as well as preparing the way for a mor=
e
> significant revision to the SoWs
> > when the RFC Format changes are operationalized.  The SoWs have also
> been reviewed and supported
> > by the RSOC [RFC Series Oversight Committee].  We consider the changes
> within the SoWs critical to the
> > clear function of the RPC and Publisher, but suggest that the changes d=
o
> not imply a significant change
> > in responsibility for the RPC or Publisher."
> >
> > The proposed SOWs, the current SOWs and a diff file for each can be
> found here under Community
> > Review: <http://iaoc.ietf.org/rfps.html>
> >
> > We appreciate the community's input and look forward to hearing from yo=
u.
> >
> > Thanks
> >
> > Ray Pelletier
> > IAD

From rpelletier@isoc.org  Tue Aug 13 09:04:44 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A216521E817D; Tue, 13 Aug 2013 09:04:43 -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 pZgNVuJA1ETt; Tue, 13 Aug 2013 09:04:43 -0700 (PDT)
Received: from smtp77.ord1c.emailsrvr.com (smtp77.ord1c.emailsrvr.com [108.166.43.77]) by ietfa.amsl.com (Postfix) with ESMTP id AC01211E8183; Tue, 13 Aug 2013 09:04:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A37FA1E81AB; Tue, 13 Aug 2013 12:04:30 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 1C73F1E829E;  Tue, 13 Aug 2013 12:04:30 -0400 (EDT)
Subject: Re: [rfc-i] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Date: Tue, 13 Aug 2013 12:04:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCE46403-65AC-4405-B8FB-14D378E4AFF6@isoc.org>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
To: Riccardo Bernardini <framefritti@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 16:04:44 -0000

Riccardo

All of the DOC files are in the process of being replaced with PDF =
files.

I apologize for the inconvenience and angst this caused.

Ray


On Aug 13, 2013, at 3:36 AM, Riccardo Bernardini wrote:

> Is this the document with the proposed SOW?
>=20
>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc
>=20
> I know that I should not this, but... I am a bit surprised
> (disappointed) in seeing a proprietary format used here.  I am not
> saying that you should not use the Office suite to write it, but you
> could convert it to PDF (better, PDF/A) before publishing it.
>=20
> Anyway, I use Linux, so I guess I will not be able to give my input =
about it.
>=20
> Best regards,
>=20
> Riccardo
>=20
>=20
> On Mon, Aug 12, 2013 at 11:54 PM, IETF Administrative Director
> <iad@ietf.org> wrote:
>> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC
>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to
>> negotiating the proposed changes with the contractor.  Community =
input will be discussed with the RSE
>> prior to negotiations and reviewed by the IAOC.
>>=20
>> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs
>> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"
>> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
>> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported
>> by the RSOC [RFC Series Oversight Committee].  We consider the =
changes within the SoWs critical to the
>> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change
>> in responsibility for the RPC or Publisher."
>>=20
>> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community
>> Review: <http://iaoc.ietf.org/rfps.html>
>>=20
>> We appreciate the community's input and look forward to hearing from =
you.
>>=20
>> Thanks
>>=20
>> Ray Pelletier
>> IAD
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest


From execd@iab.org  Thu Aug 15 15:22:31 2013
Return-Path: <execd@iab.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4DDD11E8210 for <wgchairs@ietfa.amsl.com>; Thu, 15 Aug 2013 15:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.045
X-Spam-Level: 
X-Spam-Status: No, score=-102.045 tagged_above=-999 required=5 tests=[AWL=0.555, 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 yjHGhTjO4cyJ for <wgchairs@ietfa.amsl.com>; Thu, 15 Aug 2013 15:22:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EE04311E81B9 for <wgchairs@ietf.org>; Thu, 15 Aug 2013 15:22:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IAB Executive Director <execd@iab.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: Deadline Extended: CFP: IAB Workshop on Internet Technology Adoption and Transition (ITAT) December 4-6 in Cambridge, UK
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130815222230.7611.30982.idtracker@ietfa.amsl.com>
Date: Thu, 15 Aug 2013 15:22:30 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: execd@iab.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 22:42:33 -0000

Please note the extended deadline and clarification of what is desired in
statements of interest.  Those who have submitted need take no action.

Title
    Workshop on Internet Technology Adoption and Transition (ITAT)
Date
    December 4-6(*)
Place
    Cambridge, UK

Who Should Attend
    Economists, management scientists, and other researchers
    interested in technology diffusion,  computer scientists  and
    engineers who are interested in improving likelihood of
    deployment success, and operators who can provide insights
    into their needs and challenges with regard to new technology.

Prerequisite:            A 3 - 10 page statement of interest
                        (see new information below)
Submission Deadline:     August 29, 2013
Submission URL:
https://www.easychair.org/conferences/?conf=3Ditat-2013
Acceptance Date:     September 11, 2013 (or earlier)


The Internet is a complex ecosystem that encompasses all aspects of
society.  At its heart is a protocol stack with an hourglass shape,
and IP at its center.  Recent research points to possible explanations
for the success of such a design and for the significant challenges
that arise when trying to evolve or change its middle section.  The
difficulty in transitioning from IPv4 to IPv6 seems to illustrate this
point. We have a number of other key examples of technology transition
to consider, including the next generation of web technologies,
including HTTP version 2 and real time communications on the web
(WebRTC).  The eventual success of many if not all of these protocols
will largely depend on our understanding of not only what features and
design principles contribute lasting value, but also on how early
deployment strategies can succeed in unlocking that value to foster
protocol adoption.  The latter is particularly important in that most
if not all Internet protocols exhibit significant externalities that
create strong barriers to adoption, especially in the presence of a
well-established incumbent.  Taking into account RFC 5218, which
discusses what makes a protocol successful, this workshop seeks to
explore how the complex interactions of protocol design and
deployment affect their success.  One workshop goals is, therefore, to
encourage discussions that lead to an understanding of what makes
protocols designs successful, not only in fulfilling the initial
design goals for the protocol, but more importantly in their ability
to evolve with changing protocol goals and technology.

Another equally important workshop goal is to develop protocol
deployment strategies that enable new features to rapidly gain a
foothold and ultimately realize broad adoption.  Such strategies must
be informed by both operational and economic factors.

Suggested topics include

  * Economic / evolutionary models that can provide a view toward
    identification of the factors leading to a protocol's success in
    the field

  * Studies that evaluate existing deployments of protocols that have
    succeeded or failed

  * Operators' experiences about economics of deployment of new
    features (both successful or otherwise)

  * Intersection of policy and economics with respect to technology
    diffusion

  * Studies of standards organizations and their processes and the
    effects on technology diffusion

  * Strategies to foster rapid and cost-effective adoption


Participation will be limited.  Interested parties should submit a
brief (3-10 page) statement of interest that describes ongoing or
recent related research and experience on the topic, with an eye
toward engaging a diverse audience.

Please submit using the EasyChair conference management system at the
following URL:

   https://www.easychair.org/conferences/?conf=3Ditat-2013

Submissions are due no later than August 29, 2013.  The IAB will
inform those accepted no later than September 11th.  The workshop
itself will be between 2 and 2.5 days.  Further information on this
will follow.

From rpelletier@isoc.org  Fri Aug 16 11:47:50 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C106911E8186; Fri, 16 Aug 2013 11:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEkThqIbLaUO; Fri, 16 Aug 2013 11:47:50 -0700 (PDT)
Received: from smtp101.ord1c.emailsrvr.com (smtp101.ord1c.emailsrvr.com [108.166.43.101]) by ietfa.amsl.com (Postfix) with ESMTP id 846DA11E8200; Fri, 16 Aug 2013 11:47:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D2B121B0081; Fri, 16 Aug 2013 14:47:41 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 78CC91B0187;  Fri, 16 Aug 2013 14:47:41 -0400 (EDT)
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Fri, 16 Aug 2013 14:47:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:47:51 -0000

All;

Are there any more comments on the SOWs?

This item will be on the IAOC agenda for its call on 22 August.

Ray

On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:

> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC=20
> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to=20
> negotiating the proposed changes with the contractor.  Community input =
will be discussed with the RSE=20
> prior to negotiations and reviewed by the IAOC.
>=20
> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs=20
> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"=20
> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported=20
> by the RSOC [RFC Series Oversight Committee].  We consider the changes =
within the SoWs critical to the=20
> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change=20
> in responsibility for the RPC or Publisher."
>=20
> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community=20
> Review: <http://iaoc.ietf.org/rfps.html>
>=20
> We appreciate the community's input and look forward to hearing from =
you. =20
>=20
> Thanks
>=20
> Ray Pelletier
> IAD


From sginoza@amsl.com  Fri Aug 16 13:16:39 2013
Return-Path: <sginoza@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B51911E8151; Fri, 16 Aug 2013 13:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gW8zsMZm+4h4; Fri, 16 Aug 2013 13:16:37 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 8117011E8141; Fri, 16 Aug 2013 13:16:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 64365A60D2; Fri, 16 Aug 2013 13:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XYAfIepclAf; Fri, 16 Aug 2013 13:15:17 -0700 (PDT)
Received: from new-host-5.home (pool-108-0-223-143.lsanca.fios.verizon.net [108.0.223.143]) by c9a.amsl.com (Postfix) with ESMTPA id C3632A60D1; Fri, 16 Aug 2013 13:15:16 -0700 (PDT)
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-808--1054962467
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
Date: Fri, 16 Aug 2013 13:16:35 -0700
Message-Id: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 20:16:39 -0000

--Apple-Mail-808--1054962467
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Greetings,

Since the publication of RFC 5620, the RFC Editor has been working to =
implement the RPC and Publisher split.  Based on our attempts to create =
two separable entities per RFC 5620 and later RFC 6635, our =
understanding of the motivations for splitting the RPC and Publisher =
into distinct functions, and our discussions with the RSE, the RSE has =
created a figure =
<http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpublisher&m=
edia=3Drfc-publisher-split-c.jpg> to describe where the split resides in =
practice.  We believe the figure accurately reflects the most practical =
split in terms of work allocation and portability. =20

The split described in the figure eliminates the need for the Publisher =
to have staff with detailed RFC-specific knowledge by placing the =
majority of staff-related responsibilities with the RPC. Our =
understanding is that it is important for the SoWs to be aligned with =
the split described in the figure, so many of our comments below are an =
attempt to align these documents.  We provide our comments below for =
consideration.=20

Thank you,
Sandy Ginoza=20
(for the RPC and Publisher)


Notes:=20
------

"Current" refers to text as provided in the Proposed SoWs:=20
  http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf
  http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf

"Figure" refers to the figure available at=20
  =
http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpublisher&me=
dia=3Drfc-publisher-split-c.jpg


RFC Production Center
---------------------

1) In the following, we suggest changing "reference IETF documents (RFCs =
and Internet Drafts)" to "referenced documents (RFCs and Internet =
Drafts)" because not all RFCs/I-Ds are IETF-stream documents.

Current:
1.2.  Validation of references

Ensure that references within specifications are available and that =
referenced IETF documents (RFCs and Internet Drafts) are latest versions =
available.  Also, match citations and references for consistency.  In =
the IETF standards stream, specific rules on the suitability and =
availability of references apply, as documented in RFC 2026 and =
successors, as interpreted by the IESG.  Editing of documents may be =
delayed waiting for normative references to become available.


2) In the following, we suggest that "ASN.1 (and particularly MIBs and =
MIB-related details)" be updated to reflect "MIBs".  Although MIB =
modules are written using a subset of ASN.1, the RPC does not check all =
ASN.1, we only check MIBs.  This change will reflect what is done in =
practice.  If the intent is to actually require the RPC to check all =
ASN.1, please let us know and we will discuss checking tools with the =
RSE and IAD.

Current:
1.3.  Validation of formal languages

The RPC should validate the syntax of sections of documents containing =
formal languages.  In particular ASN.1 (and particularly MIBs and =
MIB-related details), YANG, ABNF, and XML should be verified using one =
or more tools as approved by the RSE.     =20


3) Publication takes place in the "Electronic Signing & Announcements" =
box within the figure.  The following text does not seem to align with =
the figure:

Current:
2.     Documents forwarded to RFC Publisher

2.1.  The RPC will edit the documents from all streams consistent with =
the RFC Style Manual, the RFC Series, and the intent of the Authors.  =
Documents so edited will be placed in the ready-to-publish state and =
forwarded to the RFC Publisher.

In the figure, the publication-related actions occur on the RPC side =
because the RPC is responsible for posting RFCs in the public archive, =
sending out the RFC announcements, updating the various indexes, and =
digitally signing the RFCs.  This makes it possible for the RPC to =
respond to requests for legal verification of RFCs.  Therefore, we =
suggest the following update:=20

2. Documents forwarded to RFC Publisher

2.1. The RPC will edit the documents from all streams consistent with =
the RFC Style Manual, the RFC Series, and the intent of the Authors.  =
Documents so edited will be published on the RFC Editor website.=20

Alternately, Section 2.1 could be removed, as the documents will not be =
forwarded to the "Publisher" for publication and because how docs will =
be edited is discussed in Section 1.1.1. =20


For consistency with the above update, we suggest that item 2.2 be =
updated as follows:

Current:
2.2. Additionally, the RPC will forward records of all interaction and =
edits relative to the document, including dialogue with the document =
authors and stream representatives, to the RFC Publisher for archiving.

Suggested:
2.2. The RPC will post all relevant documents, including the related RFC =
files, records of all interaction and edits relative to the document, =
dialogue with the document authors and stream representatives, on the =
RFC Publisher server for archiving.


4) Because the Publisher is responsible for the website, =
webmaster@rfc-editor.org is a Publisher address (and the address in =
mentioned in the Publisher SoW). We suggest that =
"webmaster@rfc-editor.org" be removed from the text below.

Current:
6.2.  Response to general questions directed to =
rfc-editor@rfc-editor.org and webmaster@rfc-editor.org, coordinating as =
necessary with the RFC Publisher and RSE.


5) If item 3 (above) is accepted and Section 2.1 is updated or removed =
from the SoW, the Work Standards should be updated to refer to =
"publication" or "published" instead of "Forwarded Date" or "forwarded", =
for example:

Current:
A.2.1.1. A document is =93received=94 by the RPC on the date of the =
receipt of a request to publish by the each of the respective streams =
(Receipt Date).

A.2.1.2. A document is =93ready-to-publish=94 on the date it is =
forwarded to the RFC Publisher by the RPC (Forwarded Date).   =20

We suggest:
A.2.1.1. A document is =93received=94 by the RPC on the date of the =
receipt of a request to publish by the each of the respective streams =
(Receipt Date).

A.2.1.2. A document is "published" on the date the RFC is made available =
on the RFC Editor website and the RFC announcement is sent (Publication =
Date).

Note that the contractual definition of the "Publication Date" is not =
new; it is currently defined in =
http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24-11_000.=
pdf as=20

The date of announcement is defined as the date of publication.=20


If "Forwarded Date" is changed to "Publication Date", then these items =
should also be updated:

Current:
A.2.2.1. Processing times per document are from Receipt Date to =
Forwarded Date in total business days.

A.2.2.2. While the overall goal for document publication is 30 business =
days (6 weeks) from Receipt Date to Forwarded Date, the times measured =
in the defined Service Levels are times in RPC state.


6)  We suggest removing the first sentence of A.2.2.4 because it is =
redundant with earlier text and is not as clear as A.2.2.2, which can be =
summarized as:=20

- Overall goal: time in all states (RFC-Editor-controlled states + 3rd =
party states) < 6 weeks
- Actually measured for SLA: time in RFC-Editor-controlled states

Note that we also recommend changing "RPC state" to =
"RFC-Editor-controlled states" throughout for clarity.  Alternately, we =
suggest that "RPC State" be defined as special term.=20


Publisher
---------

7) In our understanding of the figure, the Publisher function provides =
access to the post-publication data, but the RPC would actually make any =
changes to post-publication data.  So, it seems inaccurate to include =
the Publisher is 'responsible for [...] post-publication data'.  =
Therefore, we suggest the following update:

Current:
The RFC Publisher function is described in RFC 6635 and is responsible =
for the storage and post-publication data for RFCs, access to the =
website, access to the errata reports, search tools and indexes, the =
archive of documents, and all backups and failover processes.

Suggested:
The RFC Publisher function is described in RFC 6635 and is responsible =
for the storage of and access to the website, errata reports, search =
tools and indexes, the archive of documents, and all backups and =
failover processes.


8) As mentioned in item 3 above, we believe that the action of =
publishing documents, and therefore the publication processes, are the =
responsibility of the RPC.  With that in mind, we suggest the following =
update to the Overview:

Current:
The Publisher will accept, store and publish documents from the RFC =
Production Center and
other material as determined by the RSE.  The RSE may authorize other =
entities to submit
documents directly for publication, but those documents are published on =
the authority of the
RSE.  Changes to the publication process and public-facing tools will be =
made under the advice
and approval of the RSE.

Suggested:
The Publisher will accept and store documents from the RFC Production =
Center and other material as determined by the RSE. =20

We suggest that the remainder of the text be removed.  While the =
Publisher houses the tools used by the various RFC Editor components, it =
is the various components that have the staff to suggest and implement =
changes to the publication process and tools.

Also, it is not clear to us what is meant by "other entities to submit =
documents directly for publication".  Does this refer to web content or =
perhaps I-Ds that are to be published without being edited?  Both of =
these cases seem to fall into the RPC SoW, as the RPC is responsible for =
content on the website, and even if an I-D is to be published without =
changes, it would need to be updated to conform with current format and =
boilerplate standards.  Are there other cases in which this "directly =
for publication" may apply?


9) To make it clear that the RPC updates various data, and the Publisher =
simply makes it available on a server, we suggest changing these =
instances of "publish" and "post" to "make available" as follows:

Current:
RFCs are published on the Publisher=92s website. This site includes one =
or more indexes with hyperlinked access to published documents as well =
as a convenient search engine.

Suggested:
RFCs are made available on the Publisher=92s website. This site includes =
one or more indexes with hyperlinked access to published documents as =
well as a convenient search engine.

(Note: SM also suggested making "Publisher's website" be "RFC Editor =
website")


Current:
1.2.5.     post Web content as provided by the RSE, ISE, and/or the RFC =
Production Center,

We suggest deleting Section 1.2.5 from the Publisher SoW or updating it =
to read:
      1.2.5.     make available Web content as provided by the RSE, ISE, =
and/or the RFC Production Center,


Current:=20
3.1.1.  Publish state information for each document in the publication =
process.

Suggested:=20
3.1.1.  State information for each document in the publication process.


10) With the understanding that the RPC is responsible for creating and =
maintaining the web content (which presumably includes organizing the =
web content), and the Publisher for serving the content, we suggest this =
item be altered as follows. (Also: second sentence deleted because =
already covered in 1.2.6.)

Current:
1.2.7.     provide continual incremental improvements, including =
regularly redesigning web page trees to respond to common usage =
patterns.  However, stable identifiers must be maintained for the RFCs, =
archives, Errata, indices and other items.

Suggested:
1.2.7.  provide data about the website usage patterns so that the =
maintainers of the web content can organize it accordingly.


11) We believe the following item should be updated because an address =
should be provided to reach the Publisher (and this same address is used =
numerous times in Appendix 1 for items for which the Publisher is =
responsible) and because the RPC should not be a middleman in cases of =
server failure, etc.=20

Current:=20
1.4. Customer Support Services. Messages sent to certain conventional =
addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall =
automatically be delivered to the RFC Production Center

Suggested:=20
1.4. Customer Support Services. Messages sent to certain conventional =
addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall =
be coordinated with the RPC as appropriate.


12) We question whether integration is really a publisher task.  The RPC =
has a programmer, so it seems the RPC would be responsible for the =
programming aspects and the Publisher would be responsible for ensuring =
the right access/security for integration.=20

Current:
3.1.2.     Integrate Production Center state information with the IETF =
tools or such other tool sets as directed by the RSE to provide =
end-to-end status tracking of documents=20

Perhaps Section 3.1.2 should be deleted, as Section 2.3.2 indicates that =
the Publisher should provide appropriate access for integration.


13) We suggest removing item 3.1.3, because it seems to be covered by =
providing state information, as described in Section 3.1.1.

Current:
3.1.3.     Provide external visibility regarding when a document is in =
an extended waiting period, the token-holder and circumstances of the =
wait.


14) While the Publisher may participate in discussions about the =
technical support systems required to address policy changes, we do not =
believe the Publisher needs to be involved in discussion regarding all =
publication policy changes.  Therefore, we suggest the following update:

Current:
6.1.  Participate in the discussions of the technical publication =
process with the RSE for policy changes.

Suggested:
6.1.  Participate in policy discussions about technical support of the =
publication process.=20


15) It is not clear to us that the Publisher enforces RFC Series =
consistency, as the Publisher is responsible for making the files =
available and maintaining the archives.

Current:=20
7.  Accountability

The Publisher is primarily responsible to the RSE as regards to RFC =
Series consistency.

Perhaps this should be updated as:
7.  Accountability

The Publisher is primarily responsible to the RSE regarding technical =
support and hosting of the RFC Series.=20


15) The Work Standards are listed in "Exhibit B", but there is no =
"Exhibit A" - is some text missing, or should Exhibit B be Exhibit A?


On Aug 16, 2013, at 11:47 AM, Ray Pelletier wrote:

> All;
>=20
> Are there any more comments on the SOWs?
>=20
> This item will be on the IAOC agenda for its call on 22 August.
>=20
> Ray
>=20
> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
>=20
>> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC=20
>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to=20
>> negotiating the proposed changes with the contractor.  Community =
input will be discussed with the RSE=20
>> prior to negotiations and reviewed by the IAOC.
>>=20
>> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs=20
>> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"=20
>> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
>> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported=20
>> by the RSOC [RFC Series Oversight Committee].  We consider the =
changes within the SoWs critical to the=20
>> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change=20
>> in responsibility for the RPC or Publisher."
>>=20
>> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community=20
>> Review: <http://iaoc.ietf.org/rfps.html>
>>=20
>> We appreciate the community's input and look forward to hearing from =
you. =20
>>=20
>> Thanks
>>=20
>> Ray Pelletier
>> IAD
>=20


--Apple-Mail-808--1054962467
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>Greetings,</div><div><br><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Since the publication of RFC 5620, the RFC Editor has been =
working to implement the RPC and Publisher split. &nbsp;Based on our =
attempts to create two separable entities per RFC 5620 and later RFC =
6635, our understanding&nbsp;of the motivations for splitting the RPC =
and Publisher into distinct functions, and our discussions with the RSE, =
the&nbsp;RSE has created a&nbsp;figure &lt;<a =
href=3D"http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpubl=
isher&amp;media=3Drfc-publisher-">http://www.rfc-editor.org/rse/wiki/lib/e=
xe/detail.php?id=3Drfcpublisher&amp;media=3Drfc-publisher-</a>split-c.jpg&=
gt; to describe where the split resides in practice. &nbsp;We believe =
the figure&nbsp;accurately reflects the most&nbsp;practical split in =
terms of work allocation&nbsp;and portability. =
&nbsp;</div></div></div></div><br><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>The split described in the =
figure eliminates the need&nbsp;for the Publisher to have staff with =
detailed RFC-specific knowledge by placing the majority of =
staff-related&nbsp;responsibilities with the RPC.&nbsp;Our understanding =
is that it is important for the SoWs to be aligned with the =
split&nbsp;described in the figure, so many of our comments below are an =
attempt to align these documents. &nbsp;We provide our comments below =
for =
consideration.&nbsp;</div></div></div></div></div></div><div><br>Thank =
you,<br>Sandy Ginoza&nbsp;</div><div>(for the RPC and =
Publisher)<br><br><br>Notes:&nbsp;<br>------<div><br>"Current" refers to =
text as provided in the Proposed SoWs:&nbsp;<br>&nbsp;&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf">ht=
tp://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf</a><br>&nbsp;=
&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf=
">http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf</a><b=
r><br>"Figure" refers to the figure available at&nbsp;<br>&nbsp;&nbsp;<a =
href=3D"http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpubl=
isher&amp;media=3Drfc-publisher-split-c.jpg">http://www.rfc-editor.org/rse=
/wiki/lib/exe/detail.php?id=3Drfcpublisher&amp;media=3Drfc-publisher-split=
-c.jpg</a><br><br><br>RFC Production =
Center<br>---------------------<br><br>1) In the following, we suggest =
changing "reference IETF documents (RFCs and Internet Drafts)" to =
"referenced&nbsp;documents (RFCs and Internet Drafts)" because not all =
RFCs/I-Ds are IETF-stream documents.<br><br>Current:<br><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">1.2.&nbsp;&nbsp;Validation&nbsp;of =
references<br><br></blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">Ensure that references within&nbsp;specifications =
are available and that referenced IETF documents (RFCs and&nbsp;Internet =
Drafts) are latest versions available.&nbsp;&nbsp;Also, match citations =
and references for consistency.&nbsp;&nbsp;In the&nbsp;IETF standards =
stream, specific&nbsp;rules on the suitability and availability of =
references apply, as documented&nbsp;in&nbsp;RFC 2026 and successors, as =
interpreted by the IESG.&nbsp;&nbsp;Editing of documents may be delayed =
waiting for&nbsp;normative&nbsp;references to become =
available.</blockquote><br><br>2)&nbsp;In the following, we suggest that =
"ASN.1 (and particularly MIBs and MIB-related details)" be updated to =
reflect "MIBs".&nbsp;&nbsp;Although MIB modules are written using a =
subset of ASN.1, the RPC does not check all ASN.1, we only check MIBs. =
&nbsp;This change will reflect what is done in practice. &nbsp;If the =
intent is to actually require the RPC to check all ASN.1, please let us =
know and we will&nbsp;discuss checking tools with the RSE and =
IAD.<br><br>Current:<br><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; =
">1.3.&nbsp;&nbsp;Validation&nbsp;of formal =
languages</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><br>The RPC should validate =
the syntax of&nbsp;sections of documents containing formal =
languages.&nbsp;&nbsp;In particular ASN.1&nbsp;(and particularly MIBs =
and MIB-related&nbsp;details), YANG, ABNF, and XML should be verified =
using one or more tools&nbsp;as&nbsp;approved by the =
RSE.&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;</blockquote><br><br>3) Publication =
takes&nbsp;place in the "Electronic Signing &amp; Announcements" box =
within the figure. &nbsp;The following text does not seem to align with =
the figure:<br><br>Current:<br><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">2.&nbsp; &nbsp;&nbsp;&nbsp;Documents forwarded to =
RFC Publisher</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; =
"><br>2.1.&nbsp;&nbsp;The&nbsp;RPC will edit the documents from all =
streams consistent with the RFC Style&nbsp;Manual, the RFC Series, =
and&nbsp;the intent of the Authors.&nbsp;&nbsp;Documents so edited will =
be placed in&nbsp;the ready-to-publish state and forwarded to&nbsp;the =
RFC Publisher.</blockquote><br>In the figure, the publication-related =
actions occur on the RPC side because the RPC is responsible for posting =
RFCs in the public archive, sending out the RFC announcements, updating =
the various indexes, and digitally signing the RFCs. &nbsp;This makes it =
possible for the RPC to respond to requests for legal verification of =
RFCs. &nbsp;Therefore, we suggest the following =
update:&nbsp;<div><br></div><blockquote class=3D"webkit-indent-blockquote"=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><div>2.&nbsp;Documents =
forwarded to RFC Publisher</div><div><br></div><div>2.1.&nbsp;The RPC =
will edit the documents from all streams consistent with the RFC Style =
Manual, the RFC Series,&nbsp;and the intent of the =
Authors.&nbsp;&nbsp;Documents so edited will be published on the RFC =
Editor website.&nbsp;</div></blockquote><div><br>Alternately, Section =
2.1 could be removed, as the documents will not be forwarded to the =
"Publisher" for publication&nbsp;and because how docs will be edited is =
discussed in Section 1.1.1.&nbsp;&nbsp;<br><br><br>For consistency with =
the above update, we suggest that item 2.2 be updated as =
follows:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>2.2. Additionally, the RPC will forward =
records of all interaction and edits relative to the =
document,&nbsp;including dialogue with the document authors and stream =
representatives, to the RFC Publisher for =
archiving.</div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>2.2. The RPC will post all relevant documents, =
including the related RFC files, records of all interaction =
and&nbsp;edits relative to the document, dialogue with the document =
authors and stream representatives, on the RFC&nbsp;Publisher server for =
archiving.</div></blockquote><div><br><br>4)&nbsp;Because the Publisher =
is responsible for the website,&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>&nbsp=
;is a Publisher address (and the address in mentioned in the Publisher =
SoW). We suggest that "<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>" =
be removed from the text =
below.</div><div><br></div><div>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.2.&nbsp;&nbsp;Response&nbsp;to general =
questions directed to&nbsp;<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&nb=
sp;and&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>,&nbs=
p;coordinating as necessary with the RFC Publisher&nbsp;and =
RSE.</div><div><br></div></blockquote><div><br>5) If item 3 (above) is =
accepted and Section 2.1 is updated or removed from the SoW, the Work =
Standards should be updated to&nbsp;refer to "publication" or =
"published" instead of "Forwarded Date" or "forwarded", for =
example:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal 'Times New Roman'; "><font class=3D"Apple-style-span" =
face=3D"Courier">A.2.1.1. A document is =93received=94 by the RPC on the =
date of the receipt of a request to publish by the each of the =
respective streams (Receipt =
Date).</font></div></div></blockquote><div><br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.1.2. A document is&nbsp;=93ready-to-publish=94=
 on the date it is forwarded to the RFC Publisher by the =
RPC&nbsp;(Forwarded Date).&nbsp; =
&nbsp;&nbsp;</div></blockquote><div><br>We suggest:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.1.1. A document is =93received=94 by the =
RPC on the date of the receipt of a request to publish by the each of =
the respective streams (Receipt Date).</div><div><br></div><div>A.2.1.2. =
A document is "published" on the date the RFC is made available on the =
RFC Editor website and the RFC announcement is sent (Publication =
Date).</div></blockquote><div><br>Note that the contractual definition =
of the "Publication Date" is not new; it is currently defined in&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24=
-11_000.pdf">http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012=
-5-24-11_000.pdf</a>&nbsp;as&nbsp;</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div dir=3D"ltr" data-font-name=3D"g_font_p0_19"=
 data-canvas-width=3D"627.8356633680341" style=3D"left: 96.1602px; top: =
667.2px; "><br></div></div><div><div dir=3D"ltr" =
data-font-name=3D"g_font_p0_19" data-canvas-width=3D"627.8356633680341" =
style=3D"left: 96.1602px; top: 667.2px; ">The date of&nbsp;announcement =
is defined as the&nbsp;<span class=3D"highlight selected">date of =
publication</span>.&nbsp;</div></div></blockquote><div><br><br></div><div>=
If "Forwarded Date" is changed to "Publication Date", then these items =
should also be =
updated:</div><div><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.2.1. Processing times per document are =
from Receipt Date to Forwarded Date in total business =
days.</div><div><br></div><div>A.2.2.2. While the overall goal for =
document publication is 30 business days (6 weeks) from Receipt Date to =
Forwarded Date, the times measured in the defined Service Levels are =
times in RPC =
state.</div></blockquote><div><br></div><div><br></div><div>6) &nbsp;We =
suggest removing the first sentence of A.2.2.4 because it is redundant =
with earlier text and is not as clear as A.2.2.2, which can be =
summarized as:&nbsp;</div><div><br></div><div>- Overall goal: time in =
all states (RFC-Editor-controlled states + 3rd party states) &lt; 6 =
weeks</div><div>- Actually measured for SLA: time in =
RFC-Editor-controlled states<br></div><div><br></div><div>Note that we =
also recommend changing "RPC state" to "RFC-Editor-controlled states" =
throughout for clarity. &nbsp;Alternately, we suggest that "RPC State" =
be defined as special =
term.&nbsp;<br><br><br>Publisher</div><div>---------<br><br>7)&nbsp;In =
our understanding of the figure, the Publisher function provides access =
to the post-publication data, but the RPC would actually make any =
changes to post-publication data. &nbsp;So, it seems inaccurate to =
include the Publisher is 'responsible for [...] post-publication data'. =
&nbsp;Therefore, we suggest the following =
update:</div><div><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The RFC Publisher function&nbsp;is described =
in RFC 6635 and is responsible for the storage =
and&nbsp;post-publication&nbsp;data for RFCs, access to the website, =
access to&nbsp;the errata reports, search tools and indexes, the archive =
of&nbsp;documents, and all&nbsp;backups and failover =
processes.</div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The RFC Publisher function is described in RFC =
6635 and is responsible for the storage of and access to =
the&nbsp;website, errata reports, search tools and indexes, the archive =
of documents, and all backups and =
failover&nbsp;processes.</div></blockquote><div><br><br>8) As mentioned =
in item 3 above, we believe that the action of publishing documents, and =
therefore the publication&nbsp;processes, are the responsibility of the =
RPC. &nbsp;With that in mind, we suggest the following update to the =
Overview:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div>The Publisher will accept, store and =
publish documents from the RFC Production Center =
and</div></div><div><div>other material as determined by the RSE. =
&nbsp;The RSE may authorize other entities to =
submit</div></div><div><div>documents directly for publication, but =
those documents are published on the authority of =
the</div></div><div><div>RSE. &nbsp;Changes to the publication process =
and public-facing tools will be made under the =
advice</div></div><div><div>and approval of the =
RSE.</div></div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The Publisher will accept and store documents =
from the RFC Production Center and other material as determined&nbsp;by =
the RSE.&nbsp;&nbsp;</div></blockquote><div><br>We suggest that the =
remainder of the text be removed. &nbsp;While the Publisher houses the =
tools used by the various RFC Editor&nbsp;components, it is the various =
components that have the staff to suggest and implement changes to the =
publication&nbsp;process and tools.<br><br>Also, it is not clear to us =
what is meant by "other entities to submit documents directly for =
publication". &nbsp;Does&nbsp;this refer to web content or perhaps I-Ds =
that are to be published without being edited? &nbsp;Both of these cases =
seem to&nbsp;fall into the RPC SoW, as the RPC is responsible for =
content on the website, and even if an I-D is to be =
published&nbsp;without changes, it would need to be updated to conform =
with current format and boilerplate standards. &nbsp;Are =
there&nbsp;other cases in which this "directly for publication" may =
apply?<br><br><br>9)&nbsp;To make it clear that the RPC updates various =
data, and the Publisher simply makes it available on a server, we =
suggest changing these instances of "publish" and "post" to "make =
available" as follows:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>RFCs are published on the Publisher=92s =
website. This site&nbsp;includes one or more indexes with hyperlinked =
access&nbsp;to published documents as&nbsp;well as a convenient search =
engine.</div></blockquote><div><br></div><div>Suggested:<br></div><blockqu=
ote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>RFCs are made available on the Publisher=92s =
website. This site includes one or more indexes with =
hyperlinked&nbsp;access to published documents as well as a convenient =
search engine.</div></blockquote><div><br>(Note: SM also suggested =
making "Publisher's website" be "RFC Editor =
website")<br><br><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.5. &nbsp; &nbsp; post Web content as =
provided by the RSE, ISE, and/or the RFC Production =
Center,</div></blockquote><div><br>We suggest deleting Section 1.2.5 =
from the Publisher SoW or updating it to read:<br>&nbsp; &nbsp; =
&nbsp;&nbsp;1.2.5. &nbsp; &nbsp; make available Web content as provided =
by the RSE, ISE, and/or the RFC Production =
Center,<br><br></div><div><br></div><div><div>Current:&nbsp;<br></div><blo=
ckquote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.1. &nbsp;Publish state information for =
each document in the&nbsp;publication =
process.</div></blockquote><div><br>Suggested:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.1. &nbsp;State information for each =
document in the publication =
process.</div></blockquote></div><div><br></div><div><br>10)&nbsp;With =
the understanding that the RPC is responsible for creating and =
maintaining the web content (which presumably includes organizing the =
web content), and the Publisher for serving the content, we suggest this =
item be altered as follows. (Also: second sentence deleted because =
already covered in 1.2.6.)<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.7.&nbsp; &nbsp;&nbsp;&nbsp;provide =
continual&nbsp;incremental improvements, including regularly redesigning =
web page trees to&nbsp;respond&nbsp;to common usage =
patterns.&nbsp;&nbsp;However, stable identifiers must be maintained for =
the RFCs, archives,&nbsp;Errata,&nbsp;indices and other =
items.</div></blockquote><div><br></div><div>Suggested:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.7. &nbsp;provide data about the website =
usage patterns so that the maintainers of the web content can organize =
it accordingly.</div></blockquote><div><br><br>11) We believe the =
following item should be updated because an address should be provided =
to reach the Publisher (and&nbsp;this same address is used numerous =
times in Appendix 1 for items for which the Publisher is responsible) =
and because&nbsp;the RPC should not be a middleman in cases of server =
failure, etc.&nbsp;<br><br>Current:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.4. Customer Support Services.&nbsp;Messages =
sent to certain conventional addresses as defined by the RSE, such =
as&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>,&nbs=
p;shall automatically be delivered to the RFC Production =
Center</div></blockquote><div><br>Suggested:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.4. Customer Support Services. Messages sent =
to certain conventional addresses as defined by the RSE, such as&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>, =
shall be coordinated with the RPC as =
appropriate.</div></blockquote><div><br><br>12) We question whether =
integration is really a publisher task. &nbsp;The RPC has a programmer, =
so it seems the RPC would&nbsp;be responsible for the programming =
aspects and the Publisher would be responsible for ensuring the right =
access/security for =
integration.&nbsp;<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.2.&nbsp; &nbsp; &nbsp;Integrate Production =
Center state information with the&nbsp;IETF tools&nbsp;or such other =
tool sets as directed&nbsp;by the RSE&nbsp;to provide end-to-end status =
tracking of documents&nbsp;</div></blockquote><div><br>Perhaps Section =
3.1.2 should be deleted, as Section 2.3.2 indicates that the Publisher =
should provide appropriate access =
for&nbsp;integration.<br><br><br></div><div>13) We suggest removing item =
3.1.3, because it seems to be covered by providing state information, as =
described in&nbsp;Section =
3.1.1.<br><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.3.&nbsp; &nbsp;&nbsp;&nbsp;Provide =
external&nbsp;visibility regarding when a document is in an extended =
waiting period, the&nbsp;token-holder and circumstances of the =
wait.</div></blockquote><div><br><br>14) While the Publisher may =
participate in discussions about the technical support systems required =
to address policy&nbsp;changes, we do not believe the Publisher needs to =
be involved in discussion regarding all publication policy =
changes.&nbsp;&nbsp;Therefore, we suggest the following =
update:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.1.&nbsp;&nbsp;Participate in&nbsp;the =
discussions of the technical publication process with the RSE for =
policy&nbsp;changes.</div></blockquote><div><br>Suggested:<br></div><block=
quote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.1. &nbsp;Participate in policy discussions =
about technical support of the publication =
process.&nbsp;</div></blockquote><div><br><br></div><div>15) It is not =
clear to us that the Publisher enforces RFC Series consistency, as the =
Publisher is responsible for making the&nbsp;files available and =
maintaining the =
archives.<br><br></div><div>Current:&nbsp;</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>7. =
&nbsp;Accountability</div><div><br></div><div>The Publisher is primarily =
responsible to the RSE as&nbsp;regards to RFC Series =
consistency.</div></blockquote><div><br>Perhaps this should be updated =
as:<br></div><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><div>7. =
&nbsp;Accountability</div><div><br></div><div>The Publisher is primarily =
responsible to the RSE regarding technical support and hosting of the =
RFC&nbsp;Series.&nbsp;</div></blockquote><div><br><br>15) The Work =
Standards are listed in "Exhibit B", but there is no "Exhibit A" - is =
some text missing, or should&nbsp;Exhibit B be Exhibit =
A?<br><br></div></div></div></div><br><div><div>On Aug 16, 2013, at =
11:47 AM, Ray Pelletier wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>All;<br><br>Are there any more comments on the =
SOWs?<br><br>This item will be on the IAOC agenda for its call on 22 =
August.<br><br>Ray<br><br>On Aug 12, 2013, at 5:54 PM, IETF =
Administrative Director wrote:<br><br><blockquote type=3D"cite">The RFC =
Series Editor (RSE) is proposing changes to the Statements of Work (SOW) =
for the RFC <br></blockquote><blockquote type=3D"cite">Production Center =
(RPC) and the RFC Publisher. &nbsp;The IAOC wants to receive community =
input prior to <br></blockquote><blockquote type=3D"cite">negotiating =
the proposed changes with the contractor. &nbsp;Community input will be =
discussed with the RSE <br></blockquote><blockquote type=3D"cite">prior =
to negotiations and reviewed by the IAOC.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In forwarding =
the proposed Statements of Work the RSE said: &nbsp;"The changes seek to =
make the SoWs <br></blockquote><blockquote type=3D"cite">more current =
[implementing RFC 6635] and specific, correcting the issues of "multiple =
masters" <br></blockquote><blockquote type=3D"cite">directing the RPC =
and Publisher, as well as preparing the way for a more significant =
revision to the SoWs<br></blockquote><blockquote type=3D"cite">when the =
RFC Format changes are operationalized. &nbsp;The SoWs have also been =
reviewed and supported <br></blockquote><blockquote type=3D"cite">by the =
RSOC [RFC Series Oversight Committee]. &nbsp;We consider the changes =
within the SoWs critical to the <br></blockquote><blockquote =
type=3D"cite">clear function of the RPC and Publisher, but suggest that =
the changes do not imply a significant change =
<br></blockquote><blockquote type=3D"cite">in responsibility for the RPC =
or Publisher."<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The proposed =
SOWs, the current SOWs and a diff file for each can be found here under =
Community <br></blockquote><blockquote type=3D"cite">Review: &lt;<a =
href=3D"http://iaoc.ietf.org/rfps.html">http://iaoc.ietf.org/rfps.html</a>=
&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">We appreciate =
the community's input and look forward to hearing from you. =
&nbsp;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Thanks<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Ray =
Pelletier<br></blockquote><blockquote =
type=3D"cite">IAD<br></blockquote><br></div></blockquote></div><br></body>=
</html>=

--Apple-Mail-808--1054962467--

From stephen.farrell@cs.tcd.ie  Fri Aug 16 13:30:11 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B9F21F9C91; Fri, 16 Aug 2013 13:30:02 -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 JYXt7hGY5AOi; Fri, 16 Aug 2013 13:29:57 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1372C11E822A; Fri, 16 Aug 2013 13:29:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B275ABE58; Fri, 16 Aug 2013 21:29:54 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zvpx0YpaqBtM; Fri, 16 Aug 2013 21:29:53 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.31.41]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C78B1BE53; Fri, 16 Aug 2013 21:29:52 +0100 (IST)
Message-ID: <520E8BBB.9050507@cs.tcd.ie>
Date: Fri, 16 Aug 2013 21:29:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sandy Ginoza <sginoza@amsl.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
In-Reply-To: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, Ray Pelletier <rpelletier@isoc.org>, rfc-interest@rfc-editor.org, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 20:30:11 -0000

Hi Sandy,

I'm not sure how or if it plays into the SoW but your diagram
shows errata handling in the publisher part.

Many people find the current errata process not that great, but
we've collectively not gotten around to figuring out something
better.

I think the possible consequence is that it might be good to
have some flexibility in terms of how errata are processed in
future, e.g. if we all do get around to figuring out something
better it might be good for that not to be precluded by this
SOW being overly prescriptive in that respect. (I don't know
that the SOW is prescriptive about this btw, I did read it a
few days ago but didn't consider this aspect and am about to
head out for the evening... and going out wins:-)

As I said, I'm not sure if that might result in some change
here, but be good if the folks thinking about this SOW keep that
in mind.

Ta,
S.

On 08/16/2013 09:16 PM, Sandy Ginoza wrote:
> Greetings,
> 
> Since the publication of RFC 5620, the RFC Editor has been working to implement the RPC and Publisher split.  Based on our attempts to create two separable entities per RFC 5620 and later RFC 6635, our understanding of the motivations for splitting the RPC and Publisher into distinct functions, and our discussions with the RSE, the RSE has created a figure <http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=rfcpublisher&media=rfc-publisher-split-c.jpg> to describe where the split resides in practice.  We believe the figure accurately reflects the most practical split in terms of work allocation and portability.  
> 
> The split described in the figure eliminates the need for the Publisher to have staff with detailed RFC-specific knowledge by placing the majority of staff-related responsibilities with the RPC. Our understanding is that it is important for the SoWs to be aligned with the split described in the figure, so many of our comments below are an attempt to align these documents.  We provide our comments below for consideration. 
> 
> Thank you,
> Sandy Ginoza 
> (for the RPC and Publisher)
> 
> 
> Notes: 
> ------
> 
> "Current" refers to text as provided in the Proposed SoWs: 
>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf
>   http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf
> 
> "Figure" refers to the figure available at 
>   http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=rfcpublisher&media=rfc-publisher-split-c.jpg
> 
> 
> RFC Production Center
> ---------------------
> 
> 1) In the following, we suggest changing "reference IETF documents (RFCs and Internet Drafts)" to "referenced documents (RFCs and Internet Drafts)" because not all RFCs/I-Ds are IETF-stream documents.
> 
> Current:
> 1.2.  Validation of references
> 
> Ensure that references within specifications are available and that referenced IETF documents (RFCs and Internet Drafts) are latest versions available.  Also, match citations and references for consistency.  In the IETF standards stream, specific rules on the suitability and availability of references apply, as documented in RFC 2026 and successors, as interpreted by the IESG.  Editing of documents may be delayed waiting for normative references to become available.
> 
> 
> 2) In the following, we suggest that "ASN.1 (and particularly MIBs and MIB-related details)" be updated to reflect "MIBs".  Although MIB modules are written using a subset of ASN.1, the RPC does not check all ASN.1, we only check MIBs.  This change will reflect what is done in practice.  If the intent is to actually require the RPC to check all ASN.1, please let us know and we will discuss checking tools with the RSE and IAD.
> 
> Current:
> 1.3.  Validation of formal languages
> 
> The RPC should validate the syntax of sections of documents containing formal languages.  In particular ASN.1 (and particularly MIBs and MIB-related details), YANG, ABNF, and XML should be verified using one or more tools as approved by the RSE.      
> 
> 
> 3) Publication takes place in the "Electronic Signing & Announcements" box within the figure.  The following text does not seem to align with the figure:
> 
> Current:
> 2.     Documents forwarded to RFC Publisher
> 
> 2.1.  The RPC will edit the documents from all streams consistent with the RFC Style Manual, the RFC Series, and the intent of the Authors.  Documents so edited will be placed in the ready-to-publish state and forwarded to the RFC Publisher.
> 
> In the figure, the publication-related actions occur on the RPC side because the RPC is responsible for posting RFCs in the public archive, sending out the RFC announcements, updating the various indexes, and digitally signing the RFCs.  This makes it possible for the RPC to respond to requests for legal verification of RFCs.  Therefore, we suggest the following update: 
> 
> 2. Documents forwarded to RFC Publisher
> 
> 2.1. The RPC will edit the documents from all streams consistent with the RFC Style Manual, the RFC Series, and the intent of the Authors.  Documents so edited will be published on the RFC Editor website. 
> 
> Alternately, Section 2.1 could be removed, as the documents will not be forwarded to the "Publisher" for publication and because how docs will be edited is discussed in Section 1.1.1.  
> 
> 
> For consistency with the above update, we suggest that item 2.2 be updated as follows:
> 
> Current:
> 2.2. Additionally, the RPC will forward records of all interaction and edits relative to the document, including dialogue with the document authors and stream representatives, to the RFC Publisher for archiving.
> 
> Suggested:
> 2.2. The RPC will post all relevant documents, including the related RFC files, records of all interaction and edits relative to the document, dialogue with the document authors and stream representatives, on the RFC Publisher server for archiving.
> 
> 
> 4) Because the Publisher is responsible for the website, webmaster@rfc-editor.org is a Publisher address (and the address in mentioned in the Publisher SoW). We suggest that "webmaster@rfc-editor.org" be removed from the text below.
> 
> Current:
> 6.2.  Response to general questions directed to rfc-editor@rfc-editor.org and webmaster@rfc-editor.org, coordinating as necessary with the RFC Publisher and RSE.
> 
> 
> 5) If item 3 (above) is accepted and Section 2.1 is updated or removed from the SoW, the Work Standards should be updated to refer to "publication" or "published" instead of "Forwarded Date" or "forwarded", for example:
> 
> Current:
> A.2.1.1. A document is “received” by the RPC on the date of the receipt of a request to publish by the each of the respective streams (Receipt Date).
> 
> A.2.1.2. A document is “ready-to-publish” on the date it is forwarded to the RFC Publisher by the RPC (Forwarded Date).    
> 
> We suggest:
> A.2.1.1. A document is “received” by the RPC on the date of the receipt of a request to publish by the each of the respective streams (Receipt Date).
> 
> A.2.1.2. A document is "published" on the date the RFC is made available on the RFC Editor website and the RFC announcement is sent (Publication Date).
> 
> Note that the contractual definition of the "Publication Date" is not new; it is currently defined in http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24-11_000.pdf as 
> 
> The date of announcement is defined as the date of publication. 
> 
> 
> If "Forwarded Date" is changed to "Publication Date", then these items should also be updated:
> 
> Current:
> A.2.2.1. Processing times per document are from Receipt Date to Forwarded Date in total business days.
> 
> A.2.2.2. While the overall goal for document publication is 30 business days (6 weeks) from Receipt Date to Forwarded Date, the times measured in the defined Service Levels are times in RPC state.
> 
> 
> 6)  We suggest removing the first sentence of A.2.2.4 because it is redundant with earlier text and is not as clear as A.2.2.2, which can be summarized as: 
> 
> - Overall goal: time in all states (RFC-Editor-controlled states + 3rd party states) < 6 weeks
> - Actually measured for SLA: time in RFC-Editor-controlled states
> 
> Note that we also recommend changing "RPC state" to "RFC-Editor-controlled states" throughout for clarity.  Alternately, we suggest that "RPC State" be defined as special term. 
> 
> 
> Publisher
> ---------
> 
> 7) In our understanding of the figure, the Publisher function provides access to the post-publication data, but the RPC would actually make any changes to post-publication data.  So, it seems inaccurate to include the Publisher is 'responsible for [...] post-publication data'.  Therefore, we suggest the following update:
> 
> Current:
> The RFC Publisher function is described in RFC 6635 and is responsible for the storage and post-publication data for RFCs, access to the website, access to the errata reports, search tools and indexes, the archive of documents, and all backups and failover processes.
> 
> Suggested:
> The RFC Publisher function is described in RFC 6635 and is responsible for the storage of and access to the website, errata reports, search tools and indexes, the archive of documents, and all backups and failover processes.
> 
> 
> 8) As mentioned in item 3 above, we believe that the action of publishing documents, and therefore the publication processes, are the responsibility of the RPC.  With that in mind, we suggest the following update to the Overview:
> 
> Current:
> The Publisher will accept, store and publish documents from the RFC Production Center and
> other material as determined by the RSE.  The RSE may authorize other entities to submit
> documents directly for publication, but those documents are published on the authority of the
> RSE.  Changes to the publication process and public-facing tools will be made under the advice
> and approval of the RSE.
> 
> Suggested:
> The Publisher will accept and store documents from the RFC Production Center and other material as determined by the RSE.  
> 
> We suggest that the remainder of the text be removed.  While the Publisher houses the tools used by the various RFC Editor components, it is the various components that have the staff to suggest and implement changes to the publication process and tools.
> 
> Also, it is not clear to us what is meant by "other entities to submit documents directly for publication".  Does this refer to web content or perhaps I-Ds that are to be published without being edited?  Both of these cases seem to fall into the RPC SoW, as the RPC is responsible for content on the website, and even if an I-D is to be published without changes, it would need to be updated to conform with current format and boilerplate standards.  Are there other cases in which this "directly for publication" may apply?
> 
> 
> 9) To make it clear that the RPC updates various data, and the Publisher simply makes it available on a server, we suggest changing these instances of "publish" and "post" to "make available" as follows:
> 
> Current:
> RFCs are published on the Publisher’s website. This site includes one or more indexes with hyperlinked access to published documents as well as a convenient search engine.
> 
> Suggested:
> RFCs are made available on the Publisher’s website. This site includes one or more indexes with hyperlinked access to published documents as well as a convenient search engine.
> 
> (Note: SM also suggested making "Publisher's website" be "RFC Editor website")
> 
> 
> Current:
> 1.2.5.     post Web content as provided by the RSE, ISE, and/or the RFC Production Center,
> 
> We suggest deleting Section 1.2.5 from the Publisher SoW or updating it to read:
>       1.2.5.     make available Web content as provided by the RSE, ISE, and/or the RFC Production Center,
> 
> 
> Current: 
> 3.1.1.  Publish state information for each document in the publication process.
> 
> Suggested: 
> 3.1.1.  State information for each document in the publication process.
> 
> 
> 10) With the understanding that the RPC is responsible for creating and maintaining the web content (which presumably includes organizing the web content), and the Publisher for serving the content, we suggest this item be altered as follows. (Also: second sentence deleted because already covered in 1.2.6.)
> 
> Current:
> 1.2.7.     provide continual incremental improvements, including regularly redesigning web page trees to respond to common usage patterns.  However, stable identifiers must be maintained for the RFCs, archives, Errata, indices and other items.
> 
> Suggested:
> 1.2.7.  provide data about the website usage patterns so that the maintainers of the web content can organize it accordingly.
> 
> 
> 11) We believe the following item should be updated because an address should be provided to reach the Publisher (and this same address is used numerous times in Appendix 1 for items for which the Publisher is responsible) and because the RPC should not be a middleman in cases of server failure, etc. 
> 
> Current: 
> 1.4. Customer Support Services. Messages sent to certain conventional addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall automatically be delivered to the RFC Production Center
> 
> Suggested: 
> 1.4. Customer Support Services. Messages sent to certain conventional addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall be coordinated with the RPC as appropriate.
> 
> 
> 12) We question whether integration is really a publisher task.  The RPC has a programmer, so it seems the RPC would be responsible for the programming aspects and the Publisher would be responsible for ensuring the right access/security for integration. 
> 
> Current:
> 3.1.2.     Integrate Production Center state information with the IETF tools or such other tool sets as directed by the RSE to provide end-to-end status tracking of documents 
> 
> Perhaps Section 3.1.2 should be deleted, as Section 2.3.2 indicates that the Publisher should provide appropriate access for integration.
> 
> 
> 13) We suggest removing item 3.1.3, because it seems to be covered by providing state information, as described in Section 3.1.1.
> 
> Current:
> 3.1.3.     Provide external visibility regarding when a document is in an extended waiting period, the token-holder and circumstances of the wait.
> 
> 
> 14) While the Publisher may participate in discussions about the technical support systems required to address policy changes, we do not believe the Publisher needs to be involved in discussion regarding all publication policy changes.  Therefore, we suggest the following update:
> 
> Current:
> 6.1.  Participate in the discussions of the technical publication process with the RSE for policy changes.
> 
> Suggested:
> 6.1.  Participate in policy discussions about technical support of the publication process. 
> 
> 
> 15) It is not clear to us that the Publisher enforces RFC Series consistency, as the Publisher is responsible for making the files available and maintaining the archives.
> 
> Current: 
> 7.  Accountability
> 
> The Publisher is primarily responsible to the RSE as regards to RFC Series consistency.
> 
> Perhaps this should be updated as:
> 7.  Accountability
> 
> The Publisher is primarily responsible to the RSE regarding technical support and hosting of the RFC Series. 
> 
> 
> 15) The Work Standards are listed in "Exhibit B", but there is no "Exhibit A" - is some text missing, or should Exhibit B be Exhibit A?
> 
> 
> On Aug 16, 2013, at 11:47 AM, Ray Pelletier wrote:
> 
>> All;
>>
>> Are there any more comments on the SOWs?
>>
>> This item will be on the IAOC agenda for its call on 22 August.
>>
>> Ray
>>
>> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
>>
>>> The RFC Series Editor (RSE) is proposing changes to the Statements of Work (SOW) for the RFC 
>>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive community input prior to 
>>> negotiating the proposed changes with the contractor.  Community input will be discussed with the RSE 
>>> prior to negotiations and reviewed by the IAOC.
>>>
>>> In forwarding the proposed Statements of Work the RSE said:  "The changes seek to make the SoWs 
>>> more current [implementing RFC 6635] and specific, correcting the issues of "multiple masters" 
>>> directing the RPC and Publisher, as well as preparing the way for a more significant revision to the SoWs
>>> when the RFC Format changes are operationalized.  The SoWs have also been reviewed and supported 
>>> by the RSOC [RFC Series Oversight Committee].  We consider the changes within the SoWs critical to the 
>>> clear function of the RPC and Publisher, but suggest that the changes do not imply a significant change 
>>> in responsibility for the RPC or Publisher."
>>>
>>> The proposed SOWs, the current SOWs and a diff file for each can be found here under Community 
>>> Review: <http://iaoc.ietf.org/rfps.html>
>>>
>>> We appreciate the community's input and look forward to hearing from you.  
>>>
>>> Thanks
>>>
>>> Ray Pelletier
>>> IAD
>>
> 
> 

From adrian@olddog.co.uk  Fri Aug 16 14:47:41 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0011E8194; Fri, 16 Aug 2013 14:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level: 
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4jW3ph-d2P3y; Fri, 16 Aug 2013 14:47:36 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 403A811E818F; Fri, 16 Aug 2013 14:47:34 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7GLlXk8008036;  Fri, 16 Aug 2013 22:47:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7GLlSdR007999 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 22:47:30 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ray Pelletier'" <rpelletier@isoc.org>, <ietf@ietf.org>
Subject: RE: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Date: Fri, 16 Aug 2013 22:47:25 +0100
Message-ID: <02df01ce9aca$35452bc0$9fcf8340$@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: Ac6ayYuJxnYNgDfoSgmm0qJczoXasw==
Content-Language: en-gb
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iaoc@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 21:47:41 -0000

Hi Ray,

Thanks for the reminder.

Meta-nit
The document seems unsure whether to say "Internet Draft" or "Internet-Draft".

---

Nits:
Para 2 
> The RPC is one of the distinct components of the RFC Editor. The primary
> responsibility for the RPC is to edit approved Internet Drafts to a consistent
> high level of quality as described by the RFC Style Manual.

1. I don't believe the RPC edits Internet Drafts. The purpose, it seems to me,
is to edit the text of Internet Drafts to create RFCs.
It would be correct to say "edits RFCs", but I can see people's toes curling. 
So say "exit the text of approved Internet Drafts".

2. s/consistent/consistently/

---

Nit:
1.1.1
What is "formal grammar" and how does it differ from "grammar"?

---

1.1.1

> Editing
> shall be accomplished in accordance with the current 'RFC Style Manual'
> maintained by the RSE . The Style Manual specification now in use will be
> used by the RPC until replaced.

I can see what is being attempted here, but it hasn't achieved it!
I think you want

The RSE maintains the 'RFC Style Manual'. The RPC shall edit in accordance with
the version of the RFC Style Manual current at the time of editing.

---

1.1.2

> Maintain a tracking system for edits, and ensure that changes are signed
> off by all authors and that any technical changes are approved by an
> authorized stream representative, except when exceptions are requested by
> the relevant stream and approved by the RSE.

"except where exceptions" is clumsy, but there is a bigger problem in that there
is an implication in the way that this is written that technical changes can be
made without sign-off by a representative of the stream if somehow requested by
the stream. I think that what was being attempted was the ability to handle
absent authors (e.g. during AUTH-48).  I suggest...

Maintain a tracking system for edits, and ensure that changes are signed-off by
all authors except when the need for sign-off is waived by an authorized
representative of the relevant stream and approved by the RSE. Also ensure that
that any technical changes are approved by an authorized representative of the
relevant stream.

---

1.2
What is the "IETF standards stream"?
Text should maybe read:
For standards track documents in the IETF stream

---

Nits
1.3
> The RPC should validate the syntax of sections of documents containing formal
> languages. In particular ASN.1 (and particularly MIBs and MIB-related
details),

s/languages/language/
s/particular/particular,/
s/MIBs/MIB modules/

---

1.5
While it is much tidier, the text "the relevant individuals" provides no clear
guidance to the RPC. How is the RPC supposed to know who constitutes a relevant
individual in order to allow or disallow their requested change?

---

1.10
I can see why "At the discretion of the RSE" would apply to 1.10.2.
It seems a bit harsh to apply it to 1.10.1. Can the RSE really tell the RPC to
not participate in these discussions?

---

Isn't 6.1.1 now in the Style Guide and covered by 9.3?

---

Nit
9.1 appears to have too many "when requested"

---

9.2
"when requested" and "regular" seem to be in conflict.

---

9.3.1

Do you mean "RFC Publisher web site" or "RFC Editor website"
cf. section 5 and 10.3

---

Nit
"authors" appears in 10.4.1.2 and 10.4.1.3

---

10.5.1
"continuously" or "continually"?

---

10.6
IANAL
This text appears to say that the RPC must take direction from the IAOC if it
receives a subpoena.
I am surprised that this can be placed in a SOW that will form the basis of a
contract.

---

Cheers,
Adrian



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Ray
> Pelletier
> Sent: 16 August 2013 19:48
> To: ietf@ietf.org
> Cc: wgchairs@ietf.org; iaoc@ietf.org; rfc-interest@rfc-editor.org;
iab@iab.org;
> iesg@ietf.org; IETF Announcement List
> Subject: Re: Community Input Sought on SOWs for RFC Production Center and
> RFC Publisher
> 
> All;
> 
> Are there any more comments on the SOWs?
> 
> This item will be on the IAOC agenda for its call on 22 August.
> 
> Ray
> 
> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
> 
> > The RFC Series Editor (RSE) is proposing changes to the Statements of Work
> (SOW) for the RFC
> > Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive
> community input prior to
> > negotiating the proposed changes with the contractor.  Community input will
> be discussed with the RSE
> > prior to negotiations and reviewed by the IAOC.
> >
> > In forwarding the proposed Statements of Work the RSE said:  "The changes
> seek to make the SoWs
> > more current [implementing RFC 6635] and specific, correcting the issues of
> "multiple masters"
> > directing the RPC and Publisher, as well as preparing the way for a more
> significant revision to the SoWs
> > when the RFC Format changes are operationalized.  The SoWs have also been
> reviewed and supported
> > by the RSOC [RFC Series Oversight Committee].  We consider the changes
> within the SoWs critical to the
> > clear function of the RPC and Publisher, but suggest that the changes do not
> imply a significant change
> > in responsibility for the RPC or Publisher."
> >
> > The proposed SOWs, the current SOWs and a diff file for each can be found
> here under Community
> > Review: <http://iaoc.ietf.org/rfps.html>
> >
> > We appreciate the community's input and look forward to hearing from you.
> >
> > Thanks
> >
> > Ray Pelletier
> > IAD


From ietfdbh@comcast.net  Fri Aug 16 15:33:48 2013
Return-Path: <ietfdbh@comcast.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1AC11E81AC for <wgchairs@ietfa.amsl.com>; Fri, 16 Aug 2013 15:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zESol-0k1zAp for <wgchairs@ietfa.amsl.com>; Fri, 16 Aug 2013 15:33:48 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 226CF11E81B2 for <wgchairs@ietf.org>; Fri, 16 Aug 2013 15:33:41 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta07.westchester.pa.mail.comcast.net with comcast id DZlb1m00317dt5G57aZhkC; Fri, 16 Aug 2013 22:33:41 +0000
Received: from [10.59.1.23] ([67.189.237.137]) by omta13.westchester.pa.mail.comcast.net with comcast id DaZa1m0012yZEBF3ZaZaUB; Fri, 16 Aug 2013 22:33:41 +0000
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Fri, 16 Aug 2013 18:33:32 -0400
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: David Harrington <ietfdbh@comcast.net>
To: <ietf@ietf.org>, Ray Pelletier <rpelletier@isoc.org>
Message-ID: <CE341C01.2FDEA%ietfdbh@comcast.net>
Thread-Topic: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
In-Reply-To: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1376692421; bh=toBYXwCb7Q4JnT3QiY0eN8ItNvgh6emjwXp6aFkrmn8=; h=Received:Received:Date:Subject:From:To:Message-ID:Mime-version: Content-type; b=tt9rlyZfSLyZqZr2tnkmpw8J52OYyyD7KYaZH53qgK8faphfu8QfQukeX0BFc9xaM xNjQIfslpGCofFlVNnwdfxojxz5V4/mlFOc04+29xyGXwmYyxZB/fLR1jOYYcqGQkb wCsIQe0+VrggAhLLbfwI8JvhBQzjGclQsXNCc1jEWiVmHCF6feYP5j5mWmO2q4AyBo Yzjk89vNWM//4Rrdjdup+QnbROFXJb+lcAy451oqyo8yl7AZysIRKarH/ZHkibOikJ iZIK1xdyeZiyTQUOyJtwH1xHW/E7JjIkDvCHXEdMm7/btEjk68qsz7BmICXYbcaj4v nw12oWLF0ZeEA==
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>, iaoc@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 22:33:48 -0000

Hi,

A few nits regrading MIB module checking...



On 8/16/13 4:16 PM, "Sandy Ginoza" <sginoza@amsl.com> wrote:
>
>
>
>2) In the following, we suggest that "ASN.1 (and particularly MIBs and
>MIB-related details)" be updated to reflect "MIBs".  Although MIB modules
>are written using a subset of ASN.1, the RPC does not check all ASN.1, we
>only check MIBs.  This change will reflect what is done in practice.  If
>the intent is to actually require the RPC to check all ASN.1, please let
>us know and we will discuss checking tools with the RSE and IAD.
>
>Current:
>
>1.3.  Validation of formal languages
>
>The RPC should validate the syntax of sections of documents containing
>formal languages.  In particular ASN.1 (and particularly MIBs and
>MIB-related details), YANG, ABNF, and XML should be verified using one or
>more tools as approved by the RSE.
>
S/MIBs/MIB modules/

MIB Modules are written using version 2 of the SMI standard, a formal
language which is an IETF-standardized "adapted subset" of ASN.1-1988.
So MIB validation might be more accurately called SMI validation or SMIv2
validation (but SMIv3 could be done at some future date.)
So s/ASN.1/SMI/ or s/ASN.1/SMIv2/

ASN.1 has moved on since the 1988 subset used for SMI.

There are tools to validate against the more current ASN.1 standard.
I'm not sure how much current ASN.1 is used in IETF documents, but if it
is, then you might want to validate it.
I think there is very little current ASN.1 usage in IETF documents.

--
David Harrington
Ietfdbh@comcast.net
+1-603-828-1401



From lear@cisco.com  Sat Aug 17 09:27:32 2013
Return-Path: <lear@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BB611E8168; Sat, 17 Aug 2013 09:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.939
X-Spam-Level: 
X-Spam-Status: No, score=-109.939 tagged_above=-999 required=5 tests=[AWL=0.659, 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 yoqbyYeN5-Xz; Sat, 17 Aug 2013 09:27:27 -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 DDEAD11E8170; Sat, 17 Aug 2013 09:27:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1982; q=dns/txt; s=iport; t=1376756847; x=1377966447; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=mjaNhN1XRSPSrRf299lmgE/HRN/tBfcfQPj3jFWnBto=; b=KUeSR2Q/WCbUDhZkOsEU34pPsy/AcupBitUmuqLwggfBu1IIbv0B8t2A Lh6vo7IpQ8ze+FgM4slpNGvwuhPtTlfzCclb/K0RhIAszSnE38zuw5wy+ L+Lyo9AdbnbEm2R38Y2pZ7lZ5+rZ/w9SBH0iItX1gTfnIifdXWRu5A4X7 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAC+jD1KtJV2a/2dsb2JhbABbgkJEhCCFXbY2gSEWdIIkAQEBAwEjVQEFCwsEAQkTFgsCAgkDAgECAUUGDQEHAQEQh3YGpwaQf5BgB4JogSoDl2SRVYFhgVcg
X-IronPort-AV: E=Sophos;i="4.89,901,1367971200";  d="scan'208,217";a="248307020"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 17 Aug 2013 16:27:20 +0000
Received: from rtp-vpn4-28.cisco.com (rtp-vpn4-28.cisco.com [10.82.208.28]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7HGRCdZ027479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 16:27:19 GMT
Message-ID: <520FA460.2060504@cisco.com>
Date: Sat, 17 Aug 2013 12:27:12 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [IAB] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
In-Reply-To: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------040705010106070101080504"
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 16:27:32 -0000

This is a multi-part message in MIME format.
--------------040705010106070101080504
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Ray,

I have one question regarding 3:

> 3.Accountability
> The RPC is responsible to the RSE as regards to RFC Series consistency.


This is the entirety of a section called "accountability".  Can this be
clarified?  What about other than RFC Series consistency?  What is
example of how this statement might be relevant or operative?

Thanks,

Eliot

--------------040705010106070101080504
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 Ray,<br>
    <br>
    I have one question regarding 3:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr" style="font-size: 16px; font-family: sans-serif;
        left: 144.16px; top: 554.88px; transform: scale(0.964316, 1);
        transform-origin: 0% 0% 0px;" data-font-name="g_font_p0_1"
        data-canvas-width="95.08160000000001">3.Accountability</div>
      <div dir="ltr" style="font-size: 16px; font-family: sans-serif;
        left: 500.16px; top: 573.44px; transform: scale(0.896831, 1);
        transform-origin: 0% 0% 0px;" data-font-name="g_font_p0_1"
        data-canvas-width="120.84800000000001">The RPC is responsible to
        the RSE as regards to RFC Series consistency. </div>
    </blockquote>
    <br>
    <br>
    This is the entirety of a section called "accountability".Â  Can this
    be clarified?Â  What about other than RFC Series consistency?Â  What
    is example of how this statement might be relevant or operative?<br>
    <br>
    Thanks,<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------040705010106070101080504--

From housley@vigilsec.com  Sat Aug 17 11:22:29 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5049221F9B01; Sat, 17 Aug 2013 11:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJ9h2mwNqJWv; Sat, 17 Aug 2013 11:22:21 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id DFAD921F9D21; Sat, 17 Aug 2013 11:22:20 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D62ECF24038; Sat, 17 Aug 2013 14:22:26 -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 KfinaKwKYM+b; Sat, 17 Aug 2013 14:22:17 -0400 (EDT)
Received: from [192.168.0.8] (75-139-113-21.dhcp.mant.nc.charter.com [75.139.113.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 06177F24032; Sat, 17 Aug 2013 14:22:19 -0400 (EDT)
Subject: Re: [IAOC] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Date: Sat, 17 Aug 2013 14:22:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
X-Mailer: Apple Mail (2.1085)
Cc: Ray Pelletier <rpelletier@isoc.org>, IETF WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, IETF <ietf@ietf.org>, IAOC <iaoc@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 18:22:30 -0000

In my experience, the RFC Editor relies on authors to compile non-MIB =
ASN.1 modules.

Russ


On Aug 17, 2013, at 8:09 AM, Jeffrey Hutzelman wrote:

> On Fri, 2013-08-16 at 13:16 -0700, Sandy Ginoza wrote:
>=20
>> 2) In the following, we suggest that "ASN.1 (and particularly MIBs =
and
>> MIB-related details)" be updated to reflect "MIBs".  Although MIB
>> modules are written using a subset of ASN.1, the RPC does not check =
all
>> ASN.1, we only check MIBs.  This change will reflect what is done in
>> practice.  If the intent is to actually require the RPC to check all
>> ASN.1, please let us know and we will discuss checking tools with the
>> RSE and IAD.
>>=20
>> Current:
>> 1.3.  Validation of formal languages
>>=20
>> The RPC should validate the syntax of sections of documents =
containing
>> formal languages.  In particular ASN.1 (and particularly MIBs and
>> MIB-related details), YANG, ABNF, and XML should be verified using =
one
>> or more tools as approved by the RSE.     =20
>=20
> I was a participant in and co-chair of a WG (Kerberos) which produced =
a
> lot of documents containing ASN.1 other than in MIBs.  Before
> considering a document ready for publication, we generally required
> verification that its ASN.1 module compiles.  Usually this was done by
> one or more implementors, who already had handy the tools and
> dependencies required to perform such a check.
>=20
> While I have no objection in principle to the RPC doing this check, it
> seems likely that the burden of doing so would be significant and, at
> least for IETF-stream documents, not worthwhile for the relatively =
small
> gains realized.  This sort of check should be done before a document =
is
> ever submitted to the IESG, let alone the RPC.
>=20
> -- Jeff
>=20


From bertietf@bwijnen.net  Sun Aug 18 00:22:55 2013
Return-Path: <bertietf@bwijnen.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E575D11E825F; Sun, 18 Aug 2013 00:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 462FzigkZk0r; Sun, 18 Aug 2013 00:22:48 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 54ED511E8252; Sun, 18 Aug 2013 00:22:47 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1VAxJv-0002gd-11; Sun, 18 Aug 2013 09:22:41 +0200
Received: from kitten.ripe.net ([193.0.1.240] helo=[IPv6:::1]) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1VAxJu-0005B5-Or; Sun, 18 Aug 2013 09:22:38 +0200
Message-ID: <52107646.1040002@bwijnen.net>
Date: Sun, 18 Aug 2013 09:22:46 +0200
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20130818 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd486a40e7d93e7704ffa0aa80312fc652c
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 07:22:55 -0000

The point w.r.t. MIB module checking was that
during editing phase, even a small typo in a
double quote or some such would render the MIB
module invalid/non-compilable (i.e. invalid SYNTAX).

So if RPC does not touch the text at all, then there
is no need for them to check. But if they DO touch
it (even for pagination or some such) I would
recommend doing the check. For MIB modules that
should be pretty easy, simple and not cause much
extra work. Of course the MIB module needs to be
checked (SYNTAX that is) BEFORE it gets submitted
to AD/IESG even.

Bert
On 8/17/13 2:09 PM, Jeffrey Hutzelman wrote:
> While I have no objection in principle to the RPC doing this check, it
> seems likely that the burden of doing so would be significant and, at
> least for IETF-stream documents, not worthwhile for the relatively small
> gains realized.  This sort of check should be done before a document is
> ever submitted to the IESG, let alone the RPC.

From jhutz@cmu.edu  Sat Aug 17 05:10:05 2013
Return-Path: <jhutz@cmu.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35BC811E8108; Sat, 17 Aug 2013 05:10:05 -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 kyb63orb82bf; Sat, 17 Aug 2013 05:09:59 -0700 (PDT)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by ietfa.amsl.com (Postfix) with ESMTP id 4699D11E80F1; Sat, 17 Aug 2013 05:09:59 -0700 (PDT)
Received: from [10.59.1.80] ([209.118.26.194]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id r7HC9pcu028417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 08:09:57 -0400 (EDT)
Message-ID: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: ietf@ietf.org
Date: Sat, 17 Aug 2013 08:09:49 -0400
In-Reply-To: <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.2-0ubuntu0.1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
X-Mailman-Approved-At: Mon, 19 Aug 2013 07:29:28 -0700
Cc: wgchairs@ietf.org, iaoc@ietf.org, Ray Pelletier <rpelletier@isoc.org>, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>, jhutz@cmu.edu
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 12:10:05 -0000

On Fri, 2013-08-16 at 13:16 -0700, Sandy Ginoza wrote:

> 2) In the following, we suggest that "ASN.1 (and particularly MIBs and
> MIB-related details)" be updated to reflect "MIBs".  Although MIB
> modules are written using a subset of ASN.1, the RPC does not check all
> ASN.1, we only check MIBs.  This change will reflect what is done in
> practice.  If the intent is to actually require the RPC to check all
> ASN.1, please let us know and we will discuss checking tools with the
> RSE and IAD.
> 
> Current:
> 1.3.  Validation of formal languages
> 
> The RPC should validate the syntax of sections of documents containing
> formal languages.  In particular ASN.1 (and particularly MIBs and
> MIB-related details), YANG, ABNF, and XML should be verified using one
> or more tools as approved by the RSE.      

I was a participant in and co-chair of a WG (Kerberos) which produced a
lot of documents containing ASN.1 other than in MIBs.  Before
considering a document ready for publication, we generally required
verification that its ASN.1 module compiles.  Usually this was done by
one or more implementors, who already had handy the tools and
dependencies required to perform such a check.

While I have no objection in principle to the RPC doing this check, it
seems likely that the burden of doing so would be significant and, at
least for IETF-stream documents, not worthwhile for the relatively small
gains realized.  This sort of check should be done before a document is
ever submitted to the IESG, let alone the RPC.

-- Jeff


From nico@cryptonector.com  Sat Aug 17 13:21:23 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9348311E8118; Sat, 17 Aug 2013 13:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level: 
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWVU-pwlzAaB; Sat, 17 Aug 2013 13:21:18 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id ACAEF21F8F24; Sat, 17 Aug 2013 13:21:18 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id 99A0A594062; Sat, 17 Aug 2013 13:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=SfHC01VeGpcR2a7dhszw y3a1B1A=; b=aJYor6jdrTNjFuPZtc8wNeQrMhJXHzmsdE0XFcemX9xg8sn6VQ+b RefvzJZ7lrtDO+YdjClrgPITvRIaE3h1NKhr3j+to2lwqOcMOjAtA/Cp6/czu7Bc FWoQ2Pl1dPzJzg//tqpkmtZRc0XXxJUR019eMCcJ2RvjnFqXeLUgcaI=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id E375E594058;  Sat, 17 Aug 2013 13:21:13 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id j17so1844437wiw.5 for <multiple recipients>; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CfjRK02Fhaylr9pd9S72TltO85AbktKPp9TQLZBKdU4=; b=QrLvn+fSZrasQfIzkw6S5GcqS4aItPmWy3MUmI12VjDIGTb7SGjXj7xKMv2UEe1MDE rg0GLSs2jw99C0fJvp8a4GxJ0UWq+oXzN7XFLBnBIBqAJnPLTyMQ/n53Fh2aWKrIPwdc FDw5+/gY9GpnI4DrLYF82zowH0k0hAHGzcmnkkS7b9FnO764yZHYg/KN1YSTd2lAoRiQ O/gm4pGl/2q3+AF80mqU1q11xcRNVhywev4Gua8I0jj6/32wRdAgas6dDIJhGoA3VfAg 8/TmVzILxRnxzBxOU2gEIuIpj5TVse5gQOVVVLn665gI8NbRsA9IRKDJXenTLBiLoNqY x0WA==
MIME-Version: 1.0
X-Received: by 10.180.187.41 with SMTP id fp9mr2643175wic.33.1376770872308; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
Received: by 10.216.31.193 with HTTP; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
In-Reply-To: <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu> <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
Date: Sat, 17 Aug 2013 15:21:12 -0500
Message-ID: <CAK3OfOhkBGEtLWk0GYOkmFhGsYx=ezqznBFUtGe-0T1V52nDvg@mail.gmail.com>
Subject: Re: [rfc-i] [IAOC] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Nico Williams <nico@cryptonector.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Mon, 19 Aug 2013 07:29:36 -0700
Cc: IAOC <iaoc@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, IETF <ietf@ietf.org>, Jeffrey Hutzelman <jhutz@cmu.edu>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 20:21:23 -0000

Several open-source compilers exist.  It would not be hard to a) make
a library of modules from RFCs (to deal with IMPORTS), b) make a
cgi-bin compiler.  It's not what I do on a daily basis, but if you put
together a cgi-bin where all I need to provide is a command to run on
a file and output warnings and errors, well, I can do that trivially.

From barryleiba@gmail.com  Tue Aug 20 18:21:33 2013
Return-Path: <barryleiba@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A18F411E8325 for <wgchairs@ietfa.amsl.com>; Tue, 20 Aug 2013 18:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gf-Rs5sjXroA for <wgchairs@ietfa.amsl.com>; Tue, 20 Aug 2013 18:21:33 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 361DB11E830C for <wgchairs@ietf.org>; Tue, 20 Aug 2013 18:21:33 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id l18so102403qak.11 for <wgchairs@ietf.org>; Tue, 20 Aug 2013 18:21:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=tJNdvP+WfSSROnn+aACqPDil+gOCxQIqnxUZ2hfbRE4=; b=Nx+N+cPNmynCdsf68xjpKJPnIyDePXy2HrOpcJ4leBbtPwyZkCBrJoAVNYTN+Yc0mi g4BJtshlqlUECcf37tEb2k90ODIBBqBNR5+T9OzJBezPk2pFiPSMNGwDGPfp+PX8QtRb Sm9LmxgJzYLMLFrMN1qiqbLf5Ga0Cp88jypl33cMH3BcVOTLNj+a7scQTwQz+IC/b5qr 1zZBbUJGRpP5xrEe44VaABQdtAdd+OEc+8BAUbkJLgrnS4tfg+41Xf+4kLQdYa5ZPZl4 ck7MnBbKNvmQCQld377e8BqDTErvUrBagCgQnsNljVXUH8K5x7gEbDGjrN2LLQ+z4h+3 KlvA==
MIME-Version: 1.0
X-Received: by 10.224.13.141 with SMTP id c13mr7324771qaa.22.1377048092579; Tue, 20 Aug 2013 18:21:32 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.59.211 with HTTP; Tue, 20 Aug 2013 18:21:32 -0700 (PDT)
Date: Tue, 20 Aug 2013 21:21:32 -0400
X-Google-Sender-Auth: 8GXvSKufpft_WYdqCg7_20DFE8s
Message-ID: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com>
Subject: Using the datatracker to request publication of your working group drafts
From: Barry Leiba <barryleiba@computer.org>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 01:21:33 -0000

With recent changes to the datatracker, the current way to request
publication of working group documents has changed: the old email
mechanism has been replaced by the datatracker.  Brian Haberman and I
have written a wiki page describing the process, and I've added it to
the working group chairs wiki (with a link to it on the main wiki
page):

http://wiki.tools.ietf.org/group/wgchairs/wiki/RequestingPublication

Barry

From stephen.farrell@cs.tcd.ie  Wed Aug 21 00:12:45 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21AA511E81C0 for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 00:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8OiterLWkZl for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 00:12:40 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDF511E81BE for <wgchairs@ietf.org>; Wed, 21 Aug 2013 00:12:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E9807BE77; Wed, 21 Aug 2013 08:12:38 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Bk1jRY6AQ9M; Wed, 21 Aug 2013 08:12:37 +0100 (IST)
Received: from [10.10.100.224] (unknown [85.182.157.82]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 97526BE74; Wed, 21 Aug 2013 08:12:36 +0100 (IST)
References: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <05C76005-104D-47A2-AE1C-DC0ACF4F2B7E@cs.tcd.ie>
X-Mailer: iPhone Mail (10B329)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Using the datatracker to request publication of your working group drafts
Date: Wed, 21 Aug 2013 09:12:32 +0200
To: Barry Leiba <barryleiba@computer.org>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 07:12:45 -0000

On 21 Aug 2013, at 03:21, Barry Leiba <barryleiba@computer.org> wrote:

> With recent changes to the datatracker, the current way to request
> publication of working group documents has changed: the old email
> mechanism has been replaced by the datatracker.  Brian Haberman and I
> have written a wiki page describing the process, and I've added it to
> the working group chairs wiki (with a link to it on the main wiki
> page):
>=20
> http://wiki.tools.ietf.org/group/wgchairs/wiki/RequestingPublication
>=20

I'm in Internet-via-phone land so can't do it but be good if that wiki remin=
ded chairs to hit the ID-nits check before changing state.

Ta
S

> Barry

From barryleiba.mailing.lists@gmail.com  Wed Aug 21 07:50:22 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A54A511E81F4 for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 07:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.955
X-Spam-Level: 
X-Spam-Status: No, score=-101.955 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GHRiESXCrAEy for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 07:50:22 -0700 (PDT)
Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFA811E81C9 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 07:50:22 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id w16so367146vbb.8 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 07:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=dnuoj5IEhp3lGFUEMq5P/gNsgPRcoWi9p9MyWgPcVK4=; b=tvT8r6Vex8WGW4wfIX3ufeuCK6rsKZnqNQ2N6yWR8w5PeI1Gp871yOlrXJW9b6LZ// YJSctflpsZzMKWwL/P8M6NoXIAt8fuR2a5faH3RuOkqord5YgOzGDwK7vgcn9DJE06gm +yYRMUGJ81TysOqeLGI5XrKmGw/ol5P7ZudQspAmUsuXTh0VG8KUOkHAQmFpPOn9glkV 0Nr/B45ckLbbaiwUxUNKCSj/7XQZW19kaju7DcDObNbXWaNB3yaeu63hj/nCjQ/BCHx5 xIF901dYad/YQPy4bWKR0wTCDX3rCB0ZTCrYEObAFMd4QHk/ec5Mw+pRIFI+bbLjFtzY LAUw==
MIME-Version: 1.0
X-Received: by 10.221.44.136 with SMTP id ug8mr6823812vcb.13.1377096621736; Wed, 21 Aug 2013 07:50:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Wed, 21 Aug 2013 07:50:21 -0700 (PDT)
In-Reply-To: <05C76005-104D-47A2-AE1C-DC0ACF4F2B7E@cs.tcd.ie>
References: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com> <05C76005-104D-47A2-AE1C-DC0ACF4F2B7E@cs.tcd.ie>
Date: Wed, 21 Aug 2013 10:50:21 -0400
X-Google-Sender-Auth: MH8JfFx1bVoT5e8rqIv32_S3d4A
Message-ID: <CAC4RtVBH9ekpOs6RTpSg-uCrQhXVJrKPVqwotw1ifjC_xLDVXg@mail.gmail.com>
Subject: Re: Using the datatracker to request publication of your working group drafts
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:50:22 -0000

> I'm in Internet-via-phone land so can't do it but be good if that wiki reminded chairs to
> hit the ID-nits check before changing state.

An excellent suggestion; I'll add it on your behalf.

Barry

From stephen.farrell@cs.tcd.ie  Wed Aug 21 08:40:20 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4003611E80FC for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 08:40: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 Y-bo9UA158sS for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 08:40:14 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7889711E8112 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 08:40:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 93273BE74; Wed, 21 Aug 2013 16:40:12 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eh8O3LGymHuX; Wed, 21 Aug 2013 16:40:12 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6DFA3BE61; Wed, 21 Aug 2013 16:40:12 +0100 (IST)
Message-ID: <5214DF5C.6090005@cs.tcd.ie>
Date: Wed, 21 Aug 2013 16:40:12 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Using the datatracker to request publication of your working group drafts
References: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com> <05C76005-104D-47A2-AE1C-DC0ACF4F2B7E@cs.tcd.ie> <CAC4RtVBH9ekpOs6RTpSg-uCrQhXVJrKPVqwotw1ifjC_xLDVXg@mail.gmail.com>
In-Reply-To: <CAC4RtVBH9ekpOs6RTpSg-uCrQhXVJrKPVqwotw1ifjC_xLDVXg@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:40:20 -0000

On 08/21/2013 03:50 PM, Barry Leiba wrote:
>> I'm in Internet-via-phone land so can't do it but be good if that wiki reminded chairs to
>> hit the ID-nits check before changing state.
> 
> An excellent suggestion; I'll add it on your behalf.

Ta,
S.

> 
> Barry
> 
> 

From warren@kumari.net  Wed Aug 21 09:42:23 2013
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F65611E822E for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 09:42:22 -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 HG2gRwoL8kYJ for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 09:42:10 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287C011E8107 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 09:42:09 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 1D8001B40CCC; Wed, 21 Aug 2013 12:42:09 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Using the datatracker to request publication of your working group drafts
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com>
Date: Wed, 21 Aug 2013 12:42:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <17AC8F82-F386-4964-93CA-3977249E30E2@kumari.net>
References: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1508)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 16:42:23 -0000

On Aug 20, 2013, at 9:21 PM, Barry Leiba <barryleiba@computer.org> =
wrote:

> With recent changes to the datatracker, the current way to request
> publication of working group documents has changed: the old email
> mechanism has been replaced by the datatracker.  Brian Haberman and I
> have written a wiki page describing the process, and I've added it to
> the working group chairs wiki (with a link to it on the main wiki
> page):
>=20
> http://wiki.tools.ietf.org/group/wgchairs/wiki/RequestingPublication

And much thanks to Barry for actually putting this in the Wiki instead =
of just slapping it in an email.=20
I have recently tried to train a few new chairs, and the chairs wiki is =
very sparse.

Yes, I know that the "correct" answer here is for me to actually update =
the wiki, but I'm choosing instead to simply kvetch.

W

>=20
> Barry
>=20

--
The plural of anecdote is not evidence.
        -- Bill Lockyer, California Attorney General




From barryleiba.mailing.lists@gmail.com  Wed Aug 21 10:43:56 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C04F311E8253 for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 10:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.958
X-Spam-Level: 
X-Spam-Status: No, score=-101.958 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAacARnrS0vl for <wgchairs@ietfa.amsl.com>; Wed, 21 Aug 2013 10:43:56 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3369B11E8242 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 10:43:56 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pb11so614080veb.25 for <wgchairs@ietf.org>; Wed, 21 Aug 2013 10:43:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9IbkflRc6qIyEAnfF7KlSbwH8XLrhUDSgGJI5hEsjYA=; b=WQy1w1TiHdcsarVyPMbia2CyAK4iCHyo3G7e4RftpOZWRW//mP6eISe/TehZ7ANDii rUqzsceN7yXrIIBVD0+95aAjsUqBrpZEFLVPo+mLPHC1/VQNX2XuXClnXMeFsSKdTBb4 pdCEKFAQ+stkM/6/GAQQ/fu0/EZEeqSAVlMigMzafy9xvR5+Ze4CIotZ0pi7hJE7sljz jXgx6Rysj5eb5wdsXE0dH8OkkEf69+WFB492S+jpquITuccjYT9l0xvPUvcctHHdeVTR /reYDMHaw6FhNjRuNKlCQn3pLygKwzcHNLIm4JJuxrEq4AET6rPMPXobDmn9JNNDpnqA iXLg==
MIME-Version: 1.0
X-Received: by 10.52.164.201 with SMTP id ys9mr866037vdb.39.1377107035570; Wed, 21 Aug 2013 10:43:55 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Wed, 21 Aug 2013 10:43:55 -0700 (PDT)
In-Reply-To: <17AC8F82-F386-4964-93CA-3977249E30E2@kumari.net>
References: <CALaySJKa8DGwKSAUQFzjR02oU_Gq83urXaLAHhkxORT1zgkO3w@mail.gmail.com> <17AC8F82-F386-4964-93CA-3977249E30E2@kumari.net>
Date: Wed, 21 Aug 2013 13:43:55 -0400
X-Google-Sender-Auth: xwi7evZMrqh5LXpASZWtoTPzHrw
Message-ID: <CAC4RtVCkZd5OGGhF7zBB+c48D_mQTu1vz3ivszHCryXGH3ZkVA@mail.gmail.com>
Subject: Re: Using the datatracker to request publication of your working group drafts
From: Barry Leiba <barryleiba@computer.org>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:43:56 -0000

> And much thanks to Barry for actually putting this in the Wiki instead of just
> slapping it in an email.  I have recently tried to train a few new chairs, and the
> chairs wiki is very sparse.

You're welcome.  And, yes, I'd like to see us fatten up the chairs
wiki and make it something that a new chair (or one who comes back
after many procedural changes) can use to figure out what to do and
how to do it.

Barry

From iad@ietf.org  Thu Aug 22 12:05:28 2013
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1CE311E80F8; Thu, 22 Aug 2013 12:05:28 -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 KKBzR2AU8cxr; Thu, 22 Aug 2013 12:05:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0532521F9E5A; Thu, 22 Aug 2013 12:05:28 -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: New IETF Trust Chair
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130822190527.13563.17128.idtracker@ietfa.amsl.com>
Date: Thu, 22 Aug 2013 12:05:27 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:05:29 -0000

The IETF Trust Trustees are pleased to announce that Ole Jacobsen has been =
selected as the IETF Trust =

Chair.  Ole was selected following the resignation of Chris Griffiths as Ch=
air, who assumed the =

chairmanship of the IAOC.   This will be Ole's second stint as Chair as he =
succeeded Marshall Eubanks =

when Marshall resigned from the IAOC.  =


Congratulations Ole!  =


Ray Pelletier
Trustee
IAD
http://trustee.ietf.org/

From mconner@amsl.com  Thu Aug 22 12:42:37 2013
Return-Path: <mconner@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1844021F89FF for <wgchairs@ietfa.amsl.com>; Thu, 22 Aug 2013 12:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZsAo2Y+YncX for <wgchairs@ietfa.amsl.com>; Thu, 22 Aug 2013 12:42:35 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id A2AE811E822A for <wgchairs@ietf.org>; Thu, 22 Aug 2013 12:42:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 6DF90A6209; Thu, 22 Aug 2013 12:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1NMu47-VtUMN; Thu, 22 Aug 2013 12:42:17 -0700 (PDT)
Received: from [64.170.98.144] (unknown [64.170.98.144]) by c9a.amsl.com (Postfix) with ESMTPSA id 4EAFE9FB31; Thu, 22 Aug 2013 12:42:17 -0700 (PDT)
From: Maddy Conner <mconner@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FE41B44B-68C3-4B26-9592-A17C78BAACD2"
Subject: Request for IETF WG and BoF Session Minutes
Date: Thu, 22 Aug 2013 12:43:44 -0700
Message-Id: <A3377244-E0EE-4288-8BF9-9EF7B557D2D7@amsl.com>
To: wgchairs@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Thu, 22 Aug 2013 12:43:42 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:42:37 -0000

--Apple-Mail=_FE41B44B-68C3-4B26-9592-A17C78BAACD2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear WG Chairs and BOF Chairs,
=20
I am in the process of compiling the proceedings for IETF 87 and we are =
still missing meeting minutes from various sessions. The cutoff for =
submissions is Friday, August 30th, 2013, and correction submissions =
cutoff is Wednesday, September 18th, 2013.  Please upload meeting =
minutes, as well as any presentations from your sessions, at your =
earliest convenience using the Meeting Materials Manager found here: =
https://pub.ietf.org/proceedings/.  Alternatively, you are welcome to =
send them to proceedings@ietf.org or mconner@amsl.com for manual =
posting.

Groups I still need minutes from are:

Application Area:
	CORE
	WEBSEC
=20
General Area:
	IPRBIS (BoF)

Internet Area:
	6MAN
	6TSCH (BoF)
	DNSSDEXT (BoF)
	HOMENET
	INTAREA
	MULTIMOB
	NETEXT
	PCP
	TICTOC
	TRILL

Operations & Management Area:
	GROW
	MBONED
	OPSEC
	V6OPS

Real-Time Applications & Infrastructure Area:
	AVTEXT
	INSIPID
	MMUSIC
	SIPREC

Routing Area:
	FORCES
	IDR
	KARP
	MANET
	MPLS
	PCE
	SIDR

Security Area:
	DANE
	SAAG
	TLS

Transport Area:
	CONEX
	TSVAREA

IRTF:
	CFRG (No agenda Received)
	DTNRG
	ICCRG
	NWCRG

https://datatracker.ietf.org/meeting/87/materials.html



Maddy Conner
IETF Registrar
48377 Fremont Blvd, Ste. 117
Fremont, CA 94538

Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com=

--Apple-Mail=_FE41B44B-68C3-4B26-9592-A17C78BAACD2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Dear WG Chairs and BOF Chairs,</div><div>&nbsp;</div><div>I am in =
the process of compiling the proceedings for IETF 87 and we are still =
missing meeting minutes from various sessions. The cutoff for =
submissions is <b>Friday, August 30th, 2013</b>, and correction =
submissions cutoff is <b>Wednesday, September 18th, 2013</b>. =
&nbsp;Please upload meeting minutes, as well as any presentations from =
your sessions, at your earliest convenience using the Meeting Materials =
Manager found here: <a =
href=3D"https://pub.ietf.org/proceedings/">https://pub.ietf.org/proceeding=
s/</a>. &nbsp;Alternatively, you are welcome to send them to <a =
href=3D"mailto:proceedings@ietf.org">proceedings@ietf.org</a> or <a =
href=3D"mailto:mconner@amsl.com">mconner@amsl.com</a> for manual =
posting.</div><div><br></div><div>Groups I still need minutes from =
are:</div><div><br></div><div>Application Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>CORE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>WEBSEC</div><div>&nbsp;</div><div>General Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>IPRBIS =
(BoF)</div><div><br></div><div>Internet Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>6MAN</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>6TSCH (BoF)</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
style=3D"font-family: arial, helvetica, clean, sans-serif; font-size: =
13px; line-height: 16px; ">DNSSDEXT&nbsp;(BoF)</span></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>HOMENET</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>INTAREA</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>MULTIMOB</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>NETEXT</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>PCP</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>TICTOC</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>TRILL</div><div><br></div><div>Operations &amp; Management =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>GROW</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MBONED</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>OPSEC</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>V6OPS</div><div><br></div><div>Real-Time Applications &amp; =
Infrastructure Area:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>AVTEXT</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>INSIPID</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MMUSIC</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>SIPREC</div><div><br></div><div>Routing Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>FORCES</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>IDR</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>KARP</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MANET</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>MPLS</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>PCE</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>SIDR</div><div><br></div><div>Security Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>DANE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>SAAG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>TLS</div><div><br></div><div>Transport Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>CONEX</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>TSVAREA</div><div><br></div><div>IRTF:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>CFRG (No =
agenda Received)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>DTNRG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>ICCRG</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>NWCRG</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/meeting/87/materials.html">https://da=
tatracker.ietf.org/meeting/87/materials.html</a></div><div><br></div><div>=
<br></div><div><br></div><div>Maddy Conner</div><div>IETF =
Registrar</div><div>48377 Fremont Blvd, Ste. 117</div><div>Fremont, CA =
94538</div><div><br></div><div>Association Management Solutions =
(AMS)</div><div>Forum Management, Meeting and Event =
Planning</div><div><a =
href=3D"http://www.amsl.com">www.amsl.com</a></div></body></html>=

--Apple-Mail=_FE41B44B-68C3-4B26-9592-A17C78BAACD2--

From agenda@ietf.org  Thu Aug 22 16:55:22 2013
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D862A11E8284; Thu, 22 Aug 2013 16:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.201
X-Spam-Level: 
X-Spam-Status: No, score=-101.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36j-hks-mzCv; Thu, 22 Aug 2013 16:55:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7592F11E8271; Thu, 22 Aug 2013 16:55:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 88th IETF - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130822235511.22351.9423.idtracker@ietfa.amsl.com>
Date: Thu, 22 Aug 2013 16:55:11 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 23:55:26 -0000

-----------------------------------------------------------------
88th IETF =E2=80=93 Vancouver, BC, Canada
Meeting Dates: November 3 =E2=80=93 8, 2013
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

We are accepting scheduling requests for all Working Groups, BOFs, and Rese=
arch Groups starting today.  The milestones and deadlines for scheduling-re=
lated activities are as follows:

NOTE: cutoff dates are subject to change.

- 2013-08-19 (Week of): Working Group and BOF scheduling begins. To request=
 a Working Group session, use the IETF Meeting Session Request Tool. (updat=
ed from 5 August).
- 2013-09-23 (Monday): Cutoff date for requests to schedule Working Group m=
eetings at UTC 24:00. To request a Working Group session, use the IETF Meet=
ing Session Request Tool.
- 2013-09-23 (Monday): Cutoff date for BOF proposal requests to Area Direct=
ors at UTC 24:00. To request a BOF, please see instructions on Requesting a=
 BOF.
- 2013-09-26 (Thursday): Cutoff date for Area Directors to approve BOFs at =
UTC 24:00.
- 2013-10-03 (Thursday): Preliminary agenda published for comment.
- 2013-10-07 (Monday): Cutoff date for requests to reschedule Working Group=
 and BOF meetings UTC 24:00.
- 2013-10-11 (Friday): Final agenda to be published.
- 2013-10-23 (Wednesday): Draft Working Group agendas due by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-10-28 (Monday): Revised Working Group agendas due by UTC 24:00, uplo=
ad using IETF Meeting Materials Management Tool.
- 2013-12-06 (Friday): Proceedings submission cutoff date by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-12-25 (Wednesday): Proceedings submission corrections cutoff date by=
 UTC 24:00, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the "I=
ETF Meeting Session Request Tool," a Web-based tool for submitting all of t=
he information that the Secretariat requires to schedule your sessions.

The URL for the tool is:

https://pub.ietf.org/sreq/

Please send requests to schedule your BOF sessions to agenda@ietf.org.  Ple=
ase include the acronym of your BOF in the subject line of the message, and=
 include all of the information specified in item (4) of "Requesting Meetin=
g Sessions at IETF Meetings" in the body.  (This document is included below=
.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the agenda=
s for your Working Group sessions as early as possible.  Draft Working Grou=
p agendas are due Wednesday, October 23rd, 2013 at UTC 24:00.  Revised Work=
ing Group agendas are due no later than Monday, October 28, 2013 at UTC 24:=
00.  The proposed agenda for a BOF session should be submitted along with y=
our request for a session.  Please be sure to copy your Area Director on th=
at message.

Please submit the agendas for your Working Group sessions using the "IETF M=
eeting Materials Management Tool," a Web-based tool for making your meeting=
 agenda, minutes, and presentation slides available to the community before=
, during, and after an IETF meeting.  If you are a BOF chair, then you may =
use the tool to submit a revised agenda as well as other materials for your=
 BOF once the BOF has been approved.

The URL for the tool is:

https://pub.ietf.org/proceedings/

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the "IETF=
 Meeting Materials" webpage as soon as they are submitted.

The URL for the "IETF 88 Meeting Materials" Web page is:

https://datatracker.ietf.org/meeting/88/materials.html

If you are a Working Group chair, then you already have accounts on the "IE=
TF Meeting Session Request Tool" and the "IETF Meeting Materials Management=
 Tool."  The same User ID and password will work for both tools.  If you ar=
e a BOF chair who is not also a Working Group chair, then you will be given=
 an account on the "IETF Meeting Materials Management Tool" when your BOF h=
as been approved.  If you require assistance in using either tool, or wish =
to report a bug, then please send a message to:
ietf-action@ietf.org.
=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
For your convenience, comprehensive information on requesting meeting sessi=
ons at IETF 88 is presented below:

1. Requests to schedule Working Group sessions should be submitted using th=
e "IETF Meeting Session Request Tool," a Web-based tool for submitting all =
of the information required by the Secretariat to schedule your sessions.  =
The URL for the tool is:

https://pub.ietf.org/sreq/

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then ple=
ase send a message to ietf-action@ietf.org.  If you are unable to use the t=
ool, then you may send your request via e-mail to agenda@ietf.org, with a c=
opy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a co=
py to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please in=
clude the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director approves the BOF. Th=
e proponents behind a BOF need to contact a relevant Area Director, prefera=
bly well in advance of the BOF approval deadline date. The AD needs to have=
 the full name of the BOF, its acronym, suggested names of chairs, an agend=
a, full description of the BOF and the information covered in item 4. Pleas=
e read RFC 5434 for instructions on how to drive a successful BOF effort. T=
he approval depends on, for instance, Internet-Drafts and list discussion o=
n the suggested topic. BOF agenda requests, if approved, will be submitted =
to the IETF Secretariat by the ADs.

3. A Working Group may request either one or two sessions.  If your Working=
 Group requires more than two sessions, then your request must be approved =
by an Area Director.  Additional sessions will be assigned, based on availa=
bility, after Monday, October 7, 2013, the cut-off date for requests to res=
chedule a session.

4. You MUST provide the following information before a Working Group or BOF=
 session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets: =


    b. AREA under which Working Group or BOF appears:

    c. CONFLICTS you wish to avoid, please be as specific as possible:

    d. Expected Attendance:

    e. Special requests:

    f. Number of sessions:

    g. Length of session: =

       - 1 hour =

       - 1 1/2 hours
       - 2 hours =

       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please r=
efer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (=
http://www.ietf.org/rfc/rfc2418.txt).
=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
For your convenience please find here a list of the IETF Area Directors wit=
h their e-mail addresses:

IETF Chair =

Jari Arkko <jari.arkko@piuha.net>

Applications Area (app)
        Barry Leiba <barryleiba@computer.org>
        Pete Resnick <presnick@qualcomm.com>

Internet Area (int) =

Brian Haberman <brian@innovationslab.net> =

        Ted Lemon <ted.lemon@nominum.com>

Operations & Management Area (ops) =

Benoit Claise <bclaise@cisco.com> =

Joel Jaeggli <joelja@bogus.com>

Real-time Applications and Infrastructure Area (rai)
Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Richard Barnes <rlb@ipv.sx>  =


Routing Area (rtg) =

Stewart Bryant <stbryant@cisco.com>
Adrian Farrel <adrian@olddog.co.uk>  =


Security Area (sec) =

Stephen Farrell <stephen.farrell@cs.tcd.ie>
Sean Turner <turners@ieca.com>  =


Transport Area (tsv) =

Martin Stiemerling <martin.stiemerling@neclab.eu> =

Spencer Dawkins  <spencerdawkins.ietf@gmail.com>
 =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
87th IETF Meeting Attendance Numbers

6lo - 127
6man - 166
6tsch BoF - 101
abfab - 22
alto  - 73
appsawg - 98
aqm BoF - 86
avtcore - 64
avtext - 37
behave - 61
bmwg - 20
ccamp - 53
ccamp (2nd session) - 59
cdni - 73
cdni (2nd session) - 38
cfrg (RG) - 40
clue - 46
clue (2nd session) - 33
conex - 67
core - 107
core (2nd session) - 46
dane - 92
dhc (joint session with sunset4) - 110
dhc (2nd session) - 54
dice BoF - 112
dime - 17
dmarc BoF - 47
dmm - 30
dnsop - 116
dnssdext BoF - 137
dtnrg (RG) - 44
dtnrg (RG) (2nd session) - 44
ecrit - 45
eman - 43
emu - 36
forces - 69
grow - 63
homenet - 128
httpauth - 59
httpbis - 93
httpbis (2nd session) - 72
i2rs - 257
iccrg (RG) - 68
iccrg (RG) (2nd session) - 77
icnrg (RG) - 86
idr - 64
insipid - 35
intarea (AG) - 93
ipfix - 35
ippm - 64
iprbis (BoF) - 26
ipsecme - 48
IRTF Open Meeting - 121
isis - 28
jose - 55
json - 36
karp - 31
kitten - 25
l2vpn - 64
l3vpn - 81
lmap - 76
lwig - 55
manet - 49
mboned - 12
mif - 41
mile - 43
mmusic - 76
mmusic (2nd session) - 85
mpls - 129
mpls (2nd session) - 78
mptcp - 108
multimob - 29
ncrg (RG) - 38
netconf - 52
netext - 40
netmod - 52
nfsv4 - 22
nmrg (RG) - 59
nsc BoF - 281
nvo3 - 182
nwcrg (PRG) - 49
oauth - 62
opsawg - 62
opsec - 52
ospf - 21
p2psip - 20
paws - 22
pce - 82
pcp - 29
pcp (2nd session) - 40
pim - 18
posh BoF - 87
ppsp - 14
precis - 19
pwe3 - 33
radext - 22
rmcat - 91
rtcweb - 127
rtcweb (2nd session) - 132
rtgarea (AG) - 118
rtgwg - 51
saag (AG) - 148
sacm - 45
scim - 26
sdnrg (RG) - 288
sidr - 62
sidr (2nd session) - 58
siprec - 27
softwire - 78
status BoF - 214
stir - 126
stox - 34
sunset4 - 99
sunset4 (joint session with dhc) - 110
tcmtf BoF - 89
tcpm - 68
tictoc - 22
tls - 63
trill - 31
tsvarea (AG) - 112
tsvwg - 59
tsvwg (2nd session) - 50
urnbis - 9
v6ops - 110
v6ops (2nd session) - 118
websec - 68
weirds - 65
xrblock - 26

From ietf-secretariat@ietf.org  Fri Aug 23 06:36:58 2013
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 833DE11E81B3; Fri, 23 Aug 2013 06:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.6
X-Spam-Level: 
X-Spam-Status: No, score=-104.6 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a+mjvAzBPz6V; Fri, 23 Aug 2013 06:36:57 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7478A11E80DC; Fri, 23 Aug 2013 06:36:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 88 - Registration Now Open!
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130823133657.18756.43809.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 06:36:57 -0700
Cc: wgchairs@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 13:36:58 -0000

88th IETF Meeting
Vancouver, BC, Canada
November 3-8, 2013
Host: Huawei

Meeting venue:  Hyatt Regency Vancouver: http://vancouver.hyatt.com/en/hote=
l/home.html

Register online at: http://www.ietf.org/meetings/88/

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  Companion Program


1. Registration
  A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October 2013 UT=
C 24:00
  B. After Early-Bird cutoff - USD 800.00
  C. Full-time Student Registrations - USD 150.00 (with proper ID)
  D. One Day Pass Registration - USD 350.00
  E. Registration Cancellation   =

              Cut-off for registration cancellation is Monday,
              28 October 2013 at UTC 24:00.
              Cancellations are subject to a 10% (ten percent)
              cancellation fee if requested by that date and time.
  F. Online Registration and Payment ends Friday, 1 November 2013, 1700 loc=
al Vancouver time.
  G. On-site Registration starting Sunday, 3 November 2013 at 1100 local Va=
ncouver time.

2. Visas & Letters of Invitation:
  Information on Visiting Canada, please visit:
http://www.cic.gc.ca/english/visit/index.asp

  After you complete the registration process, you can request an electroni=
c IETF letter of invitation as well. The registration system also allows fo=
r you to request a hard copy IETF letter of invitation. You may also reques=
t one at a later time by following the link provided in the confirmation em=
ail.

  Please note that the IETF Letter of Invitation may not be sufficient for =
obtaining a visa to enter Canada.

3.  Accommodations
  The IETF is holding a block of guest rooms at the Hyatt Regency Vancouver=
, the meeting venue, as well as at the overflow hotel Fairmont Hotel Vancou=
ver, which is located across the street from the Hyatt.
  Room Rates include in room high-speed Internet access. Taxes of 16.5% (ho=
tel room tax, GST and Destination Management Fee) are excluded from the gue=
stroom rate and are subject to change. Room rates DO NOT include daily brea=
kfast.

  Reservations Cut off Date: =

	Hyatt Regency Vancouver - 20 October 2013
	Fairmont Hotel Vancouver - 11 October 2013

For additional information on rates and policies, please visit: http://www.=
ietf.org/meetin/88/hotel.html

4.  Companion Program
 If you are traveling with a friend or family member over 18 years of age y=
ou can register them for the IETF Companion Program for only USD 25.00

 Benefits include:
 - A special welcome reception for companions from 1630-1730 on Sunday, 3 N=
ovember
 - Ability to attend the official Welcome Reception from 1700-1900 on Sunda=
y, 3 November
 - A distinctive meeting badge that grants access to the venue (not to be u=
sed to attend working sessions)
 - Participation in a separate companion email list if you choose to help c=
ommunicate and make plans with other IETF Companions.

 You can register your companion at any time via the IETF website or onsite=
 at the meeting.

 To join the 88 companions mailing list only see:
 https://www.ietf.org/mailman/listinfo/88companions

Only 71 days until the Vancouver IETF!

From iad@ietf.org  Fri Aug 23 06:59:07 2013
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E29E111E819E; Fri, 23 Aug 2013 06:59:06 -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 UFvJDhJS5iss; Fri, 23 Aug 2013 06:59:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA6111E8161; Fri, 23 Aug 2013 06:59:06 -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: Huawei to Host IETF 88 in Vancouver!
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130823135906.27066.3431.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 06:59:06 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 13:59:07 -0000

Announce Huawei Host Vancouver

The IAOC is pleased to announce that Huawei will be the Host for IETF 88 in=
 Vancouver.  =


Huawei has been a long time supporter of the IETF through its participation=
 and sponsorships =

at IETF meetings, but this is their first time as the Host of an IETF meeti=
ng.  Congratulations, =

welcome and Thank You!

Registration is now open for IETF 88 at: http://www.ietf.org/meetings/88/

Many sponsorship opportunities are still available:  =

http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf

If interested contact Andrew Dvorshak, dvorshak@isoc.org.

Once again, thank you Huawei!.  =


See you in Vancouver in 71 days.

Ray
IAD

2014 Meeting Venues

IETF 89	London	Hilton Metropole		March 2-7
IETF 90	Toronto	Fairmont Royal York	        July 20 - 25
IETF 91	Honolulu	Hilton Hawaiian Village	November 9 - 14

From bmanning@isi.edu  Fri Aug 23 10:50:43 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 214B911E81AB; Fri, 23 Aug 2013 10:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.449
X-Spam-Level: 
X-Spam-Status: No, score=-107.449 tagged_above=-999 required=5 tests=[AWL=3.150, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOgnDjitJP+F; Fri, 23 Aug 2013 10:50:39 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C71B221F9E68; Fri, 23 Aug 2013 10:50:38 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7NHn4FA002198 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 23 Aug 2013 10:49:13 -0700 (PDT)
Subject: Re: IETF 88 - Registration Now Open!
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20130823133657.18756.43809.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 10:49:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu>
References: <20130823133657.18756.43809.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
X-Mailman-Approved-At: Fri, 23 Aug 2013 10:53:00 -0700
Cc: wgchairs@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 17:50:43 -0000

and the hotel is fully booked=85.

/bill


On 23August2013Friday, at 6:36, IETF Secretariat wrote:

> 88th IETF Meeting
> Vancouver, BC, Canada
> November 3-8, 2013
> Host: Huawei
>=20
> Meeting venue:  Hyatt Regency Vancouver: =
http://vancouver.hyatt.com/en/hotel/home.html
>=20
> Register online at: http://www.ietf.org/meetings/88/
>=20
> 1.  Registration
> 2.  Visas & Letters of Invitation
> 3.  Accommodations
> 4.  Companion Program
>=20
>=20
> 1. Registration
>  A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October =
2013 UTC 24:00
>  B. After Early-Bird cutoff - USD 800.00
>  C. Full-time Student Registrations - USD 150.00 (with proper ID)
>  D. One Day Pass Registration - USD 350.00
>  E. Registration Cancellation  =20
>              Cut-off for registration cancellation is Monday,
>              28 October 2013 at UTC 24:00.
>              Cancellations are subject to a 10% (ten percent)
>              cancellation fee if requested by that date and time.
>  F. Online Registration and Payment ends Friday, 1 November 2013, 1700 =
local Vancouver time.
>  G. On-site Registration starting Sunday, 3 November 2013 at 1100 =
local Vancouver time.
>=20
> 2. Visas & Letters of Invitation:
>  Information on Visiting Canada, please visit:
> http://www.cic.gc.ca/english/visit/index.asp
>=20
>  After you complete the registration process, you can request an =
electronic IETF letter of invitation as well. The registration system =
also allows for you to request a hard copy IETF letter of invitation. =
You may also request one at a later time by following the link provided =
in the confirmation email.
>=20
>  Please note that the IETF Letter of Invitation may not be sufficient =
for obtaining a visa to enter Canada.
>=20
> 3.  Accommodations
>  The IETF is holding a block of guest rooms at the Hyatt Regency =
Vancouver, the meeting venue, as well as at the overflow hotel Fairmont =
Hotel Vancouver, which is located across the street from the Hyatt.
>  Room Rates include in room high-speed Internet access. Taxes of 16.5% =
(hotel room tax, GST and Destination Management Fee) are excluded from =
the guestroom rate and are subject to change. Room rates DO NOT include =
daily breakfast.
>=20
>  Reservations Cut off Date:=20
> 	Hyatt Regency Vancouver - 20 October 2013
> 	Fairmont Hotel Vancouver - 11 October 2013
>=20
> For additional information on rates and policies, please visit: =
http://www.ietf.org/meetin/88/hotel.html
>=20
> 4.  Companion Program
> If you are traveling with a friend or family member over 18 years of =
age you can register them for the IETF Companion Program for only USD =
25.00
>=20
> Benefits include:
> - A special welcome reception for companions from 1630-1730 on Sunday, =
3 November
> - Ability to attend the official Welcome Reception from 1700-1900 on =
Sunday, 3 November
> - A distinctive meeting badge that grants access to the venue (not to =
be used to attend working sessions)
> - Participation in a separate companion email list if you choose to =
help communicate and make plans with other IETF Companions.
>=20
> You can register your companion at any time via the IETF website or =
onsite at the meeting.
>=20
> To join the 88 companions mailing list only see:
> https://www.ietf.org/mailman/listinfo/88companions
>=20
> Only 71 days until the Vancouver IETF!


From tjc@ecs.soton.ac.uk  Fri Aug 23 11:12:35 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527A721F85EE; Fri, 23 Aug 2013 11:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, 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 ZcRKO2aNwCby; Fri, 23 Aug 2013 11:12:34 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id CAFB311E80EC; Fri, 23 Aug 2013 11:12:33 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r7NICQXu016284;  Fri, 23 Aug 2013 19:12:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r7NICQXu016284
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1377281546; bh=0lijcads9KwGe1dzRTPkV8Hn+lw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=dhszbpBHcJbUdk4+lgeWotqgAo/yt8eE/ZOGNGXrhrlRJEy3ILCO+l04QvwOMDUa9 NYxX9ibk/CcPaC6RntR+Yq15yfzL+M9fB6Ou/mC8pTFtOCGerC84arSdnIMUtnWqCf NQkPc6frUa3/BmULaIodWIHsS1a2tSogg8XKxOo4=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p7MJCQ05445469528B ret-id none; Fri, 23 Aug 2013 19:12:26 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r7NIBkcA027958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 19:12:21 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 88 - Registration Now Open!
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu>
Date: Fri, 23 Aug 2013 19:12:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|81b379a0d8b8b62d08fdda835102184ap7MJCQ03tjc|ecs.soton.ac.uk|6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
References: <20130823133657.18756.43809.idtracker@ietfa.amsl.com> <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu> <6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
To: manning bill <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p7MJCQ054454695200; tid=p7MJCQ05445469528B; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r7NICQXu016284
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: wgchairs@ietf.org, ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:12:35 -0000

On 23 Aug 2013, at 18:49, manning bill <bmanning@isi.edu> wrote:

> and the hotel is fully booked=85.

I guess it got fixed Bill, though I only booked for the meeting week =
itself.

tim

>=20
> /bill
>=20
>=20
> On 23August2013Friday, at 6:36, IETF Secretariat wrote:
>=20
>> 88th IETF Meeting
>> Vancouver, BC, Canada
>> November 3-8, 2013
>> Host: Huawei
>>=20
>> Meeting venue:  Hyatt Regency Vancouver: =
http://vancouver.hyatt.com/en/hotel/home.html
>>=20
>> Register online at: http://www.ietf.org/meetings/88/
>>=20
>> 1.  Registration
>> 2.  Visas & Letters of Invitation
>> 3.  Accommodations
>> 4.  Companion Program
>>=20
>>=20
>> 1. Registration
>> A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October =
2013 UTC 24:00
>> B. After Early-Bird cutoff - USD 800.00
>> C. Full-time Student Registrations - USD 150.00 (with proper ID)
>> D. One Day Pass Registration - USD 350.00
>> E. Registration Cancellation  =20
>>             Cut-off for registration cancellation is Monday,
>>             28 October 2013 at UTC 24:00.
>>             Cancellations are subject to a 10% (ten percent)
>>             cancellation fee if requested by that date and time.
>> F. Online Registration and Payment ends Friday, 1 November 2013, 1700 =
local Vancouver time.
>> G. On-site Registration starting Sunday, 3 November 2013 at 1100 =
local Vancouver time.
>>=20
>> 2. Visas & Letters of Invitation:
>> Information on Visiting Canada, please visit:
>> http://www.cic.gc.ca/english/visit/index.asp
>>=20
>> After you complete the registration process, you can request an =
electronic IETF letter of invitation as well. The registration system =
also allows for you to request a hard copy IETF letter of invitation. =
You may also request one at a later time by following the link provided =
in the confirmation email.
>>=20
>> Please note that the IETF Letter of Invitation may not be sufficient =
for obtaining a visa to enter Canada.
>>=20
>> 3.  Accommodations
>> The IETF is holding a block of guest rooms at the Hyatt Regency =
Vancouver, the meeting venue, as well as at the overflow hotel Fairmont =
Hotel Vancouver, which is located across the street from the Hyatt.
>> Room Rates include in room high-speed Internet access. Taxes of 16.5% =
(hotel room tax, GST and Destination Management Fee) are excluded from =
the guestroom rate and are subject to change. Room rates DO NOT include =
daily breakfast.
>>=20
>> Reservations Cut off Date:=20
>> 	Hyatt Regency Vancouver - 20 October 2013
>> 	Fairmont Hotel Vancouver - 11 October 2013
>>=20
>> For additional information on rates and policies, please visit: =
http://www.ietf.org/meetin/88/hotel.html
>>=20
>> 4.  Companion Program
>> If you are traveling with a friend or family member over 18 years of =
age you can register them for the IETF Companion Program for only USD =
25.00
>>=20
>> Benefits include:
>> - A special welcome reception for companions from 1630-1730 on =
Sunday, 3 November
>> - Ability to attend the official Welcome Reception from 1700-1900 on =
Sunday, 3 November
>> - A distinctive meeting badge that grants access to the venue (not to =
be used to attend working sessions)
>> - Participation in a separate companion email list if you choose to =
help communicate and make plans with other IETF Companions.
>>=20
>> You can register your companion at any time via the IETF website or =
onsite at the meeting.
>>=20
>> To join the 88 companions mailing list only see:
>> https://www.ietf.org/mailman/listinfo/88companions
>>=20
>> Only 71 days until the Vancouver IETF!
>=20


From acmorton@att.com  Fri Aug 23 14:26:21 2013
Return-Path: <acmorton@att.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D8B11E80FA for <wgchairs@ietfa.amsl.com>; Fri, 23 Aug 2013 14:26:21 -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, GB_I_INVITATION=-2, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPHhfWv3-flJ for <wgchairs@ietfa.amsl.com>; Fri, 23 Aug 2013 14:26:16 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 475D721F9FA7 for <wgchairs@ietf.org>; Fri, 23 Aug 2013 14:26:16 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id AA4CC120620; Fri, 23 Aug 2013 17:26:10 -0400 (EDT)
Received: from njfpsrvexg8.research.att.com (njfpsrvexg8.research.att.com [135.207.178.36]) by mail-blue.research.att.com (Postfix) with ESMTP id F3EFAF036D; Fri, 23 Aug 2013 17:26:12 -0400 (EDT)
Received: from NJFPSRVEXG8.research.att.com ([fe80::a44a:8177:9a5d:ac00]) by njfpsrvexg8.research.att.com ([fe80::a44a:8177:9a5d:ac00%15]) with mapi; Fri, 23 Aug 2013 17:26:12 -0400
From: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, manning bill <bmanning@isi.edu>
Date: Fri, 23 Aug 2013 17:24:52 -0400
Subject: RE: IETF 88 - Registration Now Open!
Thread-Topic: IETF 88 - Registration Now Open!
Thread-Index: Ac6gLIBuyxG+jvOCTWOpH4AvkGYSygAGrCq5
Message-ID: <2845723087023D4CB5114223779FA9C83BF8C4E8@njfpsrvexg8.research.att.com>
References: <20130823133657.18756.43809.idtracker@ietfa.amsl.com> <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu> <6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>, <EMEW3|81b379a0d8b8b62d08fdda835102184ap7MJCQ03tjc|ecs.soton.ac.uk|6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|81b379a0d8b8b62d08fdda835102184ap7MJCQ03tjc|ecs.soton.ac.uk|6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 21:26:21 -0000

There was a typo in this link:
http://www.ietf.org/meetin/88/hotel.html

it's
http://www.ietf.org/meeting/88/hotel.html

Al
________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] On Behalf Of Ti=
m Chown [tjc@ecs.soton.ac.uk]
Sent: Friday, August 23, 2013 2:12 PM
To: manning bill
Cc: wgchairs@ietf.org; ietf@ietf.org; IETF Announcement List; irsg@irtf.org
Subject: Re: IETF 88 - Registration Now Open!

On 23 Aug 2013, at 18:49, manning bill <bmanning@isi.edu> wrote:

> and the hotel is fully booked=85.

I guess it got fixed Bill, though I only booked for the meeting week itself=
.

tim

>
> /bill
>
>
> On 23August2013Friday, at 6:36, IETF Secretariat wrote:
>
>> 88th IETF Meeting
>> Vancouver, BC, Canada
>> November 3-8, 2013
>> Host: Huawei
>>
>> Meeting venue:  Hyatt Regency Vancouver: http://vancouver.hyatt.com/en/h=
otel/home.html
>>
>> Register online at: http://www.ietf.org/meetings/88/
>>
>> 1.  Registration
>> 2.  Visas & Letters of Invitation
>> 3.  Accommodations
>> 4.  Companion Program
>>
>>
>> 1. Registration
>> A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October 2013 U=
TC 24:00
>> B. After Early-Bird cutoff - USD 800.00
>> C. Full-time Student Registrations - USD 150.00 (with proper ID)
>> D. One Day Pass Registration - USD 350.00
>> E. Registration Cancellation
>>             Cut-off for registration cancellation is Monday,
>>             28 October 2013 at UTC 24:00.
>>             Cancellations are subject to a 10% (ten percent)
>>             cancellation fee if requested by that date and time.
>> F. Online Registration and Payment ends Friday, 1 November 2013, 1700 lo=
cal Vancouver time.
>> G. On-site Registration starting Sunday, 3 November 2013 at 1100 local V=
ancouver time.
>>
>> 2. Visas & Letters of Invitation:
>> Information on Visiting Canada, please visit:
>> http://www.cic.gc.ca/english/visit/index.asp
>>
>> After you complete the registration process, you can request an electron=
ic IETF letter of invitation as well. The registration system also allows f=
or you to request a hard copy IETF letter of invitation. You may also reque=
st one at a later time by following the link provided in the confirmation e=
mail.
>>
>> Please note that the IETF Letter of Invitation may not be sufficient for=
 obtaining a visa to enter Canada.
>>
>> 3.  Accommodations
>> The IETF is holding a block of guest rooms at the Hyatt Regency Vancouve=
r, the meeting venue, as well as at the overflow hotel Fairmont Hotel Vanco=
uver, which is located across the street from the Hyatt.
>> Room Rates include in room high-speed Internet access. Taxes of 16.5% (h=
otel room tax, GST and Destination Management Fee) are excluded from the gu=
estroom rate and are subject to change. Room rates DO NOT include daily bre=
akfast.
>>
>> Reservations Cut off Date:
>>      Hyatt Regency Vancouver - 20 October 2013
>>      Fairmont Hotel Vancouver - 11 October 2013
>>
>> For additional information on rates and policies, please visit: http://w=
ww.ietf.org/meetin/88/hotel.html
>>
>> 4.  Companion Program
>> If you are traveling with a friend or family member over 18 years of age=
 you can register them for the IETF Companion Program for only USD 25.00
>>
>> Benefits include:
>> - A special welcome reception for companions from 1630-1730 on Sunday, 3=
 November
>> - Ability to attend the official Welcome Reception from 1700-1900 on Sun=
day, 3 November
>> - A distinctive meeting badge that grants access to the venue (not to be=
 used to attend working sessions)
>> - Participation in a separate companion email list if you choose to help=
 communicate and make plans with other IETF Companions.
>>
>> You can register your companion at any time via the IETF website or onsi=
te at the meeting.
>>
>> To join the 88 companions mailing list only see:
>> https://www.ietf.org/mailman/listinfo/88companions
>>
>> Only 71 days until the Vancouver IETF!
>

From sandy@tislabs.com  Fri Aug 23 14:38:11 2013
Return-Path: <sandy@tislabs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C9D21F9E13 for <wgchairs@ietfa.amsl.com>; Fri, 23 Aug 2013 14:38: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 mBPoBWhdpOS4 for <wgchairs@ietfa.amsl.com>; Fri, 23 Aug 2013 14:38:07 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id 422F321F9D62 for <wgchairs@ietf.org>; Fri, 23 Aug 2013 14:38:07 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id E1EEC28B003A; Fri, 23 Aug 2013 17:38:06 -0400 (EDT)
Received: by nova.tislabs.com (Postfix, from userid 2005) id DC5901F8033; Fri, 23 Aug 2013 17:38:06 -0400 (EDT)
To: acmorton@att.com, bmanning@isi.edu, tjc@ecs.soton.ac.uk
Subject: RE: IETF 88 - Registration Now Open!
Message-Id: <20130823213806.DC5901F8033@nova.tislabs.com>
Date: Fri, 23 Aug 2013 17:38:06 -0400 (EDT)
From: sandy@tislabs.com
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 21:38:11 -0000

>There was a typo in this link:
>http://www.ietf.org/meetin/88/hotel.html
>
>it's
>http://www.ietf.org/meeting/88/hotel.html

Another possible confusion: reservations for the conference rate are
not made through the hyatt web site but through
https://resweb.passkey.com/go/ietf88.

(Looking at the rates the Hyatt quotes for direct to the site
reservation requests, we owe the Secretariat thanks for their
negotiation skills.)

--Sandy



From mary.ietf.barnes@gmail.com  Tue Aug 27 08:48:21 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A5F21E80E9 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.311
X-Spam-Level: 
X-Spam-Status: No, score=-102.311 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LDnNzJz5aLb for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:48:21 -0700 (PDT)
Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 31B2621E8056 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 08:48:21 -0700 (PDT)
Received: by mail-qe0-f54.google.com with SMTP id i11so2670526qej.41 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 08:48:20 -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=YsgVgy7n1OEEr7OFSuw767u2DDari+TzQzlfsNOB/ts=; b=czqvAt66moM5DNF9YbZrNPhABzOxSEh1l7UYlLsPvKW4vdnY1PM2ju+Of797YEF0xu Ro87E2zYqHdEXyIlwpE3qlYjjhvzQhVSuNBo4mLmBxRXHUeNaC+RM1exwVDWIwYpNZTz RmLQb0BmH5u5GWu4ZaDsFgi3mR54svwxi/aNLKZDYQW7vtgLVv7IoZEE1pQQC3+bMFp8 dwkc7uPqebfIowF+YqIDFD2cmRcqgalOChke9XSBX4rRP/22of6NpIE8uNYkk7k785PO PQ1qAmjxl6H8zMjCkXF1TcCHiUmD9lyhNBk7dYlHwn2qtHe2iKlpOnbyb3q2ibTp2l0p XBLw==
MIME-Version: 1.0
X-Received: by 10.49.39.39 with SMTP id m7mr24453699qek.60.1377618500672; Tue, 27 Aug 2013 08:48:20 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Tue, 27 Aug 2013 08:48:20 -0700 (PDT)
Date: Tue, 27 Aug 2013 10:48:20 -0500
Message-ID: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Subject: Allowing posting of CFPs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bdc15645e648904e4efcdb1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 15:48:21 -0000

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

Hi,

Thus far I have received this CFP (International Conference on Cryptography
...)
on just about every mailing list I am subscribed to. Personally, I consider
this SPAM as it's not coming from a member of the community.  I think we
should only be allowing these postings on a single list and that should be
the IETF discussion.  I will make a confession that as a moderator of many
mailing lists, if I've gotten to these messages before other moderators,
I've NOT been allowing them through except on the architecture discuss
mailing, which is fairly general.   It's junk email IMHO for most of the
RAI area mailing lists.  I can see some of the SEC lists possibly being
relevant although I would think a single posting to an area wide mailing is
all that's appropriate.

I'd be interested to know how others feel.

Mary
WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing lists.

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

<div dir=3D"ltr">Hi,<div><br></div><div><span class=3D"">Thus far I have re=
ceived this CFP (I</span><span class=3D"Apple-style-span" style=3D"border-c=
ollapse:collapse;font-family:arial,sans-serif">nternational Conference on C=
ryptography ...)</span></div>
<div><span class=3D"">on just about every mailing list I am subscribed to. =
Personally, I consider this SPAM as it&#39;s not coming from a member of th=
e community. =A0I think we should only be allowing these postings on a sing=
le list and that should be the IETF discussion. =A0I will make a confession=
 that as a moderator of many mailing lists, if I&#39;ve gotten to these mes=
sages before other moderators, I&#39;ve NOT been allowing them through exce=
pt on the architecture discuss mailing, which is fairly general. =A0 It&#39=
;s junk email IMHO for most of the RAI area mailing lists. =A0I can see som=
e of the SEC lists possibly being relevant although I would think a single =
posting to an area wide mailing is all that&#39;s appropriate.=A0</span></d=
iv>
<div><br></div><div>I&#39;d be interested to know how others feel. =A0</div=
><div><br></div><div>Mary</div><div>WG chair for CLUE and DISPATCH and a co=
uple dozen IAB related mailing lists.</div></div>

--047d7bdc15645e648904e4efcdb1--

From dcrocker@bbiw.net  Tue Aug 27 08:49:32 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5F411E81B6 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkCqoB1BJcfl for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:49:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8F95611E81B1 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 08:49:27 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7RFnMQu007729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Aug 2013 08:49:25 -0700
Message-ID: <521CCA7A.2050008@bbiw.net>
Date: Tue, 27 Aug 2013 08:49:14 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@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.67]); Tue, 27 Aug 2013 08:49:25 -0700 (PDT)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 15:49:32 -0000

On 8/27/2013 8:48 AM, Mary Barnes wrote:
> I'd be interested to know how others feel.

+10

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From joelja@bogus.com  Tue Aug 27 08:53:49 2013
Return-Path: <joelja@bogus.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12F4B11E8388 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:53:49 -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 J4GyeA+xMV9q for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:53:48 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2FABB11E81B6 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 08:53:43 -0700 (PDT)
Received: from mb-aye.corp.zynga.com (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 r7RFrfGC080492 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 27 Aug 2013 15:53:41 GMT (envelope-from joelja@bogus.com)
Message-ID: <521CCB80.3040006@bogus.com>
Date: Tue, 27 Aug 2013 08:53:36 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
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]); Tue, 27 Aug 2013 15:53:41 +0000 (UTC)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 15:53:49 -0000

On 8/27/13 8:48 AM, Mary Barnes wrote:
> Hi,
>
> Thus far I have received this CFP (International Conference on
> Cryptography ...)
> on just about every mailing list I am subscribed to. Personally, I
> consider this SPAM as it's not coming from a member of the community.
>  I think we should only be allowing these postings on a single list
> and that should be the IETF discussion.
They shouldn't be there either.
>  I will make a confession that as a moderator of many mailing lists,
> if I've gotten to these messages before other moderators, I've NOT
> been allowing them through except on the architecture discuss mailing,
> which is fairly general.   It's junk email IMHO for most of the RAI
> area mailing lists.  I can see some of the SEC lists possibly being
> relevant although I would think a single posting to an area wide
> mailing is all that's appropriate. 
>
I discard them when moderating.
> I'd be interested to know how others feel.  
>
> Mary
> WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing
> lists.


From housley@vigilsec.com  Tue Aug 27 08:59:16 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEFD021F9D95 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxt9Pb8WkBYU for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 08:59:10 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id A299311E8383 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 08:59:08 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 1F07AF24032; Tue, 27 Aug 2013 12:00: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 FW8MufuKCnie; Tue, 27 Aug 2013 11:58:34 -0400 (EDT)
Received: from [192.168.38.134] (static-108-15-20-23.bltmmd.fios.verizon.net [108.15.20.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id AAE8EF2402A; Tue, 27 Aug 2013 12:00:07 -0400 (EDT)
Subject: Re: Allowing posting of CFPs
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-28--120014500
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Date: Tue, 27 Aug 2013 11:59:03 -0400
Message-Id: <5A488075-EEA6-4604-BE07-8F95281E2405@vigilsec.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 15:59:16 -0000

--Apple-Mail-28--120014500
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

For one mail list, I asked the sender not to do it again.

Russ


On Aug 27, 2013, at 11:48 AM, Mary Barnes wrote:

> Hi,
>=20
> Thus far I have received this CFP (International Conference on =
Cryptography ...)
> on just about every mailing list I am subscribed to. Personally, I =
consider this SPAM as it's not coming from a member of the community.  I =
think we should only be allowing these postings on a single list and =
that should be the IETF discussion.  I will make a confession that as a =
moderator of many mailing lists, if I've gotten to these messages before =
other moderators, I've NOT been allowing them through except on the =
architecture discuss mailing, which is fairly general.   It's junk email =
IMHO for most of the RAI area mailing lists.  I can see some of the SEC =
lists possibly being relevant although I would think a single posting to =
an area wide mailing is all that's appropriate.=20
>=20
> I'd be interested to know how others feel. =20
>=20
> Mary
> WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing =
lists.


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

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">For one mail list, I asked the sender not to do it again.<div><br></div><div>Russ</div><div><br></div><div><br><div><div>On Aug 27, 2013, at 11:48 AM, Mary Barnes wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div><span class="">Thus far I have received this CFP (I</span><span class="Apple-style-span" style="border-collapse:collapse;font-family:arial,sans-serif">nternational Conference on Cryptography ...)</span></div>
<div><span class="">on just about every mailing list I am subscribed to. Personally, I consider this SPAM as it's not coming from a member of the community. &nbsp;I think we should only be allowing these postings on a single list and that should be the IETF discussion. &nbsp;I will make a confession that as a moderator of many mailing lists, if I've gotten to these messages before other moderators, I've NOT been allowing them through except on the architecture discuss mailing, which is fairly general. &nbsp; It's junk email IMHO for most of the RAI area mailing lists. &nbsp;I can see some of the SEC lists possibly being relevant although I would think a single posting to an area wide mailing is all that's appropriate.&nbsp;</span></div>
<div><br></div><div>I'd be interested to know how others feel. &nbsp;</div><div><br></div><div>Mary</div><div>WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing lists.</div></div>
</blockquote></div><br></div></body></html>
--Apple-Mail-28--120014500--

From keith.drage@alcatel-lucent.com  Tue Aug 27 09:01:07 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF02711E81A2 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.624
X-Spam-Level: 
X-Spam-Status: No, score=-110.624 tagged_above=-999 required=5 tests=[AWL=-0.025, 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 WIwtAAKJzBeP for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:01:02 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 08ED911E838B for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:00:54 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r7RG0i3U006737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Aug 2013 11:00:45 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r7RG0fGE021131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 27 Aug 2013 18:00:43 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 27 Aug 2013 18:00:42 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Dave Crocker <dcrocker@bbiw.net>, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: RE: Allowing posting of CFPs
Thread-Topic: Allowing posting of CFPs
Thread-Index: AQHOozzfvJVDsSXujkeLPXRz4xqz9ZmpEfQAgAAiC8A=
Date: Tue, 27 Aug 2013 16:00:41 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B089593@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCA7A.2050008@bbiw.net>
In-Reply-To: <521CCA7A.2050008@bbiw.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:01:07 -0000

This has been discussed in the past.

There is a distinction between those posted from non-members of the mailing=
 list, and those who are members of the mailing list.=20

For non-members of the mailing list I have no compunction about binning the=
m. (For other mails from non-members, I also do not automatically moderate =
mails through and frequently point them at what I consider to be a more app=
ropriate mailing list - the SIP mailing list used to garner numerous questi=
ons about specific voice over IP implementations). Nearly all such conferen=
ce postings come from list non-members.

For mails from members of the mailing list, obviously they do not automatic=
ally go into moderation. Further we have a criteria about the openness of t=
he IETF working groups. I would normally respond to this on a first occasio=
n asking them to justify how the mail advances the work of the working grou=
p. I have asked that mailing list members contact the chairs to discuss the=
 appropriateness or not of posting such a call. Repeated postings of such u=
njustified material would result in my setting the moderation bit. I've onl=
y done this once.

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Dave Crocker
> Sent: 27 August 2013 16:49
> To: Mary Barnes
> Cc: IETF WG Chairs
> Subject: Re: Allowing posting of CFPs
>=20
> On 8/27/2013 8:48 AM, Mary Barnes wrote:
> > I'd be interested to know how others feel.
>=20
> +10
>=20
> d/
>=20
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From pkyzivat@alum.mit.edu  Tue Aug 27 09:01:09 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B72B621E8113 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UeK3tRW2Ppbb for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:01:04 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id ACF5D21E8104 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:00:56 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta02.westchester.pa.mail.comcast.net with comcast id HnFz1m0020mv7h051s0wpl; Tue, 27 Aug 2013 16:00:56 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta11.westchester.pa.mail.comcast.net with comcast id Hs0v1m01S3ZTu2S3Xs0vBq; Tue, 27 Aug 2013 16:00:56 +0000
Message-ID: <521CCD36.4020906@alum.mit.edu>
Date: Tue, 27 Aug 2013 12:00:54 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCA7A.2050008@bbiw.net>
In-Reply-To: <521CCA7A.2050008@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1377619256; bh=RKqg6iI/H4LXgPU/+I8sjt2STJNSWln8dO8cV67wkK8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YzpAsqLRD6vOfsRHt2igyARwtyk1SbthNqaJzO2MotPF0hmqR7jVbTrqH4goH1XXX MsfSSgWK6Ng5DtbyhHjs9xVx545fmknReWpvZa2VgNWXhfVGEikQSjvqGFdpAnBoTX OIn0swU9RG4bvIPOxJ+Nb/G/wb8hzFvsc2xE8XcJ7xn+X8dzFbIrE85Vxdr9SjH69i tdxL0WvZxl2SzuiAAbzQBVAGrkfNpd5D5hWu1gB3vFJsaQFXbDb9Mm9YxdtFdTxBf8 yRO6SJZFjof5ggrDeVlTmG4yVR0Bb0lMykNfM4bSC3M/IfypkcXwSx1Y7s9wybnXdv gvVp8TnRMfBwg==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:01:09 -0000

I'm ok with this if the CFP is really relevant to the scope of the WG.
The best people to judge that are people within the WG. So if a wg 
member posts a relevant CFP to a list I moderate then I'm not likely to 
object. If the CFP comes to me for moderation I *may* allow it if it 
seems relevant without my having to do a lot of research about it. But I 
wouldn't appreciate getting floods of these needing moderation.

	Thanks,
	Paul

On 8/27/13 11:49 AM, Dave Crocker wrote:
> On 8/27/2013 8:48 AM, Mary Barnes wrote:
>> I'd be interested to know how others feel.
>
> +10
>
> d/
>


From cabo@tzi.org  Tue Aug 27 09:03:27 2013
Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2568A11E838E for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.182
X-Spam-Level: 
X-Spam-Status: No, score=-106.182 tagged_above=-999 required=5 tests=[AWL=0.067, 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 mdGv8PQJ9vl4 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:03:22 -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 2B46F11E838C for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7RG3AwJ006106; Tue, 27 Aug 2013 18:03:10 +0200 (CEST)
Received: from [192.168.217.105] (p5489240E.dip0.t-ipconnect.de [84.137.36.14]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5067FBF2; Tue, 27 Aug 2013 18:03:10 +0200 (CEST)
Subject: Re: Allowing posting of CFPs
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Date: Tue, 27 Aug 2013 18:03:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CABCA3D-5A0D-4E13-92BE-546780EAEEBE@tzi.org>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:03:27 -0000

On Aug 27, 2013, at 17:48, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

> Thus far I have received this CFP (International Conference on =
Cryptography ...)

I have that source address on auto-discard already...

I don't know if you are into this kind of humor, but have a look at =
http://www.asdf.org.in

Gr=FC=DFe, Carsten


From mary.ietf.barnes@gmail.com  Tue Aug 27 09:03:58 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5165E21F99A2 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.332
X-Spam-Level: 
X-Spam-Status: No, score=-102.332 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rmMxbDVvDC4x for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:03:57 -0700 (PDT)
Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 8131F21F967A for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:03:57 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id a11so2731687qen.11 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:03: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=4NosEGp30XfxXLZFwo2KKBVaM/FRe8MHorMOYHZGNag=; b=glJ5CPrNTuua1WTJ80COnPFC68Zc4eHcVAOE59JKlXiY9ACezqZC4cSC5zSwmeq29S LmtlCS8sdjgBBSZGqLwGUpElYBuEZATw/rw0lrd0U9Bjz65gpKKUK3VI9eHxVvTqwPyA civtzVXEv4rGo8XDBvGlWr1uTUnHrZlGox60nURDK//1EcSGO0XAj8tkY3ZPS+s/Cb9j qKOa+2SDInPjUvRzCOziwfIC6XSx4dSN7J0tU6nq1k0i7G8fGMPDPPEaNJNIRU2FSoA6 Xj9oYOpgw+d8ULIsj31WHJwHebHGVGlQpS4FPr4+2MvendbmIoEmbXpeV4VKdd2qBo4M Y0Xg==
MIME-Version: 1.0
X-Received: by 10.224.43.200 with SMTP id x8mr9140351qae.57.1377619436890; Tue, 27 Aug 2013 09:03:56 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Tue, 27 Aug 2013 09:03:56 -0700 (PDT)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B089593@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCA7A.2050008@bbiw.net> <949EF20990823C4C85C18D59AA11AD8B089593@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Date: Tue, 27 Aug 2013 11:03:56 -0500
Message-ID: <CAHBDyN6GLca6WL541hqkmttOnA+J8W+gorSpRN21-Zht7oyW4g@mail.gmail.com>
Subject: Re: Allowing posting of CFPs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7bf0ec222bee9b04e4f00570
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:03:58 -0000

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

On Tue, Aug 27, 2013 at 11:00 AM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

> This has been discussed in the past.
>
[MB] Right, however, the problem doesn't seem to be consistently handled by
the current set of WG chairs. [/MB]

>
> There is a distinction between those posted from non-members of the
> mailing list, and those who are members of the mailing list.
>
> For non-members of the mailing list I have no compunction about binning
> them. (For other mails from non-members, I also do not automatically
> moderate mails through and frequently point them at what I consider to be a
> more appropriate mailing list - the SIP mailing list used to garner
> numerous questions about specific voice over IP implementations). Nearly
> all such conference postings come from list non-members.
>
[MB] These are the ones that I have an issue with. [/MB]

>
> For mails from members of the mailing list, obviously they do not
> automatically go into moderation. Further we have a criteria about the
> openness of the IETF working groups. I would normally respond to this on a
> first occasion asking them to justify how the mail advances the work of the
> working group. I have asked that mailing list members contact the chairs to
> discuss the appropriateness or not of posting such a call. Repeated
> postings of such unjustified material would result in my setting the
> moderation bit. I've only done this once.
>
[MB] I totally agree. I would cut folks slack for infrequent postings to a
single mailing list. But, sending to more than a couple is SPAM IMHO.  I
think most areas have area wide mailing lists and I would think if the
poster thinks it might be of interest to multiple WGs in that area, that
should be the only place it gets posted. [/MB]

>
> Regards
>
> Keith
>
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> > Behalf Of Dave Crocker
> > Sent: 27 August 2013 16:49
> > To: Mary Barnes
> > Cc: IETF WG Chairs
> > Subject: Re: Allowing posting of CFPs
> >
> > On 8/27/2013 8:48 AM, Mary Barnes wrote:
> > > I'd be interested to know how others feel.
> >
> > +10
> >
> > d/
> >
> > --
> > Dave Crocker
> > Brandenburg InternetWorking
> > bbiw.net
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Tue, Aug 27, 2013 at 11:00 A=
M, DRAGE, Keith (Keith) <span dir=3D"ltr">&lt;<a href=3D"mailto:keith.drage=
@alcatel-lucent.com" target=3D"_blank">keith.drage@alcatel-lucent.com</a>&g=
t;</span> wrote:<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This has been dis=
cussed in the past.<br></blockquote><div>[MB] Right, however, the problem d=
oesn&#39;t seem to be consistently handled by the current set of WG chairs.=
 [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
There is a distinction between those posted from non-members of the mailing=
 list, and those who are members of the mailing list.<br>
<br>
For non-members of the mailing list I have no compunction about binning the=
m. (For other mails from non-members, I also do not automatically moderate =
mails through and frequently point them at what I consider to be a more app=
ropriate mailing list - the SIP mailing list used to garner numerous questi=
ons about specific voice over IP implementations). Nearly all such conferen=
ce postings come from list non-members.<br>
</blockquote><div>[MB] These are the ones that I have an issue with. [/MB]=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
For mails from members of the mailing list, obviously they do not automatic=
ally go into moderation. Further we have a criteria about the openness of t=
he IETF working groups. I would normally respond to this on a first occasio=
n asking them to justify how the mail advances the work of the working grou=
p. I have asked that mailing list members contact the chairs to discuss the=
 appropriateness or not of posting such a call. Repeated postings of such u=
njustified material would result in my setting the moderation bit. I&#39;ve=
 only done this once.<br>
</blockquote><div>[MB] I totally agree. I would cut folks slack for infrequ=
ent postings to a single mailing list. But, sending to more than a couple i=
s SPAM IMHO. =A0I think most areas have area wide mailing lists and I would=
 think if the poster thinks it might be of interest to multiple WGs in that=
 area, that should be the only place it gets posted. [/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Keith<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:wgchairs-bounces@ietf.org">wgchairs-bounces@ie=
tf.org</a> [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org">wgchairs-bo=
unces@ietf.org</a>] On<br>
&gt; Behalf Of Dave Crocker<br>
&gt; Sent: 27 August 2013 16:49<br>
&gt; To: Mary Barnes<br>
&gt; Cc: IETF WG Chairs<br>
&gt; Subject: Re: Allowing posting of CFPs<br>
&gt;<br>
&gt; On 8/27/2013 8:48 AM, Mary Barnes wrote:<br>
&gt; &gt; I&#39;d be interested to know how others feel.<br>
&gt;<br>
&gt; +10<br>
&gt;<br>
&gt; d/<br>
&gt;<br>
&gt; --<br>
&gt; Dave Crocker<br>
&gt; Brandenburg InternetWorking<br>
&gt; <a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</div></div></blockquote></div><br></div></div>

--047d7bf0ec222bee9b04e4f00570--

From mary.ietf.barnes@gmail.com  Tue Aug 27 09:07:10 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257C611E839C for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.35
X-Spam-Level: 
X-Spam-Status: No, score=-102.35 tagged_above=-999 required=5 tests=[AWL=0.249, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upJtT9q52gOk for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:07:09 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id D400F11E8391 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:07:06 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id n7so1609754qcx.24 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PhOnNu5osugU0uBlEFRBhx/uDq5x/ouThPz2reEAUwI=; b=Kgc1g16tbeV9VOXSQ0yAa5TZqiJfU9dp+ZVEUryJBpEWfa+5Y/pIOCKM56NFEtDD2s 1mMdwbYcJruFPq8TEcezQrV+3+8RnMik7p/GYDq2h7yjP3CRPqWCKETaGlWzRe4NZzsp 7Geg0Dl2UTdLbDlNYHyijS8yvAHNPgHyAiF57TJkuaI0xsyyq/QZsLCK18YubOOMK58J yTw/SDu+ekbMJqnccFMZMcqyEIvF0RnX2sc95ZijBduVDc6bbsrrNooaxBYT21viIZmm mJ1xeucCx+GhFXZLQB9dQuDDV070XqBopIlDplPZ1y9tASgtjNpNAE5BM33hM6pw/30S YReg==
MIME-Version: 1.0
X-Received: by 10.224.73.137 with SMTP id q9mr19457120qaj.13.1377619626341; Tue, 27 Aug 2013 09:07:06 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Tue, 27 Aug 2013 09:07:06 -0700 (PDT)
In-Reply-To: <6CABCA3D-5A0D-4E13-92BE-546780EAEEBE@tzi.org>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <6CABCA3D-5A0D-4E13-92BE-546780EAEEBE@tzi.org>
Date: Tue, 27 Aug 2013 11:07:06 -0500
Message-ID: <CAHBDyN4_LbNXG6UgqVCphR2DA63GLR9CW=+sYzNhey1L_9zohg@mail.gmail.com>
Subject: Re: Allowing posting of CFPs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=001a11c3bed476bc5104e4f010a3
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:07:10 -0000

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

On Tue, Aug 27, 2013 at 11:03 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 27, 2013, at 17:48, Mary Barnes <mary.ietf.barnes@gmail.com> wrote=
:
>
> > Thus far I have received this CFP (International Conference on
> Cryptography ...)
>
> I have that source address on auto-discard already...
>
[MB] I like that idea.  I wonder if we can't go further and ask AMS IT
folks to block it?  We could send a fairly polite message that IETF does
not allow bulk posting to IETF mailing lists in general and in particular
for non-WG members.  I've asked them to do that for another bulk spam we
were getting a couple weeks back, although, it was more than obvious that
it was spam. [/MB]

>
> I don't know if you are into this kind of humor, but have a look at
> http://www.asdf.org.in
>
> Gr=FC=DFe, Carsten
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Tue, Aug 27, 2013 at 11:03 A=
M, Carsten Bormann <span dir=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" ta=
rget=3D"_blank">cabo@tzi.org</a>&gt;</span> wrote:<br><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Aug 27, 2013, at 17:48, Mary Barnes &lt;<a href=3D"mai=
lto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt; wrote:<b=
r>
<br>
&gt; Thus far I have received this CFP (International Conference on Cryptog=
raphy ...)<br>
<br>
</div>I have that source address on auto-discard already...<br></blockquote=
><div>[MB] I like that idea. =A0I wonder if we can&#39;t go further and ask=
 AMS IT folks to block it? =A0We could send a fairly polite message that IE=
TF does not allow bulk posting to IETF mailing lists in general and in part=
icular for non-WG members. =A0I&#39;ve asked them to do that for another bu=
lk spam we were getting a couple weeks back, although, it was more than obv=
ious that it was spam. [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I don&#39;t know if you are into this kind of humor, but have a look at <a =
href=3D"http://www.asdf.org.in" target=3D"_blank">http://www.asdf.org.in</a=
><br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br></div></div>

--001a11c3bed476bc5104e4f010a3--

From vkg@bell-labs.com  Tue Aug 27 09:14:07 2013
Return-Path: <vkg@bell-labs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F4C21F9DB4 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.255
X-Spam-Level: 
X-Spam-Status: No, score=-110.255 tagged_above=-999 required=5 tests=[AWL=0.344, 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 1ept+4u0Pi2v for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:14:01 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id A039521F9D21 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:14:01 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r7RGDwnu026426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Aug 2013 11:13:59 -0500 (CDT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r7RGDwpx022607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Aug 2013 11:13:58 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r7RGDwrf024935; Tue, 27 Aug 2013 11:13:58 -0500 (CDT)
Message-ID: <521CD164.8080809@bell-labs.com>
Date: Tue, 27 Aug 2013 11:18:44 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:14:07 -0000

On 08/27/2013 10:48 AM, Mary Barnes wrote:
> Hi,
>
> Thus far I have received this CFP (International Conference on
> Cryptography ...)
> on just about every mailing list I am subscribed to. Personally, I
> consider this SPAM as it's not coming from a member of the community.  I
> think we should only be allowing these postings on a single list and
> that should be the IETF discussion.

Mary: The IETF discussion list is probably not the right place either.

I have been on both sides of the coin, i.e., when I want to post a
CfP and when I have to moderate one.  Here is what I do:

When I want to post a CfP pertinent to a WG list, I usually first send
an email to the WG chairs of the list and ask them permission.  I do
this even if I am subscribed to the list and my posting would normally
be allowed.  In my experience, most WG chairs are happy to oblige if
they are convinced that the CfP is in the pertinent interest of some
of the WG members.  I do think that the IETF draws its share of
academics and I see no harm in allowing CfP that are pertinent to
some members of the WG who may benefit.

When I want to moderate a CfP as a WG chair, then my actions depend on
who is posting the CfP:

   - If it is a WG member who has asked to post the CfP and if the CfP
     is congruent to the workings of the group, I go ahead and give
     permission.
   - If the CfP has been posted by a WG member without consulting chairs
     first, and the CfP is pertinent to the workings of the group, I
     usually allow it through and send a private email to the sender
     asking to be consulted for future CfPs.
   - If the CfP has been posted by a WG member but that WG member has
     only posted CfPs in the past and has not contributed to the
     betterment of the work in the group, then I usually warn the WG
     member that future CfP-only emails will result in loss of posting
     privileges.
   - If the CfP has been posted by a non-member, then it quarantined
     and when I catch up with quarantined email and I feel that the CfP
     is warranted, I will allow it to be posted.
   - If the CfP has been posted by a non-member, then it is quarantined
     and when I catch up with the quarantined email and I feel that
     the CfP is orthogonal to the workings of the group, I reject the
     posting.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq

From ynir@checkpoint.com  Tue Aug 27 09:19:02 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A26121F9A97 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.647
X-Spam-Level: 
X-Spam-Status: No, score=-10.647 tagged_above=-999 required=5 tests=[AWL=-0.048, 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 uwJ-cHJTfykL for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:18:56 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1A85E21F8BFD for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:18:55 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r7RGInV2007131; Tue, 27 Aug 2013 19:18:49 +0300
X-CheckPoint: {521CD169-0-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.173]) by IL-EX10.ad.checkpoint.com ([169.254.2.246]) with mapi id 14.02.0347.000; Tue, 27 Aug 2013 19:18:49 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Allowing posting of CFPs
Thread-Topic: Allowing posting of CFPs
Thread-Index: AQHOozzhJHea3DUHsEGnX6/C1/5mXZmpAmkAgAAHCYA=
Date: Tue, 27 Aug 2013 16:18:49 +0000
Message-ID: <49ED2E7D-F5C8-4887-A530-B319BAE1376E@checkpoint.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCB80.3040006@bogus.com>
In-Reply-To: <521CCB80.3040006@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.23]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <81F7679EA5DAFE40A0CBADB209A239D7@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:19:02 -0000

On Aug 27, 2013, at 6:53 PM, joel jaeggli <joelja@bogus.com> wrote:

> On 8/27/13 8:48 AM, Mary Barnes wrote:
>> Hi,
>>=20
>> Thus far I have received this CFP (International Conference on
>> Cryptography ...)
>> on just about every mailing list I am subscribed to. Personally, I
>> consider this SPAM as it's not coming from a member of the community.
>> I think we should only be allowing these postings on a single list
>> and that should be the IETF discussion.
> They shouldn't be there either.
>> I will make a confession that as a moderator of many mailing lists,
>> if I've gotten to these messages before other moderators, I've NOT
>> been allowing them through except on the architecture discuss mailing,
>> which is fairly general.   It's junk email IMHO for most of the RAI
>> area mailing lists.  I can see some of the SEC lists possibly being
>> relevant although I would think a single posting to an area wide
>> mailing is all that's appropriate.=20
>>=20
> I discard them when moderating.

I just ignore them and let them expire.

From lars@netapp.com  Tue Aug 27 09:20:02 2013
Return-Path: <lars@netapp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FB821F9AC1 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.713
X-Spam-Level: 
X-Spam-Status: No, score=-4.713 tagged_above=-999 required=5 tests=[AWL=-2.114, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C2HgRUTecPYS for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:19:57 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7325F11E81CF for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:19:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,968,1367996400";  d="asc'?scan'208";a="44702018"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx11-out.netapp.com with ESMTP; 27 Aug 2013 09:19:56 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.116]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Tue, 27 Aug 2013 09:19:55 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Subject: Re: Allowing posting of CFPs
Thread-Topic: Allowing posting of CFPs
Thread-Index: AQHOozzzCfkyW8MZD0ulx0wIc7xuLJmpsRIAgAAAUwA=
Date: Tue, 27 Aug 2013 16:19:55 +0000
Message-ID: <94409AF8-BDC6-4C35-B6E2-10EF6CD34107@netapp.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CD164.8080809@bell-labs.com>
In-Reply-To: <521CD164.8080809@bell-labs.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=_B00883D5-3899-4783-AEBE-DC2151ACDC4A"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:20:02 -0000

--Apple-Mail=_B00883D5-3899-4783-AEBE-DC2151ACDC4A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

I have "Subject: .*(CFP|Call for)" in the "header_filter_rules" Option =
of my mailman lists if a "hold" action, so I can moderate which get =
through.

Lars

--Apple-Mail=_B00883D5-3899-4783-AEBE-DC2151ACDC4A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQCVAwUBUhzRqtZcnpRveo1xAQJOGAP+NsyAK+CS6xOiY2g+N0ibHoeRXIKOvtyz
1y1Ch0dzTDmUnyJMGlnLiKWsoYJNBQtu6xno4yNjXFe1fYQoVrEnkiupRVOnpchU
fynAPI8XHckhh/J/p/dp6WZnhjGd3O20sCurRkyXHrA3aL9Q6Qx5Z0GEbUwkSWEI
JD7VTf+SpVA=
=gxRj
-----END PGP SIGNATURE-----

--Apple-Mail=_B00883D5-3899-4783-AEBE-DC2151ACDC4A--

From dcrocker@bbiw.net  Tue Aug 27 09:22:52 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F8A11E81CF for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9T4Uvwl7ibtX for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:22:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EFA2411E82A1 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:22:46 -0700 (PDT)
Received: from [192.168.1.74] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7RGMgnM008422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:22:46 -0700
Message-ID: <521CD250.9060906@bbiw.net>
Date: Tue, 27 Aug 2013 09:22:40 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <6CABCA3D-5A0D-4E13-92BE-546780EAEEBE@tzi.org> <CAHBDyN4_LbNXG6UgqVCphR2DA63GLR9CW=+sYzNhey1L_9zohg@mail.gmail.com>
In-Reply-To: <CAHBDyN4_LbNXG6UgqVCphR2DA63GLR9CW=+sYzNhey1L_9zohg@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.67]); Tue, 27 Aug 2013 09:22:46 -0700 (PDT)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:22:52 -0000

On 8/27/2013 9:07 AM, Mary Barnes wrote:
> [MB] I like that idea.  I wonder if we can't go further and ask AMS IT
> folks to block it?


I think the answer is yes, but it's per-mailing list.  I don't think 
there can be a 'master' blacklist for the list server, though that 
certainly would be nice.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From mary.ietf.barnes@gmail.com  Tue Aug 27 09:26:21 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F68211E8386 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.365
X-Spam-Level: 
X-Spam-Status: No, score=-102.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lpi+L0Msz1I4 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:26:15 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDE411E82DF for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:26:13 -0700 (PDT)
Received: by mail-qc0-f173.google.com with SMTP id z10so2713381qcx.32 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WnK1UziZPYwPDH8xXbB7cFmrGVvQEfrEg9M+sP/57QQ=; b=Wp8bs6UAP3VB7ClkF0bFMPYWdb/UjpIeMm3uRYbfMo6ll21IgSlaNghAO7IwB7EXU8 Sq5fAn0GxGJMclTzAsWcIJoYA+FRpQPSzuHOLsURZkgYi8bujsTURfIYk0knELjNINZH aYhV4eX/o2aN/NnTNKb7LcgC4QtRhu/mgZiBojs7HAnMn7gEz7d2WoOPU3KlG5fkn3JR GAKqVj3czzuagsXGXhWE+UYKONL5h667jCD/qOg3X1aWg+0YUWbIF1BjYO9v9qtdzSl3 pyTbVFby5/Y7X3w2Wp93yk3WnGpGFKdI6wzRo2eQh92GYKBFZA56Ae8CvYaqm1pFyoDJ g/cg==
MIME-Version: 1.0
X-Received: by 10.49.53.10 with SMTP id x10mr24363992qeo.46.1377620767012; Tue, 27 Aug 2013 09:26:07 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Tue, 27 Aug 2013 09:26:06 -0700 (PDT)
In-Reply-To: <49ED2E7D-F5C8-4887-A530-B319BAE1376E@checkpoint.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCB80.3040006@bogus.com> <49ED2E7D-F5C8-4887-A530-B319BAE1376E@checkpoint.com>
Date: Tue, 27 Aug 2013 11:26:06 -0500
Message-ID: <CAHBDyN65WDn9653ZzR-X=W30j4U_kwxnhL5+A0WZy1Hz+Z1r+A@mail.gmail.com>
Subject: Re: Allowing posting of CFPs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=047d7bd766de74009104e4f054b5
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:26:21 -0000

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

On Tue, Aug 27, 2013 at 11:18 AM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Aug 27, 2013, at 6:53 PM, joel jaeggli <joelja@bogus.com> wrote:
>
> > On 8/27/13 8:48 AM, Mary Barnes wrote:
> >> Hi,
> >>
> >> Thus far I have received this CFP (International Conference on
> >> Cryptography ...)
> >> on just about every mailing list I am subscribed to. Personally, I
> >> consider this SPAM as it's not coming from a member of the community.
> >> I think we should only be allowing these postings on a single list
> >> and that should be the IETF discussion.
> > They shouldn't be there either.
> >> I will make a confession that as a moderator of many mailing lists,
> >> if I've gotten to these messages before other moderators, I've NOT
> >> been allowing them through except on the architecture discuss mailing,
> >> which is fairly general.   It's junk email IMHO for most of the RAI
> >> area mailing lists.  I can see some of the SEC lists possibly being
> >> relevant although I would think a single posting to an area wide
> >> mailing is all that's appropriate.
> >>
> > I discard them when moderating.
>
> I just ignore them and let them expire.
>
[MB] But, you'll still reminders that you have messages in the moderator's
queue.  Of course, you can delete those, but it's still yet another email
in your inbox that is junk.[/MB]

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Aug 27, 2013 at 11:18 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 class=3D"im"><br>
On Aug 27, 2013, at 6:53 PM, joel jaeggli &lt;<a href=3D"mailto:joelja@bogu=
s.com">joelja@bogus.com</a>&gt; wrote:<br>
<br>
&gt; On 8/27/13 8:48 AM, Mary Barnes wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; Thus far I have received this CFP (International Conference on<br>
&gt;&gt; Cryptography ...)<br>
&gt;&gt; on just about every mailing list I am subscribed to. Personally, I=
<br>
&gt;&gt; consider this SPAM as it&#39;s not coming from a member of the com=
munity.<br>
&gt;&gt; I think we should only be allowing these postings on a single list=
<br>
&gt;&gt; and that should be the IETF discussion.<br>
&gt; They shouldn&#39;t be there either.<br>
&gt;&gt; I will make a confession that as a moderator of many mailing lists=
,<br>
&gt;&gt; if I&#39;ve gotten to these messages before other moderators, I&#3=
9;ve NOT<br>
&gt;&gt; been allowing them through except on the architecture discuss mail=
ing,<br>
&gt;&gt; which is fairly general. =A0 It&#39;s junk email IMHO for most of =
the RAI<br>
&gt;&gt; area mailing lists. =A0I can see some of the SEC lists possibly be=
ing<br>
&gt;&gt; relevant although I would think a single posting to an area wide<b=
r>
&gt;&gt; mailing is all that&#39;s appropriate.<br>
&gt;&gt;<br>
&gt; I discard them when moderating.<br>
<br>
</div>I just ignore them and let them expire.<br></blockquote><div>[MB] But=
, you&#39;ll still reminders that you have messages in the moderator&#39;s =
queue. =A0Of course, you can delete those, but it&#39;s still yet another e=
mail in your inbox that is junk.[/MB]=A0</div>
</div><br></div></div>

--047d7bd766de74009104e4f054b5--

From mary.ietf.barnes@gmail.com  Tue Aug 27 09:29:39 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2DA21F9BF1 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.379
X-Spam-Level: 
X-Spam-Status: No, score=-102.379 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGow2+7TN+aU for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 09:29:39 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 91DE521F9D4C for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:29:37 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id cy11so2727479qeb.38 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 09:29:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2xB/QQGmvkQKiSqSzJaBy8C1z5Lp0cf1Dhe8RbDYm/E=; b=QxcqZRv9RiYbfFh/7xx1WJ9dgg/gnpuuNwOAWCxaWWDrjZfjE2zcPPPiU1/r1XfBFe LFkAz3H1eHNwTmXuCwoPtgzlhswUcf0bK2aCk0ZPh5NwgLjyzKVwTeytpSsAjLqHSmaQ NyYL4zdSIkmRHkUYt7xmm7K0IRe0j0Zbc8/Tg1JpCeOwPxnsYS/edUi6gP349sHZIrgZ 7Xo2yjOh68bfOpqP4mkrAIBvbQhZMc6WpjRqgIjb6ItMZUyJgb8zqPMdA3DGSqNbiPyD O6+WyuXRJz6cocCSmCP2XIGOPKzu1B7Xkg4gSTJJd810CAzo9zdsor4y/gtZUhdkF0LE XHUw==
MIME-Version: 1.0
X-Received: by 10.229.228.195 with SMTP id jf3mr2342502qcb.0.1377620962948; Tue, 27 Aug 2013 09:29:22 -0700 (PDT)
Received: by 10.49.71.243 with HTTP; Tue, 27 Aug 2013 09:29:22 -0700 (PDT)
In-Reply-To: <94409AF8-BDC6-4C35-B6E2-10EF6CD34107@netapp.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CD164.8080809@bell-labs.com> <94409AF8-BDC6-4C35-B6E2-10EF6CD34107@netapp.com>
Date: Tue, 27 Aug 2013 11:29:22 -0500
Message-ID: <CAHBDyN4DStBMd8uxFF6POxfatxnW0faAhtevBtaUL_JKJzwNdQ@mail.gmail.com>
Subject: Re: Allowing posting of CFPs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=001a11343d6021bdc204e4f060d2
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:29:40 -0000

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

That's good when there is the potential for a useful CFP from a member.  In
this particular case, a lot of WG chairs were letting the email through on
lists for which I do not believe it was at all relevant.  I agree with
Vijay's approach and your suggestion is a really good one for handling
member posting.  It's the non-member posting that I'm suggesting would be
better handled if all WG chairs would agree to scrutinize more closely
before letting it through.

Mary.




On Tue, Aug 27, 2013 at 11:19 AM, Eggert, Lars <lars@netapp.com> wrote:

> Hi,
>
> I have "Subject: .*(CFP|Call for)" in the "header_filter_rules" Option of
> my mailman lists if a "hold" action, so I can moderate which get through.
>
> Lars
>

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

<div dir=3D"ltr">That&#39;s good when there is the potential for a useful C=
FP from a member. =A0In this particular case, a lot of WG chairs were letti=
ng the email through on lists for which I do not believe it was at all rele=
vant. =A0I agree with Vijay&#39;s approach and your suggestion is a really =
good one for handling member posting. =A0It&#39;s the non-member posting th=
at I&#39;m suggesting would be better handled if all WG chairs would agree =
to scrutinize more closely before letting it through.=A0<div>
<br></div><div>Mary.=A0<br><div><br></div><div><br></div></div></div><div c=
lass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Aug 27, 201=
3 at 11:19 AM, Eggert, Lars <span dir=3D"ltr">&lt;<a href=3D"mailto:lars@ne=
tapp.com" target=3D"_blank">lars@netapp.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have &quot;Subject: .*(CFP|Call for)&quot; in the &quot;header_filter_rul=
es&quot; Option of my mailman lists if a &quot;hold&quot; action, so I can =
moderate which get through.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Lars<br>
</font></span></blockquote></div><br></div>

--001a11343d6021bdc204e4f060d2--

From tom.taylor.stds@gmail.com  Tue Aug 27 10:11:48 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6333D21E8093 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcFT6blNG2TI for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:11:48 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7EF6B21E8091 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:11:46 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i18so5823513oag.15 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=cYQy574Nki5oLNzsIE0w/86UBUp+Ds2stoS5P9MmU5A=; b=gyiidYDQMrLXh1XT7UCmHjgj4XUU2RM3CnDU3aJ3LSzY2zntlt3DgkcfRKguyoMJB0 YrUg44RAMgMgbGF3qUmHJPto9Ypdg+6LZe9xC0qixznY3ufczOijml/ySsse/MBnNVtM 6PruUM8dmIOYnBnfSbOTc57eQNc9Or1VcovRtAsRS7gTySY5zb3czjHTKAVh4MOWU6kt utQRPthaySx/gSCMIIFHfp1R12/saerDRYSskRiK2Uv0r8deYqixgIV3HDyTOwtECx8L 7weWfgJZE4Q0h3CmCkKb/wCu/P4SIpKYIFL24PTwxyWLLvmRnyrHZYSE2Pe6zSxcCJGv 3lgg==
X-Received: by 10.182.18.9 with SMTP id s9mr19861032obd.15.1377623505922; Tue, 27 Aug 2013 10:11:45 -0700 (PDT)
Received: from [192.168.1.68] (dsl-173-206-67-91.tor.primus.ca. [173.206.67.91]) by mx.google.com with ESMTPSA id ps5sm21362098oeb.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 10:11:45 -0700 (PDT)
Message-ID: <521CDDCF.2020908@gmail.com>
Date: Tue, 27 Aug 2013 13:11:43 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:11:48 -0000

For member-originated CFPs my policy was similar to Keith's. The vast 
majority of such postings to the AVTCore list are from outsiders, and in 
fact, from specific individuals who represent one particular 
organization that seems to be in the business of manufacturing holidays 
disguised as meetings. My criterion was always that any 
outside-originated CFP had to pass a strict test of relevance to the WG. 
Apparently my judgement even so was too loose, since there was a 
complaint and now I leave the decision to release announcements to the 
co-Chairs.

Tom Taylor

On 27/08/2013 11:48 AM, Mary Barnes wrote:
> Hi,
>
> Thus far I have received this CFP (International Conference on
> Cryptography ...)
> on just about every mailing list I am subscribed to. Personally, I
> consider this SPAM as it's not coming from a member of the community.  I
> think we should only be allowing these postings on a single list and
> that should be the IETF discussion. ...

From tom.taylor.stds@gmail.com  Tue Aug 27 10:22:02 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBF9D21E80C6 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkHFlvLAYmkj for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:22:02 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B8E4F21E80E5 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:22:01 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id eh20so5192853obb.29 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:21:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vXiV8QtgicbftTgWJpit2UnSNyX6BGtXnmSp2wGLo/Y=; b=APuGgLIq7byWHdvavCvi6UzEpOf4JAuzviApiR6mMD9ldxqDpiZflsVPjsFCVa3UtN QRu4MHeEOEMO0+WKMqsUIon6jISJMJecjNE6s9xYsH9yWGc7Ade/RxdMD+B6QCHcrMEb bASeL3QmywEV6dT7D++8E0onXBs6XmHUh+L8ylAZ9I7xtkTaVgPz5uZOk3llOEeqKeTO WNsNZc+nrFo0aNx4rsiMBG/1wuG55/V3dxhJb8OJcFSha/20x199XtckA3vswGOMW1LF HpbaF8BqEyqNw76CRGpCmqrhO4XkyVMTLH9XDV3lCazQNpHpaQi5/yKY0Lrz+YDa8fP2 rkmw==
X-Received: by 10.60.50.135 with SMTP id c7mr8057395oeo.41.1377624118806; Tue, 27 Aug 2013 10:21:58 -0700 (PDT)
Received: from [192.168.1.68] (dsl-173-206-67-91.tor.primus.ca. [173.206.67.91]) by mx.google.com with ESMTPSA id rl1sm21405494oeb.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 10:21:57 -0700 (PDT)
Message-ID: <521CE034.5060908@gmail.com>
Date: Tue, 27 Aug 2013 13:21:56 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Allowing posting of CFPs
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CCB80.3040006@bogus.com> <49ED2E7D-F5C8-4887-A530-B319BAE1376E@checkpoint.com> <CAHBDyN65WDn9653ZzR-X=W30j4U_kwxnhL5+A0WZy1Hz+Z1r+A@mail.gmail.com>
In-Reply-To: <CAHBDyN65WDn9653ZzR-X=W30j4U_kwxnhL5+A0WZy1Hz+Z1r+A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:22:03 -0000

One thought I meant to expand on in my previous post. These days there 
is apparently a problem with bogus conferences and journals, where 
authors unexpectedly get a big bill for the privilege of being 
published. I'm not sure how much checking of reputation we can or should 
do before allowing a CFP through.

Tom Taylor

From Ted.Lemon@nominum.com  Tue Aug 27 10:25:19 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8AC411E8178 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 RLA7sC6B5v42 for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:25:13 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3F16B11E81CD for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:25:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUhzg+NSS77rrhCo7RuE2k3cF7jmqGk6V@postini.com; Tue, 27 Aug 2013 10:25:13 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A1BFC1B82D4 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:25:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 88EC019006C; Tue, 27 Aug 2013 10:25:12 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 27 Aug 2013 10:25:12 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Allowing posting of CFPs
Thread-Topic: Allowing posting of CFPs
Thread-Index: AQHOozzdq9pELzw2N0m1qZVXTpJgRpmpw6WA
Date: Tue, 27 Aug 2013 17:25:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077526751A@mbx-01.win.nominum.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A57A95EAE590C244A2B360749BEBFD3D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:25:20 -0000

On Aug 27, 2013, at 11:48 AM, Mary Barnes <mary.ietf.barnes@gmail.com> wrot=
e:
> Personally, I consider this SPAM as it's not coming from a member of the =
community.=20

You are correct=97it is spam.   If they want to announce on IETF mailing li=
sts, they should be talking to the IETF about it, not just doing it.


From sm@elandsys.com  Tue Aug 27 10:28:44 2013
Return-Path: <sm@elandsys.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DDD011E81CD for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UlQWwAKZnwz for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:42 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBF111E81BB for <wgchairs@ietf.org>; Tue, 27 Aug 2013 10:28:42 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.183]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7RHS6NL017540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 10:28:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377624511; bh=b47YVPAQKfrFar0U2e0P6P+C5UI7Z4jFQ4ZhOaokCN8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hsNwfR7hHdMCVRU3vzWrEm6NeZG+2BnAOrfYk08xwiCdqf2lV42qYDXHjOrUbTvg5 /1D0Vt4HovhVNQGE3HH/B7M3WTG8mfSFLducbGRqHxtc5coEKnsLiFLTmYFJZdjke/ QVcw+cMuYXuRluA1ulwBWPUhiK55dbePQgah3mGI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377624511; i=@elandsys.com; bh=b47YVPAQKfrFar0U2e0P6P+C5UI7Z4jFQ4ZhOaokCN8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WcbkJra2pEEdaywJjUKdqzdA0vN0FFeydB41sFZiJ+yGbj6NJlCf6RfAdZIk1SaLj uLwT6WrM+HXzvWSk+fQo6/GbYmurtcY/cHhFq54AeI+qjf/dpAq1Epq0rF1jFPCkWY o16BHwTYB479n4BBwgvIRpvE6QvLfgXx25uYprTo=
Message-Id: <6.2.5.6.2.20130827101457.0d7b1cc8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Aug 2013 10:25:33 -0700
To: Tom Taylor <tom.taylor.stds@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Allowing posting of CFPs
In-Reply-To: <521CDDCF.2020908@gmail.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <521CDDCF.2020908@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:28:44 -0000

Hi Tim,
At 10:11 27-08-2013, Tom Taylor wrote:
>For member-originated CFPs my policy was similar to Keith's. The 
>vast majority of such postings to the AVTCore list are from 
>outsiders, and in fact, from specific individuals who represent one 
>particular organization that seems to be in the business of 
>manufacturing holidays disguised as meetings. My criterion was 
>always that any outside-originated CFP had to pass a strict test of 
>relevance to the WG. Apparently my judgement even so was too loose, 
>since there was a complaint and now I leave the decision to release 
>announcements to the co-Chairs.

It's easier to reject, wait for the complaint and then quote the relevant BCP.

Regards,
S. Moonesamy 


From jouni.nospam@gmail.com  Tue Aug 27 13:35:04 2013
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2DC721F9B0E for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 13:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level: 
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=0.171,  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 Bi1ia15zMUly for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 13:35:04 -0700 (PDT)
Received: from mail-ea0-x233.google.com (mail-ea0-x233.google.com [IPv6:2a00:1450:4013:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id E319821F9B0D for <wgchairs@ietf.org>; Tue, 27 Aug 2013 13:35:03 -0700 (PDT)
Received: by mail-ea0-f179.google.com with SMTP id b10so2527782eae.10 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 13:35:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7dBd9Jz01dEo6Y/tb8fRthDY9xT+Sylko7m57q7PITk=; b=sPaOVHjRa4S67C5qHcawcpwtw4QEv3rXUn+Cmmya/HWm7PKiyT5e6z6j+Pp2uOAQ// LuZ8xXrxCkWN8p8qneWsr5t5avvpi2ASFPqr8siuVy6jlmYmIkrxIrg7ISfuGX6ugWev FJXWZcDG5sAOFb5T3+/lNgcSsT0ok39Lw4kaaf1WcqQO53wspQYDzJi4eGLHiRfGEvKv c8kHua/DBwSesPxw1XOas0HSeJr6JJOuJnT19ZaD9DQXVFXLZUE2Zp+dtqvFCuzcGBrG fyBUd76SG5D2DusLn/PKU1ecqHZvSlMwmMFho1YEBjrK4qHIfKdJ66grlHHxlKf3q5Et bY1Q==
X-Received: by 10.14.177.199 with SMTP id d47mr36852647eem.14.1377635703046; Tue, 27 Aug 2013 13:35:03 -0700 (PDT)
Received: from ?IPv6:2001:1bc8:101:f101:fc5e:23e4:7126:ddab? ([2001:1bc8:101:f101:fc5e:23e4:7126:ddab]) by mx.google.com with ESMTPSA id r48sm31800640eev.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 13:35:00 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Allowing posting of CFPs
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
Date: Tue, 27 Aug 2013 23:34:59 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D972DE5B-59D6-4EBD-A029-AF71447368F8@gmail.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 20:35:04 -0000

I discard/reject unsolicited CFPs routinely when moderating my lists.  I =
could do an exceptions if the CFP authors contact chairs in advance and =
the CFP really fits into the scope of the WG.

- Jouni


On Aug 27, 2013, at 6:48 PM, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

> Hi,
>=20
> Thus far I have received this CFP (International Conference on =
Cryptography ...)
> on just about every mailing list I am subscribed to. Personally, I =
consider this SPAM as it's not coming from a member of the community.  I =
think we should only be allowing these postings on a single list and =
that should be the IETF discussion.  I will make a confession that as a =
moderator of many mailing lists, if I've gotten to these messages before =
other moderators, I've NOT been allowing them through except on the =
architecture discuss mailing, which is fairly general.   It's junk email =
IMHO for most of the RAI area mailing lists.  I can see some of the SEC =
lists possibly being relevant although I would think a single posting to =
an area wide mailing is all that's appropriate.=20
>=20
> I'd be interested to know how others feel. =20
>=20
> Mary
> WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing =
lists.


From mconner@amsl.com  Tue Aug 27 15:08:24 2013
Return-Path: <mconner@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A8B11E83BA for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 15:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dBrbB9ZG3t1t for <wgchairs@ietfa.amsl.com>; Tue, 27 Aug 2013 15:07:50 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 2E20A11E83A9 for <wgchairs@ietf.org>; Tue, 27 Aug 2013 15:07:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 39672A609D; Tue, 27 Aug 2013 15:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FwUlyZeMeuUs; Tue, 27 Aug 2013 15:07:12 -0700 (PDT)
Received: from [64.170.98.144] (unknown [64.170.98.144]) by c9a.amsl.com (Postfix) with ESMTPSA id 18D50A609C; Tue, 27 Aug 2013 15:07:12 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_56B8C75C-189D-4D43-A9A0-1039867528F6"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Request for IETF WG and BoF Session Minutes
From: Maddy Conner <mconner@amsl.com>
In-Reply-To: <A3377244-E0EE-4288-8BF9-9EF7B557D2D7@amsl.com>
Date: Tue, 27 Aug 2013 15:09:15 -0700
Message-Id: <06209F81-2E6F-42AD-BAC4-A28E0F72273A@amsl.com>
References: <A3377244-E0EE-4288-8BF9-9EF7B557D2D7@amsl.com>
To: wgchairs@ietf.org
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Tue, 27 Aug 2013 15:09:51 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 22:08:24 -0000

--Apple-Mail=_56B8C75C-189D-4D43-A9A0-1039867528F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

Just a reminder that I am still waiting on minutes from many of you. =
Again, the cutoff for submissions is this Friday, August 30th, 2013, and =
correction submissions cutoff is Wednesday, September 18th, 2013.  =
Please upload meeting minutes, as well as any presentations from your =
sessions, at your earliest convenience using the Meeting Materials =
Manager found here: https://pub.ietf.org/proceedings/.  Alternatively, =
you are welcome to send them to proceedings@ietf.org or mconner@amsl.com =
for manual posting.

Groups I still need minutes from are:

Application Area:
	CORE
	WEBSEC
=20
General Area:
	IPRBIS (BoF)

Internet Area:
	6TSCH (BoF)
	DNSSDEXT (BoF)
	HOMENET
	NETEXT
	PCP
	TICTOC
	TRILL

Operations & Management Area:
	GROW
	MBONED
	OPSEC
	V6OPS

Real-Time Applications & Infrastructure Area:
	INSIPID
	MMUSIC

Routing Area:
	FORCES
	MPLS
	PCE

Security Area:
	SAAG
	TLS

Transport Area:
	TSVAREA

IRTF:
	CFRG (No agenda Received)
	DTNRG
	NWCRG

https://datatracker.ietf.org/meeting/87/materials.html


Maddy Conner
IETF Registrar
48377 Fremont Blvd, Ste. 117
Fremont, CA 94538

Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com


On Aug 22, 2013, at 12:43 PM, Maddy Conner <mconner@amsl.com> wrote:

> Dear WG Chairs and BOF Chairs,
> =20
> I am in the process of compiling the proceedings for IETF 87 and we =
are still missing meeting minutes from various sessions. The cutoff for =
submissions is Friday, August 30th, 2013, and correction submissions =
cutoff is Wednesday, September 18th, 2013.  Please upload meeting =
minutes, as well as any presentations from your sessions, at your =
earliest convenience using the Meeting Materials Manager found here: =
https://pub.ietf.org/proceedings/.  Alternatively, you are welcome to =
send them to proceedings@ietf.org or mconner@amsl.com for manual =
posting.
>=20
> Groups I still need minutes from are:
>=20
> Application Area:
> 	CORE
> 	WEBSEC
> =20
> General Area:
> 	IPRBIS (BoF)
>=20
> Internet Area:
> 	6MAN
> 	6TSCH (BoF)
> 	DNSSDEXT (BoF)
> 	HOMENET
> 	INTAREA
> 	MULTIMOB
> 	NETEXT
> 	PCP
> 	TICTOC
> 	TRILL
>=20
> Operations & Management Area:
> 	GROW
> 	MBONED
> 	OPSEC
> 	V6OPS
>=20
> Real-Time Applications & Infrastructure Area:
> 	AVTEXT
> 	INSIPID
> 	MMUSIC
> 	SIPREC
>=20
> Routing Area:
> 	FORCES
> 	IDR
> 	KARP
> 	MANET
> 	MPLS
> 	PCE
> 	SIDR
>=20
> Security Area:
> 	DANE
> 	SAAG
> 	TLS
>=20
> Transport Area:
> 	CONEX
> 	TSVAREA
>=20
> IRTF:
> 	CFRG (No agenda Received)
> 	DTNRG
> 	ICCRG
> 	NWCRG
>=20
> https://datatracker.ietf.org/meeting/87/materials.html
>=20
>=20
>=20
> Maddy Conner
> IETF Registrar
> 48377 Fremont Blvd, Ste. 117
> Fremont, CA 94538
>=20
> Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com


--Apple-Mail=_56B8C75C-189D-4D43-A9A0-1039867528F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
all,<div><br></div><div>Just a reminder that I am still waiting on =
minutes from many of you. Again, the&nbsp;cutoff for submissions =
is&nbsp;<b>this&nbsp;Friday, August 30th, 2013</b>, and correction =
submissions cutoff is&nbsp;<b>Wednesday, September 18th, 2013</b>. =
&nbsp;Please upload meeting minutes, as well as any presentations from =
your sessions, at your earliest convenience using the Meeting Materials =
Manager found here:&nbsp;<a =
href=3D"https://pub.ietf.org/proceedings/">https://pub.ietf.org/proceeding=
s/</a>. &nbsp;Alternatively, you are welcome to send them to&nbsp;<a =
href=3D"mailto:proceedings@ietf.org">proceedings@ietf.org</a>&nbsp;or&nbsp=
;<a href=3D"mailto:mconner@amsl.com">mconner@amsl.com</a>&nbsp;for =
manual posting.</div><div><br></div><div>Groups I still need minutes =
from are:</div><div><br></div><div><div>Application =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>CORE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	=
</span>WEBSEC</div><div>&nbsp;</div><div>General Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>IPRBIS =
(BoF)</div><div><br></div><div>Internet Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>6TSCH =
(BoF)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span><span style=3D"font-family: arial, helvetica, clean, =
sans-serif; font-size: 13px; line-height: 16px; =
">DNSSDEXT&nbsp;(BoF)</span></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>HOMENET</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>NETEXT</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>PCP</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>TICTOC</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	=
</span>TRILL</div><div><br></div><div>Operations &amp; Management =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>GROW</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>MBONED</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>OPSEC</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	=
</span>V6OPS</div><div><br></div><div>Real-Time Applications &amp; =
Infrastructure Area:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>INSIPID</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>MMUSIC</div><div><br></div><div>Routing Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>FORCES</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>MPLS</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>PCE</div><div><br></div><div>Security Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>SAAG</div><div><span class=3D"Apple-tab-span" style=3D"white-space:=
 pre; ">	</span>TLS</div><div><br></div><div>Transport =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>TSVAREA</div><div><br></div><div>IRTF:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>CFRG (No =
agenda Received)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>DTNRG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>NWCRG</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/meeting/87/materials.html">https://da=
tatracker.ietf.org/meeting/87/materials.html</a></div><div><br></div><div>=
<br></div><div>Maddy Conner</div><div>IETF Registrar</div><div>48377 =
Fremont Blvd, Ste. 117</div><div>Fremont, CA =
94538</div><div><br></div><div>Association Management Solutions =
(AMS)</div><div>Forum Management, Meeting and Event =
Planning</div><div><a =
href=3D"http://www.amsl.com/">www.amsl.com</a></div><div><br></div><div><b=
r></div><div><div>On Aug 22, 2013, at 12:43 PM, Maddy Conner &lt;<a =
href=3D"mailto:mconner@amsl.com">mconner@amsl.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Dear WG Chairs and BOF Chairs,</div><div>&nbsp;</div><div>I am in =
the process of compiling the proceedings for IETF 87 and we are still =
missing meeting minutes from various sessions. The cutoff for =
submissions is <b>Friday, August 30th, 2013</b>, and correction =
submissions cutoff is <b>Wednesday, September 18th, 2013</b>. =
&nbsp;Please upload meeting minutes, as well as any presentations from =
your sessions, at your earliest convenience using the Meeting Materials =
Manager found here: <a =
href=3D"https://pub.ietf.org/proceedings/">https://pub.ietf.org/proceeding=
s/</a>. &nbsp;Alternatively, you are welcome to send them to <a =
href=3D"mailto:proceedings@ietf.org">proceedings@ietf.org</a> or <a =
href=3D"mailto:mconner@amsl.com">mconner@amsl.com</a> for manual =
posting.</div><div><br></div><div>Groups I still need minutes from =
are:</div><div><br></div><div>Application Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>CORE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>WEBSEC</div><div>&nbsp;</div><div>General Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>IPRBIS =
(BoF)</div><div><br></div><div>Internet Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>6MAN</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>6TSCH (BoF)</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
style=3D"font-family: arial, helvetica, clean, sans-serif; font-size: =
13px; line-height: 16px; ">DNSSDEXT&nbsp;(BoF)</span></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>HOMENET</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>INTAREA</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>MULTIMOB</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>NETEXT</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>PCP</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>TICTOC</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>TRILL</div><div><br></div><div>Operations &amp; Management =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>GROW</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MBONED</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>OPSEC</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>V6OPS</div><div><br></div><div>Real-Time Applications &amp; =
Infrastructure Area:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>AVTEXT</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>INSIPID</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MMUSIC</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>SIPREC</div><div><br></div><div>Routing Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>FORCES</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>IDR</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>KARP</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>MANET</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>MPLS</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>PCE</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>SIDR</div><div><br></div><div>Security Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>DANE</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>SAAG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>TLS</div><div><br></div><div>Transport Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>CONEX</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>TSVAREA</div><div><br></div><div>IRTF:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>CFRG (No =
agenda Received)</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>DTNRG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>ICCRG</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>NWCRG</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/meeting/87/materials.html">https://da=
tatracker.ietf.org/meeting/87/materials.html</a></div><div><br></div><div>=
<br></div><div><br></div><div>Maddy Conner</div><div>IETF =
Registrar</div><div>48377 Fremont Blvd, Ste. 117</div><div>Fremont, CA =
94538</div><div><br></div><div>Association Management Solutions =
(AMS)</div><div>Forum Management, Meeting and Event =
Planning</div><div><a =
href=3D"http://www.amsl.com/">www.amsl.com</a></div></div></blockquote></d=
iv><br></div></body></html>=

--Apple-Mail=_56B8C75C-189D-4D43-A9A0-1039867528F6--

From dromasca@avaya.com  Wed Aug 28 03:28:33 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9656611E817B for <wgchairs@ietfa.amsl.com>; Wed, 28 Aug 2013 03:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.307
X-Spam-Level: 
X-Spam-Status: No, score=-103.307 tagged_above=-999 required=5 tests=[AWL=0.292, 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 VkJMMsVbRu7i for <wgchairs@ietfa.amsl.com>; Wed, 28 Aug 2013 03:28:27 -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 D77AE11E8183 for <wgchairs@ietf.org>; Wed, 28 Aug 2013 03:28:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAAjQHVKHCzI1/2dsb2JhbABagmYhgQbAKYEiFnSCJAEBAQEDEiguBgsMBAIBCA0EAQMBAQEKFAkHIREUAwYIAgQBDQUIDA6HTQMPAZwAkwgNiVMXjHmBIoEYMQcGgxZ9A5YHAYg6hWOFLYMggXE5
X-IronPort-AV: E=Sophos;i="4.89,975,1367985600"; d="scan'208";a="21594553"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 28 Aug 2013 06:28:25 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 28 Aug 2013 06:20:54 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.03.0146.000; Wed, 28 Aug 2013 12:28:22 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: RE: Allowing posting of CFPs
Thread-Topic: Allowing posting of CFPs
Thread-Index: AQHOozzgRIp61Aj5YE+Rl670BcB13pmpxmCAgAClBqA=
Date: Wed, 28 Aug 2013 10:28:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA128B9A62@AZ-FFEXMB04.global.avaya.com>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <D972DE5B-59D6-4EBD-A029-AF71447368F8@gmail.com>
In-Reply-To: <D972DE5B-59D6-4EBD-A029-AF71447368F8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 10:28:33 -0000

Same as Jouni. If the authors of the CFP contact me in advance, or if the s=
ender is a contributor to the list AND I am convinced that the event is rel=
ated to the WG charter, then I accept the message. Else I discard it.=20

Regards,

Dan




> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Jouni Korhonen
> Sent: Tuesday, August 27, 2013 11:35 PM
> To: Mary Barnes
> Cc: IETF WG Chairs
> Subject: Re: Allowing posting of CFPs
>=20
>=20
> I discard/reject unsolicited CFPs routinely when moderating my lists.  I
> could do an exceptions if the CFP authors contact chairs in advance and
> the CFP really fits into the scope of the WG.
>=20
> - Jouni
>=20
>=20
> On Aug 27, 2013, at 6:48 PM, Mary Barnes <mary.ietf.barnes@gmail.com>
> wrote:
>=20
> > Hi,
> >
> > Thus far I have received this CFP (International Conference on
> Cryptography ...)
> > on just about every mailing list I am subscribed to. Personally, I
> consider this SPAM as it's not coming from a member of the community.  I
> think we should only be allowing these postings on a single list and
> that should be the IETF discussion.  I will make a confession that as a
> moderator of many mailing lists, if I've gotten to these messages before
> other moderators, I've NOT been allowing them through except on the
> architecture discuss mailing, which is fairly general.   It's junk email
> IMHO for most of the RAI area mailing lists.  I can see some of the SEC
> lists possibly being relevant although I would think a single posting to
> an area wide mailing is all that's appropriate.
> >
> > I'd be interested to know how others feel.
> >
> > Mary
> > WG chair for CLUE and DISPATCH and a couple dozen IAB related mailing
> lists.


From glenams@gmail.com  Thu Aug 29 16:39:56 2013
Return-Path: <glenams@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 308F611E81A0 for <wgchairs@ietfa.amsl.com>; Thu, 29 Aug 2013 16:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oklu-14IfKWm for <wgchairs@ietfa.amsl.com>; Thu, 29 Aug 2013 16:39:55 -0700 (PDT)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 82AEE11E80D2 for <wgchairs@ietf.org>; Thu, 29 Aug 2013 16:39:55 -0700 (PDT)
Received: by mail-vb0-f50.google.com with SMTP id x14so854581vbb.9 for <wgchairs@ietf.org>; Thu, 29 Aug 2013 16:39:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:message-id:subject:from:to :content-type; bh=XRB0garYRDVP177vAifPSY9/vebwMHqFCUr0Z6iMnIA=; b=rdLasJhJ+WXvXpylLJ7z23EjT4ztYFgd8GYe8ECiRln8Vrm2fs1vkD/i0hyu1Vk3Oc DwFrkSQYuhlTUi68oPGadz0jWTUjHn6+v7KswP90hJp2JQRaFPpcJAL0xQaTCR5/b8Fk xkYGGc52HcrPx7oZbxPSb+GEa4dGse0Nmc0kOdX2554tPwx2jBRc5B62GH3tkhcthpS3 GZ6EiCRNd7eGiLaJqBbR2AztrmRWvqAxkl3lQiGt8AR23/4VzWO4xh7siOY5N1c/pYwY 3bemgqjjY3osgKR5F99s8gqpwZRoDNqo3YjLTLPXlbcf943HLwrG1pTHrFuSUrv+ZJ5/ SnqA==
MIME-Version: 1.0
X-Received: by 10.52.249.50 with SMTP id yr18mr3442836vdc.25.1377819592933; Thu, 29 Aug 2013 16:39:52 -0700 (PDT)
Sender: glenams@gmail.com
Received: by 10.59.1.132 with HTTP; Thu, 29 Aug 2013 16:39:52 -0700 (PDT)
Date: Thu, 29 Aug 2013 16:39:52 -0700
X-Google-Sender-Auth: ejOMVOO-b7zsM3HCFX4VMvMAmdU
Message-ID: <CABL0ig6m4ghrLt0fv5BEwz13YHkNo6EE49TnErHS_xPgVsyYSg@mail.gmail.com>
Subject: Mailman service interruption yesterday
From: Glen <glen@amsl.com>
To: Glen Barney <glen@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 29 Aug 2013 16:43:48 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: glen@amsl.com
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 23:39:56 -0000

Greetings:

Yesterday the IETF experienced a 5.5-hour service outage on its
Mailman list processor.

In this failure, Mailman started dropping messages, rather than
bouncing them, as it should have done.  This was problematic, because
there was not an immediate indication that something was wrong, nor
was there any automated or manual way that this outage could have been
detected quickly.  Fortunately, Pete Resnick, noted that several of
his emails were not being delivered, and notified the emergency alert
server at that time.

Following Pete's alert, Steve Young, the IETF system administrator,
logged in to the system, and was able to analyze the problem and
effect resolution.  He was able to restore service to Mailman and
verify that mail was now flowing directly.

Steve reported that the cause of the outage seems to have been a
permissions setting on a directory that was incorrect.  We are still
investigating whether the broken setting was due to software changes,
or a filesystem problem, and will continue to take steps to ensure
that the current system remains healthy and operational.

Because of the nature of this outage, Steve was not, unfortunately,
able to recover the lost email messages themselves.  But he did spend
several hours processing the mail logs during the outage period, and
sent notifications to all the senders that he was able to locate in
the log during the outage period, asking those individuals to resend
their email messages.  While not a foolproof response, this was a good
course of action to take in an attempt to recover the lost messages.

Service has been up and running continuously since 2100PDT yesterday,
and no further outages have been observed.  No other services were
impacted or interrupted during this time.

Although not specifically mentioned in the release notes, we attribute
this to the older version of Mailman currently in use.  We note that
we are deploying new IETF servers with the latest versions of Linux
and Mailman (and other support software) to our colocation facilities
next week, and hope to migrate the IETF to those servers soon.  This
should increase reliability and - we hope! - resolve whatever bug may
have caused Mailman to drop these emails.

In addition it has come to my attention that no notification was sent
out generally following this outage.  I was out sick today, at a
string of medical appointments, but I failed to make clear to AMS that
someone else would need to send a notification in my absence.  I
apologize for the delay, therefore, in getting this notification sent
out.

Thank you for your patience.  As always, if there are any questions,
please let me know.

Glen Barney
IT Director
AMS (IETF Secretariat)

From jari.arkko@piuha.net  Fri Aug 30 05:03:17 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA48C21E8093 for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 05:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2seT-EIErwAO for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 05:03:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB8B21E80C1 for <wgchairs@ietf.org>; Fri, 30 Aug 2013 05:03:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C7CAA2CC48; Fri, 30 Aug 2013 15:03:08 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXoY_ZVtjBS6; Fri, 30 Aug 2013 15:03:08 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 352D32CC46; Fri, 30 Aug 2013 15:03:08 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Allowing posting of CFPs
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <D972DE5B-59D6-4EBD-A029-AF71447368F8@gmail.com>
Date: Fri, 30 Aug 2013 15:03:08 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <32D55301-71F5-41D0-9428-9F6DD596C1BA@piuha.net>
References: <CAHBDyN5E9_4FHwXTzUKW_Ez3cLR87V-F=n5HDNGXDBtB+rDVFw@mail.gmail.com> <D972DE5B-59D6-4EBD-A029-AF71447368F8@gmail.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:03:18 -0000

>=20
> I discard/reject unsolicited CFPs routinely when moderating my lists.  =
I could do an exceptions if the CFP authors contact chairs in advance =
and the CFP really fits into the scope of the WG.

I think this is a reasonable approach.

Jari


From keith.drage@alcatel-lucent.com  Fri Aug 30 05:38:14 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 123A221E80D6 for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 05:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.502
X-Spam-Level: 
X-Spam-Status: No, score=-110.502 tagged_above=-999 required=5 tests=[AWL=0.097, 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 C4k4DZVDxMwc for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 05:37:55 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 617FC21F9C42 for <wgchairs@ietf.org>; Fri, 30 Aug 2013 05:25:23 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r7UCPAPX018021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <wgchairs@ietf.org>; Fri, 30 Aug 2013 07:25:12 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r7UCPAIn030404 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <wgchairs@ietf.org>; Fri, 30 Aug 2013 14:25:10 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 30 Aug 2013 14:25:10 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Subject: Mail archive links
Thread-Topic: Mail archive links
Thread-Index: Ac6le/eF/QIFEbjwTWSFXerh9Ps+Ng==
Date: Fri, 30 Aug 2013 12:25:09 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B08B723@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 12:38:20 -0000

I recently went looking for the gen-art mail list archive and could not fin=
d any page that posted a link.

The place I did expect to find it was on the non-working group mailing list=
 page here

http://www.ietf.org/list/nonwg.html=20

Could I suggest we add a new column on this page with the archive links, in=
 cases where the archive is available.

(I did eventually locate the archive by working out what the archive addres=
s should be)

Regards

Keith

From david.black@emc.com  Fri Aug 30 07:41:52 2013
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16BE21F9E4D for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 07:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.749
X-Spam-Level: 
X-Spam-Status: No, score=-102.749 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZfDXBUVJ78x for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 07:41:45 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id A02C821F9E28 for <wgchairs@ietf.org>; Fri, 30 Aug 2013 07:41:45 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r7UEfIJ8020145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2013 10:41:21 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com r7UEfIJ8020145
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1377873686; bh=o0RYilqDpZMQPL01KW49iZ0NHjs=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=lL0sLPwFT/0KfHmoIXFRfeZ6iPWbnvQ26a8G3biYXqVbuzwh/FTDY/niyez4LUkQM 1gTdq67jtVsQOdL58AwiszaenQejL9Y7f3OTKLNgrw9emmPwQacuZ2QoYCUwHSub67 O0K8/44zsUsLCejYino8kjDMA/yCIQEmRlGA5Gwk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com r7UEfIJ8020145
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd55.lss.emc.com (RSA Interceptor); Fri, 30 Aug 2013 10:41:05 -0400
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id r7UEf3Cj000547 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 Aug 2013 10:41:03 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub22.corp.emc.com ([128.222.70.134]) with mapi; Fri, 30 Aug 2013 10:41:03 -0400
From: "Black, David" <david.black@emc.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, IETF WG Chairs <wgchairs@ietf.org>
Date: Fri, 30 Aug 2013 10:41:01 -0400
Subject: RE: Mail archive links
Thread-Topic: Mail archive links
Thread-Index: Ac6le/eF/QIFEbjwTWSFXerh9Ps+NgAEpMMg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C6759BE@MX15A.corp.emc.com>
References: <949EF20990823C4C85C18D59AA11AD8B08B723@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B08B723@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-EMM-GWVC: 1
X-EMM-McAfeeVC: 1
X-RSA-Classifications: DLM_1, public
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 14:41:53 -0000

> The place I did expect to find it was on the non-working group mailing li=
st
> page here
>=20
> http://www.ietf.org/list/nonwg.html

Click on Gen-Art, to get to listinfo page: https://www.ietf.org/mailman/lis=
tinfo/gen-art

There's an archive link near the top of that page.

Thanks,
--David


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf
> Of DRAGE, Keith (Keith)
> Sent: Friday, August 30, 2013 8:25 AM
> To: IETF WG Chairs
> Subject: Mail archive links
>=20
> I recently went looking for the gen-art mail list archive and could not f=
ind
> any page that posted a link.
>=20
> The place I did expect to find it was on the non-working group mailing li=
st
> page here
>=20
> http://www.ietf.org/list/nonwg.html
>=20
> Could I suggest we add a new column on this page with the archive links, =
in
> cases where the archive is available.
>=20
> (I did eventually locate the archive by working out what the archive addr=
ess
> should be)
>=20
> Regards
>=20
> Keith


From keith.drage@alcatel-lucent.com  Fri Aug 30 16:25:46 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D19821F9C12 for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 16:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.509
X-Spam-Level: 
X-Spam-Status: No, score=-110.509 tagged_above=-999 required=5 tests=[AWL=0.090, 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 s-fG-QnXUWuN for <wgchairs@ietfa.amsl.com>; Fri, 30 Aug 2013 16:25:41 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id CDF4F21F9BB6 for <wgchairs@ietf.org>; Fri, 30 Aug 2013 16:25:40 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r7UNPaFs006973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 30 Aug 2013 18:25:38 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id r7UNPY2v021979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 31 Aug 2013 01:25:35 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Sat, 31 Aug 2013 01:25:34 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Black, David" <david.black@emc.com>, IETF WG Chairs <wgchairs@ietf.org>
Subject: RE: Mail archive links
Thread-Topic: Mail archive links
Thread-Index: Ac6le/eF/QIFEbjwTWSFXerh9Ps+NgAEpMMgABIU3lA=
Date: Fri, 30 Aug 2013 23:25:34 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B08CAA7@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B08B723@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8D3D17ACE214DC429325B2B98F3AE7129C6759BE@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C6759BE@MX15A.corp.emc.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 23:25:46 -0000

Ah...

I got to the top of that page which is the mailing list subscription form, =
knew I was not allowed to subscribe to gen-art because it is a closed list,=
 and therefore read no further.

Keith

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: 30 August 2013 15:41
> To: DRAGE, Keith (Keith); IETF WG Chairs
> Subject: RE: Mail archive links
>=20
> > The place I did expect to find it was on the non-working group mailing
> list
> > page here
> >
> > http://www.ietf.org/list/nonwg.html
>=20
> Click on Gen-Art, to get to listinfo page:
> https://www.ietf.org/mailman/listinfo/gen-art
>=20
> There's an archive link near the top of that page.
>=20
> Thanks,
> --David
>=20
>=20
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf
> > Of DRAGE, Keith (Keith)
> > Sent: Friday, August 30, 2013 8:25 AM
> > To: IETF WG Chairs
> > Subject: Mail archive links
> >
> > I recently went looking for the gen-art mail list archive and could not
> find
> > any page that posted a link.
> >
> > The place I did expect to find it was on the non-working group mailing
> list
> > page here
> >
> > http://www.ietf.org/list/nonwg.html
> >
> > Could I suggest we add a new column on this page with the archive links=
,
> in
> > cases where the archive is available.
> >
> > (I did eventually locate the archive by working out what the archive
> address
> > should be)
> >
> > Regards
> >
> > Keith

