
From Martin.Stiemerling@neclab.eu  Mon Jul  1 04:06:07 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 A810921F9C8C; Mon,  1 Jul 2013 04:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=0.900, 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 L15BFakfTGuL; Mon,  1 Jul 2013 04:06:03 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8042821F9C2A; Mon,  1 Jul 2013 04:06:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 70BF8104849; Mon,  1 Jul 2013 13:05:35 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZVEaFwVKq36; Mon,  1 Jul 2013 13:05:35 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 535E8101FFC; Mon,  1 Jul 2013 13:05:20 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 1 Jul 2013 13:05:47 +0200
Message-ID: <51D1628B.9040605@neclab.eu>
Date: Mon, 1 Jul 2013 13:05:47 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: IETF 87 Preliminary Agenda
References: <20130627215038.17941.35680.idtracker@ietfa.amsl.com> <40770153-985D-4282-AE41-6EFB56BFC86F@mnot.net>
In-Reply-To: <40770153-985D-4282-AE41-6EFB56BFC86F@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 01 Jul 2013 11:06:07 -0000

Hi Mark,

TSVWG has two slots and there is a second 1 hour slot on Monday 1510 to 
1610. However, this collides with websec, or would this slot work?

   Martin



On 06/28/2013 01:26 AM, Mark Nottingham wrote:
> The clash between Transport WG and Apps WG on Monday AM is extremely
> unfortunate; I suspect there's going to be a LOT of overlap in
> interest between them in this meeting.
>
>
> On 28/06/2013, at 7:50 AM, IETF Agenda <agenda@ietf.org> wrote:
>
>>
>> Hello Everyone,
>>
>> The preliminary agenda for IETF 87 is available for viewing.
>> Please note the cut-off date for requests to reschedule Working
>> Group, IRTF, and BoF meetings is July 1st, 2013.  The final agenda
>> will be published on July 5th, 2013.
>>
>> This agenda is extremely full and changes will be difficult to
>> make.  Please take that into consideration before requesting any
>> changes.
>>
>> https://datatracker.ietf.org/meeting/87/agenda.html
>> https://datatracker.ietf.org/meeting/87/agenda.txt
>>
>> Thank you!
>>
>> Stephanie McCammon
>
> -- Mark Nottingham   http://www.mnot.net/
>
>
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014



From dwing@cisco.com  Mon Jul  1 11:10:31 2013
Return-Path: <dwing@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 65F0B21F9A48; Mon,  1 Jul 2013 11:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.414
X-Spam-Level: 
X-Spam-Status: No, score=-110.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozFys7UNPIhw; Mon,  1 Jul 2013 11:10:26 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9B321F9A4E; Mon,  1 Jul 2013 11:10:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=457; q=dns/txt; s=iport; t=1372702226; x=1373911826; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=3kDPQiv95Hii6tFRX0/20QH31KqSnT3rKb9qTs/mGrk=; b=cLRNEcbqC4LXfOI4YaJ3jq+wJoA2ZnMyL/AgLUqhl1xg/HHMHU6yvddQ +e6F6qKzqyS/7cWdNZkVOel5Uzklvm9oUXZvjaWJupXOuGbVl7u5G/XBW eUWqiA1lSXwZpK2TKDKf4dFL52ZFRklyUM7795WXgk9QzygVUcMKkICJc 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJvE0VGrRDoH/2dsb2JhbABagwnAHIEAFnSCZD+BP4ggvDmPXoMLYwOJI44lkUWDMRw
X-IronPort-AV: E=Sophos;i="4.87,975,1363132800"; d="scan'208";a="82360857"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 01 Jul 2013 18:10:25 +0000
Received: from sjc-vpn2-667.cisco.com (sjc-vpn2-667.cisco.com [10.21.114.155]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r61IAOuS022912; Mon, 1 Jul 2013 18:10:24 GMT
From: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: BEHAVE and DNSSDEXT conflict
Date: Mon, 1 Jul 2013 11:10:22 -0700
Message-Id: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com>
To: wgchairs@ietf.org, agenda@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: "Behave Chairs \(behave-chairs@tools.ietf.org\)" <behave-chairs@tools.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, 01 Jul 2013 18:10:31 -0000

The BEHAVE WG and DNSSDEXT BoF are both scheduled for Friday and have =
significant overlap of interested participants, as BEHAVE deals with =
NATs (such as home NATs) and DNSSDEXT deals with naming (such as on home =
networks).  I know both BEHAVE chairs would like to attend DNSSDEXT, and =
I expect some BEHAVE participants would like to attend DNSSDEXT as well.

Could we resolve that conflict, dropping BEHAVE to one hour if =
necessary?

-d


From gsalguei@cisco.com  Mon Jul  1 11:42:02 2013
Return-Path: <gsalguei@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 D8ABE11E8108 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 11:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level: 
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4iXp9WDXBm1b for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 11:41:56 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id AF50611E80E8 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 11:41:56 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r61IftaT020726 for <wgchairs@ietf.org>; Mon, 1 Jul 2013 14:41:56 -0400 (EDT)
Received: from rtp-vpn2-1558.cisco.com (rtp-vpn2-1558.cisco.com [10.82.246.24]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r61IftBf011786; Mon, 1 Jul 2013 14:41:55 -0400 (EDT)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: INSIPID Conflict
Date: Mon, 1 Jul 2013 14:41:55 -0400
Message-Id: <2BD2C3CA-29A3-431C-BBFC-648AA5EB8DAB@cisco.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: xmpp-chairs@tools.ietf.org, "rai-ads@tools.ietf.org" <rai-ads@tools.ietf.org>, "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.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, 01 Jul 2013 18:42:02 -0000

In an attempt to avoid the conflict between INSIPID, ECRIT and DIME on =
Monday 1300-1500 the chairs of INSIPID are requesting a move of INSIPID =
to Thursday 1520-1650.

This proposed move avoids having to move another RAI session.  This move =
introduces a RAI conflict with XMPP, which is much more palatable.

This move request has already been vetted with the RAI ADs and the XMPP =
chairs (copied here).

Cheers,

--G


From ogud@ogud.com  Mon Jul  1 11:59:30 2013
Return-Path: <ogud@ogud.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 8DD7911E81FF for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 11:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bITItzTK6X5w for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 11:59:25 -0700 (PDT)
Received: from smtp109.ord1c.emailsrvr.com (smtp109.ord1c.emailsrvr.com [108.166.43.109]) by ietfa.amsl.com (Postfix) with ESMTP id 58C5321F9F3D for <wgchairs@ietf.org>; Mon,  1 Jul 2013 11:59:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7D0069904E; Mon,  1 Jul 2013 14:59:22 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 8C98F99045;  Mon,  1 Jul 2013 14:59:19 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: BEHAVE and DNSSDEXT conflict
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com>
Date: Mon, 1 Jul 2013 14:59:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com>
References: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: wgchairs@ietf.org, agenda@ietf.org, "Behave Chairs \(behave-chairs@tools.ietf.org\)" <behave-chairs@tools.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, 01 Jul 2013 18:59:30 -0000

There is no DNSEXT meeting in Berlin, furthermore DNSEXT may not exist =
at the Berlin meeting.=20

	Olafur

On Jul 1, 2013, at 2:10 PM, Dan Wing <dwing@cisco.com> wrote:

> The BEHAVE WG and DNSSDEXT BoF are both scheduled for Friday and have =
significant overlap of interested participants, as BEHAVE deals with =
NATs (such as home NATs) and DNSSDEXT deals with naming (such as on home =
networks).  I know both BEHAVE chairs would like to attend DNSSDEXT, and =
I expect some BEHAVE participants would like to attend DNSSDEXT as well.
>=20
> Could we resolve that conflict, dropping BEHAVE to one hour if =
necessary?
>=20
> -d
>=20


From ben@nostrum.com  Mon Jul  1 12:01:15 2013
Return-Path: <ben@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 1DDC811E826D for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 kYGPpatQVHJd for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:01:14 -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 D438811E825C for <wgchairs@ietf.org>; Mon,  1 Jul 2013 12:01:06 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-071-202.mycingular.net [166.147.71.202]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r61J14gq072589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Jul 2013 14:01:05 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: INSIPID Conflict
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <2BD2C3CA-29A3-431C-BBFC-648AA5EB8DAB@cisco.com>
Date: Mon, 1 Jul 2013 14:00:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <430E5452-7144-4CA1-9D68-9B76458F32E5@nostrum.com>
References: <2BD2C3CA-29A3-431C-BBFC-648AA5EB8DAB@cisco.com>
To: Gonzalo Salgueiro <gsalguei@cisco.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.71.202 is authenticated by a trusted mechanism)
Cc: IETF WG Chairs <wgchairs@ietf.org>, xmpp-chairs@tools.ietf.org, "rai-ads@tools.ietf.org" <rai-ads@tools.ietf.org>, "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.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, 01 Jul 2013 19:01:15 -0000

Given that the XMPP chairs just requested the cancelation of the XMPP =
meeting, there's no conflict at all.

Thanks!

Ben.

On Jul 1, 2013, at 1:41 PM, Gonzalo Salgueiro <gsalguei@cisco.com> =
wrote:

> In an attempt to avoid the conflict between INSIPID, ECRIT and DIME on =
Monday 1300-1500 the chairs of INSIPID are requesting a move of INSIPID =
to Thursday 1520-1650.
>=20
> This proposed move avoids having to move another RAI session.  This =
move introduces a RAI conflict with XMPP, which is much more palatable.
>=20
> This move request has already been vetted with the RAI ADs and the =
XMPP chairs (copied here).
>=20
> Cheers,
>=20
> --G
>=20


From tim.wicinski@teamaol.com  Mon Jul  1 12:03:09 2013
Return-Path: <tim.wicinski@teamaol.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 30DF711E8264 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAkgAwG2w+Yr for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:03:05 -0700 (PDT)
Received: from omr-m01.mx.aol.com (omr-m01.mx.aol.com [64.12.143.75]) by ietfa.amsl.com (Postfix) with ESMTP id E74AD11E819C for <wgchairs@ietf.org>; Mon,  1 Jul 2013 12:03:04 -0700 (PDT)
Received: from AOLDTCMEI31.ad.aol.aoltw.net (aoldtcmei31.office.aol.com [10.180.121.109]) by omr-m01.mx.aol.com (Outbound Mail Relay) with ESMTP id 9A4BB7008D558; Mon,  1 Jul 2013 15:03:03 -0400 (EDT)
Received: from still.local (172.17.8.193) by AOLDTCMEI31.ad.aol.aoltw.net (10.180.121.109) with Microsoft SMTP Server id 14.3.123.3; Mon, 1 Jul 2013 15:03:03 -0400
Message-ID: <51D1D266.5020607@teamaol.com>
Date: Mon, 1 Jul 2013 15:03:02 -0400
From: Tim Wicinski <tim.wicinski@teamaol.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>, Dan Wing <dwing@cisco.com>
Subject: Re: BEHAVE and DNSSDEXT conflict
References: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com> <5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com>
In-Reply-To: <5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com>
Content-Type: multipart/alternative; boundary="------------070806030502070401020308"
X-Originating-IP: [172.17.8.193]
Cc: wgchairs@ietf.org, agenda@ietf.org, "Behave Chairs \(behave-chairs@tools.ietf.org\)" <behave-chairs@tools.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, 01 Jul 2013 19:03:09 -0000

--------------070806030502070401020308
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Olafur,

I had to go look this up. This is a new/proposed working group on "DNS

http://datatracker.ietf.org/wg/dnssdext/charter/

tim

On 7/1/13 2:59 PM, Olafur Gudmundsson wrote:
> There is no DNSEXT meeting in Berlin, furthermore DNSEXT may not exist at the Berlin meeting.
>
> 	Olafur
>
> On Jul 1, 2013, at 2:10 PM, Dan Wing <dwing@cisco.com> wrote:
>
>> The BEHAVE WG and DNSSDEXT BoF are both scheduled for Friday and have significant overlap of interested participants, as BEHAVE deals with NATs (such as home NATs) and DNSSDEXT deals with naming (such as on home networks).  I know both BEHAVE chairs would like to attend DNSSDEXT, and I expect some BEHAVE participants would like to attend DNSSDEXT as well.
>>
>> Could we resolve that conflict, dropping BEHAVE to one hour if necessary?
>>
>> -d
>>


--------------070806030502070401020308
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <tt>Olafur,<br>
      <br>
      I had to go look this up. This is a new/proposed working group on
      "</tt>DNS<br>
    <tt>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
    </tt><tt><br>
      <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/wg/dnssdext/charter/">http://datatracker.ietf.org/wg/dnssdext/charter/</a><br>
      <br>
      tim<br>
      <br>
    </tt>
    <div class="moz-cite-prefix">On 7/1/13 2:59 PM, Olafur Gudmundsson
      wrote:<br>
    </div>
    <blockquote cite="mid:5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com"
      type="cite">
      <pre wrap="">There is no DNSEXT meeting in Berlin, furthermore DNSEXT may not exist at the Berlin meeting. 

	Olafur

On Jul 1, 2013, at 2:10 PM, Dan Wing <a class="moz-txt-link-rfc2396E" href="mailto:dwing@cisco.com">&lt;dwing@cisco.com&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">The BEHAVE WG and DNSSDEXT BoF are both scheduled for Friday and have significant overlap of interested participants, as BEHAVE deals with NATs (such as home NATs) and DNSSDEXT deals with naming (such as on home networks).  I know both BEHAVE chairs would like to attend DNSSDEXT, and I expect some BEHAVE participants would like to attend DNSSDEXT as well.

Could we resolve that conflict, dropping BEHAVE to one hour if necessary?

-d

</pre>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070806030502070401020308--

From gsalguei@cisco.com  Mon Jul  1 12:06:31 2013
Return-Path: <gsalguei@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 8B07821F9FD0 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 lm1xmIWMXXaw for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:06:26 -0700 (PDT)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 43AC721F9FCB for <wgchairs@ietf.org>; Mon,  1 Jul 2013 12:06:26 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r61J6ORi024165 for <wgchairs@ietf.org>; Mon, 1 Jul 2013 15:06:24 -0400 (EDT)
Received: from rtp-vpn2-1558.cisco.com (rtp-vpn2-1558.cisco.com [10.82.246.24]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r61J6NIa011628; Mon, 1 Jul 2013 15:06:23 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: INSIPID Conflict
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <430E5452-7144-4CA1-9D68-9B76458F32E5@nostrum.com>
Date: Mon, 1 Jul 2013 15:06:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A85520B3-A596-479C-B286-1F6EE5C7584E@cisco.com>
References: <2BD2C3CA-29A3-431C-BBFC-648AA5EB8DAB@cisco.com> <430E5452-7144-4CA1-9D68-9B76458F32E5@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1508)
Cc: IETF WG Chairs <wgchairs@ietf.org>, xmpp-chairs@tools.ietf.org, rai-ads@tools.ietf.org, insipid-chairs@tools.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, 01 Jul 2013 19:06:31 -0000

Even better!  :-)

Thanks, Ben.

--G

On Jul 1, 2013, at 3:00 PM, Ben Campbell <ben@nostrum.com> wrote:

> Given that the XMPP chairs just requested the cancelation of the XMPP =
meeting, there's no conflict at all.
>=20
> Thanks!
>=20
> Ben.
>=20
> On Jul 1, 2013, at 1:41 PM, Gonzalo Salgueiro <gsalguei@cisco.com> =
wrote:
>=20
>> In an attempt to avoid the conflict between INSIPID, ECRIT and DIME =
on Monday 1300-1500 the chairs of INSIPID are requesting a move of =
INSIPID to Thursday 1520-1650.
>>=20
>> This proposed move avoids having to move another RAI session.  This =
move introduces a RAI conflict with XMPP, which is much more palatable.
>>=20
>> This move request has already been vetted with the RAI ADs and the =
XMPP chairs (copied here).
>>=20
>> Cheers,
>>=20
>> --G
>>=20
>=20
>=20


From joelja@bogus.com  Mon Jul  1 12:13:03 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 57EF011E8241; Mon,  1 Jul 2013 12:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGFkEgridjmE; Mon,  1 Jul 2013 12:13:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B36CB11E819C; Mon,  1 Jul 2013 12:13:02 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r61JD1Po042443 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 19:13:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <51D1D4B8.6040000@bogus.com>
Date: Mon, 01 Jul 2013 12:12:56 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Thunderbird/22.0
MIME-Version: 1.0
To: Tim Wicinski <tim.wicinski@teamaol.com>, Olafur Gudmundsson <ogud@ogud.com>, Dan Wing <dwing@cisco.com>
Subject: Re: BEHAVE and DNSSDEXT conflict
References: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com>	<5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com> <51D1D266.5020607@teamaol.com>
In-Reply-To: <51D1D266.5020607@teamaol.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 01 Jul 2013 19:13:01 +0000 (UTC)
Cc: wgchairs@ietf.org, agenda@ietf.org, "Behave Chairs \(behave-chairs@tools.ietf.org\)" <behave-chairs@tools.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, 01 Jul 2013 19:13:03 -0000

On 7/1/13 12:03 PM, Tim Wicinski wrote:
> Olafur,
>
> I had to go look this up. This is a new/proposed working group on "DNS
>
> http://datatracker.ietf.org/wg/dnssdext/charter/

It was formerly called sdnsext...

The fear was that it would fill up with sdn folks looking for a working 
group in that slot.
>
> tim
>
> On 7/1/13 2:59 PM, Olafur Gudmundsson wrote:
>> There is no DNSEXT meeting in Berlin, furthermore DNSEXT may not exist at the Berlin meeting.
>>
>> 	Olafur
>>
>> On Jul 1, 2013, at 2:10 PM, Dan Wing<dwing@cisco.com>  wrote:
>>
>>> The BEHAVE WG and DNSSDEXT BoF are both scheduled for Friday and have significant overlap of interested participants, as BEHAVE deals with NATs (such as home NATs) and DNSSDEXT deals with naming (such as on home networks).  I know both BEHAVE chairs would like to attend DNSSDEXT, and I expect some BEHAVE participants would like to attend DNSSDEXT as well.
>>>
>>> Could we resolve that conflict, dropping BEHAVE to one hour if necessary?
>>>
>>> -d
>>>
>


From Ted.Lemon@nominum.com  Mon Jul  1 12:18:58 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 DBF9421F9A2C; Mon,  1 Jul 2013 12:18:58 -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 TFzwsq6uUqK4; Mon,  1 Jul 2013 12:18:52 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 25FFA11E8229; Mon,  1 Jul 2013 12:18:52 -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 DSNKUdHWG38NuiBxgS+C0qOwzh/A4KORmfl4@postini.com; Mon, 01 Jul 2013 12:18:52 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B12881B821F; Mon,  1 Jul 2013 12:18:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A8D7F19005D; Mon,  1 Jul 2013 12:18:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 1 Jul 2013 12:18:51 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: BEHAVE and DNSSDEXT conflict
Thread-Topic: BEHAVE and DNSSDEXT conflict
Thread-Index: AQHOdoZISZLMNs/4CUmJcago9EAHZplQonkAgAAFdQA=
Date: Mon, 1 Jul 2013 19:18:50 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751F63F6@mbx-01.win.nominum.com>
References: <BA477AC3-F443-4C9B-89BD-C02E4207C358@cisco.com> <5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com>
In-Reply-To: <5D828AF9-8CA4-4DFB-A17E-B6CEEED377F0@ogud.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4801F5DBCFF52C499DD9ED3C154238E8@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<wgchairs@ietf.org>" <wgchairs@ietf.org>, "<agenda@ietf.org>" <agenda@ietf.org>, "Behave Chairs \(behave-chairs@tools.ietf.org\)" <behave-chairs@tools.ietf.org>, Dan Wing <dwing@cisco.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: Mon, 01 Jul 2013 19:18:59 -0000

On Jul 1, 2013, at 2:59 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
> There is no DNSEXT meeting in Berlin, furthermore DNSEXT may not exist at=
 the Berlin meeting.=20

We chose the name of the DNS SD EXT BoF specifically to confuse you.   I se=
e that our clever plan was a success.   :)

(DNSSDEXT is a retargeting of the MDNSEXT BoF from last time)


From stephen.farrell@cs.tcd.ie  Mon Jul  1 12:27:56 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 E3F7811E8269 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:27: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 jjK2E7V8CFF6 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 12:27:50 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E8F3311E8258 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 12:27:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D9546BE5F; Mon,  1 Jul 2013 20:27:23 +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 yOFB3j9gUtGi; Mon,  1 Jul 2013 20:27:23 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.42.20.181]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1C478BE5B; Mon,  1 Jul 2013 20:27:23 +0100 (IST)
Message-ID: <51D1D810.8040400@cs.tcd.ie>
Date: Mon, 01 Jul 2013 20:27:12 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Any possibility of deconflicting kitten and radext
References: <tslk3le3wox.fsf@mit.edu>
In-Reply-To: <tslk3le3wox.fsf@mit.edu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: wgchairs@ietf.org, abfab-chairs@tools.ietf.org, radext-chairs@tools.ietf.org, kitten-chairs@tools.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, 01 Jul 2013 19:27:56 -0000

Hi all,

Kitten has now been moved to Thu 1520.

Cheers,
S.

On 06/28/2013 07:41 PM, Sam Hartman wrote:
> 
> 
> Is there any chance of deconflicting kitten and radext.  There's a
> significant overlap between kitten and abfab and radext is struggling
> with the question of how to handle RADIUS fragmentation, which is a big
> deal for abfab.
> Two of the three kitten chairs are heavily involved in that abfab issue.
> 

From leifj@sunet.se  Mon Jul  1 14:05:19 2013
Return-Path: <leifj@sunet.se>
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 E3D5811E827F for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 14:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZio7uB6lbMN for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 14:05:19 -0700 (PDT)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [IPv6:2001:6b0:8:2::202]) by ietfa.amsl.com (Postfix) with ESMTP id 1151011E8256 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 14:05:15 -0700 (PDT)
Received: from smtp1.nordu.net (smtp1.nordu.net [IPv6:2001:948:4:6::32]) by e-mailfilter02.sunet.se (8.14.3/8.14.3/Debian-9.4) with ESMTP id r61L5BZk022128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Mon, 1 Jul 2013 23:05:11 +0200
Received: from [10.0.0.244] (tb62-102-145-131.cust.teknikbyran.com [62.102.145.131]) (authenticated bits=0) by smtp1.nordu.net (8.14.6/8.14.6) with ESMTP id r61L5776003913 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Mon, 1 Jul 2013 21:05:11 GMT
Message-ID: <51D1EF03.5030105@sunet.se>
Date: Mon, 01 Jul 2013 23:05:07 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Any possibility of deconflicting kitten and radext
References: <tslk3le3wox.fsf@mit.edu> <51D1D810.8040400@cs.tcd.ie>
In-Reply-To: <51D1D810.8040400@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, nordu-net:default, base:default, @@RPTN)
X-p0f-Info: os=unknown unknown, link=Ethernet or modem
X-CanIt-Geo: ip=62.102.145.131; country=SE; region=26; city=Vallentuna; latitude=59.5333; longitude=18.0833; http://maps.google.com/maps?q=59.5333,18.0833&z=6
X-CanItPRO-Stream: outbound-nordu-net:outbound (inherits from outbound-nordu-net:default, nordu-net:default, base:default)
X-Canit-Stats-ID: 0aJT95blm - 3725eb7fa9a0 - 20130701
X-Antispam-Training-Forget: https://mailfilter.nordu.net/canit/b.php?i=0aJT95blm&m=3725eb7fa9a0&t=20130701&c=f
X-Antispam-Training-Nonspam: https://mailfilter.nordu.net/canit/b.php?i=0aJT95blm&m=3725eb7fa9a0&t=20130701&c=n
X-Antispam-Training-Spam: https://mailfilter.nordu.net/canit/b.php?i=0aJT95blm&m=3725eb7fa9a0&t=20130701&c=s
X-Scanned-By: CanIt (www . roaringpenguin . 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: Mon, 01 Jul 2013 21:05:20 -0000

On 07/01/2013 09:27 PM, Stephen Farrell wrote:
> Hi all,
>
> Kitten has now been moved to Thu 1520.
>
> Cheers,
> S.
>
> On 06/28/2013 07:41 PM, Sam Hartman wrote:
>>
>> Is there any chance of deconflicting kitten and radext.  There's a
>> significant overlap between kitten and abfab and radext is struggling
>> with the question of how to handle RADIUS fragmentation, which is a big
>> deal for abfab.
>> Two of the three kitten chairs are heavily involved in that abfab issue.
>>
Thx!

From warren@kumari.net  Mon Jul  1 15:19:54 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 45B4811E82EF for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 15:19:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 6iq1W0I6bJDM for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 15:19:49 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC4811E82B8 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 15:19:49 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.89]) by vimes.kumari.net (Postfix) with ESMTPSA id 52CC51B40088; Mon,  1 Jul 2013 18:19:46 -0400 (EDT)
From: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: An acceptable use for Internet-Drafts?
Date: Mon, 1 Jul 2013 18:19:42 -0400
Message-Id: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
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, 01 Jul 2013 22:19:54 -0000

Hi all,

So, I recently published a draft ( "A questionable method for mitigating =
namespace collisions" -   =
http://www.ietf.org/internet-drafts/draft-wkumari-dnsop-defense-collision-=
mitigate-00.txt ) purely so that the idea is documented somewhere, and =
hopefully someone won't go off and try patent it.

As you can guess from the title I don't think that this is a =
particularity good idea (AKA, Bad Idea Fairy was visiting when I wrote =
it), but I think that if *anyone* tries to do this, then *everyone* =
should be free to try do it.

In order to try and make this more clear, I put the word -defense- in =
the draft name.=20
Does this seem like an acceptable use of the ID system? If so, should we =
try and make having -defense- or -defensive- in the draft name be an =
unwritten convention that we use?
I figured best to chat about this here first, and then, possibly, on =
-discuss if folk think it is worth broader discussion.

W
--=20
With Feudalism, it's your Count that votes.



From keith.drage@alcatel-lucent.com  Mon Jul  1 15:56:15 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 C83CB11E8328 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 15:56:15 -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 s0n7XTri4l2t for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 15:56:10 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6033311E8324 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 15:56:10 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r61Mu6NT026033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 1 Jul 2013 17:56:08 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r61Mu51w019012 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Jul 2013 00:56:05 +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, 2 Jul 2013 00:56:05 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Warren Kumari <warren@kumari.net>, WG Chairs <wgchairs@ietf.org>
Subject: RE: An acceptable use for Internet-Drafts?
Thread-Topic: An acceptable use for Internet-Drafts?
Thread-Index: AQHOdqkizxR8lCJsMESRjHp50IjulZlQbpOw
Date: Mon, 1 Jul 2013 22:56:04 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>
In-Reply-To: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.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.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: Mon, 01 Jul 2013 22:56:15 -0000

Internet-drafts are essentially a step to something else.

Otherwise while they may be retained in the tools archive, they officially =
disappear six months after issue.

So I would not regard it as a valid usage. The function you desire is one o=
f the RFC types, probably not IETF track.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Warren Kumari
> Sent: 01 July 2013 23:20
> To: WG Chairs
> Subject: An acceptable use for Internet-Drafts?
>=20
> Hi all,
>=20
> So, I recently published a draft ( "A questionable method for mitigating
> namespace collisions" -   http://www.ietf.org/internet-drafts/draft-
> wkumari-dnsop-defense-collision-mitigate-00.txt ) purely so that the idea
> is documented somewhere, and hopefully someone won't go off and try paten=
t
> it.
>=20
> As you can guess from the title I don't think that this is a particularit=
y
> good idea (AKA, Bad Idea Fairy was visiting when I wrote it), but I think
> that if *anyone* tries to do this, then *everyone* should be free to try
> do it.
>=20
> In order to try and make this more clear, I put the word -defense- in the
> draft name.
> Does this seem like an acceptable use of the ID system? If so, should we
> try and make having -defense- or -defensive- in the draft name be an
> unwritten convention that we use?
> I figured best to chat about this here first, and then, possibly, on -
> discuss if folk think it is worth broader discussion.
>=20
> W
> --
> With Feudalism, it's your Count that votes.
>=20


From mnot@mnot.net  Mon Jul  1 16:12:43 2013
Return-Path: <mnot@mnot.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 3A8F311E82FC; Mon,  1 Jul 2013 16:12: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 gcBUtPrSkyPr; Mon,  1 Jul 2013 16:12:38 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 75C7A11E82F1; Mon,  1 Jul 2013 16:12:38 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.193.114]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DBB4522E1F4; Mon,  1 Jul 2013 19:12:19 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 87 Preliminary Agenda
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <51D1628B.9040605@neclab.eu>
Date: Tue, 2 Jul 2013 09:12:16 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <191F5DF2-2A87-4583-9122-84413042B000@mnot.net>
References: <20130627215038.17941.35680.idtracker@ietfa.amsl.com> <40770153-985D-4282-AE41-6EFB56BFC86F@mnot.net> <51D1628B.9040605@neclab.eu>
To: Martin Stiemerling <Martin.Stiemerling@neclab.eu>
X-Mailer: Apple Mail (2.1508)
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 01 Jul 2013 23:12:43 -0000

I'm not sure what you're proposing; I'm just noticing that there's an =
overlap in these populations, and therefore that scheduling the two area =
meetings to compete *might* not be a good idea.=20

It's probably best for the respective ADs and chairs to figure it out; =
I'm just a bystander here ;)

Cheers,


On 01/07/2013, at 9:05 PM, Martin Stiemerling =
<Martin.Stiemerling@neclab.eu> wrote:

> Hi Mark,
>=20
> TSVWG has two slots and there is a second 1 hour slot on Monday 1510 =
to 1610. However, this collides with websec, or would this slot work?
>=20
>  Martin
>=20
>=20
>=20
> On 06/28/2013 01:26 AM, Mark Nottingham wrote:
>> The clash between Transport WG and Apps WG on Monday AM is extremely
>> unfortunate; I suspect there's going to be a LOT of overlap in
>> interest between them in this meeting.
>>=20
>>=20
>> On 28/06/2013, at 7:50 AM, IETF Agenda <agenda@ietf.org> wrote:
>>=20
>>>=20
>>> Hello Everyone,
>>>=20
>>> The preliminary agenda for IETF 87 is available for viewing.
>>> Please note the cut-off date for requests to reschedule Working
>>> Group, IRTF, and BoF meetings is July 1st, 2013.  The final agenda
>>> will be published on July 5th, 2013.
>>>=20
>>> This agenda is extremely full and changes will be difficult to
>>> make.  Please take that into consideration before requesting any
>>> changes.
>>>=20
>>> https://datatracker.ietf.org/meeting/87/agenda.html
>>> https://datatracker.ietf.org/meeting/87/agenda.txt
>>>=20
>>> Thank you!
>>>=20
>>> Stephanie McCammon
>>=20
>> -- Mark Nottingham   http://www.mnot.net/
>>=20
>>=20
>>=20
>=20
> --=20
> martin.stiemerling@neclab.eu
>=20
> NEC Laboratories Europe
> NEC Europe Limited
> Registered Office:
> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
> Registered in England 2832014
>=20
>=20

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




From fred@cisco.com  Mon Jul  1 16:33:43 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 9A79311E8335 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GW2jPS272HSs for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:33:38 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id A9AC111E82F9 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 16:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2410; q=dns/txt; s=iport; t=1372721618; x=1373931218; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=iWV1as5FurET8bCPKgIyTh325XrYrUt9t4M78ZsfY84=; b=f4g0GAQBFYiqdQkh1l5jOtFl++Q26qqjeBtXRPzNl/dhwocAlPXMn1Ot mVIFr220QPUGW1XIFPMYGiVVyc5rpA4IoYPc/CmxZtLW9rJZ2xAIAV3si j9oY4H8/3r1GXS4kwiBX9n/ZybAn2UW7qb1w9cAF/Ia/V+fKTf5GDkepZ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAP8P0lGtJV2b/2dsb2JhbABagwkySb9IfRZ0giMBAQEDATo/BQcEAgEIEQQBAQsUCQcyFAkIAgQOBQgBiAAGDLtJjysCMQcGgn5jA5N2hHuQHIMRgig
X-IronPort-AV: E=Sophos;i="4.87,976,1363132800"; d="scan'208";a="229760163"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 01 Jul 2013 23:33:38 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r61NXb6d025851 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jul 2013 23:33:37 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Mon, 1 Jul 2013 18:33:37 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: An acceptable use for Internet-Drafts?
Thread-Topic: An acceptable use for Internet-Drafts?
Thread-Index: AQHOdqkgioxMBi6eRUGS3G3JUTEO0ZlQwtMAgAAKeYA=
Date: Mon, 1 Jul 2013 23:33:37 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net> <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.119]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6E3BBC4BDB8A7848AB5F5BB9CD4E5E3B@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: Mon, 01 Jul 2013 23:33:43 -0000

One uses Internet Drafts to provide a document to the ISE to publish, if th=
e objective is publication as an RFC. So an Internet Draft is *necessary*.

Since Internet Drafts have a lifetime beyond the stipulated 6 months (take =
a look at http://tools.ietf.org/id/draft-ietf-mpsnmp-overipx-00.txt), they =
are useful for prior art searches. If the objective is to post prior art to=
 prevent patent rights, it is a library that i used.

As to "bad idea", I would suggest putting it as seeking "experimental statu=
s" and say up front that this is an idea that is NOT RECOMMENDED, and give =
reasons for not recommending it.

On Jul 1, 2013, at 3:56 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-luc=
ent.com> wrote:

> Internet-drafts are essentially a step to something else.
>=20
> Otherwise while they may be retained in the tools archive, they officiall=
y disappear six months after issue.
>=20
> So I would not regard it as a valid usage. The function you desire is one=
 of the RFC types, probably not IETF track.
>=20
> Keith
>=20
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Warren Kumari
>> Sent: 01 July 2013 23:20
>> To: WG Chairs
>> Subject: An acceptable use for Internet-Drafts?
>>=20
>> Hi all,
>>=20
>> So, I recently published a draft ( "A questionable method for mitigating
>> namespace collisions" -   http://www.ietf.org/internet-drafts/draft-
>> wkumari-dnsop-defense-collision-mitigate-00.txt ) purely so that the ide=
a
>> is documented somewhere, and hopefully someone won't go off and try pate=
nt
>> it.
>>=20
>> As you can guess from the title I don't think that this is a particulari=
ty
>> good idea (AKA, Bad Idea Fairy was visiting when I wrote it), but I thin=
k
>> that if *anyone* tries to do this, then *everyone* should be free to try
>> do it.
>>=20
>> In order to try and make this more clear, I put the word -defense- in th=
e
>> draft name.
>> Does this seem like an acceptable use of the ID system? If so, should we
>> try and make having -defense- or -defensive- in the draft name be an
>> unwritten convention that we use?
>> I figured best to chat about this here first, and then, possibly, on -
>> discuss if folk think it is worth broader discussion.
>>=20
>> W
>> --
>> With Feudalism, it's your Count that votes.
>>=20
>=20


From johnl@iecc.com  Mon Jul  1 16:39:02 2013
Return-Path: <johnl@iecc.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 F32EA11E833C for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.094
X-Spam-Level: 
X-Spam-Status: No, score=-109.094 tagged_above=-999 required=5 tests=[AWL=-0.195, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, MANGLED_SPAM=2.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRPHCCCTZYpe for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:38:58 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C4C9211E833A for <wgchairs@ietf.org>; Mon,  1 Jul 2013 16:38:57 -0700 (PDT)
Received: (qmail 56474 invoked from network); 1 Jul 2013 23:38:56 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 1 Jul 2013 23:38:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51d21310.xn--hew.k1307; i=johnl@user.iecc.com; bh=uR9vpUkW3yqn10cdlv4Zmw7H2vnkW+e1/cRBri8AKYU=; b=MFErxBIlQQR4SXeBxLQSASrfvwvtQhh4hXpF/9zBGwPHRBVuBfYusYh2bNW8C3CnMfjXGT9Qi9vVCdzbN9Lm+0o2TM86w7Pme3BddKP5VR1j0bokpQoVdnygUHR0+RaQ26JdYPlx2IwJ4rf2QsQV1gLj5/1Cx0GZ5i3FxlxMkDd+imTUSPrnmhjx4yCvIqC0nsEH0KHmzdJwILCTiUIRV+PCbvCrCQhlwCIR0Guk7b64+nThYzTXYAYyUt8FSKWj
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51d21310.xn--hew.k1307; olt=johnl@user.iecc.com; bh=uR9vpUkW3yqn10cdlv4Zmw7H2vnkW+e1/cRBri8AKYU=; b=BXHJV7ArG6b5X2nn6ZbhhGd2kxqYTQeQsThNvcSkhmGHmL9Ig7rnDZm2qtOztejKZ/MN0oPr+F25iSbi+78LP/h7NAxyK6/Qp45JiXLdoeG3ci2zCu71jLijfpC8BGMA2Zo3JSyvVaHBighJD+Juew0le0x1wNb4f3jGA9nLmcEv2Qk4TrKlAZUhrLTg95enIQOPSwohYtf2nTJ+ir/cm5p/dg1gFrepXytmfvVMUIFIjIsap0N92SVqOvwl7l13
Date: 1 Jul 2013 23:38:34 -0000
Message-ID: <20130701233834.14632.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: wgchairs@ietf.org
Subject: Re: An acceptable use for Internet-Drafts?
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
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, 01 Jul 2013 23:39:02 -0000

>Internet-drafts are essentially a step to something else.
>
>Otherwise while they may be retained in the tools archive, they officially disappear six months after issue.
>
>So I would not regard it as a valid usage. The function you desire is one of the RFC types, probably not IETF track.

We all know in reality that I-D's may expire, but they don't
disappear, so I think we're OK there.

I also think there is some benefit to the IETF of writing up known bad
ideas, to speed up the discussion when they come around again and
again.  If they're discoverable prior art, so much the better.

When I was running the ASRG, I set up a wiki at http://wiki.asrg.sp.am
where we could document anti-spam techniques, both the good ones and
the bad ones.  It's been somewhat helpful as people reinvent stuff.

R's,
John

From paul.hoffman@vpnc.org  Mon Jul  1 16:45:21 2013
Return-Path: <paul.hoffman@vpnc.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 39FF211E8339 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 6dsa0-OSGnMb for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:45:20 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CF02B11E82FA for <wgchairs@ietf.org>; Mon,  1 Jul 2013 16:45:20 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r61NjJpi082669 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Mon, 1 Jul 2013 16:45:20 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: An acceptable use for Internet-Drafts?
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com>
Date: Mon, 1 Jul 2013 16:45:20 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <037A1049-4240-4693-9004-D9AFFB492AFD@vpnc.org>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net> <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com>
To: WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1508)
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, 01 Jul 2013 23:45:21 -0000

On Jul 1, 2013, at 4:33 PM, Fred Baker (fred) <fred@cisco.com> wrote:

> As to "bad idea", I would suggest putting it as seeking "experimental =
status" and say up front that this is an idea that is NOT RECOMMENDED, =
and give reasons for not recommending it.

That seems like overkill. A statement of the author's actual intention =
in the Abstract ("I am publishing this to maybe establish prior art, but =
not to have anyone implement it") is the honest and sufficient thing to =
do. If the author changes his mind and later wants to get the idea used, =
he or she simply issues a new draft in the same series with a different =
Abstract, again giving the actual intention.

--Paul Hoffman=

From Ted.Lemon@nominum.com  Mon Jul  1 16:48:11 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 12D1611E82FA for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pD7wPWzfi5g for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 16:48:03 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id B360111E8333 for <wgchairs@ietf.org>; Mon,  1 Jul 2013 16:48:03 -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 DSNKUdIVMslHYiiPAet69Pz6arXl9OPKY3yA@postini.com; Mon, 01 Jul 2013 16:48:03 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6C5A01B816F for <wgchairs@ietf.org>; Mon,  1 Jul 2013 16:48:02 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6640919005D; Mon,  1 Jul 2013 16:48:02 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 1 Jul 2013 16:48:02 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: An acceptable use for Internet-Drafts?
Thread-Topic: An acceptable use for Internet-Drafts?
Thread-Index: AQHOdqkeCqNWdGupv0qle21nwR96+plQ5FoAgAAK3AA=
Date: Mon, 1 Jul 2013 23:48:01 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751F6A3D@mbx-01.win.nominum.com>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net> <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B063C83@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="us-ascii"
Content-ID: <2663847F4C6E964EB1088C113414B371@nominum.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: Mon, 01 Jul 2013 23:48:11 -0000

On Jul 1, 2013, at 6:56 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-luc=
ent.com> wrote:
> So I would not regard it as a valid usage. The function you desire is one=
 of the RFC types, probably not IETF track.

Having openly published something, it is no longer (in principle) patentabl=
e.   So this would _work_ from a legal perspective, as long as evidence tha=
t it had been published isn't lost, which I think it probably wouldn't be. =
  However, Keith is right that you might as well publish it; you can use th=
e Independent Stream for documents of this sort, at least in theory.=

From cabo@tzi.org  Mon Jul  1 17:14:35 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 98E1111E833D for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 17:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id um7jSwS5Yk69 for <wgchairs@ietfa.amsl.com>; Mon,  1 Jul 2013 17:14:31 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 42E1621F957B for <wgchairs@ietf.org>; Mon,  1 Jul 2013 17:14:29 -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 r620ELTr020439; Tue, 2 Jul 2013 02:14:21 +0200 (CEST)
Received: from [192.168.217.105] (p54894870.dip0.t-ipconnect.de [84.137.72.112]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F237F3A53; Tue,  2 Jul 2013 02:14:20 +0200 (CEST)
Subject: Re: An acceptable use for Internet-Drafts?
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: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>
Date: Tue, 2 Jul 2013 02:14:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6208FA3-0B6D-44B9-8158-FA045380C120@tzi.org>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>
To: Warren Kumari <warren@kumari.net>
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: Tue, 02 Jul 2013 00:14:35 -0000

On Jul 2, 2013, at 00:19, Warren Kumari <warren@kumari.net> wrote:

> So, I recently published a draft purely so that the idea is documented =
somewhere, and hopefully someone won't go off and try patent it.

I do this all the time.  I didn't ask for permission, and don't see why =
I should.

We have discussed this before...
http://www.ietf.org/mail-archive/web/ietf/current/msg77642.html

Recently, I keep a document that serves as the container (now at -25) =
together with useful stuff, so I don't even need to alert people that a =
defensive public disclosure just occurred.

Gr=FC=DFe, Carsten


From ietf-secretariat@ietf.org  Tue Jul  2 10:47:57 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 8F51F21F9BBC; Tue,  2 Jul 2013 10:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.6
X-Spam-Level: 
X-Spam-Status: No, score=-106.6 tagged_above=-999 required=5 tests=[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 p0O92-6s6CrY; Tue,  2 Jul 2013 10:47:56 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A68FF21F9AF0; Tue,  2 Jul 2013 10:47:56 -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 87 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130702174756.28399.12287.idtracker@ietfa.amsl.com>
Date: Tue, 02 Jul 2013 10:47:56 -0700
Cc: wgchairs@ietf.org, 87all@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: Tue, 02 Jul 2013 17:47:57 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

1.  Social Event
2.  Sponsor Web page
3.  Visas & Letters of Invitation
4.  Accommodations
5.  Companion Program
6.  Childcare Information


1.  Social Event
IETF87's social event sponsored by DENIC will be held at the famous German =
Museum of Technology (Deutsches Technikmuseum) in Berlin on Tuesday, 30 Jul=
y 2013 from 19:00 to 24:00

Shuttles will be provided from/to the Intercontinental starting at 18:30. Y=
ou may also walk to the museum (directions will be available soon). It will=
 take you about 30 minutes.

The cost is $30 USD per person. 475 tickets will be available, due to the e=
xpected demand, registration is limited to IETF87 attendees and one guest. =


For more information or to purchase tickets, please visit:
http://www.ietf.org/meeting/87/social.html

2. Sponsor Web Page
DENIC, the Platinum sponsor for IETF 87 has created a web page with informa=
tion about Berlin, the URL is: http://www.ietf87.de/

3. Visas & Letters of Invitation:
For information on Visiting Germany, please visit:
http://www.auswaertiges-amt.de/EN/EinreiseUndAufenthalt/Visabestimmungen_no=
de.html

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 emai=
l.

Please note that the IETF Letter of Invitation may not be sufficient for ob=
taining a visa to enter Germany.

4.  Accommodations
Currently the venue hotel (InterContinental) and overflow hotel (Pullman) a=
re both fully booked. The following hotels are near the InterContinental th=
ough we are not holding blocks at any of them.

Pestana
http://www.pestana.com/en/pestana-berlin-tiergarten-hotel/pages/home.aspx
Distance from InterContinental: approximately 1-2 minute walk

Hotel Berlin
http://www.hotel-berlin.de/en/hotel-berlin.html
Distance from InterContinental: approximately 5-7 minute walk

Das Stue Hotel
http://www.das-stue.com/en/
Distance from InterContinental: approximately 7-10 minute walk

5.  Companion Program
If you are traveling with a friend or family member over 18 years of age yo=
u 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, 28 J=
uly
- Ability to attend the official Welcome Reception from 1700-1900 on Sunday=
, 28 July
- A distinctive meeting badge that grants access to the venue (not to be us=
ed to attend working sessions)
- Participation in a separate companion email list if you choose to help co=
mmunicate 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 87 companions mailing list only see:
https://www.ietf.org/mailman/listinfo/87companions

6.  Childcare Information
If you are staying at the InterContinental or the Pullman and are intereste=
d in childcare services, please contact the concierge at the respective hot=
el to get more information or to make arrangements. You can email the Inter=
Continental at <berha.concierge@ihg.com> and the Pullman at <pullman@berlin=
concierge.de>

Only 26 days until the Berlin IETF!

From salvatore.loreto@ericsson.com  Wed Jul  3 00:53:52 2013
Return-Path: <salvatore.loreto@ericsson.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 A54A621F9A6A; Wed,  3 Jul 2013 00:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ilX1OZP43zn; Wed,  3 Jul 2013 00:53:47 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3DBDF21F9A49; Wed,  3 Jul 2013 00:53:47 -0700 (PDT)
X-AuditID: c1b4fb25-b7f826d000001766-30-51d3d8898b06
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 64.A1.05990.988D3D15; Wed,  3 Jul 2013 09:53:46 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.147) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.2.328.9; Wed, 3 Jul 2013 09:53:45 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id B9D3E1102AF; Wed,  3 Jul 2013 10:53:45 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 98B7655482; Wed,  3 Jul 2013 10:53:42 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 2877A552AA; Wed,  3 Jul 2013 10:53:39 +0300 (EEST)
Message-ID: <51D3D880.9010609@ericsson.com>
Date: Wed, 3 Jul 2013 09:53:36 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: <wgchairs@ietf.org>
Subject: Re: IETF 87 Preliminary Agenda
References: <20130627215038.17941.35680.idtracker@ietfa.amsl.com> <40770153-985D-4282-AE41-6EFB56BFC86F@mnot.net> <51D1628B.9040605@neclab.eu> <191F5DF2-2A87-4583-9122-84413042B000@mnot.net>
In-Reply-To: <191F5DF2-2A87-4583-9122-84413042B000@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+JvrW7XjcuBBuvWCFv8ehdk8X//FEYH Jo8lS34yBTBGcdmkpOZklqUW6dslcGXM/T6frWCmUMW+pnbGBsYdfF2MnBwSAiYSk+ZMYoOw xSQu3FsPZHNxCAkcZpQ4dmcxlLOeUWJK4zUmCGcvo8S3V6uhnHWMEreXb2aGcLYzSny9vY4Z ZBivgLbEp137WUFsFgEViR2Ni9lBbDYBM4nnD7eA1YgKJEu8v3IHql5Q4uTMJywgtoiAuMSK 1evB4swCihJTt+wD6xUWUJc4MnUBC8SyfYwSO9p/gxVxCthI7J68nh2iwVbiwpzrLBC2vMT2 t3OYIb5Tk7h6bhOYLSSgJdF7tpNpAqPoLCS7ZyFpn4WkfQEj8ypG9tzEzJz0cqNNjMCAP7jl t+oOxjvnRA4xSnOwKInzbtY7EygkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMSIqY87rjQxz az5937Q/aY/WrXDxKZJb3O4tWG+7RiSTX7snebuEoeT7GGuFc3csHix/x36za4ZS/Muvr/Y7 vTJwsZ2a/zbXU9j80HGLVV9/8C2a6KqzcFeATILlQfk1FjveS01aMfc7Y2az/eMbyrV7DU/o LucvXcp5UO+jm8Vdlp+KNgymq5RYijMSDbWYi4oTAZARpupGAgAA
Cc: IETF Agenda <agenda@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, 03 Jul 2013 07:53:52 -0000

Martin,

I do think that a lot of people in APP area are really interested in the 
TSV area issues as well,
so having a conflict there is really bad!

I myself have a conflict as I have to chair the APPS wg and I won't be 
able to attend the tsvwg meeting
where I am interested to follow several SCTP drafts among the other stuff


-- 
Salvatore Loreto, PhD
www.sloreto.com



On 7/2/13 1:12 AM, Mark Nottingham wrote:
> I'm not sure what you're proposing; I'm just noticing that there's an overlap in these populations, and therefore that scheduling the two area meetings to compete *might* not be a good idea.
>
> It's probably best for the respective ADs and chairs to figure it out; I'm just a bystander here ;)
>
> Cheers,
>
>
> On 01/07/2013, at 9:05 PM, Martin Stiemerling <Martin.Stiemerling@neclab.eu> wrote:
>
>> Hi Mark,
>>
>> TSVWG has two slots and there is a second 1 hour slot on Monday 1510 to 1610. However, this collides with websec, or would this slot work?
>>
>>   Martin
>>
>>
>>
>> On 06/28/2013 01:26 AM, Mark Nottingham wrote:
>>> The clash between Transport WG and Apps WG on Monday AM is extremely
>>> unfortunate; I suspect there's going to be a LOT of overlap in
>>> interest between them in this meeting.
>>>
>>>
>>> On 28/06/2013, at 7:50 AM, IETF Agenda <agenda@ietf.org> wrote:
>>>
>>>> Hello Everyone,
>>>>
>>>> The preliminary agenda for IETF 87 is available for viewing.
>>>> Please note the cut-off date for requests to reschedule Working
>>>> Group, IRTF, and BoF meetings is July 1st, 2013.  The final agenda
>>>> will be published on July 5th, 2013.
>>>>
>>>> This agenda is extremely full and changes will be difficult to
>>>> make.  Please take that into consideration before requesting any
>>>> changes.
>>>>
>>>> https://datatracker.ietf.org/meeting/87/agenda.html
>>>> https://datatracker.ietf.org/meeting/87/agenda.txt
>>>>
>>>> Thank you!
>>>>
>>>> Stephanie McCammon
>>> -- Mark Nottingham   http://www.mnot.net/
>>>
>>>
>>>
>> -- 
>> martin.stiemerling@neclab.eu
>>
>> NEC Laboratories Europe
>> NEC Europe Limited
>> Registered Office:
>> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
>> Registered in England 2832014
>>
>>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>



From eburger@standardstrack.com  Wed Jul  3 04:56:47 2013
Return-Path: <eburger@standardstrack.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 4437821F9D38 for <wgchairs@ietfa.amsl.com>; Wed,  3 Jul 2013 04:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.185
X-Spam-Level: 
X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SQctZ4n+Pog for <wgchairs@ietfa.amsl.com>; Wed,  3 Jul 2013 04:56:42 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id A4DF421F9D2E for <wgchairs@ietf.org>; Wed,  3 Jul 2013 04:56:42 -0700 (PDT)
Received: from cpe-74-76-87-23.nycap.res.rr.com ([74.76.87.23]:53732 helo=[192.168.1.137]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UuLfl-0008Ii-Bz for wgchairs@ietf.org; Wed, 03 Jul 2013 04:56:41 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8EB2829D-851D-4C3F-BF04-B80E1FDA3F3B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Message-Id: <D0BE071A-FC30-40ED-BF5C-9059DDA43B7D@standardstrack.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: An acceptable use for Internet-Drafts?
Date: Wed, 3 Jul 2013 07:56:35 -0400
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net> <D6208FA3-0B6D-44B9-8158-FA045380C120@tzi.org>
To: WG Chairs <wgchairs@ietf.org>
In-Reply-To: <D6208FA3-0B6D-44B9-8158-FA045380C120@tzi.org>
X-Mailer: Apple Mail (2.1508)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
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, 03 Jul 2013 11:56:47 -0000

--Apple-Mail=_8EB2829D-851D-4C3F-BF04-B80E1FDA3F3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On a related note, I am starting a project (so far unfunded) to collect =
presentations from the voice over IP trade shows for the purposes of =
establishing a data bank of prior art references. Anyone have old CD's =
or DVD's or, better yet, your own presentations to share, please let me =
know.

On Jul 1, 2013, at 8:14 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jul 2, 2013, at 00:19, Warren Kumari <warren@kumari.net> wrote:
>=20
>> So, I recently published a draft purely so that the idea is =
documented somewhere, and hopefully someone won't go off and try patent =
it.
>=20
> I do this all the time.  I didn't ask for permission, and don't see =
why I should.
>=20
> We have discussed this before...
> http://www.ietf.org/mail-archive/web/ietf/current/msg77642.html
>=20
> Recently, I keep a document that serves as the container (now at -25) =
together with useful stuff, so I don't even need to alert people that a =
defensive public disclosure just occurred.
>=20
> Gr=FC=DFe, Carsten
>=20


--Apple-Mail=_8EB2829D-851D-4C3F-BF04-B80E1FDA3F3B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iQIcBAEBAgAGBQJR1BF0AAoJEORoZaSQsc1IybUQAOASlRuZoQKF6pfCDoCadoq7
5Qut9CxEpx5H7hg9QvCJX5ggRg7hsCx+YSJ/1m/F8gNjJTYLvVLKpytgoAPcYzHV
2urcSWGsTaLQ0c51h/26bza85wPBw5+RWSQP6CyfArwEZGC27Fl4jUuZBExYtyZp
5HVpMh1YenmPC+wnZ1eSUXb3N3OiR07KTKdm5noraxXxAkpMrTR2GqG7mHJUk5qU
/OWKMqYq88Z6Xo33cpxhyPpJmIr+Dtr5OZVFHQyVvMHRp5kcvOlQuDbT8hoU/e5v
KScAMGz9CSNlQUI+VF4sGKet4SiADSLObPKhxnqAYJ7zS1wd33Y0Ol/lsej0F7Oe
kSUH+dqutvyN+55gxw3N9ovKi5XK+E9/eze5P+cZ2fA1aHsiz+7AFfqxlMoh9OmB
mHy8iQkWo91wbp07xjyOVEYEZcpEjxRjjdXpQYH4NRrDLHLMVr8/IWsEomUYzlnN
/6pQut+oCu2yx/xYsbygtc/lzPEvX4jqq52Bji0knbfyImxeag+Yruba5zheIaii
nWWlE9ugeG2f0DaB3LFv4MA7TU+E9zH7+IJPjN48QW4OOTG3wpCv3yr/HorAYm0w
qyWWoRCMCI0Hh0hW/WPjt0cFDZ76Wlu9Qr4uQWzBloXz9tHgoSwpHKpndUc/aetA
s9HBVErwklUefOrhWQnI
=Bf9n
-----END PGP SIGNATURE-----

--Apple-Mail=_8EB2829D-851D-4C3F-BF04-B80E1FDA3F3B--

From iad@ietf.org  Wed Jul  3 14:31:09 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 3F6A411E821B; Wed,  3 Jul 2013 14:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.204
X-Spam-Level: 
X-Spam-Status: No, score=-101.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 joM-hYTC5mva; Wed,  3 Jul 2013 14:31:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF21911E80F6; Wed,  3 Jul 2013 14:31:08 -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: IETF 87 Registration Suspended
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
Date: Wed, 03 Jul 2013 14:31:08 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.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: Wed, 03 Jul 2013 21:31:09 -0000

Registration for IETF87 in Berlin has been suspended to consider the impact =

of a change in the VAT rules on Registration Fees.  We expect registration =

to open as soon as this matter has been clarified.

Ray
IETF Administrative Director

From Sandra.Murphy@sparta.com  Wed Jul  3 15:00:24 2013
Return-Path: <Sandra.Murphy@sparta.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 CE2E011E823E; Wed,  3 Jul 2013 15:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 n52RbQ9H03WP; Wed,  3 Jul 2013 15:00:10 -0700 (PDT)
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by ietfa.amsl.com (Postfix) with ESMTP id 2304D11E80EF; Wed,  3 Jul 2013 15:00:03 -0700 (PDT)
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r63Lxvw7011170; Wed, 3 Jul 2013 16:59:57 -0500
Received: from CVA-HUB001.centreville.ads.sparta.com ([10.62.108.11]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r63LxqHq001828; Wed, 3 Jul 2013 16:59:57 -0500
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; Wed, 3 Jul 2013 18:00:45 -0400
From: "Murphy, Sandra" <Sandra.Murphy@sparta.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Subject: RE: IETF 87 Registration Suspended
Thread-Topic: IETF 87 Registration Suspended
Thread-Index: AQHOeDTHd8AOjDX580yU2trk6x9e7ZlTgMe7
Date: Wed, 3 Jul 2013 22:00:45 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F67497638C@CVA-MB002.centreville.ads.sparta.com>
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
In-Reply-To: <20130703213108.25309.83377.idtracker@ietfa.amsl.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "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, 03 Jul 2013 22:00:24 -0000

Is there a potential for impact to those already registered?  (So we know t=
o watch for the announcement.)=0A=
=0A=
--Sandy=0A=
=0A=
________________________________________=0A=
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of IE=
TF Administrative Director [iad@ietf.org]=0A=
Sent: Wednesday, July 03, 2013 5:31 PM=0A=
To: IETF Announcement List=0A=
Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org=0A=
Subject: IETF 87 Registration Suspended=0A=
=0A=
Registration for IETF87 in Berlin has been suspended to consider the impact=
=0A=
of a change in the VAT rules on Registration Fees.  We expect registration=
=0A=
to open as soon as this matter has been clarified.=0A=
=0A=
Ray=0A=
IETF Administrative Director=0A=

From barryleiba.mailing.lists@gmail.com  Wed Jul  3 17:39:04 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 0A91211E810D; Wed,  3 Jul 2013 17:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.956
X-Spam-Level: 
X-Spam-Status: No, score=-101.956 tagged_above=-999 required=5 tests=[AWL=0.022, 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 H4NPhQy5UUZk; Wed,  3 Jul 2013 17:39:03 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 56E8A11E80E3; Wed,  3 Jul 2013 17:39:03 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id jw11so624755veb.4 for <multiple recipients>; Wed, 03 Jul 2013 17:39:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bYTKiij+i1/7wVXUkmidEGb7/PJHoD02ICteOdHqkGg=; b=T516aVhA7mFNOwU0kaQuJawgs4Qm2dEVd6rWTmnoUmcbtTLQUKdwB/lVIYb3wK9VIN ZnhxHDz0QM7cO6emGmKNlJ5IBB4AqVZ7GdEB2naZ0mArWyT9rj1Pzy7U/iA8piYUMJH9 xt+kqx5jiOgbPJdQGO/lPBt2qUK0Kvqnybq2UqeMXd7vTTewF9Ya3u83f3zKbJ40opvr bYWv91X/W8Tr6mUo5CNzBFJ6p3tHfYFQtvo6sJqfD/XxQ5++kLm8ev4TKNCKPBQaeeqd 1uHbMPFnDypEgyrrS443my38QKjL+UkJ0TUNdnKOaiLcWSXfAUa/VX8nmVpfirx6BGL3 EjfA==
MIME-Version: 1.0
X-Received: by 10.220.181.69 with SMTP id bx5mr1084721vcb.71.1372898341728; Wed, 03 Jul 2013 17:39:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 3 Jul 2013 17:39:01 -0700 (PDT)
In-Reply-To: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com>
Date: Wed, 3 Jul 2013 20:39:01 -0400
X-Google-Sender-Auth: bZ4nWxIYowPNskGhAyHUdEnA6ZM
Message-ID: <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
Subject: Re: IETF 87 Registration Suspended
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iaoc@ietf.org, IAB <iab@iab.org>, Working Group 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, 04 Jul 2013 00:39:04 -0000

> Registration for IETF87 in Berlin has been suspended to consider the impact
> of a change in the VAT rules on Registration Fees.  We expect registration
> to open as soon as this matter has been clarified.

I don't understand what the effect of VAT rules is on money collected
in the U.S. in U.S. Dollars.

But I guess we'll hear more soon.

Barry

From duerst@it.aoyama.ac.jp  Wed Jul  3 21:30:02 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 4D02F11E8125; Wed,  3 Jul 2013 21:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level: 
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8XAANh7tEaq; Wed,  3 Jul 2013 21:29:55 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 90FCF11E8104; Wed,  3 Jul 2013 21:29:55 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r644To6g013215; Thu, 4 Jul 2013 13:29:50 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 6edc_0b12_5d710b8c_e462_11e2_bf4c_001e6722eec2; Thu, 04 Jul 2013 13:29:49 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id AC1E1BF548; Thu,  4 Jul 2013 13:28:13 +0900 (JST)
Message-ID: <51D4FA2D.3040601@it.aoyama.ac.jp>
Date: Thu, 04 Jul 2013 13:29:33 +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: Barry Leiba <barryleiba@computer.org>
Subject: Re: IETF 87 Registration Suspended
References: <20130703213108.25309.83377.idtracker@ietfa.amsl.com> <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
In-Reply-To: <CAC4RtVD5XLO0iqXAYLZfLsGbaRiAHpL1jNDJLLri9jekAKN7gw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, IAB <iab@iab.org>, IETF discussion list <ietf@ietf.org>, Working Group 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, 04 Jul 2013 04:30:02 -0000

Hello Barry,

On 2013/07/04 9:39, Barry Leiba wrote:
>> Registration for IETF87 in Berlin has been suspended to consider the impact
>> of a change in the VAT rules on Registration Fees.  We expect registration
>> to open as soon as this matter has been clarified.
>
> I don't understand what the effect of VAT rules is on money collected
> in the U.S. in U.S. Dollars.

It's usual in the U.S. that taxes on goods bought and sold are levied as 
a consumption tax, at the place (i.e. in the state) where the object is 
bought (and therefore presumably consumed/used).

However, that's not a given, and VAT stands for value added tax, and the 
value addition/consumption can be presumed to happen at the meeting in 
Berlin (and there's no need for consensus here, it's the opinion of the 
local tax authority that counts :-().

Regards,   Martin.

> But I guess we'll hear more soon.
>
> Barry
>

From john@jck.com  Fri Jul  5 07:31:01 2013
Return-Path: <john@jck.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 1E1D911E80F4; Fri,  5 Jul 2013 07:31:01 -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 2KDFAL8qtMqV; Fri,  5 Jul 2013 07:30:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0392821F9F71; Fri,  5 Jul 2013 07:30:56 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1Uv729-0007GS-4s; Fri, 05 Jul 2013 10:30:49 -0400
X-Vipre-Scanned: 023EF5C2002C31023EF70F-TDI
Date: Fri, 05 Jul 2013 10:30:47 -0400
From: John C Klensin <john@jck.com>
To: l.wood@surrey.ac.uk, mrex@sap.com, duerst@it.aoyama.ac.jp
Subject: RE: IETF 87 Registration Suspended
Message-ID: <B83C42E16A057A939FFD3939@[192.168.1.128]>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp> ,	<20130705010654.ABCA31A87C@ld9781.wdf.sap.corp> <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: iaoc@ietf.org, barryleiba@computer.org, ietf@ietf.org, iab@iab.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, 05 Jul 2013 14:31:01 -0000

--On Friday, July 05, 2013 07:40 +0100 l.wood@surrey.ac.uk wrote:

> It strikes me that 'membership fees' as opposed to 'entrance
> fees' could work around this payment issue. Or incur a
> different tax...

But the use of a term like "membership fee" has profound
implications for what the IETF claims is our way of doing
business.

Folks, it is clear that this is both inconvenient and
complicated.  Would it be possible to just let the IAOC engage
in whatever discussions and consultations are needed --i.e.,
allow them to do their jobs-- without endless amateur [1]
speculation on what is going on and what should or could be done
about it.   Since people are obviously curious and in the
interest of openness and transparency, I hope that the IAOC will
explain the details and the solutions when they have things
under control.  But let's let them get them under control first.

Just my opinion, of course.

   john

[1] both amateur lawyers and amateur international taxation
experts.  Anyone who is part of the conversation who is _not_ am
amateur should probably volunteer (or market) her or his
services offlist to the IAOC or directly to Ray at iad@ietf.org




From tjc@ecs.soton.ac.uk  Fri Jul  5 07:34:20 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 F222D21F9967; Fri,  5 Jul 2013 07:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZA-0HihB-2I; Fri,  5 Jul 2013 07:34:19 -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 1985321F9963; Fri,  5 Jul 2013 07:34:18 -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 r65EYBsM020319; Fri, 5 Jul 2013 15:34:11 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r65EYBsM020319
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1373034852; bh=3AjnIc9gW+kXXpBln9JqSJBngXI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=myrX2ZNdA6mXAESr3dGkbBZXCbXNH8In6VlR7/sZY0O7ELB9pITrXA/vj7WGNUpDY Tddm4MPpI7Nl85eja4huG2xRyohJ5FzsQYp3Vc2pasHOrwOQ3hml7gmhE3RrYgeH+5 kUYMW8qjFqIFz2ozcAj8OVO5qzPbBwObICmpZAZs=
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 p64FYB0544538556dx ret-id none; Fri, 05 Jul 2013 15:34:12 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r65EYAxp001708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Jul 2013 15:34:10 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 87 Registration Suspended
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B83C42E16A057A939FFD3939@[192.168.1.128]>
Date: Fri, 5 Jul 2013 15:34:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f733db8168234a92b6acab0072053be0p64FYB03tjc|ecs.soton.ac.uk|B874A9EC-72A7-4AF6-93AA-34391074AE3D@ecs.soton.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp> , <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp> <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk> <B83C42E16A057A939FFD3939@[192.168.1.128]> <B874A9EC-72A7-4AF6-93AA-34391074AE3D@ecs.soton.ac.uk>
To: John C Klensin <john@jck.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p64FYB054453855600; tid=p64FYB0544538556dx; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=9:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r65EYBsM020319
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: wgchairs@ietf.org, mrex@sap.com, ietf@ietf.org, l.wood@surrey.ac.uk, iaoc@ietf.org, iab@iab.org, barryleiba@computer.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, 05 Jul 2013 14:34:20 -0000

On 5 Jul 2013, at 15:30, John C Klensin <john@jck.com> wrote:

> --On Friday, July 05, 2013 07:40 +0100 l.wood@surrey.ac.uk wrote:
>=20
>> It strikes me that 'membership fees' as opposed to 'entrance
>> fees' could work around this payment issue. Or incur a
>> different tax...
>=20
> But the use of a term like "membership fee" has profound
> implications for what the IETF claims is our way of doing
> business.

I would add also that many organisations (and funding bodies) would not =
support claims for "membership fees" where conference meeting =
registration fees are perfectly accepted.

Tim=

From mrex@sap.com  Thu Jul  4 18:07:11 2013
Return-Path: <mrex@sap.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 18B9B11E80E6; Thu,  4 Jul 2013 18:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.649
X-Spam-Level: 
X-Spam-Status: No, score=-9.649 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbs9h3k3FPPy; Thu,  4 Jul 2013 18:07:06 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id A810911E8103; Thu,  4 Jul 2013 18:07:04 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r6516sY7019524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Jul 2013 03:06:54 +0200 (MEST)
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <51D4FA2D.3040601@it.aoyama.ac.jp>
To: =?UTF-8?Q?=22Martin_J=2E_D=C3=BCrst=22?= <duerst@it.aoyama.ac.jp>
Date: Fri, 5 Jul 2013 03:06:54 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
X-Mailman-Approved-At: Fri, 05 Jul 2013 08:34:27 -0700
Cc: iaoc@ietf.org, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>, IAB <iab@iab.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 05 Jul 2013 01:07:11 -0000

"Martin J. D=FCrst" wrote:
>=20
>On 2013/07/04 9:39, Barry Leiba wrote:
>>> Registration for IETF87 in Berlin has been suspended to consider the im=
pact
>>> of a change in the VAT rules on Registration Fees.  We expect registrat=
ion
>>> to open as soon as this matter has been clarified.
>>
>> I don't understand what the effect of VAT rules is on money collected
>> in the U.S. in U.S. Dollars.
>=20
> It's usual in the U.S. that taxes on goods bought and sold are levied as=
=20
> a consumption tax, at the place (i.e. in the state) where the object is=
=20
> bought (and therefore presumably consumed/used).
>=20
> However, that's not a given, and VAT stands for value added tax, and the=
=20
> value addition/consumption can be presumed to happen at the meeting in=20
> Berlin (and there's no need for consensus here, it's the opinion of the=
=20
> local tax authority that counts :-().


If the money that is collected is an entrance/participation fee for
the venue itself, then the local tax authority might require the local
VAT for _all_ visitors, even those that pay in advance or in a
different country.


While it might be possible to make the necessary tweaks about the fee
(maybe not for this meeting, but for future meetings) for the WG sessions
themselves, this would be more difficult to argue for the
breakfast/buffet/brownies/beverages (I assume that still exists)
and the access to the terminal room, where some form of badge
checking is usually done in order to protect the resources.


-Martin


From mrex@sap.com  Thu Jul  4 18:19:20 2013
Return-Path: <mrex@sap.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 4518E21F9957; Thu,  4 Jul 2013 18:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.899
X-Spam-Level: 
X-Spam-Status: No, score=-9.899 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GhTJQUG21OG; Thu,  4 Jul 2013 18:19:15 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 94A3821F83EF; Thu,  4 Jul 2013 18:19:15 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r651J8JC012493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 5 Jul 2013 03:19:08 +0200 (MEST)
Subject: Re: IETF 87 Registration Suspended
In-Reply-To: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
To: mrex@sap.com
Date: Fri, 5 Jul 2013 03:19:08 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20130705011908.697B91A87C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
X-Mailman-Approved-At: Fri, 05 Jul 2013 08:34:27 -0700
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, iaoc@ietf.org, IAB <iab@iab.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 05 Jul 2013 01:19:20 -0000

Martin Rex wrote:
> "Martin J. D=FCrst" wrote:
> >=20
> >On 2013/07/04 9:39, Barry Leiba wrote:
> >>> Registration for IETF87 in Berlin has been suspended to consider the =
impact
> >>> of a change in the VAT rules on Registration Fees.  We expect registr=
ation
> >>> to open as soon as this matter has been clarified.
> >>
> >> I don't understand what the effect of VAT rules is on money collected
> >> in the U.S. in U.S. Dollars.
> >=20
> > It's usual in the U.S. that taxes on goods bought and sold are levied a=
s=20
> > a consumption tax, at the place (i.e. in the state) where the object is=
=20
> > bought (and therefore presumably consumed/used).
> >=20
> > However, that's not a given, and VAT stands for value added tax, and th=
e=20
> > value addition/consumption can be presumed to happen at the meeting in=
=20
> > Berlin (and there's no need for consensus here, it's the opinion of the=
=20
> > local tax authority that counts :-().
>=20
>=20
> If the money that is collected is an entrance/participation fee for
> the venue itself, then the local tax authority might require the local
> VAT for _all_ visitors, even those that pay in advance or in a
> different country.

It seems that the rules might be somewhat similar all over europe:

   http://www.tmf-vat.com/vat/german-vat.html


-Martin

From l.wood@surrey.ac.uk  Thu Jul  4 23:41:38 2013
Return-Path: <l.wood@surrey.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 E51D911E8234; Thu,  4 Jul 2013 23:41:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4qtokMoUShm; Thu,  4 Jul 2013 23:41:34 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.148]) by ietfa.amsl.com (Postfix) with ESMTP id CED1A11E8255; Thu,  4 Jul 2013 23:41:32 -0700 (PDT)
Received: from [195.245.231.67:3824] by server-12.bemta-5.messagelabs.com id 17/FF-22750-A9A66D15; Fri, 05 Jul 2013 06:41:30 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-82.messagelabs.com!1373006489!30395373!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.9; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1693 invoked from network); 5 Jul 2013 06:41:30 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 5 Jul 2013 06:41:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 5 Jul 2013 07:41:29 +0100
From: <l.wood@surrey.ac.uk>
To: <mrex@sap.com>, <duerst@it.aoyama.ac.jp>
Date: Fri, 5 Jul 2013 07:40:28 +0100
Subject: RE: IETF 87 Registration Suspended
Thread-Topic: IETF 87 Registration Suspended
Thread-Index: Ac55HBbpEy+OSJiKT+iAinSXcNgHdwALnLrI
Message-ID: <290E20B455C66743BE178C5C84F12408223F494EDC@EXMB01CMS.surrey.ac.uk>
References: <51D4FA2D.3040601@it.aoyama.ac.jp>, <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
In-Reply-To: <20130705010654.ABCA31A87C@ld9781.wdf.sap.corp>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 05 Jul 2013 08:34:27 -0700
Cc: iaoc@ietf.org, barryleiba@computer.org, ietf@ietf.org, iab@iab.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, 05 Jul 2013 06:41:39 -0000

It strikes me that 'membership fees' as opposed to 'entrance fees' could wo=
rk around this payment issue. Or incur a different tax...

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Martin Rex=
 [mrex@sap.com]
Sent: 05 July 2013 02:06
To: "Martin J. D=FCrst"
Cc: iaoc@ietf.org; Barry Leiba; IETF discussion list; IAB; Working Group Ch=
airs
Subject: Re: IETF 87 Registration Suspended

"Martin J. D=FCrst" wrote:
>
>On 2013/07/04 9:39, Barry Leiba wrote:
>>> Registration for IETF87 in Berlin has been suspended to consider the im=
pact
>>> of a change in the VAT rules on Registration Fees.  We expect registrat=
ion
>>> to open as soon as this matter has been clarified.
>>
>> I don't understand what the effect of VAT rules is on money collected
>> in the U.S. in U.S. Dollars.
>
> It's usual in the U.S. that taxes on goods bought and sold are levied as
> a consumption tax, at the place (i.e. in the state) where the object is
> bought (and therefore presumably consumed/used).
>
> However, that's not a given, and VAT stands for value added tax, and the
> value addition/consumption can be presumed to happen at the meeting in
> Berlin (and there's no need for consensus here, it's the opinion of the
> local tax authority that counts :-().


If the money that is collected is an entrance/participation fee for
the venue itself, then the local tax authority might require the local
VAT for _all_ visitors, even those that pay in advance or in a
different country.


While it might be possible to make the necessary tweaks about the fee
(maybe not for this meeting, but for future meetings) for the WG sessions
themselves, this would be more difficult to argue for the
breakfast/buffet/brownies/beverages (I assume that still exists)
and the access to the terminal room, where some form of badge
checking is usually done in order to protect the resources.


-Martin


From agenda@ietf.org  Fri Jul  5 17:09:13 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 C4E6811E80F3; Fri,  5 Jul 2013 17:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.878
X-Spam-Level: 
X-Spam-Status: No, score=-101.878 tagged_above=-999 required=5 tests=[AWL=0.722, 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 rIkctQC1-Tp2; Fri,  5 Jul 2013 17:09:13 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 74BB811E80EE; Fri,  5 Jul 2013 17:09:13 -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: IETF 87 Final Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130706000913.15410.67606.idtracker@ietfa.amsl.com>
Date: Fri, 05 Jul 2013 17:09:13 -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: Sat, 06 Jul 2013 00:09:13 -0000

Hello Everyone!

The final agenda is ready for viewing.  Please take a moment to note your s=
ession and meeting room(s).  At this point only Area Directors can submit c=
hanges in the form of a swap to agenda@ietf.org.  Please let me know if you=
 have any questions.

https://datatracker.ietf.org/meeting/87/agenda.html
https://datatracker.ietf.org/meeting/87/agenda.txt

Information on the 87th IETF meeting in Berlin, Germany can be found here: =
http://www.ietf.org/meeting/87/index.html

Thank you!

Stephanie McCammon

From bclaise@cisco.com  Mon Jul  8 00:55:10 2013
Return-Path: <bclaise@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 4793021F9A4B for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 00:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.596
X-Spam-Level: 
X-Spam-Status: No, score=-10.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 dNNSE+piWzpC for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 00:54:53 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 0A59821F86D5 for <wgchairs@ietf.org>; Mon,  8 Jul 2013 00:54:49 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r687sacm006664; Mon, 8 Jul 2013 09:54:36 +0200 (CEST)
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r687rtZI025794; Mon, 8 Jul 2013 09:54:01 +0200 (CEST)
Message-ID: <51DA7013.5090400@cisco.com>
Date: Mon, 08 Jul 2013 09:53:55 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: An acceptable use for Internet-Drafts?
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net> <949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 08 Jul 2013 07:55:11 -0000

Fred,
> One uses Internet Drafts to provide a document to the ISE to publish, if the objective is publication as an RFC. So an Internet Draft is *necessary*.
>
> Since Internet Drafts have a lifetime beyond the stipulated 6 months (take a look athttp://tools.ietf.org/id/draft-ietf-mpsnmp-overipx-00.txt), they are useful for prior art searches. If the objective is to post prior art to prevent patent rights, it is a library that i used.
With the first to file change in patent policy, does it still make sense 
these days?
http://gigaom.com/2013/03/18/first-to-file-patent-law-starts-today-what-it-means-in-plain-english/

Regards, Benoit
> As to "bad idea", I would suggest putting it as seeking "experimental status" and say up front that this is an idea that is NOT RECOMMENDED, and give reasons for not recommending it.
>
> On Jul 1, 2013, at 3:56 PM, "DRAGE, Keith (Keith)"<keith.drage@alcatel-lucent.com>  wrote:
>
>> Internet-drafts are essentially a step to something else.
>>
>> Otherwise while they may be retained in the tools archive, they officially disappear six months after issue.
>>
>> So I would not regard it as a valid usage. The function you desire is one of the RFC types, probably not IETF track.
>>
>> Keith
>>
>>> -----Original Message-----
>>> From:wgchairs-bounces@ietf.org  [mailto:wgchairs-bounces@ietf.org] On
>>> Behalf Of Warren Kumari
>>> Sent: 01 July 2013 23:20
>>> To: WG Chairs
>>> Subject: An acceptable use for Internet-Drafts?
>>>
>>> Hi all,
>>>
>>> So, I recently published a draft ( "A questionable method for mitigating
>>> namespace collisions" -http://www.ietf.org/internet-drafts/draft-
>>> wkumari-dnsop-defense-collision-mitigate-00.txt ) purely so that the idea
>>> is documented somewhere, and hopefully someone won't go off and try patent
>>> it.
>>>
>>> As you can guess from the title I don't think that this is a particularity
>>> good idea (AKA, Bad Idea Fairy was visiting when I wrote it), but I think
>>> that if *anyone* tries to do this, then *everyone* should be free to try
>>> do it.
>>>
>>> In order to try and make this more clear, I put the word -defense- in the
>>> draft name.
>>> Does this seem like an acceptable use of the ID system? If so, should we
>>> try and make having -defense- or -defensive- in the draft name be an
>>> unwritten convention that we use?
>>> I figured best to chat about this here first, and then, possibly, on -
>>> discuss if folk think it is worth broader discussion.
>>>
>>> W
>>> --
>>> With Feudalism, it's your Count that votes.
>>>
>


From duerst@it.aoyama.ac.jp  Mon Jul  8 03:48:04 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 6F96221F8FBE for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 03:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.415
X-Spam-Level: 
X-Spam-Status: No, score=-101.415 tagged_above=-999 required=5 tests=[AWL=-1.625, 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 bgbzhmo2RNvP for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 03:47:59 -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 5A00521F9EC1 for <wgchairs@ietf.org>; Mon,  8 Jul 2013 03:47:55 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r68All3N021786; Mon, 8 Jul 2013 19:47:47 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 3b77_8672_d4030212_e7bb_11e2_bb54_001e6722eec2; Mon, 08 Jul 2013 19:47:47 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id D835EBF4DD; Mon,  8 Jul 2013 19:46:06 +0900 (JST)
Message-ID: <51DA98BB.9090307@it.aoyama.ac.jp>
Date: Mon, 08 Jul 2013 19:47:23 +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: Benoit Claise <bclaise@cisco.com>
Subject: Re: An acceptable use for Internet-Drafts?
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>	<949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>	<8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com> <51DA7013.5090400@cisco.com>
In-Reply-To: <51DA7013.5090400@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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, 08 Jul 2013 10:48:04 -0000

Hello Benoit,

On 2013/07/08 16:53, Benoit Claise wrote:
> Fred,
>> One uses Internet Drafts to provide a document to the ISE to publish,
>> if the objective is publication as an RFC. So an Internet Draft is
>> *necessary*.
>>
>> Since Internet Drafts have a lifetime beyond the stipulated 6 months
>> (take a look
>> athttp://tools.ietf.org/id/draft-ietf-mpsnmp-overipx-00.txt), they are
>> useful for prior art searches. If the objective is to post prior art
>> to prevent patent rights, it is a library that i used.
> With the first to file change in patent policy, does it still make sense
> these days?
> http://gigaom.com/2013/03/18/first-to-file-patent-law-starts-today-what-it-means-in-plain-english/

IANAL, but I'd assume that independent of "first to file" or "first to 
invent", prior art publication still trumps both.

Regards,   Martin.

From ietfdbh@comcast.net  Mon Jul  8 06:52:50 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 5A1B321F9C6B for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 06:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.37
X-Spam-Level: 
X-Spam-Status: No, score=-100.37 tagged_above=-999 required=5 tests=[AWL=0.067, 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 P+2zAAV-E6cN for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 06:52:46 -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 E008821F9BCB for <wgchairs@ietf.org>; Mon,  8 Jul 2013 06:52:45 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta07.westchester.pa.mail.comcast.net with comcast id xnmB1l0071swQuc57psloP; Mon, 08 Jul 2013 13:52:45 +0000
Received: from JV6RVH1 ([67.189.237.137]) by omta15.westchester.pa.mail.comcast.net with comcast id xpsk1l00z2yZEBF3bpskH5; Mon, 08 Jul 2013 13:52:45 +0000
From: "ietfdbh" <ietfdbh@comcast.net>
To: "'Benoit Claise'" <bclaise@cisco.com>, "'Fred Baker \(fred\)'" <fred@cisco.com>
References: <E64E5DFB-0472-4D2C-8D62-779177B5C9B8@kumari.net>	<949EF20990823C4C85C18D59AA11AD8B063C83@FR712WXCHMBA11.zeu.alcatel-lucent.com>	<8C48B86A895913448548E6D15DA7553B92DBD0@xmb-rcd-x09.cisco.com> <51DA7013.5090400@cisco.com>
In-Reply-To: <51DA7013.5090400@cisco.com>
Subject: RE: An acceptable use for Internet-Drafts?
Date: Mon, 8 Jul 2013 09:52:14 -0400
Message-ID: <003501ce7be2$5a8e1790$0faa46b0$@comcast.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK5MDjDisA4VHkN+qoOm3JnVOxSzAE4io+uARScvJcB0w+9G5dkYhLQ
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1373291565; bh=mGxs+O84OnMBf/xnqpROQUh0mfNUvk8x3ddwJI8Julw=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=UHZoAnfWaZKAHIU2l4Qm2fESwTAczxQxIq2rgMZn84wroQuB80M4RetI8vS5BPfim XBKrEJD84AVmcLvf3nVT3GgXBwXeFQpR/YAMXrURtGNSPS+d0u2ZdFHC/bpaflC/Df Kt//ApqMigBUYkD+A4L1SQYthkTXFZdjpPp5NazmInJbiAKlYgzbmrhUTPrQPJbxO9 NaFMItaJuNBHPv4xrQm/t99Y94Ez1zx0yEcAqCJsF1IfYsSruAJUmibA1likXU8P4I 2/0CRSJo/HRpSyK5uTRD1LUj3T+/+cL3V+F7JRqXTSxM+TjfUv/GEs9Ppc6mpYqc4+ a44NULtV397NA==
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, 08 Jul 2013 13:52:50 -0000

Don't miss this section in the description you pointed to:
"America has a special rule that will help inventors in many cases. The rule
says that if you disclose the invention at a conference or elsewhere, you
have a one year grace period to file a patent for it. This means that your
disclosure will prevent someone else from getting a patent on your invention
(but it could also harm your chances to get patents in other countries)."

So "establishing prior art" might only be useful regarding US patents, and
only good for a year, but it still could be important.

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

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Benoit Claise
> Sent: Monday, July 08, 2013 3:54 AM
> To: Fred Baker (fred)
> Cc: WG Chairs
> Subject: Re: An acceptable use for Internet-Drafts?
> 
> Fred,
> > One uses Internet Drafts to provide a document to the ISE to publish, if
the
> objective is publication as an RFC. So an Internet Draft is *necessary*.
> >
> > Since Internet Drafts have a lifetime beyond the stipulated 6 months
(take
> a look athttp://tools.ietf.org/id/draft-ietf-mpsnmp-overipx-00.txt), they
are
> useful for prior art searches. If the objective is to post prior art to
prevent
> patent rights, it is a library that i used.
> With the first to file change in patent policy, does it still make sense
these
> days?
>
http://gigaom.com/2013/03/18/first-to-file-patent-law-starts-today-what-it-
> means-in-plain-english/
> 
> Regards, Benoit
> > As to "bad idea", I would suggest putting it as seeking "experimental
> status" and say up front that this is an idea that is NOT RECOMMENDED, and
> give reasons for not recommending it.
> >
> > On Jul 1, 2013, at 3:56 PM, "DRAGE, Keith (Keith)"<keith.drage@alcatel-
> lucent.com>  wrote:
> >
> >> Internet-drafts are essentially a step to something else.
> >>
> >> Otherwise while they may be retained in the tools archive, they
officially
> disappear six months after issue.
> >>
> >> So I would not regard it as a valid usage. The function you desire is
one of
> the RFC types, probably not IETF track.
> >>
> >> Keith
> >>
> >>> -----Original Message-----
> >>> From:wgchairs-bounces@ietf.org  [mailto:wgchairs-bounces@ietf.org]
> >>> On Behalf Of Warren Kumari
> >>> Sent: 01 July 2013 23:20
> >>> To: WG Chairs
> >>> Subject: An acceptable use for Internet-Drafts?
> >>>
> >>> Hi all,
> >>>
> >>> So, I recently published a draft ( "A questionable method for
> >>> mitigating namespace collisions"
> >>> -http://www.ietf.org/internet-drafts/draft-
> >>> wkumari-dnsop-defense-collision-mitigate-00.txt ) purely so that the
> >>> idea is documented somewhere, and hopefully someone won't go off
> and
> >>> try patent it.
> >>>
> >>> As you can guess from the title I don't think that this is a
> >>> particularity good idea (AKA, Bad Idea Fairy was visiting when I
> >>> wrote it), but I think that if *anyone* tries to do this, then
> >>> *everyone* should be free to try do it.
> >>>
> >>> In order to try and make this more clear, I put the word -defense-
> >>> in the draft name.
> >>> Does this seem like an acceptable use of the ID system? If so,
> >>> should we try and make having -defense- or -defensive- in the draft
> >>> name be an unwritten convention that we use?
> >>> I figured best to chat about this here first, and then, possibly, on
> >>> - discuss if folk think it is worth broader discussion.
> >>>
> >>> W
> >>> --
> >>> With Feudalism, it's your Count that votes.
> >>>
> >


From johnl@iecc.com  Mon Jul  8 09:28:32 2013
Return-Path: <johnl@iecc.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 B86FF21F9349 for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 09:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.573
X-Spam-Level: 
X-Spam-Status: No, score=-110.573 tagged_above=-999 required=5 tests=[AWL=0.626, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WhZ7lHf5Jgp for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 09:28:22 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CD4BE21F9CAA for <wgchairs@ietf.org>; Mon,  8 Jul 2013 09:28:21 -0700 (PDT)
Received: (qmail 90989 invoked from network); 8 Jul 2013 16:28:20 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Jul 2013 16:28:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dae8a4.xn--i8sz2z.k1307; i=johnl@user.iecc.com; bh=zG+20kKoquPYb3I/U7zgj1LcphR1qpG8DImQhKYNeEE=; b=ejy1FjF0sj4fR1vGpwkVDXWNWuYXPcxeMsEcYUF5EEc/1n9S228UDygqF9MyduwublkOaJezPkRIt0lEsLwzyH7A52HYsAnZzWDvRNEYfxzdTsChP8OtoWqTUAylUALSuGOm4EJEyUCi0chCtXWYdTgUPNNQBEvKMJxkTAGxs/QYC6Gp2f9uhxDd446OOZvXyJdjjPo1OS1BwtMGEgUO2I+kOkfPnsK8FIAj5UcaF7HqcTU1mqJp6i4602SsPMCL
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dae8a4.xn--i8sz2z.k1307; olt=johnl@user.iecc.com; bh=zG+20kKoquPYb3I/U7zgj1LcphR1qpG8DImQhKYNeEE=; b=K8eXSIyXu0WHe0km/DJN+32OIalLBPdlW/61HHWOXGOyVhlq4pIasaj6dM0nEB0+Bbn+K5KdQHJzgCPflhHomo8YXzwt7518JSNa4tWacRZUpkAcIrBrAMM6RpYTT2fjcwXISqC5Rgw78p67tLOScmTTTSW6mksdoyaQUp5+Wsrw2XslxyUmX4bwYuOOC5wBFHeMi+anjykylBuPFl8Fk5+kmlVQMGoGkcD7wN4UI9CUCsG8DbXJa5iUICln98nb
Date: 8 Jul 2013 16:27:58 -0000
Message-ID: <20130708162758.70068.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: wgchairs@ietf.org
Subject: Re: An acceptable use for Internet-Drafts?
In-Reply-To: <51DA7013.5090400@cisco.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
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, 08 Jul 2013 16:28:32 -0000

>With the first to file change in patent policy, does it still make sense these days?

First to file only affects priority between two applications for the same thing.

Prior art affects whether something can be patented at all.  So yes,
disclosing prior art is still very useful.

R's,
John

From johnl@iecc.com  Mon Jul  8 09:32:14 2013
Return-Path: <johnl@iecc.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 5E07421F9CB3 for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 09:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.592
X-Spam-Level: 
X-Spam-Status: No, score=-110.592 tagged_above=-999 required=5 tests=[AWL=0.607, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61e2DPPK8kmX for <wgchairs@ietfa.amsl.com>; Mon,  8 Jul 2013 09:32:10 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E2ADF21F8EEA for <wgchairs@ietf.org>; Mon,  8 Jul 2013 09:32:09 -0700 (PDT)
Received: (qmail 91852 invoked from network); 8 Jul 2013 16:32:08 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Jul 2013 16:32:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dae988.xn--i8sz2z.k1307; i=johnl@user.iecc.com; bh=cv3YWeAtAKynCExkXmt4cRFhsNTN6awRsjcmI65nmjg=; b=YuKmK0+V6UvRAlTEZOdcmrg3/me8j0lKrbw/PuCG/4Smbu7aWLrtHUa9qJWwqSuiCoPZGxc/Nd8T/v66nYMxJt/IpWL4hnaIxGuz6O/61I7+nc/gpYMCG3RE8/URcbs7+B8P/11YIvwA+pNcx652eHkgPc470bY38Qo80JDOWsXAQcPWtz5iRkTzKj7I4fLtfRAQ/CXJ202i2i4I+8qRlHm9KYkLSTBZC786pdSzV02kKoRb+scTSKD63md1sao4
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51dae988.xn--i8sz2z.k1307; olt=johnl@user.iecc.com; bh=cv3YWeAtAKynCExkXmt4cRFhsNTN6awRsjcmI65nmjg=; b=LVH+h6gqQmJukIubBVLYsxe+bVfqpojApdbBubUvOPKm1CUid9FEN6d0Vzm1rEC3xVgP+3QncjSWzTKYJvkF3zPIds+NYDPeixKrbQPDQ1uJEahyJR+J5ZGgpu1KFAT5nK19MzwvLCXnm7krgTT/bpMiH05KFqcQKxXOVPrY6KhXSS2zaCKhxxBeOqV48wglnJTcb8QrUNL4C3XIyh4+xrjP8e+02Z5kKjwFnBZdEKQTLI4/0Nw0nWlLlwYecLvO
Date: 8 Jul 2013 16:31:46 -0000
Message-ID: <20130708163146.70096.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: wgchairs@ietf.org
Subject: Re: An acceptable use for Internet-Drafts?
In-Reply-To: <003501ce7be2$5a8e1790$0faa46b0$@comcast.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
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, 08 Jul 2013 16:32:14 -0000

>So "establishing prior art" might only be useful regarding US patents, and
>only good for a year, but it still could be important.

No, that's something else.

The point of making a public disclosure about something you've
invented and aren't planning to patent, or that you are aware of but
isn't written down anywhere, is that once it's disclosed, nobody else
can patent it, ever.*  This is a fundamental rule of patent law in the U.S.
and, I am fairly sure, in all other countries.

R's,
John

* - well, unless they can prove that they invented it before you
disclosed it but still file within the one year window, and that's
pretty rare

From agenda@ietf.org  Mon Jul  8 10:17:06 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 98B0821F995F; Mon,  8 Jul 2013 10:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.981
X-Spam-Level: 
X-Spam-Status: No, score=-101.981 tagged_above=-999 required=5 tests=[AWL=0.619, 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 DJZiyJ63FvZj; Mon,  8 Jul 2013 10:17:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BE44021F9D7C; Mon,  8 Jul 2013 10:17:05 -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: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130708171705.14629.98393.idtracker@ietfa.amsl.com>
Date: Mon, 08 Jul 2013 10:17:05 -0700
Cc: edu-team@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Mon, 08 Jul 2013 17:17:07 -0000

Hello Everyone,

We will be holding a WG Chairs training lunch at IETF 87 in Berlin.  All cu=
rrent WG chairs, BOF chairs, IRTF chairs, and IESG members are welcome to a=
ttend. The lunch training will take place on Wednesday, July 31st, 2013 at =
11:30am, location TBD, and a complementary lunch will be provided.

The topic of the training will be the WG Chair portion of the datatracker. =
 It will be moderated by Margaret Wasserman.

If you would like to attend this session, please fill out the survey here h=
ttp://www.surveymonkey.com/s/ZRKLYSZ prior to the cutoff on July 19th, 2013=
. The location will be sent to those who RSVP.

If you have RSVP'd for the training lunch but will not be able to attend, p=
lease send a message to agenda@ietf.org.  =



Thank You!

Stephanie McCammon
(on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)

From caozhen@chinamobile.com  Thu Jul 11 00:22:24 2013
Return-Path: <caozhen@chinamobile.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 D2B1C21F99FB for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 00:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level: 
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RELAY_IS_221=2.222]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qXqeLwt2b4ZL for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 00:22:20 -0700 (PDT)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id 5787E21F9377 for <wgchairs@ietf.org>; Thu, 11 Jul 2013 00:22:20 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.12]) by rmmx-oa_allagent01-12001 (RichMail) with SMTP id 2ee151de5cd7f36-80f36; Thu, 11 Jul 2013 15:20:55 +0800 (CST)
X-RM-TRANSID: 2ee151de5cd7f36-80f36
Received: from cmccPC (unknown[10.2.52.226]) by rmsmtp-oa_rmapp02-12002 (RichMail) with SMTP id 2ee251de5cd6f58-12b79; Thu, 11 Jul 2013 15:20:55 +0800 (CST)
X-RM-TRANSID: 2ee251de5cd6f58-12b79
From: "Cao Zhen \(CZ\)" <caozhen@chinamobile.com>
To: "IETF WG Chairs" <wgchairs@ietf.org>
Subject: Drafts on how to call and pronounce Chinese names
Date: Thu, 11 Jul 2013 15:21:52 +0800
Message-ID: <00f501ce7e07$50eea110$f2cbe330$@chinamobile.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5+BpiQk45/zRyORkub2FB7fJ+1XA==
Content-Language: zh-cn
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, 11 Jul 2013 07:22:25 -0000

Hello Everyone,=20

Please be aware that there are drafts to refer for Chinese names and =
pronunciation tips. Your advice to improve these documents are highly =
appreciated.=20

http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00

Best regards,
caozhen
---------- Forwarded message ----------
From: Hui Deng <denghui02@gmail.com>
Date: Thu, Jul 11, 2013 at 8:04 AM
Subject: Regarding call Chinese names
To: IETF Discussion <ietf@ietf.org>


Hello all
=20
We submitted two drafts to help people here to correctly call chinese =
people names:

http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20

http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00

=20

Feel free to let us know if you have any other issues?

Best regards,




From ietf-secretariat@ietf.org  Thu Jul 11 07:34:02 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 5AC8011E81A5; Thu, 11 Jul 2013 07:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.6
X-Spam-Level: 
X-Spam-Status: No, score=-106.6 tagged_above=-999 required=5 tests=[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 AThFaofLn3HU; Thu, 11 Jul 2013 07:34:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B423F11E812B; Thu, 11 Jul 2013 07:33:59 -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 87 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130711143359.31050.74630.idtracker@ietfa.amsl.com>
Date: Thu, 11 Jul 2013 07:33:59 -0700
Cc: wgchairs@ietf.org, 87all@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: Thu, 11 Jul 2013 14:34:02 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

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

1.  Registration
2.  Social Event
3.  Sponsor Web page
4.  Visas & Letters of Invitation
5.  Accommodations
6.  Companion Program
7.  Childcare Information

1. Registration
A. Early-Bird Registration - USD 650.00 Pay by Friday, 19 July 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. All fees include 19% VAT
F. Registration Cancellation   =

          Cut-off for registration cancellation is Monday,
          22 July 2013 at UTC 24:00.
          Cancellations are subject to a 10% (ten percent)
          cancellation fee if requested by that date and time.
G. Online Registration and Payment ends Friday, 26 July 2013, 1700 local Be=
rlin time.
H. On-site Registration starting Sunday, 28 July 2013 at 1100 local Berlin =
time.

2.  Social Event
IETF87's social event sponsored by DENIC will be held at the famous German =
Museum of Technology (Deutsches Technikmuseum) in Berlin on Tuesday, 30 Jul=
y 2013 from 19:00 to 24:00

Shuttles will be provided from/to the Intercontinental starting at 18:30. Y=
ou may also walk to the museum (directions will be available soon). It will=
 take you about 30 minutes.

The cost is $30 USD per person. 475 tickets will be available, due to the e=
xpected demand, registration is limited to IETF87 attendees and one guest. =


For more information or to purchase tickets, please visit:
http://www.ietf.org/meeting/87/social.html

3. Sponsor Web Page
DENIC, the Platinum sponsor for IETF 87 has created a web page with informa=
tion about Berlin, the URL is: http://www.ietf87.de/

4. Visas & Letters of Invitation:
For information on Visiting Germany, please visit:
http://www.auswaertiges-amt.de/EN/EinreiseUndAufenthalt/Visabestimmungen_no=
de.html

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 emai=
l.

Please note that the IETF Letter of Invitation may not be sufficient for ob=
taining a visa to enter Germany.

5.  Accommodations
Currently the venue hotel (InterContinental) and overflow hotel (Pullman) a=
re both fully booked. The following hotels are near the InterContinental th=
ough we are not holding blocks at any of them.

Pestana
http://www.pestana.com/en/pestana-berlin-tiergarten-hotel/pages/home.aspx
Distance from InterContinental: approximately 1-2 minute walk

Hotel Berlin
http://www.hotel-berlin.de/en/hotel-berlin.html
Distance from InterContinental: approximately 5-7 minute walk

Das Stue Hotel
http://www.das-stue.com/en/
Distance from InterContinental: approximately 7-10 minute walk
guest room rates at both the InterContinetnal and Pullman include breakfast.

6.  Companion Program
If you are traveling with a friend or family member over 18 years of age yo=
u 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, 28 J=
uly
- Ability to attend the official Welcome Reception from 1700-1900 on Sunday=
, 28 July
- A distinctive meeting badge that grants access to the venue (not to be us=
ed to attend working sessions)
- Participation in a separate companion email list if you choose to help co=
mmunicate 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 87 companions mailing list only see:
https://www.ietf.org/mailman/listinfo/87companions

7.  Childcare Information
If you are staying at the InterContinental or the Pullman and are intereste=
d in childcare services, please contact the concierge at the respective hot=
el to get more information or to make arrangements. You can email the Inter=
Continental at <berha.concierge@ihg.com> and the Pullman at <pullman@berlin=
concierge.de>

Only 17 days until the Berlin IETF!

From margaretw42@gmail.com  Thu Jul 11 05:12:10 2013
Return-Path: <margaretw42@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 7F6AD21F9B90 for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 05:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwBeANlQMFFc for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 05:12:10 -0700 (PDT)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id E191121F98AC for <wgchairs@ietf.org>; Thu, 11 Jul 2013 05:12:09 -0700 (PDT)
Received: by mail-vc0-f177.google.com with SMTP id hv10so6511026vcb.8 for <wgchairs@ietf.org>; Thu, 11 Jul 2013 05:12:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Rki5g5sPuVccp63HXqwbYomcfAKOHtD/q7PzuVcjazA=; b=g09y4R4kCj3VlsT3Am7kUUeOMNMc7MHCZYCdY2wQiVbm8e+LpO3GCzHlGvQ+Jq2P+1 smm6btUkvWQxNJCL4d0mG/eJuPtaJwFcBR2Zau01ZrabDw1PrTTtJet2SbGdziY0p5Bp 6IWQivM+oOCPTFIuCNYjj8eQ2d1Mo4ugcJDC2zVCjPO34GgHyt64Hy+/4lDtpUk5L/rF VxPdXZUQa4/YsxoF/0Zk/0pP7KkpqtSL56KfUd5NB3Dd+MMk+8OTEejWTXGA4e30ybJr +Afblyz47EHa7Q7PWGOoE3JsAEPHlYr6vW0yVGxrCB22ZIaF+At9SkUZwTkC7OZhIaBh 18Cg==
X-Received: by 10.220.162.200 with SMTP id w8mr21497907vcx.90.1373544728996; Thu, 11 Jul 2013 05:12:08 -0700 (PDT)
Received: from new-host-3.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPSA id 20sm29455024vde.3.2013.07.11.05.12.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 05:12:06 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Drafts on how to call and pronounce Chinese names
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <00f501ce7e07$50eea110$f2cbe330$@chinamobile.com>
Date: Thu, 11 Jul 2013 08:12:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B00597E8-F8CF-43DE-8A3A-53D83B2DA8E3@gmail.com>
References: <00f501ce7e07$50eea110$f2cbe330$@chinamobile.com>
To: "Cao Zhen \(CZ\)" <caozhen@chinamobile.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Thu, 11 Jul 2013 08:09:15 -0700
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: Thu, 11 Jul 2013 12:12:10 -0000

Well done!  Thank you for sharing these with us.

Margaret


On Jul 11, 2013, at 3:21 AM, "Cao Zhen \(CZ\)" <caozhen@chinamobile.com> =
wrote:

> Hello Everyone,=20
>=20
> Please be aware that there are drafts to refer for Chinese names and =
pronunciation tips. Your advice to improve these documents are highly =
appreciated.=20
>=20
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
> http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>=20
> Best regards,
> caozhen
> ---------- Forwarded message ----------
> From: Hui Deng <denghui02@gmail.com>
> Date: Thu, Jul 11, 2013 at 8:04 AM
> Subject: Regarding call Chinese names
> To: IETF Discussion <ietf@ietf.org>
>=20
>=20
> Hello all
>=20
> We submitted two drafts to help people here to correctly call chinese =
people names:
>=20
> http://tools.ietf.org/html/draft-deng-call-chinese-names-00=20
>=20
> http://tools.ietf.org/html/draft-zcao-chinese-pronounce-00
>=20
>=20
>=20
> Feel free to let us know if you have any other issues?
>=20
> Best regards,
>=20
>=20
>=20


From acooper@cdt.org  Thu Jul 11 11:15:10 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 554F321F9FCA for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 11:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTATyOzoigXD for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 11:15:05 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 99E5321F9FD7 for <wgchairs@ietf.org>; Thu, 11 Jul 2013 11:14:52 -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)) for wgchairs@ietf.org; Thu, 11 Jul 2013 14:14:47 -0400
From: Alissa Cooper <acooper@cdt.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Trial of privacy tutorial at IETF 87
Message-Id: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
Date: Thu, 11 Jul 2013 14:14:48 -0400
To: IETF WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
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, 11 Jul 2013 18:15:10 -0000

Hi all,

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

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.

Thanks,
Alissa=


From derek@ihtfp.com  Thu Jul 11 12:20:55 2013
Return-Path: <derek@ihtfp.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 230A921F9B26 for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 12:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.988
X-Spam-Level: 
X-Spam-Status: No, score=-101.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agTLd7djAigF for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 12:20:50 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) by ietfa.amsl.com (Postfix) with ESMTP id B18C921F9A8C for <wgchairs@ietf.org>; Thu, 11 Jul 2013 12:20:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 4C8E5260248; Thu, 11 Jul 2013 15:20:49 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 16432-04; Thu, 11 Jul 2013 15:20:46 -0400 (EDT)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id C3466260299; Thu, 11 Jul 2013 15:20:46 -0400 (EDT)
Received: from fe80::224:d7ff:fee7:8924 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Thu, 11 Jul 2013 15:20:46 -0400
Message-ID: <8a67716648642c76b9a2f1f0775264f1.squirrel@mail2.ihtfp.org>
In-Reply-To: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
Date: Thu, 11 Jul 2013 15:20:46 -0400
Subject: Re: Trial of privacy tutorial at IETF 87
From: "Derek Atkins" <derek@ihtfp.com>
To: "Alissa Cooper" <acooper@cdt.org>
User-Agent: SquirrelMail/1.4.22-2.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
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: Thu, 11 Jul 2013 19:20:55 -0000

Is that AM or PM?

-derek

On Thu, July 11, 2013 2:14 pm, Alissa Cooper wrote:
> Hi all,
>
> 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.
>
> 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.
>
> Thanks,
> Alissa
>


-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant


From acooper@cdt.org  Thu Jul 11 12:55:17 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 A719221F9808 for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 12:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXB538x0uxkh for <wgchairs@ietfa.amsl.com>; Thu, 11 Jul 2013 12:55:12 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 440E211E8156 for <wgchairs@ietf.org>; Thu, 11 Jul 2013 12:55:01 -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)) for wgchairs@ietf.org; Thu, 11 Jul 2013 15:54:46 -0400
Content-Type: text/plain; charset=iso-8859-1
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>
X-Priority: 3 (Normal)
In-Reply-To: <8a67716648642c76b9a2f1f0775264f1.squirrel@mail2.ihtfp.org>
Date: Thu, 11 Jul 2013 15:54:48 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <2C9242ED-91E8-4BDF-9748-4F17FC08CFD6@cdt.org>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org> <8a67716648642c76b9a2f1f0775264f1.squirrel@mail2.ihtfp.org>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1499)
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, 11 Jul 2013 19:55:17 -0000

9:15am to 10:30am

On Jul 11, 2013, at 3:20 PM, Derek Atkins <derek@ihtfp.com> wrote:

> Is that AM or PM?
> 
> -derek
> 
> On Thu, July 11, 2013 2:14 pm, Alissa Cooper wrote:
>> Hi all,
>> 
>> 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.
>> 
>> 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.
>> 
>> Thanks,
>> Alissa
>> 
> 
> 
> -- 
>       Derek Atkins                 617-623-3745
>       derek@ihtfp.com             www.ihtfp.com
>       Computer and Internet Security Consultant
> 
> 



From alper.yegin@yegin.org  Sat Jul 13 04:38:59 2013
Return-Path: <alper.yegin@yegin.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 3C27E21F9C4F for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 04:38: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 xxP562-we1JC for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 04:38:44 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 9365621F9C15 for <wgchairs@ietf.org>; Sat, 13 Jul 2013 04:38:44 -0700 (PDT)
Received: from [172.20.10.4] ([176.219.146.133]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LsU1Q-1U0jkj3IJU-012sJa; Sat, 13 Jul 2013 07:38:26 -0400
Subject: Re: Trial of privacy tutorial at IETF 87
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
Date: Sat, 13 Jul 2013 14:38:19 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <18D1551E-5D4D-4C7C-9EBD-B01B3EFC9D0E@yegin.org>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org>
To: Alissa Cooper <acooper@cdt.org>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:Lt9dW8905FHdDq7tNaSisSBJQ7YEDLNRYeauEOK7it6 rSLpP2FeQ91N2Q+ixS+/uF6YwmssRHBzlDTJ0ZBm5CWImEDq3u IiuAYSgxIccFVtSaLEOJy6K27/yqXvC2gcEma8zzFEOzcjOegv ZViFrYL85ADkMnzvffWV6xo21gPqvOpqUBGq8DLoo62LUmn6bK JrC/6du0LkHRGS5m5iaeYc3QOTOmZe80NDJn2mJTSTcZ6AkQW7 Rkiklqn2xZGUCf6lWUch309XEELWf+TVH9OEWMljhN6bqKqKBB W1Pj9t3OVprIQYJOM1Lce92eSh8ba1SqKyMaAdinAaoZQezZ5x m5o9msZ4a65CgMigDRjJ741wn85la0qE8h0WwxEW35hPfdOFKl mmQpmzUaTsrdg==
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: Sat, 13 Jul 2013 11:38:59 -0000

Hi Alissa,

I'd have liked to attend, but I'm arriving later on Sunday.
Nevertheless, if you can share the slides, I can provide offline =
feedback.

Thank you.

Alper

On Jul 11, 2013, at 9:14 PM, Alissa Cooper 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


From hannes.tschofenig@gmx.net  Sat Jul 13 06:04:19 2013
Return-Path: <hannes.tschofenig@gmx.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 9C8F021F9D8A for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:04:19 -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 VjfJrFi+OlYF for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:04:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1B421F9D65 for <wgchairs@ietf.org>; Sat, 13 Jul 2013 06:04:05 -0700 (PDT)
Received: from [172.16.254.104] ([80.92.118.93]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LqALY-1UTJUx2WPI-00dotj; Sat, 13 Jul 2013 15:03:48 +0200
Subject: Re: Trial of privacy tutorial at IETF 87
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <18D1551E-5D4D-4C7C-9EBD-B01B3EFC9D0E@yegin.org>
Date: Sat, 13 Jul 2013 15:03:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8190FE49-6064-40E2-ADC0-A02A13171E57@gmx.net>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org> <18D1551E-5D4D-4C7C-9EBD-B01B3EFC9D0E@yegin.org>
To: Alper Yegin <alper.yegin@yegin.org>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
X-Provags-ID: V03:K0:1snK3Zk2ATbuDopFvxLbJSp44bAJKnZzamgciOKRtKsPge7jMvS L1sGHTiLIr5zcux4FDHQgKzeeBYvX5NkHEXOXd71udflPr2HkZKqOtOx+k3X/T+ar6TDYzd ITXfUNobgE7TnhoplHZFWLpC+m5k1rzgO/QLIpakhMhIf9JghwipiK8aAT8g3f0rgRZibRP G6bh1KyDoBU+an9p7VbKg==
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: Sat, 13 Jul 2013 13:04:19 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Of course the main purpose of the talk for us is to learn from the =
discussion the presentation generates.=20
Still, the slides will be made available and we could also do a video =
recording for you.=20

On Jul 13, 2013, at 1:38 PM, Alper Yegin wrote:

> Hi Alissa,
>=20
> I'd have liked to attend, but I'm arriving later on Sunday.
> Nevertheless, if you can share the slides, I can provide offline =
feedback.
>=20
> Thank you.
>=20
> Alper
>=20
> On Jul 11, 2013, at 9:14 PM, Alissa Cooper wrote:
>=20
>> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR4VAyAAoJEGhJURNOOiAt9f0H/1MXWw+kxQ0P/q8qsdpNcuPo
YPCd41Oke75VRmY7+YrTo+3nXzq4t44dITmNC/bv/tpGUyam1gRZUhHaAFSonK/J
H03IT1uHaorXL9ge6f0y3p3Cyizsh2ImjKeOe6vGSTU4uRbh0WbsjTe9OMxOJL99
fQdmO32fCyYo9lZqUFPiT5/AUX0ANaRaD4FQlJkcDRsJFEVyps5XwvwWOOj4swem
zro//mXKtYRQqvAVXclj8/h0krm0D5BhLQ3Le9ZRn8WCf3xKboOZkM1n4w3AJCHo
D1DMHEgXegjqo8DKVZN942c6RQfUOEglC817TgCWbLHHAHUruBD8rRSI8BhkoMg=3D
=3DucqE
-----END PGP SIGNATURE-----

From dcrocker@bbiw.net  Sat Jul 13 06:20:29 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 7CDA221F9D92 for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:20:29 -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 Uejmn97CmC4F for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:20:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D9B7121F9D98 for <wgchairs@ietf.org>; Sat, 13 Jul 2013 06:20:18 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6DDKBtf003248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 13 Jul 2013 06:20:14 -0700
Message-ID: <51E153EE.50704@bbiw.net>
Date: Sat, 13 Jul 2013 06:19:42 -0700
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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Trial of privacy tutorial at IETF 87
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org> <18D1551E-5D4D-4C7C-9EBD-B01B3EFC9D0E@yegin.org> <8190FE49-6064-40E2-ADC0-A02A13171E57@gmx.net>
In-Reply-To: <8190FE49-6064-40E2-ADC0-A02A13171E57@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Sat, 13 Jul 2013 06:20:14 -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: Sat, 13 Jul 2013 13:20:29 -0000

On 7/13/2013 6:03 AM, Hannes Tschofenig wrote:
> Still, the slides will be made available and we could also do a video recording for you.

That would be great.  Thanks.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jhaas@slice.pfrc.org  Sun Jul 14 17:38:55 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 C0F5521F9344 for <wgchairs@ietfa.amsl.com>; Sun, 14 Jul 2013 17:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9mgLaoYpsLf for <wgchairs@ietfa.amsl.com>; Sun, 14 Jul 2013 17:38:50 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C246921F93DB for <wgchairs@ietf.org>; Sun, 14 Jul 2013 17:38:50 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 7BECFC633; Sun, 14 Jul 2013 20:38:50 -0400 (EDT)
Date: Sun, 14 Jul 2013 20:38:50 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: New "Note Well" summary slide from the IESG
Message-ID: <20130715003850.GD6523@pfrc>
References: <518AA25F.7000404@gmail.com> <1AA58DD1-20A1-45D2-A2AC-BF6FABCED014@ogud.com> <72C77D5A-4CDA-410D-AF47-E2F7B65ADFC8@gmail.com> <1AE17A13-8EEE-4327-BC98-2F207AF0D623@cisco.com> <518C2387.7000903@sunet.se> <7F008231-F24C-4F3D-A773-86DF68F2DF69@kumari.net> <FE19ED34-3A83-4CE3-823B-850AE7CA31C2@standardstrack.com> <4842D9D7-C9BB-4837-A012-E1EF3F9E5052@icann.org> <51918C3A.3080905@qti.qualcomm.com> <51919758.8090704@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51919758.8090704@bbiw.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Mon, 15 Jul 2013 00:38:55 -0000

On Mon, May 13, 2013 at 06:46:00PM -0700, Dave Crocker wrote:
> Perhaps the slide should be cast as an oath, and begin with:
> 
> 
>    Repeat after me:

Arguably, one could say the following:
"Who here has read and agrees to comply with BCP 79?  Please raise your
hands."

"Those of you who have not raised their hands should leave the meeting."

This is arguably too strict since I believe listen-only participants have
fewer responsibilities.

-- Jeff

From kwiereng@cisco.com  Sat Jul 13 06:23:14 2013
Return-Path: <kwiereng@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 2FF3A21F91BC for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0dqD--Eru3k for <wgchairs@ietfa.amsl.com>; Sat, 13 Jul 2013 06:23:02 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1B321F91BF for <wgchairs@ietf.org>; Sat, 13 Jul 2013 06:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=492; q=dns/txt; s=iport; t=1373721783; x=1374931383; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=LCOoDUvN+IiVsnQylWEDQGwhLwLGwOkiN1w8u8fHb5o=; b=eYTxBesmtyGV1a9MGt7Z492PjABvd7++gJThdIuV/YlDvTQ5PNtK+KC3 9K1HWlLVhNjGpv5DhK5F/PHsWKhLPL8BB+bCO1v1QiK6RbDuboiOsMSWt K9ak3zytCjHgvOiGTQp5ZkLUbUEVhjPV+wJDIBwO0UFERUWvSinamA1fd 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAFABBU4VGtJXHA/2dsb2JhbABagwY0gw6/GYEIFnSCIwEBAQMBOj8FCwIBCA4KHhAyJQIEDgWICQa3BY8wMweDC2wDl1yBKZAkgxI
X-IronPort-AV: E=Sophos;i="4.89,659,1367971200"; d="scan'208";a="231409852"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 13 Jul 2013 13:23:03 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6DDN1Hu031866 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 13 Jul 2013 13:23:01 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.22]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Sat, 13 Jul 2013 08:23:01 -0500
From: "Klaas Wierenga (kwiereng)" <kwiereng@cisco.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Trial of privacy tutorial at IETF 87
Thread-Topic: Trial of privacy tutorial at IETF 87
Thread-Index: AQHOfmKkDaIAasCmMkua672ItvIaeZli0f2AgAAX4ACAAAR0AP//rRwQ
Date: Sat, 13 Jul 2013 13:23:01 +0000
Message-ID: <3E2A18E6-E7E6-4CC5-86C1-F64E6110BC09@cisco.com>
References: <13EB70E7-1834-45CB-BC1C-9E4C52F81E81@cdt.org> <18D1551E-5D4D-4C7C-9EBD-B01B3EFC9D0E@yegin.org> <8190FE49-6064-40E2-ADC0-A02A13171E57@gmx.net>, <51E153EE.50704@bbiw.net>
In-Reply-To: <51E153EE.50704@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 15 Jul 2013 09:08:43 -0700
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: Sat, 13 Jul 2013 13:23:14 -0000

Sent from my iPad

On 13 jul. 2013, at 15:20, "Dave Crocker" <dcrocker@bbiw.net> wrote:

> On 7/13/2013 6:03 AM, Hannes Tschofenig wrote:
>> Still, the slides will be made available and we could also do a video re=
cording for you.
>=20
> That would be great.  Thanks.

Indeed, I may not make this IETF at all (baby refusing to come out) but wou=
ld love to see slides/recording

Klaas

>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From agenda@ietf.org  Mon Jul 15 12:35:37 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 B5DEC21E815D; Mon, 15 Jul 2013 12:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.018
X-Spam-Level: 
X-Spam-Status: No, score=-102.018 tagged_above=-999 required=5 tests=[AWL=0.582, 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 WOTd27vxyfI7; Mon, 15 Jul 2013 12:35:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1333021E816D; Mon, 15 Jul 2013 12:35:31 -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: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130715193531.10405.94711.idtracker@ietfa.amsl.com>
Date: Mon, 15 Jul 2013 12:35:31 -0700
Cc: edu-team@ietf.org, 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: Mon, 15 Jul 2013 19:35:37 -0000

Hello Everyone,

This is a reminder that the cut-off to register for the WG Chair Lunch Trai=
ning is this Friday, July 19th.  Please fill out the survey (http://www.sur=
veymonkey.com/s/ZRKLYSZ) to RSVP for this event if you have not already don=
e so.  =


If you have RSVP'd for the training lunch but will not be able to attend, p=
lease send a message to agenda@ietf.org.  =


WG Chairs' Training Lunch Information:

Date: July 31st, 2013
Time: 11:30 am
Location: TBA
Topic: The WG Chair portion of the datatracker (moderated by Margaret Wasse=
rman).

Lunch will be provided.  All current WG chairs, BOF chairs, IRTF chairs, an=
d IESG members are welcome to attend.

Thank you!

Stephanie McCammon
(on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)






From thomas.morin@orange.com  Tue Jul 16 05:07:30 2013
Return-Path: <thomas.morin@orange.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 27C7621F9C2E for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcWG8XtuxAoA for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:07:25 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id B3DCD21F9C19 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:07:24 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 3605A2DC5F5 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 14:07:23 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 1686B35C045 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 14:07:23 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 14:07:22 +0200
From: <thomas.morin@orange.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpg==
Date: Tue, 16 Jul 2013 12:07:22 +0000
Message-ID: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6F6B22849DA902449B065AE476183B4F@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.91239
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, 16 Jul 2013 12:07:30 -0000

SGkgZXZlcnlvbmUsDQoNCkl0IGlzIG5vdCB1bnVzdWFsIHRoYXQgcGVvcGxlIHdhaXQgZm9yIGhh
dmluZyBzdWJtaXR0ZWQgdGhlaXIgZHJhZnRzIA0KYmVmb3JlIGFza2luZyBmb3IgcHJlc2VudGF0
aW9uIHNsb3RzLg0KDQpXaXRoIHRoZSBjaGFuZ2UgaW4gLTAwLy0wMSBkcmFmdCBzdWJtaXNzaW9u
IGN1dC1vZmYgZGF0ZXMsIHRoaXMgdGltZSB3ZSANCmhhdmUgaGF2ZSBvbmx5IHR3byBkYXlzIGR1
cmluZyB3aGljaCB3ZSB3aWxsIGJlIGFibGUgdG8gZXhhbWluZSByZXF1ZXN0cyANCmZvciBwcmVz
ZW50YXRpb25zIHNsb3RzIGFuZCBwcmVwYXJlIG91ciBhZ2VuZGEuDQoNCkFtIEkgdGhlIG9ubHkg
b25lIHRvIHNlZSBhIGRpZmZpY3VsdHkgaGVyZSA/DQoNClByYWN0aWNhbGx5IHNwZWFraW5nIEkg
ZXhwZWN0IHRoYXQgbWFueSBpbml0aWFsIGFnZW5kYXMgd2lsbCBiZSBldmVuIA0KbGVzcyBjbG9z
ZSB0byB0aGUgZmluYWwgYWdlbmRhcyB0aGFuIHRoZXkgdXN1YWxseSB3ZXJlLg0KV291bGRuJ3Qg
aXQgbWFrZSBzZW5zZSB0byAob2ZmaWNpYWxseSkgc2V0IHRoZSBhZ2VuZGEgc3VibWlzc2lvbiBk
YXRlIA0Kb25lIHdlZWsgbGF0ZXIsIG9yIGF0IGxlYXN0IGEgZmV3IGRheXMgbGF0ZXIgPw0KDQot
VGhvbWFzCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQg
Y29udGVuaXIgZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVz
IGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGll
cyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJy
ZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBh
aW5zaSBxdWUgbGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBl
dGFudCBzdXNjZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNw
b25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZp
ZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBj
b25maWRlbnRpYWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0
ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVk
IHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBpdHMgYXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlz
IG5vdCBsaWFibGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2Vk
IG9yIGZhbHNpZmllZC4KVGhhbmsgeW91LgoK

From ynir@checkpoint.com  Tue Jul 16 05:15:07 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 55CC421E805A for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.527
X-Spam-Level: 
X-Spam-Status: No, score=-10.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 zUIKXt8dV7oF for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:15:01 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 354DB21E805F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:14:58 -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 r6GCEvXr004855; Tue, 16 Jul 2013 15:14:57 +0300
X-CheckPoint: {51E53941-19-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Tue, 16 Jul 2013 15:14:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "<thomas.morin@orange.com> " <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnBayA
Date: Tue, 16 Jul 2013 12:14:56 +0000
Message-ID: <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 115c12db7bd3a869150c8700167ca8c95893e28077
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5632B0145F81B346B7E6F6C56A51422E@ad.checkpoint.com>
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: Tue, 16 Jul 2013 12:15:07 -0000

On Jul 16, 2013, at 3:07 PM, <thomas.morin@orange.com>
 wrote:

> Hi everyone,
>=20
> It is not unusual that people wait for having submitted their drafts=20
> before asking for presentation slots.
>=20
> With the change in -00/-01 draft submission cut-off dates, this time we=20
> have have only two days during which we will be able to examine requests=
=20
> for presentations slots and prepare our agenda.
>=20
> Am I the only one to see a difficulty here ?
>=20
> Practically speaking I expect that many initial agendas will be even=20
> less close to the final agendas than they usually were.
> Wouldn't it make sense to (officially) set the agenda submission date=20
> one week later, or at least a few days later ?

That's one way to solve this. Another is to tell people that if they spring=
 a surprise -00 draft on you a mere 2 weeks before the meeting, they don't =
get a slot.

They don't have to submit the -00 earlier, just let you know that they are =
going to.

I think it is in the interest of the general attendee population that they =
know two weeks in advance what they need to read, and it is in the interest=
 of those making presentations to have over a week to create them. I'm not =
going to start a presentation when my time slot could change significantly,=
 so I'm not going to start before the agenda is published.

Yoav


From bclaise@cisco.com  Tue Jul 16 05:21:13 2013
Return-Path: <bclaise@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 439B821F9D75 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 aCr2wTmOcjZU for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:21:07 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E3FFA21F9DBA for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:21:06 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6GCKuQM018308; Tue, 16 Jul 2013 14:20:56 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6GCKKk4005923; Tue, 16 Jul 2013 14:20:35 +0200 (CEST)
Message-ID: <51E53A84.2010503@cisco.com>
Date: Tue, 16 Jul 2013 14:20:20 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
In-Reply-To: <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Tue, 16 Jul 2013 12:21:13 -0000

On 16/07/2013 14:14, Yoav Nir wrote:
> On Jul 16, 2013, at 3:07 PM, <thomas.morin@orange.com>
>   wrote:
>
>> Hi everyone,
>>
>> It is not unusual that people wait for having submitted their drafts
>> before asking for presentation slots.
>>
>> With the change in -00/-01 draft submission cut-off dates, this time we
>> have have only two days during which we will be able to examine requests
>> for presentations slots and prepare our agenda.
>>
>> Am I the only one to see a difficulty here ?
>>
>> Practically speaking I expect that many initial agendas will be even
>> less close to the final agendas than they usually were.
>> Wouldn't it make sense to (officially) set the agenda submission date
>> one week later, or at least a few days later ?
> That's one way to solve this. Another is to tell people that if they spring a surprise -00 draft on you a mere 2 weeks before the meeting, they don't get a slot.
Not sure if you're not causing another problem.
What I've seen recently is:
A: "WG, I will be posting a draft-XXX-00"
B: "How is this different than the draft-YYY?"
So basically, there is the risk that we start discussing the content of 
virtual drafts.

Regards, Benoit
>
> They don't have to submit the -00 earlier, just let you know that they are going to.
>
> I think it is in the interest of the general attendee population that they know two weeks in advance what they need to read, and it is in the interest of those making presentations to have over a week to create them. I'm not going to start a presentation when my time slot could change significantly, so I'm not going to start before the agenda is published.
>
> Yoav
>
>
>


From thomas.morin@orange.com  Tue Jul 16 05:32:55 2013
Return-Path: <thomas.morin@orange.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 A33C411E80D7 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vc5egTtw4-O8 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:32:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 59ADB21F842A for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:32:50 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 52F933246A6; Tue, 16 Jul 2013 14:32:49 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 383BB27C06A; Tue, 16 Jul 2013 14:32:49 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 14:32:48 +0200
From: <thomas.morin@orange.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnBayAgAAVuwA=
Date: Tue, 16 Jul 2013 12:32:48 +0000
Message-ID: <29639_1373977969_51E53D71_29639_10254_2_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF15B@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
In-Reply-To: <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6FBD2A3C0FD61C4D997B5D4487A844B8@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.121521
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, 16 Jul 2013 12:32:55 -0000

SGkgWW9hdiwNCg0KMjAxMy0wNy0xNiwgWW9hdiBOaXI6DQo+DQo+IFRoYXQncyBvbmUgd2F5IHRv
IHNvbHZlIHRoaXMuIEFub3RoZXIgaXMgdG8gdGVsbCBwZW9wbGUgdGhhdCBpZiB0aGV5DQo+IHNw
cmluZyBhIHN1cnByaXNlIC0wMCBkcmFmdCBvbiB5b3UgYSBtZXJlIDIgd2Vla3MgYmVmb3JlIHRo
ZSBtZWV0aW5nLA0KPiB0aGV5IGRvbid0IGdldCBhIHNsb3QuDQo+DQo+IFRoZXkgZG9uJ3QgaGF2
ZSB0byBzdWJtaXQgdGhlIC0wMCBlYXJsaWVyLCBqdXN0IGxldCB5b3Uga25vdyB0aGF0DQo+IHRo
ZXkgYXJlIGdvaW5nIHRvLg0KDQpJIHdvdWxkIGVjaG8gQmVub2l0J3MgY29tbWVudDogaG93IGRv
ZXMgdGhpcyBoZWxwID8gYSBkcmFmdCBuYW1lIGRvZXMgDQpub3QgY2FycnkgbXVjaCBjb250ZW50
LCByaWdodD8NCg0KDQo+IEkgdGhpbmsgaXQgaXMgaW4gdGhlIGludGVyZXN0IG9mIHRoZSBnZW5l
cmFsIGF0dGVuZGVlIHBvcHVsYXRpb24gdGhhdA0KPiB0aGV5IGtub3cgdHdvIHdlZWtzIGluIGFk
dmFuY2Ugd2hhdCB0aGV5IG5lZWQgdG8gcmVhZCwgYW5kIGl0IGlzIGluDQo+IHRoZSBpbnRlcmVz
dCBvZiB0aG9zZSBtYWtpbmcgcHJlc2VudGF0aW9ucyB0byBoYXZlIG92ZXIgYSB3ZWVrIHRvDQo+
IGNyZWF0ZSB0aGVtLg0KDQpJIHdvdWxkIGFncmVlIHdpdGggdGhpcy4NCg0KQnV0IHRoZW4sIHdo
YXQgd291bGQgYmUgbW9zdCBjb25zaXN0ZW50IGlzIHRvIGNob29zZSB0aGUgb25lIHN1Ym1pc3Np
b24gDQpkZWFkbGluZSBhcyB3aGF0IHRoZSBkZWFkbGluZSB3YXMgaW4gdGhlIHBhc3QgZm9yIC0w
MCByZXZpc2lvbnMsIGFuZCBub3QgDQpvbmUgd2VlayBsYXRlci4NCg0KLVRob21hcwpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
CgpDZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBp
bmZvcm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50
IGRvbmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlz
YXRpb24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXog
bGUgc2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBw
aWVjZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGli
bGVzIGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kg
Y2UgbWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhp
cyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9y
IHByaXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhl
eSBzaG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhv
cmlzYXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFz
ZSBub3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFj
aG1lbnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZv
ciBtZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQu
ClRoYW5rIHlvdS4KCg==

From ynir@checkpoint.com  Tue Jul 16 05:33:49 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 3E34211E8195 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.536
X-Spam-Level: 
X-Spam-Status: No, score=-10.536 tagged_above=-999 required=5 tests=[AWL=0.063, 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 IkKfm-xIJ3T3 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:33:44 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BB96221F842A for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:33:43 -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 r6GCXcTw011419; Tue, 16 Jul 2013 15:33:38 +0300
X-CheckPoint: {51E53DA2-26-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Tue, 16 Jul 2013 15:33:37 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnBayAgAABfACAAAO9gA==
Date: Tue, 16 Jul 2013 12:33:38 +0000
Message-ID: <60D5D6F4-2755-461B-9F57-0EBEF23FB350@checkpoint.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com> <51E53A84.2010503@cisco.com>
In-Reply-To: <51E53A84.2010503@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 1198c44b04681de33e3f404ef9e6a0689b5f113768
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <AA4E9469141CE84A9C33BE0AC52B466F@ad.checkpoint.com>
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: Tue, 16 Jul 2013 12:33:49 -0000

On Jul 16, 2013, at 3:20 PM, Benoit Claise <bclaise@cisco.com>
 wrote:

> On 16/07/2013 14:14, Yoav Nir wrote:
>> On Jul 16, 2013, at 3:07 PM, <thomas.morin@orange.com>
>>  wrote:
>>=20
>>> Hi everyone,
>>>=20
>>> It is not unusual that people wait for having submitted their drafts
>>> before asking for presentation slots.
>>>=20
>>> With the change in -00/-01 draft submission cut-off dates, this time we
>>> have have only two days during which we will be able to examine request=
s
>>> for presentations slots and prepare our agenda.
>>>=20
>>> Am I the only one to see a difficulty here ?
>>>=20
>>> Practically speaking I expect that many initial agendas will be even
>>> less close to the final agendas than they usually were.
>>> Wouldn't it make sense to (officially) set the agenda submission date
>>> one week later, or at least a few days later ?
>> That's one way to solve this. Another is to tell people that if they spr=
ing a surprise -00 draft on you a mere 2 weeks before the meeting, they don=
't get a slot.
> Not sure if you're not causing another problem.
> What I've seen recently is:
> A: "WG, I will be posting a draft-XXX-00"
> B: "How is this different than the draft-YYY?"
> So basically, there is the risk that we start discussing the content of v=
irtual drafts.

They might. But I think this worked OK:

http://www.ietf.org/mail-archive/web/ipsec/current/msg08450.html


From ynir@checkpoint.com  Tue Jul 16 05:42:34 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 E72FE21F9B5D for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level: 
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.056, 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 Gl5RKkrWD+rr for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:42:28 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 520B521F9A14 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:42:28 -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 r6GCgRsi014049; Tue, 16 Jul 2013 15:42:27 +0300
X-CheckPoint: {51E53FB3-2-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Tue, 16 Jul 2013 15:42:26 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "<thomas.morin@orange.com> " <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnBayAgAAVuwD///H0gA==
Date: Tue, 16 Jul 2013 12:42:26 +0000
Message-ID: <BB913331-F659-489F-9055-8133D0A6515C@checkpoint.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com> <29639_1373977969_51E53D71_29639_10254_2_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF15B@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <29639_1373977969_51E53D71_29639_10254_2_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF15B@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11b09d7d52487adef0915ac47d495099e1a34dc702
Content-Type: text/plain; charset="us-ascii"
Content-ID: <69FB0A5B37C62C43B74D9ECFA826D83C@ad.checkpoint.com>
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: Tue, 16 Jul 2013 12:42:35 -0000

On Jul 16, 2013, at 3:32 PM, <thomas.morin@orange.com>
 wrote:

> Hi Yoav,
>=20
> 2013-07-16, Yoav Nir:
>>=20
>> That's one way to solve this. Another is to tell people that if they
>> spring a surprise -00 draft on you a mere 2 weeks before the meeting,
>> they don't get a slot.
>>=20
>> They don't have to submit the -00 earlier, just let you know that
>> they are going to.
>=20
> I would echo Benoit's comment: how does this help ? a draft name does=20
> not carry much content, right?

No, but I mean that they should tell you in advance, "I'm working on a draf=
t for a new encoding for FOO objects in the BAR protocol. I'll have it read=
y by the submission deadline. Can I have a slot?"

Of course, they may miss the deadline, or submit something that's really ba=
d, but it's not too bad usually.

As for whether the correct deadline is 2 or 3 weeks, I don't know. =

From adrian@olddog.co.uk  Tue Jul 16 05:45:09 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 7436D21F9C38 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UhFftTOE8r5r for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:45:03 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7EF8711E80E0 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:45:01 -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 r6GCj0Px006460;  Tue, 16 Jul 2013 13:45:00 +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 r6GCixGf006440 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Jul 2013 13:44:59 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <thomas.morin@orange.com>, <wgchairs@ietf.org>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Subject: RE: WG Agendas to submit only 2 days after -00 submission cut-off date
Date: Tue, 16 Jul 2013 13:44:58 +0100
Message-ID: <0d5d01ce8222$4839a780$d8acf680$@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: AQIX0XdZ3QsV5Kg7PEoaPivFIHtQOZjUoDxg
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: Tue, 16 Jul 2013 12:45:09 -0000

Hi Thomas,

> It is not unusual that people wait for having submitted their drafts
> before asking for presentation slots.

Shouldn't it be unusual that people are granted presentation slots =
except for the discussion and resolution of issues that have arisen on =
the mailing list and need face-to-face time. =20

While discussion of new ideas (documented in -00 drafts) at the =
face-to-face meeting is not such a bad thing, people who post -00 drafts =
so close to the meeting can reasonably be asked to generate some =
discussion on the mailing list and come back at the next meeting.

Adrian


From thomas.morin@orange.com  Tue Jul 16 05:58:55 2013
Return-Path: <thomas.morin@orange.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 E189F21F86B2 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5g69Ssohivs for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 05:58:49 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 24A1121F9A1E for <wgchairs@ietf.org>; Tue, 16 Jul 2013 05:58:27 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 8852B324AEB; Tue, 16 Jul 2013 14:58:26 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 6D669238056; Tue, 16 Jul 2013 14:58:26 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 14:58:26 +0200
From: <thomas.morin@orange.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnHs0AgAADwoA=
Date: Tue, 16 Jul 2013 12:58:25 +0000
Message-ID: <25497_1373979506_51E54372_25497_2342_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF4E2@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
In-Reply-To: <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.2]
Content-Type: text/plain; charset="utf-8"
Content-ID: <10D99DB833F57D4B92CB564A728F196F@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.121521
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, 16 Jul 2013 12:58:55 -0000

SGkgQWRyaWFuLA0KDQoyMDEzLTA3LTE2LCBBZHJpYW4gRmFycmVsOg0KPj4gSXQgaXMgbm90IHVu
dXN1YWwgdGhhdCBwZW9wbGUgd2FpdCBmb3IgaGF2aW5nIHN1Ym1pdHRlZCB0aGVpcg0KPj4gZHJh
ZnRzIGJlZm9yZSBhc2tpbmcgZm9yIHByZXNlbnRhdGlvbiBzbG90cy4NCj4NCj4gU2hvdWxkbid0
IGl0IGJlIHVudXN1YWwgdGhhdCBwZW9wbGUgYXJlIGdyYW50ZWQgcHJlc2VudGF0aW9uIHNsb3Rz
DQo+IGV4Y2VwdCBmb3IgdGhlIGRpc2N1c3Npb24gYW5kIHJlc29sdXRpb24gb2YgaXNzdWVzIHRo
YXQgaGF2ZSBhcmlzZW4NCj4gb24gdGhlIG1haWxpbmcgbGlzdCBhbmQgbmVlZCBmYWNlLXRvLWZh
Y2UgdGltZS4NCj4NCj4gV2hpbGUgZGlzY3Vzc2lvbiBvZiBuZXcgaWRlYXMgKGRvY3VtZW50ZWQg
aW4gLTAwIGRyYWZ0cykgYXQgdGhlDQo+IGZhY2UtdG8tZmFjZSBtZWV0aW5nIGlzIG5vdCBzdWNo
IGEgYmFkIHRoaW5nLCBwZW9wbGUgd2hvIHBvc3QgLTAwDQo+IGRyYWZ0cyBzbyBjbG9zZSB0byB0
aGUgbWVldGluZyBjYW4gcmVhc29uYWJseSBiZSBhc2tlZCB0byBnZW5lcmF0ZQ0KPiBzb21lIGRp
c2N1c3Npb24gb24gdGhlIG1haWxpbmcgbGlzdCBhbmQgY29tZSBiYWNrIGF0IHRoZSBuZXh0DQo+
IG1lZXRpbmcuDQoNCklmIHdlIGRvbid0IGZpcnN0IGhhdmUgYSBjaGFuZ2UgaW4gcHJhY3RpY2Vz
LCBhcHBseWluZyB0aGlzIGFzIGEgcnVsZSANCm1heSBsZWFkIHRvIG5lYXJseSBlbXB0eSBhZ2Vu
ZGFzIGZvciBzb21lIHdvcmtpbmcgZ3JvdXBzLCBmb3IgYSBmZXcgDQpJRVRGcy4uLiA7LSkNCg0K
VG8gZW5jb3VyYWdlIHRoaXMgdmlydHVvdXMgcHJhY3RpY2UsIEkgdGhpbmsgdGhhdCBpdCBtYXkg
YmUgYmV0dGVyICpub3QqIA0KdG8gc2V0IHRoZSAtMDAgZGVhZGxpbmUgbGF0ZXIgdGhhbiBpdCB3
YXMuDQoNCi1UaG9tYXMKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMg
cGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2
aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMg
b3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdl
IHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRl
dHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJv
bmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNsaW5lIHRv
dXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91
IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBj
b250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJl
IHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBv
ciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlz
IGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlz
IG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBP
cmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQs
IGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=

From lee.howard@twcable.com  Tue Jul 16 06:33:27 2013
Return-Path: <lee.howard@twcable.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 E60B121F9B94 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 06:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.963
X-Spam-Level: 
X-Spam-Status: No, score=-0.963 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14+uiEowFeiJ for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 06:33:22 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 2EC7421F9E7C for <wgchairs@ietf.org>; Tue, 16 Jul 2013 06:33:21 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,677,1367985600"; d="scan'208";a="104759578"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 16 Jul 2013 09:32:10 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Tue, 16 Jul 2013 09:32:49 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Yoav Nir <ynir@checkpoint.com>, "<thomas.morin@orange.com> " <thomas.morin@orange.com>
Date: Tue, 16 Jul 2013 09:32:50 -0400
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: Ac6CKPbM1LMpZj41RfGjmUj+6PUCIQ==
Message-ID: <CE0AC289.24B4D%Lee.Howard@twcable.com>
In-Reply-To: <730D5379-2BF0-49AD-A13C-D9CB7CFB1094@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
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: Tue, 16 Jul 2013 13:33:28 -0000

On 7/16/13 8:14 AM, "Yoav Nir" <ynir@checkpoint.com> wrote:

>
>On Jul 16, 2013, at 3:07 PM, <thomas.morin@orange.com>
> wrote:
>
>> Hi everyone,
>>
>> It is not unusual that people wait for having submitted their drafts
>> before asking for presentation slots.
>>
>> With the change in -00/-01 draft submission cut-off dates, this time we
>> have have only two days during which we will be able to examine
>>requests
>> for presentations slots and prepare our agenda.
>>
>> Am I the only one to see a difficulty here ?
>>
>> Practically speaking I expect that many initial agendas will be even
>> less close to the final agendas than they usually were.
>> Wouldn't it make sense to (officially) set the agenda submission date
>> one week later, or at least a few days later ?
>
>That's one way to solve this. Another is to tell people that if they
>spring a surprise -00 draft on you a mere 2 weeks before the meeting,
>they don't get a slot.

So the deadline for -00 should be more than two weeks before the meeting.
The contents of (nearly) all -00 drafts are a surprise.

>
>They don't have to submit the -00 earlier, just let you know that they
>are going to.

That doesn't help us know whether the WG is interested in discussing it,
since we don't know what it says.  It also doesn't help evaluate how much
time the draft might require, either to present/explain, or to discuss.


>
>I think it is in the interest of the general attendee population that
>they know two weeks in advance what they need to read, and it is in the
>interest of those making presentations to have over a week to create
>them. I'm not going to start a presentation when my time slot could
>change significantly, so I'm not going to start before the agenda is
>published.

I think it is in the interest of the general population to spread the work
across more than six weeks a year (the meetings, and the week prior when
they might do reading).  Even if you have two weeks to read drafts to find
which are interesting, and even if you have time to send comments to the
WG list, you won't have time to keep up with the discussion.  Unless you
are following only a small handful of working groups, which looks uncommon
to me.

In other words, I like having new work submitted further in advance of
meetings, where revisions may be submitted less far in advance.

Lee

>
>Yoav
>


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From tnadeau@lucidvision.com  Tue Jul 16 07:57:50 2013
Return-Path: <tnadeau@lucidvision.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 5F5F421F9A8C for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 07:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okRuM+sdEHcE for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 07:57:44 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 2A52521F9BF3 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 07:57:35 -0700 (PDT)
Received: from [172.19.131.121] (unknown [12.130.126.109]) by lucidvision.com (Postfix) with ESMTP id A4DD525000DD; Tue, 16 Jul 2013 10:57:31 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
Date: Tue, 16 Jul 2013 10:57:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <63EF799B-2351-4DA7-99D5-228966B44BE7@lucidvision.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1508)
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, 16 Jul 2013 14:57:50 -0000

On Jul 16, 2013:8:44 AM, at 8:44 AM, "Adrian Farrel" =
<adrian@olddog.co.uk> wrote:

> Hi Thomas,
>=20
>> It is not unusual that people wait for having submitted their drafts
>> before asking for presentation slots.
>=20
> Shouldn't it be unusual that people are granted presentation slots =
except for the discussion and resolution of issues that have arisen on =
the mailing list and need face-to-face time. =20
>=20
> While discussion of new ideas (documented in -00 drafts) at the =
face-to-face meeting is not such a bad thing, people who post -00 drafts =
so close to the meeting can reasonably be asked to generate some =
discussion on the mailing list and come back at the next meeting.

	I agree. Slots (as I recall) were supposed to be used for people =
to discuss issues around drafts, and not in order to present or use as a =
tutorial/summarization session. Discussion on the list ahead of time is =
a very good thing.

	--Tom


>=20
> Adrian
>=20
>=20


From Ted.Lemon@nominum.com  Tue Jul 16 07:59:59 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 A487321F9EFE for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 07:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZONt58FyT6mL for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 07:59:52 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id C4DD321F9BD0 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 07:59:52 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUeVf579CWCLupZxJxZ90ghbj/ru2HfC4@postini.com; Tue, 16 Jul 2013 07:59:52 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 48F9D1B821F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 07:59:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F2ADD190052; Tue, 16 Jul 2013 07:59:49 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 07:59:50 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "thomas.morin@orange.com" <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kA
Date: Tue, 16 Jul 2013 14:59:49 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <397BE85B3A756348B3CE9CEA127A177E@nominum.com>
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: Tue, 16 Jul 2013 14:59:59 -0000

On Jul 16, 2013, at 5:07 AM, thomas.morin@orange.com wrote:
> Practically speaking I expect that many initial agendas will be even=20
> less close to the final agendas than they usually were.
> Wouldn't it make sense to (officially) set the agenda submission date=20
> one week later, or at least a few days later ?

This is a matter of choice for working group chairs.   You are free to anno=
unce that no drafts initially submitted after a certain date will be on the=
 agenda.   If you add things to the agenda late, you risk pushback from peo=
ple who will not have time to read the documents prior to the IETF meeting.

The decision to merge the two deadlines was really just us being realistic:=
 if someone wants to submit a -00 late, they just submit a -00 with minimal=
 content before the -00 deadline, and then submit the real -00 as a -01 bef=
ore the -01 deadline.   So the extra deadline creates churn and noise, but =
provides no benefit.

It's certainly not the case that someone submitting a -00 before either dea=
dline does not already know that they want to discuss it at IETF; if they s=
ubmit their agenda request late, you should just say no, and then they will=
 know better for next time.


From Ted.Lemon@nominum.com  Tue Jul 16 08:05:28 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 5B77611E80EE for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFG5uGCee8-O for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:05:21 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id CBBA921F9D01 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:05:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUeVhLWDnsw22EQzbX4nUIY6POTK6FZFJ@postini.com; Tue, 16 Jul 2013 08:05:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6835E1B81C7 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:05:17 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 60502190052; Tue, 16 Jul 2013 08:05:17 -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, 16 Jul 2013 08:05:17 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "thomas.morin@orange.com" <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnta0AgAADwoCAACNxAA==
Date: Tue, 16 Jul 2013 15:05:16 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752138E6@mbx-01.win.nominum.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk> <25497_1373979506_51E54372_25497_2342_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF4E2@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <25497_1373979506_51E54372_25497_2342_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF4E2@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DB98AF1CE246F944A183A0E3DD71A6C9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "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, 16 Jul 2013 15:05:28 -0000

On Jul 16, 2013, at 5:58 AM, thomas.morin@orange.com wrote:
> If we don't first have a change in practices, applying this as a rule=20
> may lead to nearly empty agendas for some working groups, for a few=20
> IETFs... ;-)

Not discussing stuff the working group doesn't know about at IETF is a feat=
ure, not a bug.   Working group agendas often have a lot of fat in them tha=
t could be trimmed, and which, if trimmed, would result in a more productiv=
e meeting.


From lee.howard@twcable.com  Tue Jul 16 08:15:25 2013
Return-Path: <lee.howard@twcable.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 3F68F21E8087 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level: 
X-Spam-Status: No, score=-1.213 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wITgSd2VmINE for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:15:20 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 1481021F9BC3 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:15:19 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,677,1367985600"; d="scan'208";a="108301836"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 16 Jul 2013 11:14:33 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Tue, 16 Jul 2013 11:15:09 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, "thomas.morin@orange.com" <thomas.morin@orange.com>
Date: Tue, 16 Jul 2013 11:15:10 -0400
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: Ac6CN0I82RCepqLiTmyeoh3RmsCEHA==
Message-ID: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
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: Tue, 16 Jul 2013 15:15:25 -0000

On 7/16/13 10:59 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

>On Jul 16, 2013, at 5:07 AM, thomas.morin@orange.com wrote:
>> Practically speaking I expect that many initial agendas will be even
>> less close to the final agendas than they usually were.
>> Wouldn't it make sense to (officially) set the agenda submission date
>> one week later, or at least a few days later ?
>
>This is a matter of choice for working group chairs.   You are free to
>announce that no drafts initially submitted after a certain date will be
>on the agenda.   If you add things to the agenda late, you risk pushback
>from people who will not have time to read the documents prior to the
>IETF meeting.

I like this suggestion:  WG chairs may declare a draft-00 deadline that is
earlier than the "official" deadline.

>
>The decision to merge the two deadlines was really just us being
>realistic: if someone wants to submit a -00 late, they just submit a -00
>with minimal content before the -00 deadline, and then submit the real
>-00 as a -01 before the -01 deadline.   So the extra deadline creates
>churn and noise, but provides no benefit.

At least minimal content is *some* content.  The current situation is
potentially *no* content.

>
>It's certainly not the case that someone submitting a -00 before either
>deadline does not already know that they want to discuss it at IETF; if
>they submit their agenda request late, you should just say no, and then
>they will know better for next time.

But how do I, as a chair, evaluate their request to discuss something, if
I don't know what it is?
Teaching lessons through hard knocks means giving hard knocks to IETF
participants.  Rather, we should be supporting them in creating the best
possible document, and providing ample (and timely) opportunities for
review and discussion, both online and in person.

Lee


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From kent@bbn.com  Tue Jul 16 08:17:43 2013
Return-Path: <kent@bbn.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 1085821F9A81 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:17:43 -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 qexRagk0ltmv for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:17:37 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 344F021F9A14 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:17:37 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:54933) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Uz70Q-000CKo-IQ for wgchairs@ietf.org; Tue, 16 Jul 2013 11:17:34 -0400
Message-ID: <51E5640F.8080205@bbn.com>
Date: Tue, 16 Jul 2013 11:17:35 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
In-Reply-To: <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8; 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, 16 Jul 2013 15:17:43 -0000

Adrian,

I think different WGs have different criteria in this regard. While PKIX 
always gave
priority to discussions of extant WG items, we also allowed time (at the 
end) for presentations
on new topics that were being proposed as WG items. On occaison we ran 
out of time and the
speakers near the end didn't get to present.

Steve
> Hi Thomas,
>
>> It is not unusual that people wait for having submitted their drafts
>> before asking for presentation slots.
> Shouldn't it be unusual that people are granted presentation slots except for the discussion and resolution of issues that have arisen on the mailing list and need face-to-face time.
>
> While discussion of new ideas (documented in -00 drafts) at the face-to-face meeting is not such a bad thing, people who post -00 drafts so close to the meeting can reasonably be asked to generate some discussion on the mailing list and come back at the next meeting.
>
> Adrian
>
>


From thomas.morin@orange.com  Tue Jul 16 08:19:50 2013
Return-Path: <thomas.morin@orange.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 E520921F9C41 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:19:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.555
X-Spam-Level: 
X-Spam-Status: No, score=-2.555 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J86zLv4jGM7m for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:19:44 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8800121F9AF5 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:19:44 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id E68D0264689; Tue, 16 Jul 2013 17:19:42 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id CA59F35C045; Tue, 16 Jul 2013 17:19:42 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 17:19:42 +0200
From: <thomas.morin@orange.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexpplnHs0AgAADwoCAACNxAIAABAiA
Date: Tue, 16 Jul 2013 15:19:41 +0000
Message-ID: <6294_1373987982_51E5648E_6294_6246_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B00@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <0d5d01ce8222$4839a780$d8acf680$@olddog.co.uk> <25497_1373979506_51E54372_25497_2342_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FF4E2@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B6307752138E6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307752138E6@mbx-01.win.nominum.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.2]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1551E927DF56FC48AE54D1A6A0FE7143@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.125418
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "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, 16 Jul 2013 15:19:50 -0000

SGkgVGVkLA0KDQoyMDEzLTA3LTE2LCBUZWQgTGVtb246DQo+IE9uIEp1bCAxNiwgMjAxMywgYXQg
NTo1OCBBTSwgdGhvbWFzLm1vcmluQG9yYW5nZS5jb20gd3JvdGU6DQo+PiBJZiB3ZSBkb24ndCBm
aXJzdCBoYXZlIGEgY2hhbmdlIGluIHByYWN0aWNlcywgYXBwbHlpbmcgdGhpcyBhcyBhDQo+PiBy
dWxlIG1heSBsZWFkIHRvIG5lYXJseSBlbXB0eSBhZ2VuZGFzIGZvciBzb21lIHdvcmtpbmcgZ3Jv
dXBzLCBmb3INCj4+IGEgZmV3IElFVEZzLi4uIDstKQ0KPg0KPiBOb3QgZGlzY3Vzc2luZyBzdHVm
ZiB0aGUgd29ya2luZyBncm91cCBkb2Vzbid0IGtub3cgYWJvdXQgYXQgSUVURiBpcw0KPiBhIGZl
YXR1cmUsIG5vdCBhIGJ1Zy4gICBXb3JraW5nIGdyb3VwIGFnZW5kYXMgb2Z0ZW4gaGF2ZSBhIGxv
dCBvZiBmYXQNCj4gaW4gdGhlbSB0aGF0IGNvdWxkIGJlIHRyaW1tZWQsIGFuZCB3aGljaCwgaWYg
dHJpbW1lZCwgd291bGQgcmVzdWx0IGluDQo+IGEgbW9yZSBwcm9kdWN0aXZlIG1lZXRpbmcuDQoN
CkFnYWluLCBwZW9wbGUgYmVpbmcgd2hvIHRoZXkgYXJlIGFuZCBhY3RpbmcgbGlrZSBwZW9wbGUs
IGFuIGVhcmxpZXIgLTAwIA0KZGVhZGxpbmUgd291bGQgYWN0dWFsbHkgYmUgYSBwcmFjdGljYWwg
d2F5IHRvIGVuY291cmFnZSBlYXJseSBkaXNjdXNzaW9ucy4NCg0KLVRob21hcw0KCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18K
CkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGlu
Zm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQg
ZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNh
dGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBs
ZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBp
ZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJs
ZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBj
ZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuCgpUaGlz
IG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3Ig
cHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3Owp0aGV5
IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9y
aXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNl
IG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNo
bWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9y
IG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4K
VGhhbmsgeW91LgoK

From thomas.morin@orange.com  Tue Jul 16 08:20:59 2013
Return-Path: <thomas.morin@orange.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 C26F311E80D3 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, 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 n5uiM8cs+LIa for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:20:54 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 758ED21F9AF5 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:20:50 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id AEDC918C8FB; Tue, 16 Jul 2013 17:20:49 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 9097E35C04E; Tue, 16 Jul 2013 17:20:49 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 17:20:49 +0200
From: <thomas.morin@orange.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kA//9tawCAAAGTAA==
Date: Tue, 16 Jul 2013 15:20:48 +0000
Message-ID: <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
In-Reply-To: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.2]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2747DC21B87A984D8120ECCBEEA65C6D@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.125418
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, 16 Jul 2013 15:20:59 -0000

MjAxMy0wNy0xNiwgSG93YXJkLCBMZWU6DQo+PiBPbiBKdWwgMTYsIDIwMTMsIGF0IDU6MDcgQU0s
IHRob21hcy5tb3JpbkBvcmFuZ2UuY29tIHdyb3RlOg0KPj4+IFByYWN0aWNhbGx5IHNwZWFraW5n
IEkgZXhwZWN0IHRoYXQgbWFueSBpbml0aWFsIGFnZW5kYXMgd2lsbCBiZSBldmVuDQo+Pj4gbGVz
cyBjbG9zZSB0byB0aGUgZmluYWwgYWdlbmRhcyB0aGFuIHRoZXkgdXN1YWxseSB3ZXJlLg0KPj4+
IFdvdWxkbid0IGl0IG1ha2Ugc2Vuc2UgdG8gKG9mZmljaWFsbHkpIHNldCB0aGUgYWdlbmRhIHN1
Ym1pc3Npb24gZGF0ZQ0KPj4+IG9uZSB3ZWVrIGxhdGVyLCBvciBhdCBsZWFzdCBhIGZldyBkYXlz
IGxhdGVyID8NCj4+DQo+PiBUaGlzIGlzIGEgbWF0dGVyIG9mIGNob2ljZSBmb3Igd29ya2luZyBn
cm91cCBjaGFpcnMuICAgWW91IGFyZSBmcmVlIHRvDQo+PiBhbm5vdW5jZSB0aGF0IG5vIGRyYWZ0
cyBpbml0aWFsbHkgc3VibWl0dGVkIGFmdGVyIGEgY2VydGFpbiBkYXRlIHdpbGwgYmUNCj4+IG9u
IHRoZSBhZ2VuZGEuICAgSWYgeW91IGFkZCB0aGluZ3MgdG8gdGhlIGFnZW5kYSBsYXRlLCB5b3Ug
cmlzayBwdXNoYmFjaw0KPj5mcm9tIHBlb3BsZSB3aG8gd2lsbCBub3QgaGF2ZSB0aW1lIHRvIHJl
YWQgdGhlIGRvY3VtZW50cyBwcmlvciB0byB0aGUNCj4+IElFVEYgbWVldGluZy4NCj4NCj4gSSBs
aWtlIHRoaXMgc3VnZ2VzdGlvbjogIFdHIGNoYWlycyBtYXkgZGVjbGFyZSBhIGRyYWZ0LTAwIGRl
YWRsaW5lIHRoYXQgaXMNCj4gZWFybGllciB0aGFuIHRoZSAib2ZmaWNpYWwiIGRlYWRsaW5lLg0K
DQpXZWxsLCB0aGUgZmluYWwgZ29hbCBpcyBzZW5zaWJsZSwgYnV0IHdlIGxvc2UgdGhlIHNpbXBs
aWNpdHkgb2YgaGF2aW5nIA0Kb25lIGRlYWRsaW5lLiBBcyBhIGNvbnRyaWJ1dG9yIEkgd291bGRu
J3QgbGlrZSB0byBkZWFsIHdpdGggWCB3b3JraW5nIA0KZ3JvdXBzIGhhdmluZyBwb3NzaWJseSBY
IGRpZmZlcmVudCBkZWFkbGluZXMuLi4NCg0KLVRob21hcwpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpDZSBtZXNzYWdlIGV0
IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZvcm1hdGlvbnMgY29u
ZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRvbmMKcGFzIGV0cmUg
ZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRpb24uIFNpIHZvdXMg
YXZleiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUgc2lnbmFsZXIKYSBs
J2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVjZXMgam9pbnRlcy4g
TGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVzIGQnYWx0ZXJhdGlv
biwKT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2UgbWVzc2FnZSBhIGV0
ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBtZXNzYWdlIGFuZCBp
dHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHByaXZpbGVnZWQgaW5m
b3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBzaG91bGQgbm90IGJl
IGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlzYXRpb24uCklmIHlv
dSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNl
bmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzLgpBcyBlbWFp
bHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBtZXNzYWdlcyB0aGF0
IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRoYW5rIHlvdS4KCg==

From thomas.morin@orange.com  Tue Jul 16 08:25:08 2013
Return-Path: <thomas.morin@orange.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 EBFFE21F9AF5 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7ypRYOrTJoL for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:25:00 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8CF21F8617 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:25:00 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 0C79A324BB0; Tue, 16 Jul 2013 17:24:57 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id E745035C058; Tue, 16 Jul 2013 17:24:56 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 16 Jul 2013 17:24:56 +0200
From: <thomas.morin@orange.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kA//9wJgA=
Date: Tue, 16 Jul 2013 15:24:56 +0000
Message-ID: <6294_1373988296_51E565C8_6294_6677_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501C1D@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EC822D8311715E43A0918E2A766FC525@adroot.infra.ftgroup>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.16.125418
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, 16 Jul 2013 15:25:08 -0000

MjAxMy0wNy0xNiwgVGVkIExlbW9uOg0KPg0KPiBUaGUgZGVjaXNpb24gdG8gbWVyZ2UgdGhlIHR3
byBkZWFkbGluZXMgd2FzIHJlYWxseSBqdXN0IHVzIGJlaW5nDQo+IHJlYWxpc3RpYzogaWYgc29t
ZW9uZSB3YW50cyB0byBzdWJtaXQgYSAtMDAgbGF0ZSwgdGhleSBqdXN0IHN1Ym1pdCBhDQo+IC0w
MCB3aXRoIG1pbmltYWwgY29udGVudCBiZWZvcmUgdGhlIC0wMCBkZWFkbGluZSwgYW5kIHRoZW4g
c3VibWl0IHRoZQ0KPiByZWFsIC0wMCBhcyBhIC0wMSBiZWZvcmUgdGhlIC0wMSBkZWFkbGluZS4g
ICBTbyB0aGUgZXh0cmEgZGVhZGxpbmUNCj4gY3JlYXRlcyBjaHVybiBhbmQgbm9pc2UsIGJ1dCBw
cm92aWRlcyBubyBiZW5lZml0Lg0KDQpUaGUgZXh0cmEgZGVhZGxpbmUgY291bGQgcHJvdmlkZSBh
IGJlbmVmaXQgaWYgdmVyeSByZWNlbnRseSBzdWJtaXR0ZWQgDQotMDAgZHJhZnRzIHdoZXJlIGV4
Y2x1ZGVkIGZyb20gaGF2aW5nIHRoZSBwb3NzaWJpbGl0eSB0byBwb3N0IGJldHdlZW4gDQp0aGUg
LTAwIGRlYWRsaW5lIGFuZCB0aGUgLTAxIGRlYWRsaW5lLiBFLmcgcG9zdGluZyBhZnRlciAtMDAg
YW5kIGJlZm9yZSANCnRoZSAtMDEgZGVhZGxpbmUgd291bGQgYmUgYWxsb3dlZCBvbmx5IGZvciAt
MDEgZHJhZnQgaWYgdGhlIC0wMCBkcmFmdCBpcyANCmF0IGxlYXN0IG9uZSBtb250aCBvbGQuDQoN
Ci1UaG9tYXMKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVu
dCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2ll
ZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29w
aWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBl
cnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJl
IGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVz
IGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNsaW5lIHRvdXRlIHJl
c3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNp
ZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWlu
IGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3Rl
Y3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3Bp
ZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWls
IGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3Nh
Z2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2Ug
aXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5n
ZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=

From Ted.Lemon@nominum.com  Tue Jul 16 08:35:52 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 0D44011E80D5 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcKd7xIi6DPp for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:35:45 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6C711E80C5 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:35:45 -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 DSNKUeVoT0C7aHxU7UbiZdRmePZuK0d6ivRE@postini.com; Tue, 16 Jul 2013 08:35:45 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A9CE21B821F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:35:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 9030E190052; Tue, 16 Jul 2013 08:35:43 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 08:35:43 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgAAESwCAAAW9AA==
Date: Tue, 16 Jul 2013 15:35:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775213B6E@mbx-01.win.nominum.com>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
In-Reply-To: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B7B293ABBF11514F90057E957C5CCFFE@nominum.com>
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: Tue, 16 Jul 2013 15:35:52 -0000

On Jul 16, 2013, at 8:15 AM, "Howard, Lee" <lee.howard@twcable.com> wrote:
> But how do I, as a chair, evaluate their request to discuss something, if
> I don't know what it is?

You say "no."

> Teaching lessons through hard knocks means giving hard knocks to IETF
> participants.  Rather, we should be supporting them in creating the best
> possible document, and providing ample (and timely) opportunities for
> review and discussion, both online and in person.

I don't think I'd characterize this as hard knocks.   How hard a knock is i=
t to be told "you waited too long to inform the working group about this, p=
lease inform the working group about this in time for the next meeting and =
we will schedule you on the agenda then?"   I mean, why is getting your dra=
ft into the consciousness of working group members harder than, say, buying=
 a plane ticket and making a hotel reservation, all of which we usually do =
well before the draft submission cutoff?

Having said that, I think one thing that might work well and that I would l=
ike to see tried is a five or ten minute "lightning talk" on the agendas of=
 working groups that get a lot of new work.   People who want to raise awar=
eness of work within the working group would be encouraged to come up with =
a one-minute elevator pitch for their work, which they would be asked to re=
hearse and size so that they can present it at a slow-to-normal talking spe=
ed, so that we don't get auctioneer patter during each presentation.   Maxi=
mum of, say, four slides, fifteen seconds per slide.

If the working group doesn't know about your work, you get a one-minute slo=
t, and you make your pitch.

I don't know, maybe this is a crazy idea?


From ietf-secretariat@ietf.org  Tue Jul 16 08:39:38 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 EB3BA11E80DF; Tue, 16 Jul 2013 08:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, 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 PghRkhQd4BDA; Tue, 16 Jul 2013 08:39:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B2A611E80E8; Tue, 16 Jul 2013 08:39:34 -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 87 - Early Bird Registration Cutoff: Friday, 19 July
X-Test-IDTracker: no
X-IETF-IDTracker: 4.51.p2
Message-ID: <20130716153934.23549.56042.idtracker@ietfa.amsl.com>
Date: Tue, 16 Jul 2013 08:39:34 -0700
Cc: wgchairs@ietf.org, 87all@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: Tue, 16 Jul 2013 15:39:39 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

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

1. Registration
A. Early-Bird Registration - USD 650.00 Pay by Friday, 19 July 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. All fees include 19% VAT
F. Registration Cancellation   =

         Cut-off for registration cancellation is Monday,
         22 July 2013 at UTC 24:00.
         Cancellations are subject to a 10% (ten percent)
         cancellation fee if requested by that date and time.
G. Online Registration and Payment ends Friday, 26 July 2013, 1700 local Be=
rlin time.
H. On-site Registration starting Sunday, 28 July 2013 at 1100 local Berlin =
time.

Only 12 days until the Berlin IETF!

From Ted.Lemon@nominum.com  Tue Jul 16 08:42:49 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 297BA21F85BB for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NB7Cbf4Q7QbO for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 08:42:42 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id A6E5C21F99CF for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:42:41 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUeVp8dz/Bb4F6G8L5of27SejCvzF7fMY@postini.com; Tue, 16 Jul 2013 08:42:41 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 5509A1B821F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 08:42:41 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4F1E1190052; Tue, 16 Jul 2013 08:42:41 -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, 16 Jul 2013 08:42:41 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<thomas.morin@orange.com> " <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgAAESwCAAAGTAIAABhwA
Date: Tue, 16 Jul 2013 15:42:40 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BB9B63EE6A7DC14BA4AF1B22E4A32C5D@nominum.com>
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: Tue, 16 Jul 2013 15:42:49 -0000

On Jul 16, 2013, at 8:20 AM, <thomas.morin@orange.com> wrote:
> Well, the final goal is sensible, but we lose the simplicity of having=20
> one deadline. As a contributor I wouldn't like to deal with X working=20
> groups having possibly X different deadlines...

This is no problem.   All you have to do to avoid this is to get your draft=
s in well before the deadline, and accept that if you miss a deadline, you'=
ll have to wait until next time or beg the working group chair for forgiven=
ess.

Personally, I would argue strongly against having any deadline at all, beca=
use I think it creates a useless artificial flurry of submissions too close=
 to IETF, on the one hand, and inconveniences people who just want to publi=
sh a new version of their draft but don't intend to present it at IETF, on =
the other.

I really would encourage working group chairs to consider IETF agenda submi=
ssion deadlines to be an important part of their work.   Working group f2f =
meeting time is extraordinarily expensive, and when I attend working group =
sessions, I get the very strong impression that a great deal of it is waste=
d.   If you never say no to an agenda request, either you have an unusually=
 disciplined working group, or you are doing something wrong.


From keith.drage@alcatel-lucent.com  Tue Jul 16 09:35:25 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 21B3B11E80F6 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 09:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[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 4rEfA1ejalK9 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 09:35:18 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 8DCF521F9A5F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 09:35:18 -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 r6GGZEsL023201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Jul 2013 11:35:16 -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 r6GGZEx0018296 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 16 Jul 2013 18:35:14 +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; Tue, 16 Jul 2013 18:35:14 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, "<thomas.morin@orange.com> " <thomas.morin@orange.com>
Subject: RE: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgAAESwCAAAGTAIAABhwA//+YUyA=
Date: Tue, 16 Jul 2013 16:35:14 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [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.39
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, 16 Jul 2013 16:35:25 -0000

I agree with everything you have said here.

However human nature responds to deadlines, and if we had no submission dea=
dline, the consequence would virtually all the documents submitted on the M=
onday of the meeting with an expectation they would be discussed.

In your rational, that would be met by a WG chairs applying a bar, but to a=
void confusion among those working in multiple working groups, that needs t=
o be a consistent bar. That bar is currently expressed by the submission de=
adline(s).

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Ted Lemon
> Sent: 16 July 2013 16:43
> To: <thomas.morin@orange.com>
> Cc: wgchairs@ietf.org
> Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-of=
f
> date
>=20
> On Jul 16, 2013, at 8:20 AM, <thomas.morin@orange.com> wrote:
> > Well, the final goal is sensible, but we lose the simplicity of having
> > one deadline. As a contributor I wouldn't like to deal with X working
> > groups having possibly X different deadlines...
>=20
> This is no problem.   All you have to do to avoid this is to get your
> drafts in well before the deadline, and accept that if you miss a deadlin=
e,
> you'll have to wait until next time or beg the working group chair for
> forgiveness.
>=20
> Personally, I would argue strongly against having any deadline at all,
> because I think it creates a useless artificial flurry of submissions too
> close to IETF, on the one hand, and inconveniences people who just want t=
o
> publish a new version of their draft but don't intend to present it at
> IETF, on the other.
>=20
> I really would encourage working group chairs to consider IETF agenda
> submission deadlines to be an important part of their work.   Working
> group f2f meeting time is extraordinarily expensive, and when I attend
> working group sessions, I get the very strong impression that a great dea=
l
> of it is wasted.   If you never say no to an agenda request, either you
> have an unusually disciplined working group, or you are doing something
> wrong.


From joelja@bogus.com  Tue Jul 16 10:07:10 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 9630E11E80F7 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 10:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.218
X-Spam-Level: 
X-Spam-Status: No, score=-102.218 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Onc0YFXmwhZj for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 10:07:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 378BD11E80F1 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 10:07:10 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6GH71r5065712 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 16 Jul 2013 17:07:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <51E57DB0.8040108@bogus.com>
Date: Tue, 16 Jul 2013 10:06:56 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: "Howard, Lee" <lee.howard@twcable.com>, Yoav Nir <ynir@checkpoint.com>, "<thomas.morin@orange.com>" <thomas.morin@orange.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0AC289.24B4D%Lee.Howard@twcable.com>
In-Reply-To: <CE0AC289.24B4D%Lee.Howard@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 16 Jul 2013 17:07:01 +0000 (UTC)
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, 16 Jul 2013 17:07:10 -0000

On 7/16/13 6:32 AM, Howard, Lee wrote:
>
> On 7/16/13 8:14 AM, "Yoav Nir" <ynir@checkpoint.com> wrote:
>
>> On Jul 16, 2013, at 3:07 PM, <thomas.morin@orange.com>
>> wrote:
>>
>> Practically speaking I expect that many initial agendas will be even
>> less close to the final agendas than they usually were.
>> Wouldn't it make sense to (officially) set the agenda submission date
>> one week later, or at least a few days later ?
>> That's one way to solve this. Another is to tell people that if they
>> spring a surprise -00 draft on you a mere 2 weeks before the meeting,
>> they don't get a slot.
> So the deadline for -00 should be more than two weeks before the meeting.
> The contents of (nearly) all -00 drafts are a surprise.
Back when I was a v6ops chair, fred and I demanded discussion/interest a 
a precondition for agenda time. so while the document submission 
deadline is a deadline, you really have to work to lay claim to an 
agenda slot on the basis of a submission that late. I am personally as a 
Chair/AD quite comfortable excluding something from the agenda on the 
basis that the wg hasn't been exposed to it.
>
>>


From ajs@anvilwalrusden.com  Tue Jul 16 10:30:11 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 4878921F9A3B for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 10:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.496
X-Spam-Level: 
X-Spam-Status: No, score=-0.496 tagged_above=-999 required=5 tests=[AWL=-0.256, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, 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 RmI9MbuBZEIb for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 10:30:05 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9B621F84BB for <wgchairs@ietf.org>; Tue, 16 Jul 2013 10:30:05 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E4CC88A031 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 17:30:04 +0000 (UTC)
Date: Tue, 16 Jul 2013 13:30:03 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Message-ID: <20130716173003.GK23286@mx1.yitter.info>
References: <CE0AC289.24B4D%Lee.Howard@twcable.com> <51E57DB0.8040108@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51E57DB0.8040108@bogus.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: Tue, 16 Jul 2013 17:30:11 -0000

On Tue, Jul 16, 2013 at 10:06:56AM -0700, joel jaeggli wrote:

> Back when I was a v6ops chair, fred and I demanded
> discussion/interest a a precondition for agenda time. so while the
> document submission deadline is a deadline, you really have to work
> to lay claim to an agenda slot on the basis of a submission that
> late.

I strongly agree with this filter (and try to use the same approach
myself).  Note that it allows for some late-breaking -00 to take up a
very significant chunk of agenda if it is addressing something people
think to be important, and it still means that the natural filtering
it imposes reduces the frequency with which you get 20 minute
presentations of a new draft.

I _do_ think having some room (in an active WG) for 1-minute lightning
talk-style "here's my draft and here's why you should read it" is not
a bad thing (and I've seen that be successful).

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From spencerdawkins.ietf@gmail.com  Tue Jul 16 13:36:37 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 70CDB21E8083 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 13:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KJluZ3+6O15 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 13:36:37 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id CD7BC21F9FFB for <wgchairs@ietf.org>; Tue, 16 Jul 2013 13:36:36 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro2so1093567pbb.41 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 13:36:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mdfKaI1U2b05CRQRp7fp9QXjhvC2SRmdagVa/yOLdzI=; b=zgtOVfclPU4Qkgxj7WGKcmFktT/e6uF03z3aK2BP49DJvk/HjHdDEjYtgPNqELzQT4 KMeD10Lwr86EXhgNEjn1/vpwSI788neu9ppMFJzSU7agd9EZQteWXHdwz4D/ycHwdnv0 hpkZ8VwMaHq5QOZAywUsAcxtMg93WFXww8H5A/kUAk9CllI/0UEUfcbJqWr7lCxbsNTC MULxS3xX8E7s88em/cvBBFEhX3jAuMh5xeGVct8Hmw4JFFGx0XJjXxmXBPxFIK0cqCk2 oNYOhYJB+rce8WvhJoR1QHxnQvXGWtJa4BkpNO4emZr28nEUNWQW1q0kQPVkdlmOec3C Iezg==
X-Received: by 10.68.223.225 with SMTP id qx1mr3202130pbc.157.1374006996510; Tue, 16 Jul 2013 13:36:36 -0700 (PDT)
Received: from [192.168.1.74] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id qu10sm3669017pbb.12.2013.07.16.13.36.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Jul 2013 13:36:35 -0700 (PDT)
Message-ID: <51E5AECF.9060304@gmail.com>
Date: Tue, 16 Jul 2013 15:36:31 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0AC289.24B4D%Lee.Howard@twcable.com> <51E57DB0.8040108@bogus.com> <20130716173003.GK23286@mx1.yitter.info>
In-Reply-To: <20130716173003.GK23286@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 16 Jul 2013 13:42:03 -0700
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, 16 Jul 2013 20:36:37 -0000

On 7/16/2013 12:30 PM, Andrew Sullivan wrote:
> I _do_ think having some room (in an active WG) for 1-minute lightning 
> talk-style "here's my draft and here's why you should read it" is not 
> a bad thing (and I've seen that be successful).

The Lovely Mary Barnes and Equally Lovely Cullen Jennings can correct 
me, but I'm remembering that the DISPATCH chairs would offer to put up 
one slide on drafts that had suddenly descended from the sky, too 
suddenly to have generated mailing list traffic, if requested to do so, 
in order to familiarize interested working group participants with 
potential future work. I thought that was helpful.

If a working group has the agenda time to allow lightning talks that 
last over a minute, I think that would be fine; for what I saw in 
DISPATCH. 3 minutes would have been plenty.

Thanks,

Spencer

From mary.ietf.barnes@gmail.com  Tue Jul 16 13:57:08 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 C99E511E80F8 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 13:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 1IsAt58C7x3R for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 13:57:07 -0700 (PDT)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD8D11E80ED for <wgchairs@ietf.org>; Tue, 16 Jul 2013 13:56:58 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id n20so707297qaj.6 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 13:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3L0Uh3FuGO3gXQxiM4RseOc3wGDpbqxAFTq8GvB0Nh4=; b=qEe3h9GAzohtAajvDmRfD6l6MQj1BGotp4KwrJM7iJH/GnROPZbsVJzTB/Qzg8B9KW reGqVa30aOlG8We2/B/GRpqO/0iwdDUiPeikeQ43d8vWCvyHNgSuYhux4Zk997qlMCnb ASSGi00umzQKu/wraiIebqoFCJaRQUt+GZXFsQt5txokBNsgW2HwU1Pwpk8i5KJdkWVH G+/OV69T9HCQFsFRXj94vfAV/Dlq4HfePG4GwcL8tis8lbzQTdvvHRHEJbrgCGISDBK8 5pE+RH9tJdUMZk9KU0C24q8Xbk1/KFqduEZ2+up8UBAE6Srqp2G/ECgfDSDcwDvk15tS kYBw==
MIME-Version: 1.0
X-Received: by 10.49.110.68 with SMTP id hy4mr4665904qeb.6.1374008216243; Tue, 16 Jul 2013 13:56:56 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Tue, 16 Jul 2013 13:56:56 -0700 (PDT)
In-Reply-To: <51E5AECF.9060304@gmail.com>
References: <CE0AC289.24B4D%Lee.Howard@twcable.com> <51E57DB0.8040108@bogus.com> <20130716173003.GK23286@mx1.yitter.info> <51E5AECF.9060304@gmail.com>
Date: Tue, 16 Jul 2013 15:56:56 -0500
Message-ID: <CAHBDyN5COtL1_voowHVCjMSJk07EDQR=_zxfh6OXTQm9n=1__w@mail.gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc90aaa5f01504e1a737da
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, 16 Jul 2013 20:57:09 -0000

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

Thank you Spencer.  Yes, that's been our usual approach for documents that
weren't given agenda time for a variety of reasons.  We ask the individual
for a slide (in rare cases two) and if there were any questions comments,
then the individual could speak from the floor microphone.   We use this
approach as we learned in running the SIPPING WG that lightening talks
didn't work well at all.  If you have more than a few of these,  it ends up
more like the gong show.  It also tends to set the expectation that if you
submit a draft, you at least get one of these short slots.

Of course, we also set earlier deadlines in DISPATCH to allow additional
time for discussion before the meeting and we only give agenda time in
cases where there has been discussion or sufficient interest expressed.
 However, that's because all the DISPATCH work items are new.  It is more
difficult to do that for regular WGs as there can be value in giving agenda
time for a -00 document if it really hits on something key to the WG.   So,
I personally, thinks it's entirely up to the discretion of the chairs.

I do agree that the latter deadline for -00 makes it a tad more
challenging, but I still think it's doable as a chair.

Mary.


On Tue, Jul 16, 2013 at 3:36 PM, Spencer Dawkins <
spencerdawkins.ietf@gmail.com> wrote:

> On 7/16/2013 12:30 PM, Andrew Sullivan wrote:
>
>> I _do_ think having some room (in an active WG) for 1-minute lightning
>> talk-style "here's my draft and here's why you should read it" is not a bad
>> thing (and I've seen that be successful).
>>
>
> The Lovely Mary Barnes and Equally Lovely Cullen Jennings can correct me,
> but I'm remembering that the DISPATCH chairs would offer to put up one
> slide on drafts that had suddenly descended from the sky, too suddenly to
> have generated mailing list traffic, if requested to do so, in order to
> familiarize interested working group participants with potential future
> work. I thought that was helpful.
>
> If a working group has the agenda time to allow lightning talks that last
> over a minute, I think that would be fine; for what I saw in DISPATCH. 3
> minutes would have been plenty.
>
> Thanks,
>
> Spencer
>

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

<div dir=3D"ltr">Thank you Spencer. =A0Yes, that&#39;s been our usual appro=
ach for documents that weren&#39;t given agenda time for a variety of reaso=
ns. =A0We ask the individual for a slide (in rare cases two) and if there w=
ere any questions comments, then the individual could speak from the floor =
microphone. =A0 We use this approach as we learned in running the SIPPING W=
G that lightening talks didn&#39;t work well at all. =A0If you have more th=
an a few of these, =A0it ends up more like the gong show. =A0It also tends =
to set the expectation that if you submit a draft, you at least get one of =
these short slots.=A0<div>
<br></div><div>Of course, we also set earlier deadlines in DISPATCH to allo=
w additional time for discussion before the meeting and we only give agenda=
 time in cases where there has been discussion or sufficient interest expre=
ssed. =A0However, that&#39;s because all the DISPATCH work items are new. =
=A0It is more difficult to do that for regular WGs as there can be value in=
 giving agenda time for a -00 document if it really hits on something key t=
o the WG. =A0 So, I personally, thinks it&#39;s entirely up to the discreti=
on of the chairs. =A0</div>
<div><br></div><div>I do agree that the latter deadline for -00 makes it a =
tad more challenging, but I still think it&#39;s doable as a chair.=A0</div=
><div><br></div><div>Mary.=A0</div></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">
On Tue, Jul 16, 2013 at 3:36 PM, Spencer Dawkins <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawki=
ns.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On 7/16/2013 12:30 PM, Andrew Sullivan wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I _do_ think having some room (in an active WG) for 1-minute lightning talk=
-style &quot;here&#39;s my draft and here&#39;s why you should read it&quot=
; is not a bad thing (and I&#39;ve seen that be successful).<br>
</blockquote>
<br></div>
The Lovely Mary Barnes and Equally Lovely Cullen Jennings can correct me, b=
ut I&#39;m remembering that the DISPATCH chairs would offer to put up one s=
lide on drafts that had suddenly descended from the sky, too suddenly to ha=
ve generated mailing list traffic, if requested to do so, in order to famil=
iarize interested working group participants with potential future work. I =
thought that was helpful.<br>

<br>
If a working group has the agenda time to allow lightning talks that last o=
ver a minute, I think that would be fine; for what I saw in DISPATCH. 3 min=
utes would have been plenty.<br>
<br>
Thanks,<br>
<br>
Spencer<br>
</blockquote></div><br></div>

--047d7bdc90aaa5f01504e1a737da--

From fandreas@cisco.com  Tue Jul 16 21:03:35 2013
Return-Path: <fandreas@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 2BEDF21F9A19 for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 21:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.127
X-Spam-Level: 
X-Spam-Status: No, score=-10.127 tagged_above=-999 required=5 tests=[AWL=0.473, 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 5dF8LfqK2GEa for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 21:03:30 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 021A821F99E3 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 21:03:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2011; q=dns/txt; s=iport; t=1374033810; x=1375243410; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=JgtA40OMsV5FX0bVNusnngoqUETTtsSHN4M+BLORgas=; b=Yn4Slh/BHGX0haBLB5WCEJdt/wMRE2VhUy0Ho8EzgtKVGPqAVmGIcduu LxQ0LTkKKoR9/ehmCiVDFLPOZVQSEH99lr0ibHdoxz8oeLD90f8KmOL23 HGdPgHdtORIb2M4L1pdHq1ld6yBjfEC44frEfWy0DrEPhAqWXozI4WNuV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAPoV5lGtJXG9/2dsb2JhbABagwbDM4ENFnSCIwEBAQMBOEABBQsLGAkWDwkDAgECAUUGDQEFAgEBiAYGtVqPbgeDegOXXJFNgy4g
X-IronPort-AV: E=Sophos;i="4.89,682,1367971200"; d="scan'208";a="235749794"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 17 Jul 2013 04:03:29 +0000
Received: from Flemmings-MacBook-Pro.local (che-vpn-cluster-2-96.cisco.com [10.86.242.96]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6H43SIB016434;  Wed, 17 Jul 2013 04:03:28 GMT
Message-ID: <51E6178F.5060004@cisco.com>
Date: Wed, 17 Jul 2013 00:03:27 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 17 Jul 2013 04:03:35 -0000

On 7/16/13 10:59 AM, Ted Lemon wrote:
> On Jul 16, 2013, at 5:07 AM, thomas.morin@orange.com wrote:
>> Practically speaking I expect that many initial agendas will be even
>> less close to the final agendas than they usually were.
>> Wouldn't it make sense to (officially) set the agenda submission date
>> one week later, or at least a few days later ?
> This is a matter of choice for working group chairs.   You are free to announce that no drafts initially submitted after a certain date will be on the agenda.   If you add things to the agenda late, you risk pushback from people who will not have time to read the documents prior to the IETF meeting.
You risk a lot of other pushback when you start making up your own 
WG-specific rules (and rightfully so).

> The decision to merge the two deadlines was really just us being realistic: if someone wants to submit a -00 late, they just submit a -00 with minimal content before the -00 deadline, and then submit the real -00 as a -01 before the -01 deadline.   So the extra deadline creates churn and noise, but provides no benefit.
In practice, this has not been an issue though and in cases where it did 
happen, people seemed to understand it was bending the process, and that 
it was a good idea to discuss it with the chairs first if you expected 
to get on the agenda. I disagree completely that it did not provide any 
benefit; drafts were spaced better and -00 deadline enforced more timely 
raising of issues and new agenda requests.

> It's certainly not the case that someone submitting a -00 before either deadline does not already know that they want to discuss it at IETF; if they submit their agenda request late, you should just say no, and then they will know better for next time.
>
>
All true in theory, but this is not how it happens and works in 
practice. I prefer being pragmatic. It worked reasonably well the way it 
was before; it's not working well the way it's being done now.

Thanks

-- Flemming



From Ted.Lemon@nominum.com  Tue Jul 16 21:14:24 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 A825421F9B5D for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 21:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TzXK5Yu95pls for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 21:14:17 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id A2F7221F9B2A for <wgchairs@ietf.org>; Tue, 16 Jul 2013 21:14:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUeYaF2ZmCgRCXoXgqYji/72I25YreBn1@postini.com; Tue, 16 Jul 2013 21:14:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3A5731B821F for <wgchairs@ietf.org>; Tue, 16 Jul 2013 21:14:15 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1DEA7190052; Tue, 16 Jul 2013 21:14:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 21:14:15 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Flemming Andreasen <fandreas@cisco.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgADa84CAAAMCgA==
Date: Wed, 17 Jul 2013 04:14:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com>
In-Reply-To: <51E6178F.5060004@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5963709E78F66A40840952C60493BBDE@nominum.com>
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: Wed, 17 Jul 2013 04:14:24 -0000

On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
> You risk a lot of other pushback when you start making up your own WG-spe=
cific rules (and rightfully so).

It's hard to understand what you might mean by this.

> All true in theory, but this is not how it happens and works in practice.=
 I prefer being pragmatic. It worked reasonably well the way it was before;=
 it's not working well the way it's being done now.

Can you cite an example of an actual problem that has occurred because of t=
his change?


From yaakov_s@rad.com  Tue Jul 16 22:24:26 2013
Return-Path: <yaakov_s@rad.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 9E0FB21F89EB for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 22:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.098
X-Spam-Level: 
X-Spam-Status: No, score=-103.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPutVu2iu7bJ for <wgchairs@ietfa.amsl.com>; Tue, 16 Jul 2013 22:24:20 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id BE03D21F9AA3 for <wgchairs@ietf.org>; Tue, 16 Jul 2013 22:24:17 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 17 Jul 2013 08:24:23 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.03.0146.000; Wed, 17 Jul 2013 08:24:12 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HY5qnCKB/dEqG9qlFFsxAxJln21kA//9cqACAAR1ToA==
Date: Wed, 17 Jul 2013 05:24:12 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904E5F57C@EXRAD5.ad.rad.co.il>
References: <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
In-Reply-To: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0C0201.51E62A7E.000B,ss=1,fgs=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: Wed, 17 Jul 2013 05:24:26 -0000

>This is a matter of choice for working group chairs.   You are free to
>announce that no drafts initially submitted after a certain date will be
>on the agenda.   If you add things to the agenda late, you risk pushback
>from people who will not have time to read the documents prior to the=20
>IETF meeting.

A chair can certainly decide not discuss new drafts if (s)he thinks the
discussion would not be an informed one.

OTOH, when a new item is truly important and relevant,
then the chair can decide it is in the best interests of the WG to discuss =
it.

Declaring ahead of time a strict policy of no time for late submission
would rule this out (or at least force the chair to have to apologize to
others who WERE locked out who believe that their drafts are more important=
).

If you really want to announce a strict rule about this,=20
then announce locking out all drafts save one,
and give that one new idea a generous slot.

This will at least incentivize late submitters to propose something importa=
nt.

Y(J)S


From bclaise@cisco.com  Wed Jul 17 00:41:08 2013
Return-Path: <bclaise@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 9938021F9D98 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 00:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.557
X-Spam-Level: 
X-Spam-Status: No, score=-10.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 xWDNC1gNvcTT for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 00:41:03 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 3249921F9CA6 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 00:41:02 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6H7espX017338; Wed, 17 Jul 2013 09:40:54 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6H7e7hL015108; Wed, 17 Jul 2013 09:40:23 +0200 (CEST)
Message-ID: <51E64A57.4070403@cisco.com>
Date: Wed, 17 Jul 2013 09:40:07 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com> <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 17 Jul 2013 07:41:08 -0000

On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
> I agree with everything you have said here.
>
> However human nature responds to deadlines, and if we had no submission deadline, the consequence would virtually all the documents submitted on the Monday of the meeting with an expectation they would be discussed.
Exactly.
A 4th meeting per year would increase the productivity by 1/3, simply 
because there are extra deadlines.
Note: I'm not proposing to add an extra meeting
>
> In your rational, that would be met by a WG chairs applying a bar, but to avoid confusion among those working in multiple working groups, that needs to be a consistent bar. That bar is currently expressed by the submission deadline(s).
+1

Regards, Benoit
>
> Regards
>
> Keith
>
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Ted Lemon
>> Sent: 16 July 2013 16:43
>> To: <thomas.morin@orange.com>
>> Cc: wgchairs@ietf.org
>> Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off
>> date
>>
>> On Jul 16, 2013, at 8:20 AM, <thomas.morin@orange.com> wrote:
>>> Well, the final goal is sensible, but we lose the simplicity of having
>>> one deadline. As a contributor I wouldn't like to deal with X working
>>> groups having possibly X different deadlines...
>> This is no problem.   All you have to do to avoid this is to get your
>> drafts in well before the deadline, and accept that if you miss a deadline,
>> you'll have to wait until next time or beg the working group chair for
>> forgiveness.
>>
>> Personally, I would argue strongly against having any deadline at all,
>> because I think it creates a useless artificial flurry of submissions too
>> close to IETF, on the one hand, and inconveniences people who just want to
>> publish a new version of their draft but don't intend to present it at
>> IETF, on the other.
>>
>> I really would encourage working group chairs to consider IETF agenda
>> submission deadlines to be an important part of their work.   Working
>> group f2f meeting time is extraordinarily expensive, and when I attend
>> working group sessions, I get the very strong impression that a great deal
>> of it is wasted.   If you never say no to an agenda request, either you
>> have an unusually disciplined working group, or you are doing something
>> wrong.
>
>


From tjc@ecs.soton.ac.uk  Wed Jul 17 00:58:19 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 03A8921F8FDC for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 00:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLuFCHrr7Y1L for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 00:58:18 -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 9D96221F8F63 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 00:58:17 -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 r6H7wDJD010124 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 08:58:13 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6H7wDJD010124
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374047893; bh=/cnsyZMSiDvS99XqzognUhGmUUA=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=yRNtqMRnsd8Yv/QNQl83P6FtnnpZMYfwJi+pO4kKt5hcB2TnvZiCxayvZgNj67AmE rZ70mmWqmYaifx4FqrQ4pYcN4OAOyHPxPa36c3zjhM324LIROLy4/RNaz42rTOGAT1 EyR0WrcKqlkXZHeysw5369U9HgbdlnwT7RXtU4ZQ=
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 p6G8wD0544528371wN ret-id none; Wed, 17 Jul 2013 08:58:13 +0100
Received: from [192.168.1.103] (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 r6H7w8eJ029726 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Wed, 17 Jul 2013 08:58:08 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <51E64A57.4070403@cisco.com>
Date: Wed, 17 Jul 2013 08:58:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com> <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51E64A57.4070403@cisco.com> <0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
To: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6G8wD054452837100; tid=p6G8wD0544528371wN; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6H7wDJD010124
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 17 Jul 2013 07:58:19 -0000

On 17 Jul 2013, at 08:40, Benoit Claise <bclaise@cisco.com> wrote:

> On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
>> I agree with everything you have said here.
>>=20
>> However human nature responds to deadlines, and if we had no =
submission deadline, the consequence would virtually all the documents =
submitted on the Monday of the meeting with an expectation they would be =
discussed.
> Exactly.
> A 4th meeting per year would increase the productivity by 1/3, simply =
because there are extra deadlines.
> Note: I'm not proposing to add an extra meeting

Are we largely working to three major impulses per year?

Individual WGs can hold their own interim meetings, physical or via the =
network, to help push work forward. I recall discussion of coordinated =
interim meetings last year (around a RIPE65?) but I don't know how well =
that worked out. Is that something we should be looking to repeat?

>> In your rational, that would be met by a WG chairs applying a bar, =
but to avoid confusion among those working in multiple working groups, =
that needs to be a consistent bar. That bar is currently expressed by =
the submission deadline(s).
> +1

The volume of submissions over the weekend was, as expected, very large.

I think a more relevant question is perhaps whether the pace at which =
the important work gets done is deemed sufficient? Is important protocol =
work for solutions to problems that are needed today happening as fast =
as we'd like it to?=20

Tim

>=20
> Regards, Benoit
>>=20
>> Regards
>>=20
>> Keith
>>=20
>>> -----Original Message-----
>>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] =
On
>>> Behalf Of Ted Lemon
>>> Sent: 16 July 2013 16:43
>>> To: <thomas.morin@orange.com>
>>> Cc: wgchairs@ietf.org
>>> Subject: Re: WG Agendas to submit only 2 days after -00 submission =
cut-off
>>> date
>>>=20
>>> On Jul 16, 2013, at 8:20 AM, <thomas.morin@orange.com> wrote:
>>>> Well, the final goal is sensible, but we lose the simplicity of =
having
>>>> one deadline. As a contributor I wouldn't like to deal with X =
working
>>>> groups having possibly X different deadlines...
>>> This is no problem.   All you have to do to avoid this is to get =
your
>>> drafts in well before the deadline, and accept that if you miss a =
deadline,
>>> you'll have to wait until next time or beg the working group chair =
for
>>> forgiveness.
>>>=20
>>> Personally, I would argue strongly against having any deadline at =
all,
>>> because I think it creates a useless artificial flurry of =
submissions too
>>> close to IETF, on the one hand, and inconveniences people who just =
want to
>>> publish a new version of their draft but don't intend to present it =
at
>>> IETF, on the other.
>>>=20
>>> I really would encourage working group chairs to consider IETF =
agenda
>>> submission deadlines to be an important part of their work.   =
Working
>>> group f2f meeting time is extraordinarily expensive, and when I =
attend
>>> working group sessions, I get the very strong impression that a =
great deal
>>> of it is wasted.   If you never say no to an agenda request, either =
you
>>> have an unusually disciplined working group, or you are doing =
something
>>> wrong.
>>=20
>>=20
>=20


From joelja@bogus.com  Wed Jul 17 01:04:25 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 034F521F9D71 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 01:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y5gEBhlnfqJF for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 01:04:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABF921F9D12 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 01:04:23 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6H83vYm075412 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 17 Jul 2013 08:03:58 GMT (envelope-from joelja@bogus.com)
Message-ID: <51E64FE8.8090408@bogus.com>
Date: Wed, 17 Jul 2013 01:03:52 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>, "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com>	<6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup>	<8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com>	<949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com>	<51E64A57.4070403@cisco.com>	<0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk> <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 17 Jul 2013 08:03:58 +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: Wed, 17 Jul 2013 08:04:25 -0000

On 7/17/13 12:58 AM, Tim Chown wrote:
> On 17 Jul 2013, at 08:40, Benoit Claise <bclaise@cisco.com> wrote:
>
>> On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
>>> I agree with everything you have said here.
>>>
>>> However human nature responds to deadlines, and if we had no submission deadline, the consequence would virtually all the documents submitted on the Monday of the meeting with an expectation they would be discussed.
>> Exactly.
>> A 4th meeting per year would increase the productivity by 1/3, simply because there are extra deadlines.
>> Note: I'm not proposing to add an extra meeting
> Are we largely working to three major impulses per year?
>
> Individual WGs can hold their own interim meetings, physical or via the network, to help push work forward. I recall discussion of coordinated interim meetings last year (around a RIPE65?) but I don't know how well that worked out. Is that something we should be looking to repeat?
>
http://tools.ietf.org/html/draft-jaeggli-interim-observations-04

From bclaise@cisco.com  Wed Jul 17 01:46:40 2013
Return-Path: <bclaise@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 D390A21F9DD0 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 01:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.558
X-Spam-Level: 
X-Spam-Status: No, score=-10.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 sm7VdexaPkgY for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 01:46:36 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 159DD21F9958 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 01:46:35 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6H8kV3b026058; Wed, 17 Jul 2013 10:46:31 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6H8jtxq026212; Wed, 17 Jul 2013 10:46:05 +0200 (CEST)
Message-ID: <51E659C3.1010200@cisco.com>
Date: Wed, 17 Jul 2013 10:45:55 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com> <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51E64A57.4070403@cisco.com> <0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk> <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org 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, 17 Jul 2013 08:46:40 -0000

On 17/07/2013 09:58, Tim Chown wrote:
> On 17 Jul 2013, at 08:40, Benoit Claise <bclaise@cisco.com> wrote:
>
>> On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
>>> I agree with everything you have said here.
>>>
>>> However human nature responds to deadlines, and if we had no submission deadline, the consequence would virtually all the documents submitted on the Monday of the meeting with an expectation they would be discussed.
>> Exactly.
>> A 4th meeting per year would increase the productivity by 1/3, simply because there are extra deadlines.
>> Note: I'm not proposing to add an extra meeting
> Are we largely working to three major impulses per year?
If the metric is the draft publication rate, I guess so:
http://www.arkko.com/tools/stats/pubdistr.html

Regards, Benoit

From tjc@ecs.soton.ac.uk  Wed Jul 17 03:55:39 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 455D821F9AE9 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 03:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fF-DTw5kq5nE for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 03:55:38 -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 335DC21F9A06 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 03:55:38 -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 r6HAtWjs029759 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 11:55:32 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6HAtWjs029759
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1374058532; bh=1o9hnTZ2howjcd7CXi8hztwCQzY=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=cdpalG61ezb4u7G+8CvkYDWEFVzEENQvAF4MJQ/CA5LyNKmbnq1AuOgPzWnAEuhJI mpcIWLYFVo6XpnWjKJgjPd9tezb8+HF5xEnQfKnuLpLwBSe/jJIWrTw9WOO3XzeBix WmN5Q5K87SZIysZySfgyZCJhFfQ2DupsaMg2EAVQ=
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 p6GByW0544530872Kd ret-id none; Wed, 17 Jul 2013 11:55:32 +0100
Received: from dhcp-206-144.wireless.soton.ac.uk (dhcp-206-144.wireless.soton.ac.uk [152.78.206.144] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6HAtSs0023494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Wed, 17 Jul 2013 11:55:28 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <51E659C3.1010200@cisco.com>
Date: Wed, 17 Jul 2013 11:55:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|1df2805172b1f37aa0588d317035dd3bp6GByW03tjc|ecs.soton.ac.uk|8CB2EAEA-1B2B-4BD6-9A57-E0DF635BF594@ecs.soton.ac.uk>
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com> <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51E64A57.4070403@cisco.com> <0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk> <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk> <51E659C3.1010200@cisco.com> <8CB2EAEA-1B2B-4BD6-9A57-E0DF635BF594@ecs.soton.ac.uk>
To: "wgchairs@ietf.org Chairs" <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6GByW054453087200; tid=p6GByW0544530872Kd; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6HAtWjs029759
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 17 Jul 2013 10:55:39 -0000

On 17 Jul 2013, at 09:45, Benoit Claise <bclaise@cisco.com> wrote:

> On 17/07/2013 09:58, Tim Chown wrote:
>> On 17 Jul 2013, at 08:40, Benoit Claise <bclaise@cisco.com> wrote:
>>=20
>>> On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
>>>> I agree with everything you have said here.
>>>>=20
>>>> However human nature responds to deadlines, and if we had no =
submission deadline, the consequence would virtually all the documents =
submitted on the Monday of the meeting with an expectation they would be =
discussed.
>>> Exactly.
>>> A 4th meeting per year would increase the productivity by 1/3, =
simply because there are extra deadlines.
>>> Note: I'm not proposing to add an extra meeting
>> Are we largely working to three major impulses per year?
> If the metric is the draft publication rate, I guess so:
> http://www.arkko.com/tools/stats/pubdistr.html

I assume the counting method has changed for Jari's chart?

Tim


From stig@venaas.com  Wed Jul 17 11:28:39 2013
Return-Path: <stig@venaas.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 4027611E80CC for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 11:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3msuDPHl0P1M for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 11:28:38 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 9D39511E80BA for <wgchairs@ietf.org>; Wed, 17 Jul 2013 11:28:38 -0700 (PDT)
Received: from [10.154.208.136] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 73B147FB1; Wed, 17 Jul 2013 20:28:34 +0200 (CEST)
Message-ID: <51E6E24F.4090008@venaas.com>
Date: Wed, 17 Jul 2013 11:28:31 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 17 Jul 2013 18:28:39 -0000

On 7/16/2013 9:14 PM, Ted Lemon wrote:
> On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
>> You risk a lot of other pushback when you start making up your own WG-specific rules (and rightfully so).
>
> It's hard to understand what you might mean by this.
>
>> All true in theory, but this is not how it happens and works in practice. I prefer being pragmatic. It worked reasonably well the way it was before; it's not working well the way it's being done now.
>
> Can you cite an example of an actual problem that has occurred because of this change?

As a chair I can't, but as an individual participant I do. It gives me
less time to read up on new proposals. Before I had an extra week for
those new proposals.

I read there were cases when people uploaded a 00 as a place order,
cheating the system, but I think the majority of the 00s had real
content.

I don't mind a single deadline, but I'm wondering if it's better to
make the deadline for all drafts earlier (that is move the deadline
for updates, rather than the deadline for initial drafts).

Stig



From Ted.Lemon@nominum.com  Wed Jul 17 11:44:01 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 5425621E804D for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 11:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oj5+vcQETigB for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 11:43:54 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 21EFE21F9C70 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 11:43:52 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKUebl566pR74c82G+wYX/m5eY+7BAeD8h@postini.com; Wed, 17 Jul 2013 11:43:52 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9A4A81B821F for <wgchairs@ietf.org>; Wed, 17 Jul 2013 11:43:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 80E9B190052; Wed, 17 Jul 2013 11:43:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 17 Jul 2013 11:43:51 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Stig Venaas <stig@venaas.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgADa84CAAAMCgIAA7rGAgAAERwA=
Date: Wed, 17 Jul 2013 18:43:51 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775216946@mbx-01.win.nominum.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E6E24F.4090008@venaas.com>
In-Reply-To: <51E6E24F.4090008@venaas.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: <E2E13501893EE6449587A501272EA15B@nominum.com>
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: Wed, 17 Jul 2013 18:44:01 -0000

On Jul 17, 2013, at 11:28 AM, Stig Venaas <stig@venaas.com> wrote:
> As a chair I can't, but as an individual participant I do. It gives me
> less time to read up on new proposals. Before I had an extra week for
> those new proposals.

Wouldn't it be better to have, say, six months, rather than only two weeks,=
 to read up on proposals before attending IETF?   I don't mean to minimize =
the issue, but as an AD I typically read a dozen documents every two weeks,=
 sometimes hundreds of pages.   My experience is that this actually require=
s something like 16 to 24 working hours, and I could probably do it faster =
if I didn't get distracted by email.

This seems like a time management problem to me=97there is no way you can't=
 get through the documents you need to read in the two weeks prior to IETF =
if you make it a priority, but of course like everyone else you have other =
demands on your time.

I don't think there is one right answer to this question, and I certainly w=
ouldn't want it to be the case that I didn't find out what documents would =
be discussed until the Friday before IETF, but the difference between two w=
eeks and three doesn't seem that significant to me=97that is, it doesn't me=
et the criterion of being an actual problem, but more like a matter of pers=
onal preference.


From fandreas@cisco.com  Wed Jul 17 16:27:55 2013
Return-Path: <fandreas@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 9302721F969F for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 CK7ydV8g93Rv for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:27:50 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id E75C921F967C for <wgchairs@ietf.org>; Wed, 17 Jul 2013 16:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2156; q=dns/txt; s=iport; t=1374103670; x=1375313270; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=/g/v3gdK6ZiTsg4vBZgrwfmkTcgYwGqPJzc9cC9Mi28=; b=dUyHwvGBNYa6IdAKcybHt2s/jMDAllGoKM44bTS6R68fMUx3ewc7B0Ov eh7aqR8urPsXyGdrR3j7waaksv6bNihvL8UpilkL3xek+Re+IVg/se3cr E3gpYj2Z+H4P+n5OecYhUdjkmvuGCbdOioPo2oOCqAfMh+JofinHS49D0 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAA4n51GrRDoJ/2dsb2JhbABagwbBQ4EQFnSCIwEBAQQ4QAEQCxgJFg8JAwIBAgFFBg0BBQIBAYgLtjKPegeDewOXXJFNgy4g
X-IronPort-AV: E=Sophos;i="4.89,688,1367971200"; d="scan'208";a="83802389"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 17 Jul 2013 23:27:49 +0000
Received: from Flemmings-MacBook-Pro.local ([10.156.8.45]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6HNRmkj023282; Wed, 17 Jul 2013 23:27:48 GMT
Message-ID: <51E72874.1040004@cisco.com>
Date: Wed, 17 Jul 2013 19:27:48 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 17 Jul 2013 23:27:55 -0000

On 7/17/13 12:14 AM, Ted Lemon wrote:
> On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
>> You risk a lot of other pushback when you start making up your own WG-specific rules (and rightfully so).
> It's hard to understand what you might mean by this.
When you have a single set of consistent rules that are written down, 
it's easy for everybody to understand and accept. When the rules are WG 
specific and are created at the discretion of the WG chairs it becomes 
more of a challange:
1) Chairs now have the ability to define rules that influence desired 
outcomes (which is not to say they will)
2) People may believe that chairs in fact exercise 1), especially when 
things don't go as they like.

Neither is desirable.
>> All true in theory, but this is not how it happens and works in practice. I prefer being pragmatic. It worked reasonably well the way it was before; it's not working well the way it's being done now.
> Can you cite an example of an actual problem that has occurred because of this change?
>
>
Sure. I'm travelling this week and had to scramble last night to look at 
several -00 drafts that were requested to be on the agenda. I had to get 
on a 5:30 am call this morning to coordinate the draft agenda with my 
co-chair due to the impending draft agenda deadline. The result feels a 
bit rushed with little time to dig into exactly what the issues are in 
the drafts and hence what to prioritize and with how much time allocated.

Another example involves a -00 draft that was submitted a little more 
than a week ago to DISPATCH. The authors weren't quite sure which group 
it belonged to, asked for an MMUSIC slot, and it then bounced around 
between several WG chairs. By the time we all agreed it indeed did 
belong to DISPATCH, it was all too late because DISPATCH hadn't received 
an agenda request in time.

We can all agree that none of this would happen if people submitted 
their drafts earlier. Human nature and work commitments being what they 
are, earlier draft deadlines seem to work a lot better at facilitating 
that.

Thanks

-- Flemming






From fandreas@cisco.com  Wed Jul 17 16:32:01 2013
Return-Path: <fandreas@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 8106E11E80E2 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 VHmX7Fj1NYHG for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:31:56 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 48D3221F9814 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 16:31:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1856; q=dns/txt; s=iport; t=1374103916; x=1375313516; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uTcKT9GXQjXLaqOTf/5H0iiXyzT6L1e1Ac19dR+lAbc=; b=LwSEUJZctVKtE86YWxHVO2Sngp8b6pDP4zTiarYiZjCJVVIBa9kRkK5f A6kOf1mY4DIfYsk3AWNAud7Um1NHwF1e7zbfVEP8nX1hIJp/qAezhjL9K 3i+/u1x1SxYVnowbqUEXoJKSrSM2AuAjnBGrEbf8jrlT+lb8gN4o76sMy g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAA4n51GrRDoG/2dsb2JhbABaDoJ4wUOBEBZ0giMBAQEDAThAARALDgoJFg8JAwIBAgFFBg0BBQIBAReHbwW2Mo96B4N7A5dckU2CVFog
X-IronPort-AV: E=Sophos;i="4.89,688,1367971200"; d="scan'208";a="86376924"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 17 Jul 2013 23:31:52 +0000
Received: from Flemmings-MacBook-Pro.local ([10.156.8.45]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6HNVpge021127; Wed, 17 Jul 2013 23:31:51 GMT
Message-ID: <51E72966.3010708@cisco.com>
Date: Wed, 17 Jul 2013 19:31:50 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <CE0ADA6B.24BAF%Lee.Howard@twcable.com> <6291_1373988049_51E564D1_6291_2532_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D07501B39@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213C24@mbx-01.win.nominum.com> <949EF20990823C4C85C18D59AA11AD8B06AF19@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51E64A57.4070403@cisco.com> <0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk> <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|376011b2f082676596c987ed3c0460a4p6G8wD03tjc|ecs.soton.ac.uk|0758CB2D-6589-49E5-AC90-09BCF79DB5C3@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "wgchairs@ietf.org 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, 17 Jul 2013 23:32:01 -0000

On 7/17/13 3:58 AM, Tim Chown wrote:
> On 17 Jul 2013, at 08:40, Benoit Claise <bclaise@cisco.com> wrote:
>
>> On 16/07/2013 18:35, DRAGE, Keith (Keith) wrote:
>>> I agree with everything you have said here.
>>>
>>> However human nature responds to deadlines, and if we had no submission deadline, the consequence would virtually all the documents submitted on the Monday of the meeting with an expectation they would be discussed.
>> Exactly.
>> A 4th meeting per year would increase the productivity by 1/3, simply because there are extra deadlines.
>> Note: I'm not proposing to add an extra meeting
> Are we largely working to three major impulses per year?
Yes.
> Individual WGs can hold their own interim meetings, physical or via the network, to help push work forward. I recall discussion of coordinated interim meetings last year (around a RIPE65?) but I don't know how well that worked out. Is that something we should be looking to repeat?
Getting Interim meetings (even virtual ones) scheduled for specific 
topics with enough key participants for a single WG turns out to be 
surprisingly difficult. I can only imagine how hard it would be with 
multiple WGs.

>>> In your rational, that would be met by a WG chairs applying a bar, but to avoid confusion among those working in multiple working groups, that needs to be a consistent bar. That bar is currently expressed by the submission deadline(s).
>> +1
> The volume of submissions over the weekend was, as expected, very large.
>
> I think a more relevant question is perhaps whether the pace at which the important work gets done is deemed sufficient? Is important protocol work for solutions to problems that are needed today happening as fast as we'd like it to?
Clearly not. How to actually fix that is a much harder question though.

Thanks

-- Flemming


From Ted.Lemon@nominum.com  Wed Jul 17 16:51:15 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 D2F0821F8FF3 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S00lHafzanfg for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 16:51:03 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF9721F9AD6 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 16:51:02 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUect5FclHlTJpZeC1sfm/WNF6j8ag4Ld@postini.com; Wed, 17 Jul 2013 16:51:02 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 C6A2C1B8250 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 16:51:00 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id ABD9E190060; Wed, 17 Jul 2013 16:51:00 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 17 Jul 2013 16:51:00 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Flemming Andreasen <fandreas@cisco.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOgh0HEyqkRtiU9k6XqdpbNzexppln21kAgADa84CAAAMCgIABQk8AgAAGeoA=
Date: Wed, 17 Jul 2013 23:50:59 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com>
In-Reply-To: <51E72874.1040004@cisco.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: <90027BF5C1548F49BC662B851FA8B46D@nominum.com>
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: Wed, 17 Jul 2013 23:51:16 -0000

On Jul 17, 2013, at 4:27 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
> We can all agree that none of this would happen if people submitted their=
 drafts earlier. Human nature and work commitments being what they are, ear=
lier draft deadlines seem to work a lot better at facilitating that.

No, we can't all agree to that.   This is purely situational.  You aren't d=
escribing problems with the policy=97you are describing situations that cam=
e up that related to the policy, and that went wrong for reasons having to =
do with circumstances.   Someone published a -00 draft two weeks before IET=
F with no idea which working group it should be presented in.  This is grea=
t: it shouldn't be presented in _any_ working group at the upcoming IETF, b=
ecause it's too late.   Unless it's really important, in which case presuma=
bly we already know where it will be presented.

You were traveling and had to scramble.   That's because you were traveling=
 at the time of the deadline; if the deadline had been a week earlier, some=
one else's travel would have overlapped it, and it would have been a proble=
m for them.   There is no deadline that occurs at a time when nobody is tra=
veling.

As for your pushback answer, the fact is that people can see patterns in te=
a leaves and think that they predict the future.   It's always possible for=
 someone to interpret your actions as a working group chair as biased in so=
me way.   Chances are your actions _are_ biased sometimes.   None of us are=
 perfect.   So if someone accuses you of bias, that's just something you ne=
ed to deal with as a working group chair; the deadline has nothing to do wi=
th it.


From fandreas@cisco.com  Wed Jul 17 17:32:04 2013
Return-Path: <fandreas@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 EFA3B21F99CD for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 17:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 xwKYjMOovj2W for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 17:31:54 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 1B07021F99E8 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 17:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2578; q=dns/txt; s=iport; t=1374107508; x=1375317108; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=nLXtyy3Bb+1Zqz3Ke227liGEIPcXm25JD694yaUnbPU=; b=Kw8IJsjNsuDraUGt6bHCmQGp4B9X8M21LXW4ImNqTz/0juttVZ6w6vyG 7uVKx0PrhFYSV7QeA3kvvfK+uwnBxDzaI6lOLbDWIM4SWlTECJKwZJ5gU DyrntbfHMrU6Q4Es1TvRhgoa7BGL2z+vXKCP/WmtArTKw3kLYvAv3LzaQ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAA4251GrRDoJ/2dsb2JhbABagwbBQ4EQFnSCIwEBAQMBMgEFQAEFCwsYCRYPCQMCAQIBRQYNAQUCAQGIBgW2Oo96B4N7A5dckU2DLiA
X-IronPort-AV: E=Sophos;i="4.89,688,1367971200"; d="scan'208";a="83807672"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 18 Jul 2013 00:31:47 +0000
Received: from Flemmings-MacBook-Pro.local ([10.156.8.45]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6I0VkY8027404; Thu, 18 Jul 2013 00:31:46 GMT
Message-ID: <51E73772.1050209@cisco.com>
Date: Wed, 17 Jul 2013 20:31:46 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
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: Thu, 18 Jul 2013 00:32:04 -0000

On 7/17/13 7:50 PM, Ted Lemon wrote:
> On Jul 17, 2013, at 4:27 PM, Flemming Andreasen <fandreas@cisco.com> wrote:
>> We can all agree that none of this would happen if people submitted their drafts earlier. Human nature and work commitments being what they are, earlier draft deadlines seem to work a lot better at facilitating that.
> No, we can't all agree to that.   This is purely situational.  You aren't describing problems with the policy—you are describing situations that came up that related to the policy, and that went wrong for reasons having to do with circumstances.   Someone published a -00 draft two weeks before IETF with no idea which working group it should be presented in.  This is great: it shouldn't be presented in _any_ working group at the upcoming IETF, because it's too late.   Unless it's really important, in which case presumably we already know where it will be presented.
Why do we have a draft deadline if people meeting that deadline can't 
have their documents discussed at the meeting because they submitted 
their documents "too late" ?

> You were traveling and had to scramble.   That's because you were traveling at the time of the deadline; if the deadline had been a week earlier, someone else's travel would have overlapped it, and it would have been a problem for them.   There is no deadline that occurs at a time when nobody is traveling.
True, but the point here is that with with a window of only 2 days, it 
is very difficult to work around such conflicts when they occur. This is 
different from having a deadline known ahead of time where you could 
actually have done the work beforehand.

> As for your pushback answer, the fact is that people can see patterns in tea leaves and think that they predict the future.   It's always possible for someone to interpret your actions as a working group chair as biased in some way.   Chances are your actions _are_ biased sometimes.   None of us are perfect.   So if someone accuses you of bias, that's just something you need to deal with as a working group chair; the deadline has nothing to do with it.
No, but falling back on WG chairs having to come up with their own 
deadline rules because the draft deadline for IETF meeting X doesn't 
actually work for drafts to be potentially discussed at meeting X seems 
backwards and only invites people to perceive such bias. Why wouldn't 
there be a consistent set of IETF rules ?

I fail to see what benefits we have achieved with these -00 cutoff 
dates, but I do see problems.

Thanks

-- Flemming



From presnick@qti.qualcomm.com  Wed Jul 17 18:46:10 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 9CE5321F9C82 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 18:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 jlvG-lbfx27P for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 18:46:01 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id B128521F9C86 for <wgchairs@ietf.org>; Wed, 17 Jul 2013 18:46:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1374111961; x=1405647961; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=IZQyJmV73Pf61wyVyLRdtdP0wppyNVa8PiLWtS9ZWGc=; b=Tt7HOtqN606O/F8SmI7g868q0g+IdQRpNvuDy8aVlw0vfsoxYxm1YUG8 f1n5qy8hgw5hP75mpyqFD1HiEzXjMn62RUqyqTw3+zpuJ8HGz1yD1kYZB /ywj10UYwwN2Yd4nfCq/NG2/BIf7hYn7ctMC8cqcCQSK4/25lY4s6krmC I=;
X-IronPort-AV: E=Sophos;i="4.89,689,1367996400"; d="scan'208";a="47716516"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 17 Jul 2013 18:46:01 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 17 Jul 2013 18:45:37 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 17 Jul 2013 18:45:36 -0700
Message-ID: <51E748BF.4080702@qti.qualcomm.com>
Date: Wed, 17 Jul 2013 20:45:35 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Flemming Andreasen <fandreas@cisco.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup>	<8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com>	<51E6178F.5060004@cisco.com>	<8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com>	<51E72874.1040004@cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com>
In-Reply-To: <51E73772.1050209@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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: Thu, 18 Jul 2013 01:46:10 -0000

On 7/17/13 7:31 PM, Flemming Andreasen wrote:

> Why do we have a draft deadline if people meeting that deadline can't 
> have their documents discussed at the meeting because they submitted 
> their documents "too late" ?

Well, the question for some of us is, "Why have an IETF-wide draft 
deadline at all?" Since we automated draft submission and it no longer 
requires by-hand processing, I've never thought that such a deadline was 
needed. But I understand that some chairs like the ability for "the 
system" to default to "no" for a set number of weeks before the meeting. 
I can live with that, but I think we need some flexibility. See below:

> No, but falling back on WG chairs having to come up with their own 
> deadline rules because the draft deadline for IETF meeting X doesn't 
> actually work for drafts to be potentially discussed at meeting X 
> seems backwards and only invites people to perceive such bias. Why 
> wouldn't there be a consistent set of IETF rules ?

Because different WGs operate differently. In some high-volume WGs, it 
might be very disruptive to have drafts discussed at the meeting that 
haven't been available at least since the last meeting. For some smaller 
WGs, the ability to post up until a week before the meeting might be 
perfectly reasonable. The point is that one deadline is not sensible for 
all groups.

I've said before: I think the submission tool should always accept 
submissions, but during the IETF-wide embargo period (which could be 
even longer if we made this tool change) they would go into a holding 
area, not posted. Chairs would get a notification and could release them 
if they chose to do so. ADs could also release them. If you wanted to 
get fancy, perhaps documents for WGs that aren't meeting would auto-release.

I don't buy the perceived bias problem. So long as the chair sets up 
reasonable and consistent rules ahead of time, and is fair in making 
exceptions to those rules, there shouldn't be a problem. If there is a 
problem, it's probably time to fire the chair.

pr

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


From david.black@emc.com  Wed Jul 17 19:51:12 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 E962C21F8BD8 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 19:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 sqUo9YUhKD2b for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 19:50:47 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 556ED21F9ABB for <wgchairs@ietf.org>; Wed, 17 Jul 2013 19:50:45 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6I2oWkQ004648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jul 2013 22:50:32 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 17 Jul 2013 22:50:14 -0400
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6I2oCVF001557; Wed, 17 Jul 2013 22:50:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Wed, 17 Jul 2013 22:50:12 -0400
From: "Black, David" <david.black@emc.com>
To: Flemming Andreasen <fandreas@cisco.com>
Date: Wed, 17 Jul 2013 22:50:11 -0400
Subject: "too late" drafts and meeting time
Thread-Topic: "too late" drafts and meeting time
Thread-Index: Ac6DTkck2TomqhwWQOynBsTkqDHaNQAEhF3A
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com>
In-Reply-To: <51E73772.1050209@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
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: Thu, 18 Jul 2013 02:51:13 -0000

> Why do we have a draft deadline if people meeting that deadline can't
> have their documents discussed at the meeting because they submitted
> their documents "too late" ?

Melinda Shore recently sent a cogent answer on that to the OPSAWG list:

  We've been getting a lot of requests for time on the agenda for
  the upcoming meeting to "present" drafts which haven't been
  discussed on the mailing list.  This is a reminder that the purpose
  of meetings is face-to-face discussion of issues that haven't
  been able to make progress on the mailing list, and to progress
  deliverables.  The IETF is somewhat different from other standards
  bodies in that meeting time is generally not used for presentation
  of new material, and that the work of the organization is primarily
  done via working group mailing lists.  The most reliable way to
  get time on a meeting agenda is to have a lively discussion on
  the mailing list prior to the meeting.

There is a common misperception that meeting the draft submission
deadline "entitles" a draft to "presentation" time in the WG meeting.
The IETF simply does not work that way ...

If a "too late" draft generates lively (and appropriate) mailing list
discussion, I have no problem bashing the WG agenda at the start of
the meeting to spend time on that topic.

Thanks,
--David

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf
> Of Flemming Andreasen
> Sent: Wednesday, July 17, 2013 8:32 PM
> To: Ted Lemon
> Cc: wgchairs@ietf.org
> Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-of=
f
> date
>=20
>=20
> On 7/17/13 7:50 PM, Ted Lemon wrote:
> > On Jul 17, 2013, at 4:27 PM, Flemming Andreasen <fandreas@cisco.com> wr=
ote:
> >> We can all agree that none of this would happen if people submitted th=
eir
> drafts earlier. Human nature and work commitments being what they are, ea=
rlier
> draft deadlines seem to work a lot better at facilitating that.
> > No, we can't all agree to that.   This is purely situational.  You aren=
't
> describing problems with the policy-you are describing situations that ca=
me up
> that related to the policy, and that went wrong for reasons having to do =
with
> circumstances.   Someone published a -00 draft two weeks before IETF with=
 no
> idea which working group it should be presented in.  This is great: it
> shouldn't be presented in _any_ working group at the upcoming IETF, becau=
se
> it's too late.   Unless it's really important, in which case presumably w=
e
> already know where it will be presented.
> Why do we have a draft deadline if people meeting that deadline can't
> have their documents discussed at the meeting because they submitted
> their documents "too late" ?
>=20
> > You were traveling and had to scramble.   That's because you were trave=
ling
> at the time of the deadline; if the deadline had been a week earlier, som=
eone
> else's travel would have overlapped it, and it would have been a problem =
for
> them.   There is no deadline that occurs at a time when nobody is traveli=
ng.
> True, but the point here is that with with a window of only 2 days, it
> is very difficult to work around such conflicts when they occur. This is
> different from having a deadline known ahead of time where you could
> actually have done the work beforehand.
>=20
> > As for your pushback answer, the fact is that people can see patterns i=
n tea
> leaves and think that they predict the future.   It's always possible for
> someone to interpret your actions as a working group chair as biased in s=
ome
> way.   Chances are your actions _are_ biased sometimes.   None of us are
> perfect.   So if someone accuses you of bias, that's just something you n=
eed
> to deal with as a working group chair; the deadline has nothing to do wit=
h it.
> No, but falling back on WG chairs having to come up with their own
> deadline rules because the draft deadline for IETF meeting X doesn't
> actually work for drafts to be potentially discussed at meeting X seems
> backwards and only invites people to perceive such bias. Why wouldn't
> there be a consistent set of IETF rules ?
>=20
> I fail to see what benefits we have achieved with these -00 cutoff
> dates, but I do see problems.
>=20
> Thanks
>=20
> -- Flemming
>=20
>=20


From ajs@anvilwalrusden.com  Wed Jul 17 23:32:37 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 20B1521F8206 for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 23:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEqG1igyuh6O for <wgchairs@ietfa.amsl.com>; Wed, 17 Jul 2013 23:32:31 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 592B121F9E1E for <wgchairs@ietf.org>; Wed, 17 Jul 2013 23:32:31 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 65D568A031 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 06:32:29 +0000 (UTC)
Date: Thu, 18 Jul 2013 02:32:27 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: "too late" drafts and meeting time
Message-ID: <20130718063227.GB32746@mx1.yitter.info>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.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: Thu, 18 Jul 2013 06:32:37 -0000

On Wed, Jul 17, 2013 at 10:50:11PM -0400, Black, David wrote:

> If a "too late" draft generates lively (and appropriate) mailing list
> discussion, I have no problem bashing the WG agenda at the start of
> the meeting to spend time on that topic.

Exactly.  And if the complaint on the part of chairs is that making
these sorts of decisions exposes them to too much criticism, my
response is then, "Please give the chair to someone else."  That's why
we have the dot: to make those decisions and take the heat for them.

I am very much more in favour of chairs exercising this sort of
discipline over meeting time than I am in favour of adding Friday
afternoon and even Saturday sessions to the agenda.  And let's not
misunderstand: those are the current live options.  Either we, all of
us chairs, make meetings both more efficient and more productive; or,
the IETF meeting as a whole will last more than a week when travel is
counted.  I suggest that the time between, "meeting goes Sunday
through Sunday" and "let's stop having One Big IETF Meeting" will be
measurable in deciseconds.  I think that will be a shame, because the
only remaining thread connecting us to cross-area review will be cut.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dcrocker@bbiw.net  Thu Jul 18 07:16:08 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 3AD0A21E80F2 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 07:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 JHrFw0oXKzBn for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 07:16:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF9821F9E6B for <wgchairs@ietf.org>; Thu, 18 Jul 2013 07:16:03 -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 r6IEFxll011526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <wgchairs@ietf.org>; Thu, 18 Jul 2013 07:16:02 -0700
Message-ID: <51E7F87B.2070709@bbiw.net>
Date: Thu, 18 Jul 2013 07:15:23 -0700
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: wgchairs@ietf.org
Subject: Re: "too late" drafts and meeting time
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com> <20130718063227.GB32746@mx1.yitter.info>
In-Reply-To: <20130718063227.GB32746@mx1.yitter.info>
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, 18 Jul 2013 07:16:02 -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: Thu, 18 Jul 2013 14:16:08 -0000

> I am very much more in favour of chairs exercising this sort of
> discipline over meeting time than I am in favour of adding Friday
> afternoon and even Saturday sessions to the agenda.


That's the essence of the disparity here:  Sustaining an artificial, 
universal, inflexible deadline on everyone, vs. requiring that WG Chairs 
to actually manage their working groups, including setting whatever 
limits on the meeting agenda make sense for the working group.

I'm for the latter.  It's not exactly an onerous task, and if the wg is 
problematic enough so that the task /is/ onerous, the wg has bigger 
problems...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From kent@bbn.com  Thu Jul 18 08:23:20 2013
Return-Path: <kent@bbn.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 104C821F9635 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 08:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkJLBpA3vNLG for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 08:23:10 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8F90421F8FCE for <wgchairs@ietf.org>; Thu, 18 Jul 2013 08:23:05 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:57915) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Uzq2p-0006UO-Um; Thu, 18 Jul 2013 11:23:04 -0400
Message-ID: <51E80857.9000100@bbn.com>
Date: Thu, 18 Jul 2013 11:23:03 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: "too late" drafts and meeting time
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com> <20130718063227.GB32746@mx1.yitter.info> <51E7F87B.2070709@bbiw.net>
In-Reply-To: <51E7F87B.2070709@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; 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: Thu, 18 Jul 2013 15:23:20 -0000

+1
>
>> I am very much more in favour of chairs exercising this sort of
>> discipline over meeting time than I am in favour of adding Friday
>> afternoon and even Saturday sessions to the agenda.
>
>
> That's the essence of the disparity here:  Sustaining an artificial, 
> universal, inflexible deadline on everyone, vs. requiring that WG 
> Chairs to actually manage their working groups, including setting 
> whatever limits on the meeting agenda make sense for the working group.
>
> I'm for the latter.  It's not exactly an onerous task, and if the wg 
> is problematic enough so that the task /is/ onerous, the wg has bigger 
> problems...
>
> d/
>


From ietf-secretariat@ietf.org  Thu Jul 18 08:34:45 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 92B9221F999B; Thu, 18 Jul 2013 08:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, 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 EhArZSEXhi54; Thu, 18 Jul 2013 08:34:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 456F921E8088; Thu, 18 Jul 2013 08:33:54 -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 87 - Early Bird Registration Cutoff: Friday, 19 July
X-Test-IDTracker: no
X-IETF-IDTracker: 4.53
Message-ID: <20130718153354.15599.52397.idtracker@ietfa.amsl.com>
Date: Thu, 18 Jul 2013 08:33:54 -0700
Cc: wgchairs@ietf.org, 87all@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: Thu, 18 Jul 2013 15:34:46 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

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

1. Registration
A. Early-Bird Registration - USD 650.00 Pay by Friday, 19 July 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. All fees include 19% VAT
F. Registration Cancellation   =

        Cut-off for registration cancellation is Monday,
        22 July 2013 at UTC 24:00.
        Cancellations are subject to a 10% (ten percent)
        cancellation fee if requested by that date and time.
G. Online Registration and Payment ends Friday, 26 July 2013, 1700 local Be=
rlin time.
H. On-site Registration starting Sunday, 28 July 2013 at 1100 local Berlin =
time.

Only 10 days until the Berlin IETF!

From mary.ietf.barnes@gmail.com  Thu Jul 18 08:39:40 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 C2C5B21F8DE3 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 08:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, 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 A7FPRRUnsOWU for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 08:39:40 -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 5380111E815B for <wgchairs@ietf.org>; Thu, 18 Jul 2013 08:39:37 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id a11so1852268qen.38 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 08:39:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MJFrqnB2nPY4Rbb12PXp7hu+/ES5KEB+uXkt+zE6o4k=; b=JQHpxjrqIgGiDHvL3AsKPdWCKEDjpJDnXVeSGqv2xY/bqjuf742X2oH7C1V+TcWuc4 oIJ7R3QUR6bD0dw0LhabLgfiDs2i01kXBqwVAboU3ruxcovnGkU/d+5vfEj4YzzWHt7F m8N1kSrVBo3jfPTYGnA8l8tO7EYEniTxW9Yya4EYV4rCwt7MNT2KxDKu0nnjJn3F0Mud 30WnNeXTWaJ/mx9cgUH5WfgEv8jvC1Dniy7Iqf5uD1Ffkc3u69nwqI7zjKWCZiROv2tS /KyF/1zMAKDqKDoLbWzThTJ8yhELdhaAXB7FZCW//OlClyneJukRxXAKLjH9uQ92INJD 6OfQ==
MIME-Version: 1.0
X-Received: by 10.229.163.4 with SMTP id y4mr3133451qcx.4.1374161976748; Thu, 18 Jul 2013 08:39:36 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Thu, 18 Jul 2013 08:39:36 -0700 (PDT)
In-Reply-To: <51E7F87B.2070709@bbiw.net>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com> <20130718063227.GB32746@mx1.yitter.info> <51E7F87B.2070709@bbiw.net>
Date: Thu, 18 Jul 2013 10:39:36 -0500
Message-ID: <CAHBDyN7gf-_AXHtOiCtdXh-Rs81zx9PwmAA7qOygqgNtFMm9Aw@mail.gmail.com>
Subject: Re: "too late" drafts and meeting time
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=f46d04446a137d09ed04e1cb040a
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: Thu, 18 Jul 2013 15:39:40 -0000

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

Yep - I fully agree.


On Thu, Jul 18, 2013 at 9:15 AM, Dave Crocker <dcrocker@bbiw.net> wrote:

>
>  I am very much more in favour of chairs exercising this sort of
>> discipline over meeting time than I am in favour of adding Friday
>> afternoon and even Saturday sessions to the agenda.
>>
>
>
> That's the essence of the disparity here:  Sustaining an artificial,
> universal, inflexible deadline on everyone, vs. requiring that WG Chairs to
> actually manage their working groups, including setting whatever limits on
> the meeting agenda make sense for the working group.
>
> I'm for the latter.  It's not exactly an onerous task, and if the wg is
> problematic enough so that the task /is/ onerous, the wg has bigger
> problems...
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

<div dir=3D"ltr">Yep - I fully agree.</div><div class=3D"gmail_extra"><br><=
br><div class=3D"gmail_quote">On Thu, Jul 18, 2013 at 9:15 AM, Dave Crocker=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:dcrocker@bbiw.net" target=3D"_blan=
k">dcrocker@bbiw.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am very much more in favour of chairs exercising this sort of<br>
discipline over meeting time than I am in favour of adding Friday<br>
afternoon and even Saturday sessions to the agenda.<br>
</blockquote>
<br>
<br></div>
That&#39;s the essence of the disparity here: =A0Sustaining an artificial, =
universal, inflexible deadline on everyone, vs. requiring that WG Chairs to=
 actually manage their working groups, including setting whatever limits on=
 the meeting agenda make sense for the working group.<br>

<br>
I&#39;m for the latter. =A0It&#39;s not exactly an onerous task, and if the=
 wg is problematic enough so that the task /is/ onerous, the wg has bigger =
problems...<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</font></span></blockquote></div><br></div>

--f46d04446a137d09ed04e1cb040a--

From mary.ietf.barnes@gmail.com  Thu Jul 18 11:28:28 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 37EA221E8169 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 11:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, 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 29p-rR1VRW9M for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 11:28:27 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4534D21E8161 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 11:28:01 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s1so1906075qcw.15 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 11:27:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F1kQrLLOp/asNIWQWm4sGlRLpp/VUcPRupPg3mWRJYs=; b=uuH9ysWsMRTz8NCsyw4CiJtzMByV532bu/2wswfCetvzfQ2cVgX2snxGMNi8mw7bNN S31GTdzo0Xvce8oq9NDDdnbqpqedZfvA/wmcgHqcl5b+Wa1d7gIDEH4MKDkQ77+hmfSm pH5/s5Yf2lESELopmUbDbTKZ1nWa2RU5QW/q2wj1MBQF6UXUSyJyE2QEGJX2ieQyGK0F ePASwsunJ1E8UV8K8H1wG/+7YydzdW9BFi7dsOA8oNOhSwHe2aHj5aDQuDlcKImcVc1U y7uEyqzkMzk9O0Qoo5f0IoWqPAnRjLx88EZvKuZRJgXXa7B+dxhMAKDrEmNaY5tqa1AK 1cCA==
MIME-Version: 1.0
X-Received: by 10.49.104.72 with SMTP id gc8mr14064018qeb.35.1374172079197; Thu, 18 Jul 2013 11:27:59 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Thu, 18 Jul 2013 11:27:59 -0700 (PDT)
In-Reply-To: <51E72874.1040004@cisco.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com>
Date: Thu, 18 Jul 2013 13:27:59 -0500
Message-ID: <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b677510a415f804e1cd5e55
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: Thu, 18 Jul 2013 18:28:28 -0000

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

I have on comment below on an example cited as to the problems with the
single deadline.

Mary.


On Wed, Jul 17, 2013 at 6:27 PM, Flemming Andreasen <fandreas@cisco.com>wrote:

>
> On 7/17/13 12:14 AM, Ted Lemon wrote:
>
>> On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com>
>> wrote:
>>
>>> You risk a lot of other pushback when you start making up your own
>>> WG-specific rules (and rightfully so).
>>>
>> It's hard to understand what you might mean by this.
>>
> When you have a single set of consistent rules that are written down, it's
> easy for everybody to understand and accept. When the rules are WG specific
> and are created at the discretion of the WG chairs it becomes more of a
> challange:
> 1) Chairs now have the ability to define rules that influence desired
> outcomes (which is not to say they will)
> 2) People may believe that chairs in fact exercise 1), especially when
> things don't go as they like.
>
> Neither is desirable.
>
>  All true in theory, but this is not how it happens and works in practice.
>>> I prefer being pragmatic. It worked reasonably well the way it was before;
>>> it's not working well the way it's being done now.
>>>
>> Can you cite an example of an actual problem that has occurred because of
>> this change?
>>
>>
>>  Sure. I'm travelling this week and had to scramble last night to look at
> several -00 drafts that were requested to be on the agenda. I had to get on
> a 5:30 am call this morning to coordinate the draft agenda with my co-chair
> due to the impending draft agenda deadline. The result feels a bit rushed
> with little time to dig into exactly what the issues are in the drafts and
> hence what to prioritize and with how much time allocated.
>
> Another example involves a -00 draft that was submitted a little more than
> a week ago to DISPATCH. The authors weren't quite sure which group it
> belonged to, asked for an MMUSIC slot, and it then bounced around between
> several WG chairs. By the time we all agreed it indeed did belong to
> DISPATCH, it was all too late because DISPATCH hadn't received an agenda
> request in time.
>
[MB] This one is not a particularly good example in terms of problems
caused by the deadlines.  This is an example of someone not following the
RAI/DISPATCH WG process.  It should have been no surprise to the authors
that the document should be discussed first in the DISPATCH WG, as that is
our basic process unless it's beyond obvious that it is related
specifically to an existing chartered WG.  In addition, these authors (one
of whom is not an inexperienced IETFer) should have been aware of how we
were handling documents of a similar nature as we dispatched several at the
last IETF meeting.  I think this is an example of WG shopping and not of
too late deadlines.  In particular given that the DISPATCH deadline
required that notification of intent to submit a document and desire to
discuss a topic in dispatch was June 24th, with charter proposals/problem
statements due July 1st. This document was submitted well over a week after
the last deadline.  There's nothing wrong with a WG chair flat out saying
that a document wasn't submitted in time to garner enough consideration to
warrant agenda time at the f2f meeting.  Again, the RAI/DISPATCH process
allows progression of documents without ever having been discussed at a f2f
meeting.  We should continue discussion of situations like this on the RAI
area list where there is discussion of process/structural issues that are
currently being encountered:
http://www.ietf.org/mail-archive/web/rai/current/msg01384.html
It is unfortunate for you (and not at all your fault) that your WG is in
the middle of the concerns raised, but I think the draft deadlines are the
least of your problems.
[/MB]


> We can all agree that none of this would happen if people submitted their
> drafts earlier. Human nature and work commitments being what they are,
> earlier draft deadlines seem to work a lot better at facilitating that.
>
> Thanks
>
> -- Flemming
>
>
>
>
>
>

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

<div dir=3D"ltr">I have on comment below on an example cited as to the prob=
lems with the single deadline.=A0<div><br></div><div>Mary.<br><div class=3D=
"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jul 17, 2013 at 6:=
27 PM, Flemming Andreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@=
cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=3D"i=
m">
<br>
On 7/17/13 12:14 AM, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On Jul 16, 2013, at 9:03 PM, Flemming Andreasen &lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
You risk a lot of other pushback when you start making up your own WG-speci=
fic rules (and rightfully so).<br>
</blockquote>
It&#39;s hard to understand what you might mean by this.<br>
</blockquote></div>
When you have a single set of consistent rules that are written down, it&#3=
9;s easy for everybody to understand and accept. When the rules are WG spec=
ific and are created at the discretion of the WG chairs it becomes more of =
a challange:<br>

1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)<br>
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don&#39;t go as they like.<br>
<br>
Neither is desirable.<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;margin-bottom:0=
px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex">

All true in theory, but this is not how it happens and works in practice. I=
 prefer being pragmatic. It worked reasonably well the way it was before; i=
t&#39;s not working well the way it&#39;s being done now.<br>
</blockquote>
Can you cite an example of an actual problem that has occurred because of t=
his change?<br>
<br>
<br>
</blockquote></div>
Sure. I&#39;m travelling this week and had to scramble last night to look a=
t several -00 drafts that were requested to be on the agenda. I had to get =
on a 5:30 am call this morning to coordinate the draft agenda with my co-ch=
air due to the impending draft agenda deadline. The result feels a bit rush=
ed with little time to dig into exactly what the issues are in the drafts a=
nd hence what to prioritize and with how much time allocated.<br>

<br>
Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren&#39;t quite sure which group it b=
elonged to, asked for an MMUSIC slot, and it then bounced around between se=
veral WG chairs. By the time we all agreed it indeed did belong to DISPATCH=
, it was all too late because DISPATCH hadn&#39;t received an agenda reques=
t in time.<br>
</blockquote><div>[MB] This one is not a particularly good example in terms=
 of problems caused by the deadlines. =A0This is an example of someone not =
following the RAI/DISPATCH WG process. =A0It should have been no surprise t=
o the authors that the document should be discussed first in the DISPATCH W=
G, as that is our basic process unless it&#39;s beyond obvious that it is r=
elated specifically to an existing chartered WG. =A0In addition, these auth=
ors (one of whom is not an inexperienced IETFer) should have been aware of =
how we were handling documents of a similar nature as we dispatched several=
 at the last IETF meeting. =A0I think this is an example of WG shopping and=
 not of too late deadlines. =A0In particular given that the DISPATCH deadli=
ne required that notification of intent to submit a document and desire to =
discuss a topic in dispatch was June 24th, with charter proposals/problem s=
tatements due July 1st. This document was submitted well over a week after =
the last deadline. =A0There&#39;s nothing wrong with a WG chair flat out sa=
ying that a document wasn&#39;t submitted in time to garner enough consider=
ation to warrant agenda time at the f2f meeting. =A0Again, the RAI/DISPATCH=
 process allows progression of documents without ever having been discussed=
 at a f2f meeting. =A0We should continue discussion of situations like this=
 on the RAI area list where there is discussion of process/structural issue=
s that are currently being encountered:</div>
<div><a href=3D"http://www.ietf.org/mail-archive/web/rai/current/msg01384.h=
tml">http://www.ietf.org/mail-archive/web/rai/current/msg01384.html</a></di=
v><div>It is unfortunate for you (and not at all your fault) that your WG i=
s in the middle of the concerns raised, but I think the draft deadlines are=
 the least of your problems.=A0<br>
</div><div>[/MB]</div><div><br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;bo=
rder-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:so=
lid;padding-left:1ex">

<br>
We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.<br>

<br>
Thanks<span class=3D""><font color=3D"#888888"><br>
<br>
-- Flemming<br>
<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div></div>

--047d7b677510a415f804e1cd5e55--

From keith.drage@alcatel-lucent.com  Thu Jul 18 12:10:48 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 0638011E81D6 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 12:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Dl8Oi+JaVgS for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 12:10:42 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 56F8511E81D4 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 12:10:42 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r6IJAaiu017571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 18 Jul 2013 14:10:38 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6IJAahx021883 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jul 2013 21:10:36 +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; Thu, 18 Jul 2013 21:10:36 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Flemming Andreasen <fandreas@cisco.com>
Subject: RE: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOg0VPOvASPXVymUWzIDlWAXvZvJlqoP2AgAArH5A=
Date: Thu, 18 Jul 2013 19:10:36 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com>
In-Reply-To: <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@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.39]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B06CF91FR712WXCHMBA11zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
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: Thu, 18 Jul 2013 19:10:48 -0000

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

Sorry - not buying this.

Your comment is only applicable if you buy the argument that all new propos=
als, whether in scope or out of scope of another RAI working group, go to D=
ISPATCH, and that currently does not appear to be the case. So there is the=
 case of a document being submitted, and then some evaluation occurs that m=
aybe it ought to have been in DISPATCH, after the DISPATCH deadlines have p=
assed.

Even I am not sure if a document should be in DISPATCH or not. If I read fo=
llow the DISPATCH charter alone, then there are a number of other items on =
the MMUSIC agenda that have never been dispatched to MMUSIC (or anywhere el=
se), and therefore ought to be in DISPATCH. They do fall in scope of the MM=
USIC agenda. I could point this out in a number of other working groups. EC=
RIT even has stuff on the agenda that is not in the scope of ECRIT, has nev=
er been through DISPATCH and so on.

If the deadlines for DISPATCH had not been different, then maybe there woul=
d have been different issues, but at least it is the different DISPATCH dea=
dlines that have currently ruled out the discussion of this document in Ber=
lin.

Regards

Keith

________________________________
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Mary Barnes
Sent: 18 July 2013 19:28
To: Flemming Andreasen
Cc: wgchairs@ietf.org
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off =
date

I have on comment below on an example cited as to the problems with the sin=
gle deadline.

Mary.

On Wed, Jul 17, 2013 at 6:27 PM, Flemming Andreasen <fandreas@cisco.com<mai=
lto:fandreas@cisco.com>> wrote:

On 7/17/13 12:14 AM, Ted Lemon wrote:
On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com<mailto:=
fandreas@cisco.com>> wrote:
You risk a lot of other pushback when you start making up your own WG-speci=
fic rules (and rightfully so).
It's hard to understand what you might mean by this.
When you have a single set of consistent rules that are written down, it's =
easy for everybody to understand and accept. When the rules are WG specific=
 and are created at the discretion of the WG chairs it becomes more of a ch=
allange:
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don't go as they like.

Neither is desirable.

All true in theory, but this is not how it happens and works in practice. I=
 prefer being pragmatic. It worked reasonably well the way it was before; i=
t's not working well the way it's being done now.
Can you cite an example of an actual problem that has occurred because of t=
his change?

Sure. I'm travelling this week and had to scramble last night to look at se=
veral -00 drafts that were requested to be on the agenda. I had to get on a=
 5:30 am call this morning to coordinate the draft agenda with my co-chair =
due to the impending draft agenda deadline. The result feels a bit rushed w=
ith little time to dig into exactly what the issues are in the drafts and h=
ence what to prioritize and with how much time allocated.

Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren't quite sure which group it belon=
ged to, asked for an MMUSIC slot, and it then bounced around between severa=
l WG chairs. By the time we all agreed it indeed did belong to DISPATCH, it=
 was all too late because DISPATCH hadn't received an agenda request in tim=
e.
[MB] This one is not a particularly good example in terms of problems cause=
d by the deadlines.  This is an example of someone not following the RAI/DI=
SPATCH WG process.  It should have been no surprise to the authors that the=
 document should be discussed first in the DISPATCH WG, as that is our basi=
c process unless it's beyond obvious that it is related specifically to an =
existing chartered WG.  In addition, these authors (one of whom is not an i=
nexperienced IETFer) should have been aware of how we were handling documen=
ts of a similar nature as we dispatched several at the last IETF meeting.  =
I think this is an example of WG shopping and not of too late deadlines.  I=
n particular given that the DISPATCH deadline required that notification of=
 intent to submit a document and desire to discuss a topic in dispatch was =
June 24th, with charter proposals/problem statements due July 1st. This doc=
ument was submitted well over a week after the last deadline.  There's noth=
ing wrong with a WG chair flat out saying that a document wasn't submitted =
in time to garner enough consideration to warrant agenda time at the f2f me=
eting.  Again, the RAI/DISPATCH process allows progression of documents wit=
hout ever having been discussed at a f2f meeting.  We should continue discu=
ssion of situations like this on the RAI area list where there is discussio=
n of process/structural issues that are currently being encountered:
http://www.ietf.org/mail-archive/web/rai/current/msg01384.html
It is unfortunate for you (and not at all your fault) that your WG is in th=
e middle of the concerns raised, but I think the draft deadlines are the le=
ast of your problems.
[/MB]


We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.

Thanks

-- Flemming






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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"State" /><o:SmartTagType namespaceuri=3D"urn:schemas-m=
icrosoft-com:office:smarttags" name=3D"place" /><o:SmartTagType namespaceur=
i=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"time" /><o:SmartTa=
gType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"d=
ate" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"blue">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Sorry &#8211; not buying this.<o:p></o=
:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Your comment is only applicable if you=
 buy the argument that all new proposals, whether in scope or out of scope =
of another RAI working
 group, go to DISPATCH, and that currently does not appear to be the case. =
So there is the case of a document being submitted, and then some evaluatio=
n occurs that maybe it ought to have been in DISPATCH, after the DISPATCH d=
eadlines have passed.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Even I am not sure if a document shoul=
d be in DISPATCH or not. If I read follow the DISPATCH charter alone, then =
there are a number of
 other items on the MMUSIC agenda that have never been dispatched to MMUSIC=
 (or anywhere else), and therefore ought to be in DISPATCH. They do fall in=
 scope of the MMUSIC agenda. I could point this out in a number of other wo=
rking groups. ECRIT even has stuff
 on the agenda that is not in the scope of ECRIT, has never been through DI=
SPATCH and so on.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">If the deadlines for DISPATCH had not =
been different, then maybe there would have been different issues, but at l=
east it is the different
 DISPATCH deadlines that have currently ruled out the discussion of this do=
cument in
<st1:place w:st=3D"on"><st1:State w:st=3D"on">Berlin</st1:State></st1:place=
>.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Regards<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Keith<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</=
span></font></b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma"> wgchairs-bounces@ietf.org
 [mailto:wgchairs-bounces@ietf.org] <b><span style=3D"font-weight:bold">On =
Behalf Of
</span></b>Mary Barnes<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 19:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> Flemming Andreasen<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> wgchairs@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</span></font><span lang=
=3D"EN-US"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">I have on comment below on an example cited as to the problems with=
 the single deadline.&nbsp;<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Mary.<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></sp=
an></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">On Wed,
<st1:date Year=3D"2013" Day=3D"17" Month=3D"7" ls=3D"trans" w:st=3D"on">Jul=
 17, 2013</st1:date> at
<st1:time Minute=3D"27" Hour=3D"18" w:st=3D"on">6:27 PM</st1:time>, Flemmin=
g Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fan=
dreas@cisco.com</a>&gt; wrote:<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><br>
On <st1:date Year=3D"13" Day=3D"17" Month=3D"7" ls=3D"trans" w:st=3D"on">7/=
17/13</st1:date>
<st1:time Minute=3D"14" Hour=3D"0" w:st=3D"on">12:14 AM</st1:time>, Ted Lem=
on wrote:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">On
<st1:date Year=3D"2013" Day=3D"16" Month=3D"7" ls=3D"trans" w:st=3D"on">Jul=
 16, 2013</st1:date>, at
<st1:time Minute=3D"03" Hour=3D"21" w:st=3D"on">9:03 PM</st1:time>, Flemmin=
g Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fan=
dreas@cisco.com</a>&gt; wrote:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">You risk a lot of other pushback when you start making up your own =
WG-specific rules (and rightfully so).<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">It's hard to understand what you might mean by this.<o:p></o:p></sp=
an></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">When you have a single set of consistent rules that are written dow=
n, it's easy for everybody to understand and accept. When the rules are WG =
specific and are created
 at the discretion of the WG chairs it becomes more of a challange:<br>
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)<br>
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don't go as they like.<br>
<br>
Neither is desirable.<o:p></o:p></span></font></p>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">All true in theory, but this is not how it happens and works in pra=
ctice. I prefer being pragmatic. It worked reasonably well the way it was b=
efore; it's not working
 well the way it's being done now.<o:p></o:p></span></font></p>
</blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt">Can you cite an examp=
le of an actual problem that has occurred because of this change?<br>
<br>
<o:p></o:p></span></font></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">Sure. I'm travelling this week and had to scramble last night to lo=
ok at several -00 drafts that were requested to be on the agenda. I had to =
get on a
<st1:time Minute=3D"30" Hour=3D"5" w:st=3D"on">5:30 am</st1:time> call this=
 morning to coordinate the draft agenda with my co-chair due to the impendi=
ng draft agenda deadline. The result feels a bit rushed with little time to=
 dig into exactly what the issues are
 in the drafts and hence what to prioritize and with how much time allocate=
d.<br>
<br>
Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren't quite sure which group it belon=
ged to, asked for an MMUSIC slot, and it then bounced around between severa=
l WG chairs. By the time we all
 agreed it indeed did belong to DISPATCH, it was all too late because DISPA=
TCH hadn't received an agenda request in time.<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[MB] This one is not a particularly good example in terms of proble=
ms caused by the deadlines. &nbsp;This is an example of someone not followi=
ng the RAI/DISPATCH WG process.
 &nbsp;It should have been no surprise to the authors that the document sho=
uld be discussed first in the DISPATCH WG, as that is our basic process unl=
ess it's beyond obvious that it is related specifically to an existing char=
tered WG. &nbsp;In addition, these authors
 (one of whom is not an inexperienced IETFer) should have been aware of how=
 we were handling documents of a similar nature as we dispatched several at=
 the last IETF meeting. &nbsp;I think this is an example of WG shopping and=
 not of too late deadlines. &nbsp;In particular
 given that the DISPATCH deadline required that notification of intent to s=
ubmit a document and desire to discuss a topic in dispatch was June 24th, w=
ith charter proposals/problem statements due July 1st. This document was su=
bmitted well over a week after the
 last deadline. &nbsp;There's nothing wrong with a WG chair flat out saying=
 that a document wasn't submitted in time to garner enough consideration to=
 warrant agenda time at the f2f meeting. &nbsp;Again, the RAI/DISPATCH proc=
ess allows progression of documents without
 ever having been discussed at a f2f meeting. &nbsp;We should continue disc=
ussion of situations like this on the RAI area list where there is discussi=
on of process/structural issues that are currently being encountered:<o:p><=
/o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><a href=3D"http://www.ietf.org/mail-archive/web/rai/current/msg0138=
4.html">http://www.ietf.org/mail-archive/web/rai/current/msg01384.html</a><=
o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">It is unfortunate for you (and not at all your fault) that your WG =
is in the middle of the concerns raised, but I think the draft deadlines ar=
e the least of your problems.&nbsp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[/MB]<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt"><br>
We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.<br>
<br>
Thanks<font color=3D"#888888"><span style=3D"color:#888888"><br>
<br>
-- Flemming<br>
<br>
<br>
<br>
<br>
</span></font><o:p></o:p></span></font></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_949EF20990823C4C85C18D59AA11AD8B06CF91FR712WXCHMBA11zeu_--

From mary.ietf.barnes@gmail.com  Thu Jul 18 12:28:05 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 C064B11E81D6 for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 12:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level: 
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, 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 2g69JQQUmyWd for <wgchairs@ietfa.amsl.com>; Thu, 18 Jul 2013 12:28:04 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 18E2F11E81D0 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 12:28:04 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id z10so1930949qcx.35 for <wgchairs@ietf.org>; Thu, 18 Jul 2013 12:28:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/G6yoCFQFBsKsS90Bw+IuAV47OqBPZQRe6cuejCnsn8=; b=MXLdAZ5j7QkKJwHJAIOFLM6oqdSvX7lDQkwZwe1s9fcFAIP9o01RL1W/QWRnQbTMiO OG7la5VTQ7YKdZ06m4FRA/NICTOvbOdjU1UiNjC7GP7Qsfuk0z9keVhCnnCPVeURZ65J /PjJGXYk83HA0QmVX5qPqCxRrdK8qjuDi9bTygxX7Q+Cz+I1iHOmZlDssOgkyYjL7Ozf PYbefpGtddswtdICAwrOMBSKhTfC6Art+6vrH9RlwJW4AiKD0f0gTIF+awr8lE2/HWOS FASZknaRB69JUFE4gwoAZ3YvPpeCVVZtQniebQe55Gew3a+a1iap49AO4V2pHPv96ySN L4dw==
MIME-Version: 1.0
X-Received: by 10.49.95.97 with SMTP id dj1mr14016917qeb.46.1374175683486; Thu, 18 Jul 2013 12:28:03 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Thu, 18 Jul 2013 12:28:03 -0700 (PDT)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Date: Thu, 18 Jul 2013 14:28:03 -0500
Message-ID: <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7b6da61679280104e1ce3593
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: Thu, 18 Jul 2013 19:28:05 -0000

--047d7b6da61679280104e1ce3593
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 18, 2013 at 2:10 PM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

> ********
>
> Sorry =96 not buying this.
>
[MB] Then you should raise the issue to the ADs.  I'm the implementer of a
process that is in place for managing work in their area. [/MB]

> ****
>
> ** **
>
> Your comment is only applicable if you buy the argument that all new
> proposals, whether in scope or out of scope of another RAI working group,
> go to DISPATCH, and that currently does not appear to be the case. So the=
re
> is the case of a document being submitted, and then some evaluation occur=
s
> that maybe it ought to have been in DISPATCH, after the DISPATCH deadline=
s
> have passed.
>
[MB] As I said previously, in cases where documents are clearly under the
purview for a specific WG, then it's not an issue to go directly to the WG.
 BTW, I have no idea what document you're referring to. And, keep in mind
that the process requires notifying the chairs, so it may not be visible to
you what discussions might occur offline. [/MB]

> Even I am not sure if a document should be in DISPATCH or not. If I read
> follow the DISPATCH charter alone, then there are a number of other items
> on the MMUSIC agenda that have never been dispatched to MMUSIC (or anywhe=
re
> else), and therefore ought to be in DISPATCH. They do fall in scope of th=
e
> MMUSIC agenda. I could point this out in a number of other working groups=
.
> ECRIT even has stuff on the agenda that is not in the scope of ECRIT, has
> never been through DISPATCH and so on.
>
[MB]  I only see one document on the MMUSIC WG agenda that probably should
have first gone to DISPATCH and actually, the MMUSIC chairs could have
raised that issue and suggested such to the document authors rather than
give agenda time when they certainly do have really high priority, critical
items to discuss.   The document I am referring to relates to at least two
different WGs (including one that is now closed) and wasn't at all an
obvious fit for MMUSIC.    In addition, as I said, it should have been
obvious that there was a fairly clear expectation that  the websocket and
alternate transport docs are first discussed in  DISPATCH - e.g., BFCPbis,
mrsp websocket document, etc.
[/MB]

> ****
>
> ** **
>
> If the deadlines for DISPATCH had not been different, then maybe there
> would have been different issues, but at least it is the different DISPAT=
CH
> deadlines that have currently ruled out the discussion of this document i=
n
> ****Berlin****.
>
[MB] That's absolutely correct - that's the whole intent of the DISPATCH
deadlines - these authors simply had to send an email to the DISPATCH WG
chairs by June 24th indicating they were putting together a draft that was
an alternative to a previously discussed draft.  They didn't do so.  If
they had submitted the draft by July 1st, there would have been some
flexibility, but that wasn't the case.  There were other people that did
so, that also requested agenda time that were not given agenda time because
it wasn't deemed necessary. AGain, you can progress work without discussing
at a f2f meeting.

 If you have issues with the DISPATCH process, then please bring those to
the DISPATCH WG or better yet RAI area mailing list.  We've had this
process in place for 4 years so the concept of notifying the chairs several
weeks before draft deadlines has been there the whole time. Indeed, we had
the dates for IETF-87 much later than usual.   Keep in mind as well that
there is NOTHING in the DISPATCH/RAI process that requires a document to
have f2f discussion.  Additionally, keep in mind that the document in
question has normative dependencies such that this document cannot be
published until those docs are completed. [/MB]

> ****
>
> ** **
>
> Regards****
>
> ** **
>
> Keith****
>
> ** **
>   ------------------------------
>
> *From:* wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] *On
> Behalf Of *Mary Barnes
> *Sent:* 18 July 2013 19:28
> *To:* Flemming Andreasen
>
> *Cc:* wgchairs@ietf.org
> *Subject:* Re: WG Agendas to submit only 2 days after -00 submission
> cut-off date
> ****
>
>  ** **
>
> I have on comment below on an example cited as to the problems with the
> single deadline. ****
>
> ** **
>
> Mary.****
>
> ** **
>
> On Wed, **Jul 17, 2013** at **6:27 PM**, Flemming Andreasen <
> fandreas@cisco.com> wrote:****
>
>
> On **7/17/13** **12:14 AM**, Ted Lemon wrote:****
>
> On **Jul 16, 2013**, at **9:03 PM**, Flemming Andreasen <
> fandreas@cisco.com> wrote:****
>
> You risk a lot of other pushback when you start making up your own
> WG-specific rules (and rightfully so).****
>
> It's hard to understand what you might mean by this.****
>
> When you have a single set of consistent rules that are written down, it'=
s
> easy for everybody to understand and accept. When the rules are WG specif=
ic
> and are created at the discretion of the WG chairs it becomes more of a
> challange:
> 1) Chairs now have the ability to define rules that influence desired
> outcomes (which is not to say they will)
> 2) People may believe that chairs in fact exercise 1), especially when
> things don't go as they like.
>
> Neither is desirable.****
>
> ** **
>
> All true in theory, but this is not how it happens and works in practice.
> I prefer being pragmatic. It worked reasonably well the way it was before=
;
> it's not working well the way it's being done now.****
>
> Can you cite an example of an actual problem that has occurred because of
> this change?
>
> ****
>
>  Sure. I'm travelling this week and had to scramble last night to look at
> several -00 drafts that were requested to be on the agenda. I had to get =
on
> a **5:30 am** call this morning to coordinate the draft agenda with my
> co-chair due to the impending draft agenda deadline. The result feels a b=
it
> rushed with little time to dig into exactly what the issues are in the
> drafts and hence what to prioritize and with how much time allocated.
>
> Another example involves a -00 draft that was submitted a little more tha=
n
> a week ago to DISPATCH. The authors weren't quite sure which group it
> belonged to, asked for an MMUSIC slot, and it then bounced around between
> several WG chairs. By the time we all agreed it indeed did belong to
> DISPATCH, it was all too late because DISPATCH hadn't received an agenda
> request in time.****
>
> [MB] This one is not a particularly good example in terms of problems
> caused by the deadlines.  This is an example of someone not following the
> RAI/DISPATCH WG process.  It should have been no surprise to the authors
> that the document should be discussed first in the DISPATCH WG, as that i=
s
> our basic process unless it's beyond obvious that it is related
> specifically to an existing chartered WG.  In addition, these authors (on=
e
> of whom is not an inexperienced IETFer) should have been aware of how we
> were handling documents of a similar nature as we dispatched several at t=
he
> last IETF meeting.  I think this is an example of WG shopping and not of
> too late deadlines.  In particular given that the DISPATCH deadline
> required that notification of intent to submit a document and desire to
> discuss a topic in dispatch was June 24th, with charter proposals/problem
> statements due July 1st. This document was submitted well over a week aft=
er
> the last deadline.  There's nothing wrong with a WG chair flat out saying
> that a document wasn't submitted in time to garner enough consideration t=
o
> warrant agenda time at the f2f meeting.  Again, the RAI/DISPATCH process
> allows progression of documents without ever having been discussed at a f=
2f
> meeting.  We should continue discussion of situations like this on the RA=
I
> area list where there is discussion of process/structural issues that are
> currently being encountered:****
>
> http://www.ietf.org/mail-archive/web/rai/current/msg01384.html****
>
> It is unfortunate for you (and not at all your fault) that your WG is in
> the middle of the concerns raised, but I think the draft deadlines are th=
e
> least of your problems. ****
>
> [/MB]****
>
> ** **
>
>
> We can all agree that none of this would happen if people submitted their
> drafts earlier. Human nature and work commitments being what they are,
> earlier draft deadlines seem to work a lot better at facilitating that.
>
> Thanks
>
> -- Flemming
>
>
>
>
> ****
>
>  ** **
>

--047d7b6da61679280104e1ce3593
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Thu, Jul 18, 2013 at 2:10 PM=
, 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>&gt=
;</span> wrote:<br>
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-=
width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddin=
g-left:1ex">




<u></u><u></u><u></u><u></u>

<div lang=3D"EN-GB" link=3D"blue" vlink=3D"blue">
<div>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">Sorry =96 not buying this.</span></font>=
</p></div></div></blockquote><div>[MB] Then you should raise the issue to t=
he ADs. =A0I&#39;m the implementer of a process that is in place for managi=
ng work in their area. [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang=3D"EN=
-GB" link=3D"blue" vlink=3D"blue">
<div><p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-=
size:10pt;font-family:Arial;color:navy"><u></u><u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">Your comment is only applicable if you b=
uy the argument that all new proposals, whether in scope or out of scope of=
 another RAI working
 group, go to DISPATCH, and that currently does not appear to be the case. =
So there is the case of a document being submitted, and then some evaluatio=
n occurs that maybe it ought to have been in DISPATCH, after the DISPATCH d=
eadlines have passed.</span></font></p>
</div></div></blockquote><div>[MB] As I said previously, in cases where doc=
uments are clearly under the purview for a specific WG, then it&#39;s not a=
n issue to go directly to the WG. =A0BTW, I have no idea what document you&=
#39;re referring to. And, keep in mind that the process requires notifying =
the chairs, so it may not be visible to you what discussions might occur of=
fline. [/MB]<span class=3D"" style=3D"color:rgb(0,0,128);font-family:Arial;=
font-size:13px">=A0</span></div>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang=3D"EN=
-GB" link=3D"blue" vlink=3D"blue">
<div>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">Even I am not sure if a document should =
be in DISPATCH or not. If I read follow the DISPATCH charter alone, then th=
ere are a number of
 other items on the MMUSIC agenda that have never been dispatched to MMUSIC=
 (or anywhere else), and therefore ought to be in DISPATCH. They do fall in=
 scope of the MMUSIC agenda. I could point this out in a number of other wo=
rking groups. ECRIT even has stuff
 on the agenda that is not in the scope of ECRIT, has never been through DI=
SPATCH and so on.</span></font></p></div></div></blockquote><div>[MB] =A0I =
only see one document on the MMUSIC WG agenda that probably should have fir=
st gone to DISPATCH and actually, the MMUSIC chairs could have raised that =
issue and suggested such to the document authors rather than give agenda ti=
me when they certainly do have really high priority, critical items to disc=
uss. =A0 The document I am referring to relates to at least two different W=
Gs (including one that is now closed) and wasn&#39;t at all an obvious fit =
for MMUSIC. =A0 =A0In addition, as I said, it should have been obvious that=
 there was a fairly clear expectation that =A0the websocket and alternate t=
ransport docs are first discussed in =A0DISPATCH - e.g., BFCPbis, mrsp webs=
ocket document, etc. =A0 =A0=A0</div>
<div>[/MB]</div><blockquote class=3D"gmail_quote" style=3D"margin-top:0px;m=
argin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;b=
order-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"=
>
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"blue"><div><p class=3D""><font c=
olor=3D"navy" face=3D"Arial"><span style=3D"font-size:10pt;font-family:Aria=
l;color:navy"><u></u><u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">If the deadlines for DISPATCH had not be=
en different, then maybe there would have been different issues, but at lea=
st it is the different
 DISPATCH deadlines that have currently ruled out the discussion of this do=
cument in
<u></u><u></u>Berlin<u></u><u></u>.</span></font></p></div></div></blockquo=
te><div>[MB] That&#39;s absolutely correct - that&#39;s the whole intent of=
 the DISPATCH deadlines - these authors simply had to send an email to the =
DISPATCH WG chairs by June 24th indicating they were putting together a dra=
ft that was an alternative to a previously discussed draft. =A0They didn&#3=
9;t do so. =A0If they had submitted the draft by July 1st, there would have=
 been some flexibility, but that wasn&#39;t the case. =A0There were other p=
eople that did so, that also requested agenda time that were not given agen=
da time because it wasn&#39;t deemed necessary. AGain, you can progress wor=
k without discussing at a f2f meeting.=A0</div>
<div><br></div><div>=A0If you have issues with the DISPATCH process, then p=
lease bring those to the DISPATCH WG or better yet RAI area mailing list. =
=A0We&#39;ve had this process in place for 4 years so the concept of notify=
ing the chairs several weeks before draft deadlines has been there the whol=
e time. Indeed, we had the dates for IETF-87 much later than usual. =A0 Kee=
p in mind as well that there is NOTHING in the DISPATCH/RAI process that re=
quires a document to have f2f discussion. =A0Additionally, keep in mind tha=
t the document in question has normative dependencies such that this docume=
nt cannot be published until those docs are completed. [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang=3D"EN=
-GB" link=3D"blue" vlink=3D"blue">
<div><p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-=
size:10pt;font-family:Arial;color:navy"><u></u><u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">Regards<u></u><u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy">Keith<u></u><u></u></span></font></p>
<p class=3D""><font color=3D"navy" face=3D"Arial"><span style=3D"font-size:=
10pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></font></p>
<div style=3D"border-top-style:none;border-right-style:none;border-bottom-s=
tyle:none;border-width:initial;border-color:initial;border-left-style:solid=
;border-left-color:blue;border-left-width:1.5pt;padding-top:0cm;padding-rig=
ht:0cm;padding-bottom:0cm;padding-left:4pt">

<div>
<div class=3D"" align=3D"center" style=3D"text-align:center"><font size=3D"=
3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-size:12pt">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></font></div>
<p class=3D""><b><font face=3D"Tahoma"><span lang=3D"EN-US" style=3D"font-s=
ize:10pt;font-family:Tahoma;font-weight:bold">From:</span></font></b><font =
face=3D"Tahoma"><span lang=3D"EN-US" style=3D"font-size:10pt;font-family:Ta=
homa"> <a href=3D"mailto:wgchairs-bounces@ietf.org" target=3D"_blank">wgcha=
irs-bounces@ietf.org</a>
 [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" target=3D"_blank">wgc=
hairs-bounces@ietf.org</a>] <b><span style=3D"font-weight:bold">On Behalf O=
f
</span></b>Mary Barnes<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 19:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> Flemming Andreasen</span=
></font></p><div class=3D"im"><font face=3D"Tahoma"><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:wgchai=
rs@ietf.org" target=3D"_blank">wgchairs@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</font></div><span lang=
=3D"EN-US"><u></u><u></u></span><p></p>
</div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><u></u>=A0<u></u></span></font></p>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">I have on comment below on an example cited as to the problems =
with the single deadline.=A0<u></u><u></u></span></font></p><div><div class=
=3D"h5">

<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><u></u>=A0<u></u></span></font></p>
</div>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">Mary.<u></u><u></u></span></font></p>
<div>
<p class=3D"" style=3D"margin-bottom:12pt"><font size=3D"3" face=3D"Times N=
ew Roman"><span style=3D"font-size:12pt"><u></u>=A0<u></u></span></font></p=
>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">On Wed,
<u></u>Jul 17, 2013<u></u> at
<u></u>6:27 PM<u></u>, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@ci=
sco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<u></u><u></u><=
/span></font></p>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><br>
On <u></u>7/17/13<u></u>
<u></u>12:14 AM<u></u>, Ted Lemon wrote:<u></u><u></u></span></font></p>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">On
<u></u>Jul 16, 2013<u></u>, at
<u></u>9:03 PM<u></u>, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@ci=
sco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<u></u><u></u><=
/span></font></p>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">You risk a lot of other pushback when you start making up your =
own WG-specific rules (and rightfully so).<u></u><u></u></span></font></p>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">It&#39;s hard to understand what you might mean by this.<u></u>=
<u></u></span></font></p>
</div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">When you have a single set of consistent rules that are written=
 down, it&#39;s easy for everybody to understand and accept. When the rules=
 are WG specific and are created
 at the discretion of the WG chairs it becomes more of a challange:<br>
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)<br>
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don&#39;t go as they like.<br>
<br>
Neither is desirable.<u></u><u></u></span></font></p>
<div>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-width:initial;border-color:initial;border-left-styl=
e:solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding-to=
p:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:6pt;margin-left:4.8=
pt;margin-right:0cm">

<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><u></u>=A0<u></u></span></font></p>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-width:initial;border-color:initial;border-left-styl=
e:solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding-to=
p:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:6pt;margin-left:4.8=
pt;margin-right:0cm">

<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">All true in theory, but this is not how it happens and works in=
 practice. I prefer being pragmatic. It worked reasonably well the way it w=
as before; it&#39;s not working
 well the way it&#39;s being done now.<u></u><u></u></span></font></p>
</blockquote>
<p class=3D"" style=3D"margin-bottom:12pt"><font size=3D"3" face=3D"Times N=
ew Roman"><span style=3D"font-size:12pt">Can you cite an example of an actu=
al problem that has occurred because of this change?<br>
<br>
<u></u><u></u></span></font></p>
</blockquote>
</div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">Sure. I&#39;m travelling this week and had to scramble last nig=
ht to look at several -00 drafts that were requested to be on the agenda. I=
 had to get on a
<u></u>5:30 am<u></u> call this morning to coordinate the draft agenda with=
 my co-chair due to the impending draft agenda deadline. The result feels a=
 bit rushed with little time to dig into exactly what the issues are
 in the drafts and hence what to prioritize and with how much time allocate=
d.<br>
<br>
Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren&#39;t quite sure which group it b=
elonged to, asked for an MMUSIC slot, and it then bounced around between se=
veral WG chairs. By the time we all
 agreed it indeed did belong to DISPATCH, it was all too late because DISPA=
TCH hadn&#39;t received an agenda request in time.<u></u><u></u></span></fo=
nt></p>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">[MB] This one is not a particularly good example in terms of pr=
oblems caused by the deadlines. =A0This is an example of someone not follow=
ing the RAI/DISPATCH WG process.
 =A0It should have been no surprise to the authors that the document should=
 be discussed first in the DISPATCH WG, as that is our basic process unless=
 it&#39;s beyond obvious that it is related specifically to an existing cha=
rtered WG. =A0In addition, these authors
 (one of whom is not an inexperienced IETFer) should have been aware of how=
 we were handling documents of a similar nature as we dispatched several at=
 the last IETF meeting. =A0I think this is an example of WG shopping and no=
t of too late deadlines. =A0In particular
 given that the DISPATCH deadline required that notification of intent to s=
ubmit a document and desire to discuss a topic in dispatch was June 24th, w=
ith charter proposals/problem statements due July 1st. This document was su=
bmitted well over a week after the
 last deadline. =A0There&#39;s nothing wrong with a WG chair flat out sayin=
g that a document wasn&#39;t submitted in time to garner enough considerati=
on to warrant agenda time at the f2f meeting. =A0Again, the RAI/DISPATCH pr=
ocess allows progression of documents without
 ever having been discussed at a f2f meeting. =A0We should continue discuss=
ion of situations like this on the RAI area list where there is discussion =
of process/structural issues that are currently being encountered:<u></u><u=
></u></span></font></p>

</div>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><a href=3D"http://www.ietf.org/mail-archive/web/rai/current/msg=
01384.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/rai/curr=
ent/msg01384.html</a><u></u><u></u></span></font></p>

</div>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">It is unfortunate for you (and not at all your fault) that your=
 WG is in the middle of the concerns raised, but I think the draft deadline=
s are the least of your problems.=A0<u></u><u></u></span></font></p>

</div>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt">[/MB]<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><u></u>=A0<u></u></span></font></p>
</div>
<blockquote style=3D"border-top-style:none;border-right-style:none;border-b=
ottom-style:none;border-width:initial;border-color:initial;border-left-styl=
e:solid;border-left-color:rgb(204,204,204);border-left-width:1pt;padding-to=
p:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:6pt;margin-left:4.8=
pt;margin-right:0cm">

<p class=3D"" style=3D"margin-bottom:12pt"><font size=3D"3" face=3D"Times N=
ew Roman"><span style=3D"font-size:12pt"><br>
We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.<br>

<br>
Thanks<font color=3D"#888888"><span style=3D"color:rgb(136,136,136)"><br>
<br>
-- Flemming<br>
<br>
<br>
<br>
<br>
</span></font><u></u><u></u></span></font></p>
</blockquote>
</div>
<p class=3D""><font size=3D"3" face=3D"Times New Roman"><span style=3D"font=
-size:12pt"><u></u>=A0<u></u></span></font></p>
</div>
</div>
</div></div></div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--047d7b6da61679280104e1ce3593--

From presnick@qti.qualcomm.com  Fri Jul 19 10:12:05 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 3ADEA11E8172 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:12: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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIKRYa8+o+vb for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:12:01 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 504ED11E8163 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 10:11:57 -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=1374253917; x=1405789917; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=Xxlandz39Q+tJAALr0eVwMGvNcuerphSs9VUuYVCY4o=; b=d7eRsazX7a1k5G2ZfJ2E0tC0Wh4w6hL5cCfdEq/S4vXGNwXOxpF8yupo 4ZYWku+gD6Ho+RSDNyi/BT+BCvt837qwxz6ZSN45PjqlNmDGzWFkG7je/ o5Z7ENSqR9NYmeAdBRVY/C26eBGq0kvdX5IDMAe2w5BGaJFDRpIoxtMf4 8=;
X-IronPort-AV: E=Sophos;i="4.89,703,1367996400"; d="scan'208";a="63729919"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 19 Jul 2013 10:11:57 -0700
X-IronPort-AV: E=Sophos;i="4.89,702,1367996400"; d="scan'208";a="517138482"
Received: from nasanexhc17.na.qualcomm.com ([10.45.158.129]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Jul 2013 10:11:57 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC17.na.qualcomm.com (10.45.158.129) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 10:11:56 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 10:11:56 -0700
Message-ID: <51E9735B.9030103@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 12:11:55 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Draft submission deadline/moratorium tool proposal
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.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: Fri, 19 Jul 2013 17:12:05 -0000

Given the talk over the last week, I'd like to make a proposal. I have 
suggested something like this before. If the chairs generally think this 
is a good idea, then maybe we take it to the IETF list. (I have not 
passed this by other ADs; they can pipe up as they see fit.)

Proposal for draft submission deadline/moratorium:

1. The draft submission tool never shuts down. Everyone is *always* 
allowed to submit drafts to the tool. However, they are not always posted.

2. For X weeks before an IETF plenary meeting and during the week of the 
meeting, all submitted drafts are queued but not posted. The draft 
deadline is announced as X weeks. (I personally don't care what X is; 
suggestions welcome.)

3. Queued WG drafts can be approved for posting by an AD or the chair(s) 
of that WG.

4. Queued individual submission drafts can be approved for posting by an AD.

5. At the completion of the IETF meeting, all queued drafts are released 
from the queue.

(Other features that might be desirable, but I'm not sure about)

6a. Drafts that are in IESG-Evaluation are not queued.
...or...
6b. Drafts that are in IESG-Evaluation are always queued, regardless of 
moratorium. An AD must release them.

7. Chairs can pre-approve draft posting during the moratorium, just as 
they do for -00 drafts.

8. Chairs can put a moratorium on a particular WG (for instance, before 
an interim meeting).

Thoughts?

pr

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


From dcrocker@bbiw.net  Fri Jul 19 10:20:05 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 9C90C21E8050 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HEHxWBXSkKsB for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:20:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C1C2721F9E0B for <wgchairs@ietf.org>; Fri, 19 Jul 2013 10:19:55 -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 r6JHJqMX017969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Jul 2013 10:19:55 -0700
Message-ID: <51E97512.7040108@bbiw.net>
Date: Fri, 19 Jul 2013 10:19: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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.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, 19 Jul 2013 10:19:55 -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, 19 Jul 2013 17:20:05 -0000

On 7/19/2013 10:11 AM, Pete Resnick wrote:
> Given the talk over the last week, I'd like to make a proposal. I have
> suggested something like this before. If the chairs generally think this
> is a good idea, then maybe we take it to the IETF list. (I have not
> passed this by other ADs; they can pipe up as they see fit.)
>
> Proposal for draft submission deadline/moratorium:
>
> 1. The draft submission tool never shuts down. Everyone is *always*
> allowed to submit drafts to the tool. However, they are not always posted.


You've just increased the workload of ADs and chairs.  Although the 
design you propose is logical, it really creates a significant hassle 
for the principals in the process.

I'll suggest something a bit different:

      All submissions are accepted and posted and announced.

      However, they are not integrated into the working group document 
page during the quiet period.  (If you want to add AD/Chair authority to 
override this selectively, fine.)

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From presnick@qti.qualcomm.com  Fri Jul 19 10:29:08 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 9F7C511E817A for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kLlYd+SuuTMI for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:28:54 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id C472311E8147 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 10:28:50 -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=1374254930; x=1405790930; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pHNfmOuSI3H1WILU3irGaibD95NAfTmg6SGtDZjru3s=; b=HL3OPDCPJBJ9UmT5LCuqGLwFMMP4GtkNSXp8VWryieh1AbivBbG8IpbP sTYBk/NloyXrygw8jUaCWUBx5K9qvm8Ed3fGWWAQB9FjtdpvKzguAcIPC NLYJ6mzb4E4u5fXY94teCu+H6fsu2OEniaPd4OCXYgPKskv9mFMxZld8R I=;
X-IronPort-AV: E=Sophos;i="4.89,703,1367996400"; d="scan'208";a="47829506"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 19 Jul 2013 10:28:40 -0700
X-IronPort-AV: E=Sophos;i="4.89,702,1367996400"; d="scan'208";a="517145775"
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Jul 2013 10:28:40 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 10:27:45 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 10:27:45 -0700
Message-ID: <51E97710.6050007@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 12:27:44 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net>
In-Reply-To: <51E97512.7040108@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
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, 19 Jul 2013 17:29:08 -0000

On 7/19/13 12:19 PM, Dave Crocker wrote:
> You've just increased the workload of ADs and chairs.

This only changes the workload if the ADs and chairs even look at the 
queue. There is no requirement that they do so.

ADs already get email to approve posting after the deadline. This might 
increase the number of requests to do so.

And how many drafts do you think any given WG chair will have to look 
at, even if they chose to look at the queue?

Color me unconvinced.

> I'll suggest something a bit different:

I suspect your proposal will get a similar amount of pushback that the 
simpler "No deadline at all" proposal got. And I'd prefer to discuss the 
merits of this proposal on its own and see if it can get some consensus 
before discussing alternatives.

pr

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


From dcrocker@bbiw.net  Fri Jul 19 10:36:21 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 3883F21E80CE for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:36:21 -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 MU2gYmUBp6cC for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 10:36:16 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C00A21E8050 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 10:36:16 -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 r6JHaC2P018338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Jul 2013 10:36:15 -0700
Message-ID: <51E978E6.5010903@bbiw.net>
Date: Fri, 19 Jul 2013 10:35:34 -0700
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: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net> <51E97710.6050007@qti.qualcomm.com>
In-Reply-To: <51E97710.6050007@qti.qualcomm.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, 19 Jul 2013 10:36:16 -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, 19 Jul 2013 17:36:21 -0000

On 7/19/2013 10:27 AM, Pete Resnick wrote:
> On 7/19/13 12:19 PM, Dave Crocker wrote:
>> You've just increased the workload of ADs and chairs.
>
> This only changes the workload if the ADs and chairs even look at the
> queue. There is no requirement that they do so.

Oh.  You don't understand.

I just posted my draft and it's not showing up.  I want it released NOW.

Negotiation ensues.  Everyone is hassled.

Yes, there's another well-behaved scenario, but we know the other kind 
will happen frequently.


>
> ADs already get email to approve posting after the deadline. This might
> increase the number of requests to do so.
>
> And how many drafts do you think any given WG chair will have to look
> at, even if they chose to look at the queue?
>
> Color me unconvinced.
>
>> I'll suggest something a bit different:
>
> I suspect your proposal will get a similar amount of pushback that the
> simpler "No deadline at all" proposal got. And I'd prefer to discuss the
> merits of this proposal on its own and see if it can get some consensus
> before discussing alternatives.


I offered comments on the merits, as justifying the alternative.  Less 
workload for ADs and Chairs.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From rlb@ipv.sx  Fri Jul 19 11:02:43 2013
Return-Path: <rlb@ipv.sx>
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 6E47111E817B for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.054
X-Spam-Level: 
X-Spam-Status: No, score=-3.054 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsWalIqgnKt1 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:02:38 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 50BDF11E80E3 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:02:37 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id f4so6387652oah.7 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:02:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=EElEClCkEoc+KmRfytxuTvvwLIdNXgX6JOJxvtHHv/w=; b=jgNWEtxYhjfiIvGLnMbJGOE9lFnV2rrVVtwQQjG0S52QBITDy7eZhXXrw6CiIQhepd //w881L5JorEEXTf244ESvoxHB5+dkSGmLHPI9MZWEyWcwidcZjVAFpPiIi7qWow/ZQu 6Umt0bBOmw2CstLdyqbuVS3KXjdpes6Q0ukUOQPPwSPZ94KaqeaJ7wNdD19ATK8mqtOh 1jddlSLN88WwMH/02l2xOnz/s0pjMc2c9OTi4ozsF7UDRhxKPjZnWkFffObk9AiYHSIo YoU+13r+8j1QgNTbYKhwLwSKqz7O6o266pGIqcS+munhqQTowImE4M6eVW4Hv7zLrw+C hubQ==
MIME-Version: 1.0
X-Received: by 10.60.79.3 with SMTP id f3mr18971193oex.50.1374256957537; Fri, 19 Jul 2013 11:02:37 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Fri, 19 Jul 2013 11:02:37 -0700 (PDT)
X-Originating-IP: [192.1.51.54]
In-Reply-To: <51E978E6.5010903@bbiw.net>
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net> <51E97710.6050007@qti.qualcomm.com> <51E978E6.5010903@bbiw.net>
Date: Fri, 19 Jul 2013 14:02:37 -0400
Message-ID: <CAL02cgR0Kuo4Emmp2nU7YN=+ArQw0euLX4vMNNdaR1Luw7y4Sg@mail.gmail.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
From: Richard Barnes <rlb@ipv.sx>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0117795bc8cfa604e1e1218f
X-Gm-Message-State: ALoCoQk6o1T3+r+NU8pvOdHZtA/a+zEhIOEsmj/vWmJOI5nbVa3TERN0Z+zIFrTfzi6fW5GU/4pb
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Fri, 19 Jul 2013 18:02:43 -0000

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

I pretty much agree with Dave here.

Yes, we need a forcing function to get people to submit drafts.  The
meeting is one such deadline.  We could even have an advisory deadline.

Locking down the tool is overkill.

--Richard


On Fri, Jul 19, 2013 at 1:35 PM, Dave Crocker <dcrocker@bbiw.net> wrote:

> On 7/19/2013 10:27 AM, Pete Resnick wrote:
>
>> On 7/19/13 12:19 PM, Dave Crocker wrote:
>>
>>> You've just increased the workload of ADs and chairs.
>>>
>>
>> This only changes the workload if the ADs and chairs even look at the
>> queue. There is no requirement that they do so.
>>
>
> Oh.  You don't understand.
>
> I just posted my draft and it's not showing up.  I want it released NOW.
>
> Negotiation ensues.  Everyone is hassled.
>
> Yes, there's another well-behaved scenario, but we know the other kind
> will happen frequently.
>
>
>
>
>> ADs already get email to approve posting after the deadline. This might
>> increase the number of requests to do so.
>>
>> And how many drafts do you think any given WG chair will have to look
>> at, even if they chose to look at the queue?
>>
>> Color me unconvinced.
>>
>>  I'll suggest something a bit different:
>>>
>>
>> I suspect your proposal will get a similar amount of pushback that the
>> simpler "No deadline at all" proposal got. And I'd prefer to discuss the
>> merits of this proposal on its own and see if it can get some consensus
>> before discussing alternatives.
>>
>
>
> I offered comments on the merits, as justifying the alternative.  Less
> workload for ADs and Chairs.
>
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

<div dir=3D"ltr">I pretty much agree with Dave here.<div><br></div><div>Yes=
, we need a forcing function to get people to submit drafts. =A0The meeting=
 is one such deadline. =A0We could even have an advisory deadline.</div><di=
v><br>
</div><div>Locking down the tool is overkill.</div><div><br></div><div>--Ri=
chard</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Fri, Jul 19, 2013 at 1:35 PM, Dave Crocker <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dcrocker@bbiw.net" target=3D"_blank">dcrocker@bbiw.net</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 7/19/2013 10:27 AM, Pet=
e Resnick wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 7/19/13 12:19 PM, Dave Crocker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
You&#39;ve just increased the workload of ADs and chairs.<br>
</blockquote>
<br>
This only changes the workload if the ADs and chairs even look at the<br>
queue. There is no requirement that they do so.<br>
</blockquote>
<br></div>
Oh. =A0You don&#39;t understand.<br>
<br>
I just posted my draft and it&#39;s not showing up. =A0I want it released N=
OW.<br>
<br>
Negotiation ensues. =A0Everyone is hassled.<br>
<br>
Yes, there&#39;s another well-behaved scenario, but we know the other kind =
will happen frequently.<div class=3D"im"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
ADs already get email to approve posting after the deadline. This might<br>
increase the number of requests to do so.<br>
<br>
And how many drafts do you think any given WG chair will have to look<br>
at, even if they chose to look at the queue?<br>
<br>
Color me unconvinced.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;ll suggest something a bit different:<br>
</blockquote>
<br>
I suspect your proposal will get a similar amount of pushback that the<br>
simpler &quot;No deadline at all&quot; proposal got. And I&#39;d prefer to =
discuss the<br>
merits of this proposal on its own and see if it can get some consensus<br>
before discussing alternatives.<br>
</blockquote>
<br>
<br></div>
I offered comments on the merits, as justifying the alternative. =A0Less wo=
rkload for ADs and Chairs.<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
d/<br>
<br>
<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</div></div></blockquote></div><br></div>

--089e0117795bc8cfa604e1e1218f--

From presnick@qti.qualcomm.com  Fri Jul 19 11:10:29 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 A689521E80BA for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7yg+g2dkSfT for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:10:25 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 6DCAB21E80B6 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:10:25 -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=1374257425; x=1405793425; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=1Pqukagrxn567nzgDdfQP3HjXf5PkbqSflivW72bw+4=; b=wGmNoWbWEa3jJmhT7W8TQHig3WuQgP30emrqcWkn2vPWrkN8kf4j/w1h NWYmCkOUG0wK8KV+c0XPhw9VK7CIMD9ihzmtzl9nEDdEPCKTOkiMH63qa JbK3lQctQWsokTbR7WAYx8uHl3uNWK/umrU6zzKQWEqaTmmGcKowGXdV7 k=;
X-IronPort-AV: E=Sophos;i="4.89,703,1367996400"; d="scan'208";a="47832940"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 19 Jul 2013 11:10:24 -0700
X-IronPort-AV: E=Sophos;i="4.89,703,1367996400"; d="scan'208";a="570846335"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Jul 2013 11:10:24 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc04.na.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 11:10:24 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 11:10:24 -0700
Message-ID: <51E9810B.8070202@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 13:10:19 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net>	<51E97710.6050007@qti.qualcomm.com> <51E978E6.5010903@bbiw.net>
In-Reply-To: <51E978E6.5010903@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
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, 19 Jul 2013 18:10:29 -0000

On 7/19/13 12:35 PM, Dave Crocker wrote:
> On 7/19/2013 10:27 AM, Pete Resnick wrote:
>> On 7/19/13 12:19 PM, Dave Crocker wrote:
>>> You've just increased the workload of ADs and chairs.
>>
>> This only changes the workload if the ADs and chairs even look at the
>> queue. There is no requirement that they do so.
>
> Oh.  You don't understand.
>
> I just posted my draft and it's not showing up.  I want it released NOW.

Ah, I think you've just defined a feature clarification:

2. For X weeks before an IETF plenary meeting and during the week of the 
meeting, the submission tool says, "Posting deadline passed. No drafts 
will be posted without chair/AD approval." All submitted drafts are 
queued but not posted.

> Negotiation ensues.  Everyone is hassled.

I'd like to hear from other chairs, but I am surprised that you would 
suggest that there would be negotiation. I would expect you would either 
say, "No" or "Yes". End of negotiation. No hassle. If there is 
negotiation, fire the document editor. Seriously.

> Yes, there's another well-behaved scenario, but we know the other kind 
> will happen frequently.

Still unconvinced.

> I offered comments on the merits...

You did. As I said, I'd like to hear from other chairs before we move on 
to alternatives. Jumping to alternatives forks the discussion.

pr

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


From paul.hoffman@vpnc.org  Fri Jul 19 11:10:54 2013
Return-Path: <paul.hoffman@vpnc.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 0934D11E8189 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXZBEtbOoqX6 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:10:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD9C11E817C for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:10:53 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r6JIAq2H051141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Jul 2013 11:10:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Draft submission deadline/moratorium tool proposal
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 11:10:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org>
References: <51E9735B.9030103@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
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, 19 Jul 2013 18:10:54 -0000

Most of this seems very good. However:

> 4. Queued individual submission drafts can be approved for posting by =
an AD.

This conflates "Internet Drafts" with "IETF work" in a way I think is =
inappropriate. My previous attempts at making this distinction have =
garnered little interest, but I'll try again.

Counter-proposal: only draft-ietf-* are queued; all individual =
submission and IAB stream and IRTF stream documents are passed through.

Someone who uses individual submission to try to get a draft in front of =
a WG should be slapped down by the WG chair (or allowed through, if the =
chair agrees).

This focuses the problem exactly where it should be.

FWIW, Dave's suggestion is silly because so few people look at the WG =
page in the Datatracker that it would be indistinguishable from "no =
restriction".

--Paul Hoffman=

From presnick@qti.qualcomm.com  Fri Jul 19 11:30:09 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 EB7E221F9E6E for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 vZkrHIhUVoj9 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:30:05 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id BCDA421E80CE for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:30:05 -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=1374258605; x=1405794605; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=d5ixDHEcM4x1nKT9sSXmkOfZKnsSZIrRZkwHkR1Xa6U=; b=uAR7NL1sZRBEnfcml5csh+c7g/gHgy8jq8TStx2FI4jlobr0rTxF7ucN lJ0aFxcx4BhltemS7N/HCk7GP2pZ8F4gRyHEJ+U7WIDq5XM9myUlRGEk7 efnYY/c/i+8j9fvwA7D9tlhfZL/bPrsrtBMg253WOxJbf9jjGwywPQ9rG k=;
X-IronPort-AV: E=Sophos;i="4.89,703,1367996400"; d="scan'208";a="47727345"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 19 Jul 2013 11:30:05 -0700
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Jul 2013 11:30:04 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 11:30:04 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 19 Jul 2013 11:30:03 -0700
Message-ID: <51E985AA.8090207@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 13:30:02 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org>
In-Reply-To: <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
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, 19 Jul 2013 18:30:10 -0000

On 7/19/13 1:10 PM, Paul Hoffman wrote:
> Counter-proposal

These sound like fine "friendly amendments".

> only draft-ietf-* are queued; all individual submission and IAB stream and IRTF stream documents are passed through.
>    

Yeah, I thought about adding that. All draft-iab-* and draft-irtf-* are 
not queued (unless either of them wants a moratorium too). Added as "9".

> Someone who uses individual submission to try to get a draft in front of a WG should be slapped down by the WG chair (or allowed through, if the chair agrees).
>    

Many WGs keep things as individual submissions during initial 
discussions, so I wanted to account for that. But I guess I don't 
understand if that modifies my proposal in any way. Do you mean to add 
to 4 "or chair"?

pr

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


From rlb@ipv.sx  Fri Jul 19 11:32:19 2013
Return-Path: <rlb@ipv.sx>
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 DE3CC11E8197 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.043
X-Spam-Level: 
X-Spam-Status: No, score=-3.043 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPPuDODm7POu for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:32:15 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 646DC11E8194 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:32:14 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id f4so6483036oah.21 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:32:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=UFYNXh36uik+rRu1BJzv89X8SFVuEn27kkS5k0vDxjE=; b=Nq5tlpIpHPPj5FItIZKxm0O/ieS3VJULnC2qHiuhymypAJjQkTnYOHPxXCZVa7JMAt +B8wQod+IAPZwu+JvMa0QZrbMjxxdg7l7wadddJ3aT+cmzpK0/RtYql8b+Pe+aZY4jEn Zh4b8slT2CCjK91x+NI5iuOXynaLkzraf9SaUMj/baYe9QGsCf4q2wByAUE3VP8ULTmy iELr5cbq2OAnOJRpCQv/Dhcj4MpPAaLhr8hAcE0Fsr4XzeX7wzhsvr/jayTrx9FjI22k NLe8oWQ1agtevSAD5e5dEFAQF7MvWkWtnf1vBWyEGePuT1IZiqOE4Bqz9grUXbkTyc/M kQow==
MIME-Version: 1.0
X-Received: by 10.60.97.74 with SMTP id dy10mr18814334oeb.27.1374258734017; Fri, 19 Jul 2013 11:32:14 -0700 (PDT)
Received: by 10.60.26.135 with HTTP; Fri, 19 Jul 2013 11:32:13 -0700 (PDT)
X-Originating-IP: [192.1.51.54]
In-Reply-To: <51E985AA.8090207@qti.qualcomm.com>
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org> <51E985AA.8090207@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 14:32:13 -0400
Message-ID: <CAL02cgT8E-QL6Me=P9PD_JptwYimNUDgdd3mZ9oOk2TtwAcKBQ@mail.gmail.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
From: Richard Barnes <rlb@ipv.sx>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e0115e9faabc5d104e1e18bde
X-Gm-Message-State: ALoCoQnI+IqD1zllRgN75jaZL3iaIRsGFJCC2FrRZP6At70CHMCNpg+L0vpwssFuugd3OQdlfAHh
Cc: WG Chairs <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 19 Jul 2013 18:32:20 -0000

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

On Fri, Jul 19, 2013 at 2:30 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 7/19/13 1:10 PM, Paul Hoffman wrote:
>
>> Counter-proposal
>>
>
> These sound like fine "friendly amendments".
>
>
>  only draft-ietf-* are queued; all individual submission and IAB stream
>> and IRTF stream documents are passed through.
>>
>>
>
> Yeah, I thought about adding that. All draft-iab-* and draft-irtf-* are
> not queued (unless either of them wants a moratorium too). Added as "9".


This constraint is unnecessarily broad as well.  For example: I just went
to publish a 4-line patch to a WG doc to fix some late WGLC comments, and
got hit by the embargo.  That document isn't up for discussion at the
meeting; there's no reason to embargo it.

Publication should not be a block.  Inclusion in the meeting should be, at
the discretion of the chairs.

--Richard




>
>
>  Someone who uses individual submission to try to get a draft in front of
>> a WG should be slapped down by the WG chair (or allowed through, if the
>> chair agrees).
>>
>>
>
> Many WGs keep things as individual submissions during initial discussions,
> so I wanted to account for that. But I guess I don't understand if that
> modifies my proposal in any way. Do you mean to add to 4 "or chair"?
>
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.**com/~presnick/<http://www.qualcomm.com/~presnick/>
> >
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jul 19, 2013 at 2:30 PM, Pete Resnick <span dir=3D"ltr">&lt=
;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">presnick@qt=
i.qualcomm.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 7/19/13 1:10 PM, Paul Hoffman wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Counter-proposal<br>
</blockquote>
<br>
These sound like fine &quot;friendly amendments&quot;.<div class=3D"im"><br=
>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
only draft-ietf-* are queued; all individual submission and IAB stream and =
IRTF stream documents are passed through.<br>
=A0 =A0<br>
</blockquote>
<br></div>
Yeah, I thought about adding that. All draft-iab-* and draft-irtf-* are not=
 queued (unless either of them wants a moratorium too). Added as &quot;9&qu=
ot;.</blockquote><div><br></div><div>This constraint is unnecessarily broad=
 as well. =A0For example: I just went to publish a 4-line patch to a WG doc=
 to fix some late WGLC comments, and got hit by the embargo. =A0That docume=
nt isn&#39;t up for discussion at the meeting; there&#39;s no reason to emb=
argo it. =A0</div>
<div><br></div><div>Publication should not be a block. =A0Inclusion in the =
meeting should be, at the discretion of the chairs.</div><div><br></div><di=
v>--Richard</div><div><br></div><div><br></div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Someone who uses individual submission to try to get a draft in front of a =
WG should be slapped down by the WG chair (or allowed through, if the chair=
 agrees).<br>
=A0 =A0<br>
</blockquote>
<br></div>
Many WGs keep things as individual submissions during initial discussions, =
so I wanted to account for that. But I guess I don&#39;t understand if that=
 modifies my proposal in any way. Do you mean to add to 4 &quot;or chair&qu=
ot;?<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--089e0115e9faabc5d104e1e18bde--

From paul.hoffman@vpnc.org  Fri Jul 19 11:53:30 2013
Return-Path: <paul.hoffman@vpnc.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 1128621E80F8 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mUztj0ZWR1Wt for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 11:53:25 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 08C1411E8197 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:52:44 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r6JIqfl3052919 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Fri, 19 Jul 2013 11:52:42 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Draft submission deadline/moratorium tool proposal
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51E985AA.8090207@qti.qualcomm.com>
Date: Fri, 19 Jul 2013 11:52:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B4F887D-CEEE-4E45-A49C-5DDC6FC27D1C@vpnc.org>
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org> <51E985AA.8090207@qti.qualcomm.com>
To: WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1508)
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, 19 Jul 2013 18:53:31 -0000

On Jul 19, 2013, at 11:30 AM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

>> only draft-ietf-* are queued; all individual submission and IAB =
stream and IRTF stream documents are passed through.
>>  =20
>=20
> Yeah, I thought about adding that. All draft-iab-* and draft-irtf-* =
are not queued (unless either of them wants a moratorium too). Added as =
"9".

I think it would be much cleaner to change 2 to say "all draft-ietf-* =
drafts are queued" and leave the rest of the rules alone. That is, =
narrow the scope of the queuing to just those things that always affect =
WGs.

> Many WGs keep things as individual submissions during initial =
discussions, so I wanted to account for that.

And in doing so you have made the protocol much more complicated. Leave =
dealing with this up to the chairs of the WGs affected, don't force it =
on all of us.


On Jul 19, 2013, at 11:32 AM, Richard Barnes <rlb@ipv.sx> wrote:

> This constraint is unnecessarily broad as well.  For example: I just =
went to publish a 4-line patch to a WG doc to fix some late WGLC =
comments, and got hit by the embargo.  That document isn't up for =
discussion at the meeting; there's no reason to embargo it. =20

You are assuming that the chairs do not want to bring that patch to the =
WG.

It seems nearly harmless to tell chairs "during what used to be the =
silent period, you might get messages for drafts in your WG, and you can =
decide how to deal with them".

--Paul Hoffman=

From ietf-secretariat@ietf.org  Fri Jul 19 11:53:44 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 47C4221F99F7; Fri, 19 Jul 2013 11:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105
X-Spam-Level: 
X-Spam-Status: No, score=-105 tagged_above=-999 required=5 tests=[AWL=1.600, 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 7OWFjolv2KaL; Fri, 19 Jul 2013 11:53:42 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DA011E8145; Fri, 19 Jul 2013 11:53:05 -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 87 - Meeting Information
X-Test-IDTracker: no
X-IETF-IDTracker: 4.53
Message-ID: <20130719185305.11266.33462.idtracker@ietfa.amsl.com>
Date: Fri, 19 Jul 2013 11:53:05 -0700
Cc: wgchairs@ietf.org, 87all@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, 19 Jul 2013 18:53:44 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

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

1.  Registration - Early Bird Registration Cutoff Today, 19 July
2.  InterContinental Emergency Evacuation Procedures
3.  Social Event - currently sold out
4.  Sponsor Web page
5.  Visas & Letters of Invitation
6.  Accommodations
7.  Companion Program
8.  Childcare Information

1. Registration
A. Early-Bird Registration - USD 650.00 Pay by Friday, 19 July 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. All fees include 19% VAT
F. Registration Cancellation   =

         Cut-off for registration cancellation is Monday,
         22 July 2013 at UTC 24:00.
         Cancellations are subject to a 10% (ten percent)
         cancellation fee if requested by that date and time.
G. Online Registration and Payment ends Friday, 26 July 2013, 1700 local Be=
rlin time.
H. On-site Registration starting Sunday, 28 July 2013 at 1100 local Berlin =
time.

2.  InterContinental Emergency Procedures
Emergency evacuation procedures at the InterContinental Berlin have been po=
sted at:
http://www.ietf.org/meeting/87/emergency_InterCon.html
Information on handling a Medical Emergency is also included.

3.  Social Event - currently sold out

4. Sponsor Web Page
DENIC, the Platinum sponsor for IETF 87 has created a web page with informa=
tion about Berlin, the URL is: http://www.ietf87.de/

5. Visas & Letters of Invitation:
For information on Visiting Germany, please visit:
http://www.auswaertiges-amt.de/EN/EinreiseUndAufenthalt/Visabestimmungen_no=
de.html

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 emai=
l.

Please note that the IETF Letter of Invitation may not be sufficient for ob=
taining a visa to enter Germany.

6.  Accommodations
Currently the venue hotel (InterContinental) and overflow hotel (Pullman) a=
re both fully booked. The following hotels are near the InterContinental th=
ough we are not holding blocks at any of them.

Pestana
http://www.pestana.com/en/pestana-berlin-tiergarten-hotel/pages/home.aspx
Distance from InterContinental: approximately 1-2 minute walk

Hotel Berlin
http://www.hotel-berlin.de/en/hotel-berlin.html
Distance from InterContinental: approximately 5-7 minute walk

Das Stue Hotel
http://www.das-stue.com/en/
Distance from InterContinental: approximately 7-10 minute walk
guest room rates at both the InterContinetnal and Pullman include breakfast.

7.  Companion Program
If you are traveling with a friend or family member over 18 years of age yo=
u 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, 28 J=
uly
- Ability to attend the official Welcome Reception from 1700-1900 on Sunday=
, 28 July
- A distinctive meeting badge that grants access to the venue (not to be us=
ed to attend working sessions)
- Participation in a separate companion email list if you choose to help co=
mmunicate 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 87 companions mailing list only see:
https://www.ietf.org/mailman/listinfo/87companions

8.  Childcare Information
If you are staying at the InterContinental or the Pullman and are intereste=
d in childcare services, please contact the concierge at the respective hot=
el to get more information or to make arrangements. You can email the Inter=
Continental at <berha.concierge@ihg.com> and the Pullman at <pullman@berlin=
concierge.de>

Only 9 days until the Berlin IETF!

From Ted.Lemon@nominum.com  Fri Jul 19 12:23:16 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 792DA21E80BA for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 12:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.59
X-Spam-Level: 
X-Spam-Status: No, score=-106.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErdpkmKt69i0 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 12:23:06 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1704411E8158 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 12:23:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUemSGU/rItwq1nnxe3x6H3qp9xCgal8Z@postini.com; Fri, 19 Jul 2013 12:23:06 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9244B1B825E for <wgchairs@ietf.org>; Fri, 19 Jul 2013 12:23:05 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8C4DE190060; Fri, 19 Jul 2013 12:23:05 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 19 Jul 2013 12:23:05 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMZ6VaV/X1HSkOwPETxqTJQvZlstEEAgAACYACAAAIwAIAAHgkA
Date: Fri, 19 Jul 2013 19:23:04 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521B613@mbx-01.win.nominum.com>
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net> <51E97710.6050007@qti.qualcomm.com> <51E978E6.5010903@bbiw.net>
In-Reply-To: <51E978E6.5010903@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E34BAD3A2D585542BEC4221CD956CE74@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Fri, 19 Jul 2013 19:23:16 -0000

On Jul 19, 2013, at 12:35 PM, Dave Crocker <dcrocker@bbiw.net> wrote:
> I just posted my draft and it's not showing up.  I want it released NOW.

Didn't I just hear you arguing in favor of chairs managing their working gr=
oups?


From spencerdawkins.ietf@gmail.com  Fri Jul 19 12:25:13 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 3447A11E8179 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 12:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0qBgyw79mWi for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 12:25:12 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id B46D211E8158 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 12:25:12 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n10so6662029oag.0 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 12:25:12 -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=qVlqte1PhYUeDJHdy6bqyBTie6Nl5q3My8D/swHCDXA=; b=x5/n7H9o6mpSCSni40iifzfT1iOVGKmJ51lwehN1KF35GAwMxfz1eZhTEdvqn3GZ2o YwA6UhwNQQ9wj3AKzq4kW1KdTbgTujCQenaZ53NZi/9n39k93FrbagrfQfhT5+/0bMIP avavpuwoBl5MgpG6qFg2ZZRbJ752o7foDZmhRipOzPpFSXSMQLJb4ScapfkJER8YsryR lwyDRflyLD3lEGoWR406y2go+I0tvt6Ir44QrCv5Si1/QF8NfPARA1WpDbDX50c7vzg7 1RV2HNlreD9K7Vgq5Lbx6bnrqjFawt0t/Cs2OL3iMrWYu/oDhHWlaGxOV1/zjklaL/99 Joxg==
X-Received: by 10.60.164.33 with SMTP id yn1mr19437797oeb.5.1374261912320; Fri, 19 Jul 2013 12:25:12 -0700 (PDT)
Received: from [192.168.0.23] (173-97-219-59.pools.spcsdns.net. [173.97.219.59]) by mx.google.com with ESMTPSA id rs4sm22718557obc.10.2013.07.19.12.25.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Jul 2013 12:25:10 -0700 (PDT)
Message-ID: <51E99285.5070403@gmail.com>
Date: Fri, 19 Jul 2013 14:24:53 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org>
In-Reply-To: <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org>
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: Fri, 19 Jul 2013 19:25:13 -0000

On 7/19/2013 1:10 PM, Paul Hoffman wrote:
> Counter-proposal: only draft-ietf-* are queued; all individual submission and IAB stream and IRTF stream documents are passed through.

I'll let my chairs comment on what works for their working groups, but 
as a semi-retired IAB-stream document editor, I would have loved to be 
able to submit and post draft-iab docs during the quiet period ...

I'm thinking that research group chairs are all on the Internet Research 
Steering Group <irsg@irtf.org> mailing list, but most are not on this 
list (some research group chairs are also working group chairs, but not 
nearly all). It would be good to run a question about draft-irtf past them.

Spencer


From david.black@emc.com  Fri Jul 19 13:05:40 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 1C55021F99F7 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubk+eAC1oqLU for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:05:36 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 046D111E80DF for <wgchairs@ietf.org>; Fri, 19 Jul 2013 13:05:34 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JK5Vck016009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 16:05:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 19 Jul 2013 16:05:24 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r6JK5NGI018769; Fri, 19 Jul 2013 16:05:24 -0400
Received: from mx15a.corp.emc.com ([169.254.1.184]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Fri, 19 Jul 2013 16:05:23 -0400
From: "Black, David" <david.black@emc.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Fri, 19 Jul 2013 16:05:18 -0400
Subject: RE: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: Ac6ErguA+nOe48J0QKaSmp7KpdIwrgADIFaw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712984ACAFE@MX15A.corp.emc.com>
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org> <51E985AA.8090207@qti.qualcomm.com>
In-Reply-To: <51E985AA.8090207@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: 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, 19 Jul 2013 20:05:40 -0000

> > only draft-ietf-* are queued; all individual submission and IAB stream =
and
> IRTF stream documents are passed through.
> >

I'd make one change, as I'm involved in WGs where a lot of individual draft=
s
targeted at the WG show up, and the advance deadline for posting those is
useful.

So, in addition to draft-ietf-* being queued, draft-*-<wgname>-*
also needs to be queued.  The latter sort of drafts should be releasable by
the chairs of <wgname>.

Then someone who end-runs that by not putting <wgname> in their individual
submission draft and trying to get the result on a WG agenda does truly
deserve to be slapped around.

Thanks,
--David

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf
> Of Pete Resnick
> Sent: Friday, July 19, 2013 2:30 PM
> To: Paul Hoffman
> Cc: WG Chairs
> Subject: Re: Draft submission deadline/moratorium tool proposal
>=20
> On 7/19/13 1:10 PM, Paul Hoffman wrote:
> > Counter-proposal
>=20
> These sound like fine "friendly amendments".
>=20
> > only draft-ietf-* are queued; all individual submission and IAB stream =
and
> IRTF stream documents are passed through.
> >
>=20
> Yeah, I thought about adding that. All draft-iab-* and draft-irtf-* are
> not queued (unless either of them wants a moratorium too). Added as "9".
>=20
> > Someone who uses individual submission to try to get a draft in front o=
f a
> WG should be slapped down by the WG chair (or allowed through, if the cha=
ir
> agrees).
> >
>=20
> Many WGs keep things as individual submissions during initial
> discussions, so I wanted to account for that. But I guess I don't
> understand if that modifies my proposal in any way. Do you mean to add
> to 4 "or chair"?
>=20
> pr
>=20
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From salvatore.loreto@ericsson.com  Fri Jul 19 13:12:06 2013
Return-Path: <salvatore.loreto@ericsson.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 2D79611E819B for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:12:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.221
X-Spam-Level: 
X-Spam-Status: No, score=-104.221 tagged_above=-999 required=5 tests=[AWL=-1.622, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UweGSme7nK5p for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:12:00 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2452811E8197 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 13:11:59 -0700 (PDT)
X-AuditID: c1b4fb38-b7f456d000002e83-38-51e99d8ea0c7
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 83.1A.11907.E8D99E15; Fri, 19 Jul 2013 22:11:58 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.19) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.2.328.9; Fri, 19 Jul 2013 22:11:58 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 81A89110295 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 23:11:58 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 9A479557B7	for <wgchairs@ietf.org>; Fri, 19 Jul 2013 23:11:54 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 2BC205571D	for <wgchairs@ietf.org>; Fri, 19 Jul 2013 23:11:54 +0300 (EEST)
Message-ID: <51E99D8D.6000503@ericsson.com>
Date: Fri, 19 Jul 2013 22:11:57 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: <wgchairs@ietf.org>
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrILMWRmVeSWpSXmKPExsUyM+JvrW7/3JeBBhv5LP7vn8LowOixZMlP pgDGKC6blNSczLLUIn27BK6Mo1sesRW84Kv4cegXawPjYe4uRk4OCQETib1/jrJD2GISF+6t ZwOxhQSOMkr8/53RxcgFZK9nlDjy+RYThHOVUaJj0kIo5xijxNTOw1DOeUaJDdP7wfp5BbQl +n/fBpvLIqAqceDmDBYQm03ATOL5wy3MILaoQLLE+yt3mCHqBSVOznwCViMiIC6xYvV6sLiw gL3EgzN9jBA36Uv87vwFFucUMJD43L0EbD6zgK3EhTnXWSBseYntb+cwQ/yjJnH13CZmiF4t id6znUwTGEVmIVk3C0n7LCTtCxiZVzFyFKcWJ+WmGxlsYgQG88Etvy12MF7+a3OIUZqDRUmc d4vemUAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjBPL1OOXM5WscLnx8VJ3ScW/LR1nddI/ yUhsmWrerl0axpIe+nL3rGny82VqLVaqnPyj9eTYNyt+mwMHxQ2u7pu5WOiw3Q4lf5Gmf1VC C+877A16zy+whNPG7UFHUWQAV9Z23ZKdRyye8m3kYZpy8s7auPjCT4rxcgGJvhzilY463o1M nGxhSizFGYmGWsxFxYkA6KtDuDQCAAA=
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, 19 Jul 2013 20:12:06 -0000

it seems a reasonable proposal,
that could speed up the progress and help the discussion during the 
meeting of some important/critical draft

I would suggest that for the point #4, also the chairs should be in 
charge to approve individual submission!

/Salvatore

On 7/19/13 7:11 PM, Pete Resnick wrote:
> Given the talk over the last week, I'd like to make a proposal. I have 
> suggested something like this before. If the chairs generally think 
> this is a good idea, then maybe we take it to the IETF list. (I have 
> not passed this by other ADs; they can pipe up as they see fit.)
>
> Proposal for draft submission deadline/moratorium:
>
> 1. The draft submission tool never shuts down. Everyone is *always* 
> allowed to submit drafts to the tool. However, they are not always 
> posted.
>
> 2. For X weeks before an IETF plenary meeting and during the week of 
> the meeting, all submitted drafts are queued but not posted. The draft 
> deadline is announced as X weeks. (I personally don't care what X is; 
> suggestions welcome.)
>
> 3. Queued WG drafts can be approved for posting by an AD or the 
> chair(s) of that WG.
>
> 4. Queued individual submission drafts can be approved for posting by 
> an AD.
>
> 5. At the completion of the IETF meeting, all queued drafts are 
> released from the queue.
>
> (Other features that might be desirable, but I'm not sure about)
>
> 6a. Drafts that are in IESG-Evaluation are not queued.
> ...or...
> 6b. Drafts that are in IESG-Evaluation are always queued, regardless 
> of moratorium. An AD must release them.
>
> 7. Chairs can pre-approve draft posting during the moratorium, just as 
> they do for -00 drafts.
>
> 8. Chairs can put a moratorium on a particular WG (for instance, 
> before an interim meeting).
>
> Thoughts?
>
> pr
>


-- 
Salvatore Loreto, PhD
www.sloreto.com


From mcr@sandelman.ca  Fri Jul 19 13:25:22 2013
Return-Path: <mcr@sandelman.ca>
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 20B2B11E81AB for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4KnZKmAtiZLE for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:25:17 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id BB2A411E8141 for <wgchairs@ietf.org>; Fri, 19 Jul 2013 13:25:10 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8274C20188; Fri, 19 Jul 2013 17:30:27 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 8AB6CA902A; Fri, 19 Jul 2013 16:23:44 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 72BCBB9083; Fri, 19 Jul 2013 16:23:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
References: <51E9735B.9030103@qti.qualcomm.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 19 Jul 2013 16:23:44 -0400
Message-ID: <13773.1374265424@sandelman.ca>
Sender: mcr@sandelman.ca
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, 19 Jul 2013 20:25:22 -0000

--=-=-=


I like your proposal, with the addition of the draft-ietf-*
and draft-FOO-WG-* reduction, however....

A concern I have is about implementation constraints.

I'd like the chairs, and I think anyone logged in, in particular, any of the
authors, to be able to use the ID diff tool.  I'm pretty sure that it can
only diff drafts which are "posted".

I would propose a modification to the policy based upon where the cork can
easily be placed: drafts are posted into the  datatracker, and can be found
through the datatracker.  The rsync/FTP/HTTP/mirror server is, however, corked.
(Yes, announcements would be suppressed, so you have to know to look at it)

This also likely gets around most complaints about WGLC edits and Auth48
edits to document in progress.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


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



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

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

iQCVAwUBUemgTYqHRg3pndX9AQKBIwP+MloRL8oHq37K2wR54/4SYEjW3jUeu2Gw
QWh1H+YNAKWW/DhzCDlg35Mrkt7J9H9TE1lLOoVyB65jQ5eC0lKcJLexO3PzNYjE
s72hJM0swSqKW/pNq0omMb6Qz6OYyfTlnZUEgClPe/aVKM+PbkrECxKkzV8gfusp
Cnm9KOhZYes=
=hqtK
-----END PGP SIGNATURE-----
--=-=-=--

From ynir@checkpoint.com  Fri Jul 19 13:32:14 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 CF4F211E8184 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.568
X-Spam-Level: 
X-Spam-Status: No, score=-10.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 Wh4wF5CS1iQG for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:32:10 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BF1DA11E810D for <wgchairs@ietf.org>; Fri, 19 Jul 2013 13:32:09 -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 r6JKW0a6030741; Fri, 19 Jul 2013 23:32:01 +0300
X-CheckPoint: {51E9A240-6-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Fri, 19 Jul 2013 23:32:00 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMdj/ss1Eb2nUenSpiQnES6eplsGwmAgAAFXACAABqeAIAAB3WA
Date: Fri, 19 Jul 2013 20:31:59 +0000
Message-ID: <51FD0701-4B57-498C-9011-B95703B16A87@checkpoint.com>
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org> <51E985AA.8090207@qti.qualcomm.com> <8D3D17ACE214DC429325B2B98F3AE712984ACAFE@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984ACAFE@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.244]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11573fceac89fbf1aa23c265184c200aa49f883c64
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ACD40DB1F392E146AC7089BDD4EC9579@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 19 Jul 2013 20:32:14 -0000

On Jul 19, 2013, at 11:05 PM, "Black, David" <david.black@emc.com>
 wrote:

>>> only draft-ietf-* are queued; all individual submission and IAB stream =
and
>> IRTF stream documents are passed through.
>>>=20
>=20
> I'd make one change, as I'm involved in WGs where a lot of individual dra=
fts
> targeted at the WG show up, and the advance deadline for posting those is
> useful.
>=20
> So, in addition to draft-ietf-* being queued, draft-*-<wgname>-*
> also needs to be queued.  The latter sort of drafts should be releasable =
by
> the chairs of <wgname>.
>=20
> Then someone who end-runs that by not putting <wgname> in their individua=
l
> submission draft and trying to get the result on a WG agenda does truly
> deserve to be slapped around.

The convention of calling drafts that are intended for a working group draf=
t-someone-foowg-foo-mib-00 is quite common by now, but it's not documented =
in the guidelines (http://www.ietf.org/ietf/1id-guidelines.txt). Not everyo=
ne knows about it.

The only reference to it is in the Tao:

    If a draft is an individual submission but relates to a particular Work=
ing Group, authors sometimes follow their name with the name of the Working=
 Group, such as "draft-smith-smime-keying-00.txt".

Note the word sometimes. I don't think newbies take away from this that the=
y have to name their documents thus to get the chairs to consider them. I k=
now I didn't follow this convention for the first drafts that I posted.

Yoav


From peter@denic.de  Fri Jul 19 13:47:04 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 AE7E121E80B4 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4cEVk0GkoYE for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 13:47:04 -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 0E90B21E809B for <wgchairs@ietf.org>; Fri, 19 Jul 2013 13:47:03 -0700 (PDT)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1V0HZu-0003ns-I6; Fri, 19 Jul 2013 22:47:02 +0200
Received: from localhost by x27.adm.denic.de with local  id 1V0HZu-0003Cl-Ei; Fri, 19 Jul 2013 22:47:02 +0200
Date: Fri, 19 Jul 2013 22:47:02 +0200
From: Peter Koch <pk@ISOC.DE>
To: WG Chairs <wgchairs@ietf.org>
Subject: Re: Draft submission deadline/moratorium tool proposal
Message-ID: <20130719204702.GB23086@x28.adm.denic.de>
Mail-Followup-To: WG Chairs <wgchairs@ietf.org>
References: <51E9735B.9030103@qti.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
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, 19 Jul 2013 20:47:04 -0000

On Fri, Jul 19, 2013 at 12:11:55PM -0500, Pete Resnick wrote:

> 1. The draft submission tool never shuts down. Everyone is *always* 
> allowed to submit drafts to the tool. However, they are not always posted.

what problem are we trying to solve and why does it help to accept and
withhold the draft instead of either rejecting it or posting it right away?
What prevents people more or less than today from sending the draft
to the wg list instead?  How many drafts can be staggered in the queue?

> 3. Queued WG drafts can be approved for posting by an AD or the chair(s) 
> of that WG.

Sure chairs can manage and 'just say no', but on the other hand we're all
encouraged to be pragmatic, flexible, and inclusive. Isn't it great that
we usually have two co-chairs so we can play the 'good cop - bad cop' game?

We don't need more process, we need more quality review.  Give people
credit for those and in return they can post drafts whenever they want.

-Peter

From keith.drage@alcatel-lucent.com  Fri Jul 19 17:25:34 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 6BD4921E8095 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 17:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.581
X-Spam-Level: 
X-Spam-Status: No, score=-110.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 CvrMgW9R953z for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 17:25:28 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6BAAD11E80DC for <wgchairs@ietf.org>; Fri, 19 Jul 2013 17:25:27 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r6K0PP5w002378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Jul 2013 19:25:26 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6K0PNeb028757 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 20 Jul 2013 02:25:24 +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; Sat, 20 Jul 2013 02:25:23 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, WG Chairs <wgchairs@ietf.org>
Subject: RE: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMc0B5m+r5AeUit/uiKeb85u5lstQuA
Date: Sat, 20 Jul 2013 00:25:22 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <51E9735B.9030103@qti.qualcomm.com>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.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: Sat, 20 Jul 2013 00:25:34 -0000

Much of this works for me.

However it puts a lot of responsibility on the chairs protecting the intere=
sts of the WG members.

For example we seem to have some chairs who seem very interested in getting=
 the latest version before the meeting, such that documents get updated whe=
n the draft submission reopens on Monday, and then on Tuesday or Wednesday =
these chairs expect us to work with the new version in the meeting.

How would I as a member of the WG stop that happening, without having to wa=
ste 10 minutes of WG time at the start of the WG meeting having discovered =
that the agenda was updated while my back was turned.

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Pete Resnick
> Sent: 19 July 2013 18:12
> To: WG Chairs
> Subject: Draft submission deadline/moratorium tool proposal
>=20
> Given the talk over the last week, I'd like to make a proposal. I have
> suggested something like this before. If the chairs generally think this
> is a good idea, then maybe we take it to the IETF list. (I have not
> passed this by other ADs; they can pipe up as they see fit.)
>=20
> Proposal for draft submission deadline/moratorium:
>=20
> 1. The draft submission tool never shuts down. Everyone is *always*
> allowed to submit drafts to the tool. However, they are not always posted=
.
>=20
> 2. For X weeks before an IETF plenary meeting and during the week of the
> meeting, all submitted drafts are queued but not posted. The draft
> deadline is announced as X weeks. (I personally don't care what X is;
> suggestions welcome.)
>=20
> 3. Queued WG drafts can be approved for posting by an AD or the chair(s)
> of that WG.
>=20
> 4. Queued individual submission drafts can be approved for posting by an
> AD.
>=20
> 5. At the completion of the IETF meeting, all queued drafts are released
> from the queue.
>=20
> (Other features that might be desirable, but I'm not sure about)
>=20
> 6a. Drafts that are in IESG-Evaluation are not queued.
> ...or...
> 6b. Drafts that are in IESG-Evaluation are always queued, regardless of
> moratorium. An AD must release them.
>=20
> 7. Chairs can pre-approve draft posting during the moratorium, just as
> they do for -00 drafts.
>=20
> 8. Chairs can put a moratorium on a particular WG (for instance, before
> an interim meeting).
>=20
> Thoughts?
>=20
> pr
>=20
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478


From Ted.Lemon@nominum.com  Fri Jul 19 17:34:20 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 A825B11E81CF for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 17:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.59
X-Spam-Level: 
X-Spam-Status: No, score=-106.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vC69DZozPNrr for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 17:34:14 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id EBDCC11E81CC for <wgchairs@ietf.org>; Fri, 19 Jul 2013 17:34:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUenbBcn+0iAX6eUUqDm9rzsEO4EHREqy@postini.com; Fri, 19 Jul 2013 17:34: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 51DB01B825C for <wgchairs@ietf.org>; Fri, 19 Jul 2013 17:34:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 066C9190060; Fri, 19 Jul 2013 17:34:12 -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, 19 Jul 2013 17:34:11 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMZ6VaV/X1HSkOwPETxqTJQvZltK1AAgAACd4A=
Date: Sat, 20 Jul 2013 00:34:11 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521BFD2@mbx-01.win.nominum.com>
References: <51E9735B.9030103@qti.qualcomm.com> <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06DD37@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="us-ascii"
Content-ID: <5A972821A87B0A449CE24964707C4386@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Sat, 20 Jul 2013 00:34:20 -0000

On Jul 19, 2013, at 7:25 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lu=
cent.com> wrote:
> How would I as a member of the WG stop that happening, without having to =
waste 10 minutes of WG time at the start of the WG meeting having discovere=
d that the agenda was updated while my back was turned.

I am highly sympathetic to this concern.   However, I do wonder: would you =
rather the update _didn't_ happen?   Would you rather discuss the previous =
version of the document?   I think this is something that chairs and author=
s should avoid, and I would certainly not be happy if one of the working gr=
oups for which I am responsible AD did this.   However, in practice if the =
changes are small, rfcdiff is actually a very quick way to familiarize your=
self with changes, if you are already familiar with the draft.

So much as I want to agree with you that this sort of behavior is inappropr=
iate, I am hard pressed to do so.   A better way to characterize it is "poo=
rly timed."   If the working group chairs want the draft to be discussed at=
 the meeting, they should make damned sure that the working group is made a=
ware of the update, and the working group is well within its rights to say =
"look, we haven't had time to review this, let's drop it from the agenda un=
til the next meeting."

And the way you effect that is to get up at the mic during agenda bashing a=
nd say so.


From fred@cisco.com  Fri Jul 19 18:54:54 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 B420011E81A5 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 18:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.253
X-Spam-Level: 
X-Spam-Status: No, score=-110.253 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqLGB5XVS61N for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 18:54:49 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A47CC11E818B for <wgchairs@ietf.org>; Fri, 19 Jul 2013 18:54:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5349; q=dns/txt; s=iport; t=1374285289; x=1375494889; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8YNojy8vMmL4SPKxd88t0LpoUGA66DCtH3P3DhUqYW4=; b=SVXaRaBH+qjyPN94VAouDpcvPUZp5wIJfvweKJrUtQa2N5GYsaDsPfVS UMByWBWarMdvd0Hqtl+cHbRP9eXz7owHB4nEiaK2233h4qxR5cBEnj42U 6EXvlPFVtPqsoXZruU6oAWMWmbDYhtBD2GbEmVvEAjcLO48tW/07QN1sV o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAN3s6VGtJV2b/2dsb2JhbABXAxaCcDVQwE+BERZ0giQBAQEDAW4LBQsCAQgOFCQyJQIEDgUIiAIGDLdGj1wCIRAHEYJ/bgOIcIsWlSSDEoIq
X-IronPort-AV: E=Sophos;i="4.89,705,1367971200"; d="scan'208";a="234185334"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 20 Jul 2013 01:54:49 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6K1smLL022122 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 20 Jul 2013 01:54:48 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 19 Jul 2013 20:54:48 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMfFXKsyPbJdkelYGCtdmlYM5ltHJ2A
Date: Sat, 20 Jul 2013 01:54:47 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B944D85@xmb-rcd-x09.cisco.com>
References: <51E9735B.9030103@qti.qualcomm.com>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.91.168]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <38EB954114719C4087BE9A0F8AE57A7E@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: Sat, 20 Jul 2013 01:54:54 -0000

I think there would be some value in this; I personally would rather make t=
he tool manage a queue than make people do it. Unfortunately, it introduces=
 inconsistency and workload; I suspect that a likely change will be that pe=
ople will now ignore the deadline and assume they can get their working gro=
up chair to approve a draft as "special". That, of course, means that I am =
likely to start receiving a series of requests for special treatment during=
 the days following the start of queuing, and different chairs will take mo=
re or less hard-line positions. Note that *that* already happens as well; m=
y tools look for the text "-v6ops-" in the draft moniker, and I get request=
s to schedule drafts that are not in fact labelled as submissions to v6ops.

In v6ops, we have another factor; I really try to only put on the agenda th=
ings that have seen positive mailing list discussion, which is a rule I wou=
ld potentially have to modify, as I can't test the temperature without brea=
king the draft free from the moratorium queue.=20

For my working group, I think this would come down to "if you post after th=
e deadline, your draft will pop out after the IETF meeting". And by the way=
, I do mean "the Monday after"; if it pops out the Monday of the meeting, w=
hich it does now, we already have people trying to game that system, and th=
e one time I allowed it, it created some confusion.

An additional point; when I'm thinking about my agenda, one of my rules is =
that any draft we might discuss must have been posted since the past meetin=
g. Determination of that is straightforward today; the last draft posted fo=
r this meeting actually posted a few minutes after midnight UTC, which is t=
o say "on July 16", or was one of three drafts that somehow slipped through=
 on the 17th or 18th (perhaps posted manually after being mailed in); I can=
 simply ask whether the draft was posted after July 27. If drafts are queue=
d such as you suggest, I would humbly hope that their posting date (the dat=
e that shows up in the draft and in the ls -l line in my mirror as a result=
 of rsync) would be considered the date on which they came out of the queue=
, not the date they went in. I think I just called for some text modificati=
on in the holding queue, or for the draft queue to hold the .xml and recrea=
te the .txt file when posting.

For this meeting, I posted a draft agenda on 8 July indicating that there w=
ere a number of drafts I expected updates on, and that there was some proba=
bility of another -00 draft snaking through. Then the -00 deadline was exte=
nded. I have two later -00 drafts, one that came in on the 10th and one on =
the 15th. Neither of those got much list commentary due to timing, and I fe=
lt that I had to step away from the objective rule to a more subjective one=
 in deciding what to include; the problems addressed were both real and tim=
ely, so I included them. My rule is there because of a DDOS that occurred a=
 few years ago; for the Beijing meeting, I had 42 drafts to ask the questio=
n about, of which I actually scheduled half and should have scheduled 1/3.

So, all things considered, I think I would rather hold the -00 and -later d=
eadlines firm, having drafts that arrive after the deadline queued to pop o=
ut (and at least in the directory dated on) the Monday after the IETF meeti=
ng. You do what you need to do with IESG processing; in my working group, i=
f the IETF can't hold a deadline, I may find it necessary to impose my own =
for order's sake.


On Jul 19, 2013, at 6:11 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> Given the talk over the last week, I'd like to make a proposal. I have su=
ggested something like this before. If the chairs generally think this is a=
 good idea, then maybe we take it to the IETF list. (I have not passed this=
 by other ADs; they can pipe up as they see fit.)
>=20
> Proposal for draft submission deadline/moratorium:
>=20
> 1. The draft submission tool never shuts down. Everyone is *always* allow=
ed to submit drafts to the tool. However, they are not always posted.
>=20
> 2. For X weeks before an IETF plenary meeting and during the week of the =
meeting, all submitted drafts are queued but not posted. The draft deadline=
 is announced as X weeks. (I personally don't care what X is; suggestions w=
elcome.)
>=20
> 3. Queued WG drafts can be approved for posting by an AD or the chair(s) =
of that WG.
>=20
> 4. Queued individual submission drafts can be approved for posting by an =
AD.
>=20
> 5. At the completion of the IETF meeting, all queued drafts are released =
from the queue.
>=20
> (Other features that might be desirable, but I'm not sure about)
>=20
> 6a. Drafts that are in IESG-Evaluation are not queued.
> ...or...
> 6b. Drafts that are in IESG-Evaluation are always queued, regardless of m=
oratorium. An AD must release them.
>=20
> 7. Chairs can pre-approve draft posting during the moratorium, just as th=
ey do for -00 drafts.
>=20
> 8. Chairs can put a moratorium on a particular WG (for instance, before a=
n interim meeting).
>=20
> Thoughts?
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From fred@cisco.com  Fri Jul 19 22:33:38 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 C078121F99F6 for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 22:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.228
X-Spam-Level: 
X-Spam-Status: No, score=-110.228 tagged_above=-999 required=5 tests=[AWL=-0.228, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id isA1edlDACpt for <wgchairs@ietfa.amsl.com>; Fri, 19 Jul 2013 22:33:34 -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 EC4D811E81DD for <wgchairs@ietf.org>; Fri, 19 Jul 2013 22:33:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1327; q=dns/txt; s=iport; t=1374298414; x=1375508014; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uSSj3MwOYtPkA/JG5Y+66MQYlIx2Ozgs9s5065lfvvE=; b=eX0Mh4jL0qB85FOb3GXqKs5Ado/aiGJTJshnZB/bnE+cShpBZTcmObdj mE8/aOjsdzTKL8Nvik8gatCRsrfedozXhqEnOmxc5ygQ8RiPYyWAUfyvm v3XBe9fBqwwVZOxscvf7uSTPwcnuMoahsPDRy6hjF6s0QqgcGZ9HHPJyT c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAP0f6lGtJXG//2dsb2JhbABagwY1UMBQgREWdIIkAQEBAwE6PwULAgEIDhQUEDIlAgQOBQiIAgYMtzcEj1wCMQeDEG4DqSqDEoIq
X-IronPort-AV: E=Sophos;i="4.89,707,1367971200"; d="scan'208";a="237026817"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 20 Jul 2013 05:33:32 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6K5XWhA008914 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 20 Jul 2013 05:33:32 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Sat, 20 Jul 2013 00:33:32 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMfFXKsyPbJdkelYGCtdmlYM5lsoSWAgAAFXACAABqeAIAAB3WAgACXS4A=
Date: Sat, 20 Jul 2013 05:33:31 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B944F47@xmb-rcd-x09.cisco.com>
References: <51E9735B.9030103@qti.qualcomm.com> <9C79BDE0-3703-478F-BCB9-32CDBE0DBC50@vpnc.org> <51E985AA.8090207@qti.qualcomm.com> <8D3D17ACE214DC429325B2B98F3AE712984ACAFE@MX15A.corp.emc.com> <51FD0701-4B57-498C-9011-B95703B16A87@checkpoint.com>
In-Reply-To: <51FD0701-4B57-498C-9011-B95703B16A87@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.91.168]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EFF0B612F1F49544ABE13AB3AE05006F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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, 20 Jul 2013 05:33:38 -0000

On Jul 19, 2013, at 9:31 PM, Yoav Nir <ynir@checkpoint.com> wrote:

> Note the word sometimes. I don't think newbies take away from this that t=
hey have to name their documents thus to get the chairs to consider them. I=
 know I didn't follow this convention for the first drafts that I posted.

In fairness, they don't *have* to. What they *do* have to do is bring them =
to the chair's attention. In my case, and in the case of tools like https:/=
/datatracker.ietf.org/doc/search/?name=3Dv6ops&rfcs=3Don&activeDrafts=3Don&=
search_submit=3D, putting the working group name into the draft name pretty=
 quickly gets the chair's attention. In my case, I even have some tooling b=
ehind that. I have a daily bot that updates a mirror and some files interna=
l to Cisco. My bot notices a new -00 draft to v6ops, sends a note to the au=
thors wondering what it's about and how it relates to the charter with a re=
ply-to of the chairs, and it sends a note to the working group inviting dis=
cussion. We often get some pretty quick early discussion as a result, and t=
hat discussion often figures into whether the draft is discussed f2f. When =
they don't put the working group moniker in there, they have to do that the=
mselves.

But I do agree that it would be useful to *say* that in the guidelines.=

From leifj@sunet.se  Sat Jul 20 01:16:47 2013
Return-Path: <leifj@sunet.se>
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 5088F11E80E6 for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 01:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m85hJwECCJGO for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 01:16:46 -0700 (PDT)
Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [IPv6:2001:6b0:8:2::202]) by ietfa.amsl.com (Postfix) with ESMTP id 5E67411E80CC for <wgchairs@ietf.org>; Sat, 20 Jul 2013 01:16:45 -0700 (PDT)
Received: from smtp1.nordu.net (smtp1.nordu.net [IPv6:2001:948:4:6::32]) by e-mailfilter02.sunet.se (8.14.3/8.14.3/Debian-9.4) with ESMTP id r6K8GfwB026956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Sat, 20 Jul 2013 10:16:41 +0200
Received: from [172.20.10.6] (2.67.25.70.mobile.tre.se [2.67.25.70]) (authenticated bits=0) by smtp1.nordu.net (8.14.6/8.14.6) with ESMTP id r6K8GYdM015788 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <wgchairs@ietf.org>; Sat, 20 Jul 2013 08:16:41 GMT
Message-ID: <51EA4760.5000009@sunet.se>
Date: Sat, 20 Jul 2013 10:16:32 +0200
From: Leif Johansson <leifj@sunet.se>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <51E97512.7040108@bbiw.net> <51E97710.6050007@qti.qualcomm.com>
In-Reply-To: <51E97710.6050007@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, nordu-net:default, base:default, @@RPTN)
X-p0f-Info: os=unknown unknown, link=Ethernet or modem
X-CanIt-Geo: ip=2.67.25.70; country=SE; region=26; city=Tyreso; latitude=59.2333; longitude=18.3000; http://maps.google.com/maps?q=59.2333,18.3000&z=6
X-CanItPRO-Stream: outbound-nordu-net:outbound (inherits from outbound-nordu-net:default, nordu-net:default, base:default)
X-Canit-Stats-ID: 0aK2wgFya - 4958be3abfaa - 20130720
X-Antispam-Training-Forget: https://mailfilter.nordu.net/canit/b.php?i=0aK2wgFya&m=4958be3abfaa&t=20130720&c=f
X-Antispam-Training-Nonspam: https://mailfilter.nordu.net/canit/b.php?i=0aK2wgFya&m=4958be3abfaa&t=20130720&c=n
X-Antispam-Training-Spam: https://mailfilter.nordu.net/canit/b.php?i=0aK2wgFya&m=4958be3abfaa&t=20130720&c=s
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
X-Scanned-By: CanIt (www . roaringpenguin . 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: Sat, 20 Jul 2013 08:16:47 -0000

On 07/19/2013 07:27 PM, Pete Resnick wrote:
> On 7/19/13 12:19 PM, Dave Crocker wrote:
>> You've just increased the workload of ADs and chairs.
>
> This only changes the workload if the ADs and chairs even look at the
> queue. There is no requirement that they do so.
>
> ADs already get email to approve posting after the deadline. This
> might increase the number of requests to do so.
>
> And how many drafts do you think any given WG chair will have to look
> at, even if they chose to look at the queue?
>
> Color me unconvinced.
I don't think it will be that bad either but I'm not sure what problem
is being solved really - what happens today is that late submissions
are "pre-released" directly to the mailing list for discussion.
>
>> I'll suggest something a bit different:
>
> I suspect your proposal will get a similar amount of pushback that the
> simpler "No deadline at all" proposal got. And I'd prefer to discuss
> the merits of this proposal on its own and see if it can get some
> consensus before discussing alternatives.
>
> pr
>


From acmorton@att.com  Sat Jul 20 08:03:19 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 F38D711E810F for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 08:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.276
X-Spam-Level: 
X-Spam-Status: No, score=-106.276 tagged_above=-999 required=5 tests=[AWL=0.323, 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 iuBd8coAjVCM for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 08:03:12 -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 B512611E810E for <wgchairs@ietf.org>; Sat, 20 Jul 2013 08:03:12 -0700 (PDT)
Received: from mail-green.research.att.com (unknown [135.207.178.10]) by mail-pink.research.att.com (Postfix) with ESMTP id 78A411201D9; Sat, 20 Jul 2013 11:03:10 -0400 (EDT)
Received: from njfpsrvexg7.research.att.com (njfpsrvexg7.research.att.com [135.207.177.33]) by mail-green.research.att.com (Postfix) with ESMTP id 01178E0189; Sat, 20 Jul 2013 11:02:57 -0400 (EDT)
Received: from njfpsrvexg7.research.att.com ([fe80::3598:75fe:b400:9299]) by njfpsrvexg7.research.att.com ([fe80::3598:75fe:b400:9299%11]) with mapi; Sat, 20 Jul 2013 11:03:12 -0400
From: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>
To: Peter Koch <pk@ISOC.DE>, WG Chairs <wgchairs@ietf.org>
Date: Sat, 20 Jul 2013 11:03:11 -0400
Subject: RE: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: Ac6EwSWIGj0QNT4sTRaJ3Tk2hM72KgAlz2QA
Message-ID: <F1312FAF1A1E624DA0972D1C9A91379A1CA4D67A30@njfpsrvexg7.research.att.com>
References: <51E9735B.9030103@qti.qualcomm.com> <20130719204702.GB23086@x28.adm.denic.de>
In-Reply-To: <20130719204702.GB23086@x28.adm.denic.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: 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, 20 Jul 2013 15:03:19 -0000

I think Peter K's point on review is particularly relevant
in my experience:
...
>=20
> On Fri, Jul 19, 2013 at 12:11:55PM -0500, Pete Resnick wrote:
>=20
...
> > 3. Queued WG drafts can be approved for posting by an AD or the chair(s=
)
> > of that WG.
>=20
> Sure chairs can manage and 'just say no', but on the other hand we're all
> encouraged to be pragmatic, flexible, and inclusive. Isn't it great that
> we usually have two co-chairs so we can play the 'good cop - bad cop'
> game?
>=20
> We don't need more process, we need more quality review.  Give people
> credit for those and in return they can post drafts whenever they want.
>=20
> -Peter

Working until the deadline and submitting a draft then reduces
the probability of a quality review, just on the basis of volume. =20
I continue to encourage authors to work toward interim releases
that folks can review when they have time - it also leaves more time to fos=
ter a
review "barter system". But I can live with a lot of Pete R's proposals
as they may help to move the work forward in some WGs, recognizing
that we all work a little differently.

just 2 cents more,
Al


From dcrocker@bbiw.net  Sat Jul 20 08:09:23 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 304F411E8118 for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 08:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIlD5AyQ95NI for <wgchairs@ietfa.amsl.com>; Sat, 20 Jul 2013 08:09:18 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 19BFC11E810C for <wgchairs@ietf.org>; Sat, 20 Jul 2013 08:09:18 -0700 (PDT)
Received: from [192.168.0.83] (host-212-159-176-45.static.as13285.net [212.159.176.45]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6KF99Zu005622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 20 Jul 2013 08:09:14 -0700
Message-ID: <51EAA7EE.4080508@bbiw.net>
Date: Sat, 20 Jul 2013 16:08:30 +0100
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: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06DD37@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]); Sat, 20 Jul 2013 08:09:15 -0700 (PDT)
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Sat, 20 Jul 2013 15:09:23 -0000

On 7/20/2013 1:25 AM, DRAGE, Keith (Keith) wrote:
> Much of this works for me.
>
> However it puts a lot of responsibility on the chairs protecting the interests of the WG members.


It requires chairs to do the basics of managing their working group.

The task of deciding what documents (and what versions of those 
documents) will be reviewed at the meeting and what the submission 
deadline needs to be for the docs is not unusual or onerous, within the 
scope of managing a collaborative group.

If the chair or the wg have a problem doing that, the working group has 
bigger problems than just the meeting a submission deadline.

If, for example, the chair fails to do the scheduling or fails to do it 
collaboratively enough with the wg, then the wg needs to fix the chair 
or replace them.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From keith.drage@alcatel-lucent.com  Sun Jul 21 09:58:35 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 BF74421E8091 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 09:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.432
X-Spam-Level: 
X-Spam-Status: No, score=-109.432 tagged_above=-999 required=5 tests=[AWL=-1.133, BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3iRbPuj7gri for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 09:58:30 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 446D121E808B for <wgchairs@ietf.org>; Sun, 21 Jul 2013 09:58:29 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r6LGwQl6021659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Jul 2013 11:58:28 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6LGwPtc024938 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Jul 2013 18:58:25 +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; Sun, 21 Jul 2013 18:58:25 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: RE: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMc0B5m+r5AeUit/uiKeb85u5lstQuA///h3ICAAsRKQA==
Date: Sun, 21 Jul 2013 16:58:24 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06F537@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <51E9735B.9030103@qti.qualcomm.com> <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com> <8D23D4052ABE7A4490E77B1A012B63077521BFD2@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077521BFD2@mbx-01.win.nominum.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [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.33
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Sun, 21 Jul 2013 16:58:35 -0000

I would rather the update happened with time for chairs and WG membership t=
o absorb the changes.

Looks to me like any proposal such as this should be accompanied with some =
guidance to the chairs.

My view is leaning heavily towards updates after the deadline should not ne=
ed to happen - either the changes are so minor that they can be explained i=
n the presentation and the revision provided later, or they are so major th=
at noone would have a change to absorb them no matter how much presentation=
 time was allowed.

And in the way this is presented, the default behaviour for the chairs shou=
ld be to ignore impacted submissions unless a really good case is presented=
 for releasing them.

I certainly am in favour of the moratorium not applying at all to documents=
; i.e. those that are not on the agenda for the meeting should not need to =
be held. Conversely, I would like in some ways to establish a selective mor=
atorium for interim meetings.

And finally, I begin to think I liked the 3 week moratorium for new documen=
ts. This at least forced the submitter to identify what a potential documen=
t would be about (and therefore gave more time to discuss whether it might =
need an agenda slot) - I worry less about such a document going from -00 to=
 -01 in a few days (i.e. between 3 weeks and 2 weeks) because the submitter=
 added content later.

Keith

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
> Sent: 20 July 2013 01:34
> To: DRAGE, Keith (Keith)
> Cc: Pete Resnick; WG Chairs
> Subject: Re: Draft submission deadline/moratorium tool proposal
>=20
> On Jul 19, 2013, at 7:25 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-
> lucent.com> wrote:
> > How would I as a member of the WG stop that happening, without having t=
o
> waste 10 minutes of WG time at the start of the WG meeting having
> discovered that the agenda was updated while my back was turned.
>=20
> I am highly sympathetic to this concern.   However, I do wonder: would yo=
u
> rather the update _didn't_ happen?   Would you rather discuss the previou=
s
> version of the document?   I think this is something that chairs and
> authors should avoid, and I would certainly not be happy if one of the
> working groups for which I am responsible AD did this.   However, in
> practice if the changes are small, rfcdiff is actually a very quick way t=
o
> familiarize yourself with changes, if you are already familiar with the
> draft.
>=20
> So much as I want to agree with you that this sort of behavior is
> inappropriate, I am hard pressed to do so.   A better way to characterize
> it is "poorly timed."   If the working group chairs want the draft to be
> discussed at the meeting, they should make damned sure that the working
> group is made aware of the update, and the working group is well within
> its rights to say "look, we haven't had time to review this, let's drop i=
t
> from the agenda until the next meeting."
>=20
> And the way you effect that is to get up at the mic during agenda bashing
> and say so.


From keith.drage@alcatel-lucent.com  Sun Jul 21 10:01:59 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 6032F11E80FA for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:01:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.544
X-Spam-Level: 
X-Spam-Status: No, score=-110.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 Bt9lksuOlZFY for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:01:53 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBAB11E80F6 for <wgchairs@ietf.org>; Sun, 21 Jul 2013 10:01:53 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r6LH1aEU008021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Jul 2013 12:01:38 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6LH1ZBq025747 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Jul 2013 19:01: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; Sun, 21 Jul 2013 19:01:35 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: RE: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMc0B5m+r5AeUit/uiKeb85u5lstQuAgADWJACAAdK7QA==
Date: Sun, 21 Jul 2013 17:01:35 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06F550@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <51E9735B.9030103@qti.qualcomm.com> <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51EAA7EE.4080508@bbiw.net>
In-Reply-To: <51EAA7EE.4080508@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: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Sun, 21 Jul 2013 17:01:59 -0000

You seem to be assuming that WG chairs have lots of spare time in order to =
do this.

At least in the RAI area, we are short of chairs, and many of the existing =
ones have many other commitments.=20

Any tools that handle things automatically save the WG chair devoting cycle=
s.

The -00 and -xx deadlines at least made sure (in a very heavy handed manner=
) that all documents to be considered for the meeting where much more easil=
y identified, without constant prompting from the chairs.

Regards

Keith

> -----Original Message-----
> From: Dave Crocker [mailto:dcrocker@bbiw.net]
> Sent: 20 July 2013 16:09
> To: DRAGE, Keith (Keith)
> Cc: Pete Resnick; WG Chairs
> Subject: Re: Draft submission deadline/moratorium tool proposal
>=20
> On 7/20/2013 1:25 AM, DRAGE, Keith (Keith) wrote:
> > Much of this works for me.
> >
> > However it puts a lot of responsibility on the chairs protecting the
> interests of the WG members.
>=20
>=20
> It requires chairs to do the basics of managing their working group.
>=20
> The task of deciding what documents (and what versions of those
> documents) will be reviewed at the meeting and what the submission
> deadline needs to be for the docs is not unusual or onerous, within the
> scope of managing a collaborative group.
>=20
> If the chair or the wg have a problem doing that, the working group has
> bigger problems than just the meeting a submission deadline.
>=20
> If, for example, the chair fails to do the scheduling or fails to do it
> collaboratively enough with the wg, then the wg needs to fix the chair
> or replace them.
>=20
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From repenno@cisco.com  Sun Jul 21 10:55:08 2013
Return-Path: <repenno@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 C5DE221F868C for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.449
X-Spam-Level: 
X-Spam-Status: No, score=-9.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svadrvCvA1Yo for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:55:04 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id B8B5521F9CE7 for <wgchairs@ietf.org>; Sun, 21 Jul 2013 10:55:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3701; q=dns/txt; s=iport; t=1374429303; x=1375638903; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=y1r7IYArByM+R10NrttaCzqFqMTAp5n4CN+ITWudctc=; b=nGm+Kbgn+T9tdE5x0cAcKwcPu4zNKdlm1fVrp8Bb/a4hcHGPVSxbYCby ITfmKHYnjZyKNxXf8/3hqUrfUFJSl+ksjoXAMmQzYoBPEGimbw9EAHewQ IcIjoltH7+Uun9GUcQQi/xkSC2MJ0OtjeEw1BuRYvsT1sJilT+RrlJq1Z 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjoFACAf7FGtJV2a/2dsb2JhbABQCoMGNVDAMIEWFnSCJAEBAQEDOj8MBgEIEQQBAQEKFAk5FAkIAgQBDQUIiAi2EI5agQsxBwaDCm4DmQaQJIMSgio
X-IronPort-AV: E=Sophos;i="4.89,714,1367971200"; d="scan'208";a="237521295"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 21 Jul 2013 17:55:03 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6LHt2vk031715 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Jul 2013 17:55:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Sun, 21 Jul 2013 12:55:02 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: AQHOhKMfKTUhhG3ob0CfSKAOG123/JltCckAgAACdoCAAqVSAP//3YWA
Date: Sun, 21 Jul 2013 17:55:01 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604090CA6DE@xmb-rcd-x04.cisco.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06F537@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.242.80]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FDE488FE3F88A444BAACC7AD1CBB072C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Sun, 21 Jul 2013 17:55:08 -0000

One of the problems I faced multiple times while attending IETF remotely
is last minute changes. Presentation and draft not in synch with each
other, discussion on topics that were added to the draft at the last
revision during IETF, presentations uploaded or changed 10 seconds before
it starts, etc..=20

I think some deadline is useful to promote a smoother virtual attendance
and give people time to familiarize with the material.



On 7/21/13 1:58 PM, "DRAGE, Keith (Keith)"
<keith.drage@alcatel-lucent.com> wrote:

>I would rather the update happened with time for chairs and WG membership
>to absorb the changes.
>
>Looks to me like any proposal such as this should be accompanied with
>some guidance to the chairs.
>
>My view is leaning heavily towards updates after the deadline should not
>need to happen - either the changes are so minor that they can be
>explained in the presentation and the revision provided later, or they
>are so major that noone would have a change to absorb them no matter how
>much presentation time was allowed.
>
>And in the way this is presented, the default behaviour for the chairs
>should be to ignore impacted submissions unless a really good case is
>presented for releasing them.
>
>I certainly am in favour of the moratorium not applying at all to
>documents; i.e. those that are not on the agenda for the meeting should
>not need to be held. Conversely, I would like in some ways to establish a
>selective moratorium for interim meetings.
>
>And finally, I begin to think I liked the 3 week moratorium for new
>documents. This at least forced the submitter to identify what a
>potential document would be about (and therefore gave more time to
>discuss whether it might need an agenda slot) - I worry less about such a
>document going from -00 to -01 in a few days (i.e. between 3 weeks and 2
>weeks) because the submitter added content later.
>
>Keith
>
>> -----Original Message-----
>> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
>> Sent: 20 July 2013 01:34
>> To: DRAGE, Keith (Keith)
>> Cc: Pete Resnick; WG Chairs
>> Subject: Re: Draft submission deadline/moratorium tool proposal
>>=20
>> On Jul 19, 2013, at 7:25 PM, "DRAGE, Keith (Keith)"
>><keith.drage@alcatel-
>> lucent.com> wrote:
>> > How would I as a member of the WG stop that happening, without having
>>to
>> waste 10 minutes of WG time at the start of the WG meeting having
>> discovered that the agenda was updated while my back was turned.
>>=20
>> I am highly sympathetic to this concern.   However, I do wonder: would
>>you
>> rather the update _didn't_ happen?   Would you rather discuss the
>>previous
>> version of the document?   I think this is something that chairs and
>> authors should avoid, and I would certainly not be happy if one of the
>> working groups for which I am responsible AD did this.   However, in
>> practice if the changes are small, rfcdiff is actually a very quick way
>>to
>> familiarize yourself with changes, if you are already familiar with the
>> draft.
>>=20
>> So much as I want to agree with you that this sort of behavior is
>> inappropriate, I am hard pressed to do so.   A better way to
>>characterize
>> it is "poorly timed."   If the working group chairs want the draft to be
>> discussed at the meeting, they should make damned sure that the working
>> group is made aware of the update, and the working group is well within
>> its rights to say "look, we haven't had time to review this, let's drop
>>it
>> from the agenda until the next meeting."
>>=20
>> And the way you effect that is to get up at the mic during agenda
>>bashing
>> and say so.
>


From keith.drage@alcatel-lucent.com  Sun Jul 21 10:55:44 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 756F121E8094 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.545
X-Spam-Level: 
X-Spam-Status: No, score=-110.545 tagged_above=-999 required=5 tests=[AWL=0.053, 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 d3zCuh3AR9z8 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 10:55:38 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id E562721F9D71 for <wgchairs@ietf.org>; Sun, 21 Jul 2013 10:55:34 -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 r6LHtQxA010494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Jul 2013 12:55:28 -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 r6LHtQ4p015538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Jul 2013 19:55:26 +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; Sun, 21 Jul 2013 19:55:26 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: RE: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Topic: WG Agendas to submit only 2 days after -00 submission cut-off date
Thread-Index: AQHOg+zrOvASPXVymUWzIDlWAXvZvJlvbWBA
Date: Sun, 21 Jul 2013 17:55:25 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B06F5C6@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com>
In-Reply-To: <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@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.41]
Content-Type: multipart/alternative; boundary="_000_949EF20990823C4C85C18D59AA11AD8B06F5C6FR712WXCHMBA11zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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: Sun, 21 Jul 2013 17:55:44 -0000

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

What I am not buying is your contention that confusion does not exist becau=
se dispatch has different deadlines.

I'd note the words

"in cases where documents are clearly under the purview for a specific WG, =
then it's not an issue to go directly to the WG"

Do not actually appear in the DISPATCH charter - which refers generally to =
"new work" without any further clarification.

So we are left having to interpret the overlap between charters of existing=
 WG, which presumably have some ownership and DISPATCH.

So for discussions that fall in this overlap, the fact that DISPATCH has di=
fferent deadlines adds to the confusion.

And I can list a number of documents in the past where the author has waver=
ed between DISPATCH and other working groups, and apparently ended up going=
 for the wrong working group.

Keith

________________________________
From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 18 July 2013 20:28
To: DRAGE, Keith (Keith)
Cc: Flemming Andreasen; wgchairs@ietf.org
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off =
date

On Thu, Jul 18, 2013 at 2:10 PM, DRAGE, Keith (Keith) <keith.drage@alcatel-=
lucent.com<mailto:keith.drage@alcatel-lucent.com>> wrote:
Sorry - not buying this.
[MB] Then you should raise the issue to the ADs.  I'm the implementer of a =
process that is in place for managing work in their area. [/MB]

Your comment is only applicable if you buy the argument that all new propos=
als, whether in scope or out of scope of another RAI working group, go to D=
ISPATCH, and that currently does not appear to be the case. So there is the=
 case of a document being submitted, and then some evaluation occurs that m=
aybe it ought to have been in DISPATCH, after the DISPATCH deadlines have p=
assed.
[MB] As I said previously, in cases where documents are clearly under the p=
urview for a specific WG, then it's not an issue to go directly to the WG. =
 BTW, I have no idea what document you're referring to. And, keep in mind t=
hat the process requires notifying the chairs, so it may not be visible to =
you what discussions might occur offline. [/MB]
Even I am not sure if a document should be in DISPATCH or not. If I read fo=
llow the DISPATCH charter alone, then there are a number of other items on =
the MMUSIC agenda that have never been dispatched to MMUSIC (or anywhere el=
se), and therefore ought to be in DISPATCH. They do fall in scope of the MM=
USIC agenda. I could point this out in a number of other working groups. EC=
RIT even has stuff on the agenda that is not in the scope of ECRIT, has nev=
er been through DISPATCH and so on.
[MB]  I only see one document on the MMUSIC WG agenda that probably should =
have first gone to DISPATCH and actually, the MMUSIC chairs could have rais=
ed that issue and suggested such to the document authors rather than give a=
genda time when they certainly do have really high priority, critical items=
 to discuss.   The document I am referring to relates to at least two diffe=
rent WGs (including one that is now closed) and wasn't at all an obvious fi=
t for MMUSIC.    In addition, as I said, it should have been obvious that t=
here was a fairly clear expectation that  the websocket and alternate trans=
port docs are first discussed in  DISPATCH - e.g., BFCPbis, mrsp websocket =
document, etc.
[/MB]

If the deadlines for DISPATCH had not been different, then maybe there woul=
d have been different issues, but at least it is the different DISPATCH dea=
dlines that have currently ruled out the discussion of this document in Ber=
lin.
[MB] That's absolutely correct - that's the whole intent of the DISPATCH de=
adlines - these authors simply had to send an email to the DISPATCH WG chai=
rs by June 24th indicating they were putting together a draft that was an a=
lternative to a previously discussed draft.  They didn't do so.  If they ha=
d submitted the draft by July 1st, there would have been some flexibility, =
but that wasn't the case.  There were other people that did so, that also r=
equested agenda time that were not given agenda time because it wasn't deem=
ed necessary. AGain, you can progress work without discussing at a f2f meet=
ing.

 If you have issues with the DISPATCH process, then please bring those to t=
he DISPATCH WG or better yet RAI area mailing list.  We've had this process=
 in place for 4 years so the concept of notifying the chairs several weeks =
before draft deadlines has been there the whole time. Indeed, we had the da=
tes for IETF-87 much later than usual.   Keep in mind as well that there is=
 NOTHING in the DISPATCH/RAI process that requires a document to have f2f d=
iscussion.  Additionally, keep in mind that the document in question has no=
rmative dependencies such that this document cannot be published until thos=
e docs are completed. [/MB]

Regards

Keith

________________________________
From: wgchairs-bounces@ietf.org<mailto:wgchairs-bounces@ietf.org> [mailto:w=
gchairs-bounces@ietf.org<mailto:wgchairs-bounces@ietf.org>] On Behalf Of Ma=
ry Barnes
Sent: 18 July 2013 19:28
To: Flemming Andreasen

Cc: wgchairs@ietf.org<mailto:wgchairs@ietf.org>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off =
date

I have on comment below on an example cited as to the problems with the sin=
gle deadline.

Mary.

On Wed, Jul 17, 2013 at 6:27 PM, Flemming Andreasen <fandreas@cisco.com<mai=
lto:fandreas@cisco.com>> wrote:

On 7/17/13 12:14 AM, Ted Lemon wrote:
On Jul 16, 2013, at 9:03 PM, Flemming Andreasen <fandreas@cisco.com<mailto:=
fandreas@cisco.com>> wrote:
You risk a lot of other pushback when you start making up your own WG-speci=
fic rules (and rightfully so).
It's hard to understand what you might mean by this.
When you have a single set of consistent rules that are written down, it's =
easy for everybody to understand and accept. When the rules are WG specific=
 and are created at the discretion of the WG chairs it becomes more of a ch=
allange:
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don't go as they like.

Neither is desirable.

All true in theory, but this is not how it happens and works in practice. I=
 prefer being pragmatic. It worked reasonably well the way it was before; i=
t's not working well the way it's being done now.
Can you cite an example of an actual problem that has occurred because of t=
his change?
Sure. I'm travelling this week and had to scramble last night to look at se=
veral -00 drafts that were requested to be on the agenda. I had to get on a=
 5:30 am call this morning to coordinate the draft agenda with my co-chair =
due to the impending draft agenda deadline. The result feels a bit rushed w=
ith little time to dig into exactly what the issues are in the drafts and h=
ence what to prioritize and with how much time allocated.

Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren't quite sure which group it belon=
ged to, asked for an MMUSIC slot, and it then bounced around between severa=
l WG chairs. By the time we all agreed it indeed did belong to DISPATCH, it=
 was all too late because DISPATCH hadn't received an agenda request in tim=
e.
[MB] This one is not a particularly good example in terms of problems cause=
d by the deadlines.  This is an example of someone not following the RAI/DI=
SPATCH WG process.  It should have been no surprise to the authors that the=
 document should be discussed first in the DISPATCH WG, as that is our basi=
c process unless it's beyond obvious that it is related specifically to an =
existing chartered WG.  In addition, these authors (one of whom is not an i=
nexperienced IETFer) should have been aware of how we were handling documen=
ts of a similar nature as we dispatched several at the last IETF meeting.  =
I think this is an example of WG shopping and not of too late deadlines.  I=
n particular given that the DISPATCH deadline required that notification of=
 intent to submit a document and desire to discuss a topic in dispatch was =
June 24th, with charter proposals/problem statements due July 1st. This doc=
ument was submitted well over a week after the last deadline.  There's noth=
ing wrong with a WG chair flat out saying that a document wasn't submitted =
in time to garner enough consideration to warrant agenda time at the f2f me=
eting.  Again, the RAI/DISPATCH process allows progression of documents wit=
hout ever having been discussed at a f2f meeting.  We should continue discu=
ssion of situations like this on the RAI area list where there is discussio=
n of process/structural issues that are currently being encountered:
http://www.ietf.org/mail-archive/web/rai/current/msg01384.html
It is unfortunate for you (and not at all your fault) that your WG is in th=
e middle of the concerns raised, but I think the draft deadlines are the le=
ast of your problems.
[/MB]


We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.

Thanks

-- Flemming






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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" xmlns=3D"http://ww=
w.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType namespaceuri=3D"urn:schemas-microsoft-com:offic=
e:smarttags" name=3D"State" /><o:SmartTagType namespaceuri=3D"urn:schemas-m=
icrosoft-com:office:smarttags" name=3D"place" /><o:SmartTagType namespaceur=
i=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"time" /><o:SmartTa=
gType namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"d=
ate" /><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"blue">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">What I am not buying is your contentio=
n that confusion does not exist because dispatch has different deadlines.<o=
:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">I&#8217;d note the words
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">&#8220;</span></font>in cases where do=
cuments are clearly under the purview for a specific WG, then it's not an i=
ssue to go directly to the
 WG&#8221; <o:p></o:p></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Do not actually appear in the DISPATCH=
 charter &#8211; which refers generally to &#8220;new work&#8221; without a=
ny further clarification.
<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">So we are left having to interpret the=
 overlap between charters of existing WG, which presumably have some owners=
hip and DISPATCH.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">So for discussions that fall in this o=
verlap, the fact that DISPATCH has different deadlines adds to the confusio=
n.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">And I can list a number of documents i=
n the past where the author has wavered between DISPATCH and other working =
groups, and apparently
 ended up going for the wrong working group.<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy">Keith<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</=
span></font></b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma"> Mary Barnes
 [mailto:mary.ietf.barnes@gmail.com] <br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 20:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> DRAGE, Keith (Keith)<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> Flemming Andreasen; wgch=
airs@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</span></font><span lang=
=3D"EN-US"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">On Thu,
<st1:date Year=3D"2013" Day=3D"18" Month=3D"7" ls=3D"trans" w:st=3D"on">Jul=
 18, 2013</st1:date> at
<st1:time Minute=3D"10" Hour=3D"14" w:st=3D"on">2:10 PM</st1:time>, DRAGE, =
Keith (Keith) &lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com" target=
=3D"_blank">keith.drage@alcatel-lucent.com</a>&gt; wrote:<o:p></o:p></span>=
</font></p>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">Sorry &#8211; not buying this.</span></font><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[MB] Then you should raise the issue to the ADs. &nbsp;I'm the impl=
ementer of a process that is in place for managing work in their area. [/MB=
]&nbsp;<o:p></o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">Your comment is only applicable if you buy the argument that al=
l new proposals,
 whether in scope or out of scope of another RAI working group, go to DISPA=
TCH, and that currently does not appear to be the case. So there is the cas=
e of a document being submitted, and then some evaluation occurs that maybe=
 it ought to have been in DISPATCH,
 after the DISPATCH deadlines have passed.</span></font><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[MB] As I said previously, in cases where documents are clearly und=
er the purview for a specific WG, then it's not an issue to go directly to =
the WG. &nbsp;BTW, I have no
 idea what document you're referring to. And, keep in mind that the process=
 requires notifying the chairs, so it may not be visible to you what discus=
sions might occur offline. [/MB]</span></font><font size=3D"2" color=3D"nav=
y" face=3D"Arial"><span style=3D"font-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">Even I am not sure if a document should be in DISPATCH or not. =
If I read follow
 the DISPATCH charter alone, then there are a number of other items on the =
MMUSIC agenda that have never been dispatched to MMUSIC (or anywhere else),=
 and therefore ought to be in DISPATCH. They do fall in scope of the MMUSIC=
 agenda. I could point this out
 in a number of other working groups. ECRIT even has stuff on the agenda th=
at is not in the scope of ECRIT, has never been through DISPATCH and so on.=
</span></font><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[MB] &nbsp;I only see one document on the MMUSIC WG agenda that pro=
bably should have first gone to DISPATCH and actually, the MMUSIC chairs co=
uld have raised that issue and
 suggested such to the document authors rather than give agenda time when t=
hey certainly do have really high priority, critical items to discuss. &nbs=
p; The document I am referring to relates to at least two different WGs (in=
cluding one that is now closed) and wasn't
 at all an obvious fit for MMUSIC. &nbsp; &nbsp;In addition, as I said, it =
should have been obvious that there was a fairly clear expectation that &nb=
sp;the websocket and alternate transport docs are first discussed in &nbsp;=
DISPATCH - e.g., BFCPbis, mrsp websocket document, etc.
 &nbsp; &nbsp;&nbsp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[/MB]<o:p></o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">If the deadlines for DISPATCH had not been different, then mayb=
e there would
 have been different issues, but at least it is the different DISPATCH dead=
lines that have currently ruled out the discussion of this document in
<st1:State w:st=3D"on"><st1:place w:st=3D"on">Berlin</st1:place></st1:State=
>.</span></font><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">[MB] That's absolutely correct - that's the whole intent of the DIS=
PATCH deadlines - these authors simply had to send an email to the DISPATCH=
 WG chairs by June 24th
 indicating they were putting together a draft that was an alternative to a=
 previously discussed draft. &nbsp;They didn't do so. &nbsp;If they had sub=
mitted the draft by July 1st, there would have been some flexibility, but t=
hat wasn't the case. &nbsp;There were other people
 that did so, that also requested agenda time that were not given agenda ti=
me because it wasn't deemed necessary. AGain, you can progress work without=
 discussing at a f2f meeting.&nbsp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt">&nbsp;If you have issues with the DISPATCH process, then please bri=
ng those to the DISPATCH WG or better yet RAI area mailing list. &nbsp;We'v=
e had this process in place for 4
 years so the concept of notifying the chairs several weeks before draft de=
adlines has been there the whole time. Indeed, we had the dates for IETF-87=
 much later than usual. &nbsp; Keep in mind as well that there is NOTHING i=
n the DISPATCH/RAI process that requires
 a document to have f2f discussion. &nbsp;Additionally, keep in mind that t=
he document in question has normative dependencies such that this document =
cannot be published until those docs are completed. [/MB]&nbsp;<o:p></o:p><=
/span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">Regards</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">Keith</span></font><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"2" color=3D"navy" face=3D"Arial"><span style=3D"font=
-size:10.0pt;font-family:Arial;
color:navy">&nbsp;</span></font><o:p></o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt;
border-width:initial;border-color:initial">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></font></div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><font size=3D"2" face=3D"Tahoma"><span lang=3D"EN-US" style=3D"=
font-size:10.0pt;font-family:Tahoma;
font-weight:bold">From:</span></font></b><font size=3D"2" face=3D"Tahoma"><=
span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:Tahoma">
<a href=3D"mailto:wgchairs-bounces@ietf.org" target=3D"_blank">wgchairs-bou=
nces@ietf.org</a> [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" targ=
et=3D"_blank">wgchairs-bounces@ietf.org</a>]
<b><span style=3D"font-weight:bold">On Behalf Of </span></b>Mary Barnes<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 19:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> Flemming Andreasen</span=
></font><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Tahoma"><span style=3D"font=
-size:12.0pt;
font-family:Tahoma"><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:wgchai=
rs@ietf.org" target=3D"_blank">
wgchairs@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</span></font><o:p></o:p=
></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">&nbsp;<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">I have on comment below on an example cited as to the problems wit=
h the single deadline.&nbsp;<o:p></o:p></span></font></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">&nbsp;<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">Mary.<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0p=
t">&nbsp;<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">On Wed,
<st1:date Year=3D"2013" Day=3D"17" Month=3D"7" ls=3D"trans" w:st=3D"on">Jul=
 17, 2013</st1:date> at
<st1:time Minute=3D"27" Hour=3D"18" w:st=3D"on">6:27 PM</st1:time>, Flemmin=
g Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fan=
dreas@cisco.com</a>&gt; wrote:<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt"><br>
On <st1:date Year=3D"13" Day=3D"17" Month=3D"7" ls=3D"trans" w:st=3D"on">7/=
17/13</st1:date>
<st1:time Minute=3D"14" Hour=3D"0" w:st=3D"on">12:14 AM</st1:time>, Ted Lem=
on wrote:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">On
<st1:date Year=3D"2013" Day=3D"16" Month=3D"7" ls=3D"trans" w:st=3D"on">Jul=
 16, 2013</st1:date>, at
<st1:time Minute=3D"03" Hour=3D"21" w:st=3D"on">9:03 PM</st1:time>, Flemmin=
g Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fan=
dreas@cisco.com</a>&gt; wrote:<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">You risk a lot of other pushback when you start making up your own=
 WG-specific rules (and rightfully so).<o:p></o:p></span></font></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">It's hard to understand what you might mean by this.<o:p></o:p></s=
pan></font></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">When you have a single set of consistent rules that are written do=
wn, it's easy for everybody to understand
 and accept. When the rules are WG specific and are created at the discreti=
on of the WG chairs it becomes more of a challange:<br>
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)<br>
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don't go as they like.<br>
<br>
Neither is desirable.<o:p></o:p></span></font></p>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt;
border-width:initial;border-color:initial">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">&nbsp;<o:p></o:p></span></font></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt;
border-width:initial;border-color:initial">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">All true in theory, but this is not how it happens and works in pr=
actice. I prefer being pragmatic. It worked
 reasonably well the way it was before; it's not working well the way it's =
being done now.<o:p></o:p></span></font></p>
</blockquote>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0p=
t">Can you cite an example of an actual problem that has occurred because o=
f this change?<o:p></o:p></span></font></p>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">Sure. I'm travelling this week and had to scramble last night to l=
ook at several -00 drafts that were requested
 to be on the agenda. I had to get on a <st1:time Minute=3D"30" Hour=3D"5" =
w:st=3D"on">
5:30 am</st1:time> call this morning to coordinate the draft agenda with my=
 co-chair due to the impending draft agenda deadline. The result feels a bi=
t rushed with little time to dig into exactly what the issues are in the dr=
afts and hence what to prioritize
 and with how much time allocated.<br>
<br>
Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren't quite sure which group it belon=
ged to, asked for an MMUSIC slot, and it then bounced around between severa=
l WG chairs. By the time we all
 agreed it indeed did belong to DISPATCH, it was all too late because DISPA=
TCH hadn't received an agenda request in time.<o:p></o:p></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">[MB] This one is not a particularly good example in terms of probl=
ems caused by the deadlines. &nbsp;This is an example
 of someone not following the RAI/DISPATCH WG process. &nbsp;It should have=
 been no surprise to the authors that the document should be discussed firs=
t in the DISPATCH WG, as that is our basic process unless it's beyond obvio=
us that it is related specifically to
 an existing chartered WG. &nbsp;In addition, these authors (one of whom is=
 not an inexperienced IETFer) should have been aware of how we were handlin=
g documents of a similar nature as we dispatched several at the last IETF m=
eeting. &nbsp;I think this is an example of
 WG shopping and not of too late deadlines. &nbsp;In particular given that =
the DISPATCH deadline required that notification of intent to submit a docu=
ment and desire to discuss a topic in dispatch was June 24th, with charter =
proposals/problem statements due July
 1st. This document was submitted well over a week after the last deadline.=
 &nbsp;There's nothing wrong with a WG chair flat out saying that a documen=
t wasn't submitted in time to garner enough consideration to warrant agenda=
 time at the f2f meeting. &nbsp;Again, the
 RAI/DISPATCH process allows progression of documents without ever having b=
een discussed at a f2f meeting. &nbsp;We should continue discussion of situ=
ations like this on the RAI area list where there is discussion of process/=
structural issues that are currently
 being encountered:<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt"><a href=3D"http://www.ietf.org/mail-archive/web/rai/current/msg013=
84.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/rai/current=
/msg01384.html</a><o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">It is unfortunate for you (and not at all your fault) that your WG=
 is in the middle of the concerns raised,
 but I think the draft deadlines are the least of your problems.&nbsp;<o:p>=
</o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">[/MB]<o:p></o:p></span></font></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">&nbsp;<o:p></o:p></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt;
border-width:initial;border-color:initial">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0p=
t"><br>
We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.<br>
<br>
Thanks<font color=3D"#888888"><span style=3D"color:#888888"><br>
<br>
-- Flemming<br>
<br>
<br>
<br>
</span></font><o:p></o:p></span></font></p>
</blockquote>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">&nbsp;<o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_949EF20990823C4C85C18D59AA11AD8B06F5C6FR712WXCHMBA11zeu_--

From mary.ietf.barnes@gmail.com  Sun Jul 21 15:30:12 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 91E1921F9A43 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 15:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 3eqIDEHY3i+0 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 15:30:10 -0700 (PDT)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7C97E21F9A1D for <wgchairs@ietf.org>; Sun, 21 Jul 2013 15:30:10 -0700 (PDT)
Received: by mail-qa0-f41.google.com with SMTP id bs12so484492qab.7 for <wgchairs@ietf.org>; Sun, 21 Jul 2013 15:30:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cv/mEn9opiGk9xLXsRcR0AgsMlEkXcFfny0u6tiEDFw=; b=EA1OG9RPCGcEIP5MP6xutZwKELtJxeELbQtD72LcPXP8+cImZ46DBha7LdoVq1aDmi BEeE4PqgkgONzALwhWHaf/fUwOSWVoeC7DdjD/HNCkQcLV7Gml8uvzDQsrpoxsSM5xmL ixnlkGa8VuZwScQ87vm6nEf3GDs50qNp2nC/bfVEs7vCEraDnreNf81QfkAjkgf81KI1 nMr54I+rmIQzlIv28G6YbOCSBUyWGEFfmNcI7sKPsrC4ZyaqL88K4qLFxDVCIam0JLXM 2+1FuZtijhnXCnOIDkitCwReFH18lUv4u726ADfwG4KAlygMv4kiOFbTP/DmBYR/exr9 EZaA==
MIME-Version: 1.0
X-Received: by 10.229.114.209 with SMTP id f17mr6754050qcq.26.1374445808453; Sun, 21 Jul 2013 15:30:08 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Sun, 21 Jul 2013 15:30:08 -0700 (PDT)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06F5C6@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06F5C6@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Date: Sun, 21 Jul 2013 17:30:08 -0500
Message-ID: <CAHBDyN7cYnAvCv0xC2m6qWp=no-fxPUiM7vx3Hmzcqv40ei=7w@mail.gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=00235429d6c42d6be104e20d1a29
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: Sun, 21 Jul 2013 22:30:12 -0000

--00235429d6c42d6be104e20d1a29
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 21, 2013 at 12:55 PM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

> ********
>
> What I am not buying is your contention that confusion does not exist
> because dispatch has different deadlines.****
>
> ** **
>
> I=92d note the words ****
>
> ** **
>
> =93in cases where documents are clearly under the purview for a specific
> WG, then it's not an issue to go directly to the WG=94 ****
>
> ** **
>
> Do not actually appear in the DISPATCH charter =96 which refers generally=
 to
> =93new work=94 without any further clarification. ****
>
> ** **
>
> So we are left having to interpret the overlap between charters of
> existing WG, which presumably have some ownership and DISPATCH.****
>
> ** **
>
> So for discussions that fall in this overlap, the fact that DISPATCH has
> different deadlines adds to the confusion.****
>
> ** **
>
> And I can list a number of documents in the past where the author has
> wavered between DISPATCH and other working groups, and apparently ended u=
p
> going for the wrong working group.
>
[MB] And, that's why if you are uncertain, then bring it to DISPATCH.  It's
also *extremely* useful to follow the naming convention and include
-dispatch - it makes it much easier for the chairs to notice and keep an
eye on new work.

DISPATCH has had different deadlines for 4+ years.  The reason we
implemented DISPATCH is because the SIPPING WG clearly showed us that it is
extremely ineffective to have a kitchen sink WG.  And, WG shopping just
wastes everyone's time, which is what we had ALOT of before we chartered
DISPATCH  We've done quite well with the WGs that we've chartered for
discrete work items.

You are correct that there can be lack of clarity when things *might* look
like SIPCORE or MMUSIC or AVT/EXT, etc.  In those cases, unless you've
talked to the ADs and they've said to take the item to a specific WG, you
should bring it to DISPATCH.   The motivation behind the early deadline is
there is often little value in discussing a draft that is submitted at the
-00 deadline as there is rarely enough time to determine if there is any
interest in the topic.  The whole point was to get away from allocating
agenda time just because someone submitted a draft.  Perhaps you've
forgotten the insanity we had in SIPPING prior to DISPATCH - it was insane.
 We had WG items with 5 minutes of agenda time, we had work items that
totally languished, etc.  If you have better suggestions as to how to
manage the volume of new work that comes into the RAI area, including work
items that overlap WGs, then please post those on the RAI area mailing list
where that discussion has already been started.
[/MB]

> ****
>
> ** **
>
> Keith****
>
> ** **
>   ------------------------------
>
> *From:* Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
> *Sent:* 18 July 2013 20:28
> *To:* DRAGE, Keith (Keith)
> *Cc:* Flemming Andreasen; wgchairs@ietf.org
>
> *Subject:* Re: WG Agendas to submit only 2 days after -00 submission
> cut-off date
> ****
>
>  ** **
>
> On Thu, **Jul 18, 2013** at **2:10 PM**, DRAGE, Keith (Keith) <
> keith.drage@alcatel-lucent.com> wrote:****
>
>  Sorry =96 not buying this.****
>
>  [MB] Then you should raise the issue to the ADs.  I'm the implementer of
> a process that is in place for managing work in their area. [/MB] ****
>
>   ****
>
> Your comment is only applicable if you buy the argument that all new
> proposals, whether in scope or out of scope of another RAI working group,
> go to DISPATCH, and that currently does not appear to be the case. So the=
re
> is the case of a document being submitted, and then some evaluation occur=
s
> that maybe it ought to have been in DISPATCH, after the DISPATCH deadline=
s
> have passed.****
>
>  [MB] As I said previously, in cases where documents are clearly under
> the purview for a specific WG, then it's not an issue to go directly to t=
he
> WG.  BTW, I have no idea what document you're referring to. And, keep in
> mind that the process requires notifying the chairs, so it may not be
> visible to you what discussions might occur offline. [/MB] ****
>
>  Even I am not sure if a document should be in DISPATCH or not. If I read
> follow the DISPATCH charter alone, then there are a number of other items
> on the MMUSIC agenda that have never been dispatched to MMUSIC (or anywhe=
re
> else), and therefore ought to be in DISPATCH. They do fall in scope of th=
e
> MMUSIC agenda. I could point this out in a number of other working groups=
.
> ECRIT even has stuff on the agenda that is not in the scope of ECRIT, has
> never been through DISPATCH and so on.****
>
>  [MB]  I only see one document on the MMUSIC WG agenda that probably
> should have first gone to DISPATCH and actually, the MMUSIC chairs could
> have raised that issue and suggested such to the document authors rather
> than give agenda time when they certainly do have really high priority,
> critical items to discuss.   The document I am referring to relates to at
> least two different WGs (including one that is now closed) and wasn't at
> all an obvious fit for MMUSIC.    In addition, as I said, it should have
> been obvious that there was a fairly clear expectation that  the websocke=
t
> and alternate transport docs are first discussed in  DISPATCH - e.g.,
> BFCPbis, mrsp websocket document, etc.     ****
>
> [/MB]****
>
>   ****
>
> If the deadlines for DISPATCH had not been different, then maybe there
> would have been different issues, but at least it is the different DISPAT=
CH
> deadlines that have currently ruled out the discussion of this document i=
n
> ****Berlin****.****
>
>  [MB] That's absolutely correct - that's the whole intent of the DISPATCH
> deadlines - these authors simply had to send an email to the DISPATCH WG
> chairs by June 24th indicating they were putting together a draft that wa=
s
> an alternative to a previously discussed draft.  They didn't do so.  If
> they had submitted the draft by July 1st, there would have been some
> flexibility, but that wasn't the case.  There were other people that did
> so, that also requested agenda time that were not given agenda time becau=
se
> it wasn't deemed necessary. AGain, you can progress work without discussi=
ng
> at a f2f meeting. ****
>
> ** **
>
>  If you have issues with the DISPATCH process, then please bring those to
> the DISPATCH WG or better yet RAI area mailing list.  We've had this
> process in place for 4 years so the concept of notifying the chairs sever=
al
> weeks before draft deadlines has been there the whole time. Indeed, we ha=
d
> the dates for IETF-87 much later than usual.   Keep in mind as well that
> there is NOTHING in the DISPATCH/RAI process that requires a document to
> have f2f discussion.  Additionally, keep in mind that the document in
> question has normative dependencies such that this document cannot be
> published until those docs are completed. [/MB] ****
>
>   ****
>
> Regards****
>
>  ****
>
> Keith****
>
>  ****
>   ------------------------------
>
> *From:* wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] *On
> Behalf Of *Mary Barnes
> *Sent:* 18 July 2013 19:28
> *To:* Flemming Andreasen****
>
>
> *Cc:* wgchairs@ietf.org
> *Subject:* Re: WG Agendas to submit only 2 days after -00 submission
> cut-off date****
>
>  ****
>
> I have on comment below on an example cited as to the problems with the
> single deadline. ****
>
>  ****
>
> Mary.****
>
>  ****
>
> On Wed, **Jul 17, 2013** at **6:27 PM**, Flemming Andreasen <
> fandreas@cisco.com> wrote:****
>
>
> On **7/17/13** **12:14 AM**, Ted Lemon wrote:****
>
> On **Jul 16, 2013**, at **9:03 PM**, Flemming Andreasen <
> fandreas@cisco.com> wrote:****
>
> You risk a lot of other pushback when you start making up your own
> WG-specific rules (and rightfully so).****
>
> It's hard to understand what you might mean by this.****
>
> When you have a single set of consistent rules that are written down, it'=
s
> easy for everybody to understand and accept. When the rules are WG specif=
ic
> and are created at the discretion of the WG chairs it becomes more of a
> challange:
> 1) Chairs now have the ability to define rules that influence desired
> outcomes (which is not to say they will)
> 2) People may believe that chairs in fact exercise 1), especially when
> things don't go as they like.
>
> Neither is desirable.****
>
>  ****
>
> All true in theory, but this is not how it happens and works in practice.
> I prefer being pragmatic. It worked reasonably well the way it was before=
;
> it's not working well the way it's being done now.****
>
> Can you cite an example of an actual problem that has occurred because of
> this change?****
>
>  Sure. I'm travelling this week and had to scramble last night to look at
> several -00 drafts that were requested to be on the agenda. I had to get =
on
> a ** 5:30 am** call this morning to coordinate the draft agenda with my
> co-chair due to the impending draft agenda deadline. The result feels a b=
it
> rushed with little time to dig into exactly what the issues are in the
> drafts and hence what to prioritize and with how much time allocated.
>
> Another example involves a -00 draft that was submitted a little more tha=
n
> a week ago to DISPATCH. The authors weren't quite sure which group it
> belonged to, asked for an MMUSIC slot, and it then bounced around between
> several WG chairs. By the time we all agreed it indeed did belong to
> DISPATCH, it was all too late because DISPATCH hadn't received an agenda
> request in time.****
>
> [MB] This one is not a particularly good example in terms of problems
> caused by the deadlines.  This is an example of someone not following the
> RAI/DISPATCH WG process.  It should have been no surprise to the authors
> that the document should be discussed first in the DISPATCH WG, as that i=
s
> our basic process unless it's beyond obvious that it is related
> specifically to an existing chartered WG.  In addition, these authors (on=
e
> of whom is not an inexperienced IETFer) should have been aware of how we
> were handling documents of a similar nature as we dispatched several at t=
he
> last IETF meeting.  I think this is an example of WG shopping and not of
> too late deadlines.  In particular given that the DISPATCH deadline
> required that notification of intent to submit a document and desire to
> discuss a topic in dispatch was June 24th, with charter proposals/problem
> statements due July 1st. This document was submitted well over a week aft=
er
> the last deadline.  There's nothing wrong with a WG chair flat out saying
> that a document wasn't submitted in time to garner enough consideration t=
o
> warrant agenda time at the f2f meeting.  Again, the RAI/DISPATCH process
> allows progression of documents without ever having been discussed at a f=
2f
> meeting.  We should continue discussion of situations like this on the RA=
I
> area list where there is discussion of process/structural issues that are
> currently being encountered:****
>
> http://www.ietf.org/mail-archive/web/rai/current/msg01384.html****
>
> It is unfortunate for you (and not at all your fault) that your WG is in
> the middle of the concerns raised, but I think the draft deadlines are th=
e
> least of your problems. ****
>
> [/MB]****
>
>  ****
>
>
> We can all agree that none of this would happen if people submitted their
> drafts earlier. Human nature and work commitments being what they are,
> earlier draft deadlines seem to work a lot better at facilitating that.
>
> Thanks
>
> -- Flemming
>
>
>
> ****
>
>   ****
>
>  ** **
>

--00235429d6c42d6be104e20d1a29
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sun, Jul 21, 2013 at 12:55 PM, DRAGE, Keith (Keith) <span dir=3D=
"ltr">&lt;<a href=3D"mailto:keith.drage@alcatel-lucent.com" target=3D"_blan=
k">keith.drage@alcatel-lucent.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">



<u></u><u></u><u></u><u></u>

<div lang=3D"EN-GB" link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">What I am not buying is your =
contention that confusion does not exist because dispatch has different dea=
dlines.<u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">I=92d note the words
<u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=93</span></font>in cases whe=
re documents are clearly under the purview for a specific WG, then it&#39;s=
 not an issue to go directly to the
 WG=94 <u></u><u></u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Do not actually appear in the=
 DISPATCH charter =96 which refers generally to =93new work=94 without any =
further clarification.
<u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">So we are left having to inte=
rpret the overlap between charters of existing WG, which presumably have so=
me ownership and DISPATCH.<u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">So for discussions that fall =
in this overlap, the fact that DISPATCH has different deadlines adds to the=
 confusion.<u></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">And I can list a number of do=
cuments in the past where the author has wavered between DISPATCH and other=
 working groups, and apparently
 ended up going for the wrong working group.</span></font></p></div></div><=
/blockquote><div>[MB] And, that&#39;s why if you are uncertain, then bring =
it to DISPATCH. =A0It&#39;s also *extremely* useful to follow the naming co=
nvention and include -dispatch - it makes it much easier for the chairs to =
notice and keep an eye on new work. =A0</div>
<div><br></div><div>DISPATCH has had different deadlines for 4+ years. =A0T=
he reason we implemented DISPATCH is because the SIPPING WG clearly showed =
us that it is extremely ineffective to have a kitchen sink WG. =A0And, WG s=
hopping just wastes everyone&#39;s time, which is what we had ALOT of befor=
e we chartered DISPATCH =A0We&#39;ve done quite well with the WGs that we&#=
39;ve chartered for discrete work items. =A0</div>
<div><br></div><div>You are correct that there can be lack of clarity when =
things *might* look like SIPCORE or MMUSIC or AVT/EXT, etc. =A0In those cas=
es, unless you&#39;ve talked to the ADs and they&#39;ve said to take the it=
em to a specific WG, you should bring it to DISPATCH. =A0 The motivation be=
hind the early deadline is there is often little value in discussing a draf=
t that is submitted at the -00 deadline as there is rarely enough time to d=
etermine if there is any interest in the topic. =A0The whole point was to g=
et away from allocating agenda time just because someone submitted a draft.=
 =A0Perhaps you&#39;ve forgotten the insanity we had in SIPPING prior to DI=
SPATCH - it was insane. =A0We had WG items with 5 minutes of agenda time, w=
e had work items that totally languished, etc. =A0If you have better sugges=
tions as to how to manage the volume of new work that comes into the RAI ar=
ea, including work items that overlap WGs, then please post those on the RA=
I area mailing list where that discussion has already been started. =A0</di=
v>
<div>[/MB]</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"=
blue" vlink=3D"blue"><div><p class=3D"MsoNormal"><font color=3D"navy" face=
=3D"Arial"><span style=3D"font-size:10.0pt;font-family:Arial;color:navy"><u=
></u><u></u></span></font></p>

<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Keith<u></u><u></u></span></f=
ont></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy"><u></u>=A0<u></u></span></fon=
t></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></font></div>
<p class=3D"MsoNormal"><b><font face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></fon=
t></b><font face=3D"Tahoma"><span lang=3D"EN-US" style=3D"font-size:10.0pt;=
font-family:Tahoma"> Mary Barnes
 [mailto:<a href=3D"mailto:mary.ietf.barnes@gmail.com" target=3D"_blank">ma=
ry.ietf.barnes@gmail.com</a>] <br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 20:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> DRAGE, Keith (Keith)<br>
<b><span style=3D"font-weight:bold">Cc:</span></b> Flemming Andreasen; <a h=
ref=3D"mailto:wgchairs@ietf.org" target=3D"_blank">wgchairs@ietf.org</a></s=
pan></font></p><div><div class=3D"h5"><font face=3D"Tahoma"><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</font></div></div><span=
 lang=3D"EN-US"><u></u><u></u></span><p></p>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">On Thu,
<u></u>Jul 18, 2013<u></u> at
<u></u>2:10 PM<u></u>, DRAGE, Keith (Keith) &lt;<a href=3D"mailto:keith.dra=
ge@alcatel-lucent.com" target=3D"_blank">keith.drage@alcatel-lucent.com</a>=
&gt; wrote:<u></u><u></u></span></font></p>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Sorry =96 not buying this.</s=
pan></font><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[MB] Then you should raise the issue to the ADs. =A0=
I&#39;m the implementer of a process that is in place for managing work in =
their area. [/MB]=A0<u></u><u></u></span></font></p>

</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><u></u><u></=
u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Your comment is only applicab=
le if you buy the argument that all new proposals,
 whether in scope or out of scope of another RAI working group, go to DISPA=
TCH, and that currently does not appear to be the case. So there is the cas=
e of a document being submitted, and then some evaluation occurs that maybe=
 it ought to have been in DISPATCH,
 after the DISPATCH deadlines have passed.</span></font><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[MB] As I said previously, in cases where documents =
are clearly under the purview for a specific WG, then it&#39;s not an issue=
 to go directly to the WG. =A0BTW, I have no
 idea what document you&#39;re referring to. And, keep in mind that the pro=
cess requires notifying the chairs, so it may not be visible to you what di=
scussions might occur offline. [/MB]</span></font><font color=3D"navy" face=
=3D"Arial"><span style=3D"font-size:10.0pt;font-family:Arial;color:navy">=
=A0</span></font><u></u><u></u></p>

</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Even I am not sure if a docum=
ent should be in DISPATCH or not. If I read follow
 the DISPATCH charter alone, then there are a number of other items on the =
MMUSIC agenda that have never been dispatched to MMUSIC (or anywhere else),=
 and therefore ought to be in DISPATCH. They do fall in scope of the MMUSIC=
 agenda. I could point this out
 in a number of other working groups. ECRIT even has stuff on the agenda th=
at is not in the scope of ECRIT, has never been through DISPATCH and so on.=
</span></font><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[MB] =A0I only see one document on the MMUSIC WG age=
nda that probably should have first gone to DISPATCH and actually, the MMUS=
IC chairs could have raised that issue and
 suggested such to the document authors rather than give agenda time when t=
hey certainly do have really high priority, critical items to discuss. =A0 =
The document I am referring to relates to at least two different WGs (inclu=
ding one that is now closed) and wasn&#39;t
 at all an obvious fit for MMUSIC. =A0 =A0In addition, as I said, it should=
 have been obvious that there was a fairly clear expectation that =A0the we=
bsocket and alternate transport docs are first discussed in =A0DISPATCH - e=
.g., BFCPbis, mrsp websocket document, etc.
 =A0 =A0=A0<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[/MB]<u></u><u></u></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><u></u><u></=
u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">If the deadlines for DISPATCH=
 had not been different, then maybe there would
 have been different issues, but at least it is the different DISPATCH dead=
lines that have currently ruled out the discussion of this document in
<u></u><u></u>Berlin<u></u><u></u>.</span></font><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[MB] That&#39;s absolutely correct - that&#39;s the =
whole intent of the DISPATCH deadlines - these authors simply had to send a=
n email to the DISPATCH WG chairs by June 24th
 indicating they were putting together a draft that was an alternative to a=
 previously discussed draft. =A0They didn&#39;t do so. =A0If they had submi=
tted the draft by July 1st, there would have been some flexibility, but tha=
t wasn&#39;t the case. =A0There were other people
 that did so, that also requested agenda time that were not given agenda ti=
me because it wasn&#39;t deemed necessary. AGain, you can progress work wit=
hout discussing at a f2f meeting.=A0<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0If you have issues with the DISPATCH process, the=
n please bring those to the DISPATCH WG or better yet RAI area mailing list=
. =A0We&#39;ve had this process in place for 4
 years so the concept of notifying the chairs several weeks before draft de=
adlines has been there the whole time. Indeed, we had the dates for IETF-87=
 much later than usual. =A0 Keep in mind as well that there is NOTHING in t=
he DISPATCH/RAI process that requires
 a document to have f2f discussion. =A0Additionally, keep in mind that the =
document in question has normative dependencies such that this document can=
not be published until those docs are completed. [/MB]=A0<u></u><u></u></sp=
an></font></p>

</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link=3D"blue" vlink=3D"blue">
<div>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><u></u><u></=
u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Regards</span></font><u></u><=
u></u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><u></u><u></=
u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">Keith</span></font><u></u><u>=
</u></p>
<p class=3D"MsoNormal"><font color=3D"navy" face=3D"Arial"><span style=3D"f=
ont-size:10.0pt;font-family:Arial;color:navy">=A0</span></font><u></u><u></=
u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt;border-width:initial;border-color:initial">
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span lang=3D"EN-US" style=3D"font-siz=
e:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></font></div>
<p class=3D"MsoNormal"><b><font face=3D"Tahoma"><span lang=3D"EN-US" style=
=3D"font-size:10.0pt;font-family:Tahoma;font-weight:bold">From:</span></fon=
t></b><font face=3D"Tahoma"><span lang=3D"EN-US" style=3D"font-size:10.0pt;=
font-family:Tahoma">
<a href=3D"mailto:wgchairs-bounces@ietf.org" target=3D"_blank">wgchairs-bou=
nces@ietf.org</a> [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org" targ=
et=3D"_blank">wgchairs-bounces@ietf.org</a>]
<b><span style=3D"font-weight:bold">On Behalf Of </span></b>Mary Barnes<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> 18 July 2013 19:28<br>
<b><span style=3D"font-weight:bold">To:</span></b> Flemming Andreasen</span=
></font><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Tahoma"><span style=3D"font=
-size:12.0pt;font-family:Tahoma"><br>
<b><span style=3D"font-weight:bold">Cc:</span></b> <a href=3D"mailto:wgchai=
rs@ietf.org" target=3D"_blank">
wgchairs@ietf.org</a><br>
<b><span style=3D"font-weight:bold">Subject:</span></b> Re: WG Agendas to s=
ubmit only 2 days after -00 submission cut-off date</span></font><u></u><u>=
</u></p>
</div>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">I have on comment below on an example cited as to th=
e problems with the single deadline.=A0<u></u><u></u></span></font></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Mary.<u></u><u></u></span></font></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt">=A0<u></u><u></u></sp=
an></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">On Wed,
<u></u>Jul 17, 2013<u></u> at
<u></u>6:27 PM<u></u>, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@ci=
sco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<u></u><u></u><=
/span></font></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><br>
On <u></u>7/17/13<u></u>
<u></u>12:14 AM<u></u>, Ted Lemon wrote:<u></u><u></u></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">On
<u></u>Jul 16, 2013<u></u>, at
<u></u>9:03 PM<u></u>, Flemming Andreasen &lt;<a href=3D"mailto:fandreas@ci=
sco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<u></u><u></u><=
/span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">You risk a lot of other pushback when you start maki=
ng up your own WG-specific rules (and rightfully so).<u></u><u></u></span><=
/font></p>

<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">It&#39;s hard to understand what you might mean by t=
his.<u></u><u></u></span></font></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">When you have a single set of consistent rules that =
are written down, it&#39;s easy for everybody to understand
 and accept. When the rules are WG specific and are created at the discreti=
on of the WG chairs it becomes more of a challange:<br>
1) Chairs now have the ability to define rules that influence desired outco=
mes (which is not to say they will)<br>
2) People may believe that chairs in fact exercise 1), especially when thin=
gs don&#39;t go as they like.<br>
<br>
Neither is desirable.<u></u><u></u></span></font></p>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt;border-width:initial;border-color:initial">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt;border-width:initial;border-color:initial">
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">All true in theory, but this is not how it happens a=
nd works in practice. I prefer being pragmatic. It worked
 reasonably well the way it was before; it&#39;s not working well the way i=
t&#39;s being done now.<u></u><u></u></span></font></p>
</blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt">Can you cite an examp=
le of an actual problem that has occurred because of this change?<u></u><u>=
</u></span></font></p>

</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">Sure. I&#39;m travelling this week and had to scramb=
le last night to look at several -00 drafts that were requested
 to be on the agenda. I had to get on a <u></u>
5:30 am<u></u> call this morning to coordinate the draft agenda with my co-=
chair due to the impending draft agenda deadline. The result feels a bit ru=
shed with little time to dig into exactly what the issues are in the drafts=
 and hence what to prioritize
 and with how much time allocated.<br>
<br>
Another example involves a -00 draft that was submitted a little more than =
a week ago to DISPATCH. The authors weren&#39;t quite sure which group it b=
elonged to, asked for an MMUSIC slot, and it then bounced around between se=
veral WG chairs. By the time we all
 agreed it indeed did belong to DISPATCH, it was all too late because DISPA=
TCH hadn&#39;t received an agenda request in time.<u></u><u></u></span></fo=
nt></p>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[MB] This one is not a particularly good example in =
terms of problems caused by the deadlines. =A0This is an example
 of someone not following the RAI/DISPATCH WG process. =A0It should have be=
en no surprise to the authors that the document should be discussed first i=
n the DISPATCH WG, as that is our basic process unless it&#39;s beyond obvi=
ous that it is related specifically to
 an existing chartered WG. =A0In addition, these authors (one of whom is no=
t an inexperienced IETFer) should have been aware of how we were handling d=
ocuments of a similar nature as we dispatched several at the last IETF meet=
ing. =A0I think this is an example of
 WG shopping and not of too late deadlines. =A0In particular given that the=
 DISPATCH deadline required that notification of intent to submit a documen=
t and desire to discuss a topic in dispatch was June 24th, with charter pro=
posals/problem statements due July
 1st. This document was submitted well over a week after the last deadline.=
 =A0There&#39;s nothing wrong with a WG chair flat out saying that a docume=
nt wasn&#39;t submitted in time to garner enough consideration to warrant a=
genda time at the f2f meeting. =A0Again, the
 RAI/DISPATCH process allows progression of documents without ever having b=
een discussed at a f2f meeting. =A0We should continue discussion of situati=
ons like this on the RAI area list where there is discussion of process/str=
uctural issues that are currently
 being encountered:<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><a href=3D"http://www.ietf.org/mail-archive/web/rai/=
current/msg01384.html" target=3D"_blank">http://www.ietf.org/mail-archive/w=
eb/rai/current/msg01384.html</a><u></u><u></u></span></font></p>

</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">It is unfortunate for you (and not at all your fault=
) that your WG is in the middle of the concerns raised,
 but I think the draft deadlines are the least of your problems.=A0<u></u><=
u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">[/MB]<u></u><u></u></span></font></p>
</div>
<div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt;border-width:initial;border-color:initial">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><font size=3D"3" face=
=3D"Times New Roman"><span style=3D"font-size:12.0pt"><br>
We can all agree that none of this would happen if people submitted their d=
rafts earlier. Human nature and work commitments being what they are, earli=
er draft deadlines seem to work a lot better at facilitating that.<br>

<br>
Thanks<font color=3D"#888888"><span style=3D"color:#888888"><br>
<br>
-- Flemming<br>
<br>
<br>
<br>
</span></font><u></u><u></u></span></font></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt">=A0<u></u><u></u></span></font></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:12.0pt"><u></u>=A0<u></u></span></font></p>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div></div>

--00235429d6c42d6be104e20d1a29--

From dcrocker@bbiw.net  Sun Jul 21 23:27:09 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 AD06521E8064 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 23:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 wk5gkZlJKRW5 for <wgchairs@ietfa.amsl.com>; Sun, 21 Jul 2013 23:27:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1AC21F9F50 for <wgchairs@ietf.org>; Sun, 21 Jul 2013 23:27:03 -0700 (PDT)
Received: from [192.168.0.83] (host-212-159-176-45.static.as13285.net [212.159.176.45]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6M6QIxS010932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 21 Jul 2013 23:26:23 -0700
Message-ID: <51ECD088.5090903@bbiw.net>
Date: Mon, 22 Jul 2013 07:26:16 +0100
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: Draft submission deadline/moratorium tool proposal
References: <51E9735B.9030103@qti.qualcomm.com> <949EF20990823C4C85C18D59AA11AD8B06DD37@FR712WXCHMBA11.zeu.alcatel-lucent.com> <51EAA7EE.4080508@bbiw.net> <949EF20990823C4C85C18D59AA11AD8B06F550@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B06F550@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]); Sun, 21 Jul 2013 23:26:24 -0700 (PDT)
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Mon, 22 Jul 2013 06:27:09 -0000

On 7/21/2013 6:01 PM, DRAGE, Keith (Keith) wrote:
> You seem to be assuming that WG chairs have lots of spare time in
> order to do this.

No.  I'm assuming that it is reasonable to expect chairs to manage their
groups and that the tasks of management have some substance.


> At least in the RAI area, we are short of chairs, and many of the
> existing ones have many other commitments.

The ability to recruit a reasonable array of participants -- including 
those who will do working group management, document writing, 
shepherding, etc, is a de facto filter on whether the work has enough 
community interest to justify pursuit in the IETF.

So you are citing a problem that is far more basic, and far more 
serious, than the current issue.



> Any tools that handle things automatically save the WG chair devoting
> cycles.
>
> The -00 and -xx deadlines at least made sure (in a very heavy handed
> manner) that all documents to be considered for the meeting where
> much more easily identified, without constant prompting from the
> chairs.

A working group that has so many documents active at one time that it is 
difficult to keep track of them probably has deeper management problems 
than we are talking about here.

In any event, the idea that a Procrustean rule is justified because it 
makes the life of a wg chair easier -- rather than because it's needed 
and appropriate in its own right -- ought to bother us,

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From lee.howard@twcable.com  Mon Jul 22 04:58:04 2013
Return-Path: <lee.howard@twcable.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 95DCA21E8056 for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 04:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.296
X-Spam-Level: 
X-Spam-Status: No, score=-1.296 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YtdU8W1rT7zO for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 04:57:59 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB7721E8064 for <wgchairs@ietf.org>; Mon, 22 Jul 2013 04:57:55 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,719,1367985600"; d="scan'208";a="111055296"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Jul 2013 07:56:53 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 22 Jul 2013 07:57:54 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Dave Crocker <dcrocker@bbiw.net>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Date: Mon, 22 Jul 2013 07:57:55 -0400
Subject: Re: Draft submission deadline/moratorium tool proposal
Thread-Topic: Draft submission deadline/moratorium tool proposal
Thread-Index: Ac6G0rKb83DTkJt7SB6A14c3pwoBJQ==
Message-ID: <CE1291DF.2E8B0%lee.howard@twcable.com>
In-Reply-To: <51ECD088.5090903@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.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: Mon, 22 Jul 2013 11:58:04 -0000

On 7/22/13 2:26 AM, "Dave Crocker" <dcrocker@bbiw.net> wrote:

>
>> At least in the RAI area, we are short of chairs, and many of the
>> existing ones have many other commitments.
>
>The ability to recruit a reasonable array of participants -- including
>those who will do working group management, document writing,
>shepherding, etc, is a de facto filter on whether the work has enough
>community interest to justify pursuit in the IETF.

Two separate points here:
1) We only want volunteer managers (WG chairs, ADs, etc.) who aren't busy.
2) We only support work undertaken by people who aren't busy.
I agree that this is currently the intake filter.  I believe this to be a
flaw.
"Busy" can include fixing outages, preparing budgets by deadline, being on
summer vacation, or anything else that is time-sensitive in the weeks
before an IETF meeting.  I think we need to find ways to make the IETF
accessible to busy people, and that busy people can be the best
contributors--including management roles, if we can find ways to
accommodate them.

>>The -00 and -xx deadlines at least made sure (in a very heavy handed
>> manner) that all documents to be considered for the meeting where
>> much more easily identified, without constant prompting from the
>> chairs.
>
>A working group that has so many documents active at one time that it is
>difficult to keep track of them probably has deeper management problems
>than we are talking about here.

"Active" can mean a great many things; I don't think WG agendas are, or
should be, limited to documents already adopted by the WG.  The fact that
many people have something to say on a topic is a sign of health, and
potentially a sign of a need to recharter.  The participants in the WG
need to review the documents and decide by consensus on whether WG
time--that is, mailing list threads and meeting discussion time--should be
spent working on each one.


>In any event, the idea that a Procrustean rule is justified because it
>makes the life of a wg chair easier -- rather than because it's needed
>and appropriate in its own right -- ought to bother us,

Agreed--we should adopt rules that keep barriers to participation low;
that is, make it easy for knowledgeable people to participate.  For me,
that means agendas need to be posted well enough in advance that
participants have time to read the drafts (for all of the WGs in which
they participate), and drafts need to be posted well enough in advance
that chairs know which ones to include in the agenda (preferably, based on
list discussion).

Lee


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From ogud@ogud.com  Mon Jul 22 07:59:00 2013
Return-Path: <ogud@ogud.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 DAD1E11E8118 for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 07:59:00 -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 HqsKWeq2uFNg for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 07:58:55 -0700 (PDT)
Received: from smtp93.ord1c.emailsrvr.com (smtp93.ord1c.emailsrvr.com [108.166.43.93]) by ietfa.amsl.com (Postfix) with ESMTP id CE28421F9E28 for <wgchairs@ietf.org>; Mon, 22 Jul 2013 07:58:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4AE63140131; Mon, 22 Jul 2013 10:58:55 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 096A1140260;  Mon, 22 Jul 2013 10:58:54 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Draft submission deadline/moratorium tool proposal
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <51E9735B.9030103@qti.qualcomm.com>
Date: Mon, 22 Jul 2013 10:58:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBF75F94-36E3-4ECA-AA3D-F2B0461750D4@ogud.com>
References: <51E9735B.9030103@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
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: Mon, 22 Jul 2013 14:59:01 -0000

Pete,=20
Sorry for the top post, I read all the replies and thought about my =
experiences as WG chair.=20

Having a publication deadline is a good thing, thus I do not support in =
general to get rid of that=20
there are few exceptions to this general rule, on the other hand I =
support the hold feature of submitted drafts=20
in the week before the meeting and that all of them are released at the =
beginning of the meeting with one exception.=20
	Documents that are in IESG review should be updatable at any =
time if AD and/or Chair approves, this is
	critical around the spring meeting when WG are fighting the =
deadline of AD leaving the IESG and avoiding having
	the "new" IESG reviewing the document(s) again.=20

In short my proposal is document cutoff 2 weeks before meeting, =
documents can be submitted after that but held until 03:00 on=20
Monday/Tuesday meeting local time.=20

The only exception is that documents in following states can be posted =
if AD and/or Chair approves:=20
	IESG Evaluation=20
	AD Followup
	Point Raised=20

	Olafur



On Jul 19, 2013, at 1:11 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Given the talk over the last week, I'd like to make a proposal. I have =
suggested something like this before. If the chairs generally think this =
is a good idea, then maybe we take it to the IETF list. (I have not =
passed this by other ADs; they can pipe up as they see fit.)
>=20
> Proposal for draft submission deadline/moratorium:
>=20
> 1. The draft submission tool never shuts down. Everyone is *always* =
allowed to submit drafts to the tool. However, they are not always =
posted.
>=20
> 2. For X weeks before an IETF plenary meeting and during the week of =
the meeting, all submitted drafts are queued but not posted. The draft =
deadline is announced as X weeks. (I personally don't care what X is; =
suggestions welcome.)
>=20
> 3. Queued WG drafts can be approved for posting by an AD or the =
chair(s) of that WG.
>=20
> 4. Queued individual submission drafts can be approved for posting by =
an AD.
>=20
> 5. At the completion of the IETF meeting, all queued drafts are =
released from the queue.
>=20
> (Other features that might be desirable, but I'm not sure about)
>=20
> 6a. Drafts that are in IESG-Evaluation are not queued.
> ...or...
> 6b. Drafts that are in IESG-Evaluation are always queued, regardless =
of moratorium. An AD must release them.
>=20
> 7. Chairs can pre-approve draft posting during the moratorium, just as =
they do for -00 drafts.
>=20
> 8. Chairs can put a moratorium on a particular WG (for instance, =
before an interim meeting).
>=20
> Thoughts?
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From fandreas@cisco.com  Mon Jul 22 08:34:18 2013
Return-Path: <fandreas@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 3DF3011E80EF for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 08:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.284
X-Spam-Level: 
X-Spam-Status: No, score=-10.284 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id di6BRW+omC6N for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 08:34:13 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id DAE5C21F9DFA for <wgchairs@ietf.org>; Mon, 22 Jul 2013 08:34:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10529; q=dns/txt; s=iport; t=1374507253; x=1375716853; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=jzHJpvY3mMRIrA2lo5TSKGqSKYVgM+GBC6vDim3qbzY=; b=lG4Cb4LhQy4TRs2F3OXcQj8/zrHNSr+3YA4vtXfGxq3TElA9WXnHxVq6 HycSKf9qSJbtbOw0njyhGs5BUd79C2zRvQrVqYmbgoOpcKz1CNBL2Cs3N Ji8q30x/Il9fQHiKhhR32u+9OPemJIHuOr5bVv3GzG+z/AT+jgPGhT+hC Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQFAEZQ7VGtJV2c/2dsb2JhbABagkJEiWy3SYEWFnSCJAEBAQMBbgoBBQsLGAkWCAcJAwIBAgE0EQYNAQUCAQGIBga3f45UgUIHg34Dl12RTYMuIIE1
X-IronPort-AV: E=Sophos;i="4.89,720,1367971200";  d="scan'208,217";a="237871594"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 22 Jul 2013 15:34:12 +0000
Received: from rtp-fandreas-8715.cisco.com (rtp-fandreas-8715.cisco.com [10.117.7.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6MFYBk1006809;  Mon, 22 Jul 2013 15:34:11 GMT
Message-ID: <51ED50F3.4030302@cisco.com>
Date: Mon, 22 Jul 2013 11:34:11 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com>
In-Reply-To: <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080502060409030004000609"
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: Mon, 22 Jul 2013 15:34:18 -0000

This is a multi-part message in MIME format.
--------------080502060409030004000609
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit


On 7/18/13 3:28 PM, Mary Barnes wrote:
> On Thu, Jul 18, 2013 at 2:10 PM, DRAGE, Keith (Keith) 
> <keith.drage@alcatel-lucent.com 
> <mailto:keith.drage@alcatel-lucent.com>> wrote:
>
>     Even I am not sure if a document should be in DISPATCH or not. If
>     I read follow the DISPATCH charter alone, then there are a number
>     of other items on the MMUSIC agenda that have never been
>     dispatched to MMUSIC (or anywhere else), and therefore ought to be
>     in DISPATCH. They do fall in scope of the MMUSIC agenda. I could
>     point this out in a number of other working groups. ECRIT even has
>     stuff on the agenda that is not in the scope of ECRIT, has never
>     been through DISPATCH and so on.
>
> [MB]  I only see one document on the MMUSIC WG agenda that probably 
> should have first gone to DISPATCH and actually, the MMUSIC chairs 
> could have raised that issue and suggested such to the document 
> authors rather than give agenda time when they certainly do have 
> really high priority, critical items to discuss.   The document I am 
> referring to relates to at least two different WGs (including one that 
> is now closed) and wasn't at all an obvious fit for MMUSIC.    In 
> addition, as I said, it should have been obvious that there was a 
> fairly clear expectation that  the websocket and alternate transport 
> docs are first discussed in  DISPATCH - e.g., BFCPbis, mrsp websocket 
> document, etc.
> [/MB]
The MMUSIC agenda is a draft agenda at this point. If you have concerns 
with it, please raise those on the MMUSIC mailing list.

>     If the deadlines for DISPATCH had not been different, then maybe
>     there would have been different issues, but at least it is the
>     different DISPATCH deadlines that have currently ruled out the
>     discussion of this document in Berlin.
>
> [MB] That's absolutely correct - that's the whole intent of the 
> DISPATCH deadlines - these authors simply had to send an email to the 
> DISPATCH WG chairs by June 24th indicating they were putting together 
> a draft that was an alternative to a previously discussed draft.  They 
> didn't do so.  If they had submitted the draft by July 1st, there 
> would have been some flexibility, but that wasn't the case.  There 
> were other people that did so, that also requested agenda time that 
> were not given agenda time because it wasn't deemed necessary. AGain, 
> you can progress work without discussing at a f2f meeting.
>
>  If you have issues with the DISPATCH process, then please bring those 
> to the DISPATCH WG or better yet RAI area mailing list.  We've had 
> this process in place for 4 years so the concept of notifying the 
> chairs several weeks before draft deadlines has been there the whole 
> time. Indeed, we had the dates for IETF-87 much later than usual.   
> Keep in mind as well that there is NOTHING in the DISPATCH/RAI process 
> that requires a document to have f2f discussion.  Additionally, keep 
> in mind that the document in question has normative dependencies such 
> that this document cannot be published until those docs are completed. 
> [/MB]
The different points raised in this thread only reaffirms my view that 
having a single set of consistent procedures shared by the WGs would be 
useful. I also understand this view is not shared by all, so belaboring 
the point is probably not going to be productive.

Thanks

-- Flemming



--------------080502060409030004000609
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 7/18/13 3:28 PM, Mary Barnes wrote:<br>
    </div>
    <blockquote
cite="mid:CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">
        <div class="gmail_extra">On Thu, Jul 18, 2013 at 2:10 PM, DRAGE,
          Keith (Keith) <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:keith.drage@alcatel-lucent.com"
              target="_blank">keith.drage@alcatel-lucent.com</a>&gt;</span>
          wrote:<br>
          <div class="gmail_quote"><br>
            <blockquote class="gmail_quote"
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div link="blue" vlink="blue" lang="EN-GB">
                <div>
                  <p class=""><font color="navy" face="Arial"><span
                        style="font-size:10pt;font-family:Arial;color:navy">Even
                        I am not sure if a document should be in
                        DISPATCH or not. If I read follow the DISPATCH
                        charter alone, then there are a number of other
                        items on the MMUSIC agenda that have never been
                        dispatched to MMUSIC (or anywhere else), and
                        therefore ought to be in DISPATCH. They do fall
                        in scope of the MMUSIC agenda. I could point
                        this out in a number of other working groups.
                        ECRIT even has stuff on the agenda that is not
                        in the scope of ECRIT, has never been through
                        DISPATCH and so on.</span></font></p>
                </div>
              </div>
            </blockquote>
            <div>[MB]  I only see one document on the MMUSIC WG agenda
              that probably should have first gone to DISPATCH and
              actually, the MMUSIC chairs could have raised that issue
              and suggested such to the document authors rather than
              give agenda time when they certainly do have really high
              priority, critical items to discuss.   The document I am
              referring to relates to at least two different WGs
              (including one that is now closed) and wasn't at all an
              obvious fit for MMUSIC.    In addition, as I said, it
              should have been obvious that there was a fairly clear
              expectation that  the websocket and alternate transport
              docs are first discussed in  DISPATCH - e.g., BFCPbis,
              mrsp websocket document, etc.     </div>
            <div>[/MB]</div>
          </div>
        </div>
      </div>
    </blockquote>
    The MMUSIC agenda is a draft agenda at this point. If you have
    concerns with it, please raise those on the MMUSIC mailing list. <br>
    <br>
    <blockquote
cite="mid:CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote"
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div link="blue" vlink="blue" lang="EN-GB">
                <div>
                  <p class=""><font color="navy" face="Arial"><span
                        style="font-size:10pt;font-family:Arial;color:navy"> </span></font></p>
                  <p class=""><font color="navy" face="Arial"><span
                        style="font-size:10pt;font-family:Arial;color:navy">If
                        the deadlines for DISPATCH had not been
                        different, then maybe there would have been
                        different issues, but at least it is the
                        different DISPATCH deadlines that have currently
                        ruled out the discussion of this document in
                        Berlin.</span></font></p>
                </div>
              </div>
            </blockquote>
            <div>[MB] That's absolutely correct - that's the whole
              intent of the DISPATCH deadlines - these authors simply
              had to send an email to the DISPATCH WG chairs by June
              24th indicating they were putting together a draft that
              was an alternative to a previously discussed draft.  They
              didn't do so.  If they had submitted the draft by July
              1st, there would have been some flexibility, but that
              wasn't the case.  There were other people that did so,
              that also requested agenda time that were not given agenda
              time because it wasn't deemed necessary. AGain, you can
              progress work without discussing at a f2f meeting. </div>
            <div><br>
            </div>
            <div> If you have issues with the DISPATCH process, then
              please bring those to the DISPATCH WG or better yet RAI
              area mailing list.  We've had this process in place for 4
              years so the concept of notifying the chairs several weeks
              before draft deadlines has been there the whole time.
              Indeed, we had the dates for IETF-87 much later than
              usual.   Keep in mind as well that there is NOTHING in the
              DISPATCH/RAI process that requires a document to have f2f
              discussion.  Additionally, keep in mind that the document
              in question has normative dependencies such that this
              document cannot be published until those docs are
              completed. [/MB] <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    The different points raised in this thread only reaffirms my view
    that having a single set of consistent procedures shared by the WGs
    would be useful. I also understand this view is not shared by all,
    so belaboring the point is probably not going to be productive. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <br>
  </body>
</html>

--------------080502060409030004000609--

From mary.ietf.barnes@gmail.com  Mon Jul 22 09:06:41 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 5220411E8118 for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 09:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, 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 xMw7mbcKh5cI for <wgchairs@ietfa.amsl.com>; Mon, 22 Jul 2013 09:06:40 -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 6D27611E80F6 for <wgchairs@ietf.org>; Mon, 22 Jul 2013 09:06:37 -0700 (PDT)
Received: by mail-qe0-f54.google.com with SMTP id 1so643247qee.13 for <wgchairs@ietf.org>; Mon, 22 Jul 2013 09:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6BRxRCUincQ/QUQk66lV9+lqpqvLt7eRgW4kDzK+AHk=; b=NimjelXjt/IBbWUmhiQho9mNGg0yCH6Qhl6fUbuuqvfP3GBYkId0eJJiHT/k5vkX4e uXjECEvgK8GPJMBzojXAGzSXs/uk7yH+3F2ApD8xkmudfnjjyp+pKDCUeWaQGb21Qtrm OEdCz4zeGjYEchsYpp6xO3Rq8JHbvA5ds+/Nm4/hlM1CiTIU0evFihPJdNo6I+lVPRcR eoWtK3n9XGsTeaRjx51lpNc2p+IeM9/aPa1q2TJoFv6sHausGwb9P28V4MrwJWXTHNQX 26/c7vFwow+YgknvvBg8KBVOCpU9k4ckCXMwjJgUtp67/hZaOM13oe3T7ByxCI0cxGiZ 7m5A==
MIME-Version: 1.0
X-Received: by 10.224.12.81 with SMTP id w17mr6301432qaw.37.1374509196850; Mon, 22 Jul 2013 09:06:36 -0700 (PDT)
Received: by 10.49.76.167 with HTTP; Mon, 22 Jul 2013 09:06:36 -0700 (PDT)
In-Reply-To: <51ED50F3.4030302@cisco.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <CAHBDyN7OF7qyK2Ne2hV_O8NiqRiC0QK-3HMUTjg1EH=Ff1ptpQ@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B06CF91@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAHBDyN56L+nyjot-P_DN71hqh6ryuemDdmLE8NDjLCRJaDrNbQ@mail.gmail.com> <51ED50F3.4030302@cisco.com>
Date: Mon, 22 Jul 2013 11:06:36 -0500
Message-ID: <CAHBDyN5m+Q9G-pLfsVwi1baFDgMp6P6EYZsh-EY288B0iZ8A7A@mail.gmail.com>
Subject: Re: WG Agendas to submit only 2 days after -00 submission cut-off date
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary=089e013cb7cc6b3eb204e21bdca0
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: Mon, 22 Jul 2013 16:06:41 -0000

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

On Mon, Jul 22, 2013 at 10:34 AM, Flemming Andreasen <fandreas@cisco.com>wrote:

>
> On 7/18/13 3:28 PM, Mary Barnes wrote:
>
>  On Thu, Jul 18, 2013 at 2:10 PM, DRAGE, Keith (Keith) <
> keith.drage@alcatel-lucent.com> wrote:
>
>   Even I am not sure if a document should be in DISPATCH or not. If I
>> read follow the DISPATCH charter alone, then there are a number of other
>> items on the MMUSIC agenda that have never been dispatched to MMUSIC (or
>> anywhere else), and therefore ought to be in DISPATCH. They do fall in
>> scope of the MMUSIC agenda. I could point this out in a number of other
>> working groups. ECRIT even has stuff on the agenda that is not in the scope
>> of ECRIT, has never been through DISPATCH and so on.
>>
> [MB]  I only see one document on the MMUSIC WG agenda that probably should
> have first gone to DISPATCH and actually, the MMUSIC chairs could have
> raised that issue and suggested such to the document authors rather than
> give agenda time when they certainly do have really high priority, critical
> items to discuss.   The document I am referring to relates to at least two
> different WGs (including one that is now closed) and wasn't at all an
> obvious fit for MMUSIC.    In addition, as I said, it should have been
> obvious that there was a fairly clear expectation that  the websocket and
> alternate transport docs are first discussed in  DISPATCH - e.g., BFCPbis,
> mrsp websocket document, etc.
> [/MB]
>
> The MMUSIC agenda is a draft agenda at this point. If you have concerns
> with it, please raise those on the MMUSIC mailing list.
>
[MB] My point was not a criticism of your agenda.  My point was that there
was a request to the MMUSIC WG to discuss a document that really should
first be dealt with in DISPATCH WG (per the RAI process) - that's what
Keith was using as the reason why we all need the same deadlines.  I think
it would have been a bad idea to give that document agenda time, as I noted
MMUSIC WG has a lot of higher priority work (I don't think anyone will
debate that point).  I see that your current agenda is geared towards the
latter, with documents that aren't high priority noted as "time allows".
That's good. [/MB]

>
>
>>
>> If the deadlines for DISPATCH had not been different, then maybe there
>> would have been different issues, but at least it is the different DISPATCH
>> deadlines that have currently ruled out the discussion of this document in
>> Berlin.
>>
> [MB] That's absolutely correct - that's the whole intent of the DISPATCH
> deadlines - these authors simply had to send an email to the DISPATCH WG
> chairs by June 24th indicating they were putting together a draft that was
> an alternative to a previously discussed draft.  They didn't do so.  If
> they had submitted the draft by July 1st, there would have been some
> flexibility, but that wasn't the case.  There were other people that did
> so, that also requested agenda time that were not given agenda time because
> it wasn't deemed necessary. AGain, you can progress work without discussing
> at a f2f meeting.
>
>   If you have issues with the DISPATCH process, then please bring those
> to the DISPATCH WG or better yet RAI area mailing list.  We've had this
> process in place for 4 years so the concept of notifying the chairs several
> weeks before draft deadlines has been there the whole time. Indeed, we had
> the dates for IETF-87 much later than usual.   Keep in mind as well that
> there is NOTHING in the DISPATCH/RAI process that requires a document to
> have f2f discussion.  Additionally, keep in mind that the document in
> question has normative dependencies such that this document cannot be
> published until those docs are completed. [/MB]
>
> The different points raised in this thread only reaffirms my view that
> having a single set of consistent procedures shared by the WGs would be
> useful. I also understand this view is not shared by all, so belaboring the
> point is probably not going to be productive.
>

[MB] The specific points I am raising about deadlines with regards to
DISPATCH is the RAI process for new work that we implemented over 4+ years
ago.  I think aligning the issues one sees with the deadlines set by the
RAI process with this thread of document deadlines in general is a red
herring. As I noted, there is a discussion with regards to the RAI process
overall, including how to handle WGs that have very tight coupling.  I
don't think the deadlines have any relation whatsoever to the issues around
the latter point and should be discussed on the RAI area list.

As to my opinion with regards to the general idea that we need a rigid
process defining deadlines that all the WGs apply across all areas use,  I
don't think that solves any real problems with managing work in WGs.  If
folks can't follow a mailing list close enough to know the expectations of
chairs in terms of deadlines for planning their meetings (or progressing
work in general), then as others have noted, the WG has a much bigger
problem than draft deadlines.  Chairs have always been able to make
exceptions for documents that miss the deadlines.  There are good reasons
why this happens sometimes, I think the process needs to remain flexible
enough for chairs to deal with that.  If WG members don't tolerate any
changes in concepts or problems to be solved for 2-3 weeks before the
meetings, then we end up with 6-9 weeks of the year (about 2 months) where
we limit progress.  As a chair, I have allowed discussion of drafts (even
individual ones) that missed the deadline in cases where the document
updates where significant enough that it could help with WG progress.  Yes,
people did complain, but again I believe WG chairs must have flexibility in
how they manage their WGs.    [/MB]

>
> Thanks
>
> -- Flemming
>
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jul 22, 2013 at 10:34 AM, Flemming Andreasen <span dir=3D"l=
tr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@ci=
sco.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">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    <br>
    <div>On 7/18/13 3:28 PM, Mary Barnes wrote:<br>
    </div>
    </div><blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div class=3D"gmail_extra"><div class=3D"im">On Thu, Jul 18, 2013 a=
t 2:10 PM, 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><div class=3D"im"><div class=3D"gmail_quote"><br>
            <blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margi=
n-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div link=3D"blue" vlink=3D"blue" lang=3D"EN-GB">
                <div>
                  <p><font color=3D"navy" face=3D"Arial"><span style=3D"fon=
t-size:10pt;font-family:Arial;color:navy">Even
                        I am not sure if a document should be in
                        DISPATCH or not. If I read follow the DISPATCH
                        charter alone, then there are a number of other
                        items on the MMUSIC agenda that have never been
                        dispatched to MMUSIC (or anywhere else), and
                        therefore ought to be in DISPATCH. They do fall
                        in scope of the MMUSIC agenda. I could point
                        this out in a number of other working groups.
                        ECRIT even has stuff on the agenda that is not
                        in the scope of ECRIT, has never been through
                        DISPATCH and so on.</span></font></p>
                </div>
              </div>
            </blockquote>
            <div>[MB] =A0I only see one document on the MMUSIC WG agenda
              that probably should have first gone to DISPATCH and
              actually, the MMUSIC chairs could have raised that issue
              and suggested such to the document authors rather than
              give agenda time when they certainly do have really high
              priority, critical items to discuss. =A0 The document I am
              referring to relates to at least two different WGs
              (including one that is now closed) and wasn&#39;t at all an
              obvious fit for MMUSIC. =A0 =A0In addition, as I said, it
              should have been obvious that there was a fairly clear
              expectation that =A0the websocket and alternate transport
              docs are first discussed in =A0DISPATCH - e.g., BFCPbis,
              mrsp websocket document, etc. =A0 =A0=A0</div>
            <div>[/MB]</div>
          </div>
        </div></div>
      </div>
    </blockquote>
    The MMUSIC agenda is a draft agenda at this point. If you have
    concerns with it, please raise those on the MMUSIC mailing list. <br></=
div></blockquote><div>[MB] My point was not a criticism of your agenda. =A0=
My point was that there was a request to the MMUSIC WG to discuss a documen=
t that really should first be dealt with in DISPATCH WG (per the RAI proces=
s) - that&#39;s what Keith was using as the reason why we all need the same=
 deadlines. =A0I think it would have been a bad idea to give that document =
agenda time, as I noted MMUSIC WG has a lot of higher priority work (I don&=
#39;t think anyone will debate that point). =A0I see that your current agen=
da is geared towards the latter, with documents that aren&#39;t high priori=
ty noted as &quot;time allows&quot;. That&#39;s good. [/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000"><d=
iv class=3D"im">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margi=
n-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;borde=
r-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div link=3D"blue" vlink=3D"blue" lang=3D"EN-GB">
                <div>
                  <p><font color=3D"navy" face=3D"Arial"><span style=3D"fon=
t-size:10pt;font-family:Arial;color:navy">=A0</span></font></p>
                  <p><font color=3D"navy" face=3D"Arial"><span style=3D"fon=
t-size:10pt;font-family:Arial;color:navy">If
                        the deadlines for DISPATCH had not been
                        different, then maybe there would have been
                        different issues, but at least it is the
                        different DISPATCH deadlines that have currently
                        ruled out the discussion of this document in
                        Berlin.</span></font></p>
                </div>
              </div>
            </blockquote>
            <div>[MB] That&#39;s absolutely correct - that&#39;s the whole
              intent of the DISPATCH deadlines - these authors simply
              had to send an email to the DISPATCH WG chairs by June
              24th indicating they were putting together a draft that
              was an alternative to a previously discussed draft. =A0They
              didn&#39;t do so. =A0If they had submitted the draft by July
              1st, there would have been some flexibility, but that
              wasn&#39;t the case. =A0There were other people that did so,
              that also requested agenda time that were not given agenda
              time because it wasn&#39;t deemed necessary. AGain, you can
              progress work without discussing at a f2f meeting.=A0</div>
            <div><br>
            </div>
            <div>=A0If you have issues with the DISPATCH process, then
              please bring those to the DISPATCH WG or better yet RAI
              area mailing list. =A0We&#39;ve had this process in place for=
 4
              years so the concept of notifying the chairs several weeks
              before draft deadlines has been there the whole time.
              Indeed, we had the dates for IETF-87 much later than
              usual. =A0 Keep in mind as well that there is NOTHING in the
              DISPATCH/RAI process that requires a document to have f2f
              discussion. =A0Additionally, keep in mind that the document
              in question has normative dependencies such that this
              document cannot be published until those docs are
              completed. [/MB] <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote></div>
    The different points raised in this thread only reaffirms my view
    that having a single set of consistent procedures shared by the WGs
    would be useful. I also understand this view is not shared by all,
    so belaboring the point is probably not going to be productive. <br></d=
iv></blockquote><div>=A0</div><div>[MB] The specific points I am raising ab=
out deadlines with regards to DISPATCH is the RAI process for new work that=
 we implemented over 4+ years ago. =A0I think aligning the issues one sees =
with the deadlines set by the RAI process with this thread of document dead=
lines in general is a red herring. As I noted, there is a discussion with r=
egards to the RAI process overall, including how to handle WGs that have ve=
ry tight coupling. =A0I don&#39;t think the deadlines have any relation wha=
tsoever to the issues around the latter point and should be discussed on th=
e RAI area list. =A0</div>
<div><br></div><div>As to my opinion with regards to the general idea that =
we need a rigid process defining deadlines that all the WGs apply across al=
l areas use, =A0I don&#39;t think that solves any real problems with managi=
ng work in WGs. =A0If folks can&#39;t follow a mailing list close enough to=
 know the expectations of chairs in terms of deadlines for planning their m=
eetings (or progressing work in general), then as others have noted, the WG=
 has a much bigger problem than draft deadlines. =A0Chairs have always been=
 able to make exceptions for documents that miss the deadlines. =A0There ar=
e good reasons why this happens sometimes, I think the process needs to rem=
ain flexible enough for chairs to deal with that. =A0If WG members don&#39;=
t tolerate any changes in concepts or problems to be solved for 2-3 weeks b=
efore the meetings, then we end up with 6-9 weeks of the year (about 2 mont=
hs) where we limit progress. =A0As a chair, I have allowed discussion of dr=
afts (even individual ones) that missed the deadline in cases where the doc=
ument updates where significant enough that it could help with WG progress.=
 =A0Yes, people did complain, but again I believe WG chairs must have flexi=
bility in how they manage their WGs. =A0 =A0[/MB]<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#0000=
00">
    <br>
    Thanks <br><span class=3D"HOEnZb"><font color=3D"#888888">
    <br>
    -- Flemming <br>
    <br>
    <br>
  </font></span></div>

</blockquote></div><br></div></div>

--089e013cb7cc6b3eb204e21bdca0--

From prvs=0916af48bc=sandra.murphy@parsons.com  Tue Jul 23 09:50:52 2013
Return-Path: <prvs=0916af48bc=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 5AD1611E82DB; Tue, 23 Jul 2013 09:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACdAeRcFuqhL; Tue, 23 Jul 2013 09:50:46 -0700 (PDT)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id E906311E8213; Tue, 23 Jul 2013 09:50:41 -0700 (PDT)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id r6NGeZ47014062;  Tue, 23 Jul 2013 11:50:23 -0500
Received: from m4.sparta.com (m4.sparta.com [157.185.61.2]) by txdal11mx03.parsons.com with ESMTP id 1dsutx8td0-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 23 Jul 2013 11:50:23 -0500
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r6NGoBIP018418; Tue, 23 Jul 2013 11:50:11 -0500
Received: from CVA-HUB002.centreville.ads.sparta.com ([10.62.108.29]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r6NGo8Xs011643; Tue, 23 Jul 2013 11:50:11 -0500
Received: from CVA-MB002.centreville.ads.sparta.com ([fe80::6046:a82a:c500:c9ad]) by CVA-HUB002.centreville.ads.sparta.com ([fe80::9817:c0c5:e172:9d1c%11]) with mapi id 14.02.0342.003; Tue, 23 Jul 2013 12:49:30 -0400
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: IETF Agenda <agenda@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: RE: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
Thread-Topic: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
Thread-Index: AQHOgZJ+Pds/RdnRpUCQy37u7SPLj5lyharG
Date: Tue, 23 Jul 2013 16:49:29 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com>
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com>
In-Reply-To: <20130715193531.10405.94711.idtracker@ietfa.amsl.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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-07-23_05:2013-07-22, 2013-07-23, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=5.10375075535308e-12 kscore.compositescore=0 circleOfTrustscore=48.064 compositescore=0.0468750453387092 urlsuspect_oldscore=0.468750453387092 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=6008 rbsscore=0.0468750453387092 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-1307230111
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, 23 Jul 2013 16:50:52 -0000

I went looking for my message rsvp'ing, then realized that the survey was t=
he rsvp.=0A=
=0A=
So I now can't be sure I rsvp-d.=0A=
=0A=
If I did, would I have a confirmation?  If I did not, is it now too late?=
=0A=
=0A=
--Sandy=0A=
=0A=
________________________________________=0A=
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of IE=
TF Agenda [agenda@ietf.org]=0A=
Sent: Monday, July 15, 2013 3:35 PM=0A=
To: Working Group Chairs=0A=
Cc: edu-team@ietf.org; irsg@irtf.org=0A=
Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER=0A=
=0A=
Hello Everyone,=0A=
=0A=
This is a reminder that the cut-off to register for the WG Chair Lunch Trai=
ning is this Friday, July 19th.  Please fill out the survey (http://www.sur=
veymonkey.com/s/ZRKLYSZ) to RSVP for this event if you have not already don=
e so.=0A=
=0A=
If you have RSVP'd for the training lunch but will not be able to attend, p=
lease send a message to agenda@ietf.org.=0A=
=0A=
WG Chairs' Training Lunch Information:=0A=
=0A=
Date: July 31st, 2013=0A=
Time: 11:30 am=0A=
Location: TBA=0A=
Topic: The WG Chair portion of the datatracker (moderated by Margaret Wasse=
rman).=0A=
=0A=
Lunch will be provided.  All current WG chairs, BOF chairs, IRTF chairs, an=
d IESG members are welcome to attend.=0A=
=0A=
Thank you!=0A=
=0A=
Stephanie McCammon=0A=
(on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)=0A=
=0A=
=0A=
=0A=
=0A=
=0A=

From tnadeau@lucidvision.com  Tue Jul 23 10:29:09 2013
Return-Path: <tnadeau@lucidvision.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 C601511E8302; Tue, 23 Jul 2013 10:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lptbAuuft0bP; Tue, 23 Jul 2013 10:29:03 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 30E6711E8110; Tue, 23 Jul 2013 10:28:58 -0700 (PDT)
Received: from [172.28.130.112] (westford-nat.juniper.net [66.129.232.2]) by lucidvision.com (Postfix) with ESMTP id 7029E250BABD; Tue, 23 Jul 2013 13:28:57 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com>
Date: Tue, 23 Jul 2013 13:28:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com>
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com>
To: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
X-Mailer: Apple Mail (2.1508)
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 23 Jul 2013 17:29:09 -0000

It would be great to have a date set soon so that we could block out the =
date/time on the calendar.=20


On Jul 23, 2013:12:49 PM, at 12:49 PM, "Murphy, Sandra" =
<Sandra.Murphy@parsons.com> wrote:

> I went looking for my message rsvp'ing, then realized that the survey =
was the rsvp.
>=20
> So I now can't be sure I rsvp-d.
>=20
> If I did, would I have a confirmation?  If I did not, is it now too =
late?
>=20
> --Sandy
>=20
> ________________________________________
> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf =
of IETF Agenda [agenda@ietf.org]
> Sent: Monday, July 15, 2013 3:35 PM
> To: Working Group Chairs
> Cc: edu-team@ietf.org; irsg@irtf.org
> Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
>=20
> Hello Everyone,
>=20
> This is a reminder that the cut-off to register for the WG Chair Lunch =
Training is this Friday, July 19th.  Please fill out the survey =
(http://www.surveymonkey.com/s/ZRKLYSZ) to RSVP for this event if you =
have not already done so.
>=20
> If you have RSVP'd for the training lunch but will not be able to =
attend, please send a message to agenda@ietf.org.
>=20
> WG Chairs' Training Lunch Information:
>=20
> Date: July 31st, 2013
> Time: 11:30 am
> Location: TBA
> Topic: The WG Chair portion of the datatracker (moderated by Margaret =
Wasserman).
>=20
> Lunch will be provided.  All current WG chairs, BOF chairs, IRTF =
chairs, and IESG members are welcome to attend.
>=20
> Thank you!
>=20
> Stephanie McCammon
> (on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)
>=20
>=20
>=20
>=20
>=20
>=20


From br@brianrosen.net  Tue Jul 23 10:32:55 2013
Return-Path: <br@brianrosen.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 2FB0511E8307; Tue, 23 Jul 2013 10:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.978
X-Spam-Level: 
X-Spam-Status: No, score=-97.978 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_43=0.6, 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 EEGulORaMIua; Tue, 23 Jul 2013 10:32:50 -0700 (PDT)
Received: from mm2.idig.net (unknown [70.33.247.98]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9E811E8110; Tue, 23 Jul 2013 10:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brianrosen.net; s=default;  h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=9/EOcyRIe6JiLzI0AzoXbUKGpS2kBhk83KHI+ks0CJM=;  b=XOijF10b0Lxcev66wZFSK3Yl8SJwTvqY2q/mURg1cUUAcZEzKVJYL/ah6431uOG/Ur0qKKx4SwOPsRG6CGe6eAplf10p2DwDFmKmeLITknZ8KAdB6bnlHeEEMyiQuTmfEbZcwa72sXPdPGldNT3n6ivBMauuU2u8/dCoOihuJiw=;
Received: from neustargw.va.neustar.com ([209.173.53.233]:55462 helo=[10.33.192.17]) by mm2.idig.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <br@brianrosen.net>) id 1V1gS9-00080e-6k; Tue, 23 Jul 2013 13:32:49 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com>
Date: Tue, 23 Jul 2013 13:32:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9AEE5DE2-573D-4CF7-98B1-589D7CD7D0AD@brianrosen.net>
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com> <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.1508)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - mm2.idig.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - brianrosen.net
X-Get-Message-Sender-Via: mm2.idig.net: authenticated_id: br@brianrosen.net
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 23 Jul 2013 17:32:55 -0000

It's always Wednesday at 11:30, as noted.

You can block that time out for the next several IETFs at least.

Brian

On Jul 23, 2013, at 1:28 PM, Thomas Nadeau <tnadeau@lucidvision.com> =
wrote:

> It would be great to have a date set soon so that we could block out =
the date/time on the calendar.=20
>=20
>=20
> On Jul 23, 2013:12:49 PM, at 12:49 PM, "Murphy, Sandra" =
<Sandra.Murphy@parsons.com> wrote:
>=20
>> I went looking for my message rsvp'ing, then realized that the survey =
was the rsvp.
>>=20
>> So I now can't be sure I rsvp-d.
>>=20
>> If I did, would I have a confirmation?  If I did not, is it now too =
late?
>>=20
>> --Sandy
>>=20
>> ________________________________________
>> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf =
of IETF Agenda [agenda@ietf.org]
>> Sent: Monday, July 15, 2013 3:35 PM
>> To: Working Group Chairs
>> Cc: edu-team@ietf.org; irsg@irtf.org
>> Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
>>=20
>> Hello Everyone,
>>=20
>> This is a reminder that the cut-off to register for the WG Chair =
Lunch Training is this Friday, July 19th.  Please fill out the survey =
(http://www.surveymonkey.com/s/ZRKLYSZ) to RSVP for this event if you =
have not already done so.
>>=20
>> If you have RSVP'd for the training lunch but will not be able to =
attend, please send a message to agenda@ietf.org.
>>=20
>> WG Chairs' Training Lunch Information:
>>=20
>> Date: July 31st, 2013
>> Time: 11:30 am
>> Location: TBA
>> Topic: The WG Chair portion of the datatracker (moderated by Margaret =
Wasserman).
>>=20
>> Lunch will be provided.  All current WG chairs, BOF chairs, IRTF =
chairs, and IESG members are welcome to attend.
>>=20
>> Thank you!
>>=20
>> Stephanie McCammon
>> (on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


From adam@nostrum.com  Tue Jul 23 10:41:47 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 861A111E8302; Tue, 23 Jul 2013 10:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.060, 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 JqWeG5woVdvC; Tue, 23 Jul 2013 10:41:47 -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 F350511E823F; Tue, 23 Jul 2013 10:41:46 -0700 (PDT)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r6NHfh0P016192 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Jul 2013 12:41:45 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <51EEC051.2050900@nostrum.com>
Date: Tue, 23 Jul 2013 12:41:37 -0500
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: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 23 Jul 2013 17:41:47 -0000

On 7/23/13 11:49, Murphy, Sandra wrote:
> If I did, would I have a confirmation?

I'm about 90% sure I RSVPed, but when I went looking for a confirmation 
a couple of days ago to be 100% sure, I didn't find one. There is 
probably no confirmation.

It think the new process needs some refinement -- it would be nice to 
have immediate confirmation of signing up.

/a

From Adam.Montville@cisecurity.org  Tue Jul 23 10:42:43 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 7357F11E82AF; Tue, 23 Jul 2013 10:42:43 -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, J_CHICKENPOX_43=0.6, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlp7FL3PVtEH; Tue, 23 Jul 2013 10:42:38 -0700 (PDT)
Received: from mail1.bemta12.messagelabs.com (mail1.bemta12.messagelabs.com [216.82.251.11]) by ietfa.amsl.com (Postfix) with ESMTP id 148A811E8302; Tue, 23 Jul 2013 10:42:36 -0700 (PDT)
Received: from [216.82.250.179:63834] by server-11.bemta-12.messagelabs.com id 8B/3C-32766-A80CEE15; Tue, 23 Jul 2013 17:42:34 +0000
X-Env-Sender: Adam.Montville@cisecurity.org
X-Msg-Ref: server-3.tower-210.messagelabs.com!1374601353!2778552!1
X-Originating-IP: [69.195.43.86]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=cisecurity.org,-,-
X-VirusChecked: Checked
Received: (qmail 24642 invoked from network); 23 Jul 2013 17:42:34 -0000
Received: from mail.msisac.org (HELO mail.msisac.org) (69.195.43.86) by server-3.tower-210.messagelabs.com with AES128-SHA encrypted SMTP; 23 Jul 2013 17:42:34 -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; Tue, 23 Jul 2013 13:42:18 -0400
From: Adam Montville <Adam.Montville@cisecurity.org>
To: Brian Rosen <br@brianrosen.net>, Thomas Nadeau <tnadeau@lucidvision.com>
Subject: RE: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
Thread-Topic: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
Thread-Index: AQHOgZKEjpEa3CuXykmpv7pcWy/MnZlyyRuAgAALCYCAAAEQgP//vz+Q
Date: Tue, 23 Jul 2013 17:42:19 +0000
Message-ID: <05BCCEB107AF88469B9F99783D47C1D67363E2@CISEXCHANGE1.msisac.org.local>
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com> <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com> <9AEE5DE2-573D-4CF7-98B1-589D7CD7D0AD@brianrosen.net>
In-Reply-To: <9AEE5DE2-573D-4CF7-98B1-589D7CD7D0AD@brianrosen.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.252.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 23 Jul 2013 17:42:43 -0000

Will there be an opportunity to get the training at a later date or to oth=
erwise have any materials distributed before or after the fact?  This time=
 appears to interfere with the NOMCOM lunch from what I can tell.

Adam

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Brian Rosen
> Sent: Tuesday, July 23, 2013 10:33 AM
> To: Thomas Nadeau
> Cc: Working Group Chairs; IETF Agenda
> Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
>=20
> It's always Wednesday at 11:30, as noted.
>=20
> You can block that time out for the next several IETFs at least.
>=20
> Brian
>=20
> On Jul 23, 2013, at 1:28 PM, Thomas Nadeau <tnadeau@lucidvision.com>
> wrote:
>=20
> > It would be great to have a date set soon so that we could block out t=
he
> date/time on the calendar.
> >
> >
> > On Jul 23, 2013:12:49 PM, at 12:49 PM, "Murphy, Sandra"
> <Sandra.Murphy@parsons.com> wrote:
> >
> >> I went looking for my message rsvp'ing, then realized that the survey=
=20was
> the rsvp.
> >>
> >> So I now can't be sure I rsvp-d.
> >>
> >> If I did, would I have a confirmation?  If I did not, is it now too l=
ate?
> >>
> >> --Sandy
> >>
> >> ________________________________________
> >> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf=

> of IETF Agenda [agenda@ietf.org]
> >> Sent: Monday, July 15, 2013 3:35 PM
> >> To: Working Group Chairs
> >> Cc: edu-team@ietf.org; irsg@irtf.org
> >> Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
> >>
> >> Hello Everyone,
> >>
> >> This is a reminder that the cut-off to register for the WG Chair Lunc=
h
> Training is this Friday, July 19th.  Please fill out the survey
> (http://www.surveymonkey.com/s/ZRKLYSZ) to RSVP for this event if you
> have not already done so.
> >>
> >> If you have RSVP'd for the training lunch but will not be able to att=
end,
> please send a message to agenda@ietf.org.
> >>
> >> WG Chairs' Training Lunch Information:
> >>
> >> Date: July 31st, 2013
> >> Time: 11:30 am
> >> Location: TBA
> >> Topic: The WG Chair portion of the datatracker (moderated by Margaret=

> Wasserman).
> >>
> >> Lunch will be provided.  All current WG chairs, BOF chairs, IRTF chai=
rs, and
> IESG members are welcome to attend.
> >>
> >> Thank you!
> >>
> >> Stephanie McCammon
> >> (on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)
> >>
> >>
> >>
> >>
> >>
> >>
> >
>=20
> ...

This message and attachments may contain confidential information.  If it =
appears that this message was sent to you by mistake, any retention, disse=
mination, distribution or copying of this message and attachments is stric=
tly prohibited.  Please notify the sender immediately and permanently dele=
te the message and any attachments.

From jmpolk@cisco.com  Tue Jul 23 12:26:51 2013
Return-Path: <jmpolk@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 2D11511E82A5; Tue, 23 Jul 2013 12:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level: 
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEd-3HgHwEJg; Tue, 23 Jul 2013 12:26:46 -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 F125D11E80A2; Tue, 23 Jul 2013 12:26:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3239; q=dns/txt; s=iport; t=1374607606; x=1375817206; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=UqUsGJJLsSVzBacQh3gytUzfD3cmkw3/C9YMMp7dljg=; b=NC3JRsXhV4GnXHj4YZBX6//C60RUQzVpH4KSJQDr/NVer/sUwRcfogYH XOfYgmJ8H3lK0J8kmhoo5yFONsmyIEHvghl3FpCNveRhW6gbGA3bnSyq2 5J+wxZVvD5v/701tIYZCYqAHgx9HjClPVKtNTwfJaMgkyogUhicQMP4Xp 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAIfX7lGtJXHB/2dsb2JhbABbgwY1wSyBExZ0giQBAQEEGCACPwwEBwQRAwEBAQEJFQkHDwotCQgGARIch3QMuDePfQcGgwxuA4kqoAKDMh4
X-IronPort-AV: E=Sophos;i="4.89,729,1367971200"; d="scan'208";a="238251486"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 23 Jul 2013 19:26:38 +0000
Received: from jmpolk-WS.cisco.com ([10.89.8.39]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6NJQbNC006328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jul 2013 19:26:38 GMT
Message-Id: <201307231926.r6NJQbNC006328@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Jul 2013 14:26:24 -0500
To: Adam Montville <Adam.Montville@cisecurity.org>, Brian Rosen <br@brianrosen.net>, Thomas Nadeau <tnadeau@lucidvision.com>
From: James Polk <jmpolk@cisco.com>
Subject: RE: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
In-Reply-To: <05BCCEB107AF88469B9F99783D47C1D67363E2@CISEXCHANGE1.msisac .org.local>
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com> <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com> <9AEE5DE2-573D-4CF7-98B1-589D7CD7D0AD@brianrosen.net> <05BCCEB107AF88469B9F99783D47C1D67363E2@CISEXCHANGE1.msisac.org.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Agenda <agenda@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, 23 Jul 2013 19:26:51 -0000

The WG chairs lunch has been Wed at 11:30am local time since 2005, so 
all newly scheduled conflicts knew the WG chairs were meeting at this 
day and time...

-j

At 12:42 PM 7/23/2013, Adam Montville wrote:
>Will there be an opportunity to get the training at a later date or 
>to otherwise have any materials distributed before or after the 
>fact?  This time appears to interfere with the NOMCOM lunch from 
>what I can tell.
>
>Adam
>
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> > Behalf Of Brian Rosen
> > Sent: Tuesday, July 23, 2013 10:33 AM
> > To: Thomas Nadeau
> > Cc: Working Group Chairs; IETF Agenda
> > Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
> >
> > It's always Wednesday at 11:30, as noted.
> >
> > You can block that time out for the next several IETFs at least.
> >
> > Brian
> >
> > On Jul 23, 2013, at 1:28 PM, Thomas Nadeau <tnadeau@lucidvision.com>
> > wrote:
> >
> > > It would be great to have a date set soon so that we could block out the
> > date/time on the calendar.
> > >
> > >
> > > On Jul 23, 2013:12:49 PM, at 12:49 PM, "Murphy, Sandra"
> > <Sandra.Murphy@parsons.com> wrote:
> > >
> > >> I went looking for my message rsvp'ing, then realized that the 
> survey was
> > the rsvp.
> > >>
> > >> So I now can't be sure I rsvp-d.
> > >>
> > >> If I did, would I have a confirmation?  If I did not, is it 
> now too late?
> > >>
> > >> --Sandy
> > >>
> > >> ________________________________________
> > >> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf
> > of IETF Agenda [agenda@ietf.org]
> > >> Sent: Monday, July 15, 2013 3:35 PM
> > >> To: Working Group Chairs
> > >> Cc: edu-team@ietf.org; irsg@irtf.org
> > >> Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
> > >>
> > >> Hello Everyone,
> > >>
> > >> This is a reminder that the cut-off to register for the WG Chair Lunch
> > Training is this Friday, July 19th.  Please fill out the survey
> > (http://www.surveymonkey.com/s/ZRKLYSZ) to RSVP for this event if you
> > have not already done so.
> > >>
> > >> If you have RSVP'd for the training lunch but will not be able 
> to attend,
> > please send a message to agenda@ietf.org.
> > >>
> > >> WG Chairs' Training Lunch Information:
> > >>
> > >> Date: July 31st, 2013
> > >> Time: 11:30 am
> > >> Location: TBA
> > >> Topic: The WG Chair portion of the datatracker (moderated by Margaret
> > Wasserman).
> > >>
> > >> Lunch will be provided.  All current WG chairs, BOF chairs, 
> IRTF chairs, and
> > IESG members are welcome to attend.
> > >>
> > >> Thank you!
> > >>
> > >> Stephanie McCammon
> > >> (on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> >
> > ...
>
>This message and attachments may contain confidential 
>information.  If it appears that this message was sent to you by 
>mistake, any retention, dissemination, distribution or copying of 
>this message and attachments is strictly prohibited.  Please notify 
>the sender immediately and permanently delete the message and any attachments.


From smccammon@amsl.com  Tue Jul 23 13:06:46 2013
Return-Path: <smccammon@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 2E05811E82D6; Tue, 23 Jul 2013 13:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level: 
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, 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 OP-RNAtkJaid; Tue, 23 Jul 2013 13:06:45 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4FE11E8116; Tue, 23 Jul 2013 13:06:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 81248A8AEB; Tue, 23 Jul 2013 13:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YiJo8wI7I_bH; Tue, 23 Jul 2013 13:05:35 -0700 (PDT)
Received: from [10.194.120.207] (mobile-166-137-214-034.mycingular.net [166.137.214.34]) by c9a.amsl.com (Postfix) with ESMTPSA id 4F23CA8938; Tue, 23 Jul 2013 13:05:34 -0700 (PDT)
Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
References: <20130715193531.10405.94711.idtracker@ietfa.amsl.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C6B2E@CVA-MB002.centreville.ads.sparta.com> <C5BEEC5C-7DED-4869-9E1B-E6C0D1C42B80@lucidvision.com> <9AEE5DE2-573D-4CF7-98B1-589D7CD7D0AD@brianrosen.net> <05BCCEB107AF88469B9F99783D47C1D67363E2@CISEXCHANGE1.msisac.org.local>
From: Stephanie McCammon <smccammon@amsl.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <05BCCEB107AF88469B9F99783D47C1D67363E2@CISEXCHANGE1.msisac.org.local>
Message-Id: <10A71C15-3001-4BF5-B051-ABBF31C341FA@amsl.com>
Date: Tue, 23 Jul 2013 13:02:28 -0700
To: Adam Montville <Adam.Montville@cisecurity.org>
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (9B176)
Cc: IETF Agenda <agenda@ietf.org>, Working Group 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, 23 Jul 2013 20:06:46 -0000

Hi Adam,

The WG Chairs training will be recorded by Meetecho and available at a later=
 date.  Please let me know if you need anything else!

Thank you,

Stephanie McCammon

Sent from my iPhone

On Jul 23, 2013, at 10:42 AM, Adam Montville <Adam.Montville@cisecurity.org>=
 wrote:

> Will there be an opportunity to get the training at a later date or to oth=
erwise have any materials distributed before or after the fact?  This time a=
ppears to interfere with the NOMCOM lunch from what I can tell.
>=20
> Adam
>=20
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Brian Rosen
>> Sent: Tuesday, July 23, 2013 10:33 AM
>> To: Thomas Nadeau
>> Cc: Working Group Chairs; IETF Agenda
>> Subject: Re: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
>>=20
>> It's always Wednesday at 11:30, as noted.
>>=20
>> You can block that time out for the next several IETFs at least.
>>=20
>> Brian
>>=20
>> On Jul 23, 2013, at 1:28 PM, Thomas Nadeau <tnadeau@lucidvision.com>
>> wrote:
>>=20
>>> It would be great to have a date set soon so that we could block out the=

>> date/time on the calendar.
>>>=20
>>>=20
>>> On Jul 23, 2013:12:49 PM, at 12:49 PM, "Murphy, Sandra"
>> <Sandra.Murphy@parsons.com> wrote:
>>>=20
>>>> I went looking for my message rsvp'ing, then realized that the survey w=
as
>> the rsvp.
>>>>=20
>>>> So I now can't be sure I rsvp-d.
>>>>=20
>>>> If I did, would I have a confirmation?  If I did not, is it now too lat=
e?
>>>>=20
>>>> --Sandy
>>>>=20
>>>> ________________________________________
>>>> From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf
>> of IETF Agenda [agenda@ietf.org]
>>>> Sent: Monday, July 15, 2013 3:35 PM
>>>> To: Working Group Chairs
>>>> Cc: edu-team@ietf.org; irsg@irtf.org
>>>> Subject: IETF 87 - Working Group Chairs' Training Lunch - REMINDER
>>>>=20
>>>> Hello Everyone,
>>>>=20
>>>> This is a reminder that the cut-off to register for the WG Chair Lunch
>> Training is this Friday, July 19th.  Please fill out the survey
>> (http://www.surveymonkey.com/s/ZRKLYSZ) to RSVP for this event if you
>> have not already done so.
>>>>=20
>>>> If you have RSVP'd for the training lunch but will not be able to atten=
d,
>> please send a message to agenda@ietf.org.
>>>>=20
>>>> WG Chairs' Training Lunch Information:
>>>>=20
>>>> Date: July 31st, 2013
>>>> Time: 11:30 am
>>>> Location: TBA
>>>> Topic: The WG Chair portion of the datatracker (moderated by Margaret
>> Wasserman).
>>>>=20
>>>> Lunch will be provided.  All current WG chairs, BOF chairs, IRTF chairs=
, and
>> IESG members are welcome to attend.
>>>>=20
>>>> Thank you!
>>>>=20
>>>> Stephanie McCammon
>>>> (on behalf of Mirjam Kuehne, Radia Perlman, & the Edu Team)
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>=20
>> ...
>=20
> This message and attachments may contain confidential information.  If it a=
ppears that this message was sent to you by mistake, any retention, dissemin=
ation, distribution or copying of this message and attachments is strictly p=
rohibited.  Please notify the sender immediately and permanently delete the m=
essage and any attachments.
>=20

From margaretw42@gmail.com  Wed Jul 24 04:25:51 2013
Return-Path: <margaretw42@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 2BB1C11E8200; Wed, 24 Jul 2013 04:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2OebbTmDvWw; Wed, 24 Jul 2013 04:25:50 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 5F87411E81D0; Wed, 24 Jul 2013 04:25:50 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m46so1421894wev.8 for <multiple recipients>; Wed, 24 Jul 2013 04:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=4x8hphCKm5AYUHQ1HtlubtUxmSgTIxw8B7jE2iO8HoU=; b=KboDkWMLbc7Co5CDef4KkYAmzm2WHxWZ2QzRagiNLAjH6tH6qAStc1FoUCNfYPOvvL xrQ922aqp1xtiPSPF4x7oGUDSj5Nq6ZKOgQy9XafeLYyxXYx+ESkiWAmzHom/dmTVp6g W6TMAL3g2PngZIscEjUY3jrtmoik0DsrkQV3ezqRDAH5+BzegFCgkWa2ef4m0bYooned srWAC616iUM/AEnJwbBX8lkzHv0bUcybWeKGG5l5iP5cTnJA9vYU8kMVxfyAeKDtdBPm ysb5/hy028qxoH4+c5MgBALiIMetjvZdstcKoDBfiPbOiNKWepXBhqPD+GHTz9d9uefa lzJg==
X-Received: by 10.194.19.3 with SMTP id a3mr27284730wje.54.1374665149469; Wed, 24 Jul 2013 04:25:49 -0700 (PDT)
Received: from [10.47.180.116] ([31.55.49.119]) by mx.google.com with ESMTPSA id u9sm4554743wif.6.2013.07.24.04.25.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 04:25:48 -0700 (PDT)
Sender: Margaret Wasserman <margaretw42@gmail.com>
From: Margaret Wasserman <mrw@lilacglade.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Success With WG Data Tracker?
Message-Id: <D969B639-E669-4B1B-AFBC-E4ED5026A373@lilacglade.org>
Date: Wed, 24 Jul 2013 07:25:44 -0400
To: IETF WG Chairs <wgchairs@ietf.org>, iesg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
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, 24 Jul 2013 11:25:51 -0000

Hi All,

I am looking for a few WG Chairs who have been successful using the WG =
Chair portions of the Data Tracker for help with a WG Chairs Training =
session during the Wednesday Lunch Slot.  So, if you have found the WG =
Chair's portion of the data tracker particularly useful for your =
efforts, please contact me directly.

Thanks,
Margaret



From ietf-secretariat@ietf.org  Thu Jul 25 02:32:32 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 12A4221F9633; Thu, 25 Jul 2013 02:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[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 t-87I2hdwyFv; Thu, 25 Jul 2013 02:32:31 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7697221F96A8; Thu, 25 Jul 2013 02:31:55 -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 87 - Online Registration and Payment Cutoff
X-Test-IDTracker: no
X-IETF-IDTracker: 4.60p1
Message-ID: <20130725093155.28408.61934.idtracker@ietfa.amsl.com>
Date: Thu, 25 Jul 2013 02:31:55 -0700
Cc: wgchairs@ietf.org, 87all@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: Thu, 25 Jul 2013 09:32:32 -0000

87th IETF Meeting
Berlin, Germany
July 28-August 2, 2013
Platinum Sponsor: DENIC
Gold Sponsors: Deutsche Telekom and EURid
Bronze Sponsor: Dyn

Meeting venue:  InterContinental Berlin: http://www.berlin.intercontinental=
.com/

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

Online Registration and Payment ends Friday, 26 July 2013, 1700 local Berli=
n time.

On-site Registration starting Sunday, 28 July 2013 at 1100 local Berlin tim=
e.

Only 3 days until the Berlin IETF!

From fluffy@cisco.com  Fri Jul 26 10:15:42 2013
Return-Path: <fluffy@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 B152121F99DD for <wgchairs@ietfa.amsl.com>; Fri, 26 Jul 2013 10:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.524
X-Spam-Level: 
X-Spam-Status: No, score=-110.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 yFkW9gtR8S3R for <wgchairs@ietfa.amsl.com>; Fri, 26 Jul 2013 10:15:37 -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 277F621F9993 for <wgchairs@ietf.org>; Fri, 26 Jul 2013 10:15:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1574; q=dns/txt; s=iport; t=1374858937; x=1376068537; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LudxNPLh70aOclQIysK148oE4A5cnRBpMzL2O8J5lFw=; b=GQB8udge9Ss+M2gvbtCIqPlVTOluMmiR6NxRK+vSPvj8kL0gqyuToEnh eRCkRiMZ9nnh7Zi+/EBiCtwYKLXW1MyHMVpqiNKtVkTH+qrvbSPzV2/Sd nqLsYKbbuWAOFg73izkM/9eldJb472Dt9FBVE81GgVjLAFz8+CUqJ9yaY I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAK+t8lGtJV2d/2dsb2JhbABbgwaBBb1egRkWdIIkAQEBAwFuCxACAQgiJDIlAgQOBQgUh24GuGCPSgIxB4MWbwOpK4MUgio
X-IronPort-AV: E=Sophos;i="4.89,752,1367971200"; d="scan'208";a="239945400"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP; 26 Jul 2013 17:15:36 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6QHFaDT006642 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 26 Jul 2013 17:15:36 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.29]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Fri, 26 Jul 2013 12:15:36 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: "too late" drafts and meeting time
Thread-Topic: "too late" drafts and meeting time
Thread-Index: AQHOiiO90p9jO3ePqk+QALAfosikgw==
Date: Fri, 26 Jul 2013 17:15:35 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB113614744@xmb-aln-x02.cisco.com>
References: <20476_1373976443_51E5377B_20476_2943_1_AC1ADC68A92CF94FA8CFCB406C1CBE3D074FEEB0@PEXCVZYM13.corporate.adroot.infra.ftgroup> <8D23D4052ABE7A4490E77B1A012B630775213875@mbx-01.win.nominum.com> <51E6178F.5060004@cisco.com> <8D23D4052ABE7A4490E77B1A012B630775215878@mbx-01.win.nominum.com> <51E72874.1040004@cisco.com> <8D23D4052ABE7A4490E77B1A012B6307752171D9@mbx-01.win.nominum.com> <51E73772.1050209@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AC779@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <288D08EAB8DD734D89424BA86EEE078B@emea.cisco.com>
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, 26 Jul 2013 17:15:42 -0000

On Jul 17, 2013, at 8:50 PM, "Black, David" <david.black@emc.com> wrote:

>> Why do we have a draft deadline if people meeting that deadline can't
>> have their documents discussed at the meeting because they submitted
>> their documents "too late" ?
>=20
> Melinda Shore recently sent a cogent answer on that to the OPSAWG list:
>=20
>  We've been getting a lot of requests for time on the agenda for
>  the upcoming meeting to "present" drafts which haven't been
>  discussed on the mailing list.  This is a reminder that the purpose
>  of meetings is face-to-face discussion of issues that haven't
>  been able to make progress on the mailing list, and to progress
>  deliverables.  The IETF is somewhat different from other standards
>  bodies in that meeting time is generally not used for presentation
>  of new material, and that the work of the organization is primarily
>  done via working group mailing lists.  The most reliable way to
>  get time on a meeting agenda is to have a lively discussion on
>  the mailing list prior to the meeting.
>=20
> There is a common misperception that meeting the draft submission
> deadline "entitles" a draft to "presentation" time in the WG meeting.
> The IETF simply does not work that way ...
>=20
> If a "too late" draft generates lively (and appropriate) mailing list
> discussion, I have no problem bashing the WG agenda at the start of
> the meeting to spend time on that topic.
>=20
> Thanks,
> --David

+1 Melinda. That text could be added to the wg chair training templates =85=
.


From jari.arkko@piuha.net  Fri Jul 26 14:59:20 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 41F8711E816B for <wgchairs@ietfa.amsl.com>; Fri, 26 Jul 2013 14:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.027, 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 o8LZ3dwwYCDG for <wgchairs@ietfa.amsl.com>; Fri, 26 Jul 2013 14:59:16 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 57A7511E8162 for <wgchairs@ietf.org>; Fri, 26 Jul 2013 14:59:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B17632CC61 for <wgchairs@ietf.org>; Sat, 27 Jul 2013 00:59:13 +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 BFnd1GfleVkR for <wgchairs@ietf.org>; Sat, 27 Jul 2013 00:59:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 456E62CC60 for <wgchairs@ietf.org>; Sat, 27 Jul 2013 00:59:12 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3FC0D26B-A8EF-4A43-9F80-461D3E8A790F"
Subject: moving (some) reviews earlier
Message-Id: <076D38B1-EBDB-44C1-8013-97FA31EAF24B@piuha.net>
Date: Sat, 27 Jul 2013 00:59:12 +0300
To: Working Group Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
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, 26 Jul 2013 21:59:20 -0000

--Apple-Mail=_3FC0D26B-A8EF-4A43-9F80-461D3E8A790F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

All,

We are planning to start the following experiment with some directorate =
reviews that are happening during the final stages of the IETF process. =
We would like to get your feedback.

----

Internet Drafts sent for approval as RFCs are reviewed by individuals =
during the IETF Last Call, the Area Directors, IANA, as well as a number =
of volunteers from various directorates and review teams. The reviews =
from these teams has gained a significant role in ensuring that the IETF =
produces high-quality, understandable and implementable RFCs.

Yet, as discussed in =
http://www.ietf.org/blog/2013/05/balancing-the-process/ we have a =
general problem that quite a lot of the work around IETF documents =
happens at the end of the process. In particular, a number of the =
reviews during IETF last call point out issues that end up being raised =
by the IESG as comments. It is of course good that issues are caught, =
but raising them earlier would be better. And it would be better if the =
working groups - the intended focus point of work on a topic - would get =
to handle them, as opposed to raising these issues with the IESG. The =
IESG discussed these issues in its May 2013 retreat, and decided to =
experiment with three actions designed to move more work to the =
responsibility of the working groups:

(1) Perform some reviews that are now happening at IETF Last Call a bit =
earlier. This will put the working group in a bigger role in resolving =
cross-area and general issues.

(2) Invite document shepherds on IESG telechats when there's a document =
that is likely to require discussion. This will make it possible for the =
document shepherd to me directly be=20

(3) When a document has a number of issues, hand over the process back =
to the working group, as opposed to the IESG tracking the issues. Among =
other things, this will ensure that changes are discussed in an open =
working group list and agreed through consensus.

Some of you have seen (2) and (3) happen, more will come. For (1), =
building quality and cross-area review to the process earlier is of =
course a big effort. We plan to launch an experiment to make a small =
change to current directorate review procedures to learn if we can move =
reviews a little bit earlier. If successful, this experiment will enable =
working groups to deal with issues before IETF Last Call and IESG review =
and empower the working groups to be in charge of the documents =
throughout their life cycle. We are also hoping that document quality =
will improve and number of issues discussed in the IESG will be lower.

While the number of reviews as such is not changed, some additional =
effort and care will however be required from the reviewers, directorate =
coordinators/secretaries, the working group chairs, and other =
participants. The experiment will show us whether this effort is =
reasonable and if there are any unexpected effects. The experiment is =
performed on a voluntary basis by each directorate. As early review =
requests come in, the directorates can throttle workload by either =
processing the requests or reverting to the existing procedures. =
Initially, the Gen-ART, Security Directorate, and Applications Area =
Directorate are included in this effort. Other directorates may be added =
later. The experiment will be reviewed after six months.

Care must be taken to avoid a number of possible drawbacks. There may be =
problematic documents that would require much re-review and effort. =
Similarly, working groups often perform a number of working group last =
calls on a document, and it would be undesirable to engage the reviewer =
before the document was really ready to be sent forward. And when =
reviewers send comments, it is important that the group listens to the =
comments in the right way, like you would for a review from a security =
expert or a general networking expert. E-mail practices around sending =
and responding to comments have to be carefully managed, as the outside =
reviewers are typically not list members.

For the working group chairs, you can request a review by sending mail =
to dir-coord@ietf.org, indicating the name of the document. You can ask =
for a review as soon as a working group last call has ended successfully =
and the document edits are done. Initially, it would make sense to ask =
for reviews on documents that you feel are likely the most stable ones. =
To avoid congesting the reviewer resources, ask for this service only =
for some documents, not as a wholesale service on every document you =
submit for publication.=20

You can ask for the review in parallel with ongoing AD reviews, filling =
out the shepherd questionnaire, etc. The hope is that reviews can come =
in in the same time frame as other tasks in this stage, and that you can =
take the comments into account and revise the document before finally =
sending it out for IETF Last Call. Reviews will be sent to you and =
potentially the working group mailing list. You may need to forward =
comments and/or approve new posters to the list. Discussion on the =
mailing list is encouraged, but please try to ensure that the reviewer =
is kept on the Cc line, as he or she may not be on the list itself. =
Treat the reviews with respect and keep it in mind that outside experts =
may have opinions that need to be taken into account, even if the =
working group had not considered those aspects before. Mediate and =
monitor the discussion actively. Try to keep the reviewer out of e-mail =
storms and work out solutions separately and then engage the reviewer =
again.

For the directorate coordinators/secretaries, please monitor the =
dir-coord@ietf.list. If there is a request for a review, dispatch the =
task to a reviewer. Managing overload is your task. Please acknowledge =
requests and whether you can accommodate them. Directorates that today =
review documents twice, at IETF Last Call and then before entering the =
IESG telechat should continue this practice by doing the early review =
and then the IESG telechat review. Existing practices such as retaining =
the same reviewer for checking the same version is useful. Your review =
tools and practices may need adjustment to accommodate reviews happening =
at different times.

For the reviewers, take into account the context. Post your reviews to =
the working group chairs, authors, and Cc the working group mailing list =
if necessary. If your review team uses a template for these e-mails, =
some changes may be necessary in the template for the early review. Some =
of those changes have been discussed, e.g., in the Gen-ART list.

For everyone, please collect your experiences so that in six months we =
can evaluate how you liked the experience. And thank you for your =
participation in this effort!

Jari Arkko for the IESG=

--Apple-Mail=_3FC0D26B-A8EF-4A43-9F80-461D3E8A790F
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>All,</div><div><br></div><div>We are planning to start the =
following experiment with some directorate reviews that are happening =
during the final stages of the IETF process. We would like to get your =
feedback.</div><div><br></div><div>----</div><div><br></div>Internet =
Drafts sent for approval as RFCs are reviewed by individuals during the =
IETF Last Call, the Area Directors, IANA, as well as a number of =
volunteers from various directorates and review teams. The =
reviews&nbsp;from these teams has gained a significant role in ensuring =
that the IETF produces high-quality, understandable and implementable =
RFCs.<br><br>Yet, as discussed in&nbsp;<a =
href=3D"http://www.ietf.org/blog/2013/05/balancing-the-process/">http://ww=
w.ietf.org/blog/2013/05/balancing-the-process/</a>&nbsp;we have a =
general problem that quite a lot of the work around IETF documents =
happens at the end of the process. In particular, a&nbsp;number of the =
reviews during IETF last call point out issues that end up being raised =
by the IESG as comments. It is of course good that issues are =
caught,&nbsp;but raising them earlier would be better. And it would be =
better if the working groups - the intended focus point of work on a =
topic - would get to handle them, as opposed to raising these issues =
with the IESG. The&nbsp;IESG discussed these issues in its May 2013 =
retreat, and decided to experiment with three actions designed to move =
more work to the responsibility of the working =
groups:<br><br><blockquote style=3D"margin: 0 0 0 40px; border: none; =
padding: 0px;">(1) Perform some reviews that are now happening at IETF =
Last Call a bit earlier. This will put the working group in a bigger =
role in resolving cross-area and general issues.<div><br></div><div>(2) =
Invite document shepherds on IESG telechats when there's a document that =
is likely to require discussion. This will make it possible for the =
document shepherd to me directly be&nbsp;</div><div><br></div><div>(3) =
When a document has a number of issues, hand over the process back to =
the working group, as opposed to the IESG tracking the issues. Among =
other things, this will ensure that changes are discussed in =
an&nbsp;open working group list and agreed through =
consensus.</div></blockquote><div><br></div><div>Some of you have seen =
(2) and (3) happen, more will come. For (1), building quality and =
cross-area review to the process earlier is of course a big effort. We =
plan to launch an experiment to make a small change to current =
directorate review procedures to&nbsp;learn if we can move reviews a =
little bit earlier. If successful, this experiment will enable working =
groups to deal with issues before IETF Last Call and IESG review and =
empower the working groups to be in charge&nbsp;of the documents =
throughout their life cycle. We are also hoping that document quality =
will improve and number of issues discussed in the IESG will be =
lower.<br><br>While the number of reviews as such is not changed, some =
additional effort and care will however be required from the reviewers, =
directorate coordinators/secretaries, the working group chairs, and =
other&nbsp;participants. The experiment will show us whether this effort =
is reasonable and if there are any unexpected effects. The experiment is =
performed on a voluntary basis by each directorate. As early review =
requests&nbsp;come in, the directorates can throttle workload by either =
processing the requests or reverting to the existing procedures. =
Initially, the Gen-ART, Security Directorate, and Applications Area =
Directorate are included&nbsp;in this effort. Other directorates may be =
added later. The experiment will be reviewed after six =
months.<br><br>Care must be taken to avoid a number of possible =
drawbacks. There may be problematic documents that would require much =
re-review and effort. Similarly, working groups often perform a number =
of working&nbsp;group last calls on a document, and it would be =
undesirable to engage the reviewer before the document was really ready =
to be sent forward. And when reviewers send comments, it is important =
that the group&nbsp;listens to the comments in the right way, like you =
would for a review from a security expert or a general networking =
expert. E-mail practices around sending and responding to comments have =
to be carefully&nbsp;managed, as the outside reviewers are typically not =
list members.<br><br>For the&nbsp;<b>working group chairs</b>, you can =
request a review by sending mail to&nbsp;dir-coord@ietf.org, indicating =
the name of the document. You can ask for a review as soon as a working =
group last call has ended&nbsp;successfully and the document edits are =
done. Initially, it would make sense to ask for reviews on documents =
that you feel are likely the most stable ones. To avoid congesting the =
reviewer resources, ask for this&nbsp;service only for some documents, =
not as a wholesale service on every document you submit for =
publication.&nbsp;<br><br>You can ask for the review in parallel with =
ongoing AD reviews, filling out the shepherd questionnaire, etc. The =
hope is that reviews can come in in the same time frame as other tasks =
in this stage, and that you&nbsp;can take the comments into account and =
revise the document before finally sending it out for IETF Last Call. =
Reviews will be sent to you and potentially the working group mailing =
list. You may need to forward&nbsp;comments and/or approve new posters =
to the list. Discussion on the mailing list is encouraged, but please =
try to ensure that the reviewer is kept on the Cc line, as he or she may =
not be on the list itself. Treat the&nbsp;reviews with respect and keep =
it in mind that outside experts may have opinions that need to be taken =
into account, even if the working group had not considered those aspects =
before. Mediate and monitor the&nbsp;discussion actively. Try to keep =
the reviewer out of e-mail storms and work out solutions separately and =
then engage the reviewer again.<br><br>For the&nbsp;<b>directorate =
coordinators/secretaries</b>, please monitor =
the&nbsp;dir-coord@ietf.list. If there is a request for a review, =
dispatch the task to a reviewer. Managing overload is your task. Please =
acknowledge&nbsp;requests and whether you can accommodate them. =
Directorates that today review documents twice, at IETF Last Call and =
then before entering the IESG telechat should continue this practice by =
doing the early&nbsp;review and then the IESG telechat review. Existing =
practices such as retaining the same reviewer for checking the same =
version is useful. Your review tools and practices may need adjustment =
to accommodate&nbsp;reviews happening at different times.<br><br>For =
the&nbsp;<b>reviewers</b>, take into account the context. Post your =
reviews to the working group chairs, authors, and Cc the working group =
mailing list if necessary. If your review team uses a template for these =
e-mails,&nbsp;some changes may be necessary in the template for the =
early review. Some of those changes have been discussed, e.g., in the =
Gen-ART list.<br><br>For everyone, please collect your experiences so =
that in six months we can evaluate how you liked the experience. And =
thank you for your participation in this effort!<br><br>Jari Arkko for =
the IESG</div></body></html>=

--Apple-Mail=_3FC0D26B-A8EF-4A43-9F80-461D3E8A790F--

From amorris@amsl.com  Sun Jul 28 01:41:08 2013
Return-Path: <amorris@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 3528E21F9D92; Sun, 28 Jul 2013 01:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CqFuKDcx3EPL; Sun, 28 Jul 2013 01:41:07 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 73B4221F9D7E; Sun, 28 Jul 2013 01:41:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 6C8CC9FB74; Sun, 28 Jul 2013 01:39:38 -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 CRe1IqrliIXC; Sun, 28 Jul 2013 01:39:38 -0700 (PDT)
Received: from dhcp-6301.meeting.ietf.org (dhcp-6301.meeting.ietf.org [130.129.99.1]) by c9a.amsl.com (Postfix) with ESMTPSA id 927C59FB67; Sun, 28 Jul 2013 01:39:37 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Reminder: Newcomers' Meet-and-Greet Today
Date: Sun, 28 Jul 2013 01:41:04 -0700
Message-Id: <BD82CA97-EF79-4FEE-BB30-8D5AAB858089@amsl.com>
To: 87-1st-timers@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: "wgchairs@ietf.org Group" <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, 28 Jul 2013 08:41:08 -0000

This is a reminder that you are invited to a Meet-and-Greet with WG =
Chairs from 1600-1700 today. Only first-time attendees and WG Chairs, =
IESG members, and IAB members are invited to this special reception, =
which will take place in the Hugos South room of the Intercontinental =
Hotel.  Beer, wine, soda, and light appetizers will be provided.=20

The sole purpose of this gathering is to give you some time to mingle =
with the WG Chairs, providing a forum for you to get answers to any =
questions you may have about the IETF.  If you are hoping to speak with =
a  particular WG Chair, you may want to check out our WG Chair =
Directory, where you can find photos of many of the IETF WG Chairs: =
http://www.ietf.org/wg/chair-photos.html

We are experimenting with something new for this Meet-and-Greet and =
putting area signs (Applications, Internet, Routing, etc.) on tables =
throughout the room (one table per area) so that attendees can gather in =
their area of interest and/or expertise and hopefully find each other =
more readily. =20

If you have signed up to participate in our new Mentoring Program, you =
may be able to meet your mentor there as well. We will have a designated =
area for mentors and program participants to meet. For more information =
about the Mentoring Program, please see =
http://www.ietf.org/resources/mentoring-program.html.

The Meet-and-Greet will end promptly at 5pm.  At that time, you are =
encouraged to attend the official IETF Welcome Reception.

Regards,

Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From jari.arkko@piuha.net  Tue Jul 30 00:50:42 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 824A311E81CF for <wgchairs@ietfa.amsl.com>; Tue, 30 Jul 2013 00:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XoLyK0CxFIsF for <wgchairs@ietfa.amsl.com>; Tue, 30 Jul 2013 00:50:38 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C921D11E81D6 for <wgchairs@ietf.org>; Tue, 30 Jul 2013 00:50:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F0E642CC54; Tue, 30 Jul 2013 10:50:31 +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 3f87qG1zUMF8; Tue, 30 Jul 2013 10:50:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 642762CC48; Tue, 30 Jul 2013 10:50:30 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: media at IETF-87
Date: Tue, 30 Jul 2013 09:50:29 +0200
Message-Id: <51F4398A-077D-4B46-90AE-66C9AE9C56F0@piuha.net>
To: Working Group Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: Greg Wood <wood@isoc.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, 30 Jul 2013 07:50:42 -0000

I wanted to let you know that there are a few press representatives =
among the IETF crowd this week. For instance, Manfred Klolber and Peer =
Welchering will be reporting from the IETF to Forschung Aktuell on Radio =
Germany (http://de.wikipedia.org/wiki/Forschung_Aktuell), which seems to =
be a widely listened to program in Germany.

The reporters' plan is to sit in on some working group sessions and =
interview a few folks. They are badged and will have pretty obvious =
microphones. They may be approaching you and asking about your =
technology, and you may be interested in talking about all the great =
stuff you are developing :-)

Greg Wood, responsible for IETF and ISOC communications, has more =
details and can help you with any questions or other thoughts you may =
have with media interactions in general.

Jari


From mcr@sandelman.ca  Tue Jul 30 01:09:42 2013
Return-Path: <mcr@sandelman.ca>
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 5075E11E80DF; Tue, 30 Jul 2013 01:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[AWL=0.396,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDjNJliGgmPt; Tue, 30 Jul 2013 01:09:41 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id C799221F9E37; Tue, 30 Jul 2013 01:09:41 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 96B642017B; Tue, 30 Jul 2013 05:15:33 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CA3CD63A7C; Tue, 30 Jul 2013 04:08:08 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id ACFAF636AD; Tue, 30 Jul 2013 04:08:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: attendees <87attendees@ietf.org>, WG Chairs <wgchairs@ietf.org>
Subject: mics are open
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 30 Jul 2013 04:08:08 -0400
Message-ID: <11114.1375171688@sandelman.ca>
Sender: mcr@sandelman.ca
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, 30 Jul 2013 08:09:42 -0000

--=-=-=


I just want to remind people, particularly WG chairs, that the microphones
are alive before sessions, and after them.  So, if you have conversations
at the front table before and after, please do not assume they are private.

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



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

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

iQCVAwUBUfd0ZYqHRg3pndX9AQI79gQAy5hbW7N9FmdXkiZTfOCK2btnIoi2z2jh
+Fy1pxLS14XhvIMvdMrUhGWroYxtkwPDEMXHawvJFttwUzyDtCJK5yihvC9uaf9I
LDCbQwg+B5Uzuh0oCaR7610eObJBlGaJx0sB3S2WsFdr9drQXiwP/yHsyoR8xSPg
krLk1seLKro=
=Cinq
-----END PGP SIGNATURE-----
--=-=-=--

From lee.howard@twcable.com  Tue Jul 30 06:20:28 2013
Return-Path: <lee.howard@twcable.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 CBDDE21F9E6D for <wgchairs@ietfa.amsl.com>; Tue, 30 Jul 2013 06:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.717
X-Spam-Level: 
X-Spam-Status: No, score=0.717 tagged_above=-999 required=5 tests=[AWL=-0.381,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_IMAGE_ONLY_28=1.561, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7q-Ft4JqGVT for <wgchairs@ietfa.amsl.com>; Tue, 30 Jul 2013 06:20:05 -0700 (PDT)
Received: from cdcipgw01.twcable.com (cdcipgw01.twcable.com [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id B761A21F86B2 for <wgchairs@ietf.org>; Tue, 30 Jul 2013 06:19:39 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,778,1367985600"; d="scan'208,217";a="35387355"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 30 Jul 2013 09:18:50 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 30 Jul 2013 09:19:37 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Jari Arkko <jari.arkko@piuha.net>, Working Group Chairs <wgchairs@ietf.org>
Date: Tue, 30 Jul 2013 09:19:50 -0400
Subject: Re: media at IETF-87
Thread-Topic: media at IETF-87
Thread-Index: Ac6NJ3AnRp4mpK9zS828UL/mi0KMTg==
Message-ID: <CE1D34C0.2745F%Lee.Howard@twcable.com>
In-Reply-To: <51F4398A-077D-4B46-90AE-66C9AE9C56F0@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CE1D34C02745FLeeHowardtwcablecom_"
MIME-Version: 1.0
Cc: Greg Wood <wood@isoc.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, 30 Jul 2013 13:20:28 -0000

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

Streaming Flash, OGG, and MP3 from dradio.de
[http://tnx.nl/legacy-ip-only.svg]



On 7/30/13 3:50 AM, "Jari Arkko" <jari.arkko@piuha.net<mailto:jari.arkko@pi=
uha.net>> wrote:

I wanted to let you know that there are a few press representatives among t=
he IETF crowd this week. For instance, Manfred Klolber and Peer Welchering =
will be reporting from the IETF to Forschung Aktuell on Radio Germany (http=
://de.wikipedia.org/wiki/Forschung_Aktuell), which seems to be a widely lis=
tened to program in Germany.

The reporters' plan is to sit in on some working group sessions and intervi=
ew a few folks. They are badged and will have pretty obvious microphones. T=
hey may be approaching you and asking about your technology, and you may be=
 interested in talking about all the great stuff you are developing :-)

Greg Wood, responsible for IETF and ISOC communications, has more details a=
nd can help you with any questions or other thoughts you may have with medi=
a interactions in general.

Jari



________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; font-family: Calibri, sans-serif; font-size: 14=
px; color: rgb(0, 0, 0); ">
<div>Streaming Flash, OGG, and MP3 from dradio.de</div>
<div><img style=3D"margin-top: 11px;" id=3D"irc_mi" src=3D"http://tnx.nl/le=
gacy-ip-only.svg" height=3D"410" width=3D"299"></div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>On 7/30/13 3:50 AM, &quot;Jari Arkko&quot; &lt;<a href=3D"mailto:jari.=
arkko@piuha.net">jari.arkko@piuha.net</a>&gt; wrote:</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>I wanted to let you know that there are a few press representatives am=
ong the IETF crowd this week. For instance, Manfred Klolber and Peer Welche=
ring will be reporting from the IETF to Forschung Aktuell on Radio Germany =
(<a href=3D"http://de.wikipedia.org/wiki/Forschung_Aktuell">http://de.wikip=
edia.org/wiki/Forschung_Aktuell</a>),
 which seems to be a widely listened to program in Germany.</div>
<div><br>
</div>
<div>The reporters' plan is to sit in on some working group sessions and in=
terview a few folks. They are badged and will have pretty obvious microphon=
es. They may be approaching you and asking about your technology, and you m=
ay be interested in talking about
 all the great stuff you are developing :-)</div>
<div><br>
</div>
<div>Greg Wood, responsible for IETF and ISOC communications, has more deta=
ils and can help you with any questions or other thoughts you may have with=
 media interactions in general.</div>
<div><br>
</div>
<div>Jari</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_CE1D34C02745FLeeHowardtwcablecom_--

From wesley.george@twcable.com  Wed Jul 31 00:58:35 2013
Return-Path: <wesley.george@twcable.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 9DBB211E8165 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 00:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.115
X-Spam-Level: 
X-Spam-Status: No, score=0.115 tagged_above=-999 required=5 tests=[AWL=-0.911,  BAYES_05=-1.11, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 UrQlFqPjGqMD for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 00:58:30 -0700 (PDT)
Received: from cdcipgw01.twcable.com (cdcipgw01.twcable.com [165.237.91.110]) by ietfa.amsl.com (Postfix) with ESMTP id 481E011E817C for <wgchairs@ietf.org>; Wed, 31 Jul 2013 00:58:30 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,785,1367985600"; d="scan'208,217";a="35566305"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdcipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 31 Jul 2013 03:57:41 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 31 Jul 2013 03:58:29 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Wed, 31 Jul 2013 03:58:29 -0400
Subject: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Topic: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Index: Ac6Nw7Bwx19WDaQNSBmX+4sR/fkVhQ==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2671C6CDFBB59E47B64C10B3E0BD592304395E4765PRVPEXVS15cor_"
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: Wed, 31 Jul 2013 07:58:36 -0000

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

I've now been in two different working group sessions where the chairs didn=
't ask for jabber scribes, but had remote participants  in the jabber room,=
 and I ended up becoming the jabber scribe by default.
Unless this has changed and someone didn't tell me, a identifying jabber sc=
ribe is REQUIRED prior to starting your session, whether you have other rem=
ote participation tools active (e.g. meetecho, webex) or not.

Thanks,

Wes George

Anything below this line has been added by my company's mail server, I have=
 no control over it.
-----------


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I&#8217;ve now been in two different working group s=
essions where the chairs didn&#8217;t ask for jabber scribes, but had remot=
e participants&nbsp; in the jabber room, and I ended up becoming the jabber=
 scribe by default.<o:p></o:p></p>
<p class=3D"MsoNormal">Unless this has changed and someone didn&#8217;t tel=
l me, a identifying jabber scribe is REQUIRED prior to starting your sessio=
n, whether you have other remote participation tools active (e.g. meetecho,=
 webex) or not.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Wes George<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#7F7F7F">Anything below this li=
ne has been added by my company&#8217;s mail server, I have no control over=
 it.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#7F7F7F">-----------<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_2671C6CDFBB59E47B64C10B3E0BD592304395E4765PRVPEXVS15cor_--

From cpignata@cisco.com  Wed Jul 31 01:07:57 2013
Return-Path: <cpignata@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 69A9E21F9F21 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.457
X-Spam-Level: 
X-Spam-Status: No, score=-110.457 tagged_above=-999 required=5 tests=[AWL=0.141, 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 PKuX8a8FyWEM for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:07:51 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 5686311E80EE for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:07:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6797; q=dns/txt; s=iport; t=1375258071; x=1376467671; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=jdEFJnG6pG6inIvicQp9UD5lr5VsxXL3pOXpIORVsG0=; b=GbQeto4UtQDgMV6gwVXiURbA9tQsgt/xY37TegqyGOFeu6W8iAkr+DXu KX4+yJ7IASE18RUlw+JzLneGIDLnEog5Gd7aOPp9otJhmbH3s+U819EJQ AFBoOyEoG23shhNE3VeQK+/qyI1ZB39wgIuPHIRGGoMCusbofbRAtmcHD s=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAL7E+FGtJXHA/2dsb2JhbABbgkJEgQW+HIEYFnSCJAEBAQMBcgcFCwIBCCIkMiUBAQQOBQgGh3wGuFKORoEHMQeDGHEDkBKBLZdsgxSBcTk
X-IronPort-AV: E=Sophos;i="4.89,785,1367971200";  d="asc'?scan'208,217";a="241674619"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 31 Jul 2013 08:07:51 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6V87orn001525 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Jul 2013 08:07:50 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.29]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Wed, 31 Jul 2013 03:07:50 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Topic: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Index: Ac6Nw7Bwx19WDaQNSBmX+4sR/fkVhQAK0RqA
Date: Wed, 31 Jul 2013 08:07:49 +0000
Message-ID: <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.106.13]
Content-Type: multipart/signed; boundary="Apple-Mail=_A9C2E719-6F06-4F22-8FD1-E9740A6CE998"; 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: Wed, 31 Jul 2013 08:07:57 -0000

--Apple-Mail=_A9C2E719-6F06-4F22-8FD1-E9740A6CE998
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_2BB8ADC3-CF6D-4AAD-85B6-37A5ECD99611"


--Apple-Mail=_2BB8ADC3-CF6D-4AAD-85B6-37A5ECD99611
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Is there a checklist to refer to in some wiki for things to do to enable =
remote participation? And is Jabber expected to be only unidirectional =
from the room towards remotes? I've also seen chairs relaying =
comments/questions from Jabber into the mike.

Thanks,

-- Carlos.

On Jul 31, 2013, at 9:58 AM, "George, Wes" <wesley.george@twcable.com>
 wrote:

> I=92ve now been in two different working group sessions where the =
chairs didn=92t ask for jabber scribes, but had remote participants  in =
the jabber room, and I ended up becoming the jabber scribe by default.
> Unless this has changed and someone didn=92t tell me, a identifying =
jabber scribe is REQUIRED prior to starting your session, whether you =
have other remote participation tools active (e.g. meetecho, webex) or =
not.
> =20
> Thanks,
> =20
> Wes George
> =20
> Anything below this line has been added by my company=92s mail server, =
I have no control over it.
> -----------
> =20
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.


--Apple-Mail=_2BB8ADC3-CF6D-4AAD-85B6-37A5ECD99611
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"><base href=3D"x-msg://1077/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Is there a checklist to refer =
to in some wiki for things to do to enable remote participation? And is =
Jabber expected to be only unidirectional from the room towards remotes? =
I've also seen chairs relaying comments/questions from Jabber into the =
mike.<div><br></div><div>Thanks,</div><div><br></div><div>-- =
Carlos.<br><div><br><div><div>On Jul 31, 2013, at 9:58 AM, "George, Wes" =
&lt;<a =
href=3D"mailto:wesley.george@twcable.com">wesley.george@twcable.com</a>&gt=
;</div><div>&nbsp;wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"font-family: =
Helvetica; font-size: medium; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">I=92ve now been in two different working group =
sessions where the chairs didn=92t ask for jabber scribes, but had =
remote participants&nbsp; in the jabber room, and I ended up becoming =
the jabber scribe by default.<o:p></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
">Unless this has changed and someone didn=92t tell me, a identifying =
jabber scribe is REQUIRED prior to starting your session, whether you =
have other remote participation tools active (e.g. meetecho, webex) or =
not.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Thanks,<o:p></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Wes =
George<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(127, 127, 127); ">Anything below this line has been added by my =
company=92s mail server, I have no control over =
it.<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(127, 127, 127); ">-----------<o:p></o:p></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div></div><br><hr><font =
face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its =
attachments may contain Time Warner Cable proprietary information, which =
is privileged, confidential, or subject to copyright belonging to Time =
Warner Cable. This E-mail is intended solely for the use of the =
individual or entity to which it is addressed. If you are not the =
intended recipient of this E-mail, you are hereby notified that any =
dissemination, distribution, copying, or action taken in relation to the =
contents of and attachments to this E-mail is strictly prohibited and =
may be unlawful. If you have received this E-mail in error, please =
notify the sender immediately and permanently delete the original and =
any copy of this E-mail and any =
printout.<br></font></div></blockquote></div><br></div></div></body></html=
>=

--Apple-Mail=_2BB8ADC3-CF6D-4AAD-85B6-37A5ECD99611--

--Apple-Mail=_A9C2E719-6F06-4F22-8FD1-E9740A6CE998
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

iEYEARECAAYFAlH4xdUACgkQtfDPGTp3USx/lwCguWTw9n1+8wZ2M0oZqnbYowfx
yrYAoKNIxRwNHs4LaBA91MnIbJNMrAhu
=cu9I
-----END PGP SIGNATURE-----

--Apple-Mail=_A9C2E719-6F06-4F22-8FD1-E9740A6CE998--

From yaronf.ietf@gmail.com  Wed Jul 31 01:09:47 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 1AF1A21F9E05 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCcNM00VKCV2 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:09:46 -0700 (PDT)
Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE8521F9CAC for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:09:45 -0700 (PDT)
Received: by mail-bk0-f41.google.com with SMTP id jc10so125828bkc.14 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:09:44 -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=3EhfRguRNGstK38C5c36DuDkN3tcJM1HN7ii2VlqnxQ=; b=F0yxxo49WyjZ8DyYMcYoXdSUIG8F3nIynO+aT3tPPSJrchE4s0CdgcbuFCb6wpsyRL SJzfvb5WbOVuE2eddu5+RruWBsE8fbDfWUnYKj8I2Wnjvp1JSRowMhAX88EajQj37nMJ wI1Ta8+AabiQBYXSLJRpJ/kBl0xQNZQ5GmvGDs/dcvLXe1o9cfABaywIcCTZeMseGM39 bHFKy9GNswdBd7dE9pchKdVIvTfq/pPj7xJjjAQAZeLCrKMu4VZbEufDbsNsvU5X/dQq /qloag0uEQENjlmssG1HgT7JlaGJmVEob3Y1OEZqVr68nZvVJGJI7mLlNxY+p6IXE0m+ hELA==
X-Received: by 10.205.22.138 with SMTP id qw10mr9129033bkb.29.1375258184097; Wed, 31 Jul 2013 01:09:44 -0700 (PDT)
Received: from [192.168.1.132] (e179047018.adsl.alicedsl.de. [85.179.47.18]) by mx.google.com with ESMTPSA id px7sm81788bkb.9.2013.07.31.01.09.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 31 Jul 2013 01:09:43 -0700 (PDT)
Message-ID: <51F8C646.5060509@gmail.com>
Date: Wed, 31 Jul 2013 10:09:42 +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: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com> <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>
In-Reply-To: <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 8bit
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, 31 Jul 2013 08:09:47 -0000

Yes, it's also the jabber scribe's job to "channel" jabber comments to 
the room. Some would say this is even more important than the other 
direction.

Thanks,
	Yaron

On 2013-07-31 10:07, Carlos Pignataro (cpignata) wrote:
> Is there a checklist to refer to in some wiki for things to do to enable
> remote participation? And is Jabber expected to be only unidirectional
> from the room towards remotes? I've also seen chairs relaying
> comments/questions from Jabber into the mike.
>
> Thanks,
>
> -- Carlos.
>
> On Jul 31, 2013, at 9:58 AM, "George, Wes" <wesley.george@twcable.com
> <mailto:wesley.george@twcable.com>>
>   wrote:
>
>> I’ve now been in two different working group sessions where the chairs
>> didn’t ask for jabber scribes, but had remote participants  in the
>> jabber room, and I ended up becoming the jabber scribe by default.
>> Unless this has changed and someone didn’t tell me, a identifying
>> jabber scribe is REQUIRED prior to starting your session, whether you
>> have other remote participation tools active (e.g. meetecho, webex) or
>> not.
>> Thanks,
>> Wes George
>> Anything below this line has been added by my company’s mail server, I
>> have no control over it.
>> -----------
>>
>> ------------------------------------------------------------------------
>> This E-mail and any of its attachments may contain Time Warner Cable
>> proprietary information, which is privileged, confidential, or subject
>> to copyright belonging to Time Warner Cable. This E-mail is intended
>> solely for the use of the individual or entity to which it is
>> addressed. If you are not the intended recipient of this E-mail, you
>> are hereby notified that any dissemination, distribution, copying, or
>> action taken in relation to the contents of and attachments to this
>> E-mail is strictly prohibited and may be unlawful. If you have
>> received this E-mail in error, please notify the sender immediately
>> and permanently delete the original and any copy of this E-mail and
>> any printout.
>

From wesley.george@twcable.com  Wed Jul 31 01:14:33 2013
Return-Path: <wesley.george@twcable.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 05D2F21F9E96 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.538
X-Spam-Level: 
X-Spam-Status: No, score=-0.538 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 lQeDXImPqFoY for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:14:26 -0700 (PDT)
Received: from cdcipgw02.twcable.com (cdcipgw02.twcable.com [165.237.91.111]) by ietfa.amsl.com (Postfix) with ESMTP id 4D06121E80BE for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:13:15 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,785,1367985600"; d="scan'208,217";a="29284623"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdcipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 31 Jul 2013 04:11:46 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 31 Jul 2013 04:13:14 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Date: Wed, 31 Jul 2013 04:13:14 -0400
Subject: RE: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Topic: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Index: Ac6Nw7Bwx19WDaQNSBmX+4sR/fkVhQAK0RqAAApqHYA=
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com> <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>
In-Reply-To: <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2671C6CDFBB59E47B64C10B3E0BD592304395E4766PRVPEXVS15cor_"
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: Wed, 31 Jul 2013 08:14:34 -0000
X-List-Received-Date: Wed, 31 Jul 2013 08:14:34 -0000

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

There's been some discussion about getting better documentation out on the =
WG chairs' wiki or other places to cover this (see the thread on 87attendee=
s list), I've volunteered to help.

Jabber is usually two way, so remotes can proxy comments to the mic, and to=
 supplement the audio feed and sure, chairs can monitor jabber themselves, =
if in fact they commit to doing that consistently.

Thanks,

Wes

From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com]
Sent: Wednesday, July 31, 2013 4:08 AM
To: George, Wes
Cc: wgchairs@ietf.org
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!

* PGP Signed by an unknown key
Is there a checklist to refer to in some wiki for things to do to enable re=
mote participation? And is Jabber expected to be only unidirectional from t=
he room towards remotes? I've also seen chairs relaying comments/questions =
from Jabber into the mike.

Thanks,

-- Carlos.

On Jul 31, 2013, at 9:58 AM, "George, Wes" <wesley.george@twcable.com<mailt=
o:wesley.george@twcable.com>>
 wrote:


I've now been in two different working group sessions where the chairs didn=
't ask for jabber scribes, but had remote participants  in the jabber room,=
 and I ended up becoming the jabber scribe by default.
Unless this has changed and someone didn't tell me, a identifying jabber sc=
ribe is REQUIRED prior to starting your session, whether you have other rem=
ote participation tools active (e.g. meetecho, webex) or not.

Thanks,

Wes George

Anything below this line has been added by my company's mail server, I have=
 no control over it.
-----------


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

* Unknown Key
* 0x3A77512C


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><base href=3D"x-msg://1077/"><!--[if !mso]><=
style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Franklin Gothic Medium";
	panose-1:2 11 6 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There&#82=
17;s been some discussion about getting better documentation out on the WG =
chairs&#8217; wiki or other places to cover this (see the thread on 87atten=
dees list), I&#8217;ve volunteered to help.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>Jabber is usually two way, so remotes can proxy comments to the mic, and t=
o supplement the audio feed and sure, chairs can monitor jabber themselves,=
 if in fact they commit to doing that consistently. <o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>Wes<o:p></o:p></span></=
p></div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=
=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><di=
v><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif"'> Carlos Pignataro (cpignata) [mailto:cpi=
gnata@cisco.com] <br><b>Sent:</b> Wednesday, July 31, 2013 4:08 AM<br><b>To=
:</b> George, Wes<br><b>Cc:</b> wgchairs@ietf.org<br><b>Subject:</b> Re: Re=
minder - ASK FOR JABBER SCRIBES!!<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><div style=3D'border:solid #E5CFC3 1.5pt;=
border-bottom:solid #E5CFC3 1.0pt;padding:4.0pt 4.0pt 4.0pt 4.0pt'><p class=
=3DMsoNormal style=3D'background:#F2E2DA'><span style=3D'font-size:10.0pt;f=
ont-family:"Franklin Gothic Medium","sans-serif";color:black'>* PGP Signed =
by an unknown key<o:p></o:p></span></p></div><div style=3D'border-top:1.0pt=
;border-left:1.5pt;border-bottom:1.0pt;border-right:1.5pt;border-color:#E5C=
FC3;border-style:solid;padding:14.0pt 14.0pt 14.0pt 17.0pt'><p class=3DMsoN=
ormal>Is there a checklist to refer to in some wiki for things to do to ena=
ble remote participation? And is Jabber expected to be only unidirectional =
from the room towards remotes? I've also seen chairs relaying comments/ques=
tions from Jabber into the mike.<o:p></o:p></p><div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Thanks,<o:p></o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMs=
oNormal>-- Carlos.<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><div><div><p class=3DMsoNormal>On Jul 31, 2013, at 9:58 AM, &quot;Geor=
ge, Wes&quot; &lt;<a href=3D"mailto:wesley.george@twcable.com">wesley.georg=
e@twcable.com</a>&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal>&nbsp;w=
rote:<o:p></o:p></p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div>=
<div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif"'>I&#8217;ve now been in two different working group sessi=
ons where the chairs didn&#8217;t ask for jabber scribes, but had remote pa=
rticipants&nbsp; in the jabber room, and I ended up becoming the jabber scr=
ibe by default.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Unless this h=
as changed and someone didn&#8217;t tell me, a identifying jabber scribe is=
 REQUIRED prior to starting your session, whether you have other remote par=
ticipation tools active (e.g. meetecho, webex) or not.<o:p></o:p></span></p=
></div><div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif"'>Thanks,<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p></o:=
p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'>Wes George<o:p></o:p></span></p></div=
><div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#7F7F7F'>Anything below this line has been added by my company&#8217;s m=
ail server, I have no control over it.</span><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#7F7F7F'>-----------</span><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif"'><o:p></o:p></span></p></div><div><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif"'>&nbsp;<o:p></o:p></span></p></div><p class=3DMsoNormal><span style=
=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><o:p>&nbsp;</o:p=
></span></p><div class=3DMsoNormal align=3Dcenter style=3D'text-align:cente=
r'><span style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><h=
r size=3D2 width=3D"100%" align=3Dcenter></span></div><p class=3DMsoNormal>=
<span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'=
>This E-mail and any of its attachments may contain Time Warner Cable propr=
ietary information, which is privileged, confidential, or subject to copyri=
ght belonging to Time Warner Cable. This E-mail is intended solely for the =
use of the individual or entity to which it is addressed. If you are not th=
e intended recipient of this E-mail, you are hereby notified that any disse=
mination, distribution, copying, or action taken in relation to the content=
s of and attachments to this E-mail is strictly prohibited and may be unlaw=
ful. If you have received this E-mail in error, please notify the sender im=
mediately and permanently delete the original and any copy of this E-mail a=
nd any printout.</span><span style=3D'font-size:13.5pt;font-family:"Helveti=
ca","sans-serif"'><o:p></o:p></span></p></div></div><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p></div></div></div><div style=3D'border:solid #E5CFC3 1.5=
pt;border-top:solid #E5CFC3 1.0pt;padding:4.0pt 4.0pt 4.0pt 4.0pt'><p class=
=3DMsoNormal style=3D'background:#F2E2DA'><span style=3D'font-size:10.0pt;f=
ont-family:"Franklin Gothic Medium","sans-serif";color:black'>* Unknown Key=
<br>* 0x3A77512C<o:p></o:p></span></p></div><p class=3DMsoNormal>&nbsp;<o:p=
></o:p></p></div></div></body></html>=

--_000_2671C6CDFBB59E47B64C10B3E0BD592304395E4766PRVPEXVS15cor_--

From barryleiba.mailing.lists@gmail.com  Wed Jul 31 01:43:41 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 0C77B21E812D for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.972
X-Spam-Level: 
X-Spam-Status: No, score=-101.972 tagged_above=-999 required=5 tests=[AWL=0.006, 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 gwJRhceaywzF for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 01:43:28 -0700 (PDT)
Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id B8EC821F9F44 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:36:12 -0700 (PDT)
Received: by mail-vb0-f51.google.com with SMTP id x16so402811vbf.24 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 01:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/JwfqSR2r/DIA+i02PND1eb2O0x5JZooeXvNKKPOJ4E=; b=td0b1QzrSCOHIHdvtJ1Dk6rPXc5wIZYAG50unQdpuH6jdc7d5+ZaHbesr9gXqmYPF4 LeruF3wPuWJ+hd+LU18Euc2CTa57ZdJXjZMDK95PGU8voOyIBDwozHLwt4LbBNcI4O5d T2hxF66IIXBHuF50DU3kG6avtxNvkgUwGsr6YsBt9nmQPgj3AucABuTiTIQh1pY2s+eD YxgQ6I2AoiTR9NMKl3FAJLK3L9Uhv8M4U/JLhej2csoHqU/0jf14or1+JAF/jgMKt9dn H4xD4oOvPOe8nMcs0U9m97w5FhPC32FvwJGj4BvAJpahXyk1RN2azKWaaitvzluqAPxQ ETdQ==
MIME-Version: 1.0
X-Received: by 10.58.207.195 with SMTP id ly3mr28395481vec.77.1375259761165; Wed, 31 Jul 2013 01:36:01 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 01:36:01 -0700 (PDT)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com> <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com> <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com>
Date: Wed, 31 Jul 2013 04:36:01 -0400
X-Google-Sender-Auth: bOxIXPReASFUvKhR1lhS4_ZuSOk
Message-ID: <CAC4RtVD7Go0qV05ic=yj0OFuZ+CPoT67SUPtoBcn0p7E13aBmg@mail.gmail.com>
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
From: Barry Leiba <barryleiba@computer.org>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, "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, 31 Jul 2013 08:43:55 -0000

> There=92s been some discussion about getting better documentation out on =
the
> WG chairs=92 wiki

It's a wiki, and you are empowered.  Add a section or a page for
"Checklist for working group meeting sessions", and put in a start.
Encourage other chairs to tweak it.  Take the bull by the horns.

Barry

From prvs=1924aa2a34=sandra.murphy@parsons.com  Wed Jul 31 02:22:00 2013
Return-Path: <prvs=1924aa2a34=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 F1FDC21F9815 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.015,  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 ZRD6Z5aSZnTh for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:21:17 -0700 (PDT)
Received: from txdal11mx03.parsons.com (txdal11mx03.parsons.com [206.219.199.111]) by ietfa.amsl.com (Postfix) with ESMTP id A598321F99CF for <wgchairs@ietf.org>; Wed, 31 Jul 2013 02:17:35 -0700 (PDT)
Received: from pps.filterd (txdal11mx03 [127.0.0.1]) by txdal11mx03.parsons.com (8.14.5/8.14.5) with SMTP id r6V9FNcQ016114;  Wed, 31 Jul 2013 04:17:29 -0500
Received: from m4.sparta.com (m4.sparta.com [157.185.61.2]) by txdal11mx03.parsons.com with ESMTP id 1dxvaugrm0-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 31 Jul 2013 04:17:28 -0500
Received: from Beta5.sparta.com ([10.62.8.21]) by M4.sparta.com (8.14.4/8.14.4) with ESMTP id r6V9HFVF028419; Wed, 31 Jul 2013 04:17:15 -0500
Received: from CVA-HUB002.centreville.ads.sparta.com ([10.62.108.29]) by Beta5.sparta.com (8.13.8/8.13.8) with ESMTP id r6V9HF4P020713; Wed, 31 Jul 2013 04:17:15 -0500
Received: from CVA-MB002.centreville.ads.sparta.com ([fe80::6046:a82a:c500:c9ad]) by CVA-HUB002.centreville.ads.sparta.com ([fe80::9817:c0c5:e172:9d1c%11]) with mapi id 14.02.0342.003; Wed, 31 Jul 2013 05:17:15 -0400
From: "Murphy, Sandra" <Sandra.Murphy@parsons.com>
To: "George, Wes" <wesley.george@twcable.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Subject: RE: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Topic: Reminder - ASK FOR JABBER SCRIBES!!
Thread-Index: Ac6Nw7Bwx19WDaQNSBmX+4sR/fkVhQAK0RqAAApqHYD//2vJOg==
Date: Wed, 31 Jul 2013 09:17:13 +0000
Message-ID: <24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82@CVA-MB002.centreville.ads.sparta.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com> <95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>, <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.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_24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82CVAMB002centrev_"
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-07-31_04:2013-07-31, 2013-07-31, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=3.21409565628983e-14 kscore.compositescore=0 circleOfTrustscore=24.5875043252163 compositescore=0.0230061268206222 urlsuspect_oldscore=0.230061268206222 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=7040 rbsscore=0.0230061268206222 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-1307310033
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, 31 Jul 2013 09:22:02 -0000

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

NOT relaying remote comments from jabber to the room pretty much disenfranc=
hises the remote participants.  They might as well listen to the audio and =
view the slides as some time of their choosing.

It is really important for the jabber remote comments to be relayed to the =
room.

--Sandy
________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of Ge=
orge, Wes [wesley.george@twcable.com]
Sent: Wednesday, July 31, 2013 4:13 AM
To: Carlos Pignataro (cpignata)
Cc: wgchairs@ietf.org
Subject: RE: Reminder - ASK FOR JABBER SCRIBES!!

There=92s been some discussion about getting better documentation out on th=
e WG chairs=92 wiki or other places to cover this (see the thread on 87atte=
ndees list), I=92ve volunteered to help.

Jabber is usually two way, so remotes can proxy comments to the mic, and to=
 supplement the audio feed and sure, chairs can monitor jabber themselves, =
if in fact they commit to doing that consistently.

Thanks,

Wes

From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com]
Sent: Wednesday, July 31, 2013 4:08 AM
To: George, Wes
Cc: wgchairs@ietf.org
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!

* PGP Signed by an unknown key
Is there a checklist to refer to in some wiki for things to do to enable re=
mote participation? And is Jabber expected to be only unidirectional from t=
he room towards remotes? I've also seen chairs relaying comments/questions =
from Jabber into the mike.

Thanks,

-- Carlos.

On Jul 31, 2013, at 9:58 AM, "George, Wes" <wesley.george@twcable.com<mailt=
o:wesley.george@twcable.com>>
 wrote:


I=92ve now been in two different working group sessions where the chairs di=
dn=92t ask for jabber scribes, but had remote participants  in the jabber r=
oom, and I ended up becoming the jabber scribe by default.
Unless this has changed and someone didn=92t tell me, a identifying jabber =
scribe is REQUIRED prior to starting your session, whether you have other r=
emote participation tools active (e.g. meetecho, webex) or not.

Thanks,

Wes George

Anything below this line has been added by my company=92s mail server, I ha=
ve no control over it.
-----------


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

* Unknown Key
* 0x3A77512C


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

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style>=0A=
<!--=0A=
@font-face=0A=
	{font-family:Helvetica}=0A=
@font-face=0A=
	{font-family:Helvetica}=0A=
@font-face=0A=
	{font-family:Calibri}=0A=
@font-face=0A=
	{font-family:Tahoma}=0A=
@font-face=0A=
	{font-family:"Franklin Gothic Medium"}=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:12.0pt;=0A=
	font-family:"Times New Roman","serif"}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline}=0A=
a:visited, span.MsoHyperlinkFollowed=0A=
	{color:purple;=0A=
	text-decoration:underline}=0A=
span.EmailStyle17=0A=
	{font-family:"Calibri","sans-serif";=0A=
	color:#1F497D}=0A=
.MsoChpDefault=0A=
	{font-size:10.0pt}=0A=
@page WordSection1=0A=
	{margin:1.0in 1.0in 1.0in 1.0in}=0A=
-->=0A=
</style><style type=3D"text/css" id=3D"owaParaStyle"></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" fpstyle=3D"1" ocsi=3D"0=
">
<div style=3D"direction: ltr;font-family: Arial;color: #000000;font-size: 1=
0pt;">NOT relaying remote comments from jabber to the room pretty much dise=
nfranchises the remote participants. &nbsp;They might as well listen to the=
 audio and view the slides as some time
 of their choosing.
<div><br>
</div>
<div>It is really important for the jabber remote comments to be relayed to=
 the room.</div>
<div><br>
</div>
<div>--Sandy<br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div id=3D"divRpF424955" 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 George, Wes [wesley.george@twcable.com]<br=
>
<b>Sent:</b> Wednesday, July 31, 2013 4:13 AM<br>
<b>To:</b> Carlos Pignataro (cpignata)<br>
<b>Cc:</b> wgchairs@ietf.org<br>
<b>Subject:</b> RE: Reminder - ASK FOR JABBER SCRIBES!!<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">There=92s been some dis=
cussion about getting better documentation out on the WG chairs=92 wiki or =
other places to cover this (see the thread on 87attendees list),
 I=92ve volunteered to help.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Jabber is usually two w=
ay, so remotes can proxy comments to the mic, and to supplement the audio f=
eed and sure, chairs can monitor jabber themselves, if in
 fact they commit to doing that consistently. </span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Thanks,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Wes</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0in 0in 0i=
n 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Carlos=
 Pignataro (cpignata) [mailto:cpignata@cisco.com]
<br>
<b>Sent:</b> Wednesday, July 31, 2013 4:08 AM<br>
<b>To:</b> George, Wes<br>
<b>Cc:</b> wgchairs@ietf.org<br>
<b>Subject:</b> Re: Reminder - ASK FOR JABBER SCRIBES!!</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div style=3D"border:solid #E5CFC3 1.5pt; border-bottom:solid #E5CFC3 1.0pt=
; padding:4.0pt 4.0pt 4.0pt 4.0pt">
<p class=3D"MsoNormal" style=3D"background:#F2E2DA"><span style=3D"font-siz=
e:10.0pt; font-family:&quot;Franklin Gothic Medium&quot;,&quot;sans-serif&q=
uot;; color:black">* PGP Signed by an unknown key</span></p>
</div>
<div style=3D"border-top:1.0pt; border-left:1.5pt; border-bottom:1.0pt; bor=
der-right:1.5pt; border-color:#E5CFC3; border-style:solid; padding:14.0pt 1=
4.0pt 14.0pt 17.0pt">
<p class=3D"MsoNormal">Is there a checklist to refer to in some wiki for th=
ings to do to enable remote participation? And is Jabber expected to be onl=
y unidirectional from the room towards remotes? I've also seen chairs relay=
ing comments/questions from Jabber
 into the mike.</p>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">-- Carlos.</p>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div>
<p class=3D"MsoNormal">On Jul 31, 2013, at 9:58 AM, &quot;George, Wes&quot;=
 &lt;<a href=3D"mailto:wesley.george@twcable.com" target=3D"_blank">wesley.=
george@twcable.com</a>&gt;</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;wrote:</p>
</div>
<p class=3D"MsoNormal"><br>
<br>
</p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">I=92ve now been in two different worki=
ng group sessions where the chairs didn=92t ask for jabber scribes, but had=
 remote participants&nbsp; in the jabber room, and I ended up becoming
 the jabber scribe by default.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">Unless this has changed and someone di=
dn=92t tell me, a identifying jabber scribe is REQUIRED prior to starting y=
our session, whether you have other remote participation tools
 active (e.g. meetecho, webex) or not.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">Thanks,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">Wes George</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#7F7F7F">Anything below this lin=
e has been added by my company=92s mail server, I have no control over it.<=
/span><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#7F7F7F">-----------</span><span=
 style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt; font-family:&quot;H=
elvetica&quot;,&quot;sans-serif&quot;">&nbsp;</span></p>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-size:13.5pt; font-family:&quot;Helvetica&quot;,&quot;sans-se=
rif&quot;">
<hr size=3D"2" width=3D"100%" align=3D"center">
</span></div>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt; font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;; color:gray">This E-mail and any of its at=
tachments may contain Time Warner Cable proprietary information, which is p=
rivileged, confidential, or subject to copyright belonging
 to Time Warner Cable. This E-mail is intended solely for the use of the in=
dividual or entity to which it is addressed. If you are not the intended re=
cipient of this E-mail, you are hereby notified that any dissemination, dis=
tribution, copying, or action taken
 in relation to the contents of and attachments to this E-mail is strictly =
prohibited and may be unlawful. If you have received this E-mail in error, =
please notify the sender immediately and permanently delete the original an=
d any copy of this E-mail and any
 printout.</span><span style=3D"font-size:13.5pt; font-family:&quot;Helveti=
ca&quot;,&quot;sans-serif&quot;"></span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
<div style=3D"border:solid #E5CFC3 1.5pt; border-top:solid #E5CFC3 1.0pt; p=
adding:4.0pt 4.0pt 4.0pt 4.0pt">
<p class=3D"MsoNormal" style=3D"background:#F2E2DA"><span style=3D"font-siz=
e:10.0pt; font-family:&quot;Franklin Gothic Medium&quot;,&quot;sans-serif&q=
uot;; color:black">* Unknown Key<br>
* 0x3A77512C</span></p>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82CVAMB002centrev_--

From jhaas@slice.pfrc.org  Wed Jul 31 02:26:23 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 811A321F9EFC for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TabKO8M5RI3j for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:26:15 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 40DC621F8EE6 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 02:26:07 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 9ACD7C2A5; Wed, 31 Jul 2013 05:26:05 -0400 (EDT)
Date: Wed, 31 Jul 2013 05:26:05 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: wgchairs@ietf.org
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
Message-ID: <20130731092605.GA29173@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82@CVA-MB002.centreville.ads.sparta.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: Wed, 31 Jul 2013 09:26:24 -0000

On Wed, Jul 31, 2013 at 09:17:13AM +0000, Murphy, Sandra wrote:
> NOT relaying remote comments from jabber to the room pretty much disenfranchises the remote participants.  They might as well listen to the audio and view the slides as some time of their choosing.
> 
> It is really important for the jabber remote comments to be relayed to the room.

Also, when the scribe is a regular WG participant, ensure you permit them
time to interact with the mic on their own.  I've been cut-off from mic
comments in two different due to deferring comments toward the end of a line
so I could either scribe or take minutes.  I now actively avoid
being scribe in WGs when I intend to actively participate in the session.

-- Jeff

From joelja@bogus.com  Wed Jul 31 02:34:57 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 EAD2A21F9EEE for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dr8G-QOyaCrH for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 02:34:56 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 60A0421F9EB6 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 02:34:49 -0700 (PDT)
Received: from dhcp-603a.meeting.ietf.org (dhcp-603a.meeting.ietf.org [130.129.96.58]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r6V9YWZY082451 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 31 Jul 2013 09:34:34 GMT (envelope-from joelja@bogus.com)
Message-ID: <51F8DA27.2080807@bogus.com>
Date: Wed, 31 Jul 2013 11:34:31 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: "Murphy, Sandra" <Sandra.Murphy@parsons.com>, "George, Wes" <wesley.george@twcable.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
References: <2671C6CDFBB59E47B64C10B3E0BD592304395E4765@PRVPEXVS15.corp.twcable.com>	<95067C434CE250468B77282634C96ED322D68935@xmb-aln-x02.cisco.com>, <2671C6CDFBB59E47B64C10B3E0BD592304395E4766@PRVPEXVS15.corp.twcable.com> <24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82@CVA-MB002.centreville.ads.sparta.com>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F6749C8E82@CVA-MB002.centreville.ads.sparta.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 31 Jul 2013 09:34:35 +0000 (UTC)
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, 31 Jul 2013 09:34:57 -0000

On 7/31/13 11:17 AM, Murphy, Sandra wrote:
> NOT relaying remote comments from jabber to the room pretty much
> disenfranchises the remote participants.  They might as well listen to
> the audio and view the slides as some time of their choosing.
>
> It is really important for the jabber remote comments to be relayed to
> the room.
it is helpful if as a remote participant that you state that you would
like the comment taken to the mic.

managing the queue at the microphones is effortful, jabber scribes are
trying to transcribe, and the chairs are juggling.
>
> --Sandy
> ------------------------------------------------------------------------
> *From:* wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on
> behalf of George, Wes [wesley.george@twcable.com]
> *Sent:* Wednesday, July 31, 2013 4:13 AM
> *To:* Carlos Pignataro (cpignata)
> *Cc:* wgchairs@ietf.org
> *Subject:* RE: Reminder - ASK FOR JABBER SCRIBES!!
>
> There’s been some discussion about getting better documentation out on
> the WG chairs’ wiki or other places to cover this (see the thread on
> 87attendees list), I’ve volunteered to help.
>
>  
>
> Jabber is usually two way, so remotes can proxy comments to the mic,
> and to supplement the audio feed and sure, chairs can monitor jabber
> themselves, if in fact they commit to doing that consistently.
>
>  
>
> Thanks,
>
>  
>
> Wes
>
>  
>
> *From:*Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com]
> *Sent:* Wednesday, July 31, 2013 4:08 AM
> *To:* George, Wes
> *Cc:* wgchairs@ietf.org
> *Subject:* Re: Reminder - ASK FOR JABBER SCRIBES!!
>
>  
>
> * PGP Signed by an unknown key
>
> Is there a checklist to refer to in some wiki for things to do to
> enable remote participation? And is Jabber expected to be only
> unidirectional from the room towards remotes? I've also seen chairs
> relaying comments/questions from Jabber into the mike.
>
>  
>
> Thanks,
>
>  
>
> -- Carlos.
>
>  
>
> On Jul 31, 2013, at 9:58 AM, "George, Wes" <wesley.george@twcable.com
> <mailto:wesley.george@twcable.com>>
>
>  wrote:
>
>
>
> I’ve now been in two different working group sessions where the chairs
> didn’t ask for jabber scribes, but had remote participants  in the
> jabber room, and I ended up becoming the jabber scribe by default.
>
> Unless this has changed and someone didn’t tell me, a identifying
> jabber scribe is REQUIRED prior to starting your session, whether you
> have other remote participation tools active (e.g. meetecho, webex) or
> not.
>
>  
>
> Thanks,
>
>  
>
> Wes George
>
>  
>
> Anything below this line has been added by my company’s mail server, I
> have no control over it.
>
> -----------
>
>  
>
>  
>
> ------------------------------------------------------------------------
>
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
> to copyright belonging to Time Warner Cable. This E-mail is intended
> solely for the use of the individual or entity to which it is
> addressed. If you are not the intended recipient of this E-mail, you
> are hereby notified that any dissemination, distribution, copying, or
> action taken in relation to the contents of and attachments to this
> E-mail is strictly prohibited and may be unlawful. If you have
> received this E-mail in error, please notify the sender immediately
> and permanently delete the original and any copy of this E-mail and
> any printout.
>
>  
>
> * Unknown Key
> * 0x3A77512C
>
>  
>


From peter@denic.de  Wed Jul 31 03:25:05 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 D478411E80DF for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 03:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DvWL7Gg6DFUd for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 03:25:05 -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 4DBE211E80C5 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 03:25:05 -0700 (PDT)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp   id 1V4TaZ-0000o9-VC; Wed, 31 Jul 2013 12:25:03 +0200
Received: from localhost by x27.adm.denic.de with local  id 1V4TaZ-0007xC-Rl; Wed, 31 Jul 2013 12:25:03 +0200
Date: Wed, 31 Jul 2013 12:25:03 +0200
From: Peter Koch <pk@ISOC.DE>
To: wgchairs@ietf.org
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
Message-ID: <20130731102503.GS23086@x28.adm.denic.de>
Mail-Followup-To: wgchairs@ietf.org
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130731092605.GA29173@pfrc>
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: Wed, 31 Jul 2013 10:25:06 -0000

On Wed, Jul 31, 2013 at 05:26:05AM -0400, Jeffrey Haas wrote:

> Also, when the scribe is a regular WG participant, ensure you permit them
> time to interact with the mic on their own.  I've been cut-off from mic

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.  That has occasionally even been
easier than to find a single volunteer.  So far, the shared responsibility
wasn't a problem in and of itself.

-Peter

From duerst@it.aoyama.ac.jp  Wed Jul 31 03:53:32 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 C633F11E80EC for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 03:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.53
X-Spam-Level: 
X-Spam-Status: No, score=-103.53 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1bIMyAFiALs for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 03:53:26 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0886F21F9C69 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 03:53:25 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id r6VArLvr017626 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 19:53:21 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 1a5e_3e49_6a86831a_f9cf_11e2_a4ef_001e6722eec2; Wed, 31 Jul 2013 19:53:21 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id BBDF6BF54B for <wgchairs@ietf.org>; Wed, 31 Jul 2013 19:51:16 +0900 (JST)
Message-ID: <51F8EC91.50209@it.aoyama.ac.jp>
Date: Wed, 31 Jul 2013 19:53:05 +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: wgchairs@ietf.org
Subject: Re: Reminder - ASK FOR JABBER SCRIBES!!
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>
In-Reply-To: <20130731102503.GS23086@x28.adm.denic.de>
Content-Type: text/plain; charset=UTF-8; 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: Wed, 31 Jul 2013 10:53:32 -0000

On 2013/07/31 19:25, Peter Koch 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.

Regards,   Martin.

>  That has occasionally even been
> easier than to find a single volunteer.  So far, the shared responsibility
> wasn't a problem in and of itself.
>
> -Peter
>

From bew@cisco.com  Wed Jul 31 08:07:36 2013
Return-Path: <bew@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 34BF021F9E7C for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.832
X-Spam-Level: 
X-Spam-Status: No, score=-110.832 tagged_above=-999 required=5 tests=[AWL=-0.232, 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 PbxDNoz3vfKp for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:07:31 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id B5BE021F9E6C for <wgchairs@ietf.org>; Wed, 31 Jul 2013 08:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1228; q=dns/txt; s=iport; t=1375283251; x=1376492851; h=from:content-transfer-encoding:subject:date:references: to:message-id:mime-version; bh=coaxznBYkhi3qIML33HJvwSUH2VChAs4KZjkSwgKvng=; b=A7hexM7JIoEdsNrlDX4Z8zN9ILhyZJ9GlldrOlt/ebNf8TyRWwIwNVO+ TibCG6tR7b+yFq0xlpLVLLLY8oNMYwyd0TFl6BW0jp4DJOFMqN2084abE XAFE9H6rkj7vr4l1aU2HUrXjfLXmdr/WBs7GZXuTf0iMWNG8o6psCoxum 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigFADMn+VGrRDoJ/2dsb2JhbABYA4MGNQG+bIEYFnSCJAEBAQMBAQEBNzQQCxwDAQIvJyYCCAYTiAoFDbhpBI4/gTgdC4MHcwOXX4YjiyqDFjqBNQ
X-IronPort-AV: E=Sophos;i="4.89,788,1367971200"; d="scan'208";a="84993110"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 31 Jul 2013 15:07:30 +0000
Received: from [10.21.70.187] ([10.21.70.187]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6VF7Rte010679 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Wed, 31 Jul 2013 15:07:29 GMT
From: Brian Weis <bew@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Fwd: [87attendees] Slide numbers
Date: Wed, 31 Jul 2013 17:07:26 +0200
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com>
To: Working Group Chairs <wgchairs@ietf.org>
Message-Id: <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
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, 31 Jul 2013 15:07:36 -0000

Forwarding this to the WG chairs list. This is a serious issue for =
scribes and Jabber scribes in particular. I make it a point to remind =
presenters in my WG that they need to include slide numbers. Usually =
it's most efficient when giving them instructions about the deadline by =
which I need the slides. And when they still forget (3 presentations =
this meeting) I either add them myself and inform the authors or =
(especially in the case of PDF) tell them to give them to me again with =
page numbers.

Brian

Begin forwarded message:

> From: Yoav Nir <ynir@checkpoint.com>
> Subject: [87attendees] Slide numbers
> Date: July 31, 2013 4:24:01 PM GMT+02:00
> To: "<87attendees@ietf.org>" <87attendees@ietf.org>
>=20
> I've seen way too many slides this week with no slide numbers. Might =
be mostly too late now, but we should remember to remind people two =
weeks before the meeting that slides need numbers.
>=20
> _______________________________________________
> 87attendees mailing list
> 87attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/87attendees

--=20
Brian Weis
Security, Enterprise Networking Group, Cisco Systems
Telephone: +1 408 526 4796
Email: bew@cisco.com


From stpeter@stpeter.im  Wed Jul 31 08:18:18 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 A2AB321F9CA4 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:18:17 -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 TJBj4Eu3LGX1 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:18:11 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D79C121F9D05 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 08:18:10 -0700 (PDT)
Received: from che-vpn-cluster-2-456.cisco.com (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6C7B340046; Wed, 31 Jul 2013 09:20:25 -0600 (MDT)
Message-ID: <51F92AAF.8070706@stpeter.im>
Date: Wed, 31 Jul 2013 17:18:07 +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: Brian Weis <bew@cisco.com>
Subject: Re: Fwd: [87attendees] Slide numbers
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
In-Reply-To: <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Working Group 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, 31 Jul 2013 15:18:18 -0000

A big +1.

On 7/31/13 5:07 PM, Brian Weis wrote:
> Forwarding this to the WG chairs list. This is a serious issue for scribes and Jabber scribes in particular. I make it a point to remind presenters in my WG that they need to include slide numbers. Usually it's most efficient when giving them instructions about the deadline by which I need the slides. And when they still forget (3 presentations this meeting) I either add them myself and inform the authors or (especially in the case of PDF) tell them to give them to me again with page numbers.
> 
> Brian
> 
> Begin forwarded message:
> 
>> From: Yoav Nir <ynir@checkpoint.com>
>> Subject: [87attendees] Slide numbers
>> Date: July 31, 2013 4:24:01 PM GMT+02:00
>> To: "<87attendees@ietf.org>" <87attendees@ietf.org>
>>
>> I've seen way too many slides this week with no slide numbers. Might be mostly too late now, but we should remember to remind people two weeks before the meeting that slides need numbers.
>>
>> _______________________________________________
>> 87attendees mailing list
>> 87attendees@ietf.org
>> https://www.ietf.org/mailman/listinfo/87attendees
> 


From michael.scharf@alcatel-lucent.com  Wed Jul 31 08:19:20 2013
Return-Path: <michael.scharf@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 9F2F821F9CA6 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.482
X-Spam-Level: 
X-Spam-Status: No, score=-10.482 tagged_above=-999 required=5 tests=[AWL=0.117, 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 juAoubpGpbeK for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:19:14 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A2C0521F9C7D for <wgchairs@ietf.org>; Wed, 31 Jul 2013 08:19:14 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r6VFJ9uw011096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 Jul 2013 10:19:10 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6VFJ8Go005962 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Jul 2013 17:19:08 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.60]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Wed, 31 Jul 2013 17:19:08 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Brian Weis <bew@cisco.com>, Working Group Chairs <wgchairs@ietf.org>
Subject: RE: [87attendees] Slide numbers
Thread-Topic: [87attendees] Slide numbers
Thread-Index: AQHOjfma0lQDeEOoCkuYtQjjkBt7Fpl+43zigAAAxrA=
Date: Wed, 31 Jul 2013 15:19:07 +0000
Message-ID: <655C07320163294895BBADA28372AF5D07B167@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
In-Reply-To: <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.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: Wed, 31 Jul 2013 15:19:20 -0000

> Forwarding this to the WG chairs list. This is a serious=20
> issue for scribes and Jabber scribes in particular. I make it=20
> a point to remind presenters in my WG that they need to=20
> include slide numbers. Usually it's most efficient when=20
> giving them instructions about the deadline by which I need=20
> the slides. And when they still forget (3 presentations this=20
> meeting) I either add them myself and inform the authors or=20
> (especially in the case of PDF) tell them to give them to me=20
> again with page numbers.

For what it is worth, in TCPM two presenters originally had "$COMPANY Propr=
ietary and Confidential" and *no* slide numbers. Despite an explicit reques=
t for slide numbers on the TCPM list :(

In addition to stating what SHOULD be on a slide, is there somewhere a clea=
r guideline what MUST NOT be on a slide, which I could use as a reference?

Thanks

Michael


> Brian
>=20
> Begin forwarded message:
>=20
> > From: Yoav Nir <ynir@checkpoint.com>
> > Subject: [87attendees] Slide numbers
> > Date: July 31, 2013 4:24:01 PM GMT+02:00
> > To: "<87attendees@ietf.org>" <87attendees@ietf.org>
> >=20
> > I've seen way too many slides this week with no slide=20
> numbers. Might be mostly too late now, but we should remember=20
> to remind people two weeks before the meeting that slides=20
> need numbers.
> >=20
> > _______________________________________________
> > 87attendees mailing list
> > 87attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/87attendees
>=20
> --
> Brian Weis
> Security, Enterprise Networking Group, Cisco Systems
> Telephone: +1 408 526 4796
> Email: bew@cisco.com
>=20
> =

From cabo@tzi.org  Wed Jul 31 08:52:55 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 0AD0A21F9946 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.049
X-Spam-Level: 
X-Spam-Status: No, score=-106.049 tagged_above=-999 required=5 tests=[AWL=0.200, 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 D0ATy31IQRtO for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 08:52:49 -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 470E721F9306 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 08:52:45 -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 r6VFqdJX002270; Wed, 31 Jul 2013 17:52:39 +0200 (CEST)
Received: from dhcp-90f8.meeting.ietf.org (dhcp-90f8.meeting.ietf.org [130.129.8.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8E45597D; Wed, 31 Jul 2013 17:52:39 +0200 (CEST)
Subject: Re: [87attendees] Slide numbers
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: <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
Date: Wed, 31 Jul 2013 17:52:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED25710E-4A4E-44D7-BCB9-8CFE96C989D8@tzi.org>
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
To: Brian Weis <bew@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: Working Group 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, 31 Jul 2013 15:52:55 -0000

On Jul 31, 2013, at 17:07, Brian Weis <bew@cisco.com> wrote:

> And when they still forget

Why allow presenters to use their own slides?

I consolidate the slides into a single slide set.  (With numbers, of =
course.)
And I get to throw out nonsense in the process.

Gr=FC=DFe, Carsten


From paul.hoffman@vpnc.org  Wed Jul 31 09:06:55 2013
Return-Path: <paul.hoffman@vpnc.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 2064A21F9E5C for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:06: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 nI2qFWfo8XrQ for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:06:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 101F321F9B0C for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:06:32 -0700 (PDT)
Received: from dhcp-64c3.meeting.ietf.org (dhcp-64c3.meeting.ietf.org [130.129.100.195]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r6VG6Oad060037 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:06:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: "Thank you, and see you in Vancouver"
Message-Id: <AB8C46A1-2382-4DAB-A7AA-1D714FCFD7A1@vpnc.org>
Date: Wed, 31 Jul 2013 18:06:20 +0200
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
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, 31 Jul 2013 16:06:55 -0000

I have been hearing the phrase in the subject line a bunch this week. =
This kind of sounds like "I won't see you on the list for another few =
months", which is definitely not the tone most chairs want to set. Maybe =
we should be saying "Thank you, and see you on the list".

--Paul Hoffman=

From ajs@anvilwalrusden.com  Wed Jul 31 09:17:47 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 D4C3C21F9E12 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.836
X-Spam-Level: 
X-Spam-Status: No, score=-0.836 tagged_above=-999 required=5 tests=[AWL=0.004,  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 NYyXc1DogAfE for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:17:42 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 31C8021F9E2A for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:17:37 -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 669278A031 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 16:17:36 +0000 (UTC)
Date: Wed, 31 Jul 2013 12:17:41 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: wgchairs@ietf.org
Subject: Re: [87attendees] Slide numbers
Message-ID: <20130731161740.GC56454@mx1.yitter.info>
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com> <655C07320163294895BBADA28372AF5D07B167@FR712WXCHMBA15.zeu.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <655C07320163294895BBADA28372AF5D07B167@FR712WXCHMBA15.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: Wed, 31 Jul 2013 16:17:48 -0000

On Wed, Jul 31, 2013 at 03:19:07PM +0000, Scharf, Michael (Michael) wrote:
> 
> "$COMPANY Proprietary and Confidential" 

> In addition to stating what SHOULD be on a slide, is there somewhere a clear guideline what MUST NOT be on a slide, which I could use as a reference?

That one, at least, is easy: Note Well.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From derek@ihtfp.com  Wed Jul 31 09:20:12 2013
Return-Path: <derek@ihtfp.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 C25D621E809C for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:20: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 2DZp+ZsXXgBu for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:20:04 -0700 (PDT)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:4830:143:1::3a11]) by ietfa.amsl.com (Postfix) with ESMTP id 2ADDF21F8925 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:19:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 3C82A2602B8; Wed, 31 Jul 2013 12:19:49 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 18367-05; Wed, 31 Jul 2013 12:19:47 -0400 (EDT)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id 394172602C9; Wed, 31 Jul 2013 12:19:47 -0400 (EDT)
Received: from 2001:df8:0:80:224:d7ff:fee7:8924 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Wed, 31 Jul 2013 12:19:47 -0400
Message-ID: <67fbdcae5867e474f8cf7930288d4888.squirrel@mail2.ihtfp.org>
In-Reply-To: <AB8C46A1-2382-4DAB-A7AA-1D714FCFD7A1@vpnc.org>
References: <AB8C46A1-2382-4DAB-A7AA-1D714FCFD7A1@vpnc.org>
Date: Wed, 31 Jul 2013 12:19:47 -0400
Subject: Re: "Thank you, and see you in Vancouver"
From: "Derek Atkins" <derek@ihtfp.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
User-Agent: SquirrelMail/1.4.22-2.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
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: Wed, 31 Jul 2013 16:20:12 -0000

On Wed, July 31, 2013 12:06 pm, Paul Hoffman wrote:
> I have been hearing the phrase in the subject line a bunch this week. This
> kind of sounds like "I won't see you on the list for another few months",
> which is definitely not the tone most chairs want to set. Maybe we should
> be saying "Thank you, and see you on the list".

I don't know about you but I rarely see people on mailing lists; I only
hear from them on the lists.  So technically, yes, the next time I will
actually *see* many people is in Vancouver, even if I'll be communicating
with them next week.

> --Paul Hoffman

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant


From dcrocker@bbiw.net  Wed Jul 31 09:27:39 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 0174E21F9995 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppw4wSuxyWzh for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:27:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C574E21F9C8E for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:27:30 -0700 (PDT)
Received: from [130.129.84.47] (dhcp-542f.meeting.ietf.org [130.129.84.47]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6VGROm3018964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Jul 2013 09:27:29 -0700
Message-ID: <51F93AE7.80406@bbiw.net>
Date: Wed, 31 Jul 2013 18:27:19 +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: Derek Atkins <derek@ihtfp.com>
Subject: Re: "Thank you, and see you in Vancouver"
References: <AB8C46A1-2382-4DAB-A7AA-1D714FCFD7A1@vpnc.org> <67fbdcae5867e474f8cf7930288d4888.squirrel@mail2.ihtfp.org>
In-Reply-To: <67fbdcae5867e474f8cf7930288d4888.squirrel@mail2.ihtfp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Wed, 31 Jul 2013 09:27:29 -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: Wed, 31 Jul 2013 16:27:39 -0000

On 7/31/2013 6:19 PM, Derek Atkins wrote:
> I don't know about you but I rarely see people on mailing lists


I'll bet you do, in your mind's eye...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From eburger@standardstrack.com  Wed Jul 31 09:34:21 2013
Return-Path: <eburger@standardstrack.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 AA54C21F99BB for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.139
X-Spam-Level: 
X-Spam-Status: No, score=-100.139 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtBscVkl4MoY for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:34:15 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id B6F2D21E804E for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:34:12 -0700 (PDT)
Received: from dhcp-6516.meeting.ietf.org ([130.129.101.22]:50791) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1V4ZLW-0005Es-3J for wgchairs@ietf.org; Wed, 31 Jul 2013 09:33:54 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C93D0875-3B67-43A6-87B6-F5BE39056730"; protocol="application/pgp-signature"; micalg=pgp-sha1
Subject: Chair dinner?
Message-Id: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com>
Date: Wed, 31 Jul 2013 18:33:52 +0200
To: WG Chairs <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
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, 31 Jul 2013 16:34:21 -0000

--Apple-Mail=_C93D0875-3B67-43A6-87B6-F5BE39056730
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

I hear they have beer in Berlin...

--Apple-Mail=_C93D0875-3B67-43A6-87B6-F5BE39056730
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

iQIcBAEBAgAGBQJR+TxwAAoJEORoZaSQsc1I4DQP/RXLGBflKgxzvayJCitMmXOe
Bl4nzCBCtjb2VOp8XksuxUN/Rl6pvVn+ngPCVJs/5kDAynr63ytvyMV0f3Xg8E6k
5Avz/ABPwrgsHHSMUeymOfbKu0kDzav5BtIKzpHfJ+BFst5KvrOvIecs/s5YwupC
tsCB+b+pCWMtdpWSowMYvUEkciSgu6vWjow31GunMG3jNIvZl0pmi9VPeQ1aJFLe
Rr1ecJHW8MbBVOls7/Z8xY2XnxeqOpMsqQ4cWLUpsBmCLceFvSZS3XsHQzKo+Osh
mlwl2oTCtLg9PNSIiSKs3xZwjCHRM2lCQ3fztBOkCfJl3eeDOnpr+S1Hk/O8Oocq
Yce3Zig6LohbYd3n25RuEC7EUaw/Jh+CbArALGXJN5oTjbGNKqyafDaedS5X7Fck
CvSsxSA1U5B2UMeFxrLY0F8b7ZoP8UqJ6fUUtbF6VwhQRXxSig3iLHFmQkVOmlkv
2JIK9qfCM1pVaFhuIHGASTVgbNrMLMSO8m5j19BcaTQqVfJK9HnPXoj6Y12gqUDY
siCxldPufWdmv+OPTBMpG5luoK5fDwJAX3SRxhSW0jap+8rDMv0wlk1uJYW3VyGp
T6mefnS066U2H8nx+YGcPQLSV5Zua1gzJ1eEAAV6VtZOUg1dHQfz1jo4SaY2jBWy
DK+jGoc0Ug5IFmjYk8kK
=WQHp
-----END PGP SIGNATURE-----

--Apple-Mail=_C93D0875-3B67-43A6-87B6-F5BE39056730--

From salvatore.loreto@ericsson.com  Wed Jul 31 09:36:49 2013
Return-Path: <salvatore.loreto@ericsson.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 26A5021F9980 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.119
X-Spam-Level: 
X-Spam-Status: No, score=-105.119 tagged_above=-999 required=5 tests=[AWL=1.130, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cm-Hmevx+Iaj for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:36:43 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 5164421F97E6 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:36:22 -0700 (PDT)
X-AuditID: c1b4fb25-b7f826d000001766-bd-51f93d0418eb
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 0B.56.05990.40D39F15; Wed, 31 Jul 2013 18:36:21 +0200 (CEST)
Received: from mail.lmf.ericsson.se (153.88.183.150) by smtp.internal.ericsson.com (153.88.183.80) with Microsoft SMTP Server id 14.2.328.9; Wed, 31 Jul 2013 18:36:20 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 89463110233 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 19:36:20 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 158D44FE29	for <wgchairs@ietf.org>; Wed, 31 Jul 2013 19:36:16 +0300 (EEST)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 81ADF4FA79	for <wgchairs@ietf.org>; Wed, 31 Jul 2013 19:36:15 +0300 (EEST)
Message-ID: <51F93D03.3040108@ericsson.com>
Date: Wed, 31 Jul 2013 18:36:19 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: <wgchairs@ietf.org>
Subject: Re: Chair dinner?
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com>
In-Reply-To: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUyM+JvrS6r7c9Ag4Uv2Sz+75/C6MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujO0dm5gKDjFWfL7TzdbAOIexi5GTQ0LAROLKzWnMELaYxIV7 69m6GLk4hAQOM0qc+X2PCcLZwChxqO8pK4RzlVHi/fQJUJljjBIz7z9mh3DOAzlXH7OBDOMV 0Ja4se49K4jNIqAqsf7KJBYQm03ATOL5wy1gC0UFkiXeX7nDDFEvKHFy5hOwGhEBcYkVq9eD xYUFpCS23D7PBGILCbhKTD89BWw+p4CbxNu7D8GeYBawlbgw5zoLhC0vsf3tHKiH1CSuntvE DNGrJdF7tpNpAqPILCTrZiFpn4WkfQEj8ypG9tzEzJz0cqNNjMBwPrjlt+oOxjvnRA4xSnOw KInzbtY7EygkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBcd3zuZ8WpJzNzX9wv8Do1ImrEvfT a0W59x398NVLvZkh9GT+kTNf1ycqf2adw7FDYeH+sz22+xaE2fH0+wjZXD+gsGxaVdzWY41z vyuzrNo+81rYy5i2A2Gzt9QcTZdwzcz4q75e2+3lrD+7l4iF9qbIbeZ89u/WZ75bxdL35qkm Xc88v/x3+TclluKMREMt5qLiRACDPAA0NQIAAA==
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, 31 Jul 2013 16:36:49 -0000

On 7/31/13 6:33 PM, Eric Burger wrote:
> I hear they have beer in Berlin...
there is going to be a bierfestival starting on Friday

http://www.bierfestival-berlin.de/index%20eng.html




From dcrocker@bbiw.net  Wed Jul 31 09:38:09 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 D4DA721F9D53 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J2ozZFnDhU7H for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:38:04 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AD30321F8617 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:38:04 -0700 (PDT)
Received: from [130.129.84.47] (dhcp-542f.meeting.ietf.org [130.129.84.47]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6VGbs3l019215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Jul 2013 09:37:59 -0700
Message-ID: <51F93D5E.4010504@bbiw.net>
Date: Wed, 31 Jul 2013 18:37:50 +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: Eric Burger <eburger@standardstrack.com>
Subject: Re: Chair dinner?
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com>
In-Reply-To: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.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]); Wed, 31 Jul 2013 09:38:00 -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: Wed, 31 Jul 2013 16:38:10 -0000

On 7/31/2013 6:33 PM, Eric Burger wrote:
> I hear they have beer in Berlin...


I have a 30-60 minute thing right after the plenary, but wouldn't mind 
knowing where you folks land, in case I can make it.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From keith.drage@alcatel-lucent.com  Wed Jul 31 10:00:01 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 EE73D21F9B31 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.641
X-Spam-Level: 
X-Spam-Status: No, score=-110.641 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 BdaHrnNBQMwz for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 09:59:54 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 73D9F21F9B5F for <wgchairs@ietf.org>; Wed, 31 Jul 2013 09:57:48 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r6VGvHIg028199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 Jul 2013 11:57:18 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6VGvG24022712 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Jul 2013 18:57:16 +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; Wed, 31 Jul 2013 18:57:16 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Brian Weis <bew@cisco.com>, Working Group Chairs <wgchairs@ietf.org>
Subject: RE: [87attendees] Slide numbers
Thread-Topic: [87attendees] Slide numbers
Thread-Index: AQHOjf+qZlqcifphqUKiMN8f7jV6t5l/Acbw
Date: Wed, 31 Jul 2013 16:57:16 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B079245@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com>
In-Reply-To: <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.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.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
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, 31 Jul 2013 17:00:01 -0000

If any one is doing a template, it would also be useful if it had slide x o=
f y, rather than just slide x.

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Brian Weis
> Sent: 31 July 2013 16:07
> To: Working Group Chairs
> Subject: Fwd: [87attendees] Slide numbers
>=20
> Forwarding this to the WG chairs list. This is a serious issue for scribe=
s
> and Jabber scribes in particular. I make it a point to remind presenters
> in my WG that they need to include slide numbers. Usually it's most
> efficient when giving them instructions about the deadline by which I nee=
d
> the slides. And when they still forget (3 presentations this meeting) I
> either add them myself and inform the authors or (especially in the case
> of PDF) tell them to give them to me again with page numbers.
>=20
> Brian
>=20
> Begin forwarded message:
>=20
> > From: Yoav Nir <ynir@checkpoint.com>
> > Subject: [87attendees] Slide numbers
> > Date: July 31, 2013 4:24:01 PM GMT+02:00
> > To: "<87attendees@ietf.org>" <87attendees@ietf.org>
> >
> > I've seen way too many slides this week with no slide numbers. Might be
> mostly too late now, but we should remember to remind people two weeks
> before the meeting that slides need numbers.
> >
> > _______________________________________________
> > 87attendees mailing list
> > 87attendees@ietf.org
> > https://www.ietf.org/mailman/listinfo/87attendees
>=20
> --
> Brian Weis
> Security, Enterprise Networking Group, Cisco Systems
> Telephone: +1 408 526 4796
> Email: bew@cisco.com


From barryleiba.mailing.lists@gmail.com  Wed Jul 31 10:18:42 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 16DA121E80C8 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.974
X-Spam-Level: 
X-Spam-Status: No, score=-101.974 tagged_above=-999 required=5 tests=[AWL=0.004, 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 mUqz7hnH5tlR for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:18:41 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB4721F9FFF for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:18:41 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id d10so1120290vea.33 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Yp8wJJ4WDia56lStMO5Yvhmr3d2lwzqYFMZjNW0XeKU=; b=vrTDOhZqO8AqbMSVkAq1mDkUOXtYSzhDSCVZfqO2QaAbEW0c2MAzGGNnRUJelmKNgL Am7YVJU7hJRcL1sKu8ZsWmetpv/J/QMmBc8BPAeF+IBMsQm7X09krmwD7GZFwATD2rZ1 GFpuZngG9GeHLLzJ3z7PH0WzzlhkCY0S9OQ0bj6FnaAPDuO+VSb6TZlO5AsVwNZZqYTX pA5DogiWz5iFdmsWMc3Uu3fkAtPlxm2rwHjKdEMIWesWsHpYyQ39oGLze0MiIBKpbMmQ VkHIq0IDqr5vtBu3aZQzikCV9/a5UocoklPAICBzgQD14BtkXwWsFjgEIJsaOSQP2jZp ZCsA==
MIME-Version: 1.0
X-Received: by 10.220.20.3 with SMTP id d3mr11999169vcb.55.1375291120901; Wed, 31 Jul 2013 10:18:40 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 10:18:40 -0700 (PDT)
In-Reply-To: <51F93D5E.4010504@bbiw.net>
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net>
Date: Wed, 31 Jul 2013 13:18:40 -0400
X-Google-Sender-Auth: tatlrROZ3HwE5yqK2D5sUUYIV5Y
Message-ID: <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com>
Subject: Re: Chair dinner?
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 31 Jul 2013 17:18:42 -0000

>> I hear they have beer in Berlin...
>
> I have a 30-60 minute thing right after the plenary, but wouldn't mind
> knowing where you folks land, in case I can make it.

A few of us are going to the nearby Biergarten.  Others would
certainly be Willkommen.

Barry

From michael.scharf@alcatel-lucent.com  Wed Jul 31 10:23:47 2013
Return-Path: <michael.scharf@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 637D121E80D1 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.489
X-Spam-Level: 
X-Spam-Status: No, score=-10.489 tagged_above=-999 required=5 tests=[AWL=0.110, 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 qhKyDpWs-JF7 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:23:26 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id AB09021F9A30 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:23:14 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r6VHLxlV018672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 Jul 2013 12:22:01 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6VHLxsr032094 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Jul 2013 19:21:59 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.60]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Wed, 31 Jul 2013 19:21:59 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: [87attendees] Slide numbers
Thread-Topic: [87attendees] Slide numbers
Thread-Index: AQHOjfma0lQDeEOoCkuYtQjjkBt7Fpl+43zigAAAxrD///E5gIAALBpw
Date: Wed, 31 Jul 2013 17:21:58 +0000
Message-ID: <655C07320163294895BBADA28372AF5D07B367@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <C95AD15C-FC2B-4863-A3F4-9E6B03DD6013@checkpoint.com> <56116D44-0727-4D8D-8447-D0536D5B12DC@cisco.com> <655C07320163294895BBADA28372AF5D07B167@FR712WXCHMBA15.zeu.alcatel-lucent.com> <20130731161740.GC56454@mx1.yitter.info>
In-Reply-To: <20130731161740.GC56454@mx1.yitter.info>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
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
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, 31 Jul 2013 17:23:48 -0000

> > "$COMPANY Proprietary and Confidential"=20
>=20
> > In addition to stating what SHOULD be on a slide, is there=20
> somewhere a clear guideline what MUST NOT be on a slide,=20
> which I could use as a reference?
>=20
> That one, at least, is easy: Note Well.

I was looking for something that that states this in a bullet-proof way for=
 guys that cannot even read an e-mail with an explicit request for slide nu=
mbers.

Michael


From weiler@tislabs.com  Wed Jul 31 10:30:03 2013
Return-Path: <weiler@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 3860911E8167 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:30:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4I7H4MKHQlo for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:29:58 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id C07FD21F9D12 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:29:58 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 54C6D28B0017; Wed, 31 Jul 2013 13:29:58 -0400 (EDT)
Received: from nova.tislabs.com (nova.tislabs.com [10.66.1.77]) by nova.tislabs.com (Postfix) with ESMTP id 433321F8032; Wed, 31 Jul 2013 13:29:58 -0400 (EDT)
Date: Wed, 31 Jul 2013 13:29:58 -0400 (EDT)
From: Samuel Weiler <weiler@tislabs.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Chair dinner?
In-Reply-To: <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com>
Message-ID: <alpine.LRH.2.03.1307311324190.2145@tislabs.com>
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net> <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com>
User-Agent: Alpine 2.03 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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: Wed, 31 Jul 2013 17:30:03 -0000

On Wed, 31 Jul 2013, Barry Leiba wrote:

> A few of us are going to the nearby Biergarten.

Which one?  (There are at least two.)

One is Cafe on Neuen See.  It's "over the bridge".  Much larger than 
Schleusenkrug.  Semi-self-serve food includes pizza, ribs, wurst, salads. 
They also have a white-tablecloth restaurant. 
http://www.cafeamneuensee.de/biergarten/

The other is Schleusenkrug, at the far end of the zoo (no crossing of the 
water).  Find a table, take note of the table number, then order at the 
window.  Food is brought to you.  Be warned that the path you take there 
(along the water) may be closed later in the evening, and you may need to 
come back by going around the zoo.
schleusenkrug.de

I found the food better and more diverse at Schleusenkrug, though one 
could argue that the atmospehere is better at Cafe on Neuen See.

-- Sam


From barryleiba.mailing.lists@gmail.com  Wed Jul 31 10:42:05 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 9CB9611E8168 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.974
X-Spam-Level: 
X-Spam-Status: No, score=-101.974 tagged_above=-999 required=5 tests=[AWL=0.004, 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 oJ0SodBEmPuN for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:42:05 -0700 (PDT)
Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id F1F5711E8133 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:42:04 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id pa12so1136630veb.30 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:42:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HpBww+LTifYfGzsfGSxHqvCIayWFh+UA0cQPJmOuUBE=; b=wIjRNkJmlDDaBWqM0UvHnaqKUUwchT3Mp8zRCLLS0UIwzJV0yEXBOMAyae2PuCkvuI HgcmILGgO2IOC/fygzAVZUP+P7PIPcotO9iU2HTyq133ISURBoKHKEGZVFLdOD1jkusx vV9OmlanLnYAWFSesZvLjS04kq15Qzxvmm9BbjqCBqW5JKoQQDcAu9eXbVOc56pO5Ysb YLI+dHMc6PAguUgEtTMUNB0RCjt3PjsyOIpdXJROSheBHk6EcLDCVi3VCoGTF8uUhdwQ vC0ZmE/bTibloxxzliU9+MC9CHu75uqeTpR8DaIqYvxVBz9F/0V0y4XFNaYqAeZXoVXe +fmQ==
MIME-Version: 1.0
X-Received: by 10.52.244.78 with SMTP id xe14mr6034450vdc.30.1375292523203; Wed, 31 Jul 2013 10:42:03 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 31 Jul 2013 10:42:03 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.03.1307311324190.2145@tislabs.com>
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net> <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com> <alpine.LRH.2.03.1307311324190.2145@tislabs.com>
Date: Wed, 31 Jul 2013 13:42:03 -0400
X-Google-Sender-Auth: Jc_g6ukxX_cB7Cn_xr4blqJ8guM
Message-ID: <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@mail.gmail.com>
Subject: Re: Chair dinner?
From: Barry Leiba <barryleiba@computer.org>
To: Samuel Weiler <weiler@tislabs.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Wed, 31 Jul 2013 17:42:05 -0000

I think we were thinking of Neuen Zee.

On Wed, Jul 31, 2013 at 1:29 PM, Samuel Weiler <weiler@tislabs.com> wrote:
> On Wed, 31 Jul 2013, Barry Leiba wrote:
>
>> A few of us are going to the nearby Biergarten.
>
>
> Which one?  (There are at least two.)
>
> One is Cafe on Neuen See.  It's "over the bridge".  Much larger than
> Schleusenkrug.  Semi-self-serve food includes pizza, ribs, wurst, salads.
> They also have a white-tablecloth restaurant.
> http://www.cafeamneuensee.de/biergarten/
>
> The other is Schleusenkrug, at the far end of the zoo (no crossing of the
> water).  Find a table, take note of the table number, then order at the
> window.  Food is brought to you.  Be warned that the path you take there
> (along the water) may be closed later in the evening, and you may need to
> come back by going around the zoo.
> schleusenkrug.de
>
> I found the food better and more diverse at Schleusenkrug, though one could
> argue that the atmospehere is better at Cafe on Neuen See.
>
> -- Sam
>

From tjc@ecs.soton.ac.uk  Wed Jul 31 10:46:53 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 23EAB21F9C01 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, 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 ZvdC2Quhw0ix for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 10:46:52 -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 5EE5E11E8186 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 10:46:47 -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 r6VHkaXB016274;  Wed, 31 Jul 2013 18:46:36 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r6VHkaXB016274
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1375292796; bh=Pwm+qCruaI6wT/6UZSN+ihhLEyY=; h=References:Mime-Version:In-Reply-To:Cc:From:Subject:Date:To; b=3xlEpaw8Gkmi+XNuHu/IubhSiZ1XiLo+VsYZ/fLtiV/M56CgHBB9VnxLdRqMxWE37 GKQ1mNY2AxtLIm5jQI3HoPV5xs6LFTf/xgQdyCDXgJwLDRKEOiT9DhHP2bsuuOpZVu j7hystbgqOqym0XSObzLf+G+r/fgsJtSWkBj3sV4=
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 p6UIka0544557828Ns ret-id none; Wed, 31 Jul 2013 18:46:36 +0100
Received: from [130.129.70.51] (dhcp-4633.meeting.ietf.org [130.129.70.51]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r6VHkWJl007253 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 31 Jul 2013 18:46:32 +0100
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net> <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com> <alpine.LRH.2.03.1307311324190.2145@tislabs.com> <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@mail.gmail.com> <234320D7-258C-4E29-A608-69D7B9A57218@ecs.soton.ac.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9b42803ce0027645c3903c3a07d176c2p6UIka03tjc|ecs.soton.ac.uk|234320D7-258C-4E29-A608-69D7B9A57218@ecs.soton.ac.uk>
X-Mailer: iPhone Mail (10B329)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Chair dinner?
Date: Wed, 31 Jul 2013 18:46:30 +0100
To: Barry Leiba <barryleiba@computer.org>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p6UIka054455782800; tid=p6UIka0544557828Ns; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r6VHkaXB016274
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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: Wed, 31 Jul 2013 17:46:53 -0000

It's easy to get to, just go out the back of the hotel through the restauran=
t door, follow the path to the river, then turn left along the river, under t=
he bridge, up the other side on to the bridge, cross, and its 200m or so on t=
he left.

--
Tim

On 31 Jul 2013, at 18:42, Barry Leiba <barryleiba@computer.org> wrote:

> I think we were thinking of Neuen Zee.
>=20
> On Wed, Jul 31, 2013 at 1:29 PM, Samuel Weiler <weiler@tislabs.com> wrote:=

>> On Wed, 31 Jul 2013, Barry Leiba wrote:
>>=20
>>> A few of us are going to the nearby Biergarten.
>>=20
>>=20
>> Which one?  (There are at least two.)
>>=20
>> One is Cafe on Neuen See.  It's "over the bridge".  Much larger than
>> Schleusenkrug.  Semi-self-serve food includes pizza, ribs, wurst, salads.=

>> They also have a white-tablecloth restaurant.
>> http://www.cafeamneuensee.de/biergarten/
>>=20
>> The other is Schleusenkrug, at the far end of the zoo (no crossing of the=

>> water).  Find a table, take note of the table number, then order at the
>> window.  Food is brought to you.  Be warned that the path you take there
>> (along the water) may be closed later in the evening, and you may need to=

>> come back by going around the zoo.
>> schleusenkrug.de
>>=20
>> I found the food better and more diverse at Schleusenkrug, though one cou=
ld
>> argue that the atmospehere is better at Cafe on Neuen See.
>>=20
>> -- Sam
>>=20

From johnl@iecc.com  Wed Jul 31 11:18:53 2013
Return-Path: <johnl@iecc.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 875C011E81AC for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 11:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.853
X-Spam-Level: 
X-Spam-Status: No, score=-110.853 tagged_above=-999 required=5 tests=[AWL=0.346, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNULV0YxRiq6 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 11:18:49 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id EEDA211E81A5 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 11:18:48 -0700 (PDT)
Received: (qmail 13482 invoked from network); 31 Jul 2013 18:18:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 31 Jul 2013 18:18:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51f95506.xn--3zv.k1307; i=johnl@user.iecc.com; bh=4M6C+xLPIQ4Rij7RhepvPiZF+mBd3S7mD0qGbxX6l/0=; b=4z9yxwq9zydlSvjzDf/B9eUYV/9bbvPnrkqfd00zz4VkLFdFe8lARnMDdm/dIbF5I7t8dPk4FFuhCFt/zSYPzfMdKFWS0nFbI9aupQl8Eg2jdJrQmV2EvEO0XKMRWP8NwD3Uy8m4fKPxYjDhpBj6jmmtXyKc3p5u04A+k7uRNRd6LykBne5v9EuWqiGvEfwxNZGl9gZdvmwZjWqO99RQf4vEpjeS3V8uGuu8jdio2SHHZRz+ccDtGVJ5naIYyBbn
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51f95506.xn--3zv.k1307; olt=johnl@user.iecc.com; bh=4M6C+xLPIQ4Rij7RhepvPiZF+mBd3S7mD0qGbxX6l/0=; b=QkCIT0h5a8xice0uLlo9/8CvzmEtDNLvWBh0PWoeOSkFiZYM4iSLCfhmhhvh3kCV28zunfNOc6YMFDzvgOTjITLHMDP8zS96ZK7xvHZw2B5bO5itNuzgO4q/9jhyWSy7eoW6cY98C2t8jOorqmCP2g1OECnCY5kLdj+Q5tnGpxgHFN9Yw5Xmbzg/k3DYNM1ChG/ApfFBuEQjmY58TYRpaSPPuHdbOvtVr8eyWKXhBWpG0GYRjO5udDTmI3j+xGlA
Date: 31 Jul 2013 18:18:24 -0000
Message-ID: <20130731181824.2999.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: wgchairs@ietf.org
Subject: Re: Chair dinner?
In-Reply-To: <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: barryleiba@computer.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, 31 Jul 2013 18:18:53 -0000

>A few of us are going to the nearby Biergarten.  Others would
>certainly be Willkommen.

Which one?  Cafe am neun Zee (other side of the river) or
Schleusenkrug (this side of the river, behind the zoo)

Reviews say Schleusenkrug is better.


From tobias.gondrom@gondrom.org  Wed Jul 31 11:48:09 2013
Return-Path: <tobias.gondrom@gondrom.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 B4B6B21F8C66 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 11:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.208
X-Spam-Level: 
X-Spam-Status: No, score=-96.208 tagged_above=-999 required=5 tests=[AWL=-0.846, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzdVP0WeITVC for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 11:48:05 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id E888D21F8F3C for <wgchairs@ietf.org>; Wed, 31 Jul 2013 11:48:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=jITAE9KDmlNQxsdjBIzvkUPx3tg6kXsJbuM3mni1HYRvpHevkihekjrScyxqEWdwdNeDLYITH/sp6NaZkBmKKCuez4adGtX8x7lMVS+vxKQGWgpKKclJkOFudEdYhrxy; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 27800 invoked from network); 31 Jul 2013 20:48:03 +0200
Received: from dhcp-461e.meeting.ietf.org (HELO ?130.129.70.30?) (130.129.70.30) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 31 Jul 2013 20:48:03 +0200
Message-ID: <51F95BE3.6010407@gondrom.org>
Date: Wed, 31 Jul 2013 20:48:03 +0200
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: barryleiba@computer.org
Subject: Re: Chair dinner?
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net> <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com> <alpine.LRH.2.03.1307311324190.2145@tislabs.com> <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@mail.gmail.com>
In-Reply-To: <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@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
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, 31 Jul 2013 18:48:09 -0000

Ok, guys see you at the Cafe am Neuen See (CANS).
Cheers, Tobias


On 31/07/13 19:42, Barry Leiba wrote:
> I think we were thinking of Neuen Zee.
>
> On Wed, Jul 31, 2013 at 1:29 PM, Samuel Weiler <weiler@tislabs.com> wrote:
>> On Wed, 31 Jul 2013, Barry Leiba wrote:
>>
>>> A few of us are going to the nearby Biergarten.
>>
>> Which one?  (There are at least two.)
>>
>> One is Cafe on Neuen See.  It's "over the bridge".  Much larger than
>> Schleusenkrug.  Semi-self-serve food includes pizza, ribs, wurst, salads.
>> They also have a white-tablecloth restaurant.
>> http://www.cafeamneuensee.de/biergarten/
>>
>> The other is Schleusenkrug, at the far end of the zoo (no crossing of the
>> water).  Find a table, take note of the table number, then order at the
>> window.  Food is brought to you.  Be warned that the path you take there
>> (along the water) may be closed later in the evening, and you may need to
>> come back by going around the zoo.
>> schleusenkrug.de
>>
>> I found the food better and more diverse at Schleusenkrug, though one could
>> argue that the atmospehere is better at Cafe on Neuen See.
>>
>> -- Sam
>>


From dcrocker@bbiw.net  Wed Jul 31 14:09:12 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 2B9E711E8111 for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 14:09:12 -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 QOFMcGiIHpeA for <wgchairs@ietfa.amsl.com>; Wed, 31 Jul 2013 14:09:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 35EEC21F99A0 for <wgchairs@ietf.org>; Wed, 31 Jul 2013 14:09:06 -0700 (PDT)
Received: from [192.168.1.203] (e178124165.adsl.alicedsl.de [85.178.124.165]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6VL90c0024137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <wgchairs@ietf.org>; Wed, 31 Jul 2013 14:09:05 -0700
Message-ID: <51F97CE7.2010109@bbiw.net>
Date: Wed, 31 Jul 2013 23:08:55 +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: wgchairs@ietf.org
Subject: Re: Chair dinner?
References: <1A75FC33-8D04-4BCC-8B7C-7748FB415708@standardstrack.com> <51F93D5E.4010504@bbiw.net> <CAC4RtVB_UOKQTO1iS6eLz_V-=_UZDtNUbzeJ98MKD6XBMsjAyg@mail.gmail.com> <alpine.LRH.2.03.1307311324190.2145@tislabs.com> <CAC4RtVBjoHEXCqphsZ9+K87LnnnMGAHWLm+K1MbHy4OLOLgc_g@mail.gmail.com> <51F95BE3.6010407@gondrom.org>
In-Reply-To: <51F95BE3.6010407@gondrom.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Wed, 31 Jul 2013 14:09:06 -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: Wed, 31 Jul 2013 21:09:12 -0000

On 7/31/2013 8:48 PM, Tobias Gondrom wrote:
> Ok, guys see you at the Cafe am Neuen See (CANS).


Sorry.  My 0-60 minute thing lasted the rest of the evening.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
