
From nobody Tue Apr  1 02:23:09 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086A11A702B for <wgchairs@ietfa.amsl.com>; Tue,  1 Apr 2014 02:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76l6KS6-K-M4 for <wgchairs@ietfa.amsl.com>; Tue,  1 Apr 2014 02:23:06 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 391FA1A7016 for <wgchairs@ietf.org>; Tue,  1 Apr 2014 02:23:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1396344182; d=isode.com; s=selector; i=@isode.com; bh=zwPzc8GQDIsqwHPFU2YLL8m3dnK62TwHaBBXX9kfNHQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=ZTsoOdfB7d0qiQ/Hm4lJVSZWW1vMituKaHdGSKJ52mYrQVIXFzSaNz4EtexGO7oHZVbNR9 r93Xwsmx2ECmqILO4RwrqmhjJWqSC60W9dU97R3WefPIy/2pVFhVaG3qS0zv7JW0GNGXOv 5PXDt1ghtkdZqTMeQaA64dBXJ3fu8WM=;
Received: from [192.168.0.7] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UzqFcwAOZiL3@statler.isode.com>; Tue, 1 Apr 2014 10:23:00 +0100
Message-ID: <533A8575.50405@isode.com>
Date: Tue, 01 Apr 2014 10:23:01 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
To: Robert Sparks <rjsparks@nostrum.com>, wgchairs@ietf.org
Subject: Re: Do milestones need to be reflected on a document's main page
References: <532097E9.4030009@nostrum.com> <5339833A.6030705@nostrum.com>
In-Reply-To: <5339833A.6030705@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/QPEQBxvYg9AGndEQRFcAAVXGwUI
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Apr 2014 09:23:08 -0000

On 31/03/2014 16:01, Robert Sparks wrote:
> I haven't gotten any response to this.
I would possibly keep WGLC and Submitted to IESG milestones, if this is 
easy to implement. But I agree that in the example you gave 5 dates are 
not useful.
> Would anyone object if I removed those badges from the document page?
>
> RjS
>
> On 3/12/14, 12:22 PM, Robert Sparks wrote:
>> Please take a moment to look at the IETF State line at:
>> <http://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/>
>>
>> There are 5 dates (well, two really, but 5 instances) listed on that 
>> line.
>> It is not obvious what they are about until you mouse over them.
>> They reflect milestones this document has been associated with.
>>
>> I'm not sure how we ended up with this as the display motif for that 
>> information.
>> It isn't clear to me what it's trying to convey. The contents of the 
>> mouseover don't really help.
>>
>> I'm not trying to point to this particular document, but rather this 
>> particular feature of a document's
>> main page.
>>
>> What should it be trying to say? Are there documents where the 
>> current implementation works well
>> to convey information? What would make it better?
>>
>> RjS


From nobody Tue Apr  1 07:18:44 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B70F1A06C4 for <wgchairs@ietfa.amsl.com>; Tue,  1 Apr 2014 07:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWC7NzyKV5Ru for <wgchairs@ietfa.amsl.com>; Tue,  1 Apr 2014 07:18:42 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id A62081A06BE for <wgchairs@ietf.org>; Tue,  1 Apr 2014 07:18:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1356; q=dns/txt; s=iport; t=1396361918; x=1397571518; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=LIccHNYPvWND457kE0tyckBjuCt91Z9Lvwot/jS2O5I=; b=eYRdTWX7yCfhFsDKEa4unoKOVAufih3lW4CEWlllly3eWRhorcRvKGFx dmG9Sp3PaoixmzSLoxByGzvA2N6L+LJcag1AVkvDV4QqIG3RH6Zu0XGAo iwAUgGq7Asv/ENL5WwvRPzNm069S9mlARlIqZ+7GuHOQYwMBFgcxWtNw7 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAG7JOlOtJssV/2dsb2JhbABZgwY7xCWBGhZ0giUBAQEDAThAEQsOExYPCQMCAQIBRQYBDAgBAYdtCA3RYReOd4Q4AQOYVoEzhRyLaoMyOw
X-IronPort-AV: E=Sophos;i="4.97,773,1389744000";  d="scan'208";a="8526996"
Received: from aer-core-4.cisco.com ([173.38.203.21]) by aer-iport-4.cisco.com with ESMTP; 01 Apr 2014 14:18:37 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s31EIYQ7023578; Tue, 1 Apr 2014 14:18:34 GMT
Message-ID: <533ACABA.3010902@cisco.com>
Date: Tue, 01 Apr 2014 16:18:34 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Re: Do milestones need to be reflected on a document's main page
References: <532097E9.4030009@nostrum.com>
In-Reply-To: <532097E9.4030009@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Jn-MmE_61ldQCVlo3lcGvYsdjno
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Apr 2014 14:18:43 -0000

Hi Robert
> Please take a moment to look at the IETF State line at:
> <http://datatracker.ietf.org/doc/draft-ietf-jose-json-web-key/>
>
> There are 5 dates (well, two really, but 5 instances) listed on that 
> line.
> It is not obvious what they are about until you mouse over them.
> They reflect milestones this document has been associated with.
That's the first condition for this feature to be useful: The draft and 
milestones must be associated
This is not the case for many OPS WGs, even we saw in increase recently.
Therefore, we can really rely on that feature.

>
> I'm not sure how we ended up with this as the display motif for that 
> information.
> It isn't clear to me what it's trying to convey. The contents of the 
> mouseover don't really help.
>
> I'm not trying to point to this particular document, but rather this 
> particular feature of a document's
> main page.
>
> What should it be trying to say? Are there documents where the current 
> implementation works well
> to convey information? What would make it better?
A link, somewhere in the tracker, directly to the WG milestones , would 
be more useful to me.
The cherry on the cake would be if the draft in question would be 
highlighted on that page, in case the draft and milestones are associated.

Regards, Benoit
>
> RjS
>
>
>
>
>


From nobody Wed Apr  2 08:49:50 2014
Return-Path: <mconner@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169791A0286 for <wgchairs@ietfa.amsl.com>; Wed,  2 Apr 2014 08:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBUazMFpTz_p for <wgchairs@ietfa.amsl.com>; Wed,  2 Apr 2014 08:49:13 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id F3F7C1A022F for <wgchairs@ietf.org>; Wed,  2 Apr 2014 08:49:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8547C1E12A4; Wed,  2 Apr 2014 08:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6psetM_KN1iE; Wed,  2 Apr 2014 08:48:26 -0700 (PDT)
Received: from [64.170.98.144] (unknown [64.170.98.144]) by c8a.amsl.com (Postfix) with ESMTPSA id 61DBF1E12A2; Wed,  2 Apr 2014 08:48:26 -0700 (PDT)
From: Maddy Conner <mconner@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B194CC5C-7FBA-409E-AA7A-8BEE65CC6D1B"
Subject: Reminder: Request for IETF WG and BoF Session Minutes
Message-Id: <45B3CAED-1A49-4319-BE01-13F109953164@amsl.com>
Date: Wed, 2 Apr 2014 08:49:09 -0700
To: "wgchairs@ietf.org" <wgchairs@ietf.org>, "irsg@irtf.org" <irsg@irtf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/gyMm1MF95vPWGq0peWgQmUYlm1c
X-Mailman-Approved-At: Wed, 02 Apr 2014 08:49:48 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Apr 2014 15:49:17 -0000

--Apple-Mail=_B194CC5C-7FBA-409E-AA7A-8BEE65CC6D1B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

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

Groups I still need minutes from are:

Application Area:
	APPSAWG
	CORE
	EPPEXT
	PAWS

Internet Area:
	6MAN
	INTAREA
	LISP
	TRILL

Operations & Management Area:
	V6OPS

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

Routing Area:
	KARP
	L2VPN

Security Area:
	DANE
	SAAG

Transport Area:
	This area has turned in all of their minutes!

IRTF:
	CFRG
	NMRG
	NWCRG
	SDNRG

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




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

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


--Apple-Mail=_B194CC5C-7FBA-409E-AA7A-8BEE65CC6D1B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
all,<br><br>Just a reminder that I am still waiting on minutes from many =
of you. Again, the cutoff for submissions is&nbsp;<b>this&nbsp;Friday, =
April 4th, 2014</b>,&nbsp;and correction submissions cutoff =
is&nbsp;<b>Wednesday,&nbsp;April 23rd, 2014</b>. &nbsp;Please upload =
meeting minutes, as well as any presentations&nbsp;from your sessions, =
at your earliest convenience using the Meeting Materials Manager found =
here:&nbsp;<a =
href=3D"https://pub.ietf.org/proceedings/">https://pub.ietf.org/proceeding=
s/</a>.&nbsp;&nbsp;Alternatively, you are welcome to send them =
to&nbsp;proceedings at&nbsp;<a =
href=3D"http://ietf.org/">ietf.org</a>&nbsp;or&nbsp;mconner at&nbsp;<a =
href=3D"http://amsl.com/">amsl.com</a>&nbsp;for manual =
posting.<br><br>Groups I still need minutes from =
are:<div><br></div><div>Application Area:<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>APPSAWG<br><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>CORE<div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>EPPEXT</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>PAWS</div><div><br>Internet Area:<br><span class=3D"Apple-tab-span"=
 style=3D"white-space: pre; ">	</span>6MAN<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>INTAREA</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>LISP</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>TRILL</div><div><br>Operations &amp; Management =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>V6OPS<br><br>Real-Time Applications &amp; Infrastructure =
Area:<br></div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>AVTEXT</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>DISPATCH</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>INSIPID</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>MMUSIC</div><div><br>Routing =
Area:<br><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>KARP</div><div><span class=3D"Apple-tab-span" style=3D"white-space:=
 pre; ">	</span>L2VPN</div><div><br>Security Area:<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>DANE</div><div><span class=3D"Apple-tab-span" style=3D"white-space:=
 pre; ">	</span>SAAG</div><div><br>Transport Area:<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>This area =
has turned in all of their minutes!</div><div><br>IRTF:<br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>CFRG</div><div><span class=3D"Apple-tab-span" style=3D"white-space:=
 pre; ">	</span>NMRG</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>NWCRG</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>SDNRG<br><br><a =
href=3D"https://datatracker.ietf.org/meeting/89/materials.html">https://da=
tatracker.ietf.org/meeting/89/materials.html</a><br><br><br></div></div><d=
iv><br></div><div><br></div><div apple-content-edited=3D"true">
<div style=3D"color: rgb(0, 0, 0); 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; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Maddy =
Conner<br>IETF Registrar<br>48377 Fremont Blvd, Ste. 117<br>Fremont, CA =
94538<br><br>Association Management Solutions&nbsp;(AMS)<br>Forum =
Management, Meeting and Event&nbsp;Planning<br><a =
href=3D"http://www.amsl.com">www.amsl.com</a></div>
</div>
<br></body></html>=

--Apple-Mail=_B194CC5C-7FBA-409E-AA7A-8BEE65CC6D1B--


From nobody Thu Apr  3 07:32:13 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F151A0211; Thu,  3 Apr 2014 07:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.892
X-Spam-Level: 
X-Spam-Status: No, score=-101.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQiS5n6TNRoe; Thu,  3 Apr 2014 07:31:57 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0187.outbound.protection.outlook.com [207.46.163.187]) by ietfa.amsl.com (Postfix) with ESMTP id 533061A020E; Thu,  3 Apr 2014 07:31:57 -0700 (PDT)
Received: from [192.168.0.34] (184.61.83.93) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.913.9; Thu, 3 Apr 2014 14:31:52 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Liaison Statement Improvements SOW for Community Input
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20140324183422.4579.53478.idtracker@ietfa.amsl.com>
Date: Thu, 3 Apr 2014 10:31:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <B3589989-2FD8-4D88-9460-05B64645353B@isoc.org>
References: <20140324183422.4579.53478.idtracker@ietfa.amsl.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [184.61.83.93]
X-ClientProxiedBy: BLUPR01CA002.prod.exchangelabs.com (10.255.223.160) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 0170DAF08C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(243025003)(377454003)(51704005)(199002)(189002)(24454002)(51856001)(76796001)(54316002)(81816001)(80976001)(83072002)(76482001)(15202345003)(85852003)(77096001)(74366001)(46102001)(95666003)(4396001)(50226001)(98676001)(99396002)(56776001)(50986001)(97186001)(76786001)(59766001)(49866001)(47736001)(81686001)(47976001)(77982001)(97336001)(15975445006)(81342001)(92566001)(53806001)(82746002)(77156001)(79102001)(74502001)(50466002)(88136002)(19580405001)(92726001)(83322001)(19580395003)(69226001)(62966002)(85306002)(95416001)(93136001)(63696002)(47776003)(36756003)(87266001)(81542001)(94316002)(87286001)(93516002)(83716003)(66066001)(80022001)(42186004)(23746002)(33656001)(47446002)(74706001)(89996001)(86362001)(56816005)(31966008)(90146001)(74662001)(65816001)(74876001)(87976001)(93916002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.34]; FPR:FCF8F21C.AC3A9719.70E39EAB.8AA6DA4D.203E1; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/ygQvW4V30M_FugEp1o_vxnf0Nec
Cc: iaoc@ietf.org, "iab@iab.org IAB" <iab@iab.org>, IETF Announcement list <ietf-announce@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Apr 2014 14:32:02 -0000

All;

A reminder that Community input is being sought for this Liaison =
Statement Improvements SOW
http://iaoc.ietf.org/documents/liaison-sow-03.pdf

Thanks
Ray

On Mar 24, 2014, at 2:34 PM, IETF Administrative Director <iad@ietf.org> =
wrote:

> The IAOC desires improvements to the liaison statement tracking =
capabilities in the datatracker to=20
> address community requests and to simplify ongoing maintenance of the =
related code.
>=20
> The community comment period ends 7 April 2014.  The IAOC will =
consider all comments received=20
> during this prior.
>=20
> Liaison relationships with other standards setting bodies are managed =
by the IAB. The processes for=20
> managing the relationships are detailed in RFC4052, and the procedures =
for handling liaison statements=20
> are detailed in RFC4053. The current liaison statement management tool =
(LSMT) began from the=20
> definitions in that RFC and the LMST has been improved through =
previous contracted development.=20
> Individuals using the tool must follow the guidelines in RFC4691.  =
Developers working on the liaison=20
> statement management section of the datatracker must be familiar with =
all three RFCs.=20
>=20
> SOW Deliverables / Tasks
>=20
> a.  Migrate the codebase and data to new models, refining the models =
as necessary.=20
> b.  Add history to liaison statements, capturing when they were =
received, posted, resent, approved, marked=20
> dead or modified.
> c.  Add Point of Contact email addresses for each body to be used as =
the default Response Contact.
> d.  Capture other SDOs identifiers for liaison statements.
> e.  Add =93Action Holder=94 email addresses to incoming liaison =
statements.
> f.  Add the ability for a liaison statement to reference multiple =
other liaison statements as related.
> g.  Allow a liaison statement to be sent from multiple bodies and sent =
to multiple bodies.
> h.  Add the concept of a =93dead=94 liaison statement, allowing an =
approver or the secretariat to remove a=20
> statement from the pending queue without posting it. Add a view to =
manage the set of dead liaison statements.
> i.  Add the ability to resend a liaison statement.
> j.  Improve search over posted liaison statements, searching all =
fields and allowing the results to be=20
> limited to a particular source and/or destination body and/or a =
particular time range. Facilitate browsing a=20
> series of related liaison statements as a =93thread=94.
> k.  Address known issues with the liaison statement entry form when =
used as the secretariat and when used=20
> as a liaison manager.
> l.  Make it easier to see which liaison statements still need action.
> m.  Ensure liaison statement approvers are notified when there is =
something to approve.
> n.  Remove the restriction against duplicate liaison statement titles.
> o.  Allow the set of attachments to a liaison statement to be edited. =
In particular allow an attachment to be=20
> deleted. Leave a record in the history for each editing event.
> p.  Improve test coverage, and ensure tests exercise the use cases =
detailed in this document.
>=20
> All information submitted in response to this announcement is =
voluntary and may be used in the=20
> development of the SOW.
>=20
> Thanks for your continuing advice and support.
>=20
> Ray Pelletier=20
> IETF Administrative Director=20
>=20


From nobody Thu Apr  3 08:05:51 2014
Return-Path: <julian.reschke@gmx.de>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827E81A00B2; Thu,  3 Apr 2014 01:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVbk2aicGxfN; Thu,  3 Apr 2014 01:10:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id DA9D51A00A3; Thu,  3 Apr 2014 01:10:44 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.104.143]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Md3Eg-1Wnq4M0BwA-00IBst; Thu, 03 Apr 2014 10:10:28 +0200
Message-ID: <533D176C.3010600@gmx.de>
Date: Thu, 03 Apr 2014 10:10:20 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mohammed serrhini <serrhini@mail.ru>, iab@iab.org, ietf@ietf.org,  wgchairs@ietf.org, iesg@ietf.org, iad@ietf.org
Subject: Re: Fwd: Re[2]: IAOC Seeks Community Input on IETF Website Revamp SOW
References: <1395020361.178909826@f402.i.mail.ru>
In-Reply-To: <1395020361.178909826@f402.i.mail.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:mbCcdQ+6ETSlzZU5SvJTSVzf7n7DYIb5m5z4zMkxXTHLnca3Vi0 PVN+tXoIycNl/GHijA16ga3JntRXlbUejaLDevL/Aal9v5BxZVZUHyhtVNgclzvU9FS8sKx yFU8FKhV+fXjXoBbksG/owh+DEbpNVxOV1C6b0ktMR/Smf8RyMcDnNthdF9hs44gOLfpo8x fg2lyBe0a+pcm2Tal/EPQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/fNqQqn3nqj-6GzDOaaDAnLRMZV8
X-Mailman-Approved-At: Thu, 03 Apr 2014 08:05:48 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Apr 2014 08:10:54 -0000

On 2014-03-17 02:39, mohammed serrhini wrote:
>
>
> Hello
> to Modernize the web site visual design  the main page must be not
> scrollable as it is now.

-1. There is no problem with "scrollable" content.

> 7.d.vii: "For pages that require the use of applets, a link to the page
> where the user can obtain the plug-ins will be provided. some plugins
> are known as 0 days attacks vulnerability .
> I propose also a link to update this plugins if out of date.

It simply shouldn't use plugins or applets.

> for 2 .c  and e.i .Responsive Design: I propose for mobile devices that
> mobile version of the IETF web site must be developed and accessible
> from the link m.ietf.org

I would avoid that until proven to be needed.

> for 5. h. Events calendar must be in the form of calendar months table
> with selection button of years and month to allow users to select date
> quickly and to view the full IETF agenda By Month and by year

Actually, event information should be available as a calendar resource 
(ics).

Best regards, Julian


From nobody Fri Apr  4 11:00:18 2014
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1ED1A0442; Fri,  4 Apr 2014 11:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xri3qHX3ktxS; Fri,  4 Apr 2014 11:00:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A40831A0235; Fri,  4 Apr 2014 11:00:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: =?utf-8?q?Community_Input_Requested_on_Trustees=E2=80=99_Intent_to?= =?utf-8?q?_Renounce_=E2=80=9CIETF_Secretariat=E2=80=9D_Trademark?=
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Date: Fri, 04 Apr 2014 11:00:01 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/8K-tITLZAal9iT1gpCLpot7U96c
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:00:06 -0000

All;

The Trustees of the IETF Trust have voted an intent to renounce (abandon) the “IETF Secretariat” 
trademark, but before taking any action they desire to hear from the community.  

Specifically:  

It is the Trustees’ intent to:

1. Not renew the “IETF Secretariat” trademark, Registration 3860848, in the European Community 
at an approximate cost of $5,000 USD for a ten-year period when due on May 28, 2014, and 
thereby renounce the trademark as having no foreseeable future value in accordance with Article 7.1a 
of the Amended and Restated Trust Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  
The trademark has no foreseeable future value as the “IETF” trademark is registered in the European 
Community and its use with Secretariat is protected.

2. Not renew the “IETF Secretariat” trademark, Registration 2392833, in the United States at an unknown 
future cost when the trademark expires on October 10, 2020, and thereby renounce the trademark as 
having no foreseeable future value in accordance with Article 7.1a of the Amended and Restated Trust 
Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The trademark has no foreseeable 
future value as the “IETF” trademark is registered in the United States and its use with Secretariat is 
protected.

Authority:

The Trustees have the authority to renounce the trademark in accordance with Article 7.1a of the 
Amended and Restated Trust Agreement after consulting with the Beneficiary.   
<http://trustee.ietf.org/trust-agreement-2014.html>

This Article states in relevant part:
"the Trustees may, after due consultation with the Beneficiary, dispose of, assign, sell, transfer, 
renounce, convey or terminate Trust Assets that are of no current or foreseeable future value to 
the Beneficiary and which require the expenditure of funds to retain.This exception does not 
include RFCs.”

The purpose of this announcement is to begin the consultation with the Beneficiary, the IETF 
Community.  This thirty (30) day comment period expires on 5 May 2014.  The Trustees will consider 
the Community input before making a decision whether to renounce the “IETF Secretariat” trademark 
or not.  

Your feedback is appreciated.

Thanks
Ray Pelletier
IETF Administrative Director
Trustee
IETF Trust


From nobody Fri Apr  4 11:18:07 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B291A04B1; Fri,  4 Apr 2014 11:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sfv6UMrDx7sT; Fri,  4 Apr 2014 11:14:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACD81A027C; Fri,  4 Apr 2014 11:13:04 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s34ICuiQ012350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 4 Apr 2014 11:12:59 -0700
Message-ID: <533EF5BE.7080300@dcrocker.net>
Date: Fri, 04 Apr 2014 11:11:10 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF Administrative Director <iad@ietf.org>, iaoc@ietf.org
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 04 Apr 2014 11:12:59 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/eLExi_MZlgyVyVC0TH5iUEegHss
X-Mailman-Approved-At: Fri, 04 Apr 2014 11:18:02 -0700
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@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, 04 Apr 2014 18:14:27 -0000

On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
> The Trustees of the IETF Trust have voted an intent to renounce (abandon) the “IETF Secretariat”
> trademark,


It sounds as if this will open the door to my being able to advertise 
myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr  4 11:20:08 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D801A0231; Fri,  4 Apr 2014 11:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgzxIMBRTi1D; Fri,  4 Apr 2014 11:19:53 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id 731861A0265; Fri,  4 Apr 2014 11:19:53 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149) with Microsoft SMTP Server (TLS) id 15.0.913.9; Fri, 4 Apr 2014 18:19:47 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: =?windows-1252?Q?Re=3A_Community_Input_Requested_on_Trustees=92_?= =?windows-1252?Q?Intent_to_Renounce_=93IETF_Secretariat=94_Trade?= =?windows-1252?Q?mark?=
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <533EF5BE.7080300@dcrocker.net>
Date: Fri, 4 Apr 2014 14:19:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BN1PR06CA019.namprd06.prod.outlook.com (10.141.56.39) To CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: =?Windows-1252?Q?SFV:NSPM; SFS:(10019001)(6049001)(6009001)(428001)(517040?= =?Windows-1252?Q?05)(377454003)(479174003)(24454002)(199002)(189002)(7648?= =?Windows-1252?Q?2001)(56776001)(81542001)(53806001)(42186004)(54316002)(?= =?Windows-1252?Q?76796001)(74706001)(57306001)(33656001)(76786001)(629660?= =?Windows-1252?Q?02)(51856001)(81342001)(4396001)(50226001)(97186001)(973?= =?Windows-1252?Q?36001)(19580405001)(19580395003)(83322001)(74876001)(367?= =?Windows-1252?Q?56003)(46102001)(95666003)(49866001)(47736001)(74366001)?= =?Windows-1252?Q?(47976001)(50986001)(93516002)(81686001)(47446002)(81816?= =?Windows-1252?Q?001)(93136001)(87976001)(94316002)(99396002)(93916002)(8?= =?Windows-1252?Q?6362001)(92566001)(92726001)(89996001)(79102001)(7466200?= =?Windows-1252?Q?1)(66066001)(80022001)(98676001)(80976001)(69226001)(745?= =?Windows-1252?Q?02001)(88136002)(83716003)(94946001)(65816001)(82746002)?= =?Windows-1252?Q?(23746002)(83072002)(224303002)(85852003)(31966008)(2077?= =?Windows-1252?Q?6003)(63696002)(59766001)(77982001)(85306002)(47776003)(?= =?Windows-1252?Q?224313003)(87286001)(77096001)(95416001)(87266001)(90146?= =?Windows-1252?Q?001)(77156001)(56816005);DIR:OUT;SFP:1102;SCL:1;SRVR:CO1?= =?Windows-1252?Q?PR06MB237;H:[192.168.0.34];FPR:9F05F521.208A44E9.7AF02FA?= =?Windows-1252?Q?7.C8A0B371.20120;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG?= =?Windows-1252?Q?:en;?=
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/bMq_pdGQYMFZmBQSetfdd1-a0wA
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org, "iab@iab.org IAB" <iab@iab.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Apr 2014 18:19:58 -0000

On Apr 4, 2014, at 2:11 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
>> The Trustees of the IETF Trust have voted an intent to renounce =
(abandon) the =93IETF Secretariat=94
>> trademark,
>=20
>=20
> It sounds as if this will open the door to my being able to advertise =
myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?

You could certainly use =93Secretariat=94 but you cannot use =93IETF =
Secretariat=94 without violating the =93IETF=94 trademark.

Ray

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


From nobody Fri Apr  4 12:47:48 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B67B41A01CC; Fri,  4 Apr 2014 12:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4hkBvvwJ9FG; Fri,  4 Apr 2014 12:47:33 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 82EA91A055D; Fri,  4 Apr 2014 12:46:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WWA3p-000DgJ-Lk; Fri, 04 Apr 2014 15:45:57 -0400
Date: Fri, 04 Apr 2014 15:45:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ray Pelletier <rpelletier@isoc.org>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
Message-ID: <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
In-Reply-To: <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/fmd6f3hi1n1ZBx-E1dK8K8APh68
Cc: Working Group Chairs <wgchairs@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Apr 2014 19:47:38 -0000

--On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
<rpelletier@isoc.org> wrote:

>> It sounds as if this will open the door to my being able to
>> advertise myself as the IETF Secretariat.  Or even the ITU's
>> being able to.  Yes?
> 
> You could certainly use "Secretariat" but you cannot use
> "IETF Secretariat" without violating the "IETF"
> trademark.

Ray, I assume that if Dave (or someone else) set themselves up
as the International Elegant Tophat Fabrication Society, made at
least a perfunctory effect to establish themselves as being in
that business, established a business unit that they called
their "Secretariat", and then advertised the result as the "IETF
Secretariat", things could get dicey.  Given the different line
of business, they might even be able to take out a trademark on
"IETF Secretariat".  Right?

Now, whether having a trademark registered as "IETF Secretariat"
with whatever line of business the IETF and IETF Secretariat
claim to be in would offer significant protection against that
attack is far outside my knowledge or experience.

I have enough trouble imagining someone going to the trouble to
attempt the above as an attack that I think it would probably be
foolish to worry about it, but it is, in principle, the
difference between "no risk" and "no risk worth worrying about".

    john





From nobody Fri Apr  4 14:58:40 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473C21A0132; Fri,  4 Apr 2014 14:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OrTizsTs5vh4; Fri,  4 Apr 2014 14:58:16 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6F31A00CA; Fri,  4 Apr 2014 14:58:16 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149) with Microsoft SMTP Server (TLS) id 15.0.913.9; Fri, 4 Apr 2014 21:58:02 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
Date: Fri, 4 Apr 2014 17:57:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BLUPR06CA016.namprd06.prod.outlook.com (10.141.20.36) To CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(189002)(199002)(24454002)(377454003)(51704005)(74662001)(79102001)(92566001)(86362001)(89996001)(92726001)(88136002)(74502001)(69226001)(83716003)(66066001)(80976001)(80022001)(98676001)(47976001)(50986001)(74366001)(99396002)(94316002)(93916002)(81686001)(47446002)(93516002)(87976001)(93136001)(81816001)(87286001)(77156001)(90146001)(87266001)(56816005)(77096001)(95416001)(23746002)(94946001)(65816001)(83072002)(82746002)(77982001)(59766001)(47776003)(85306002)(63696002)(85852003)(20776003)(31966008)(50466002)(33656001)(76786001)(51856001)(62966002)(76796001)(74706001)(4396001)(81342001)(81542001)(53806001)(76482001)(56776001)(54316002)(36756003)(49866001)(47736001)(46102001)(95666003)(97186001)(50226001)(74876001)(97336001)(19580405001)(19580395003)(83322001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR06MB237; H:[192.168.0.34]; FPR:1CC4F01C.AF2697E8.F1E3736B.84E6DA6B.202D9; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Az1jPezrDSlEoxk38T1fIvKWhyw
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Apr 2014 21:58:20 -0000

On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
> <rpelletier@isoc.org> wrote:
>=20
>>> It sounds as if this will open the door to my being able to
>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>> being able to.  Yes?
>>=20
>> You could certainly use "Secretariat" but you cannot use
>> "IETF Secretariat" without violating the "IETF"
>> trademark.
>=20
> Ray, I assume that if Dave (or someone else) set themselves up
> as the International Elegant Tophat Fabrication Society, made at
> least a perfunctory effect to establish themselves as being in
> that business, established a business unit that they called
> their "Secretariat", and then advertised the result as the "IETF
> Secretariat", things could get dicey.  Given the different line
> of business, they might even be able to take out a trademark on
> "IETF Secretariat".  Right?

The "risk" applies to IETF in addition to IETF Secretariat. =20
We don't own IETF in every class of goods and services.=20
IETF bananas, top hats and car tires can be sold and =20
that won=92t violate our IETF trademark =20

People aren=92t going to be confused between the two,
just like they aren=92t for Apple computers and Apple records.

Ray
>=20
> Now, whether having a trademark registered as "IETF Secretariat"
> with whatever line of business the IETF and IETF Secretariat
> claim to be in would offer significant protection against that
> attack is far outside my knowledge or experience.
>=20
> I have enough trouble imagining someone going to the trouble to
> attempt the above as an attack that I think it would probably be
> foolish to worry about it, but it is, in principle, the
> difference between "no risk" and "no risk worth worrying about".
>=20
>    john
>=20
>=20
>=20
>=20


From nobody Fri Apr  4 15:20:35 2014
Return-Path: <pranesh@cis-india.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763561A0121; Fri,  4 Apr 2014 15:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.345
X-Spam-Level: *
X-Spam-Status: No, score=1.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FU_ENDS_2_WRDS=0.255, MIME_8BIT_HEADER=0.3, RCVD_IN_PSBL=2.7, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJNSL4e9gVEI; Fri,  4 Apr 2014 15:06:46 -0700 (PDT)
Received: from mail.cis-india.org (mail.cis-india.org [202.190.125.68]) by ietfa.amsl.com (Postfix) with ESMTP id A248F1A0150; Fri,  4 Apr 2014 15:06:45 -0700 (PDT)
Received: from [192.168.1.65] (unknown [162.243.72.125]) by mail.cis-india.org (Postfix) with ESMTPSA id 2AC13A7CB9C; Fri,  4 Apr 2014 22:04:19 +0000 (UTC)
Message-ID: <533F2CE3.3080102@cis-india.org>
Date: Fri, 04 Apr 2014 18:06:27 -0400
From: Pranesh Prakash <pranesh@cis-india.org>
Organization: Centre for Internet and Society
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, IETF Administrative Director <iad@ietf.org>,  iaoc@ietf.org
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net>
In-Reply-To: <533EF5BE.7080300@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo"
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/-ZUoPCfmGudmIDydgn5GkI1mMjU
X-Mailman-Approved-At: Fri, 04 Apr 2014 15:20:33 -0700
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Apr 2014 22:06:51 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Dave Crocker <dhc@dcrocker.net> [2014-04-004 11:11:10 -0700]:
> On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
>> The Trustees of the IETF Trust have voted an intent to renounce
>> (abandon) the =E2=80=9CIETF Secretariat=E2=80=9D
>> trademark,
>
>
> It sounds as if this will open the door to my being able to advertise
> myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?=


IAAL: Anyone can do that already.  One must remember that trademarks are =

granted on a class-wise basis.

A trademark for IETF (or IETF Secretariat) can simultaneously belong to=20
multiple companies and organization as long as they are for different=20
classes (of goods and services).

--=20
Pranesh Prakash
Policy Director, Centre for Internet and Society
T: +91 80 40926283 | W: http://cis-india.org
-------------------
Access to Knowledge Fellow, Information Society Project, Yale Law School
M: +1 520 314 7147 | W: http://yaleisp.org
PGP ID: 0x1D5C5F07 | Twitter: https://twitter.com/pranesh_prakash


--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTPyzjAAoJEFUPonS5l6Cppf4P/0KE9NaaBAgIzTNDKeah3e95
n10gHnal4BlFFtwVyzjZCqjytkcchBF9rCaa8RnkIa3ACVkfmNPcmKNsvkt51C04
aX7kqS2URedTVKZoOwABuItWCxOMVI+4JrVVrXDvP7FVeMhZyBfjvNETUT77sN74
Dx810EilkUo4C7KspRSsJf6MgIOK0DgZcygo2lJZO6W5aYzEKUmo3lAzPotl6Uqk
qIrRoKp4N7sU7P2AQGymRLLib2fMGS3VuMK8sLAHtdKT3Xh8ZMrlt2+MfkrL/Yo0
XlOy8OPjrUap8WXuYOoKykkag7wCzvnxgCJmz1DSJO7XQltv0bTzzjJDpUkXBQDE
VX3vJj6EBYA3mbviFL3OfciPFHS0hLASvkMb+jaujfYiDvdsJ50mzEPiaBHp+RcY
3yx2HNLsD/MwQ8b05AmLGoCufKMQGR47VNgHzJqsRx+5qUACOcHrZRjVU2Mipdgu
NAJdfRi4CwLzNxZXM5YY80QVYJNywZQGlowHgIH1zYK7jW3HrMRT2wHVk/QrARqu
UgBboOWUpvKzbgLKiPSogqLDDoEOlj9e6l4zIg7KIZJRXK2puCnZpFeB+jSYgPZ5
0+rnhhLt7TSWb/Objp8QgUI8yXkPt6YShrHtE6HCmD/MSwc+s+J0Hhp8ENfN51Mk
SdIf3XmQ/D7zsZHJdk09
=iISK
-----END PGP SIGNATURE-----

--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo--


From nobody Fri Apr  4 15:33:11 2014
Return-Path: <cdel@firsthand.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3438D1A014B; Fri,  4 Apr 2014 15:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.25
X-Spam-Level: 
X-Spam-Status: No, score=0.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63FfwWJmGPZY; Fri,  4 Apr 2014 15:08:59 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABA31A00CA; Fri,  4 Apr 2014 15:08:59 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=firsthand.net;  b=gcxJJWoKMUTXeyPiXMdAVkWKnUFM2SUoOPYounclwqUMP1HTPp9rzvXYHwkHJzxlFgjEo781l86KHtsNt7njp8/3069w6cbxw/OfADiB/Hkh8AQc8BfXV76SGS0Ak4wU; h=X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:Received:References:In-Reply-To:Mime-Version:Content-Transfer-Encoding:Content-Type:Message-Id:Cc:X-Mailer:From:Subject:Date:To;
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from [192.168.1.118] (host-78-149-8-96.as13285.net [78.149.8.96]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id 957EFE0004; Fri,  4 Apr 2014 23:08:51 +0100 (BST)
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com> <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
In-Reply-To: <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
X-Mailer: iPad Mail (11D167)
From: "cdel.firsthand.net" <cdel@firsthand.net>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
Date: Fri, 4 Apr 2014 23:08:51 +0100
To: Ray Pelletier <rpelletier@isoc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/icFfJY7I_SMb9dNL0_eeTSDu6lE
X-Mailman-Approved-At: Fri, 04 Apr 2014 15:33:09 -0700
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Apr 2014 22:09:03 -0000

I was about to ask under what classes IETF registrations are held?=20


Christian de Larrinaga


> On 4 Apr 2014, at 22:57, Ray Pelletier <rpelletier@isoc.org> wrote:
>=20
>=20
>> On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> wrote:
>>=20
>>=20
>>=20
>> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
>> <rpelletier@isoc.org> wrote:
>>=20
>>>> It sounds as if this will open the door to my being able to
>>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>>> being able to.  Yes?
>>>=20
>>> You could certainly use "Secretariat" but you cannot use
>>> "IETF Secretariat" without violating the "IETF"
>>> trademark.
>>=20
>> Ray, I assume that if Dave (or someone else) set themselves up
>> as the International Elegant Tophat Fabrication Society, made at
>> least a perfunctory effect to establish themselves as being in
>> that business, established a business unit that they called
>> their "Secretariat", and then advertised the result as the "IETF
>> Secretariat", things could get dicey.  Given the different line
>> of business, they might even be able to take out a trademark on
>> "IETF Secretariat".  Right?
>=20
> The "risk" applies to IETF in addition to IETF Secretariat. =20
> We don't own IETF in every class of goods and services.=20
> IETF bananas, top hats and car tires can be sold and =20
> that won=E2=80=99t violate our IETF trademark =20
>=20
> People aren=E2=80=99t going to be confused between the two,
> just like they aren=E2=80=99t for Apple computers and Apple records.
>=20
> Ray
>>=20
>> Now, whether having a trademark registered as "IETF Secretariat"
>> with whatever line of business the IETF and IETF Secretariat
>> claim to be in would offer significant protection against that
>> attack is far outside my knowledge or experience.
>>=20
>> I have enough trouble imagining someone going to the trouble to
>> attempt the above as an attack that I think it would probably be
>> foolish to worry about it, but it is, in principle, the
>> difference between "no risk" and "no risk worth worrying about".
>>=20
>>   john
>=20


From nobody Tue Apr  8 15:32:59 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914541A04AF for <wgchairs@ietfa.amsl.com>; Tue,  8 Apr 2014 14:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.701
X-Spam-Level: 
X-Spam-Status: No, score=-101.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ypxdKT8JVaf6 for <wgchairs@ietfa.amsl.com>; Tue,  8 Apr 2014 14:50:41 -0700 (PDT)
Received: from dkim.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7E21A02A8 for <wgchairs@ietf.org>; Tue,  8 Apr 2014 14:50:40 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2734; t=1396993760; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=KsRubGYopeL0NsUvsG1ff98SwgQ=; b=LiVlgTvKnLvdU92CPirp uka6FuzlICkqLEvQ/4n4F4OhkQq1ozfQtjSMf8cmneaPBuds/djs5QGxOF+mj2/R s4bfwhcvBRkSTH2jy7oWTBGr3xFg8uFfi0dX4yFEqzJFJ1AMgsjZHoIYiMtGnjiX vroGkna+RGk7irMs3YCQCf8=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for wgchairs@ietf.org; Tue, 08 Apr 2014 17:49:20 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 102344081.3.3520; Tue, 08 Apr 2014 17:49:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2734; t=1396993706; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=jgRSVXx 9DqW2Bc2Lhs5AtWCVjDJNICOM+HylXtwdvWo=; b=r3oLUqykKvq9HHUdBehAE+6 +tN7b1+pnSy6q1PhgWzFDXFskFkIqWd+694RhsleT+2OdzeJrXplOpJMu3seobFP T+KuVsJQUuWmLmFGmXqp9PDXv1oZc0TGN4AG1IvKhv6kGSaQnTNe48SHRqnwen46 pPl11baxFnT0u08aqBrc=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for wgchairs@ietf.org; Tue, 08 Apr 2014 17:48:26 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 121882156.9.3304; Tue, 08 Apr 2014 17:48:25 -0400
Message-ID: <53446EDF.6090504@isdg.net>
Date: Tue, 08 Apr 2014 17:49:19 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/3sxCFmah3MMobzOi7huSj-fJqaw
X-Mailman-Approved-At: Tue, 08 Apr 2014 15:32:57 -0700
Cc: iaoc@ietf.org, iab@iab.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Apr 2014 21:50:42 -0000

I don't see a legal issue or lost of trademark infringement protection 
for the reason stated.  I would suggest that, if necessary, the IETF 
could still legally list "IETF Secretariat" as a trademark <TM>, just 
not registered (R).

--
HLS

On 4/4/2014 2:00 PM, IETF Administrative Director wrote:
> All;
>
> The Trustees of the IETF Trust have voted an intent to renounce (abandon) the “IETF Secretariat”
> trademark, but before taking any action they desire to hear from the community.
>
> Specifically:
>
> It is the Trustees’ intent to:
>
> 1. Not renew the “IETF Secretariat” trademark, Registration 3860848, in the European Community
> at an approximate cost of $5,000 USD for a ten-year period when due on May 28, 2014, and
> thereby renounce the trademark as having no foreseeable future value in accordance with Article 7.1a
> of the Amended and Restated Trust Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.
> The trademark has no foreseeable future value as the “IETF” trademark is registered in the European
> Community and its use with Secretariat is protected.
>
> 2. Not renew the “IETF Secretariat” trademark, Registration 2392833, in the United States at an unknown
> future cost when the trademark expires on October 10, 2020, and thereby renounce the trademark as
> having no foreseeable future value in accordance with Article 7.1a of the Amended and Restated Trust
> Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The trademark has no foreseeable
> future value as the “IETF” trademark is registered in the United States and its use with Secretariat is
> protected.
>
> Authority:
>
> The Trustees have the authority to renounce the trademark in accordance with Article 7.1a of the
> Amended and Restated Trust Agreement after consulting with the Beneficiary.
> <http://trustee.ietf.org/trust-agreement-2014.html>
>
> This Article states in relevant part:
> "the Trustees may, after due consultation with the Beneficiary, dispose of, assign, sell, transfer,
> renounce, convey or terminate Trust Assets that are of no current or foreseeable future value to
> the Beneficiary and which require the expenditure of funds to retain.This exception does not
> include RFCs.”
>
> The purpose of this announcement is to begin the consultation with the Beneficiary, the IETF
> Community.  This thirty (30) day comment period expires on 5 May 2014.  The Trustees will consider
> the Community input before making a decision whether to renounce the “IETF Secretariat” trademark
> or not.
>
> Your feedback is appreciated.
>
> Thanks
> Ray Pelletier
> IETF Administrative Director
> Trustee
> IETF Trust
>
>
>



From nobody Tue Apr  8 16:05:37 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67EDF1A0767; Tue,  8 Apr 2014 16:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-GZ33UmVKBa; Tue,  8 Apr 2014 16:05:27 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id DDD261A075C; Tue,  8 Apr 2014 16:05:26 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so1617488yho.32 for <multiple recipients>; Tue, 08 Apr 2014 16:05:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VcbWQmbw3rPntD9Q5dJz/9jQxrJs6Ctb7jjdwTUxU9k=; b=jEyPHWSKcl8hvsBSTmOhO9GJJs7vXzLAhGsYx/Gzg0Z68YAds9AXUD4hf54FoJiU5s MOCAoJuF3EpF2R/IsCyrRrFnaD4R9opd1O+9/Wnlao8YKucSSrHOMvK180EEfrFpJ28J vcrcAg/uDgrdDFIyj2PlpQ2MqNn3TcUkmkVJNn/cy5gXHZY7NAqNRYc0Lnyji8Z4kn4j u2uPZ5+ShbvWZJjwMAvc7sEptTwpEVpyIq9Nb3nS9mKXBO3uSMAIevG7Gtv035SC44Ou nNVXdIGGxKm1URpzRfr6xcZDn9+yq9e4JTQkw9QTU2zVfgwrnQJAFC0vcjVT7jDGOoQU Ks2A==
MIME-Version: 1.0
X-Received: by 10.236.85.45 with SMTP id t33mr9202655yhe.74.1396998326576; Tue, 08 Apr 2014 16:05:26 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Tue, 8 Apr 2014 16:05:26 -0700 (PDT)
In-Reply-To: <53446EDF.6090504@isdg.net>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <53446EDF.6090504@isdg.net>
Date: Wed, 9 Apr 2014 00:05:26 +0100
Message-ID: <CADnDZ8972WfDumGrSSK3a9fuJSAv69d3_O1t2sBn0nDT5bTbLA@mail.gmail.com>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=20cf3005dd4e020f1004f6900562
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/3yZytDrJvMAWFuMVDlPtQt2LBgo
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 08 Apr 2014 23:05:28 -0000

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

On Tuesday, April 8, 2014, Hector Santos wrote:

> I don't see a legal issue or lost of trademark infringement protection for
> the reason stated.  I would suggest that, if necessary, the IETF could
> still legally list "IETF Secretariat" as a trademark <TM>, just not
> registered (R)


Yes. However, I don't understand what is the real value of that
registered mark. I don't understand why it was started/continued in the
first place for such volunteering organisation. If IETF
community agree/identifies that there are some values, then we can find
alternatives. Mostly we only need the one IETF trademark.

AB



>

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

<br>On Tuesday, April 8, 2014, Hector Santos  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">I don&#39;t see a legal issue or lost of trademark infringeme=
nt protection for the reason stated. =A0I would suggest that, if necessary,=
 the IETF could still legally list &quot;IETF Secretariat&quot; as a tradem=
ark &lt;TM&gt;, just not registered (R)</blockquote>
<div><br></div><div>Yes. However,=A0I don&#39;t understand what is the real=
=A0value of that registered=A0mark. I don&#39;t understand why it was start=
ed/continued=A0in the first place for such volunteering organisation. If IE=
TF community=A0agree/identifies that=A0there are some values, then we can f=
ind alternatives. Mostly we only need the=A0one IETF=A0trademark.=A0</div>
<div><br></div><div>AB</div><div><br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
</blockquote>

--20cf3005dd4e020f1004f6900562--


From nobody Wed Apr  9 10:48:13 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0984B1A02D4; Wed,  9 Apr 2014 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.502
X-Spam-Level: 
X-Spam-Status: No, score=-100.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GN60jYj02W8b; Wed,  9 Apr 2014 10:48:02 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0144.outbound.protection.outlook.com [207.46.163.144]) by ietfa.amsl.com (Postfix) with ESMTP id 3B53E1A0303; Wed,  9 Apr 2014 10:48:01 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.913.9; Wed, 9 Apr 2014 17:47:58 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
Date: Wed, 9 Apr 2014 13:47:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7FA1855F-AE17-41DC-B0CD-1A11B293C5A3@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com> <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org> <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
To: cdel.firsthand.net <cdel@firsthand.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BLUPR06CA004.namprd06.prod.outlook.com (10.255.223.142) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 01762B0D64
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(377454003)(51704005)(199002)(189002)(24454002)(74502001)(92566001)(77982001)(81342001)(99396002)(92726001)(80976001)(57306001)(82746002)(46102001)(50466002)(79102001)(20776003)(50226001)(83322001)(4396001)(88136002)(36756003)(74662001)(89996001)(93916002)(19580405001)(86362001)(42186004)(87976001)(31966008)(62966002)(81542001)(19580395003)(23746002)(83072002)(80022001)(66066001)(87286001)(77156001)(83716003)(33656001)(76482001)(47776003)(85852003)(50986999)(76176999); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.34]; FPR:1CC4F01C.AF2297E8.F1E3736B.84E6D9AB.20336; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Lzj8_XDGVcn84E9BkZg57UTAaYo
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Apr 2014 17:48:07 -0000

=20
On Apr 4, 2014, at 6:08 PM, cdel.firsthand.net <cdel@firsthand.net> =
wrote:

> I was about to ask under what classes IETF registrations are held?=20

IETF is in Class 42.

The IETF Logo is in the following classes:  9, 35, 42

=93IETF Secretariat=94 is in: 35, 42.

Ray


>=20
>=20
> Christian de Larrinaga
>=20
>=20
>> On 4 Apr 2014, at 22:57, Ray Pelletier <rpelletier@isoc.org> wrote:
>>=20
>>=20
>>> On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> =
wrote:
>>>=20
>>>=20
>>>=20
>>> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
>>> <rpelletier@isoc.org> wrote:
>>>=20
>>>>> It sounds as if this will open the door to my being able to
>>>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>>>> being able to.  Yes?
>>>>=20
>>>> You could certainly use "Secretariat" but you cannot use
>>>> "IETF Secretariat" without violating the "IETF"
>>>> trademark.
>>>=20
>>> Ray, I assume that if Dave (or someone else) set themselves up
>>> as the International Elegant Tophat Fabrication Society, made at
>>> least a perfunctory effect to establish themselves as being in
>>> that business, established a business unit that they called
>>> their "Secretariat", and then advertised the result as the "IETF
>>> Secretariat", things could get dicey.  Given the different line
>>> of business, they might even be able to take out a trademark on
>>> "IETF Secretariat".  Right?
>>=20
>> The "risk" applies to IETF in addition to IETF Secretariat. =20
>> We don't own IETF in every class of goods and services.=20
>> IETF bananas, top hats and car tires can be sold and =20
>> that won=92t violate our IETF trademark =20
>>=20
>> People aren=92t going to be confused between the two,
>> just like they aren=92t for Apple computers and Apple records.
>>=20
>> Ray
>>>=20
>>> Now, whether having a trademark registered as "IETF Secretariat"
>>> with whatever line of business the IETF and IETF Secretariat
>>> claim to be in would offer significant protection against that
>>> attack is far outside my knowledge or experience.
>>>=20
>>> I have enough trouble imagining someone going to the trouble to
>>> attempt the above as an attack that I think it would probably be
>>> foolish to worry about it, but it is, in principle, the
>>> difference between "no risk" and "no risk worth worrying about".
>>>=20
>>>  john
>>=20


From nobody Thu Apr 10 12:35:37 2014
Return-Path: <sandy@tislabs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 131D91A0422 for <wgchairs@ietfa.amsl.com>; Thu, 10 Apr 2014 12:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhlzq2ps8lAS for <wgchairs@ietfa.amsl.com>; Thu, 10 Apr 2014 12:35:32 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id 704611A0420 for <wgchairs@ietf.org>; Thu, 10 Apr 2014 12:35:32 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 8037628B0077 for <wgchairs@ietf.org>; Thu, 10 Apr 2014 15:35:31 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 682D81F8032; Thu, 10 Apr 2014 15:35:31 -0400 (EDT)
From: Sandra Murphy <sandy@tislabs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: doing a global email address change
Date: Thu, 10 Apr 2014 15:35:31 -0400
Message-Id: <FF8A3409-67F8-4613-81A6-DEDC61750437@tislabs.com>
To: wgchairs@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/h-jdgDfVkplM85Oii63zQLGqmoU
Cc: Sandra Murphy <sandy@tislabs.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Apr 2014 19:35:34 -0000

Thanks to a suggestion on this list, I was able to globally change my =
email address.

Two things to note:

The wgchairs wiki point to the instructions page =
http://wiki.tools.ietf.org/group/wgchairs/wiki/GlobalEmailChange.

The instructions tell you how to do a global email address change from =
your membership configuration page for the ietf list =
[https://www.ietf.org/mailman/options/ietf/<email-address>]  You can do =
the same from your membership configuration page for any mailing list.  =
(You don't have to join the ietf list in order to make the global =
change.)

You might also want to use the membership configuration page to make a =
global password change.  This could be useful, since your old passwords =
for each mailing list do not work for your new subscription.

One comment:

I tried to add this to the wiki page.  I logged in with my tools =
password and could make changes to my working group wiki page, but the =
wgchairs wiki wanted "IETF" authorization.  Others have made changes to =
the wgchairs wiki page - any clues how to make that work?

--Sandy=


From nobody Mon Apr 14 08:49:36 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4C2A1A04E9 for <wgchairs@ietfa.amsl.com>; Mon, 14 Apr 2014 08:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.171
X-Spam-Level: 
X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KajrXFGtz2lY for <wgchairs@ietfa.amsl.com>; Mon, 14 Apr 2014 08:49:33 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id C92BA1A03D7 for <wgchairs@ietf.org>; Mon, 14 Apr 2014 08:49:33 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3EFnU6M080441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for <wgchairs@ietf.org>; Mon, 14 Apr 2014 10:49:31 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89] claimed to be unnumerable.local
Message-ID: <534C0389.2060901@nostrum.com>
Date: Mon, 14 Apr 2014 10:49:29 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "<wgchairs@ietf.org>" <wgchairs@ietf.org>
Subject: Fwd: Logging into the datatracker
References: <534C0366.10600@nostrum.com>
In-Reply-To: <534C0366.10600@nostrum.com>
X-Forwarded-Message-Id: <534C0366.10600@nostrum.com>
Content-Type: multipart/alternative; boundary="------------070303000101040506020800"
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/GYlVXR47U4ysHJ7kaJ7mW0A-kgA
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 14 Apr 2014 15:49:35 -0000

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

In case you aren't frequently catching up on ietf general:


-------- Original Message --------
Subject: 	Logging into the datatracker
Date: 	Mon, 14 Apr 2014 10:48:54 -0500
From: 	Robert Sparks <rjsparks@nostrum.com>
To: 	ietf@ietf.org <ietf@ietf.org>



Today's datatracker release changed the way you sign in, and has added
the ability to sign out.

See <https://datatracker.ietf.org/release/> for details.

RjS

p.s. As usual, if you need to request a password reset, you can do so at
<http://datatracker.ietf.org/accounts/>





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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    In case you aren't frequently catching up on ietf general:<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>Logging into the datatracker</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Mon, 14 Apr 2014 10:48:54 -0500</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td>Robert Sparks <a class="moz-txt-link-rfc2396E" href="mailto:rjsparks@nostrum.com">&lt;rjsparks@nostrum.com&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:ietf@ietf.org">&lt;ietf@ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Today's datatracker release changed the way you sign in, and has added 
the ability to sign out.

See <a class="moz-txt-link-rfc2396E" href="https://datatracker.ietf.org/release/">&lt;https://datatracker.ietf.org/release/&gt;</a> for details.

RjS

p.s. As usual, if you need to request a password reset, you can do so at
<a class="moz-txt-link-rfc2396E" href="http://datatracker.ietf.org/accounts/">&lt;http://datatracker.ietf.org/accounts/&gt;</a>


</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------070303000101040506020800--


From nobody Mon Apr 14 22:49:54 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84E3F1A0348 for <wgchairs@ietfa.amsl.com>; Mon, 14 Apr 2014 22:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlTrIhyEvoSH for <wgchairs@ietfa.amsl.com>; Mon, 14 Apr 2014 22:49:52 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CCEBD1A033B for <wgchairs@ietf.org>; Mon, 14 Apr 2014 22:49:51 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id w7so6419661lbi.2 for <wgchairs@ietf.org>; Mon, 14 Apr 2014 22:49:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=znRAaq8lo5FOf1+jUsV2eA5S0jmyWax/fIBTF4/0/QQ=; b=GsFCy17aeuGIoMiZZkeaag1+kBnTw3ChoREWkHeVqUpM480FItmlLYuKlS1IeX7CuS 2hiRrVleccg29UP2KW23YCNbwYDiPOTRL2tXZA87Y+MQinyF0KlkhZrXKxGdYTHC6rvj TXfRRWzABqYLf/idRFuLh3e6Ym1LqOxf37PqoAZKUoZ5Sl8rxJZqFc9pwC/IoXkZr0m5 D2qvmUgPa+A2MJNzsKmEqFRExqPHAT2GzdmpoKbvi/Z5xdT5y6LjO0NqVudsnpluVprE EYFAsJJSm0OF+Uq3lOIUiYI5B5gmGv7MixXEvi7NnGx2UODT01SzE2aLyQakM4EUdZHO e5iA==
X-Received: by 10.112.131.65 with SMTP id ok1mr137503lbb.51.1397540988514; Mon, 14 Apr 2014 22:49:48 -0700 (PDT)
Received: from [10.37.155.233] ([77.95.242.69]) by mx.google.com with ESMTPSA id lm5sm18013413lac.13.2014.04.14.22.49.47 for <wgchairs@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 22:49:47 -0700 (PDT)
Message-ID: <534CC864.1050008@gmail.com>
Date: Tue, 15 Apr 2014 08:49:24 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: issue tracker.. issues
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/I_4mBDCXxf4mpKLLg0nS7eLEpfs
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Apr 2014 05:49:53 -0000

Hi again,

Some more odd stuff.. what to do when:
1) tickets belong to a document that does not exist as a WG document
2) a WG document does not show up in the "Component" pull down menu
?

- Jouni


From nobody Tue Apr 15 08:45:47 2014
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B811A049A for <wgchairs@ietfa.amsl.com>; Tue, 15 Apr 2014 08:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixgMq1EGvSn1 for <wgchairs@ietfa.amsl.com>; Tue, 15 Apr 2014 08:45:41 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id EAD811A0176 for <wgchairs@ietf.org>; Tue, 15 Apr 2014 08:45:40 -0700 (PDT)
Received: from h25n7-s-oev-a31.ias.bredband.telia.com ([81.229.146.25]:50958 helo=vigonier.tools.ietf.org) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1Wa5YH-0007ax-OJ; Tue, 15 Apr 2014 17:45:37 +0200
Message-ID: <534D541C.2020507@levkowetz.com>
Date: Tue, 15 Apr 2014 17:45:32 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>, wgchairs@ietf.org
References: <534CC864.1050008@gmail.com>
In-Reply-To: <534CC864.1050008@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 81.229.146.25
X-SA-Exim-Rcpt-To: jouni.nospam@gmail.com, wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: issue tracker.. issues
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/yIpMrZY2F-lUm4RV3JFs_dXlZ-Q
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Apr 2014 15:45:45 -0000

Hi Jouni,

On 2014-04-15 07:49 Jouni Korhonen said the following:
> Hi again,
> 
> Some more odd stuff.. what to do when:
> 1) tickets belong to a document that does not exist as a WG document

Manually add the document as a component (all chairs have Admin rights
for their issue trackers

> 2) a WG document does not show up in the "Component" pull down menu
> ?

Email me so I can look for the bug :-)


Best regards,

	Henrik


From nobody Wed Apr 16 22:43:01 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3DD1A0066 for <wgchairs@ietfa.amsl.com>; Wed, 16 Apr 2014 22:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dKEcYof5gnt for <wgchairs@ietfa.amsl.com>; Wed, 16 Apr 2014 22:42:58 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id BE9441A002A for <wgchairs@ietf.org>; Wed, 16 Apr 2014 22:42:57 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id n15so8821252lbi.41 for <wgchairs@ietf.org>; Wed, 16 Apr 2014 22:42:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=AyVg+LSDGzKgBY+FecnKCEfARhYojorU5hE7IJh3gY8=; b=uSG4Q5ahZ/kMVaqKWeQscUPJDVxpD8Yoi2Fga7QLF4ejbNA2x9CbsQBvDufVJz7k+R +OoXNodsY4Q2Z7d1EDgWEuRVHSxei7+pqpu17VnpW3T64JgFgKr5NsugakG7sXBEKd4l J69/EJ+yU9vKYVEWhkqSydxJhnGRBnG+efuAr57IvzGYjR80GKoAAMEg2sPEWOou9kZ7 9zSe9mY8iEVwrAGAtMap6Gp0ocTQ9SG5EtY1lTgq96xomELD0eLgH1gtMLoE0FXAtZoh 7soGKlvVnYzBmySJTAy6r5mD6qWCtxweXIcyz2ths9HTegYLjEd9b5EIohJ6mzzX79pW CluA==
X-Received: by 10.112.139.6 with SMTP id qu6mr5718713lbb.5.1397713373488; Wed, 16 Apr 2014 22:42:53 -0700 (PDT)
Received: from [192.168.250.176] ([194.100.71.98]) by mx.google.com with ESMTPSA id z2sm24102529laz.4.2014.04.16.22.42.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 22:42:52 -0700 (PDT)
Message-ID: <534F69C9.80105@gmail.com>
Date: Thu, 17 Apr 2014 08:42:33 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: issue tracker.. issues
References: <534CC864.1050008@gmail.com> <534D541C.2020507@levkowetz.com>
In-Reply-To: <534D541C.2020507@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/5eI7JnaEmPg_Ixewcv5CSrlp7_Q
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Apr 2014 05:42:59 -0000

Henrik,

4/15/2014 6:45 PM, Henrik Levkowetz kirjoitti:
> Hi Jouni,
>
> On 2014-04-15 07:49 Jouni Korhonen said the following:
>> Hi again,
>>
>> Some more odd stuff.. what to do when:
>> 1) tickets belong to a document that does not exist as a WG document
>
> Manually add the document as a component (all chairs have Admin rights
> for their issue trackers

Great. Did not know about this! This one seems to be the way to fix things.

- Jouni


>
>> 2) a WG document does not show up in the "Component" pull down menu
>> ?
>
> Email me so I can look for the bug :-)

Doing the 1) above, this sorted out..

Thanks,
	Jouni


>
>
> Best regards,
>
> 	Henrik
>


From nobody Mon Apr 21 15:24:44 2014
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99D3B1A02D1; Mon, 21 Apr 2014 15:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lgW58ePekKNk; Mon, 21 Apr 2014 15:24:36 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 512E81A0067; Mon, 21 Apr 2014 15:24:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 90th IETF - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 5.3.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140421222436.23895.20687.idtracker@ietfa.amsl.com>
Date: Mon, 21 Apr 2014 15:24:36 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/qHuTNKBbYZqekJMsJZe3QrrsaGM
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Apr 2014 22:24:41 -0000

-----------------------------------------------------------------
90th IETF – Toronto, ON, Canada
Meeting Dates: July 20 - 25, 2014
-----------------------------------------------------------------

We are accepting scheduling requests for all Working Groups, BOFs, and Research Groups starting today.  

NOTE: Please ensure your list of conflicts is complete and up to date prior to submitting your session request.

The milestones and deadlines for scheduling-related activities are as follows:
Cut-off dates are subject to change.

•	2014-04-21 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool.
•	2014-06-06 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool.
•	2014-06-06 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
•	2014-06-13 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
•	2014-06-20 (Friday): Preliminary agenda published for comment.
•	2014-06-23 (Monday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
•	2014-06-27 (Friday): Final agenda to be published.
•	2014-07-07 (Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
•	2014-07-14 (Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
•	2014-08-15 (Friday): Proceedings submission cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
•	2014-09-05 (Friday): Proceedings submission corrections cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

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

The URL for the tool is:
https://datatracker.ietf.org/secr/sreq/

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

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the agendas for your Working Group sessions as early as possible.  Draft Working Group agendas are due Monday, July 7th, 2014 at UTC 23:59.  Revised Working Group agendas are due no later than Monday, July 14th, 2014 at UTC 23:59.  The proposed agenda for a BOF session should be submitted along with your request for a session.  Please be sure to copy your Area Director on that message.

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

The URL for the tool is:

https://datatracker.ietf.org/secr/proceedings/

Additional information about this tool is available at:

http://www.ietf.org/wg/meeting-materials.html

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

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

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

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

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

https://datatracker.ietf.org/secr/sreq/

Instructions for using the tool are available at:

http://www.ietf.org/wg/request-tool-instructions.html

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

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

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

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

3. A Working Group may request either one or two sessions.  If your Working Group requires more than two sessions, then your request must be approved by an Area Director.  Additional sessions will be assigned, based on availability, after Monday, June 23rd, 2014, the cut-off date for requests to reschedule a session.

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

    a. Working Group or BOF full name with acronym in brackets: 
    b. AREA under which Working Group or BOF appears:
    c. CONFLICTS you wish to avoid, please be as specific as possible:
    d. Expected Attendance:
    e. Special requests:
    f. Number of sessions:
    g. Length of session: 
       - 1 hour 
       - 1 1/2 hours
       - 2 hours 
       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions, please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and Procedures" (http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors with their e-mail addresses:

IETF Chair 
        Jari Arkko <jari.arkko@piuha.net>

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

Internet Area (int) 
        Brian Haberman <brian@innovationslab.net> 
        Ted Lemon <ted.lemon@nominum.com>

Operations & Management Area (ops) 
        Benoit Claise <bclaise@cisco.com> 
        Joel Jaeggli <joelja@bogus.com>

Real-time Applications and Infrastructure Area (rai)
        Richard Barnes <rlb@ipv.sx>  
        Alissa Cooper <alissa@cooperw.in>  

Routing Area (rtg) 
        Alia Atlas <akatlas+iesg@gmail.com>
        Adrian Farrel <adrian@olddog.co.uk>  

Security Area (sec) 
       Stephen Farrell <stephen.farrell@cs.tcd.ie>
       Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>  

Transport Area (tsv) 
       Spencer Dawkins  <spencerdawkins.ietf@gmail.com>
       Martin Stiemerling <martin.stiemerling@neclab.eu> 

 ===========================================================
89th IETF Meeting Attendance Numbers

6lo - 88
6man - 165
6tisch - 49
abfab – 22
ace (BoF) - 123
alto  - 57
appsawg/apparea - 129
aqm - 110
avtcore - 44
avtext – 52
bfcpbis - 15
bmwg - 18
ccamp - 47
ccamp (2nd session) - 39
cdni – 42
cfrg - 52
clue – 32
clue (2nd session) - 26
core - 59
core (2nd session) – 62
dane - 133
dbound (BoF) - 127
dhc - 63
dice - 72
dime - 18
dispatch - 67
dmm – 45
dnse (BoF) - 206
dnsop – 118
dnsop (2nd session) – not provided
dnssd - 95
ecrit - 28
eman – not provided
eppext - 28
geopriv – 40
grow - 49
homenet - 136
httpauth - 65
httpbis - 113
httpbis (2nd session) - 107
i2rs - 205
iccrg (RG) - 125
icnrg (RG) - 105
idr - 102
igovupdate BoF - 144
insipid - 24
intarea (AG) - 129
ippm - 70
ipsecme - 50
IRTF Open Meeting - 65
isis - 67
jose - 38
json - 36
karp – not provided
kitten - 38
l2vpn - 101
l3vpn - 67
lisp - 70
lmap - 48
lwig - 38
manet - 28
mboned - 16
mif – 48
mile - 29
mmusic - 59
mmusic (2nd session) - 58
mpls - 98
mpls (2nd session) - 99
mptcp - 105
ncrg (RG) - 52
netconf - 73
netext - 29
netmod - 47
nfsv4 - 11
nmrg (RG) - 40
ntp (combined with tictoc) - 16
nvo3 - 174
nwcrg (PRG) - 53
oauth - 54
opsawg/opsarea - 72
ospf - 28
paws – 19
payload - 30
pce - 75
pcp - 39
pim - 17
ppsp - 18
precis - 33
pwe3 - 50
radext - 25
rfcform - 47
rmcat - 70
roll - 45
rtcweb - 136
rtcweb (2nd session) - 119
rtgarea (AG) - 97
rtgwg - 77
saag (AG) - 108
sacm - 27
scim - 25
sdnrg (RG) – 198
sfc - 244
sidr – 69
sipcore – 49
sipcore (2nd session) - 44
siprec – 22
softwire - 48
spring - 90
stir - 61
straw – 41
sunset4 – 49
taps (BoF) – 162
tcmtf - 64
tcpm – 66
tcpm (2nd session) - 53
tictoc (combined with ntp) - 16
tls – 107
tram (BoF) – 52
trans (BoF) - 65
trill - 34
tsvarea (AG) - 89
tsvwg - 71
tsvwg (2nd session) – 68
uta - 85
v6ops - 100
v6ops (2nd session) – 71
vnfpool (BoF) - 170
weirds - 55
wpkops - 28
xmpp - 36
xrblock - 19


From nobody Tue Apr 22 07:46:32 2014
Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2F61A04C2; Tue, 22 Apr 2014 07:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.2
X-Spam-Level: 
X-Spam-Status: No, score=-3.2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_INVITATION=-2, GB_I_LETTER=-2] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ZBVLJbekdiO; Tue, 22 Apr 2014 07:46:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 550CF1A049E; Tue, 22 Apr 2014 07:46:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 90 - Registration Now Open!
X-Test-IDTracker: no
X-IETF-IDTracker: 5.3.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140422144623.7409.84870.idtracker@ietfa.amsl.com>
Date: Tue, 22 Apr 2014 07:46:23 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/fF57Elvar36tXvGKbwCruCxhpSQ
Cc: wgchairs@ietf.org, recentattendees@ietf.org, irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf-secretariat@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: Tue, 22 Apr 2014 14:46:28 -0000

90th IETF Meeting
Toronto, ON, Canada
July 20-25, 2014
Host: Ericsson

Meeting venue:  Fairmont Royal York Toronto: http://www.fairmont.com/royal-york-toronto/

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

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  Companion Program
5.  IETF 90 Wiki


1. Registration
A. Early-Bird Registration - USD 650.00, if paid in full prior to 23:59 UTC 11 July 2014.
B. After Early-Bird cutoff - USD 800.00
C. Full-time Student Registrations - USD 150.00 (with proper ID)
D. One Day Pass Registration - USD 350.00
E. Registration Cancellation   
          Cut-off for registration cancellation is Monday,
          14 July 2014 at UTC 23:59.
          Cancellations are subject to a 10% (ten percent)
          cancellation fee if requested by that date and time.
F. Online Registration and Payment ends Friday, 18 July 2014, 1700 local Toronto time.
G. On-site Registration starting Sunday, 20 July 2014 at 1100 local Toronto time.

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

After you complete the registration process, you can request an electronic IETF letter of invitation as well. The registration system also allows for you to request a hard copy IETF letter of invitation. You may also request one at a later time by following the link provided in the confirmation email.

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

3.  Accommodations
The IETF is holding a block of guest rooms at the Fairmont Royal York Toronto, the meeting venue. Room Rates include in-room high-speed Internet access. HST Taxes of 13% and GTHA Fee of 3% are NOT included in the room rates and are subject to change. Room rates at the Fairmont Royal York DO NOT include breakfast. A continental breakfast will be included as part of your IETF meeting registration fee and will be available from 8:00am - 9:00am Monday-Friday at the meeting venue.

Reservations Cut-off Date: 
	Fairmont Royal York Toronto - 30 June 2014

For additional information on rates and policies, please visit: http://www.ietf.org/meeting/90/hotel.html

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

Benefits include:
- A special welcome reception for companions from 1630-1730 on Sunday, 20 July
- Ability to attend the official Welcome Reception from 1700-1900 on Sunday, 20 July
- A distinctive meeting badge that grants access to the venue (not to be used to attend working sessions)
- Participation in a separate companion email list if you choose to communicate and make plans with other IETF Companions.

You can register your companion at any time via the IETF website through the "Attendee Self-Service Portal" at https://www.ietf.org/registration/ietf90/selfservice.py or onsite at the meeting.

A companion may join the 90 Companions mailing list without any cost at:
https://www.ietf.org/mailman/listinfo/90companions

5.  IETF 90 Wiki
The IETF 90 meeting wiki (Your Wiki) has been created for the attendees of IETF 90 meeting to exchange information.

Your IETF 90 (Toronto) wiki can be found here:
http://www.ietf.org/registration/MeetingWiki/wiki/ietf90
and is also accessible from the Toronto meeting page on the IETF website.

If you are registered for IETF 90, a user account has been automatically created for you on this Wiki. Your user name is the email address you registered under, and your initial password is your 10 digit confirmation number. You can change your password in your profile settings. 

Only 88 days until the Toronto IETF!


From nobody Tue Apr 22 10:30:44 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 856B01A06B2 for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 10:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCVn2xSbU_dj for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 10:30:30 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4231A06BB for <wgchairs@ietf.org>; Tue, 22 Apr 2014 10:30:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1672; q=dns/txt; s=iport; t=1398187821; x=1399397421; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=9aUkdhZa7C+e0BCdkTWM5RwIoRMv/jAnbMr4oaszzjA=; b=jZXJlyft+nUU4+fwR8lUBfPUIYVNcmLrRpGYBjoMCQqrJl484YpgD3/1 y0+efn6t11mwjSJwuENKLC9BUv1Zc2Mqq9v+l8h1gtaa7jNNXX8xZFTCU ECWNfI2zIy/GNPBUU+gJzKvc+D+jl7pQ3l3p/Fa9DJpowFXoTyNZ7EO05 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFALemVlOtJV2c/2dsb2JhbABZgwaBJsQYgRYWdIIsbh0BGmYXDgIEiFSaI7JEF45dhDgEiSyPRJJSgzGCKw
X-IronPort-AV: E=Sophos;i="4.97,905,1389744000"; d="scan'208";a="37816271"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 22 Apr 2014 17:30:21 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3MHULod021937 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <wgchairs@ietf.org>; Tue, 22 Apr 2014 17:30:21 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Tue, 22 Apr 2014 12:30:20 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "'WG Chairs'" <wgchairs@ietf.org>
Subject: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKg==
Date: Tue, 22 Apr 2014 17:30:20 +0000
Message-ID: <CF7BF13E.B1AE%repenno@cisco.com>
In-Reply-To: <5122C634.2020903@bbiw.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.145.177]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2B8CEDF0BA3F824D939A156825EF987B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/P_nJZemu8Z8OJChLol_Evq-3jMQ
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Apr 2014 17:30:35 -0000

Hi,

I=B9ve been thinking about how some Wgs get stuck and others loose steam an=
d
would like to propose an optional way to structure new WGs.

I think the delay or failure of many WGs can be attribute as the way we
IETF structures WGs.

When a WG is formed there is lots of energy, many drafts, people with
running code (yes, these people still exist) and great participation. But
then, the IETF step on the brakes by following a cookie cutter approach of
asking for a problem statement draft, some form of architecture draft and
produces, most often than not, a set in stone charter.  This alone makes a
boatload of people leave the WG effort. Some of these folks have even
running code (I=B9ve been there) or drafts that many folks are interested
but can not be discussed until the current charter is done.

And the WG struggles on and on because of the very fact that some of the
folks with energy that could drive the WG will not wait on the sidelines
for 2 years until rechartering so that maybe, just maybe, their draft can
get on the charter.

My proposal is that certain WGs should be formed with some overall charter
and the definite charter should be written _after_ say, two official WG
meetings, where lots of discussion on mailing list and presentations
happen. Then the charter becomes the most important drafts people are
interested. In this case for example, the problem statement becomes in
fact those drafts.=20

Maybe this is already allowed but it is not known or not encouraged. At
least if possible it would be good to experiment with that approach in
some of the popular or struggling WGs.

Thanks,

-Reinaldo



From nobody Tue Apr 22 11:04:24 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822E21A06C7 for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m3VimLkz1boR for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:04:15 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1D51A06C5 for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:04:14 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id q58so5370477wes.34 for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:04:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LXAxFzXWJ3gzkMpD/f6BIZuGTn/SrMk34qEBSczE6nc=; b=V40b65jt9MEb7SLo9934lhOWa4yvxOOjvRmCIPWKWHilZ8Zq6F/LoIZUBmh8YJGT0o nbaHsN40aCk1AWUmh/hE6mpuU0F8dVgsfXT9HR3PdD/nAjt51nQpQ4DODETobpiPqwLU w7/LV4dgK3vKtkSnqzQHcN/nS7UxM6sSffa7gtLdok/M58BjWSxsogSiJLkOeOjtLKW0 u6q7mgHmbRFhiYWN6d+09JZ/3gULvCrxOf3fRt3upzxv4Ic6gjDiM+I61fjKeQ2uO1D3 pxx6mGy2g2o900oSTzmSvr63CHpR9UNWcyozvjXBD9D2LgXvj3e4P5UL72oJpe350q+0 dNAw==
MIME-Version: 1.0
X-Received: by 10.180.19.69 with SMTP id c5mr19980908wie.7.1398189849051; Tue, 22 Apr 2014 11:04:09 -0700 (PDT)
Received: by 10.216.10.6 with HTTP; Tue, 22 Apr 2014 11:04:08 -0700 (PDT)
In-Reply-To: <CF7BF13E.B1AE%repenno@cisco.com>
References: <5122C634.2020903@bbiw.net> <CF7BF13E.B1AE%repenno@cisco.com>
Date: Tue, 22 Apr 2014 13:04:08 -0500
Message-ID: <CAHBDyN6qWBuQAfJ6CjUh2sj7Cf49d1HZwiv42aKC4Nr8M3TB9g@mail.gmail.com>
Subject: Re: Proposal for Structuring New WGs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec53d5a8b4809a304f7a57105
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/hSvdxrspjwkFoyQnTdWkQnTJACk
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Apr 2014 18:04:20 -0000

--bcaec53d5a8b4809a304f7a57105
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 22, 2014 at 12:30 PM, Reinaldo Penno (repenno) <
repenno@cisco.com> wrote:

> Hi,
>
> I=C2=B9ve been thinking about how some Wgs get stuck and others loose ste=
am and
> would like to propose an optional way to structure new WGs.
>
> I think the delay or failure of many WGs can be attribute as the way we
> IETF structures WGs.
>
> When a WG is formed there is lots of energy, many drafts, people with
> running code (yes, these people still exist) and great participation. But
> then, the IETF step on the brakes by following a cookie cutter approach o=
f
> asking for a problem statement draft, some form of architecture draft and
> produces, most often than not, a set in stone charter.  This alone makes =
a
> boatload of people leave the WG effort. Some of these folks have even
> running code (I=C2=B9ve been there) or drafts that many folks are interes=
ted
> but can not be discussed until the current charter is done.
>
[MB] AFAIK there is no requirement to follow this cookie cutter approach.
It makes sense for some WGs and not for others. The STOX WG in RAI is a
good example where some more mature work (based on running code) was
brought in and then refined within the WG. [/MB]

>
> And the WG struggles on and on because of the very fact that some of the
> folks with energy that could drive the WG will not wait on the sidelines
> for 2 years until rechartering so that maybe, just maybe, their draft can
> get on the charter.
>
[MB] Yes, there is very frequently an energy issue. The problem I see is
that we don't do a very good job as chairs of recognizing when that has
occurred and managing it.  IMHO, it's up to the chairs to ensure there's a
plan to drive the work. This gets us back to the perennial topic of
deadlines - it's normal behavior for many of us to not get something done
until right before a deadline.  There's absolutely nothing that precludes
chairs from setting  earlier deadlines and intermediate deadlines between
f2f meetings. And, we have found weekly one hour calls to be very helpful
in the CLUE WG to resolve specific issues and focus on key drafts. If
people can't meet deadlines, then the chairs have option of recruiting new
document editors or worst case working with the ADs and shutting down WGs
We've done that in the RAI. So, in my opinion, we don't need a new WG
structure or process. We just need to be more diligent in managing WGs (and
perhaps doing a better job of choosing chairs that have the time to
dedicate to the work other than a few weeks before and after f2f meetings).
[/MB]

>
> My proposal is that certain WGs should be formed with some overall charte=
r
> and the definite charter should be written _after_ say, two official WG
> meetings, where lots of discussion on mailing list and presentations
> happen. Then the charter becomes the most important drafts people are
> interested. In this case for example, the problem statement becomes in
> fact those drafts.
>
[MB] Isn't the above the current model we already have with Bofs? [/MB]

>
> Maybe this is already allowed but it is not known or not encouraged. At
> least if possible it would be good to experiment with that approach in
> some of the popular or struggling WGs.
>
> Thanks,
>
> -Reinaldo
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Tue, Apr 22, 2014 at 12:30 P=
M, Reinaldo Penno (repenno) <span dir=3D"ltr">&lt;<a href=3D"mailto:repenno=
@cisco.com" target=3D"_blank">repenno@cisco.com</a>&gt;</span> wrote:<br><d=
iv class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<br>
I=C2=B9ve been thinking about how some Wgs get stuck and others loose steam=
 and<br>
would like to propose an optional way to structure new WGs.<br>
<br>
I think the delay or failure of many WGs can be attribute as the way we<br>
IETF structures WGs.<br>
<br>
When a WG is formed there is lots of energy, many drafts, people with<br>
running code (yes, these people still exist) and great participation. But<b=
r>
then, the IETF step on the brakes by following a cookie cutter approach of<=
br>
asking for a problem statement draft, some form of architecture draft and<b=
r>
produces, most often than not, a set in stone charter. =C2=A0This alone mak=
es a<br>
boatload of people leave the WG effort. Some of these folks have even<br>
running code (I=C2=B9ve been there) or drafts that many folks are intereste=
d<br>
but can not be discussed until the current charter is done.<br></blockquote=
><div>[MB] AFAIK there is no requirement to follow this cookie cutter appro=
ach. It makes sense for some WGs and not for others. The STOX WG in RAI is =
a good example where some more mature work (based on running code) was brou=
ght in and then refined within the WG. [/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
And the WG struggles on and on because of the very fact that some of the<br=
>
folks with energy that could drive the WG will not wait on the sidelines<br=
>
for 2 years until rechartering so that maybe, just maybe, their draft can<b=
r>
get on the charter.<br></blockquote><div>[MB] Yes, there is very frequently=
 an energy issue. The problem I see is that we don&#39;t do a very good job=
 as chairs of recognizing when that has occurred and managing it. =C2=A0IMH=
O, it&#39;s up to the chairs to ensure there&#39;s a plan to drive the work=
. This gets us back to the perennial topic of deadlines - it&#39;s normal b=
ehavior for many of us to not get something done until right before a deadl=
ine. =C2=A0There&#39;s absolutely nothing that precludes chairs from settin=
g =C2=A0earlier deadlines and intermediate deadlines between f2f meetings. =
And, we have found weekly one hour calls to be very helpful in the CLUE WG =
to resolve specific issues and focus on key drafts. If people can&#39;t mee=
t deadlines, then the chairs have option of recruiting new document editors=
 or worst case working with the ADs and shutting down WGs We&#39;ve done th=
at in the RAI. So, in my opinion, we don&#39;t need a new WG structure or p=
rocess. We just need to be more diligent in managing WGs (and perhaps doing=
 a better job of choosing chairs that have the time to dedicate to the work=
 other than a few weeks before and after f2f meetings). [/MB]=C2=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
My proposal is that certain WGs should be formed with some overall charter<=
br>
and the definite charter should be written _after_ say, two official WG<br>
meetings, where lots of discussion on mailing list and presentations<br>
happen. Then the charter becomes the most important drafts people are<br>
interested. In this case for example, the problem statement becomes in<br>
fact those drafts.<br></blockquote><div>[MB] Isn&#39;t the above the curren=
t model we already have with Bofs? [/MB]=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">

<br>
Maybe this is already allowed but it is not known or not encouraged. At<br>
least if possible it would be good to experiment with that approach in<br>
some of the popular or struggling WGs.<br>
<br>
Thanks,<br>
<br>
-Reinaldo<br>
<br></blockquote></div></div></div>

--bcaec53d5a8b4809a304f7a57105--


From nobody Tue Apr 22 11:08:10 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ED211A06C5 for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQS0moojgXqT for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:08:03 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 671F41A023A for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:08:03 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id pv20so4631503lab.37 for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:07:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mRQDagmZTwCRgA+gD7VCLz7ESVrl4B0ErP7vrbKjij4=; b=SdJNm2C8meT9dGZ+FQDgQanvlMio03cGa5e6WaKwi8STfn/d9gb5W9EtE85GZx9yAi +hCG7AZs1xcO8NOOj0Chk1nKa+IVhRHVsV+46UgvLQwGrz8HODPgORrNditGBooOASkM mr9qYc8tq8N8lBcYS6mqffhC9EwKmVf5eyS+AXshc+RWRYgPmdJROg8FGgF0Hyso5b+G xJapJk0Wj40BVC9BoZkB9Eq6vbFRSlymMgMQyPzNRogBxfgjC2Kg5h6UDdhAJoadVniL 4Uu50rB4gY850pJNUMqQD0HkbJL8Gw10Rf0AWGeTD2hjaX+FpYBcpSQQzSYJWRye4s1z QkNA==
MIME-Version: 1.0
X-Received: by 10.112.35.14 with SMTP id d14mr520478lbj.43.1398190077392; Tue, 22 Apr 2014 11:07:57 -0700 (PDT)
Received: by 10.114.70.165 with HTTP; Tue, 22 Apr 2014 11:07:57 -0700 (PDT)
In-Reply-To: <CF7BF13E.B1AE%repenno@cisco.com>
References: <5122C634.2020903@bbiw.net> <CF7BF13E.B1AE%repenno@cisco.com>
Date: Tue, 22 Apr 2014 13:07:57 -0500
Message-ID: <CAC8QAcese5FfcyWNd4ttCTTgVA1rvt=cLCrc2oCXHEesAzpkYw@mail.gmail.com>
Subject: Re: Proposal for Structuring New WGs
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
Content-Type: multipart/alternative; boundary=14dae93d8f52e4400704f7a57e6a
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/WA7M6LCneWZLkfnRdIa6La0kzCU
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.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: Tue, 22 Apr 2014 18:08:08 -0000

--14dae93d8f52e4400704f7a57e6a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Reinaldo,

In Multimob, we followed the approach of directly going into solutions as
you seem to advocate.

However later on we realized that some requirements work needed to judge on
the solution proposals because for almost all charter items we had more
than one solution proposals.

In the end we ended up not doing any requirement work but we still got
delayed due to the solution candidate selection process that took longer
than expected.

Regards,

Behcet


On Tue, Apr 22, 2014 at 12:30 PM, Reinaldo Penno (repenno) <
repenno@cisco.com> wrote:

> Hi,
>
> I=C2=B9ve been thinking about how some Wgs get stuck and others loose ste=
am and
> would like to propose an optional way to structure new WGs.
>
> I think the delay or failure of many WGs can be attribute as the way we
> IETF structures WGs.
>
> When a WG is formed there is lots of energy, many drafts, people with
> running code (yes, these people still exist) and great participation. But
> then, the IETF step on the brakes by following a cookie cutter approach o=
f
> asking for a problem statement draft, some form of architecture draft and
> produces, most often than not, a set in stone charter.  This alone makes =
a
> boatload of people leave the WG effort. Some of these folks have even
> running code (I=C2=B9ve been there) or drafts that many folks are interes=
ted
> but can not be discussed until the current charter is done.
>
> And the WG struggles on and on because of the very fact that some of the
> folks with energy that could drive the WG will not wait on the sidelines
> for 2 years until rechartering so that maybe, just maybe, their draft can
> get on the charter.
>
> My proposal is that certain WGs should be formed with some overall charte=
r
> and the definite charter should be written _after_ say, two official WG
> meetings, where lots of discussion on mailing list and presentations
> happen. Then the charter becomes the most important drafts people are
> interested. In this case for example, the problem statement becomes in
> fact those drafts.
>
> Maybe this is already allowed but it is not known or not encouraged. At
> least if possible it would be good to experiment with that approach in
> some of the popular or struggling WGs.
>
> Thanks,
>
> -Reinaldo
>
>
>

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

<div dir=3D"ltr"><div><div><div><div><div>Hi Reinaldo,<br><br></div>In Mult=
imob, we followed the approach of directly going into solutions as you seem=
 to advocate.<br><br></div>However later on we realized that some requireme=
nts work needed to judge on the solution proposals because for almost all c=
harter items we had more than one solution proposals.<br>
<br></div>In the end we ended up not doing any requirement work but we stil=
l got delayed due to the solution candidate selection process that took lon=
ger than expected.<br><br></div>Regards,<br><br></div>Behcet<br></div><div =
class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Tue, Apr 22, 2014 at 12:30 PM, Reinal=
do Penno (repenno) <span dir=3D"ltr">&lt;<a href=3D"mailto:repenno@cisco.co=
m" target=3D"_blank">repenno@cisco.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
Hi,<br>
<br>
I=C2=B9ve been thinking about how some Wgs get stuck and others loose steam=
 and<br>
would like to propose an optional way to structure new WGs.<br>
<br>
I think the delay or failure of many WGs can be attribute as the way we<br>
IETF structures WGs.<br>
<br>
When a WG is formed there is lots of energy, many drafts, people with<br>
running code (yes, these people still exist) and great participation. But<b=
r>
then, the IETF step on the brakes by following a cookie cutter approach of<=
br>
asking for a problem statement draft, some form of architecture draft and<b=
r>
produces, most often than not, a set in stone charter. =C2=A0This alone mak=
es a<br>
boatload of people leave the WG effort. Some of these folks have even<br>
running code (I=C2=B9ve been there) or drafts that many folks are intereste=
d<br>
but can not be discussed until the current charter is done.<br>
<br>
And the WG struggles on and on because of the very fact that some of the<br=
>
folks with energy that could drive the WG will not wait on the sidelines<br=
>
for 2 years until rechartering so that maybe, just maybe, their draft can<b=
r>
get on the charter.<br>
<br>
My proposal is that certain WGs should be formed with some overall charter<=
br>
and the definite charter should be written _after_ say, two official WG<br>
meetings, where lots of discussion on mailing list and presentations<br>
happen. Then the charter becomes the most important drafts people are<br>
interested. In this case for example, the problem statement becomes in<br>
fact those drafts.<br>
<br>
Maybe this is already allowed but it is not known or not encouraged. At<br>
least if possible it would be good to experiment with that approach in<br>
some of the popular or struggling WGs.<br>
<br>
Thanks,<br>
<br>
-Reinaldo<br>
<br>
<br>
</blockquote></div><br></div>

--14dae93d8f52e4400704f7a57e6a--


From nobody Tue Apr 22 11:21:16 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3321A06AA for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.772
X-Spam-Level: 
X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boFRyklIxHzg for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:21:05 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id EDD651A024D for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4179; q=dns/txt; s=iport; t=1398190859; x=1399400459; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=gKCOYtX5/WjXVb0x0nulfmJYI00bmVtUSiV9WulFMhk=; b=LdfISjC9VbJGhqtDVs/oQEdbHwonngIabbVxrgvkBqtsIIu+WCoZtK4h VLAg1lF7aEKvRCzqtNEBeuEQ3XJ+XXxzrN9epQIhHq1S0QfMwBcBMoE5y DVjCwwTdIRzAyZUl59XgKEeeLXfZKRGbx/cn+OiWZmtdBH0rvmL8Kn8h9 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAPCxVlOtJV2a/2dsb2JhbABZgkJEgSbEHoEWFnSCJQECBG4LEgEIBA0DAQIoKBEUCQgCBA4FiC0DEcYvDYVqF4w+ggcRB4Q4BJcCgW6NAIVSgzGCKw
X-IronPort-AV: E=Sophos; i="4.97,905,1389744000"; d="scan'208,217"; a="37812883"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-6.cisco.com with ESMTP; 22 Apr 2014 18:20:59 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3MIKxos018024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Apr 2014 18:20:59 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Tue, 22 Apr 2014 13:20:58 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpseQbMA//+PWoA=
Date: Tue, 22 Apr 2014 18:20:57 +0000
Message-ID: <CF7BFED1.B1FC%repenno@cisco.com>
In-Reply-To: <CAHBDyN6qWBuQAfJ6CjUh2sj7Cf49d1HZwiv42aKC4Nr8M3TB9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.21.145.177]
Content-Type: multipart/alternative; boundary="_000_CF7BFED1B1FCrepennociscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/xltjdUJUkHnzQjlNSZEF-Hz2qis
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Apr 2014 18:21:11 -0000

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

I think this is a bit different. IMO during BOF people are really trying to=
 sell the idea but people really converge after the WG is officially formed=
 and go-ahead is given.

From: Mary Barnes <mary.ietf.barnes@gmail.com<mailto:mary.ietf.barnes@gmail=
.com>>
Date: Tuesday, April 22, 2014 at 11:04 AM
To: Cisco Employee <repenno@cisco.com<mailto:repenno@cisco.com>>
Cc: WG Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
Subject: Re: Proposal for Structuring New WGs

My proposal is that certain WGs should be formed with some overall charter
and the definite charter should be written _after_ say, two official WG
meetings, where lots of discussion on mailing list and presentations
happen. Then the charter becomes the most important drafts people are
interested. In this case for example, the problem statement becomes in
fact those drafts.
[MB] Isn't the above the current model we already have with Bofs? [/MB]

--_000_CF7BFED1B1FCrepennociscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <D555D16B1C7E7649AE730E59FCB5D3D5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>I think this is a bit different. IMO during BOF people are really tryi=
ng to sell the idea but people really converge after the WG is officially f=
ormed and go-ahead is given.</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Mary Barnes &lt;<a href=3D"ma=
ilto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, April 22, 2014 at 11=
:04 AM<br>
<span style=3D"font-weight:bold">To: </span>Cisco Employee &lt;<a href=3D"m=
ailto:repenno@cisco.com">repenno@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>WG Chairs &lt;<a href=3D"mailto=
:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Proposal for Structuri=
ng New WGs<br>
</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri; font-size: medium; font-style: normal; font-variant: normal; fon=
t-weight: normal; letter-spacing: normal; line-height: normal; orphans: aut=
o; text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; ma=
rgin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204=
, 204, 204); border-left-style: solid; padding-left: 1ex;">
My proposal is that certain WGs should be formed with some overall charter<=
br>
and the definite charter should be written _after_ say, two official WG<br>
meetings, where lots of discussion on mailing list and presentations<br>
happen. Then the charter becomes the most important drafts people are<br>
interested. In this case for example, the problem statement becomes in<br>
fact those drafts.<br>
</blockquote>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;=
 font-style: normal; font-variant: normal; font-weight: normal; letter-spac=
ing: normal; line-height: normal; orphans: auto; text-align: start; text-in=
dent: 0px; text-transform: none; white-space: normal; widows: auto; word-sp=
acing: 0px; -webkit-text-stroke-width: 0px;">
[MB] Isn't the above the current model we already have with Bofs? [/MB]&nbs=
p;</div>
</span>
</body>
</html>

--_000_CF7BFED1B1FCrepennociscocom_--


From nobody Tue Apr 22 11:41:26 2014
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B14101A022B for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:41:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.572
X-Spam-Level: 
X-Spam-Status: No, score=-4.572 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vgfsDBvIOePY for <wgchairs@ietfa.amsl.com>; Tue, 22 Apr 2014 11:41:21 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2B21A0226 for <wgchairs@ietf.org>; Tue, 22 Apr 2014 11:41:21 -0700 (PDT)
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3MIfESc018249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Apr 2014 14:41:14 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3MIfESc018249
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398192074; bh=tD0t1YOBvchq4d+Aw/d1UYWbtI0=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=LAMJXJO344jYRUe95x1qq1a24HIwKJpxtcwdTIQSWE/b/9/cxlVJWrFn3La5H8K9p aYCufST8aTeCi3huv5/YlNFp05i2WbvtvlWu200GvlyYG/X/LExSH4cRBx7zIhW7xY bB9U7c+dktvI1iyUfbXwrAEVfOIx8zbB/c7vWSE8=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3MIfESc018249
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd56.lss.emc.com (RSA Interceptor); Tue, 22 Apr 2014 14:40:59 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3MIexdO016174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Apr 2014 14:40:59 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Tue, 22 Apr 2014 14:40:59 -0400
From: "Black, David" <david.black@emc.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
Date: Tue, 22 Apr 2014 14:40:58 -0400
Subject: RE: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpseQbMA//+PWoCAACQ4sA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC893@MX15A.corp.emc.com>
References: <CAHBDyN6qWBuQAfJ6CjUh2sj7Cf49d1HZwiv42aKC4Nr8M3TB9g@mail.gmail.com> <CF7BFED1.B1FC%repenno@cisco.com>
In-Reply-To: <CF7BFED1.B1FC%repenno@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_8D3D17ACE214DC429325B2B98F3AE712076C2EC893MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/uEDT8PRIGjYvMBZYg7xtSARsuqI
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Apr 2014 18:41:25 -0000

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

That depends on whether a BoF is intended to be WG-forming.  A WG-forming B=
oF is supposed to come up with a charter.  There could be some preceding ex=
ploratory non-WG-forming BoFs, although with some care, as it's a short dis=
tance from there to a world in which an effort can take more than 2 BoFs to=
 come up with the charter (e.g., experiences in the recent past with "bar B=
oFs" having quite a bit of formality and organization).

I've definitely seen the scenario that Reinaldo describes - a WG formed w/a=
 head of steam to go do "something" in an area, but it's not exactly clear =
what that "something" should be ... so a lot of time and effort are expende=
d on things like a problem statement, framework, architecture, etc. towards=
 figuring out what that "something" ought to be ... and a lot of people los=
e interest along the way :-(.

Thanks,
--David

From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Reinaldo Pen=
no (repenno)
Sent: Tuesday, April 22, 2014 2:21 PM
To: Mary Barnes
Cc: WG Chairs
Subject: Re: Proposal for Structuring New WGs

I think this is a bit different. IMO during BOF people are really trying to=
 sell the idea but people really converge after the WG is officially formed=
 and go-ahead is given.

From: Mary Barnes <mary.ietf.barnes@gmail.com<mailto:mary.ietf.barnes@gmail=
.com>>
Date: Tuesday, April 22, 2014 at 11:04 AM
To: Cisco Employee <repenno@cisco.com<mailto:repenno@cisco.com>>
Cc: WG Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
Subject: Re: Proposal for Structuring New WGs

My proposal is that certain WGs should be formed with some overall charter
and the definite charter should be written _after_ say, two official WG
meetings, where lots of discussion on mailing list and presentations
happen. Then the charter becomes the most important drafts people are
interested. In this case for example, the problem statement becomes in
fact those drafts.
[MB] Isn't the above the current model we already have with Bofs? [/MB]

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>That depends on whet=
her a BoF is intended to be WG-forming.&nbsp; A WG-forming BoF is supposed =
to come up with a charter.&nbsp; There could be some preceding exploratory =
non-WG-forming BoFs, although with some care, as it&#8217;s a short distanc=
e from there to a world in which an effort can take more than 2 BoFs to com=
e up with the charter (e.g., experiences in the recent past with &#8220;bar=
 BoFs&#8221; having quite a bit of formality and organization).<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>I&#=
8217;ve definitely seen the scenario that Reinaldo describes - a WG formed =
w/a head of steam to go do &#8220;something&#8221; in an area, but it&#8217=
;s not exactly clear what that &#8220;something&#8221; should be ... so a l=
ot of time and effort are expended on things like a problem statement, fram=
ework, architecture, etc. towards figuring out what that &#8220;something&#=
8221; ought to be ... and a lot of people lose interest along the way :-(.<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><div><div=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>Thanks,<br>--David</span><span style=3D'font-size:11.0pt;=
font-family:"Courier New";color:black'><o:p></o:p></span></p></div></div><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:black'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border=
-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border=
:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3D=
MsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-ser=
if"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'> WGChairs [mailto:wgchairs-bounces@ietf.org] <b>On Behalf Of <=
/b>Reinaldo Penno (repenno)<br><b>Sent:</b> Tuesday, April 22, 2014 2:21 PM=
<br><b>To:</b> Mary Barnes<br><b>Cc:</b> WG Chairs<br><b>Subject:</b> Re: P=
roposal for Structuring New WGs<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span style=3D'=
font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>I think th=
is is a bit different. IMO during BOF people are really trying to sell the =
idea but people really converge after the WG is officially formed and go-ah=
ead is given.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span st=
yle=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:=
p>&nbsp;</o:p></span></p></div><div style=3D'border:none;border-top:solid #=
B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>From: =
</span></b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f";color:black'>Mary Barnes &lt;<a href=3D"mailto:mary.ietf.barnes@gmail.co=
m">mary.ietf.barnes@gmail.com</a>&gt;<br><b>Date: </b>Tuesday, April 22, 20=
14 at 11:04 AM<br><b>To: </b>Cisco Employee &lt;<a href=3D"mailto:repenno@c=
isco.com">repenno@cisco.com</a>&gt;<br><b>Cc: </b>WG Chairs &lt;<a href=3D"=
mailto:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br><b>Subject: </b>Re: =
Proposal for Structuring New WGs<o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-se=
rif";color:black'><o:p>&nbsp;</o:p></span></p></div><blockquote style=3D'bo=
rder:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-=
left:4.8pt;margin-right:0in;orphans: auto;text-align:start;widows: auto;-we=
bkit-text-stroke-width: 0px;word-spacing:0px'><p class=3DMsoNormal><span st=
yle=3D'font-size:13.5pt;font-family:"Calibri","sans-serif";color:black'>My =
proposal is that certain WGs should be formed with some overall charter<br>=
and the definite charter should be written _after_ say, two official WG<br>=
meetings, where lots of discussion on mailing list and presentations<br>hap=
pen. Then the charter becomes the most important drafts people are<br>inter=
ested. In this case for example, the problem statement becomes in<br>fact t=
hose drafts.<o:p></o:p></span></p></blockquote><div><p class=3DMsoNormal><s=
pan style=3D'font-size:13.5pt;font-family:"Calibri","sans-serif";color:blac=
k'>[MB] Isn't the above the current model we already have with Bofs? [/MB]&=
nbsp;<o:p></o:p></span></p></div></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712076C2EC893MX15Acorpemcc_--


From nobody Wed Apr 23 07:52:24 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E8931A03C7; Wed, 23 Apr 2014 07:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.773
X-Spam-Level: 
X-Spam-Status: No, score=-0.773 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w3tFBQoor6jI; Wed, 23 Apr 2014 07:52:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 428971A02A7; Wed, 23 Apr 2014 07:52:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED14820029; Wed, 23 Apr 2014 10:52:58 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B50E263ABD; Wed, 23 Apr 2014 10:52:12 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A370D63AB2; Wed, 23 Apr 2014 10:52:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "'WG Chairs'" <wgchairs@ietf.org>, iab@ietf.org
Subject: Re: Proposal for Structuring New WGs
In-Reply-To: <CF7BF13E.B1AE%repenno@cisco.com>
References: <CF7BF13E.B1AE%repenno@cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 23 Apr 2014 10:52:12 -0400
Message-ID: <17962.1398264732@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/q4VlRzskzVd7BHZa0mB_ECJ8b-8
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 14:52:23 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Reinaldo Penno (repenno) <repenno@cisco.com> wrote:
    > I=C2=B9ve been thinking about how some Wgs get stuck and others loose=
 steam and
    > would like to propose an optional way to structure new WGs.

    > I think the delay or failure of many WGs can be attribute as the way =
we
    > IETF structures WGs.

    > When a WG is formed there is lots of energy, many drafts, people with
    > running code (yes, these people still exist) and great participation.=
 But
    > then, the IETF step on the brakes by following a cookie cutter approa=
ch of
    > asking for a problem statement draft, some form of architecture draft=
 and
    > produces, most often than not, a set in stone charter.  This alone ma=
kes a
    > boatload of people leave the WG effort. Some of these folks have even
    > running code (I=C2=B9ve been there) or drafts that many folks are int=
erested
    > but can not be discussed until the current charter is done.

I don't think that the IETF forces this in a structural way.

I think that this occurs as an import from other SDOs, from the discredited
software 'waterfall' method, etc.

I think that people are naturally much more agile when left to run on their
enthusiasm, and I think that our mantra of running code and rough consensus
was attempting to channel that.  However, we do want to have some milestones
that make sense, and perhaps the right thing here would be to come up with
a newer, more agile, template charter/milestones that captures the desired
iterative nature that we really want.
(HEY, IAB people, I mean, *YOU*... you guys got a retreat about to happen?)


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


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

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

iQCVAwUBU1fTnIqHRg3pndX9AQIfJAP9Gfe+/9sBOIwL7YdbLPqOoxcXu+CixUrX
3FXkYMXDB2aeVokFmyU1qqAxmfhhaflQUpbPBGUEZZ7nEHPPaljlhlgRDB0VWjLr
CQr3ZeoREalHq0nPpBejrwSbXu/1/UFdQdDPtylIZ2RHJFpbdiBc5dPdhnH2pcrG
cIY2PeA0rNo=
=2jij
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 23 08:07:02 2014
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E4B1A03CB; Wed, 23 Apr 2014 08:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsj7OD0dtdTQ; Wed, 23 Apr 2014 08:06:57 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C8E8D1A0104; Wed, 23 Apr 2014 08:06:56 -0700 (PDT)
Received: from [IPv6:2620:0:230:2002::1000] (unknown [IPv6:2620:0:230:2002::1000]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A88F5403CA; Wed, 23 Apr 2014 11:06:49 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: [IAB] Proposal for Structuring New WGs
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <17962.1398264732@sandelman.ca>
Date: Wed, 23 Apr 2014 11:06:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2706C4BF-2E4C-49D9-88A9-11665D475279@viagenie.ca>
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/8gYCEoz8A5aXB5djFlQai49LNNg
Cc: WG Chairs <wgchairs@ietf.org>, iab@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 15:07:00 -0000

Le 2014-04-23 =E0 10:52, Michael Richardson <mcr+ietf@sandelman.ca> a =
=E9crit :

>=20
> Reinaldo Penno (repenno) <repenno@cisco.com> wrote:
>> I=B9ve been thinking about how some Wgs get stuck and others loose =
steam and
>> would like to propose an optional way to structure new WGs.
>=20
>> I think the delay or failure of many WGs can be attribute as the way =
we
>> IETF structures WGs.
>=20
>> When a WG is formed there is lots of energy, many drafts, people with
>> running code (yes, these people still exist) and great participation. =
But
>> then, the IETF step on the brakes by following a cookie cutter =
approach of
>> asking for a problem statement draft, some form of architecture draft =
and
>> produces, most often than not, a set in stone charter.  This alone =
makes a
>> boatload of people leave the WG effort. Some of these folks have even
>> running code (I=B9ve been there) or drafts that many folks are =
interested
>> but can not be discussed until the current charter is done.
>=20
> I don't think that the IETF forces this in a structural way.
>=20
> I think that this occurs as an import from other SDOs, from the =
discredited
> software 'waterfall' method, etc.
>=20
> I think that people are naturally much more agile when left to run on =
their
> enthusiasm, and I think that our mantra of running code and rough =
consensus
> was attempting to channel that.  However, we do want to have some =
milestones
> that make sense, and perhaps the right thing here would be to come up =
with
> a newer, more agile, template charter/milestones that captures the =
desired
> iterative nature that we really want.

agree on the agility/iterative idea. but it is a fine balance between =
too structured and not enough structured...

Marc.

> (HEY, IAB people, I mean, *YOU*... you guys got a retreat about to =
happen?)
>=20
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>=20


From nobody Wed Apr 23 08:07:13 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 939391A03EB; Wed, 23 Apr 2014 08:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_bzXj-uI50C; Wed, 23 Apr 2014 08:07:00 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 45AF61A0104; Wed, 23 Apr 2014 08:07:00 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id x13so977259wgg.2 for <multiple recipients>; Wed, 23 Apr 2014 08:06:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3MiHkmefSj8MhWMhsWZUJ3PLarIFn24pK5hEWQ8Ve3I=; b=y7wsoPTBsvRhufzNu3Wn+vs6ch1mt9tbpP26thw7+wYKltsOG6nOyzweY+CIP4/aL9 XsyNZDdXDweUXDo10fAWKXUGDZy0vtnd21B5nRWqWM/5RQEXhdhTUubpRq8n0nJ3qmGR l99u79IIMTv/aEOPqLpK8FBZyeEveZ6xy5ErG4uOlrGy8uBge7qnt3PqrQYfMU+Qv7nG JdaOUUEAMN9FNgbRLLO1mLiEPJvwxA3z49ceD2M2nCj2537wZ+3AiMM8SOBkitcU/mAm pml6X9c1kI9pVrVzxfzN46KLEqM2J0p3wjr6KOztms4qrvNw5fD0n2bb9m13W2DfWQpV lOMg==
MIME-Version: 1.0
X-Received: by 10.194.57.77 with SMTP id g13mr13287025wjq.42.1398265614108; Wed, 23 Apr 2014 08:06:54 -0700 (PDT)
Received: by 10.216.10.6 with HTTP; Wed, 23 Apr 2014 08:06:54 -0700 (PDT)
In-Reply-To: <17962.1398264732@sandelman.ca>
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca>
Date: Wed, 23 Apr 2014 10:06:54 -0500
Message-ID: <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com>
Subject: Re: Proposal for Structuring New WGs
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=047d7bacc0fa3b113d04f7b71565
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/fcRjBO8dZZFYfNIpYvOh-fbcwWk
Cc: WG Chairs <wgchairs@ietf.org>, "iab@ietf.org" <iab@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 15:07:05 -0000

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

On Wed, Apr 23, 2014 at 9:52 AM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> Reinaldo Penno (repenno) <repenno@cisco.com> wrote:
>     > I=C2=B9ve been thinking about how some Wgs get stuck and others loo=
se
> steam and
>     > would like to propose an optional way to structure new WGs.
>
>     > I think the delay or failure of many WGs can be attribute as the wa=
y
> we
>     > IETF structures WGs.
>
>     > When a WG is formed there is lots of energy, many drafts, people wi=
th
>     > running code (yes, these people still exist) and great
> participation. But
>     > then, the IETF step on the brakes by following a cookie cutter
> approach of
>     > asking for a problem statement draft, some form of architecture
> draft and
>     > produces, most often than not, a set in stone charter.  This alone
> makes a
>     > boatload of people leave the WG effort. Some of these folks have ev=
en
>     > running code (I=C2=B9ve been there) or drafts that many folks are
> interested
>     > but can not be discussed until the current charter is done.
>
> I don't think that the IETF forces this in a structural way.
>
> I think that this occurs as an import from other SDOs, from the discredit=
ed
> software 'waterfall' method, etc.
>
> I think that people are naturally much more agile when left to run on the=
ir
> enthusiasm, and I think that our mantra of running code and rough consens=
us
> was attempting to channel that.  However, we do want to have some
> milestones
> that make sense, and perhaps the right thing here would be to come up wit=
h
> a newer, more agile, template charter/milestones that captures the desire=
d
> iterative nature that we really want.
> (HEY, IAB people, I mean, *YOU*... you guys got a retreat about to happen=
?)
>
[MB] There's absolutely nothing in the current model to prevent WG chairs
from doing more detailed project planning.  I don't think we need a process
in place as the task can be straightforward for some WGs. And, chairs are
totally free to implement a process that they feel does the job.  I
maintain a spreadsheet for my WGs that includes intermediate milestones,
since we almost always iterate documents through the WG milestones - i.e.,
multiple WG last calls including what I call a pre-WGLC=10.  This isn't a
tool or process problem, this is an issue with WG chairs not managing the
process we have. [/MB]

>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Apr 23, 2014 at 9:52 AM, Michael Richardson <span dir=3D"lt=
r">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@=
sandelman.ca</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br>
Reinaldo Penno (repenno) &lt;<a href=3D"mailto:repenno@cisco.com">repenno@c=
isco.com</a>&gt; wrote:<br>
</div><div class=3D"">=C2=A0 =C2=A0 &gt; I=C2=B9ve been thinking about how =
some Wgs get stuck and others loose steam and<br>
=C2=A0 =C2=A0 &gt; would like to propose an optional way to structure new W=
Gs.<br>
<br>
=C2=A0 =C2=A0 &gt; I think the delay or failure of many WGs can be attribut=
e as the way we<br>
=C2=A0 =C2=A0 &gt; IETF structures WGs.<br>
<br>
=C2=A0 =C2=A0 &gt; When a WG is formed there is lots of energy, many drafts=
, people with<br>
=C2=A0 =C2=A0 &gt; running code (yes, these people still exist) and great p=
articipation. But<br>
=C2=A0 =C2=A0 &gt; then, the IETF step on the brakes by following a cookie =
cutter approach of<br>
=C2=A0 =C2=A0 &gt; asking for a problem statement draft, some form of archi=
tecture draft and<br>
=C2=A0 =C2=A0 &gt; produces, most often than not, a set in stone charter. =
=C2=A0This alone makes a<br>
=C2=A0 =C2=A0 &gt; boatload of people leave the WG effort. Some of these fo=
lks have even<br>
=C2=A0 =C2=A0 &gt; running code (I=C2=B9ve been there) or drafts that many =
folks are interested<br>
=C2=A0 =C2=A0 &gt; but can not be discussed until the current charter is do=
ne.<br>
<br>
</div>I don&#39;t think that the IETF forces this in a structural way.<br>
<br>
I think that this occurs as an import from other SDOs, from the discredited=
<br>
software &#39;waterfall&#39; method, etc.<br>
<br>
I think that people are naturally much more agile when left to run on their=
<br>
enthusiasm, and I think that our mantra of running code and rough consensus=
<br>
was attempting to channel that. =C2=A0However, we do want to have some mile=
stones<br>
that make sense, and perhaps the right thing here would be to come up with<=
br>
a newer, more agile, template charter/milestones that captures the desired<=
br>
iterative nature that we really want.<br>
(HEY, IAB people, I mean, *YOU*... you guys got a retreat about to happen?)=
<br></blockquote><div>[MB] There&#39;s absolutely nothing in the current mo=
del to prevent WG chairs from doing more detailed project planning. =C2=A0I=
 don&#39;t think we need a process in place as the task can be straightforw=
ard for some WGs. And, chairs are totally free to implement a process that =
they feel does the job. =C2=A0I maintain a spreadsheet for my WGs that incl=
udes intermediate milestones, since we almost always iterate documents thro=
ugh the WG milestones - i.e., multiple WG last calls including what I call =
a pre-WGLC=10. =C2=A0This isn&#39;t a tool or process problem, this is an i=
ssue with WG chairs not managing the process we have. [/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
IETF ROLL WG co-chair. =C2=A0 =C2=A0<a href=3D"http://datatracker.ietf.org/=
wg/roll/charter/" target=3D"_blank">http://datatracker.ietf.org/wg/roll/cha=
rter/</a><br>
<br>
</blockquote></div><br></div></div>

--047d7bacc0fa3b113d04f7b71565--


From nobody Wed Apr 23 13:54:24 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9381A064D; Wed, 23 Apr 2014 13:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPYgCklttdSU; Wed, 23 Apr 2014 13:54:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9171A019F; Wed, 23 Apr 2014 13:54:21 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 977DB20029; Wed, 23 Apr 2014 16:54:58 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 504C263ABD; Wed, 23 Apr 2014 16:54:12 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3EEED63AA2; Wed, 23 Apr 2014 16:54:12 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Proposal for Structuring New WGs
In-Reply-To: <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com>
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca> <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 23 Apr 2014 16:54:12 -0400
Message-ID: <29478.1398286452@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/kfD56kV-rO23olhIt9Y8sdaXeD8
Cc: WG Chairs <wgchairs@ietf.org>, "iab@ietf.org" <iab@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 20:54:22 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
    > [MB] There's absolutely nothing in the current model to prevent WG ch=
airs from
    > doing more detailed project planning. =C2=A0I don't think we need a p=
rocess in place
    > as the task can be straightforward for some WGs. And, chairs are
    > totally free

I'm not suggesting any process changes, but rather a reference
design/template/running code of a more agile/iterative charter + milestones.
Something that has been pre-reviewed by I* types.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




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

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

iQCVAwUBU1godIqHRg3pndX9AQKMNQQAn5PRZ5GwX1X8+MyZFtma+wsUIhQov7dM
JaPnjarVDHPhMyj/2hksgDxWKYaezqD85FlwunHGzqr5X9D2QNpaOkj7KIO3QQth
dEpnwwcYY/SqRY1aAt5LZS6cK75LNvVLVdLEYZ/HJEJEul5Guc3pk1NKRaSslreO
OAXjRARYExU=
=/Igp
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 23 15:07:35 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D00841A06DC; Wed, 23 Apr 2014 15:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dff8O0kfsIw2; Wed, 23 Apr 2014 15:07:31 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 12F791A06DB; Wed, 23 Apr 2014 15:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=923; q=dns/txt; s=iport; t=1398290845; x=1399500445; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=uc0Me80Qo632KE2C2SCrwf8SozNiA8o2zRnumXFe8j4=; b=J9myi7lUxQ3q8pNBzo0XvQeZqKG0rsGCLb8QxcjjEVHxcSlmid22zmTO /o9e87oGJBkbM1eoPcMByudhhv5HfcJ4oeMF2ME9HWHPYaAbkVn+DJ/hF rMpv33JN6U+VmgRRHr0sbi3W0/YwdhJpRs0LKh2eE3ukTp8/jK86/crOJ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFACY4WFOtJA2F/2dsb2JhbABagwaBJsQ4gRwWdIIlAQEBBDo/EgEIGB4xESUCBAENBYgtAxHHAw2GVBeMQIIYB4Q5AQOXBYFwjQKFU4Mxgis
X-IronPort-AV: E=Sophos;i="4.97,914,1389744000"; d="scan'208";a="38200499"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-5.cisco.com with ESMTP; 23 Apr 2014 22:07:25 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id s3NM7P62022370 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Apr 2014 22:07:25 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Wed, 23 Apr 2014 17:07:24 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpsfnmgAgAAEGwCAAGEJAP//nxQA
Date: Wed, 23 Apr 2014 22:07:23 +0000
Message-ID: <CF7D8733.B2C7%repenno@cisco.com>
In-Reply-To: <29478.1398286452@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.155.65.252]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <739D215B39F9754891AA9C4B8EFEC5A8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/ew0XqIBaQ97Q09CngVN6X1L1z7Y
Cc: WG Chairs <wgchairs@ietf.org>, "iab@ietf.org" <iab@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 22:07:33 -0000

Thanks Michael for the good summary, I fully agree. As I mention the
process today might allow these agile WGs, but we need the backing, tools
and encouragement to actually make this a reality.

On 4/23/14, 1:54 PM, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:

>
>Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>    > [MB] There's absolutely nothing in the current model to prevent WG
>chairs from
>    > doing more detailed project planning.  I don't think we need a
>process in place
>    > as the task can be straightforward for some WGs. And, chairs are
>    > totally free
>
>I'm not suggesting any process changes, but rather a reference
>design/template/running code of a more agile/iterative charter +
>milestones.
>Something that has been pre-reviewed by I* types.
>
>--
>Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>
>
>


From nobody Wed Apr 23 15:17:02 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FD91A06E4 for <wgchairs@ietfa.amsl.com>; Wed, 23 Apr 2014 15:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.772
X-Spam-Level: 
X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eR4-mNOoUJ89 for <wgchairs@ietfa.amsl.com>; Wed, 23 Apr 2014 15:16:58 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id AA7EA1A06DE for <wgchairs@ietf.org>; Wed, 23 Apr 2014 15:16:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5069; q=dns/txt; s=iport; t=1398291413; x=1399501013; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=avCiTjL8aRP3xbqskWoQV5Oho57Gbl5aHegIJs3erlk=; b=RWzR3SkcKWrX2Ub6QMgN+BPInYoYM+28Dk2tNl6KAiiI4yyO1pE8D/3t 311CS4wm0VM8NWCAwu7IfCU3/FFXFYiRlBbNYqOmFqhqfp4A1gXsWlrjD NOA4Zwk/StIuawpcsWLCZVQlU/yboe/AGmalR9J9jEttI5YkB0mY81A1G 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AicFAPI6WFOtJV2c/2dsb2JhbABagkJEgSbEOIEcFnSCJQECBHkSAQgRAQIBAig5FAMGCAIEDgWIQc1oF45HEQeEOQSYdZJVgzGCKw
X-IronPort-AV: E=Sophos; i="4.97,914,1389744000"; d="scan'208,217"; a="38194889"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-6.cisco.com with ESMTP; 23 Apr 2014 22:16:52 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3NMGqQd014858 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Apr 2014 22:16:52 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Wed, 23 Apr 2014 17:16:52 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpseQbMA//+PWoCAACQ4sIABsAAA
Date: Wed, 23 Apr 2014 22:16:51 +0000
Message-ID: <CF7D8923.B2DA%repenno@cisco.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C2EC893@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.155.65.252]
Content-Type: multipart/alternative; boundary="_000_CF7D8923B2DArepennociscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/r_caqSjwYjgbcfaaWStVwhINDhQ
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Apr 2014 22:17:00 -0000

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

if you ask some developers to reach an agreement on the definition of Firew=
all, it will never happen. But if you ask them to code a firewall product, =
they can deliver one to you in no time. And there, IMHO,  is the main probl=
em of the way most WGs are structured.

From: <Black>, David <david.black@emc.com<mailto:david.black@emc.com>>
Date: Tuesday, April 22, 2014 at 11:40 AM
To: Cisco Employee <repenno@cisco.com<mailto:repenno@cisco.com>>
Cc: WG Chairs <wgchairs@ietf.org<mailto:wgchairs@ietf.org>>
Subject: RE: Proposal for Structuring New WGs

I=92ve definitely seen the scenario that Reinaldo describes - a WG formed w=
/a head of steam to go do =93something=94 in an area, but it=92s not exactl=
y clear what that =93something=94 should be ... so a lot of time and effort=
 are expended on things like a problem statement, framework, architecture, =
etc. towards figuring out what that =93something=94 ought to be ... and a l=
ot of people lose interest along the way :-(.

Thanks,
--David

--_000_CF7D8923B2DArepennociscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <3664CD5CAA3CD34E99DA63E9DFA23F68@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>if you ask some developers to reach an agreement on the definition of =
Firewall, it will never happen. But if you ask them to code a firewall prod=
uct, they can deliver one to you in no time. And there, IMHO, &nbsp;is the =
main problem of the way most WGs are
 structured.</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&lt;Black&gt;, David &lt;<a h=
ref=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, April 22, 2014 at 11=
:40 AM<br>
<span style=3D"font-weight:bold">To: </span>Cisco Employee &lt;<a href=3D"m=
ailto:repenno@cisco.com">repenno@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>WG Chairs &lt;<a href=3D"mailto=
:wgchairs@ietf.org">wgchairs@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>RE: Proposal for Structuri=
ng New WGs<br>
</div>
<div><br>
</div>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; color: rgb(0, 0, 0); font-style: nor=
mal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-=
transform: none; white-space: normal; widows: auto; word-spacing: 0px; -web=
kit-text-stroke-width: 0px;">
<span style=3D"font-size: 10pt; font-family: 'Courier New'; color: black;">=
I=92ve definitely seen the scenario that Reinaldo describes - a WG formed w=
/a head of steam to go do =93something=94 in an area, but it=92s not exactl=
y clear what that =93something=94 should be ...
 so a lot of time and effort are expended on things like a problem statemen=
t, framework, architecture, etc. towards figuring out what that =93somethin=
g=94 ought to be ... and a lot of people lose interest along the way :-(.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; color: rgb(0, 0, 0); font-style: nor=
mal; font-variant: normal; font-weight: normal; letter-spacing: normal; lin=
e-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-=
transform: none; white-space: normal; widows: auto; word-spacing: 0px; -web=
kit-text-stroke-width: 0px;">
<span style=3D"font-size: 10pt; font-family: 'Courier New'; color: black;">=
<o:p>&nbsp;</o:p></span></p>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri; font-size: medium;=
 font-style: normal; font-variant: normal; font-weight: normal; letter-spac=
ing: normal; line-height: normal; orphans: auto; text-align: start; text-in=
dent: 0px; text-transform: none; white-space: normal; widows: auto; word-sp=
acing: 0px; -webkit-text-stroke-width: 0px;">
<div>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif;">
<span style=3D"font-size: 10pt; font-family: 'Courier New'; color: black;">=
Thanks,<br>
--David</span></p>
</div>
</div>
</span>
</body>
</html>

--_000_CF7D8923B2DArepennociscocom_--


From nobody Wed Apr 23 19:09:46 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8497C1A0103 for <wgchairs@ietfa.amsl.com>; Wed, 23 Apr 2014 19:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGmmV8x9rCId for <wgchairs@ietfa.amsl.com>; Wed, 23 Apr 2014 19:09:43 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8C01A00F4 for <wgchairs@ietf.org>; Wed, 23 Apr 2014 19:09:42 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta14.westchester.pa.mail.comcast.net with comcast id tbDV1n0061GhbT85Ee9d54; Thu, 24 Apr 2014 02:09:37 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id te9c1n00d3ZTu2S3Te9c3G; Thu, 24 Apr 2014 02:09:37 +0000
Message-ID: <53587260.3060002@alum.mit.edu>
Date: Wed, 23 Apr 2014 22:09:36 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Proposal for Structuring New WGs
References: <CF7D8923.B2DA%repenno@cisco.com>
In-Reply-To: <CF7D8923.B2DA%repenno@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1398305377; bh=mq+iDxAKIk9ioRIQvIhGtlPKTQLNhb/cpxqXj5ydRic=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=KICZ0c5V+Lm7Cpai5znJOfKktc2fGIjSRR5N+MpkIrEPCslGid0wCtNVYuYjQKfmt b295pep53HhO8gLmzQtbLYiiUbD2Zwxnu/5sGxgWIAYNpQdhC7CLcc0KSEhs5PCWOX dT7eKMUzZ/tTzEb/49yeDx9dckQuid2tWVh49P1zudf91OBYqqS78fDMInmt9ow/tA qWruTZ746DXAB4dHdL007Jgepo9PKpOcKwSCZlcmRe+Q5x9kRB7KmERU91romYgNBt UrxwhghOUJyWqBwYHZtgHxeTSrwkzz+UBAOzDWfvu7F6Qwc2bA7AYxR9NCjRAmrMlY GEBHjX8l4b8Ww==
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/lFUwNlhdTvUkiXenfEy_q2hPO34
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Apr 2014 02:09:44 -0000

On 4/23/14 6:16 PM, Reinaldo Penno (repenno) wrote:
> if you ask some developers to reach an agreement on the definition of
> Firewall, it will never happen. But if you ask them to code a firewall
> product, they can deliver one to you in no time. And there, IMHO,  is
> the main problem of the way most WGs are structured.

And when two of them do that, they probably will not agree that what the 
other has developed *is* a firewall.

It is problems like that which have led to a request to start with 
requirements.

There is probably a happy medium somewhere, but it isn't always in the 
same place.

	Thanks,
	Paul

> From: <Black>, David <david.black@emc.com <mailto:david.black@emc.com>>
> Date: Tuesday, April 22, 2014 at 11:40 AM
> To: Cisco Employee <repenno@cisco.com <mailto:repenno@cisco.com>>
> Cc: WG Chairs <wgchairs@ietf.org <mailto:wgchairs@ietf.org>>
> Subject: RE: Proposal for Structuring New WGs
>
> I’ve definitely seen the scenario that Reinaldo describes - a WG formed
> w/a head of steam to go do “something” in an area, but it’s not exactly
> clear what that “something” should be ... so a lot of time and effort
> are expended on things like a problem statement, framework,
> architecture, etc. towards figuring out what that “something” ought to
> be ... and a lot of people lose interest along the way :-(.
>
> Thanks,
> --David
>


From nobody Thu Apr 24 11:33:46 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFF261A03BA; Thu, 24 Apr 2014 11:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuuiocmHm9HS; Thu, 24 Apr 2014 11:33:41 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0D21E1A039B; Thu, 24 Apr 2014 11:33:41 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id EB359C0E8; Thu, 24 Apr 2014 14:33:34 -0400 (EDT)
Date: Thu, 24 Apr 2014 14:33:34 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Proposal for Structuring New WGs
Message-ID: <20140424183334.GA3825@pfrc>
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca> <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com> <29478.1398286452@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29478.1398286452@sandelman.ca>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/7CnBXpai1_MnNwO7azSyZaYSvn4
Cc: WG Chairs <wgchairs@ietf.org>, "iab@ietf.org" <iab@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 24 Apr 2014 18:33:42 -0000

On Wed, Apr 23, 2014 at 04:54:12PM -0400, Michael Richardson wrote:
> Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>     > [MB] There's absolutely nothing in the current model to prevent WG chairs from
>     > doing more detailed project planning. ??I don't think we need a process in place
>     > as the task can be straightforward for some WGs. And, chairs are
>     > totally free
> 
> I'm not suggesting any process changes, but rather a reference
> design/template/running code of a more agile/iterative charter + milestones.
> Something that has been pre-reviewed by I* types.

I'd suggest there are two different issues being discussed here:
- Project management of WG tasks.  The above seems to fall in this category.
- Process that, when injected into WG work, is toxic to WG throughput.
  (Whether the process was needed and why is I think what kicked off the
   thread.)

FWIW, I'm a fan of "best practices for running a WG".  The one thing I'll
note is that the lag-time of various individuals in being able to
participate in the group's work can complicate certain forms of "agile". :-)

(I keep telling myself in my copious spare time that I'd analyze WG mail
list contribution activity surrounding the conferences and certain holidays,
but keep failing to find such copious spare time.)

The process issue is a bit different, IMO.  When architecture, problem
statements or use cases are thrown at an issue it's typically because
there's either enough difference in view as to what should be worked on or
its output. (The recent "here's three firewalls and no one does the same as
the others example elsewhere in-thread.)  Such requirements documents are
typical mitigation mechanisms elsewhere in the hardware/software industry so
asking for them isn't bad in itself.

What's problematic is when those documents either "circle the drain" because
no one can agree with each other or they don't get effort because people
aren't interested in working on them and just want to start writing code.

Fixing this is hard.

-- Jeff


From nobody Fri Apr 25 04:40:43 2014
Return-Path: <tmmorin.orange@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5597F1A0478; Fri, 25 Apr 2014 04:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLzNAnoP-DQT; Fri, 25 Apr 2014 04:40:39 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 56AAA1A0187; Fri, 25 Apr 2014 04:40:39 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id u57so251360wes.13 for <multiple recipients>; Fri, 25 Apr 2014 04:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hTI9c4ZKLYTQBpj73gWrPztFhYZaVFtVfe2P7+JqZpE=; b=DBS27br6fpjzHtPgEpOFCqtizdKxoeh3vLW9sdSE0qBBHHPsQM6fyQr9S6oWTfAPz3 5iD15HLefJDLVt1AP5SH/g77qtl2LWEXRe/igN/LvqQVIS5fmzh7Laiklna+N5q6MaQm QlM/Z56Mzt5KbPrS++WGz8uIeWG0z+In+EWwTNi+jznnoPknuFTRtes3LJkmw3qwayND J+X+z7LATrtURnOgNpoazyR6lSVqfWRjPhSVx1uVgvkK3E4exUInI2zK7ZZFsvPsUdmU AmJukIjytCkCZpniIz8YVRcJ1BfMdZhvzBN9qYx31jnLuz3uhzACOfMXp0S0vOz0fGQQ 6Scw==
X-Received: by 10.194.77.50 with SMTP id p18mr637696wjw.68.1398426032476; Fri, 25 Apr 2014 04:40:32 -0700 (PDT)
Received: from [127.0.0.1] (ARennes-652-1-23-26.w86-214.abo.wanadoo.fr. [86.214.14.26]) by mx.google.com with ESMTPSA id bj5sm5396203wib.3.2014.04.25.04.40.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 04:40:32 -0700 (PDT)
Sender: Thomas Morin <tmmorin.orange@gmail.com>
Message-ID: <535A498E.1080901@orange.com>
Date: Fri, 25 Apr 2014 13:39:58 +0200
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF Agenda <agenda@ietf.org>
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com>
In-Reply-To: <20140421222436.23895.20687.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/6__Ti-TineUoVaMKkAitsZiB7g4
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 11:40:41 -0000

Hi,

The tool only offers me the option to "Edit / Cancel Previously 
Requested Sessions" for the *last* IETF (89) and has no mention of IETF 
90.  I'm pretty sure that last Tuesday it was proposing the creation of 
a new request for the next meeting.

Am I right to assume that there is a glitch in the tool ?

Thanks,

-Thomas

IETF Agenda :
> Please submit requests to schedule your Working Group sessions using the "IETF Meeting Session Request Tool," a Web-based tool for submitting all of the information that the Secretariat requires to schedule your sessions.
>
> The URL for the tool is:
> https://datatracker.ietf.org/secr/sreq/
>


From nobody Fri Apr 25 04:41:53 2014
Return-Path: <gvandeve@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B901A0187; Fri, 25 Apr 2014 04:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.773
X-Spam-Level: 
X-Spam-Status: No, score=-14.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5PgMakS2rP8; Fri, 25 Apr 2014 04:41:49 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id E93DB1A0478; Fri, 25 Apr 2014 04:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1274; q=dns/txt; s=iport; t=1398426103; x=1399635703; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=pTKcqGIJYpCoxxqBDR9x3xfBlfqc6j0GCU7qgd0CwK4=; b=TrXhZiiZim62cHAr3b1U/SS8Nm5Bmx/l2xuMgeTRr3J0J4CYuYqbXBjB s55gSMaeTMoX/EGexGa2x4YqNCKKBlJVP0ZYQzp2nCCnvoezzMKLSRtCE OAug54OhXZ8RVpPSlcWEMJIL0lDnRSd+AazOv+PfuDgFUyZs5wp6XJBT2 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAJ9JWlOtJV2d/2dsb2JhbABZgwZPV4JlwToZdhZ0giUBAQEEIxFFDAQCAQgRBAEBAwIGHQMCAgIwFAEICAIEAQ0FCIg5DacNo00TBIEpjH8xBwaCaTWBFQEDq2GDMYIr
X-IronPort-AV: E=Sophos;i="4.97,926,1389744000"; d="scan'208";a="320322646"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-3.cisco.com with ESMTP; 25 Apr 2014 11:41:26 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s3PBfPCW030759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Apr 2014 11:41:25 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.118]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Fri, 25 Apr 2014 06:41:25 -0500
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: Thomas Morin <thomas.morin@orange.com>, IETF Agenda <agenda@ietf.org>
Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Topic: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Index: AQHPXbCAjWWQPufc20m45ldbhnH+mpsijpwA//+shVA=
Date: Fri, 25 Apr 2014 11:41:24 +0000
Message-ID: <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com>
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com>
In-Reply-To: <535A498E.1080901@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.164.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/HQskXky6Cjy_PowBYW1huAwlqIc
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 11:41:51 -0000

U2F3IHNhbWUgaXNzdWUgeWVzdGVyZGF5Li4uLg0KDQpHLw0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogV0dDaGFpcnMgW21haWx0bzp3Z2NoYWlycy1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YgVGhvbWFzIE1vcmluDQpTZW50OiAyNSBBcHJpbCAyMDE0IDEzOjQwDQpU
bzogSUVURiBBZ2VuZGENCkNjOiB3Z2NoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IDkwdGgg
SUVURiAtIFdvcmtpbmcgR3JvdXAvQk9GL0lSVEYgU2NoZWR1bGluZw0KDQpIaSwNCg0KVGhlIHRv
b2wgb25seSBvZmZlcnMgbWUgdGhlIG9wdGlvbiB0byAiRWRpdCAvIENhbmNlbCBQcmV2aW91c2x5
IFJlcXVlc3RlZCBTZXNzaW9ucyIgZm9yIHRoZSAqbGFzdCogSUVURiAoODkpIGFuZCBoYXMgbm8g
bWVudGlvbiBvZiBJRVRGIDkwLiAgSSdtIHByZXR0eSBzdXJlIHRoYXQgbGFzdCBUdWVzZGF5IGl0
IHdhcyBwcm9wb3NpbmcgdGhlIGNyZWF0aW9uIG9mIGEgbmV3IHJlcXVlc3QgZm9yIHRoZSBuZXh0
IG1lZXRpbmcuDQoNCkFtIEkgcmlnaHQgdG8gYXNzdW1lIHRoYXQgdGhlcmUgaXMgYSBnbGl0Y2gg
aW4gdGhlIHRvb2wgPw0KDQpUaGFua3MsDQoNCi1UaG9tYXMNCg0KSUVURiBBZ2VuZGEgOg0KPiBQ
bGVhc2Ugc3VibWl0IHJlcXVlc3RzIHRvIHNjaGVkdWxlIHlvdXIgV29ya2luZyBHcm91cCBzZXNz
aW9ucyB1c2luZyB0aGUgIklFVEYgTWVldGluZyBTZXNzaW9uIFJlcXVlc3QgVG9vbCwiIGEgV2Vi
LWJhc2VkIHRvb2wgZm9yIHN1Ym1pdHRpbmcgYWxsIG9mIHRoZSBpbmZvcm1hdGlvbiB0aGF0IHRo
ZSBTZWNyZXRhcmlhdCByZXF1aXJlcyB0byBzY2hlZHVsZSB5b3VyIHNlc3Npb25zLg0KPg0KPiBU
aGUgVVJMIGZvciB0aGUgdG9vbCBpczoNCj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9z
ZWNyL3NyZXEvDQo+DQoNCg==


From nobody Fri Apr 25 04:47:45 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9597E1A0478; Fri, 25 Apr 2014 04:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6n4ZkcIMGke; Fri, 25 Apr 2014 04:47:39 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 667BB1A017B; Fri, 25 Apr 2014 04:47:38 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s3PBlVsr026232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Apr 2014 06:47:32 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s3PBlUtL010782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 25 Apr 2014 13:47:30 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.94]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 25 Apr 2014 13:47:30 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: IETF Agenda <agenda@ietf.org>
Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Topic: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Index: AQHPXbCWzOxls2vwd0y/ekx61kfve5siGUMAgAAAZgCAACMOYA==
Date: Fri, 25 Apr 2014 11:47:29 +0000
Message-ID: <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com>
In-Reply-To: <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.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.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/omTu3BZm_INTtFsMTMrduAbduR4
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 11:47:41 -0000

U2FtZSBpc3N1ZSB0b2RheSBmb3IgVENQTQ0KDQpNaWNoYWVsDQoNCg0KPiAtLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBXR0NoYWlycyBbbWFpbHRvOndnY2hhaXJzLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBHdW50ZXINCj4gVmFuIGRlIFZlbGRlIChndmFuZGV2ZSkN
Cj4gU2VudDogRnJpZGF5LCBBcHJpbCAyNSwgMjAxNCAxOjQxIFBNDQo+IFRvOiBUaG9tYXMgTW9y
aW47IElFVEYgQWdlbmRhDQo+IENjOiB3Z2NoYWlyc0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSRTog
OTB0aCBJRVRGIC0gV29ya2luZyBHcm91cC9CT0YvSVJURiBTY2hlZHVsaW5nDQo+IA0KPiBTYXcg
c2FtZSBpc3N1ZSB5ZXN0ZXJkYXkuLi4uDQo+IA0KPiBHLw0KPiANCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogV0dDaGFpcnMgW21haWx0bzp3Z2NoYWlycy1ib3VuY2VzQGll
dGYub3JnXSBPbiBCZWhhbGYgT2YgVGhvbWFzDQo+IE1vcmluDQo+IFNlbnQ6IDI1IEFwcmlsIDIw
MTQgMTM6NDANCj4gVG86IElFVEYgQWdlbmRhDQo+IENjOiB3Z2NoYWlyc0BpZXRmLm9yZw0KPiBT
dWJqZWN0OiBSZTogOTB0aCBJRVRGIC0gV29ya2luZyBHcm91cC9CT0YvSVJURiBTY2hlZHVsaW5n
DQo+IA0KPiBIaSwNCj4gDQo+IFRoZSB0b29sIG9ubHkgb2ZmZXJzIG1lIHRoZSBvcHRpb24gdG8g
IkVkaXQgLyBDYW5jZWwgUHJldmlvdXNseQ0KPiBSZXF1ZXN0ZWQgU2Vzc2lvbnMiIGZvciB0aGUg
Kmxhc3QqIElFVEYgKDg5KSBhbmQgaGFzIG5vIG1lbnRpb24gb2YgSUVURg0KPiA5MC4gIEknbSBw
cmV0dHkgc3VyZSB0aGF0IGxhc3QgVHVlc2RheSBpdCB3YXMgcHJvcG9zaW5nIHRoZSBjcmVhdGlv
biBvZg0KPiBhIG5ldyByZXF1ZXN0IGZvciB0aGUgbmV4dCBtZWV0aW5nLg0KPiANCj4gQW0gSSBy
aWdodCB0byBhc3N1bWUgdGhhdCB0aGVyZSBpcyBhIGdsaXRjaCBpbiB0aGUgdG9vbCA/DQo+IA0K
PiBUaGFua3MsDQo+IA0KPiAtVGhvbWFzDQo+IA0KPiBJRVRGIEFnZW5kYSA6DQo+ID4gUGxlYXNl
IHN1Ym1pdCByZXF1ZXN0cyB0byBzY2hlZHVsZSB5b3VyIFdvcmtpbmcgR3JvdXAgc2Vzc2lvbnMg
dXNpbmcNCj4gdGhlICJJRVRGIE1lZXRpbmcgU2Vzc2lvbiBSZXF1ZXN0IFRvb2wsIiBhIFdlYi1i
YXNlZCB0b29sIGZvcg0KPiBzdWJtaXR0aW5nIGFsbCBvZiB0aGUgaW5mb3JtYXRpb24gdGhhdCB0
aGUgU2VjcmV0YXJpYXQgcmVxdWlyZXMgdG8NCj4gc2NoZWR1bGUgeW91ciBzZXNzaW9ucy4NCj4g
Pg0KPiA+IFRoZSBVUkwgZm9yIHRoZSB0b29sIGlzOg0KPiA+IGh0dHBzOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvc2Vjci9zcmVxLw0KPiA+DQoNCg==


From nobody Fri Apr 25 04:56:50 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94421A048D; Fri, 25 Apr 2014 04:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.493
X-Spam-Level: 
X-Spam-Status: No, score=-1.493 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PI-5ya8xeTER; Fri, 25 Apr 2014 04:56:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id AA6D81A047E; Fri, 25 Apr 2014 04:56:45 -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 s3PBuYBU011647; Fri, 25 Apr 2014 12:56:34 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s3PBuYBU011647
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1398426995; bh=sQR+k5Zj+cQhrSfxoweUIyDLRYY=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=6ZqDcQxRpE0twNT5F+WDxsAmecDIOGhmpMkGcqA2kpao0TkwykFKjTs26FZwuv4J3 4sbBfP7kwiFVXYdi37iHlkG5nA3Q2rF7TpR0XOjBoiU8aOxNJPQDPYNQTQE7jovjXe egtePWJGw/+fYmdLyMYKKqqdJ4nAd/1ijTGt/koo=
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 q3OCuY0546055289dF ret-id none; Fri, 25 Apr 2014 12:56:35 +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 s3PBuYrd027515 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Apr 2014 12:56:34 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Date: Fri, 25 Apr 2014 12:56:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com> <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com> <FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1874)
X-smtpf-Report: sid=q3OCuY054605528900; tid=q3OCuY0546055289dF; 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: s3PBuYBU011647
X-ECS-MailScanner: Found to be clean
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/TcfGGcRCy2pVB3X09nTFwk6w9Xc
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 11:56:47 -0000

Hmmm, I seemed to request a dnssd meeting just fine for IETF90.  I =
copied the IETF89 request (I think there was  a button to import that), =
edited, and submitted.

Tim

On 25 Apr 2014, at 12:47, Scharf, Michael (Michael) =
<michael.scharf@alcatel-lucent.com> wrote:

> Same issue today for TCPM
>=20
> Michael
>=20
>=20
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Gunter
>> Van de Velde (gvandeve)
>> Sent: Friday, April 25, 2014 1:41 PM
>> To: Thomas Morin; IETF Agenda
>> Cc: wgchairs@ietf.org
>> Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
>>=20
>> Saw same issue yesterday....
>>=20
>> G/
>>=20
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Thomas
>> Morin
>> Sent: 25 April 2014 13:40
>> To: IETF Agenda
>> Cc: wgchairs@ietf.org
>> Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
>>=20
>> Hi,
>>=20
>> The tool only offers me the option to "Edit / Cancel Previously
>> Requested Sessions" for the *last* IETF (89) and has no mention of =
IETF
>> 90.  I'm pretty sure that last Tuesday it was proposing the creation =
of
>> a new request for the next meeting.
>>=20
>> Am I right to assume that there is a glitch in the tool ?
>>=20
>> Thanks,
>>=20
>> -Thomas
>>=20
>> IETF Agenda :
>>> Please submit requests to schedule your Working Group sessions using
>> the "IETF Meeting Session Request Tool," a Web-based tool for
>> submitting all of the information that the Secretariat requires to
>> schedule your sessions.
>>>=20
>>> The URL for the tool is:
>>> https://datatracker.ietf.org/secr/sreq/
>>>=20
>=20


From nobody Fri Apr 25 05:33:55 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31681A04AF; Fri, 25 Apr 2014 05:33:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ydt4MkKi3GZ; Fri, 25 Apr 2014 05:33:52 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 505111A04B1; Fri, 25 Apr 2014 05:33:52 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id uo5so3160639pbc.18 for <multiple recipients>; Fri, 25 Apr 2014 05:33:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=c/DjTu5QMPHH6WqpC2oot3BLqMsDwMo32AIq/SfP+RI=; b=jCxgtYRnJVVfIaJDtUkxRKRa2x3sEYTDWnZEs2gAKhefz1yjSDLnpn+KtxmTAsrEGP ltZ7JrIg+gyx2uDCNShwQ2tQThx8dtpvOj0fwR8ImJBWOO7L5xZyYR5ldVUuOzLpJ0/k qifvaYujhgT1h5+mkK5ZVWUPVXs56+/iuGkjqQDLci+2in7klxde4kJ3YyeRpwVMOgn6 E8eQkY55XrhS2T5K2tRKF5C2Z2+bBVUfStVpEQo6Sc6KzQ5XlxTduRn4263nWpld1NI/ UYIZoDKGCvYOuHdVsLSaRaMl1hBsAylVyCJuw7xcEVzZNtj/dt/2qpxY+5DLFvGtx9nc dPiA==
X-Received: by 10.68.194.97 with SMTP id hv1mr10998146pbc.162.1398429225989; Fri, 25 Apr 2014 05:33:45 -0700 (PDT)
Received: from feather.local ([12.197.85.10]) by mx.google.com with ESMTPSA id oz7sm15702970pbc.41.2014.04.25.05.33.45 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Apr 2014 05:33:45 -0700 (PDT)
Message-ID: <535A5627.10407@gmail.com>
Date: Fri, 25 Apr 2014 05:33:43 -0700
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Thunderbird/30.0a2
MIME-Version: 1.0
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com> <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com> <FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/rtxXgL25ywihjYmu77Q3mLKTieo
Cc: IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 12:33:54 -0000

This link (authenticated of course) appears to be fine for dnsop.


perhaps the tool will only allow the scheduling of DNS meetings?

tim

On 4/25/14, 4:56 AM, Tim Chown wrote:
> Hmmm, I seemed to request a dnssd meeting just fine for IETF90.  I copied the IETF89 request (I think there was  a button to import that), edited, and submitted.
>
> Tim
>
> On 25 Apr 2014, at 12:47, Scharf, Michael (Michael) <michael.scharf@alcatel-lucent.com> wrote:
>
>> Same issue today for TCPM
>>
>> Michael
>>
>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Gunter
>>> Van de Velde (gvandeve)
>>> Sent: Friday, April 25, 2014 1:41 PM
>>> To: Thomas Morin; IETF Agenda
>>> Cc: wgchairs@ietf.org
>>> Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
>>>
>>> Saw same issue yesterday....
>>>
>>> G/
>>>
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Thomas
>>> Morin
>>> Sent: 25 April 2014 13:40
>>> To: IETF Agenda
>>> Cc: wgchairs@ietf.org
>>> Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
>>>
>>> Hi,
>>>
>>> The tool only offers me the option to "Edit / Cancel Previously
>>> Requested Sessions" for the *last* IETF (89) and has no mention of IETF
>>> 90.  I'm pretty sure that last Tuesday it was proposing the creation of
>>> a new request for the next meeting.
>>>
>>> Am I right to assume that there is a glitch in the tool ?
>>>
>>> Thanks,
>>>
>>> -Thomas
>>>
>>> IETF Agenda :
>>>> Please submit requests to schedule your Working Group sessions using
>>> the "IETF Meeting Session Request Tool," a Web-based tool for
>>> submitting all of the information that the Secretariat requires to
>>> schedule your sessions.
>>>>
>>>> The URL for the tool is:
>>>> https://datatracker.ietf.org/secr/sreq/
>>>>
>>
>


From nobody Fri Apr 25 05:47:54 2014
Return-Path: <acmorton@att.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A57E1A04A3; Fri, 25 Apr 2014 05:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.473
X-Spam-Level: 
X-Spam-Status: No, score=-4.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ks0GjsyL5t84; Fri, 25 Apr 2014 05:47:51 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [204.178.8.22]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFDF1A01AC; Fri, 25 Apr 2014 05:47:51 -0700 (PDT)
Received: from mail-green.research.att.com (H-135-207-255-15.research.att.com [135.207.255.15]) by mail-pink.research.att.com (Postfix) with ESMTP id 6119F1208AC; Fri, 25 Apr 2014 08:48:16 -0400 (EDT)
Received: from njfpsrvexg8.research.att.com (unknown [135.207.255.242]) by mail-green.research.att.com (Postfix) with ESMTP id ED5BEE0102; Fri, 25 Apr 2014 08:47:36 -0400 (EDT)
Received: from NJFPSRVEXG8.research.att.com ([fe80::cdea:b3f6:3efa:1841]) by njfpsrvexg8.research.att.com ([fe80::cdea:b3f6:3efa:1841%13]) with mapi; Fri, 25 Apr 2014 08:47:44 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Tim Wicinski <tjw.ietf@gmail.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Date: Fri, 25 Apr 2014 08:47:43 -0400
Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Topic: 90th IETF - Working Group/BOF/IRTF Scheduling
Thread-Index: Ac9ggqLLbZft6PhxTXCUGqhAP6S1sQAAThNQ
Message-ID: <2845723087023D4CB5114223779FA9C801795CC8D5@njfpsrvexg8.research.att.com>
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com> <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com> <FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <535A5627.10407@gmail.com>
In-Reply-To: <535A5627.10407@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/dhomm5JMDcKfRkukKhO8ZAxB7TA
Cc: IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 12:47:52 -0000

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Tim
> Wicinski
> Sent: Friday, April 25, 2014 8:34 AM
...
>=20
> This link (authenticated of course) appears to be fine for dnsop.
>=20
> perhaps the tool will only allow the scheduling of DNS meetings?
>=20
> tim

When I first looked at the session request page, it was ietf-89.
I went on to do some draft maintenance in datatracker,
and tried again - ietf-90...

so, make sure your drafts are up to date,=20
and you may be rewarded with the right to schedule?

wfm,
Al

...
> >>>> The URL for the tool is:
> >>>> https://datatracker.ietf.org/secr/sreq/
> >>>>
> >>



From nobody Fri Apr 25 05:54:43 2014
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3877D1A04A3; Fri, 25 Apr 2014 05:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39nwo-qmmtjD; Fri, 25 Apr 2014 05:54:36 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 5152D1A048D; Fri, 25 Apr 2014 05:54:36 -0700 (PDT)
Received: from h25n7-s-oev-a31.ias.bredband.telia.com ([81.229.146.25]:58740 helo=vigonier.tools.ietf.org) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1Wdfe2-00088y-Oa; Fri, 25 Apr 2014 14:54:23 +0200
Message-ID: <535A5AC7.1030308@levkowetz.com>
Date: Fri, 25 Apr 2014 14:53:27 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>,  "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com> <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com> <FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 81.229.146.25
X-SA-Exim-Rcpt-To: tjc@ecs.soton.ac.uk, michael.scharf@alcatel-lucent.com, wgchairs@ietf.org, agenda@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/5wqZRen81DbnMiJsyZ8jttH8Asg
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, IETF Agenda <agenda@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 12:54:40 -0000

Hi,

This was an issue with shifting assumptions brought about by a new
agenda scheduling tool we've recently deployed.  Formerly, the 'current
meeting' was assumed to be the entry in the database meeting table with
the latest date and at least a skeleton agenda.  With the new tool,
agenda scheduling work can be done in parallel by secretariat folks and
ADs as preliminary agendas, and won't show up as associated with the
current meeting until it's much closer to being finalized.

I've now changed the code to assume that the ietf meeting in the table
which has the latest date is the 'current' meeting, whether or not
there's an agenda associated with it.  This should let you see the
session request tool for the correct meeting (90).

Best regards,

	Henrik

On 2014-04-25 13:56 Tim Chown said the following:
> Hmmm, I seemed to request a dnssd meeting just fine for IETF90.  I copied the IETF89 request (I think there was  a button to import that), edited, and submitted.
> 
> Tim
> 
> On 25 Apr 2014, at 12:47, Scharf, Michael (Michael) <michael.scharf@alcatel-lucent.com> wrote:
> 
>> Same issue today for TCPM
>> 
>> Michael
>> 
>> 
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Gunter
>>> Van de Velde (gvandeve)
>>> Sent: Friday, April 25, 2014 1:41 PM
>>> To: Thomas Morin; IETF Agenda
>>> Cc: wgchairs@ietf.org
>>> Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
>>> 
>>> Saw same issue yesterday....
>>> 
>>> G/
>>> 
>>> -----Original Message-----
>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Thomas
>>> Morin
>>> Sent: 25 April 2014 13:40
>>> To: IETF Agenda
>>> Cc: wgchairs@ietf.org
>>> Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
>>> 
>>> Hi,
>>> 
>>> The tool only offers me the option to "Edit / Cancel Previously
>>> Requested Sessions" for the *last* IETF (89) and has no mention of IETF
>>> 90.  I'm pretty sure that last Tuesday it was proposing the creation of
>>> a new request for the next meeting.
>>> 
>>> Am I right to assume that there is a glitch in the tool ?
>>> 
>>> Thanks,
>>> 
>>> -Thomas
>>> 
>>> IETF Agenda :
>>>> Please submit requests to schedule your Working Group sessions using
>>> the "IETF Meeting Session Request Tool," a Web-based tool for
>>> submitting all of the information that the Secretariat requires to
>>> schedule your sessions.
>>>> 
>>>> The URL for the tool is:
>>>> https://datatracker.ietf.org/secr/sreq/
>>>> 
>> 
> 
> 


From nobody Fri Apr 25 10:26:02 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12EC11A06CE for <wgchairs@ietfa.amsl.com>; Fri, 25 Apr 2014 10:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7xT-Y-4bgeK for <wgchairs@ietfa.amsl.com>; Fri, 25 Apr 2014 10:25:56 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id C8E931A028B for <wgchairs@ietf.org>; Fri, 25 Apr 2014 10:25:56 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3PHPnKr023999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for <wgchairs@ietf.org>; Fri, 25 Apr 2014 12:25:50 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-107-66.dllstx.fios.verizon.net [173.57.107.66] claimed to be unnumerable.local
Message-ID: <535A9A9D.9060406@nostrum.com>
Date: Fri, 25 Apr 2014 12:25:49 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535A498E.1080901@orange.com> <67832B1175062E48926BF3CB27C49B24113A0C0B@xmb-aln-x12.cisco.com> <655C07320163294895BBADA28372AF5D2C2A90@FR712WXCHMBA15.zeu.alcatel-lucent.com> <FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <EMEW3|b76c2d751a5255ec50f01111ac284d08q3OCuY03tjc|ecs.soton.ac.uk|FFA75E35-1C22-49AF-9C15-9DCB7A71DD3C@ecs.soton.ac.uk> <535A5AC7.1030308@levkowetz.com>
In-Reply-To: <535A5AC7.1030308@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/4cktC8thQ2Am1wqZ435OdqyWb5k
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Apr 2014 17:25:59 -0000

If you put in a request already, but would like to verify it took what 
you intended, you can verify it at
<http://datatracker.ietf.org/meeting/90/requests>

RjS

On 4/25/14, 7:53 AM, Henrik Levkowetz wrote:
> Hi,
>
> This was an issue with shifting assumptions brought about by a new
> agenda scheduling tool we've recently deployed.  Formerly, the 'current
> meeting' was assumed to be the entry in the database meeting table with
> the latest date and at least a skeleton agenda.  With the new tool,
> agenda scheduling work can be done in parallel by secretariat folks and
> ADs as preliminary agendas, and won't show up as associated with the
> current meeting until it's much closer to being finalized.
>
> I've now changed the code to assume that the ietf meeting in the table
> which has the latest date is the 'current' meeting, whether or not
> there's an agenda associated with it.  This should let you see the
> session request tool for the correct meeting (90).
>
> Best regards,
>
> 	Henrik
>
> On 2014-04-25 13:56 Tim Chown said the following:
>> Hmmm, I seemed to request a dnssd meeting just fine for IETF90.  I copied the IETF89 request (I think there was  a button to import that), edited, and submitted.
>>
>> Tim
>>
>> On 25 Apr 2014, at 12:47, Scharf, Michael (Michael) <michael.scharf@alcatel-lucent.com> wrote:
>>
>>> Same issue today for TCPM
>>>
>>> Michael
>>>
>>>
>>>> -----Original Message-----
>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Gunter
>>>> Van de Velde (gvandeve)
>>>> Sent: Friday, April 25, 2014 1:41 PM
>>>> To: Thomas Morin; IETF Agenda
>>>> Cc: wgchairs@ietf.org
>>>> Subject: RE: 90th IETF - Working Group/BOF/IRTF Scheduling
>>>>
>>>> Saw same issue yesterday....
>>>>
>>>> G/
>>>>
>>>> -----Original Message-----
>>>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Thomas
>>>> Morin
>>>> Sent: 25 April 2014 13:40
>>>> To: IETF Agenda
>>>> Cc: wgchairs@ietf.org
>>>> Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
>>>>
>>>> Hi,
>>>>
>>>> The tool only offers me the option to "Edit / Cancel Previously
>>>> Requested Sessions" for the *last* IETF (89) and has no mention of IETF
>>>> 90.  I'm pretty sure that last Tuesday it was proposing the creation of
>>>> a new request for the next meeting.
>>>>
>>>> Am I right to assume that there is a glitch in the tool ?
>>>>
>>>> Thanks,
>>>>
>>>> -Thomas
>>>>
>>>> IETF Agenda :
>>>>> Please submit requests to schedule your Working Group sessions using
>>>> the "IETF Meeting Session Request Tool," a Web-based tool for
>>>> submitting all of the information that the Secretariat requires to
>>>> schedule your sessions.
>>>>> The URL for the tool is:
>>>>> https://datatracker.ietf.org/secr/sreq/
>>>>>
>>


From nobody Sat Apr 26 01:26:19 2014
Return-Path: <loa@pi.nu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9E41A0324 for <wgchairs@ietfa.amsl.com>; Sat, 26 Apr 2014 01:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLFQ8GbdzeVG for <wgchairs@ietfa.amsl.com>; Sat, 26 Apr 2014 01:26:16 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id B73501A0473 for <wgchairs@ietf.org>; Sat, 26 Apr 2014 01:26:16 -0700 (PDT)
Received: from [192.168.1.5] (unknown [112.208.110.53]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id F045B1800905 for <wgchairs@ietf.org>; Sat, 26 Apr 2014 10:26:07 +0200 (CEST)
Message-ID: <535B6D9C.4010506@pi.nu>
Date: Sat, 26 Apr 2014 10:26:04 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Proposal for Structuring New WGs
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca> <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com> <29478.1398286452@sandelman.ca>
In-Reply-To: <29478.1398286452@sandelman.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Jg4rjuznRwn0ImU3s8v_fBiwjQY
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Apr 2014 08:26:18 -0000

Folks,

What is the driver behind this i there a wildly felt need to for
giving each and every working the same structure?

/Loa

On 2014-04-23 22:54, Michael Richardson wrote:
>
> Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>      > [MB] There's absolutely nothing in the current model to prevent WG chairs from
>      > doing more detailed project planning.  I don't think we need a process in place
>      > as the task can be straightforward for some WGs. And, chairs are
>      > totally free
>
> I'm not suggesting any process changes, but rather a reference
> design/template/running code of a more agile/iterative charter + milestones.
> Something that has been pre-reviewed by I* types.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>   -= IPv6 IoT consulting =-
>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Sun Apr 27 21:44:55 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1EB1A070B for <wgchairs@ietfa.amsl.com>; Sun, 27 Apr 2014 21:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYnqIy4aRzo3 for <wgchairs@ietfa.amsl.com>; Sun, 27 Apr 2014 21:44:52 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id ECB3F1A06F1 for <wgchairs@ietf.org>; Sun, 27 Apr 2014 21:44:51 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id u14so1652710lbd.2 for <wgchairs@ietf.org>; Sun, 27 Apr 2014 21:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bNVOSI05Zhf9KOnXHLMINI0dbTnlqxqqGTugNB4w2gk=; b=PeY8azi8+xk5ln63hSJ/egAal+ZHIhmaLTIASzWYMcfqD305FoM6v3ct75aINRwq6A fQmwfEkzmq5/yUJS5pGkTOqubxETU0bBTIQTT5zRhrI3SwXR81MiJWKq2G0ScP8ZRAA5 ThFH6e2+d9bufXf+9yV/tA7MTwKor8I+70tPe48k59uEh+choVhGyiLP+pSTVyIHYicM gQ3keAUnngQx8UB6oJKoK6wTqv5ammrQmWoUIXg1mdYILbIpfVKyZQ7NBlNwRFjeOTJi AFoRKE8QDZ0vsainR0DPYAaKcOtibmasgQPkpbGYk4RC0WYabBgF/sprVkkziAeMWW1q n8Ew==
X-Received: by 10.112.173.196 with SMTP id bm4mr127057lbc.38.1398660290232; Sun, 27 Apr 2014 21:44:50 -0700 (PDT)
Received: from [10.37.192.81] ([77.95.242.69]) by mx.google.com with ESMTPSA id q8sm17570761lbr.3.2014.04.27.21.44.48 for <wgchairs@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 27 Apr 2014 21:44:49 -0700 (PDT)
Message-ID: <535DDCAD.4040604@gmail.com>
Date: Mon, 28 Apr 2014 07:44:29 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com>
In-Reply-To: <20140421222436.23895.20687.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/EpVbCooCEN7OJnv55WtiP9tIibI
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 04:44:53 -0000

I managed to successfully schedule my WGs (dime, radext, dmm). However, 
I had to go back to do edits to some of the schedulings but clicking 
"edit" on WG Chair Dashboard results in an internal server error. Anyone 
else experienced the same?

- Jouni



4/22/2014 1:24 AM, IETF Agenda kirjoitti:
>
> -----------------------------------------------------------------
> 90th IETF – Toronto, ON, Canada
> Meeting Dates: July 20 - 25, 2014
> -----------------------------------------------------------------
>
> We are accepting scheduling requests for all Working Groups, BOFs, and Research Groups starting today.
>
> NOTE: Please ensure your list of conflicts is complete and up to date prior to submitting your session request.
>
> The milestones and deadlines for scheduling-related activities are as follows:
> Cut-off dates are subject to change.
>
> •	2014-04-21 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool.
> •	2014-06-06 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool.
> •	2014-06-06 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
> •	2014-06-13 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
> •	2014-06-20 (Friday): Preliminary agenda published for comment.
> •	2014-06-23 (Monday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
> •	2014-06-27 (Friday): Final agenda to be published.
> •	2014-07-07 (Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-07-14 (Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-08-15 (Friday): Proceedings submission cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
> •	2014-09-05 (Friday): Proceedings submission corrections cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>


From nobody Mon Apr 28 01:16:11 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28351A08E7 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 01:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2u0zu6UyhbeT for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 01:16:09 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id E78771A08D8 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 01:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7458; q=dns/txt; s=iport; t=1398672967; x=1399882567; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=DKhoemQ464kj/dgP/jo0J9RKi+X3PQ7wDJMiPsNTMTU=; b=dlMVTzv6JOo7ejz1BJ4tUhidpsx72e2xPFJAu42u/HfrpDmVeydb5Nq6 +hAfHXOp+fdqEeEESkisR6QAwSO9VWnPZfPecVjwgWUq3Up2ezQ6nvYUr AW8VSvAnvFEe1tFYWKWRhBBrw5XgnC4zLFK1672edKVIGO+VF3xLG2SoR c=;
X-IronPort-AV: E=Sophos; i="4.97,942,1389744000"; d="scan'208,217"; a="25520288"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 28 Apr 2014 08:16:06 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3S8G5cC013084; Mon, 28 Apr 2014 08:16:05 GMT
Message-ID: <535E0E45.9010104@cisco.com>
Date: Mon, 28 Apr 2014 10:16:05 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
Subject: Re: Proposal for Structuring New WGs
References: <CF7BF13E.B1AE%repenno@cisco.com>
In-Reply-To: <CF7BF13E.B1AE%repenno@cisco.com>
Content-Type: multipart/alternative; boundary="------------040206090001050307040902"
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/0npGmgCfaQxF3zbSVwCX4aaYdco
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 08:16:10 -0000

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

Hi Reinaldo,
> Hi,
>
> I¹ve been thinking about how some Wgs get stuck and others loose steam and
> would like to propose an optional way to structure new WGs.
>
> I think the delay or failure of many WGs can be attribute as the way we
> IETF structures WGs.
>
> When a WG is formed there is lots of energy, many drafts, people with
> running code (yes, these people still exist) and great participation. But
> then, the IETF step on the brakes by following a cookie cutter approach of
> asking for a problem statement draft, some form of architecture draft and
> produces, most often than not, a set in stone charter.  This alone makes a
> boatload of people leave the WG effort. Some of these folks have even
> running code (I¹ve been there) or drafts that many folks are interested
> but can not be discussed until the current charter is done.
Yes, this is a real problem.
While discussing this issue, Spencer Dawkins reminded me of RFC 5434:

    In many cases,
    however, the intent is to form a WG.  In those cases, the goal of the
    BOF is to demonstrate that the community has agreement that:

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

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

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

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

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

Special attention to the third bullet point above.
If the problem is well understood enough for a working group to be 
chartered, how much more work does a working group need to do, in 
defining the problem?
Maybe we should apply this rule in a stricter manner. You wrote "When a 
WG is formed there is lots of energy ", I would observe that when a WG 
is about to be created (BoF), there is even more energy ... to get the 
WG created. We should really capitalize on it.

Regards, Benoit
>
> And the WG struggles on and on because of the very fact that some of the
> folks with energy that could drive the WG will not wait on the sidelines
> for 2 years until rechartering so that maybe, just maybe, their draft can
> get on the charter.
>
> My proposal is that certain WGs should be formed with some overall charter
> and the definite charter should be written _after_ say, two official WG
> meetings, where lots of discussion on mailing list and presentations
> happen. Then the charter becomes the most important drafts people are
> interested. In this case for example, the problem statement becomes in
> fact those drafts.
>
> Maybe this is already allowed but it is not known or not encouraged. At
> least if possible it would be good to experiment with that approach in
> some of the popular or struggling WGs.
>
> Thanks,
>
> -Reinaldo
>
>
>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Reinaldo,<br>
    </div>
    <blockquote cite="mid:CF7BF13E.B1AE%25repenno@cisco.com" type="cite">
      <pre wrap="">Hi,

I&sup1;ve been thinking about how some Wgs get stuck and others loose steam and
would like to propose an optional way to structure new WGs.

I think the delay or failure of many WGs can be attribute as the way we
IETF structures WGs.

When a WG is formed there is lots of energy, many drafts, people with
running code (yes, these people still exist) and great participation. But
then, the IETF step on the brakes by following a cookie cutter approach of
asking for a problem statement draft, some form of architecture draft and
produces, most often than not, a set in stone charter.  This alone makes a
boatload of people leave the WG effort. Some of these folks have even
running code (I&sup1;ve been there) or drafts that many folks are interested
but can not be discussed until the current charter is done.</pre>
    </blockquote>
    Yes, this is a real problem.<br>
    While discussing this issue, Spencer Dawkins reminded me of RFC 5434:<br>
    <br>
    <pre class="newpage">   In many cases,
   however, the intent is to form a WG.  In those cases, the goal of the
   BOF is to demonstrate that the community has agreement that:

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

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

     <font color="#ff0000"> - the scope of the problem is well defined and understood, that
        is, people generally understand what the WG will work on (and
        what it won't) and what its actual deliverables will be.</font>

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

      - it is believed that the WG has a reasonable probability of
        having success (i.e., in completing the deliverables in its
        charter in a timely fashion).</pre>
    Special attention to the third bullet point above.<br>
    If the problem is well understood enough for a working group to be
    chartered, how much more work does a working group need to do, in
    defining the problem?<br>
    Maybe we should apply this rule in a stricter manner. You wrote
    "When a WG is formed there is lots of energy
    ", I would observe that when a WG is about to be created (BoF),
    there is even more energy ... to get the WG created. We should
    really capitalize on it.<br>
    <br>
    Regards, Benoit<br>
    <blockquote cite="mid:CF7BF13E.B1AE%25repenno@cisco.com" type="cite">
      <pre wrap="">

And the WG struggles on and on because of the very fact that some of the
folks with energy that could drive the WG will not wait on the sidelines
for 2 years until rechartering so that maybe, just maybe, their draft can
get on the charter.

My proposal is that certain WGs should be formed with some overall charter
and the definite charter should be written _after_ say, two official WG
meetings, where lots of discussion on mailing list and presentations
happen. Then the charter becomes the most important drafts people are
interested. In this case for example, the problem statement becomes in
fact those drafts. 

Maybe this is already allowed but it is not known or not encouraged. At
least if possible it would be good to experiment with that approach in
some of the popular or struggling WGs.

Thanks,

-Reinaldo



</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040206090001050307040902--


From nobody Mon Apr 28 02:33:10 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C98141A082A for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 02:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUrIUwbxJt-r for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 02:32:57 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id D3D8A1A075F for <wgchairs@ietf.org>; Mon, 28 Apr 2014 02:32:56 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3S9WZc0022920; Mon, 28 Apr 2014 10:32:35 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3S9WR48022742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Apr 2014 10:32:28 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Benoit Claise'" <bclaise@cisco.com>, "'Reinaldo Penno \(repenno\)'" <repenno@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com>
In-Reply-To: <535E0E45.9010104@cisco.com>
Subject: RE: Proposal for Structuring New WGs
Date: Mon, 28 Apr 2014 10:32:25 +0100
Message-ID: <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKoR+6uePXZvSV93DO03hjwwBAGYwEbvwYJmWwSxPA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20660.006
X-TM-AS-Result: No--8.241-10.0-31-10
X-imss-scan-details: No--8.241-10.0-31-10
X-TMASE-MatchedRID: 9d2LtCNB3NIkzrQfI6wWyOYAh37ZsBDCzdHzFaLfgBFLjXXGQy6nlMIE WwKN7d6VXKdjrSp48nz2N0enZsxy1b52zSPzPvrjW7gz/Gbgpl4HdYH++bm0GNhaunXv2miGhls 0WvdOE0PJHKifp/CC1M97RpyefUIM8IDC+zKI/xiWLCkl1lq7B0Crr/LkAQ46Ysz9F4FLBTBVrl 4dPkDCJoSY+NPKVbHM8vAoHLzFKo+K6EB7L3k2mpCYtcHXhxbafiuvKi9huaZXopZjyO6CZb/C8 L6a8Cw82lwKSUqVRIfkY5jnILkv8ZzwTSXODCF6U+OjsPhIWDhb2iL0xnz/ElfXgfL55invgx0s FCXnAdo0vci8BoxZiwWybAXaTso4JXSv0ZHOBlpwUSK4/EeOxTRsfGqPls+VULzpjrEhojr6HzU bYzyTZbbeMwYI4+z9RTMw2YgTW5UfTQBZ1bNjblZ14JN9Kx7yu56wFPSkMVEgcyGevtftJ6PFjJ EFr+olfeZdJ1Xsorg65tgsJWcFUXnN0DN7HnFmVkWyoqD+DMGCOn22UB1x+EC+2DxJYTvfJIA3K f0ogqLALV/087/prJRMZUCEHkRt
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/HKnDnzKFp59jPYC8ZLpUp5GnPoI
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 28 Apr 2014 09:33:00 -0000

Hi Benoit,

Thanks for flagging this piece of text...

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

You said...

> If the problem is well understood enough for a working group to be
> chartered, how much more work does a working group need to do,
> in defining the problem?

I have seen a number of cases recently where the problem was *not* well enough
understood to charter a working group. True, if you stopped any one person in
the corridor, they might have said that *they* understood the problem well
enough, but it was clear to me in these cases that there was not even a rough
consensus of agreement of understanding of the problem.

In these cases there are three option:
1. Say no. Ask for more work agreeing the problem and hold
   another BoF later.
2. Form a WG to work to agree on the problem and recharter
   later.
3. Take a punt. Form the WG to do real, solutions work. 

I have seen the third of these go horribly wrong: many people developing
different solutions in the same space to do subtly different and conflicting
things.

The first option, on the other hand, seems to be more blocking of progress than
the second option, and so I tend to adopt the second option. That option brings
the work into the IETF, but requires that effort is expended developing the
problem space and scoping the solutions space.

So, when Reinaldo bemoans that:

> the IETF step on the brakes by following a cookie cutter approach of
> asking for a problem statement draft, some form of architecture draft and
> produces, most often than not, a set in stone charter.

I find that this is often a necessary step that has been "borrowed" from the BoF
process. That is, it is legacy work that should have been done before the WG was
formed, but which we have decided to let slip until after the WG has been
formed. We have chosen to form the WG because it is clear that we have a topic
that has significant interest and is in scope for the IETF, but we also
recognise that the problem is not well-defined or understood.

But where I am repeatedly frustrated is the length of time the WG spends in this
state. If, as is widely claimed, the problem *is* well understood to the extent
that running code exists, I do not understand why it takes multiple IETF cycles,
and often multiple years, to document the problem.  If so many people are
interested and working in the space, why is none of them capable of writing a 20
page document that clearly and concisely describes the problem? If there is a
space where many people are writing code, why is it so hard to get consensus on
the problem statement?

No, I know two answers to my questions both predicated on the assumption that
writing a short document is not problem statement:

a. It is not as exciting as writing code.
b. It is not beneficial to all parties to document the problem space.

The second of these may be me being cynical and jaundiced. But it seems to me
that if you have written code and you find that the problem is defined different
from what you have coded this may be unfortunate for you. At one end of the
spectrum it could cost a lot of money; at the other end of the spectrum it is an
attack on someone's baby.

So my question back to Benoit, and rephrasing his question...

If the problem is well understood enough for a working group to be chartered,
why does it take that working group so long to write a tight and clear document
defining the problem?

Cheers,
Adrian


From nobody Mon Apr 28 04:16:46 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 988561A097D for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 04:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A-3AArfnTV_C for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 04:16:42 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 22A111A095F for <wgchairs@ietf.org>; Mon, 28 Apr 2014 04:16:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10536; q=dns/txt; s=iport; t=1398683801; x=1399893401; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=eTOu+TdMZagGNiENWtfQpVJm1X9x3ZjGIDzZhUUnrxM=; b=GQcxDMyOvoK1Jbkz3okKXyzxpNKHU12uoVigKHgSkzrfOp1UZkl0Bm9R Nq4yiG8glvsFZsCjmmcRBqgV2fylwSyyc7N4/rnvHCUx1T0BZ2vEuWZV7 YGbZQEb6fniwGj0sAK7uriX9awM4EsWXXjehg51xI7odpNJ6Vfl11PrmX I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAEE4XlOtJA2H/2dsb2JhbABZgkJEgSbEZ4EPFnSCJQEBAQRuGwIBCBEBAwEBCyQyFwYIAgQBGgyILcoDF44oOIMkgRUEiTeiM4Mxgis
X-IronPort-AV: E=Sophos; i="4.97,943,1389744000"; d="scan'208,217"; a="39323886"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-8.cisco.com with ESMTP; 28 Apr 2014 11:16:41 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3SBGffw030364 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <wgchairs@ietf.org>; Mon, 28 Apr 2014 11:16:41 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Mon, 28 Apr 2014 06:16:40 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
Subject: RE: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpsnC2OA///SP7Y=
Date: Mon, 28 Apr 2014 11:16:39 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040B8C60B2@xmb-rcd-x04.cisco.com>
References: <CF7BF13E.B1AE%repenno@cisco.com>,<535E0E45.9010104@cisco.com>
In-Reply-To: <535E0E45.9010104@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.80.184]
Content-Type: multipart/alternative; boundary="_000_45A697A8FFD7CF48BCF2BE7E106F06040B8C60B2xmbrcdx04ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/ppu38aYS--z045L0gC-OuUYUL7g
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 11:16:44 -0000

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


________________________________
From: Benoit Claise (bclaise)
Sent: Monday, April 28, 2014 1:16 AM
To: Reinaldo Penno (repenno); 'WG Chairs'
Subject: Re: Proposal for Structuring New WGs

Hi Reinaldo,

Hi,

I=B9ve been thinking about how some Wgs get stuck and others loose steam an=
d
would like to propose an optional way to structure new WGs.

I think the delay or failure of many WGs can be attribute as the way we
IETF structures WGs.

When a WG is formed there is lots of energy, many drafts, people with
running code (yes, these people still exist) and great participation. But
then, the IETF step on the brakes by following a cookie cutter approach of
asking for a problem statement draft, some form of architecture draft and
produces, most often than not, a set in stone charter.  This alone makes a
boatload of people leave the WG effort. Some of these folks have even
running code (I=B9ve been there) or drafts that many folks are interested
but can not be discussed until the current charter is done.

Yes, this is a real problem.
While discussing this issue, Spencer Dawkins reminded me of RFC 5434:


   In many cases,
   however, the intent is to form a WG.  In those cases, the goal of the
   BOF is to demonstrate that the community has agreement that:

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

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

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

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

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

Special attention to the third bullet point above.
If the problem is well understood enough for a working group to be chartere=
d, how much more work does a working group need to do, in defining the prob=
lem?

[RP] My answer is none. If the problem space is well understood why do we n=
eed "problem statement" drafts? The charter should suffice and we can hit t=
he ground running. But that is certainly not the case that's why I proposed=
 agile WGs that work around such blocking issues and get work done.

Maybe we should apply this rule in a stricter manner. You wrote "When a WG =
is formed there is lots of energy ",

[RP] I replied to this point to another person. In my view it is a differen=
t kind of energy and priority as I discuss below.

I would observe that when a WG is about to be created (BoF), there is even =
more energy ... to get the WG created. We should really capitalize on it.

[RP] Right, this is key: "to get the WG created". During BOF phase what I n=
otice is that getting the WG formed takes priority over anything, all other=
 issues are brushed aside in the hopes to get the WG formed and getting wor=
k done. I mean, otherwise how come in a BOF we can get 100 people to agree =
on a single set of ideas (really??) and later have endless threads on the l=
ist.

[RP] I do not want to go in a tangent here but asking a huge audience if th=
ey all agree that the scope of problem is well understood and getting no di=
sagreements would be a red flag right there.


Regards, Benoit

And the WG struggles on and on because of the very fact that some of the
folks with energy that could drive the WG will not wait on the sidelines
for 2 years until rechartering so that maybe, just maybe, their draft can
get on the charter.

My proposal is that certain WGs should be formed with some overall charter
and the definite charter should be written _after_ say, two official WG
meetings, where lots of discussion on mailing list and presentations
happen. Then the charter becomes the most important drafts people are
interested. In this case for example, the problem statement becomes in
fact those drafts.

Maybe this is already allowed but it is not known or not encouraged. At
least if possible it would be good to experiment with that approach in
some of the popular or struggling WGs.

Thanks,

-Reinaldo






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

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:=
0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1" bgcolor=3D"#FFFFFF">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;"><br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"direction: ltr;" id=3D"divRpF620563"><font color=3D"#000000" =
face=3D"Tahoma" size=3D"2"><b>From:</b> Benoit Claise (bclaise)<br>
<b>Sent:</b> Monday, April 28, 2014 1:16 AM<br>
<b>To:</b> Reinaldo Penno (repenno); 'WG Chairs'<br>
<b>Subject:</b> Re: Proposal for Structuring New WGs<br>
</font><br>
</div>
<div></div>
<div>
<div class=3D"moz-cite-prefix">Hi Reinaldo,<br>
</div>
<blockquote type=3D"cite">
<pre>Hi,=0A=
=0A=
I=B9ve been thinking about how some Wgs get stuck and others loose steam an=
d=0A=
would like to propose an optional way to structure new WGs.=0A=
=0A=
I think the delay or failure of many WGs can be attribute as the way we=0A=
IETF structures WGs.=0A=
=0A=
When a WG is formed there is lots of energy, many drafts, people with=0A=
running code (yes, these people still exist) and great participation. But=
=0A=
then, the IETF step on the brakes by following a cookie cutter approach of=
=0A=
asking for a problem statement draft, some form of architecture draft and=
=0A=
produces, most often than not, a set in stone charter.  This alone makes a=
=0A=
boatload of people leave the WG effort. Some of these folks have even=0A=
running code (I=B9ve been there) or drafts that many folks are interested=
=0A=
but can not be discussed until the current charter is done.</pre>
</blockquote>
Yes, this is a real problem.<br>
While discussing this issue, Spencer Dawkins reminded me of RFC 5434:<br>
<br>
<pre class=3D"newpage">   In many cases,=0A=
   however, the intent is to form a WG.  In those cases, the goal of the=0A=
   BOF is to demonstrate that the community has agreement that:=0A=
=0A=
      - there is a problem that needs solving, and the IETF is the right=0A=
        group to attempt solving it.=0A=
=0A=
      - there is a critical mass of participants willing to work on the=0A=
        problem (e.g., write drafts, review drafts, etc.).=0A=
=0A=
     <font color=3D"#ff0000"> - the scope of the problem is well defined an=
d understood, that=0A=
        is, people generally understand what the WG will work on (and=0A=
        what it won't) and what its actual deliverables will be.</font>=0A=
=0A=
      - there is agreement that the specific deliverables (i.e.,=0A=
        proposed documents) are the right set.=0A=
=0A=
      - it is believed that the WG has a reasonable probability of=0A=
        having success (i.e., in completing the deliverables in its=0A=
        charter in a timely fashion).</pre>
Special attention to the third bullet point above.<br>
If the problem is well understood enough for a working group to be chartere=
d, how much more work does a working group need to do, in defining the prob=
lem?<br>
<br>
[RP] My answer is none. If the problem space is well understood why do we n=
eed &quot;problem statement&quot; drafts? The charter should suffice and we=
 can hit the ground running. But that is certainly not the case that's why =
I proposed agile WGs that work around such
 blocking issues and get work done.<br>
<br>
Maybe we should apply this rule in a stricter manner. You wrote &quot;When =
a WG is formed there is lots of energy &quot;,
<br>
<br>
[RP] I replied to this point to another person. In my view it is a differen=
t kind of energy and priority as I discuss below.<br>
<br>
I would observe that when a WG is about to be created (BoF), there is even =
more energy ... to get the WG created. We should really capitalize on it.<b=
r>
<br>
[RP] Right, this is key: &quot;to get the WG created&quot;. During BOF phas=
e what I notice is that getting the WG formed takes priority over anything,=
 all other issues are brushed aside in the hopes to get the WG formed and g=
etting work done. I mean, otherwise how come
 in a BOF we can get 100 people to agree on a single set of ideas (really??=
) and later have endless threads on the list.
<br>
<br>
[RP] I do not want to go in a tangent here but asking a huge audience if th=
ey all agree that the scope of problem is well understood and getting no di=
sagreements would be a red flag right there.
<br>
<br>
<br>
Regards, Benoit<br>
<blockquote type=3D"cite">
<pre>And the WG struggles on and on because of the very fact that some of t=
he=0A=
folks with energy that could drive the WG will not wait on the sidelines=0A=
for 2 years until rechartering so that maybe, just maybe, their draft can=
=0A=
get on the charter.=0A=
=0A=
My proposal is that certain WGs should be formed with some overall charter=
=0A=
and the definite charter should be written _after_ say, two official WG=0A=
meetings, where lots of discussion on mailing list and presentations=0A=
happen. Then the charter becomes the most important drafts people are=0A=
interested. In this case for example, the problem statement becomes in=0A=
fact those drafts. =0A=
=0A=
Maybe this is already allowed but it is not known or not encouraged. At=0A=
least if possible it would be good to experiment with that approach in=0A=
some of the popular or struggling WGs.=0A=
=0A=
Thanks,=0A=
=0A=
-Reinaldo=0A=
=0A=
=0A=
=0A=
</pre>
</blockquote>
<br>
</div>
</div>
</div>
</body>
</html>

--_000_45A697A8FFD7CF48BCF2BE7E106F06040B8C60B2xmbrcdx04ciscoc_--


From nobody Mon Apr 28 05:58:22 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0150A1A078F for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 05:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.151
X-Spam-Level: 
X-Spam-Status: No, score=-10.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uaASzOVdBddS for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 05:58:18 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBFC1A047C for <wgchairs@ietf.org>; Mon, 28 Apr 2014 05:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10066; q=dns/txt; s=iport; t=1398689897; x=1399899497; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=2TtfvojDjBiFuhbZg8HVdMqkxxDGpvQsC62K2ETjEN0=; b=TsL9DNqDlLk1p3y3V9+BwVrAERc8lHkJcLtQW93aNn1BF5GGlFapgos/ 68JiwVW+pTPmECmWwKRz8CmqzgnEsuR+gerqZoUhwofv1sLgSzieyNc1p AHf3+ld2cS4TQvHpcfyXMadRvdUDqjhyfSOkuC6q3XypwmigIoWJOCOeX U=;
X-IronPort-AV: E=Sophos; i="4.97,944,1389744000"; d="scan'208,217"; a="25754663"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 28 Apr 2014 12:58:16 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3SCwGU2032546; Mon, 28 Apr 2014 12:58:16 GMT
Message-ID: <535E5068.308@cisco.com>
Date: Mon, 28 Apr 2014 14:58:16 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Reinaldo Penno (repenno)'" <repenno@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
Subject: Re: Proposal for Structuring New WGs
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com> <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
In-Reply-To: <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------060300000208010300050805"
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/OeaNeakLw9hByN9DxVj_WDd1u5k
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 12:58:20 -0000

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

On 28/04/2014 11:32, Adrian Farrel wrote:
> Hi Benoit,
>
> Thanks for flagging this piece of text...
>
>>> - the scope of the problem is well defined and understood, that
>>>     is, people generally understand what the WG will work on (and
>>>     what it won't) and what its actual deliverables will be.
> You said...
>
>> If the problem is well understood enough for a working group to be
>> chartered, how much more work does a working group need to do,
>> in defining the problem?
> I have seen a number of cases recently where the problem was *not* well enough
> understood to charter a working group. True, if you stopped any one person in
> the corridor, they might have said that *they* understood the problem well
> enough, but it was clear to me in these cases that there was not even a rough
> consensus of agreement of understanding of the problem.
>
> In these cases there are three option:
> 1. Say no. Ask for more work agreeing the problem and hold
>     another BoF later.
> 2. Form a WG to work to agree on the problem and recharter
>     later.
> 3. Take a punt. Form the WG to do real, solutions work.
>
> I have seen the third of these go horribly wrong: many people developing
> different solutions in the same space to do subtly different and conflicting
> things.
>
> The first option, on the other hand, seems to be more blocking of progress than
> the second option, and so I tend to adopt the second option. That option brings
> the work into the IETF, but requires that effort is expended developing the
> problem space and scoping the solutions space.
>
> So, when Reinaldo bemoans that:
>
>> the IETF step on the brakes by following a cookie cutter approach of
>> asking for a problem statement draft, some form of architecture draft and
>> produces, most often than not, a set in stone charter.
> I find that this is often a necessary step that has been "borrowed" from the BoF
> process. That is, it is legacy work that should have been done before the WG was
> formed, but which we have decided to let slip until after the WG has been
> formed. We have chosen to form the WG because it is clear that we have a topic
> that has significant interest and is in scope for the IETF, but we also
> recognise that the problem is not well-defined or understood.
>
> But where I am repeatedly frustrated is the length of time the WG spends in this
> state. If, as is widely claimed, the problem *is* well understood to the extent
> that running code exists, I do not understand why it takes multiple IETF cycles,
> and often multiple years, to document the problem.  If so many people are
> interested and working in the space, why is none of them capable of writing a 20
> page document that clearly and concisely describes the problem? If there is a
> space where many people are writing code, why is it so hard to get consensus on
> the problem statement?
>
> No, I know two answers to my questions both predicated on the assumption that
> writing a short document is not problem statement:
>
> a. It is not as exciting as writing code.
> b. It is not beneficial to all parties to document the problem space.
>
> The second of these may be me being cynical and jaundiced. But it seems to me
> that if you have written code and you find that the problem is defined different
> from what you have coded this may be unfortunate for you. At one end of the
> spectrum it could cost a lot of money; at the other end of the spectrum it is an
> attack on someone's baby.
>
> So my question back to Benoit, and rephrasing his question...
>
> If the problem is well understood enough for a working group to be chartered,
> why does it take that working group so long to write a tight and clear document
> defining the problem?
Because once the WG is created, it's more fun to design a solution than 
to document the problem statement.

Let's go back to your 3 categories:

    1. Say no. Ask for more work agreeing the problem and hold
        another BoF later.
    2. Form a WG to work to agree on the problem and recharter
        later.
    3. Take a punt. Form the WG to do real, solutions work.


All 3 are viable options.
For category 2, I'm now in favor of adding in the charter: if the WG 
can't agree upon a problem statement by date D, it will be closed

Regards, Benoit
>
> Cheers,
> Adrian
>
> .
>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 28/04/2014 11:32, Adrian Farrel
      wrote:<br>
    </div>
    <blockquote cite="mid:01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk"
      type="cite">
      <pre wrap="">Hi Benoit,

Thanks for flagging this piece of text...

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">- the scope of the problem is well defined and understood, that
   is, people generally understand what the WG will work on (and
   what it won't) and what its actual deliverables will be.
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
You said...

</pre>
      <blockquote type="cite">
        <pre wrap="">If the problem is well understood enough for a working group to be
chartered, how much more work does a working group need to do,
in defining the problem?
</pre>
      </blockquote>
      <pre wrap="">
I have seen a number of cases recently where the problem was *not* well enough
understood to charter a working group. True, if you stopped any one person in
the corridor, they might have said that *they* understood the problem well
enough, but it was clear to me in these cases that there was not even a rough
consensus of agreement of understanding of the problem.

In these cases there are three option:
1. Say no. Ask for more work agreeing the problem and hold
   another BoF later.
2. Form a WG to work to agree on the problem and recharter
   later.
3. Take a punt. Form the WG to do real, solutions work. 

I have seen the third of these go horribly wrong: many people developing
different solutions in the same space to do subtly different and conflicting
things.

The first option, on the other hand, seems to be more blocking of progress than
the second option, and so I tend to adopt the second option. That option brings
the work into the IETF, but requires that effort is expended developing the
problem space and scoping the solutions space.

So, when Reinaldo bemoans that:

</pre>
      <blockquote type="cite">
        <pre wrap="">the IETF step on the brakes by following a cookie cutter approach of
asking for a problem statement draft, some form of architecture draft and
produces, most often than not, a set in stone charter.
</pre>
      </blockquote>
      <pre wrap="">
I find that this is often a necessary step that has been "borrowed" from the BoF
process. That is, it is legacy work that should have been done before the WG was
formed, but which we have decided to let slip until after the WG has been
formed. We have chosen to form the WG because it is clear that we have a topic
that has significant interest and is in scope for the IETF, but we also
recognise that the problem is not well-defined or understood.

But where I am repeatedly frustrated is the length of time the WG spends in this
state. If, as is widely claimed, the problem *is* well understood to the extent
that running code exists, I do not understand why it takes multiple IETF cycles,
and often multiple years, to document the problem.  If so many people are
interested and working in the space, why is none of them capable of writing a 20
page document that clearly and concisely describes the problem? If there is a
space where many people are writing code, why is it so hard to get consensus on
the problem statement?

No, I know two answers to my questions both predicated on the assumption that
writing a short document is not problem statement:

a. It is not as exciting as writing code.
b. It is not beneficial to all parties to document the problem space.

The second of these may be me being cynical and jaundiced. But it seems to me
that if you have written code and you find that the problem is defined different
from what you have coded this may be unfortunate for you. At one end of the
spectrum it could cost a lot of money; at the other end of the spectrum it is an
attack on someone's baby.

So my question back to Benoit, and rephrasing his question...

If the problem is well understood enough for a working group to be chartered,
why does it take that working group so long to write a tight and clear document
defining the problem?</pre>
    </blockquote>
    Because once the WG is created, it's more fun to design a solution
    than to document the problem statement.<br>
    <br>
    Let's go back to your 3 categories:<br>
    <blockquote>
      <pre wrap="">1. Say no. Ask for more work agreeing the problem and hold
   another BoF later.
2. Form a WG to work to agree on the problem and recharter
   later.
3. Take a punt. Form the WG to do real, solutions work. </pre>
    </blockquote>
    <br>
    All 3 are viable options.<br>
    For category 2, I'm now in favor of adding in the charter: if the WG
    can't agree upon a problem statement by date D, it will be closed<br>
    <br>
    Regards, Benoit<br>
    <blockquote cite="mid:01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk"
      type="cite">
      <pre wrap="">

Cheers,
Adrian

.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060300000208010300050805--


From nobody Mon Apr 28 06:44:38 2014
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D847D1A0A1D for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 06:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level: 
X-Spam-Status: No, score=-4.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVSBZ9j4rr6C for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 06:44:26 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 5838C1A0A1A for <wgchairs@ietf.org>; Mon, 28 Apr 2014 06:44:26 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SDiJAH023867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 09:44:22 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s3SDiJAH023867
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398692662; bh=g/QY5SWsh9GuS8MmWkTxQqFY7Ac=; h=From:To:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=rbY2YSYS0NYJgeqTwws0K0pNiY+AOXtTr3fqHi2/4Be1sC60NDjR5KphnqwPaO1Zn d69XiuU4qkpZ4A9ZMJOgrT8RtCzUNZpBrx+dI6x7b/9KpHs2nBDxM0Jf+37fLkLk2U /qPIWBzh7RD1AWiubrR9NTEfG6v+DIRnvl9N8q7Q=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s3SDiJAH023867
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd55.lss.emc.com (RSA Interceptor); Mon, 28 Apr 2014 09:44:10 -0400
Received: from mxhub39.corp.emc.com (mxhub39.corp.emc.com [128.222.70.106]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SDi8LD004349 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 09:44:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub39.corp.emc.com ([128.222.70.106]) with mapi; Mon, 28 Apr 2014 09:42:52 -0400
From: "Black, David" <david.black@emc.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Reinaldo Penno (repenno)'" <repenno@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
Date: Mon, 28 Apr 2014 09:44:09 -0400
Subject: RE: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQKoR+6uePXZvSV93DO03hjwwBAGYwEbvwYJmWwSxPCAAErWcA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2ECF7C@MX15A.corp.emc.com>
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com> <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
In-Reply-To: <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/PsL5zU9f4n7cKsPunklcPPHOMzc
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 13:44:30 -0000

Selective excerpts from Adrian's note ...

> 2. Form a WG to work to agree on the problem and recharter later.

> The first option, on the other hand, seems to be more blocking of progres=
s than
> the second option, and so I tend to adopt the second option. That option =
brings
> the work into the IETF, but requires that effort is expended developing t=
he
> problem space and scoping the solutions space.

> But where I am repeatedly frustrated is the length of time the WG spends =
in this
> state. If, as is widely claimed, the problem *is* well understood to the =
extent
> that running code exists, I do not understand why it takes multiple IETF =
cycles,
> and often multiple years, to document the problem.  If so many people are
> interested and working in the space, why is none of them capable of writi=
ng a 20
> page document that clearly and concisely describes the problem? If there =
is a
> space where many people are writing code, why is it so hard to get consen=
sus on
> the problem statement?

I know of at least one case, with which Adrian is quite familiar ;-), where
there's a good 20/20 hindsight case to be made that the new WG was asked to
merge two problems into one - I still have some of the scars from what it t=
ook
to write the resulting problem statement (which is now at the RFC Editor).

NB: hindsight is always 20/20; the hard part is making the decision w/o tha=
t.
IMHO, the approach of trying to do all of the problem unscrambling/clarific=
ation
in one WG seemed like a plausible idea at the time ...
... and there had been some even broader prior BoFs and non-BoFs.

Thanks,
--David (an author of more than one WG problem statement doc)

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Adrian Far=
rel
> Sent: Monday, April 28, 2014 5:32 AM
> To: 'Benoit Claise'; 'Reinaldo Penno (repenno)'; 'WG Chairs'
> Subject: RE: Proposal for Structuring New WGs
>=20
> Hi Benoit,
>=20
> Thanks for flagging this piece of text...
>=20
> >> - the scope of the problem is well defined and understood, that
> >>    is, people generally understand what the WG will work on (and
> >>    what it won't) and what its actual deliverables will be.
>=20
> You said...
>=20
> > If the problem is well understood enough for a working group to be
> > chartered, how much more work does a working group need to do,
> > in defining the problem?
>=20
> I have seen a number of cases recently where the problem was *not* well e=
nough
> understood to charter a working group. True, if you stopped any one perso=
n in
> the corridor, they might have said that *they* understood the problem wel=
l
> enough, but it was clear to me in these cases that there was not even a r=
ough
> consensus of agreement of understanding of the problem.
>=20
> In these cases there are three option:
> 1. Say no. Ask for more work agreeing the problem and hold
>    another BoF later.
> 2. Form a WG to work to agree on the problem and recharter
>    later.
> 3. Take a punt. Form the WG to do real, solutions work.
>=20
> I have seen the third of these go horribly wrong: many people developing
> different solutions in the same space to do subtly different and conflict=
ing
> things.
>=20
> The first option, on the other hand, seems to be more blocking of progres=
s
> than
> the second option, and so I tend to adopt the second option. That option
> brings
> the work into the IETF, but requires that effort is expended developing t=
he
> problem space and scoping the solutions space.
>=20
> So, when Reinaldo bemoans that:
>=20
> > the IETF step on the brakes by following a cookie cutter approach of
> > asking for a problem statement draft, some form of architecture draft a=
nd
> > produces, most often than not, a set in stone charter.
>=20
> I find that this is often a necessary step that has been "borrowed" from =
the
> BoF
> process. That is, it is legacy work that should have been done before the=
 WG
> was
> formed, but which we have decided to let slip until after the WG has been
> formed. We have chosen to form the WG because it is clear that we have a =
topic
> that has significant interest and is in scope for the IETF, but we also
> recognise that the problem is not well-defined or understood.
>=20
> But where I am repeatedly frustrated is the length of time the WG spends =
in
> this
> state. If, as is widely claimed, the problem *is* well understood to the
> extent
> that running code exists, I do not understand why it takes multiple IETF
> cycles,
> and often multiple years, to document the problem.  If so many people are
> interested and working in the space, why is none of them capable of writi=
ng a
> 20
> page document that clearly and concisely describes the problem? If there =
is a
> space where many people are writing code, why is it so hard to get consen=
sus
> on
> the problem statement?
>=20
> No, I know two answers to my questions both predicated on the assumption =
that
> writing a short document is not problem statement:
>=20
> a. It is not as exciting as writing code.
> b. It is not beneficial to all parties to document the problem space.
>=20
> The second of these may be me being cynical and jaundiced. But it seems t=
o me
> that if you have written code and you find that the problem is defined
> different
> from what you have coded this may be unfortunate for you. At one end of t=
he
> spectrum it could cost a lot of money; at the other end of the spectrum i=
t is
> an
> attack on someone's baby.
>=20
> So my question back to Benoit, and rephrasing his question...
>=20
> If the problem is well understood enough for a working group to be charte=
red,
> why does it take that working group so long to write a tight and clear
> document
> defining the problem?
>=20
> Cheers,
> Adrian
>=20


From nobody Mon Apr 28 06:53:15 2014
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172E01A0A13 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 06:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQUiXPERhG1Q for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 06:53:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 8F26C1A015E for <wgchairs@ietf.org>; Mon, 28 Apr 2014 06:53:09 -0700 (PDT)
Received: from [192.168.131.128] ([80.92.122.106]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MSMKx-1WTSOS1zUx-00TVxe; Mon, 28 Apr 2014 15:53:03 +0200
Message-ID: <535E5C51.3060903@gmx.net>
Date: Mon, 28 Apr 2014 15:49:05 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Benoit Claise' <bclaise@cisco.com>,  "'Reinaldo Penno (repenno)'" <repenno@cisco.com>, 'WG Chairs' <wgchairs@ietf.org>
Subject: Re: Proposal for Structuring New WGs
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com> <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
In-Reply-To: <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="9lHUCsG9BxTdC5T3JBgohCR3J3iaBu0Ie"
X-Provags-ID: V03:K0:k4rxTqQ7nfYLKGMJ2Cgrt4ON6BwrqOw2o6ELlBApaKhJiltzj6Z 7F0wX+nr4pPJ/ztQtZ3LIedS53QK478I4/lgMJJcLusJ/LLpJdYU0A1Mpyo5a+4L5lPL+fe kzFepdC0qZzwOje7a5e81T48Cde6b/dQCeX9r73gSG8MG7wMZm8M/7N53Nmgt//0/xoNYR3 hqcJ3QXQUmYUX+EURyalg==
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/qfxRJLuH19fvyhgwWJipvP2ntwA
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 13:53:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9lHUCsG9BxTdC5T3JBgohCR3J3iaBu0Ie
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

My problem with these discussions is that they tend to be very abstract.
Hence, it is difficult to draw a useful conclusion from the discussion
other than everyone has their unique experience with a number of groups.

On 04/28/2014 11:32 AM, Adrian Farrel wrote:
> Hi Benoit,
>=20
> Thanks for flagging this piece of text...
>=20
>>> - the scope of the problem is well defined and understood, that
>>>    is, people generally understand what the WG will work on (and
>>>    what it won't) and what its actual deliverables will be.
>=20
> You said...
>=20
>> If the problem is well understood enough for a working group to be
>> chartered, how much more work does a working group need to do,
>> in defining the problem?
>=20
> I have seen a number of cases recently where the problem was *not* well=
 enough
> understood to charter a working group. True, if you stopped any one per=
son in
> the corridor, they might have said that *they* understood the problem w=
ell
> enough, but it was clear to me in these cases that there was not even a=
 rough
> consensus of agreement of understanding of the problem.
>=20
> In these cases there are three option:
> 1. Say no. Ask for more work agreeing the problem and hold
>    another BoF later.
> 2. Form a WG to work to agree on the problem and recharter
>    later.
> 3. Take a punt. Form the WG to do real, solutions work.=20
>=20
> I have seen the third of these go horribly wrong: many people developin=
g
> different solutions in the same space to do subtly different and confli=
cting
> things.
>=20
> The first option, on the other hand, seems to be more blocking of progr=
ess than
> the second option, and so I tend to adopt the second option. That optio=
n brings
> the work into the IETF, but requires that effort is expended developing=
 the
> problem space and scoping the solutions space.
>=20
> So, when Reinaldo bemoans that:
>=20
>> the IETF step on the brakes by following a cookie cutter approach of
>> asking for a problem statement draft, some form of architecture draft =
and
>> produces, most often than not, a set in stone charter.
>=20
> I find that this is often a necessary step that has been "borrowed" fro=
m the BoF
> process. That is, it is legacy work that should have been done before t=
he WG was
> formed, but which we have decided to let slip until after the WG has be=
en
> formed. We have chosen to form the WG because it is clear that we have =
a topic
> that has significant interest and is in scope for the IETF, but we also=

> recognise that the problem is not well-defined or understood.
>=20
> But where I am repeatedly frustrated is the length of time the WG spend=
s in this
> state. If, as is widely claimed, the problem *is* well understood to th=
e extent
> that running code exists, I do not understand why it takes multiple IET=
F cycles,
> and often multiple years, to document the problem.  If so many people a=
re
> interested and working in the space, why is none of them capable of wri=
ting a 20
> page document that clearly and concisely describes the problem? If ther=
e is a
> space where many people are writing code, why is it so hard to get cons=
ensus on
> the problem statement?
>=20
> No, I know two answers to my questions both predicated on the assumptio=
n that
> writing a short document is not problem statement:
>=20
> a. It is not as exciting as writing code.
> b. It is not beneficial to all parties to document the problem space.
>=20
> The second of these may be me being cynical and jaundiced. But it seems=
 to me
> that if you have written code and you find that the problem is defined =
different
> from what you have coded this may be unfortunate for you. At one end of=
 the
> spectrum it could cost a lot of money; at the other end of the spectrum=
 it is an
> attack on someone's baby.
>=20
> So my question back to Benoit, and rephrasing his question...
>=20
> If the problem is well understood enough for a working group to be char=
tered,
> why does it take that working group so long to write a tight and clear =
document
> defining the problem?
>=20
> Cheers,
> Adrian
>=20


--9lHUCsG9BxTdC5T3JBgohCR3J3iaBu0Ie
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTXlxRAAoJEGhJURNOOiAt/b8IAJ7Ccdw26TpWr35JCN6YPL6s
W/bGB82PRrnhKa/CEzTNIGesmI0pW9zgme90CNPQif+ciU05f0ctTQoicZocIE5v
qqkCHla8ntbTsVqojjtExKJg8rQ5dNA0SqfaYcgpz9ZDDoR5++LGd+yb0mFUw+eG
8ucwunD5mhi57fO2CoLfx7c2g/5PedS3xDRqXt1S/W3Bxd+2nbJmpC5T6rQ7HdHE
Go/HsYLqRGWQpAvH9bohu5O2YLDRfaVHaVga1CJ9KH0iG2u50Pzpgmf6w/aauvln
IE73TO1NUWN/9G5taHz6l4YmKDNrzU38f05lpCDMzVvohlO0emvkLKBbojKoE8Q=
=hH3D
-----END PGP SIGNATURE-----

--9lHUCsG9BxTdC5T3JBgohCR3J3iaBu0Ie--


From nobody Mon Apr 28 07:25:51 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162941A0983 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 07:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ezzzgMoaNIE for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 07:25:47 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3059C1A0A27 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 07:25:47 -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 s3SEPe70024091; Mon, 28 Apr 2014 15:25:41 +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 s3SEPcEo024044 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Apr 2014 15:25:38 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Hannes Tschofenig'" <hannes.tschofenig@gmx.net>, "'Benoit Claise'" <bclaise@cisco.com>, "'Reinaldo Penno \(repenno\)'" <repenno@cisco.com>, "'WG Chairs'" <wgchairs@ietf.org>
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com> <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk> <535E5C51.3060903@gmx.net>
In-Reply-To: <535E5C51.3060903@gmx.net>
Subject: RE: Proposal for Structuring New WGs
Date: Mon, 28 Apr 2014 15:25:35 +0100
Message-ID: <02ac01cf62ed$b9ee7f20$2dcb7d60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKoR+6uePXZvSV93DO03hjwwBAGYwEbvwYJApJSh4cCJz+RqJlGnZsQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20662.000
X-TM-AS-Result: No--15.591-10.0-31-10
X-imss-scan-details: No--15.591-10.0-31-10
X-TMASE-MatchedRID: vEvJ7Rh1lGgkzrQfI6wWyPHkpkyUphL90i/hFXziUdNq4coTktrGX+DH q5tSm72eKnU6PabtYtkldfX71wfl0WDsPG/Srtq1kX71Hy/ufOaHxi2fvkKUM9Q7R95qD2m5B0r kv3k6oVFnkcvraRIj5VBi+V5Q8p6TJol1F8fRTeVHFWsq1vzd1BbZsplSG8S6cVdapPIqr6j8XU Gt5rtvIr87f9xnS/26mcpj1PqVhGd+dq81W9lAv34f9De+CyQCzVE3gQTykCprMbakJN8OefU72 nYVxvYNgfI0Z1PHf6Q2WW7gEIXLDfD+AX9A5zEbVP9jNEQH04rvJY9pBzgg1AKPvjSCRzuuilvA b18i4hM9xaH1eNTuN7ZMGUUyuIF5sL7meEdr9ozpnOP6QxEGtn0tCKdnhB58vqq8s2MNhPB9j2G wzTE3vSq2rl3dzGQ1A/3R8k/14e0=
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Won4Z178thjnUY8EXigCXYwjyjE
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 28 Apr 2014 14:25:50 -0000

> My problem with these discussions is that they tend to be very abstract.
> Hence, it is difficult to draw a useful conclusion from the discussion
> other than everyone has their unique experience with a number of groups.

Yeah, life is hard, isn't it?
I don't like using individual people's screw-ups (even my own) as examples in
public debate.

But let's look at ACE.

It has been obvious since before the ACE working group was started at the
beginning of December last year, that there was a group of people very
determined to work in this area. A BoF was held in London. More work was needed
to refine the problem statement and the area of work.

Now (end of April and so five months on) there is a draft charter (quite
lengthy) that still needs review and discussion. The charter includes a lot of
text that scopes the problem, but still includes the first deliverable (of a
total of two) as "Produce use cases and requirements."  It is clear to me,
therefore, that some aspects of the problem statement are captured in the
charter text, but that there is not sufficient consensus and agreement on the
problem statement to move straight to solutions work.

If I was a developer writing security code for applications in constrained
environments, would I feel annoyed that the IETF was still fiddling with this
and not moving ahead faster? Working with my team of developers or my online
community, I could write a lot of code in five months. And it will presumably be
more months before the working group (if formed) get around to adopting
solutions documents.

As it happens, I think the ACE community has done the right thing. I might wish
they had done it faster and more focussed, but that was clearly their choice and
not the influence of the wider IETF community. And that is my broader point...

Stated with more bluntness than is likely to be good for me: When people
complain that the IETF is slow to adopt work or slow to publish work, have those
people actually been contributing constructively to the consensus process? Have
they contributed text? Or were they part of the problem?

Cheers,
Adrian


From nobody Mon Apr 28 07:26:44 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98ED71A047E for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 07:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4T-miQlSOlL for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 07:26:39 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id E697F1A0983 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 07:26:38 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id uz6so7424171obc.0 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 07:26:38 -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=a7lZlfd6tEwT5qVJFBCeZLptLvBjbrjkPcZLbVVW6Js=; b=R6qhtF2IOUAvHxptvFJtI4XubWnhGJ0X3WlniwUwmrh/hIDcWIn7NQC7hRk0ya9Xyt vDBEYLZHpBAIc7Ua63kkNSzVCwxoad5THB/0IKetxsznefD7dh7PlJhMtU8oFFuyuw3a Ors3U5H1CnB1rsp8sCNvL0Pf7fseN0MsFHE2J16lkIC7kGUoa2YW+2/q0dmxHIi8j6h0 n39/IhnbO8mJOI6lpyguOCfI7sftTzJL97RzFYVz6a//nqubQ69Vv2ri5UZGjoc27n6A osXFg5w3glV37+6/NUXedeuCojGDt0B7cqT08wlW10Ot2knoL9Mz2yVFuUTBfmHyWK5v fbWA==
X-Received: by 10.182.33.99 with SMTP id q3mr22779574obi.33.1398695198098; Mon, 28 Apr 2014 07:26:38 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id dh8sm74151093oeb.10.2014.04.28.07.26.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Apr 2014 07:26:37 -0700 (PDT)
Message-ID: <535E651B.5000202@gmail.com>
Date: Mon, 28 Apr 2014 09:26:35 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>, wgchairs@ietf.org
Subject: Re: Proposal for Structuring New WGs
References: <CF7BF13E.B1AE%repenno@cisco.com> <17962.1398264732@sandelman.ca> <CAHBDyN70B84PWv7k-6n+nYresJwZ7VRR7vYXg8iWTh3a19WvOw@mail.gmail.com> <29478.1398286452@sandelman.ca> <535B6D9C.4010506@pi.nu>
In-Reply-To: <535B6D9C.4010506@pi.nu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/B8xIm5_UGlPeJ8MCht7NPyu0Fxo
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 14:26:41 -0000

On 04/26/2014 03:26 AM, Loa Andersson wrote:
> Folks,
>
> What is the driver behind this i there a wildly felt need to for
> giving each and every working the same structure?

Speaking only for myself, when I feel wild needs, it's pretty much never 
this one :D

More seriously, and I'm conjecturing, I suspect that this is a 
combination of people cloning what worked in previous WG charter efforts 
and people who are active in other SDOs cloning what other SDOs do in 
the IETF.

I don't know what other ADs tell their BOF requestors, but most of the 
BOF requests I see propose a charter that includes the investigation-ish 
sort of documents.

Spencer

> /Loa
>
> On 2014-04-23 22:54, Michael Richardson wrote:
>>
>> Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
>>      > [MB] There's absolutely nothing in the current model to 
>> prevent WG chairs from
>>      > doing more detailed project planning.  I don't think we need a 
>> process in place
>>      > as the task can be straightforward for some WGs. And, chairs are
>>      > totally free
>>
>> I'm not suggesting any process changes, but rather a reference
>> design/template/running code of a more agile/iterative charter + 
>> milestones.
>> Something that has been pre-reviewed by I* types.
>>
>> -- 
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>   -= IPv6 IoT consulting =-
>>
>>
>>
>


From nobody Mon Apr 28 09:26:54 2014
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399A91A0943 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 09:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBjl4sYbGhwC for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 09:26:50 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA871A6F61 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 09:26:50 -0700 (PDT)
Received: from [2a01:3f0:1:0:8df3:7798:9606:f3d] (port=56759 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1WeoOD-0008Dq-TZ; Mon, 28 Apr 2014 18:26:46 +0200
Message-ID: <535E8145.6000709@levkowetz.com>
Date: Mon, 28 Apr 2014 18:26:45 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>, wgchairs@ietf.org
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535DDCAD.4040604@gmail.com>
In-Reply-To: <535DDCAD.4040604@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:8df3:7798:9606:f3d
X-SA-Exim-Rcpt-To: jouni.nospam@gmail.com, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); Unknown failure
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/KXflYxJJQpoOaRC31YFgjDNeuoA
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 16:26:53 -0000

Hi Jouni,

On 2014-04-28 06:44 Jouni Korhonen said:
> 
> I managed to successfully schedule my WGs (dime, radext, dmm). However, 
> I had to go back to do edits to some of the schedulings but clicking 
> "edit" on WG Chair Dashboard results in an internal server error. Anyone 
> else experienced the same?

This was an error in the permissions checking for one particular path in
to the edit view.  I've patched it to behave as intended, and it works
for me when I go to /secr/sreq/mip4/edit/ as mip4 chair.  Could you check
if it works for you now, please?


Best regards,
	
	Henrik

> 
> - Jouni
> 
> 
> 
> 4/22/2014 1:24 AM, IETF Agenda kirjoitti:
>>
>> -----------------------------------------------------------------
>> 90th IETF – Toronto, ON, Canada
>> Meeting Dates: July 20 - 25, 2014
>> -----------------------------------------------------------------
>>
>> We are accepting scheduling requests for all Working Groups, BOFs, and Research Groups starting today.
>>
>> NOTE: Please ensure your list of conflicts is complete and up to date prior to submitting your session request.
>>
>> The milestones and deadlines for scheduling-related activities are as follows:
>> Cut-off dates are subject to change.
>>
>> •	2014-04-21 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool.
>> •	2014-06-06 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool.
>> •	2014-06-06 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
>> •	2014-06-13 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
>> •	2014-06-20 (Friday): Preliminary agenda published for comment.
>> •	2014-06-23 (Monday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
>> •	2014-06-27 (Friday): Final agenda to be published.
>> •	2014-07-07 (Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>> •	2014-07-14 (Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>> •	2014-08-15 (Friday): Proceedings submission cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>> •	2014-09-05 (Friday): Proceedings submission corrections cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>>
> 
> 


From nobody Mon Apr 28 10:33:28 2014
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AB51A6FAD for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Level: 
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wQLMQdDkcXY for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:33:26 -0700 (PDT)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by ietfa.amsl.com (Postfix) with ESMTP id DDEA71A6F8E for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:33:25 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id u57so3483742wes.13 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:33:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=LAUSR0ylr8gDaXZC34QL1w0hPxPyamdkMVHsmpk2usk=; b=P1J+e6wfycp1syi/janJGKODiOGIHjNG0uLutYFHXb3QCM6vrahIcpqK3OXIYNs5Iz Hmon84y6pV7nX1TZ6kVK0wDVjEZWLCu9+x0r6aE2gtpwyEmERyHgRW+74Z/rJw/pwQVA 7nW3PgjSqm6wgKU/myJ40y/VG1g6Fzwjip5K1aqNFq36DQYm4tp/9KqGe7ifPYjdQbV8 vUbyeRFrRxJKl2E+oXJQkLPSIhKV/sY1Nlp5w0rMttTHfy1XD5JPpPpQ00qcTPRvP13S s863lfcec1mQiTH7M3IzDnntt8AMIE2iNWvU7YWtu5daVJmGvitHylINSPtbUJe5cff9 uw4Q==
X-Gm-Message-State: ALoCoQnbTY3HyZeqh44o8kg4gq/IxwVEkpQ1XMMIVtUM7ur0qImRkpFX6YckmqWPm+JH2/b3D6jZ
MIME-Version: 1.0
X-Received: by 10.181.5.6 with SMTP id ci6mr16434534wid.39.1398706404631; Mon, 28 Apr 2014 10:33:24 -0700 (PDT)
Received: by 10.194.54.162 with HTTP; Mon, 28 Apr 2014 10:33:24 -0700 (PDT)
X-Originating-IP: [98.244.98.35]
Date: Mon, 28 Apr 2014 13:33:24 -0400
Message-ID: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com>
Subject: How many folk were there at my WG meeting?
From: Warren Kumari <warren@kumari.net>
To: WG Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/c3HuEfH6EBb-gQy2U595WT1kOpM
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:33:27 -0000

Hi there,

So, I just went along to request a session in Toronto.
I clicked the "Retrieve info from last session" button (great addition).
Apparently in London I requested a room for 75 people -- great!

Unfortunately, the room was overflowing, folk were sitting on the
floor, standing, etc., so obviously I should request a larger room --
but how many folk were there? 100? 200? 76?

Everyone^w Most signed the bluesheets, but I either:
A: the end of the meeting was a blur / deer in the headlights and / or
B: my co-chair took them and dropped them off at the secretariat.
and so have no idea how many attendees there actually were.

It would be (IMO) very helpful if the secretariat could post the
number of folk who signed the bluesheets (each line is numbered,
simply add up the rows filled from each) in the datatracker tool.
That way when scheduling a meeting the tool could say "Last time you
requested space for 75 people, only 6 showed up", or "Last time you
requested 50, 127 folk signed the sheets".

This would allow us to better decide how much space to request...

Thoughts?
W


From nobody Mon Apr 28 10:36:55 2014
Return-Path: <sandy@tislabs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481DE1A6F8E for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3UdRfAeEIA2s for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:36:53 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id E77381A0515 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:36:52 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 4121D28B003A; Mon, 28 Apr 2014 13:36:52 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 3DB521F8036; Mon, 28 Apr 2014 13:36:52 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Proposal for Structuring New WGs
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
Date: Mon, 28 Apr 2014 13:36:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <37962B10-A83C-42FC-9E9A-3B3BA88B6CAB@tislabs.com>
References: <CF7BF13E.B1AE%repenno@cisco.com> <535E0E45.9010104@cisco.com> <01eb01cf62c4$c6e37060$54aa5120$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/pAp7_nrNazMtD8Qo2yLqdCd2yHg
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:36:54 -0000

On Apr 28, 2014, at 5:32 AM, "Adrian Farrel" <adrian@olddog.co.uk> =
wrote:

> If the problem is well understood enough for a working group to be =
chartered,
> why does it take that working group so long to write a tight and clear =
document
> defining the problem?

My answers (related):

Abstraction is hard for humans.  A definition is an abstraction of the =
important attributes of a problem, and hence hard.

Writing is hard for humans.  I read someone's quote once that writing =
was the greatest spur to clear thinking.(*)  So the process of trying to =
write a description of the problem exposes any fuzzy thinking.  (I used =
to think that one thought clearly, and then one wrote clearly.  But I've =
experienced the feedback process myself.)

This is hard for one human and mutiplicatively hard for multiple humans =
in collaboration.

--Sandy

(*)Don't know my original source. Quick web search yields lots of =
similar comments. On Writing Well by William Zinsser, among many others. =
=20=


From nobody Mon Apr 28 10:44:46 2014
Return-Path: <sbanks@akamai.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7681A0515 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAUd4jb9P-Yl for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:44:43 -0700 (PDT)
Received: from prod-mail-xrelay08.akamai.com (prod-mail-xrelay08.akamai.com [96.6.114.112]) by ietfa.amsl.com (Postfix) with ESMTP id CDF061A6F60 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:44:43 -0700 (PDT)
Received: from prod-mail-xrelay08.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id D8885481C3; Mon, 28 Apr 2014 17:44:42 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (prod-mail-relay03.akamai.com [172.27.8.26]) by prod-mail-xrelay08.akamai.com (Postfix) with ESMTP id C75B6481C9; Mon, 28 Apr 2014 17:44:42 +0000 (GMT)
Received: from ustx2ex-cashub.dfw01.corp.akamai.com (ustx2ex-cashub7.dfw01.corp.akamai.com [172.27.25.73]) by prod-mail-relay03.akamai.com (Postfix) with ESMTP id C39CD2FD61; Mon, 28 Apr 2014 17:44:42 +0000 (GMT)
Received: from USMBX2.msg.corp.akamai.com ([169.254.1.44]) by ustx2ex-cashub7.dfw01.corp.akamai.com ([172.27.25.73]) with mapi; Mon, 28 Apr 2014 12:44:42 -0500
From: "Banks, Sarah" <sbanks@akamai.com>
To: Warren Kumari <warren@kumari.net>, WG Chairs <wgchairs@ietf.org>
Date: Mon, 28 Apr 2014 12:44:56 -0500
Subject: Re: How many folk were there at my WG meeting?
Thread-Topic: How many folk were there at my WG meeting?
Thread-Index: Ac9jCYi8WNdGFCh3SI6+dyYLizaE4A==
Message-ID: <CF83E110.393E%sbanks@akamai.com>
References: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com>
In-Reply-To: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/D7xY_Bf5Ih7-exfB71TgiRjTeEI
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:44:46 -0000

SGkgV2FycmVuLA0KCUkgZmluZCB0aGlzIGZlZWRiYWNrIHVzZWZ1bDsgaW4gdGhlIHBhc3QsIHRv
IHNvbHZlIHRoaXMgcHJvYmxlbSwgSSd2ZQ0KdXN1YWxseSB0YWtlbiBhIHNuYXBzaG90IG9mIHRo
ZSBibHVlIHNoZWV0IGJlZm9yZSBJJ3ZlIHR1cm5lZCBpdCBpbi4gVGhpcw0KbGV0J3MgbWUgdW5k
ZXJzdGFuZCB0aGUgbnVtYmVyIG9mIGZvbGtzIHdobyBzaWduZWQgaW4gZm9yIHRoZSBsYXN0DQpt
ZWV0aW5nLCBhcyB3ZWxsIGFzIChvZnRlbikgcmV0cmlldmUgY29ycmVjdCBzcGVsbGluZyBvZiBz
cGVha2VyIG5hbWVzIGZvcg0KbWludXRlcyB0aGF0IEkgcmV2aWV3LCBwcmlvciB0byBwb3N0aW5n
LiA6KQ0KDQoJSXQgdGFrZXMgYSBiaXQgb2YgZGlzY2lwbGluZSB0byByZW1lbWJlciwgYmVjYXVz
ZSBhZ3JlZWQsIHRoZSBlbmQgb2YgdGhlDQptZWV0aW5nIGNhbiBiZSBhIGJsdXIsIHBhcnRpY3Vs
YXJseSBpZiB5b3UgcnVuIHJpZ2h0IHVwIHRvIHRoZSBsYXN0DQptaW51dGUsIGFuZCB0aGUgbmV4
dCBncm91cCBpcyBjb21pbmcgaW4gLSBidXQgYSBxdWljayBwaWN0dXJlIHdpdGggeW91cg0KcGhv
bmUgb3IgdGFibGV0IGNhbiBzYXZlIGEgbG90IG9mIHRpbWUuIEhvcGUgdGhpcyBoZWxwcyENCg0K
UmVnYXJkcywNClNhcmFoDQoNCk9uIDQvMjgvMTQsIDEwOjMzIEFNLCAiV2FycmVuIEt1bWFyaSIg
PHdhcnJlbkBrdW1hcmkubmV0PiB3cm90ZToNCg0KPkhpIHRoZXJlLA0KPg0KPlNvLCBJIGp1c3Qg
d2VudCBhbG9uZyB0byByZXF1ZXN0IGEgc2Vzc2lvbiBpbiBUb3JvbnRvLg0KPkkgY2xpY2tlZCB0
aGUgIlJldHJpZXZlIGluZm8gZnJvbSBsYXN0IHNlc3Npb24iIGJ1dHRvbiAoZ3JlYXQgYWRkaXRp
b24pLg0KPkFwcGFyZW50bHkgaW4gTG9uZG9uIEkgcmVxdWVzdGVkIGEgcm9vbSBmb3IgNzUgcGVv
cGxlIC0tIGdyZWF0IQ0KPg0KPlVuZm9ydHVuYXRlbHksIHRoZSByb29tIHdhcyBvdmVyZmxvd2lu
ZywgZm9sayB3ZXJlIHNpdHRpbmcgb24gdGhlDQo+Zmxvb3IsIHN0YW5kaW5nLCBldGMuLCBzbyBv
YnZpb3VzbHkgSSBzaG91bGQgcmVxdWVzdCBhIGxhcmdlciByb29tIC0tDQo+YnV0IGhvdyBtYW55
IGZvbGsgd2VyZSB0aGVyZT8gMTAwPyAyMDA/IDc2Pw0KPg0KPkV2ZXJ5b25lXncgTW9zdCBzaWdu
ZWQgdGhlIGJsdWVzaGVldHMsIGJ1dCBJIGVpdGhlcjoNCj5BOiB0aGUgZW5kIG9mIHRoZSBtZWV0
aW5nIHdhcyBhIGJsdXIgLyBkZWVyIGluIHRoZSBoZWFkbGlnaHRzIGFuZCAvIG9yDQo+QjogbXkg
Y28tY2hhaXIgdG9vayB0aGVtIGFuZCBkcm9wcGVkIHRoZW0gb2ZmIGF0IHRoZSBzZWNyZXRhcmlh
dC4NCj5hbmQgc28gaGF2ZSBubyBpZGVhIGhvdyBtYW55IGF0dGVuZGVlcyB0aGVyZSBhY3R1YWxs
eSB3ZXJlLg0KPg0KPkl0IHdvdWxkIGJlIChJTU8pIHZlcnkgaGVscGZ1bCBpZiB0aGUgc2VjcmV0
YXJpYXQgY291bGQgcG9zdCB0aGUNCj5udW1iZXIgb2YgZm9sayB3aG8gc2lnbmVkIHRoZSBibHVl
c2hlZXRzIChlYWNoIGxpbmUgaXMgbnVtYmVyZWQsDQo+c2ltcGx5IGFkZCB1cCB0aGUgcm93cyBm
aWxsZWQgZnJvbSBlYWNoKSBpbiB0aGUgZGF0YXRyYWNrZXIgdG9vbC4NCj5UaGF0IHdheSB3aGVu
IHNjaGVkdWxpbmcgYSBtZWV0aW5nIHRoZSB0b29sIGNvdWxkIHNheSAiTGFzdCB0aW1lIHlvdQ0K
PnJlcXVlc3RlZCBzcGFjZSBmb3IgNzUgcGVvcGxlLCBvbmx5IDYgc2hvd2VkIHVwIiwgb3IgIkxh
c3QgdGltZSB5b3UNCj5yZXF1ZXN0ZWQgNTAsIDEyNyBmb2xrIHNpZ25lZCB0aGUgc2hlZXRzIi4N
Cj4NCj5UaGlzIHdvdWxkIGFsbG93IHVzIHRvIGJldHRlciBkZWNpZGUgaG93IG11Y2ggc3BhY2Ug
dG8gcmVxdWVzdC4uLg0KPg0KPlRob3VnaHRzPw0KPlcNCj4NCg0K


From nobody Mon Apr 28 10:50:28 2014
Return-Path: <sandy@tislabs.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC33C1A6F9E for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level: 
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_81=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nGijAyhmLCJ for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:50:25 -0700 (PDT)
Received: from walnut.tislabs.com (walnut.tislabs.com [192.94.214.200]) by ietfa.amsl.com (Postfix) with ESMTP id 237601A6F8E for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:50:25 -0700 (PDT)
Received: from nova.tislabs.com (unknown [10.66.1.77]) by walnut.tislabs.com (Postfix) with ESMTP id 6F8A028B003A; Mon, 28 Apr 2014 13:50:24 -0400 (EDT)
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by nova.tislabs.com (Postfix) with ESMTP id 5676D1F803D; Mon, 28 Apr 2014 13:50:24 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: How many folk were there at my WG meeting?
From: Sandra Murphy <sandy@tislabs.com>
In-Reply-To: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com>
Date: Mon, 28 Apr 2014 13:50:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com>
References: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/QIOjsQ45BL8gtkLoadPAd_yRZq8
Cc: WG Chairs <wgchairs@ietf.org>, Sandra Murphy <sandy@tislabs.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:50:26 -0000

I don't know if this helps, but the Secretariat has started scanning the =
blue sheets into the proceedings.

I don't know what wg you are talking about, but here are two examples =
that seem to be associated with your name on the wg chairs page:

=
http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-opsarea-01.pdf=


http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-dane-01.pdf

You have to do your own counting, however.

--Sandy


On Apr 28, 2014, at 1:33 PM, Warren Kumari <warren@kumari.net> wrote:

> Hi there,
>=20
> So, I just went along to request a session in Toronto.
> I clicked the "Retrieve info from last session" button (great =
addition).
> Apparently in London I requested a room for 75 people -- great!
>=20
> Unfortunately, the room was overflowing, folk were sitting on the
> floor, standing, etc., so obviously I should request a larger room --
> but how many folk were there? 100? 200? 76?
>=20
> Everyone^w Most signed the bluesheets, but I either:
> A: the end of the meeting was a blur / deer in the headlights and / or
> B: my co-chair took them and dropped them off at the secretariat.
> and so have no idea how many attendees there actually were.
>=20
> It would be (IMO) very helpful if the secretariat could post the
> number of folk who signed the bluesheets (each line is numbered,
> simply add up the rows filled from each) in the datatracker tool.
> That way when scheduling a meeting the tool could say "Last time you
> requested space for 75 people, only 6 showed up", or "Last time you
> requested 50, 127 folk signed the sheets".
>=20
> This would allow us to better decide how much space to request...
>=20
> Thoughts?
> W


From nobody Mon Apr 28 10:55:05 2014
Return-Path: <sbanks@akamai.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3EEE1A6F8E for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level: 
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_81=0.6, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-FxWOs0_oCA for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:55:00 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 332361A6FB8 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:55:00 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 5498216559E; Mon, 28 Apr 2014 17:54:59 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (prod-mail-relay03.akamai.com [172.27.8.26]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id 498631655AF; Mon, 28 Apr 2014 17:54:59 +0000 (GMT)
Received: from ustx2ex-cashub.dfw01.corp.akamai.com (ustx2ex-cashub5.dfw01.corp.akamai.com [172.27.25.71]) by prod-mail-relay03.akamai.com (Postfix) with ESMTP id 42CC52FD60; Mon, 28 Apr 2014 17:54:59 +0000 (GMT)
Received: from USMBX2.msg.corp.akamai.com ([169.254.1.44]) by ustx2ex-cashub5.dfw01.corp.akamai.com ([172.27.25.71]) with mapi; Mon, 28 Apr 2014 12:54:58 -0500
From: "Banks, Sarah" <sbanks@akamai.com>
To: Sandra Murphy <sandy@tislabs.com>, Warren Kumari <warren@kumari.net>
Date: Mon, 28 Apr 2014 12:55:13 -0500
Subject: Re: How many folk were there at my WG meeting?
Thread-Topic: How many folk were there at my WG meeting?
Thread-Index: Ac9jCvibhFXvdEPFSFurX0MNU5XW9w==
Message-ID: <CF83E3DB.394F%sbanks@akamai.com>
References: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com> <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com>
In-Reply-To: <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/FrVU_MT0ImZV2vfeRc-4WD_Pgk8
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:55:03 -0000

SGkgU2FuZHksDQoJSSB0aGluayB0aGF0J3MgcHJldHR5IGF3ZXNvbWUuIFRoYW5rcyBmb3Igc2hh
cmluZyA6KSBJIHdhcyBhYmxlIHRvIHN1Yg0KdGhlIFdHIG5hbWUgYmVsb3cgZm9yIG1pbmUgYW5k
IHdhcyBhYmxlIHRvIGxvYWQgbXkgYmx1ZSBzaGVldCBqdXN0IGZpbmUuDQpPbiBtaW5lLCBhdCB0
aGUgdG9wLCBzb21lb25lIGhhZCB3cml0dGVuIHRoZSBhdHRlbmRlZSBjb3VudCBhbmQgY2lyY2xl
ZA0KaXQsIEZZSS4NCg0KQ2hlZXJzDQpTYXJhaA0KDQoNCk9uIDQvMjgvMTQsIDEwOjUwIEFNLCAi
U2FuZHJhIE11cnBoeSIgPHNhbmR5QHRpc2xhYnMuY29tPiB3cm90ZToNCg0KPkkgZG9uJ3Qga25v
dyBpZiB0aGlzIGhlbHBzLCBidXQgdGhlIFNlY3JldGFyaWF0IGhhcyBzdGFydGVkIHNjYW5uaW5n
IHRoZQ0KPmJsdWUgc2hlZXRzIGludG8gdGhlIHByb2NlZWRpbmdzLg0KPg0KPkkgZG9uJ3Qga25v
dyB3aGF0IHdnIHlvdSBhcmUgdGFsa2luZyBhYm91dCwgYnV0IGhlcmUgYXJlIHR3byBleGFtcGxl
cw0KPnRoYXQgc2VlbSB0byBiZSBhc3NvY2lhdGVkIHdpdGggeW91ciBuYW1lIG9uIHRoZSB3ZyBj
aGFpcnMgcGFnZToNCj4NCj5odHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzg5L2JsdWVz
aGVldHMvYmx1ZXNoZWV0cy04OS1vcHNhcmVhLTAxLnBkZg0KPg0KPmh0dHA6Ly93d3cuaWV0Zi5v
cmcvcHJvY2VlZGluZ3MvODkvYmx1ZXNoZWV0cy9ibHVlc2hlZXRzLTg5LWRhbmUtMDEucGRmDQo+
DQo+WW91IGhhdmUgdG8gZG8geW91ciBvd24gY291bnRpbmcsIGhvd2V2ZXIuDQo+DQo+LS1TYW5k
eQ0KPg0KPg0KPk9uIEFwciAyOCwgMjAxNCwgYXQgMTozMyBQTSwgV2FycmVuIEt1bWFyaSA8d2Fy
cmVuQGt1bWFyaS5uZXQ+IHdyb3RlOg0KPg0KPj4gSGkgdGhlcmUsDQo+PiANCj4+IFNvLCBJIGp1
c3Qgd2VudCBhbG9uZyB0byByZXF1ZXN0IGEgc2Vzc2lvbiBpbiBUb3JvbnRvLg0KPj4gSSBjbGlj
a2VkIHRoZSAiUmV0cmlldmUgaW5mbyBmcm9tIGxhc3Qgc2Vzc2lvbiIgYnV0dG9uIChncmVhdCBh
ZGRpdGlvbikuDQo+PiBBcHBhcmVudGx5IGluIExvbmRvbiBJIHJlcXVlc3RlZCBhIHJvb20gZm9y
IDc1IHBlb3BsZSAtLSBncmVhdCENCj4+IA0KPj4gVW5mb3J0dW5hdGVseSwgdGhlIHJvb20gd2Fz
IG92ZXJmbG93aW5nLCBmb2xrIHdlcmUgc2l0dGluZyBvbiB0aGUNCj4+IGZsb29yLCBzdGFuZGlu
ZywgZXRjLiwgc28gb2J2aW91c2x5IEkgc2hvdWxkIHJlcXVlc3QgYSBsYXJnZXIgcm9vbSAtLQ0K
Pj4gYnV0IGhvdyBtYW55IGZvbGsgd2VyZSB0aGVyZT8gMTAwPyAyMDA/IDc2Pw0KPj4gDQo+PiBF
dmVyeW9uZV53IE1vc3Qgc2lnbmVkIHRoZSBibHVlc2hlZXRzLCBidXQgSSBlaXRoZXI6DQo+PiBB
OiB0aGUgZW5kIG9mIHRoZSBtZWV0aW5nIHdhcyBhIGJsdXIgLyBkZWVyIGluIHRoZSBoZWFkbGln
aHRzIGFuZCAvIG9yDQo+PiBCOiBteSBjby1jaGFpciB0b29rIHRoZW0gYW5kIGRyb3BwZWQgdGhl
bSBvZmYgYXQgdGhlIHNlY3JldGFyaWF0Lg0KPj4gYW5kIHNvIGhhdmUgbm8gaWRlYSBob3cgbWFu
eSBhdHRlbmRlZXMgdGhlcmUgYWN0dWFsbHkgd2VyZS4NCj4+IA0KPj4gSXQgd291bGQgYmUgKElN
TykgdmVyeSBoZWxwZnVsIGlmIHRoZSBzZWNyZXRhcmlhdCBjb3VsZCBwb3N0IHRoZQ0KPj4gbnVt
YmVyIG9mIGZvbGsgd2hvIHNpZ25lZCB0aGUgYmx1ZXNoZWV0cyAoZWFjaCBsaW5lIGlzIG51bWJl
cmVkLA0KPj4gc2ltcGx5IGFkZCB1cCB0aGUgcm93cyBmaWxsZWQgZnJvbSBlYWNoKSBpbiB0aGUg
ZGF0YXRyYWNrZXIgdG9vbC4NCj4+IFRoYXQgd2F5IHdoZW4gc2NoZWR1bGluZyBhIG1lZXRpbmcg
dGhlIHRvb2wgY291bGQgc2F5ICJMYXN0IHRpbWUgeW91DQo+PiByZXF1ZXN0ZWQgc3BhY2UgZm9y
IDc1IHBlb3BsZSwgb25seSA2IHNob3dlZCB1cCIsIG9yICJMYXN0IHRpbWUgeW91DQo+PiByZXF1
ZXN0ZWQgNTAsIDEyNyBmb2xrIHNpZ25lZCB0aGUgc2hlZXRzIi4NCj4+IA0KPj4gVGhpcyB3b3Vs
ZCBhbGxvdyB1cyB0byBiZXR0ZXIgZGVjaWRlIGhvdyBtdWNoIHNwYWNlIHRvIHJlcXVlc3QuLi4N
Cj4+IA0KPj4gVGhvdWdodHM/DQo+PiBXDQo+DQoNCg==


From nobody Mon Apr 28 10:59:33 2014
Return-Path: <smccammon@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5466E1A6F8E for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.053
X-Spam-Level: 
X-Spam-Status: No, score=-0.053 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_81=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5L2dUfkJJZwn for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 10:59:29 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id B64661A6F54 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 10:59:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0478A1E12A4; Mon, 28 Apr 2014 10:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wWfNDu3jGgR; Mon, 28 Apr 2014 10:59:19 -0700 (PDT)
Received: from [192.168.1.66] (99-110-51-88.lightspeed.sntcca.sbcglobal.net [99.110.51.88]) by c8a.amsl.com (Postfix) with ESMTPSA id B91261E1890; Mon, 28 Apr 2014 10:59:19 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: How many folk were there at my WG meeting?
From: Stephanie McCammon <smccammon@amsl.com>
In-Reply-To: <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com>
Date: Mon, 28 Apr 2014 10:59:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7919248B-5871-4A49-A79F-6AE7241BDCD8@amsl.com>
References: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com> <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com>
To: WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/164BUgPlFMqypgD1qjuHeMql7VI
Cc: Sandra Murphy <sandy@tislabs.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 17:59:31 -0000

Hello Working Group Chairs,

At the bottom of the email sent out to announce that scheduling has been =
opened there is a list of all the blue sheet totals for the previous =
meeting by working group.  It=92s towards the bottom of the announcement =
email so I believe it may be easily missed.  I=92ve included the list =
here in case that is helpful.  Please let me know if you need help with =
anything else.

Sincerely,

Stephanie McCammon
IETF Project Manager
48377 Fremont Blvd, Ste. 117
Fremont, CA 94538
T: +1.510.492.4081
F: +1.510.492.4001

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


89th IETF Meeting Attendance Numbers

6lo - 88
6man - 165
6tisch - 49
abfab =96 22
ace (BoF) - 123
alto  - 57
appsawg/apparea - 129
aqm - 110
avtcore - 44
avtext =96 52
bfcpbis - 15
bmwg - 18
ccamp - 47
ccamp (2nd session) - 39
cdni =96 42
cfrg - 52
clue =96 32
clue (2nd session) - 26
core - 59
core (2nd session) =96 62
dane - 133
dbound (BoF) - 127
dhc - 63
dice - 72
dime - 18
dispatch - 67
dmm =96 45
dnse (BoF) - 206
dnsop =96 118
dnsop (2nd session) =96 not provided
dnssd - 95
ecrit - 28
eman =96 not provided
eppext - 28
geopriv =96 40
grow - 49
homenet - 136
httpauth - 65
httpbis - 113
httpbis (2nd session) - 107
i2rs - 205
iccrg (RG) - 125
icnrg (RG) - 105
idr - 102
igovupdate BoF - 144
insipid - 24
intarea (AG) - 129
ippm - 70
ipsecme - 50
IRTF Open Meeting - 65
isis - 67
jose - 38
json - 36
karp =96 not provided
kitten - 38
l2vpn - 101
l3vpn - 67
lisp - 70
lmap - 48
lwig - 38
manet - 28
mboned - 16
mif =96 48
mile - 29
mmusic - 59
mmusic (2nd session) - 58
mpls - 98
mpls (2nd session) - 99
mptcp - 105
ncrg (RG) - 52
netconf - 73
netext - 29
netmod - 47
nfsv4 - 11
nmrg (RG) - 40
ntp (combined with tictoc) - 16
nvo3 - 174
nwcrg (PRG) - 53
oauth - 54
opsawg/opsarea - 72
ospf - 28
paws =96 19
payload - 30
pce - 75
pcp - 39
pim - 17
ppsp - 18
precis - 33
pwe3 - 50
radext - 25
rfcform - 47
rmcat - 70
roll - 45
rtcweb - 136
rtcweb (2nd session) - 119
rtgarea (AG) - 97
rtgwg - 77
saag (AG) - 108
sacm - 27
scim - 25
sdnrg (RG) =96 198
sfc - 244
sidr =96 69
sipcore =96 49
sipcore (2nd session) - 44
siprec =96 22
softwire - 48
spring - 90
stir - 61
straw =96 41
sunset4 =96 49
taps (BoF) =96 162
tcmtf - 64
tcpm =96 66
tcpm (2nd session) - 53
tictoc (combined with ntp) - 16
tls =96 107
tram (BoF) =96 52
trans (BoF) - 65
trill - 34
tsvarea (AG) - 89
tsvwg - 71
tsvwg (2nd session) =96 68
uta - 85
v6ops - 100
v6ops (2nd session) =96 71
vnfpool (BoF) - 170
weirds - 55
wpkops - 28
xmpp - 36
xrblock - 19



On Apr 28, 2014, at 10:50 , Sandra Murphy <sandy@tislabs.com> wrote:

I don't know if this helps, but the Secretariat has started scanning the =
blue sheets into the proceedings.

I don't know what wg you are talking about, but here are two examples =
that seem to be associated with your name on the wg chairs page:

=
http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-opsarea-01.pdf=


http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-dane-01.pdf

You have to do your own counting, however.

--Sandy


On Apr 28, 2014, at 1:33 PM, Warren Kumari <warren@kumari.net> wrote:

> Hi there,
>=20
> So, I just went along to request a session in Toronto.
> I clicked the "Retrieve info from last session" button (great =
addition).
> Apparently in London I requested a room for 75 people -- great!
>=20
> Unfortunately, the room was overflowing, folk were sitting on the
> floor, standing, etc., so obviously I should request a larger room --
> but how many folk were there? 100? 200? 76?
>=20
> Everyone^w Most signed the bluesheets, but I either:
> A: the end of the meeting was a blur / deer in the headlights and / or
> B: my co-chair took them and dropped them off at the secretariat.
> and so have no idea how many attendees there actually were.
>=20
> It would be (IMO) very helpful if the secretariat could post the
> number of folk who signed the bluesheets (each line is numbered,
> simply add up the rows filled from each) in the datatracker tool.
> That way when scheduling a meeting the tool could say "Last time you
> requested space for 75 people, only 6 showed up", or "Last time you
> requested 50, 127 folk signed the sheets".
>=20
> This would allow us to better decide how much space to request...
>=20
> Thoughts?
> W



From nobody Mon Apr 28 11:10:41 2014
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F91F1A6F9E; Mon, 28 Apr 2014 10:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level: 
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, LOTS_OF_MONEY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JuTOmLpMk1FK; Mon, 28 Apr 2014 10:50:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 377D01A6FBB; Mon, 28 Apr 2014 10:50:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Extension of Call for Nominations: Jonathan B. Postel Service Award
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140428175043.26026.47649.idtracker@ietfa.amsl.com>
Date: Mon, 28 Apr 2014 10:50:43 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/vhIQ0sn4O-SkyigLF0jqRxSqhzY
X-Mailman-Approved-At: Mon, 28 Apr 2014 11:10:32 -0700
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 17:50:47 -0000

Nominations Sought for 2014 Jonathan B. Postel Service Award are extended to 16 May 2014.

The Internet Society is soliciting nominations of qualified candidates for the 2014 Jonathan
B. Postel Service Award by 7 May. This annual award is presented to an individual or organization 
that has made outstanding contributions in service to the data communications community. The 
award, which includes a presentation crystal and a USD 20,000 prize, is scheduled to be presented 
during the 90th Internet Engineering Task Force (IETF) meeting in Toronto, ON, Canada, 20 -25 
July 2014. 

Extension Deadline for nominations is 16 May 2014.

More About the Award

The Jonathan B. Postel Service Award was established by the Internet Society to honor a person 
who has made outstanding contributions in service to the data communications community. The 
award is focused on sustained and substantial technical contributions, service to the community, 
and leadership. With respect to leadership, the award committee places particular emphasis on candidates 
who have supported and enabled others in addition to their own specific actions.
 
The award is named for Dr. Jonathan B. Postel to recognize and commemorate the extraordinary stewardship 
exercised by Jon over the course of a thirty year career in networking. He served as the editor of the RFC 
series of notes from its inception in 1969 until 1998. He also served as the ARPANET “numbers Czar” and Internet 
Assigned Numbers Authority over the same period of time. He was a founding member of the Internet Architecture 
(nee Activities) Board and the first individual member of the Internet Society, which he also served as a Trustee.
 
Find out more
•	Learn more about Jon Postel’s life and contributions.
•	Find the out more on the award, nomination procedures, and online submission forms.
•	I'm ready to nominate someone!

For any questions please contact postel@isoc.org

Best Regards,

Internet Society Team


From nobody Mon Apr 28 11:19:25 2014
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 095131A6F46 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 11:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_81=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxVBMISPDi7a for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 11:19:22 -0700 (PDT)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by ietfa.amsl.com (Postfix) with ESMTP id D9A841A6FBF for <wgchairs@ietf.org>; Mon, 28 Apr 2014 11:19:20 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id d1so6202704wiv.1 for <wgchairs@ietf.org>; Mon, 28 Apr 2014 11:19:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pvtlAxsz4zokUufKL5nmLijaMZhzUcmyZieshcUKJ58=; b=HBKwMMiFdDjeOpboVSOLg5vsD+GqX7L8lh/QpEMUZ+2wWbZ1NfCg0AelpctN5JcJBe P6MCu524x01rew8xMevZ364WUbXOYLoFepmUmWa4hipen0YISoe7W7M23BFStWkkjPBc q+Iqd8/BCGsjDDiwPdFvAKrLddxThZIit0Iq2lD8ovdbMh6hps0Ogx8qBrbj3XS1OX18 gEbbwy1tAtPdevTdGaG1Vac32qzE0x8fivnOjzalmiybHNWcbJow1StM0B0cccQ8HEa8 bBxk/iteaZLqXuA8fpbfzYAW8WmJkdwwIhCrmNVpPGptBQuy+TORXWGJN0SuV8fLcl3S Ej8g==
X-Gm-Message-State: ALoCoQnz2EdsblfnFhSO3NDrv5BEmoqgzdwDxg1atTAMLXiYxwx3Pwxrhcm1Cx/HMPenUpIQwxFJ
MIME-Version: 1.0
X-Received: by 10.180.105.132 with SMTP id gm4mr16581859wib.39.1398709159629;  Mon, 28 Apr 2014 11:19:19 -0700 (PDT)
Received: by 10.194.54.162 with HTTP; Mon, 28 Apr 2014 11:19:19 -0700 (PDT)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <7919248B-5871-4A49-A79F-6AE7241BDCD8@amsl.com>
References: <CAHw9_iJYXhcjjgtnbcumnD9gDR4UBp+-ycD8ioyYrhSSump39A@mail.gmail.com> <73D108CB-8CCB-41E6-881F-BA9BA79AE6C0@tislabs.com> <7919248B-5871-4A49-A79F-6AE7241BDCD8@amsl.com>
Date: Mon, 28 Apr 2014 14:19:19 -0400
Message-ID: <CAHw9_iKFrQ-3PF95Ct1Ut=h4BhhLq=kc+cmUiKN9JEXb4GmpXg@mail.gmail.com>
Subject: Re: How many folk were there at my WG meeting?
From: Warren Kumari <warren@kumari.net>
To: Stephanie McCammon <smccammon@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/boC4SMaMBbsI6UFqyZF0Xu37-MM
Cc: WG Chairs <wgchairs@ietf.org>, Sandra Murphy <sandy@tislabs.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 18:19:24 -0000

On Mon, Apr 28, 2014 at 1:59 PM, Stephanie McCammon <smccammon@amsl.com> wr=
ote:
>
>
> Hello Working Group Chairs,
>
> At the bottom of the email sent out to announce that scheduling has been =
opened there is a list of all the blue sheet totals for the previous meetin=
g by working group.  It's towards the bottom of the announcement email so I=
 believe it may be easily missed.

Yup! I usually just see the subject line and ignore the rest.. :-)

>  I've included the list here in case that is helpful.  Please let me know=
 if you need help with anything else.

Yup, this is perfect!

Thanks Stephanie!
W


>
> Sincerely,
>
> Stephanie McCammon
> IETF Project Manager
> 48377 Fremont Blvd, Ste. 117
> Fremont, CA 94538
> T: +1.510.492.4081
> F: +1.510.492.4001
>
> Association Management Solutions (AMS)
> Forum Management, Meeting, and Event Planning
> www.amsl.com
>
>
> 89th IETF Meeting Attendance Numbers
>
> 6lo - 88
> 6man - 165
> 6tisch - 49
> abfab - 22
> ace (BoF) - 123
> alto  - 57
> appsawg/apparea - 129
> aqm - 110
> avtcore - 44
> avtext - 52
> bfcpbis - 15
> bmwg - 18
> ccamp - 47
> ccamp (2nd session) - 39
> cdni - 42
> cfrg - 52
> clue - 32
> clue (2nd session) - 26
> core - 59
> core (2nd session) - 62
> dane - 133
> dbound (BoF) - 127
> dhc - 63
> dice - 72
> dime - 18
> dispatch - 67
> dmm - 45
> dnse (BoF) - 206
> dnsop - 118
> dnsop (2nd session) - not provided
> dnssd - 95
> ecrit - 28
> eman - not provided
> eppext - 28
> geopriv - 40
> grow - 49
> homenet - 136
> httpauth - 65
> httpbis - 113
> httpbis (2nd session) - 107
> i2rs - 205
> iccrg (RG) - 125
> icnrg (RG) - 105
> idr - 102
> igovupdate BoF - 144
> insipid - 24
> intarea (AG) - 129
> ippm - 70
> ipsecme - 50
> IRTF Open Meeting - 65
> isis - 67
> jose - 38
> json - 36
> karp - not provided
> kitten - 38
> l2vpn - 101
> l3vpn - 67
> lisp - 70
> lmap - 48
> lwig - 38
> manet - 28
> mboned - 16
> mif - 48
> mile - 29
> mmusic - 59
> mmusic (2nd session) - 58
> mpls - 98
> mpls (2nd session) - 99
> mptcp - 105
> ncrg (RG) - 52
> netconf - 73
> netext - 29
> netmod - 47
> nfsv4 - 11
> nmrg (RG) - 40
> ntp (combined with tictoc) - 16
> nvo3 - 174
> nwcrg (PRG) - 53
> oauth - 54
> opsawg/opsarea - 72
> ospf - 28
> paws - 19
> payload - 30
> pce - 75
> pcp - 39
> pim - 17
> ppsp - 18
> precis - 33
> pwe3 - 50
> radext - 25
> rfcform - 47
> rmcat - 70
> roll - 45
> rtcweb - 136
> rtcweb (2nd session) - 119
> rtgarea (AG) - 97
> rtgwg - 77
> saag (AG) - 108
> sacm - 27
> scim - 25
> sdnrg (RG) - 198
> sfc - 244
> sidr - 69
> sipcore - 49
> sipcore (2nd session) - 44
> siprec - 22
> softwire - 48
> spring - 90
> stir - 61
> straw - 41
> sunset4 - 49
> taps (BoF) - 162
> tcmtf - 64
> tcpm - 66
> tcpm (2nd session) - 53
> tictoc (combined with ntp) - 16
> tls - 107
> tram (BoF) - 52
> trans (BoF) - 65
> trill - 34
> tsvarea (AG) - 89
> tsvwg - 71
> tsvwg (2nd session) - 68
> uta - 85
> v6ops - 100
> v6ops (2nd session) - 71
> vnfpool (BoF) - 170
> weirds - 55
> wpkops - 28
> xmpp - 36
> xrblock - 19
>
>
>
> On Apr 28, 2014, at 10:50 , Sandra Murphy <sandy@tislabs.com> wrote:
>
> I don't know if this helps, but the Secretariat has started scanning the =
blue sheets into the proceedings.
>
> I don't know what wg you are talking about, but here are two examples tha=
t seem to be associated with your name on the wg chairs page:
>
> http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-opsarea-01.pd=
f
>
> http://www.ietf.org/proceedings/89/bluesheets/bluesheets-89-dane-01.pdf
>
> You have to do your own counting, however.
>
> --Sandy
>
>
> On Apr 28, 2014, at 1:33 PM, Warren Kumari <warren@kumari.net> wrote:
>
>> Hi there,
>>
>> So, I just went along to request a session in Toronto.
>> I clicked the "Retrieve info from last session" button (great addition).
>> Apparently in London I requested a room for 75 people -- great!
>>
>> Unfortunately, the room was overflowing, folk were sitting on the
>> floor, standing, etc., so obviously I should request a larger room --
>> but how many folk were there? 100? 200? 76?
>>
>> Everyone^w Most signed the bluesheets, but I either:
>> A: the end of the meeting was a blur / deer in the headlights and / or
>> B: my co-chair took them and dropped them off at the secretariat.
>> and so have no idea how many attendees there actually were.
>>
>> It would be (IMO) very helpful if the secretariat could post the
>> number of folk who signed the bluesheets (each line is numbered,
>> simply add up the rows filled from each) in the datatracker tool.
>> That way when scheduling a meeting the tool could say "Last time you
>> requested space for 75 people, only 6 showed up", or "Last time you
>> requested 50, 127 folk signed the sheets".
>>
>> This would allow us to better decide how much space to request...
>>
>> Thoughts?
>> W
>
>


From nobody Mon Apr 28 12:56:54 2014
Return-Path: <repenno@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02ADF1A6FB7 for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 12:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvnukWvw3uUY for <wgchairs@ietfa.amsl.com>; Mon, 28 Apr 2014 12:56:43 -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 2B8191A6FBB for <wgchairs@ietf.org>; Mon, 28 Apr 2014 12:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1584; q=dns/txt; s=iport; t=1398715003; x=1399924603; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=scT0GbacoQctbJ2zYYWgDzrNBnHgoglgGQ5KdTPpQeM=; b=bq0kAPHfn5QO6USQmnbXVAxIOh7/xoBjNIK+sjDl9wir7J6Mjyct03E6 N2L9Ya1Q7gpkddekGUarL+WJuZ73eUWU7uiFWfb6EjhizzVxiCa8IYi2s uFiWE/WqovnRQRbzYI8QVqp+QbAH2E/ySc2sb8dl+VI3mQ4JJJDceNp34 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFaxXlOtJA2K/2dsb2JhbABZgwaBJsRqgRsWdIIlAQEBBHkSAQgOCmAlAgQBDQWIQch8F44mMweEOQEDiTePVZJegzGCKw
X-IronPort-AV: E=Sophos;i="4.97,945,1389744000"; d="scan'208";a="321061492"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-4.cisco.com with ESMTP; 28 Apr 2014 19:56:42 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3SJugGA032146 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 19:56:42 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.212]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Mon, 28 Apr 2014 14:56:41 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Sandra Murphy <sandy@tislabs.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: Proposal for Structuring New WGs
Thread-Topic: Proposal for Structuring New WGs
Thread-Index: AQHPXlCIjhj+2JczIkOgpazDF7+vKpsnC2OAgAAVVICAAIdZgP//scGA
Date: Mon, 28 Apr 2014 19:56:41 +0000
Message-ID: <CF83FF26.B473%repenno@cisco.com>
In-Reply-To: <37962B10-A83C-42FC-9E9A-3B3BA88B6CAB@tislabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.154.148.31]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B8DDAFACDDB1AC41BE608E848FD91243@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/SYVqQBIvIS64eiyqq12p0cxPqZo
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Apr 2014 19:56:48 -0000

Right!

I tried an analogy with Firewall development but maybe this is a better
one:

You can get dozens of nations to search for a missing plane, but if you
have asked them before starting the search to write a =B3problem statement=
=B2
document they certainly would still be at it trying to define what is the
exact definition of =B3missing=B2.  And I think due to our very nature this
problem amplified.

Therefore my proposal for more agile WGs.


Thanks,


On 4/28/14, 10:36 AM, "Sandra Murphy" <sandy@tislabs.com> wrote:

>On Apr 28, 2014, at 5:32 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>
>> If the problem is well understood enough for a working group to be
>>chartered,
>> why does it take that working group so long to write a tight and clear
>>document
>> defining the problem?
>
>My answers (related):
>
>Abstraction is hard for humans.  A definition is an abstraction of the
>important attributes of a problem, and hence hard.
>
>Writing is hard for humans.  I read someone's quote once that writing was
>the greatest spur to clear thinking.(*)  So the process of trying to
>write a description of the problem exposes any fuzzy thinking.  (I used
>to think that one thought clearly, and then one wrote clearly.  But I've
>experienced the feedback process myself.)
>
>This is hard for one human and mutiplicatively hard for multiple humans
>in collaboration.
>
>--Sandy
>
>(*)Don't know my original source. Quick web search yields lots of similar
>comments. On Writing Well by William Zinsser, among many others. =20


From nobody Tue Apr 29 02:58:39 2014
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A971A06DF; Tue, 29 Apr 2014 02:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nv10q6uasVfS; Tue, 29 Apr 2014 02:58:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D461A0273; Tue, 29 Apr 2014 02:58:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: CORRECTIONS: Nominations Sought for 2014 Jonathan B. Postel Service Award are extended to 16 May 2014.
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140429095823.17080.94823.idtracker@ietfa.amsl.com>
Date: Tue, 29 Apr 2014 02:58:23 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/RZQ9vivdrNmQ7La4sazkuCjuHwE
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 29 Apr 2014 09:58:25 -0000

The Internet Society is soliciting nominations of qualified candidates for the 2014 Jonathan B. Postel 
Service Award by 16 May. This annual award is presented to an individual or organization that has 
made outstanding contributions in service to the data communications community. The award, which
 includes a presentation crystal and a USD 20,000 prize, is scheduled to be presented during the 
90th Internet Engineering Task Force (IETF) meeting in Toronto, ON, Canada, 20 -25 July 2014. 
Extension Deadline for nominations is 16 May 2014.


More About the Award

The Jonathan B. Postel Service Award was established by the Internet Society to honor a person who 
has made outstanding contributions in service to the data communications community. The award is 
focused on sustained and substantial technical contributions, service to the community, and 
leadership. With respect to leadership, the award committee places particular emphasis on 
candidates who have supported and enabled others in addition to their own specific actions.

 
The award is named for Dr. Jonathan B. Postel to recognize and commemorate the extraordinary 
stewardship exercised by Jon over the course of a thirty year career in networking. He served as the 
editor of the RFC series of notes from its inception in 1969 until 1998. He also served as the 
ARPANET “numbers Czar” and Internet Assigned Numbers Authority over the same period of time. He 
was a founding member of the Internet Architecture (nee Activities) Board and the first individual 
member of the Internet Society, which he also served as a Trustee.


Find out more

•Jon Postel’s life an contributions 
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/postel-service-award

•Award nomination procedures and online submission forms 
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/postel-service-award/procedures

For any questions please contact postel@isoc.org


Best Regards,


Internet Society Team


From nobody Tue Apr 29 04:27:39 2014
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8ACD1A082F for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 04:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cp8mkjvXmsa0 for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 04:27:35 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 9822B1A084B for <wgchairs@ietf.org>; Tue, 29 Apr 2014 04:27:35 -0700 (PDT)
Received: from [192.168.131.128] ([80.92.122.106]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Md3li-1WN1Ne47cI-00I9K5 for <wgchairs@ietf.org>; Tue, 29 Apr 2014 13:27:33 +0200
Message-ID: <535F8C16.20104@gmx.net>
Date: Tue, 29 Apr 2014 13:25:10 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: 'WG Chairs' <wgchairs@ietf.org>
Subject: Broken Links ?
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PRs08X6KBDWOUHmO1cbvVO70nOWciKUKD"
X-Provags-ID: V03:K0:nug8QcDevwwRJz4wUtsDR3M3vPzSvYRzFwYmd6qYOmfSCL0JbWo pEf9v/w1540/aYpKTtZGiOX7y7LdSbFZP1m8+FT/ubBTH/0V1Y0iSACBu9CbmlNi1BDNVcP 1Qbw6xMkFJXna4c5ptdTUOEeGmsU6zvU1zM1C3jvIVyrJtVaoJwYKHlsI8sCmE5VROfhd1G 5835J0blOyyy4zlAgNyBw==
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/OZqGGd16QOABTGnVKiu10828BCs
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Apr 2014 11:27:37 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PRs08X6KBDWOUHmO1cbvVO70nOWciKUKD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

several working group members in OAuth reported broken links to me
(links that point to documents on http://tools.ietf.org/) and I
sometimes also see 404 messages.

Have you experienced similar problems?

Ciao
Hannes


--PRs08X6KBDWOUHmO1cbvVO70nOWciKUKD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTX4wWAAoJEGhJURNOOiAtCycH/igNdek0lDQ4VLV/rMttolps
Dc8HdJAb22DEWi5qb5w96Tf6HJvaxmCXUDeZqf9HwZN4HeAUtnCD10ZjVlF9Jgkg
k8DdTBjAgKm0j0LrTxV4w1ZjMaNHbue+eszXJrfJi7kqIJi40T0lM9cpJ5GENen9
DM5tKy0Lnt6cY8L7A4wyWfkjYdpftvx1UkACNa1VE62tTONG0E3S0ICZP27phrjt
HMvvfGldJlQ86it/8K/zXKVFi6B2Prfp8cZ2t9i0lb3eVxtRCy5Gg+YVo/xvqVJe
g3t/Xz+vqiIrc3agI6Z0kfp3Oy5YYqmk1gOpDuwXSxdJbI1jhHxW4Bmk9R7Cefo=
=pTXC
-----END PGP SIGNATURE-----

--PRs08X6KBDWOUHmO1cbvVO70nOWciKUKD--


From nobody Tue Apr 29 08:56:33 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984E11A0910 for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 08:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2kEKEeFKWTU for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 08:56:31 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BABE31A08DB for <wgchairs@ietf.org>; Tue, 29 Apr 2014 08:56:30 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id d1so7681778wiv.1 for <wgchairs@ietf.org>; Tue, 29 Apr 2014 08:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=NMVoDl0fHK6MhRzgQohkUK0KeTja2eR2bOS/HFcyAqQ=; b=p85ayqFBxbJE5tXqCQOqDk1+Z4Q+EYhyUtO5ZCevLZANJaYkJhuW/dC9OXkhurYWDJ CyU1cmDjFQKCLeO2nZmyuWSUspK9SRXY6JdtmuH7UOlQtEwYZXoOMUcN6ny+nij8mjP6 BFZ9AusythP4piFEYFz+CDVtCSLUmVFPhbACSHR5Wb6PvAbFxhuyfQLXmjG7aPNj/wru TYthkTaKlk+SCKIN71l6hEbj5+HlWg7SEdqcRvOQyWvqs4dNIK4huZGhUlEtUywdxPpd yIsSMMb12nDjEtySHZiFWGjfUB17gRwbISK7JI9LagaEiQ0POAH2bkRoiUaPvWvpOr2r WZVw==
MIME-Version: 1.0
X-Received: by 10.194.57.77 with SMTP id g13mr221278wjq.42.1398786989115; Tue, 29 Apr 2014 08:56:29 -0700 (PDT)
Received: by 10.216.93.68 with HTTP; Tue, 29 Apr 2014 08:56:29 -0700 (PDT)
In-Reply-To: <rt-4.0.8-6005-1398692393-237.64766-6-0@www.ietf.org/rt>
References: <RT-Ticket-64766@www.ietf.org/rt> <CAHBDyN77nv4w4S2Fixc6nq8M0_J5u9oxYFz=W6dzNGEF5c0+Kw@mail.gmail.com> <rt-4.0.8-11594-1397260163-1819.64766-6-0@www.ietf.org/rt> <CAHBDyN7kt2+8OM+b5XUBzb-ixtJeRu=H=rCLxyw+bzQvX+V-Xg@mail.gmail.com> <rt-4.0.8-11205-1397260608-1739.64766-6-0@www.ietf.org/rt> <CAHBDyN6DkwPUOqZedkZOFv51Ba0+PWyfSUr11X2mTeDcDzKL9A@mail.gmail.com> <rt-4.0.8-9396-1398278215-462.64766-6-0@www.ietf.org/rt> <rt-4.0.8-6005-1398692393-237.64766-6-0@www.ietf.org/rt>
Date: Tue, 29 Apr 2014 10:56:29 -0500
Message-ID: <CAHBDyN7WbEzb07aYDRWAOvg7sOtdmGxetwyJsJkehbCnBQmarw@mail.gmail.com>
Subject: Fwd: [www.ietf.org/rt #64766] Email address associated with Shepherd field in the datatracker
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bacc0fa9a502a04f8307920
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/_uXG7t2aWIfn64UwgBaYWaDZVoQ
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Apr 2014 15:56:32 -0000

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

I thought this information might be helpful as I wasn't previously aware
that we can now manipulate the email addresses that are used by the tools.
 I was having problems getting notifications about non-WG documents that I
shepherd as an old work email was available in the dropdown when my name
was added as shepherd, so my old work email address was sometimes getting
put in the shepherd field (e.g., when an AD would add me as shepherd).
This also gives you the ability to associate different email addresses with
different roles/aliases.

Mary.

---------- Forwarded message ----------
From: Matt Larson via RT <ietf-action@ietf.org>
Date: Mon, Apr 28, 2014 at 8:39 AM
Subject: [www.ietf.org/rt #64766] Email address associated with Shepherd
field in the datatracker
To: mary.ietf.barnes@gmail.com


Greetings!

Please visit https://datatracker.ietf.org/accounts/profile/ and set your
email
address for the role(s) in question. This should resolve the issue, and the
settings will propagate to the tools servers.

Matt




--
--------------------------------------
Matthew Larson, Asst. IT Director
Association Management Solutions
Forum Management, Meeting and Event Planning
48377 Fremont Blvd., Suite 117, Fremont, CA 94538
http://www.amsl.com

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

<div dir=3D"ltr">I thought this information might be helpful as I wasn&#39;=
t previously aware that we can now manipulate the email addresses that are =
used by the tools. =C2=A0I was having problems getting notifications about =
non-WG documents that I shepherd as an old work email was available in the =
dropdown when my name was added as shepherd, so my old work email address w=
as sometimes getting put in the shepherd field (e.g., when an AD would add =
me as shepherd). =C2=A0 This also gives you the ability to associate differ=
ent email addresses with different roles/aliases.=C2=A0<div>
<br></div><div>Mary.<br><br><div class=3D"gmail_quote">---------- Forwarded=
 message ----------<br>From: <b class=3D"gmail_sendername">Matt Larson via =
RT</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf-action@ietf.org">ietf-a=
ction@ietf.org</a>&gt;</span><br>
Date: Mon, Apr 28, 2014 at 8:39 AM<br>Subject: [<a href=3D"http://www.ietf.=
org/rt">www.ietf.org/rt</a> #64766] Email address associated with Shepherd =
field in the datatracker<br>To: <a href=3D"mailto:mary.ietf.barnes@gmail.co=
m">mary.ietf.barnes@gmail.com</a><br>
<br><br>Greetings!<br>
<br>
Please visit <a href=3D"https://datatracker.ietf.org/accounts/profile/" tar=
get=3D"_blank">https://datatracker.ietf.org/accounts/profile/</a> and set y=
our email<br>
address for the role(s) in question. This should resolve the issue, and the=
<br>
settings will propagate to the tools servers.<br>
<br>
Matt<br>
<div><div class=3D"h5"><br>
<br><br>
<br>
</div></div>--<br>
--------------------------------------<br>
Matthew Larson, Asst. IT Director<br>
Association Management Solutions<br>
Forum Management, Meeting and Event Planning<br>
48377 Fremont Blvd., Suite 117, Fremont, CA 94538<br>
<a href=3D"http://www.amsl.com" target=3D"_blank">http://www.amsl.com</a><b=
r>
<br>
</div><br></div></div>

--047d7bacc0fa9a502a04f8307920--


From nobody Tue Apr 29 13:25:37 2014
Return-Path: <warren@kumari.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAE811A0958 for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 13:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVstpcvlGIQf for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 13:25:31 -0700 (PDT)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF031A094C for <wgchairs@ietf.org>; Tue, 29 Apr 2014 13:25:30 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id l18so744433wgh.26 for <wgchairs@ietf.org>; Tue, 29 Apr 2014 13:25:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Oi11Ma4n359meRZbO3Z8lRpNfHRQhveIe9u9XuNqC3k=; b=XmAFnD5/FHz0K/mRU/YYi3uHFbULJZm2b4JyaSsc7YaXRyhs1rEc3cu9pU8YlJdl+E K8q00w1/Gb4NipUB3aqqVrp9hz6jmt3ZaBKt8DVsNPN9XhgyFsv3GYtnvaw8gp7b5Uo+ KHvrs50uyfIZomUJjDloXZdtEwcBJYW6UTJB6Iu7beNrSnaD44nY76waUcbR169/m0kX qzc8DoZjGUv3Bn1IDe4quX/7+BB4pGJNAxcsKGG01jrvwW+/jWQYGRasxiANEQWue760 8Faw0y1sejNcWVABLULOsUWzP0WHbpFkSzy/+Ng5epDI76Srrn3k5Ww8/MwP4BkiYkUp 40EQ==
X-Gm-Message-State: ALoCoQlkdPFYfjd07O+i8ogIvJgsN/LuI2GRaWrmrip7S4FxY0oO05zYZ4Jzh/9T1zpRviCxI5O0
MIME-Version: 1.0
X-Received: by 10.180.105.132 with SMTP id gm4mr22273074wib.39.1398803129376;  Tue, 29 Apr 2014 13:25:29 -0700 (PDT)
Received: by 10.194.54.162 with HTTP; Tue, 29 Apr 2014 13:25:29 -0700 (PDT)
X-Originating-IP: [66.84.81.44]
In-Reply-To: <535F8C16.20104@gmx.net>
References: <535F8C16.20104@gmx.net>
Date: Tue, 29 Apr 2014 16:25:29 -0400
Message-ID: <CAHw9_i+6g23x88OqO-HPEG2iw6uyhcv3w+DkHbvuwPCYNFuZgA@mail.gmail.com>
Subject: Re: Broken Links ?
From: Warren Kumari <warren@kumari.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/PaiQbe8ZX7102NB12LQt33u6I5k
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Apr 2014 20:25:35 -0000

On Tue, Apr 29, 2014 at 7:25 AM, Hannes Tschofenig
<hannes.tschofenig@gmx.net> wrote:
> Hi all,
>
> several working group members in OAuth reported broken links to me
> (links that point to documents on http://tools.ietf.org/) and I
> sometimes also see 404 messages.
>
> Have you experienced similar problems?

I have not -- perhaps sharing some of hte links would be helpful?

W


>
> Ciao
> Hannes
>


From nobody Tue Apr 29 23:00:51 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F251A6EE0 for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 23:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RxRH6-DsXTU for <wgchairs@ietfa.amsl.com>; Tue, 29 Apr 2014 23:00:31 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE2F1A09C5 for <wgchairs@ietf.org>; Tue, 29 Apr 2014 23:00:30 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id mc6so889600lab.1 for <wgchairs@ietf.org>; Tue, 29 Apr 2014 23:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=eLQyvSixeXuooiR6tLjz1EhADMVOD1TYX3pQ9skX7Es=; b=0XzphpW6JAa6GcHT8L9goh6yJC9IibbUVQPGejdqO8TsS81LuNqd6950RaMhs+hrQI MzR3XdkOMlHWYiQ3+3DunVXj9QW6R1fyHxVFdMYnPRqBuJLRFFLxJdLpEu2lNmnvi9MX FE+JVxP2XfPk6HzRlciQ4f9XuGbR8n2DgTFKjNBslQuNWpPvIFvWuk+BDNxXsPYIw0AG /umdOVbdbnCL4CSyCnbm3VNwNfHl2+yS4qcTsXerHy2mNvmi3Z3GvAMGbjnJVea9RcHl 3iUGMmSaIXe0D+GSYbqAuMTf1vOtogz+ZRRVAlPUYZDvFUX6KiWdJ49l264DIINj+NaC aoaA==
X-Received: by 10.112.118.198 with SMTP id ko6mr1544283lbb.6.1398837628431; Tue, 29 Apr 2014 23:00:28 -0700 (PDT)
Received: from [192.168.250.144] ([194.100.71.98]) by mx.google.com with ESMTPSA id am9sm15521786lac.11.2014.04.29.23.00.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Apr 2014 23:00:27 -0700 (PDT)
Message-ID: <53609168.30804@gmail.com>
Date: Wed, 30 Apr 2014 09:00:08 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>, wgchairs@ietf.org
Subject: Re: 90th IETF - Working Group/BOF/IRTF Scheduling
References: <20140421222436.23895.20687.idtracker@ietfa.amsl.com> <535DDCAD.4040604@gmail.com> <535E8145.6000709@levkowetz.com>
In-Reply-To: <535E8145.6000709@levkowetz.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/wgchairs/Rkp5B_EYL4J_VQkxOyAlCBMHcns
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.15
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, 30 Apr 2014 06:00:38 -0000

Works now. Thanks!

- jOUNI



4/28/2014 7:26 PM, Henrik Levkowetz kirjoitti:
> Hi Jouni,
>
> On 2014-04-28 06:44 Jouni Korhonen said:
>>
>> I managed to successfully schedule my WGs (dime, radext, dmm). However,
>> I had to go back to do edits to some of the schedulings but clicking
>> "edit" on WG Chair Dashboard results in an internal server error. Anyone
>> else experienced the same?
>
> This was an error in the permissions checking for one particular path in
> to the edit view.  I've patched it to behave as intended, and it works
> for me when I go to /secr/sreq/mip4/edit/ as mip4 chair.  Could you check
> if it works for you now, please?
>
>
> Best regards,
> 	
> 	Henrik
>
>>
>> - Jouni
>>
>>
>>
>> 4/22/2014 1:24 AM, IETF Agenda kirjoitti:
>>>
>>> -----------------------------------------------------------------
>>> 90th IETF – Toronto, ON, Canada
>>> Meeting Dates: July 20 - 25, 2014
>>> -----------------------------------------------------------------
>>>
>>> We are accepting scheduling requests for all Working Groups, BOFs, and Research Groups starting today.
>>>
>>> NOTE: Please ensure your list of conflicts is complete and up to date prior to submitting your session request.
>>>
>>> The milestones and deadlines for scheduling-related activities are as follows:
>>> Cut-off dates are subject to change.
>>>
>>> •	2014-04-21 (Monday): Working Group and BOF scheduling begins. To request a Working Group session, use the IETF Meeting Session Request Tool.
>>> •	2014-06-06 (Friday): Cut-off date for requests to schedule Working Group meetings at UTC 23:59. To request a Working Group session, use the IETF Meeting Session Request Tool.
>>> •	2014-06-06 (Friday): Cut-off date for BOF proposal requests to Area Directors at UTC 23:59. To request a BOF, please see instructions on Requesting a BOF.
>>> •	2014-06-13 (Friday): Cut-off date for Area Directors to approve BOFs at UTC 23:59.
>>> •	2014-06-20 (Friday): Preliminary agenda published for comment.
>>> •	2014-06-23 (Monday): Cut-off date for requests to reschedule Working Group and BOF meetings UTC 23:59.
>>> •	2014-06-27 (Friday): Final agenda to be published.
>>> •	2014-07-07 (Monday): Draft Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>>> •	2014-07-14 (Monday): Revised Working Group agendas due by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>>> •	2014-08-15 (Friday): Proceedings submission cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>>> •	2014-09-05 (Friday): Proceedings submission corrections cutoff date by UTC 23:59, upload using IETF Meeting Materials Management Tool.
>>>
>>
>>

