
From aparsons@amsl.com  Mon Apr  1 08:04:18 2013
Return-Path: <aparsons@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBE9C21E8045 for <wgchairs@ietfa.amsl.com>; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wg-dzOLPG8yq for <wgchairs@ietfa.amsl.com>; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7C321E8041 for <wgchairs@ietf.org>; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 26B9B128BA1; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nol8ZYb379Jy; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
Received: from [64.170.98.186] (unknown [64.170.98.186]) by c8a.amsl.com (Postfix) with ESMTPSA id 084BB12460C; Mon,  1 Apr 2013 08:04:18 -0700 (PDT)
From: Ashlee Parsons <aparsons@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5017C556-B71C-425B-9E7E-EFC79665D202"
Subject: Second Request for IETF WG and BOF Session Minutes
Date: Mon, 1 Apr 2013 08:04:18 -0700
Message-Id: <04ACB876-2286-409D-B50D-EBF716F4FE73@amsl.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Mon, 01 Apr 2013 08:08:47 -0700
Cc: "irsg@irtf.org" <irsg@irtf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 15:04:19 -0000

--Apple-Mail=_5017C556-B71C-425B-9E7E-EFC79665D202
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

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

Groups I still need minutes from are:

Application Area:
	- AGGSRV
	- JSON
=20
General Area:
	- IPRBIS BOF

Internet Area:
	- HOMENET
	- LISP
	- NTP
	- TRILL

Operations & Management Area:
	- NETCONF
	- NETMOD
	- OPSANWB
	- OPSEC
	- V6OPS
	- WPKOPS

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

Routing Area:
	- L2VPN
	- L3VPN
	- MPLS
	- NVO3
	- RTGWG
	- SIDR

Security Area:
	- TLS

Transport Area:
	- NFSV4
	- PPSP
	- RMCAT

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



Ashlee Parsons
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=_5017C556-B71C-425B-9E7E-EFC79665D202
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div style=3D"margin: =
0in 0in 0.0001pt; "><div style=3D"margin: 0in 0in 0.0001pt; font-family: =
Courier; "><span style=3D"font-family: Arial, sans-serif; "><font =
color=3D"#030303">Dear WG Chairs and BOF =
Chairs,<o:p></o:p></font></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-family: Courier; "><span style=3D"font-family: Arial, =
sans-serif; "><font color=3D"#030303">&nbsp;</font></span></div><div =
style=3D"margin: 0in 0in 0.0001pt; "><font color=3D"#030303"><font =
class=3D"Apple-style-span"><span class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">I am in the process of =
compiling the proceedings for IETF 86 and we are still missing meeting =
minutes from various sessions. The cutoff for submissions =
is&nbsp;</span><font face=3D"Arial"><b>Friday, April 12th, =
2013</b></font><span class=3D"Apple-style-span" style=3D"font-family: =
Arial, sans-serif; ">,&nbsp;</span></font><font =
class=3D"Apple-style-span"><span class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">and correction submissions =
cutoff is&nbsp;<b>Wednesday, May 1st, 2013</b></span><span =
class=3D"Apple-style-span" style=3D"font-family: Arial, sans-serif; =
">.&nbsp; Please upload meeting minutes, as well as any presentations =
from your sessions, at your earliest convenience using the Meeting =
Materials Manager found here:&nbsp;</span></font><a =
href=3D"https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi" =
title=3D"blocked::https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.c=
gi" style=3D"font-family: Arial, sans-serif; =
">https://pub.ietf.org/proceedings/</a><font class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">.&nbsp; Alternatively, you =
are welcome to send them to&nbsp;</font><a =
href=3D"mailto:proceedings@ietf.org" style=3D"font-family: Arial, =
sans-serif; ">proceedings@ietf.org</a><font class=3D"Apple-style-span" =
style=3D"font-family: Arial, sans-serif; ">&nbsp;or&nbsp;<a =
href=3D"mailto:aparsons@amsl.com">aparsons@amsl.com</a></font><span =
style=3D"font-family: Arial, sans-serif; ">&nbsp;for manual =
posting.</span></font></div></div></div></blockquote><br>Groups I still =
need minutes from are:</div><div><br></div><div>Application =
Area:<br><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>- AGGSRV</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- =
JSON</div><div>&nbsp;</div><div>General Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- IPRBIS =
BOF</div><div><br></div><div>Internet Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
HOMENET</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>- NTP</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
TRILL</div><div><br></div><div>Operations &amp; Management =
Area:</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>- NETCONF</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- NETMOD</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
OPSANWB</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>- OPSEC</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- V6OPS</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
WPKOPS</div><div><br></div><div>Real-Time Applications &amp; =
Infrastructure Area:</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- AVTCORE</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
AVTEXT</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>- INSIPID</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- =
MMUSIC</div><div><br></div><div>Routing Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
L2VPN</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>- L3VPN</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- MPLS</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
NVO3</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">	</span>- RTGWG</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- =
SIDR</div><div><br></div><div>Security Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
TLS</div><div><br></div><div>Transport Area:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- =
NFSV4</div><div><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>- PPSP</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>- =
RMCAT</div><div><br></div><div><a =
href=3D"https://datatracker.ietf.org/meeting/86/materials.html">https://da=
tatracker.ietf.org/meeting/86/materials.html</a></div><div><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div style=3D"margin: 0in 0in =
0.0001pt; "><div style=3D"margin: 0in 0in 0.0001pt; =
"><br></div></div></div></div><div><br></div><br><div =
apple-content-edited=3D"true"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Ashlee Parsons</div><div>IETF Registrar</div><div>48377 Fremont =
Blvd, Ste. 117</div><div>Fremont, CA =
94538</div><div><br></div><div>Association Management Solutions =
(AMS)</div><div>Forum Management, Meeting and Event =
Planning</div><div><a =
href=3D"http://www.amsl.com/">www.amsl.com</a></div></div></div></div></di=
v><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; "><div><br></div></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_5017C556-B71C-425B-9E7E-EFC79665D202--

From henrik@levkowetz.com  Wed Apr  3 06:51:11 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19D9121F8A91 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 06:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.2
X-Spam-Level: 
X-Spam-Status: No, score=-102.2 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4A-JFO2Lhni for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 06:51:07 -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 D15A121F8DD4 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 06:51:06 -0700 (PDT)
Received: from [2a01:3f0:1:0:4ea:d07:2364:7570] (port=51676 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNO5X-0002oK-NE; Wed, 03 Apr 2013 15:50:56 +0200
Message-ID: <515C33BF.9040105@levkowetz.com>
Date: Wed, 03 Apr 2013 15:50:55 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4ea:d07:2364:7570
X-SA-Exim-Rcpt-To: wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Is a new state needed in the WG states for drafts?
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)
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 13:51:11 -0000

Hi,

During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
talk about how to best use the WG State tracking which is currently
available in the datatracker.

I think we sorted out most of the things they would like to do, but
there were at least one issue which remained, which may need some
tweaking to the states and code.

Refering to the state summary at
  https://datatracker.ietf.org/help/state/draft/stream-ietf/ :

The only WG state which exists before "Adopted by a WG"/"WG Document"
is "Call For Adoption By WG Issued".  But in the case of MPLS, there
can be a rather large number of documents which are under consideration
for adoption as WG documents, without an actual call for adoption having
been issued yet.

Considering that every WG can choose which, if any, of the states to use,
what do you think about adding another state which may be used before the
"Call For Adoption By WG Issued" state, named something like "Candidate
for WG Adoption"?


Best regards,

	Henrik
	(Datatracker Maintenance Hat)



From cabo@tzi.org  Wed Apr  3 07:00:56 2013
Return-Path: <cabo@tzi.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D930121F8E47 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1ikY+D8+C1J for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:00:56 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 25A9021F8E3C for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r33E0mfo003814; Wed, 3 Apr 2013 16:00:48 +0200 (CEST)
Received: from [192.168.217.105] (p548925A8.dip.t-dialin.net [84.137.37.168]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id D2690389D; Wed,  3 Apr 2013 16:00:47 +0200 (CEST)
Subject: Re: Is a new state needed in the WG states for drafts?
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
Date: Wed, 3 Apr 2013 16:00:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D892249-990D-42B8-88DE-BFA361C008EC@tzi.org>
References: <515C33BF.9040105@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.1503)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:00:57 -0000

On Apr 3, 2013, at 15:50, Henrik Levkowetz <henrik@levkowetz.com> wrote:

> "Candidate
> for WG Adoption"?

That is state that would be nice to record, e.g., when there has been =
in-room consensus to collect reviews and then issue the call for =
adoption.

Gr=FC=DFe, Carsten


From ynir@checkpoint.com  Wed Apr  3 07:09:51 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5EE21F8C10 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqQSlLuY5pJS for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:09:51 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0B79A21F8BC4 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:09:49 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r33E9iIw000819; Wed, 3 Apr 2013 17:09:44 +0300
X-CheckPoint: {515C3625-2-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Wed, 3 Apr 2013 17:09:43 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJX2ZdoMGmSXkqmZ6BGwUqs4ZjEVBcAgAAChYA=
Date: Wed, 3 Apr 2013 14:09:42 +0000
Message-ID: <AF3D4152-6F04-48A0-9829-9204B546BED3@checkpoint.com>
References: <515C33BF.9040105@levkowetz.com> <3D892249-990D-42B8-88DE-BFA361C008EC@tzi.org>
In-Reply-To: <3D892249-990D-42B8-88DE-BFA361C008EC@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.24.145]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F94ED374C54FB142BED0FC1FB10A0F03@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:09:51 -0000

On Apr 3, 2013, at 5:00 PM, Carsten Bormann <cabo@tzi.org>
 wrote:

> On Apr 3, 2013, at 15:50, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>=20
>> "Candidate
>> for WG Adoption"?
>=20
> That is state that would be nice to record, e.g., when there has been in-=
room consensus to collect reviews and then issue the call for adoption.

+1=20

"Call issued" implies that a decision needs to be reached soon. It also imp=
lies that it's inappropriate to rev the doc, because people are answering a=
 question about that version. This is only an implication - documents somet=
imes get revved even during LC, but it does imply a stable version.

So yes, marking something as under consideration (with a mail to the mailin=
g list) would be great.

Yoav



From suresh.krishnan@ericsson.com  Wed Apr  3 07:18:52 2013
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A37521F8E71 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hjJOaJTwB5X5 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:18:52 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id EE75321F8E49 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:18:51 -0700 (PDT)
X-AuditID: c6180641-b7faf6d00000096b-f3-515c3a4b61cb
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 1D.C8.02411.B4A3C515; Wed,  3 Apr 2013 16:18:51 +0200 (CEST)
Received: from eusaamw0712.eamcs.ericsson.se (147.117.20.181) by EUSAAHC003.ericsson.se (147.117.188.81) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Apr 2013 10:18:46 -0400
Received: from [142.133.180.233] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.181) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 3 Apr 2013 10:18:46 -0400
Message-ID: <515C39B3.9070807@ericsson.com>
Date: Wed, 3 Apr 2013 10:16:19 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHLMWRmVeSWpSXmKPExsUyuXRPoK63VUygwbddyhbNbYfYLP7vn8Lo wOSxZMlPJo/l83cwBjBFcdmkpOZklqUW6dslcGX0vk4uWMVSMW3qJ/YGxh3MXYycHBICJhJn 1nYwQthiEhfurWfrYuTiEBI4yijxYsltRghnN5CzcjcThLONUWLV3x1sIC28AtoSpyeeZAGx WQRUJCYs/cIOYrMBjd2w8zMTiC0qECax98I0qHpBiZMzn4DViwD19t34wwpiMwsoStyd8B+s XljAXuJPVyPYeUICOhJ9W66D1XAK6Eq83XgK6lRJiS0v2tkhevUkplxtYYSw5SW2v50D1asp sXXNd9YJjMKzkKyehaRlFpKWBYzMqxg5SotTy3LTjQw3MQLD+JgEm+MOxgWfLA8xSnOwKInz hrpeCBASSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAqB7HEtOhsjYu0teKd8HZW70a4bMZCqfV Ze1iFDCyvePVffLF9qLuaulzbA2FvX6eepbXGX71Oeiu+MXvE71B7c6NHvGwCK5KV1mRNXF/ ni9o+aq+/JnBn8P7Ip5xSHJ0FfY8+/bTfsKaD2xX1zxeej3n90VrWY1Peemvb3Ob/vFPlOtd 8e6PEktxRqKhFnNRcSIAt0XV6TECAAA=
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:18:52 -0000

Hi Henrik,

On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?

That sounds like a great idea. Personally, I would prefer something more
generic like "Chair is watching" (similar to AD is watching) as there
are more reasons to closely watch a document than just eying adoption.

Thanks
Suresh



From acmorton@att.com  Wed Apr  3 07:29:25 2013
Return-Path: <acmorton@att.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0046221F8C6F for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vc0w7wOAAeYZ for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:29:24 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 81B8621F8617 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:29:24 -0700 (PDT)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id 755B21208F2; Wed,  3 Apr 2013 10:29:28 -0400 (EDT)
Received: from njfpsrvexg1.research.att.com (njfpsrvexg1.research.att.com [135.207.177.20]) by mail-blue.research.att.com (Postfix) with ESMTP id 30C23EF69C; Wed,  3 Apr 2013 10:29:24 -0400 (EDT)
Received: from concierge.research.att.com (135.207.179.20) by njfpsrvexg1.research.att.com (135.207.177.20) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 3 Apr 2013 10:29:24 -0400
Received: from njfpsrvexg7.research.att.com ([fe80:0000:0000:0000:3598:75fe:180.0.146.153]) by concierge.research.att.com ([135.207.24.83]) with mapi; Wed, 3 Apr 2013 10:29:23 -0400
From: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Henrik Levkowetz <henrik@levkowetz.com>
Date: Wed, 3 Apr 2013 10:29:22 -0400
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: Ac4wdjFba3c98cScSVaZLWjPI+1RkgAAVKeA
Message-ID: <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com>
In-Reply-To: <515C39B3.9070807@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:29:25 -0000

+1 for Chair is Watching, it's sufficiently nebulous.
Al

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Wednesday, April 03, 2013 10:16 AM
> To: Henrik Levkowetz
> Cc: WG Chairs
> Subject: Re: Is a new state needed in the WG states for drafts?
>=20
> Hi Henrik,
>=20
> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
> > Considering that every WG can choose which, if any, of the states to
> use,
> > what do you think about adding another state which may be used before
> the
> > "Call For Adoption By WG Issued" state, named something like "Candidate
> > for WG Adoption"?
>=20
> That sounds like a great idea. Personally, I would prefer something more
> generic like "Chair is watching" (similar to AD is watching) as there
> are more reasons to closely watch a document than just eying adoption.
>=20
> Thanks
> Suresh
>=20


From alexey.melnikov@isode.com  Wed Apr  3 07:33:44 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5525521F8700 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuXKocCoj05V for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:33:43 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id AE98621F86C1 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:33:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1364999622; d=isode.com; s=selector; i=@isode.com; bh=EBy0xrQPGOU5mQPSoyy3BefumzSw/FlGAmks/Uy3nCU=; 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=M0eJ/Jonm3rEQ+0LoV7/6b1CwR9lu5R26FRRV3fF9xplfbIGGfyx/YIxcfWBAjKMdWoH89 Q7XI6AEShog5A3JM1siPCF0uPCmg/FZh2H8BDbXjOuTO6Qa3Hj46H37K+MXFNfp0YjmeMG PkBZYAnA0mP8biKOnNviRi2K30t2FMc=;
Received: from [188.28.63.7] (188.28.63.7.threembb.co.uk [188.28.63.7])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UVw9xQA4j8W0@statler.isode.com>; Wed, 3 Apr 2013 15:33:42 +0100
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com>
In-Reply-To: <515C39B3.9070807@ericsson.com>
Message-Id: <94B31F79-0B69-4A0E-877C-A8049446A3FA@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Is a new state needed in the WG states for drafts?
Date: Wed, 3 Apr 2013 15:35:43 +0100
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:33:44 -0000

On 3 Apr 2013, at 15:16, Suresh Krishnan <suresh.krishnan@ericsson.com> wrot=
e:

> Hi Henrik,
>=20
> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
>> Considering that every WG can choose which, if any, of the states to use,=

>> what do you think about adding another state which may be used before the=

>> "Call For Adoption By WG Issued" state, named something like "Candidate
>> for WG Adoption"?
>=20
> That sounds like a great idea. Personally, I would prefer something more
> generic like "Chair is watching" (similar to AD is watching) as there
> are more reasons to closely watch a document than just eying adoption.

I like this as well.


From yaakov_s@rad.com  Wed Apr  3 07:46:34 2013
Return-Path: <yaakov_s@rad.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F73821F8BBB for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrY2dNhEnsBR for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:34 -0700 (PDT)
Received: from rad.co.il (mailrelay01.rad.co.il [62.0.23.252]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6EE21F8C74 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:46:31 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay01 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 3 Apr 2013 17:44:53 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Wed, 3 Apr 2013 17:46:23 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJTIpax1M1SNEeiQRg8tqU78pjEWG+AgAADpgCAADYRkA==
Date: Wed, 3 Apr 2013 14:46:23 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904CF1D47@EXRAD5.ad.rad.co.il>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com>
In-Reply-To: <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0C0206.515C40C4.0045,ss=1,fgs=0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:46:34 -0000

Actually, why is the WG chair important here ?
Adopting a draft is a WG decision.

I think we could have a state called something like "has been presented to =
the WG",
and perhaps a dead-end state "WG not interested in adopting"=20
to explain why IDs didn't make it to "Call For Adoption".

Y(J)S

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of MORTON JR., ALFRED C (AL)
Sent: 03 April, 2013 17:29
To: Suresh Krishnan; Henrik Levkowetz
Cc: WG Chairs
Subject: RE: Is a new state needed in the WG states for drafts?

+1 for Chair is Watching, it's sufficiently nebulous.
Al

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Wednesday, April 03, 2013 10:16 AM
> To: Henrik Levkowetz
> Cc: WG Chairs
> Subject: Re: Is a new state needed in the WG states for drafts?
>=20
> Hi Henrik,
>=20
> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
> > Considering that every WG can choose which, if any, of the states to
> use,
> > what do you think about adding another state which may be used before
> the
> > "Call For Adoption By WG Issued" state, named something like "Candidate
> > for WG Adoption"?
>=20
> That sounds like a great idea. Personally, I would prefer something more
> generic like "Chair is watching" (similar to AD is watching) as there
> are more reasons to closely watch a document than just eying adoption.
>=20
> Thanks
> Suresh
>=20


From henrik@levkowetz.com  Wed Apr  3 07:47:57 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7923521F8DEF for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rewa+TrCgV5V for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:47:57 -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 B557121F8DD6 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:47:56 -0700 (PDT)
Received: from [2a01:3f0:1:0:4ea:d07:2364:7570] (port=52027 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNOyc-0004T5-Oj; Wed, 03 Apr 2013 16:47:51 +0200
Message-ID: <515C4116.4050604@levkowetz.com>
Date: Wed, 03 Apr 2013 16:47:50 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com>
In-Reply-To: <515C39B3.9070807@ericsson.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4ea:d07:2364:7570
X-SA-Exim-Rcpt-To: suresh.krishnan@ericsson.com, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Is a new state needed in the WG states for drafts?
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)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:47:57 -0000

Hi Suresh,

On 2013-04-03 16:16 Suresh Krishnan said:
> Hi Henrik,
> 
> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
>> Considering that every WG can choose which, if any, of the states to use,
>> what do you think about adding another state which may be used before the
>> "Call For Adoption By WG Issued" state, named something like "Candidate
>> for WG Adoption"?
> 
> That sounds like a great idea. Personally, I would prefer something more
> generic like "Chair is watching" (similar to AD is watching) as there
> are more reasons to closely watch a document than just eying adoption.

That sounds like another good pre-WG-document state to have.  I think we
could add both "Chair is watching" and "Candidate for WG Adoption" --
sometimes being specific about the latter is good.


Best regards,

	Henrik




From keith.drage@alcatel-lucent.com  Wed Apr  3 07:52:08 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F2921F8C6F for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UdY-PNRsK8g for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:52:07 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 20D4521F8AE7 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:52:07 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r33Eq5T5007362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 3 Apr 2013 09:52:05 -0500 (CDT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id r33Eq4B1009103 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Apr 2013 10:52:04 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 3 Apr 2013 10:52:04 -0400
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Wed, 3 Apr 2013 16:51:33 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, WG Chairs <wgchairs@ietf.org>
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJaJ3KiUfNQlk2gUkXHj41y15jElEqA
Date: Wed, 3 Apr 2013 14:51:32 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B01FD8A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <515C33BF.9040105@levkowetz.com>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:52:08 -0000

What is the real problem here?

Is it really that we are missing a state, or are we just missing a potentia=
l many to one association with a charter milestone?

Regards

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Henrik Levkowetz
> Sent: 03 April 2013 14:51
> To: WG Chairs
> Subject: Is a new state needed in the WG states for drafts?
>=20
> Hi,
>=20
> During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
> talk about how to best use the WG State tracking which is currently
> available in the datatracker.
>=20
> I think we sorted out most of the things they would like to do, but
> there were at least one issue which remained, which may need some
> tweaking to the states and code.
>=20
> Refering to the state summary at
>   https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
>=20
> The only WG state which exists before "Adopted by a WG"/"WG Document"
> is "Call For Adoption By WG Issued".  But in the case of MPLS, there
> can be a rather large number of documents which are under consideration
> for adoption as WG documents, without an actual call for adoption having
> been issued yet.
>=20
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?
>=20
>=20
> Best regards,
>=20
> 	Henrik
> 	(Datatracker Maintenance Hat)
>=20


From loa@pi.nu  Wed Apr  3 07:53:35 2013
Return-Path: <loa@pi.nu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B3B21F8B11 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbfbvh7uoraK for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:53:34 -0700 (PDT)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 3EBF621F8A2A for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:53:20 -0700 (PDT)
Received: from [192.168.10.101] (unknown [121.54.51.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 7661C824AC; Wed,  3 Apr 2013 16:53:15 +0200 (CEST)
Message-ID: <515C4254.9000105@pi.nu>
Date: Wed, 03 Apr 2013 16:53:08 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:53:35 -0000

Henrik,

the time spent in Oralndo using the ID tracker for wg document were
well spent.

In thinking about we said and wished for there are a couple of thing
just looks more important than others

1. The grabbing state - when the discussions with neighbor wg is done
    and we all agree to which wg this document belongs, but before we at
    all decided that we want to go ahead with the document.
    Henrik call this "Candidate for WG Adoption". Suresh call it
    "Chair is watching", I can live with both, the only reason not to
    call "Chair is watching" is that is similar to "AD is watching" and
    "AD is watching" has somewhat of a negative flavor, often used as
    an escape state when "sending it back to the wg".
    I really like to have both states - but if I have to make the choice
    I'd prefer something that announces "this is our document, talk to
    the wg (chairs) if you think otherwise".
    The point I'm trying to make is that "WG chair watching" is too
    layed back, - yes I'm watching but I do not care that much. We
    could do "Being Prepared for WG Adoption", to indicate that we are
    putting a lot of effort. Then the WG's can decide how much process
    is needed in that state.

2. The dates that gets into the log if I update tags only - just now
    it seems that the date is the date when the latest state changed
    happened.

3. The possibility for chairs (modulo AD support) to delegate
    "chair-like" rights to wg secretaries.

4. The new tag "New ID needed" (when cleared) bumps the document into
    "AD is watching", well I hope they do, but this should really be
    "Chair is Watching" or better "Waiting for WG chair go aheaad".

/Loa


On 2013-04-03 15:50, Henrik Levkowetz wrote:
> Hi,
>
> During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
> talk about how to best use the WG State tracking which is currently
> available in the datatracker.
>
> I think we sorted out most of the things they would like to do, but
> there were at least one issue which remained, which may need some
> tweaking to the states and code.
>
> Refering to the state summary at
>    https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
>
> The only WG state which exists before "Adopted by a WG"/"WG Document"
> is "Call For Adoption By WG Issued".  But in the case of MPLS, there
> can be a rather large number of documents which are under consideration
> for adoption as WG documents, without an actual call for adoption having
> been issued yet.
>
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?
>
>
> Best regards,
>
> 	Henrik
> 	(Datatracker Maintenance Hat)
>
>

-- 


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

From Ted.Lemon@nominum.com  Wed Apr  3 07:55:20 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F071021F8D11 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uk2M5lyvtFZN for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 07:55:20 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 6985F21F8AF0 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:55:20 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUVxC2DWGzc0ccv9KsQdrCUS4qiJhIZNV@postini.com; Wed, 03 Apr 2013 07:55:20 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1095F108A99 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 07:55:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 09E2F19005C; Wed,  3 Apr 2013 07:55:20 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 3 Apr 2013 07:55:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Yaakov Stein <yaakov_s@rad.com>
Subject: Re: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJPrsVCHVe0XEKa/GiJ8Hbg15jFABOAgAADpQCAAATBgIAAAoAA
Date: Wed, 3 Apr 2013 14:55:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077512F62A@mbx-01.win.nominum.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com> <07F7D7DED63154409F13298786A2ADC904CF1D47@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904CF1D47@EXRAD5.ad.rad.co.il>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F9CAF168329A1143B844AA802D6C1095@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 14:55:21 -0000

On Apr 3, 2013, at 10:46 AM, Yaakov Stein <yaakov_s@rad.com> wrote:
> I think we could have a state called something like "has been presented t=
o the WG",
> and perhaps a dead-end state "WG not interested in adopting"=20
> to explain why IDs didn't make it to "Call For Adoption".

Unfortunately I don't think that works, because until a draft has been adop=
ted it's an individual submission, and hence subject to working group shopp=
ing.  I suppose having a list of the working groups to which it has been sh=
opped in the history might be useful... :)


From henrik@levkowetz.com  Wed Apr  3 08:04:51 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9325821F8C5C for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.36
X-Spam-Level: 
X-Spam-Status: No, score=-102.36 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJoOhvDPEWUq for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:04:51 -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 4BB2621F8DA0 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 08:04:50 -0700 (PDT)
Received: from [2a01:3f0:1:0:4ea:d07:2364:7570] (port=52120 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNPEy-0005B5-Be; Wed, 03 Apr 2013 17:04:44 +0200
Message-ID: <515C450C.6060607@levkowetz.com>
Date: Wed, 03 Apr 2013 17:04:44 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
References: <515C33BF.9040105@levkowetz.com> <515C4254.9000105@pi.nu>
In-Reply-To: <515C4254.9000105@pi.nu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4ea:d07:2364:7570
X-SA-Exim-Rcpt-To: loa@pi.nu, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Is a new state needed in the WG states for drafts?
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)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 15:04:51 -0000

Hi Loa,

On 2013-04-03 16:53 Loa Andersson said:
> Henrik,
> 
> the time spent in Oralndo using the ID tracker for wg document were
> well spent.
> 
> In thinking about we said and wished for there are a couple of thing
> just looks more important than others
> 
> 1. The grabbing state - when the discussions with neighbor wg is done
>     and we all agree to which wg this document belongs, but before we at
>     all decided that we want to go ahead with the document.
>     Henrik call this "Candidate for WG Adoption". Suresh call it
>     "Chair is watching", I can live with both, the only reason not to
>     call "Chair is watching" is that is similar to "AD is watching" and
>     "AD is watching" has somewhat of a negative flavor, often used as
>     an escape state when "sending it back to the wg".
>     I really like to have both states - but if I have to make the choice
>     I'd prefer something that announces "this is our document, talk to
>     the wg (chairs) if you think otherwise".
>     The point I'm trying to make is that "WG chair watching" is too
>     layed back, - yes I'm watching but I do not care that much. We
>     could do "Being Prepared for WG Adoption", to indicate that we are
>     putting a lot of effort. Then the WG's can decide how much process
>     is needed in that state.

Yes.  I think this is desirable, and needs discussion.

> 2. The dates that gets into the log if I update tags only - just now
>     it seems that the date is the date when the latest state changed
>     happened.

This one I consider a bug -- I don't think we need to discuss it :-)

> 3. The possibility for chairs (modulo AD support) to delegate
>     "chair-like" rights to wg secretaries.

That should already be in place -- see my separate mail about assigning
WG delegates -- there's already a tab in the chair view of a WG's page
to do that.

> 4. The new tag "New ID needed" (when cleared) bumps the document into
>     "AD is watching", well I hope they do, but this should really be
>     "Chair is Watching" or better "Waiting for WG chair go aheaad".

Also a bug, I think -- I was going to look at the code to find out why
it was doing that.


Best regards,

	Henrik

> /Loa
> 
> 
> On 2013-04-03 15:50, Henrik Levkowetz wrote:
>> Hi,
>>
>> During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
>> talk about how to best use the WG State tracking which is currently
>> available in the datatracker.
>>
>> I think we sorted out most of the things they would like to do, but
>> there were at least one issue which remained, which may need some
>> tweaking to the states and code.
>>
>> Refering to the state summary at
>>    https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
>>
>> The only WG state which exists before "Adopted by a WG"/"WG Document"
>> is "Call For Adoption By WG Issued".  But in the case of MPLS, there
>> can be a rather large number of documents which are under consideration
>> for adoption as WG documents, without an actual call for adoption having
>> been issued yet.
>>
>> Considering that every WG can choose which, if any, of the states to use,
>> what do you think about adding another state which may be used before the
>> "Call For Adoption By WG Issued" state, named something like "Candidate
>> for WG Adoption"?
>>
>>
>> Best regards,
>>
>> 	Henrik
>> 	(Datatracker Maintenance Hat)
>>
>>
> 

From ynir@checkpoint.com  Wed Apr  3 08:07:04 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2B021F8E62 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCpnjq8NkgYR for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:07:04 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id B1E2B21F8DDD for <wgchairs@ietf.org>; Wed,  3 Apr 2013 08:07:03 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r33F6jCa017618; Wed, 3 Apr 2013 18:06:45 +0300
X-CheckPoint: {515C4383-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Wed, 3 Apr 2013 18:06:45 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Subject: Re: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJX2ZdoMGmSXkqmZ6BGwUqs4ZjEYkYAgAAERYA=
Date: Wed, 3 Apr 2013 15:06:44 +0000
Message-ID: <0283A40A-E408-43E9-9252-F69784479465@checkpoint.com>
References: <515C33BF.9040105@levkowetz.com> <949EF20990823C4C85C18D59AA11AD8B01FD8A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B01FD8A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.24.145]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <993F87CFCE66FB4D8B6AA51345696204@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 15:07:04 -0000

Sometimes a draft presents a new idea to the group (within the general stuf=
f that the group is working on), but there still isn't a milestone in the c=
harter.

In that case, the chairs usually ask a twofold question: (1) Do we want to =
work on FOO?, and (2) Is draft-snooki-ipv8m-foo a good starting point?

In that case it would be good to be able to mark the draft.

The other case is when FOO is already on the charter, and we are considerin=
g draft-snooki as a solution, in which case the only question is (2).

Either way marking the draft as "chair is watching" or "under consideration=
" sends a signal to the authors to stop shopping around (for now), and to o=
ther chairs to not call for this draft's adoption without first talking to =
the working group whose chair has set the state.

Yoav

=20
On Apr 3, 2013, at 5:51 PM, "DRAGE, Keith (Keith)" <keith.drage@alcatel-luc=
ent.com>
 wrote:

> What is the real problem here?
>=20
> Is it really that we are missing a state, or are we just missing a potent=
ial many to one association with a charter milestone?
>=20
> Regards
>=20
> Keith
>=20
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of Henrik Levkowetz
>> Sent: 03 April 2013 14:51
>> To: WG Chairs
>> Subject: Is a new state needed in the WG states for drafts?
>>=20
>> Hi,
>>=20
>> During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
>> talk about how to best use the WG State tracking which is currently
>> available in the datatracker.
>>=20
>> I think we sorted out most of the things they would like to do, but
>> there were at least one issue which remained, which may need some
>> tweaking to the states and code.
>>=20
>> Refering to the state summary at
>>  https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
>>=20
>> The only WG state which exists before "Adopted by a WG"/"WG Document"
>> is "Call For Adoption By WG Issued".  But in the case of MPLS, there
>> can be a rather large number of documents which are under consideration
>> for adoption as WG documents, without an actual call for adoption having
>> been issued yet.
>>=20
>> Considering that every WG can choose which, if any, of the states to use=
,
>> what do you think about adding another state which may be used before th=
e
>> "Call For Adoption By WG Issued" state, named something like "Candidate
>> for WG Adoption"?
>>=20
>>=20
>> Best regards,
>>=20
>> 	Henrik
>> 	(Datatracker Maintenance Hat)
>>=20
>=20
>=20
> Email secured by Check Point


From yaakov_s@rad.com  Wed Apr  3 08:08:40 2013
Return-Path: <yaakov_s@rad.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F5421F8AE7 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwfzIpPknvCl for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:08:40 -0700 (PDT)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 4570721F8BE2 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 08:08:33 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 3 Apr 2013 16:27:35 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Wed, 3 Apr 2013 18:08:30 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJTIpax1M1SNEeiQRg8tqU78pjEWG+AgAADpgCAADYRkP//0TAAgAAzsjA=
Date: Wed, 3 Apr 2013 15:08:29 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC904CF1E94@EXRAD5.ad.rad.co.il>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com> <07F7D7DED63154409F13298786A2ADC904CF1D47@EXRAD5.ad.rad.co.il> <8D23D4052ABE7A4490E77B1A012B63077512F62A@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077512F62A@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.140.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A0C0201.515C45EE.019F,ss=1,fgs=0
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 15:08:40 -0000

Why do you care if the same draft appears as "presented" in >1 WG ?

The problem I have is knowing if a given draft is known to a given WG,
if it has been discussed, and thereafter if it is being considered or not.

Y(J)S



-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: 03 April, 2013 17:55
To: Yaakov Stein
Cc: Henrik Levkowetz; WG Chairs
Subject: Re: Is a new state needed in the WG states for drafts?

On Apr 3, 2013, at 10:46 AM, Yaakov Stein <yaakov_s@rad.com> wrote:
> I think we could have a state called something like "has been presented t=
o the WG",
> and perhaps a dead-end state "WG not interested in adopting"=20
> to explain why IDs didn't make it to "Call For Adoption".

Unfortunately I don't think that works, because until a draft has been adop=
ted it's an individual submission, and hence subject to working group shopp=
ing.  I suppose having a list of the working groups to which it has been sh=
opped in the history might be useful... :)


From henrik@levkowetz.com  Wed Apr  3 08:15:43 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDC6B21F8EE8 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eL3a8ixwXeRl for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 08:15:43 -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 2482321F8AE7 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 08:15:43 -0700 (PDT)
Received: from [2a01:3f0:1:0:4ea:d07:2364:7570] (port=52217 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNPPR-0006jJ-3o; Wed, 03 Apr 2013 17:15:33 +0200
Message-ID: <515C4794.90804@levkowetz.com>
Date: Wed, 03 Apr 2013 17:15:32 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yaakov Stein <yaakov_s@rad.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com> <07F7D7DED63154409F13298786A2ADC904CF1D47@EXRAD5.ad.rad.co.il> <8D23D4052ABE7A4490E77B1A012B63077512F62A@mbx-01.win.nominum.com> <07F7D7DED63154409F13298786A2ADC904CF1E94@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC904CF1E94@EXRAD5.ad.rad.co.il>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4ea:d07:2364:7570
X-SA-Exim-Rcpt-To: yaakov_s@rad.com, Ted.Lemon@nominum.com, wgchairs@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Is a new state needed in the WG states for drafts?
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)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 15:15:43 -0000

Hi Yaakov,

On 2013-04-03 17:08 Yaakov Stein said:
> Why do you care if the same draft appears as "presented" in >1 WG ?
> 
> The problem I have is knowing if a given draft is known to a given WG,
> if it has been discussed, and thereafter if it is being considered or not.

Maybe the issue about your proposal is that we don't have per-WG states
for drafts, which would be needed in order to keep a 'WG foo isn't interested'
state visible when another WG chair has changed the state to 'Candidate for
WG Adoption'.

The document history will show who set a given state, but the state
indication will only show one current state, not one per WG.

Using the document history, it's perfectly possible to see that chair  Foo
set 'Candidate for WG Adoption' at some date, then removed it later (if
the WG determined it wasn't interested), possibly followed by other similar
sequences for other WGs.


Best regards,

	Henrik



> Y(J)S
> 
> 
> 
> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com] 
> Sent: 03 April, 2013 17:55
> To: Yaakov Stein
> Cc: Henrik Levkowetz; WG Chairs
> Subject: Re: Is a new state needed in the WG states for drafts?
> 
> On Apr 3, 2013, at 10:46 AM, Yaakov Stein <yaakov_s@rad.com> wrote:
>> I think we could have a state called something like "has been presented to the WG",
>> and perhaps a dead-end state "WG not interested in adopting" 
>> to explain why IDs didn't make it to "Call For Adoption".
> 
> Unfortunately I don't think that works, because until a draft has been adopted it's an individual submission, and hence subject to working group shopping.  I suppose having a list of the working groups to which it has been shopped in the history might be useful... :)
> 
> 

From lee.howard@twcable.com  Wed Apr  3 09:01:34 2013
Return-Path: <lee.howard@twcable.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E057421F8F25 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIWBR-vvtiUY for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:01:34 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8AF21F8EA0 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:01:34 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.87,402,1363147200"; d="scan'208";a="51333925"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 03 Apr 2013 12:01:08 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.95]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Wed, 3 Apr 2013 12:01:33 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Date: Wed, 3 Apr 2013 12:01:34 -0400
Subject: Re: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: Ac4whIL5wMsk9Hw4TcOvpTgqktN/sA==
Message-ID: <CD81C8FA.18576%lee.howard@twcable.com>
In-Reply-To: <515C4116.4050604@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:01:35 -0000

On 4/3/13 10:47 AM, "Henrik Levkowetz" <henrik@levkowetz.com> wrote:

>Hi Suresh,
>
>On 2013-04-03 16:16 Suresh Krishnan said:
>> Hi Henrik,
>>
>> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
>>> Considering that every WG can choose which, if any, of the states to
>>>use,
>>> what do you think about adding another state which may be used before
>>>the
>>> "Call For Adoption By WG Issued" state, named something like "Candidate
>>> for WG Adoption"?
>>
>> That sounds like a great idea. Personally, I would prefer something more
>> generic like "Chair is watching" (similar to AD is watching) as there
>> are more reasons to closely watch a document than just eying adoption.
>
>That sounds like another good pre-WG-document state to have.  I think we
>could add both "Chair is watching" and "Candidate for WG Adoption" --
>sometimes being specific about the latter is good.

I don't understand what "Chair is watching" means.
"Presented to WG" doesn't mean much.  It was discussed on list?  It was
discussed at a meeting?  Provides no information about document
status/state.
"Candidate for WG Adoption" sounds a little prejudicial; the WG chair has
already decided this document is a candidate.

Other than "Active" or "Expired," I don't know what state exists prior to
adoption.  Until the WG agrees that it is working on a document, it's an
individual submission.

Lee


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

From sarikaya2012@gmail.com  Wed Apr  3 09:05:18 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECC521F8C08 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aFlIBrEWm-OZ for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:05:18 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 94E3C21F8BF8 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:05:17 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id ek20so1588199lab.2 for <wgchairs@ietf.org>; Wed, 03 Apr 2013 09:05:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=s7d6SrrjvnEujNuffnY63LfPQbIuWNeilcPSvtXgfXw=; b=DSywCM1crZrCpGW3seoR4chDEash+l//DYVLO/MHCIK7Mql7L1biVvN2CjMNSJsPs2 +d9lExYvxXTCWBTBAcx5Jw6ZLZs2uFBmDrrVUTw9RjIDXtdcRSVW3nxClmmA+uGReZRG OS7GTT7GYb+BcU8S3kVB277rSjHVS3+XgNhHKv7k0JwByAW6s+FvwrigMYf/G5sOZEnN cg6TWS8fYnFeOCG/uHChqMuNlrPtjbcwhxqidWbC3CbYNQrkAbgvYjh979X/9dyoLCfx HTx4qlUcOTDF0Suavm3Lxu9wscyUZ3b/iyYfeFzMw0uN/hLeOIOBcWE+JegCu5sXRYyn 5G1Q==
MIME-Version: 1.0
X-Received: by 10.152.104.36 with SMTP id gb4mr1273372lab.13.1365005116532; Wed, 03 Apr 2013 09:05:16 -0700 (PDT)
Received: by 10.114.17.104 with HTTP; Wed, 3 Apr 2013 09:05:16 -0700 (PDT)
In-Reply-To: <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <F1312FAF1A1E624DA0972D1C9A91379A1BFC09306C@njfpsrvexg7.research.att.com>
Date: Wed, 3 Apr 2013 11:05:16 -0500
Message-ID: <CAC8QAcec89n5hYXtiq_EzmH9AkgCdnCueXiTVrPVE3A2U5LyCw@mail.gmail.com>
Subject: Re: Is a new state needed in the WG states for drafts?
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>
Content-Type: multipart/alternative; boundary=f46d04083d1516703f04d9770560
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 03 Apr 2013 16:05:18 -0000

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

You mean
Chairs are watching?

Behcet

On Wed, Apr 3, 2013 at 9:29 AM, MORTON JR., ALFRED C (AL)
<acmorton@att.com>wrote:

> +1 for Chair is Watching, it's sufficiently nebulous.
> Al
>
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> > Behalf Of Suresh Krishnan
> > Sent: Wednesday, April 03, 2013 10:16 AM
> > To: Henrik Levkowetz
> > Cc: WG Chairs
> > Subject: Re: Is a new state needed in the WG states for drafts?
> >
> > Hi Henrik,
> >
> > On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
> > > Considering that every WG can choose which, if any, of the states to
> > use,
> > > what do you think about adding another state which may be used before
> > the
> > > "Call For Adoption By WG Issued" state, named something like "Candidate
> > > for WG Adoption"?
> >
> > That sounds like a great idea. Personally, I would prefer something more
> > generic like "Chair is watching" (similar to AD is watching) as there
> > are more reasons to closely watch a document than just eying adoption.
> >
> > Thanks
> > Suresh
> >
>
>

--f46d04083d1516703f04d9770560
Content-Type: text/html; charset=ISO-8859-1

You mean<br>Chairs are watching?<br><br>Behcet<br><br><div class="gmail_quote">On Wed, Apr 3, 2013 at 9:29 AM, MORTON JR., ALFRED C (AL) <span dir="ltr">&lt;<a href="mailto:acmorton@att.com" target="_blank">acmorton@att.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 for Chair is Watching, it&#39;s sufficiently nebulous.<br>
<span class="HOEnZb"><font color="#888888">Al<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
&gt; -----Original Message-----<br>
&gt; From: <a href="mailto:wgchairs-bounces@ietf.org">wgchairs-bounces@ietf.org</a> [mailto:<a href="mailto:wgchairs-bounces@ietf.org">wgchairs-bounces@ietf.org</a>] On<br>
&gt; Behalf Of Suresh Krishnan<br>
&gt; Sent: Wednesday, April 03, 2013 10:16 AM<br>
&gt; To: Henrik Levkowetz<br>
&gt; Cc: WG Chairs<br>
&gt; Subject: Re: Is a new state needed in the WG states for drafts?<br>
&gt;<br>
&gt; Hi Henrik,<br>
&gt;<br>
&gt; On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:<br>
&gt; &gt; Considering that every WG can choose which, if any, of the states to<br>
&gt; use,<br>
&gt; &gt; what do you think about adding another state which may be used before<br>
&gt; the<br>
&gt; &gt; &quot;Call For Adoption By WG Issued&quot; state, named something like &quot;Candidate<br>
&gt; &gt; for WG Adoption&quot;?<br>
&gt;<br>
&gt; That sounds like a great idea. Personally, I would prefer something more<br>
&gt; generic like &quot;Chair is watching&quot; (similar to AD is watching) as there<br>
&gt; are more reasons to closely watch a document than just eying adoption.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Suresh<br>
&gt;<br>
<br>
</div></div></blockquote></div><br>

--f46d04083d1516703f04d9770560--

From mcr@sandelman.ca  Wed Apr  3 09:09:50 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB8B21F8E04 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:09:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTygEk2nv1bs for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:09:50 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id E9D2B21F8DBF for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:09:49 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CDDE320168; Wed,  3 Apr 2013 12:19:04 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 272F4638E8; Wed,  3 Apr 2013 12:09:34 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 049CE638E7; Wed,  3 Apr 2013 12:09:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: WG Chairs <wgchairs@ietf.org>
Subject: Re: Is a new state needed in the WG states for drafts?
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B01FD8A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <515C33BF.9040105@levkowetz.com> <949EF20990823C4C85C18D59AA11AD8B01FD8A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
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, 03 Apr 2013 12:09:34 -0400
Message-ID: <30052.1365005374@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:09:50 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Keith" =3D=3D Keith  <DRAGE> writes:
    Keith> What is the real problem here?

    Keith> Is it really that we are missing a state, or are we just
    Keith> missing a potential many to one association with a charter
    Keith> milestone?=20

yes, that would also work: it additional work, and it also requires that
the milestones be presented clearly in the database.  I would suggest
that this is a good "step 2".

I like the "chair is watching", and I'd like the bit to be three-stated
having also "chair is ignoring".

Why? Right now we have the "related Documents" test which looks for the=20
one WG name in the document title and shows it.  Apparently looking for
more than one became a problem once we had "core" as WG name.

What I'd like to be able to do with "Chair is watching" is to clearly
have the chair able to acknowledge a document (regardless of name) as
belonging on the list.

I would like the "chair is ignoring" for a document which would
otherwise have shown up in Related Documents, but the WG has looked at
it, and decided it is not relevant.=20=20

Things with neither watching nor ignoring could continue to use the WG
name in document title process.


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



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

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

iQCVAwUAUVxUPYqHRg3pndX9AQLmUQP+PQyI2T+deK6jrwy1a8+vAsiav/UmjAe+
PEGG3GC0HfwR4TQbf9eQl0RHkZSRGfIk8o+ZsKkRod5A2a7NqYILX9riMhSgD3sA
zwxaie8GEtz0v284H2M0dVPGCCLOGZakRG9728SpgjqM5V5G9PoA2m6c6Bj/hR8B
dGqj3lXXXKU=
=3nS/
-----END PGP SIGNATURE-----
--=-=-=--

From housley@vigilsec.com  Wed Apr  3 09:12:17 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55F821F8ED6 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRlsxxA1-qOj for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:12:17 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2C62F21F8DBF for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:12:17 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 32F889A4103; Wed,  3 Apr 2013 12:12:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id kn842pCcc4zA; Wed,  3 Apr 2013 12:12:15 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id B0A8E9A410D; Wed,  3 Apr 2013 12:12:15 -0400 (EDT)
Subject: Re: Is a new state needed in the WG states for drafts?
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
Date: Wed, 3 Apr 2013 12:12:14 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com>
References: <515C33BF.9040105@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.1085)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:12:17 -0000

This seems like a good addition to me.

Russ


On Apr 3, 2013, at 9:50 AM, Henrik Levkowetz wrote:

> Hi,
> 
> During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
> talk about how to best use the WG State tracking which is currently
> available in the datatracker.
> 
> I think we sorted out most of the things they would like to do, but
> there were at least one issue which remained, which may need some
> tweaking to the states and code.
> 
> Refering to the state summary at
>  https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
> 
> The only WG state which exists before "Adopted by a WG"/"WG Document"
> is "Call For Adoption By WG Issued".  But in the case of MPLS, there
> can be a rather large number of documents which are under consideration
> for adoption as WG documents, without an actual call for adoption having
> been issued yet.
> 
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?
> 
> 
> Best regards,
> 
> 	Henrik
> 	(Datatracker Maintenance Hat)
> 
> 


From lee.howard@twcable.com  Wed Apr  3 09:31:19 2013
Return-Path: <lee.howard@twcable.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A4021F8F4D for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhyG6lP308Sv for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:31:16 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 61FAC21F8F44 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:31:16 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.87,402,1363147200"; d="scan'208";a="51358406"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 03 Apr 2013 12:30:50 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.95]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 3 Apr 2013 12:31:15 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, WG Chairs <wgchairs@ietf.org>
Date: Wed, 3 Apr 2013 12:31:16 -0400
Subject: Re: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: Ac4wiKlAlLNwEw4TQd6ISwWNgNq3mA==
Message-ID: <CD81CDE8.1858D%lee.howard@twcable.com>
In-Reply-To: <30052.1365005374@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:31:19 -0000

On 4/3/13 12:09 PM, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:

>
>>>>>> "Keith" =3D=3D Keith  <DRAGE> writes:
>    Keith> What is the real problem here?
>
>    Keith> Is it really that we are missing a state, or are we just
>    Keith> missing a potential many to one association with a charter
>    Keith> milestone?
>
>yes, that would also work: it additional work, and it also requires that
>the milestones be presented clearly in the database.  I would suggest
>that this is a good "step 2".
>
>I like the "chair is watching", and I'd like the bit to be three-stated
>having also "chair is ignoring".
>
>Why? Right now we have the "related Documents" test which looks for the
>one WG name in the document title and shows it.  Apparently looking for
>more than one became a problem once we had "core" as WG name.
>
>What I'd like to be able to do with "Chair is watching" is to clearly
>have the chair able to acknowledge a document (regardless of name) as
>belonging on the list.

I like this--I would like to be able to use "Related Documents" as a list
of non-WG documents that may be discussed at a meeting, or which WG
participants may find interesting or informative reading.
I'm not sure a new state is the right mechanism for that, if a chair could
add recommended reading.  Or, chair can ask authors to rename their
documents "draft-lastname-wg-subject-of-draft" which for really
interesting drafts might have to be
"draft-lastname-wgfoo-wgbar-wgbaz-subject-of-draft".

Lee


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

From gvandeve@cisco.com  Wed Apr  3 09:49:27 2013
Return-Path: <gvandeve@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5593B21F8F0B for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XU0JBGxbQMXR for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 09:49:26 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C6B6D21F8D8C for <wgchairs@ietf.org>; Wed,  3 Apr 2013 09:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1666; q=dns/txt; s=iport; t=1365007766; x=1366217366; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=VsZ39Cd5DFfqF6gq9Amskx36rZK/r8hi7bAXpD0vALI=; b=Bo1Sx6Zg6ubikPV8t6jY1rVFtuxH9mG07rnmKP3sIMLvbVnL0JcANEWf mbq+38ymJ6S1+ko0gtOoMB9DPp3M1srTy7WlTj+IzAVtdIJphVfAiii/E OvpymkFmkzlhEl9+0JT6eWcOMoIKcTePIZjA2bHgiEh9p6xkjoDnKA4cB c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AngGAEBdXFGtJXHA/2dsb2JhbABDgwe9ZoMRgQwWdIIfAQEBBB0dPwwEAgEIEQQBAQEKFAkHMhQJCAIEAQ0FCIgMwE6OaDEHBoJZYQOndoMLgig
X-IronPort-AV: E=Sophos;i="4.87,402,1363132800"; d="scan'208";a="194430497"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 03 Apr 2013 16:49:18 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r33GnGQ6029488 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Apr 2013 16:49:17 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.138]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Wed, 3 Apr 2013 11:49:16 -0500
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMHJShGpfNh5WWUSKXRPzF6ld9pjE3ouAgAAIzwD//8rq8A==
Date: Wed, 3 Apr 2013 16:49:16 +0000
Message-ID: <67832B1175062E48926BF3CB27C49B240C8C891E@xmb-aln-x12.cisco.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com> <515C4116.4050604@levkowetz.com>
In-Reply-To: <515C4116.4050604@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.165.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 16:49:27 -0000

What is issue with what is there is right now? I am 100% happy in the proce=
ss right now.

I manage a WG with pretty light activity.

For the moment I do not need extra document state .
It is either individual document or it is accepted as WG document.

I see no reason for a document status to be somewhere in between in the twi=
light zone.=20
My view is to have 'no' WG chair to show formal preference for a document t=
o become WG document=20
or not (as that is what imho this intermediate state could result towards).

G/

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Henrik Levkowetz
Sent: 03 April 2013 16:48
To: Suresh Krishnan
Cc: WG Chairs
Subject: Re: Is a new state needed in the WG states for drafts?

Hi Suresh,

On 2013-04-03 16:16 Suresh Krishnan said:
> Hi Henrik,
>=20
> On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
>> Considering that every WG can choose which, if any, of the states to=20
>> use, what do you think about adding another state which may be used=20
>> before the "Call For Adoption By WG Issued" state, named something=20
>> like "Candidate for WG Adoption"?
>=20
> That sounds like a great idea. Personally, I would prefer something=20
> more generic like "Chair is watching" (similar to AD is watching) as=20
> there are more reasons to closely watch a document than just eying adopti=
on.

That sounds like another good pre-WG-document state to have.  I think we co=
uld add both "Chair is watching" and "Candidate for WG Adoption" -- sometim=
es being specific about the latter is good.


Best regards,

	Henrik




From mcr@sandelman.ca  Wed Apr  3 10:08:04 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD1E21F8F7A for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 10:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RN6EHBdUUNkm for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 10:08:03 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 515E321F8F7B for <wgchairs@ietf.org>; Wed,  3 Apr 2013 10:08:03 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 100EC20168; Wed,  3 Apr 2013 13:17:18 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 55692638E8; Wed,  3 Apr 2013 13:07:47 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 446A4638E7; Wed,  3 Apr 2013 13:07:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Howard, Lee" <lee.howard@twcable.com>
Subject: Re: Is a new state needed in the WG states for drafts?
In-Reply-To: <CD81CDE8.1858D%lee.howard@twcable.com>
References: <CD81CDE8.1858D%lee.howard@twcable.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
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, 03 Apr 2013 13:07:47 -0400
Message-ID: <8213.1365008867@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 17:08:04 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Howard," =3D=3D Howard, Lee <lee.howard@twcable.com> writes:
    >> yes, that would also work: it additional work, and it also requires =
that
    >> the milestones be presented clearly in the database.  I would suggest
    >> that this is a good "step 2".
    >>=20
    >> I like the "chair is watching", and I'd like the bit to be three-sta=
ted
    >> having also "chair is ignoring".
    >>=20
    >> Why? Right now we have the "related Documents" test which looks for =
the
    >> one WG name in the document title and shows it.  Apparently looking =
for
    >> more than one became a problem once we had "core" as WG name.
    >>=20
    >> What I'd like to be able to do with "Chair is watching" is to clearly
    >> have the chair able to acknowledge a document (regardless of name) as
    >> belonging on the list.

    Howard> I like this--I would like to be able to use "Related Documents"=
 as a list
    Howard> of non-WG documents that may be discussed at a meeting, or whic=
h WG
    Howard> participants may find interesting or informative reading.
    Howard> I'm not sure a new state is the right mechanism for that, if a =
chair could
    Howard> add recommended reading.  Or, chair can ask authors to rename t=
heir
    Howard> documents "draft-lastname-wg-subject-of-draft" which for really
    Howard> interesting drafts might have to be
    Howard> "draft-lastname-wgfoo-wgbar-wgbaz-subject-of-draft".

The first problem with the wgfoo-wgbar-wgbaz is that it turns out that it's
hard to actually have bar and baz found and presented.

The second problem is that the control over related documents is now
under the control of the document submitters, not the WG (in the form of
WG chairs).

I like wgfoo-wgbar-wgbaz as a way to bring a document to the attention
of the WG chair, who then clicks on the "watch" (or whatever verb we
conclude makes most sense).   Maybe "considering" is the right verb.

We need WG is ignoring only if we continue to make the "Related
Documents" area a free-for-all.  I think that we probably should do
that, as I think that I am happy with that aspect of openness.

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

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

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

iQCVAwUAUVxh4oqHRg3pndX9AQIIMwP/admY8tmwCItzzCtNSdfr7PBddCACCwu0
YSCtq3rHuT0ioecVQL+hZ/BC/KBjh9TVTGkEigMSr6TaHTLjkWt+QQSv5Fmh4JLR
SaeqgJkUSb5N3hRS3NRTE+kaXW7uUDDO24Fg/CCBFDnFftZirDp0cW06L7yrGVCq
seQcNIPFyQ0=
=KbOJ
-----END PGP SIGNATURE-----
--=-=-=--

From david.black@emc.com  Wed Apr  3 11:05:53 2013
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83E9B21F8AE8 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGtfC-rTDWZC for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:05:53 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id DADCC21F8AAA for <wgchairs@ietf.org>; Wed,  3 Apr 2013 11:05:52 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33I5pDu002349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Apr 2013 14:05:52 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 3 Apr 2013 14:05:35 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33I5XVs029351; Wed, 3 Apr 2013 14:05:34 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Wed, 3 Apr 2013 14:05:34 -0400
From: "Black, David" <david.black@emc.com>
To: Russ Housley <housley@vigilsec.com>
Date: Wed, 3 Apr 2013 14:05:32 -0400
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: Ac4whiHdk+tR2sl+RimdSOvwBAsjIQADqLgA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D371FA@MX15A.corp.emc.com>
References: <515C33BF.9040105@levkowetz.com> <8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com>
In-Reply-To: <8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 18:05:53 -0000

+1

Also, for individual submission drafts that have the WG name embedded,
e.g., draft-person-wgfoo-something-interesting, it seems worthwhile to
enable the named WG, i.e., wgfoo, but *only* wgfoo, to record a decision
that the WG has looked at the draft and is not interested,
e.g., "No WG Interest".

That may encourages the draft authors to continue shopping the draft
by renaming it, e.g., to draft-wgbar-something-interesting.  While honest
(by comparison to leaving the name of a no-longer-interested WG in the
draft name), it's also a bit of an obfuscation, and invites subterfuge,
e.g., if the rename is to draft-wgbar-something-else, tracking down
what it replaced may not be easy.

Thanks,
--David


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Beh=
alf
> Of Russ Housley
> Sent: Wednesday, April 03, 2013 12:12 PM
> To: Henrik Levkowetz
> Cc: WG Chairs
> Subject: Re: Is a new state needed in the WG states for drafts?
>=20
> This seems like a good addition to me.
>=20
> Russ
>=20
>=20
> On Apr 3, 2013, at 9:50 AM, Henrik Levkowetz wrote:
>=20
> > Hi,
> >
> > During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
> > talk about how to best use the WG State tracking which is currently
> > available in the datatracker.
> >
> > I think we sorted out most of the things they would like to do, but
> > there were at least one issue which remained, which may need some
> > tweaking to the states and code.
> >
> > Refering to the state summary at
> >  https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
> >
> > The only WG state which exists before "Adopted by a WG"/"WG Document"
> > is "Call For Adoption By WG Issued".  But in the case of MPLS, there
> > can be a rather large number of documents which are under consideration
> > for adoption as WG documents, without an actual call for adoption havin=
g
> > been issued yet.
> >
> > Considering that every WG can choose which, if any, of the states to us=
e,
> > what do you think about adding another state which may be used before t=
he
> > "Call For Adoption By WG Issued" state, named something like "Candidate
> > for WG Adoption"?
> >
> >
> > Best regards,
> >
> > 	Henrik
> > 	(Datatracker Maintenance Hat)
> >
> >
>=20


From randy_presuhn@mindspring.com  Wed Apr  3 11:52:48 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB46121F8BF2 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yS1npJcsuNCf for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:52:48 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 0A73821F8BDD for <wgchairs@ietf.org>; Wed,  3 Apr 2013 11:52:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=RqCaIYD+LIFHyFXbKzofHcTZWlT0ioE/GPrlQBnPXa0UeJMPeGtOCdfaRzir1xGm; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.52.237] (helo=oemcomputer) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UNSnd-0000bC-VC for wgchairs@ietf.org; Wed, 03 Apr 2013 14:52:47 -0400
Message-ID: <00e201ce309c$a36a30c0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "WG Chairs" <wgchairs@ietf.org>
References: <515C33BF.9040105@levkowetz.com><8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com> <8D3D17ACE214DC429325B2B98F3AE71293D371FA@MX15A.corp.emc.com>
Subject: Re: Is a new state needed in the WG states for drafts?
Date: Wed, 3 Apr 2013 11:54:10 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe9461a3812194c1b6a084039bbaafc96ad0e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.52.237
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 18:52:49 -0000

Hi -

> From: "Black, David" <david.black@emc.com>
...
> Also, for individual submission drafts that have the WG name embedded,
> e.g., draft-person-wgfoo-something-interesting, it seems worthwhile to
> enable the named WG, i.e., wgfoo, but *only* wgfoo, to record a decision
> that the WG has looked at the draft and is not interested,
> e.g., "No WG Interest".

Since it's not always a case of "no" interest, if we go this route,
I'd suggest "Insufficient WG Interest".

Randy


From david.black@emc.com  Wed Apr  3 11:59:49 2013
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68EA421F8BF2 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fx0SI5QhPLAi for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 11:59:49 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D0D2C21F8BDD for <wgchairs@ietf.org>; Wed,  3 Apr 2013 11:59:48 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33IxjQr024958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Apr 2013 14:59:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 3 Apr 2013 14:59:27 -0400
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33IxRwF010349; Wed, 3 Apr 2013 14:59:27 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub17.corp.emc.com ([10.254.93.46]) with mapi; Wed, 3 Apr 2013 14:59:26 -0400
From: "Black, David" <david.black@emc.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, WG Chairs <wgchairs@ietf.org>
Date: Wed, 3 Apr 2013 14:59:26 -0400
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: Ac4wnIVB0Gwx+SZ/TqGkLhxfBLLIAwAAMzcQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D37224@MX15A.corp.emc.com>
References: <515C33BF.9040105@levkowetz.com><8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com> <8D3D17ACE214DC429325B2B98F3AE71293D371FA@MX15A.corp.emc.com> <00e201ce309c$a36a30c0$6b01a8c0@oemcomputer>
In-Reply-To: <00e201ce309c$a36a30c0$6b01a8c0@oemcomputer>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 18:59:49 -0000

WFM, Thanks, --David

> Hi -
>=20
> > From: "Black, David" <david.black@emc.com>
> ...
> > Also, for individual submission drafts that have the WG name embedded,
> > e.g., draft-person-wgfoo-something-interesting, it seems worthwhile to
> > enable the named WG, i.e., wgfoo, but *only* wgfoo, to record a decisio=
n
> > that the WG has looked at the draft and is not interested,
> > e.g., "No WG Interest".
>=20
> Since it's not always a case of "no" interest, if we go this route,
> I'd suggest "Insufficient WG Interest".
>=20
> Randy
>=20


From presnick@qti.qualcomm.com  Wed Apr  3 12:12:57 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD79D21F8F08 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 12:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPK-ZCRLik0A for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 12:12:57 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id E03EE21F8F05 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 12:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1365016376; x=1396552376; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=PahOqNRz45F53opzXblSZssIBACto2BjFsr6iSL2UT8=; b=PTuoovAfF8kQOVJPUwCmPAbsYEtbcRr7zIXuFmUVnx5wvhUQDa2kATDP DvIfNUrcms+hoWQwPNptUwCd+cHc7QhGa6NrpPtVx5nvQNsOiYMvr06ug 1moSzoczncc3DfbdxtwHmvgLfFanQt20BJHAMkk8B2Hn2j3uQ4UWif6kA o=;
X-IronPort-AV: E=Sophos;i="4.87,402,1363158000"; d="scan'208";a="33563089"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 03 Apr 2013 12:12:56 -0700
X-IronPort-AV: E=Sophos;i="4.87,402,1363158000"; d="scan'208";a="452847361"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2013 12:12:56 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Apr 2013 12:12:56 -0700
Message-ID: <515C7F35.8090008@qti.qualcomm.com>
Date: Wed, 3 Apr 2013 14:12:53 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com>
In-Reply-To: <515C33BF.9040105@levkowetz.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 19:12:57 -0000

On 4/3/13 8:50 AM, Henrik Levkowetz wrote:
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?
>    

Given the discussion thus far, this now seems like an exceedingly *bad* 
idea to me. A document can be a candidate for adoption in several WGs at 
the same time, and AFAICT there is no way to represent that with a 
single state, since a document entering the WG tracker can only have a 
single WG associated with it. This is exactly why Robert finally beat 
the ADs about using the "AD is Watching" state for simply indicating 
that a document is at the beginning of the process and you are keeping 
an eye on it: It stays with you from then on until some other AD picks 
up the document or you mark it as DEAD, which people don't like to do 
because it looks bad.

It seems to me that the suggestion to revamp the "Related Documents" 
list is really what is needed. People have the personal tracker to track 
what documents they are interested in. What you want is for the WG to be 
able to have its own "personal tracker" so that other people can see 
what documents the WG is interested in. They can be documents from other 
WGs, or documents that are proposed for adoption, or whatever else the 
WG wants to use that list for.

It seems to me that you are trying to use the hammer of "WG document 
state" to drive in this screw. Put down the hammer. Find a screwdriver. 
You're only going to end up with a mashed up screw that doesn't hold 
very well.

pr

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


From henrik@levkowetz.com  Wed Apr  3 14:01:01 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD7721F8EDE for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24TV9CZto954 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:01:00 -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 95F5B21F8ED4 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 14:01:00 -0700 (PDT)
Received: from localhost ([127.0.0.1]:47913 helo=vigonier.lan ident=henrik) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNUnj-0002Hm-9e; Wed, 03 Apr 2013 23:00:59 +0200
Message-ID: <515C988B.2050201@levkowetz.com>
Date: Wed, 03 Apr 2013 23:00:59 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com> <515C7F35.8090008@qti.qualcomm.com>
In-Reply-To: <515C7F35.8090008@qti.qualcomm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: presnick@qti.qualcomm.com, wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 21:01:01 -0000

Hi Pete,

(and also Gunter, see the last few paragraph of mine below regarding the
number of potential WG documents the MPLS WG has to deal with)

A couple of points which I'd like to mention in reply to Pete's comments,
which you may not have realized:

On 2013-04-03 21:12 Pete Resnick said the following:
> On 4/3/13 8:50 AM, Henrik Levkowetz wrote:
>> Considering that every WG can choose which, if any, of the states to use,
>> what do you think about adding another state which may be used before the
>> "Call For Adoption By WG Issued" state, named something like "Candidate
>> for WG Adoption"?
>>    
> 
> Given the discussion thus far, this now seems like an exceedingly *bad* 
> idea to me. A document can be a candidate for adoption in several WGs at 
> the same time, and AFAICT there is no way to represent that with a 
> single state, since a document entering the WG tracker can only have a 
> single WG associated with it.

1. Yes, but there may be a point to this, which I don't think has been mentioned
this time around, but was taken up when draft-ietf-proto-wgdocument-states
which became RFC 6174 was discussed:  Being able to set a state on a non-WG
document can work as a flag, telling other WG chairs that one group is already
looking at a document from some point of view, so that they will start by talking
to the chairs that have so marked it, instead of starting a parallel discussion
in their own WG without knowledge that a draft is already under consideration
elsewhere.

> This is exactly why Robert finally beat 
> the ADs about using the "AD is Watching" state for simply indicating 
> that a document is at the beginning of the process and you are keeping 
> an eye on it: It stays with you from then on until some other AD picks 
> up the document or you mark it as DEAD, which people don't like to do 
> because it looks bad.

It could be that the cases aren't parallel...

> It seems to me that the suggestion to revamp the "Related Documents" 
> list is really what is needed. People have the personal tracker to track 
> what documents they are interested in. What you want is for the WG to be 
> able to have its own "personal tracker" so that other people can see 
> what documents the WG is interested in. They can be documents from other 
> WGs, or documents that are proposed for adoption, or whatever else the 
> WG wants to use that list for.

2. Some more data here:  The MPLS working group has currently *almost 50*
active related documents.  With the additional state, as proposed, the
chairs would be able to signal which of these were actually under consideration
for adoption at any given time.  As far as I can tell, this meshes very well
with other uses of the WG document states.

The only effect of depriving the working group of a "Candidate for WG Adoption"
state is that they will be using the current "Call For Adoption By WG Issued"
state to signal the same thing, but with a larger chance of miscommunication
because it doesn't clearly say what they want to indicate.

> It seems to me that you are trying to use the hammer of "WG document 
> state" to drive in this screw. Put down the hammer. Find a screwdriver. 
> You're only going to end up with a mashed up screw that doesn't hold 
> very well.

While the hammer/screw analogy can often be used to dissuade people from doing
silly things, I actually don't think it's applicable here, in view of my point
1. above.


Best regards,

	Henrik



From dcrocker@bbiw.net  Wed Apr  3 14:05:37 2013
Return-Path: <dcrocker@bbiw.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2049D21F8F0E for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level: 
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_27=1, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1IymubxBgV48 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:05:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 38CCA21F8F0D for <wgchairs@ietf.org>; Wed,  3 Apr 2013 14:05:22 -0700 (PDT)
Received: from com.flipdogsolutions (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r33L5FjA003412 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 3 Apr 2013 14:05:18 -0700
Date: Wed, 3 Apr 2013 14:05:20 -0700
From: Dave Crocker <dcrocker@bbiw.net>
To: Henrik Levkowetz <henrik@levkowetz.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Message-ID: <d08d60b1-9a3d-4d7b-8e93-473343c1fd41.maildroid@localhost>
In-Reply-To: <515C39B3.9070807@ericsson.com>
References: <515C33BF.9040105@levkowetz.com> <515C39B3.9070807@ericsson.com>
Subject: Re: Is a new state needed in the WG states for drafts?
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2_1097318832.1365023120555"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Wed, 03 Apr 2013 14:05:19 -0700 (PDT)
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 21:05:37 -0000

------=_Part_2_1097318832.1365023120555
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Suresh's note suggests that the state could apply at various times throughout the eg life of the doc.


/d

--
Dave Crocker
bbiw.net

via mobile

-----Original Message-----
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Cc: WG Chairs <wgchairs@ietf.org>
Sent: Wed, 03 Apr 2013 7:18 AM
Subject: Re: Is a new state needed in the WG states for drafts?

Hi Henrik,

On 04/03/2013 09:50 AM, Henrik Levkowetz wrote:
> Considering that every WG can choose which, if any, of the states to use,
> what do you think about adding another state which may be used before the
> "Call For Adoption By WG Issued" state, named something like "Candidate
> for WG Adoption"?

That sounds like a great idea. Personally, I would prefer something more
generic like "Chair is watching" (similar to AD is watching) as there
are more reasons to closely watch a document than just eying adoption.

Thanks
Suresh


------=_Part_2_1097318832.1365023120555
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div>Suresh's note suggests that the state could apply at various times throughout the eg life of the doc.<br/>
<br/>
<br/>
<font color="#888888"><font color="#888888">/d</font></font><br/>
<br/>
<font color="#888888"><font color="#888888">--</font></font><br/>
<font color="#888888"><font color="#888888">Dave Crocker</font></font><br/>
<font color="#888888"><font color="#888888"><a href="http://bbiw.net">bbiw.net</a></font></font><br/>
<br/>
<font color="#888888"><font color="#888888">via mobile</font></font><br/><br/>-----Original Message-----<br/>From: Suresh Krishnan &lt;suresh.krishnan@ericsson.com&gt;<br/>To: Henrik Levkowetz &lt;henrik@levkowetz.com&gt;<br/>Cc: WG Chairs &lt;wgchairs@ietf.org&gt;<br/>Sent: Wed, 03 Apr 2013 7:18 AM<br/>Subject: Re: Is a new state needed in the WG states for drafts?<br/><br/></div>Hi Henrik,&#13;<br/>
&#13;<br/>
On 04/03/<a href="tel:201309">2013 09</a>:50 AM, Henrik Levkowetz wrote:&#13;<br/>
&gt; Considering that every WG can choose which, if any, of the states to use,&#13;<br/>
&gt; what do you think about adding another state which may be used before the&#13;<br/>
&gt; "Call For Adoption By WG Issued" state, named something like "Candidate&#13;<br/>
&gt; for WG Adoption"?&#13;<br/>
&#13;<br/>
That sounds like a great idea. Personally, I would prefer something more&#13;<br/>
generic like "Chair is watching" (similar to AD is watching) as there&#13;<br/>
are more reasons to closely watch a document than just eying adoption.&#13;<br/>
&#13;<br/>
Thanks&#13;<br/>
Suresh&#13;<br/>
&#13;<br/>

------=_Part_2_1097318832.1365023120555--

From henrik@levkowetz.com  Wed Apr  3 14:05:57 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D763221F85F3 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KS153vxO1nB for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 14:05:57 -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 383FC21F85D8 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 14:05:57 -0700 (PDT)
Received: from localhost ([127.0.0.1]:48155 helo=vigonier.lan ident=henrik) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UNUsT-00052Y-7r; Wed, 03 Apr 2013 23:05:53 +0200
Message-ID: <515C99B0.8060809@levkowetz.com>
Date: Wed, 03 Apr 2013 23:05:52 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com> <8BE70A8C-ABAB-4E6A-B62D-7C66CAEEE54B@vigilsec.com> <8D3D17ACE214DC429325B2B98F3AE71293D371FA@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293D371FA@MX15A.corp.emc.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: david.black@emc.com, housley@vigilsec.com, wgchairs@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: WG Chairs <wgchairs@ietf.org>, Russ Housley <housley@vigilsec.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 21:05:58 -0000

Hi David,

On 2013-04-03 20:05 Black, David said the following:
> +1
> 
> Also, for individual submission drafts that have the WG name embedded,
> e.g., draft-person-wgfoo-something-interesting, it seems worthwhile to
> enable the named WG, i.e., wgfoo, but *only* wgfoo, to record a decision
> that the WG has looked at the draft and is not interested,
> e.g., "No WG Interest".

I think this could an excellent addition to the proposal.  It of course means
that more code is needed, not only an additional state entry in the state
list, but that's fine.

> That may encourages the draft authors to continue shopping the draft
> by renaming it, e.g., to draft-wgbar-something-interesting.  While honest
> (by comparison to leaving the name of a no-longer-interested WG in the
> draft name), it's also a bit of an obfuscation, and invites subterfuge,
> e.g., if the rename is to draft-wgbar-something-else, tracking down
> what it replaced may not be easy.

True.  But I think this could still be a good idea.


Best regards,

	Henrik


> Thanks,
> --David
> 
> 
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf
>> Of Russ Housley
>> Sent: Wednesday, April 03, 2013 12:12 PM
>> To: Henrik Levkowetz
>> Cc: WG Chairs
>> Subject: Re: Is a new state needed in the WG states for drafts?
>> 
>> This seems like a good addition to me.
>> 
>> Russ
>> 
>> 
>> On Apr 3, 2013, at 9:50 AM, Henrik Levkowetz wrote:
>> 
>> > Hi,
>> >
>> > During IETF 86, I sat down with Loa Andersson and Martin Vigoreux to
>> > talk about how to best use the WG State tracking which is currently
>> > available in the datatracker.
>> >
>> > I think we sorted out most of the things they would like to do, but
>> > there were at least one issue which remained, which may need some
>> > tweaking to the states and code.
>> >
>> > Refering to the state summary at
>> >  https://datatracker.ietf.org/help/state/draft/stream-ietf/ :
>> >
>> > The only WG state which exists before "Adopted by a WG"/"WG Document"
>> > is "Call For Adoption By WG Issued".  But in the case of MPLS, there
>> > can be a rather large number of documents which are under consideration
>> > for adoption as WG documents, without an actual call for adoption having
>> > been issued yet.
>> >
>> > Considering that every WG can choose which, if any, of the states to use,
>> > what do you think about adding another state which may be used before the
>> > "Call For Adoption By WG Issued" state, named something like "Candidate
>> > for WG Adoption"?
>> >
>> >
>> > Best regards,
>> >
>> > 	Henrik
>> > 	(Datatracker Maintenance Hat)
>> >
>> >
>> 
> 
> 

From keith.drage@alcatel-lucent.com  Wed Apr  3 15:23:13 2013
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA0EE21F8648 for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 15:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJj9xaISSF3t for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 15:23:13 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id A6E1D21F9121 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 15:23:12 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r33MN7QE028095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 3 Apr 2013 17:23:08 -0500 (CDT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id r33MN6BJ020530 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Apr 2013 18:23:07 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 3 Apr 2013 18:23:06 -0400
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.201]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Thu, 4 Apr 2013 00:23:03 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: RE: Is a new state needed in the WG states for drafts?
Thread-Topic: Is a new state needed in the WG states for drafts?
Thread-Index: AQHOMJ89J3KiUfNQlk2gUkXHj41y15jFEOxg
Date: Wed, 3 Apr 2013 22:23:02 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B02038A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <515C33BF.9040105@levkowetz.com> <515C7F35.8090008@qti.qualcomm.com>
In-Reply-To: <515C7F35.8090008@qti.qualcomm.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2013 22:23:13 -0000

I believe I concur.

To me, the state should identify the degree of progress of the document, an=
d these do not seem to be progress.

Rather there seems to be a need to retain extractable information about the=
 document and the relationship to the working group, e.g. document consider=
ed within the scope of a working group, document considered to be within th=
e scope of working group charter milestone. Note that these relationships c=
ould possibly be many to many.

At some point an identified relationship could be removed, and possibly eit=
her the addition or removal could be accompanied by a note indicating the r=
easons for the association in the first place, or for its removal. These wo=
uld be listed with the history of the document.


Keith


> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Pete Resnick
> Sent: 03 April 2013 20:13
> To: Henrik Levkowetz
> Cc: WG Chairs
> Subject: Re: Is a new state needed in the WG states for drafts?
>=20
> On 4/3/13 8:50 AM, Henrik Levkowetz wrote:
> > Considering that every WG can choose which, if any, of the states to us=
e,
> > what do you think about adding another state which may be used before
> the
> > "Call For Adoption By WG Issued" state, named something like "Candidate
> > for WG Adoption"?
> >
>=20
> Given the discussion thus far, this now seems like an exceedingly *bad*
> idea to me. A document can be a candidate for adoption in several WGs at
> the same time, and AFAICT there is no way to represent that with a
> single state, since a document entering the WG tracker can only have a
> single WG associated with it. This is exactly why Robert finally beat
> the ADs about using the "AD is Watching" state for simply indicating
> that a document is at the beginning of the process and you are keeping
> an eye on it: It stays with you from then on until some other AD picks
> up the document or you mark it as DEAD, which people don't like to do
> because it looks bad.
>=20
> It seems to me that the suggestion to revamp the "Related Documents"
> list is really what is needed. People have the personal tracker to track
> what documents they are interested in. What you want is for the WG to be
> able to have its own "personal tracker" so that other people can see
> what documents the WG is interested in. They can be documents from other
> WGs, or documents that are proposed for adoption, or whatever else the
> WG wants to use that list for.
>=20
> It seems to me that you are trying to use the hammer of "WG document
> state" to drive in this screw. Put down the hammer. Find a screwdriver.
> You're only going to end up with a mashed up screw that doesn't hold
> very well.
>=20
> pr
>=20
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478


From mcr@sandelman.ca  Wed Apr  3 17:19:43 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 611E421F8FFB for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 17:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waogf8sc4SUa for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 17:19:42 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id A703F21F8F98 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 17:19:42 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id CF5AA20168; Wed,  3 Apr 2013 20:28:57 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6E7AD638E8; Wed,  3 Apr 2013 20:19:25 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5854863781; Wed,  3 Apr 2013 20:19:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: WG Chairs <wgchairs@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Is a new state needed in the WG states for drafts?
In-Reply-To: <515C7F35.8090008@qti.qualcomm.com>
References: <515C33BF.9040105@levkowetz.com> <515C7F35.8090008@qti.qualcomm.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
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, 03 Apr 2013 20:19:25 -0400
Message-ID: <30509.1365034765@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 00:19:43 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Pete" =3D=3D Pete Resnick <presnick@qti.qualcomm.com> writes:
    Pete> Given the discussion thus far, this now seems like an
    Pete> exceedingly *bad* idea=20
    Pete> to me. A document can be a candidate for adoption in several
    Pete> WGs at the same=20
    Pete> time, and AFAICT there is no way to represent that with a
    Pete> single state, since=20

I think that it's not a bad idea.
It may be a useless idea, but I don't think it's harmful.=20
It's very cheap, literally, I think, one row in a table. While I think
that some code changes will be made, they are optional.

Don't let perfect get in the way of good enough.

If good enough isn't good enough, then we can do version 2 at larger
software effort.    It's software afterall.

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


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

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

iQCVAwUAUVzHDYqHRg3pndX9AQISPwP/YSU08uRPAWtsGWb9nYCY2VZ0snnY5LI8
pIUJh0DQ4UJWhVYFDGQxsVxdvVbv/cQ+odhbrqGXSOtBQBbX2B6OybNIiIFKIFld
rc7ZV4QAYcgIOqjBvzMfoyfe25+fIQ76I5ryusuSXk4wcpHGN9FTB5lfvDWPBwcd
0bPpYzX9nLw=
=500f
-----END PGP SIGNATURE-----
--=-=-=--

From loa@pi.nu  Wed Apr  3 21:17:19 2013
Return-Path: <loa@pi.nu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEFA321E803C for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 21:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmxmsuwjGJXu for <wgchairs@ietfa.amsl.com>; Wed,  3 Apr 2013 21:17:17 -0700 (PDT)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 4984D21E8037 for <wgchairs@ietf.org>; Wed,  3 Apr 2013 21:17:16 -0700 (PDT)
Received: from [192.168.10.101] (unknown [121.54.51.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 7872C7FE07 for <wgchairs@ietf.org>; Thu,  4 Apr 2013 06:17:11 +0200 (CEST)
Message-ID: <515CFEC2.5090705@pi.nu>
Date: Thu, 04 Apr 2013 06:17:06 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Is a new state needed in the WG states for drafts?
References: <515C33BF.9040105@levkowetz.com> <515C7F35.8090008@qti.qualcomm.com> <30509.1365034765@sandelman.ca>
In-Reply-To: <30509.1365034765@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2013 04:17:19 -0000

All,

I agree with Michael that this is not a bad idea.

In my case it is very useful, to the point where if I can't
reflect what happens to a document before it is formally
adopted as a working group document the use of the ID tracker
is not beneficial. We'll go back and managed the the spreadsheet
as we don't up to mow. Much clearer and pregnant info; but it requires
a manual intervention each time we do anything.

"Candidate Document for WG" (or what ever we call it) does not reflect a
preference by the wg chairs; it reflects the fact that the authors of
a document has told the wg chairs the the document is ready to become a
working group document and that the wg (chairs) has committed to go
through the steps to see if there is consensus in the working group
to make it a wg doc.

For me there is several steps in this process
1. the doc is reviewed by review team members (and chair(s))
2. the comment from this review is resolved and it is verified that
    the comments are satisfactorily addressed.
3. we do an IPR poll
4. we do a poll to see if we have rough consensus to  adopt it as
    a working group document

Step 4 above reflect "Call for working group adoption issued". I need
the state to reflect the pre-poll activities. I don't understand why
this is bad or what harm if could do if it optional.

"WG Chair watching" I'd like to use when there seems to be a dropping
interest by authors to do what they once committed to.

/Loa

On 2013-04-04 02:19, Michael Richardson wrote:
>
>>>>>> "Pete" == Pete Resnick <presnick@qti.qualcomm.com> writes:
>      Pete> Given the discussion thus far, this now seems like an
>      Pete> exceedingly *bad* idea
>      Pete> to me. A document can be a candidate for adoption in several
>      Pete> WGs at the same
>      Pete> time, and AFAICT there is no way to represent that with a
>      Pete> single state, since
>
> I think that it's not a bad idea.
> It may be a useless idea, but I don't think it's harmful.
> It's very cheap, literally, I think, one row in a table. While I think
> that some code changes will be made, they are optional.
>
> Don't let perfect get in the way of good enough.
>
> If good enough isn't good enough, then we can do version 2 at larger
> software effort.    It's software afterall.
>

-- 


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

From yaronf.ietf@gmail.com  Fri Apr  5 13:18:33 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9E221F95EA for <wgchairs@ietfa.amsl.com>; Fri,  5 Apr 2013 13:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.183
X-Spam-Level: 
X-Spam-Status: No, score=-100.183 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YOt0hCumH+qX for <wgchairs@ietfa.amsl.com>; Fri,  5 Apr 2013 13:18:33 -0700 (PDT)
Received: from mail-ea0-x235.google.com (mail-ea0-x235.google.com [IPv6:2a00:1450:4013:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 9489E21F942C for <wgchairs@ietf.org>; Fri,  5 Apr 2013 13:18:32 -0700 (PDT)
Received: by mail-ea0-f181.google.com with SMTP id z10so1463696ead.12 for <wgchairs@ietf.org>; Fri, 05 Apr 2013 13:18:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=YcekoSY6IHMm/nLDSCl345c4Rb5cgUsKvC4r+Ev85AE=; b=vD5ON5HV33ktltkKRnL5cvQYiTCxQEvz6med2duVKMb+AWS7oxlJe+DZ3X2EnWNBap t87OnRiPArMfYfdJaICJy/GA5vasYTBAQWGKlw0Ad+SNOmao9axi7KQQQZYVgyP2/gxQ VeNBiTVRNFxbKffkCSkiilz5+Pho64Q97JYAEIaeQBgrOGouA4na8mr9byinCgUAGXlb F3VmjitkZy4B3fDww2jbmPW0K4k6Xgdt5kOZcR47Njh+BUllbZGdgCrZtQAXsGC364mQ x46WDT2wUgHjq6LK/cpkl1vMkaFb1jrQGKr4ii4m+xdJRnGpw54+fgklIK5p/c6xkkdL AcdQ==
X-Received: by 10.14.175.71 with SMTP id y47mr22554431eel.18.1365193111538; Fri, 05 Apr 2013 13:18:31 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-181-109-111.red.bezeqint.net. [79.181.109.111]) by mx.google.com with ESMTPS id a1sm17420650eep.2.2013.04.05.13.18.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 13:18:30 -0700 (PDT)
Message-ID: <515F3194.5020907@gmail.com>
Date: Fri, 05 Apr 2013 23:18:28 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Fwd: New Version Notification for draft-sheffer-running-code-03.txt
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>
In-Reply-To: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2013 20:18:33 -0000

Hi,

we have just published a new version of our draft that defines a new, 
optional Implementation Status section.

The most significant addition in this rev is proposed introductory text 
for this section. We also included a list of current I-Ds that adopt 
this proposal.

Adrian and I would like to last-call this draft soon, and we solicit 
this list's comments before we do.

Thanks,
	Yaron

-------- Original Message --------
Subject: New Version Notification for draft-sheffer-running-code-03.txt
Date: Fri, 05 Apr 2013 12:42:51 -0700
From: internet-drafts@ietf.org
To: yaronf.ietf@gmail.com
CC: adrian@olddog.co.uk


A new version of I-D, draft-sheffer-running-code-03.txt
has been successfully submitted by Yaron Sheffer and posted to the
IETF repository.

Filename:	 draft-sheffer-running-code
Revision:	 03
Title:		 Improving Awareness of Running Code: the Implementation Status 
Section
Creation date:	 2013-04-05
Group:		 Individual Submission
Number of pages: 9
URL: 
http://www.ietf.org/internet-drafts/draft-sheffer-running-code-03.txt
Status:          http://datatracker.ietf.org/doc/draft-sheffer-running-code
Htmlized:        http://tools.ietf.org/html/draft-sheffer-running-code-03
Diff: 
http://www.ietf.org/rfcdiff?url2=draft-sheffer-running-code-03

Abstract:
    This document describes a simple process that allows authors of
    Internet-Drafts to record the status of known implementations by
    including an Implementation Status section.  This will allow
    reviewers and working groups to assign due consideration to documents
    that have the benefit of running code and potentially reward the
    documented protocols by treating the documents with implementations
    preferentially.

    The process in this document is offered as an experiment.  Authors of
    Internet-Drafts are encouraged to consider using the process for
    their documents, and working groups are invited to think about
    applying the process to all of their protocol specifications.  The
    authors of this document intend to collate experiences with this
    experiment and to report them to the community.

 



The IETF Secretariat




From stpeter@stpeter.im  Fri Apr  5 18:41:30 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B24A321F9679 for <wgchairs@ietfa.amsl.com>; Fri,  5 Apr 2013 18:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GxZZERbnNM9 for <wgchairs@ietfa.amsl.com>; Fri,  5 Apr 2013 18:41:29 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5EC21F965C for <wgchairs@ietf.org>; Fri,  5 Apr 2013 18:41:27 -0700 (PDT)
Received: from [192.168.1.9] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4F86940E24 for <wgchairs@ietf.org>; Fri,  5 Apr 2013 19:51:19 -0600 (MDT)
Message-ID: <515F7D47.4060109@stpeter.im>
Date: Fri, 05 Apr 2013 19:41:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Fwd: New Version Notification for draft-sheffer-running-code-03.txt
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com> <515F3194.5020907@gmail.com>
In-Reply-To: <515F3194.5020907@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Apr 2013 01:41:30 -0000

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

On 4/5/13 2:18 PM, Yaron Sheffer wrote:
> Hi,
> 
> we have just published a new version of our draft that defines a
> new, optional Implementation Status section.
> 
> The most significant addition in this rev is proposed introductory
> text for this section. We also included a list of current I-Ds that
> adopt this proposal.
> 
> Adrian and I would like to last-call this draft soon, and we
> solicit this list's comments before we do.

Looks good. I'll add an implementation status section to a few of the
I-Ds I have in process as an individual contributor and query the
document editors in my one WG about doing so, too.

Peter

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


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

iQIcBAEBAgAGBQJRX31HAAoJEOoGpJErxa2pjGQQALIPM1bFqIspfH+Gl8PlE1yC
RMI2oxbxrFEV7HsYAA31k9thvvwt3c2aMlDNpSTtblJquFISdnWY+7KTGiLRWV0+
/jiKHXqmKRuqDLOBHkamx14MMuRi+gu/5vfgK6Z6/yw4iomIbUeDMsnqX1tphE4D
397pr0sJq+fs2lpnyyPdb9UqL8gYJIMV+0U2wanlRknZley9UtzWPzFYfx/Gh4VC
Lhmj+6d7CJVbR0PVSpBMoycwlNAxGc4jk2QdWdPEO7u2qRQSqcZc9HG2Io1hK8bz
xSFNvGOfhiqwExxTzUDB6dT+xJJRFBO5uwZpa5EKjD5MwVuNFLnHXR+sQ+QVgFK7
zGauKFVVVM9UhU7f8rN9wnVo11l4RL0h6/hnaDUE9KwaUPs2YnXCASojJccK9rkD
YOy5G66eqcrcs9UwSQNAQqiw5es0MebpBPAemme5trAn0y4evo/k8qDRQuwju42q
wu+ao19tCnGSTllEjOhI+MPqV0PZWfGxUs41aA85bbqTw8AohAqZv3sjT3zsIDW0
F/2Vrkie32n+HNdvt7LFO1V5xnZPpdhbgn+fFcxNCgQnk4x9fzs7ma891sJ2ESdp
z3O0RCEGaymsZH/Htoxh2kY7oC21bT4wYpckXe1HOwo3KrkPaeBlaP+SWbQcWmnn
o70fSEEKACFzZAvsif1J
=9cQZ
-----END PGP SIGNATURE-----

From aparsons@amsl.com  Mon Apr  8 07:38:06 2013
Return-Path: <aparsons@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84DB521F97F2 for <wgchairs@ietfa.amsl.com>; Mon,  8 Apr 2013 07:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6J4DAF3tBNqz for <wgchairs@ietfa.amsl.com>; Mon,  8 Apr 2013 07:38:05 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id A927521F97EE for <wgchairs@ietf.org>; Mon,  8 Apr 2013 07:38:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A4349127845; Mon,  8 Apr 2013 07:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUIvjssPv4GK; Mon,  8 Apr 2013 07:38:05 -0700 (PDT)
Received: from [64.170.98.186] (unknown [64.170.98.186]) by c8a.amsl.com (Postfix) with ESMTPSA id 76A35127843; Mon,  8 Apr 2013 07:38:05 -0700 (PDT)
From: Ashlee Parsons <aparsons@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0BF78247-5BBD-4BA6-974E-3869B5048AE3"
Subject: THIRD Request for IETF WG and BOF Session Minutes
Date: Mon, 8 Apr 2013 07:38:11 -0700
Message-Id: <E6E0E218-7572-401B-8BEC-71E1CE6CA449@amsl.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Mon, 08 Apr 2013 07:38:57 -0700
Cc: "irsg@irtf.org" <irsg@irtf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2013 14:38:06 -0000

--Apple-Mail=_0BF78247-5BBD-4BA6-974E-3869B5048AE3
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


Dear WG Chairs and BOF Chairs,

I am still in the process of compiling the proceedings for IETF 86 and we

are still missing meeting minutes from various sessions. The cutoff

for submissions is THIS FRIDAY, 
Dear WG Chairs and BOF Chairs,

I am still in the process of compiling the proceedings for IETF 86 and we

are still missing meeting minutes from various sessions. The cutoff

for submissions is THIS FRIDAY, April 12th, 2013, and correction

submissions cutoff is Wednesday, May 1st, 2013.  Please upload

meeting minutes, as well as any presentations from your sessions, at

your earliest convenience using the Meeting Materials Manager found

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

<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>.

Alternatively, you are welcome to send them to proceedings@ietf.org

<mailto:proceedings@ietf.org> or aparsons@amsl.com

<mailto:aparsons@amsl.com> for manual posting.

 

PLEASE get this done as soon as possible!

 

I am still missing minutes from the following groups:

 

APPLICATIONS:

-       JSON

 

GENERAL:

            - IPRBIS

 

INTERNET:

-       LISP

-       TRILL

 

OPERATIONS & MANAGEMENT:

-       NETMOD

-       OPSAWG

-       V6OPS

 

REAL-TIME APPLICATIONS & INFRASTRUCTURE:

-       AVTEXT

-       MMUSIC

 

ROUTING:

-       L2VPN

-       L3VPN

-       MPLS

-       SIDR

 

SECURITY:

-       TLS

 

TRANSPORT:

-       BEHAVE

 

IRTF:

-       NMRG

, and correction

submissions cutoff is *Wednesday, May 1st, 2013*.  Please upload

meeting minutes, as well as any presentations from your sessions, at

your earliest convenience using the Meeting Materials Manager found

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

<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>.

Alternatively, you are welcome to send them to proceedings@ietf.org

<mailto:proceedings@ietf.org> or aparsons@amsl.com

<mailto:aparsons@amsl.com> for manual posting.

 

PLEASE get this done as soon as possible!

 

I am still missing minutes from the following groups:

 

APPLICATIONS:

-       JSON

 

GENERAL:

            - IPRBIS

 

INTERNET:

-       LISP

-       TRILL

 

OPERATIONS & MANAGEMENT:

-       NETMOD

-       OPSAWG

-       V6OPS

 

REAL-TIME APPLICATIONS & INFRASTRUCTURE:

-       AVTEXT

-       MMUSIC

 

ROUTING:

-       L2VPN

-       L3VPN

-       MPLS

-       SIDR

 

SECURITY:

-       TLS

 

TRANSPORT:

-       BEHAVE

 

IRTF:

-       NMRG



Ashlee Parsons
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=_0BF78247-5BBD-4BA6-974E-3869B5048AE3
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>






<!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>200</o:Words>
  <o:Characters>1140</o:Characters>
  <o:Company>AMS</o:Company>
  <o:Lines>9</o:Lines>
  <o:Paragraphs>2</o:Paragraphs>
  <o:CharactersWithSpaces>1338</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]-->

<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
   <w:UseFELayout/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="276">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->

<!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:Cambria;
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->



<!--StartFragment--><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">Dear
WG Chairs and BOF Chairs,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">I
am still in the process of compiling the proceedings for IETF 86 and we<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">are
still missing meeting minutes from various sessions. The cutoff<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">for
submissions is THIS FRIDAY,&nbsp;</span>






<!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>200</o:Words>
  <o:Characters>1140</o:Characters>
  <o:Company>AMS</o:Company>
  <o:Lines>9</o:Lines>
  <o:Paragraphs>2</o:Paragraphs>
  <o:CharactersWithSpaces>1338</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]-->

<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
   <w:UseFELayout/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="276">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]-->

<!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:Cambria;
	mso-ascii-font-family:Cambria;
	mso-ascii-theme-font:minor-latin;
	mso-hansi-font-family:Cambria;
	mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->



<!--StartFragment--><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">Dear
WG Chairs and BOF Chairs,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">I
am still in the process of compiling the proceedings for IETF 86 and we<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">are
still missing meeting minutes from various sessions. The cutoff<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">for
submissions is <b>THIS FRIDAY, April 12th, 2013</b>, and correction<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">submissions
cutoff is <b>Wednesday, May 1st, 2013</b>. &nbsp;Please upload<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">meeting
minutes, as well as any presentations from your sessions, at<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">your
earliest convenience using the Meeting Materials Manager found<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">here:
<a href="https://pub.ietf.org/proceedings/"><span style="color:windowtext">https://pub.ietf.org/proceedings/</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi"><span style="color:windowtext">https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi</span></a>&gt;.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">Alternatively,
you are welcome to send them to <a href="mailto:proceedings@ietf.org"><span style="color:windowtext">proceedings@ietf.org</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="mailto:proceedings@ietf.org"><span style="color:windowtext">mailto:proceedings@ietf.org</span></a>&gt;
or <a href="mailto:aparsons@amsl.com"><span style="color:windowtext">aparsons@amsl.com</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="mailto:aparsons@amsl.com"><span style="color:windowtext">mailto:aparsons@amsl.com</span></a>&gt;
for manual posting.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">PLEASE get
this done as soon as possible!<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">I am still
missing minutes from the following groups:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">APPLICATIONS:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">JSON<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">GENERAL:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
IPRBIS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">INTERNET:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">LISP<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">TRILL<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">OPERATIONS &amp; MANAGEMENT:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">NETMOD<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">OPSAWG<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">V6OPS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">REAL-TIME APPLICATIONS &amp; INFRASTRUCTURE:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">AVTEXT<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">MMUSIC<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">ROUTING:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">L2VPN<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">L3VPN<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">MPLS<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">SIDR<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">SECURITY:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">TLS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">TRANSPORT:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">BEHAVE<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">IRTF:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">NMRG<o:p></o:p></span></p>

<!--EndFragment--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">, and correction<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">submissions
cutoff is *Wednesday, May 1st, 2013*. &nbsp;Please upload<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">meeting
minutes, as well as any presentations from your sessions, at<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">your
earliest convenience using the Meeting Materials Manager found<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">here:
<a href="https://pub.ietf.org/proceedings/"><span style="color:windowtext">https://pub.ietf.org/proceedings/</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi"><span style="color:windowtext">https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi</span></a>&gt;.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">Alternatively,
you are welcome to send them to <a href="mailto:proceedings@ietf.org"><span style="color:windowtext">proceedings@ietf.org</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="mailto:proceedings@ietf.org"><span style="color:windowtext">mailto:proceedings@ietf.org</span></a>&gt;
or <a href="mailto:aparsons@amsl.com"><span style="color:windowtext">aparsons@amsl.com</span></a><o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&lt;<a href="mailto:aparsons@amsl.com"><span style="color:windowtext">mailto:aparsons@amsl.com</span></a>&gt;
for manual posting.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">PLEASE get
this done as soon as possible!<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">I am still
missing minutes from the following groups:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">APPLICATIONS:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin;mso-bidi-font-family:Helvetica">JSON<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">GENERAL:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
IPRBIS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">INTERNET:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">LISP<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">TRILL<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">OPERATIONS &amp; MANAGEMENT:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">NETMOD<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">OPSAWG<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">V6OPS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">REAL-TIME APPLICATIONS &amp; INFRASTRUCTURE:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">AVTEXT<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">MMUSIC<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">ROUTING:<o:p></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">L2VPN<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">L3VPN<o:p></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left:.75in;mso-add-space:
auto;text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">MPLS<o:p></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">SIDR<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">SECURITY:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">TLS<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">TRANSPORT:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">BEHAVE<o:p></o:p></span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">&nbsp;</span></p><p class="MsoNormal"><span style="font-family:Calibri;mso-ascii-theme-font:major-latin;
mso-hansi-theme-font:major-latin">IRTF:<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]-->-<span style="font-size: 7pt; font-family: 'Times New Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><!--[endif]--><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin">NMRG<o:p></o:p></span></p><p class="MsoListParagraph" style="margin-left:.75in;mso-add-space:auto;
text-indent:-.25in;mso-list:l0 level1 lfo1"><span style="font-family:Calibri;mso-ascii-theme-font:
major-latin;mso-hansi-theme-font:major-latin"><br></span></p>

<!--EndFragment--></div><div apple-content-edited="true">
<div style="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; "><div>Ashlee Parsons</div><div>IETF Registrar</div><div>48377 Fremont Blvd, Ste. 117</div><div>Fremont, CA 94538</div><div><br></div><div>Association Management Solutions (AMS)</div><div>Forum Management, Meeting and Event Planning</div><div><a href="http://www.amsl.com">www.amsl.com</a></div><div><br></div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></body></html>
--Apple-Mail=_0BF78247-5BBD-4BA6-974E-3869B5048AE3--

From aparsons@amsl.com  Thu Apr 11 07:52:42 2013
Return-Path: <aparsons@amsl.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60CE21F8D90 for <wgchairs@ietfa.amsl.com>; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32Far3D2MUJC for <wgchairs@ietfa.amsl.com>; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2980F21F8D6A for <wgchairs@ietf.org>; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 26733127811; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CeeVnNBp-gDV; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
Received: from [64.170.98.186] (unknown [64.170.98.186]) by c8a.amsl.com (Postfix) with ESMTPSA id 08E49127805; Thu, 11 Apr 2013 07:52:42 -0700 (PDT)
From: Ashlee Parsons <aparsons@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4C46C7E1-18DE-4FF7-8137-BE03C82CFB10"
Subject: FINAL Request for IETF WG and BOF Session Minutes!!!!!!
Date: Thu, 11 Apr 2013 07:52:42 -0700
Message-Id: <EB86A989-5368-43C6-9C10-D879FDF315C6@amsl.com>
To: "wgchairs@ietf.org" <wgchairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-Mailman-Approved-At: Thu, 11 Apr 2013 07:57:28 -0700
Cc: "irsg@irtf.org" <irsg@irtf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2013 14:52:43 -0000

--Apple-Mail=_4C46C7E1-18DE-4FF7-8137-BE03C82CFB10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear WG Chairs and BOF Chairs,

I am completing process of compiling the proceedings for IETF 86 and we =
are STILL missing meeting minutes from various sessions. The cutoff for =
submissions is TOMORROW (Friday), April 12, 2013, and correction =
submissions cutoff is Wednesday, May 1st, 2013.  Please upload meeting =
minutes, as well as any presentations from your sessions, now. Please =
use the Meeting Materials Manager found here: =
https://pub.ietf.org/proceedings/

<https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi>.

Alternatively, you are welcome to send them to proceedings@ietf.org

<mailto:proceedings@ietf.org> or aparsons@amsl.com

<mailto:aparsons@amsl.com> for manual posting.

PLEASE get this done now!=20

I am still missing minutes from the following groups:=20

INTERNET:

-       TRILL

OPERATIONS & MANAGEMENT:

-       NETMOD

-       V6OPS

REAL-TIME APPLICATIONS & INFRASTRUCTURE:

-       AVTEXT

-       MMUSIC

ROUTING:

-       L2VPN

-       MPLS

-       SIDR=20

SECURITY:

-       TLS

Ashlee Parsons
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=_4C46C7E1-18DE-4FF7-8137-BE03C82CFB10
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; "><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">Dear WG =
Chairs and BOF Chairs,<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family: Calibri; ">I am completing process of compiling =
the proceedings for IETF 86 and we&nbsp;</span><span style=3D"font-family:=
 Calibri; ">are STILL missing meeting minutes from various sessions. The =
cutoff&nbsp;</span><span style=3D"font-family: Calibri; ">for =
submissions is <b>TOMORROW (Friday), April 12, 2013</b></span><span =
style=3D"font-family: Calibri; ">, and correction&nbsp;</span><span =
style=3D"font-family: Calibri; ">submissions cutoff is</span><span =
style=3D"font-family: Calibri; ">&nbsp;</span><b style=3D"font-family: =
Calibri; ">Wednesday, May 1st, 2013</b><span style=3D"font-family: =
Calibri; ">. &nbsp;Please upload&nbsp;</span><span style=3D"font-family: =
Calibri; ">meeting minutes, as well as any presentations from your =
sessions, now. Please</span><span style=3D"font-family: Calibri; =
">&nbsp;use the Meeting Materials Manager found&nbsp;</span><span =
style=3D"font-family: Calibri; ">here:</span><span style=3D"font-family: =
Calibri; ">&nbsp;</span><a href=3D"https://pub.ietf.org/proceedings/" =
style=3D"font-family: Calibri; "><span style=3D"color: windowtext; =
">https://pub.ietf.org/proceedings/</span></a></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">&lt;<a =
href=3D"https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi"><span =
style=3D"color: windowtext; =
">https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi</span></a>&gt=
;.<o:p></o:p></span></p><p class=3D"MsoNormal"><span style=3D"font-family:=
 Calibri; ">Alternatively, you are welcome to send them to&nbsp;<a =
href=3D"mailto:proceedings@ietf.org"><span style=3D"color: windowtext; =
">proceedings@ietf.org</span></a><o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">&lt;<a =
href=3D"mailto:proceedings@ietf.org"><span style=3D"color: windowtext; =
">mailto:proceedings@ietf.org</span></a>&gt; or&nbsp;<a =
href=3D"mailto:aparsons@amsl.com"><span style=3D"color: windowtext; =
">aparsons@amsl.com</span></a><o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">&lt;<a =
href=3D"mailto:aparsons@amsl.com"><span style=3D"color: windowtext; =
">mailto:aparsons@amsl.com</span></a>&gt; for manual =
posting.</span></p><p class=3D"MsoNormal"><span style=3D"font-family: =
Calibri; "><b>PLEASE get this done now!</b></span><span =
style=3D"font-family: Calibri; ">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">I am still =
missing minutes from the following groups:</span><span =
style=3D"font-family: Calibri; ">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; =
">INTERNET:</span></p><p class=3D"MsoListParagraphCxSpLast" =
style=3D"margin-left: 0.75in; text-indent: -0.25in; ">-<span =
style=3D"font-size: 7pt; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">TRILL</span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">OPERATIONS =
&amp; MANAGEMENT:<o:p></o:p></span></p><p =
class=3D"MsoListParagraphCxSpFirst" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">NETMOD</span></p><p =
class=3D"MsoListParagraphCxSpLast" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">V6OPS</span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; ">REAL-TIME =
APPLICATIONS &amp; INFRASTRUCTURE:<o:p></o:p></span></p><p =
class=3D"MsoListParagraphCxSpFirst" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">AVTEXT<o:p></o:p></span></p><p =
class=3D"MsoListParagraphCxSpLast" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">MMUSIC</span></p><p =
class=3D"MsoNormal"><span style=3D"font-family: Calibri; =
">ROUTING:<o:p></o:p></span></p><p class=3D"MsoListParagraphCxSpFirst" =
style=3D"margin-left: 0.75in; text-indent: -0.25in; ">-<span =
style=3D"font-size: 7pt; font-family: 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">L2VPN</span></p><p =
class=3D"MsoListParagraphCxSpMiddle" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">MPLS<o:p></o:p></span></p><p =
class=3D"MsoListParagraphCxSpLast" style=3D"margin-left: 0.75in; =
text-indent: -0.25in; ">-<span style=3D"font-size: 7pt; font-family: =
'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">SIDR</span><span style=3D"font-family: =
Calibri; ">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"font-family: Calibri; ">SECURITY:<o:p></o:p></span></p><p =
class=3D"MsoListParagraph" style=3D"margin-left: 0.75in; text-indent: =
-0.25in; ">-<span style=3D"font-size: 7pt; font-family: 'Times New =
Roman'; ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span><span =
style=3D"font-family: Calibri; ">TLS</span></p><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; =
"><div>Ashlee Parsons</div><div>IETF Registrar</div><div>48377 Fremont =
Blvd, Ste. 117</div><div>Fremont, CA =
94538</div><div><br></div><div>Association Management Solutions =
(AMS)</div><div>Forum Management, Meeting and Event =
Planning</div><div><a =
href=3D"http://www.amsl.com">www.amsl.com</a></div><div><br></div><div><br=
></div></div><br class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_4C46C7E1-18DE-4FF7-8137-BE03C82CFB10--

From derek@ihtfp.com  Fri Apr 19 08:24:46 2013
Return-Path: <derek@ihtfp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C5F21F85C3 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.988
X-Spam-Level: 
X-Spam-Status: No, score=-101.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flIkOSQ9HjWI for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:24:31 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) by ietfa.amsl.com (Postfix) with ESMTP id B474821F87B1 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 08:24:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id EF0C8260261 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 11:24:17 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 05413-10 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 11:24:10 -0400 (EDT)
Received: from mocana.ihtfp.org (unknown [IPv6:fe80::224:d7ff:fee7:8924]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (not verified)) by mail2.ihtfp.org (Postfix) with ESMTPS id 31B1F26002D for <wgchairs@ietf.org>; Fri, 19 Apr 2013 11:24:10 -0400 (EDT)
Received: (from warlord@localhost) by mocana.ihtfp.org (8.14.5/8.14.5/Submit) id r3JFO9JU010075; Fri, 19 Apr 2013 11:24:09 -0400
From: Derek Atkins <derek@ihtfp.com>
To: wgchairs@ietf.org
Subject: Help re-marking an expired, renamed draft?
Date: Fri, 19 Apr 2013 11:24:09 -0400
Message-ID: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.2a
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 15:24:46 -0000

Hi,

I received the following request from one of my WG document authors.  We
renamed a draft from a personally-named draft to a WG-named draft, but
somehow missed the window to get a tombstone installed.  Is there some
way in the data tracker for me to get a tombstone installed?

Thanks,

> http://tools.ietf.org/html/draft-jones-json-web-token-10 doesn=E2=80=99t =
say
> that it=E2=80=99s been superseded by
> http://tools.ietf.org/html/draft-ietf-oauth-json-web-token .  I know
> that the tool supports it, because, for instance, if you go to
> http://tools.ietf.org/html/draft-jones-json-web-signature-04 you=E2=80=99=
ll
> see that it=E2=80=99s been marked as having been superseded by the
> draft-ietf-jose version.
>
> Could one of you do what it takes to mark the draft-jones version as obso=
lete?
>   I just ran across somebody using it today!

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

From housley@vigilsec.com  Fri Apr 19 08:38:49 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399AE21F9629 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:38:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4+V7mK0VsjJ for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:38:48 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 71A9621F961B for <wgchairs@ietf.org>; Fri, 19 Apr 2013 08:38:48 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4B6E8F24078; Fri, 19 Apr 2013 11:39:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id y9ex+x5hfWof; Fri, 19 Apr 2013 11:38:36 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1C1DEF2406E; Fri, 19 Apr 2013 11:39:02 -0400 (EDT)
Subject: Re: Help re-marking an expired, renamed draft?
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
Date: Fri, 19 Apr 2013 11:38:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <06BBE1E0-3734-4EBA-99D9-AAB50D746C73@vigilsec.com>
References: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
To: Derek Atkins <derek@ihtfp.com>
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 15:38:49 -0000

As the Secretariat to insert the Replaced-By record in the datatracker.

In this case, draft-jones-json-web-token is replaced by =
draft-ietf-oauth-json-web-token.

Russ


On Apr 19, 2013, at 11:24 AM, Derek Atkins wrote:

> Hi,
>=20
> I received the following request from one of my WG document authors.  =
We
> renamed a draft from a personally-named draft to a WG-named draft, but
> somehow missed the window to get a tombstone installed.  Is there some
> way in the data tracker for me to get a tombstone installed?
>=20
> Thanks,
>=20
>> http://tools.ietf.org/html/draft-jones-json-web-token-10 doesn=92t =
say
>> that it=92s been superseded by
>> http://tools.ietf.org/html/draft-ietf-oauth-json-web-token .  I know
>> that the tool supports it, because, for instance, if you go to
>> http://tools.ietf.org/html/draft-jones-json-web-signature-04 you=92ll
>> see that it=92s been marked as having been superseded by the
>> draft-ietf-jose version.
>>=20
>> Could one of you do what it takes to mark the draft-jones version as =
obsolete?
>>  I just ran across somebody using it today!
>=20
> -derek
> --=20
>       Derek Atkins                 617-623-3745
>       derek@ihtfp.com             www.ihtfp.com
>       Computer and Internet Security Consultant


From adrian@olddog.co.uk  Fri Apr 19 08:39:22 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 299CB21F87B1 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8n4T9wRcRj-i for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:39:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 41AA121F8C30 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 08:39:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3JFdKU0005541;  Fri, 19 Apr 2013 16:39:20 +0100
Received: from 950129200 (50-76-52-225-ip-static.hfc.comcastbusiness.net [50.76.52.225]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3JFdHpZ005470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 16:39:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Derek Atkins'" <derek@ihtfp.com>, <wgchairs@ietf.org>
References: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
In-Reply-To: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
Subject: RE: Help re-marking an expired, renamed draft?
Date: Fri, 19 Apr 2013 16:39:16 +0100
Message-ID: <034a01ce3d14$0e6f52a0$2b4df7e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQErsKTfQM7JMFeGPqNfE3aPynDIHJoixoaQ
Content-Language: en-gb
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 15:39:22 -0000

Derek,

Send mail to the Secretariat saying "Please mark =
draft-jones-json-web-token as replaced by =
draft-ietf-oauth-json-web-token."

Adrian

> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf =
Of Derek
> Atkins
> Sent: 19 April 2013 16:24
> To: wgchairs@ietf.org
> Subject: Help re-marking an expired, renamed draft?
>=20
> Hi,
>=20
> I received the following request from one of my WG document authors.  =
We
> renamed a draft from a personally-named draft to a WG-named draft, but
> somehow missed the window to get a tombstone installed.  Is there some
> way in the data tracker for me to get a tombstone installed?
>=20
> Thanks,
>=20
> > http://tools.ietf.org/html/draft-jones-json-web-token-10 =
doesn=E2=80=99t say
> > that it=E2=80=99s been superseded by
> > http://tools.ietf.org/html/draft-ietf-oauth-json-web-token .  I know
> > that the tool supports it, because, for instance, if you go to
> > http://tools.ietf.org/html/draft-jones-json-web-signature-04 =
you=E2=80=99ll
> > see that it=E2=80=99s been marked as having been superseded by the
> > draft-ietf-jose version.
> >
> > Could one of you do what it takes to mark the draft-jones version as =
obsolete?
> >   I just ran across somebody using it today!
>=20
> -derek
> --
>        Derek Atkins                 617-623-3745
>        derek@ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant


From derek@ihtfp.com  Fri Apr 19 08:48:55 2013
Return-Path: <derek@ihtfp.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246C121F9640 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iH3jc27X2zx5 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 08:48:54 -0700 (PDT)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:4830:143:1::3a11]) by ietfa.amsl.com (Postfix) with ESMTP id 0662921F9630 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 08:48:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id E249B26002D; Fri, 19 Apr 2013 11:48:52 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 05646-03; Fri, 19 Apr 2013 11:48:50 -0400 (EDT)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id 2DC92260296; Fri, 19 Apr 2013 11:48:50 -0400 (EDT)
Received: from 192.168.248.158 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Fri, 19 Apr 2013 11:48:50 -0400
Message-ID: <91ef27a27b54a1c48483653940b3c863.squirrel@mail2.ihtfp.org>
In-Reply-To: <034a01ce3d14$0e6f52a0$2b4df7e0$@olddog.co.uk>
References: <sjmy5cek0h2.fsf@mocana.ihtfp.org> <034a01ce3d14$0e6f52a0$2b4df7e0$@olddog.co.uk>
Date: Fri, 19 Apr 2013 11:48:50 -0400
Subject: RE: Help re-marking an expired, renamed draft?
From: "Derek Atkins" <derek@ihtfp.com>
To: adrian@olddog.co.uk
User-Agent: SquirrelMail/1.4.22-2.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 15:48:55 -0000

Thanks.  I guess I expected some way to do this in the data tracker.
I'll go send mail.

-derek

On Fri, April 19, 2013 11:39 am, Adrian Farrel wrote:
> Derek,
>
> Send mail to the Secretariat saying "Please mark
> draft-jones-json-web-token as replaced by
> draft-ietf-oauth-json-web-token."
>
> Adrian
>
>> -----Original Message-----
>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
>> Derek
>> Atkins
>> Sent: 19 April 2013 16:24
>> To: wgchairs@ietf.org
>> Subject: Help re-marking an expired, renamed draft?
>>
>> Hi,
>>
>> I received the following request from one of my WG document authors.  We
>> renamed a draft from a personally-named draft to a WG-named draft, but
>> somehow missed the window to get a tombstone installed.  Is there some
>> way in the data tracker for me to get a tombstone installed?
>>
>> Thanks,
>>
>> > http://tools.ietf.org/html/draft-jones-json-web-token-10 doesn’t say
>> > that it’s been superseded by
>> > http://tools.ietf.org/html/draft-ietf-oauth-json-web-token .  I know
>> > that the tool supports it, because, for instance, if you go to
>> > http://tools.ietf.org/html/draft-jones-json-web-signature-04 you’ll
>> > see that it’s been marked as having been superseded by the
>> > draft-ietf-jose version.
>> >
>> > Could one of you do what it takes to mark the draft-jones version as
>> obsolete?
>> >   I just ran across somebody using it today!
>>
>> -derek
>> --
>>        Derek Atkins                 617-623-3745
>>        derek@ihtfp.com             www.ihtfp.com
>>        Computer and Internet Security Consultant
>
>


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


From martin.vigoureux@alcatel-lucent.com  Fri Apr 19 10:17:54 2013
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7A121F8F05 for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 10:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RK3cr0D6nc2N for <wgchairs@ietfa.amsl.com>; Fri, 19 Apr 2013 10:17:53 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 97EFF21F9616 for <wgchairs@ietf.org>; Fri, 19 Apr 2013 10:17:53 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r3JHHqxZ027222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Apr 2013 12:17:53 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id r3JHHqDk014276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Apr 2013 13:17:52 -0400
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 19 Apr 2013 13:17:52 -0400
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.46]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 19 Apr 2013 19:17:49 +0200
From: "VIGOUREUX, MARTIN (MARTIN)" <martin.vigoureux@alcatel-lucent.com>
To: Derek Atkins <derek@ihtfp.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: Help re-marking an expired, renamed draft?
Thread-Topic: Help re-marking an expired, renamed draft?
Thread-Index: AQHOPRIVua5UpKyyMkiN8ZvVuczu8pjdyX0K
Date: Fri, 19 Apr 2013 17:17:48 +0000
Message-ID: <FEA27CFACBAF3A429E381E6FD69CDC7305C0E2@FR712WXCHMBA09.zeu.alcatel-lucent.com>
References: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
In-Reply-To: <sjmy5cek0h2.fsf@mocana.ihtfp.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_FEA27CFACBAF3A429E381E6FD69CDC7305C0E2FR712WXCHMBA09zeu_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2013 17:17:54 -0000

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

Derek

If you look at the datatracker for these drafts, the replacement info is in=
dicated, but it is not on tools.ietf.org
I noticed that some differences exist between the datatracker and tools.iet=
f.org regarding replacement info.
Henrik should be able to tell you more on this.

-m
________________________________
De : Derek Atkins
Envoy=E9 : 19/04/2013 17:25
=C0 : wgchairs@ietf.org
Objet : Help re-marking an expired, renamed draft?

Hi,

I received the following request from one of my WG document authors.  We
renamed a draft from a personally-named draft to a WG-named draft, but
somehow missed the window to get a tombstone installed.  Is there some
way in the data tracker for me to get a tombstone installed?

Thanks,

> http://tools.ietf.org/html/draft-jones-json-web-token-10 doesn=92t say
> that it=92s been superseded by
> http://tools.ietf.org/html/draft-ietf-oauth-json-web-token .  I know
> that the tool supports it, because, for instance, if you go to
> http://tools.ietf.org/html/draft-jones-json-web-signature-04 you=92ll
> see that it=92s been marked as having been superseded by the
> draft-ietf-jose version.
>
> Could one of you do what it takes to mark the draft-jones version as obso=
lete?
>   I just ran across somebody using it today!

-derek
--
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com<http://www.ihtfp.com>
       Computer and Internet Security Consultant

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Derek<br>
<br>
If you look at the datatracker for these drafts, the replacement info is in=
dicated, but it is not on tools.ietf.org<br>
I noticed that some differences exist between the datatracker and tools.iet=
f.org regarding replacement info.<br>
Henrik should be able to tell you more on this.<br>
<br>
-m<br>
</div>
</div>
<hr>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">De :
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">Derek =
Atkins</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">Envoy=E9 :
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">19/04/=
2013 17:25</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">=C0&nbsp;:
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">wgchai=
rs@ietf.org</span><br>
<span style=3D"font-family:Tahoma,sans-serif; font-size:10pt; font-weight:b=
old">Objet :
</span><span style=3D"font-family:Tahoma,sans-serif; font-size:10pt">Help r=
e-marking an expired, renamed draft?</span><br>
<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Hi,<br>
<br>
I received the following request from one of my WG document authors.&nbsp; =
We<br>
renamed a draft from a personally-named draft to a WG-named draft, but<br>
somehow missed the window to get a tombstone installed.&nbsp; Is there some=
<br>
way in the data tracker for me to get a tombstone installed?<br>
<br>
Thanks,<br>
<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-jones-json-web-token-10">h=
ttp://tools.ietf.org/html/draft-jones-json-web-token-10</a> doesn=92t say<b=
r>
&gt; that it=92s been superseded by<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-oauth-json-web-token"=
>http://tools.ietf.org/html/draft-ietf-oauth-json-web-token</a> .&nbsp; I k=
now<br>
&gt; that the tool supports it, because, for instance, if you go to<br>
&gt; <a href=3D"http://tools.ietf.org/html/draft-jones-json-web-signature-0=
4">http://tools.ietf.org/html/draft-jones-json-web-signature-04</a> you=92l=
l<br>
&gt; see that it=92s been marked as having been superseded by the<br>
&gt; draft-ietf-jose version.<br>
&gt;<br>
&gt; Could one of you do what it takes to mark the draft-jones version as o=
bsolete?<br>
&gt;&nbsp;&nbsp; I just ran across somebody using it today!<br>
<br>
-derek<br>
-- <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Derek Atkins&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 617-=
623-3745<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; derek@ihtfp.com&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"http://www.iht=
fp.com">www.ihtfp.com</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Computer and Internet Security Consult=
ant<br>
</div>
</span></font>
</body>
</html>

--_000_FEA27CFACBAF3A429E381E6FD69CDC7305C0E2FR712WXCHMBA09zeu_--

From iad@ietf.org  Mon Apr 22 03:30:36 2013
Return-Path: <iad@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445E821E8045; Mon, 22 Apr 2013 03:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmbgQZBsd7ko; Mon, 22 Apr 2013 03:30:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A28C21F8EB1; Mon, 22 Apr 2013 03:30:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IAOC Announces Meeting Registration Gender Data Gathering Decision
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p3
Message-ID: <20130422103024.15473.141.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2013 03:30:24 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 10:30:36 -0000

On 11 April the IAOC announced that it was considering asking for =

gender information during the IETF meeting registration process =

starting with IETF 87, and asked for the community to provide feedback =

by 17 April as the IAOC planned to make a decision on 18 April.

The data is being gathered to benchmark and track gender participation =

at IETF meetings currently, over time, and to inform IETF diversity =

initiatives should any be undertaken.

The IAOC appreciates the feedback provided directly and the thoughtful =

discussion on the list.

After considering the feedback from the community and counsel, the =

IAOC approved the collection of gender data on the IETF meeting =

registration form.

A question about gender will be added to the registration form =

starting with the Berlin meeting (IETF 87).

Answering the gender question will of course be optional and the =

gender data will not be associated with individual registration =

records and only retained and reported in aggregate form.

Thanks again for your input.

Bob Hinden
Chair

From bclaise@cisco.com  Mon Apr 22 06:51:05 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E795421F90A1 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 06:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.981
X-Spam-Level: 
X-Spam-Status: No, score=-9.981 tagged_above=-999 required=5 tests=[AWL=-0.451, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6nvHRmb59xu for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 06:51:04 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6D021F905F for <wgchairs@ietf.org>; Mon, 22 Apr 2013 06:51:03 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3MDoxYs008555 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:50:59 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3MDoiWg000746 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:50:54 +0200 (CEST)
Message-ID: <5174E1DA.7020904@cisco.com>
Date: Mon, 22 Apr 2013 09:08:10 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: WG Chairs <wgchairs@ietf.org>
Subject: Document shepherd role
References: <5172F297.2080301@bogus.com>
In-Reply-To: <5172F297.2080301@bogus.com>
X-Forwarded-Message-Id: <5172F297.2080301@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 13:51:05 -0000

IETF WG chairs,

We sent a similar message to the operations an management area chairs.
Therefore if you have seen the contents before, apologies, the resulting
IESG discussion has indicated that we should distribute it more widely.

During the last IETF meeting, the community discussed a lot about the
transport AD situation. One aspect of this is the time commitment for an
AD position!

During the last IETF meeting, the community discussed a lot about
diversity. All sort of diversities, including the IESG diversity. One
specific aspect is the diversity of IESG member affiliations.

Let me share my experience after one year of service as AD.
1. Yes, I like this job. I believe it makes a positive a difference for
the Internet (hopefully positive, you'll be the judges, but that's not
the point of this email )
2. Yes, this AD role requires (more than) a full time job if done
conscientiously.
3. I'm concerned that we slowly created a set of requirements for an
IESG position that will make difficult to find ADs in the future ...
except from big companies, or when dedicated funding is allocated. Not
good for diversity.
4. Believe it or not, one substantial part of my OPS activities is the
follow up on the open issues. Recently, for a single draft, I spent
hoouuurrrssss trying to track all the open issues from the directorates
and the IESG, and chasing the authors. On top of taking some time, I had
to be become expert for every single aspect of the specifications to
evaluate whether the answer was right. After all, I have to defend your
WG document during the IESG call.

Considering the discussion above, let me focus on one important role
within the community: the document shepherd.  This job, when done
according to RFC 4858 would free up a huge amount of time for the ADs,
and would speed up the document publication.

Please read RFC 4858, specifically
      3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
      3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10

Bottom line, the document shepherd job doesn't stop when the write-up is
sent.
I would like the document shepherds to follow the RFC 4858 instructions.
Specifically concerning the follow up part.
That being said, the shepherd, chairs, and the WG participants together
are the custodians of WG output. So the obligations isn't solely
invested in the shepherds. Their role via the questionnaire
fundamentally is to document that the things required have been done,
and to manage the remainder of the process.

To come back to the first paragraph of my email, the document shepherd
job (let me stress again, when done according to the function described
in RFC 4858) would be beneficial for the entire community longer term.
Let me explain: if the AD job was not a full time job, it might be
easier to have diversity in the pool of AD candidates.

This message was sent to all OPS WG chairs, and is now being distributed
more widely.

Also, let's keep in mind that it's not a requirement that only WG chairs
are document shepherds. See
http://www.ietf.org/iesg/statement/document-shepherds.html,The Shepherds
role is a source of valuable insight into the later stages of the RFC
process and a stepping stone for competency in other IETF roles.

Regards, Benoit




From lee.howard@twcable.com  Mon Apr 22 12:37:44 2013
Return-Path: <lee.howard@twcable.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E939321E804C for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 12:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SARE_WEOFFER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DoTh55TmkVuh for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 12:37:44 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3731B11E80D9 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 12:37:44 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.87,528,1363147200"; d="scan'208";a="61158800"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Apr 2013 15:36:54 -0400
Received: from PRVPEXVS17.corp.twcable.com ([10.136.163.96]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Mon, 22 Apr 2013 15:37:43 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Benoit Claise <bclaise@cisco.com>, WG Chairs <wgchairs@ietf.org>
Date: Mon, 22 Apr 2013 15:37:42 -0400
Subject: Re: Document shepherd role
Thread-Topic: Document shepherd role
Thread-Index: Ac4/kNtxLZ679CgmQyW2Zfr3FLpWxQ==
Message-ID: <CD9B0317.1B7A2%lee.howard@twcable.com>
In-Reply-To: <5174E1DA.7020904@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 19:37:45 -0000

On 4/22/13 3:08 AM, "Benoit Claise" <bclaise@cisco.com> wrote:
...
>
>Please read RFC 4858, specifically
>      3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
>      3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10

...

>
>
>To come back to the first paragraph of my email, the document shepherd
>job (let me stress again, when done according to the function described
>in RFC 4858) would be beneficial for the entire community longer term.
>Let me explain: if the AD job was not a full time job, it might be
>easier to have diversity in the pool of AD candidates.

Can we offer some recognition for Document Shepherds? I don't think they
even get listed in the Acknowledgments section, unless they have already
contributed.  Unlike Author, Contributor, WG Chair, AD, Directorate, and
Secretary, the Shepherd toils in anonymity.

Shepherding is good experience for a future WG chair.  It would be nice to
recognize the work in and of itself.

Lee


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

From stpeter@stpeter.im  Mon Apr 22 12:45:38 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1DEF21F9349 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 12:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.036
X-Spam-Level: 
X-Spam-Status: No, score=-102.036 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, SARE_WEOFFER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tUnwu65-Hyv for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 12:45:38 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1EA21F9347 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 12:45:38 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0E7DE41026; Mon, 22 Apr 2013 13:56:24 -0600 (MDT)
Message-ID: <51759361.3070405@stpeter.im>
Date: Mon, 22 Apr 2013 13:45:37 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Howard, Lee" <lee.howard@twcable.com>
Subject: Re: Document shepherd role
References: <CD9B0317.1B7A2%lee.howard@twcable.com>
In-Reply-To: <CD9B0317.1B7A2%lee.howard@twcable.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 19:45:39 -0000

On 4/22/13 1:37 PM, Howard, Lee wrote:

> Can we offer some recognition for Document Shepherds? I don't think they
> even get listed in the Acknowledgments section, unless they have already
> contributed.  Unlike Author, Contributor, WG Chair, AD, Directorate, and
> Secretary, the Shepherd toils in anonymity.

Not always... :-)

http://tools.ietf.org/html/draft-saintandre-impp-call-info-02#appendix-A

This is something we can all do as document authors and WG chairs.

> Shepherding is good experience for a future WG chair.  It would be nice to
> recognize the work in and of itself.

+1

Peter



From bclaise@cisco.com  Mon Apr 22 13:10:55 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B14821E80DD for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 13:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.337
X-Spam-Level: 
X-Spam-Status: No, score=-10.337 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_WEOFFER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfqDeEIz-owS for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 13:10:54 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 5988021E80D8 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 13:10:54 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3MKApRj013408; Mon, 22 Apr 2013 22:10:51 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3MK9uOD021072; Mon, 22 Apr 2013 22:10:11 +0200 (CEST)
Message-ID: <51759913.7050000@cisco.com>
Date: Mon, 22 Apr 2013 22:09:55 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Document shepherd role
References: <CD9B0317.1B7A2%lee.howard@twcable.com> <51759361.3070405@stpeter.im>
In-Reply-To: <51759361.3070405@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: WG Chairs <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 20:10:55 -0000

On 22/04/2013 21:45, Peter Saint-Andre wrote:
> On 4/22/13 1:37 PM, Howard, Lee wrote:
>
>> Can we offer some recognition for Document Shepherds? I don't think they
>> even get listed in the Acknowledgments section, unless they have already
>> contributed.  Unlike Author, Contributor, WG Chair, AD, Directorate, and
>> Secretary, the Shepherd toils in anonymity.
> Not always... :-)
>
> http://tools.ietf.org/html/draft-saintandre-impp-call-info-02#appendix-A
>
> This is something we can all do as document authors and WG chairs.
>
>> Shepherding is good experience for a future WG chair.  It would be nice to
>> recognize the work in and of itself.
That makes a lot of sense.
And I like the way Peter did it in the example above.

Regards, Benoit

From pkyzivat@alum.mit.edu  Mon Apr 22 14:46:07 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9749021F87B7 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 14:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KE1qMGqB6JjD for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 14:46:06 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 26C7C21F87B1 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 14:46:02 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta02.westchester.pa.mail.comcast.net with comcast id SzMR1l0051GhbT8519m1h3; Mon, 22 Apr 2013 21:46:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id T9m11l00k3ZTu2S3T9m1nk; Mon, 22 Apr 2013 21:46:01 +0000
Message-ID: <5175AF99.4020408@alum.mit.edu>
Date: Mon, 22 Apr 2013 17:46:01 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: wgchairs@ietf.org
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com>
In-Reply-To: <5174E1DA.7020904@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366667162; bh=bm/sQ4ZYmjGtP0jlJr/u9jOY+DiKj9ml6sAtU8JB2ps=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YxsgX28NAos7afiuonZ8HhNkRdEO3KR6aTLvOlEzLqFCxZjLwEzLDRneK3031PyG+ zO8wx1P8mTpNcpylAReGvOyRSdSwfMqOwRsNa8HYYcIH1imPPije7remmhc/2dzXEd E3IgOCwG7+6tPk4EqcDBOoeBco2PReC7mR5wqwhPE4H5sXli01KIK38ov061C/7rQu cL/ahlXLNPkHrjmRGvEv1V/+9Wc03USgxPbsE9/PK5yIXd7sW5ott/9HNAlBOoVYPO KjL/mrG4NQ9NOUd04PdJSTjiqi6ekJyUuQI90M7s8s5R5Xz931Akix8hTzA31pTlHv 5xo8bQxJTc3dw==
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 21:46:07 -0000

I found this discussion enlightening.

I'd like to add a slightly different, but related, suggestion:

Several times now when I have shepherded a draft, I start doing the 
writeup and realize it would have been really helpful to started on that 
writeup sooner - even before the document was ready for progression. My 
conclusion is that it would probably be good to assign a shepherd to a 
document as soon as it is adopted as a wg draft. (Assuming there is an 
intent that it become an RFC.) And then the shepherd can *start* filling 
out the template early. That way, after WGLC it won't take a lot of 
research, and a good memory, to fill in everything.

	Thanks,
	Paul

On 4/22/13 3:08 AM, Benoit Claise wrote:
> IETF WG chairs,
>
> We sent a similar message to the operations an management area chairs.
> Therefore if you have seen the contents before, apologies, the resulting
> IESG discussion has indicated that we should distribute it more widely.
>
> During the last IETF meeting, the community discussed a lot about the
> transport AD situation. One aspect of this is the time commitment for an
> AD position!
>
> During the last IETF meeting, the community discussed a lot about
> diversity. All sort of diversities, including the IESG diversity. One
> specific aspect is the diversity of IESG member affiliations.
>
> Let me share my experience after one year of service as AD.
> 1. Yes, I like this job. I believe it makes a positive a difference for
> the Internet (hopefully positive, you'll be the judges, but that's not
> the point of this email )
> 2. Yes, this AD role requires (more than) a full time job if done
> conscientiously.
> 3. I'm concerned that we slowly created a set of requirements for an
> IESG position that will make difficult to find ADs in the future ...
> except from big companies, or when dedicated funding is allocated. Not
> good for diversity.
> 4. Believe it or not, one substantial part of my OPS activities is the
> follow up on the open issues. Recently, for a single draft, I spent
> hoouuurrrssss trying to track all the open issues from the directorates
> and the IESG, and chasing the authors. On top of taking some time, I had
> to be become expert for every single aspect of the specifications to
> evaluate whether the answer was right. After all, I have to defend your
> WG document during the IESG call.
>
> Considering the discussion above, let me focus on one important role
> within the community: the document shepherd.  This job, when done
> according to RFC 4858 would free up a huge amount of time for the ADs,
> and would speed up the document publication.
>
> Please read RFC 4858, specifically
>       3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
>       3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10
>
> Bottom line, the document shepherd job doesn't stop when the write-up is
> sent.
> I would like the document shepherds to follow the RFC 4858 instructions.
> Specifically concerning the follow up part.
> That being said, the shepherd, chairs, and the WG participants together
> are the custodians of WG output. So the obligations isn't solely
> invested in the shepherds. Their role via the questionnaire
> fundamentally is to document that the things required have been done,
> and to manage the remainder of the process.
>
> To come back to the first paragraph of my email, the document shepherd
> job (let me stress again, when done according to the function described
> in RFC 4858) would be beneficial for the entire community longer term.
> Let me explain: if the AD job was not a full time job, it might be
> easier to have diversity in the pool of AD candidates.
>
> This message was sent to all OPS WG chairs, and is now being distributed
> more widely.
>
> Also, let's keep in mind that it's not a requirement that only WG chairs
> are document shepherds. See
> http://www.ietf.org/iesg/statement/document-shepherds.html,The Shepherds
> role is a source of valuable insight into the later stages of the RFC
> process and a stepping stone for competency in other IETF roles.
>
> Regards, Benoit
>
>
>
>


From mrw@lilacglade.org  Mon Apr 22 14:54:38 2013
Return-Path: <mrw@lilacglade.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBF921E809C for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 14:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuiKkk2CFfIk for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 14:54:37 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id BAECB21E8088 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 14:54:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 4844220218; Mon, 22 Apr 2013 17:52:39 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wOZNmS2O78iL; Mon, 22 Apr 2013 17:52:38 -0400 (EDT)
Received: from new-host-4.home (pool-71-184-79-25.bstnma.fios.verizon.net [71.184.79.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: mrw@mail.suchdamage.org) by mail.painless-security.com (Postfix) with ESMTPSA; Mon, 22 Apr 2013 17:52:38 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Document shepherd role
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <5175AF99.4020408@alum.mit.edu>
Date: Mon, 22 Apr 2013 17:54:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A159B9B4-DBE3-4CD8-8E28-23D88D9B5168@lilacglade.org>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1499)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 21:54:38 -0000

In busy working groups, ones with a lot of documents, it isn't unusual =
for the chairs to divide up responsibility for the active WG drafts.  =
When those drafts go into the IESG, the WG chair who has been =
responsible for the document during the WG process usually shepherds the =
draft through the IESG.  That works pretty well, in my experience.

In less busy groups, ones with fewer drafts, the chairs may work =
together on all of the documents.  They then have to assign a shepherd =
at the end.  Depending on the roles of the individual chairs, this can =
work well, but sometimes the chair needs to fill in a lot of knowledge =
to do the shepherding task.  In these cases, I agree it might make sense =
to explicitly decide who will shepherd the draft earlier in the process.

Margaret

On Apr 22, 2013, at 5:46 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> I found this discussion enlightening.
>=20
> I'd like to add a slightly different, but related, suggestion:
>=20
> Several times now when I have shepherded a draft, I start doing the =
writeup and realize it would have been really helpful to started on that =
writeup sooner - even before the document was ready for progression. My =
conclusion is that it would probably be good to assign a shepherd to a =
document as soon as it is adopted as a wg draft. (Assuming there is an =
intent that it become an RFC.) And then the shepherd can *start* filling =
out the template early. That way, after WGLC it won't take a lot of =
research, and a good memory, to fill in everything.
>=20
> 	Thanks,
> 	Paul
>=20
> On 4/22/13 3:08 AM, Benoit Claise wrote:
>> IETF WG chairs,
>>=20
>> We sent a similar message to the operations an management area =
chairs.
>> Therefore if you have seen the contents before, apologies, the =
resulting
>> IESG discussion has indicated that we should distribute it more =
widely.
>>=20
>> During the last IETF meeting, the community discussed a lot about the
>> transport AD situation. One aspect of this is the time commitment for =
an
>> AD position!
>>=20
>> During the last IETF meeting, the community discussed a lot about
>> diversity. All sort of diversities, including the IESG diversity. One
>> specific aspect is the diversity of IESG member affiliations.
>>=20
>> Let me share my experience after one year of service as AD.
>> 1. Yes, I like this job. I believe it makes a positive a difference =
for
>> the Internet (hopefully positive, you'll be the judges, but that's =
not
>> the point of this email )
>> 2. Yes, this AD role requires (more than) a full time job if done
>> conscientiously.
>> 3. I'm concerned that we slowly created a set of requirements for an
>> IESG position that will make difficult to find ADs in the future ...
>> except from big companies, or when dedicated funding is allocated. =
Not
>> good for diversity.
>> 4. Believe it or not, one substantial part of my OPS activities is =
the
>> follow up on the open issues. Recently, for a single draft, I spent
>> hoouuurrrssss trying to track all the open issues from the =
directorates
>> and the IESG, and chasing the authors. On top of taking some time, I =
had
>> to be become expert for every single aspect of the specifications to
>> evaluate whether the answer was right. After all, I have to defend =
your
>> WG document during the IESG call.
>>=20
>> Considering the discussion above, let me focus on one important role
>> within the community: the document shepherd.  This job, when done
>> according to RFC 4858 would free up a huge amount of time for the =
ADs,
>> and would speed up the document publication.
>>=20
>> Please read RFC 4858, specifically
>>      3.2.  Document Shepherding during AD Evaluation  . . . . . . . . =
 9
>>      3.3.  Document Shepherding during IESG Evaluation  . . . . . . . =
10
>>=20
>> Bottom line, the document shepherd job doesn't stop when the write-up =
is
>> sent.
>> I would like the document shepherds to follow the RFC 4858 =
instructions.
>> Specifically concerning the follow up part.
>> That being said, the shepherd, chairs, and the WG participants =
together
>> are the custodians of WG output. So the obligations isn't solely
>> invested in the shepherds. Their role via the questionnaire
>> fundamentally is to document that the things required have been done,
>> and to manage the remainder of the process.
>>=20
>> To come back to the first paragraph of my email, the document =
shepherd
>> job (let me stress again, when done according to the function =
described
>> in RFC 4858) would be beneficial for the entire community longer =
term.
>> Let me explain: if the AD job was not a full time job, it might be
>> easier to have diversity in the pool of AD candidates.
>>=20
>> This message was sent to all OPS WG chairs, and is now being =
distributed
>> more widely.
>>=20
>> Also, let's keep in mind that it's not a requirement that only WG =
chairs
>> are document shepherds. See
>> http://www.ietf.org/iesg/statement/document-shepherds.html,The =
Shepherds
>> role is a source of valuable insight into the later stages of the RFC
>> process and a stepping stone for competency in other IETF roles.
>>=20
>> Regards, Benoit
>>=20
>>=20
>>=20
>>=20
>=20


From barryleiba.mailing.lists@gmail.com  Mon Apr 22 15:00:33 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBDA721E809C for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.752
X-Spam-Level: 
X-Spam-Status: No, score=-101.752 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+eXQE8-zWlK for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:00:33 -0700 (PDT)
Received: from mail-vb0-x22c.google.com (mail-vb0-x22c.google.com [IPv6:2607:f8b0:400c:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2E18221E80B3 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:00:32 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id e12so6362383vbg.17 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wRqmAX6Ofeu8UXBQ3sJB0Q7Iy3IHKjxTbvYCKBR9b5I=; b=F85gghNGpaZrSkK3trA8LEIR+foBkSDU4ykEYsYQFoxJvusLCXziT07XphIK8hSkqv 0u53wBK+JnuPp3gV9elf8DqPe4uZ0/Aj6Ox7JWZphroxniXAsdIe5CGMNrsvXDB5Ke0s QsvRNYNI9Tu7UycFit1Z+jWQwN6BPkjWw8aMl/orlYh+qdllZJ5dpm9CT9YDp4E5GmWv 4N7aKslYnTMNpk+o+j+HiwC1ocR9AsU0af/et4IS6u7nhijt7wUbk9NAErD/yn3DgGEZ lumIl8IF1D/gITls4Yb/R1Xk1uVa1Bp+XuEshV8dkWWffGkk9Gt5O9jj1cyRqH3z+BuY EqVQ==
MIME-Version: 1.0
X-Received: by 10.52.96.138 with SMTP id ds10mr17423591vdb.3.1366668031526; Mon, 22 Apr 2013 15:00:31 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 22 Apr 2013 15:00:31 -0700 (PDT)
In-Reply-To: <5175AF99.4020408@alum.mit.edu>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu>
Date: Mon, 22 Apr 2013 18:00:31 -0400
X-Google-Sender-Auth: 1_NPYiU0uHAc2W_wXm-rbcZHXz0
Message-ID: <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
Subject: Re: Document shepherd role
From: Barry Leiba <barryleiba@computer.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=20cf307f3a368b8ef604dafa327a
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 22:00:34 -0000

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

Gee, Paul, you've provided the perfect intro.   Please check out my
document, which I'm trying to figure out what to do with:
https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/

Barry

On Monday, April 22, 2013, Paul Kyzivat wrote:

> I found this discussion enlightening.
>
> I'd like to add a slightly different, but related, suggestion:
>
> Several times now when I have shepherded a draft, I start doing the
> writeup and realize it would have been really helpful to started on that
> writeup sooner - even before the document was ready for progression. My
> conclusion is that it would probably be good to assign a shepherd to a
> document as soon as it is adopted as a wg draft. (Assuming there is an
> intent that it become an RFC.) And then the shepherd can *start* filling
> out the template early. That way, after WGLC it won't take a lot of
> research, and a good memory, to fill in everything.
>
>         Thanks,
>         Paul
>
> On 4/22/13 3:08 AM, Benoit Claise wrote:
>
>> IETF WG chairs,
>>
>> We sent a similar message to the operations an management area chairs.
>> Therefore if you have seen the contents before, apologies, the resulting
>> IESG discussion has indicated that we should distribute it more widely.
>>
>> During the last IETF meeting, the community discussed a lot about the
>> transport AD situation. One aspect of this is the time commitment for an
>> AD position!
>>
>> During the last IETF meeting, the community discussed a lot about
>> diversity. All sort of diversities, including the IESG diversity. One
>> specific aspect is the diversity of IESG member affiliations.
>>
>> Let me share my experience after one year of service as AD.
>> 1. Yes, I like this job. I believe it makes a positive a difference for
>> the Internet (hopefully positive, you'll be the judges, but that's not
>> the point of this email )
>> 2. Yes, this AD role requires (more than) a full time job if done
>> conscientiously.
>> 3. I'm concerned that we slowly created a set of requirements for an
>> IESG position that will make difficult to find ADs in the future ...
>> except from big companies, or when dedicated funding is allocated. Not
>> good for diversity.
>> 4. Believe it or not, one substantial part of my OPS activities is the
>> follow up on the open issues. Recently, for a single draft, I spent
>> hoouuurrrssss trying to track all the open issues from the directorates
>> and the IESG, and chasing the authors. On top of taking some time, I had
>> to be become expert for every single aspect of the specifications to
>> evaluate whether the answer was right. After all, I have to defend your
>> WG document during the IESG call.
>>
>> Considering the discussion above, let me focus on one important role
>> within the community: the document shepherd.  This job, when done
>> according to RFC 4858 would free up a huge amount of time for the ADs,
>> and would speed up the document publication.
>>
>> Please read RFC 4858, specifically
>>       3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
>>       3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10
>>
>> Bottom line, the document shepherd job doesn't stop when the write-up is
>> sent.
>> I would like the document shepherds to follow the RFC 4858 instructions.
>> Specifically concerning the follow up part.
>> That being said, the shepherd, chairs, and the WG participants together
>> are the custodians of WG output. So the obligations isn't solely
>> invested in the shepherds. Their role via the questionnaire
>> fundamentally is to document that the things required have been done,
>> and to manage the remainder of the process.
>>
>> To come back to the first paragraph of my email, the document shepherd
>> job (let me stress again, when done according to the function described
>> in RFC 4858) would be beneficial for the entire community longer term.
>> Let me explain: if the AD job was not a full time job, it might be
>> easier to have diversity in the pool of AD candidates.
>>
>> This message was sent to all OPS WG chairs, and is now being distributed
>> more widely.
>>
>> Also, let's keep in mind that it's not a requirement that only WG chairs
>> are document shepherds. See
>> http://www.ietf.org/iesg/**statement/document-shepherds.**html,The<http://www.ietf.org/iesg/statement/document-shepherds.html,The>Shepherds
>> role is a source of valuable insight into the later stages of the RFC
>> process and a stepping stone for competency in other IETF roles.
>>
>> Regards, Benoit
>>
>>
>>
>>
>>
>

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

Gee, Paul, you&#39;ve provided the perfect intro. =A0 Please check out my d=
ocument, which I&#39;m trying to figure out what to do with:<div><a href=3D=
"https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/">https=
://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/</a></div>
<div><br></div><div>Barry<span></span><br><br>On Monday, April 22, 2013, Pa=
ul Kyzivat  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I found this discussio=
n enlightening.<br>

<br>
I&#39;d like to add a slightly different, but related, suggestion:<br>
<br>
Several times now when I have shepherded a draft, I start doing the writeup=
 and realize it would have been really helpful to started on that writeup s=
ooner - even before the document was ready for progression. My conclusion i=
s that it would probably be good to assign a shepherd to a document as soon=
 as it is adopted as a wg draft. (Assuming there is an intent that it becom=
e an RFC.) And then the shepherd can *start* filling out the template early=
. That way, after WGLC it won&#39;t take a lot of research, and a good memo=
ry, to fill in everything.<br>

<br>
=A0 =A0 =A0 =A0 Thanks,<br>
=A0 =A0 =A0 =A0 Paul<br>
<br>
On 4/22/13 3:08 AM, Benoit Claise wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
IETF WG chairs,<br>
<br>
We sent a similar message to the operations an management area chairs.<br>
Therefore if you have seen the contents before, apologies, the resulting<br=
>
IESG discussion has indicated that we should distribute it more widely.<br>
<br>
During the last IETF meeting, the community discussed a lot about the<br>
transport AD situation. One aspect of this is the time commitment for an<br=
>
AD position!<br>
<br>
During the last IETF meeting, the community discussed a lot about<br>
diversity. All sort of diversities, including the IESG diversity. One<br>
specific aspect is the diversity of IESG member affiliations.<br>
<br>
Let me share my experience after one year of service as AD.<br>
1. Yes, I like this job. I believe it makes a positive a difference for<br>
the Internet (hopefully positive, you&#39;ll be the judges, but that&#39;s =
not<br>
the point of this email )<br>
2. Yes, this AD role requires (more than) a full time job if done<br>
conscientiously.<br>
3. I&#39;m concerned that we slowly created a set of requirements for an<br=
>
IESG position that will make difficult to find ADs in the future ...<br>
except from big companies, or when dedicated funding is allocated. Not<br>
good for diversity.<br>
4. Believe it or not, one substantial part of my OPS activities is the<br>
follow up on the open issues. Recently, for a single draft, I spent<br>
hoouuurrrssss trying to track all the open issues from the directorates<br>
and the IESG, and chasing the authors. On top of taking some time, I had<br=
>
to be become expert for every single aspect of the specifications to<br>
evaluate whether the answer was right. After all, I have to defend your<br>
WG document during the IESG call.<br>
<br>
Considering the discussion above, let me focus on one important role<br>
within the community: the document shepherd. =A0This job, when done<br>
according to RFC 4858 would free up a huge amount of time for the ADs,<br>
and would speed up the document publication.<br>
<br>
Please read RFC 4858, specifically<br>
=A0 =A0 =A0 3.2. =A0Document Shepherding during AD Evaluation =A0. . . . . =
. . . =A09<br>
=A0 =A0 =A0 3.3. =A0Document Shepherding during IESG Evaluation =A0. . . . =
. . . 10<br>
<br>
Bottom line, the document shepherd job doesn&#39;t stop when the write-up i=
s<br>
sent.<br>
I would like the document shepherds to follow the RFC 4858 instructions.<br=
>
Specifically concerning the follow up part.<br>
That being said, the shepherd, chairs, and the WG participants together<br>
are the custodians of WG output. So the obligations isn&#39;t solely<br>
invested in the shepherds. Their role via the questionnaire<br>
fundamentally is to document that the things required have been done,<br>
and to manage the remainder of the process.<br>
<br>
To come back to the first paragraph of my email, the document shepherd<br>
job (let me stress again, when done according to the function described<br>
in RFC 4858) would be beneficial for the entire community longer term.<br>
Let me explain: if the AD job was not a full time job, it might be<br>
easier to have diversity in the pool of AD candidates.<br>
<br>
This message was sent to all OPS WG chairs, and is now being distributed<br=
>
more widely.<br>
<br>
Also, let&#39;s keep in mind that it&#39;s not a requirement that only WG c=
hairs<br>
are document shepherds. See<br>
<a href=3D"http://www.ietf.org/iesg/statement/document-shepherds.html,The" =
target=3D"_blank">http://www.ietf.org/iesg/<u></u>statement/document-shephe=
rds.<u></u>html,The</a> Shepherds<br>
role is a source of valuable insight into the later stages of the RFC<br>
process and a stepping stone for competency in other IETF roles.<br>
<br>
Regards, Benoit<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote></div>

--20cf307f3a368b8ef604dafa327a--

From pkyzivat@alum.mit.edu  Mon Apr 22 15:05:03 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B31B71F0D09 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SklSi9nHpuq8 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:05:03 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 4C87A1F0D1F for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:05:01 -0700 (PDT)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta04.westchester.pa.mail.comcast.net with comcast id T7ep1l0020ldTLk54A4qMj; Mon, 22 Apr 2013 22:04:50 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta04.westchester.pa.mail.comcast.net with comcast id TA4p1l00d3ZTu2S3QA4pTJ; Mon, 22 Apr 2013 22:04:50 +0000
Message-ID: <5175B401.6070303@alum.mit.edu>
Date: Mon, 22 Apr 2013 18:04:49 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <A159B9B4-DBE3-4CD8-8E28-23D88D9B5168@lilacglade.org>
In-Reply-To: <A159B9B4-DBE3-4CD8-8E28-23D88D9B5168@lilacglade.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366668290; bh=Ohv01CQoPfGbFOEW4wL3uIjuuZ5RnnkB3w0ePP5opSg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=VqAFRZMb92SZ4nAO8WD3nct76MU4BK1U1ozRuv8wEPkanYlWE6cYdhLYCnvhnMGND R4VgQkhD5q3Af8jpJslbBnaPBM+MxSy/vMqCJ5OwE0fGKFiSGIQ0dZ7zG/znfvgpjr D2KYk4RO0tQ603CWh8J6PGn1s2/Cy9R4VFBLVdaGn6CVsZ9qk3v+dy3IKBmOiG/Lhb 9bXJOoSFJ/xA1QzgjYCrZaQaHGdx2JYmYWdtMyiL54MC8kKUoLGw1KtEZ+fqBmlhwb GqCkwH+PPq1ORhtiuKuweruieuwHO4JM1EVMGIS2fCbdp0bPgejmBZ2GXcwErXd9ej rjUCQMT2LRlkw==
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 22:05:03 -0000

On 4/22/13 5:54 PM, Margaret Wasserman wrote:
>
> In busy working groups, ones with a lot of documents, it isn't unusual for the chairs to divide up responsibility for the active WG drafts.  When those drafts go into the IESG, the WG chair who has been responsible for the document during the WG process usually shepherds the draft through the IESG.  That works pretty well, in my experience.
>
> In less busy groups, ones with fewer drafts, the chairs may work together on all of the documents.  They then have to assign a shepherd at the end.  Depending on the roles of the individual chairs, this can work well, but sometimes the chair needs to fill in a lot of knowledge to do the shepherding task.  In these cases, I agree it might make sense to explicitly decide who will shepherd the draft earlier in the process.

In the groups I chair we haven't overtly considered who will shepherd a 
document until after WGLC. Maybe this isn't a problem for other groups. 
But for mine I'm just discovering that starting this earlier would be 
helpful.

	Thanks,
	Paul

> Margaret
>
> On Apr 22, 2013, at 5:46 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> I found this discussion enlightening.
>>
>> I'd like to add a slightly different, but related, suggestion:
>>
>> Several times now when I have shepherded a draft, I start doing the writeup and realize it would have been really helpful to started on that writeup sooner - even before the document was ready for progression. My conclusion is that it would probably be good to assign a shepherd to a document as soon as it is adopted as a wg draft. (Assuming there is an intent that it become an RFC.) And then the shepherd can *start* filling out the template early. That way, after WGLC it won't take a lot of research, and a good memory, to fill in everything.
>>
>> 	Thanks,
>> 	Paul
>>
>> On 4/22/13 3:08 AM, Benoit Claise wrote:
>>> IETF WG chairs,
>>>
>>> We sent a similar message to the operations an management area chairs.
>>> Therefore if you have seen the contents before, apologies, the resulting
>>> IESG discussion has indicated that we should distribute it more widely.
>>>
>>> During the last IETF meeting, the community discussed a lot about the
>>> transport AD situation. One aspect of this is the time commitment for an
>>> AD position!
>>>
>>> During the last IETF meeting, the community discussed a lot about
>>> diversity. All sort of diversities, including the IESG diversity. One
>>> specific aspect is the diversity of IESG member affiliations.
>>>
>>> Let me share my experience after one year of service as AD.
>>> 1. Yes, I like this job. I believe it makes a positive a difference for
>>> the Internet (hopefully positive, you'll be the judges, but that's not
>>> the point of this email )
>>> 2. Yes, this AD role requires (more than) a full time job if done
>>> conscientiously.
>>> 3. I'm concerned that we slowly created a set of requirements for an
>>> IESG position that will make difficult to find ADs in the future ...
>>> except from big companies, or when dedicated funding is allocated. Not
>>> good for diversity.
>>> 4. Believe it or not, one substantial part of my OPS activities is the
>>> follow up on the open issues. Recently, for a single draft, I spent
>>> hoouuurrrssss trying to track all the open issues from the directorates
>>> and the IESG, and chasing the authors. On top of taking some time, I had
>>> to be become expert for every single aspect of the specifications to
>>> evaluate whether the answer was right. After all, I have to defend your
>>> WG document during the IESG call.
>>>
>>> Considering the discussion above, let me focus on one important role
>>> within the community: the document shepherd.  This job, when done
>>> according to RFC 4858 would free up a huge amount of time for the ADs,
>>> and would speed up the document publication.
>>>
>>> Please read RFC 4858, specifically
>>>       3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
>>>       3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10
>>>
>>> Bottom line, the document shepherd job doesn't stop when the write-up is
>>> sent.
>>> I would like the document shepherds to follow the RFC 4858 instructions.
>>> Specifically concerning the follow up part.
>>> That being said, the shepherd, chairs, and the WG participants together
>>> are the custodians of WG output. So the obligations isn't solely
>>> invested in the shepherds. Their role via the questionnaire
>>> fundamentally is to document that the things required have been done,
>>> and to manage the remainder of the process.
>>>
>>> To come back to the first paragraph of my email, the document shepherd
>>> job (let me stress again, when done according to the function described
>>> in RFC 4858) would be beneficial for the entire community longer term.
>>> Let me explain: if the AD job was not a full time job, it might be
>>> easier to have diversity in the pool of AD candidates.
>>>
>>> This message was sent to all OPS WG chairs, and is now being distributed
>>> more widely.
>>>
>>> Also, let's keep in mind that it's not a requirement that only WG chairs
>>> are document shepherds. See
>>> http://www.ietf.org/iesg/statement/document-shepherds.html,The Shepherds
>>> role is a source of valuable insight into the later stages of the RFC
>>> process and a stepping stone for competency in other IETF roles.
>>>
>>> Regards, Benoit
>>>
>>>
>>>
>>>
>>
>
>


From pkyzivat@alum.mit.edu  Mon Apr 22 15:26:15 2013
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3959F21E80A3 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7LHXStWn+Xi for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:26:11 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id E579D21E80AB for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:25:47 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta02.westchester.pa.mail.comcast.net with comcast id Sz7C1l0020Fqzac51ARj6o; Mon, 22 Apr 2013 22:25:43 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id TARi1l00T3ZTu2S3UARjvg; Mon, 22 Apr 2013 22:25:43 +0000
Message-ID: <5175B89A.1090001@alum.mit.edu>
Date: Mon, 22 Apr 2013 18:24:26 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
In-Reply-To: <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366669543; bh=ivChODFv7kJOr9jwHJveSVNbCmvWroOGZyHGKCqN2d4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=C8XH8FYI6pab8CmCsm9Bp5LwEThd+SQtotbqhCTqvnvqcmh+qWOmBrazQmPgJoztp E92KGgMB8fOawOZnch/2UBoA30xSVkNZE126gkAmatEFb8Jh4d1hbHITLpXFB0zofU xCtZ0KiFDS9TyJGMIbsaZz+Iqan372pWqx4F2lGA8pI2gj077xMlxIX3jNm+ydf7hC LSPhd3gDUcoc1K5lJHg8Q4wyIchWnx2C2+exPrikjxsXVYSQcb82dcajMOl0WRZSwK pMPUE5gYDkaocgXIedgN6wvmGySMV+sSMxV/E83cH5UAIww3ovMQnQwN17Xz5uUyYO oA4+41BehQnVA==
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 22:26:15 -0000

On 4/22/13 6:00 PM, Barry Leiba wrote:
> Gee, Paul, you've provided the perfect intro.   Please check out my
> document, which I'm trying to figure out what to do with:
> https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/

Perfect!

But I do think the writeup can usefully be started before WGLC.
It will then provide a place to keep useful information. For instance, 
if there is a lot of debate and controversy about some points, then info 
about that can be captured in the draft writeup while the memory of that 
is fresh. (Better than reading through months or years of email later to 
remember the details of that controversy.)

	Thanks,
	Paul

> Barry
>
> On Monday, April 22, 2013, Paul Kyzivat wrote:
>
>     I found this discussion enlightening.
>
>     I'd like to add a slightly different, but related, suggestion:
>
>     Several times now when I have shepherded a draft, I start doing the
>     writeup and realize it would have been really helpful to started on
>     that writeup sooner - even before the document was ready for
>     progression. My conclusion is that it would probably be good to
>     assign a shepherd to a document as soon as it is adopted as a wg
>     draft. (Assuming there is an intent that it become an RFC.) And then
>     the shepherd can *start* filling out the template early. That way,
>     after WGLC it won't take a lot of research, and a good memory, to
>     fill in everything.
>
>              Thanks,
>              Paul
>
>     On 4/22/13 3:08 AM, Benoit Claise wrote:
>
>         IETF WG chairs,
>
>         We sent a similar message to the operations an management area
>         chairs.
>         Therefore if you have seen the contents before, apologies, the
>         resulting
>         IESG discussion has indicated that we should distribute it more
>         widely.
>
>         During the last IETF meeting, the community discussed a lot
>         about the
>         transport AD situation. One aspect of this is the time
>         commitment for an
>         AD position!
>
>         During the last IETF meeting, the community discussed a lot about
>         diversity. All sort of diversities, including the IESG
>         diversity. One
>         specific aspect is the diversity of IESG member affiliations.
>
>         Let me share my experience after one year of service as AD.
>         1. Yes, I like this job. I believe it makes a positive a
>         difference for
>         the Internet (hopefully positive, you'll be the judges, but
>         that's not
>         the point of this email )
>         2. Yes, this AD role requires (more than) a full time job if done
>         conscientiously.
>         3. I'm concerned that we slowly created a set of requirements for an
>         IESG position that will make difficult to find ADs in the future ...
>         except from big companies, or when dedicated funding is
>         allocated. Not
>         good for diversity.
>         4. Believe it or not, one substantial part of my OPS activities
>         is the
>         follow up on the open issues. Recently, for a single draft, I spent
>         hoouuurrrssss trying to track all the open issues from the
>         directorates
>         and the IESG, and chasing the authors. On top of taking some
>         time, I had
>         to be become expert for every single aspect of the specifications to
>         evaluate whether the answer was right. After all, I have to
>         defend your
>         WG document during the IESG call.
>
>         Considering the discussion above, let me focus on one important role
>         within the community: the document shepherd.  This job, when done
>         according to RFC 4858 would free up a huge amount of time for
>         the ADs,
>         and would speed up the document publication.
>
>         Please read RFC 4858, specifically
>                3.2.  Document Shepherding during AD Evaluation  . . . .
>         . . . .  9
>                3.3.  Document Shepherding during IESG Evaluation  . . .
>         . . . . 10
>
>         Bottom line, the document shepherd job doesn't stop when the
>         write-up is
>         sent.
>         I would like the document shepherds to follow the RFC 4858
>         instructions.
>         Specifically concerning the follow up part.
>         That being said, the shepherd, chairs, and the WG participants
>         together
>         are the custodians of WG output. So the obligations isn't solely
>         invested in the shepherds. Their role via the questionnaire
>         fundamentally is to document that the things required have been
>         done,
>         and to manage the remainder of the process.
>
>         To come back to the first paragraph of my email, the document
>         shepherd
>         job (let me stress again, when done according to the function
>         described
>         in RFC 4858) would be beneficial for the entire community longer
>         term.
>         Let me explain: if the AD job was not a full time job, it might be
>         easier to have diversity in the pool of AD candidates.
>
>         This message was sent to all OPS WG chairs, and is now being
>         distributed
>         more widely.
>
>         Also, let's keep in mind that it's not a requirement that only
>         WG chairs
>         are document shepherds. See
>         http://www.ietf.org/iesg/__statement/document-shepherds.__html,The
>         <http://www.ietf.org/iesg/statement/document-shepherds.html,The>
>         Shepherds
>         role is a source of valuable insight into the later stages of
>         the RFC
>         process and a stepping stone for competency in other IETF roles.
>
>         Regards, Benoit
>
>
>
>
>


From volz@cisco.com  Mon Apr 22 15:31:31 2013
Return-Path: <volz@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E45A21E803D for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yU6PGltMPqLO for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 15:31:27 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C41011F0D1B for <wgchairs@ietf.org>; Mon, 22 Apr 2013 15:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6457; q=dns/txt; s=iport; t=1366669886; x=1367879486; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=lWFI589uljhPm5oEVX6Mb01K1XuaYubon8k5YP/5mT0=; b=RYVUUWWNS4tdG1b7e9AY9O08PepHcTmJvRh5tVtot9oHy6hGURAuaVCX 6IrmRvq34PPc3USQZVhB1Nur1wTZOZVI4zZS1TkThIu5mremIUS2NkpaM HxDWWYvYLUC2EMktNvLpZdOiEnhy0x+n8B3OJ0Vw5I8BuP/bhYJ5az/4h I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAMy5dVGtJXG+/2dsb2JhbABPDoJ4NsEQgQYWdIIfAQEBAwE6MQkFBQcEAgEIDgMEAQEBChQJBzIUCQgCBAENBQgBC4d6Bgy7Yo19gREmCwcGXYIDYQOoL4JNMg2BczU
X-IronPort-AV: E=Sophos;i="4.87,529,1363132800"; d="scan'208";a="201718853"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-7.cisco.com with ESMTP; 22 Apr 2013 22:31:03 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3MMV2EX006805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Apr 2013 22:31:02 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Mon, 22 Apr 2013 17:31:02 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Barry Leiba <barryleiba@computer.org>
Subject: RE: Document shepherd role
Thread-Topic: Document shepherd role
Thread-Index: AQHOP2BzmtMvBbIru0SPTOkQuU2Ff5jjGqCAgAAEDYCAAAavAP//rXdw
Date: Mon, 22 Apr 2013 22:31:01 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E18513A8F@xmb-rcd-x04.cisco.com>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com> <5175B89A.1090001@alum.mit.edu>
In-Reply-To: <5175B89A.1090001@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.245.110]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 22:31:31 -0000

I think before the WGLC is started or during the WGLC process, the shepherd=
 (or WG chair) should really review the document as if doing the shepherd w=
rite -up (it makes the final write-up easy). I've used the process recently=
 when doing WGLCs for DHC WG documents.

- Bernie

-----Original Message-----
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Paul Kyzivat
Sent: Monday, April 22, 2013 6:24 PM
To: Barry Leiba
Cc: wgchairs@ietf.org
Subject: Re: Document shepherd role

On 4/22/13 6:00 PM, Barry Leiba wrote:
> Gee, Paul, you've provided the perfect intro.   Please check out my
> document, which I'm trying to figure out what to do with:
> https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/

Perfect!

But I do think the writeup can usefully be started before WGLC.
It will then provide a place to keep useful information. For instance, if t=
here is a lot of debate and controversy about some points, then info about =
that can be captured in the draft writeup while the memory of that is fresh=
. (Better than reading through months or years of email later to remember t=
he details of that controversy.)

	Thanks,
	Paul

> Barry
>
> On Monday, April 22, 2013, Paul Kyzivat wrote:
>
>     I found this discussion enlightening.
>
>     I'd like to add a slightly different, but related, suggestion:
>
>     Several times now when I have shepherded a draft, I start doing the
>     writeup and realize it would have been really helpful to started on
>     that writeup sooner - even before the document was ready for
>     progression. My conclusion is that it would probably be good to
>     assign a shepherd to a document as soon as it is adopted as a wg
>     draft. (Assuming there is an intent that it become an RFC.) And then
>     the shepherd can *start* filling out the template early. That way,
>     after WGLC it won't take a lot of research, and a good memory, to
>     fill in everything.
>
>              Thanks,
>              Paul
>
>     On 4/22/13 3:08 AM, Benoit Claise wrote:
>
>         IETF WG chairs,
>
>         We sent a similar message to the operations an management area
>         chairs.
>         Therefore if you have seen the contents before, apologies, the
>         resulting
>         IESG discussion has indicated that we should distribute it more
>         widely.
>
>         During the last IETF meeting, the community discussed a lot
>         about the
>         transport AD situation. One aspect of this is the time
>         commitment for an
>         AD position!
>
>         During the last IETF meeting, the community discussed a lot about
>         diversity. All sort of diversities, including the IESG
>         diversity. One
>         specific aspect is the diversity of IESG member affiliations.
>
>         Let me share my experience after one year of service as AD.
>         1. Yes, I like this job. I believe it makes a positive a
>         difference for
>         the Internet (hopefully positive, you'll be the judges, but
>         that's not
>         the point of this email )
>         2. Yes, this AD role requires (more than) a full time job if done
>         conscientiously.
>         3. I'm concerned that we slowly created a set of requirements for=
 an
>         IESG position that will make difficult to find ADs in the future =
...
>         except from big companies, or when dedicated funding is
>         allocated. Not
>         good for diversity.
>         4. Believe it or not, one substantial part of my OPS activities
>         is the
>         follow up on the open issues. Recently, for a single draft, I spe=
nt
>         hoouuurrrssss trying to track all the open issues from the
>         directorates
>         and the IESG, and chasing the authors. On top of taking some
>         time, I had
>         to be become expert for every single aspect of the specifications=
 to
>         evaluate whether the answer was right. After all, I have to
>         defend your
>         WG document during the IESG call.
>
>         Considering the discussion above, let me focus on one important r=
ole
>         within the community: the document shepherd.  This job, when done
>         according to RFC 4858 would free up a huge amount of time for
>         the ADs,
>         and would speed up the document publication.
>
>         Please read RFC 4858, specifically
>                3.2.  Document Shepherding during AD Evaluation  . . . .
>         . . . .  9
>                3.3.  Document Shepherding during IESG Evaluation  . . .
>         . . . . 10
>
>         Bottom line, the document shepherd job doesn't stop when the
>         write-up is
>         sent.
>         I would like the document shepherds to follow the RFC 4858
>         instructions.
>         Specifically concerning the follow up part.
>         That being said, the shepherd, chairs, and the WG participants
>         together
>         are the custodians of WG output. So the obligations isn't solely
>         invested in the shepherds. Their role via the questionnaire
>         fundamentally is to document that the things required have been
>         done,
>         and to manage the remainder of the process.
>
>         To come back to the first paragraph of my email, the document
>         shepherd
>         job (let me stress again, when done according to the function
>         described
>         in RFC 4858) would be beneficial for the entire community longer
>         term.
>         Let me explain: if the AD job was not a full time job, it might b=
e
>         easier to have diversity in the pool of AD candidates.
>
>         This message was sent to all OPS WG chairs, and is now being
>         distributed
>         more widely.
>
>         Also, let's keep in mind that it's not a requirement that only
>         WG chairs
>         are document shepherds. See
>         http://www.ietf.org/iesg/__statement/document-shepherds.__html,Th=
e
>         <http://www.ietf.org/iesg/statement/document-shepherds.html,The>
>         Shepherds
>         role is a source of valuable insight into the later stages of
>         the RFC
>         process and a stepping stone for competency in other IETF roles.
>
>         Regards, Benoit
>
>
>
>
>


From barryleiba.mailing.lists@gmail.com  Mon Apr 22 16:11:30 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C999211E80D9 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 16:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.797
X-Spam-Level: 
X-Spam-Status: No, score=-101.797 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgCoK0neTsCA for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 16:11:30 -0700 (PDT)
Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 37F6D11E80BA for <wgchairs@ietf.org>; Mon, 22 Apr 2013 16:11:30 -0700 (PDT)
Received: by mail-vb0-f43.google.com with SMTP id q12so11146vbe.30 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 16:11:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xjp3ll87tlEGbs3Ao/+Wp/61LhO6v2/H2iMfKPFspLc=; b=jL847P/raX87m/4bHYvXsmU5x5+OylOtGAQymURKOvr8VQgVF6wcb05U0Hpsx95Bxz 0/Gat30VitF5wrvEJPlXdTZQyiIbBeU+lTj/RdUWq1dOCQlNS0DnaAXE3xEtftSMxDoR c4w5FRZPrMJKiLczckMsGpgyLL/l0wp002JEpfVx6unQwjlXxNTHkeE+hS1DRWZp0GNN s6C9cxwc8/1WqwZFdTqSuBPbTHewJalif5o04Mt3gnov0F+wKg+46wO20HRM430CTTwV fvG4sSHvuD/FM5+SmEra7UEQosmWw41MdMNINfpjeu0N9uR6TQVVJb25ZpSdsGL//fL5 X4Xg==
MIME-Version: 1.0
X-Received: by 10.52.89.229 with SMTP id br5mr17380125vdb.24.1366672289670; Mon, 22 Apr 2013 16:11:29 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 22 Apr 2013 16:11:29 -0700 (PDT)
In-Reply-To: <5175B89A.1090001@alum.mit.edu>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com> <5175B89A.1090001@alum.mit.edu>
Date: Mon, 22 Apr 2013 19:11:29 -0400
X-Google-Sender-Auth: DGZvWp1PcZsYLx6gLdgCkhte8cQ
Message-ID: <CAC4RtVBhzSCpaZH5QBLXz0TOCRpH5KL-7HdXP-JMKLwWM7i1Kw@mail.gmail.com>
Subject: Re: Document shepherd role
From: Barry Leiba <barryleiba@computer.org>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=20cf307f376259e04904dafb3083
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 23:11:30 -0000

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

> But I do think the writeup can usefully be started before WGLC.
> It will then provide a place to keep useful information. For instance,
> if there is a lot of debate and controversy about some points, then info
> about that can be captured in the draft writeup while the memory of that
is
> fresh. (Better than reading through months or years of email later to
> remember the details of that controversy.)

Yes, this is excellent input (and almost verbatim text) for the next
version of the draft.  Thanks.

Barry

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

<font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0=
)">&gt;=A0But I do think the writeup can usefully be started before WGLC.<b=
r>&gt;=A0It will then provide a place to keep useful=A0information. For ins=
tance,</span></font><div>
<font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0=
)">&gt; if there is a lot of debate and controversy about some points, then=
 info</span></font></div><div><font><span style=3D"line-height:normal;backg=
round-color:rgba(255,255,255,0)">&gt;=A0about that can be captured in the d=
raft writeup while the memory of that is</span></font></div>
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)">&gt;=A0fresh. (Better than reading through months or years of email=
 later to</span></font></div><div><font><span style=3D"line-height:normal;b=
ackground-color:rgba(255,255,255,0)">&gt;=A0remember the details of that co=
ntroversy.)</span></font></div>
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)"><br></span></font></div><div><font><span style=3D"line-height:norma=
l;background-color:rgba(255,255,255,0)">Yes, this is excellent input (and a=
lmost verbatim text) for the next version of the draft. =A0Thanks.</span></=
font></div>
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)"><br></span></font></div><div><font><span style=3D"line-height:norma=
l;background-color:rgba(255,255,255,0)">Barry<span></span></span></font></d=
iv>
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)"><br></span></font></div>

--20cf307f376259e04904dafb3083--

From adrian@olddog.co.uk  Mon Apr 22 16:17:55 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6981F0D1C for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 16:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level: 
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyuRVn3mO0YA for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 16:17:54 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id E2DA51F0D1B for <wgchairs@ietf.org>; Mon, 22 Apr 2013 16:17:53 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3MNHiHl004070;  Tue, 23 Apr 2013 00:17:44 +0100
Received: from 950129200 ([66.129.246.4]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3MNHeTH004049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Apr 2013 00:17:41 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com>	<5175AF99.4020408@alum.mit.edu>	<CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>	<5175B89A.1090001@alum.mit.edu> <CAC4RtVBhzSCpaZH5QBLXz0TOCRpH5KL-7HdXP-JMKLwWM7i1Kw@mail.gmail.com>
In-Reply-To: <CAC4RtVBhzSCpaZH5QBLXz0TOCRpH5KL-7HdXP-JMKLwWM7i1Kw@mail.gmail.com>
Subject: RE: Document shepherd role
Date: Tue, 23 Apr 2013 00:17:37 +0100
Message-ID: <011901ce3faf$95e9d780$c1bd8680$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011A_01CE3FB7.F7B06260"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKqLwNywuro73hxer1YbRJ6ujR08gHLFb6OAVUEpDQCRWUNVwHk+iT5ArAhSO2W2ysXgA==
Content-Language: en-gb
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 23:17:55 -0000

This is a multipart message in MIME format.

------=_NextPart_000_011A_01CE3FB7.F7B06260
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

In fact, and agreeing that this is useful input, why not start the shepherding
*process* much sooner? That is: issue tracking; milestone chasing; making sure
comments are addressed/resolved; etc.
 
While most chairs might already do this on their own or in conjunction with the
document authors, this is function that could be delegated within the working
group.
 
A
 
From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behalf Of
Barry Leiba
Sent: 23 April 2013 00:11
To: Paul Kyzivat
Cc: wgchairs@ietf.org
Subject: Re: Document shepherd role
 
> But I do think the writeup can usefully be started before WGLC.
> It will then provide a place to keep useful information. For instance,
> if there is a lot of debate and controversy about some points, then info
> about that can be captured in the draft writeup while the memory of that is
> fresh. (Better than reading through months or years of email later to
> remember the details of that controversy.)
 
Yes, this is excellent input (and almost verbatim text) for the next version of
the draft.  Thanks.
 
Barry
 

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CE3FB7.F4293770"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>In fact, and agreeing that =
this is useful input, why not start the shepherding *process* much =
sooner? That is: issue tracking; milestone chasing; making sure comments =
are addressed/resolved; etc.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>While most chairs might =
already do this on their own or in conjunction with the document =
authors, this is function that could be delegated within the working =
group.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>A<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] <b>On =
Behalf Of </b>Barry Leiba<br><b>Sent:</b> 23 April 2013 =
00:11<br><b>To:</b> Paul Kyzivat<br><b>Cc:</b> =
wgchairs@ietf.org<br><b>Subject:</b> Re: Document shepherd =
role<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&gt;&nbsp;But I do think the writeup can usefully be =
started before WGLC.<br>&gt;&nbsp;It will then provide a place to keep =
useful&nbsp;information. For instance,<o:p></o:p></p><div><p =
class=3DMsoNormal>&gt; if there is a lot of debate and controversy about =
some points, then info<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&gt;&nbsp;about that can be captured in the draft =
writeup while the memory of that is<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&gt;&nbsp;fresh. (Better than reading through months =
or years of email later to<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&gt;&nbsp;remember the details of that =
controversy.)<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Yes, this is excellent input (and almost verbatim =
text) for the next version of the draft. =
&nbsp;Thanks.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Barry<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_011A_01CE3FB7.F7B06260--


From barryleiba.mailing.lists@gmail.com  Mon Apr 22 17:10:50 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C26521F9488 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 17:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.827
X-Spam-Level: 
X-Spam-Status: No, score=-101.827 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EH-Tv5vw2pa0 for <wgchairs@ietfa.amsl.com>; Mon, 22 Apr 2013 17:10:49 -0700 (PDT)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 25D8221F911E for <wgchairs@ietf.org>; Mon, 22 Apr 2013 17:10:38 -0700 (PDT)
Received: by mail-vb0-f50.google.com with SMTP id w16so45048vbb.23 for <wgchairs@ietf.org>; Mon, 22 Apr 2013 17:10:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=D78Q4uKUOduE78oLqxTfG5hKIBrdhhNrLXu+ix+0QK4=; b=ymkfZvvyyiXr0GLfcuZBzz4wT/iD+IJWzQ6RmF/TCO55zqVnZAuWw2SylGA6v0FN2+ soZCZ49fFskxcUo4ExtodCbruVkuqLRvPrNtDK9jzljk2d17j2Iwd/gZ1CawjoCRI+bx l8URPawusebjWRz/OPeK5vRJBSOmtkUOLkJUHNmwk+8sn0KW0ofyIaVvRDaUPcxdFYT5 c2viaYsjRPRY4hpNYDIxbXV2Hj9w3bUFmCFUH2/h0dm9AqTGZMBsAB8TmApEo3s/xhcc RbUWkiBQBSRT2K3zLl1j478pxSt0CL3dmeMQYoWKy77/PHEzJRPnUUGKFTKar+Pp/UZk zvKQ==
MIME-Version: 1.0
X-Received: by 10.59.3.9 with SMTP id bs9mr20862125ved.38.1366675837617; Mon, 22 Apr 2013 17:10:37 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 22 Apr 2013 17:10:37 -0700 (PDT)
In-Reply-To: <011901ce3faf$95e9d780$c1bd8680$@olddog.co.uk>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com> <5175B89A.1090001@alum.mit.edu> <CAC4RtVBhzSCpaZH5QBLXz0TOCRpH5KL-7HdXP-JMKLwWM7i1Kw@mail.gmail.com> <011901ce3faf$95e9d780$c1bd8680$@olddog.co.uk>
Date: Mon, 22 Apr 2013 20:10:37 -0400
X-Google-Sender-Auth: lnyKTLA0IsYmiykZRHT-OSzzdKI
Message-ID: <CAC4RtVBA4_3w3ft4ogT17RGLuafQ87n8eskPk-6tHPTfMj=cdw@mail.gmail.com>
Subject: Re: Document shepherd role
From: Barry Leiba <barryleiba@computer.org>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=e89a8f921936d314e704dafc037b
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 00:10:50 -0000

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

On Monday, April 22, 2013, Adrian Farrel wrote:

> In fact, and agreeing that this is useful input, why not start the
> shepherding *process* much sooner? That is: issue tracking; milestone
> chasing; making sure comments are addressed/resolved; etc.
>
>
...Which is, of course, what my draft is all about.

Barry

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

On Monday, April 22, 2013, Adrian Farrel  wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><p class=3D=
"MsoNormal">
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">In fact, and agreeing that this is useful input,=
 why not start the shepherding *process* much sooner? That is: issue tracki=
ng; milestone chasing; making sure comments are addressed/resolved; etc.</s=
pan></p>
<p class=3D"MsoNormal"></p></div></div></blockquote><div>=A0</div><div>...W=
hich is, of course, what my draft is all about.</div><div><br></div><div>Ba=
rry<span></span></div>

--e89a8f921936d314e704dafc037b--

From bclaise@cisco.com  Tue Apr 23 03:50:29 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B463621F9643 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 03:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.485
X-Spam-Level: 
X-Spam-Status: No, score=-10.485 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HG+1fNmcQbr4 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 03:50:29 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E887621F9627 for <wgchairs@ietf.org>; Tue, 23 Apr 2013 03:50:28 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3NAoMD6007201; Tue, 23 Apr 2013 12:50:22 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3NAnkNc007141; Tue, 23 Apr 2013 12:50:02 +0200 (CEST)
Message-ID: <5176674A.9090205@cisco.com>
Date: Tue, 23 Apr 2013 12:49:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com> <5175B89A.1090001@alum.mit.edu> <CAC4RtVBhzSCpaZH5QBLXz0TOCRpH5KL-7HdXP-JMKLwWM7i1Kw@mail.gmail.com> <011901ce3faf$95e9d780$c1bd8680$@olddog.co.uk> <CAC4RtVBA4_3w3ft4ogT17RGLuafQ87n8eskPk-6tHPTfMj=cdw@mail.gmail.com>
In-Reply-To: <CAC4RtVBA4_3w3ft4ogT17RGLuafQ87n8eskPk-6tHPTfMj=cdw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000208040502020108050901"
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 10:50:29 -0000

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

On 23/04/2013 02:10, Barry Leiba wrote:
> On Monday, April 22, 2013, Adrian Farrel wrote:
>
>     In fact, and agreeing that this is useful input, why not start the
>     shepherding *process* much sooner? That is: issue tracking;
>     milestone chasing; making sure comments are addressed/resolved; etc.
>
> ...Which is, of course, what my draft is all about.
+ 1

I believe it's time to revive draft-leiba-extended-doc-shepherd-01, 
modifying its content in the form of an experiment.

Regards, Benoit
>
> Barry


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 23/04/2013 02:10, Barry Leiba wrote:<br>
    </div>
    <blockquote
cite="mid:CAC4RtVBA4_3w3ft4ogT17RGLuafQ87n8eskPk-6tHPTfMj=cdw@mail.gmail.com"
      type="cite">On Monday, April 22, 2013, Adrian Farrel wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">
        <div link="blue" vlink="purple" lang="EN-GB">
          <div>
            <p class="MsoNormal">
              <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">In
                fact, and agreeing that this is useful input, why not
                start the shepherding *process* much sooner? That is:
                issue tracking; milestone chasing; making sure comments
                are addressed/resolved; etc.</span></p>
          </div>
        </div>
      </blockquote>
      <div>&nbsp;</div>
      <div>...Which is, of course, what my draft is all about.</div>
    </blockquote>
    + 1<br>
    <br>
    I believe it's time to revive draft-leiba-extended-doc-shepherd-01,
    modifying its content in the form of an experiment.<br>
    <br>
    Regards, Benoit<br>
    <blockquote
cite="mid:CAC4RtVBA4_3w3ft4ogT17RGLuafQ87n8eskPk-6tHPTfMj=cdw@mail.gmail.com"
      type="cite">
      <div><br>
      </div>
      <div>Barry<span></span></div>
    </blockquote>
    <br>
  </body>
</html>

--------------000208040502020108050901--

From mark@townsley.net  Tue Apr 23 04:45:07 2013
Return-Path: <mark@townsley.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E33BB21F8E47 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 04:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjhWAVxMwzMh for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 04:45:05 -0700 (PDT)
Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3CE21F969B for <wgchairs@ietf.org>; Tue, 23 Apr 2013 04:45:05 -0700 (PDT)
Received: by mail-ee0-f41.google.com with SMTP id c1so208426eek.14 for <wgchairs@ietf.org>; Tue, 23 Apr 2013 04:45:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:message-id:references:to:x-mailer:x-gm-message-state; bh=6AN1joqkf719TIxlu/c5f3/0Kae1jS8X2y9FEEna7EY=; b=nCmNbiJahVqYE6gj1v/LPsEQ+Qi9BcCaRPFKlvcp8sB1wOI5EfBYHD18nkpQuf1iHo C/HeM/8IyqgN12sjzafDeWrSk32LzyXaopHp80Dm+bdagKuuXxg97h7pAROqJbfpKUpe hQEdnhLXWrFpXZOAGOeMg4BnBdvQa4+QICBN/gS1HXbhvQd5kscs1gGDKispkMgF0+4x 6q40AU2sswXBe8i87yLjEaCo2AAZt63ylYu3V+5OtO4P9i0StjoRDuw7FGgXGgYAoBVm 8ZlcBeZ2VgFh8xLuF4cKrOqeBHAFWKALqCF++HLW0STzdgeG69TYWxjivwfLKC6qA+/2 uAaQ==
X-Received: by 10.15.83.73 with SMTP id b49mr50518527eez.25.1366717504297; Tue, 23 Apr 2013 04:45:04 -0700 (PDT)
Received: from ?IPv6:2001:420:c0c1:8:c465:9da6:b82a:5245? ([2001:420:c0c1:8:c465:9da6:b82a:5245]) by mx.google.com with ESMTPS id b5sm46402389eew.16.2013.04.23.04.45.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Apr 2013 04:45:02 -0700 (PDT)
Subject: Re: Document shepherd role
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_86DEB3F1-AB92-4CE4-AEDA-B229AF361453"
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
Date: Tue, 23 Apr 2013 13:45:00 +0200
Message-Id: <6F0C918E-38FE-417E-8234-A90168C5E61D@townsley.net>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1283)
X-Gm-Message-State: ALoCoQlZe2BeeToY4cQALE7I8hRWMNY+K19b0emK1kVOCxaJn5avRiZdu2CG5fTU5WW7ZTbdviLU
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 11:45:07 -0000

--Apple-Mail=_86DEB3F1-AB92-4CE4-AEDA-B229AF361453
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 23, 2013, at 12:00 AM, Barry Leiba wrote:

> Gee, Paul, you've provided the perfect intro.   Please check out my =
document, which I'm trying to figure out what to do with:
> https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
>=20
> Barry
>=20
> On Monday, April 22, 2013, Paul Kyzivat wrote:
> I found this discussion enlightening.
>=20
> I'd like to add a slightly different, but related, suggestion:
>=20
> Several times now when I have shepherded a draft, I start doing the =
writeup and realize it would have been really helpful to started on that =
writeup sooner - even before the document was ready for progression. My =
conclusion is that it would probably be good to assign a shepherd to a =
document as soon as it is adopted as a wg draft. (Assuming there is an =
intent that it become an RFC.) And then the shepherd can *start* filling =
out the template early. That way, after WGLC it won't take a lot of =
research, and a good memory, to fill in everything.

Excellent idea.=20

Barry, sounds like something for the General AD to consider shepherding =
(or appointing a shepherd for!)

- Mark

>=20
>         Thanks,
>         Paul
>=20
> On 4/22/13 3:08 AM, Benoit Claise wrote:
> IETF WG chairs,
>=20
> We sent a similar message to the operations an management area chairs.
> Therefore if you have seen the contents before, apologies, the =
resulting
> IESG discussion has indicated that we should distribute it more =
widely.
>=20
> During the last IETF meeting, the community discussed a lot about the
> transport AD situation. One aspect of this is the time commitment for =
an
> AD position!
>=20
> During the last IETF meeting, the community discussed a lot about
> diversity. All sort of diversities, including the IESG diversity. One
> specific aspect is the diversity of IESG member affiliations.
>=20
> Let me share my experience after one year of service as AD.
> 1. Yes, I like this job. I believe it makes a positive a difference =
for
> the Internet (hopefully positive, you'll be the judges, but that's not
> the point of this email )
> 2. Yes, this AD role requires (more than) a full time job if done
> conscientiously.
> 3. I'm concerned that we slowly created a set of requirements for an
> IESG position that will make difficult to find ADs in the future ...
> except from big companies, or when dedicated funding is allocated. Not
> good for diversity.
> 4. Believe it or not, one substantial part of my OPS activities is the
> follow up on the open issues. Recently, for a single draft, I spent
> hoouuurrrssss trying to track all the open issues from the =
directorates
> and the IESG, and chasing the authors. On top of taking some time, I =
had
> to be become expert for every single aspect of the specifications to
> evaluate whether the answer was right. After all, I have to defend =
your
> WG document during the IESG call.
>=20
> Considering the discussion above, let me focus on one important role
> within the community: the document shepherd.  This job, when done
> according to RFC 4858 would free up a huge amount of time for the ADs,
> and would speed up the document publication.
>=20
> Please read RFC 4858, specifically
>       3.2.  Document Shepherding during AD Evaluation  . . . . . . . . =
 9
>       3.3.  Document Shepherding during IESG Evaluation  . . . . . . . =
10
>=20
> Bottom line, the document shepherd job doesn't stop when the write-up =
is
> sent.
> I would like the document shepherds to follow the RFC 4858 =
instructions.
> Specifically concerning the follow up part.
> That being said, the shepherd, chairs, and the WG participants =
together
> are the custodians of WG output. So the obligations isn't solely
> invested in the shepherds. Their role via the questionnaire
> fundamentally is to document that the things required have been done,
> and to manage the remainder of the process.
>=20
> To come back to the first paragraph of my email, the document shepherd
> job (let me stress again, when done according to the function =
described
> in RFC 4858) would be beneficial for the entire community longer term.
> Let me explain: if the AD job was not a full time job, it might be
> easier to have diversity in the pool of AD candidates.
>=20
> This message was sent to all OPS WG chairs, and is now being =
distributed
> more widely.
>=20
> Also, let's keep in mind that it's not a requirement that only WG =
chairs
> are document shepherds. See
> http://www.ietf.org/iesg/statement/document-shepherds.html,The =
Shepherds
> role is a source of valuable insight into the later stages of the RFC
> process and a stepping stone for competency in other IETF roles.
>=20
> Regards, Benoit
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_86DEB3F1-AB92-4CE4-AEDA-B229AF361453
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Apr 23, 2013, at 12:00 AM, Barry Leiba =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Gee, Paul, you've provided the perfect intro. &nbsp; =
Please check out my document, which I'm trying to figure out what to do =
with:<div><a =
href=3D"https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd=
/">https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/</a>=
</div>
<div><br></div><div>Barry<span></span><br><br>On Monday, April 22, 2013, =
Paul Kyzivat  wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex; position: =
static; z-index: auto; ">I found this discussion enlightening.<br>

<br>
I'd like to add a slightly different, but related, suggestion:<br>
<br>
Several times now when I have shepherded a draft, I start doing the =
writeup and realize it would have been really helpful to started on that =
writeup sooner - even before the document was ready for progression. My =
conclusion is that it would probably be good to assign a shepherd to a =
document as soon as it is adopted as a wg draft. (Assuming there is an =
intent that it become an RFC.) And then the shepherd can *start* filling =
out the template early. That way, after WGLC it won't take a lot of =
research, and a good memory, to fill in =
everything.<br></blockquote></div></blockquote><div><br></div><div>Excelle=
nt idea.&nbsp;</div><div><br></div><div>Barry, sounds like something for =
the General AD to consider shepherding (or appointing a shepherd =
for!)</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div><blockquote class=3D"gmail_quote" style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; ">

<br>
&nbsp; &nbsp; &nbsp; &nbsp; Thanks,<br>
&nbsp; &nbsp; &nbsp; &nbsp; Paul<br>
<br>
On 4/22/13 3:08 AM, Benoit Claise wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
IETF WG chairs,<br>
<br>
We sent a similar message to the operations an management area =
chairs.<br>
Therefore if you have seen the contents before, apologies, the =
resulting<br>
IESG discussion has indicated that we should distribute it more =
widely.<br>
<br>
During the last IETF meeting, the community discussed a lot about =
the<br>
transport AD situation. One aspect of this is the time commitment for =
an<br>
AD position!<br>
<br>
During the last IETF meeting, the community discussed a lot about<br>
diversity. All sort of diversities, including the IESG diversity. =
One<br>
specific aspect is the diversity of IESG member affiliations.<br>
<br>
Let me share my experience after one year of service as AD.<br>
1. Yes, I like this job. I believe it makes a positive a difference =
for<br>
the Internet (hopefully positive, you'll be the judges, but that's =
not<br>
the point of this email )<br>
2. Yes, this AD role requires (more than) a full time job if done<br>
conscientiously.<br>
3. I'm concerned that we slowly created a set of requirements for an<br>
IESG position that will make difficult to find ADs in the future ...<br>
except from big companies, or when dedicated funding is allocated. =
Not<br>
good for diversity.<br>
4. Believe it or not, one substantial part of my OPS activities is =
the<br>
follow up on the open issues. Recently, for a single draft, I spent<br>
hoouuurrrssss trying to track all the open issues from the =
directorates<br>
and the IESG, and chasing the authors. On top of taking some time, I =
had<br>
to be become expert for every single aspect of the specifications to<br>
evaluate whether the answer was right. After all, I have to defend =
your<br>
WG document during the IESG call.<br>
<br>
Considering the discussion above, let me focus on one important role<br>
within the community: the document shepherd. &nbsp;This job, when =
done<br>
according to RFC 4858 would free up a huge amount of time for the =
ADs,<br>
and would speed up the document publication.<br>
<br>
Please read RFC 4858, specifically<br>
&nbsp; &nbsp; &nbsp; 3.2. &nbsp;Document Shepherding during AD =
Evaluation &nbsp;. . . . . . . . &nbsp;9<br>
&nbsp; &nbsp; &nbsp; 3.3. &nbsp;Document Shepherding during IESG =
Evaluation &nbsp;. . . . . . . 10<br>
<br>
Bottom line, the document shepherd job doesn't stop when the write-up =
is<br>
sent.<br>
I would like the document shepherds to follow the RFC 4858 =
instructions.<br>
Specifically concerning the follow up part.<br>
That being said, the shepherd, chairs, and the WG participants =
together<br>
are the custodians of WG output. So the obligations isn't solely<br>
invested in the shepherds. Their role via the questionnaire<br>
fundamentally is to document that the things required have been =
done,<br>
and to manage the remainder of the process.<br>
<br>
To come back to the first paragraph of my email, the document =
shepherd<br>
job (let me stress again, when done according to the function =
described<br>
in RFC 4858) would be beneficial for the entire community longer =
term.<br>
Let me explain: if the AD job was not a full time job, it might be<br>
easier to have diversity in the pool of AD candidates.<br>
<br>
This message was sent to all OPS WG chairs, and is now being =
distributed<br>
more widely.<br>
<br>
Also, let's keep in mind that it's not a requirement that only WG =
chairs<br>
are document shepherds. See<br>
<a href=3D"http://www.ietf.org/iesg/statement/document-shepherds.html,The"=
 =
target=3D"_blank">http://www.ietf.org/iesg/<u></u>statement/document-sheph=
erds.<u></u>html,The</a> Shepherds<br>
role is a source of valuable insight into the later stages of the =
RFC<br>
process and a stepping stone for competency in other IETF roles.<br>
<br>
Regards, Benoit<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote></div>
</blockquote></div><br></body></html>=

--Apple-Mail=_86DEB3F1-AB92-4CE4-AEDA-B229AF361453--

From jari.arkko@piuha.net  Tue Apr 23 05:44:01 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3BD021F96C1 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 05:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3gnXSG0ODYE for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 05:44:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 70A7321F96C0 for <wgchairs@ietf.org>; Tue, 23 Apr 2013 05:44:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8A76E2CC56; Tue, 23 Apr 2013 15:43:59 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K_euH0C1f0kj; Tue, 23 Apr 2013 15:43:58 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 74C7E2CC55; Tue, 23 Apr 2013 15:43:58 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Document shepherd role
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6F0C918E-38FE-417E-8234-A90168C5E61D@townsley.net>
Date: Tue, 23 Apr 2013 15:43:57 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7CA6631-95AA-4223-849B-8AFD5D028569@piuha.net>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com> <6F0C918E-38FE-417E-8234-A90168C5E61D@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1503)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 12:44:01 -0000

> Barry, sounds like something for the General AD to consider =
shepherding (or appointing a shepherd for!)

And I'm tracking it=85 and I like what the draft says, but I'm trying to =
figure out how to not repeat what happened last year when this draft =
went to the previous IESG and did not get approved. (I wasn't there, so =
I'm still trying to collect the pieces of history. But I think the issue =
had to do more with how it was packaged, rather than the actual content. =
A process experiment would seem like the right thing to do here.)

Jari



From david.black@emc.com  Tue Apr 23 09:21:04 2013
Return-Path: <david.black@emc.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 090DB21F9629 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 09:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.547
X-Spam-Level: 
X-Spam-Status: No, score=-101.547 tagged_above=-999 required=5 tests=[AWL=1.051, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2T3Og4Q12aU5 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 09:21:00 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 010E221F9627 for <wgchairs@ietf.org>; Tue, 23 Apr 2013 09:20:59 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3NGKnjW030303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Apr 2013 12:20:51 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Tue, 23 Apr 2013 12:20:33 -0400
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3NGKX7G008541; Tue, 23 Apr 2013 12:20:33 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Tue, 23 Apr 2013 12:20:32 -0400
From: "Black, David" <david.black@emc.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Tue, 23 Apr 2013 12:20:31 -0400
Subject: RE: Document shepherd role
Thread-Topic: Document shepherd role
Thread-Index: Ac4/pT1EGcRC8lF9Qh2R2GafbNoBnQAl896A
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293F3B969@MX15A.corp.emc.com>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
In-Reply-To: <CAC4RtVA9r2AQ5vC+yVpijzYfycQep2quvaTV1+vPXxO=vBBeAw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE71293F3B969MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 16:21:04 -0000

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

Hi Barry,

Hmm - it looks like I have some relevant "running code" experience with the=
 WG
document stage of this from the IPS working group, which was a three-ring c=
ircus,
as the WG was effectively working on three major protocols concurrently.  H=
ere's
the relevant charter text from: http://www.ietf.org/wg/concluded/ips.html:

  A technical coordinator will be identified and selected for each
  protocol encapsulation adopted as a work item by the group. This person
  will be responsible for coordinating the technical efforts of the group
  with respect to that encapsulation, working with and motivating the
  document editors, and evangelizing the group's work within both the
  community and relevant external organizations such as T10 and T11.

That structure was reasonably effective, due in part to the clear technical
division of scope of responsibility (by major protocol) among the technical
coordinators.  I'd use that structure again for a WG with similarly broad
scope and level of activity, and asking the coordinators to continue on to
serve as document shepherds makes sense to me.

Please note - during most of the IPS WG's lifetime there were two co-chairs=
,
and there were three for a while.  Although I was the last WG chair left
standing when IPS concluded, I did not run that entire effort single-handed=
ly.

Thanks,
--David

From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On Behal=
f Of Barry Leiba
Sent: Monday, April 22, 2013 6:01 PM
To: Paul Kyzivat
Cc: wgchairs@ietf.org
Subject: Re: Document shepherd role

Gee, Paul, you've provided the perfect intro.   Please check out my documen=
t, which I'm trying to figure out what to do with:
https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/

Barry

On Monday, April 22, 2013, Paul Kyzivat wrote:
I found this discussion enlightening.

I'd like to add a slightly different, but related, suggestion:

Several times now when I have shepherded a draft, I start doing the writeup=
 and realize it would have been really helpful to started on that writeup s=
ooner - even before the document was ready for progression. My conclusion i=
s that it would probably be good to assign a shepherd to a document as soon=
 as it is adopted as a wg draft. (Assuming there is an intent that it becom=
e an RFC.) And then the shepherd can *start* filling out the template early=
. That way, after WGLC it won't take a lot of research, and a good memory, =
to fill in everything.

        Thanks,
        Paul

On 4/22/13 3:08 AM, Benoit Claise wrote:
IETF WG chairs,

We sent a similar message to the operations an management area chairs.
Therefore if you have seen the contents before, apologies, the resulting
IESG discussion has indicated that we should distribute it more widely.

During the last IETF meeting, the community discussed a lot about the
transport AD situation. One aspect of this is the time commitment for an
AD position!

During the last IETF meeting, the community discussed a lot about
diversity. All sort of diversities, including the IESG diversity. One
specific aspect is the diversity of IESG member affiliations.

Let me share my experience after one year of service as AD.
1. Yes, I like this job. I believe it makes a positive a difference for
the Internet (hopefully positive, you'll be the judges, but that's not
the point of this email )
2. Yes, this AD role requires (more than) a full time job if done
conscientiously.
3. I'm concerned that we slowly created a set of requirements for an
IESG position that will make difficult to find ADs in the future ...
except from big companies, or when dedicated funding is allocated. Not
good for diversity.
4. Believe it or not, one substantial part of my OPS activities is the
follow up on the open issues. Recently, for a single draft, I spent
hoouuurrrssss trying to track all the open issues from the directorates
and the IESG, and chasing the authors. On top of taking some time, I had
to be become expert for every single aspect of the specifications to
evaluate whether the answer was right. After all, I have to defend your
WG document during the IESG call.

Considering the discussion above, let me focus on one important role
within the community: the document shepherd.  This job, when done
according to RFC 4858 would free up a huge amount of time for the ADs,
and would speed up the document publication.

Please read RFC 4858, specifically
      3.2.  Document Shepherding during AD Evaluation  . . . . . . . .  9
      3.3.  Document Shepherding during IESG Evaluation  . . . . . . . 10

Bottom line, the document shepherd job doesn't stop when the write-up is
sent.
I would like the document shepherds to follow the RFC 4858 instructions.
Specifically concerning the follow up part.
That being said, the shepherd, chairs, and the WG participants together
are the custodians of WG output. So the obligations isn't solely
invested in the shepherds. Their role via the questionnaire
fundamentally is to document that the things required have been done,
and to manage the remainder of the process.

To come back to the first paragraph of my email, the document shepherd
job (let me stress again, when done according to the function described
in RFC 4858) would be beneficial for the entire community longer term.
Let me explain: if the AD job was not a full time job, it might be
easier to have diversity in the pool of AD candidates.

This message was sent to all OPS WG chairs, and is now being distributed
more widely.

Also, let's keep in mind that it's not a requirement that only WG chairs
are document shepherds. See
http://www.ietf.org/iesg/statement/document-shepherds.html,The Shepherds
role is a source of valuable insight into the later stages of the RFC
process and a stepping stone for competency in other IETF roles.

Regards, Benoit





--_000_8D3D17ACE214DC429325B2B98F3AE71293F3B969MX15Acorpemccom_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40"><head><meta http-equiv=3DContent-Type content=3D"text/html; charset=3Du=
s-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medi=
um)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=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'>Hi Barry,<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=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Hm=
m - it looks like I have some relevant &#8220;running code&#8221; experienc=
e with the WG<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:black'>document stage of this =
from the IPS working group, which was a three-ring circus,<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New";color:black'>as the WG was effectively working on three major prot=
ocols concurrently.&nbsp; Here&#8217;s<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black=
'>the relevant charter text from: <a href=3D"http://www.ietf.org/wg/conclud=
ed/ips.html">http://www.ietf.org/wg/concluded/ips.html</a>: <o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp;=
 A technical coordinator will be identified and selected for each<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Courier New";color:black'>&nbsp; protocol encapsulation adopted as a wor=
k item by the group. This person<br>&nbsp; will be responsible for coordina=
ting the technical efforts of the group <br>&nbsp;&nbsp;with respect to tha=
t encapsulation, working with and motivating the <br>&nbsp;&nbsp;document e=
ditors, and evangelizing the group's work within both the <br>&nbsp;&nbsp;c=
ommunity and relevant external organizations such as T10 and T11.<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-famil=
y:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>T=
hat structure was reasonably effective, due in part to the clear technical<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New";color:black'>division of scope of responsibility (=
by major protocol) among the technical<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black=
'>coordinators.&nbsp; I&#8217;d use that structure again for a WG with simi=
larly broad<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;font-family:"Courier New";color:black'>scope and level of activi=
ty, and asking the coordinators to continue on to<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";=
color:black'>serve as document shepherds makes sense to me.<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Please =
note - during most of the IPS WG&#8217;s lifetime there were two co-chairs,=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'>and there were three for a while.&nb=
sp; Although I was the last WG chair left<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";color:bl=
ack'>standing when IPS concluded, I did not run that entire effort single-h=
andedly.<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>=
<div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cour=
ier 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><p c=
lass=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-l=
eft:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'border:n=
one;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMs=
oNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif"'> wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] <b=
>On Behalf Of </b>Barry Leiba<br><b>Sent:</b> Monday, April 22, 2013 6:01 P=
M<br><b>To:</b> Paul Kyzivat<br><b>Cc:</b> wgchairs@ietf.org<br><b>Subject:=
</b> Re: Document shepherd role<o:p></o:p></span></p></div></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Gee, Paul, you've pr=
ovided the perfect intro. &nbsp; Please check out my document, which I'm tr=
ying to figure out what to do with:<o:p></o:p></p><div><p class=3DMsoNormal=
><a href=3D"https://datatracker.ietf.org/doc/draft-leiba-extended-doc-sheph=
erd/">https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/</=
a><o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div=
><div><p class=3DMsoNormal>Barry<br><br>On Monday, April 22, 2013, Paul Kyz=
ivat wrote:<o:p></o:p></p><p class=3DMsoNormal>I found this discussion enli=
ghtening.<br><br>I'd like to add a slightly different, but related, suggest=
ion:<br><br>Several times now when I have shepherded a draft, I start doing=
 the writeup and realize it would have been really helpful to started on th=
at writeup sooner - even before the document was ready for progression. My =
conclusion is that it would probably be good to assign a shepherd to a docu=
ment as soon as it is adopted as a wg draft. (Assuming there is an intent t=
hat it become an RFC.) And then the shepherd can *start* filling out the te=
mplate early. That way, after WGLC it won't take a lot of research, and a g=
ood memory, to fill in everything.<br><br>&nbsp; &nbsp; &nbsp; &nbsp; Thank=
s,<br>&nbsp; &nbsp; &nbsp; &nbsp; Paul<br><span style=3D'color:black'> </sp=
an><br>On 4/22/13 3:08 AM, Benoit Claise wrote:<o:p></o:p></p><p class=3DMs=
oNormal style=3D'margin-bottom:12.0pt'>IETF WG chairs,<br><br>We sent a sim=
ilar message to the operations an management area chairs.<br>Therefore if y=
ou have seen the contents before, apologies, the resulting<br>IESG discussi=
on has indicated that we should distribute it more widely.<br><br>During th=
e last IETF meeting, the community discussed a lot about the<br>transport A=
D situation. One aspect of this is the time commitment for an<br>AD positio=
n!<br><br>During the last IETF meeting, the community discussed a lot about=
<br>diversity. All sort of diversities, including the IESG diversity. One<b=
r>specific aspect is the diversity of IESG member affiliations.<br><br>Let =
me share my experience after one year of service as AD.<br>1. Yes, I like t=
his job. I believe it makes a positive a difference for<br>the Internet (ho=
pefully positive, you'll be the judges, but that's not<br>the point of this=
 email )<br>2. Yes, this AD role requires (more than) a full time job if do=
ne<br>conscientiously.<br>3. I'm concerned that we slowly created a set of =
requirements for an<br>IESG position that will make difficult to find ADs i=
n the future ...<br>except from big companies, or when dedicated funding is=
 allocated. Not<br>good for diversity.<br>4. Believe it or not, one substan=
tial part of my OPS activities is the<br>follow up on the open issues. Rece=
ntly, for a single draft, I spent<br>hoouuurrrssss trying to track all the =
open issues from the directorates<br>and the IESG, and chasing the authors.=
 On top of taking some time, I had<br>to be become expert for every single =
aspect of the specifications to<br>evaluate whether the answer was right. A=
fter all, I have to defend your<br>WG document during the IESG call.<br><br=
>Considering the discussion above, let me focus on one important role<br>wi=
thin the community: the document shepherd. &nbsp;This job, when done<br>acc=
ording to RFC 4858 would free up a huge amount of time for the ADs,<br>and =
would speed up the document publication.<br><br>Please read RFC 4858, speci=
fically<br>&nbsp; &nbsp; &nbsp; 3.2. &nbsp;Document Shepherding during AD E=
valuation &nbsp;. . . . . . . . &nbsp;9<br>&nbsp; &nbsp; &nbsp; 3.3. &nbsp;=
Document Shepherding during IESG Evaluation &nbsp;. . . . . . . 10<br><br>B=
ottom line, the document shepherd job doesn't stop when the write-up is<br>=
sent.<br>I would like the document shepherds to follow the RFC 4858 instruc=
tions.<br>Specifically concerning the follow up part.<br>That being said, t=
he shepherd, chairs, and the WG participants together<br>are the custodians=
 of WG output. So the obligations isn't solely<br>invested in the shepherds=
. Their role via the questionnaire<br>fundamentally is to document that the=
 things required have been done,<br>and to manage the remainder of the proc=
ess.<br><br>To come back to the first paragraph of my email, the document s=
hepherd<br>job (let me stress again, when done according to the function de=
scribed<br>in RFC 4858) would be beneficial for the entire community longer=
 term.<br>Let me explain: if the AD job was not a full time job, it might b=
e<br>easier to have diversity in the pool of AD candidates.<br><br>This mes=
sage was sent to all OPS WG chairs, and is now being distributed<br>more wi=
dely.<br><br>Also, let's keep in mind that it's not a requirement that only=
 WG chairs<br>are document shepherds. See<br><a href=3D"http://www.ietf.org=
/iesg/statement/document-shepherds.html,The" target=3D"_blank">http://www.i=
etf.org/iesg/statement/document-shepherds.html,The</a> Shepherds<br>role is=
 a source of valuable insight into the later stages of the RFC<br>process a=
nd a stepping stone for competency in other IETF roles.<br><br>Regards, Ben=
oit<br><br><br><br><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE71293F3B969MX15Acorpemccom_--

From sm@elandsys.com  Tue Apr 23 17:52:18 2013
Return-Path: <sm@elandsys.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A1621F93A6 for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 17:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvyo5syqvlMe for <wgchairs@ietfa.amsl.com>; Tue, 23 Apr 2013 17:52:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFDC21F933F for <wgchairs@ietf.org>; Tue, 23 Apr 2013 17:52:17 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.133.186]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3O0q2TR025564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Apr 2013 17:52:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366764734; bh=ebjVV79rB/slJme3YTKuWrPG/wYl0FGzPQpLHtIdAQ4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mJqi2zoIs/v/TiUKhshmDfnoGnbw4zkDo/AmY8s1kQnKl5DJdnQbugRGbfPRhu5cs d8LOjpBzutCALFlsxN4+eJDHpWznTf0+eo9egKUXCXcIAVE1xPGA5U7m5q9P/eWt+S RnpBk2DpdT2IF4bKul+1McOTV4CkItBVFJtimu4U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1366764734; i=@elandsys.com; bh=ebjVV79rB/slJme3YTKuWrPG/wYl0FGzPQpLHtIdAQ4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OEfBhVlUYuGWIl7go2tk4zBL7xOryneNTKPlmoFfJsz3p3kp0Gu+b3cYEGd2P2CoC 7iCKhBtI1FbRHk2i3xQtNP1WDNabduyn7cJ4EkoPJ33cp1Bwtpu8TV93+WVFK+fNXE h5OAxveF3KSoObkdIIOkk/jIDRLYTpAR202/rXqw=
Message-Id: <6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Apr 2013 17:46:54 -0700
To: Benoit Claise <bclaise@cisco.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Document shepherd role
In-Reply-To: <5174E1DA.7020904@cisco.com>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 00:52:18 -0000

Hi Benoit,
At 00:08 22-04-2013, Benoit Claise wrote:
>4. Believe it or not, one substantial part of my OPS activities is the
>follow up on the open issues. Recently, for a single draft, I spent
>hoouuurrrssss trying to track all the open issues from the directorates
>and the IESG, and chasing the authors. On top of taking some time, I had
>to be become expert for every single aspect of the specifications to
>evaluate whether the answer was right. After all, I have to defend your
>WG document during the IESG call.

Thanks for responding to the AppsDir review of 
draft-ietf-ipfix-flow-selection-tech-14.  I hope that the author (who 
was responsive) did not go through the usual bad IETF experience.

I'll comment from an AppsDir perspective.  The only document 
shepherds who have interacted with AppsDir (I'll ignore Apps folks) are:

   Jeffrey Hutzelman
   Joel Halpern
   Warren Kumari
   Andrew Sullivan

The AppsDir reviewers do not usually take an antagonist position and 
go out of their way, in my opinion, to help the document 
authors.  Some of that work is document shepherd work instead of 
reviewer work.  The follow-up (to the review) ends up as more 
work.  Sometimes issues raised in an AppsDir review are not 
addressed.  I view that as a lack of consideration for the reviewer 
who has put in his/her free time to look at a draft in which he/she 
does not have any interest.  It's difficult enough to get reviews done.

Regards,
S. Moonesamy 


From bclaise@cisco.com  Wed Apr 24 07:27:02 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4170E21F8AD5 for <wgchairs@ietfa.amsl.com>; Wed, 24 Apr 2013 07:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.526
X-Spam-Level: 
X-Spam-Status: No, score=-10.526 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4qvQSOcs2Y1 for <wgchairs@ietfa.amsl.com>; Wed, 24 Apr 2013 07:27:01 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id C450921F90EB for <wgchairs@ietf.org>; Wed, 24 Apr 2013 07:27:00 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3OEQgmm023243; Wed, 24 Apr 2013 16:26:42 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3OEQFB6001932; Wed, 24 Apr 2013 16:26:31 +0200 (CEST)
Message-ID: <5177EB87.8010700@cisco.com>
Date: Wed, 24 Apr 2013 16:26:15 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com>
Content-Type: multipart/alternative; boundary="------------090600010307010603020002"
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 14:27:02 -0000

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

Hi,

Thanks for your feedback.
See in line.
> Hi Benoit,
> At 00:08 22-04-2013, Benoit Claise wrote:
>> 4. Believe it or not, one substantial part of my OPS activities is the
>> follow up on the open issues. Recently, for a single draft, I spent
>> hoouuurrrssss trying to track all the open issues from the directorates
>> and the IESG, and chasing the authors. On top of taking some time, I had
>> to be become expert for every single aspect of the specifications to
>> evaluate whether the answer was right. After all, I have to defend your
>> WG document during the IESG call.
>
> Thanks for responding to the AppsDir review of 
> draft-ietf-ipfix-flow-selection-tech-14.
Not sure why you mentioned this draft specifically.
It's not the one I had in mind when I wrote the paragraph above.
Anyway, it doesn't matter. See below.
> I hope that the author (who was responsive) did not go through the 
> usual bad IETF experience.
>
> I'll comment from an AppsDir perspective.  The only document shepherds 
> who have interacted with AppsDir (I'll ignore Apps folks) are:
>
>   Jeffrey Hutzelman
>   Joel Halpern
>   Warren Kumari
>   Andrew Sullivan
>
> The AppsDir reviewers do not usually take an antagonist position and 
> go out of their way, in my opinion, to help the document authors.  
> Some of that work is document shepherd work instead of reviewer work.  
> The follow-up (to the review) ends up as more work.
> Sometimes issues raised in an AppsDir review are not addressed.  I 
> view that as a lack of consideration for the reviewer who has put in 
> his/her free time to look at a draft in which he/she does not have any 
> interest.  It's difficult enough to get reviews done.
This should not happen!
One of the difficulties with directorates is that they have different 
goals, and therefore, send their draft review feedback to different 
people: to their respective ADs, to the directorate mailer, to the 
authors, to the WG. Some are not even archived.
Recently, we realized that some reviews were not reaching the right 
persons. At least not the draft AD ... who should be one of persons 
follow up.
In the OPS directorate, we have solved this by inserting this note in 
the review request email:

    Reviews are sent the OPS DIR mailing list (ops-dir@ietf.org) and to
    the authors, WG chairs, and respective AD. The way to reach the
    authors, WG chairs, and respective AD is to send an email to
    <draft-name>.all@tools.ietf.org

To make the link with the document shepherd, one issue needs to be 
fixed: currently the <draft-name>.all@tools.ietf.org doesn't contain the 
doc shepherd. I'll work on that one.

Regards, Benoit
>
> Regards,
> S. Moonesamy
>


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi, <br>
      <br>
      Thanks for your feedback.<br>
      See in line.<br>
    </div>
    <blockquote
      cite="mid:6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com"
      type="cite">Hi Benoit,
      <br>
      At 00:08 22-04-2013, Benoit Claise wrote:
      <br>
      <blockquote type="cite">4. Believe it or not, one substantial part
        of my OPS activities is the
        <br>
        follow up on the open issues. Recently, for a single draft, I
        spent
        <br>
        hoouuurrrssss trying to track all the open issues from the
        directorates
        <br>
        and the IESG, and chasing the authors. On top of taking some
        time, I had
        <br>
        to be become expert for every single aspect of the
        specifications to
        <br>
        evaluate whether the answer was right. After all, I have to
        defend your
        <br>
        WG document during the IESG call.
        <br>
      </blockquote>
      <br>
      Thanks for responding to the AppsDir review of
      draft-ietf-ipfix-flow-selection-tech-14. <br>
    </blockquote>
    Not sure why you mentioned this draft specifically.<br>
    It's not the one I had in mind when I wrote the paragraph above. <br>
    Anyway, it doesn't matter. See below.<br>
    <blockquote
      cite="mid:6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com"
      type="cite"> I hope that the author (who was responsive) did not
      go through the usual bad IETF experience.
      <br>
      <br>
      I'll comment from an AppsDir perspective.&nbsp; The only document
      shepherds who have interacted with AppsDir (I'll ignore Apps
      folks) are:
      <br>
      <br>
      &nbsp; Jeffrey Hutzelman
      <br>
      &nbsp; Joel Halpern
      <br>
      &nbsp; Warren Kumari
      <br>
      &nbsp; Andrew Sullivan
      <br>
      <br>
      The AppsDir reviewers do not usually take an antagonist position
      and go out of their way, in my opinion, to help the document
      authors.&nbsp; Some of that work is document shepherd work instead of
      reviewer work.&nbsp; The follow-up (to the review) ends up as more
      work. <br>
    </blockquote>
    <blockquote
      cite="mid:6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com"
      type="cite"> Sometimes issues raised in an AppsDir review are not
      addressed.&nbsp; I view that as a lack of consideration for the
      reviewer who has put in his/her free time to look at a draft in
      which he/she does not have any interest.&nbsp; It's difficult enough to
      get reviews done.
      <br>
    </blockquote>
    This should not happen!<br>
    One of the difficulties with directorates is that they have
    different goals, and therefore, send their draft review feedback to
    different people: to their respective ADs, to the directorate
    mailer, to the authors, to the WG. Some are not even archived.<br>
    Recently, we realized that some reviews were not reaching the right
    persons. At least not the draft AD ... who should be one of persons
    follow up.<br>
    In the OPS directorate, we have solved this by inserting this note
    in the review request email:<br>
    <blockquote>Reviews are sent the OPS DIR mailing list
      (<a class="moz-txt-link-abbreviated" href="mailto:ops-dir@ietf.org">ops-dir@ietf.org</a>) and to the authors, WG chairs, and respective
      AD. The way to reach the authors, WG chairs, and respective AD is
      to send an email to &lt;draft-name&gt;.all@tools.ietf.org<br>
    </blockquote>
    To make the link with the document shepherd, one issue needs to be
    fixed: currently the &lt;draft-name&gt;.all@tools.ietf.org doesn't
    contain the doc shepherd. I'll work on that one.<br>
    <br>
    Regards, Benoit<br>
    <blockquote
      cite="mid:6.2.5.6.2.20130423165515.0c3fbc58@elandnews.com"
      type="cite">
      <br>
      Regards,
      <br>
      S. Moonesamy <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------090600010307010603020002--

From joelja@bogus.com  Wed Apr 24 10:42:12 2013
Return-Path: <joelja@bogus.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E28B21F9164 for <wgchairs@ietfa.amsl.com>; Wed, 24 Apr 2013 10:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdZmKJex64H4 for <wgchairs@ietfa.amsl.com>; Wed, 24 Apr 2013 10:42:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 388BE21F9027 for <wgchairs@ietf.org>; Wed, 24 Apr 2013 10:42:11 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r3OHg9BW087642 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 24 Apr 2013 17:42:09 GMT (envelope-from joelja@bogus.com)
Message-ID: <5178196B.3070106@bogus.com>
Date: Wed, 24 Apr 2013 10:42:03 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: Document shepherd role
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com>	<5175AF99.4020408@alum.mit.edu>	<A159B9B4-DBE3-4CD8-8E28-23D88D9B5168@lilacglade.org> <5175B401.6070303@alum.mit.edu>
In-Reply-To: <5175B401.6070303@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 24 Apr 2013 17:42:09 +0000 (UTC)
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Apr 2013 17:42:12 -0000

On 4/22/13 3:04 PM, Paul Kyzivat wrote:
> On 4/22/13 5:54 PM, Margaret Wasserman wrote:
>>
>> In busy working groups, ones with a lot of documents, it isn't 
>> unusual for the chairs to divide up responsibility for the active WG 
>> drafts.  When those drafts go into the IESG, the WG chair who has 
>> been responsible for the document during the WG process usually 
>> shepherds the draft through the IESG.  That works pretty well, in my 
>> experience.
>>
>> In less busy groups, ones with fewer drafts, the chairs may work 
>> together on all of the documents.  They then have to assign a 
>> shepherd at the end.  Depending on the roles of the individual 
>> chairs, this can work well, but sometimes the chair needs to fill in 
>> a lot of knowledge to do the shepherding task.  In these cases, I 
>> agree it might make sense to explicitly decide who will shepherd the 
>> draft earlier in the process.
>
> In the groups I chair we haven't overtly considered who will shepherd 
> a document until after WGLC. Maybe this isn't a problem for other 
> groups. But for mine I'm just discovering that starting this earlier 
> would be helpful.

So I don't think the task is especially onerous, hard or requires deeply 
advance planning. The part that chairs are generally good at and  
generally do well in the case where they are the shepherds  is reviewing 
the consensus,  and ticking the ipr boxes.

>     Thanks,
>     Paul
>
>> Margaret
>>
>> On Apr 22, 2013, at 5:46 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>>> I found this discussion enlightening.
>>>
>>> I'd like to add a slightly different, but related, suggestion:
>>>
>>> Several times now when I have shepherded a draft, I start doing the 
>>> writeup and realize it would have been really helpful to started on 
>>> that writeup sooner - even before the document was ready for 
>>> progression. My conclusion is that it would probably be good to 
>>> assign a shepherd to a document as soon as it is adopted as a wg 
>>> draft. (Assuming there is an intent that it become an RFC.) And then 
>>> the shepherd can *start* filling out the template early. That way, 
>>> after WGLC it won't take a lot of research, and a good memory, to 
>>> fill in everything.
>>>
>>>     Thanks,
>>>     Paul
>>>
>>> On 4/22/13 3:08 AM, Benoit Claise wrote:
>>>> IETF WG chairs,
>>>>
>>>> We sent a similar message to the operations an management area chairs.
>>>> Therefore if you have seen the contents before, apologies, the 
>>>> resulting
>>>> IESG discussion has indicated that we should distribute it more 
>>>> widely.
>>>>
>>>> During the last IETF meeting, the community discussed a lot about the
>>>> transport AD situation. One aspect of this is the time commitment 
>>>> for an
>>>> AD position!
>>>>
>>>> During the last IETF meeting, the community discussed a lot about
>>>> diversity. All sort of diversities, including the IESG diversity. One
>>>> specific aspect is the diversity of IESG member affiliations.
>>>>
>>>> Let me share my experience after one year of service as AD.
>>>> 1. Yes, I like this job. I believe it makes a positive a difference 
>>>> for
>>>> the Internet (hopefully positive, you'll be the judges, but that's not
>>>> the point of this email )
>>>> 2. Yes, this AD role requires (more than) a full time job if done
>>>> conscientiously.
>>>> 3. I'm concerned that we slowly created a set of requirements for an
>>>> IESG position that will make difficult to find ADs in the future ...
>>>> except from big companies, or when dedicated funding is allocated. Not
>>>> good for diversity.
>>>> 4. Believe it or not, one substantial part of my OPS activities is the
>>>> follow up on the open issues. Recently, for a single draft, I spent
>>>> hoouuurrrssss trying to track all the open issues from the 
>>>> directorates
>>>> and the IESG, and chasing the authors. On top of taking some time, 
>>>> I had
>>>> to be become expert for every single aspect of the specifications to
>>>> evaluate whether the answer was right. After all, I have to defend 
>>>> your
>>>> WG document during the IESG call.
>>>>
>>>> Considering the discussion above, let me focus on one important role
>>>> within the community: the document shepherd.  This job, when done
>>>> according to RFC 4858 would free up a huge amount of time for the ADs,
>>>> and would speed up the document publication.
>>>>
>>>> Please read RFC 4858, specifically
>>>>       3.2.  Document Shepherding during AD Evaluation  . . . . . . 
>>>> . .  9
>>>>       3.3.  Document Shepherding during IESG Evaluation  . . . . . 
>>>> . . 10
>>>>
>>>> Bottom line, the document shepherd job doesn't stop when the 
>>>> write-up is
>>>> sent.
>>>> I would like the document shepherds to follow the RFC 4858 
>>>> instructions.
>>>> Specifically concerning the follow up part.
>>>> That being said, the shepherd, chairs, and the WG participants 
>>>> together
>>>> are the custodians of WG output. So the obligations isn't solely
>>>> invested in the shepherds. Their role via the questionnaire
>>>> fundamentally is to document that the things required have been done,
>>>> and to manage the remainder of the process.
>>>>
>>>> To come back to the first paragraph of my email, the document shepherd
>>>> job (let me stress again, when done according to the function 
>>>> described
>>>> in RFC 4858) would be beneficial for the entire community longer term.
>>>> Let me explain: if the AD job was not a full time job, it might be
>>>> easier to have diversity in the pool of AD candidates.
>>>>
>>>> This message was sent to all OPS WG chairs, and is now being 
>>>> distributed
>>>> more widely.
>>>>
>>>> Also, let's keep in mind that it's not a requirement that only WG 
>>>> chairs
>>>> are document shepherds. See
>>>> http://www.ietf.org/iesg/statement/document-shepherds.html,The 
>>>> Shepherds
>>>> role is a source of valuable insight into the later stages of the RFC
>>>> process and a stepping stone for competency in other IETF roles.
>>>>
>>>> Regards, Benoit
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>


From sarikaya2012@gmail.com  Thu Apr 25 11:37:44 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE5C321F967F for <wgchairs@ietfa.amsl.com>; Thu, 25 Apr 2013 11:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zL69fnLG8k+C for <wgchairs@ietfa.amsl.com>; Thu, 25 Apr 2013 11:37:44 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1093821F9675 for <wgchairs@ietf.org>; Thu, 25 Apr 2013 11:37:43 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id ea20so2873117lab.2 for <wgchairs@ietf.org>; Thu, 25 Apr 2013 11:37:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=CZ8m2fr3Gg7iSAoNo1HBJ5OuTABYXahTyZ93F3JfpeI=; b=auAU6Z91F8VFp3jeP+QmitUzx2GApC8ROJjn4X2nHkMWhD3ANFLyne6TuI6wgJEXQ+ swmsnkj9aTSgWY0wOq4D9Ayhwn970zXC7UvSHeYXmkLZY9iMXomFLf0lOqwY36DaYjeh atlMQ5GUJvSKhrSO4k0ABj6iZ81phN41c5ytfw60M+0jt8G8bEZpYdPCbBVnZRfU24jZ 3b35ujcY2nWGyYG0h8uDy8rnLm8mHsO1bZ+VPQs9zCkZvVtXnnU4NQfFKsFvYnRSiI+L 7D8lLmbcSTQGDADK0ml5ILlsTGDrHvtEs/BVG1yBaliIYxU/XLCxIucK4rvoVXIBI6aF Pdzw==
MIME-Version: 1.0
X-Received: by 10.112.150.228 with SMTP id ul4mr8213661lbb.132.1366915062974;  Thu, 25 Apr 2013 11:37:42 -0700 (PDT)
Received: by 10.114.175.140 with HTTP; Thu, 25 Apr 2013 11:37:42 -0700 (PDT)
In-Reply-To: <5178196B.3070106@bogus.com>
References: <5172F297.2080301@bogus.com> <5174E1DA.7020904@cisco.com> <5175AF99.4020408@alum.mit.edu> <A159B9B4-DBE3-4CD8-8E28-23D88D9B5168@lilacglade.org> <5175B401.6070303@alum.mit.edu> <5178196B.3070106@bogus.com>
Date: Thu, 25 Apr 2013 13:37:42 -0500
Message-ID: <CAC8QAceZjUJakprkLH1PFwqpKHc8y3sZpkjeFgry=NNZBcZ+YA@mail.gmail.com>
Subject: Re: Document shepherd role
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=047d7b342d28c44c6304db33b615
Cc: wgchairs@ietf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 25 Apr 2013 18:37:44 -0000

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

+1

Regards,

Behcet

On Wed, Apr 24, 2013 at 12:42 PM, joel jaeggli <joelja@bogus.com> wrote:

>
> So I don't think the task is especially onerous, hard or requires deeply
> advance planning. The part that chairs are generally good at and  generally
> do well in the case where they are the shepherds  is reviewing the
> consensus,  and ticking the ipr boxes.
>
>

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

+1<br><br>Regards,<br><br>Behcet<br><br><div class=3D"gmail_quote">On Wed, =
Apr 24, 2013 at 12:42 PM, joel jaeggli <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:joelja@bogus.com" target=3D"_blank">joelja@bogus.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br></div>
So I don&#39;t think the task is especially onerous, hard or requires deepl=
y advance planning. The part that chairs are generally good at and =A0gener=
ally do well in the case where they are the shepherds =A0is reviewing the c=
onsensus, =A0and ticking the ipr boxes.<div class=3D"HOEnZb">
<div class=3D"h5"><br></div></div></blockquote></div>

--047d7b342d28c44c6304db33b615--

From adrian@olddog.co.uk  Thu Apr 25 14:32:05 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E83521F96F7 for <wgchairs@ietfa.amsl.com>; Thu, 25 Apr 2013 14:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nEQdLl2iit60 for <wgchairs@ietfa.amsl.com>; Thu, 25 Apr 2013 14:32:04 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF4421F96E6 for <wgchairs@ietf.org>; Thu, 25 Apr 2013 14:32:00 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3PLVxeP008185 for <wgchairs@ietf.org>; Thu, 25 Apr 2013 22:31:59 +0100
Received: from 950129200 ([69.38.252.85]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3PLVdtT007966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <wgchairs@ietf.org>; Thu, 25 Apr 2013 22:31:58 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <wgchairs@ietf.org>
Subject: Your review appreciated [Was: Last Call: <draft-sheffer-running-code-04.txt>]
Date: Thu, 25 Apr 2013 22:31:38 +0100
Message-ID: <01ca01ce41fc$50b9a1f0$f22ce5d0$@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: Ac5B6M+mkqPPHOxKSTOKkJeA2NRD1g==
Content-Language: en-gb
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Apr 2013 21:32:05 -0000

If you have a few cycles, your last call review would be very helpful.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 12 April 2013 22:57
> To: IETF-Announce
> Subject: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness
of
> Running Code: the Implementation Status Section) to Experimental RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Improving Awareness of Running Code: the Implementation Status
> Section'
>   <draft-sheffer-running-code-04.txt> as Experimental RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-05-10. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document describes a simple process that allows authors of
>    Internet-Drafts to record the status of known implementations by
>    including an Implementation Status section.  This will allow
>    reviewers and working groups to assign due consideration to documents
>    that have the benefit of running code, by considering the running
>    code as evidence of valuable experimentation and feedback that has
>    made the implemented protocols more mature.
> 
>    The process in this document is offered as an experiment.  Authors of
>    Internet-Drafts are encouraged to consider using the process for
>    their documents, and working groups are invited to think about
>    applying the process to all of their protocol specifications.  The
>    authors of this document intend to collate experiences with this
>    experiment and to report them to the community.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.



From agenda@ietf.org  Mon Apr 29 07:32:16 2013
Return-Path: <agenda@ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B79F021F9DBD; Mon, 29 Apr 2013 07:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.201
X-Spam-Level: 
X-Spam-Status: No, score=-101.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fl2GbmXegU8e; Mon, 29 Apr 2013 07:32:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C130C21F9DBA; Mon, 29 Apr 2013 07:32:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Agenda <agenda@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>
Subject: 87th IETF - Working Group/BOF/IRTF Scheduling
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p4
Message-ID: <20130429143215.6457.60981.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2013 07:32:15 -0700
Cc: irsg@irtf.org
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/wgchairs>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 14:32:16 -0000

-----------------------------------------------------------------
87th IETF =E2=80=93 Berlin, Germany
Meeting Dates: July 28 =E2=80=93 August 2, 2013
-----------------------------------------------------------------
IETF meetings start Monday morning and run through Friday afternoon (13:30).

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

NOTE: cutoff dates are subject to change.

- 2013-04-29 (Monday): Working Group and BOF scheduling begins. To request =
a Working Group session, use the IETF Meeting Session Request Tool.
- 2013-06-03 (Monday): Cutoff date for requests to schedule Working Group m=
eetings at UTC 24:00. To request a Working Group session, use the IETF Meet=
ing Session Request Tool.
- 2013-06-17 (Monday): Cutoff date for BOF proposal requests to Area Direct=
ors at UTC 24:00. To request a BOF, please see instructions on Requesting a=
 BOF.
- 2013-06-20 (Thursday): Cutoff date for Area Directors to approve BOFs at =
UTC 24:00.
- 2013-06-27 (Thursday): Preliminary agenda published for comment.
- 2013-07-01 (Monday): Cutoff date for requests to reschedule Working Group=
 and BOF meetings UTC 24:00.
- 2013-07-05 (Friday): Final agenda to be published.
- 2013-07-17 (Wednesday): Draft Working Group agendas due by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-07-22 (Monday): Revised Working Group agendas due by UTC 24:00, uplo=
ad using IETF Meeting Materials Management Tool.
- 2013-08-30 (Friday): Proceedings submission cutoff date by UTC 24:00, upl=
oad using IETF Meeting Materials Management Tool.
- 2013-09-18 (Wednesday): Proceedings submission corrections cutoff date by=
 UTC 24:00, upload using IETF Meeting Materials Management Tool.

Submitting Requests for Working Group and BOF Sessions

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

The URL for the tool is:

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

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

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the agenda=
s for your Working Group sessions as early as possible.  Draft Working Grou=
p agendas are due Wednesday, July 17, 2013 at UTC 24:00.  Revised Working G=
roup agendas are due no later than Monday, July 22, 2013 at UTC 24:00.  The=
 proposed agenda for a BOF session should be submitted along with your requ=
est for a session.  Please be sure to copy your Area Director on that messa=
ge.

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

The URL for the tool is:

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

Additional information about this tool is available at:

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

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

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

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

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

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

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

Instructions for using the tool are available at:

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

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

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

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

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

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

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

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


    b. AREA under which Working Group or BOF appears:

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

    d. Expected Attendance:

    e. Special requests:

    f. Number of sessions:

    g. Length of session: =

       - 1 hour =

       - 1 1/2 hours
       - 2 hours =

       - 2 1/2 hours

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

IETF Chair =

Jari Arkko <jari.arkko@piuha.net>

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

Internet Area (int) =

Brian Haberman <brian@innovationslab.net> =

Ted Lemon <ted.lemon@nominum.com>

Operations & Management Area (ops) =

Benoit Claise <bclaise@cisco.com> =

Joel Jaeggli <joelja@bogus.com>

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


Routing Area (rtg) =

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


Security Area (sec) =

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


Transport Area (tsv) =

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

 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
86th IETF Meeting Attendance Number

6man - 96
abfab - 34
alto  - 36
appsawg - 98
avtcore - 57
avtext - 61
behave - 45
bmwg - 24
ccamp - 87
ccamp (2nd session) - 51
ccamp (3rd session) - 32
cdni - 51
cdni (2nd session) - 49
cfrg (RG) - 35
clue - 53
clue (2nd session) - 50
core - 67
core (2nd session) - 49
dhc - 54
dime - 24
dispatch - 66
dmm - 30
dnsop - 50
ecrit - 39
eman - 28
emu - 24
forces - 41
grow - 49
homenet - 137
httpauth - 64
httpbis - 79
i2rs - 228
iccrg (RG) - 97
icnrg (RG) - 76
idr - 80
intarea (AG) - 72
ipfix - 19
ippm - 44
ippm (2nd session) - 36
ipsecme - 47
IRTF Open Meeting - 63
isis - 46
jose - 65
karp - 29
l2vpn - 103
l3vpn - 82
lwig - 39
manet - 23
mboned - 24
mif - 40
mile - 39
mmusic - 92
mmusic (2nd session) - 61
mpls - 114
mpls (2nd session) - 107
mptcp - 43
multimob - 32
ncrg (RG) - 73
netconf - 67
nfsv4 - 13
nmrg (RG) - 15
nvo3 - 226
oauth - 42
oauth (2nd session) - 44
opsawg - 88
opsec - 32
ospf - 26
p2psip - 27
paws - 32
pce - 99
pcp - 43
pcp (2nd session) - 33
pim - 24
pkix - 50
precis - 27
pwe3 - 77
radext - 22
rmcat - 82
roll - 63
rtcweb - 170
rtcweb (2nd session) - 137
rtgarea (AG) - 51
rtgwg - 117
saag (AG) - 115
sacm - 48
scim - 25
sdnrg (RG) - 265
sidr - 69
sidr (2nd session) - 57
siprec - 27
softwire - 75
softwire (2nd session) - 66
straw - 26
sunset4 - 82
tcpm - 39
tictoc - 26
tls - 76
trill - 55
tsvarea (AG) - 160
tsvwg - 94
tsvwg (2nd session) - 54
v6ops - 157
v6ops (2nd session) - 113
websec - 68
weirds - 55
weirds (2nd session) - 25
wpkops - 34
xmpp - 23
xrblock - 27
